Sankarshan (সঙ্কর্ষণ) wrote:
Michael DeHaan wrote:
- trapping boot failures and providing ability to diagnose them
not sure I understand what a "boot failure" is in this context.
figuring out system-level issues in terms of when a node decided not to
boot up or worse did not get provisioned etc
Yeah, some are, some aren't. You're starting to talk about larger
management solutions for sure.
In a somewhat tangential way I was looking at the genome site and trying
to figure whether all these stuff especially the management and making
management easy via DSLs part is actually converging.
genome solves a particular developer workflow case, I wouldn't say it's
a generic solution or an official convergence point. Is it is one of many
examples of using them in conjunction, similar to what many of the users
of the seperate applications already do, but also dissimilar in many
ways from typical ways folks manage systems that make it not be applicable.
This would probably a very good time to get that discussion going on
those lists (specifically ovirt) if you had specific needs/requirements.
Mostly this area is being handled by ovirt, including a lot of work
around the minimal OS image info, and also how to do lightweight monitoring
and basic hypervisor management.
I agree. Although a traditional PoS kind of thin node looks to be
different from an AOS, it actually isn't so a significant bit of oVirt
roadmap/code should be ready for consumption in both camps
_______________________________________________
Stateless-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/stateless-list
