so i take that host from the #ansible playbook specific inventory file and copy it into my fancy new globally specified inventory. while the dedicated inventory file still works, the global one now throws "Failed to connect to the host via ssh: Connection closed by UNKNOWN port 65535" for one of my hosts wtf. The only obvious different thing is that i call a children:
and if I as a non-organizer may add: if you say you'll come, please do. There are typically many no-shows and food has to be thrown away which is dreadful.
I don't think there's a generally correct answer for this question (please refrain from attempting to convince me or others otherwise), rather I'm curious about your own hunch.
Trying to automatically/programmatically replicate #DockerCompose stacks on the same host. E.g. I have an application that requires multiple containers, and I want to replicate the WHOLE application with its own volumes, networks, subdomain, etc. Any pointers on how to do that? #Ansible? Please don't say #Kubernetes.
Are there people among you who have used both(!) #Ansible and #SaltStack personally?
I’m currently using Salt for some of my personal & freelance infrastructure, but it feels like it’s losing the popularity battle, and I think about switching to Ansible.
I usually run Salt agent-less, local-only (config repo cloned to the machine). I assume that’s possible with Ansible, too?
How declarative is Ansible these days? I want to define target states, the system should figure out how to get there.
@scy After 10 years with ansible and 2 with salt: I wouldn’t start anything new with ansible. Though it’s a lot easier at first and the simple (and rigid) structure helps a lot with learning, anything slightly more complex than the examples can lead to ugly workarounds. It’s absolutely great for simple and local stuff, but for anything distributed or complex, I‘d prefer the flexibility of salt. If you are already familiar with salt, I think there is little to be gained by switching to ansible.
Does anyone have a simple idea of using a gopass output as an #ansible vault instead of just as the password TO a vault.
So i'd like to put all variable settings e.g. a yaml into my gopass and include it instead of putting vaults into git repos.
I fail to find a (compatible) way of including variables from script output, or using an external vault application in ansible.
I already use a gopass script to fetch the vaults password, but i feel its a bit clumpsy to maintain a vault in the ansible git, and maintain the vault password in the gopass git.
@jpmens gopass is basically a git/gpg command line based vault. Possible team password management. You can store arbitrary files in there although thought as a keepass similar password manager.
Got it to work with 10 lines of python in a vars plugin.
New customer using user logins + sudo and i am not going to type my sudo password over and over again using their ansible stuff.
My sudo password is in my gopass, and ansible may access it.
Segfault when running the #Ansible apt module to remove wifi and Bluetooth related packages on my raspberry pi. But no problem using the equivalent apt commands. That's weird.
Anyway, this raspberry pi ("pilote") needs to be upgraded (Debian 10 to 12). A perfect time to install it from scratch and use Ansible.
As promised in my talk at #SCaLE, I've done a big refacto of this repository to publish it on github. Soon™ 🤞🏻
There's an interesting discussion happening in the #Ansible forum that we'd like you all to participate in, regarding the future of the Ansible community package (aka what you get if you pip install ansible).
I really wish #ansible module devs would make up their minds about how to pass stuff to it. So like the packages module? Pass it a list of packages, super easy
ansible.builtin.packages:
foo
bar
baz
state: present
But say you want to create a bunch of directories? Well, sucks for you - the file module doesn't work that way:
ansible.builtin.file:
path: "{{item}}"
owner: larted
group: luser
mode: "0755"
state: directory
with_items:
"/haha"
"/fuck"
"/consistency"
And these are both BUILTIN modules. Seriously folks, make up your fucking minds. Shit like this makes being a #sysadmin pointlessly difficult.
Ansible.builtin.packages installs all the packages in one invocation. I.e. it's the equivalent of apt-get install foo bar baz.
Your example with ansible.builtin.file is using a loop construct iterating over a list of directories to create them one by one. The with_items is generic feature of Ansible and not something the file module is implementing. You could do the same when installing packages.
I find it annoying that #ansible#awx is installed using an operator. What are people doing that they would adding or removing AWX instances so that an operator makes sense vs a normal Helm based workflow? What am I missing?
Had to change the config, now I wait for Ansible to run again. I swear to you all I started using Kube and avoiding Ansible for this very reason. #ansible#awx
