So in working on making the node more generic, I've initially taken on the startup processes. Right now I have patches that I'm finishing which will give a more generic way of performing the following functions:
* AWAKE - notify the management system the node is awake
* READY - notify the management system the node is ready to perform
tasks and run VMS
* OFFLINE - notify the management system the node is going offline
What are other points we need to consider regarding the node's state and
lifecycle? I'm looking to explore what should be our initial set of
generic APIs that a management system would want to have available on a
node to make use of it.
Ideas?
--
Darryl L. Pierce, Sr. Software Engineer @ Red Hat, Inc.
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
pgpaKnm3fZN6b.pgp
Description: PGP signature
_______________________________________________ Ovirt-devel mailing list [email protected] https://www.redhat.com/mailman/listinfo/ovirt-devel
