Here is the scenario that has happened to us.
Our open nebula server connects to our vcenter instance to deploy vm’s. We have imported the virtual networks from vcenter into open nebula and have deployed a few hundred vm’s across 2 virtual networks with no problems.
we had a hardware failure on one of our vmware hosts a few weeks ago and so we had to restore the open nebula system from a backup, about 6-8 hours back. This caused some of the vm’s deployed by open nebula to remain on the vmware host without open nebula being aware of their presence. This was OK as we just removed these non crtical systems since that was acceptable in our particular environment and moved on.
Now a week or so later we are seeing a strange symptom that I am not sure if it’s related. Our vm’s are sometimes deploying with duplicate mac addresses even after the old ones are gone. I cannot seem to find any of the obvious commonalities to figure out why the mac address is being duplicated.
I would prefer to have vmware do the “auto” mac address feature instead, so that mac address conflicts cannot exist. is there a way to do this rather then the open nebula static assignment of mac addresses? if not, does anyone have any help to offer with this one?