Ability to add an IP without reboot

Completed

Follow

Erik Hensema

January 10, 2013 15:30

We regularly need to add an IP to a server in order to facilitate SSL websites. Currently a reboot of the VM is needed to add an IP to it.

It would be a killer feature to us if we were able to add an IP without reboot (preferably via the API).

This would:

• Add the IP to the OnApp database
• Update the iptables firewall on the HV

This would NOT:

• Rebuild the network on the VM
• Interact with the VM in any way

Of course, when we choose to rebuild the network of the VM at any point in the future, the IP will be added to its configuration in the regular way.

Our internal automation tools will add the IP to the running server.

24

• 

  Ryan MacDonald March 04, 2013 12:13

  This is a pretty huge one, we operate allot of IP space within our cloud stacks and very frequently assign out additional addresses to customers and they are never happy about having us reboot their VM for such a simple task.

  0

  Comment actions Permalink
• 

  David Majchrzak November 28, 2013 10:39

  Should just be like adding another option / hook to the current GUI where you can choose not to rebuild network in the VM.

  0

  Comment actions Permalink
• 

  Derek Gundersen August 01, 2014 16:45

  I know it has been a while since this suggestion was submitted but we have not formally replied to the request. A while back we implemented the UpdateFirewall transaction in OnApp that will update the iptables rules on a hypervisor when an IP address is added to a VM so that the routing rules are in place. You can now add an IP to a VM without a reboot and then manually configure the additional IP address within the VM and the IP will then route to the VM without a reboot. If you would like the OnApp system to configure the IP on the VM then a rebuild network will be necessary, which will reboot the VM. 

  0

  Comment actions Permalink

Please sign in to leave a comment.