<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Automation on dobriak::blog</title>
    <link>https://dobriak.github.io/categories/automation/</link>
    <description>Recent content in Automation on dobriak::blog</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 30 Apr 2018 09:39:03 -0700</lastBuildDate>
    
	<atom:link href="https://dobriak.github.io/categories/automation/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Autoscaling Reporter</title>
      <link>https://dobriak.github.io/post/autoscaling-reporter/</link>
      <pubDate>Mon, 30 Apr 2018 09:39:03 -0700</pubDate>
      
      <guid>https://dobriak.github.io/post/autoscaling-reporter/</guid>
      <description>&lt;p&gt;I frequently get asked about utilizing AWS CloudWatch metrics collecting abilities to autoscale DC/OS EE clusters. Usually people figure out quickly how to use the AWS built in metrics (for example CPU utilization) but are not completely sure how they can start emitting their own, custom ones and use those instead.&lt;/p&gt;

&lt;p&gt;In this article, I will help you set up a simple Marathon app that will do just that for us: forward some DC/OS built-in metrics and even create and push a custom one.&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>DC/OS Service Accounts in Restricted Environments</title>
      <link>https://dobriak.github.io/post/service-account-restricted-environment/</link>
      <pubDate>Sun, 29 Apr 2018 15:44:45 -0700</pubDate>
      
      <guid>https://dobriak.github.io/post/service-account-restricted-environment/</guid>
      <description>&lt;p&gt;We are so used to having handy little pieces of software that help us do our jobs better. If you too work in the DevOps world and write automation for infrastructure or software (or pretty much anything else) you know what I mean. Take &lt;code&gt;jq&lt;/code&gt; for an example: can you imagine writing any sort of shell script that interacts with any JSON producing API and &lt;em&gt;NOT&lt;/em&gt; using good ole trustworthy &lt;code&gt;jq&lt;/code&gt;?&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>DC/OS on KVM CoreOS VMs</title>
      <link>https://dobriak.github.io/post/kvm-coreos-dcos/</link>
      <pubDate>Sat, 28 Oct 2017 13:29:29 -0700</pubDate>
      
      <guid>https://dobriak.github.io/post/kvm-coreos-dcos/</guid>
      <description>&lt;p&gt;In this article we will automate the DC/OS installation procedure specifically for CoreOS VMs running on KVM (libvirt).&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Compiling Local DC/OS Universe</title>
      <link>https://dobriak.github.io/post/compiling-local-universe/</link>
      <pubDate>Sat, 27 May 2017 00:51:14 -0700</pubDate>
      
      <guid>https://dobriak.github.io/post/compiling-local-universe/</guid>
      <description>&lt;p&gt;DC/OS offers its users the ability to install various frameworks with a single click from a central publicly hosted package repository called Universe.&lt;/p&gt;

&lt;p&gt;Many Mesosphere clients run their DC/OS clusters in air-gapped environments with no access to the internet, thus not allowing for said one click installation of framework packages.&lt;/p&gt;

&lt;p&gt;You can easily solve this problem if your DC/OS cluster is running in such a restricted environment.&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Automating advanced DC/OS installation.</title>
      <link>https://dobriak.github.io/post/automated-advanced-dcos-installation/</link>
      <pubDate>Thu, 27 Apr 2017 20:23:50 -0700</pubDate>
      
      <guid>https://dobriak.github.io/post/automated-advanced-dcos-installation/</guid>
      <description>&lt;p&gt;In this article we will look at automating the advanced DC/OS installation procedure. We will break down the requirements and look for opportunities to speed up the lengthy installation.&lt;/p&gt;

&lt;p&gt;&lt;/p&gt;</description>
    </item>
    
  </channel>
</rss>