cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chiradeep Vittal <>
Subject Re: [PROPOSAL] - Change Primary IP Address
Date Thu, 29 May 2014 04:27:29 GMT
Curious: What is the reason to change the primary IP?  Quite un-cloudy.

@Wido: changing the IP in basic zone is quite involved, not just changing a dnsmasq entry.

From: Wido den Hollander <<>>
Reply-To: "<>" <<>>
Date: Wednesday, May 28, 2014 at 2:08 PM
To: "<>" <<>>
Subject: Re: [PROPOSAL] - Change Primary IP Address

On 05/28/2014 04:36 PM, Alex Hitchins wrote:
All, I'd like to submit the below proposal. This can also be found here :

I've started looking into this project although before anything is written
I'd like community thoughts and feedback.

Why only Advanced? I think this feature would benefit Basic Zone
networks as well.

I know that a lot of public cloud offerings use the Basic Zone
networking and would love to see this feature.



Subject: New API call to change Primary IP address after VM creation in
Advanced Zones.

Background: Currently the only way to change the IP address (via the API) is
to drop a NIC attached to the VM and then add a new NIC with the desired new
IP address. The process is as follows:

1. Add Temp NIC
2. Make Temp NIC default
3. Remove original NIC
4. Add NIC on same network as NIC removed in step 3, specifying IP as you
add it 5. Make newly added NIC default 6. Remove Temp NIC

This process works however it will mean the VM will see a new MAC address
which could mean additional configuration is required.

The existing API calls (removeIPFromNic & addIpToNic) only allow the user to
modify the secondary IP addresses. This proposal is to create a new API call
allowing the user to reset the IP address without the need to remove and add
a new NIC.


1. Add a new API call under the NIC section for root & admin users, allowing
them to specify a new IP address for a given NIC e.g. amendIpToNic ( int
nicId, string oldIpAddress, string newIpAddress )
2. The system should check to ensure the new IP address that is being
applied isn't already in use on the network.
3. The API call on success will require the virtual machine to be restarted
for DHCP to be refreshed.
4. The functionality should apply to Advanced Zones.


While we will perform a cursory check to see that the IP address isn't
already in use, no other checks will be made. It will still be up to the
domain administrator to manage IP allocation.

Alex Hitchins
M: 07788 423 969
T: 01892 523 587

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message