Omnibus installer doesn't create /etc/chef?


#1

Ohai chefs,

When I use the omnibus chef-client installer on Ubuntu 12.04 it doesn’t
create the /etc/chef directory. Is that normal? It seems like it should
create it for you.


#2

I also just installed chef via ruby gems and it didn’t create /etc/chef
either. Can that directory be added to the chef-client install procedures
as a default?

Thanks,
Jeremiah

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp jeremiah.snapp@gmail.comwrote:

Ohai chefs,

When I use the omnibus chef-client installer on Ubuntu 12.04 it doesn’t
create the /etc/chef directory. Is that normal? It seems like it should
create it for you.


#3

There are many ways the /etc/chef directory gets created and it’s
always when chef is being configured.

‘knife bootstrap’ will create the appropriate directories over ssh or winrm.

The debian packaging configures the client using debconf and will
create the appropriate directories.

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

When I use the omnibus chef-client installer on Ubuntu 12.04 it doesn’t
create the /etc/chef directory. Is that normal? It seems like it should
create it for you.

Omnibus creates /etc/chef when you configure Chef using

/opt/chef/setup.sh -v validation_key -o hosted_chef organization
/opt/chef/setup.sh -v validation_key -u http://chef_server.example.org

On Tue, Jun 26, 2012 at 7:51 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

I also just installed chef via ruby gems and it didn’t create /etc/chef
either. Can that directory be added to the chef-client install procedures
as a default?

As a packaging system, Rubygems isn’t really designed for complete
application configuration. Since we aren’t going to do the
configuration, it is presumptuous to create a directory that may not
be used. This action may also make it harder to do the correct thing
in other packaging systems that base off of the Rubygem.

Bryan


#4

Thanks for the excellent explanation. That makes total sense.

Jeremiah

On Tue, Jun 26, 2012 at 10:18 AM, Bryan McLellan btm@loftninjas.org wrote:

There are many ways the /etc/chef directory gets created and it’s
always when chef is being configured.

‘knife bootstrap’ will create the appropriate directories over ssh or
winrm.

The debian packaging configures the client using debconf and will
create the appropriate directories.

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

When I use the omnibus chef-client installer on Ubuntu 12.04 it doesn’t
create the /etc/chef directory. Is that normal? It seems like it should
create it for you.

Omnibus creates /etc/chef when you configure Chef using

/opt/chef/setup.sh -v validation_key -o hosted_chef organization
/opt/chef/setup.sh -v validation_key -u http://chef_server.example.org

On Tue, Jun 26, 2012 at 7:51 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

I also just installed chef via ruby gems and it didn’t create /etc/chef
either. Can that directory be added to the chef-client install
procedures
as a default?

As a packaging system, Rubygems isn’t really designed for complete
application configuration. Since we aren’t going to do the
configuration, it is presumptuous to create a directory that may not
be used. This action may also make it harder to do the correct thing
in other packaging systems that base off of the Rubygem.

Bryan


#5

Jeremiah, here is my bootstrap template in a gist for RHEL 6.2 using
omnibus 6.2

On Wed, Jun 27, 2012 at 1:17 PM, Jeremiah Snapp jeremiah.snapp@gmail.comwrote:

Thanks for the excellent explanation. That makes total sense.

Jeremiah

On Tue, Jun 26, 2012 at 10:18 AM, Bryan McLellan btm@loftninjas.orgwrote:

There are many ways the /etc/chef directory gets created and it’s
always when chef is being configured.

‘knife bootstrap’ will create the appropriate directories over ssh or
winrm.

The debian packaging configures the client using debconf and will
create the appropriate directories.

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

When I use the omnibus chef-client installer on Ubuntu 12.04 it doesn’t
create the /etc/chef directory. Is that normal? It seems like it
should
create it for you.

Omnibus creates /etc/chef when you configure Chef using

/opt/chef/setup.sh -v validation_key -o hosted_chef organization
/opt/chef/setup.sh -v validation_key -u http://chef_server.example.org

On Tue, Jun 26, 2012 at 7:51 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

I also just installed chef via ruby gems and it didn’t create /etc/chef
either. Can that directory be added to the chef-client install
procedures
as a default?

As a packaging system, Rubygems isn’t really designed for complete
application configuration. Since we aren’t going to do the
configuration, it is presumptuous to create a directory that may not
be used. This action may also make it harder to do the correct thing
in other packaging systems that base off of the Rubygem.

Bryan


#6

Thanks Bryan. I’m curious, is there anything wrong with the default
template for RHEL 6.2? Or are you just creating your own template to
accomplish your customizations?

On Wed, Jun 27, 2012 at 7:22 AM, Bryan Berry bryan.berry@gmail.com wrote:

Jeremiah, here is my bootstrap template in a gist for RHEL 6.2 using
omnibus 6.2

https://gist.github.com/2948410

On Wed, Jun 27, 2012 at 1:17 PM, Jeremiah Snapp jeremiah.snapp@gmail.comwrote:

Thanks for the excellent explanation. That makes total sense.

Jeremiah

On Tue, Jun 26, 2012 at 10:18 AM, Bryan McLellan btm@loftninjas.orgwrote:

There are many ways the /etc/chef directory gets created and it’s
always when chef is being configured.

‘knife bootstrap’ will create the appropriate directories over ssh or
winrm.

The debian packaging configures the client using debconf and will
create the appropriate directories.

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

When I use the omnibus chef-client installer on Ubuntu 12.04 it doesn’t
create the /etc/chef directory. Is that normal? It seems like it
should
create it for you.

Omnibus creates /etc/chef when you configure Chef using

/opt/chef/setup.sh -v validation_key -o hosted_chef organization
/opt/chef/setup.sh -v validation_key -u http://chef_server.example.org

On Tue, Jun 26, 2012 at 7:51 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

I also just installed chef via ruby gems and it didn’t create /etc/chef
either. Can that directory be added to the chef-client install
procedures
as a default?

As a packaging system, Rubygems isn’t really designed for complete
application configuration. Since we aren’t going to do the
configuration, it is presumptuous to create a directory that may not
be used. This action may also make it harder to do the correct thing
in other packaging systems that base off of the Rubygem.

Bryan


#7

afaik the default template doesn’t use omnibus, however I haven’t looked at
it in a long time

I need to delete that damn fprintd cuz it sends lots of annoying e-mails
about not being able to connect to a fingerprint reader.

On Wed, Jun 27, 2012 at 1:49 PM, Jeremiah Snapp jeremiah.snapp@gmail.comwrote:

Thanks Bryan. I’m curious, is there anything wrong with the default
template for RHEL 6.2? Or are you just creating your own template to
accomplish your customizations?

On Wed, Jun 27, 2012 at 7:22 AM, Bryan Berry bryan.berry@gmail.comwrote:

Jeremiah, here is my bootstrap template in a gist for RHEL 6.2 using
omnibus 6.2

https://gist.github.com/2948410

On Wed, Jun 27, 2012 at 1:17 PM, Jeremiah Snapp <jeremiah.snapp@gmail.com

wrote:

Thanks for the excellent explanation. That makes total sense.

Jeremiah

On Tue, Jun 26, 2012 at 10:18 AM, Bryan McLellan btm@loftninjas.orgwrote:

There are many ways the /etc/chef directory gets created and it’s
always when chef is being configured.

‘knife bootstrap’ will create the appropriate directories over ssh or
winrm.

The debian packaging configures the client using debconf and will
create the appropriate directories.

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

When I use the omnibus chef-client installer on Ubuntu 12.04 it
doesn’t
create the /etc/chef directory. Is that normal? It seems like it
should
create it for you.

Omnibus creates /etc/chef when you configure Chef using

/opt/chef/setup.sh -v validation_key -o hosted_chef organization
/opt/chef/setup.sh -v validation_key -u http://chef_server.example.org

On Tue, Jun 26, 2012 at 7:51 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

I also just installed chef via ruby gems and it didn’t create
/etc/chef
either. Can that directory be added to the chef-client install
procedures
as a default?

As a packaging system, Rubygems isn’t really designed for complete
application configuration. Since we aren’t going to do the
configuration, it is presumptuous to create a directory that may not
be used. This action may also make it harder to do the correct thing
in other packaging systems that base off of the Rubygem.

Bryan


#8

Yeah Chef 0.10.10 began using chef-full (aka Omnibus) as the default
template for knife bootstrap. But it wouldn’t have your funny comment
about the “bloody fingerprint scanner”. Why are you scanning bloody
fingerprints. :wink:

On Wed, Jun 27, 2012 at 8:08 AM, Bryan Berry bryan.berry@gmail.com wrote:

afaik the default template doesn’t use omnibus, however I haven’t looked
at it in a long time

I need to delete that damn fprintd cuz it sends lots of annoying e-mails
about not being able to connect to a fingerprint reader.

On Wed, Jun 27, 2012 at 1:49 PM, Jeremiah Snapp jeremiah.snapp@gmail.comwrote:

Thanks Bryan. I’m curious, is there anything wrong with the default
template for RHEL 6.2? Or are you just creating your own template to
accomplish your customizations?

On Wed, Jun 27, 2012 at 7:22 AM, Bryan Berry bryan.berry@gmail.comwrote:

Jeremiah, here is my bootstrap template in a gist for RHEL 6.2 using
omnibus 6.2

https://gist.github.com/2948410

On Wed, Jun 27, 2012 at 1:17 PM, Jeremiah Snapp <
jeremiah.snapp@gmail.com> wrote:

Thanks for the excellent explanation. That makes total sense.

Jeremiah

On Tue, Jun 26, 2012 at 10:18 AM, Bryan McLellan btm@loftninjas.orgwrote:

There are many ways the /etc/chef directory gets created and it’s
always when chef is being configured.

‘knife bootstrap’ will create the appropriate directories over ssh or
winrm.

The debian packaging configures the client using debconf and will
create the appropriate directories.

On Tue, Jun 26, 2012 at 7:43 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

When I use the omnibus chef-client installer on Ubuntu 12.04 it
doesn’t
create the /etc/chef directory. Is that normal? It seems like it
should
create it for you.

Omnibus creates /etc/chef when you configure Chef using

/opt/chef/setup.sh -v validation_key -o hosted_chef organization
/opt/chef/setup.sh -v validation_key -u http://chef_server.example.org

On Tue, Jun 26, 2012 at 7:51 AM, Jeremiah Snapp
jeremiah.snapp@gmail.com wrote:

I also just installed chef via ruby gems and it didn’t create
/etc/chef
either. Can that directory be added to the chef-client install
procedures
as a default?

As a packaging system, Rubygems isn’t really designed for complete
application configuration. Since we aren’t going to do the
configuration, it is presumptuous to create a directory that may not
be used. This action may also make it harder to do the correct thing
in other packaging systems that base off of the Rubygem.

Bryan