[[chef-dev]] Re: [[chef-dev]] Bootstrap templates

Bryan McLellan 
<
 >
 writes:

Hi, 

> We're happy with the success of moving the knife cloud providers into
> separate projects, particularly with the increased release cycle for
> the more active ones. We have found ourselves on a similar decision
> path for bootstrap templates. There is a desire to add more operating
> system bootstrap templates [1] to the project, and with that brings
> the possibility of managing many templates that are difficult for us
> to test regularly. How should we manage the matrix of multiple
> operating systems, releases and installation methods?
>
> Our one idea so far is to fork most or all of the bootstrap templates
> into a knife-bootstrap project. There's a little reluctance of the
> overhead of another project, but it seems like it would be a net win.
> Thoughts?

just some offtopic thoughts :)
I dislike the bootstrap templates, they are awful shell scripts and
not idempotent at all, that makes me think they're not compatible with
chef's concepts. ;-)

I'd rather see chroot and remote(ssh) support for resources instead.
That would enable the use of resources/definitions/recipes to
bootstrap nodes and chef clients.

so to answer the initial question: yes create a new project for it !
get it out of chef and let's make chef able to install himself with
its resources and providers ! ;-)

-- 
Laurent