attributes not only allows us to tune/customize the behavior of an recipe, without changing it (kinda open close principle applied to recipes) , but also provides a mechanism for detecting or storing persistent information beyond a chef run. So even if you dont want to customize a property, but just want to access it beyond the chef run you might want to model it as an attribute. iirc the mysql cookbook generates a random root password (using the openssl cookbook libraries?) and stores it as an attribute, here you cant change it , but still you can grab it and use for other tooling (like the lwrps for database and user uses this info), the cookbook also restrict the root access to localhost.regarding multiple service start, ubuntu does this as part of the installation, and also the config changes require service restart/reload again.Again these are not the best implementation, but they are getting better. I recall joshua had posted on the mailing list regarding this specific case, i.e. mysql root password/mysql cookbook and some tricky use cases.On Tue, Mar 26, 2013 at 2:57 PM, Steven Barre < " target="_blank"> > wrote:
I've also been wondering why some attributes are "tuneable" and others are not. I also noticed the config file seems to just be the stock ubuntu one with a few modifications.
I'm also trying to understand why mysql is installed, started, and then the conf file is changed then mysql restarted. Wouldn't it make more sense to have the config file set up before the first run of mysql? Things like pid file and innodb log files don't handle changing very well. (as pointed out here http://tickets.opscode.com/browse/COOK-2100)
I'm starting to think this need some rewriting .... I'll volunteer, but I'm new at this. Some input from others would be appreciated.
================================================= Steven Barre, RHCE, ZCE, MCP " target="_blank"> Systems Administrator / Programmer Real Estate Webmasters - 250-753-9893 ==================================================On 2013-03-26 14:07, Jesse Campbell wrote:
Same here, i set it in the database server role for our nodes... it seems undocumented, and i was waiting / hoping whomever added that code would comment here
On Tue, Mar 26, 2013 at 2:51 PM, Aaron Brown < " target="_blank"> > wrote:
I discovered that I had to set it manually.
On Tue, Mar 26, 2013 at 2:24 PM, Steven Barre < " target="_blank"> > wrote:
Does no one know how this is supposed to work?
=================================================
Steven Barre, RHCE, ZCE, MCP
" target="_blank">
Systems Administrator / Programmer
Real Estate Webmasters - 250-753-9893
==================================================
On 2013-03-21 15:23, Steven Barre wrote:
Hello
In attributes/server.rb
https://github.com/opscode-cookbooks/mysql/blob/bfabce615dffe144a161bc5979873a7e9811f172/attributes/server.rb#L41-47
There is the use of node["mysql"]["version"]. But I don't see where that gets set. Could someone explain that to me?
Archive powered by MHonArc 2.6.16.