Clik here to view.
DevOps: how we got here
Developer toolset From the developer point of view, there are some tools involved in the source-to-deploy process Source control management tools: Subversion, Git, Mercurial, Perforce,… Build tools:...
View ArticleClik here to view.
Is DevOps killing the Operations team?
Hearing everywhere about DevOps and how it is all about automation, and how manual steps should be removed from Operations. Starting to worry about your OPs job? On one hand, yes, you should worry. My...
View ArticleClik here to view.
Infrastructure as Code
DevOps is not about the tools That’s true, in the same way that agile is not about the tools either, it’s a set of ideas, concepts, best practices,… Nice, but… how can I successfully implement it?...
View ArticleClik here to view.
Introduction to Puppet
Enough about philosophical posts, let’s get started with some practical Puppet. Manifests Puppet configuration files are called manifests, written in a ruby-like DSL. Puppet provides types and...
View ArticleClik here to view.
Automatically download and install VirtualBox guest additions in Vagrant
So, are you already using Vagrant to manage your VirtualBox VMs? Then you probably have realized already how annoying is to keep the VBox guest additions up to date in your VMs. Don’t worry, you can...
View ArticleClik here to view.
MaestroDev named DevOps “Cool Vendor” by Gartner
Warning, some self-promotion ahead! Gartner has published their annual list of Cool Vendors, including a section for DevOps, where we are one of the 5 selected companies. Not a big fan of this analyst...
View ArticleClik here to view.
Anatomy of a DevOps Orchestration Engine: (I) Workflow
At MaestroDev we have been building what may be called, for lack of a better name, a DevOps Orchestration Engine, and is long overdue to talk about what we have been doing there and most importantly,...
View ArticleClik here to view.
Anatomy of a DevOps Orchestration Engine: (II) Architecture
Previously: (I) Workflow Maestro architecture is basically defined by a master server and multiple agents, written in Java and Ruby (JRuby) for the backend and JavaScript for the frontend using...
View ArticleClik here to view.
Anatomy of a DevOps Orchestration Engine: (III) Agents
Previously: (II) Architecture In Maestro we typically use a Maestro master server and multiple Maestro agents. Each Maestro Agent is just a small service where the actual work happens, it processes the...
View ArticleClik here to view.
Learning Puppet or Chef? Check out Vagrant!
If you are starting to use Puppet or Chef, you must have Vagrant. Learning Puppet can be a tedious task, getting up the master, agents, writing your first manifests,… A good way to start is using...
View Article