6 ms·
Ansible 2.0 should have some new strategies to speed things up, depending on your requirements: https://docs.ansible.com/ansible/playbooks_strategies.html https
by justingood 11y ago
Ansible 2.0 should have some new strategies to speed things up, depending on your requirements:
https://docs.ansible.com/ansible/playbooks_strategies.html https://docs.ansible.com/ansible/playbooks_strategies.html
It will be interesting to see how performance is after it's released.
We eventually settled on having Ansible build an AMI for us that can then be spun up by as part of a Cloudformation template (also initiated by Ansible).
We've actually been moving further and further away from having Ansible handle the configuration management side of things, and deal with Orchestration primarily.
- swinglock 11y agoWhat do you use for configuration management?
- justingood 11y agoWe've moved to using Hashicorp's Consul-Template (https://github.com/hashicorp/consul-template https://github.com/hashicorp/consul-template). Ansible populates Consul with any required configuration changes during the deployment of a new version, and Consul-Template knows about these changes and automatically writes them to disk. Applications running on the host are then reloaded to pick up the changes.