Page History

...

• If a user trying to acquire the IP belongs to an account that has a dedicated IP range then an IP from the dedicated range should be chosen
  • If all the IP’s dedicated to the account have been acquired then the request should failuser can acquire IP's from the system pool
• If a user trying to acquire the IP belongs to an account that has no dedicated IP range then an IP from the system pool should be chosen 

...

• In Infrastructure -> Zones -> <zone> -> <physical network> -> Public under ‘Ip Ranges’
  • If there are no accounts associated with the Ip range show an Add button next to the range
    • If the button is clicked provide the same widget as the one for CreateVlanIp Ranges that allows the admin to provide account name and domain
    • Action to perform – Call DedicatePublicIpRange API with id set to the id of the vlan ip range and account and domainId set to the values provided in the button
• In Infrastructure -> Zones -> <zone> -> <physical network> -> Public under ‘Ip Ranges’
  • Add an action to remove the account the IP range is dedicated to
  • Action to perform – Call ReleasePublicIpRange API with vlanid id set to the id of the vlan ip range

...

Current DB configuration for dedicated Public IP range,

In table Table ‘account_vlan_map’ will have has an entry for every Public IP range that is dedicated to an account

...

Enhancement

...

1. Add a zone level configuration to configure if a tenant can acquire IP's from the system pool once the tenant has exhausted all Public IP's dedicated to it with default value set to true

Test cases

TBD

Usage

TBD