Thanks to Paul, Morgan, and Elijah for pointing out an inaccuracy:
On Apr 25, 2013, at 2:46 PM, Paul Graydon <[email protected]> wrote:
> On 04/25/2013 11:33 AM, Morgan Blackthorne wrote:
>>
>> "Chef works atop ssh, which – while the gold standard for cryptographically
>> secure systems management – is computationally expensive to the point where
>> most master servers fall over under the weight of 700-1500 clients."
>>
>> This is factually incorrect on two counts. The crypto negotiation for knife
>> ssh is not done on the Chef server but instead on the knife client. However,
>> regular Chef client->server communication is done over HTTP(S), depending on
>> how you've configured your settings
Interesting-- looks like I dropped the ball here. I'll issue an update to
address this-- thanks for catching it.
> It's also completely incorrect about the cause of the speed problems, which
> was mostly down to a combination of Ruby & CouchDB on the server side, not
> SSH. Opscode have been quite open about where the pain points were.
I freely admit I'm not a Chef guy-- my experience with it came down to
puttering around with it for a couple of days a few years ago trying to make
sense of it. As a result, my knowledge is out of date, and apparently largely
inaccurate. Sweet! Have a citation for where Opscode has fingered Ruby +
CouchDB? I'd prefer to not have to retract the retraction...
-- Corey
_______________________________________________
Discuss mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/discuss
This list provided by the League of Professional System Administrators
http://lopsa.org/
