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
Thanks to everyone for the feedback. I'll begin working on the proposed changes
today.
Thanks,
Andy
Aaron Peeler wrote:
I like these changes also, this falls in line with our overall
modularization goal.
Aaron
--On February 12, 2009 3:48:30 PM -0500 Andy Kurth
wrote:
I would like to be
I like these changes also, this falls in line with our overall
modularization goal.
Aaron
--On February 12, 2009 3:48:30 PM -0500 Andy Kurth
wrote:
I would like to begin defining and documenting the API for the backend
code as people are actively working on developing new modules. I have
b
I like these proposed changes, and am for them. This neatly solves the issue
of having provisioning modules needing to shutdown or reboot machines at the
appropriate time. Now, xcat can reboot the machine when it's has all the pxe
files in place, while the vmware or esx modules can shut it down to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Andy,
What you have proposed makes sense to me. I vote to go ahead with it.
Josh
On Thursday February 12, 2009, Andy Kurth wrote:
> I would like to begin defining and documenting the API for the backend code
> as people are actively working on deve
I would like to begin defining and documenting the API for the backend code as
people are actively working on developing new modules. I have begun some pages
on the Confluence site and would like to start discussing this.
API development is somewhat related to the image capture and modularizat