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 t
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
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 the VM.
There is a
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 a
Sounds good.
On the vm modules, we'd need to decide on when a node is considered loaded.
With xcat there is a state we can check, install,image, boot, etc. With vm
we just start the vm, a couple of ideas are, maybe we wait some time period
or until it's pingable, or something else then return i
-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 monitorin
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 and waiting for the computer's OS to respond after an image has been
loaded. It would be better if this task were handled by the OS
