General discussion about Chef

[chef] Re: Re: Re: custom cookbook


Chronological Thread 
  • From: Nikhil Shah < >
  • To: " " < >
  • Subject: [chef] Re: Re: Re: custom cookbook
  • Date: Tue, 21 Jul 2015 14:30:22 -0400
Thanks guys, I ended up taking Sean's advise and hosting the package on a remote webserver and editing my recipe to use remote_file instead. 

On Tue, Jul 21, 2015 at 1:24 PM, Ranjib Dey < " target="_blank"> > wrote:
+1
this will be an enormous performance pain. use s3 or something similar, a file server for all your installers, large files etc. i use remote_file and s3_file ,

even if you make chefserver work for those large files, your client runs gonna impact, as these large files will be served in compressed forms, decompressing them will be cpu intensive, same with checksum computing..

On Tue, Jul 21, 2015 at 9:35 AM, Sean OMeara < " target="_blank"> > wrote:
Uploading large binary files to the Chef server is "Bad, Mkay(tm)"

I'd look for an httpd server to host bootstrap.tar.xz, and use remote_file

-s

On Tue, Jul 21, 2015 at 10:27 AM, Nikhil Shah < " target="_blank"> > wrote:
> Hello,
>
> I am having a hard time uploading a cookbook larger than typical cookbooks.
> This is a POC cookbook and the vendor was able to upload to chef hosted;
> however, I cannot upload to my chef server.
>
>> Note: I've updated the /var/opt/opscode/nginx/etc/nginx.conf file and
>> edited the line for client_max_body_size 2048M;
>
>
> Also restarted nginx service via chef-server-ctl restart.
>
> Everytime I try to upload the cookbook, I get the following error:
>
>
>> knife cookbook upload dcos
>> Uploading dcos           [0.1.0]
>> ERROR: Failed to upload
>> /root/chef/cookbooks/dcos/files/default/bootstrap.tar.xz
>> (dd69f42f36246af0bfc3dfad0f5d1195) to
 >> https://chef04.theorchard.local:443/bookshelf/organization-436175e59363fc55b3620eecfe443b82/checksum-dd69f42f36246af0bfc3dfad0f5d1195?AWSAccessKeyId=23c9de96b156f0c1a59234ed809e60cafb7a3e5e764&Expires=1437423489325&Signature=toghY/CTHQUHWFbd5TJcOPaIJBE%3D
>> : 413 "Request Entity Too Large"
>> <html>
>> <head><title>413 Request Entity Too Large</title></head>
>> <body bgcolor="white">
>> <center><h1>413 Request Entity Too Large</h1></center>
>> <hr><center>openresty/1.7.10.1</center>
>> </body>
>> </html>
>> ERROR: Request Entity Too Large
>
>
> Any insight would be greatly appreciated.
>
> Thanks,
>
> --
> Nikhil Shah • System Administrator
> " target="_blank"> • p. (+1) 212 308-5648
>
> THE ORCHARD Distribution Done Right
> 23 E 4th St Fl 3, New York, NY 10003
> www.theorchard.com
>
> Follow us: The Daily Rind • Facebook • Twitter • YouTube • LinkedIn
>
> Privileged And Confidential Communication. This electronic transmission, and
> any documents attached hereto, (a) are protected by the Electronic
> Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain
> confidential and/or legally privileged information, and (c) are for the sole
> use of the intended recipient named above. If you have received this
> electronic message in error, please notify the sender and delete the
> electronic message. Any disclosure, copying, distribution, or use of the
> contents of the information received in error is strictly prohibited.




--
Nikhil Shah • System Administrator

THE ORCHARD Distribution Done Right
23 E 4th St Fl 3, New York, NY 10003

Follow us: The Daily Rind • Facebook • Twitter • YouTube • LinkedIn

Privileged And Confidential Communication. This electronic transmission, and any documents attached hereto, (a) are protected by the Electronic Communications Privacy Act (18 USC §§ 2510-2521), (b) may contain confidential and/or legally privileged information, and (c) are for the sole use of the intended recipient named above. If you have received this electronic message in error, please notify the sender and delete the electronic message. Any disclosure, copying, distribution, or use of the contents of the information received in error is strictly prohibited.

Archive powered by MHonArc 2.6.16.

§