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
Welcome to Technology Short Take #60. As usual, I’ve gathered what I hope to be a useful but varied collection of articles and links on key data center technologies. I hope something I’ve included here will be helpful—enjoy!
Featuring speakers from Industrial Light and Magic, Atlassian, Cisco and more!
We're happy to share our speaker lineup for AnsibleFest London on Thursday, February 18th at InterContinental London - The O2. Our one-day user conference brings together hundreds of Ansible users, developers and industry partners to share best-practices, case studies and Ansible news.
With yet another record setting amount of submissions, our engineering team had their work cut out for them. We took each submission, anonymized them to remove any speaker/company/product information, and sent them off to our team of engineers for blind review. We then picked out a well-rounded agenda from the highest scoring talks.
Stay tuned for additional speakers announcements leading up to the event.
Deploying a Mesos Based Visual Effects Studio with Ansible
Aaron Carey, Production Engineer, Industrial Light and Magic
Jim Vanns, Senior Production Engineer, Industrial Light and Magic
Industrial Light and Magic is leveraging Ansible to deploy a Mesos cluster from scratch on multiple cloud platforms, build its application docker images and deploy them as services. This presentation will look at how ILM is using tags to manage services dynamically, and the steps taken to make it work across different cloud providers.
Featuring speakers from Industrial Light and Magic, Atlassian, Cisco and more!
We're happy to share our speaker lineup for AnsibleFest London on Thursday, February 18th at InterContinental London - The O2. Our one-day user conference brings together hundreds of Ansible users, developers and industry partners to share best-practices, case studies and Ansible news.
With yet another record setting amount of submissions, our engineering team had their work cut out for them. We took each submission, anonymized them to remove any speaker/company/product information, and sent them off to our team of engineers for blind review. We then picked out a well-rounded agenda from the highest scoring talks.
Stay tuned for additional speakers announcements leading up to the event.
Deploying a Mesos Based Visual Effects Studio with Ansible
Aaron Carey, Production Engineer, Industrial Light and Magic
Jim Vanns, Senior Production Engineer, Industrial Light and Magic
Industrial Light and Magic is leveraging Ansible to deploy a Mesos cluster from scratch on multiple cloud platforms, build its application docker images and deploy them as services. This presentation will look at how ILM is using tags to manage services dynamically, and the steps taken to make it work across different cloud providers.
In this post, I’m going to show you how to use macvlan interfaces with Docker for networking. The use of macvlan interfaces presents an interesting networking configuration for Docker containers that may (depending on your use case) address issues with the standard Linux bridge configuration.
Macvlan interfaces, if you’re unfamiliar with them, are a (somewhat) recent addition to the Linux kernel that enables users to add multiple MAC address-based logical interfaces to a single physical interface. These logical interfaces must reside in the same broadcast domain as the associated physical interface, which means that Docker containers attached to macvlan interfaces also will be in the same broadcast domain as the associated physical interface. In other words, the Docker containers will be on the same network as the host—no IPTables rules, no Linux bridge, just attached directly to the host’s network. This introduces some interesting possibilities (and potential challenges), but I’ll save that discussion for a future post.
Right now, macvlan supported is implemented via an unsupported Docker Network plugin hosted on GitHub. However, I suspect that the macvlan functionality found in this plugin will find its way into the core of Docker Network, and probably sooner rather than later.
You’ll Continue reading
Here’s a quick run-down:
There really should be a drum roll playing as you read this, because this feature has been at the top of everyone’s wish list for as long as Galaxy has been around. But here it is… Organizations now have a home in Galaxy. Yes, you can import roles into an organization!
How, you ask? Just click the import button. Really. That’s it. The role will be imported exactly as the repository appears in GitHub. If the role belongs to ‘acmeco’ in GitHub, then it will appear under ‘acmeco’ in Galaxy.
You can import any repositories from GitHub where you are a collaborator or owner. Log in as yourself, and import your roles or your organization’s roles.
Existing roles prior to Galaxy 2.0 have not been changed. To move a role from your username to an organization, delete the role and import it again.
Sharing links to your content in Galaxy now makes sense with user-friendly URLs that include GitHub username or organization and Continue reading
Here’s a quick run-down:
There really should be a drum roll playing as you read this, because this feature has been at the top of everyone’s wish list for as long as Galaxy has been around. But here it is… Organizations now have a home in Galaxy. Yes, you can import roles into an organization!
How, you ask? Just click the import button. Really. That’s it. The role will be imported exactly as the repository appears in GitHub. If the role belongs to ‘acmeco’ in GitHub, then it will appear under ‘acmeco’ in Galaxy.
You can import any repositories from GitHub where you are a collaborator or owner. Log in as yourself, and import your roles or your organization’s roles.
Existing roles prior to Galaxy 2.0 have not been changed. To move a role from your username to an organization, delete the role and import it again.
Sharing links to your content in Galaxy now makes sense with user-friendly URLs that include GitHub username or organization and Continue reading
Almost every year since 2012, I’ve been publishing a list of projects/goals for the upcoming year (here’s the original list for 2012, then 2013, I skipped 2014, and here’s the list for 2015). In this post, I’m going to share with you the list of projects/goals for 2016.
Here’s the list for 2016. For some of the items below, I’m also going to include a stretch goal, something I’ll aim toward but won’t count against myself if I don’t actually attain it.
Complete a new book (again). In addition to actually completing the new network automation book I’m writing with Jason Edelman and Matt Oswalt (it’s available now as an Early Access edition), I have another book project lined up that I intend to finish and get published in 2016.
Make more open source contributions. I failed this one miserably last year (see last year’s report card), but I am intent on making this one happen. Over time, I expect that this will just be part of who I am, but until then I’m going to explicitly call it out. Since I’m not a programmer (not yet, may never be), these contributions will have Continue reading