It seems like just yesterday that we were putting together the recap of Ansible's community growth in 2014. That was a very good year.
Here we are at the start of 2016 already -- and looking back on 2015, it was an even better year than 2014 was.
First, let's take a look at the numbers. For consistency's sake, we'll mostly compare to 2014 numbers, which can be found in last year's analysis. Note that the same caveats from last year's analysis also apply this year.
Debian’s Popularity Contest is an opt-in way for Debian users to share information about the software they’re running on their systems. Although it represents only a small sample of the Linux distro world, it’s useful because it’s one of the few places where we can really see an apples-to-apples comparison of install bases of the various tools. Because Ansible is agentless, we compare the Ansible package to the server packages of other configuration management tools.
For the first time in 2015, Ansible installations on this chart outnumbered Puppetmaster installations. Ansible shows continued strong growth, and appears to remain on an upward trend into 2016.
Caveats abound with this chart, but it does Continue reading
It seems like just yesterday that we were putting together the recap of Ansible's community growth in 2014. That was a very good year.
Here we are at the start of 2016 already -- and looking back on 2015, it was an even better year than 2014 was.
First, let's take a look at the numbers. For consistency's sake, we'll mostly compare to 2014 numbers, which can be found in last year's analysis. Note that the same caveats from last year's analysis also apply this year.
Debian’s Popularity Contest is an opt-in way for Debian users to share information about the software they’re running on their systems. Although it represents only a small sample of the Linux distro world, it’s useful because it’s one of the few places where we can really see an apples-to-apples comparison of install bases of the various tools. Because Ansible is agentless, we compare the Ansible package to the server packages of other configuration management tools.
For the first time in 2015, Ansible installations on this chart outnumbered Puppetmaster installations. Ansible shows continued strong growth, and appears to remain on an upward trend into 2016.
Caveats abound with this chart, but it does Continue reading
We have recently published a Technical Support Bulletin (TSB-2016-230-A) encouraging all customers to upgrade to version 2.1 or newer: you can find the details of this TSB on http://my.brocade.com. Upgrade to most recent version If you are running an older version of Brocade Services Director prior to version 2.1, you will need to upgrade to... Read more →
The post Worth Reading: Standardized Models For Networking appeared first on 'net work.
Patreon recently snagged $30 Million in funding. It seems the model of pledging $1 for individual feature releases or code changes won't support fast enough growth. CEO Jack Conte says: We need to bring in so many people so fast. We need to keep up with hiring and keep up with making all of the things.
Since HighScalability is giving Patreon a try I've naturally wondered how it's built. Modulo some serious security issues Patreon has always worked well. So I was interested to dig up this nugget in a thread on the funding round where the Director of Engineering at Patreon shares a little about how Patreon works:
In my last post, I talked about some of the more physical aspects of my virtual home lab. We talked about the need for nested virtualization as well as what the physical and virtual network would look like. In this post, we’re going to look at building the VMs as well as getting the operating systems ready for the OpenStack install. As a quick reminder, let’s take a look at what the logical lab looks like…
The lab will consists of 3 VMs (to start with), a controller, and two compute nodes. Wile OpenStack can be installed on a variety of Linux operating systems, this series will be focusing on Ubuntu version 14.04. The first thing we need to do is create a base image. Without a base image, we’re going to be forced to install Ubuntu individually on each server which is not ideal. So the first thing you’ll want to do is download the correct ISO and upload it to your ProxMox server.
Note: Getting around in ProxMox is out of scope for this series. HOWEVER – ProxMox has a rather large following on the internet which Continue reading
Configuration Management is a big category today, largely comprised of Puppet and Chef, followed by Ansible and Salt, but what is Configuration Management? Configuration Management is, at it’s simplest, a matter of boolean states on a machine, stack, or infrastructure. Is the Apache httpd installed on this server? If not, install it. Does this file […]
The post Configuration Management: DevOps From Ops appeared first on Packet Pushers.
Configuration Management is a big category today, largely comprised of Puppet and Chef, followed by Ansible and Salt, but what is Configuration Management? Configuration Management is, at it’s simplest, a matter of boolean states on a machine, stack, or infrastructure. Is the Apache httpd installed on this server? If not, install it. Does this file […]
The post Configuration Management: DevOps From Ops appeared first on Packet Pushers.
In part 1 of this series, I pointed out that there are three interesting questions we can ask about BGP security. The third question I outlined there was this: What is it we can actually prove in a packet switched network? This is the first question I want dive in too—this is a deep dive, so be prepared for a long series. This question feels like it is actually asking three different things, what we might call “subquestions,” or perhaps “supporting points.” These three questions are:
These are the things I can try to prove, or would like to know, in a packet switched network. Note that I want to intentionally focus on the data plane and then transfer these questions to the control plane (BGP). This is the crucial point to remember: If I Continue reading
A paltry 15% of the radio spectrum that is suitable for broadband in the US has been made available to the private sector.