From 233864ff32af10a2c927cdbca3475b537c8e6808 Mon Sep 17 00:00:00 2001 From: Steven Dake Date: Wed, 2 Sep 2015 22:33:01 -0700 Subject: Rename docs dir to doc for publishing The publishing docs expect the documentation to be present in the /doc directory not the /docs directory. If the documentation is in the /docs directory, according to fungi the docs won't be published properly. Change-Id: I718fec7e69d298a5cb2376ca4e2455e12169566e Partially-Implements: blueprint kola-tox-doc --- docs/cinder-guide.rst | 77 --------------------------------------------------- 1 file changed, 77 deletions(-) delete mode 100644 docs/cinder-guide.rst (limited to 'docs/cinder-guide.rst') diff --git a/docs/cinder-guide.rst b/docs/cinder-guide.rst deleted file mode 100644 index 7247cc02a..000000000 --- a/docs/cinder-guide.rst +++ /dev/null @@ -1,77 +0,0 @@ -Cinder in Kolla -=============== - -Overview --------- -Currently Kolla can deploy the cinder services: - -- cinder-api -- cinder-scheduler -- cinder-backup -- cinder-volume - -The cinder implementation defaults to using LVM storage. The default -implementation requires a volume group be set up. This can either be -a real physical volume or a loopback mounted file for development. - -Create a Volume Group ---------------------- -Use pvcreate and vgcreate to create the volume group. For example with -the devices /dev/sdb and /dev/sdc: - -:: - - - - pvcreate /dev/sdb /dev/sdc - vgcreate cinder-volumes /dev/sdb /dev/sdc - -During development, it may be desireable to use file backed block storage. It -is possible to use a file and mount it as a block device via the loopback -system. - -:: - - mknod /dev/loop2 b 7 2 - dd if=/dev/zero of=/var/lib/cinder_data.img bs=1g count=20 - losetup /dev/loop2 /var/lib/cinder_data.img - pvcreate /dev/loop2 - vgcreate cinder-volumes /dev/loop2 - -Validation ----------- - -Create a volume as follows: - -:: - - $ openstack volume create --size 1 steak_volume - - -Verify it is available. If it says "error" here something went wrong during -LVM creation of the volume. - -:: - - $ openstack volume list - +--------------------------------------+--------------+-----------+------+-------------+ - | ID | Display Name | Status | Size | Attached to | - +--------------------------------------+--------------+-----------+------+-------------+ - | 0069c17e-8a60-445a-b7f0-383a8b89f87e | steak_volume | available | 1 | | - +--------------------------------------+--------------+-----------+------+-------------+ - -Attach the volume to a server using: - -:: - - openstack server add volume steak_server 0069c17e-8a60-445a-b7f0-383a8b89f87e - -Check the console log added the disk: - -:: - - opoenstack console log show steak_server - -A /dev/vdb should appear in the console log, atleast when booting cirros. -If the disk stays in the available state, something went wrong during the -iSCSI mounting of the volume to the guest VM. -- cgit v1.2.3