openstack/kolla
Code Issues Proposed changes

Fix some spelling and formatting errors in the Cinder doc

Browse Source 
Closes-bug: #1480174

Change-Id: I1ef695e910405f41045ffa1c8a13afa1a443c39e
This commit is contained in:
Ryan Hallisey 2015-07-31 08:15:59 -04:00
parent 532051080b
commit d9a3afbfe0
1 changed files with 17 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

25
docs/storage-guide.md → docs/block-storage-guide.md
View File

@ -1,14 +1,19 @@
# Storage Guide
This is a overview of how Cinder is implemented in Kolla so that it is easier to understand how to use it. Keep in mind, this is the first iteration for Cinder as support for Ceph and physical devices will follow.
This is a overview of how Cinder is implemented in Kolla so that it is easier
to understand how to use it. Keep in mind, this is the first iteration for
Cinder as support for Ceph and physical devices will follow.
## Overview
Kolla's setup for Cinder uses tgtd as the default iSCSI helper to implement persistent targets. By default, we use a loop back file that is defined by CINDER_LVM_LO_VOLUME_SIZE to create the cinder-volumes volume group.
Kolla's setup for Cinder uses tgtd as the default iSCSI helper to implement
persistent targets. By default, we use a loop back file that is defined by
CINDER_LVM_LO_VOLUME_SIZE to create the cinder-volumes volume group.
## Configure Cinder
Listed below are the default configurations for Cinder. For more info on what each variable does look at the [integration guide.](https://github.com/stackforge/kolla/blob/master/docs/integration-guide.md):
Listed below are the default configurations for Cinder. For more info on what
each variable does look at the [integration guide.](https://github.com/stackforge/kolla/blob/master/docs/integration-guide.md):
# Cinder Volume
CINDER_ENABLED_BACKEND=lvm57
@ -22,7 +27,8 @@ Listed below are the default configurations for Cinder. For more info on what e
## Using Cinder
After you've started all you containers, you should be able to interact with Cinder.
After you've started all your containers, you should be able to interact
with Cinder.
cinder list
@ -33,13 +39,16 @@ Next, you will want to create a volume and attach it to a running instance.
## Debugging and deleting volumes
The cinder-volumes volume group can't be seen from the host. In order to interact with an existing volume, you need to jump into the Cinder Volume container.
The cinder-volumes volume group can't be seen from the host. In order to
interact with an existing volume, you need to jump into the Cinder Volume
container.
sudo docker exec -it <cinder_volume_container> /bin/bash
sudo vgs
vgs
Running 'vgs' will list the volumes groups. From there, you can look at specific volumes to make sure volume creation succeeded.
Running 'vgs' will list the volumes groups. From there, you can look
specific volumes to make sure volume creation succeeded.
To delete the cinder-volumes volume group from within the container run:
sudo vgs remove cinder-volumes
vgs remove cinder-volumes