yahoo-eng-team team mailing list archive

[Shraddha Pandhe <spandhe.openstack@xxxxxxxxx>]

Public bug reported:

We (Yahoo) have some use cases where it would be great if following
information is associated with the subnet db table

1. Rack switch info
2. Backplane info
3. DHCP ip helpers
4. Option to tag allocation pools inside subnets
5. Multiple gateway addresses

We also want to store some information about the backplanes locally, so
a different table might be useful.

In a way, this information is not specific to our company. Its generic
information which ought to go with the subnets. Different companies can
use this information differently in their IPAM drivers. But, the
information needs to be made available to justify the flexibility of
ipam. In fact, there are few companies that are interested in some
having some of these attributes in the database.

Considering that the community is against arbitrary JSON blobs, I think
we can expand the database to incorporate such use cases. I would prefer
to avoid having our own database to make sure that our use-cases are
always shared with the community.

** Affects: neutron
     Importance: Undecided
         Status: New


** Tags: rfe

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

Title:
  Extend IPAM tables to store more information helpful for IPAM drivers

Status in neutron:
  New

Bug description:
  We (Yahoo) have some use cases where it would be great if following
  information is associated with the subnet db table

  1. Rack switch info
  2. Backplane info
  3. DHCP ip helpers
  4. Option to tag allocation pools inside subnets
  5. Multiple gateway addresses

  We also want to store some information about the backplanes locally,
  so a different table might be useful.

  In a way, this information is not specific to our company. Its generic
  information which ought to go with the subnets. Different companies
  can use this information differently in their IPAM drivers. But, the
  information needs to be made available to justify the flexibility of
  ipam. In fact, there are few companies that are interested in some
  having some of these attributes in the database.

  Considering that the community is against arbitrary JSON blobs, I
  think we can expand the database to incorporate such use cases. I
  would prefer to avoid having our own database to make sure that our
  use-cases are always shared with the community.

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