Planet Ubuntu-be.org http://ubuntu-be.org/nl/planet/rss Planet Feeds nl Reglementitis http://feedproxy.google.com/~r/MarkVanDenBorre/~3/1FwqMXUQoos/reglementitis.html <a href="http://www.standaard.be/cnt/dmf20140418_01073334">Wie toerist laat overnachten riskeert boete</a><br /><br /><br /><br /><br /><br />Wat we zelf regelneven regelneven we beter!<img src="http://feeds.feedburner.com/~r/MarkVanDenBorre/~4/1FwqMXUQoos" height="1" width="1"/> Mark Van den Borre Fri, 18 Apr 2014 09:49:00 +0200 MODELLING INFRASTRUCTURE WITH ANSIBLE INVENTORY DATA http://ginsys.eu/modelling-infrastructure-with-ansible-inventory-data/?utm_source=rss&utm_medium=rss&utm_campaign=rss&utm_source=rss&utm_medium=rss&utm_campaign=rss <p>Today I gave <a href="https://speakerdeck.com/svg/modelling-infrastructure-with-ansible-inventory-data#">a talk</a> at <a title="cfgmgmtcamp.eu" href="http://cfgmgmtcamp.eu/">cfgmgmtcamp.eu</a>, &#8220;MODELLING INFRASTRUCTURE WITH INVENTORY DATA&#8221;. <a href="https://speakerdeck.com/svg/modelling-infrastructure-with-ansible-inventory-data#">PDF slides are on Speakerdeck.<a title="cfgmgmtcamp.eu" href="http://cfgmgmtcamp.eu/">cfgmgmtcamp.eu</a>. Or, if you prefer de reveal.js source, have a look at it on my <a href="https://github.com/sergevanginderachter/revealjs-presentations/tree/cfgmgmtcampeu-ansible-inventory/Presentation">Github</a>. </p> Serge van Ginderachter Tue, 04 Feb 2014 20:36:46 +0100 Packt Publishing Ansible Configuration Management review http://ginsys.eu/packt-publishing-ansible-configuration-management-review/?utm_source=rss&utm_medium=rss&utm_campaign=rss&utm_source=rss&utm_medium=rss&utm_campaign=rss <p>Around late November 2013 I &#8211; too &#8211; got contacted by <a href="http://www.packtpub.com/">Packt Publishing</a>, asking to do a review on <a href="http://www.packtpub.com/ansible-configuration-management/book?utm_source=socialmedia.com&amp;utm_medium=books&amp;utm_campaign=Anisble+Configuration+Mangement">Ansible Configuration Management</a>. I was a bit surprised, as I had declined their offer to write that book, which they asked me exactly two months earlier. Two months seemed like a short period of time to manage to write a book and get it published.</p> <p>Either way, I kind of agreed, and got the book in pdf, printed it out, started some reading, lended it to a colleague (we us <a href="http://ansible.com/">Ansible</a> extensively at work), and just recently got it back so I could finish to have a look at it.</p> <p><em>&#8220;Ansible Configuration Management&#8221;</em> is an introductory book for beginners. I won&#8217;t introduce Ansible here, there are a lot of good resources on that, just <a href="https://duckduckgo.com/?q=ansible">duck it</a>. Ansible being relatively new, has evolved quite a bit in the previous year, releasing 1.4 by the end of November. The current development cycle focuses more on bug fixes, and under the hood stuff, and less on new syntax, which was quite the opposite when going from 0.9 through 1.2, and up until the then and now current 1.3.</p> <p>Knowing what major changes would get into 1.3 was easy when you followed the project. One of the major changes is the syntax for variables and templates. Basically, don&#8217;t use $myvar or ${othervar} any more, but only use {{ anicevar }}. If you know ansible, you know this is an important thing. I was very disappointed to notice the author didn&#8217;t stress this. Whilst most examples use the new syntax, at one point all syntax&#8217;s are presented as equally possible &#8211; which is correct for the then latest 1.3, but it was well known at the time it would be deprecated.</p> <p>Of course, writing a tech book on a rapid evolving Open Source tool, will always be deprecated by the time it gets published. But I think this should be expected, and a good book on such a subject should of course focus on the most recent possible release, but also try to mention the newer features that are to be expected. Especially for a publisher that also focuses on Open Source.</p> <p>A quirk, is when code snippets are discussed. Some of those longer snippets are printed across more than one page, and the book mentions certain line numbers. Which is confusing, and even unreadable, when the snippets don&#8217;t have line numbers. Later in the book, sometimes line numbers are used, but not in a very standard way:</p> <p>&nbsp;</p> <div id="attachment_297" style="width: 310px" class="wp-caption aligncenter"><a href="http://ginsys.eu/files/2014/01/20140118143510.png"><img class=" wp-image-297 " title="Weird Line Numbers" alt="code snippet with weird line number" src="http://ginsys.eu/files/2014/01/20140118143510-300x165.png" width="300" height="165" /></a><p class="wp-caption-text">code snippet with weird line number</p></div> <p>Whilst most of this book has a clear layout at first sight, things like this don&#8217;t feel very professional.</p> <p>This books gives a broad overview and discusses several basic things in ansible. It goes from basic syntax, over inventory, small playbooks, and extended playbooks ans also mentions custom code things. It gives lots of examples, discusses special variables, modules, plugins&#8230; and many more. Not all of them, but that is not needed, given the <a href="http://docs.ansible.com/">very good documentation</a> the project publishes. This book is an introduction to ansible, so focusing on the big principles is more important at this point, than having a full inventory of all features. As it&#8217;s a relatively short book (around 75 pages), it&#8217;s small enough to be appealing as a quick introduction.</p> <p>It&#8217;s a pity the publisher and the author didn&#8217;t pay more attention to details. The less critical user, with little to no previous ansible experience, will however get a good enough introduction with this book, with some more hand-holding and overview than what can easily be found freely on-line.</p> Serge van Ginderachter Sat, 18 Jan 2014 14:53:39 +0100