Hi All, I'm sorry I was in vacation yesterday(in JST), and I did not notice this discussion. I registered "bug 1496235".
In our case , there is Nova 2 az(az1, az2),and Cinder 1 az (default). Cinder backend is ceph, that is a cluster of compute nodes inclued az1 and az2 of nova. Nova's 2 az always use cinder default zone . When I resistered, the option I wanted is that I can select "sync" or "async" az between nova and cinder. Regards, IKUO Kumagai 2015-09-24 10:05 GMT+09:00 Sam Morrison <sorri...@gmail.com>: > > > On 24 Sep 2015, at 9:59 am, Andrew Laski <and...@lascii.com> wrote: > > > > I was perhaps hasty in approving that patch and didn't realize that Matt > had reached out for operator feedback at the same time that he proposed it. > Since this is being used in production I wouldn't want it to be removed > without at least having an alternative, and hopefully better, method of > achieving your goal. Reverting the deprecation seems reasonable to me for > now while we work out the details around Cinder/Nova AZ interactions. > > Thanks Andrew, > > What we basically want is for our users to have instances and volumes on a > section of hardware and then for them to be able to have other instances > and volumes in another section of hardware. > > If one section dies then the other section is fine. For us we use > availability-zones for this. If this is not the intended use for AZs what > is a better way for us to do this. > > Cheers, > Sam > > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
