Skip to main content

Cloud lessons I'm still learning

EVENT: I have a single Rackspace instance that I'm using for a client of mine. The machine was intended to host multiple projects and clients but I never tried very hard and so my client is only paying me about 50% of the VPS cost alone.

LESSON: margins should never be less than 50-100% of cost.

EVENT: That same machine is in a zone that Rackspace has designated end of life. At some point they are going to turn it off or migrate it for me.

LESSON: projects or customers that do not generate enough raw revenue need better margins so there is incentive to maintain them. Regardless of the actual code complexity there is a basic devops cost per application and machine and user... etc.

EVENT: Moving bulk VMs from vendor to vendor or datacenter to datacenter is not without risk. I had 3 VMs in Google's compute engine. While the service is nice and pretty reasonable it's better than having to drive into a COLO in order to reboot a machine. The Risk is that these VMs are too easy to delete. I moved my development environment from GCE to an in-house server. Now that things are working nicely, in-house, it's time to decommission the GCE device. I deleted the wrong machine. The machine names I selected were DEVBOX, PCORE1, PCORE3.... I deleted PCORE3 when I had meant to delete DEVBOX.

LESSON1: completely separate prod from dev. Name the machines better. find a way to put a token inside the filesystem of the target machine that can act like a LOCK such that a delete script might have to see the token before deleting the environment. I'm not saying what happens when you have 100's of machines; just a few.

LESSON2: use a script to delete the VM, but the script should take a snapshot of the environment first. This way you can be assured that target is, in fact, the right one.

NOTE: containers might be the way to go, however, while this might protect the VM it's not going to protect the container and especially the data volume container.

Popular posts from this blog

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).

TL;DR;

I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

Weave vs Flannel

While Weave and Flannel have some features in common weave includes DNS for service discovery and a wrapper process for capturing that info. In order to get some parity you'd need to add a DNS service like SkyDNS and then write your own script to weave the two together.
In Weave your fleet file might have some of this:
[Service] . . . ExecStartPre=/opt/bin/weave run --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
In sky + flannel it might look like:
[Service] . . . ExecStartPre=docker run -d --net=host --name bob ncx/bob ExecStartPre=etcdctl set /skydns/local/ncx/bob '{"host":"`docker inspect --format '{{ .NetworkSettings.IPAddress }}' bob`","port":8080}' ExecStart=/usr/bin/docker attach bob
I'd like it to look like this:
[Service] . . . ExecStartPre=skyrun --net=host --name bob ncx/bob ExecStart=/usr/bin/docker attach bob
That's the intent anyway. I'm not sure the exact commands will work and that's partly why we…