Commit Graph

6 Commits

Author SHA1 Message Date
Takashi NATSUME fa43227f6e Update document related to host aggregate
The arguments of nova CLI commands related to host aggregate
(I93f44a12b6d5a91b448f6f8d238311d58bf40c01) are fixed.
The host APIs have been deprecated since microversion 2.43.
So remove description related to nova host commands.
And add description about nova hypervisor commands.

Change-Id: Ibf78865844da6f007b610f12430df4866076f00b
Closes-Bug: #1726658
2017-11-21 02:01:40 +00:00
Jenkins 659b63d84b Merge "fix nova accepting invalid availability zone name with ':'" 2017-10-04 18:54:23 +00:00
Matt Riedemann 7db0e3c2b6 doc: make host aggregates examples more discoverable
When one is looking for an explanation and examples of
how to associate host aggregates to flavors, it's useful
to be able to point to that from the more top-level
aggregates page, which is linked from the main home page.

This change links from that to a somewhat buried reference
doc on host aggregates, which is actually really useful here.

Change-Id: I9e03c6649afd9a7aa816b9af1d931f9e0cffb94a
2017-09-27 14:58:37 -04:00
Tetsuro Nakamura 38b25397e8 fix nova accepting invalid availability zone name with ':'
Nova has a legacy hack to allow admins to specify hosts via an
availability zone using az:host:node. That means ':' cannot be
included in the name of an availability zone itself.

However, the aggregate API accepts requests which have
availability zone names including ':'.

This patch checks the availabilty zone name when aggregate is
created or updated and raises an error if it contains ':'.

Change-Id: I9b0d8e8d4b3ab2cb3d578c22fa259e0e7c0d325b
Closes-Bug: #1695861
2017-09-24 15:12:43 +09:00
Sean Dague 613f55c26a fix list rendering in aggregates
List items need to be exactly 2 spaces off of the parent, and the top
level left justified, otherwise <blockquote> gets thrown into the
html.

Part of bp: doc-migration

Change-Id: I16634edbc562aff69744e5d7c7275689326ab8d0
2017-08-03 08:02:24 -04:00
Stephen Finucane ef9cbc0017 doc: Populate the 'user' section
Per the spec [1]:

  user/ – end-user content such as concept guides, advice, tutorials,
  step-by-step instructions for using the CLI to perform specific tasks,
  etc.

The remaining content all ends up in here.

[1] specs.openstack.org/openstack/docs-specs/specs/pike/os-manuals-migration

Change-Id: I480eee9cd7568efe2f76dd185004774588eb4a99
2017-07-18 15:41:20 +01:00