I’m just getting started with chef and I’m somewhat frustrated by how long it
takes to debug recipes. Chef-Solo takes 4 seconds to fire up and run a simple
recipe on a mac and 20 seconds on windows. We’re porting a bunch of automation
from powershell and batch scripts to chef, and I’m used to making a change and
running it instantly.
I figure I am just a newbie and don’t know the tricks behind doing chef
development. What tricks are people using to do this?
Shef, shef,shef did I mention shef?
On Mar 28, 2012 5:30 PM, pmccallick@paraport.com wrote:
I'm just getting started with chef and I'm somewhat frustrated by how long
it
takes to debug recipes. Chef-Solo takes 4 seconds to fire up and run a
simple
recipe on a mac and 20 seconds on windows. We're porting a bunch of
automation
from powershell and batch scripts to chef, and I'm used to making a change
and
running it instantly.I figure I am just a newbie and don't know the tricks behind doing chef
development. What tricks are people using to do this?
I have not had any luck getting shef to reload a recipe from disk. How is done?
Also, shef does not run on windowz.
From: Bryan Berry [mailto:bryan.berry@gmail.com]
Sent: Wednesday, March 28, 2012 8:36 AM
To: chef@lists.opscode.com
Subject: [chef] Re: Speeding up development
Shef, shef,shef did I mention shef?
On Mar 28, 2012 5:30 PM, <pmccallick@paraport.commailto:pmccallick@paraport.com> wrote:
I’m just getting started with chef and I’m somewhat frustrated by how long it
takes to debug recipes. Chef-Solo takes 4 seconds to fire up and run a simple
recipe on a mac and 20 seconds on windows. We’re porting a bunch of automation
from powershell and batch scripts to chef, and I’m used to making a change and
running it instantly.
I figure I am just a newbie and don’t know the tricks behind doing chef
development. What tricks are people using to do this?
Ohai runs at the beginning of every client run and, on windows, add
significant time to run time. I've been considering commenting out the
drivers section of the wondows ohai plugin, just to see if it breaks
anything. It pulls a boatload of data that I see no use for at the moment
(for my current project anyway).
On Wed, Mar 28, 2012 at 11:10 AM, Paul McCallick PMcCallick@paraport.comwrote:
I have not had any luck getting shef to reload a recipe from disk. How is
done?****
Also, shef does not run on windowz. ****
From: Bryan Berry [mailto:bryan.berry@gmail.com]
Sent: Wednesday, March 28, 2012 8:36 AM
To: chef@lists.opscode.com
Subject: [chef] Re: Speeding up development****
Shef, shef,shef did I mention shef?****
On Mar 28, 2012 5:30 PM, pmccallick@paraport.com wrote:****
I'm just getting started with chef and I'm somewhat frustrated by how long
it
takes to debug recipes. Chef-Solo takes 4 seconds to fire up and run a
simple
recipe on a mac and 20 seconds on windows. We're porting a bunch of
automation
from powershell and batch scripts to chef, and I'm used to making a change
and
running it instantly.I figure I am just a newbie and don't know the tricks behind doing chef
development. What tricks are people using to do this?****
On Mar 28, 2012, at 12:13 PM, Sascha Bates wrote:
Ohai runs at the beginning of every client run and, on windows, add significant time to run time. I've been considering commenting out the drivers section of the wondows ohai plugin, just to see if it breaks anything. It pulls a boatload of data that I see no use for at the moment (for my current project anyway).
Like what? (Curious if there is a pattern.)
-Jesse
Like what? (Curious if there is a pattern.)
In one case an IRC denizen (whose name escapes me) and I, tracked it
down some pretty significant slowness to here:
https://github.com/opscode/ohai/blob/master/lib/ohai/plugins/windows/kernel.rb#L63
That's what I'm talking bout. It maps out what looks like everything
ever found by device manager and I don't think I need that info and I
don't think any of the cookbooks I'm using need it.
On 3/28/12 3:30 PM, Steven Danna wrote:
Like what? (Curious if there is a pattern.)
In one case an IRC denizen (whose name escapes me) and I, tracked it
down some pretty significant slowness to here:https://github.com/opscode/ohai/blob/master/lib/ohai/plugins/windows/kernel.rb#L63
We should move that in to another portion of ohai, so we can easily
exclude it, rather then tucking it away inside of kernel.rb. Want to
whip up a patch, Sascha?
Adam
On Wed, Mar 28, 2012 at 3:14 PM, Sascha Bates sascha.bates@gmail.com wrote:
That's what I'm talking bout. It maps out what looks like everything ever
found by device manager and I don't think I need that info and I don't think
any of the cookbooks I'm using need it.On 3/28/12 3:30 PM, Steven Danna wrote:
Like what? (Curious if there is a pattern.)
In one case an IRC denizen (whose name escapes me) and I, tracked it
down some pretty significant slowness to here:https://github.com/opscode/ohai/blob/master/lib/ohai/plugins/windows/kernel.rb#L63
--
Opscode, Inc.
Adam Jacob, Chief Customer Officer
T: (206) 619-7151 E: adam@opscode.com
Yes, love to. (stand by while I fill out my contributor forms)
On 3/29/12 12:22 PM, Adam Jacob wrote:
We should move that in to another portion of ohai, so we can easily
exclude it, rather then tucking it away inside of kernel.rb. Want to
whip up a patch, Sascha?Adam
On Wed, Mar 28, 2012 at 3:14 PM, Sascha Batessascha.bates@gmail.com wrote:
That's what I'm talking bout. It maps out what looks like everything ever
found by device manager and I don't think I need that info and I don't think
any of the cookbooks I'm using need it.On 3/28/12 3:30 PM, Steven Danna wrote:
Like what? (Curious if there is a pattern.)
In one case an IRC denizen (whose name escapes me) and I, tracked it
down some pretty significant slowness to here:https://github.com/opscode/ohai/blob/master/lib/ohai/plugins/windows/kernel.rb#L63