Open Stack

Hi, I'd like you to take a look at this patch for potential
DocImpact.
https://review.openstack.org/18675

Log:
commit fe9c18ae1ae0d0a14b4d93932ef413b83f5a7013
Author: Joe Gordon <jogo at cloudscaling.com>
Date:   Thu Dec 20 03:13:01 2012 +0000

    Remove availability_zones from service table
    
    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