Versions Compared

Old Version 17

changes.mady.by.user Likitha Shetty

Saved on

compared with

New Version 18

changes.mady.by.user Likitha Shetty

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Admins should be allowed to dedicate a Public IP range to a specific account
  • The range can be dedicated to an account either during the IP range creation or after it has been created
  • In the following scenarios an admin request to dedicate an IP range should fail
    • IP range specified is
    If admin tries to dedicate a
    • non-existent
    • IP range
    or an
    • specified has already been dedicated
    IP range then the request should fail
    • If
    by dedicating the IP address range, the
    • on dedication the account’s Public IP limits
    are exceeded the request should fail
    • will be exceeded
    • Any one of the IPs in the range has already been acquired by a different account 

Creating a Public IP range

...

  • 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 user can acquire IP's 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 any of the IP’s belonging to the range are is in use (load-balancing etc.), the IP range should be released back to the system pool
      •  The IP's that are in use should continue to be acquired by the account in which it is being used
    • If any of the IP’s 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)

...

ApiName

Request parameters

Response parameters

dedicatePublicIpRange 

  • id (id of the Public IP range, type - uuid, required - true)
  • account (account who the Public IP range will be dedicated to, type - String, required - true)
  • domainid (domain ID of the account the Public IP range is dedicated to, type - uuid, required - true)

VlanIpRangeResponse

releasePublicIpRange 

  • id (id of the Public IP range, type - uuid, required - true)

Boolean

...

  • In Infrastructure -> Zones -> <zone> -> <physical network> -> Public under ‘Ip Ranges’
    • If there are no accounts associated with the Ip 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 CreateVlanIpRanges 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 id set to the id of the vlan ip range

...