[chef] Re: RE: Re: RE: Re: No chefdk RPM available for RHEL 5?


Chronological Thread 
  • From: AJ Christensen < >
  • To: " " < >
  • Subject: [chef] Re: RE: Re: RE: Re: No chefdk RPM available for RHEL 5?
  • Date: Tue, 17 Mar 2015 10:43:13 +1300

I am pretty confident that there are no srpms. It's all omnibus. I know, :mindblown:, right?

https://github.com/chef/chef-dk

Why do you need berkshelf on your edge nodes? you typically run it from a workstation/CI then consume the assembled assets toward the edge. Resolving on the edge all the time is not something seen very often, I think.

You may have varying mileage by modifying the omnibus-chef/chef-dk/.. to target RH5 as a build platform; you typically just setup whatever Omnibus needs then run it inside the VM.

GL, HF!

cheers,

--aj

On Tue, Mar 17, 2015 at 10:31 AM, Nico Kadel-Garcia < " target="_blank"> > wrote:

I’m afraid this puts me in a difficult place. It means that, for RHEL 5 based operating systems, I’ll have to use the standard ‘chef’ client, which means that to use Berkshelf on them I’ll have to compile Berkshelf. I’m not sure if anyone’s mentioned lately that Berkshelf takes a quite long time, and quite a few resources, to compile: many smaller virtual machins running RHEL 5 will effectively swap themselves to death, or even run out of swap space and crash, if the root user tries to compile Berkshelf. It means that to use my preferred chef-solo environments for RHEL 5 based systems, I’ll have to compile it on a sample host and push the newly compiled components, out of band, to the target systems.

 

I’d be happy to take a look at building an RHEL 5 RPM myself, if I had some sense of the build environments or .spec files actually used for chefdk RPM building. Are the SRPM’s available anywhere, or source with the actual .spec files and any applied patches, available anywhere public? I’d also really like to encourage publishing the SRPM.

 

In fact, as I checked the RPM, I noticed that it has no ‘License’ option set. May I suggest putting that in the spec file? I’d offer a patch to it, but I can’t seem to find the relevant chefdk.spec file in a public repository.

 

Nico Kadel-Garcia

Lead DevOps Engineer

" target="_blank">

 

 

From: Julian C. Dunn [mailto: " target="_blank"> ]
Sent: Thursday, March 05, 2015 5:56 PM
To: " target="_blank">
Subject: [chef] Re: RE: Re: No chefdk RPM available for RHEL 5?

 

We made a conscious product decision not to support RHEL 5 as a platform for ChefDK.

 

 

- Julian

 

On Thu, Mar 5, 2015 at 9:46 AM, Fouts, Chris < " target="_blank"> > wrote:

I’ve tried installing ChefDK on RHEL 5.11 to no avail since it requires ruby libraries that are not available.

 

Chris

 

From: Peter Burkholder [mailto: " target="_blank"> ]
Sent: Wednesday, March 04, 2015 10:31 PM
To: " target="_blank">
Subject: [chef] Re: No chefdk RPM available for RHEL 5?

 

You should be able to use the RHEL 6 rpm on RHEL 5. Worth a try.

 

On Wed, Mar 4, 2015 at 6:27 PM, Nico Kadel-Garcia < " target="_blank"> > wrote:

I've been testing some environments with RHEL 6 and chefdk 0.4.0, which works well, but can't seem to find chedk for RHEL 5. I particularly want it for the integrated Berkshelf support, which is much easier to use from chefdk rather than compiling it locally.

Is thee a chefk RPM available for RHEL 5? Can I do anything to help create one? I've done *many, many, many* RPM backports in my career.

Nico Kadel-Garcia
Lead DevOps Engineer
" target="_blank">



 

--

Peter Burkholder — Customer Success Engineer

Unavailability: Travel March 2-3; Vacation March 16-20; ChefConf March 30-April 3

301-204-5767 –  " target="_blank">  – my: Linkedin  Twitter  Calendar

CHEF

CHEF.IO

TM

chef.io   Blog   Facebook   Twitter   Youtube  

 



 

--

[ Julian C. Dunn < " target="_blank"> >          * Sorry, I'm    ]
[ WWW: http://www.aquezada.com/staff/julian    * only Web 1.0  ]
[ gopher://sdf.org/1/users/keymaker/           * compliant!    ]
[ PGP: 91B3 7A9D 683C 7C16 715F 442C 6065 D533 FDC2 05B9       ]





Archive powered by MHonArc 2.6.16.

§