-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Tuesday, June 26, 2012 8:27:07 AM Michael Jinks wrote:
It
looks like Aaron got it right when he directed me to the configuration
settings for the management node, where public-side IP configuration is
set to Static, that apparently means set
No, that's not the problem we're having. (We *did* have that problem,
and just deleting the offending rule file no lnoger works in RHEL 6,
but we fixed it by creating
/etc/udev/rules.d/75-persistent-net-generator.rules as a symlink to
/dev/null). At this point, Linux is doing the right thing
Hello Mike,
I'm curious if the management node set to statically assign the public address.
Can you double check the settings for your management node? Select
Management node- Edit management Node Information and select Edit.
Near the bottom.
With this feature you can define how VCL handles the
Michael
Could you please check that 'eth0macaddress', 'privateIPAddress' and 'hostname'
(in VCL DB) matches 'hardware ethernet', 'fixed address' and 'host-name'
options in dhcpd.conf for the host? Also, /etc/hosts should have an entry
'privateIPAddress hostname' for captured computer.
Can
Hi Aaron.
Ah, sure enough, it is set to Static. Silly me, when I first set this
up I read that to mean don't try to set the public IP, leave it to us
humans to configure.
...Okay, so how would we get that behvior? We'll want our deployed VM's
to come up with predictable IP addresses so that
Hi Dmitri.
DHCP on the backnet works as expected. eth0 is being configured
correctly (gets the expected MAC address, which matches the one in
dhcpd.conf). /etc/hosts is correct for both the private IP and the
(intended) public-side IP.
The problem is that the config file for eth1 is being
Thanks Aaron.
Maybe this will be obvious when we get further into our testing, but how
do you provide access to deployed hosts where the DHCP-assigned
addresses are random? Are you using DynDNS?
On Tue, Jun 26, 2012 at 09:36:52AM -0400, Aaron Peeler wrote:
Set it to dynamic dhcp, this setting
Yes, in the vcl code during the post_load tasks of the OS modules.
There is a step to collect the network configuration of the loaded
node(vm or bare-metal), figure out the publicly assigned address and
then update the database which is then presented to the end-user.
Aaron
On Tue, Jun 26, 2012
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.
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,
That's more or less what we're doing. Here are some details:
The source VM I'm capturing from is not represented in DNS at all.
On my management node in /etc/hosts I have:
10.50.84.15 vcl-linux-template-2-bak
128.135.192.15 vcl-linux-template-2
(The second line is for my reference; it
Ahh, I think you're running into this:
http://markmail.org/message/t2ajnaew5qe4jxul
On Mon, Jun 25, 2012 at 5:55 PM, Michael Jinks mji...@uchicago.edu wrote:
That's more or less what we're doing. Here are some details:
The source VM I'm capturing from is not represented in DNS at all.
On
To clarify: Linux is probably creating an eth2 because it's holding out
that its OLD eth0 (which was in your image) might someday come back.
On Mon, Jun 25, 2012 at 6:22 PM, Mike Haudenschild m...@longsight.comwrote:
Ahh, I think you're running into this:
13 matches
Mail list logo
