Bryan J Smith wrote:
On Mon, 2008-09-29 at 12:05 -0400, Michael DeHaan wrote:
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.

I'm not against that.  The question is how much I should say before I
inherit the workload?  I.e., I try not to push too much "hot air," and
much of my donation is driven by the client.  Right now the client has
me on other priorities, and it's hard to do much GPL "on their
dollar" (long story).  I'll help all I can outside of the client hours,
although I don't know if that's even remotely a dent, given my
unfamiliarity with a lot of the solutions.

I can't say I understand the above, my earlier comments were mainly WRT the idea that system-config-netboot
was going to be maintained again, which I'm not so sure is wise.
Right now I only used s-c-n to do some "proof of concept" (PoC)
discovery/testing, largely so I have something in the lab for testing
(without having to install on systems).  I'm switching more of my gears
back to livecd-tools, and what I can add in %post and other areas to get
things working.  But I'll keep it all in-mind as I do it.

I'm a big fan of just doing things in the context of the live images when possible.

FYI:  https://fedorahosted.org/cobbler/wiki/HowToPxeAnyLiveCd

Here's an example of how to deploy a live CD to an arbitrary network of machines from cobbler, for integration with livecd-iso-to-pxeboot.


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).

I also don't support the infrastructure.  That's an even later
consideration, and something I'll have about a 2% say on (again, don't
get me started).  My entire focus right now is getting a PoC going just
for the thin + server.  But, again, I'll really try to keep Cobbler/Koan
in-mind as I do anything.
If you don't support the infrastructure, then I would imagine you really don't want to support
the infrastructure using s-c-n :)




_______________________________________________
Stateless-list mailing list
[email protected]
http://www.redhat.com/mailman/listinfo/stateless-list

Reply via email to