- From: "Kadel-Garcia, Nico" <
>
- To: "
" <
>
- Subject: [chef] RE: Re: Getting local yum repositories enabled before other cookbooks demand them in bootstrap
- Date: Sun, 16 Mar 2014 21:15:24 +0000
- Accept-language: en-US
Julian, I'm afraid that the relevant yum repositories, namely for packages
such as "socat" from EPEL and the "Percona-XtreDB-Cluster-server-55" from the
the Percona repositories, are not detected as available until after the
"yum::epel" or more recent "yum-epel" recipes have been successfully run, and
after the "yumrepo::percona" recipe has been successfully run. But when
bootstrapping a system, those have not been run successfully yet. the
installation recipes for the "mysql" or "percona" or any other cookbook
winds up using information from an earlier compilation stage *before* those
yum repository recipes have actually been run and enabled the 3rd party
repositores.
Because it uses an earlier compiled list of available packages, it reports
Percona-XtraDB-Cluster-sever-55 as unavailable and reports errors before any
recipe even gets run, so the bootstrap recipe list cannot even run. I can
manually pre-run 'chef-client -o
'recipe[yum::epel],recipe[yumrepo::percona]'. But it's painful, and breaks
push-button deployment via a pure bootstrap procedure.
It's quite frustrating. I intend to look at the "now" cookbook recommended by
Sean O'Mara as a possible solution, and look forward to Chef 12 perhaps being
less presumptive that the contents of yum installations can be predicted
before the "package" parts of recipes are compiled.
--
Nico Kadel-Garcia
Senior Systems Consultant
Email:
Cell Phone: +1.339.368.2428
________________________________________
From: Julian C. Dunn
<
>
Sent: Saturday, March 15, 2014 4:02 PM
To:
Subject: [chef] Re: Getting local yum repositories enabled before other
cookbooks demand them in bootstrap
Nico,
I'm a little confused by what you're describing. If you bootstrap a
fresh system with the run_list being something like
'recipe[yum-epel],recipe[yumrepo::percona],recipe[mysql::server]' and
the attribute node['mysql']['server']['packages'] =
['Percona-XtraDB-Cluster-Server'], you're saying it doesn't work?
Isn't the yum repo file created by the yumrepo::percona recipe you're
describing, so that it's available for the mysql::server run?
- Julian
--
[ Julian C. Dunn
<
>
* 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.