Skip to main content

PXE boot on a home network

I have several home routers which I tend to swap around as I need various services or features. But now comes the hardest of all. I work from home and while I use different virtual servers, digital ocean(DO), google compute engine(GCE), amazon web services(AWS); the problem is that in order to enable enough headroom in my compute instances requires considerable cash outlay. On the other hand when you consider capital outlay, depreciation, sound polution, and the cost of residential power running my own hardware may not be an ideal option. (there is something to be said about lights out operations and continuous deployment from the outset).

Jumping into things... my Dell C6100 does not boot to USB or iPXE. It only supports PXE. Now that I've forked a CoreOS PXE installer project, upgraded it to the latest CoreOS image and fixed a few bugs I'm ready to test PXE booting a raw VM image.

Trying to PXE boot a VMware instance using a PXE server running on another VMware instance means that the instances need to be (i) bridged to the network so that the services are not hiding behind a NAT. But it also means that there can be (ii) only one DHCP server in the network. I'm not certain how the PXE client locates a DHCP server but it's probably something like UDP or port scanning. In either case my client is not locating the right DHCP server. (and a google search resulted in similar findings)

** I suppose I should mention that the machine in question is a Dell C6100 and when all 4 nodes are running a production workload they are working at 962 watts. Depending on the actual cost of electricity it could be between $400 and $1100 a year. Plus the original cost of the hardware.

Considering how much effort has already been put into this endeavor I think the project should be cancelled and look for a VPS bargain instead.

Ooops; I forgot to mention that my C6100 includes 96GB or memory. Just matching the memory needs with Digital Ocean at a cost of $1000/mo. Maybe it's a bargain to run these from home after all.

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…