Michael DeHaan wrote: > In all fairness, system-config-netboot has largely become irrelevant.
>From the perspective of large number of thin client node deployments sadly yes. s-c-n had been left alone in the dark and at this point in time the demands of features in provisioning and management can be handled reasonably well by stuff in cobbler and puppet/genome > Let's instead talk about what you need in cobbler that isn't there, and > contribute to one common codebase. I think that's a better route. An use case where large number of thin clients are deployed, the demands crop up (as Bryan has mentioned in passing) at various levels: - creating a client image that has remarkably small footprint - provisioning the clients with this small footprint - managing the client boxen in terms of services and diagnostics - bare metal provisioning the client boxes when need arise - client box health monitoring on a reasonable continuum - trapping boot failures and providing ability to diagnose them But these aren't cobbler features and they bubble up to become features of a management tool which would perhaps be using puppet underneath and consuming features being made available via cobbler. -- http://www.gutenberg.net - Fine literature digitally re-published http://www.plos.org - Public Library of Science http://www.creativecommons.org - Flexible copyright for creative work _______________________________________________ Stateless-list mailing list [email protected] http://www.redhat.com/mailman/listinfo/stateless-list
