The consensus is that Neutron has enough existing primitives to address
user's expectations when dealing with dualstack environments.
The situation that prompted this RFE where address exhaustion on one
subnet may lead to a user facing error may be prevented by being
explicit on what subnet to all
We took a look at this again during the Austin '16 summit, let's see if
we can resurrect this.
** Changed in: neutron
Status: Expired => Confirmed
** Changed in: neutron
Assignee: (unassigned) => Sean M. Collins (scollins)
--
You received this bug notification because you are a memb
[Expired for neutron because there has been no activity for 60 days.]
** Changed in: neutron
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1372441
Ti
3 matches
Mail list logo