diff --git a/src/developers-guide/pom.xml b/src/getting-started/pom.xml
similarity index 79%
rename from src/developers-guide/pom.xml
rename to src/getting-started/pom.xml
index a75b137..1f00f43 100644
--- a/src/developers-guide/pom.xml
+++ b/src/getting-started/pom.xml
@@ -19,10 +19,10 @@
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
4.0.0com.mirantis.murano
- developers-guide
+ murano-getting-started-guide1.0.0-SNAPSHOTjar
- Murano Project Documentation
+ Murano Deployment Guide
@@ -40,13 +40,6 @@
true100
-
-
-
-
-
-
-
diff --git a/src/getting-started/src/docbkx/content/before_you_begin.xml b/src/getting-started/src/docbkx/content/before_you_begin.xml
new file mode 100644
index 0000000..659ace9
--- /dev/null
+++ b/src/getting-started/src/docbkx/content/before_you_begin.xml
@@ -0,0 +1,1056 @@
+
+
+
+ About Murano
+
+ About Murano
+ Murano is a new service which allows a non-experienced user to deploy reliable Windows based environments in a “push-the-button” manner. The key goal is to provide a UI and API enabling the deployment and operation of Windows Environments at the Windows Services abstraction level. The service is able to orchestrate complex circular dependent cases in order to set up a complex Windows Environment with multiple dependant services.
+
+ The service addresses following use cases:
+
+
+ Self-provisioning of predefined Windows services with their dependencies
+
+
+ Automation of administrative tasks during data center roll-out
+
+
+ Custom windows application as a windows service
+
+
+
+ The solution provides higher level of abstraction for manipulation Windows Environments. Key concepts are:
+
+
+ Windows Service - a service such as Active Directory, MSSQL, or IIS, which usually consists of multiple virtual machines and has multiple dependencies.
+
+
+ Windows Environment - a logical unit for all Services and represents a classical Windows Datacenter
+
+
+ Windows VM instance - a VM which hosts a Windows Service. A Windows Service might be deployed over several Windows VM instances.
+
+
+
+ The Key Features of the Service are the following:
+
+
+ Native to OpenStack
+
+
+ Introduces abstraction level for Windows Environments
+
+
+ Supports Availability Zones and Disaster Recovery scenarios
+
+
+ Uses native Windows features for HA solutions
+
+
+
+
+ Before You Begin
+
+
+ Naming Conventions
+ To clearly separate commands and parts of configuration files we use boxes, like shown below:
+
+
+ ...# Part of config file here...
+
+
+ All commands start either with ‘>$’ mark or with ‘>#’ mark. The difference is that first should be executed as regular user, while second - as superuser (‘root’).
+
+
+ >$ echo ‘Execute this command as regular user’
+
+
+
+ ># echo ‘Execute this command as root’
+
+
+
+
+ Use Appropriate Branch
+ There are a few branches that can be found in all Murano repositories: master, release-0.1, release-0.2 and so on. Branch master is the most recent between the releases, but not as stable as release-x.x branches.
+
+
+ Use Separate vHost in RabbitMQ
+ In general it is OK to configure Murano services to use the root (‘/’) vHost in RabbitMQ and use the same user credentials as OpenStack services use.
+
+ However, we recommend to create a separate vHost with separate user for each Murano devbox. There are a few reasons for that:
+
+
+ this prevents queue name collisions
+
+
+ this prevents message stealing from queues
+
+
+ this simplify debugging
+
+
+
+ If you are planning to use only one devbox then you may stay with ‘/’ vHost.
+
+ Steps required to configure your own vHost are described in RabbitMQ Configuration Notes.
+
+
+ System Requirements
+
+
+ OpenStack Lab
+
+
+ Supported OS
+
+
+ Ubuntu Server 12.04 x64
+
+
+
+
+ Hardware Requirements
+
+
+ CPU: 8+ cores
+
+
+ RAM: 12+ GB
+
+
+ HDD (select any option)
+
+
+ NIC: 1x Ethernet 1+ Gbps
+
+
+
+
+ Software Requirements
+
+
+ Heat installed
+
+
+ Denis Koryavov:This is Getting Started Guide, so is better to create an instruction how to create vhost in RabbitMQ.RabbitMQ configured (+ additional vhosts and user accounts)
+
+
+ Windows Server 2012 Standard image imported into Glance (described later)
+
+
+ Samba share with prerequisites (described later)
+
+
+ OpenStack metadata service.
+
+
+
+
+ Devbox
+ We suggest to use virtual machine for Murano, as it allows you to backup your VM easily.
+
+ Any type of hypervisor software which supports linux as guest OS could be used.
+ KVM, VMWare and VirtualBox were tested with success.
+
+ There is a Murano VM section in Appendix which contains steps to build your own VM.
+
+
+ Supported OS
+
+
+ Ubuntu Server 12.04 LTS x86_64
+
+
+ CentOS 6.4 x86_64
+
+
+
+
+ Hardware Requirements
+
+
+ RAM: 512 MB
+
+
+ CPU: 1 core
+
+
+ HDD: 20 GB
+
+
+ 1 NIC
+
+
+
+
+ Software Requirements
+
+
+ Packages:
+
+
+ X Server is NOT required and system runlevel 3 is preferred.
+
+
+
+
+ Setup Lab Environment
+
+
+ Install OpenStack
+ You need a working installation of OpenStack first. It could be your own installation which meets the requirements, or a new one using the installation method provided below.
+
+
+ Using Devstack
+ Currently the most simple way to build a lab is to use devstack.
+
+ The steps are quite simple:
+
+
+ Install and configure OS on your hardware. The recommended OS is Ubuntu Server 12.04 x64. Minimal configuration would be enough.
+
+
+ Install all the latest updates.
+
+
+
+ ># apt-get update># apt-get -y upgrade
+
+
+
+ Create a user stack
+
+
+
+ ># adduser stack
+
+
+
+ Add user stack to sudoers
+
+
+
+ ># echo ‘stack ALL=(ALL) NOPASSWD:ALL' > /etc/sudoers.d/stack># chmod 0440 /etc/sudoers.d/stack
+
+
+
+ Create a folder for OpenStack installation files
+
+
+
+ ># mkdir /opt/stack># chown stack:stack /opt/stack
+
+
+
+ Clone the devstack repo
+
+
+
+ ># su stack>$ cd>$ git clone https://github.com/openstack-dev/devstack.git
+
+
+
+ Checkout the stable/grizzly branch
+
+
+
+ >$ cd devstack>$ git checkout stable/grizzly
+
+
+
+ Get localrc and local.sh files
+
+
+
+ >$ wget https://raw.github.com/stackforge/murano-deployment/release-0.2/getting-started/localrc -O localrc>$ wget https://raw.github.com/stackforge/murano-deployment/release-0.2/getting-started/local.sh -O local.sh>$ chmod +x local.sh
+
+
+
+ Start devstack
+
+
+
+ >$ ./stack.sh
+
+
+
+ When stack.sh finishes execution your OpenStack installation is ready.
+
+
+
+
+ Prepare Shared Prerequisites
+
+
+ Configure Samba Share
+
+
+ Install SAMBA
+
+
+
+ ># apt-get update># apt-get install samba
+
+
+
+ Create shared folder
+
+
+
+ ># mkdir -p /opt/samba/share># chown nobody:nogroup /opt/samba/share
+
+
+
+ Edit /etc/samba/smb.conf
+
+
+
+ ...[global] ... security = user...[share] comment = Deployment Share path = /opt/samba/share browsable = yes guest ok = yes guest account = nobody read only = no create mask = 0755
+
+
+
+ Restart services
+
+
+
+ ># restart smbd># restart nmdb
+
+
+
+ Copy Prerequisites Into The Share
+
+
+ Create folder structure
+
+
+
+ ># mkdir -p “/opt/samba/share/Prerequisites/IIS”># mkdir -p “/opt/samba/share/Prerequisites/SQL Server/2012”># mkdir -p “/opt/samba/share/Prerequisites/SQL Server/Tools”
+
+
+
+ Add files to the folder structure under /opt/samba/share folder:
+
+
+
+
+ Build Windows Image
+ A pre-built Windows Image is required to create environments in Murano. Because of its size it’s better to build the image on the same host where OpenStack is installed.
+
+ This section describe steps required to build such an image.
+
+
+ Prepare Build Environment
+
+
+ Samba should be already installed (See Configure samba share)
+
+
+ Clone murano-deployment repository
+
+
+
+ ># cd /opt/git># git clone git://github.com/stackforge/murano-deployment.git
+
+
+
+ Change directory to murano-deployment/image-builder folder
+
+
+
+ ># cd /opt/git/murano-deployment/image-builder
+
+
+
+ Create folder structure for image builder
+
+
+
+ ># make build-root
+
+
+
+ Add files into folder structure under /opt/image-builder folder:
+
+
+ Test that all required files are in place
+
+
+
+ ># make test-build-files
+
+
+
+ Build The Image
+
+
+ Get list of supported images
+
+
+
+ ># make
+
+
+
+ Run image build process
+
+
+
+ ># make ws-2012-std
+
+
+
+ Wait until process finishes
+
+
+ The image file ws-2012-std.qcow2 will be stored in /opt/image-builder/share/images folder.
+
+
+
+
+ Import Windows Image Into Glance
+ Now when you’ve built a Windows Image it must be imported into Glance.
+
+
+
+ Import openrc file which contains environment variables definitions required by OpenStack components
+
+
+
+ >$ source openrc
+
+
+
+ Import the Windows Server 2012 image into Glance
+
+
+
+ >$ cd /opt/image-builder/share/images>$ glance image-create \ --name ws-2012-std \ --disk-format qcow2 \ --container-type bare \ --file ws-2012-std.qcow2 \ --is-public true \ --property murano_image_info='{"type":"ws-2012-std",\ "title":"Windows Server 2012 Standard"}'
+
+
+ WARNING: the value of the --property argument named murano_image_info is a JSON string. Only double quotes are valid in JSON, so please type the string exactly as in the example above.
+
+
+ Setup Devbox
+ There are a few ways to install Murano devbox
+
+
+ using Vagrant automation tool
+
+
+ using a script to install all components automatically
+
+
+ install everything manually
+
+
+
+ NOTE: The preferred way is to use script for automated installation. It is described in Automated Way section below.
+
+
+ Vagrant Way
+ There is a simple way to get working Murano devbox. This could be done using Vagrant tool.
+
+
+ Prepare Environment
+
+
+ Ubuntu
+
+
+ Install VirtualBox:
+
+
+
+ ># apt-get install virtualbox
+
+
+
+ Install VirtualBox Extension tsufiev:Where is the command for Extension Pack or instructions (if you mean Guest Additions)?Dmitry Teselkin:No, I mean Extension Pack. There is no simple command, the easiest way is to download it from the site and "run it" - VirtuaBox will open the file and imports the pack.tsufiev:Ok, let's leave it as an exercise to the user :)Pack.
+
+
+ Install Vagrant:
+
+
+
+ ># apt-get install vagrant tsufiev:Actually, it is called --no-install-recommendsDmitry Teselkin:Thanks, fixed--no-install-recommends
+
+
+
+ Upgrade the Vagrant:
+
+
+
+ ># wget http://files.vagrantup.com/packages/7ec0ee1d00a916f80b109a298bab08e391945243/vagrant_1.2.7_x86_64.deb
+
+
+
+
+
+ ># dpkg --install vagrant_1.2.7_x86_64.deb
+
+
+
+ Launch The Box
+
+
+ Clone murano-vagrant repository
+
+
+
+ >$ git clone https://github.comakuznetsova:I think you should change this repositoryDmitry Teselkin:I will, laterDmitry Teselkin:Done/stackforge/murano-deployment.git
+
+
+
+ Change directory to cloned repository folder
+
+
+
+ >$ cd murano-deployment/getting-started>$ git checkout -b release-0.2 origin/release-0.2
+
+
+
+ IMPORTANT STEP: Edit the lab-binding.rc file - replace all the markers ‘***’ tsufiev:It is reasonable to show here lab-binding.rc with places to be filled - or provide the link to the lab-binding.rc in text below.Dmitry Teselkin:Doneto your settings. For example:
+
+
+
+ ...# Lab Settings#-------------# Address of the host which provides Keystone service.## LAB_HOST='192.168.1.2'LAB_HOST='***.***.***.***'...
+
+
+
+ Launch the box:
+
+
+
+ >$ ./launch-the-box.sh
+
+
+
+ The script will do the following:
+
+
+ Vagrant will do the rest:
+
+
+ When everything is done open thehttp://127.0.0.1:8080/horizon link.
+
+
+
+
+ <note><remark>Denis Koryavov:</remark></note><note><remark>It is necessary to write that this way is recommended and Manual Way should be used ONLY if something got wrong with automated way.</remark></note>Automated Way
+
+ Denis Koryavov:
+
+
+ It is necessary to write that this way is recommended and Manual Way should be used ONLY if something got wrong with automated way.
+
+ Build your VM using instructions from Murano VM first.
+
+
+
+ Create a folder to hold cloned repositories
+
+
+
+ ># mkdir -p /opt/git
+
+
+
+ Clone murano-deployment repository
+
+
+
+ ># cd /opt/git># git clone git://github.com/stackforge/murano-deployment.git
+
+
+
+ Change directory to murano-deployment and switch to release-0.2 branch
+
+
+
+ ># cd /opt/git/murano-deployment># git checkout -b release-0.2 origin/release-0.2
+
+
+
+ Install prerequisites
+
+
+
+ ># cd /opt/git/murano-deployment/devbox-scripts># ./murano-git-install.sh prerequisites
+
+
+
+ Configure lab binding configuration file /etc/murano-deployment/lab-binding.rc
+
+
+
+ LAB_HOST='***Denis Koryavov:I think there should be an other address..***.***.***'AUTH_URL="http://$LAB_HOST:5000/v2.0"ADMIN_USER='admin'ADMIN_PASSWORD='***'RABBITMQ_LOGIN='tsufiev:Is it really 'muranouser' and not 'murano' we use on our devboxes?muranouser'RABBITMQ_PASSWORD='murano'RABBITMQ_VHOST=tsufiev:Considering that most users are an idiots (or like me :)), I'd stress that 'muranovhost' must already exist.'muranovhost'BRANCH_NAME='release-0.Igor Yozhikov:In the release-0.2 default BRANCH_NAME='master' instad of 'release-0.2'2'
+
+
+ Please remember that recommend to Use separate vHost in RabbitMQ
+
+
+ Install Murano components
+
+
+
+ ># ./murano-git-install.sh install
+
+
+
+ Login to the Dashboard using URL http://<your VM IP>/dashboard
+
+
+
+
+ Manual Way
+ Build your VM using instructions fromDenis Myznikov:Link in nowhereDmitry Teselkin:Fixed Murano VM first.
+
+ Package for Ubuntu and CentOS already in progress and will soon be accessible for users. While they are not available, we provide information about how to get and install all murano services from source code below. We made setup scripts for automated installation of our products which accepts install and uninstall command line arguments. Service startup jobs are handled by Upstart.
+ At first we need to create some kind of working directory.
+
+ NOTE: All installation steps require the superuser rights.
+
+
+ ># mkdir -p /opt/git && cd /opt/git
+
+ NOTE: Please, track actual projects stable branch, at the time of writing current stable branch is - release-0.2
+
+
+ Murano-Api
+
+
+ Get source code
+
+
+
+ ># git clone https://github.com/stackforge/murano-api -b release-0.2># chmod +x murano-api/setup*.sh
+
+
+
+ Install the component
+
+
+
+ ># murano-api/setup.sh install
+
+
+
+
+
+ ># murano-api/setup-centos.sh install
+
+
+ Configuration:
+
+ ># cd /etc/murano-api && cp murano-api-paste.ini.sample murano-api-paste.ini># cd /etc/murano-api && cp murano-api.conf.sample murano-api.conf
+
+ NOTE: Denis Myznikov:IMHO need add 2 lines - vi murano-api-paste.ini and vi murano-api.conf for better understandingBefore start service, set proper configuration values in configuration files mentioned above.
+
+ tsufiev:Looks like step-by-step instructions. Imagine the user saying to himself: why the hell am i doing this?! ))))Service control:
+
+ ># start murano-api># stop murano-api># restart murano-api># status murano-api
+
+
+
+ Murano-Conductor
+
+
+ Get source code
+
+
+
+ Denis Myznikov:Need to add "cd /opt/git/"># git clone https://github.com/stackforge/murano-conductor -b release-0.2># chmod +x murano-conductor/setup*.sh
+
+
+
+ Install the component
+
+
+
+ ># murano-conductor/setup.sh install
+
+
+
+ on CentOS
+
+
+
+ ># murano-conductor/setup-centos.sh install
+
+ Configuration
+
+ ># cd /etc/murano-conductor && cp conductor-paste.ini.sample conductor-paste.ini># cd /etc/murano-conductor && cp conductor.conf.sample conductor.conf
+
+ NOTE: Denis Myznikov:IMHO also line - vi conductor.conf, no need to edit the file conductor-paste.initsufiev:Also, s/start/starting the/Before start service, set proper configuration values in configuration files mentioned Denis Myznikov:and start the service by command ># start murano-conductorabove.
+
+ Service control:
+
+ ># start murano-conductor># stop murano-conductor># restart murano-conductor># status murano-conductor
+
+
+
+ Murano-Dashboard
+ At first, Install OpenStack dashboard(Horizon) and dependent packages.
+
+ How-to do this:
+
+
+ On Ubuntu
+
+
+
+ ># apt-get install -y memcached libapache2-mod-wsgi openstack-dashboard># dpkg --purge openstack-dashboard-ubuntu-theme # optional step
+
+ After install is complete, openstack dashboard should be available at: http://<your VM IP>/horizon
+
+
+
+ On CentOS
+
+
+
+ ># yum install python-netaddr.noarch python-keystoneclient.noarch python-django-horizon.noarch python-django-openstack-auth.noarch httpd.x86_64 mod_wsgi.x86_64 openstack-dashboard.noarch --assumeyes># chkconfig httpd on
+
+ After install complete, openstack dashboard should be available at: http://<your VM IP>/dashboard
+
+ Installation of the murano-dashboard is described below.
+
+
+ Get source code
+
+
+
+ ># git clone https://github.com/stackforge/murano-dashboard -b release-0.2># chmod +x murano-dashboard/setup*.sh
+
+
+
+ Install the component
+
+
+
+
+
+
+ ># murano-dashboard/setup.sh install
+
+
+
+
+
+ ># murano-dashboard/setup-centos.sh install
+
+
+
+ Murano Services Configuration
+
+
+ RabbitMQ Configuration Notes
+ OpenStack rabbitMQ credentials could be used for murano services, but prefered way is to make additional changes into rabbitMQ configuration, like own vhost, login and password. These steps require superuser rights and should be run on the OpenStack controller node where rabbitMQ service resides.
+
+ How to do this:
+
+ ># rabbitmqctl add_user muranouser muranopassword># rabbitmqctl set_user_tags muranouser administrator># rabbitmqctl add_vhost muranovhost># rabbitmqctl set_permissions -p muranovhost muranouser ".*" ".*" ".*"
+
+
+
+ Keystone Configuration Notes
+ Service entry for murano-api and endpoint associated with it could also be configured in the keystone. If there is no record about murano-api in the keystone murano-dashboard would try to reach murano-api service at localhost on the default murano-api port 8082.
+
+ How to add service record into the keystone using python keystone client:
+
+ ># keystone service-create --name muranoapi --type murano --description "Murano-Api Service"
+
+ This command returns UUID of the created service record, which should be used below.
+
+
+ ># keystone endpoint-create \ --region RegionOne \ --service-id UUID_from_above \ --publicurl http://murano_vm_address:8082 \ --internalurl http://murano_vm_address:8082 \ --adminurl http://murano_vm_address:8082
+
+
+
+ Murano-Api
+ Configuration files of the murano-api service reside at /etc/murano-api directory. Basic configuration parameters are listed below.
+
+
+ murano-api.conf
+
+
+
+ [DEFAULT]...bind_host = 0.0.0.0bind_port = 8082log_file = /var/log/murano-api.log...…[database]...#connection = mysql://mysqluser:mysqlpassword@mysqlhost:3306/muranoconnection = sqlite:////etc/murano-api/murano.sqlite…...[rabbitmq]host = <rabbitmq ip>port = 5672login = <rabbitmq login>password = <rabbitmq password>virtual_host = <rabbitmq vhost>...
+
+
+
+ murano-api-paste.ini
+
+
+
+ ...[filter:authtoken]auth_host = <keystone_ip>auth_port = 35357auth_protocol = httpadmin_tenant_name = adminadmin_user = adminadmin_password = admin_password...
+
+
+
+ Murano-Conductor
+ Configuration files of the murano-conductor service reside at /etc/murano-conductor directory. Basic configuration parameters are listed below:
+
+
+ conductor.conf
+
+
+
+ [DEFAULT]…log_file = /var/log/murano-conductor.log……[keystone]# URL of OpenStack KeyStone service REST API.# Typically only hostname (or IP) needs to be changedauth_url = http://keystone_ip:5000/v2.0......[rabbitmq]host = <rabbitmq ip>port = 5672login = <rabbitmq login>password = <rabbitmq password>virtual_host = <rabbitmq vhost>...
+
+
+
+ conductor-paste.ini
+
+
+ It’s empty but must exist.
+
+
+ Murano-Dashboard
+ Murano-dashboard does not need to be configured, but we need to set up proper OPENSTACK_HOST variable in the OpenStack dashboard configuration file, which resides at /etc/openstack-dashboard directory. It should point to the OpenStack controller node.
+
+
+ …# optional, but sometimes very useful to set DEBUG to ‘True’DEBUG = True...OPENSTACK_HOST = “openstack_controller_address” ...
+
+
+
+ Troubleshooting
+ Set debug options to "true" in all config files - dashboard, api, conductor.
+
+ NOTE: the following debug sequence should be used when you have no idea about why the system isn't working. If you have one, you may skip unnecessary sections.
+
+ First, stop both murano-api and murano-conductor services. We will start them one by one from the console.
+
+
+ Murano-Api
+
+
+ Open new console
+
+
+ Start api service manually
+
+
+
+ ># murano-api --config-dir /etc/murano-api > /var/log/murano-api-live.log &># tailf /var/log/murano-api-live.log
+
+
+
+ Open dashboard, create and send to deploy some simple environment.
+
+
+ Open RabbitMQ web console, open your vhost and ensure that queues were created and there is at least one message.
+
+
+ Check log for errors - there shouldn't be any
+
+
+ Keep murano-api service running.
+
+
+
+
+ Murano-Conductor
+
+
+ Open new console
+
+
+ Start conductor from console
+
+
+
+ ># muranoconductor --config-dir /etc/murano-conductor > /var/log/murano-conductor-live.log &># tailf /var/log/murano-conductor-live.log
+
+
+
+ Check that there is no python exceptions in the log. Some errors like 404 are ok, as conductor tries to delete environment that doesn't exist.
+
+
+ Check heat stack status. It should not be in FAILED state. If it is - check heat and nova error log to find the cause.
+
+
+ Keep murano-conductor service running.
+
+
+
+ Now, the environment should be created, and instance(s) launched.
+
+ Next, check if instances were configured correctly by the cloudbase init tool.
+
+ Log in to any instance and open powershell log file at C:\Murano\PowerShell.log. There shouldn't be any exceptions logged. Other symptoms of successful configuration is that the instance was renamed and you have to press <Ctrl>+<Alt>+<Del> to log into. Unconfigured instance has autologon enabled for the first logon, so if console is open, the instance is not configured (yet).
+
+ Check that Murano Agent has correct config file. If there is a .bak file, then it was changed by the init script. Check the file, ensure that it has correct values.
+
+ Check Murano Agent log file. There should be logged all tasks received by the agent from the conductor.
+
+ Check PowerShell log. There should be messages about all functions, executed on the instance.
+
+
+ Log files
+
+
+ Murano Log Files
+
+
+ /var/log/murano-api.log
+
+
+ /var/log/murano-conductor.log
+
+
+ akuznetsova:Also need to add info about new log file for dashboardtsufiev:Should be fixed for releases >0.2/var/log/apache2/errors.log
+
+
+ /var/log/httpd/errors.log
+
+
+
+
+ Windows Log Files
+
+
+ C:\Murano\PowerShell.log
+
+
+ C:\Murano\Agent\log.txt
+
+
+
+
+ Appendix
+
+
+ Murano VM
+ NOTE: Your VM MUST be attached to the network with Internet and openstack management network (lab network) access.
+
+
+ Ubuntu Server 12.04 LTS x86_64
+ Installation steps:
+
+
+ Install minimal version of the system
+
+
+ When prompted, mark OpenSSH Server to be installed
+
+
+ Login as root
+
+
+ Enable Cloud Archive repository
+
+
+ Update installed OS and packages
+
+
+
+
+
+ Add lines below to the /etc/apt/sources.list.d/grizzly.list file
+
+
+
+ deb http://ubuntu-cloud.archive.canonical.com/ubuntu precise-updates/grizzly maindeb http://archive.gplhost.com/debian grizzly maindeb http://archive.gplhost.com/debian grizzly-backports main
+
+
+
+
+ Update the system
+
+
+
+ ># apt-get update># apt-get install ubuntu-cloud-keyring># apt-get install gplhost-archive-keyringDenis Koryavov:Maybe add # reboot after this command?Denis Myznikov:No. It works.># apt-get upgrade
+
+
+
+ Install additional packages
+
+
+
+ ># apt-get install mc unzip git make gcc python-setuptools python-pip
+
+
+
+ CentOS 6.4 x86_64
+ Installation steps:
+
+
+ Install minimal version of the system.
+
+
+ When prompted, mark OpenSSH Server to be installed
+
+
+ Login as root
+
+
+ Enable RedHat Openstack and Epel repository
+
+
+ Update installed OS and packages
+
+
+
+
+ Add repositories and update OS
+
+
+
+ ># yum install -y http://rdo.fedorapeople.org/openstack/openstack-grizzly/rdo-release-grizzly.rpm># yum install -y http://mirror.yandex.ru/epel/6/x86_64/epel-release-6-8.noarch.rpm># yum update># yum upgrade
+
+
+
+ Install additional packages
+
+
+
+ ># yum install mc unzip git make gcc python-setuptools python-pip upstart
+
+ Most of dependent packages will be installed automatically with setup scripts.
+
+ NOTE: Some words about pip (python-pip) version. In order to have proper versions of python dependency packages installed, pip version MUST be 1.4 or higher!
+
+ How-to determine python-pip version:
+
+ ># pip --version
+
+
+ How-to upgrade pip to latest version:
+
+ ># pip install --upgrade pip
+
+ or
+
+ ># pip install https://pypi.python.org/packages/source/p/pip/pip-1.4.1.tar.gz
+
+
+ NOTE: you should pay attention to python-pip after upgrade to version 1.4, because its filesystem location can change from /usr/bin/pip to /usr/local/bin/pip !
+
+ How to handle this situation:
+
+ ># rm /usr/bin/pip># ln -s /usr/local/bin/pip /usr/bin/pip
+
+
+
+
\ No newline at end of file
diff --git a/src/user-guide/src/docbkx/content/murano-dashboard.xml b/src/user-guide/src/docbkx/content/murano-dashboard.xml
index 680c0ff..833d8e6 100644
--- a/src/user-guide/src/docbkx/content/murano-dashboard.xml
+++ b/src/user-guide/src/docbkx/content/murano-dashboard.xml
@@ -300,7 +300,7 @@
- You can login to the virtual machine directly from the horizon (if you Openstack installation allows you) or by RDP protocol.
+ You can login to the virtual machine directly from the horizon (if your Openstack installation allows you) or by RDP protocol.
diff --git a/src/user-guide/src/docbkx/images/deployment_configuration.png b/src/user-guide/src/docbkx/images/deployment_configuration.png
new file mode 100644
index 0000000..c80737e
Binary files /dev/null and b/src/user-guide/src/docbkx/images/deployment_configuration.png differ
diff --git a/src/user-guide/src/docbkx/images/deployment_logs.png b/src/user-guide/src/docbkx/images/deployment_logs.png
new file mode 100644
index 0000000..72a587f
Binary files /dev/null and b/src/user-guide/src/docbkx/images/deployment_logs.png differ
diff --git a/src/user-guide/src/docbkx/images/deployments.png b/src/user-guide/src/docbkx/images/deployments.png
new file mode 100644
index 0000000..adceb9a
Binary files /dev/null and b/src/user-guide/src/docbkx/images/deployments.png differ
diff --git a/src/user-guide/src/docbkx/images/env_delete.png b/src/user-guide/src/docbkx/images/env_delete.png
new file mode 100644
index 0000000..72959f3
Binary files /dev/null and b/src/user-guide/src/docbkx/images/env_delete.png differ
diff --git a/src/user-guide/src/docbkx/images/env_edit.png b/src/user-guide/src/docbkx/images/env_edit.png
new file mode 100644
index 0000000..ffcdce2
Binary files /dev/null and b/src/user-guide/src/docbkx/images/env_edit.png differ
diff --git a/src/user-guide/src/docbkx/images/env_edit2.png b/src/user-guide/src/docbkx/images/env_edit2.png
new file mode 100644
index 0000000..cfa072a
Binary files /dev/null and b/src/user-guide/src/docbkx/images/env_edit2.png differ
diff --git a/src/user-guide/src/docbkx/images/env_show.png b/src/user-guide/src/docbkx/images/env_show.png
new file mode 100644
index 0000000..53ed12f
Binary files /dev/null and b/src/user-guide/src/docbkx/images/env_show.png differ
diff --git a/src/user-guide/src/docbkx/images/instance_console.png b/src/user-guide/src/docbkx/images/instance_console.png
new file mode 100644
index 0000000..a16b0aa
Binary files /dev/null and b/src/user-guide/src/docbkx/images/instance_console.png differ
diff --git a/src/user-guide/src/docbkx/images/name_link.png b/src/user-guide/src/docbkx/images/name_link.png
new file mode 100644
index 0000000..979346f
Binary files /dev/null and b/src/user-guide/src/docbkx/images/name_link.png differ
diff --git a/src/user-guide/src/docbkx/images/service_delete.png b/src/user-guide/src/docbkx/images/service_delete.png
new file mode 100644
index 0000000..3b30198
Binary files /dev/null and b/src/user-guide/src/docbkx/images/service_delete.png differ
diff --git a/src/user-guide/src/docbkx/user-guide.xml b/src/user-guide/src/docbkx/user-guide.xml
index 68af2a7..c1cbbeb 100644
--- a/src/user-guide/src/docbkx/user-guide.xml
+++ b/src/user-guide/src/docbkx/user-guide.xml
@@ -50,7 +50,7 @@
This document is intended for individuals who wish to
- use our product or intend to contribute.
+ use Murano Product.