ok, np.
I'll go ahead and update both the database and get_vmhost_info routine in
utils.pm.
Encrypting the password - (I think you also mentioned this), but it might
be easier to use plain text on the password field at first and then once
that is working - encrypt the password via some
option 2 - vmprofile table is the definitely the correct location to store
this type of data.
The vmhost table will eventually only have 4 columns
id,computerid,vmlimit,vmprofileid.All additional info about a given
hypervisor should in a profile.
After extending the database - we'll need to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu March 5 2009 3:41:47 pm Aaron Peeler wrote:
option 2 - vmprofile table is the definitely the correct location to store
this type of data.
snip
Whichever table it goes in, here are the lines to be added to the vcl.sql
file:
