Page History

...

• A Public IP range can be dedicated to an account only during the creation of the range
• If an admin dedicates an IP range to an account then all the IP's IPs of that range get acquired by a single isolated network in that account during dedication
• When a network that has a dedicated IP range is deleted, the mapping between the account that owned the network and the IP range persists
• Even if a range is dedicated to an account, any network that belongs to this account including the one that has acquired the IP's IPs can acquire more IP's IPs from the system pool
• An IP range that has been dedicated to an account cannot be released back to the system pool

...

• 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 IPs dedicated to the account have been acquired then the user can acquire IPs 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 

...

• Admin should be allowed to release a Public IP range that is dedicated to an account back to the system pool
  • Even If one/more of the IP’s belonging to the range is in use (load-balancing etc.), the IP range should be released back to the system pool
    •  The IP's IPs that are in use should continue to be acquired by the account in which it is being used
  • If any of the IP’s IPs have been acquired but are not in use then the IP’s should be disassociated and the entire range should be released back to the system pool (keeping with the current behavior)

...

• No change from the existing CloudStack behavior
  • If one/more of the IP’s IPs belonging to the range is in use (load-balancing etc.), deletion will fail
  • If any of the IP’s IPs have been acquired but are not in use and if the range is dedicated then the IP will be disassociated and the range will be deleted

...