The moment I heard about this book, I wanted to read it. The title is self-explanatory: “How Google Runs Production Systems”. It looked so interesting to me that I immediately purchased it. At that time I had other books waiting in my bookshelf, but I was so impatient to read this one, that I admit I started immediately after the Phoenix Project. This one was the one that I absolutely wanted to read.
The contents in this book are well organised, chapter after chapter it’s easy to accept the challenges that an organisation of this size had to conquer to become successful in managing the infrastructure, processes and people.
Continue reading “Site Reliability Engineering”
After a couple of months of being GA (Generally Available) I was in the WSL bandwagon.
I started using Windows Subsystem for Linux (WSL) for a lot of good reasons, especially in my role as System Engineer. I work on different environments and across various operating systems and in my world virtualization and containers are the rule. My tools of trade are Powershell, BaSH and Python on the so having all of them in the same Operating System is really handy.
I attended Meetup events where WSL was presented, I’ve presented a brownbag myself on WSL, and recently as Techsnips Contributor I’ve create a small video on how to install it. So I’ll try in this article to give you a brief introduction.
Continue reading “Windows Subsystem for Linux”
The Phoenix Project is a novel about IT. That was enough for me to get all of my attention. Describing today’s challenges and DevOps practices it’s a brilliant and original idea! I’m even more convinced after reading this book, I’ve also discovered that the authors have been inspired by “The Goal” by Eliyahu M. Goldratt.
Continue reading “The Phoenix Project”
My ultimate goal as a DevOps engineer is providing solutions focusing on aligning IT systems to company’s culture and business processes. Limiting the time spent on creating bespoke tools and scripts that not all sysops are able to understand or maintain properly. Any custom tool is hard to maintain without a basic software engineering background and it needs a proper design, documentation, QA and all diligence and discipline required along the way.
From imperative to declarative
To achieve this result I need to shift from a developer mindset where is imperative (creating flows) writing programs or automation scripts to declarative, specifying just the desired state of a system in a YAML or JSON files that are a “lingua franca” between devs and sysops providing an up-to-date documentation that can be safely managed on a SCM (like GIT).
Continue reading “DevOps: VMs lifecycle management with Vagrant”
Learning PowerShell is really a fast process where you can be productive in a matter of days or in a month of lunches as Don Jones and Jeffery Hicks said. But in my humble opinion, there aren’t much online resources that make you pay enough attention on how to run scripts and configure the environment properly in order to leverage all the technology features that Powershell and Windows environment is capable of.
So I’ve decided to add some articles to conquer this problem and help you on your journey, it’s an interesting subject for students and professional developers/it pros at any level of experience.
Continue reading “PowerShell Learning and Security Features”