Solum/solum m2 demo

Solum Milestone 2 Demo

The Solum M2 Demo represents the longer term program direction and does not represent currently implemented Solum features.

Solum Demo Vagrant Installation Instructions

These installation instructions were tested on Mac OSX v10.7.5 and OSX 10.8.5

1. Install Vagrant (http://www.vagrantup.com/downloads.html). Tested with Vagrant v1.5.4

2. Make a directory for the two repositories, and activate the demo UI. This demo uses the ~/Solum_Demo directory.

mkdir ~/Solum-Demo
cd ~/Solum-Demo
git clone https://github.com/rackerlabs/vagrant-solum-dev.git vagrant
git clone https://github.com/rackerlabs/solum-m2demo-ui.git m2demo
export WEBGUI=`pwd`/m2demo

For those who prefer to use VMs instead of Docker containers (the default).

export SOLUM_IMAGE_FORMAT=vm # Add only if you don't want Docker containers

3. Create the demo environment on your system:

cd vagrant
vagrant up

NOTE: This may take between about 15 and 60 minutes to install, depending on the speed of your machine and network.

4. Add a route so the demo app can be seen from your host machine:

sudo route add -net 192.168.78.0/24 192.168.76.11

5. Browse to this URL to see the demo: (http://192.168.76.11:9001/solum/)

Common Vagrant Commands

vagrant halt --- Stops the running vagrant but doesn't delete anything
vagrant up --provision --- Restarts a halted vagrant, and runs all provisioning scripts, including devstack in our case. Please note that this option will likely fail until the Vagrant scripts are updated. vagrant destroy and then vagrant up is the most reliable option right now.
vagrant destroy --- Deletes the vagrant and all data (be careful!)

Navigating the Vagrant Screen Sessions

To log into the Vagrant session, use vagrant ssh
To list the screen sessions available use screen -ls
To connect to a given screen, screen -x bridge for example (it works as long as the name is an unambiguous subset of one screen session's name)

Pulling Down Latest Demo Code

Git pull new code from solum-m2demo-ui

Note: This should be all that is needed but in some cases, Django may need to be restarted to pick up the new code. In this case:

Go to the vagrant directory where Vagrantfile exists
vagrant ssh
screen -x bridge
Control-C to stop Django
Up arrow and enter to re-run the command (which is: python ./manage.py runserver 0.0.0.0:9001)
Control-A Control-D to detach