Merge "Converts section_glusterfs_removal.xml to RST"
This commit is contained in:
commit
cb2321676d
|
@ -59,6 +59,7 @@ troubleshoot your installation and back up your Compute volumes.
|
|||
.. include:: blockstorage_glusterfs_backend.rst
|
||||
.. include:: blockstorage_multi_backend.rst
|
||||
.. include:: blockstorage_backup_disks.rst
|
||||
.. include:: blockstorage_glusterfs_removal.rst
|
||||
.. include:: blockstorage-lio-iscsi-support.rst
|
||||
.. include:: blockstorage-consistency-groups.rst
|
||||
.. include:: blockstorage-driver-filter-weighing.rst
|
||||
|
@ -72,6 +73,7 @@ troubleshoot your installation and back up your Compute volumes.
|
|||
blockstorage_glusterfs_backend.rst
|
||||
blockstorage_multi_backend.rst
|
||||
blockstorage_backup_disks.rst
|
||||
blockstorage_glusterfs_removal.rst
|
||||
blockstorage-lio-iscsi-support.rst
|
||||
blockstorage-consistency-groups.rst
|
||||
blockstorage-driver-filter-weighing.rst
|
||||
|
@ -79,7 +81,6 @@ troubleshoot your installation and back up your Compute volumes.
|
|||
|
||||
.. TODO (MZ) Convert and include the following sections
|
||||
include: blockstorage/section_volume-migration.xml
|
||||
include: blockstorage/section_glusterfs_removal.xml
|
||||
include: blockstorage/section_volume-backups.xml
|
||||
include: blockstorage/section_volume-backups-export-import.xml
|
||||
include: blockstorage/section_volume_number_weighter.xml
|
||||
|
|
|
@ -0,0 +1,35 @@
|
|||
.. _glusterfs_removal:
|
||||
|
||||
.. highlight: ini
|
||||
:linenothreshold: 5
|
||||
|
||||
Gracefully remove a GlusterFS volume from usage
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
Configuring the ``cinder`` volume service to use GlusterFS involves creating a
|
||||
shares file (for example, :file:`/etc/cinder/glusterfs`). This shares file
|
||||
lists each GlusterFS volume (with its corresponding storage server) that
|
||||
the ``cinder`` volume service can use for back end storage.
|
||||
|
||||
To remove a GlusterFS volume from usage as a back end, delete the volume's
|
||||
corresponding entry from the shares file. After doing so, restart the Block
|
||||
Storage services.
|
||||
|
||||
To restart the Block Storage services on CentOS, Fedora, openSUSE,
|
||||
Red Hat Enterprise Linux, or SUSE Linux Enterprise, run::
|
||||
|
||||
# for i in api scheduler volume; do service openstack-cinder-$i restart; done
|
||||
|
||||
To restart the Block Storage services on Ubuntu or Debian, run::
|
||||
|
||||
# for i in api scheduler volume; do service cinder-${i} restart; done
|
||||
|
||||
Restarting the Block Storage services will prevent the ``cinder`` volume
|
||||
service from exporting the deleted GlusterFS volume. This will prevent any
|
||||
instances from mounting the volume from that point onwards.
|
||||
|
||||
However, the removed GlusterFS volume might still be mounted on an instance
|
||||
at this point. Typically, this is the case when the volume was already
|
||||
mounted while its entry was deleted from the shares file.
|
||||
Whenever this occurs, you will have to unmount the volume as normal after
|
||||
the Block Storage services are restarted.
|
Loading…
Reference in New Issue