PageRenderTime 55ms CodeModel.GetById 24ms RepoModel.GetById 1ms app.codeStats 0ms

/blog/public/blog/2011/06/24/59995517/index.html

https://github.com/sbates/Bratty-Redhead
HTML | 294 lines | 182 code | 108 blank | 4 comment | 0 complexity | f715218f07dfb7c429a687ef7a7e2a16 MD5 | raw file
    

  1. 

  2. <!DOCTYPE html>
    3. 

  3. <!--[if IEMobile 7 ]><html class="no-js iem7"><![endif]-->
    4. 

  4. <!--[if lt IE 9]><html class="no-js lte-ie8"><![endif]-->
    5. 

  5. <!--[if (gt IE 8)|(gt IEMobile 7)|!(IEMobile)|!(IE)]><!--><html class="no-js" lang="en"><!--<![endif]-->
    6. 

  6. <head>
    7. 

  7.   <meta charset="utf-8">
    8. 

  8.   <title>My ohai plugin - WYSIWYG</title>
    9. 

  9.   <meta name="author" content="Sascha Bates">
    10. 

  10. 

  11.   
    12. 

  12.   <meta name="description" content="The plugin at github When we started the Chef infrastructure automation project last year, a dev team started up at nearly the same time.&nbsp; I &hellip;">
    13. 

  13.   
    14. 

  14. 

  15.   <!-- http://t.co/dKP3o1e -->
    16. 

  16.   <meta name="HandheldFriendly" content="True">
    17. 

  17.   <meta name="MobileOptimized" content="320">
    18. 

  18.   <meta name="viewport" content="width=device-width, initial-scale=1">
    19. 

  19. 

  20.   
    21. 

  21.   <link rel="canonical" href="http://brattyredhead.com/blog/2011/06/24/59995517">
    22. 

  22.   <link href="/favicon.png" rel="icon">
    23. 

  23.   <link href="/stylesheets/screen.css" media="screen, projection" rel="stylesheet" type="text/css">
    24. 

  24.   <script src="/javascripts/modernizr-2.0.js"></script>
    25. 

  25.   <script src="/javascripts/ender.js"></script>
    26. 

  26.   <script src="/javascripts/octopress.js" type="text/javascript"></script>
    27. 

  27.   <link href="/atom.xml" rel="alternate" title="WYSIWYG" type="application/atom+xml">
    28. 

  28.   <!--Fonts from Google"s Web font directory at http://google.com/webfonts -->
    29. 

  29. <link href="http://fonts.googleapis.com/css?family=PT+Serif:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
    30. 

  30. <link href="http://fonts.googleapis.com/css?family=PT+Sans:regular,italic,bold,bolditalic" rel="stylesheet" type="text/css">
    31. 

  31. 

  32.   
    33. 

  33. 

  34. </head>
    35. 

  35. 

  36. <body   >
    37. 

  37.   <header role="banner"><hgroup>
    38. 

  38.   <h1><a href="/">WYSIWYG</a></h1>
    39. 

  39.   
    40. 

  40.     <h2>no subtext here</h2>
    41. 

  41.   
    42. 

  42. </hgroup>
    43. 

  43. 

  44. </header>
    45. 

  45.   <nav role="navigation"><ul class="subscription" data-subscription="rss">
    46. 

  46.   <li><a href="/atom.xml" rel="subscribe-rss" title="subscribe via RSS">RSS</a></li>
    47. 

  47.   
    48. 

  48. </ul>
    49. 

  49.   
    50. 

  50. <form action="http://www.duckduckgo.com/" method="get">
    51. 

  51.   <fieldset role="search">
    52. 

  52.     <input type="hidden" name="q" value="site:brattyredhead.com" />
    53. 

  53.     <input class="search" type="text" name="q" results="0" placeholder="Search"/>
    54. 

  54.   </fieldset>
    55. 

  55. </form>
    56. 

  56.   
    57. 

  57. <ul class="main-navigation">
    58. 

  58.   <li><a href="/">Blog</a></li>
    59. 

  59.   <li><a href="/blog/archives">Archives</a></li>
    60. 

  60. </ul>
    61. 

  61. 

  62. </nav>
    63. 

  63.   <div id="main">
    64. 

  64.     <div id="content">
    65. 

  65.       <div>
    66. 

  66. <article class="hentry" role="article">
    67. 

  67.   
    68. 

  68.   <header>
    69. 

  69.     
    70. 

  70.       <h1 class="entry-title">My Ohai Plugin</h1>
    71. 

  71.     
    72. 

  72.     
    73. 

  73.       <p class="meta">
    74. 

  74.         
    75. 

  75. 

  76. 

  77. 

  78. 

  79. 

  80. 

  81. 

  82. 

  83.   
    84. 

  84. 

  85. 

  86. <time datetime="2011-06-24T00:00:00-05:00" pubdate data-updated="true">Jun 24<span>th</span>, 2011</time>
    87. 

  87.         
    88. 

  88.       </p>
    89. 

  89.     
    90. 

  90.   </header>
    91. 

  91. 

  92. 

  93. <div class="entry-content"><p><a href="https://github.com/sbates/Chef-odds-n-ends/blob/master/ohai/parse_host_plugin.rb" title="The plugin at github" target="_blank">The plugin at github</a></p>

    94. 

  94. <p>When we started the Chef infrastructure automation project last year,  a dev team started up at nearly the same time.&nbsp; I didn&#8217;t know enough  about Chef to have (much of) an opinion on how others were addressing  cookbook issues they faced. So for the first few months, I worked on my  problems to solve while the devs worked on theirs.&nbsp; I did eventually  started paying attention to what was going on with the dev team and  discovered that they had started to create role names that looked like  app_name_env(e.g. riak_prod), causing a role for each app to be created  in each environment, but with nearly identical run lists.&nbsp; They were  labeling their attributes with environment and used the roles to sort  them out.</p>

    95. 

  95. <p>So we came up with a quick solution.&nbsp; We created an attribute called  node[:env] and put it in a role called env_dev, env_qa, etc.&nbsp; And the  same goes for other things we needed to set like node[:swimlane] and  node[:zone]. Every time a node was created, relevant env attribute roles  were added along with the platform_base and any application roles.&nbsp; We  all refactored our code and started using the env variable to sort out  environment-specific attributes. This worked well in the short term, for  about 6 months.</p>

    96. 

  96. <p>About 2 months ago, we started planning for provisioning a second  data center.&nbsp; With another data center containing two environments (prod  and stage) came a location issue.&nbsp; Now we have two sets of ntp servers,  different DNS servers and a whole host of location-specific coding  issues. I went to go add some location-specific roles and started  thinking about the refactoring we&rsquo;d need to do to account for two  locations.</p>

    97. 

  97. <p>As I started to make the first role, I realized that this was quickly  becoming an unwieldy solution.&nbsp; We were configuring the nodes managed  by our automation system <strong>by hand</strong>.&nbsp; This boggled me. And the number of managed nodes continues to grow.</p>

    98. 

  98. <p>&nbsp;</p>

    99. 

  99. <p>One of the problems we struggle with is that we have no system of  record.&nbsp; We get most of our new server info on spreadsheets from various  project teams or ops/mgmt teams.&nbsp; We can&rsquo;t call any central system API  to get info. &nbsp;All the servers have static IPs and minimum of two  networks. The ops team doesn&rsquo;t believe in DNS. So we have to keep all of  this information somewhere or figure out clever ways to deduce the  information we want (or set roles by hand, ugh!).</p>

    100. 

  100. <p>A secondary problem I had with the roles is that their attributes  weren&rsquo;t set early enough for me to use logic in the attributes file.&nbsp;  Node[:env] didn&rsquo;t get set until after attributes files were compile  which was causing me other problems.</p>

    101. 

  101. <p>So as I thought about the location role, I rebelled.&nbsp; I was <strong>done</strong> setting roles by hand.&nbsp; UGH!</p>

    102. 

  102. <p>All of our host names are the same length and contain a rich amount  of data encoded in their names.&nbsp; I thought that there must be a way to  extract and label that information for use as node attibutes.&nbsp; I&rsquo;m no  Ruby genius and I still struggle with anything beyond fancy scripting,  but it&rsquo;s extra fun for me to run at a problem head on and obsess over  it. And that&rsquo;s what I did.&nbsp;</p>

    103. 

  103. <p>When I came out of the weekend, I had an oHai plugin that parsed a  host name, set 3 top level attributes and 5 nested attributes thatI  thought might be useful for logic in cookbooks.&nbsp; It looks like this:</p>

    104. 

  104. <p>[root@pxqpkyapp05 tmp]# ohai -f /tmp/plugins/parse_host_plugin.rb&nbsp; -l debug<br /> [Fri, 24 Jun 2011 19:09:09 -0500] DEBUG: ohai plugin: parse_host: parsing new host pxqpkyapp05<br /> {</p>

    105. 

  105. <p><strong>&nbsp; &#8220;environment&#8221;: &#8220;qa&#8221;</strong><br /> <strong>&nbsp; &#8220;location&#8221;: &#8220;pismo&#8221;,</strong><br /> &nbsp; &#8220;hostdata&#8221;: {<br /> &nbsp;&nbsp;&nbsp; &#8220;server_type&#8221;: &#8220;application&#8221;,<br /> &nbsp;&nbsp;&nbsp; &#8220;loc&#8221;: &#8220;p&#8221;,<br /> &nbsp;&nbsp;&nbsp; &#8220;env&#8221;: &#8220;q&#8221;,<br /> &nbsp;&nbsp;&nbsp; &#8220;application&#8221;: &#8220;Pooky&#8221;,<br /> &nbsp;&nbsp;&nbsp; &#8220;platform&#8221;: &#8220;solaris&#8221;<br /> &nbsp; },<br /> }<br /> </p>

    106. 

  106. <p>I didn&rsquo;t think this would be useful to anyone but us.&nbsp; Surely  everyone else was using Chef in the cloud, right?&nbsp; Heck no.&nbsp; It turns  out, as I was chatting with folks at Velocity last week, that several  people are data center-bound with encoded host names.&nbsp; Discussing it, I  thought it might be useful to share, even if it would require some  tweaking to make it work with any else&rsquo;s environment.</p>

    107. 

  107. <p>Basically, I set a hash with environment data and then set variables  using a regex on the host name.&nbsp; I set the environment and location vars  separately and then put indexes in the hash for any values I want to  add into the hostdata hash.&nbsp; I took most of our custom logic out, like  the node[:zone] logic that no one needs, although I left in a custom  piece I had to add for an oddly named environment at a third data center  location.&nbsp; All app names and locations have been changed to protect the  innocent (that&rsquo;s me).</p>

    108. 

  108. <p>I hope someone else can use it.&nbsp; It was my first step beyond recipes  and I&rsquo;m rather proud of it. I&#8217;ve already had a request from a team mate  to move the logic to a library so that we can use it in our host  management activities and that&#8217;s what I&#8217;m working on now.&nbsp; I&#8217;ve created a  class and a function that uses the class, but need to translate it to  Chef-specific DSL.</p>

    109. 

  109. <p>Here are some examples of how we&#8217;re using them:</p>

    110. 

  110. <p>&nbsp;</p>

    111. 

  111. <p>in the recipe: dnsinfo = search(:dns, &#8220;id:#{node.location}&#8221;)</p>

    112. 

  112. <p>in the template:</p>

    113. 

  113. <p>domain &lt;%= @dnsinfo[&#8220;domain&#8221;] %&gt;<br />search &lt;%= @dnsinfo[&#8220;search&#8221;] %&gt;<br />&lt;% @dnsinfo[&#8220;nameservers&#8221;].each do |ns| %&gt;<br />nameserver &lt;%= ns %&gt;<br />&lt;% end %&gt;</p>

    114. 

  114. <p># Unload unwanted packages<br />unless node.env == &#8220;dev&#8221; || node.attribute?(&#8220;keep_gcc&#8221;)<br />&nbsp;package &#8220;gcc&#8221; do<br />&nbsp;&nbsp; action :remove<br />&nbsp;end<br />end<p /></p>

    115. 

  115. <p>chefsearch = search(&#8220;chef_servers&#8221;,&#8221;env:#{node.env} AND id:#{node.hostdata.loc}*&#8221;).first<br />node.set.chef.my_chef_server = chefsearch[&#8220;id&#8221;]</p>

    116. 

  116. <p>node.set.chef.server_url = &#8220;http://#{node.chef.my_chef_server}&#8221;<br />node.set.chef.mrepo_url = &#8220;http://#{node.chef.my_chef_server}/mrepo&#8221;<br />node.set.chef.proxy_url = &#8220;http://#{node.chef.my_chef_server}:8000&#8221;</p>

    117. 

  117. <p>&nbsp;</p>

    118. 

  118. <p>This will also come in handy once we&#8217;ve migrated to .10 where we can  set so many more things within Chef based on environment.&nbsp; The plugin is  phrased in functions as my original plugin file was rather messy with  comments and things.&nbsp; I felt like breaking it down this way made it  easier to follow wth was going on.</p>

    119. 

  119. <p>Please let me know if you find this useful or if you have questions.&nbsp;  This is my first community contribution and so I&#8217;m kind of like the kid  with the cool shiny thing they want to show everyone.&nbsp; Look at my  shiny!</p>
    120. 

  120. </div>
    121. 

  121. 

  122. 

  123.   <footer>
    124. 

  124.     <p class="meta">
    125. 

  125.       
    126. 

  126.   
    127. 

  127. 

  128. <span class="byline author vcard">Posted by <span class="fn">Sascha Bates</span></span>
    129. 

  129. 

  130.       
    131. 

  131. 

  132. 

  133. 

  134. 

  135. 

  136. 

  137. 

  138. 

  139.   
    140. 

  140. 

  141. 

  142. <time datetime="2011-06-24T00:00:00-05:00" pubdate data-updated="true">Jun 24<span>th</span>, 2011</time>
    143. 

  143.       
    144. 

  144. 

  145. 

  146.     </p>
    147. 

  147.     
    148. 

  148.       <div class="sharing">
    149. 

  149.   
    150. 

  150.   <a href="http://twitter.com/share" class="twitter-share-button" data-url="http://brattyredhead.com/blog/2011/06/24/59995517/" data-via="sascha_d" data-counturl="http://brattyredhead.com/blog/2011/06/24/59995517/" >Tweet</a>
    151. 

  151.   
    152. 

  152.   
    153. 

  153.   
    154. 

  154. </div>
    155. 

  155. 

  156.     
    157. 

  157.     <p class="meta">
    158. 

  158.       
    159. 

  159.         <a class="basic-alignment left" href="/blog/2011/06/23/another-chapter-done/" title="Previous Post: Another Chapter Done">&laquo; Another Chapter Done</a>
    160. 

  160.       
    161. 

  161.       
    162. 

  162.         <a class="basic-alignment right" href="/blog/2011/06/24/reason-eleventyseven-to-automate/" title="Next Post: Reason #eleventyseven to automate">Reason #eleventyseven to automate &raquo;</a>
    163. 

  163.       
    164. 

  164.     </p>
    165. 

  165.   </footer>
    166. 

  166. </article>
    167. 

  167. 

  168. </div>
    169. 

  169. 

  170. <aside class="sidebar">
    171. 

  171.   
    172. 

  172.     <section>
    173. 

  173.   <h1>About Me</h1>
    174. 

  174.   <p>A little something about me.</p>
    175. 

  175. </section>
    176. 

  176. <section>
    177. 

  177.   <h1>Recent Posts</h1>
    178. 

  178.   <ul id="recent_posts">
    179. 

  179.     
    180. 

  180.       <li class="post">
    181. 

  181.         <a href="/blog/2012/05/27/finding-sanity-with-chef/">Finding Sanity With Chef</a>
    182. 

  182.       </li>
    183. 

  183.     
    184. 

  184.       <li class="post">
    185. 

  185.         <a href="/blog/2012/05/08/test/">test</a>
    186. 

  186.       </li>
    187. 

  187.     
    188. 

  188.       <li class="post">
    189. 

  189.         <a href="/blog/2012/04/27/my-favorite-jvm-arg-ever/">My Favorite JVM Arg EVER</a>
    190. 

  190.       </li>
    191. 

  191.     
    192. 

  192.       <li class="post">
    193. 

  193.         <a href="/blog/2012/04/26/the-alien-technology-tuning-challenge/">The Alien Technology Tuning Challenge</a>
    194. 

  194.       </li>
    195. 

  195.     
    196. 

  196.       <li class="post">
    197. 

  197.         <a href="/blog/2012/04/15/yak-hacking/">Yak Hacking - A Story</a>
    198. 

  198.       </li>
    199. 

  199.     
    200. 

  200.       <li class="post">
    201. 

  201.         <a href="/blog/2012/04/01/weekend-chef-and-puppet-projects/">Weekend Chef and Puppet Projects</a>
    202. 

  202.       </li>
    203. 

  203.     
    204. 

  204.       <li class="post">
    205. 

  205.         <a href="/blog/2012/03/26/annoying-recruiter-call-45/">Annoying Recruiter Call #45</a>
    206. 

  206.       </li>
    207. 

  207.     
    208. 

  208.       <li class="post">
    209. 

  209.         <a href="/blog/2012/03/23/i-am-not-a-fangirl/">I am not a fangirl</a>
    210. 

  210.       </li>
    211. 

  211.     
    212. 

  212.       <li class="post">
    213. 

  213.         <a href="/blog/2011/11/19/puppet-for-chef-users-part-2-when-is-a-node-a/">Puppet for Chef Users - Part 2 - When is a node a node? </a>
    214. 

  214.       </li>
    215. 

  215.     
    216. 

  216.       <li class="post">
    217. 

  217.         <a href="/blog/2011/11/07/puppet-for-chef-users/">Puppet for Chef Users</a>
    218. 

  218.       </li>
    219. 

  219.     
    220. 

  220.   </ul>
    221. 

  221. </section>
    222. 

  222. 

  223. <section>
    224. 

  224.   <h1>Latest Tweets</h1>
    225. 

  225.   <ul id="tweets">
    226. 

  226.     <li class="loading">Status updating...</li>
    227. 

  227.   </ul>
    228. 

  228.   <script type="text/javascript">
    229. 

  229.     $.domReady(function(){
    230. 

  230.       getTwitterFeed("sascha_d", 4, false);
    231. 

  231.     });
    232. 

  232.   </script>
    233. 

  233.   <script src="/javascripts/twitter.js" type="text/javascript"> </script>
    234. 

  234.   
    235. 

  235.     <a href="http://twitter.com/sascha_d" class="twitter-follow-button" data-show-count="false">Follow @sascha_d</a>
    236. 

  236.   
    237. 

  237. </section>
    238. 

  238. 

  239. 

  240. <section>
    241. 

  241.   <h1>My Pinboard</h1>
    242. 

  242.   <ul id="pinboard_linkroll">Fetching linkroll...</ul>
    243. 

  243.   <p><a href="http://pinboard.in/u:sascha_d">My Pinboard Bookmarks &raquo;</a></p>
    244. 

  244. </section>
    245. 

  245. <script type="text/javascript">
    246. 

  246.   var linkroll = 'pinboard_linkroll'; //id target for pinboard list
    247. 

  247.   var pinboard_user = "sascha_d"; //id target for pinboard list
    248. 

  248.   var pinboard_count = 3; //id target for pinboard list
    249. 

  249.   (function(){
    250. 

  250.     var pinboardInit = document.createElement('script');
    251. 

  251.     pinboardInit.type = 'text/javascript';
    252. 

  252.     pinboardInit.async = true;
    253. 

  253.     pinboardInit.src = '/javascripts/pinboard.js';
    254. 

  254.     document.getElementsByTagName('head')[0].appendChild(pinboardInit);
    255. 

  255.   })();
    256. 

  256. </script>
    257. 

  257. 

  258. 

  259.   
    260. 

  260. </aside>
    261. 

  261. 

  262. 

  263.     </div>
    264. 

  264.   </div>
    265. 

  265.   <footer role="contentinfo"><p>
    266. 

  266.   Copyright &copy; 2012 - Sascha Bates -
    267. 

  267.   <span class="credit">Powered by <a href="http://octopress.org">Octopress</a></span>
    268. 

  268. </p>
    269. 

  269. 

  270. </footer>
    271. 

  271.   
    272. 

  272. 

  273. 

  274. 

  275. 

  276. 

  277. 

  278. 

  279.   <script type="text/javascript">
    280. 

  280.     (function(){
    281. 

  281.       var twitterWidgets = document.createElement('script');
    282. 

  282.       twitterWidgets.type = 'text/javascript';
    283. 

  283.       twitterWidgets.async = true;
    284. 

  284.       twitterWidgets.src = 'http://platform.twitter.com/widgets.js';
    285. 

  285.       document.getElementsByTagName('head')[0].appendChild(twitterWidgets);
    286. 

  286.     })();
    287. 

  287.   </script>
    288. 

  288. 

  289. 

  290. 

  291. 

  292. 

  293. </body>
    294. 

  294. </html>
    295. 

  295.