Right, you basically capture the image and on that image make sure you have the VEM injected in it I believe. My sticking point is that when I need to add a node to a cluster I have to request both physical and virtual ports for my node. So the physical ports are configured and hooked into the physical server, trunks applied to the physical ports. However on my vmk ports for the ESXi Node I would have dvport 18 for service console, 118 for vmotion, 225 for iscsi1 and 226 for iscsi2. The rest of the ports on the virtual switch are in a shut state. So you could automatically grab one but it will be in a blocked state or even worse you could grab one that has been pre allocated to a virtual machine.
So now that we have that out of the way, what I am wondering is since Host Profiles mentions nothing about "ports" and only references the "port-profile" is there a way that I can inject this field or have it pull this data from somewhere else IE file share, something....
I know I can do stateful with the method we have now, but to me that doesnt buy you a whole lot. We would really like to get to stateless with caching.
