General discussion about Chef

[chef] Re: Re: Re: Error file size


Chronological Thread 
  • From: Cassiano Leal < >
  • To:
  • Subject: [chef] Re: Re: Re: Error file size
  • Date: Mon, 28 Jul 2014 11:48:53 -0300
I don’t think so. The Chef Server is not intended to be used as a file serving mechanism. Cookbook files are for simple stuff — a static config file, a static public key of some sort, maybe a .rc file, etc.

Think about it for a second: you have a 350Mb file that you want to have as a part of your cookbook. After uploading it, you realise that there’s a small typo in a recipe. You fix it and re-upload it. Now this simple RPM is taking up 700Mb on your server. Escalate that to multiple versions and you begin to see the problem. In a way it’s akin to committing your compiled JARs to source control (in more than one way really, if you’re doing it right and keeping the cookbook on a VCS).

Binaries and big files are better served via HTTP, FTP or something else.


On Jul 28, 2014, at 11:24, Ana Ferreira < "> > wrote:

it must be a way to change that limit? or not?




On Mon, Jul 28, 2014 at 3:01 PM, Cassiano Leal < " target="_blank"> > wrote:
Well, yes. Remove the RPM, publish it on an external server, change your recipes to grab it from there and re-upload the cookbook.

There’s file size limit for cookbook files, but I can’t remember what it is. I’m sure someone else will chime in with the actual figure. :)

Cheers
Cassiano

> On Jul 28, 2014, at 10:47, < "> > < "> > wrote:
>
>
> Hello,
>
> does anyone know how to resolve this problem:
>
> RUNING: knife cookbook upload -a
>
> 413 "Request Entity Too Large"
>
> ERROR: Request Entity Too Large
> Response: <html>
> <head><title>413 Request Entity Too Large</title></head>
> <body bgcolor="white">
> <center><h1>413 Request Entity Too Large</h1></center>
> <hr><center>nginx/1.4.4</center>
> </body>
> </html>
>
> i'm trying to upload a 350mb rpm file.




Archive powered by MHonArc 2.6.16.

§