Jump to: navigation, search

Difference between revisions of "Solum/solum m2 demo"

(Formatting and rewording)
(Solum Demo Vagrant Installation Instructions)
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.''
+
''These installation instructions were tested on Mac OSX v10.7.5 and OSX 10.8.5''
  
* Install Vagrant (http://www.vagrantup.com/downloads.html). ''Tested with Vagrant v1.5.4''
+
1. 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>.''
+
2. Make a directory for the two repositories, and activate the demo UI. ''This demo uses the'' <tt>~/Solum_Demo</tt> ''directory.''
  
<pre>
+
mkdir ~/Solum-Demo
mkdir ~/Solum-Demo
+
cd ~/Solum-Demo
cd ~/Solum-Demo
+
git clone https://github.com/rackerlabs/vagrant-solum-dev.git vagrant
git clone https://github.com/rackerlabs/vagrant-solum-dev.git vagrant
+
git clone https://github.com/rackerlabs/solum-m2demo-ui.git m2demo
git clone https://github.com/rackerlabs/solum-m2demo-ui.git m2demo
+
export WEBGUI=`pwd`/m2demo
export WEBGUI=`pwd`/m2demo
 
</pre>
 
  
* 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>
+
For those who prefer to use VMs instead of Docker containers (the default).
  
<pre>
+
export SOLUM_IMAGE_FORMAT=vm # Add only if you don't want Docker containers
cd vagrant
 
vagrant up
 
</pre>
 
  
This may take about 15 minutes or so to install.
+
3. Create the demo environment on your system:
 +
cd vagrant
 +
vagrant up
  
* Finally, add a route so the demo app can be seen from your host machine:
+
NOTE: This may take between about 15 and 60 minutes to install, depending on the speed of your machine and network.
  
<pre>
+
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
 
</pre>
 
  
* Now, just browse to this URL to see the demo: (http://192.168.76.11:9001/solum/)
+
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 ====
 
==== Common Vagrant Commands ====

Revision as of 06:43, 1 May 2014

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.
  • 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)