Live data from Hacker News

Red Hat is buying Ansible

venturebeat.com

61–70 of 186 posts

Re: Red Hat is buying Ansible

#61
I always wonder why cf-engine is so unpopular on HN. It has some nice advantages like no dependency on ssh or a scripting language. It is not as simple to get started, though.

Re: Red Hat is buying Ansible

#62
I think that this will fit nicely with the Cockpit project which should "revolutionize" remote administration (it isn't bad). So now Red Hat wants to add something for wholesome orchestration, which was really needed in that space.

Re: Red Hat is buying Ansible

#63
post #8

Supposedly a > $100mm deal. Both companies are already headquartered in N.C., and Ansible has a ton of momentum in the RHEL and OpenStack arenas, so it would make sense to pull the project into the fold. One thing I wonder is how much the project's priorities would shift away from (if at all) anything non-RHEL-centric.

As a Red Hat customer I'll be interesting to see how it affects the complete fucking shambles that has been the Satellite 6 rollout, which was supposed to be full Foreman/Puppet integration for provisioning and config management. Apart from the fact that it's been a shambles, Red Hat have been solidly pushing customers down the puppet route. I expect there will be some grumpy meetings in the next few weeks.

Reminds me of their switch from Xen to KVM from RHEL 5 to 6, so I wouldn't put it past them to change course.

Re: Red Hat is buying Ansible

#65

I found this sentence funny "Representatives of Red Hat and Ansible did not immediately respond to requests for comment". I take it to mean: "we wanted to run the story as quickly as possible; still it would have been nice to get superquick comments by RH or Ansible; tough luck, though."

To me "did not immediately respond to requests for comment" smacks of neediness and self importance on the reporter's part (answer me now, you fools, don't you know who I am and what power I behold?!) and the people that would respond to such comments being in the middle of dealing with something more important at the time (perhaps answering a queue of queries that came in first, or queries from people who are more i…

Those quotes are found in a huge number of stories.

Sure you can blame them for a rush to publish if you want. I think mainly they are trying to indicate they reached out to a relevant party and didn't hear back. And by saying didn't hear back immediately they are making clear that it may well be the party wasn't immediately available (not that they were not willing to respond at all).

On some (maybe all, I don't know) sites, they then update the story if they get responses.

Re: Red Hat is buying Ansible

#66

I found this sentence funny "Representatives of Red Hat and Ansible did not immediately respond to requests for comment". I take it to mean: "we wanted to run the story as quickly as possible; still it would have been nice to get superquick comments by RH or Ansible; tough luck, though."

To me "did not immediately respond to requests for comment" smacks of neediness and self importance on the reporter's part (answer me now, you fools, don't you know who I am and what power I behold?!) and the people that would respond to such comments being in the middle of dealing with something more important at the time (perhaps answering a queue of queries that came in first, or queries from people who are more i…

> answer me now, you fools, don't you know who I am and what power I behold?!

Alternatively, "Answer me now, before someone else beats me to publication, oh god please ... c'mmooon it's almost deadline, pickuppickuppickuppickup ah dammit, too late."

Re: Red Hat is buying Ansible

#67
post #56

Earlier quoted context omitted.

In defense of maven it does provide neither branching nor looping statements so refering to it as a "programming language" is hard to justify.

Neither does HTML and the L stands for language.

"language" != "programming language"

Re: Red Hat is buying Ansible

#68

I think the price point here is about a couple of things: - Chef and Puppet are too expensive for most companies to acquire, and have too much operational cost for too little revenue - Ansible got a strong following in the SMB space, Red Hat probably thinks they can move that upmarket some - Ansible's agentless configuration management has potentially strong applicability in a container world (why do I need a chunky…

SMB = small business?

Re: Red Hat is buying Ansible

#69
post #68

I think the price point here is about a couple of things: - Chef and Puppet are too expensive for most companies to acquire, and have too much operational cost for too little revenue - Ansible got a strong following in the SMB space, Red Hat probably thinks they can move that upmarket some - Ansible's agentless configuration management has potentially strong applicability in a container world (why do I need a chunky…

SMB = small business?

Small and Medium Business

Re: Red Hat is buying Ansible

#70
post #68

I think the price point here is about a couple of things: - Chef and Puppet are too expensive for most companies to acquire, and have too much operational cost for too little revenue - Ansible got a strong following in the SMB space, Red Hat probably thinks they can move that upmarket some - Ansible's agentless configuration management has potentially strong applicability in a container world (why do I need a chunky…

SMB = small business?

Small and Medium Business
Post reply on HN