QA:Testcase Create Cinder Volumes

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
m (use systemctl instead of service)
Line 15: Line 15:
 
it's not started by default, so to do that:
 
it's not started by default, so to do that:
  
  sudo service openstack-cinder-volume start
+
  sudo systemctl start openstack-cinder-volume.service
  
 
== Actions after each reboot ==
 
== Actions after each reboot ==
Line 23: Line 23:
  
 
  sudo losetup -f /var/lib/cinder/cinder-volumes.img
 
  sudo losetup -f /var/lib/cinder/cinder-volumes.img
  sudo service openstack-cinder-volume start
+
  sudo systemctl start openstack-cinder-volume.service
  
 
If you intend to make them persist automatically, then enable the service to start in the standard manner,
 
If you intend to make them persist automatically, then enable the service to start in the standard manner,

Revision as of 10:26, 21 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 systemctl start openstack-cinder-volume.service

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 systemctl start openstack-cinder-volume.service

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