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
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 seizadi@infoblox.com 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-deploymentThanks,
-Soheil
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^2On Tue, Feb 3, 2015 at 3:11 PM, Soheil Eizadi <seizadi@infoblox.com (mailto:seizadi@infoblox.com)> 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-deploymentThanks,
-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
Couple of questions:
- Are there omnibus packages for ubuntu 14.04? (If yes can I have the path please)
- Does the omnibus packages pull in the complete environment? (One of the advantages of the chef-dk install is that it has the complete ruby environment and tooling bundled)
Thanks,
-Soheil
From: Daniel DeLeo [ddeleo@kallistec.com] on behalf of Daniel DeLeo [dan@kallistec.com]
Sent: Tuesday, February 03, 2015 3:07 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Re: Chef/Foreman Integration
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^2On Tue, Feb 3, 2015 at 3:11 PM, Soheil Eizadi <seizadi@infoblox.com (mailto:seizadi@infoblox.com)> 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-deploymentThanks,
-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
please check these links
https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/13.04/x86_64/chef_12.0.3-1_amd64.deb
omnibus will have ruby, gem, bundler + chef-(shell/solo/apply/client) ,
does that constitute your environment?
chefdk will add berks, chefspec, test-kitchen etc on top of it,
On Tue, Feb 3, 2015 at 4:22 PM, Soheil Eizadi seizadi@infoblox.com wrote:
Couple of questions:
- Are there omnibus packages for ubuntu 14.04? (If yes can I have the path
please)- Does the omnibus packages pull in the complete environment? (One of the
advantages of the chef-dk install is that it has the complete ruby
environment and tooling bundled)Thanks,
-Soheil
From: Daniel DeLeo [ddeleo@kallistec.com] on behalf of Daniel DeLeo [
dan@kallistec.com]
Sent: Tuesday, February 03, 2015 3:07 PM
To: chef@lists.opscode.com
Subject: [chef] Re: Re: Chef/Foreman IntegrationOn 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^2On Tue, Feb 3, 2015 at 3:11 PM, Soheil Eizadi <seizadi@infoblox.com
(mailto:seizadi@infoblox.com)> 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-deploymentThanks,
-SoheilFor 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 bootstrapor 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-clientruns for a second time.--
Daniel DeLeo
Saw the 13.04, was not obvious it would support 14.04, thanks for the detail on the various options.
For my use case, for production the omnibus is fine. For test environment I need the first node to run Chef-Zero w/ berks, so the chef install from JJ for that environment would work best.
-Soheil
From: Ranjib Dey [dey.ranjib@gmail.com]
Sent: Tuesday, February 03, 2015 4:27 PM
To: chef@lists.opscode.com
Subject: [chef] Re: RE: Re: Re: Chef/Foreman Integration
please check these links
https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/13.04/x86_64/chef_12.0.3-1_amd64.deb
omnibus will have ruby, gem, bundler + chef-(shell/solo/apply/client) , does that constitute your environment?
chefdk will add berks, chefspec, test-kitchen etc on top of it,
On Tue, Feb 3, 2015 at 4:22 PM, Soheil Eizadi <seizadi@infoblox.commailto:seizadi@infoblox.com> wrote:
Couple of questions:
- Are there omnibus packages for ubuntu 14.04? (If yes can I have the path please)
- Does the omnibus packages pull in the complete environment? (One of the advantages of the chef-dk install is that it has the complete ruby environment and tooling bundled)
Thanks,
-Soheil
From: Daniel DeLeo [ddeleo@kallistec.commailto:ddeleo@kallistec.com] on behalf of Daniel DeLeo [dan@kallistec.commailto:dan@kallistec.com]
Sent: Tuesday, February 03, 2015 3:07 PM
To: chef@lists.opscode.commailto:chef@lists.opscode.com
Subject: [chef] Re: Re: Chef/Foreman Integration
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.0722tel:512.619.0722 t: @jjasghar irc: j^2On Tue, Feb 3, 2015 at 3:11 PM, Soheil Eizadi <seizadi@infoblox.commailto:seizadi@infoblox.com (mailto:seizadi@infoblox.commailto:seizadi@infoblox.com)> 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-deploymentThanks,
-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