Report: Red Hat Buying DevOps Startup Ansible (venturebeat.com)
An anonymous reader writes: According to VentureBeat Red Hat Inc is about to buy the company behind the automation and orchestration software Ansible. The move is seen as a good acquisition, since Ansible, other than being almost universally expanding, is also used by Red Hat's own cloud and system platforms. It could probably use some strong backing for the extra services it wishes to offer. The question remains whether this will have consequences in the future direction of the Python-based, open source platform itself (on GitHub). It's one of the most trivial to implement (compared to cfengine, ever-changing puppet or Chef) yet very powerful, and Red Hat may want to optimize it for their own purposes.
Update: 10/16 15:39 GMT by S : Red Hat has confirmed the acquisition and explained their reasons for doing so.
that Red Hat is controlling or attempting to control the direction of Linux subtly and not so subtly. Where Red Hat goes, so goes Linux in many ways. I don't even want to get into the whole systemd thing with Lennart Poettering, stuff with Kay Sievers, or others, but Red Hat seems to have a disproportionate level of control over the direction of Linux, kernel itself aside.
And make it depend on systemd.
You are all donkeys.Donkeys Heee Hawwww!!Hee Hawww!!Heee hawwww say the donkeys.You all red hat donkeys.
Thai chick with a dick
Hard truth known, could not resist
Loved those bolt on tits
Early stuff is for cows.Cows say MOOOOOOOO.MOOOOOOOOO.MOOOOOOO.MOOOO says the cows.You early stuffed cows.
Considering the origin of the very word "ansible" -- Ursula K. le Guin's anarchist-syndicalist novel The Dispossessed -- this money hogwash reeks of irony.
Yet another VCgasm before the party ends?
The Ansible guys are decent and a good amount of them are in NC with Redhat and are ex-Redhat, so I am sure that was a big factor. I just wish I would have tried harder to get a position with them 6 months ago :P.
As far as the future. Everything is going go and there will be no real CM systems, just Docker or other deployment scripts. Bare metal will just bootp in to a good packer base and cloud-init will take care of every where else. So it is a great time to get out of the CM business.
Because DevOps means nothing.
Another sign that RedHat is going down the crapper. First systemd, now this.
Finally, the year of Linux on the Desktop, now that RH will have faster-than-light communications!
Browsing at +1 - no ACs, I ignore their posts. So refreshing!
Why buy what you can download for free? They after the talent or something?
This has come at a time when our company is evaluating puppet and ansible for deployment of Jboss EAP and applications. I see this as another plus on the "ansible" side, for several reasons. Firstly it will be a lot easier getting support with possible JBoss deployment issues, there will be one port of call. Secondly the large company backing is a plus. And finally there is a very strong possibility of future integration.
I wonder if it will be integrated int Jboss Operations Network. It looks a lot slicker than the current ant-based deployment architecture.
Snakes Hissssss!!Hissss!!Hissssss... say the snakes.You all cowy snakes.
Is it web scale too?
It's interesting that they bought out another tool when they already do some of the work a configuration management tool does with their satellite server, and for a larger setup integrate/sell puppet enterprise (one of Ansible's main competitors).
I've worked with Chef and puppet for a few years each and evaluated ansible at my current company because it's the new buzzword and it's clientless. My concerns for not wanting to go with Ansible for system management was that to get the web endpoints for things like auto-scaling you have to get Tower. And if I'm going to pay $10k to setup tower, I might as well setup a Chef server which will scale FAR more than Tower will on the same hardware and will cost substantially less. Also, to really be effective with Ansible you need to setup a user/password (or ssh keypair) combination which I really don't like because if it's compromised, you're whole infrastructure is compromised. Chef has safeguards to help with this and you'd still have a bit of panic if a key is compromised, but you're not required to put "root" keys on everything. So there's still damage, but it's mitigated and can be corrected. Finally, Chef 12 really helps give me overall system state of everything out of the box which I absolutely love. You don't get that with Ansible until you get Tower.. Anyway, my two cents.. I am curious though what this means for Ansible moving forward.
Quality title there, that "Report:" improves it so much.
This pretty much cements the trend - Ansible has been increasingly popular over the last couple of years: http://www.google.com/trends/e...
Wonder if they'll soon find a good way to integrate it with Spacewalk (Satellite).
Also, will Canonical grab SaltStack now? :)
I believe this implies the death of the Katello project, something I've been looking forward to as stable.
DevOps... I have a Solutions company, someone buy it!