| Thread Previous • Date Previous • Date Next • Thread Next |
Following a discussion in the latest L3 team meeting[1], we're going to
mark this bug as invalid for the following reasons.
First, nothing currently prevents a port having a fixed-ip outside the
allocation pools of a subnet, provided that it falls within the CIDR.
Allocation pools exist only for defining which IPs should be
automatically handed out by neutron. Users can choose any ip from the
subnet, regardless of allocation pools.
Second, in order to achieve this you have a choice of two approaches -
either you force a change of all allocations on the subnet to come from
the new allocation pool, or you require the manual deletion of all
allocations before resizing the pool. In the first case, this could
cause unexpected and unnecessary interruptions to VMs on the subnet. In
the second case, this would be no different from the current situation,
where fixed ips can be updated to come from the new pool if desired.
Third, this is effectively a breaking change to the api for users of the
system as it currently exists.
If you think we've missed an important reason for this bug to remain
open, please let us know. Thanks.
[1]
http://eavesdrop.openstack.org/meetings/neutron_l3/2017/neutron_l3.2017-03-09-15.00.log.txt
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1634330
Title:
[RFE] add verification when narrowing allocation pool
Status in neutron:
Invalid
Bug description:
problem
the step to describe the proble:
1.before ,we create a network and subnet(which the cidr is 192.168.10.0/24)
and the allocation pool is 192.168.10.2,192.168.10.254.
2.we create some virtual machines ,which the ips are 192.168.10.2,192.168.10.3 and so on.(disable dhcp service)
3.Now we want to narrow the allocation pool,changing to 192.168.10.10,192.168.10.50.
we update the subnet ,this operation can succed.
4.But ,like the ip(192.168.10.2,192.168.10.3) belong to the vms ,how to deal with them?
the ip of vm is not in the new allocation pool ,but it's correlated wit that subnet
5.we wish to add verifications taking the ips of vm into account,
when narrowing the allocation pool
solution
The ipaddress of vm in ipallocation must belong to a ipallocationpools when narrowing the range of allocation pool.
we get the ipallocation from db
verify the allocation poll with the vm ips
if not ,raise IPAllocationNotInAllocationPools
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1634330/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
