Set cinder_cross_az_attach to false

[Bjoern]

Please explore if we can set cinder_cross_az_attach by default to false preventing anyone, at least unattended, to create volumes different from a nova AZ. In cases where customers have physical DC separation configured and reflecting this in different cinder and nova AZs. What do you guys think?

[git-harry (git-harry)]

I've uploaded a patch [1] to make this option configurable in the template. I'm not sure if this project has a particular stance on overriding the defaults of upstream projects but I think in general it makes sense to follow their lead.

[1] https://review.openstack.org/#/c/194102/

[Kevin Carter (kevin-carter)]

master https://review.openstack.org/#/c/194102/
kilo cherry pick https://review.openstack.org/#/c/194213/

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/194213
Committed: https://git.openstack.org/cgit/stackforge/os-ansible-deployment/commit/?id=2d1e6186166fa10f90bc19d6f5e3769500ec7420
Submitter: Jenkins
Branch: kilo

commit 2d1e6186166fa10f90bc19d6f5e3769500ec7420
Author: git-harry <email address hidden>
Date: Mon Jun 22 12:41:06 2015 +0100

    Add configurable option [cinder]/cross_az_attach

    nova has the configuration option [cinder]/cross_az_attach with a
    default of True. This option allows attaching between instances and
    volumes in different availability zones.

    This commit makes this option configurable in the nova.conf template
    and uses a default of True.

    Change-Id: Ia95f3d4447b026a8e93c74a8c65a63dcea89994f
    Closes-bug: 1457140
    (cherry picked from commit 92b0c769ebfbb6c62df752959eaadcef807408d7)

[Davanum Srinivas (DIMS) (dims-v)]

This issue was fixed in the openstack/openstack-ansible 11.2.14 release.