Yep, that answers my question. Thanks! On Thu, Feb 18, 2010 at 10:05 PM, James Patrick Sigmon <jpsig...@ncsu.edu>wrote:
> Jeff, > > I think this answers what you are asking. > > When you make a reservation for a vmware-type-image, vcl uses a vmguest > (virtual machine) to load that image on. That image will receive the mac > addresses and the ip addresses from you vmguest. > > If you want to make say 10 concurrent reservations, you will need to make > 10 vmguests with different private ip address (and public if using static) > and mac addresses. > > Hope this helps, > > Patrick Sigmon > North Carolina State University > > On Feb 19, 2010, at 12:09 AM, Jeffrey Wisman wrote: > > > It seems that either my understanding of the VCL provisioning engine is > > wrong, or it isn't working right. I can't create subsequent reservations > to > > the first. I have "computers" available in the computers table. I have > the > > image. I do not have virtual machines created for the guests though, as > I > > thought that would happen as part of the provisioning process. > > > > So in re-reading this, I realize I need to specify a mac address for each > > "computer". This would indicate a real virtual machine existing, right? > As > > of now, there are no virtual machines so there are no mac addresses I can > > specify. > > > > Am I misunderstanding, or do I need to create 10 virtual machines to go > with > > my 10 "computers" and then assign the mac address from each virtual > machine > > to each computer? This doesn't seem especially scalable, so I hope I'm > > misunderstanding and that there is really something else going on. > > > > Let me know if I'm on the right track. > > > > Thanks, > > Jeff > > > > > > On Sun, Feb 7, 2010 at 9:35 PM, James Patrick Sigmon <jpsig...@ncsu.edu > >wrote: > > > >> Hey Jeff, > >> > >> It looks like you have not filled in your mac address information for > your > >> virtual machine. Vmware likes a particular format for this. Try > >> 00:50:56:2A:3B:00 for eth0macaddress and 00:50:56:2A:3B:01 for > >> eth1macaddress. > >> > >> The field "IPaddress" corresponds to the "public" address. Though, I > don't > >> think this will matter here. A public IP address typically will be > generate > >> for your machine. Try a reservation with the mac addresses and see if > that > >> fixes this. > >> > >> You may have already done these steps but I thought I would add them to > be > >> safe: > >> > >> You should have an entry for your virtual machine in your /etc/hosts > file. > >> (ex. 10.75.144.15 csuvm15). > >> > >> You should also have an entry in your dhcpd.conf file as well for each > >> virtual machine. > >> > >> Hope this helps, > >> > >> Patrick > >> > >> > >> On Feb 8, 2010, at 12:14 AM, Jeffrey Wisman wrote: > >> > >>> We're now at the point where we can create reservations and virtual > >> machines > >>> get loaded with images. The issue we're having is that the virtual > >> machines > >>> come up on their private IP addresses only. The reservation screen > shows > >>> the private IP and the RDP file has that IP in it. We have the virtual > >>> machines configured with two interfaces - one on the private network > for > >> VCL > >>> admin stuff, and the other on the public network where we have the > campus > >>> DHCP server configured to give it an IP. However, it doesn't seem to > be > >>> working, or at least if it is getting a public IP, VCL isn't telling us > >> what > >>> it is. > >>> > >>> I'm wondering if the issue is in the database. Each virtual machine has > >> an > >>> "IPaddress" and a "privateIPaddress". On our virtual machines, they > are > >> set > >>> to the same thing. Here is an example: > >>> > >>> mysql> select * from computer; > >>> > >> > +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+-------+------------+-----------+---------+-----------------------+-----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+ > >>> | id | stateid | ownerid | platformid | scheduleid | currentimageid | > >>> preferredimageid | nextimageid | imagerevisionid | RAM | procnumber | > >>> procspeed | network | hostname | IPaddress | > >>> privateIPaddress | eth0macaddress | eth1macaddress | type | > >>> provisioningid | drivetype | deleted | notes | lastcheck | location | > dsa > >> | > >>> dsapub | rsa | rsapub | host | hostpub | vmhostid | vmtypeid | > >>> > >> > +----+---------+---------+------------+------------+----------------+------------------+-------------+-----------------+-------+------------+-----------+---------+-----------------------+-----------------+------------------+----------------+----------------+----------------+----------------+-----------+---------+-------+-----------+----------+------+--------+------+--------+------+---------+----------+----------+ > >>> <snip> > >>> | 24 | 2 | 1 | 1 | 1 | 4 > >>> | 0 | 0 | 0 | 512 | 1 > >>> | 2000 | 1000 | csuvm15 | 10.75.144.15 | > >>> 10.75.144.15 | NULL | NULL | virtualmachine > >>> | 4 | hda | 0 | NULL | NULL | NULL | > >> NULL > >>> | NULL | NULL | NULL | NULL | NULL | 1 | NULL | > >>> > >>> > >>> Should one be NULLed out or set to something else? Should we put all > the > >>> private entries in the /etc/hosts file of the VMWare management server? > >>> Currently I haven't done that, but read it in one of the posts here. > Any > >>> other ideas? > >>> > >>> Thanks, > >>> Jeff > >> > >> > >
