[chef] Re: [chef-dev] Re: Re: Re: CHEF-3747 - Compile Time Packages

[Jesse Campbell < >]

I see you're implementing this from the perspective of the postgresql gem requiring the postgresql client... I run into the same thing with mysql.

Right now we have to have phases of deploy, which to us means running bootstrap twice or in some cases 3 or 4 times, adding roles as we go.

the simple case for us:
1. mysql gem is required for the mysql cookbook.

2. mysql-devel package is required to build mysql gem

3. yum repositories need to be configured for mysql-devel to install (its a custom package for us)

#1 must be compile time, #2 could be either, and #3 is converge time (using the opscode provided yum resources)

stages would fix this.

-jesse

On Tue, Jan 29, 2013 at 6:40 AM, Bryan Berry < " target="_blank"> > wrote:

big +1 for "phases"  or "stages"

forcing resources to execute during compile-time ultimately breaks
cookbook reusability

I think puppet may already have stages and I am curious how well those
work in practice. I have never used them.
http://docs.puppetlabs.com/puppet/2.7/reference/lang_run_stages.html

On Tue, Jan 29, 2013 at 11:53 AM, Peter Donald < "> > wrote:
> On Tue, Jan 29, 2013 at 11:21 AM, Sean OMeara < "> > wrote:
>>
>> Compile time modification is a hack that should very much be discouraged.
>>
>> I'd rather see something akin to "run stages" where you could force
>> the convergence of a recipe before the compile phase of another.
>
>
> +1
>
> If a single chef run could be multiple stages, where each stage was a
> runlist and each stage compiled and converged before the next stage,  this
> would make my life a lot easier. For bonus points you could make it possible
> to run stages individually and suddenly application deploys would be much
> easier in chef.
>
> --
> Cheers,
>
> Peter Donald