Skip to main content

docker registry pushing latest

My latest CI/CD performs all the functions that a build and deploy system is supposed to. Sure there are some purists that talk about deploying everything, chaos monkey, and so on... but until you've trashed a financial database with millions of records your opinion might not matter.

CI/CD can promote systems to production either through a push or a pull. And there are not many advantages although some security people would prefer a pull and I understand that... but the last thing you want to do it get your head wrapped around versions. I'm currently tagging my registry images with the pipeline ID. And as each pipeline completes I also push 'latest'.

Depending on the speed of the CI/CD runner 'latest' can be assigned to the wrong image. Also, it really isn't the latest until it's been pushed all the way around the system. Now that I'm using pipeline ID instead of the one ID:latest I'm seeing that latest can be promoted prematurely.

Just look at any of the images on the hub and you'll see that there is some crazy numbering schemes there... seems that at some point in their projects there is a branch and the promotion of the branch with some config identifies the version. Make sense? It's just a lot of many versioning.  Just look at the golang package... it's crazy how many versions they publish at once. I think I get the why and how but as a best practice it means there is an army of high priced SREs managing the bits.

Right now my project looks like:



The build task builds the system, packages it and pushes it by ID and latest to the registry. Staging is a QA instance even though there is a DEV instance too. "Weston" is one prod instance and "Zurvita" is another. The challenge here is that we deploy from gitlab and there is no manual deploy. So at what point does the version become "latest" and does it really matter?

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…