hi all,
new to this list. i have started setting up vcl here and clemson university and
this thread has touched on one of the questions i had in trying to do so. do i
assign mac addresses based on what esxi generates? if not, how do i map those
correctly? thanks.
will
On 06/20/2012
thanks michael.
will
On 06/25/2012 09:58 AM, Michael Jinks wrote:
Hi Will.
I believe that VCL requires manually assigning MAC addresses when you
generate the VM records -- you must use the multi-add page under Add
Computers, and have it assign a range of MAC addresses.
Note that VMware uses
Hi Will --
The MAC address range Mike identified below is the best to use. ESXi
expects any manually-assigned MAC addresses to fall within the range
00:50:56:00:yy:zz and 00:50:56:3F:yy:zz [1]. (Note these are
manually-assigned from ESXi's perspective, not VCL's perspective. VCL
generates a
thanks. i'm not sure i want to
blow what i have configured away. i have a colleague working on
this with me who is pretty knowledgeable with mysql. i'm sure i
can get him to help me fix these up. this has also convinced me
to install phpmyadmin to
For the record: the trouble was that we didn't have defined MAC
addresses in our database records for these VM's.
Adding the MAC addresses to the computer database by hand fixed the
issue.
On Tue, Jun 19, 2012 at 04:53:40PM -0500, Michael Jinks wrote:
Hi, all.
Trying to resurrect a thread I
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:
Hi All,
I've been working on an initial spec file for VCL 2.2.1. Currently I
believe all the dependencies, CPAN modules included, can be obtained
from the EPEL and RPMForge repositories. If the project is going to
support RHEL and CentOS only then providing a RPM could allow you to
remove the
11 matches
Mail list logo