The commits I made on 2/26 extended the state modules with the new flow
described in this thread. Up to this point, nothing has functionally changed
because none of the provisioning or OS modules have been committed which have
been modified to use the new flow.
The image capture flow changes
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:
