diff --git a/doc/src/docbkx/openstack-compute-admin/computeadmin.xml b/doc/src/docbkx/openstack-compute-admin/computeadmin.xml index 53a431e89d..c04a4d4c6b 100644 --- a/doc/src/docbkx/openstack-compute-admin/computeadmin.xml +++ b/doc/src/docbkx/openstack-compute-admin/computeadmin.xml @@ -591,10 +591,11 @@ euca-register mybucket/windowsserver.img.manifest.xml A- Installing the nova-volume service on the cloud controller. - B- Configuring the nova-volumes volume group on the compute nodes. + B- Configuring the "nova-volumes" volume group on the compute + nodes. - C- Troubleshooting your nova-volumes installation. + C- Troubleshooting your nova-volume installation. D- Backup your nova volumes. @@ -602,8 +603,8 @@ euca-register mybucket/windowsserver.img.manifest.xml - A- Install nova-volumes on the cloud controller. - This is simply done by installing the two components on the cloud controller : apt-get install lvm2 nova-volumesFor Ubuntu distros, the nova-volumes component will not properly work (regarding the part which deals with volumes deletion) without a small fix. In dorder to fix that, do the following : + A- Install nova-volume on the cloud controller. + This is simply done by installing the two components on the cloud controller : apt-get install lvm2 nova-volumeFor Ubuntu distros, the nova-volumes component will not properly work (regarding the part which deals with volumes deletion) without a small fix. In dorder to fix that, do the following : sudo visudo Then add an entry for the nova user (here is the default sudoers file with our added nova user) : @@ -645,7 +646,7 @@ root ALL=(ALL) ALL Configure Volumes for use with - nova-volumes + nova-volume If you do not already have LVM volumes on hand, but have free drive space, you will need to create a LVM volume before proceeding. Here is a short run down of how you would create a LVM from free drive space on @@ -732,7 +733,7 @@ vgcreate nova-volumes /dev/sda5 - B- Configuring nova-volumes on the compute nodes + B- Configuring nova-volume on the compute nodes Since you have created the volume group, you will be able to use the following tools for managing your volumes: euca-create-volume @@ -815,7 +816,7 @@ tcp: [1] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-0000000b KVM changes the device name, since it's not considered to be the same type of device as the instances uses as it's - local one, you will find the nova-volumes will be designated as + local one, you will find the nova-volume will be designated as "/dev/vdX" devices, while local are named "/dev/sdX". You can check the volume attachment by running : dmesg | tail @@ -884,7 +885,7 @@ mount /dev/vdb1 /extraspace - C- Troubleshoot your nova-volumes installation + C- Troubleshoot your nova-volume installation If the volume attachment doesn't work, you should be able to perform different checks in order to see where the issue is. The nova-volume.log and nova-compute.log will help you to diagnosis the errors you could encounter : @@ -1023,7 +1024,7 @@ tcp: [9] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000014 - D- Backup your nova-volumes + D- Backup your nova-volume disks While Diablo provides the snapshot functionality (using LVM snapshot), were are going to see here how you can backup your EBS-volumes. The way we will do it offers the advantage to make backup that don't size much, in fact, only existing data will @@ -1235,8 +1236,8 @@ tcp: [9] 172.16.40.244:3260,1 iqn.2010-10.org.openstack:volume-00000014 6- Automate your backups - You will mainly have more and more volumes on your nova-volumes' server. It might - be interesting then to automate things a bit. This script You will mainly have more and more volumes allocated to your nova-volume service. + It might be interesting then to automate things a bit. This script here will assist you on this task. The script does the operations we just did earlier, but also provides mail report and backup running (based on the "