Is it possible to use a fenced deployment to NAT IP addresses between vCloud Networks?
Let's say I have two networks defined - a Direct Connect legacy network using 192.168.63.0/24 and a new vCloud Internal Network using 192.168.10.0/24. I want to take VMs which existed before my vCloud Director deployment that have .63 addresses and rely on eachother for application functionality and bring them under vCloud Director Control. I then want to capture them into a vApp, publish it to my catalog, then have users be able to deploy a fenced copy of the vApp, but with .10 addresses as their NATted addresses, but maintain their old .63 addresses inside the fence.
I'm not seeing any way to define a different network for the fence NAT than whatever it can scrounge off the Org vDC Network chosen for the VMs in the first place. Does anyone have any ideas or know of a way I can get things moved without having to re-IP all my legacy servers?