summaryrefslogtreecommitdiffstats
path: root/doc/source
diff options
context:
space:
mode:
authorSandy Walsh <sandy.walsh@rackspace.com>2011-04-08 13:45:19 -0300
committerSandy Walsh <sandy.walsh@rackspace.com>2011-04-08 13:45:19 -0300
commit9da9d9c8d5f763ec18c1286bf10f33ae67c84ced (patch)
tree716e5609c45c5cd1d4ca663954e6b706fbbb7da6 /doc/source
parent845d32660eb18b8a402519d382392232f79f2990 (diff)
downloadnova-9da9d9c8d5f763ec18c1286bf10f33ae67c84ced.tar.gz
nova-9da9d9c8d5f763ec18c1286bf10f33ae67c84ced.tar.xz
nova-9da9d9c8d5f763ec18c1286bf10f33ae67c84ced.zip
merge prop tweaks 2
Diffstat (limited to 'doc/source')
-rw-r--r--doc/source/devref/zone.rst5
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/source/devref/zone.rst b/doc/source/devref/zone.rst
index acc7398bf..234a96916 100644
--- a/doc/source/devref/zone.rst
+++ b/doc/source/devref/zone.rst
@@ -57,6 +57,7 @@ Zone administrative operations are usually done using python-novaclient_
In order to use the Zone operations, be sure to enable administrator operations in OpenStack API by setting the `--allow_admin_api=true` flag.
+Finally you need to enable Zone Forwarding. This will be used by the Distributed Scheduler initiative currently underway. Set `--enable_zone_routing=true` to enable this feature.
Find out about this Zone
------------------------
@@ -83,7 +84,7 @@ This equates to a GET operation on `.../zones/info`. If you have no child Zones
Adding a child Zone
-------------------
-From a parent zone you can add a child zone with the following command:
+Any Zone can be a parent Zone. Children are associated to a Zone. The Zone where this command originates from is known as the Parent Zone. Routing is only ever conducted from a Zone to its children, never the other direction. From a parent zone you can add a child zone with the following command:
::
@@ -123,4 +124,4 @@ Removing a child Zone
nova zone-delete <N>
-This equates to a DELETE call to `.../zones/N`. The Zone with ID=N will be removed. This will only remove the zone entry from the current (parent) Zone, no child Zones are affected.
+This equates to a DELETE call to `.../zones/N`. The Zone with ID=N will be removed. This will only remove the zone entry from the current (parent) Zone, no child Zones are affected. Removing a Child Zone doesn't affect any other part of the hierarchy.