[chef] Re: Re: 403 "Forbidden" when uploading cookbooks with large files

[Stephen Delano < >]

On Tue, Apr 22, 2014 at 2:27 AM, Tomasz Chmielewski < " target="_blank"> > wrote:

I can understand your point for some cases, but there are lots of valid
reasons to use chef to serve files of that size anyway.

Can you enumerate on these reasons? There are lots of reasons why you DON'T want to do this as well.

• Every time a developer checks out the cookbook repo for the first time, they're downloading multiple large files
• If a developer has a slow connection, they can't upload the cookbooks in a reasonable time
• When these files change, it will exacerbate this problem
• If a node needs a cookbook but doesn't need the large file, it still has to download the large file

The chef server wasn't designed to serve multi-hundred MB artifacts. It was designed to serve JSON data, text files, and templates. It CAN do it, but that doesn't mean you should. Don't be surprised if you find more tunable values that you'll need to change when you attempt to work out of the box like this.

Don't get me wrong, I'm not telling you not to do this or that I know what's best for you and your infrastructure. You're the ultimate decision maker there. I'm just warning you about the pitfalls you may encounter when straying from the beaten path. You've obviously already hit some of those, and you're still in the stages of uploading cookbooks. Good luck in your journey!

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