[Ovirt-devel] Thinking about a more generic node...

[Darryl L. Pierce]

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/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/ovirt-devel/attachments/20100223/dbea5400/attachment.sig>