Herding cats in the Cloud

I gave my "Herding Cats..." talk at the 2017 New England VTUG Winter Warmer.

The talk covers technical, social and organizational issues for fast, agile development at large scale (~1k machines, 10ks of TPS, ~500TB transfer) in a cloud environment.

See the slides on SlideShare.net.

In conjunction with this talk I was interviewed by Silicon Angle for theCube. See the segment here.


Project: Makessl

Makessl is a Makefile for GNU make that assists you in generating SSL keys, certificate requests, and (optionally) certificates.

Using it is as simple as:

 git clone https://github.com/deweysasser/makessl
 cd makessl
 vi ssl-data.txt # set the certificate data to your own information
 mkdir -p hosts/www.example.com

The result is that an RSA key and certificate request will be left in that subdirectory. If, instead of 'make', you use:

Simple S3 Backup script

Announcing availability of a simple program to backup the output of commands to Amazon S3 storage.

Sane branch naming conventions in GIT

The Problem: The state of the branch

I need to be able to glance over a repo and determine exactly what is ready to go and what it does.

I work on a lot of different projects, and will leave a project in an intermediate state for a long time. I also, alas, have projects for which I'm managing multiple release streams. There isn't just a "next" release, there is a "next release on the 5.4 branch", "next release on the 5.5 branch", etc.

Thoughts on running software

I'm partially on operations guy, so, net result, I'm responsible making software run. What exactly does this mean?

Here's the minimum set:

  • RUN: Arrange for it to run
  • MONITOR: How do I find out if it stops running?
  • PUBLISH: Make it available to the people who need it
  • ADVERTISE: And make sure those people know about it.

Other things I might want to do depend on the quality of job I want to do (a.k.a. "Service Level Agreement" or SLA)

Introducing docker-xymon

In short: build and deploy this for instant monitoring.

Seeing no viable containerization of the Xymon monitoring system (and the 'net is large -- I could have missed it), I have created some.

Eventually I will be maintaining images on the Docker Hub as well as the source.

For now, get it from https://github.com/deweysasser/docker-xymon

Here's the README...

Changing Username on technical social sites

I'm getting into Docker, and have recently registered "deweysasser" as my docker hub username. Neither my Github username nor my Twitter handle match this, so it's time to refactor handles.

Wherever possible I'm going to move to "DeweySasser". Most of these services have some migration capability, so links, following, etc should automatically update. If not, please update your bookmarks, etc.

Current usernames (this will be kept up to date):

  • github: dmsasser
  • twitter: DeweyS
  • StackExchange: dmsasser

Notes and Summary from DevOps Days Boston 2014

These are my notes from DevOps Days Boston in 2014. See the section entitled "Dewey's Summary" for, well, just that. The rest is pretty much raw notes.

I'm not expecting this page to be generally useful to the public but want to share it with some specific people. If it is generally useful, bonus!

GIT for SVN users: A simple Github workflow with multiple repositories

This is one article in my series on GIT for SVN users. See the introduction.

One of the inherent assumptions in the SVN world is "the" repository. "The" repository is the place from where you check out, from where you update, to where you commit.

GIT for SVN users: An introduction

This is part of a series of posts about GIT for people with an SVN background. If you're an experienced GIT user, my series of "GIT for SVN users" is likely not going to be useful (other GIT articles might be -- you'll have to make that call).


Subscribe to DeweySasser.com RSS