[chef] Re: Knife upload cookbook slowness

[Stephen Delano < >]

Hi Geoff,

`knife cookbook upload` is definitely not the fastest kid on the block, but "HOURS" to upload 20 cookbooks seems quite a bit out of the ordinary.

First off, are you uploading to an open source Chef server or Opscode's Hosted Chef?

> It seems to do a whole separate signed certificate-authenticated request for each little part of the cookbook it uploads looking at the debug..

If you're using the open source Chef server, you would be correct. You are uploading files directly to the server, so the requests must be signed. You wouldn't want someone dumping files onto your chef-server just by hitting the API would you?

If you're using Hosted Chef, the individual file uploads are not signed, but are instead sent to pre-signed, time-expired URLs that verify checksum integrity upon completion.

How many files do you have in this collection of 20 cookbooks?

What does your chef-server infrastructure look like? Is there a load-balancer, firewall, or some other appliance between you and your chef-server?

Cheers,

Stephen

On Mon, Sep 12, 2011 at 8:36 AM, Geoff Meakin Acid < "> > wrote:

Hi all,

Does anybody else find knife uploading cookbooks slow.. I mean really slow… (chef 0.10)

I have site installed about 20 cookbooks, but to upload them to my own chef server using the knife command takes >>HOURS

I have fallen back on rake installing from the server instead, (which takes a few seconds in comparison!) simply because knife uploading is taking so long it isnt really a viable option for me - but I cant think that that's what was intended. It seems to do a whole separate signed certificate-authenticated request for each little part of the cookbook it uploads looking at the debug..

Cheers
Geoff

--
Stephen Delano
Software Development Engineer
Opscode, Inc.
1008 Western Avenue
Suite 601
Seattle, WA 98104