[openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-17 Thread Brandon Logan
As part of the routed networks work [1], the DHCP agent and scheduling needs to be segment aware. Right now, the dhcpagentscheduler extension exposes API resources to manage networks: - List networks hosted by an agent - GET /agents/{agent_id}/dhcp-networks - Response Body: {"netw

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-17 Thread Kevin Benton
I'm leaning towards option A because it keeps things cleanly separated. Also, if a cloud is using a plugin that supports segments, an operator could use the new API for everything (including single segment networks) so it shouldn't be that unfriendly. However... >If there's some other option that

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-18 Thread Brandon Logan
On Tue, 2016-05-17 at 13:29 -0700, Kevin Benton wrote: > I'm leaning towards option A because it keeps things cleanly > separated. Also, if a cloud is using a plugin that supports segments, > an operator could use the new API for everything (including single > segment networks) so it shouldn't be t

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-18 Thread Kevin Benton
>I may have wrongly assumed that segments MAY have the possibility of being l2 adjacent, even if the entire network they are in is not, which would mean that viewing and scheduling these in the context of a segment could be useful. Segments could be L2 adjacent, but I think it would be pretty unco

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-19 Thread Carl Baldwin
On Wed, May 18, 2016 at 1:36 PM, Kevin Benton wrote: >>I may have wrongly assumed that segments MAY have the possibility of being >> l2 adjacent, even if the entire network they are in is not, which would mean >> that viewing and scheduling these in the context of a segment could be >> useful. > >

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-20 Thread Brandon Logan
On Thu, 2016-05-19 at 14:16 -0600, Carl Baldwin wrote: > On Wed, May 18, 2016 at 1:36 PM, Kevin Benton wrote: > >>I may have wrongly assumed that segments MAY have the possibility of being > >> l2 adjacent, even if the entire network they are in is not, which would > >> mean > >> that viewing and

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-21 Thread Carl Baldwin
On Fri, May 20, 2016 at 1:44 PM, Brandon Logan wrote: > On Thu, 2016-05-19 at 14:16 -0600, Carl Baldwin wrote: >> On Wed, May 18, 2016 at 1:36 PM, Kevin Benton wrote: >> >>I may have wrongly assumed that segments MAY have the possibility of being >> >> l2 adjacent, even if the entire network they

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-22 Thread Gary Kotton
Today the DHCP schedulers have support for ‘AZ hints’. My understanding is that a segment is a subset of an AZ. So why are we not able to leverage that logic or make it more generic? Thanks Gary On 5/22/16, 4:02 AM, "Carl Baldwin" wrote: >On Fri, May 20, 2016 at 1:44 PM, Brandon Logan > wrote:

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-22 Thread Kevin Benton
This is a little different because it also requires scheduling to multiple segments (i.e. one network will have DHCP instances on every segment). There may be some overlap in filtering candidate agents based on their connectivity properties, but a lot of it will be orthogonal. On Sun, May 22, 2016

Re: [openstack-dev] [neutron] DHCP Agent Scheduling for Segments

2016-05-23 Thread Carl Baldwin
It would be worth looking at the code that adds AZ awareness to DHCP scheduling. There might be something to learn. However, by design, segments and AZs are orthogonal concepts that don't force any kind of correlation. There are segments that span AZs and AZs that span segments. I really want t