cinder/doc/source/contributor/volume.rst
Jay S. Bryant be10de4b91 [Doc Bld Fix] Add links to man page contents
The pages under man/ had not been linked to from anywhere.  This
was causing Sphinx to issue warnings during build.  This patch
corrects that.

There was also a 'todo' directive that wasn't valid that needed
to be removed.  This patch also corrects that.

Change-Id: I8ab75b7be921a05e9e4eb023c4dfe90cf4404e6c
2017-08-21 13:56:27 -05:00

65 lines
1.8 KiB
ReStructuredText

..
Copyright 2010-2011 United States Government as represented by the
Administrator of the National Aeronautics and Space Administration.
All Rights Reserved.
Licensed under the Apache License, Version 2.0 (the "License"); you may
not use this file except in compliance with the License. You may obtain
a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS, WITHOUT
WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
License for the specific language governing permissions and limitations
under the License.
Storage Volumes, Disks
======================
.. note::
TODO(todd or vish): rework after iSCSI merge (see 'Old Docs') (todd or vish)
The :mod:`cinder.volume.manager` Module
---------------------------------------
.. automodule:: cinder.volume.manager
:noindex:
:members:
:undoc-members:
:show-inheritance:
The :mod:`cinder.volume.driver` Module
--------------------------------------
.. automodule:: cinder.volume.driver
:noindex:
:members:
:undoc-members:
:show-inheritance:
Tests
-----
The :mod:`cinder.tests.unit.volume` Module
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.. automodule:: cinder.tests.unit.volume
:noindex:
:members:
:undoc-members:
:show-inheritance:
Old Docs
--------
Cinder uses iSCSI to export storage volumes from multiple storage nodes. These iSCSI exports are attached (using libvirt) directly to running instances.
Cinder volumes are exported over the primary system VLAN (usually VLAN 1), and not over individual VLANs.
The underlying volumes by default are LVM logical volumes, created on demand within a single large volume group.