[chef] Getting local yum repositories enabled before other cookbooks demand them in bootstrap


Chronological Thread 
  • From: "Kadel-Garcia, Nico" < >
  • To: " " < >
  • Subject: [chef] Getting local yum repositories enabled before other cookbooks demand them in bootstrap
  • Date: Thu, 13 Mar 2014 11:43:12 +0000
  • Accept-language: en-US

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.

§