Using omnibus


#1

Hi Folks!

I am trying to use Omnibus (https://github.com/opscode/omnibus) to install
chef server… Out of the box, it built me
a chef-server-full-0.10.0-1-ubuntu-10.04-x86_64.tar.gz by following the
steps on github and /opt/opscode/{embedded,bin} directories…

What are the next steps? Does anyone have good template for getting the
server up and running? Perhaps using chef-server recipe + chef-solo +
config file + chef-server recipe?
(or do I have to produce init.d scripts manually after this?)

-Steve


#2

On Tue, Dec 6, 2011 at 3:10 AM, Steve Jang estebanjang@gmail.com wrote:

I am trying to use Omnibus (https://github.com/opscode/omnibus) to install
chef server… Out of the box, it built me
a chef-server-full-0.10.0-1-ubuntu-10.04-x86_64.tar.gz by following the
steps on github and /opt/opscode/{embedded,bin} directories…

Omnibus is a build system for creating Chef builds that are easy to
install. It wasn’t meant for each individual to install Omnibus to
create a build and then install it.

What are the next steps? Does anyone have good template for getting the
server up and running? Perhaps using chef-server recipe + chef-solo + config
file + chef-server recipe?
(or do I have to produce init.d scripts manually after this?)

Omnibus Server, that is the Omnibus install that includes the Chef
Server, doesn’t work for 0.10 and is incomplete. Notably it is missing
the additional dependencies of 0.10 and wasn’t completed. We put some
work into it, which you could see in the 0.10 branch, but ran into
difficulties debugging it due to Clojure’s lack of error messages and
functional stack traces. We’re going to rewrite the Omnibus build
system in Ruby in the future, but we’re in the design phase right now.

Omnibus Client is in a beta release and we’re actively working on
testing and expanding its coverage toward a full release soon. You can
find our original post about the beta release here:
http://lists.opscode.com/sympa/arc/chef-dev/2011-08/msg00055.html

You should install follow the documentation on the wiki for installing
the Chef Server. You can start here:
http://wiki.opscode.com/display/chef/Installing+Chef+Server

Installing using Rubygems is the most common install path, which you
can find directions for here:
http://wiki.opscode.com/display/chef/Installing+Chef+Server+using+Chef+Solo

Bryan


#3

Ah. Got it. Thanks for the detailed response.
I had written a little wrapper script for installing chef server myself,
but was looking to replace it with omnibus.

-Steve

On Tue, Dec 6, 2011 at 5:16 AM, Bryan McLellan btm@loftninjas.org wrote:

On Tue, Dec 6, 2011 at 3:10 AM, Steve Jang estebanjang@gmail.com wrote:

I am trying to use Omnibus (https://github.com/opscode/omnibus) to
install
chef server… Out of the box, it built me
a chef-server-full-0.10.0-1-ubuntu-10.04-x86_64.tar.gz by following the
steps on github and /opt/opscode/{embedded,bin} directories…

Omnibus is a build system for creating Chef builds that are easy to
install. It wasn’t meant for each individual to install Omnibus to
create a build and then install it.

What are the next steps? Does anyone have good template for getting the
server up and running? Perhaps using chef-server recipe + chef-solo +
config
file + chef-server recipe?
(or do I have to produce init.d scripts manually after this?)

Omnibus Server, that is the Omnibus install that includes the Chef
Server, doesn’t work for 0.10 and is incomplete. Notably it is missing
the additional dependencies of 0.10 and wasn’t completed. We put some
work into it, which you could see in the 0.10 branch, but ran into
difficulties debugging it due to Clojure’s lack of error messages and
functional stack traces. We’re going to rewrite the Omnibus build
system in Ruby in the future, but we’re in the design phase right now.

Omnibus Client is in a beta release and we’re actively working on
testing and expanding its coverage toward a full release soon. You can
find our original post about the beta release here:
http://lists.opscode.com/sympa/arc/chef-dev/2011-08/msg00055.html

You should install follow the documentation on the wiki for installing
the Chef Server. You can start here:
http://wiki.opscode.com/display/chef/Installing+Chef+Server

Installing using Rubygems is the most common install path, which you
can find directions for here:
http://wiki.opscode.com/display/chef/Installing+Chef+Server+using+Chef+Solo

Bryan


#4

On Dec 6, 2011, at 11:21 AM, Steve Jang wrote:

Ah. Got it. Thanks for the detailed response.
I had written a little wrapper script for installing chef server myself, but was looking to replace it with omnibus.

I would think that you should be able to do an install using the “full-stack chef-client installer” from the omnibus build system, and then from there proceed on to getting the rest of the chef-server stuff built. At least, that would save you a certain amount of work.


Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1


#5

On Tue, Dec 6, 2011 at 12:34 PM, Brad Knowles bknowles@ihiji.com wrote:

I would think that you should be able to do an install using the “full-stack chef-client installer” from the omnibus build system, and then from there proceed on to getting the rest of the chef-server stuff built. At least, that would save you a certain amount of work.

I would recommend against that.

For starters, it is hard for anyone to support or help you if you have
problems, because you’re doing it in a unique way. If you follow the
documented directions and run into an issue because of something
special about your setup, it is more likely that someone else would
have made the same mistake and you’ll be able to find their notes or
thoughts online.

Further though, Omnibus Client installs to an isolated part of the
system. For instance, it comes with its own known-working version of
ruby that won’t interfere with another version of ruby installed on
the system. Installing the Omnibus client and the chef server some
other way will mean that you’ve got the server and client working on
different ruby stacks, and you’ll have multiple installs of rubygems,
including multiple versions of the chef gems installed.

Using the Chef-solo install is pretty easy if you’ve got ruby because
it uses Chef-solo to set up the server for you, with init scripts. If
you have any experience with rubygems, it’s the easiest path.

http://wiki.opscode.com/display/chef/Installing+Chef+Server+using+Chef+Solo

Bryan


#6

On Dec 6, 2011, at 11:40 AM, Bryan McLellan wrote:

Using the Chef-solo install is pretty easy if you’ve got ruby because
it uses Chef-solo to set up the server for you, with init scripts. If
you have any experience with rubygems, it’s the easiest path.

Tim Toady is not always your friend? :wink:


Brad Knowles bknowles@ihiji.com
SAGE Level IV, Chef Level 0.0.1


#7

On Tue, Dec 6, 2011 at 12:43 PM, Brad Knowles bknowles@ihiji.com wrote:

Tim Toady is not always your friend? :wink:

Well, there’s more than one way to do it by yourself in a vacuum in
space, where you are alone, sad, and crying. =D

But if you want to make friends and have fun, some compromise is needed.

Bryan


#8

On Tue, Dec 6, 2011 at 1:16 PM, Bryan McLellan btm@loftninjas.org wrote:

Omnibus Server, that is the Omnibus install that includes the Chef
Server, doesn’t work for 0.10 and is incomplete. Notably it is missing
the additional dependencies of 0.10 and wasn’t completed. We put some
work into it, which you could see in the 0.10 branch, but ran into
difficulties debugging it due to Clojure’s lack of error messages and
functional stack traces. We’re going to rewrite the Omnibus build
system in Ruby in the future, but we’re in the design phase right now.

I’d previously had 0.10.4 server up from omnibus using a bunch of
local changes, all on github, but I can’t sign the CLA :expressionless:

I tried 0.10.6 last night and installing it just now on first glance
it looks like its all there and running… any pointers as to what
might be missing?

We’ve really struggled with chef server as we’re stuck on an ancient
RedHat release (don’t ask…) and the omnibus client’s dealt with all
that pain, our plan was to try doing the server over christmas but I’m
wondering what we’re missing.


Alex Kiernan


#9

On 16 December 2011 23:26, Alex Kiernan alex.kiernan@gmail.com wrote:

On Tue, Dec 6, 2011 at 1:16 PM, Bryan McLellan btm@loftninjas.org wrote:

Omnibus Server, that is the Omnibus install that includes the Chef
Server, doesn’t work for 0.10 and is incomplete. Notably it is missing
the additional dependencies of 0.10 and wasn’t completed. We put some
work into it, which you could see in the 0.10 branch, but ran into
difficulties debugging it due to Clojure’s lack of error messages and
functional stack traces. We’re going to rewrite the Omnibus build
system in Ruby in the future, but we’re in the design phase right now.

I’d previously had 0.10.4 server up from omnibus using a bunch of
local changes, all on github, but I can’t sign the CLA :expressionless:

Why can’t you sign the CLA?

–AJ

I tried 0.10.6 last night and installing it just now on first glance
it looks like its all there and running… any pointers as to what
might be missing?

We’ve really struggled with chef server as we’re stuck on an ancient
RedHat release (don’t ask…) and the omnibus client’s dealt with all
that pain, our plan was to try doing the server over christmas but I’m
wondering what we’re missing.


Alex Kiernan


#10

On Fri, Dec 16, 2011 at 10:38 AM, AJ Christensen aj@junglist.gen.nz wrote:

On 16 December 2011 23:26, Alex Kiernan alex.kiernan@gmail.com wrote:

On Tue, Dec 6, 2011 at 1:16 PM, Bryan McLellan btm@loftninjas.org wrote:

Omnibus Server, that is the Omnibus install that includes the Chef
Server, doesn’t work for 0.10 and is incomplete. Notably it is missing
the additional dependencies of 0.10 and wasn’t completed. We put some
work into it, which you could see in the 0.10 branch, but ran into
difficulties debugging it due to Clojure’s lack of error messages and
functional stack traces. We’re going to rewrite the Omnibus build
system in Ruby in the future, but we’re in the design phase right now.

I’d previously had 0.10.4 server up from omnibus using a bunch of
local changes, all on github, but I can’t sign the CLA :expressionless:

Why can’t you sign the CLA?

Corporate lunacy.


Alex Kiernan