# F5 disable pool/node

**URL:** <https://forum.ansible.com/t/f5-disable-pool-node/17577>\
**Category:** Ansible Project\
**Created:** [February 20, 2015, 4:47pm UTC](https://forum.ansible.com/t/f5-disable-pool-node/17577 "2015-02-20T16:47:54Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Michael\_Perzel](https://avatars.discourse-cdn.com/v4/letter/m/8491ac/32.png) [@Michael\_Perzel](https://forum.ansible.com/u/Michael_Perzel)\
**Post date:** [March 6, 2015, 6:36pm UTC](https://forum.ansible.com/t/f5-disable-pool-node/17577/21 "2015-03-06T18:36:29Z")

</div>

I’m still in the preliminary phase of developing requirements. From a high level we have multiple datacenters and use the GTM to route traffic (round-robin by default but during maintenance we may “pin” traffic to one datacenter). I should have more specifics in a few weeks.

I’ve been reading up on the bigsuds api and would be more than willing to help develop this.

---

<div class="post-metadata">

**Author:** ![Matt\_Hite](https://avatars.discourse-cdn.com/v4/letter/m/5fc32e/32.png) [@Matt\_Hite](https://forum.ansible.com/u/Matt_Hite)\
**Post date:** [March 12, 2015, 3:42am UTC](https://forum.ansible.com/t/f5-disable-pool-node/17577/22 "2015-03-12T03:42:43Z")

</div>

BTW, if you don’t mind – for those of you who have tested this, please comment on the pull requests so Brian knows it works as intended.

[https://github.com/ansible/ansible-modules-extras/pull/288](https://github.com/ansible/ansible-modules-extras/pull/288)

[https://github.com/ansible/ansible-modules-extras/pull/282](https://github.com/ansible/ansible-modules-extras/pull/282)

Thanks,

-M

---

<div class="post-metadata">

**Author:** ![Michael\_Perzel](https://avatars.discourse-cdn.com/v4/letter/m/8491ac/32.png) [@Michael\_Perzel](https://forum.ansible.com/u/Michael_Perzel)\
**Post date:** [April 7, 2015, 3:17pm UTC](https://forum.ansible.com/t/f5-disable-pool-node/17577/23 "2015-04-07T15:17:29Z")

</div>

I am going to start putting some effort into automating our GTM updates now.

Our basic process is:

- Confirm pools are reporting up
- Then going to DNS\>GSLB and swapping what pools are a member of a particular fqdn.

DevCentral has a couple examples: [https://devcentral.f5.com/wiki/iControl.python-bigsuds-Get-or-Set-GTM-Pool-TTL.ashx](https://devcentral.f5.com/wiki/iControl.python-bigsuds-Get-or-Set-GTM-Pool-TTL.ashx) and [https://devcentral.f5.com/wiki/iControl.python-bigsuds-Get-GTM-Pool-Status.ashx](https://devcentral.f5.com/wiki/iControl.python-bigsuds-Get-GTM-Pool-Status.ashx)

Seems relatively straightforward. I was thinking for a first step, a module that can get the GTM status and set the member pools would be good. Let me know if you are still interested in taking a look at this or I can put together a initial module as well.

---

<div class="post-metadata">

**Author:** ![Michael\_Perzel](https://avatars.discourse-cdn.com/v4/letter/m/8491ac/32.png) [@Michael\_Perzel](https://forum.ansible.com/u/Michael_Perzel)\
**Post date:** [May 29, 2015, 5:22pm UTC](https://forum.ansible.com/t/f5-disable-pool-node/17577/24 "2015-05-29T17:22:30Z")

</div>

Not sure if anyone is still monitoring this thread but I submitted a pull request for this functionality. As time is available, I’d like to keep adding features even though I’ve got everything I personally need now.

[https://github.com/ansible/ansible-modules-extras/pull/551/files](https://github.com/ansible/ansible-modules-extras/pull/551/files)

I accidentally intermingled some unrelated windows changes into this branch. I rolled them back but not sure how to get rid of the history.

[Previous page](https://forum.ansible.com/t/f5-disable-pool-node/17577.md?page=1)