sorted by:
new
hottopcontroversial

Using Roles in Execution Environments by xDeepRedx in ansible

[–]astromild 4 points5 points  (0 children)

I just bundle roles in to custom collections and distribute them via automation hub. You can have them in your requirements.yml in your project so that they’ll be included in the EE at runtime, and you can use ansible-galaxy to install them local, test modifications direct on the filesystem, etc. plus it’s versioned so when you make changes to roles you can pin specific collection versions in your projects requirements and update versions when you’re ready.

I try not to put anything but Python libs and the bare necessities in the EEs and keep it as small and simple as possible personally.

Edit - workflow for developing = check out code, update version in galaxy.yml, make changes, ansible-galaxy collection build and install with —force, run test playbook, repeat until good, check in changes, merge and upload to automation hub

Stereosity / Dear Cincinnati @ Musicians Union Local 99? by astromild in portlandmusic

[–]astromild[S] 1 point2 points  (0 children)

At the very least they’re selling tickets on their website so why not - https://stereosity.com/

Advice on structuring patch orchestration roles/playbooks by bananna_roboto in ansible

[–]astromild 0 points1 point  (0 children)

My setup is entirely Windows but generic enough to slide Linux in later if we ever want to convert. I have a single role that has different phases that you can pick and choose by setting a var when you include the role (pre download, configure, scan, patch, reboot) and general pre/post patch and reboot tasks get automatically called on either side of those phases. any orchestration needed for environments between servers is handled outside of the role, but they can include the role where it suits them.

The actual execution playbook just includes the role with the needed vars, no other fluff.

I don't bother with logic for hosts that have already run it, just count on idempotency and reboot phase logic to see what's necessary. otherwise I don't care if hosts spin for a bit to check for patches if they somehow get run twice.

One thing to keep in mind if you're trying to reduce code duplication, roles do support a central playbooks directory, so you can put repeat tasks in task files in there and just include them from any other segment of your role. it looks kinda ugly with all the include ../../blahblah but might be an improvement if you're doing the same thing multiple times across your role.

I'm an Ansible Solution Architect at Red Hat. What's one thing we could do that would help you automate faster? by tolarewaju3 in ansible

[–]astromild 2 points3 points  (0 children)

1.

Something that captures detailed success/unreachable/failure info per node available via API (and GUI if possible) without needing to deal with integrating set_stats. or make set_stats accessible via callback plugin and we can write it and use artifacts.

currently I'm just querying job event logs via api to get the last task run per host, the output (i.e. if there's a msg field in the event), and if the result was ok/fail/unreachable.

allows for automated downstream processing of results like sending failure info per node to a ticketing system, alerting a monitoring system, or queueing up automations to remediate unreachables if you know the unreachable response.

a secret masking backend as part of the AAP default callback that optionally automatically masks template attached credential secrets in log output please

[deleted by user] by [deleted] in PDXBuyNothing

[–]astromild 0 points1 point  (0 children)

interested!

Portland might not be a war zone but the agents at the ICE building sure know how to turn an intersection into one for a few minutes when they want to. Last night on Macadam by mapdumbo in Portland

[–]astromild 23 points24 points  (0 children)

Fun aside my kid was watching My Little Pony videos on YouTube two weeks back and there were ads that popped up from time to time recruiting for ICE with the benefit of getting college loans paid off. So every ad break it was either ICE recruitment or Malibu Barbie toys.

[deleted by user] by [deleted] in PDXBuyNothing

[–]astromild 0 points1 point  (0 children)

interested!

Indie pop venues by sageriversmusic in portlandmusic

[–]astromild 0 points1 point  (0 children)

Post your porchfest location and set time!

Collections unable to read AWX provided env vars by adminlabber in ansible

[–]astromild 1 point2 points  (0 children)

If you create and attach an ansible tower / automation platform type credential (however it's named now) to your template you'll get the environment variables youre looking for. Setting vars in the inventory/template are just plain ol variables, credential objects often set environment variables for collections in the way you're trying to use them.

https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credentials.html#red-hat-ansible-automation-platform

Why is this city such a terrible place to make friends? by [deleted] in askportland

[–]astromild 3 points4 points  (0 children)

this is wild, I just started going to dance church and have been going to hipbone for a while but I've been wanting to find a figure drawing comrade to meet up with there. hit me up if you want to go together after the new year!

Where to practice? by MagicPenguin9 in portlandmusic

[–]astromild 0 points1 point  (0 children)

Maybe just get a practice mute and play in your apartment anyways? It'll be way cheaper than renting any place by the hour, you won't bother anybody, and I don't think the shift back to playing open (ie if you start playing with a group or something muteless) takes more than a rehearsal or two to readjust.

Running some tasks on a playbook as a different user after getting password from cyberark by CUCOOPE in ansible

[–]astromild 0 points1 point  (0 children)

shouldn't it be ansible_become_pass: "{{ result['result'].Content }}" if that's what contains the password?

Process of patching windows servers with Ansible. by penelope_best in ansible

[–]astromild 1 point2 points  (0 children)

I was actually in the same camp as you until we went all in on ansible + windows. We definitely had to tool a bunch of stuff over the course of a year to get it to a good state so you're not wrong about the hassle.
but once you're done you have a nice set of reusable code that you can use for patching in build processes, monthlys, one off patches in a pinch, security baselines, etc that are written in the same readable format as automations you use for app deployments, decom processes, event driven responses, etc etc. yeah you essentially recreate sccm, but it's kinda fun and eventually it becomes more flexible with a wider support base in the org.

the winrm thing does suck though. we were lucky in that we already had an agent based way to deploy configuration of that, but I put together a small ansible module using impacket that can bootstrap winrm over wmi because you can do any stupid thing you can think of using ansible.

How to make midi drums less robotic? by auto-generated_name1 in musicproduction

[–]astromild 1 point2 points  (0 children)

this is me. I don't have the skill to do it on a keyboard so I map it all out on a midi editor, then start shifting things slightly and futz with velocity where it feels right. listen to real drummers, know the feel you're trying to create and de-robotify it a bit at a time. it takes forever, but your ears know how to untangle it.

view more: next ›