• http://archive.openflow.org/wk/index.php/OpenFlow_Tutorial
• http://www.opendaylight.org/project/technical-overview

 /mnt/vm00/sdn_testbed/devstack
 

/dev/sdb4 is lvm2 used by cider (volume).

1. HOST_IP is the ip of virbr0 interface: 192.168.122.1

1. Make sure stack user (current user) has permission for httpd, etc.
2. Checkout devstack for stable version icehouse

   git clone https://github.com/openstack-dev/devstack.git devstack cd devstack git fetch remote git checkout -b icehouse origin/stable/icehouse
   Now we are working with devstack configured to download openstack from the stable icehouse realease.

3. Installation cp local.conf ./ ; vim local.conf #HOSTIP, PWD, ETC. ./stack.sh
   4. Fix Horizon httpd virtualhost to run on HOSTIP, so that it doesn't mess up with other httpd sites: dokuwiki, etc. vim /etc/httpd/conf.d/horizon.conf
   -<VirtualHost 0.0.0.0:80> +<VirtualHost 192.168.122.1:80>
   systemctl restart httpd.service

   Working with stack

   Restart devstack

First run with

  ./stack.sh
  

Stop with

  ./unstack.sh
  

Devstack scripts will start all openstack services then detach them with “screen” instead of as system services. All screen command are written in “stack-screenrc”. This file is used by “rejoin-stack.sh” to start all services after reboot (without calling unstack.sh).

See next steps first stack.sh will clean database and setup system again. So use rejoint-stack.sh to start OpenStack:

./rejoin-stack.sh

Oppsss… start httpd first

  systemctl restart httpd

Start mariadb (mysqld). If it's down keystone will not work. Page through screen to see any error output from keystone.

  systemctl start mysqld

To exit rejoin-stack screen using:

  ctrl+a+d
    

Reopen screen:

  screen -x

Loop through each screened service using

  ctrl+a+"
  ctrl+ a + n(ext)
  ctrl+ a + n(prev) 

Kill currently shown screen/service with “Ctrl+C”. The screen is just a terminal where the command is run.

Running

  sudo losetup -f /opt/stack/data/stack-volumes-backing-file

before rejoin-stack.sh makes the volume group come online and cinder-volume will start ok.

• http://docs.openstack.org/user-guide/content/openstack_user_guide.html

By default a loopdevice is associated with the stack volumes backing file:

  sudo losetup -f /opt/stack/data/stack-volumes-backing-file
  

Build the Loopback File and Persist It

Start by checking on the amount of storage you have available on your node. This guide assume the loopback file will be created in the root partition. Become root and then execute the following command:

df -ah /

Take a gander at the result:

root@flop:/home/kord# df -ah / Filesystem Size Used Avail Use% Mounted on /dev/sda2 2.8T 2.5G 2.6T 1% /

We're good to create a 1TB file on that partition. Now execute the command to create the file we'll loop:

dd if=/dev/zero of=cinder-volumes bs=1 count=0 seek=1024G

Results come back instantly:

root@flop:/home/kord# dd if=/dev/zero of=/cinder-volumes bs=1 count=0 seek=1024G 0+0 records in 0+0 records out 0 bytes (0 B) copied, 1.035e-05 s, 0.0 kB/s

Now loop up the file to the loopback device (we'll use loop2 here):

losetup /dev/loop2 /cinder-volumes

Finally, create a rc file to mount the loopback file after a reboot:

echo “losetup /dev/loop2 /cinder-volumes; exit 0;”

> /etc/init.d/cinder-setup-backing-file