Do I still have to use the chef-repo?


#1

Hi!

This is probably a very lame question, but with all the confusion with
workflows, I don’t know what to do. Do I still have to use the chef-repo, even
if I have a git repository for every cookbook?

Thanks

David Gil
Agència Estatal de Meteorologia a Catalunya


#2

In my opinion, it’s still a good idea to keep a chef-repo for your other Chef components, such as data_bags, environments, roles, etc.

The stackforge/openstack project has a nice example of a chef-repo (https://github.com/stackforge/openstack-chef-repo) and separate cookbook repositories.

Curtis Stewart
Consultant
m 217.390.5067
Skype cstewart8710
cstewart@momentumsi.commailto:cstewart@momentumsi.com
www.momentumsi.comhttp://www.momentumsi.com/

[cid:71466434-A311-4F82-BC03-F7D6BA0FA526]http://www.momentumsi.com/http://www.momentumsi.com/

Cloud Migration - Architecture - DevOps - Big Data - App Dev

On May 16, 2014, at 5:16 AM, dgilo@aemet.esmailto:dgilo@aemet.es wrote:

Hi!

This is probably a very lame question, but with all the confusion with
workflows, I don’t know what to do. Do I still have to use the chef-repo, even
if I have a git repository for every cookbook?

Thanks

David Gil
Agència Estatal de Meteorologia a Catalunya


#3

It’s not a lame question. You will still need the chef repo to create and
store environments, data bags etcŠ I use it to use it to check in my
environment json files.

David Williams

On 5/16/14 5:16 AM, "dgilo@aemet.es" dgilo@aemet.es wrote:

Hi!

This is probably a very lame question, but with all the confusion with
workflows, I don’t know what to do. Do I still have to use the chef-repo,
even
if I have a git repository for every cookbook?

Thanks

David Gil
Agència Estatal de Meteorologia a Catalunya

CONFIDENTIALITY NOTICE: This electronic mail may contain information that is privileged, confidential, and/or otherwise protected from disclosure to anyone other than its intended recipient(s). Any dissemination or use of this electronic mail or its contents by persons other than the intended recipient(s) is strictly prohibited. If you have received this communication in error, please notify the sender immediately by reply e-mail so that we may correct our internal records. Please then delete the original message. Thank you.


#4

You don’t really need one. These objects can be created directly on the
Chef server. What you miss is the ability to have them in source control.

Depending on your use case, that might make sense. I have done things this
way in the past and would do it again if it made sense.

On Friday, 16 May 2014, David A. Williams dwilliams@daxko.com wrote:

It’s not a lame question. You will still need the chef repo to create and
store environments, data bags etcŠ I use it to use it to check in my
environment json files.

David Williams

On 5/16/14 5:16 AM, "dgilo@aemet.es <javascript:;>" <dgilo@aemet.es<javascript:;>>
wrote:

Hi!

This is probably a very lame question, but with all the confusion with
workflows, I don’t know what to do. Do I still have to use the chef-repo,
even
if I have a git repository for every cookbook?

Thanks

David Gil
Agència Estatal de Meteorologia a Catalunya

CONFIDENTIALITY NOTICE: This electronic mail may contain information that
is privileged, confidential, and/or otherwise protected from disclosure to
anyone other than its intended recipient(s). Any dissemination or use of
this electronic mail or its contents by persons other than the intended
recipient(s) is strictly prohibited. If you have received this
communication in error, please notify the sender immediately by reply
e-mail so that we may correct our internal records. Please then delete the
original message. Thank you.