Conversation

Notices

1. Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Wednesday, 16-Feb-2022 07:17:47 UTC Santa Claes 🇸🇪🇭🇰🎅
   TIL about pyinfra.com/ as an alternative to Terraform + Ansible.
   
   #pyinfra #terraform #ansible #InfrastructureAsCode
   pyinfra
   
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Wednesday, 16-Feb-2022 07:19:16 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to
     Of course there is also Puppet, Chef, Salt, Nix, NixOps, Guix and a slew of other tools that overlap with various parts of each other and the above.
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Wednesday, 16-Feb-2022 07:56:25 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • kravietz 🦇
     @kravietz I haven't used it enough to say.
   • kravietz 🦇 (kravietz@agora.echelon.pl)'s status on Wednesday, 16-Feb-2022 07:56:26 UTC kravietz 🦇

     in reply to
     @clacke
     
     As talk about #devops configuration management, I use mainly Ansible and Puppet, and the main challenge I have with the former is that if you have a single playbook for the whole infra it takes ages to run it as it's pretty much sequential. Puppet OTOH just picks up the relevant bits through agents, but I'm not the fan of Ruby syntax. Or am I doing something wrong with Ansible?
   • Santa Claes 🇸🇪🇭🇰🎅 (clacke@libranet.de)'s status on Wednesday, 16-Feb-2022 08:17:52 UTC Santa Claes 🇸🇪🇭🇰🎅

     in reply to

     • Björn Lindström
     @bkhl I just expect Python to exist.
   • Björn Lindström (bkhl@mastodon.sdf.org)'s status on Wednesday, 16-Feb-2022 08:17:53 UTC Björn Lindström

     in reply to

     @clacke I just feel like this keeps the main deficit of Ansible which is you get the whole issue if distributing Python in the bargain.

   • cryptix (cryptix@social.coop)'s status on Wednesday, 16-Feb-2022 11:14:23 UTC cryptix

     in reply to

     • kravietz 🦇

     @kravietz @clacke that’s also the critique I heard for ansible. Especially if it’s tried for host provisioning. Though this applies to service/application prov too once the systems get complex enough..

   • kravietz 🦇 (kravietz@agora.echelon.pl)'s status on Thursday, 17-Feb-2022 11:21:34 UTC kravietz 🦇

     in reply to

     • Derek Gurchik

     @gurchik

     OK, so after a bit of reading it seems like the “proper” way of doing #devops using Ansible is:

     • use regular ansible-playbook push from management workstation to deploy any required secrets and anything else that needs ansible-vault
     • anything else that works without ansible-vault can be done using ansible-pull

     This seems quite feasible and I’m going to try it next.

     Santa Claes 🇸🇪🇭🇰🎅 likes this.
   • Derek Gurchik (gurchik@mastodon.social)'s status on Thursday, 17-Feb-2022 11:21:39 UTC Derek Gurchik

     in reply to

     • kravietz 🦇

     @kravietz In general you're right. In *some* cases you can speed it up by using "when" conditionals. For example I have a task that builds a binary and is slow, so I only run the command "when" the binary doesn't exist. But this is a rare situation, 90% of playbooks are copying files or installing packages which are already smart. If you don't like the Puppet syntax, Saltstack uses YAML. But the additional complexity an agent introduces is not great. Thanks for teaching me about ansible-pull.