4 ms·
A good strategy is to use both (these are complementary tools) - one is stronger for config management (Ansible), the other for provisioning infrastructure (T
by bproven 9y ago
A good strategy is to use both (these are complementary tools) - one is stronger for config management (Ansible), the other for provisioning infrastructure (TF). Build and manage the infra itself (instances, security groups, VPCs etc) with TF and use Ansible to configure (e.g. install, maintain nginx on the instance). They work well together since there is a provisioner for Ansible in TF.
Optionally if you go the totally immutable route you may only need TF (plus somethig like packer) and not Ansible.
I have not had to migrate from on to the other, so unfortunately I can't be much help here. Maybe someone else can share their insights on that (including benefits/drawbacks).
- albertlie 9y agoHi Bproven, Thanks for the answer! Did you use terraform or ansible fully then in your current work? Any challenges you can share when dealing with terraform or is there any reason you fully use Terraform?
- bproven 9y agoFor TF, I found it easy to work with and also cloud agnostic (nice bonus). So you only have to learn one tool instead of one for each cloud provider (Azure's Resource templates , AWS's CloudFormation, etc). Also it seems to have great traction in the industry and is a very active project so I don't see it going anywhere soon...
- albertlie 9y agoGot it. Thanks!