Skip to main content

Observations - VPS hosting and the aftermarket

I just purchased a Dell C6100 for $300 including shipping and as I was sitting around this morning thinking about how I was going to handle the IPMI password problem I started to ask myself about why there were no drives included in the purchase. DUH! The machines were likely part of an end of life purge at some VPS. According to the seller they have sold hundreds of machines so I wondered where they sourced the machines that they could sell them for so cheap; considering that they had to have some markup to make money.
"hundreds" of machines probably means that they sourced the machines at Peer1 or maybe Rackspace. They would not be sourcing from Google because they design their own machines.
As I was considering my purchase I recall a conversation with a coworker. I was against the purchase for production because we have a lightsout operation and frequent hardware failures would only increase our costs. If "we" were willing to give up our free time to repair used systems then we might be better of directing that time a revenue opportunities instead.

Well, I'm looking forward to my new arrival. 4 systems in a 2U rackmount with rails and 96GB ram. In all I should be able to build out my system fairly easily although I'm just a little concerned about the noise from the fans. Given the price I should be able to cut the expense of my Google Compute and Digital Ocean instances. In fact the savings could let me install a second network in the house for a little redundancy and speed.

In all, just on the cost savings alone (a) I could host myself (b) buy enough backup hardware for those eventual failures.

Popular posts from this blog

Prometheus vs Bosun

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


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…