By Roger Perkin, IOD Expert The tools and processes network engineers have used to manage networks have not really changed in the last 25 years. Using tools like Putty or…
Do you want to start using Ansible? Are you already using it, but coming up against challenges? Even if you don’t fall into either category, don’t stop reading. I’m going to show you why you might actually need Ansible and how to best take advantage of it..
Ansible’s catchphrase is “simple IT automation,” which is a pretty accurate description of what it does. In its most popular mode of operation (there are several), Ansible is described as a desired state of input, and it manipulates a set of machines to achieve this state. At this point, you may be thinking “yeah, but we’ve already got shell scripts for that.” Ansible, though, offers several advantages over good old shell scripts.
First of all, the playbook, which describes the desired state, is declarative and written in YAML. Using a playbook means you don’t need to handle the error control and condition checking yourself. It also means no actions will be taken if the state is already satisfied (e.g. apt-get won’t run if there’s an nginx package installed).
But this is only part of the story.
Tech Guru Timothy Fitz on making the jump to Continuous Deployment, the buzz around DevOps, and why GitHub has set back Software Departments by 5-10 years…
BlazeMeter invited me to ask 5 key questions to Timothy Fitz – the man who coined and popularized Continuous Deployment. Here are the results:
How would you define continuous deployment and how is it different to continuous delivery?
Timothy Fitz: This is a great question that isn’t frequently asked, since it is often assumed that they both mean the same thing. Usually, when people refer to continuous delivery, they actually mean continuous deployment.
[GUEST POST] ironSource is the world leading platform for software discovery, distribution, delivery and monetization. The solution consists of four cores – installCore, mobileCore, displayCore, and mediaCore – that connect software developers and users across platforms and devices.
The infrastructure department’s responsibilities include handling data received from all of our platforms for our own data analysis and billing. On any given day, we receive tens or even hundreds of millions of events from desktop computers, mobile phones, and web browsers. Our system comprises hundreds of servers supporting more than 5,000 concurrent connections.
In this article I will describe how we at ironSource scales Node.js with Docker – automatically build, deploy and run a Node.js application within a docker container to production.