yahoo-eng-team team mailing list archive

[Pavel Bondar <pbondar@xxxxxxxxxxxx>]

Public bug reported:

Currently ipam driver is called on subnet_update only if allocation_pools set in subnet dict. See [1].
This happens because original design expectation is that the only information ipam driver 
has to update is allocation pools.
For reference ipam driver that is absolutely correct.

But 3rd party ipam vendors might want to utilize this call to keep track of other fields updates in subnet.
So my suggestion here is to call update_subnet in ipam_driver on each subnet update
and let ipam driver decide if it has to do some processing or not.

In Infoblox we need it to keep track of dns_nameservers on subnet_update.
Currently we can obtain this dns_nameservers  info on subnet update only if allocation_pools present in subnet_update request.

Is it a bug from neutron perspective?

[1]
https://github.com/openstack/neutron/blob/master/neutron/db/ipam_pluggable_backend.py#L356

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1534625

Title:
  [Pluggable IPAM] Ipam driver is not called on update subnet if
  allocation pools are blank

Status in neutron:
  New

Bug description:
  Currently ipam driver is called on subnet_update only if allocation_pools set in subnet dict. See [1].
  This happens because original design expectation is that the only information ipam driver 
  has to update is allocation pools.
  For reference ipam driver that is absolutely correct.

  But 3rd party ipam vendors might want to utilize this call to keep track of other fields updates in subnet.
  So my suggestion here is to call update_subnet in ipam_driver on each subnet update
  and let ipam driver decide if it has to do some processing or not.

  In Infoblox we need it to keep track of dns_nameservers on subnet_update.
  Currently we can obtain this dns_nameservers  info on subnet update only if allocation_pools present in subnet_update request.

  Is it a bug from neutron perspective?

  [1]
  https://github.com/openstack/neutron/blob/master/neutron/db/ipam_pluggable_backend.py#L356

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1534625/+subscriptions