Ansible vs StackStorm: What are the differences?
Ansible: Radically simple configuration-management, application deployment, task-execution, and multi-node orchestration engine. Ansible is an IT automation tool. It can configure systems, deploy software, and orchestrate more advanced IT tasks such as continuous deployments or zero downtime rolling updates. Ansible’s goals are foremost those of simplicity and maximum ease of use; StackStorm: Open Source IFTTT for Ops: event-driven automation, security responses, auto-remediation with workflow engine & ChatOps. StackStorm is a platform for integration and automation across services and tools. It ties together your existing infrastructure and application environment so you can more easily automate that environment -- with a particular focus on taking actions in response to events.
Ansible can be classified as a tool in the "Server Configuration and Automation" category, while StackStorm is grouped under "Remote Server Task Execution".
Some of the features offered by Ansible are:
- Ansible's natural automation language allows sysadmins, developers, and IT managers to complete automation projects in hours, not weeks.
- Ansible uses SSH by default instead of requiring agents everywhere. Avoid extra open ports, improve security, eliminate "managing the management", and reclaim CPU cycles.
- Ansible automates app deployment, configuration management, workflow orchestration, and even cloud provisioning all from one system.
On the other hand, StackStorm provides the following key features:
- Automations tie events to actions you’d like to take, using a rules engine and, if you want, comprehensive workflow. Automations are your operational patterns summarized as code.
- StackStorm automations work either by starting with your existing scripts – just add simple meta data – or by authoring the automations within StackStorm.
- Automations are the heart of StackStorm – they allow you to share operational patterns, boost productivity, and automate away the routine.
"Agentless" is the primary reason why developers consider Ansible over the competitors, whereas "Auto-remediation" was stated as the key factor in picking StackStorm.
Ansible and StackStorm are both open source tools. It seems that Ansible with 38.2K GitHub stars and 16K forks on GitHub has more adoption than StackStorm with 3.32K GitHub stars and 439 GitHub forks.
What is Ansible?
What is StackStorm?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to add, upvote and see more prosMake informed product decisions
Sign up to get full access to all the companiesMake informed product decisions
Sign up to get full access to all the tool integrationsMake informed product decisions
StackStorm wires together all tools like Chef, Trello, Puppet, Slack, Jira, NewRelic, GitHub, AWS, Ansible, Nagios, Docker, Logstash and all those other 100500 services into single Operations Center.
You can tie anything with anything. This approach improves existing configuration management and monitoring solutions to deliver automation in completely new, more efficient way.
So if you want to create something like smart self-healing infrastructure or maybe just rule your 100 servers from slack chat - StackStorm can help with that. And it's completely OpenSource!
Ansible is the deployment tool for people who don't like deployment tools. It's close to scripting, doesn't pollute your servers with agents or centralized servers, and just makes immediate sense. The entire stack at Cloudcraft.co is orchestrated by Ansible. What does that mean? Beyond the obvious of installing packages and configuring services, Ansible coordinates all the machines into a working deployment: It adds API servers to the loadbancer pool, opens ports on the DB server for the backend servers to connect, gracefully upgrades services in a rolling fashion for zero-downtime deployments etc. And it's so easy to use, it's easier to use than doing things by hand, meaning it's a deployment tool you'll actually use every time!
We use Ansible to synchronize the few configuration-options we've taken on our CoreOS-Machines. This makes deployment even easier and the fact that it's Agentless made the decision even easier.
Ansible is used in both the development and production deployment process. A playbook couple with a Vagrantfile, easy deploys a local virtual machine that will mirror the setup in production.
I use Ansible to manage the configuration between all of the different pieces of equipment, and because it's agentless I can even manage things like networking devices all from one repo.