Versions Compared

Old Version 26

changes.mady.by.user Likitha Shetty

Saved on

compared with

New Version Current

changes.mady.by.user Likitha Shetty

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

  • 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 IPs belonging to the range is in use (load-balancing etc.), the IP range should be released back to the system pool
      •  The IPs that are in use should continue to be acquired by the account in which it is being used
    • If any of the IPs have been acquired but are not in use then the IP’s IPs should be disassociated and the entire range should be released back to the system pool (keeping with the current behavior)

...

Web Services APIs

New API’s

ApiName

Request parameters

Response parameters

dedicatePublicIpRange 

  • id (id of the Public IP range, type - uuid, required - true)
  • account (account 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

...

Parameter name

description

id

primary key

account_db_id

account the Public IP range is dedicated to

vlan_db_id

db id of the VLAN Public IP range

Enhancement

  1. Add a zone level configuration to configure if an account can acquire IP's IPs from the system pool once the account has exhausted all of its dedicated Public IP's IPs (default set to true).

A new global config use.system.public.ips

  • To allow root admin to disallow any account from acquiring public IPs from the system if the account has dedicated public IPs and these dedicated public IPs have all been consumed.

...

  •  
  • Will be configurable at the account level too.
  • Default value is true.

Usage

Dedication by admin is equivalent to users acquiring IP and hence user should be charged from the time an IP is dedicated

  • When an IP is dedicated usage event 'EVENT_NET_IP_ASSIGN' should be published 
  • If an IP is dedicated event 'EVENT_NET_IP_ASSIGN' should not be published when the dedicated IP is acquired
  • When a dedicated IP is released from an account event 'EVENT_NET_IP_RELEASE' should be published only when the the range of IPs it belongs to is released back to the system pool and not when an account that has acquired the IP releases it

Test cases

TBD

Usage

...