openstack/kolla-ansible
Code Issues Proposed changes

Fix typos in kolla/doc

Browse Source 
Change-Id: I17b4b40a6c49210faa535bdf3032c000daae0e2e
This commit is contained in:
Mitsuhiro SHIGEMATSU 2015-12-05 17:06:58 +09:00
parent 939b464d12
commit 897cdf900d
3 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/ceph-guide.rst
View File

@ -18,7 +18,7 @@ Preparation and Deployment
To prepare a disk for use as a To prepare a disk for use as a
`Ceph OSD <http://docs.ceph.com/docs/master/man/8/ceph-osd/>`_ you must add a `Ceph OSD <http://docs.ceph.com/docs/master/man/8/ceph-osd/>`_ you must add a
special partition label to the disk. This partition label is how Kolla detects special partition label to the disk. This partition label is how Kolla detects
the disks to format and bootstrap. Any disk with a matching parition label will the disks to format and bootstrap. Any disk with a matching partition label will
be reformatted so use caution. be reformatted so use caution.
To prepare an OSD as a storage drive, execute the following operations: To prepare an OSD as a storage drive, execute the following operations:
@ -72,7 +72,7 @@ Using a Cache Tier
An optional An optional
`cache tier <http://docs.ceph.com/docs/hammer/rados/operations/cache-tiering/>`_ `cache tier <http://docs.ceph.com/docs/hammer/rados/operations/cache-tiering/>`_
can be deployed by formating at least one cache device and enabling cache can be deployed by formatting at least one cache device and enabling cache
tiering in the globals.yml configuration file. tiering in the globals.yml configuration file.
To prepare an OSD as a cache device, execute the following operations: To prepare an OSD as a cache device, execute the following operations:

4
doc/cinder-guide.rst
View File

@ -26,7 +26,7 @@ the devices /dev/sdb and /dev/sdc:
pvcreate /dev/sdb /dev/sdc pvcreate /dev/sdb /dev/sdc
vgcreate cinder-volumes /dev/sdb /dev/sdc vgcreate cinder-volumes /dev/sdb /dev/sdc
During development, it may be desireable to use file backed block storage. It During development, it may be desirable to use file backed block storage. It
is possible to use a file and mount it as a block device via the loopback is possible to use a file and mount it as a block device via the loopback
system. system.
@ -72,6 +72,6 @@ Check the console log added the disk:
openstack console log show steak_server openstack console log show steak_server
A /dev/vdb should appear in the console log, atleast when booting cirros. A /dev/vdb should appear in the console log, at least when booting cirros.
If the disk stays in the available state, something went wrong during the If the disk stays in the available state, something went wrong during the
iSCSI mounting of the volume to the guest VM. iSCSI mounting of the volume to the guest VM.

2
doc/swift-guide.rst
View File

@ -73,7 +73,7 @@ container directories:
/etc/kolla/config/swift/${ring}.builder rebalance; /etc/kolla/config/swift/${ring}.builder rebalance;
done done
Similar commands can be used for multinode, you will just need to run the the 'add' step for each IP Similar commands can be used for multinode, you will just need to run the 'add' step for each IP
in the cluster. in the cluster.
For more info, see For more info, see