- From: Tomasz Chmielewski <
>
- To: Stephen Delano <
>
- Cc:
- Subject: [chef] Re: Re: 403 "Forbidden" when uploading cookbooks with large files
- Date: Tue, 22 Apr 2014 16:25:26 +0100
- Domainkey-signature: a=rsa-sha1; c=nofws; d=wpkg.org; h=to:subject :mime-version:content-type:content-transfer-encoding:date:from :cc:in-reply-to:references:message-id; q=dns; s=default; b=5EPhx 95pTwsUWSiTJPvLHvdwtEkJpN+YY1VmlI3sf+T9ihtD7eHkfALFyb0tXnTe5w22n dc0IZAr7t6nTx8AadG0qUUqahO4NdKrGP1D1GI7T635zNe7DDMSos2DJEizf5HvJ MvysdD0Fnaw9FoAuwaRHRI7j87i/lL/J4SvQQ4=
On 2014-04-22 15:57, Stephen Delano wrote:
On Tue, Apr 22, 2014 at 2:27 AM, Tomasz Chmielewski
<
>
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.
Basically, that's simplicity, especially for smaller deployments.
* no need to set up a separate webserver for file serving
* no need to worry about separate webserver auth, SSL certificates,
credentials,
* lower learning curve for Chef - once I'm able to do simple things
(uploading a single file should be a simple thing), I can jump to more
complicated ones
* "large file" turned out to be ~150 MB for my link, but could be 10 MB
for someone else with a slower link. Also, I'd argue if most people
reading this have ~150 MB in mind if they read "multi-hundred MB
artifact"
* if Chef wasn't designed to serve files of some sizes, it should
complain about it (i.e. "WARN: file XYZ is larger than 10 MB, this
exceeds Chef design"); not fail with unclear reason,
* official documentation for cookbook_file,
http://docs.opscode.com/resource_cookbook_file.html, or
http://docs.opscode.com/essentials_cookbook_files.html, does not mention
potential file size issues - but could be I wasn't looking in the right
place.
Of course I find your all points valid, too.
--
Tomasz Chmielewski
http://wpkg.org
Archive powered by MHonArc 2.6.16.