This is an update on VCL-291. I have made the changes to all of the relevant
files except for esxthin.pm and committed them. I didn't want to touch
esxthin.pm in case Brian is working on it. The changes are currently being
tested/used in NCSU's production implementation and I have not seen
Aaron Peeler wrote:
makesshgkh is part of xcat1.3(which is EOL'd) and is used to collect the
ssh host keys after the install.
xCAT2.X does something different to collect the ssh host keys, so
eventually makesshgkh and the original xCAT.pm module will not be needed.
Ok, that makes sense.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sounds like a good idea to me.
Josh
On Tuesday January 19, 2010, Andy Kurth wrote:
I'd like to propose a design change for the modularized backend code. The
provisioning modules (xCAT.pm, vmware.pm, etc) are currently responsible
for monitoring
I would consider a node loaded from a provisioning module's standpoint as the
point when the bits are on the node's disk and it has been powered on. After
this point, the OS module is responsible. xCAT detecting the boot state would
be equivalent to successfully turning on the VM.
There is
Another option might be to have a $provision_module-post_load() routine.
Once the new.pm module detects the node is loaded and accessible, it could
call $provision_module-post_load() before moving on to the
$os-post_load().
Aaron
--On January 19, 2010 4:16:16 PM -0500 Andy Kurth
Andy Kurth wrote:
I would consider a node loaded from a provisioning module's standpoint as the
point when the bits are on the node's disk and it has been powered on. After
this point, the OS module is responsible. xCAT detecting the boot state would
be equivalent to successfully turning on
