Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-21 Thread Hirofumi Ichihara
On 2015/12/16 17:16, Kevin Benton wrote: What will the availability zones API tell the user about the zones? Are they just opaque strings that the user doesn't really understand? They shows available zones in the time. What I'm a little worried about is that it seems like we are having the

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-16 Thread Kevin Benton
What will the availability zones API tell the user about the zones? Are they just opaque strings that the user doesn't really understand? What I'm a little worried about is that it seems like we are having the user doing the work of the scheduler. Is this is for getting affinity or anti-affinity

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-14 Thread Armando M.
tions)" < >> openstack-dev@lists.openstack.org> >> Date: 12/14/2015 13:33 >> Subject: Re: [openstack-dev] [neutron] - availability zone performance >> regression and discussion about added network field >> -- >> >> >

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Hirofumi Ichihara
On 2015/12/14 15:58, Kevin Benton wrote: What decision would lead the user to request AZ1 and AZ2 in the first place? Especially since when it fails to get AZ2, they just request again with AZ1 and AZ3 instead. I expected that user gets AZ1 and AZ2 (and AZ3) via GET Availability zones API fir

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Kevin Benton
Stack Development Mailing List (not for usage questions)" < > openstack-dev@lists.openstack.org> > Date: 12/14/2015 13:33 > Subject: Re: [openstack-dev] [neutron] - availability zone performance > regression and discussion about added network field > -

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Kevin Benton
What decision would lead the user to request AZ1 and AZ2 in the first place? Especially since when it fails to get AZ2, they just request again with AZ1 and AZ3 instead. On Sun, Dec 13, 2015 at 10:31 PM, Hirofumi Ichihara < ichihara.hirof...@lab.ntt.co.jp> wrote: > > > On 2015/12/14 14:52, Kevin

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Hirofumi Ichihara
On 2015/12/14 14:52, Kevin Benton wrote: I see, so regular users are supposed to use this information as well. But how are they supposed to use it? For example, if they see that their network has availability zones 1 and 4, but their instance is hosted in zone 3, what are they supposed to do?

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Hong Hui Xiao
Stack Development Mailing List (not for usage questions)" Date: 12/14/2015 13:33 Subject: Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field Hi Kevin, On 2015/12/14 11:10, Kevin Benton w

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Kevin Benton
I see, so regular users are supposed to use this information as well. But how are they supposed to use it? For example, if they see that their network has availability zones 1 and 4, but their instance is hosted in zone 3, what are they supposed to do? On Sun, Dec 13, 2015 at 8:57 PM, Hirofumi Ich

Re: [openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Hirofumi Ichihara
Hi Kevin, On 2015/12/14 11:10, Kevin Benton wrote: Hi all, The availability zone code added a new field to the network API that shows the availability zones of a network. This caused a pretty big performance impact to get_networks calls because it resulted in a database lookup for every netw

[openstack-dev] [neutron] - availability zone performance regression and discussion about added network field

2015-12-13 Thread Kevin Benton
Hi all, The availability zone code added a new field to the network API that shows the availability zones of a network. This caused a pretty big performance impact to get_networks calls because it resulted in a database lookup for every network.[1] I already put a patch up to join the information