<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://lopsa.org">
<channel>
 <title>League of Professional System Administrators blogs</title>
 <link>http://lopsa.org/blog</link>
 <description></description>
 <language>en</language>
<item>
 <title>Conference report: Configuration Management Summit 2010</title>
 <link>http://lopsa.org/node/1969</link>
 <description>&lt;p&gt;My report from USENIX 2010 Configuration Management Summit is at  &lt;a href=&quot;http://www.linux-mag.com/id/7841&quot;&gt;http://www.linux-mag.com/id/7841&lt;/a&gt;&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1969&quot; dc:identifier=&quot;http://lopsa.org/node/1969&quot; dc:title=&quot;Conference report: Configuration Management Summit 2010&quot; trackback:ping=&quot;http://lopsa.org/trackback/1969&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Wed, 25 Aug 2010 00:27:45 -0700</pubDate>
 <author>Aleksey Tsalolikhin</author>
</item>
<item>
 <title>Updating Rubygems: a necessary step before installing the Amazon gem</title>
 <link>http://lopsa.org/node/1954</link>
 <description>&lt;p&gt;This article shows you how to install a gem (a ruby package) that provides access to Amazon APIs for EC2, ELB, and RDS. But along the way it also provides important information on the entire Rubygems environment. This information is critical for anyone who is tasked with maintaining a working Ruby environment.&lt;/p&gt;
&lt;p&gt;Yesterday I posted an entry about using Ruby to access the Amazon EC2 API and I mentioned a gem that provided the classes needed to make such access easy. Gem is the package system for ruby, and fills a role similar to one that CPAN provides for perl. The Amazon gem is called &lt;i &gt;amazon-ec2&lt;/i&gt; and it is written and supported by Glenn Rempe.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1954&quot; dc:identifier=&quot;http://lopsa.org/node/1954&quot; dc:title=&quot;Updating Rubygems: a necessary step before installing the Amazon gem&quot; trackback:ping=&quot;http://lopsa.org/trackback/1954&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <pubDate>Mon, 16 Aug 2010 10:47:08 -0700</pubDate>
 <author>wnl</author>
</item>
<item>
 <title>Using Ruby with Amazon Web Services, an example</title>
 <link>http://lopsa.org/node/1953</link>
 <description>I&#039;ve been recently extolling the virtues of Ruby on the Lopsa IRC channel so
I thought it would be fun to take a real world problem and write a
Ruby-based solution. This particular problem has to do with
manipulating snapshots in Amazon&#039;s EC2. Those who administer EC2
instances know (or should know) that the storage associated with an
instance does not outlast the instance. If you want persistent storage
you have to create a volume of elastic block store. Not only will it
outlast the instance, it can be moved between them and it can be
backed up into something called a snapshot.
&lt;p&gt;
On most of our instances we have a cron job that creates a snapshot of

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1953&quot; dc:identifier=&quot;http://lopsa.org/node/1953&quot; dc:title=&quot;Using Ruby with Amazon Web Services, an example&quot; trackback:ping=&quot;http://lopsa.org/trackback/1953&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <pubDate>Sun, 15 Aug 2010 14:10:55 -0700</pubDate>
 <author>wnl</author>
</item>
<item>
 <title>Cool things I saw at SIGGRAPH 2010 exhibition hall</title>
 <link>http://lopsa.org/node/1948</link>
 <description>&lt;p&gt;SIGGGRAPH 2010&lt;/p&gt;
&lt;p&gt;Trip Report of Cool Things Aleksey Saw in the Exhibition Hall&lt;/p&gt;
&lt;p&gt;(Coolest stuff at the top.)&lt;/p&gt;
&lt;p&gt;- FusionIO had the coolest demo!! 1500 DVD-quality videos streaming&lt;br /&gt;
from a single Fusion IO (RAM-based) 640 GB drive displayed onto a large&lt;br /&gt;
virtual screen (composed of 16 - that&#039;s 4x4 large displayes).  all 1500&lt;br /&gt;
videos were displayed simultaneiously in tiny little rectangles.&lt;/p&gt;
&lt;p&gt;- Digital Double Agency - a French company (&lt;a href=&quot;http://www.adnda.com&quot;&gt;www.adnda.com&lt;/a&gt;) used to capture&lt;br /&gt;
your face (three sessions of 4 hours each) and a wide variety of facial expression; and capture your voice; and then the double can talk and interact -- so you can capture a celebrity&#039;s likeness and have the digital double act in movies; or so you can have an avatar online.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1948&quot; dc:identifier=&quot;http://lopsa.org/node/1948&quot; dc:title=&quot;Cool things I saw at SIGGRAPH 2010 exhibition hall&quot; trackback:ping=&quot;http://lopsa.org/trackback/1948&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Thu, 29 Jul 2010 10:14:08 -0700</pubDate>
 <author>Aleksey Tsalolikhin</author>
</item>
<item>
 <title>Results of trying to vary GNU tar blocking factor to increase tape write/read speed for 2K content</title>
 <link>http://lopsa.org/node/1940</link>
 <description>My results transferring 685 2K frames (11MB per file, 8.1 GB total) using GNU tar to/from LTO4 tape

&lt;table&gt;
&lt;tr&gt;
&lt;th&gt;
GNU tar Blocking Factor
&lt;/th&gt;
&lt;th&gt;Write LTO4&lt;/th&gt;
&lt;th&gt;Read LTO4&lt;/th&gt;
&lt;/tr&gt;
&lt;/tr&gt;&lt;td&gt;1024&lt;/td&gt;            
&lt;td&gt;2m34s&lt;/td&gt;           
&lt;td&gt;1m16s&lt;/td&gt;
&lt;/tr&gt;

&lt;tr&gt;
&lt;td&gt;2048&lt;/td&gt;            &lt;td&gt;1m24s&lt;/td&gt;           &lt;td&gt;1m16s&lt;/td&gt;
&lt;/tr&gt;

&lt;tr&gt;
&lt;td&gt;4096&lt;/td&gt;            &lt;td&gt;1m19s&lt;/td&gt;           &lt;td&gt;1m34s&lt;/td&gt;
&lt;/tr&gt;
&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1940&quot; dc:identifier=&quot;http://lopsa.org/node/1940&quot; dc:title=&quot;Results of trying to vary GNU tar blocking factor to increase tape write/read speed for 2K content&quot; trackback:ping=&quot;http://lopsa.org/trackback/1940&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 09 Jul 2010 16:17:19 -0700</pubDate>
 <author>Aleksey Tsalolikhin</author>
</item>
<item>
 <title>Sixth Annual Triangle InfoSeCon Conference - &quot;Call for Papers&quot;</title>
 <link>http://lopsa.org/node/1938</link>
 <description>&lt;p&gt;Sixth Annual Triangle InfoSeCon Conference - &quot;Call for Papers&quot;&lt;/p&gt;
&lt;p&gt;Sixth Annual Triangle InfoSeCon Conference  - &quot;Call for Papers&quot;&lt;br /&gt;
&amp;gt;&lt;br /&gt;
&amp;gt; Members and Fellow ITSec Professionals,&lt;br /&gt;
&amp;gt;&lt;br /&gt;
&amp;gt; CALL for PAPERS is now open! See conference webpages&lt;br /&gt;
&amp;gt; (&lt;a href=&quot;http://raleigh.issa.org/conference.html&quot;&gt;http://raleigh.issa.org/conference.html&lt;/a&gt;).&lt;br /&gt;
&amp;gt;&lt;br /&gt;
&amp;gt; Spread the word within your organizations and among your cohort.&lt;br /&gt;
&amp;gt;&lt;br /&gt;
&amp;gt; The Raleigh ISSA Chapter announces the sixth annual Triangle InfoSeCon. This&lt;br /&gt;
&amp;gt; Information Security conference is on Thursday, October 21, 2010, at the&lt;br /&gt;
&amp;gt; McKimmon Center  in Raleigh, North&lt;br /&gt;
&amp;gt; Carolina located  on the campus of&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1938&quot; dc:identifier=&quot;http://lopsa.org/node/1938&quot; dc:title=&quot;Sixth Annual Triangle InfoSeCon Conference - &quot;Call for Papers&quot;&quot; trackback:ping=&quot;http://lopsa.org/trackback/1938&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Tue, 29 Jun 2010 13:54:05 -0700</pubDate>
 <author>Liyun Yu</author>
</item>
<item>
 <title>Turning perl regular expressions from line noise into documented code</title>
 <link>http://lopsa.org/node/1935</link>
 <description>&lt;p&gt;Problem:  Sufficiently long regular expressions start to look like line noise and become unmaintainable&lt;/p&gt;
&lt;p&gt;Solution:  Use perl regular expressions with the /x modifier&lt;/p&gt;
&lt;p&gt;perlre manpage reads:&lt;/p&gt;
&lt;p&gt;/x&lt;br /&gt;
Extend your pattern&#039;s legibility by permitting whitespace and comments.&lt;br /&gt;
These are usually written as ``the /x modifier&#039;&#039;...&lt;/p&gt;
&lt;p&gt;The /x modifier itself needs a little more explanation. It tells the&lt;br /&gt;
regular expression parser to ignore whitespace that is neither&lt;br /&gt;
backslashed nor within a character class. You can use this to break up&lt;br /&gt;
your regular expression into (slightly) more readable parts.&lt;/p&gt;
&lt;p&gt;The # character is also treated as a metacharacter introducing a&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1935&quot; dc:identifier=&quot;http://lopsa.org/node/1935&quot; dc:title=&quot;Turning perl regular expressions from line noise into documented code&quot; trackback:ping=&quot;http://lopsa.org/trackback/1935&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 25 Jun 2010 12:21:36 -0700</pubDate>
 <author>Aleksey Tsalolikhin</author>
</item>
<item>
 <title>Do you run a LUG,sysadmin user group, SAGE or LOPSA chapters?</title>
 <link>http://lopsa.org/node/1930</link>
 <description>&lt;p&gt;LOPSA-NJ has started a mailing list for the people that run technical user groups (LUGs,sysadmin user groups, SAGE or LOPSA chapters, and so on). The purpose of this mailing list is to encourage information sharing on topics such as:&lt;/p&gt;
&lt;p&gt;How to promote your group, how to find speakers, how to get started, tips on how to run a meeting, volunteer retention, and anything else related to the running of such groups. The only forbidden topic is who&#039;s computer/editor/OS/language/whatever is better/worse that mine/yours.&lt;/p&gt;
&lt;p&gt;To be on this list you must be the chair/co-chair/president/board-member or somehow be in charge of organizing a user group with live, in-person meetings (or be involved in starting one).&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1930&quot; dc:identifier=&quot;http://lopsa.org/node/1930&quot; dc:title=&quot;Do you run a LUG,sysadmin user group, SAGE or LOPSA chapters?&quot; trackback:ping=&quot;http://lopsa.org/trackback/1930&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Wed, 09 Jun 2010 06:41:43 -0700</pubDate>
 <author>wbilancio</author>
</item>
<item>
 <title>Notes on Zenoss ZenPacks</title>
 <link>http://lopsa.org/node/1926</link>
 <description>&lt;p&gt;Recently I was building a ZenPack for Zenoss. The ZenPack included an Event Command which executed a custom script. I wanted to store the custom script in the ZenPack and I didn’t want to do anything other than have proper script dependencies in place for it to work. (&lt;a href=&quot;http://www.cmdln.org/2010/05/24/notes-on-zenoss-zenpacks/&quot;&gt;Read More&lt;/a&gt;)&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1926&quot; dc:identifier=&quot;http://lopsa.org/node/1926&quot; dc:title=&quot;Notes on Zenoss ZenPacks&quot; trackback:ping=&quot;http://lopsa.org/trackback/1926&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/28">Applications</category>
 <pubDate>Tue, 25 May 2010 13:19:50 -0700</pubDate>
 <author>nickanderson</author>
</item>
<item>
 <title>trials in LACP</title>
 <link>http://lopsa.org/node/1925</link>
 <description>&lt;p&gt;I need to transfer about 40TB from one zfs box to another box because of a problem of initial setup in box 1 that left it without redundant raid and it now has a failing disk. ZFS points this out quite nicely, but we have to get all that data off before the disk fails completely, even though it&#039;s a backup box. (Apparently you can&#039;t replace a disk in a pure stripe without zfs having conniptions).&lt;/p&gt;
&lt;p&gt;So, what to do? zfs send/recv are a marvelous tool for this, especially combined with a pure network stream like ttcp or netcat or the like. First, start up 20 listening processes on the receiver listening on 20 different ports piped into zfs recv. Second, make a snapshot on all of the filesystems so you have a consistent starting point. zfs snapshot -r zpool1@mig1. Third, send all of these filesystems over in parallel using a quick bash script and incrementing the port number.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1925&quot; dc:identifier=&quot;http://lopsa.org/node/1925&quot; dc:title=&quot;trials in LACP&quot; trackback:ping=&quot;http://lopsa.org/trackback/1925&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Mon, 24 May 2010 19:28:05 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Analyzing I/O performance in Linux</title>
 <link>http://lopsa.org/node/1924</link>
 <description>&lt;p&gt;Monitoring and analyzing performance is an important task for any sysadmin. Disk I/O bottlenecks can bring applications to a crawl. What are IOPS?  Should I use SATA, SAS, or FC? How many spindles do I need? What RAID level should I use? Is my system read or write heavy? These are common questions for anyone embarking on an disk I/O analysis quest. Obligatory disclaimer: I do not consider myself an expert in storage or anything for that mater. This is just how I have done I/O analysis in the past. I welcome additions and corrections. I believe it’s also important to note that this analysis is geared toward random operations than sequential read/write workloads.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1924&quot; dc:identifier=&quot;http://lopsa.org/node/1924&quot; dc:title=&quot;Analyzing I/O performance in Linux&quot; trackback:ping=&quot;http://lopsa.org/trackback/1924&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/155">Performance Tuning</category>
 <pubDate>Mon, 24 May 2010 10:35:44 -0700</pubDate>
 <author>nickanderson</author>
</item>
<item>
 <title>Office 2010 - a preview</title>
 <link>http://lopsa.org/node/1920</link>
 <description>&lt;p&gt;I thought I would write a little about Office 2010. I realize this isn&#039;t about Windows, but Office is important too. I really think that Microsoft messed up the user interface on 2007, and I know a lot of people that feel the same way. Granted, they were looking to improve the user experience, and they primarily had the new user in mind. But what about the literally millions of users that they left behind?&lt;/p&gt;
&lt;p&gt;Well, it looks like the interface has been improved further for 2010. The ribbons are still there, but at least it appears to look a little bit more like the 2003 interface than 2007 did. One aspect of 2010 that really gets me excited is the Office Web piece! This looks like it might be the start of a beautiful friendship between a lot of new users and Microsoft, especially because the web access is free to everyone. It includes the abiliy to store documents online so the user can access them from any computer that has access to the Internet.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1920&quot; dc:identifier=&quot;http://lopsa.org/node/1920&quot; dc:title=&quot;Office 2010 - a preview&quot; trackback:ping=&quot;http://lopsa.org/trackback/1920&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/27">Windows</category>
 <pubDate>Sun, 16 May 2010 22:30:00 -0700</pubDate>
 <author>dglick5</author>
</item>
<item>
 <title>CHIMIT &#039;10 wants your stories from the trenches</title>
 <link>http://lopsa.org/node/1915</link>
 <description>&lt;p&gt;Business, people, and technology:  When we put them together, what works?  What doesn’t?  What explodes?&lt;/p&gt;
&lt;p&gt;ACM CHIMIT &#039;10 - Computer-Human Interaction for Management of Information Technology&lt;br /&gt;
November 12-13, 2010, San Jose, CA (co-located with USENIX LISA, in San Jose)&lt;/p&gt;
&lt;p&gt;IT management is hard – in the enterprise, in small business, and even in the home.  Let’s make it better. CHIMIT &#039;10 will be co-located with LISA in San Jose this November and we would love to hear some of your stories from the trenches.  This is your chance to help us understand what your job is like and how we can help!&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1915&quot; dc:identifier=&quot;http://lopsa.org/node/1915&quot; dc:title=&quot;CHIMIT &#039;10 wants your stories from the trenches&quot; trackback:ping=&quot;http://lopsa.org/trackback/1915&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Mon, 03 May 2010 11:47:11 -0700</pubDate>
 <author>nicolefv</author>
</item>
<item>
 <title>Cool videos about PICC</title>
 <link>http://lopsa.org/node/1913</link>
 <description>&lt;p&gt;I am really excited that I am going to go to PICC (&lt;a href=&quot;http://picconf.org&quot;&gt;http://picconf.org&lt;/a&gt;).  The organizers have put together some great short videos of some of the speakers. I like this one:&lt;/p&gt;
&lt;p&gt;&lt;a href=&quot;http://www.youtube.com/user/lopsavideo#p/u/12/oK4cg7R3_88&quot;&gt;http://www.youtube.com/user/lopsavideo#p/u/12/oK4cg7R3_88&lt;/a&gt;&lt;/p&gt;
&lt;p&gt;Tom Limoncelli interviews Eben Haber, PICC keynote speaker, about his research, his keynote topic, and why he is excited to come to the conference. (PICC is the Professional IT Community Conference May 7-8, 2010, New Brunswick, NJ, USA; &lt;a href=&quot;http://picconf.org&quot;&gt;http://picconf.org&lt;/a&gt;, brought to you by the New Jersey chapter of the League of System Administrators (LOPSA), a non-profit educational organization.)&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1913&quot; dc:identifier=&quot;http://lopsa.org/node/1913&quot; dc:title=&quot;Cool videos about PICC&quot; trackback:ping=&quot;http://lopsa.org/trackback/1913&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Mon, 12 Apr 2010 10:50:47 -0700</pubDate>
 <author>lois</author>
</item>
<item>
 <title>More thoughts on bcfg2</title>
 <link>http://lopsa.org/node/1911</link>
 <description>&lt;p&gt;
In my &lt;a href=&quot;https://lopsa.org/node/1903&quot;&gt;last post&lt;/a&gt; I gave some first impressions using &lt;a href=&quot;http://trac.mcs.anl.gov/projects/bcfg2&quot;&gt;bcfg2&lt;/a&gt;.  We ended up selecting bcfg2 as our configuration management system for a new project.  I&#039;m going to start with the &amp;quot;bad&amp;quot; and get that out of the way.
&lt;/p&gt;
&lt;p&gt;
&lt;h3&gt;The bad&lt;/h3&gt;
The biggest problem so far is getting the entire team up to speed on bcfg2.  It&#039;s very different from what we&#039;re used to with cfengine2.  One challenge is wrapping your mind around what I think is one of the basic tenets of bcfg2 - you specify everything twice.  Let me explain: bcfg2 separates out configurations into an abstract specification, and a concrete implementation.  For example, you may decide a certain group needs an  &lt;em&gt;/etc/motd&lt;/em&gt;file.  So in the abstract configuration (called a Bundle), you simply say: &lt;em&gt;&amp;lt;Path name=&#039;/etc/motd&#039;/&amp;gt;&lt;/em&gt;.  This is great for easily seeing what should be there.  However, it gives no clue as to where that file comes from.  It could come from the plugin that distributes static files, or one of the plugins that parses templates and distributes the results.
&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1911&quot; dc:identifier=&quot;http://lopsa.org/node/1911&quot; dc:title=&quot;More thoughts on bcfg2&quot; trackback:ping=&quot;http://lopsa.org/trackback/1911&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/26">Linux</category>
 <pubDate>Wed, 31 Mar 2010 19:04:31 -0700</pubDate>
 <author>jlothian</author>
</item>
</channel>
</rss>
