Using Ansible and Nomad for a homelab (part 1)

Re:Using Ansible and Nomad for a homelab (part 1) by mdaniel on Sunday February 27, 2022 @10:50PM (#30496193)

I have seen saltstack references in the kubernetes repo, and that alone was enough to pique my interest to read into it, but I guess maybe the "chicken and egg" is causing salt to be just massively behind on what one can do with ansible

For example, this[1] is all that seems to be available for "cloud" on AWS. Now, I am super, super cognizant that there is a camp of "TF all the cloud, then $something on the machine" but here salt seems to be dipping its toes into the AWS API, and yet treating that machine as a pet, not even offering ASG nor LaunchTemplate knobs that could bring the machine back to life if it falls over

1: https://docs.saltproject.io/en/3004/ref/clouds/all/salt.clou...

I will say, it seems salt's documentation just absolutely spanks ansible's approach, so there's that

[ Parent | on HN ]

Re:Using Ansible and Nomad for a homelab (part 1) by Jedd on Sunday February 27, 2022 @11:54PM (#30496565)

Yeah, there's certainly some fuzzy borders that delineate the various domains of deployment, fleet orchestration , config management, BCP, etc.

Similar to author of TFA, I use Consul & Nomad and config management (in my case Salt) to manage a fleet of 'home' systems, and a couple of IaaS boxes (DO rather than AWS, because Jeff). $dayjob uses Ansible & Tower, but nothing about that experience has inspired me to try to lift and shift to that side of the fence. In any case, I've not hit many functionality gaps with Salt, though my requirements are relatively modest.

My favourite demonstration of one of the pain points with Ansible is:

https://docs.ansible.com/ansible/latest/user_guide/playbooks...

[ Parent | on HN ]