- From: Joseph Bowman <
>
- To:
- Subject: [chef] Re: Re: Re: An deep topic
- Date: Fri, 11 Jul 2014 10:10:51 -0400
No, chef saved me a ton of time fixing heartbleed where I used chef,
sorry I wasn't clear. My pain was in the stacks that were not managed
by chef.
On 7/11/14, Mikael Henriksson
<
>
wrote:
>
My experiences are the opposite of Joseph's! It took me around 20 minutes to
>
fix the heart bleed bug and when people in the company started posting about
>
it in the chat rooms I could say it's been fixed for a week already and this
>
is thanks to the amazing tooling that chef brings to the table (berkshelf
>
and friends).
>
>
On Fri, Jul 11, 2014 at 3:56 PM, Brian Akins
>
<
>
>
wrote:
>
>
> Coming late to this thread, but I am one of the folks who had an offline
>
> discussion/rant with lusis.
>
> When Heartbleed (#1) happened, I needed to rebuild a ton of omnibus
>
> things
>
> and omnibus was just horribly broken. It had worked fine just a few days
>
> before then it just didn't. In a fury of vendoring things and doing
>
> horrible hacks to get through the ordeal, I vented privately to a few
>
> folks
>
> who were having to do the same and also had a few public "wtf?!"
>
> comments.
>
> In this instance, it was just incredible bad timing and had the "breaking
>
> features" happened a week later, it probably would not have been a big
>
> deal. It was a stressful 48-72 hours to put it mildly, and the rants
>
> were
>
> just me blowing off some steam. Then a few weeks later, omnibus broke
>
> again, then again, etc. I do appreciated the statement ChefCo made
>
> concerning omnibus and what would and would not be "supported" - it was
>
> just a little late for me. Similar things have happened with other parts
>
> of the toolchain.
>
> I am (or was) just an end user of the tool chain. I'll admit I was
>
> enamored
>
> with "oh, shiny new workflow/tools" for a while, but then I needed to get
>
> stuff done. Chef is an awesome tool, but at the end of that day that's
>
> all
>
> it is to me. It's great that an "ecosystem" is developing around it, but
>
> ultimately I just need to get stuff done. From the outside looking in,
>
> it
>
> does seem that the Chef community forgets this sometimes and becomes
>
> enamored with the tools themselves. I include myself in that. Same could
>
> be said about a bunch of open source communities as well.
>
> I've taken a different career path -- for a while at least -- so, I don't
>
> necessarily have to think about such things every day. A lot of the
>
> "venom" in my original rants was because of 48-72 hours of dealing with
>
> Heartbleed. Heck, I ranted about pretty much every piece of tooling I had
>
> to deal with that day and everyone just assumed all the complaints were
>
> about them ;) However, there was some truth to the rant - "why can't
>
> this
>
> crap just work???"
>
> Hugs to every one. I feel like this should be a discussion at a bar or
>
> something.
>
> As a former co-worker stated: "there are two types of software: software
>
> that @bakins hates and software that @bakins will hate"
>
> --Brian
- [chef] Re: Re: An deep topic, (continued)
Archive powered by MHonArc 2.6.16.