Difference between revisions of "Solum/solum m2 demo"
< Solum
Ed Cranford (talk | contribs) (Formatting and rewording) |
|||
Line 4: | Line 4: | ||
=== Solum Demo Vagrant Installation Instructions === | === Solum Demo Vagrant Installation Instructions === | ||
− | '' | + | ''These installation instructions were tested on Mac OS X v10.7.5.'' |
− | * Install Vagrant (http://www.vagrantup.com/downloads.html) | + | * Install Vagrant (http://www.vagrantup.com/downloads.html). ''Tested with Vagrant v1.5.4'' |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | + | * Make a directory for the two repositories, and activate the demo UI. ''This demo uses the arbitrary <tt>~/Solum_Demo</tt>.'' | |
− | + | <pre> | |
+ | 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 | ||
+ | </pre> | ||
− | Now, just browse to this URL to see the demo: http://192.168.76.11:9001/solum/ | + | * This demo uses docker containers by default but if a virtual machine is desired instead, add this command: <tt>export SOLUM_IMAGE_FORMAT=vm</tt> |
+ | |||
+ | <pre> | ||
+ | cd vagrant | ||
+ | vagrant up | ||
+ | </pre> | ||
+ | |||
+ | This may take about 15 minutes or so to install. | ||
+ | |||
+ | * Finally, add a route so the demo app can be seen from your host machine: | ||
+ | |||
+ | <pre> | ||
+ | sudo route add -net 192.168.78.0/24 192.168.76.11 | ||
+ | </pre> | ||
+ | |||
+ | * Now, just browse to this URL to see the demo: (http://192.168.76.11:9001/solum/) | ||
==== Common Vagrant Commands ==== | ==== Common Vagrant Commands ==== | ||
− | * vagrant halt --- Stops the running vagrant but doesn't delete anything | + | * <tt>vagrant halt</tt> --- Stops the running vagrant but doesn't delete anything |
− | * vagrant up --provision --- Restarts a halted vagrant | + | * <tt>vagrant up --provision</tt> --- Restarts a halted vagrant, and runs all provisioning scripts, including devstack in our case. |
− | * vagrant destroy --- Deletes the vagrant and all data (be careful!) | + | * <tt>vagrant destroy</tt> --- Deletes the vagrant and all data (be careful!) |
=== Navigating the Vagrant Screen Sessions === | === Navigating the Vagrant Screen Sessions === | ||
− | * To log into the Vagrant session, use | + | * To log into the Vagrant session, use <tt>vagrant ssh</tt> |
− | * To list the screen sessions available use | + | * To list the screen sessions available use <tt>screen -ls</tt> |
− | * To connect to a given screen, | + | * To connect to a given screen, <tt>screen -x bridge</tt> for example (it works as long as the name is an unambiguous subset of one screen session's name) |
Revision as of 19:21, 30 April 2014
Contents
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 OS X v10.7.5.
- Install Vagrant (http://www.vagrantup.com/downloads.html). Tested with Vagrant v1.5.4
- Make a directory for the two repositories, and activate the demo UI. This demo uses the arbitrary ~/Solum_Demo.
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
- This demo uses docker containers by default but if a virtual machine is desired instead, add this command: export SOLUM_IMAGE_FORMAT=vm
cd vagrant vagrant up
This may take about 15 minutes or so to install.
- Finally, 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
- Now, just 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.
- vagrant destroy --- Deletes the vagrant and all data (be careful!)
- 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)