QA:Testcase Create Cinder Volumes

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
Line 1: Line 1:
 
{{QA/Test_Case
 
{{QA/Test_Case
 
|description=Setup required for the OpenStack Volumes.
 
|description=Setup required for the OpenStack Volumes.
 
|actions=
 
 
 
In the Folsom release of OpenStack, the nova-volume service
 
In the Folsom release of OpenStack, the nova-volume service
 
was deprecated by the split out cinder service.
 
was deprecated by the split out cinder service.
 +
 +
|actions=
  
 
To create the cinder-volumes Volume Group for the openstack-cinder-volume service
 
To create the cinder-volumes Volume Group for the openstack-cinder-volume service
Line 11: Line 10:
 
  sudo truncate -s20G /var/lib/cinder/cinder-volumes.img
 
  sudo truncate -s20G /var/lib/cinder/cinder-volumes.img
 
  sudo vgcreate cinder-volumes $(sudo losetup --show -f /var/lib/cinder/cinder-volumes.img)
 
  sudo vgcreate cinder-volumes $(sudo losetup --show -f /var/lib/cinder/cinder-volumes.img)
 +
  
 
Because the volume service is dependent on the volume group being available,
 
Because the volume service is dependent on the volume group being available,
Line 17: Line 17:
 
  sudo service openstack-cinder-volume start
 
  sudo service openstack-cinder-volume start
  
<span style="color:red;">Note!</span> None of the above commands are persistent across reboots,
+
== Actions after each reboot ==
so please rerun them after reboot, or configure them to run automatically on reboot.
+
 
 +
The above commands are not persistent across reboots,
 +
so please rerun these commands after reboot:
 +
 
 +
sudo losetup -f /var/lib/cinder/cinder-volumes.img
 +
sudo service openstack-cinder-volume start
 +
 
 +
If you intend to make them persist automatically, then enable the service to start in the standard manner,
 +
but ensure that the losetup is run early in the boot process, or instead, use an implicitly persistent
 +
block device/partition.
 +
 
 +
== Temporary workaround for packaging issue ==
  
Also note that in Folsom, the iSCSI target configuration files are dropped into /var/lib/nova/volumes, so we need to ensure that these are picked up by the tgt daemon.  
+
In Folsom, the iSCSI target configuration files are dropped into /var/lib/cinder/volumes,
 +
so we need to ensure that these are picked up by the tgt daemon.  
  
 
Prepend that directory to the tgt target configuration file:
 
Prepend that directory to the tgt target configuration file:
  
  sudo sed -i '1iinclude /var/lib/nova/volumes/*' /etc/tgt/targets.conf
+
  sudo sed -i '1iinclude /var/lib/cinder/volumes/*' /etc/tgt/targets.conf
  
 
then restart tgtd:
 
then restart tgtd:
Line 31: Line 43:
  
 
|results=
 
|results=
 +
Check the volume group is listed by this command
 +
vgs
 
Check that no errors are reported in /var/log/cinder/* or by this command:
 
Check that no errors are reported in /var/log/cinder/* or by this command:
 
  sudo service openstack-cinder-volume status
 
  sudo service openstack-cinder-volume status

Revision as of 12:26, 20 September 2012

Contents

Description

Setup required for the OpenStack Volumes. In the Folsom release of OpenStack, the nova-volume service was deprecated by the split out cinder service.


How to test

To create the cinder-volumes Volume Group for the openstack-cinder-volume service

sudo truncate -s20G /var/lib/cinder/cinder-volumes.img
sudo vgcreate cinder-volumes $(sudo losetup --show -f /var/lib/cinder/cinder-volumes.img)


Because the volume service is dependent on the volume group being available, it's not started by default, so to do that:

sudo service openstack-cinder-volume start

Actions after each reboot

The above commands are not persistent across reboots, so please rerun these commands after reboot:

sudo losetup -f /var/lib/cinder/cinder-volumes.img
sudo service openstack-cinder-volume start

If you intend to make them persist automatically, then enable the service to start in the standard manner, but ensure that the losetup is run early in the boot process, or instead, use an implicitly persistent block device/partition.

Temporary workaround for packaging issue

In Folsom, the iSCSI target configuration files are dropped into /var/lib/cinder/volumes, so we need to ensure that these are picked up by the tgt daemon.

Prepend that directory to the tgt target configuration file:

sudo sed -i '1iinclude /var/lib/cinder/volumes/*' /etc/tgt/targets.conf

then restart tgtd:

sudo service tgtd restart

Expected Results

Check the volume group is listed by this command

vgs

Check that no errors are reported in /var/log/cinder/* or by this command:

sudo service openstack-cinder-volume status