# In development branch, network modules now available on Galaxy

**URL:** <https://forum.ansible.com/t/in-development-branch-network-modules-now-available-on-galaxy/15984>\
**Category:** Ansible Project\
**Tags:** galaxy-ng\
**Created:** [August 19, 2014, 12:40pm UTC](https://forum.ansible.com/t/in-development-branch-network-modules-now-available-on-galaxy/15984 "2014-08-19T12:40:32Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 19, 2014, 12:40pm UTC](https://forum.ansible.com/t/in-development-branch-network-modules-now-available-on-galaxy/15984/1 "2014-08-19T12:40:32Z")

</div>

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/](https://eos.arista.com/introducing-arista-eos-roles-for-ansible/)

Juniper also has some content:

[https://galaxy.ansible.com/list#/roles/1116](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](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

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 19, 2014, 12:41pm UTC](https://forum.ansible.com/t/in-development-branch-network-modules-now-available-on-galaxy/15984/2 "2014-08-19T12:41:25Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Dave\_Hatton](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@Dave\_Hatton](https://forum.ansible.com/u/Dave_Hatton)\
**Post date:** [August 19, 2014, 1:40pm UTC](https://forum.ansible.com/t/in-development-branch-network-modules-now-available-on-galaxy/15984/3 "2014-08-19T13:40:50Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 19, 2014, 3:54pm UTC](https://forum.ansible.com/t/in-development-branch-network-modules-now-available-on-galaxy/15984/4 "2014-08-19T15:54:30Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![Dave\_Hatton](https://avatars.discourse-cdn.com/v4/letter/d/a88e57/32.png) [@Dave\_Hatton](https://forum.ansible.com/u/Dave_Hatton)\
**Post date:** [August 19, 2014, 3:56pm UTC](https://forum.ansible.com/t/in-development-branch-network-modules-now-available-on-galaxy/15984/5 "2014-08-19T15:56:38Z")

</div>

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