I think that we are talking about insurance policies that make you install an app on your phone directly. The app publishes directly to the Internet.
jaxxed
joined 1 year ago
I thought that there might be a way to a custom facts (gather_facts) to all machines, and indicate leader/joiner status there, but I can't get the data to stick.
sounds like the same idea. So you use run_once on a task?
Let me try to reword it to make it clear.
I have 3 machines in my group. 1 of those will be the "leader". The others will be "joiners". The leader could already be initialized, so I need to check all machines to see if there is a leader already. If no Leader exists then any of the machines will do (the first) All of the machines that will join will need some data from the leader, so there will be a role task that will be delegated to the leader (ansible needs to know which host is the leader so as to be able to delegate to it)
This may sound complex but it is a very common pattern for distributed application setup.
idempotency doesn't play a role in this behaviour - the machines are all unique, but who knows what may have changed between ansible runs.
Is it ostree based? I guess I should RTM
That idea leads to Authoritarians getting charges put on their opponents.
If the Biden campaign thought that hish payment felonies were going to cost Trump the election, then they haven't been paying attention for the last 10 years
Or, you know, maybe the kid shouldn't have had a firearm. He clearly had no respect for them.
He gets to blame it on the Israelis.
Toronto suburb I lived in had a no outdoor cats rule. Massive changes uears later, all the way up to increases in rabbits, deer, and coyotes.
I'm quite fond of my fbsd laptop. Wifi is a bit clunky, but it never bothered me. Full wayland-niri desktop works well, and there are pretty cool virtualization features.
The whole thread is full of them.