Bootstrapping chef


#1

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the
biggest pains we have is getting Chef to work on a new platform. Once
Chef works we leave the world of crappy shell scripts and enter the
world of Chef.

Has anyone come up with any nice scripts to get Chef and its
dependencies installed and happy on a variety of platforms/images?

Thanks,

Josh


#2

On Fri, May 4, 2012 at 3:05 PM, Joshua Blatt jblatt@verticloud.com wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the biggest
pains we have is getting Chef to work on a new platform. Once Chef works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh

The “omnibus” route is the best one, imho. Alternately, packaging a
ruby + chef install with fpm is the other one.


#3

Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, May 4, 2012 at 2:05 PM, Joshua Blatt jblatt@verticloud.com wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the biggest
pains we have is getting Chef to work on a new platform. Once Chef works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh


#4

+1 for Omnibus…

On Fri, May 4, 2012 at 3:45 PM, Matt Ray matt@opscode.com wrote:

Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, May 4, 2012 at 2:05 PM, Joshua Blatt jblatt@verticloud.com
wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the
biggest
pains we have is getting Chef to work on a new platform. Once Chef
works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh


Charles Sullivan
charlie.sullivan@gmail.com


#5

+1 Omnibus

We’re on CentOS/Fedora/Amazon/Windows

On May 4, 2012, at 1:47 PM, Charles Sullivan wrote:

+1 for Omnibus…

On Fri, May 4, 2012 at 3:45 PM, Matt Ray matt@opscode.com wrote:
Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, May 4, 2012 at 2:05 PM, Joshua Blatt jblatt@verticloud.com wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the biggest
pains we have is getting Chef to work on a new platform. Once Chef works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh


Charles Sullivan
charlie.sullivan@gmail.com


#6

Tried omnibus on CentOS 6.0. It just worked which was nice, but Ruby
is limited to the 1.8.7 which means our Chef recipes cannot make use of
any 1.9.x features if we want them to be portable.

On 05/04/2012 01:52 PM, John Martinez wrote:

+1 Omnibus

We’re on CentOS/Fedora/Amazon/Windows

On May 4, 2012, at 1:47 PM, Charles Sullivan wrote:

+1 for Omnibus…

On Fri, May 4, 2012 at 3:45 PM, Matt Ray <matt@opscode.com
mailto:matt@opscode.com> wrote:

Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point
you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com <mailto:matt@opscode.com> | (512) 731-2218
<tel:%28512%29%20731-2218>
Twitter, IRC, GitHub: mattray


On Fri, May 4, 2012 at 2:05 PM, Joshua Blatt
<jblatt@verticloud.com <mailto:jblatt@verticloud.com>> wrote:
> Hi guys,
>
> I'm relatively new to Chef, but I've already noticed that one
of the biggest
> pains we have is getting Chef to work on a new platform.   Once
Chef works
> we leave the world of crappy shell scripts and enter the world
of Chef.
>
> Has anyone come up with any nice scripts to get Chef and its
dependencies
> installed and happy on a variety of platforms/images?
>
> Thanks,
>
> Josh


Charles Sullivan
charlie.sullivan@gmail.com mailto:charlie.sullivan@gmail.com


#7

Which, if you are just writing chef recipes, they will be.

Adam

On Fri, May 4, 2012 at 2:19 PM, Joshua Blatt jblatt@verticloud.com wrote:

Tried omnibus on CentOS 6.0. It just worked which was nice, but Ruby is
limited to the 1.8.7 which means our Chef recipes cannot make use of any
1.9.x features if we want them to be portable.

On 05/04/2012 01:52 PM, John Martinez wrote:

+1 Omnibus

We’re on CentOS/Fedora/Amazon/Windows

On May 4, 2012, at 1:47 PM, Charles Sullivan wrote:

+1 for Omnibus…

On Fri, May 4, 2012 at 3:45 PM, Matt Ray matt@opscode.com wrote:

Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, May 4, 2012 at 2:05 PM, Joshua Blatt jblatt@verticloud.com
wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the
biggest
pains we have is getting Chef to work on a new platform. Once Chef
works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its
dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh


Charles Sullivan
charlie.sullivan@gmail.com


Opscode, Inc.
Adam Jacob, Chief Customer Officer
T: (206) 619-7151 E: adam@opscode.com


#8

Unless you use 1.9 features in which case they won’t be.

On 05/04/2012 02:27 PM, Adam Jacob wrote:

Which, if you are just writing chef recipes, they will be.

Adam

On Fri, May 4, 2012 at 2:19 PM, Joshua Blattjblatt@verticloud.com wrote:

Tried omnibus on CentOS 6.0. It just worked which was nice, but Ruby is
limited to the 1.8.7 which means our Chef recipes cannot make use of any
1.9.x features if we want them to be portable.

On 05/04/2012 01:52 PM, John Martinez wrote:

+1 Omnibus

We’re on CentOS/Fedora/Amazon/Windows

On May 4, 2012, at 1:47 PM, Charles Sullivan wrote:

+1 for Omnibus…

On Fri, May 4, 2012 at 3:45 PM, Matt Raymatt@opscode.com wrote:

Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, May 4, 2012 at 2:05 PM, Joshua Blattjblatt@verticloud.com
wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the
biggest
pains we have is getting Chef to work on a new platform. Once Chef
works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its
dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh


Charles Sullivan
charlie.sullivan@gmail.com


#9

The chef full stack packages Built by omnibus have ruby 1.9.2-p290 included.

/opt/opscode/embedded/bin/ruby -v

To verify.

This is an all inclusive package for chef, so if you want ruby 1.9 for your application stack you will need to build an rpm and host that and then use chef with a recipe to install it for your app.

On May 4, 2012, at 15:32, Joshua Blatt jblatt@verticloud.com wrote:

Unless you use 1.9 features in which case they won’t be.

On 05/04/2012 02:27 PM, Adam Jacob wrote:

Which, if you are just writing chef recipes, they will be.

Adam

On Fri, May 4, 2012 at 2:19 PM, Joshua Blattjblatt@verticloud.com wrote:

Tried omnibus on CentOS 6.0. It just worked which was nice, but Ruby is
limited to the 1.8.7 which means our Chef recipes cannot make use of any
1.9.x features if we want them to be portable.

On 05/04/2012 01:52 PM, John Martinez wrote:

+1 Omnibus

We’re on CentOS/Fedora/Amazon/Windows

On May 4, 2012, at 1:47 PM, Charles Sullivan wrote:

+1 for Omnibus…

On Fri, May 4, 2012 at 3:45 PM, Matt Raymatt@opscode.com wrote:

Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, May 4, 2012 at 2:05 PM, Joshua Blattjblatt@verticloud.com
wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the
biggest
pains we have is getting Chef to work on a new platform. Once Chef
works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its
dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh


Charles Sullivan
charlie.sullivan@gmail.com


#10

Ah! Very cool.

Thanks,

Josh

On 05/04/2012 02:40 PM, Joshua Timberman wrote:

The chef full stack packages Built by omnibus have ruby 1.9.2-p290 included.

/opt/opscode/embedded/bin/ruby -v

To verify.

This is an all inclusive package for chef, so if you want ruby 1.9 for your application stack you will need to build an rpm and host that and then use chef with a recipe to install it for your app.

On May 4, 2012, at 15:32, Joshua Blattjblatt@verticloud.com wrote:

Unless you use 1.9 features in which case they won’t be.

On 05/04/2012 02:27 PM, Adam Jacob wrote:

Which, if you are just writing chef recipes, they will be.

Adam

On Fri, May 4, 2012 at 2:19 PM, Joshua Blattjblatt@verticloud.com wrote:

Tried omnibus on CentOS 6.0. It just worked which was nice, but Ruby is
limited to the 1.8.7 which means our Chef recipes cannot make use of any
1.9.x features if we want them to be portable.

On 05/04/2012 01:52 PM, John Martinez wrote:

+1 Omnibus

We’re on CentOS/Fedora/Amazon/Windows

On May 4, 2012, at 1:47 PM, Charles Sullivan wrote:

+1 for Omnibus…

On Fri, May 4, 2012 at 3:45 PM, Matt Raymatt@opscode.com wrote:

Which platforms do you need? There is already a wide range of
supported platforms, let us know what you need and we can point you in
the right direction.

Thanks,
Matt Ray
Senior Technical Evangelist | Opscode Inc.
matt@opscode.com | (512) 731-2218
Twitter, IRC, GitHub: mattray

On Fri, May 4, 2012 at 2:05 PM, Joshua Blattjblatt@verticloud.com
wrote:

Hi guys,

I’m relatively new to Chef, but I’ve already noticed that one of the
biggest
pains we have is getting Chef to work on a new platform. Once Chef
works
we leave the world of crappy shell scripts and enter the world of Chef.

Has anyone come up with any nice scripts to get Chef and its
dependencies
installed and happy on a variety of platforms/images?

Thanks,

Josh


Charles Sullivan
charlie.sullivan@gmail.com


#11

Another +1 for the omnibus chef-full install.

In fact I use the chef-full knife bootstrap template [1] which can be
dropped in ~/.chef/bootstrap/ and used by knife to bootstrap a server with
the omnibus chef-client install. The benefit of this method is that it not
only installs chef but it also configures it according to your knife.rb
settings. So the server you are bootstrapping will know what chef-server
to connect to as well as what validation key to use and also install any
encrypted data bag key you may be using.

[1]
https://github.com/opscode/chef/blob/master/chef/lib/chef/knife/bootstrap/chef-full.erb


#12

On Fri, May 4, 2012 at 7:08 PM, Jeremiah Snapp jeremiah.snapp@gmail.com wrote:

In fact I use the chef-full knife bootstrap template [1] which can be
dropped in ~/.chef/bootstrap/ and used by knife to bootstrap a server with
the omnibus chef-client install. The benefit of this method is that it not
only installs chef but it also configures it according to your knife.rb
settings. So the server you are bootstrapping will know what chef-server to
connect to as well as what validation key to use and also install any
encrypted data bag key you may be using.

[1] https://github.com/opscode/chef/blob/master/chef/lib/chef/knife/bootstrap/chef-full.erb

The chef-full template will be the default template for knife
bootstrap in Chef 0.10.10+.

Bryan