DevOps: AnsibleWorks promises easier administration of cloud or datacenter infrastructure

Every time I meet another company that helps DevOps types do their work, I think of my brother +Alex Scoble who works for the government in Oregon keeping tons of infrastructure up and running in datacenters and cloud systems.

Here +Tim Gerla , VP of Services, shows me +AnsibleWorks  , which is a dev/op tool that helps you administer your cloud computing and datacenter infrastructure. http://www.ansibleworks.com/

It's easier than the competitors and lets you avoid writing scripts or custom code to deploy and update your applications.

My brother is using +Puppet Labs. I wonder if this, or SaltStack (which I featured on a previous video at https://plus.google.com/+Scobleizer/posts/J5Q4tVvxJAA ) will get him to switch?
55
10
Douglas Leffert's profile photoHans kullberg's profile photoDiraj Goel's profile photoscott layden's profile photo
15 comments
 
One problem is that Ansible manages Linux only so isn't really suited to heterogeneous environments.
 
Alex, that's not true, actually.  We have a ton of users on OS X, BSD, Solaris, and even a bit of HPUX/AIX.  Perhaps you still have some Windows, which is something we're going to have something for soon.
 
Yes, what I meant was that it can't currently manage windows.
 
As an aside, the fact that Microsoft has never built SSH functionality into Windows is a pretty major mistake, in my opinion.
 
Transports in Ansible are pluggable, when we do Windows it's not going to be using SSH.
 
How does Ansible respond to the criticism that "SSH in a loop is not configuration management"?
 
Not managing windows is a feature not a bug IMHO
 
Unless you need to manage Windows...
 
Tom, I'd suggest you find an hour to try it and see what you think.   We have an idempotent resource model which is what most people think about bash scripts and SSH, and we actually have strong resource models and are using SSH for transport -- because it's more secure and easier to set up.
 
Getting SSH setup correctly between all the systems is always the first thing I do, and then everything I develop from there leverages off it.   Been doing it this way for decades and ended up developing software modules to provide higher and higher level abstractions. 
Add a comment...