🎄 Happy Holidays! 🥳
Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.
Happy Holidays!
Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.
Using Ansible to Automate the Configuration of Solace PubSub+ Event Broker
Are you responsible for Solace PubSub+ DevOps?
Using Ansible modules for PubSub+ may make your life easier … check out this blog post
https://solace.com/blog/using-ansible-automate-config-pubsub-plus/
Comments
-
@swenhelge Thank you for sharing this!
0 -
Thanks @swenhelge, I had no idea this existed!
0 -
@marc - but wait there's more - even including a cat pic: https://solace.community/discussion/389/event-mess-to-event-mesh-automating-the-configuration-of-a-hybrid-iot-event-mesh-with-ansible#latest
2 -
hi @Joy - rollback is not a concept that ansible supports directly. I.e. ansible does not keep state of before and after.
So, what I typically do is to manage state manually. roughly:- you create a separate parameters yaml / json file that describes a state - let's call it 'state1.yml'
- you run your playbook with state1.yml ==> broker is configured with state1 parameters
- you apply state2.yml and then you realize you want to go back to 'state1.yml'
- you run the playbook again with state1.yml ==> rollback done.
I usually only work with roll-forward, never with roll-back. otherwise you end up with a management challenge of your state files.
3
