# Getting cl\_prefix\_check included in Ansible

**URL:** <https://forum.ansible.com/t/getting-cl-prefix-check-included-in-ansible/16863>\
**Category:** Ansible Developer\
**Created:** [November 24, 2014, 3:51pm UTC](https://forum.ansible.com/t/getting-cl-prefix-check-included-in-ansible/16863 "2014-11-24T15:51:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Sean\_Cavanaugh](https://avatars.discourse-cdn.com/v4/letter/s/e68b1a/32.png) [@Sean\_Cavanaugh](https://forum.ansible.com/u/Sean_Cavanaugh)\
**Post date:** [November 24, 2014, 3:51pm UTC](https://forum.ansible.com/t/getting-cl-prefix-check-included-in-ansible/16863/1 "2014-11-24T15:51:36Z")

</div>

Hey Ansible Dev Team. Awhile ago Stanley and I at Cumulus created a bunch of modules. I think the first one that has no dependencies on Cumulus Linux (as in it will work on any Linux distro that has the ip route command) is finished. Right now its located at [https://github.com/CumulusNetworks/cumulus-linux-ansible-modules/blob/master/library/cl\_prefix\_check](https://github.com/CumulusNetworks/cumulus-linux-ansible-modules/blob/master/library/cl_prefix_check)

I suggest (based on feedback from others) that we rename it prefix\_check. I don’t care what the name is as long as it gets pushed into main. This module allows me to check routes easily (if they are present or absent) and adds the ability of a timeout to give their route table to remove or add the route based on the user’s desired outcome. This was based on our distro (Cumulus Linux) running Quagga but this module is not dependent on our distro, or quagga. A user could make changes with static routes or any route engine (Quagga, Bird, etc). This gives Ansible the ability to check route changes on a live change and now not only can Ansible provision the network, it can now move traffic around like a controller.

My question is what do I have to do to get to the next phase? How do I push this into main the correct way. Reading [http://docs.ansible.com/developing\_modules.html#getting-your-module-into-ansible](http://docs.ansible.com/developing_modules.html#getting-your-module-into-ansible) suggested I email this list 🙂

Thanks!

-Sean Cavanaugh  
Cumulus Networks

---

<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:** [November 24, 2014, 10:52pm UTC](https://forum.ansible.com/t/getting-cl-prefix-check-included-in-ansible/16863/2 "2014-11-24T22:52:22Z")

</div>

Hi Sean,

We no longer include switch management modules in core ansible (because it’s something the vendors can maintain better than us, and it sometimes gets weird), but we would encourage you to submit this to Galaxy.

In doing so, I’d recommend registering an Ansible Galaxy account called “CumulusLinux” or whatever, and then we’re going to have a “showcase” page soon that highlights some interesting vendor and non-vendor modules that will make these super easy to find.

(Note that we’ve also removed modules of some other hardware vendors in the routing/switching category that used to be in core - we’ll continue to include load balancer stuff like F5, A10, etc, as those are a bit different of a use case).

Still very glad to see this!