Yes, one of the two vmwareGSX and vmwarefreeserver entries in the
vmtype table should be removed because they are redundant.
Speaking of redundancy in the vmtype table vcl.sql file, I'm confused
about why there are independent entries for ESX and ESX 3i. The
esx.pm provisioning module uses the VMware API (http://www.vmware.com/support/pubs/sdk_pubs.html
) which is designed by VMware to be identical with ESX and ESX 3i.
This way, folks like us don't have to implement custom code for one
ESX vs ESX 3i. Because of this, does it even matter which
vmprofile.vmtypeid was added to the vcl.sql file? What do you think?
Given that VCL can't deploy ESX 3i (the free version), I propose VCL
shouldn't mess with the 3i hypervisors until this can be revisited as
a larger issue. As a fix, how about if we set the vmprofile.imageid
to 4 (No Image) because of this? What do you think?
Secure Open Systems Initiative
On Apr 8, 2009, at 11:46 AM, Josh Thompson wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Brian's commit to the vcl.sql file highlighted an issue to me. The
table includes an imageid field. Even though we don't ship any
images, we do
ship entries in the image table to serve as examples. In our
we need to have one of two things:
1) tell users how to create the images that correspond with the
ship in the image table
2) tell users that after they've created their own VM host server
added them to the image table, they need to update the vmprofile
web interface to assign the correct image to the profile
The vmtype table has both vmwareGSX and vmwarefreeserver, which are
thing. Can we remove one of them?
Brian: For the "VMware ESX SAN" vmprofile entry you added, you have
set to 5 which is vmwareESX3. Should that have been 6 which is
instead? (and maybe vmwareESXi should be vmware ESX3i?). Also, you
imageid set to 9 which is "VMware ESX 3.5 standard server". There
entry in the image table for an ESX 3i server, but given the above
there's really no image that would correspond to an entry for it in
table anyway; so, it doesn't really matter that much.
Virtual Computing Lab (VCL)
North Carolina State University
my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
-----END PGP SIGNATURE-----