QA:Testcase Create Cinder Volumes

From FedoraProject

(Difference between revisions)
Jump to: navigation, search
(remove reference to 'install packages' test case, current instructions use openstack-demo-install)
 
(10 intermediate revisions by 3 users not shown)
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,
 
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 ==
 +
 
 +
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.
 +
 
 +
== Integration with tgtd ==
 +
 
 +
In RHEL based systems the config files in /etc/tgt/conf.d/ don't honor globbing.
 +
Only the main /etc/tgt/targets.conf seems does.
 +
So to avoid that issue causing tgtd to not start:
 +
 
 +
sudo sed -i '1iinclude /etc/nova/volumes/*' /etc/tgt/targets.conf
 +
sudo sed -i '1iinclude /etc/cinder/volumes/*' /etc/tgt/targets.conf
 +
 
 +
then restart tgtd:
  
<span style="color:red;">Note!</span> None of the above commands are persistent across reboots,
+
sudo service tgtd restart
so please rerun them after reboot, or configure them to run automatically on reboot.
+
  
 
|results=
 
|results=
 +
Check the volume group is listed by this command
 +
sudo 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 systemctl status openstack-cinder-volume.service
 
}}
 
}}
  
 
[[Category:OpenStack Test Cases]]
 
[[Category:OpenStack Test Cases]]

Latest revision as of 14:22, 19 November 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.

Integration with tgtd

In RHEL based systems the config files in /etc/tgt/conf.d/ don't honor globbing. Only the main /etc/tgt/targets.conf seems does. So to avoid that issue causing tgtd to not start:

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

then restart tgtd:

sudo service tgtd restart

Expected Results

Check the volume group is listed by this command

sudo vgs

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

sudo systemctl status openstack-cinder-volume.service