There is a script to automate Murano installation onto devbox.
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 required branch (e.g.master)
># cd /opt/git/murano-deployment ># git checkout -b master origin/master
Install prerequisites
># cd /opt/git/murano-deployment/devbox-scripts ># ./murano-git-install.sh prerequisites
Configure the following parameters in lab binding configuration file /etc/murano-deployment/lab-binding.rc
LAB_HOST - IP or nostname of the lab. Actually, this address/name should point to the host where Keystone is installed.
ADMIN_USER - OpenStack admin user
ADMIN_PASSWORD - A password for OpenStack admin user
RABBITMQ_USER - User to connect to RabbitMQ host
RABBITMQ_PASSWORD - Password for that user
RABBITMQ_VHOST - vHost which will be used by Murano components. Provides additional layer of isolation from other devboxes.
RABBITMQ_HOST - (optional) IP address or hostname of the host where RabbitMQ is installed IF it is not the same host as LAB_HOST points to
RABBITMQ_HOST_ALT - (optional) IP address or hostname of the RabbitMQ host to connect from inside the Windows instance. In some cases the addresses like LAB_HOST or RABBITMQ_HOST are inaccessible from instances, and they must use different address.
FILE_SHARE_HOST - (optional) IP address or hostname of the host where file share with prerequisites is located IF it is not the same host as LAB_HOST points to.
BRANCH_NAME - branch name from which all Murano components will be fetched for installation
SSL_ENABLED - Set 'true' if OpenStack is configured with SSL support and 'false' otherwise.
SSL_CA_FILE - Path to CA certificate for certificate validation on client side.
Install Murano components
># ./murano-git-install.sh install
Login to the Dashboard using URL http://<your VM IP>/dashboard or http://<your VM IP>/horizon