Hello my friend,
as you know, Ansible is one of the leading tools for the automation of the IT and network infrastructure. We have written a lot about it earlier (e.g. CLI configs, OpenConfig with NETCONF, or VNF-M). Recently Red Hat announced the new version of Ansible (Ansible 2.10), which changes a lot the way we used to work with that.
No part of this blogpost could be reproduced, stored in a
retrieval system, or transmitted in any form or by any
means, electronic, mechanical or photocopying, recording,
or otherwise, for commercial purposes without the
prior permission of the author.
Eager to learn about network automation?
We are here to help you. At our network automation training you learn all you need to know to be successful with such tasks in your profession:
- Linux, Docker, KVM
- YANG models
- JSON, XML, Protocol Buffers (Protobuf) data formats
- SSH, REST API, gRPC transport
- gNMI, NETCONF, RESTCONF protocols
- How to use and manage everything above with Ansible, Bash, and Python
What that is about
Ansible 2.10 is more than a just another Ansible’s update. It is a new approach, paradigm shift, if you like in the way of packaging, distributing and controlling Ansible core part and extended modules. In the webinar we covers the root cause for that, followed by the explanation what exactly has changed and how that affects your network automation playbooks.
The presentation used during the webinar is available for you. You can use it as an example or guideline to start the transition towards Ansible 2.10.
You can enjoy the video recording in our YouTube channel. Post comments and share in your social medias, if you like it, please.
The changes are unavoidable part of the development of any tool. Beware about them and you will always have the best tools available for your networks. Stay tuned. Take care and good bye.
If you have further questions or you need help with your networks, I’m happy to assist you, just send me message. Also don’t forget to share the article on your social media, if you like it.