IP address and Hostname for horizontally scaled VM
- Priyadharshini (Tata Elxsi)
- Ramesh Ramanathan (Tata Elxsi)
In the current approach, for horizontally scaled VMs, IP addresses are allocated incrementally and fixed hostname is configured via Cloudinit. In the production environment, IP addresses and hostnames are expected to be configurable for scaled VMs.
Use case 1 : Right now during auto scaling, the next sequence IP of the parent VM is attempted by OSM for scaled VM. The instantiation fails from VIM in case OSM requested IP is not free. Once failed, OSM attempts to reinstantiate using the next sequential IP. This process is repeated until instantiation is successful. This complete process can take huge time until successful IP allocation from VIM. The current mechanism in place is unaware of the subnet mask of IPs and requests incremental IP which is uncontrolled.
Use case 2 : Operators want to provision static IPs for all the VMs for various operational reasons. Right now for parent VM the IPs could be specified, whereas when the VM scales, the next sequential IP is allocated by OSM. Operators want to have control over it and wanted to define specific IP/range/pool for scaled VMs. One of the operational requirement is to keep the VNF specific firewall policies applied in advance for the IP range of that VNF.
Demo or definition of done
A new Robot test will be contributed and the feature will be considered done when the Robot test passes. In the robot test, IP address should be configurable and hostname should be unique in scaled VMs.