I think you correctly caught my point. This seems very workable, *if* the 'yum-epel" can be reasonably included inside a recipe I'm writing. Getting it into an upstream recipe that hasn't predetermined what yum repositories I'm personally selecting..... may take more work.
But it looks like a solid approach, I'll try it.
[1] http://docs.opscode.com/dsl_recipe_method_resources.htmlinclude_recipe 'yum-epel'y = resources("yum_repository[epel]")y.action(:nothing)y.run_action(:create)
Good morning!
I'm testing some CentOS based systems that need Percona clustering. If I bootstrap the systems and have the 'recipe[yum::epel],recipe[yumrepo::percona]' recipes in the bootstrap run list, all is good. If I then configure the mysql settings to require the Percona versions of MySQL components,, such as setting the ":mysql => { :server => { packages => "Percona-XtraDB-Cluster-Server" } }' and other relevant settings, those packages are not visible at the time I do the initial bootstrap, so the bootstrap fails. They're only visible to chef *after* some earlier chef run has already enabled the particular yum repositories.
I'm not an expert, and this confuses me. Is there any graceful way to get the yum repositories enabled, and their contents properly detected, for later processing by mysql recipes?
--
Nico Kadel-Garcia
Senior Systems Consultant
Email: ">
Cell Phone: +1.339.368.2428
Archive powered by MHonArc 2.6.16.