Hi,
We are trying to use the cloning/customization workflows with RHEL 6.1 and, at the most basic level, getNumberOfNic() isn't working. In the same workflow, choosing a Windows VM returns a value of 1.0, but Linux, 0. After that there are mess of network related issues most likly because the workflow can't bind to the vm to get information.
The VM has the latest VMware Tools running, (hosted on an ESXi 4.1.0 host).
Any ideas?
Thanks,
Jim
So, I figured out that getNumberOfNic() doesn't have VirtualVmxnet3 as an option.
Does vCO not support this NIC type?
The library workflows for clone/customize indeed are missing support for that nic type due to that action not being updated. Here's what you can do as a work-around:
var devices = vm.config.hardware.device;
var sourceVirtualEthernetCard = null;
if (nicPosition <= 0 || nicPosition > 5) nicPosition = 1;
var actualPos = 1;
for (var i in devices) {
if (devices[i] instanceof VcVirtualE1000 || devices[i] instanceof VcVirtualVmxnet || devices[i] instanceof VcVirtualPCNet32 || devices[i] instanceof VcVirtualVmxnet2 || devices[i] instanceof VcVirtualVmxnet3) {
if (actualPos++ == nicPosition) {
System.log("Found a Virtual Ethernet card at " + i + ". Key: " + devices[i].key);
sourceVirtualEthernetCard = devices[i];
}
}
}
I have had to do this in a number of the projects I have worked on as well. The code snippet above is nearly identical to that of the action... I simply added a check for the VMXnet3 type
Please note that the action HAS BEEN UPDATED in vCO 4.2 and newer so that the VMXNet3 NIC is recognized. If your action requires the code change I provided above to work, then you must be using an older version of vCO.
We're on 4.1.1. The problem seems to run a bit deeper, so I'm not sure how you got that working. I started tracing the path and had to change probably 3 workflows and four or five custom actions. I'll try your method while we see if we can get 4.2 in house.
4.2 upgrade wont be happening as we're not going to vSphere 5 in the immediate future.
Just as an FYI, vSphere 5 is not REQUIRED to use vCO 4.2 4.2 DOES work with vCenter 4.x
Is that an officially support scenario?
The release notes aren't clear on that:
http://www.vmware.com/support/orchestrator/doc/vcenter-orchestrator-42-release-notes.html
The documentation points to the compatability matrix which doesn't say it is supported:
http://www.vmware.com/resources/compatibility/sim/interop_matrix.php
I looked into the code of VC plugin for vCO 4.2 and vCO 5.0 and I can confirm that there is support for VirtualVmxnet3 (since vCO 4.2). I can say also that we have backward compatibility and it is true that vCO 4.2 can work with vSphere 4.1, but I do not know why the documents do not state this clearly.
Docs point to the VMware Product Interoperability Matrixes, because it is hard to maintain this information at two places. Will try to figure out how to get the matrixes updated.
vCO 4.2 works with vCenter Server 4.1. This is stated in the Installation and Configuration docs.
There are three issues here, both which need clarification.
1. Does vCO 4.1.1 on vCenter 4.1 support Vmxnet3? The class is there and we have successfully wired up all of the workflows and custom actions. (This is of particular importance as we need to decide on how to move forward with our configuration.)
2. Based on the answer to number 1, is this an officially supported configuration?
3. Is vCO 4.2 on vCenter 4.x an officially support configuration?
"It works" is not sufficient. We need to maintain our systems and deliverables in a supported configuration. The documentation and website need to clearly reflect that.
Thanks for looking into it.
Jim
Any update?
Sorry for the late reply.
... to your questions...
1. Does vCO 4.1.1 on vCenter 4.1 support Vmxnet3? The class is there and we have successfully wired up all of the workflows and custom actions. (This is of particular importance as we need to decide on how to move forward with our configuration.)
2. Based on the answer to number 1, is this an officially supported configuration?
3. Is vCO 4.2 on vCenter 4.x an officially support configuration?
My answers are:
1. Does vCO 4.1.1 on vCenter 4.1 support Vmxnet3? -> Yes - vCO 4.1.1 on vCenter 4.1 supports Vmxnet3
2. Is this an officially supported configuration? -> I can't say, because I do not see it in the compatibility matrix on the official site. We will need some time to investigate this and eventually to update matrix. We’ll have the answer in near future, but I can't say exactly when.
3. Is vCO 4.2 on vCenter 4.x an officially support configuration? -> vCO 4.2 is compatible with vCenter Server 4.1. Currently we’re making the necessary steps to update the matrix with this info.
Best Regards.
Thank you! I'll wait patiently for official answer.