<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Pets on Mark&#39;s Blog</title>
    <link>https://mark.lavi.us/tags/pets/</link>
    <description>Recent content in Pets on Mark&#39;s Blog</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>This work is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.</copyright>
    <lastBuildDate>Tue, 30 Aug 2022 11:03:38 -0500</lastBuildDate>
    <atom:link href="https://mark.lavi.us/tags/pets/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Learning AlpineLinux.org, Ansible.com, and Packer.io</title>
      <link>https://mark.lavi.us/post/learning-alpine-linux-ansible-and-packer/</link>
      <pubDate>Tue, 26 Jan 2021 09:37:33 -0600</pubDate>
      <guid>https://mark.lavi.us/post/learning-alpine-linux-ansible-and-packer/</guid>
      <description>&lt;p&gt;For my 2020-1 holiday break, I decided my next personal project would be to rebuild my home infrastructure on containers. I&amp;rsquo;d been inspired by a recent discovery of &lt;a href=&#34;https://linuxserver.io&#34;&gt;LinuxServer.io&lt;/a&gt;, where open source projects are built and run as containers. While I have a burning desire to better my Kubernetes practice, not enough of the world delivers software as a Helm chart, so merely running everything as containers would be a good intermediate step. Let me share my first six steps with examples&amp;hellip;&lt;/p&gt;</description>
    </item>
    <item>
      <title>Ten Steps from Pets to Cattle</title>
      <link>https://mark.lavi.us/post/ten_steps_from_pets_to_cattle/</link>
      <pubDate>Wed, 25 Jan 2017 11:05:13 -0700</pubDate>
      <guid>https://mark.lavi.us/post/ten_steps_from_pets_to_cattle/</guid>
      <description>&lt;p&gt;Why do we need DevOps when IT and Operations succeed in their responsibility&#xA;for security and uptime, using administrative tools to maintain, backup, patch, and&#xA;restore those systems achieving a &amp;ldquo;keep the lights on&amp;rdquo; goal? Because the operations domain must be documented,&#xA;democratized, and distributed to achieve agility so Operations returns&#xA;to become a business force multiplier.&#xA;Let me demonstrate that traditional values for long lived infrastructure and&#xA;their retroactive justification do not apply when progressing to a DevOps&#xA;mindset.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
