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 From: Julian C. Dunn [mailto:
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:
-- [ Julian C. Dunn <
" target="_blank">
> * Sorry, I'm ] |
Archive powered by MHonArc 2.6.16.