Skip to main content

Hashicorp Packer; is it a waste of time and money?

I'm lazy. There, I've said it. It's that laziness that prevents me from creating "things" with layers of complexity and simplicity. I simply want to GST (get sh*t done) in the fewest keystrokes, lines of code, and features. All those things are nice to have but in all honestly get some revenue first. Paying customers with feature requests is better than no customers burning through investment.
I recall in one environment we talked about HA replication and scaling to 10s-100s of servers. That was a nice exercise, however, we always said "transaction volume would be a different class of problem to solve". Sadly it never happened and we never grew past a single deployment and all of that DB and security replication cost money to develop and test... and worse support in production. And those features never generated a single extra dollar in revenue.
So what does Packer get you? Frankly I'm not sure. They support a number of different targets but all of them require customization. I'm not sure you get real scale there when you later start adding chef, puppet or ansible. The layers and costs just continue to mount.

Bootstrapping an environment is a common function. It usually means that there is a source code repository some place with at least one script that can initiate the full deployment. Sometimes this bootstrap system is transient and sometimes it's permanent. It does depend on the operating rules. But one thing for certain is that there are certain challenges when you are looking at recursion... you cannot bootstrap a git server if the code you need is in the git server. That's why I believe in the simplest system possible.

My simple solution is a matter of putting my general purpose tools in a public repo like gitlab, github, etc. I'll clone that code onto my bootstrap system.
to regress for a moment, my bootstrap system is either a simple dedicated guest or some other system that resides inside the target network. This resource has access to the tools and the ability to run them. That could include docker, docker-machine, some credentials.
At this point I have private script that can deploy an admin console. Once  the admin console is created all of the clusters config scripts are loaded and deployed. Currently I'm using docker swarm with some minor k8s and k3s implementations. Once the cluster is ready it's just matter of deploying apps and services. That in itself is just a matter of launching some docker stack or service commands. None of which requires packer, chef, etc... just simple shell commands. Once deployed normal orchestration applies.

Simply put you already need a Dockerfile and in some cases some sort of a compose file... now adding layers of configuration as code called packer is a waste.

Comments

Popular posts from this blog

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.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: http://www.eeti.com.tw/drivers_Linux.html (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the setup.sh answer all of the questio…

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…