[chef] Re: Re: customizing bootstrap


Chronological Thread 
  • From: Lamont Granquist < >
  • To:
  • Subject: [chef] Re: Re: customizing bootstrap
  • Date: Wed, 26 Nov 2014 10:02:00 -0800

On 11/26/14, 5:57 AM, Steven Danna wrote:
Hi,

Can you show us your modified install.sh? The current install.sh
script makes use of a service called "omnitruck" [0] and it appears
that your script is still expecting that API to exist [1].  Namely, we
are expecting

     
https://testing.exmaple.com/chef/metadata?v=11.16.2&prerelease=false&nightlies=false&p=el&pv=6&m=x86_64

to return something like:

     url     
https://opscode-omnibus-packages.s3.amazonaws.com/el/6/x86_64/chef-11.16.2-1.el6.x86_64.rpm
     md5     8731b6558009fc322f6469b415a759f8
     sha256  dc7bc9d6084d29ffec67664fdae455406c3e7657c4aebcbef19f5a9ba459db37

where the url is the actual location of the package to download.  To
host the packages yourself, you can either:

1) Host the packages on your local server and then modify install.sh
to simply point at the package and not need the omnitruck API
2) Host the packages in a local package repository and modify
install.sh to configure your system to use that repository


I wouldn't use install.sh or omnitruck at all. Just download the RPM or deb packages, set up your own internal repo, and modify bootstrap to configure the repo and install the package. If you want to host internal packages you'll want that internal repo anyway.




Archive powered by MHonArc 2.6.16.

§