Currently in cloudstack we can add multiple public ip ranges. we want to provide similar flexibility for management and guest ip ranges.
Presently we can add multiple guest ip ranges within the same subnet (Basic zone) but we cannot add ip ranges form different subnets.
This feature provides this functionality for adding guest ip ranges (for Basic zone) and management ip range for both the advanced and basic zones.
There may be cases where some part of the subnet is allocated for some other purpose and the admin wants to use the rest of the ip range or admin may want to add more ip address once the old ones are exhausted. Admin may want to add the ip ranges form the same subnet or from different one. Currently in cloudstack there is no flexibility to do this for management and guest ip ranges (ip ranges from different subnets).
Basic zone guest IPs.
presently the createVlanIpRange api is used to add the guest ip range to a network (shared) in basic zone. The ips mentioned in this range are assigned to the guest VMs. These are public ips and allow guest to communicate with the internet. Presently we can add multiple ranges form the same subnet but not from a different one. This feature will extend the createVlanIpRange to add guest ips from a different subnet to a shared network in basic zone.
API Name |
API parameters |
API response |
Available only for root admin |
|---|---|---|---|
createVlanIpRange |
Using the existing parameters. no new parameters will be added |
returns the ip ranges |
yes |
for description of existing parameters please
Validation.
#1 Will fail if the zone is not a basic zone or if forvirtual network is true.
#2 if the ip is from a different subnet, netmask and gateway should be provided.
Implementation detail.
In cases where a ip range form a different subnet is added, we need to configure an nic with a ip form the this new subnet or add this ip from different to the existing nic. This is required as the ip to the guest VMs is allocated using a DHCP server. So the router should have a interface on the new subnet.
execution flow.
#1 validate the inputs.
#2 if the ip range is form the new subnet add the new range.
pick one of the ips form the new range and configure a interface with this ip on the VR.
configure the DHCP server to listen on this new interface.(Also need to configure the DHCP server to work with the new interface.)
#3 if not form a different subnet add them.
Note. The admin should manually configure the gateway of the new subnet before adding the ip range.
For Basic and Advanced Zone Management(pod) IPs.
Currently there is no way to add additional pod ip ranges. This feature will enable adding pod IP ranges from same subnet or different subnet. The pod ipranges are assigned to router vms and systemvms. The ip configuration is passed in as boot args. So in this case we need not configure the DHCP server.
API Name |
API parameters |
API response |
Available only for root admin |
|---|---|---|---|
AddPodIpRange |
*podId, *IpaddressStart, IpaddressEnd, *Netmask, *Gateway. |
returns the IP ranges of the pod |
yes |
Description of parameters.
Parameter Name |
Description |
required |
|---|---|---|
podID |
specifies the id of the pod to which the new range is added |
true |
IpaddressStart |
starting address of the IP range |
true |
IpaddressEnd |
ending address of the IP range. use the entire cidr if not specified. |
false |
Netmask |
Netmask of the subnet |
true |
Gateway |
Gateway of the subnet |
true |
validation.
#1 We modify the checkpodAttributes function in configurationManagerImpl by removing the check for IP ranges which do not belong to the same cidr (cidr of the pod.)
execution flow.
#1 validate the input.(This will be done using the checkpodAttributes function of the configureationManagerImpl).
#2 Add the new range.
No Database changes are required.