Bryan J Smith wrote:
On Mon, 2008-09-29 at 11:37 -0400, Michael DeHaan wrote:
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.
Most of my issues are outside of the provisioning route.
The s-c-netboot utility does handle a few, other details.
Otherwise, I agree with your commentary for provisioning.
Yes, I am somewhat aware of those.
Rather than cleaning up s-c-n, how about making the other bits a
seperate project for setup of the stateless images (fedora hosted would
be excellent for this), and looking at how we can integrate with
Cobbler. That way we can leave s-c-n properly deprecated, as it should be.
A major issue is that s-c-n doesn't scale to datacenter size deployments
when dealing with provisioning and integration with provisioning /is/
going to be important, even if it's just making sure the right
kernel/initrd rolls out to the right networks and you're not doing
installations. More than likely though, you'd be doing /some/
installations, and some statelessy-things (see ovirt -- the host is
largely stateless while the guests are traditionally installed over
traditional means).
--Michael
_______________________________________________
Stateless-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/stateless-list
