index.xml

<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Fewbytes on The Fewbytes legacy</title><link>https://www.fewbytes.com/</link><description>Recent content in Fewbytes on The Fewbytes legacy</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Thu, 09 Jul 2020 09:32:17 +0300</lastBuildDate><atom:link href="https://www.fewbytes.com/index.xml" rel="self" type="application/rss+xml"/><item><title>The Problem With Configurations</title><link>https://www.fewbytes.com/the-problem-with-configurations/</link><pubDate>Sat, 13 Jun 2015 11:34:02 +0300</pubDate><guid>https://www.fewbytes.com/the-problem-with-configurations/</guid><description>&lt;p>&lt;em>Originally published in &lt;a href="http://www.netocratic.com/devops-the-problem-with-configurations-89297">Netocratic&lt;/a>&lt;/em>&lt;/p>
&lt;p>&lt;strong>Configuration&lt;/strong> is one of those things we usually take for granted. Yet, as more and more configurations are added the use of configurations becomes hard and complicated. With enough configuration parameters, keeping track of what the current configuration “is” can be quite problematic. Often, people misconfigure systems due to various reasons such as poor documentation or unexpected interactions between different parameters. Sometimes, the configuration itself can be complex and requires a language to express it, raising the bar of required knowledge for defining the configuration. Despite the “boring” nature of configurations they can and do &lt;a href="http://dealbook.nytimes.com/2012/08/02/knight-capital-says-trading-mishap-cost-it-440-million">obliterate entire companies in matter of hours&lt;/a>.&lt;/p></description></item><item><title>Docker, SELinux and the myth of kernel independence</title><link>https://www.fewbytes.com/docker-selinux-and-the-myth-of-kernel-independence/</link><pubDate>Fri, 21 Nov 2014 17:05:12 +0200</pubDate><guid>https://www.fewbytes.com/docker-selinux-and-the-myth-of-kernel-independence/</guid><description>Recently I built docker images for omnibus builds. Omnibus packages must be built on the target distro so I needed images for centos, debian and ubuntu. Usually I build such docker images on my laptop which is running Ubuntu; I try to make the builds as repeatable as possible using the excellent packer tool and when I publish images I build them again (using a build server) on cloud instances. In this case, I was using GCE CentOS 7 instance to perform the build and I was surprised when a build that was smooth on my laptop failed miserably.</description></item><item><title>OpsTalk Meetup #7 - Riemann workshop</title><link>https://www.fewbytes.com/opstalk-meetup-7-riemann-workshop/</link><pubDate>Wed, 12 Feb 2014 14:01:55 +0200</pubDate><guid>https://www.fewbytes.com/opstalk-meetup-7-riemann-workshop/</guid><description>Opstalk 7th monthly meetup is getting close, this time we&amp;rsquo;re going to have a Riemann workshop
The meetup is due to take place on Thursday, March 13, 2014
For more info &amp;amp; RSVP please visit the meetup&amp;rsquo;s page</description></item><item><title>Thoughts about configuration management</title><link>https://www.fewbytes.com/thoughts-about-configuration-management/</link><pubDate>Wed, 12 Feb 2014 09:56:48 +0200</pubDate><guid>https://www.fewbytes.com/thoughts-about-configuration-management/</guid><description>Current configuration management tools solve a huge problem, providing a way to place repeatable, eventually coordinated application and server setup on large scale environments.
Although we have come a long way since handcrafting our servers, even with Chef or Puppet, I still feel like we’re chasing our tails.
Virtual Human Before we had configurable software, we needed to edit a few source files or headers, change a few constants and recompile.</description></item><item><title>Using S3 as a cookbook store backend for chef-server 11</title><link>https://www.fewbytes.com/using-s3-as-a-cookbook-store-backend-for-chef-server-11/</link><pubDate>Fri, 25 Oct 2013 09:48:53 +0300</pubDate><guid>https://www.fewbytes.com/using-s3-as-a-cookbook-store-backend-for-chef-server-11/</guid><description>chef-server is a modular service - various tasks are delegated to different sub-services, one of which is Bookshelf, Chef&amp;rsquo;s cookbook store in charge of storing and serving cookbook files. Bookshelf&amp;rsquo;s API is S3 compatible by design (I can only assume Opscode are using S3 for their SAAS) and can be replaced with S3. Using S3 as the backend store makes sense for clustering, but there&amp;rsquo;s very little information on the web on how to configure chef-server to use it.</description></item><item><title>Autonomation in web systems</title><link>https://www.fewbytes.com/autonomation-in-web-systems/</link><pubDate>Sat, 25 May 2013 17:25:40 +0300</pubDate><guid>https://www.fewbytes.com/autonomation-in-web-systems/</guid><description>Yes, I got the spelling right. Autonomation is a manufacturing methodology originally developed by Toyota (part of the famed Toyota Production System). The idea is sort of like this: you have a machine on a production line; this machine is supervised by a human and is feeding its output to some other machine down the line. Occasionally something goes wrong, perhaps a defective product by the machine. The machine stops itself immediately and the human will fix/change the machine (not the product, the machine!</description></item><item><title>Using include_recipe in Chef LWRP</title><link>https://www.fewbytes.com/using-includerecipe-in-chef-lwrp/</link><pubDate>Fri, 10 May 2013 16:13:33 +0300</pubDate><guid>https://www.fewbytes.com/using-includerecipe-in-chef-lwrp/</guid><description>A big part of Chef&amp;rsquo;s resources internal nuts and bolts has been change over the last year. One of the most welcome changes has been recipe_eval - a mini Chef run that can be used inside Chef LWRP. This mechanism has been put to good use in use_inline_resources dsl directive in LWRP, in chef-stage and in inline_recipe.
Now that LWRPs have become so powerful, there aren&amp;rsquo;t many reasons to use definitions.</description></item><item><title>How to prevent Continuous Deployment from turning into a Continuous Disaster</title><link>https://www.fewbytes.com/how-to-prevent-continuous-deployment-from-turning-into-a-continuous-disaster/</link><pubDate>Sat, 13 Apr 2013 15:45:50 +0300</pubDate><guid>https://www.fewbytes.com/how-to-prevent-continuous-deployment-from-turning-into-a-continuous-disaster/</guid><description>These days, one the of most frequent request we hear from clients is setting up continuous deployment. Every company wants it, every DevOps related conference has sessions about it. However, newcomers tend to miss one of the key points of CI/CD – it really isn’t an automation problem, it’s a cultural problem. From a pure technical perspective implementing a build-deploy pipeline is fairly simple with current tools and this has been the case for several years.</description></item><item><title>IT is NOT ops</title><link>https://www.fewbytes.com/it-is-not-ops/</link><pubDate>Tue, 12 Feb 2013 15:06:49 +0200</pubDate><guid>https://www.fewbytes.com/it-is-not-ops/</guid><description>At the end of DevopsCon I participated in a panel discussing the future of Ops and DevOps. One thread of discussion at that panel followed a statement by Ben Kepes which basically amounted to &amp;ldquo;in the future, there won&amp;rsquo;t be any IT Ops guys anymore&amp;rdquo; (I can&amp;rsquo;t remember the exact wording, apologies). I was very disturbed by that statement; not because of fear for my profession, but rather because of the lack of dismay in the crowd.</description></item><item><title>Cronic Disease</title><link>https://www.fewbytes.com/cronic-disease/</link><pubDate>Tue, 27 Nov 2012 14:26:20 +0200</pubDate><guid>https://www.fewbytes.com/cronic-disease/</guid><description>There’s no denying Cron is one of the most useful tools in any *nix O/S but it&amp;rsquo;s Every so often, there’s a cron job going haywire. Jobs fail to run and nobody notices, the sterile environment (no sane default PATH) eludes users and from time to time, a really bizarre critical issue - like cron filling up the disk with its mail output buffer because a job is looping and spewing an endless stream of error messages.</description></item></channel></rss>