Overloaded use of the storage_availability_zone configuration option

[Michael Kerrin]

The storage_availability_zone configuration option is used for two purposes

The first is to specify which az a service belongs too. But it is also used by the api service to specify the default availability zone for a new volume.

So if you want to run the cinder-api and cinder-volume on the same machine then you can't specify the default AZ.

I propose adding a new configuration option 'default_availability_zone' that is used when creating volumes to specify this.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/45631

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/45631
Committed: http://github.com/openstack/cinder/commit/4fd5f9d68312776d10cc2ef775a76c0f3ece60de
Submitter: Jenkins
Branch: master

commit 4fd5f9d68312776d10cc2ef775a76c0f3ece60de
Author: Michael Kerrin <email address hidden>
Date: Mon Sep 9 08:12:27 2013 +0000

    Add default_availability_zone configuration option to cinder

    This option is used to specify the default AZ for the whole service. So when
    creating a new volume this value is used to specify the AZ of a volume.

    Previously we were overloading the use of the storage_availability_zone option
    which is also used to specify what AZ a service belongs to. We still fail back
    on the storage_availability_zone when creating a new volume if the
    default_availability_zone is not set.

    Fixes bug: 1221260

    Change-Id: Iec381f50c9aeb4a0abbcaa1d7b0107de09a73544