-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Brian's commit to the vcl.sql file highlighted an issue to me.  The vmprofile 
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 documentation, 
we need to have one of two things:

1) tell users how to create the images that correspond with the entries we 
ship in the image table

or

2) tell users that after they've created their own VM host server images and 
added them to the image table, they need to update the vmprofile through the 
web interface to assign the correct image to the profile

The vmtype table has both vmwareGSX and vmwarefreeserver, which are the same 
thing.  Can we remove one of them?


Brian:  For the "VMware ESX SAN" vmprofile entry you added, you have vmtypeid 
set to 5 which is vmwareESX3.  Should that have been 6 which is vmwareESXi 
instead?  (and maybe vmwareESXi should be vmware ESX3i?).  Also, you have 
imageid set to 9 which is "VMware ESX 3.5 standard server".  There is no 
entry in the image table for an ESX 3i server, but given the above issue, 
there's really no image that would correspond to an entry for it in the image 
table anyway; so, it doesn't really matter that much.

Josh
- -- 
- -------------------------------
Josh Thompson
Systems Programmer
Virtual Computing Lab (VCL)
North Carolina State University

josh_thomp...@ncsu.edu
919-515-5323

my GPG/PGP key can be found at pgp.mit.edu
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFJ3MbLV/LQcNdtPQMRAusZAJoDyLJx68lrr0L5d7C7CoITH3jYoQCfYKKV
kzNCRfCzSwHSMfIrMrxt0JU=
=uVO6
-----END PGP SIGNATURE-----

Reply via email to