In development branch, network modules now available on Galaxy

Archives Ansible Project
1

Hi folks,

As I mentioned previously to allow network hardware vendors to more easily manage their own content, we’re going to be hosting things moving forward for these vendors on Galaxy.

Here’s a blog about Arista’s modules, which used to be part of core in 1.7.X and before:

https://eos.arista.com/introducing-arista-eos-roles-for-ansible/

Juniper also has some content:

https://galaxy.ansible.com/list#/roles/1116

Addtionally, Cumulus does not require modules for writing config files and such, so there are no roles yet, but we’re doing a webinar about Cumulus soon:

http://go.cumulusnetworks.com/Ansible-Cumulus

In any event, there are now some nice new additions on Galaxy and thanks for everyone involved. Let me know if there are questions!

Thanks,

–Michael

2

(Note this does not affect any other modules, such as load balancer modules, which remain as is)

3

If I read this correctly, one executes the eos role first to make the modules contained in the role available to the playbook?

Would it make sense to introduce a specific keyword for this as opposed to the generic role?

This would clearly delineate this new roles which provide modules whilst allowing the use of the roles within the palybook?
(A bit like pre_tasks and post_tasks)

initialization_role:
support_role:

or something similar.

4

A new language keyword for ansible is not required.

You could have a comment in your YAML though

bring in arista modules

  • { role: arista.eos }

do stuff

  • { role: stuff }

etc

5

I hadn’t tried using role more than once. Thanks for the tip.