On 3/27/14, 11:03 AM, "Day, Phil" <philip....@hp.com> wrote:
>> >> The need arises when you need a way to use both the zones to be >>used for >> scheduling when no specific zone is specified. The only way to do that >>is >> either have a AZ which is a superset of the two AZ or the other way >>could be >> if the default_scheduler_zone can take a list of zones instead of just >>1. > >If you don't configure a default_schedule_zone, and don't specify an >availability_zone to the request - then I thought that would make the AZ >filter in effect ignore AZs for that request. Isn't that want you need ? No what I want is a default_schedule_zone that uses hosts from two other AZs but in my deployment I might have other AZs defined as well which I want to be filtered out when the boot command does not specify a AZ. Thanks, Sangeeta > >_______________________________________________ >OpenStack-dev mailing list >OpenStack-dev@lists.openstack.org >http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev