# New module idea brainstorming

**URL:** <https://forum.ansible.com/t/new-module-idea-brainstorming/12828>\
**Category:** Ansible Project\
**Created:** [May 19, 2013, 2:01pm UTC](https://forum.ansible.com/t/new-module-idea-brainstorming/12828 "2013-05-19T14:01:26Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![David\_Golden](https://avatars.discourse-cdn.com/v4/letter/d/d2c977/32.png) [@David\_Golden](https://forum.ansible.com/u/David_Golden)\
**Post date:** [May 21, 2013, 3:20pm UTC](https://forum.ansible.com/t/new-module-idea-brainstorming/12828/21 "2013-05-21T15:20:23Z")

</div>

You _can_, but it would be nice not not have to do that for one or two packages. My hack has been to set a ‘creates’ on a file that the package installs. That doesn’t help for versioning, but it avoid repetitive installs.

David

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [May 21, 2013, 4:18pm UTC](https://forum.ansible.com/t/new-module-idea-brainstorming/12828/22 "2013-05-21T16:18:31Z")

</div>

yum can still take filesystem paths though.

---

<div class="post-metadata">

**Author:** ![Edgars](https://avatars.discourse-cdn.com/v4/letter/e/f17d59/32.png) [@Edgars](https://forum.ansible.com/u/Edgars)\
**Post date:** [May 23, 2013, 1:49pm UTC](https://forum.ansible.com/t/new-module-idea-brainstorming/12828/23 "2013-05-23T13:49:59Z")

</div>

Regarding Cisco, I found that Puppet already has this functionality:

[https://puppetlabs.com/blog/puppet-network-device-management/](https://puppetlabs.com/blog/puppet-network-device-management/)

Edgars

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan2](https://avatars.discourse-cdn.com/v4/letter/m/da6949/32.png) [@Michael\_DeHaan2](https://forum.ansible.com/u/Michael_DeHaan2)\
**Post date:** [May 23, 2013, 1:57pm UTC](https://forum.ansible.com/t/new-module-idea-brainstorming/12828/24 "2013-05-23T13:57:16Z")

</div>

Cisco hardware is generally difficult because it comes in difficult flavors (Catalyst, Nexus, etc) and doesn’t have a lot of strong APIs.

These modules don’t seem to be well received:

[http://www.scottyob.com/2012/12/08/my-experiences-of-managing-a-cisco-switch-with-puppet/](http://www.scottyob.com/2012/12/08/my-experiences-of-managing-a-cisco-switch-with-puppet/)

That all being said, I’d like to not discuss other CM tools too much on this list, as a professional courtesy.

[Previous page](https://forum.ansible.com/t/new-module-idea-brainstorming/12828.md?page=1)
