As a technolgy fan I always try to find and hack how things work, my passion for technolgy in general lead me to pursue interests in coding, automation, metrics and analitics, IoT, electronics and DIY projects of all sorts.
From simple hello world coding in new languajes to automating a full fleet of servers (or raspberry pi’s), creating kubernetes clusters, database clusters, DIY electronics, home lighting and automation, energy efficiency, among others can be seen in my personal projects.
In this blog I will share some of this projects, most things I do for fun at home as side projects, my drive for automation lead me to try to keep as much things in code to be able to reproduce my projects from scratch.
My idea is to share this projects which might save others some time for their presonal projects.
One of the most popular services from cloud providers is cloud storage, to be more specific AWS S3, Google Cloud Storage, Azure Storage or any similar service from other cloud providers. This service is very convenient for developers and SREs or System Admins, it solves the problem of managing disks, storage devices , storage servers, etc at a very low cost for storing files, depending on the cloud provider, some of them even offer a staggering 99.
Whenever someone is working with docker and need to move images between hosts without the need for rebuilding them or hosting a private registry. This lightning post will show us 2 commands that will help us to easy move container images between hosts. How to save a docker image for reuse in other host? There is a handy command that helps save a docker image that is already in the system or already built, there are situations where builds take a long time and building the images in multiple hosts is time consuming, so we can save the image and copy it to other host and import it for reuse.
Did you ever had trouble with a proxy config? Found that is not simple to test a proxy locally?. Why this? simple, I found many times deploying a proxy configuration to production, even a small change like adding a new path, a redirection or just updating ssl certs, can lead to a disruption or an outage because sometimes it’s hard to properly test it before pushing the configuration. So I found a couple of tricks that can help test locally in our laptops or machine before even pushing the code or config giving a safer path to deploy a proxy config.
After about 2 months of launching this blog I realized that creating blog content is a time consuming task. While the whole purpose of my blog is to share some of my experiences and it’s my own way to contribute to the open source community (most of what I talk about here is open source tech), I figured that I wanted to keep adding content every week, but some weeks it’s much harder than other weeks to create a full blown blog post, I write this in my free time so between work and personal life it’s hard to keep full blown projects every week.
In a previous post I talked about Taming the cpu metrics, while that post was an overview of cpu metrics I thought it was a good topic to emphasize on the cpu steal metric in linux hosts. This is something I recently found and didn’t know it even existed, but it can be very useful when running in virtualized environments and helping us tune either the vm, or the physical host that runs the vms.