[chef] Re: Re: Chef/Foreman Integration

[Daniel DeLeo < >]

On Tuesday, February 3, 2015 at 2:49 PM, JJ Asghar wrote:
> Hi Soheil,
>  
> Yeah it looks like it also assumes that you leverage yum/apt to
> install chef also. you might want to look into just doing a curl -L
> https://chef.sh ;| sudo bash instead of the yum install chef line.
>  
> Granted this'll install chef not chef-dk.
>  
> It's a place to start, i wish i could be more help.
> Best Regards,
> JJ Asghar
> c: 512.619.0722 t: @jjasghar irc: j^2
>  
>  
> On Tue, Feb 3, 2015 at 3:11 PM, Soheil Eizadi 
> <
 
>  
> (mailto:
 )>
>  wrote:
> > I am trying to figure out best practice to boostrap a Node using Foreman
> > with chef-dk, the current reference on Foreman does not reference the
> > chef-dk:
> > http://projects.theforeman.org/projects/foreman/wiki/Chef-deployment
> >  
> > Thanks,
> > -Soheil
>  


For your non-workstation systems, the Omnibus chef-client packages should be 
sufficient; ChefDK packages in extra testing and workflow tools that are 
generally more relevant on your workstation (though you may find them useful 
for build nodes if you run cookbooks through a Ci pipeline of some sort).

The workstation side would mostly come into play if you create new systems by 
running a bootstrap process from the command line on your workstation (e.g., 
`knife bootstrap` or similar). In that case, you’d need to either customize 
the bootstrap script to install the foreman stuff before it runs 
`chef-client`, or you could use Chef to install it. Downside of the second 
option is that the foreman integration probably wouldn’t work until 
`chef-client` runs for a second time.

--  
Daniel DeLeo