<?xml version="1.0" encoding="UTF-8"?><feed
	xmlns="http://www.w3.org/2005/Atom"
	xmlns:thr="http://purl.org/syndication/thread/1.0"
	xml:lang="en-US"
	
	xmlns:georss="http://www.georss.org/georss"
	xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#"
	>
	<title type="text">Ramblings</title>
	<subtitle type="text">Musings of Matt Williams</subtitle>

	<updated>2016-09-01T01:07:25Z</updated>

	<link rel="alternate" type="text/html" href="http://matthewkwilliams.com" />
	<id>http://matthewkwilliams.com/index.php/feed/atom/</id>
	<link rel="self" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/feed/atom/" />

	<generator uri="https://wordpress.org/" version="6.9.4">WordPress</generator>
	<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Weaving with Light Pt. 1]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/08/31/weaving-with-light-pt-1/" />

		<id>http://matthewkwilliams.com/?p=1317</id>
		<updated>2016-09-01T01:07:25Z</updated>
		<published>2016-09-01T01:07:25Z</published>
		<category scheme="http://matthewkwilliams.com" term="cosplay" /><category scheme="http://matthewkwilliams.com" term="electronics" /><category scheme="http://matthewkwilliams.com" term="hardware" /><category scheme="http://matthewkwilliams.com" term="textiles" /><category scheme="http://matthewkwilliams.com" term="weaving" />
		<summary type="html"><![CDATA[This is the first in a series of posts regarding a recent project which integrated handweaving, fiber optics, and electronics. It&#8217;s a part of a costume for a cosplayer at work, but I&#8217;ll be discussing my part of it. TL;DR For those who can&#8217;t wait, here&#8217;s what the project looks like in the dark: And &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/08/31/weaving-with-light-pt-1/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/08/31/weaving-with-light-pt-1/#comments" thr:count="0" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/08/31/weaving-with-light-pt-1/feed/atom/" thr:count="0" />
			<thr:total>0</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Abusing HAProxy: Stupid Simple Easy Dashboards]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/06/24/abusing-haproxy-stupid-simple-easy-dashboards/" />

		<id>http://matthewkwilliams.com/?p=1312</id>
		<updated>2016-06-24T20:35:04Z</updated>
		<published>2016-06-24T20:35:04Z</published>
		<category scheme="http://matthewkwilliams.com" term="devops" /><category scheme="http://matthewkwilliams.com" term="Docker" /><category scheme="http://matthewkwilliams.com" term="hack" /><category scheme="http://matthewkwilliams.com" term="infrastructure" /><category scheme="http://matthewkwilliams.com" term="monitoring" />
		<summary type="html"><![CDATA[I wanted a simple way to have a dashboard to show if hosts and services are alive &#38; didn&#8217;t want to write much code and/or run up a nagios instance (or anything like that). All I care is whether it&#8217;s green or red. I&#8217;d already been setting up HAProxy for a proxy forwarder, so I &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/06/24/abusing-haproxy-stupid-simple-easy-dashboards/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/06/24/abusing-haproxy-stupid-simple-easy-dashboards/#comments" thr:count="0" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/06/24/abusing-haproxy-stupid-simple-easy-dashboards/feed/atom/" thr:count="0" />
			<thr:total>0</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Rules for Operations]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/25/rules-for-operations/" />

		<id>http://matthewkwilliams.com/?p=1289</id>
		<updated>2016-04-25T01:59:09Z</updated>
		<published>2016-04-25T12:00:46Z</published>
		<category scheme="http://matthewkwilliams.com" term="devops" /><category scheme="http://matthewkwilliams.com" term="infrastructure" /><category scheme="http://matthewkwilliams.com" term="monitoring" /><category scheme="http://matthewkwilliams.com" term="philosophy" />
		<summary type="html"><![CDATA[The following list was compiled in 2012 for a talk on Operations Principles for Developers (Ops4Devs). They are loosely inspired by the list of rules from Zombieland as well as from my experiences and those shared by others. Looking over the list four years later, I believe that they are still (very) applicable for all &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/04/25/rules-for-operations/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/25/rules-for-operations/#comments" thr:count="3" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/04/25/rules-for-operations/feed/atom/" thr:count="3" />
			<thr:total>3</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[DevOps Creed (Work in Progress)]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/24/devops-creed-work-in-progress/" />

		<id>http://matthewkwilliams.com/?p=1293</id>
		<updated>2016-04-25T02:36:43Z</updated>
		<published>2016-04-25T02:36:43Z</published>
		<category scheme="http://matthewkwilliams.com" term="devops" /><category scheme="http://matthewkwilliams.com" term="disaster recovery" /><category scheme="http://matthewkwilliams.com" term="philosophy" />
		<summary type="html"><![CDATA[This is a work in progress of a DevOps Creed. It will always be a work in progress as I and others learn and grow. Suggestions are welcome! I have drunk deep of the DevOps Kool-Aid. From the visions which ensued, I have come to the following&#8230;. I Believe: DevOps methodologies lead to systems which &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/04/24/devops-creed-work-in-progress/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/24/devops-creed-work-in-progress/#comments" thr:count="0" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/04/24/devops-creed-work-in-progress/feed/atom/" thr:count="0" />
			<thr:total>0</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[I am not a Mindreader: a mini-saga]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/11/i-am-not-a-mindreader-a-mini-saga/" />

		<id>http://matthewkwilliams.com/?p=1283</id>
		<updated>2016-04-11T19:58:29Z</updated>
		<published>2016-04-11T19:58:29Z</published>
		<category scheme="http://matthewkwilliams.com" term="mini sagas" /><category scheme="http://matthewkwilliams.com" term="rants" />
		<summary type="html"><![CDATA[I must confess a severe failing on my part. I am not a mindreader. I am not privy to the thoughts in your head. I do not know your needs or desires. And I am certainly not aware of your expectations. This is why requirement documents exist. Please use them.]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/11/i-am-not-a-mindreader-a-mini-saga/#comments" thr:count="3" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/04/11/i-am-not-a-mindreader-a-mini-saga/feed/atom/" thr:count="3" />
			<thr:total>3</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Cloudera Manager Disaster Recovery with JSON Deployment Dump]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/07/cloudera-manager-disaster-recovery-with-json-deployment-dump/" />

		<id>http://matthewkwilliams.com/?p=1276</id>
		<updated>2016-04-07T12:20:23Z</updated>
		<published>2016-04-07T12:00:07Z</published>
		<category scheme="http://matthewkwilliams.com" term="cloudera manager" /><category scheme="http://matthewkwilliams.com" term="disaster recovery" /><category scheme="http://matthewkwilliams.com" term="gotchas" />
		<summary type="html"><![CDATA[Cloudera Manager is fairly opinionated. In its defence, it pretty much needs to be given that it needs to wrangle multiple underlying Open Source projects. Each of these, in turn, have their own quirks and opinions. The following is a description of how to recover a Cloudera Manager cluster post disaster, assuming that you have &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/04/07/cloudera-manager-disaster-recovery-with-json-deployment-dump/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/04/07/cloudera-manager-disaster-recovery-with-json-deployment-dump/#comments" thr:count="0" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/04/07/cloudera-manager-disaster-recovery-with-json-deployment-dump/feed/atom/" thr:count="0" />
			<thr:total>0</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Interesting Feature of Dockerfile Volume Directives]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/30/interesting-feature-of-dockerfile-volumes/" />

		<id>http://matthewkwilliams.com/?p=1273</id>
		<updated>2016-03-30T17:00:38Z</updated>
		<published>2016-03-30T17:00:38Z</published>
		<category scheme="http://matthewkwilliams.com" term="cloudera" /><category scheme="http://matthewkwilliams.com" term="cloudera manager" /><category scheme="http://matthewkwilliams.com" term="Docker" /><category scheme="http://matthewkwilliams.com" term="gotchas" /><category scheme="http://matthewkwilliams.com" term="hadoop" />
		<summary type="html"><![CDATA[I&#8217;ve been rewriting a cleanroom version of the hadoop-in-a-box &#8212; just about finished. And, truth be told, the code, all in all, is a bit tighter than the original encumbered version. However, I ran into an interesting feature of Volumes &#8212; I had thought perhaps to optimize things a bit, but it caused some unexpected &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/03/30/interesting-feature-of-dockerfile-volumes/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/30/interesting-feature-of-dockerfile-volumes/#comments" thr:count="1" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/03/30/interesting-feature-of-dockerfile-volumes/feed/atom/" thr:count="1" />
			<thr:total>1</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Docker, Cgroups, Memory Constraints, and Java: A  Cautionary Tale, or Here be Reapers (sometimes)]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/17/docker-cgroups-memory-constraints-and-java-cautionary-tale/" />

		<id>http://matthewkwilliams.com/?p=1260</id>
		<updated>2016-03-17T02:54:54Z</updated>
		<published>2016-03-17T12:00:02Z</published>
		<category scheme="http://matthewkwilliams.com" term="Docker" /><category scheme="http://matthewkwilliams.com" term="Experiments" /><category scheme="http://matthewkwilliams.com" term="gotchas" /><category scheme="http://matthewkwilliams.com" term="Java" /><category scheme="http://matthewkwilliams.com" term="JVM" /><category scheme="http://matthewkwilliams.com" term="linux" />
		<summary type="html"><![CDATA[TL;DR: Java and cgroups/Docker memory constraints don&#8217;t always behave as you might expect. Always explicitly specify JVM heap sizes. Also be aware that kernel features may not be enabled. And Linux&#8230; lies. I&#8217;ve recently discovered an interesting &#8220;quirk&#8221; in potential interactions between Java, cgroups, Docker, and the kernel which can cause some surprising results. Unless &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/03/17/docker-cgroups-memory-constraints-and-java-cautionary-tale/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/17/docker-cgroups-memory-constraints-and-java-cautionary-tale/#comments" thr:count="9" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/03/17/docker-cgroups-memory-constraints-and-java-cautionary-tale/feed/atom/" thr:count="9" />
			<thr:total>9</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Zombie Apocalypse! Docker AUFS + Java + Low Memory &#8230;. Hadoop in a Box Cloudera Manager Cluster]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/15/zombie_apocalypse/" />

		<id>http://matthewkwilliams.com/?p=1236</id>
		<updated>2016-03-15T19:35:10Z</updated>
		<published>2016-03-15T19:34:07Z</published>
		<category scheme="http://matthewkwilliams.com" term="cloudera manager" /><category scheme="http://matthewkwilliams.com" term="Docker" /><category scheme="http://matthewkwilliams.com" term="gotchas" /><category scheme="http://matthewkwilliams.com" term="howto" /><category scheme="http://matthewkwilliams.com" term="Java" /><category scheme="http://matthewkwilliams.com" term="troubleshooting" /><category scheme="http://matthewkwilliams.com" term="Uncategorized" />
		<summary type="html"><![CDATA[TL;DR &#8212; When using AUFS in a memory constrained environment, Java can spawn (lots!) of Zombies. A workaround is to change the storage driver to the device mapper. In working on the Hadoop in a box CDH cluster with Cloudera Manager, I&#8217;ve discovered a few interesting things about AUFS. These experiences are with Ubuntu 14.04 &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/03/15/zombie_apocalypse/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/15/zombie_apocalypse/#comments" thr:count="0" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/03/15/zombie_apocalypse/feed/atom/" thr:count="0" />
			<thr:total>0</thr:total>
			</entry>
		<entry>
		<author>
			<name>Matt Williams</name>
							<uri>http://matt@matthewkwilliams.com</uri>
						</author>

		<title type="html"><![CDATA[Cloudera Manager GUI and API Can Step on Each Other]]></title>
		<link rel="alternate" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/10/cloudera-manager-gui-and-api-can-step-on-each-other/" />

		<id>http://matthewkwilliams.com/?p=1243</id>
		<updated>2016-03-10T16:19:57Z</updated>
		<published>2016-03-10T16:19:57Z</published>
		<category scheme="http://matthewkwilliams.com" term="cloudera manager" /><category scheme="http://matthewkwilliams.com" term="gotchas" />
		<summary type="html"><![CDATA[While learning how the configuration worked &#8212; in particular which arguments to pass in order to set non-default values, I discovered that I could lose changes by following these steps: Use the GUI to set a value and save it. This is just so that you can find the variable. Keep the GUI open. Dump &#8230; </p><p><a class="more-link block-button" href="http://matthewkwilliams.com/index.php/2016/03/10/cloudera-manager-gui-and-api-can-step-on-each-other/">Continue reading &#187;</a>]]></summary>

		
					<link rel="replies" type="text/html" href="http://matthewkwilliams.com/index.php/2016/03/10/cloudera-manager-gui-and-api-can-step-on-each-other/#comments" thr:count="0" />
			<link rel="replies" type="application/atom+xml" href="http://matthewkwilliams.com/index.php/2016/03/10/cloudera-manager-gui-and-api-can-step-on-each-other/feed/atom/" thr:count="0" />
			<thr:total>0</thr:total>
			</entry>
	</feed>
