5c5927a3d2
These closely related features are the source of a disproportionate number of bugs and a large amount of confusion among users. The spread of information around multiple docs probably doesn't help matters. Do what we've already done for the metadata service and remote consoles and clean these docs up. There are a number of important changes: - All documentation related to host aggregates and availability zones is placed in one of three documents, '/user/availability-zones', '/admin/aggregates' and '/admin/availability-zones'. (note that there is no '/user/aggregates' document since this is not user-facing) - References to these features are updated to point to the new location - A glossary is added. Currently this only contains definitions for host aggregates and availability zones - nova CLI commands are replaced with their openstack CLI counterparts - Some gaps in related documentation are closed Change-Id: If847b0085dbfb4c813d4a8d14d99346f8252bc19 Signed-off-by: Stephen Finucane <sfinucan@redhat.com>
26 lines
1.0 KiB
ReStructuredText
26 lines
1.0 KiB
ReStructuredText
========
|
|
Glossary
|
|
========
|
|
|
|
.. glossary::
|
|
|
|
Availability Zone
|
|
Availability zones are a logical subdivision of cloud block storage,
|
|
compute and network services. They provide a way for cloud operators to
|
|
logically segment their compute based on arbitrary factors like
|
|
location (country, datacenter, rack), network layout and/or power
|
|
source.
|
|
|
|
For more information, refer to :doc:`/admin/aggregates`.
|
|
|
|
Host Aggregate
|
|
Host aggregates can be regarded as a mechanism to further partition an
|
|
:term:`availability zone`; while availability zones are visible to
|
|
users, host aggregates are only visible to administrators. Host
|
|
aggregates provide a mechanism to allow administrators to assign
|
|
key-value pairs to groups of machines. Each node can have multiple
|
|
aggregates, each aggregate can have multiple key-value pairs, and the
|
|
same key-value pair can be assigned to multiple aggregates.
|
|
|
|
For more information, refer to :doc:`/admin/aggregates`.
|