Crypto.com is hiring Java Developer (Mid to Senior)
#java #springframework #cryptocurrency #ansible #aws #kafka #kubernetes #sql #seniorengineer
Bangalore, India
Full-time
Crypto.com
Job details https://jobsfordevelopers.com/jobs/java-developer-mid-to-senior-at-crypto-com-mar-12-2024-3e3f95?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
#Ansible's decision to use Jinja in values only, and not render the YAML itself through Jinja (like Salt does) might make some things a bit more clean, but it also makes a _lot_ of things significantly more difficult. 
OK, this seems to be the python that Ansible is using. Being called directly without all the PATH mangling that the .ansible-wrapped script does. Which explains why it does not find the kubernetes module...
(Thanks @darix for the hint)
Running the playbook with -v shows me that it is using a completely different python3 from /nix/store/lhpwdis5hkyljz1d200bj1s6g51ljq9k-python3-3.12.8/bin/python3 which does not have the kubernetes module apparently.
No idea how it picks this up, where it takes that information from and how to fix this...
Hardcoding a nix path, even it is just ~/.nix-profile/bin/python3, is of course not feasible if the code is being used on other machines where this is not guaranteed to exist (as outlined in the answers yesterday).
What am I missing?
Fourth and hopefully last round for the #NixOS #Ansible bubble:
Short recap: Having the kubernetes module in the ansible derivation/package is not enough, it needs to also be in the python3 or python312 derivation/package.
Fun fact:
- `which python3` gives me /home/tux.penguin/.nix-profile/bin/python3
- this links to /nix/store/ipwx571dlhxmdf1n1yd8vgqq5ndjnxba-python3-3.12.8-env/bin/python3
- `which -a python3` only gives me this one python, no other binaries found in the PATH with that name
1. Using /nix/store/ipwx571dlhxmdf1n1yd8vgqq5ndjnxba-python3-3.12.8-env/bin/python3 as ansible_python_interpreter works, the kubernetes module is found
2. Using /home/tux.penguin/.nix-profile/bin/python3 for ansible_python_interpreter works
3. Using "{{ lookup('env','HOME') }}/.nix-profile/bin/python3" for ansible_python_interpreter works
4. Using just python3 DOES NOT work?!?!? What the hell? Even if this is resolved (in the shell at least) to the same python3 binary/link in ~/.nix-profile/bin/python3? What the hell?
Third round for the #NixOS #Ansible bubble:
I think I have a solution! At least I got some thing working.
Having the python312 nixpkg installed is not enough. It is also not enough to have python312, python312Packages.kubernetes and python312Packages.cryptography installed.
I had to install them "in the same package":
```
home.packages = with pkgs; [
ansible
ansible-lint
(pkgs.python3.withPackages (python-pkgs: [
python-pkgs.cryptography
python-pkgs.kubernetes
]))
];
```
Then I could set the ansible_python_interpreter to `python3` and could use the kubernetes python module for using things from the kubernetes.core Ansible collection.
This is in addition to having the modules also available in the ansible derivation, no idea if that is really necessary.
I'll do some more digging and testing, but at least something worked now! I call that a win!
Second round for the #NixOS #Ansible bubble:
With lots of help I now have a Ansible derivation that includes python modules for requirements from e.g. the kubernetes.core Ansible collection.
But things still do not work. Example: Creating something in a Kubernetes cluster using the kubernetes.core collection. No matter whether I target localhost in my playbook or the remote host with a delegate_to for localhost.
Ansible uses the installed python directly, but without all the module-including-voodoo that is done in the .ansible-wrapped file (that is being called when "ansible" is being invoked". And thus the kubernetes module is not found.
I also tried installing python3 and python3Packages.kubernetes in addition to ansible. I see the kubernetes in $HOME/.nix-profile/lib/python3.12/site-packages/, but it is still not found. I tried telling Ansible that localhost has a python interpreter, but no change.
Frustrating...
Fun question for the #NixOS #Ansible bubble:
I noticed that Ansible on NixOS does not find python modules that have been installed from NixPkgs. This means, modules like the kubernetes module are not found and Ansible cannot do its work, when a task is executed on localhost (e.g. via delegate_to)
Is there a way to install those additional modules together with the Ansible package?
Or is this just some messup with autodetecting the python interpreter on localhost?
Lambda is hiring Post Sales Machine Learning Engineer
#ansible #docker #machinelearning San Francisco, California Full-time Lambda
Job details https://jobsfordevelopers.com/jobs/post-sales-machine-learning-engineer-at-lambdalabs-com-oct-22-2024-15c2d2?utm_source=mastodon.world&utm_medium=social&utm_campaign=posting
#jobalert #jobsearch #hiring
In today's exercise in bravery/silliness, I'm going to complete reconfigure the gateway via #ansible.
Lately, I've just been running single updates:
ansible-playbook gateway.yml --tags=pf
Today, the tags are coming off. All the updates.
ansible-playbook gateway.yml
The @tailscale folks have some excellent YT videos on setting up self-hosted servers on Digital Ocean using Terraform, Ansible, and of course, Tailscale. I just got my first Droplet running.
Part 1 - Getting started with cloud-init: https://youtu.be/e-X5FJwrkaA?si=t3iLP-k9B4SmDAMp
Part 2 - Terraform: https://youtu.be/PEoMmZOj6Cg?si=2IwHCw4HuIa71YFZ
Part 3 - Ansible: https://youtu.be/k5Xgt31yK2U?si=28MPbwmiIOB-18nv
Just a big shoutout to #Ansible and #AWX for being able to manage a AWX instance using Ansible.
The instance is running in #Kubernetes, managed by #ArgoCD. But the inner configuration of AWX (LDAP, Teams, Organisations, Permissions, Templates, Projects, Inventories, Credentials) needs to be managed,too. That is where Ansible comes in.
Next week I will once again have a AWX instance that manages itself by running a job on AWX. Nice, eh?
Dear #AWX users out there (AWX as in Ansible, not AWS as in Amazon...),
does anyone have good pointers on connecting AWX and #Hashicorp #Vault / #OpenBoa **without** having to define each secret/credential again in AWX?
I have set up a basic connection according to the documentation: https://ansible.readthedocs.io/projects/awx/en/24.6.1/userguide/credential_plugins.html#ug-credentials-hashivault
And I have created a credential using that lookup and could successfully output its value in a playbook run in AWX.
But having to define a AWX credential for each secret that I need to pull from Vault/OpenBoa sounds like a lot of unnecessary duplication.
(Yes, I know you can manage AWX via Ansible. We do that already. But still, you need to define the credentials in your code somewhere for the automation to create it in AWX)
AAP 2.5 using config-as-cod/cac how to structure multiple org project/How to to run
https://www.redhat.com/en/blog/ansible-automation-controller-cac-gitops
Discussions: https://discu.eu/q/https://www.redhat.com/en/blog/ansible-automation-controller-cac-gitops
I'm new to #k8s and am wondering how to handle templating large amounts of config files. I couldn't find anything super useful in my search so I have an #Ansible sidecar I run to generate the kustomizations and config files. My most recent Ansible change was 30 lines, it resulted in changing 5,000 lines of YAML which will further be fed to Kustomize.
There has to be a better way?
I've heard about Helm, Yoke, KRO, and using an operator pattern. My understanding of those options is:
* Helm - My Org recommends avoiding (I don't know why)
* KRO - Not stable, but FFS neither is Kustomize
* Yoke - Almost kinda operator pattern
* Operator Pattern - This feels like reinventing a fucking config manager (ala #Ansible, #Puppet, #Chef, #Saltstack) for every fucking project. What new hell this is.
I'm hoping I'm missing something because the only workable flow for this workload is:
1) Create ansible roles/playbook to generate the kustomization.yaml and resources
2) Generate those kustomizations, check them into git
3) Use Kustomize via GitOps to expand the YAML even more
4) Push a metric fuckton of YAML to production
I'm losing my mind over here.
OK, today I took some time and finally reworked the #semaphoreui package for @opensuse. I had it on my todo list for ages and never got around to it. It was already 90% finished but lacking some fine details.
Now I have properly cleaned it up and removed the "ansible-" from the name, as it is no longer just for executing #Ansible code. Apparently Semaphore can now execute #terraform #opentofu and #pulumi code as well.
I'll do more testing before I send it to #Tumbleweed.
In other words: new vagrant-libvirt setup incoming! :-)
Stay tuned.
Red Hat has been named to Fast Company’s annual list of the World’s Most Innovative Companies of 2025! Red Hat is ranked #15 in the enterprise category.
https://www.fastcompany.com/91269402/enterprise-most-innovative-companies-2025
