Hi Mike,

I handle this by running DHCP on the private VCL network, assigning MAC 
addresses to specific VMs so as to make them predictable. Then add each hosts 
PRIVATE IP to the management node's /etc/hosts file. This will force the 
management node to resolve the compute name to the private IP, instead of the 
public IP (which is probably coming from your DNS server). 


Sent via iPhone

On Jun 25, 2012, at 15:45, Michael Jinks <mji...@uchicago.edu> wrote:

> Hi List.  Still trying to get a successful capture and deploy to run;
> here's my latest glitch.
> In the VCL web interface, under "Manage Computers" -> "Edit Computer
> Information", there's a single field for "IP address".  I've been
> entering the private-side IP address for VM's I'm trying to capture.
> ...But, a few minutes ago I realized that VCL is using that field to
> rewrite my VM's public-facing address configuration during the capture
> process.  Needless to say, that causes a failure when the captured VM
> boots.
> So, I tried filling the "IP Address" field with the public-side address,
> but that causes a failure when we try to capture the image, because vcld
> tries to ssh to that address, which is obviously wrong, as the VCL ssh
> key is trusted on the private-side sshd instance.
> What should I be doing instead?  Is there any way to get the correct
> address set for the public and private interfaces?  Do I have to do this
> by hand in the database?
> -- 
> Michael Jinks :: mji...@uchicago.edu
> University of Chicago IT Services

Reply via email to