Changing IP on existing adapter

[alans09]

I have virtual machine that I need to clone and change network settings.
So I defined it's name and networks. It looks that this is working but.

After clone It just create new adapter with settings. This adapter is even not connected to network (network label). Network connections are empty.

Issue a)
It is possible to connect adapter to some known network/virtual switch

Issue b)
Is there any way how to clone virtual machine and:
1) remove all network adapters and get new one that is connected to specified network (eg. dummy network)
2) edit adapter that exists and change just ip address?

Maybe the 1) feature will be the best but I hope there is possibility for 2 also.

[snobear]

@alans09

ezmomi clone currenlty just adds new adapters. It doesn't edit any existing adapters.

For simplicity's sake, I like your first proposal -- remove any existing adapters and create new ones as needed.

New adapters should be placed in the appropriate VMWare network. If it is not working for you, it could be that your network settings are not set up correctly in your config.yml file.

For example, with the below settings, if you supplied an IP of 172.10.16.50, the adapter would be placed in the network with the "My Internal Net" label.

# List your networks here
networks:
  '172.10.16.0/20':
    datacenter: 'Nashville'
    cluster:    'Nashville Server Cluster'
    datastore:  'Mystore 1'
    network:    'My Internal Net'
    gateway:    '172.10.16.1'

Does that answer your questions and give a good proposed solution?

[alans09]

OK, first proposal is good, but this means I have to create a virtual machine that does not have any adapter at all.

But when I do this I loose a ability to update virtual machine on system that is used for cloning.
OK I'm not loosing it but I'll have to create snapshot without adapter every time machine gets updated.

I have about 40 different OS combinations that I need to clone in the beginning of test automation process. These machines needs to be up to date in every time I need to work with them. So the best for me is to edit virtual adapter. But I can live with this solution it just makes my machine maintenance a little more complex.

[snobear]

Thanks for the reply. I agree that it is convenient to have an adapter configured on the template so that you can convert to a VM and update it periodically. However, with this proposal, your VM templates can still have a virtual adapter.

So, whenever you clone to new VMs, the clones will delete any adapters and create new ones based on the IPs you supplied. The important point here is that the adapter will not be deleted on the template; the template is left untouched.

Does that make sense? Perhaps I'm not totally understanding your scenario?

[alans09]

hmm... so maybe the only problem is that I'm not deploying from template but from real vmware machine.

If deploy is made from machine that is not template it will not remove adapters. This means if I deploy 2 or more machines from let say XP machine. I get 3 machines that have the same IP on one adapter and other on 2nd adapter that is created by using script..

Ok I'm closing this issue now. I will try to use templates instead of real machines.

[snobear]

Currently, ezmomi does not remove existing adapters, regardless of the clone source being a template or regular VM. This "feature" should be added, so I'm reopening the issue.

Sorry, I may have confused you in my last comment. The main points of this discussion are:

• currently, ezmomi only adds new adapters for the IPs supplied. Any existing adapters from the clone source are copied over to the clones.
• the proposal is that ezmomi should NOT copy any existing adapters when creating clones.

That sound clear?

[alans09]

Simple said the proposal is to have same amount of adapters that is defined in config file.

So yes I just want to remove all existing adapters and add only new.

[snobear]

Fixed in #27.