Since the early days the assignment of IP can be done either Statical or Dynamic (configurable options). Yet the current method is a pain to work with.
E.g. when configuring a Dynamic or Static package the philosophy would be a minimum setup, base package. This can have 512mb, 1core, 5 GB of disk and 1 IP address. Provisioning this package will be no issue.
The problem / Configurable options
Yet when setting up this within the module it works fine for deploying. But as soon as we add the "ip_addresses" field there will rise a problem. The offset for calculating IP's is 0. Ok, initially the field came as "Extra IP addresses|ip_addresses", but using 0 IPs will override the initial static value (1) with 0. Resulting the VM not to deploy properly and manual intervention is needed. When having the minimal amount set as 1 there will be one IP calculated within the price. Which is not ideally as some of have a base package pricing, which can be displayed on the main website for informational purposes / package pricing.
1) A solution would be to have a minimal offset of 1 IP in the base, nonetheless of the selected configurable options. This will result in a truly "configurable option" and provisional vm's.
2) Second could be an extra checkbox in statical module configuration next to the IP amount where you are able to set the behaviour for the configurable option (additional / override).
Please sign in to leave a comment.