Skip to main content

Turbo - Introduction

I'm not sure how many parts this is going to take. I think most authors actually write the whole article and then find sensible places to split the article. Here's what I'm thinking about for the moment and the basic outline:

  1. Introduction
  2. Requirements
  3. Tools and libraries
  4. The implementation
  5. The final project
  6. Next steps
Over the last 8-10 weeks I have been writing reports using SQL. The database I've been connected to is SQL Server and I have had to export the reports in many different formats including: dot, csv, tsv, text, table, html, and even xlsx. I also needed to email the file to a distribution list and I needed to upload it to an s3 archive. One thing I was hoping to implement was that I was going to be able to produce the same export just in different format. That meant that I needed to store my SQL in glossary form and that I could be assured that the one SQL statement would produce exactly the same results regardless of he format.

I've been using .sh files (bash) and some bash script-foo to get things going. Now I have nearly 50 reports and I feel like I'm losing the library battle. And so the Turbo project begins.

As a historical reference Turbo Pascal, C, C++ and Assembler are where I lived for a stretch of time that represented my greatest learning. (most learning in the least amount of time). So, in part homage and part fond memory and hopes for the future, I named this project Turbo.

(anyone wanting to contribute in any way is welcome)

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…