Skip to main content

software lab in a box - step 1

I've been fumbling around with chickens and eggs to figure out how to deploy a good software development lab and production environment. There is a constant battle between management and developers to provide good enough security, disaster recover, usability; as every three legged stool has.

Developers want to be trusted with the keys to the space shuttle but we know that kids like to take cars for joy rides and while some joy rides end without being caught there are others that end in disaster. Furthermore, moving something from the lab to production should require study and validation. And the fox should not be watching the hen house. (see any vampire or zombie movie)

So, in the beginning of the deployment there is the big-bang or bootstrap. That starts in three places. [1]  basic hardware like desktops and laptops with the usual configuration [2] software starting with communications like email and messaging. Somewhere in (1) and (2) you have to buy server hardware like mail servers or services like gmail etc.

[3] software assets need to be stored as development begins. And if you're ahead of the curve then you need CI/CD. I think a good starting point here is something like FreeNAS or Synology. They offer plugins for gitlab and even webmail. One can also run gitlab runners on desktops when they are idle in addition to dedicated servers and cloud services. I'd like to deploy runners adhoc but there is a huge cost unless the build process is actually proportionally longer.... for example I have some reports that run once a month and they need 32GB or ram to complete the task. The report also runs for about an house so a deploy, run and destroy would be fine since it's only once a month and we're not paying for idle system time.

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…