Public bug reported: This RFE is related to the bug [1].
Now the response of network-ip-availabilites api contains: (1) total_ips (2) used_ips (1) total_ips - subnet cidr, when there are no allocation pools in the network - the sum of ips in each allocation pool, when there are allocation pools in the network (2) used_ips - the number of used ips in the network (does not consider allocation pools) We cannot know how many available ips are in the allocation pools from the response. There are use cases that we need to know the number of available ips in the allocation pools, such as check ip availability before create a vm in the network. Therefore, I suggest add more information to the response, so the response would have four information: (1) the total number of IP addresses of a subnet (2) the total number of IP addresses in allocation pools (3) the number of used IP addresses of a subnet (<- it is same as the response of the current "used_ips" IIUC) (4) the number of used IP addresses from allocation pools >From comment #19 in [1], it appears this has already been discussed in drivers meeting. [1] https://bugs.launchpad.net/neutron/+bug/1843211 ** 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/2107316 Title: [RFE] Add more information to network-ip-availabilites response Status in neutron: New Bug description: This RFE is related to the bug [1]. Now the response of network-ip-availabilites api contains: (1) total_ips (2) used_ips (1) total_ips - subnet cidr, when there are no allocation pools in the network - the sum of ips in each allocation pool, when there are allocation pools in the network (2) used_ips - the number of used ips in the network (does not consider allocation pools) We cannot know how many available ips are in the allocation pools from the response. There are use cases that we need to know the number of available ips in the allocation pools, such as check ip availability before create a vm in the network. Therefore, I suggest add more information to the response, so the response would have four information: (1) the total number of IP addresses of a subnet (2) the total number of IP addresses in allocation pools (3) the number of used IP addresses of a subnet (<- it is same as the response of the current "used_ips" IIUC) (4) the number of used IP addresses from allocation pools From comment #19 in [1], it appears this has already been discussed in drivers meeting. [1] https://bugs.launchpad.net/neutron/+bug/1843211 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/2107316/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
