In development branch, network modules now available on Galaxy

47 views
Skip to first unread message

Michael DeHaan

unread,
Aug 19, 2014, 8:40:38 AM8/19/14
to ansible...@googlegroups.com
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:


Juniper also has some content:


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:


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



Michael DeHaan

unread,
Aug 19, 2014, 8:41:29 AM8/19/14
to ansible...@googlegroups.com
(Note this does not affect any other modules, such as load balancer modules, which remain as is)


Dave Hatton

unread,
Aug 19, 2014, 9:40:50 AM8/19/14
to ansible...@googlegroups.com
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.

Michael DeHaan

unread,
Aug 19, 2014, 11:54:36 AM8/19/14
to ansible...@googlegroups.com
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




--
You received this message because you are subscribed to the Google Groups "Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/0016b35a-21a2-4fbb-93e2-d67351498e0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Dave Hatton

unread,
Aug 19, 2014, 11:56:38 AM8/19/14
to ansible...@googlegroups.com
I hadn't tried using role more than once. Thanks for the tip.
Reply all
Reply to author
Forward
0 new messages