Joe Gordon
1ab2fc6477
This is the final step in enabling availability_zones using aggregate metadata. Previously all services had an availability_zone, but the availability_zone is only used for nova-compute. Services such as nova-scheduler, nova-network, nova-conductor have always spanned all availability_zones. After this change only compute nodes (nova-compute), will have an availability_zone. In order to preserve current APIs, when running: * nova host-list (os-hosts) * euca-describe-availability-zones verbose * nova-manage service list Internal services will appear in there own internal availability_zone (CONF.internal_service_availability_zone) Internal zone is hidden in euca-describe-availability_zones (non-verbose) CONF.node_availability_zone has been renamed to CONF.default_availability_zone and is only used by the nova-api and nova-scheduler. CONF.node_availability_zone still works but is deprecated DocImpact Completes blueprint aggregate-based-availability-zones Change-Id: Ib772df5f9ac2865f20df479f8ddce575a9ce3aff
OpenStack Nova Documentation README =================================== Included documents: - developer reference guide(devref) - man pages Building the docs ----------------- From the root nova director:: python setup.py build_sphinx Building just the man pages --------------------------- from the root nova director:: python setup.py build_sphinx -b man Installing the man pages ------------------------- After building the man pages, they can be found in ``doc/build/man/``. You can install the man page onto your system by following the following steps: Example for ``nova-manage``:: mkdir /usr/local/man/man1 install -g 0 -o 0 -m 0644 doc/build/man/nova-manage.1 /usr/local/man/man1/nova-manage.1 gzip /usr/local/man/man1/nova-manage.1 man nova-manage