Skip to main content

how to pick a docker stack name?

I'm working on a very small project that is meant to demonstrate a small web application (not a service) so I can get all the moving parts together and at some point I might be able to script project scaffolding creation. But one thing I have been facing is that the target URLs lose meaning/context; there is still plenty of manual cleanup; while I liked the k8s mode of using the uuid or branch name to deploy a dev instance there is a bunch of leftover topic.

This is a docker swarm installation. There are analogs with k8s but the swarm is easier to deploy regardless of the fact that k8s is integrated. That's simply for another day. So now there are a bunch of things that need names:

  • domain
  • stack
  • service(s)
  • url

A quick search to review the docker docs did not turn up anything interesting. My definition of a docker stack is analogous to docker-compose because they use similar config files. The purpose of a docker compose is to link and name a set of services. For example an application server and a database server for storing it's data. The docker-compose file describes the services with the outside world and with each other. A comic book inventory application might be connected to a comic book database but not connected to a newspaper database. The composition file provides some ephemeral connectivity.
production requests stay in production and staging requests stay in staging.
Given the 4 names above it's also important to note that there are multiple states to consider... dev, branch, staging, production... and maybe a few more. When you create the cross product from the two lists the number of names explodes and frankly requires some care. Especially when you might only have one domain or if you have multiple projects... in fact this is one of the shortcomings of traefik and micro services.

One nice thing about the gitlab+k8s design is that it simply uses a uuid and the rest is up to the user and the subsequent compose file. But then what about the other names?

But then it falls apart again...


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…

Agile is still dead and has been since 1991

[updated 2011.09.30] yet another response to Agile is good.
When you have so much of you career invested in something like Agile, XP etc... it can be hard to see the forest for the trees. I had a consulting job in The Haag many years ago. IBM was the incumbent contractor at the customer site (a bank) but after 5 years on the job they had not written a single line of functioning code. In the office there were two teams of software people... both behind closed doors. The first team was the Data team and the second team was Functional. They rarely spoke and they never shared information. I was there for a week, introduced the client to OO and we had a functioning prototype. Smart people do smart things, You cannot make an underachiever exceptional by using Agile. Either they get "it" or they don't.
I just commented on a blog. I'm sure there is some validity to his post beyond observing that Agile Scrum is broken. It certainly is not what it was originally intended but for…

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: (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 answer all of the questio…