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 I accidentally intermingled some unrelated windows changes into this branch. I rolled them back but not sure how to get rid of the history. On Tuesday, April 7, 2015 at 10:17:29 AM UTC-5, Michael Perzel wrote: > > 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 > > and > 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. > > On Friday, March 6, 2015 at 12:36:29 PM UTC-6, Michael Perzel wrote: >> >> 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. >> >> On Friday, March 6, 2015 at 11:56:32 AM UTC-6, Matt Hite wrote: >>> >>> Sorry, I realized I answer your first question but not your second. >>> >>> I have not started work on GTM modules but am open to implementing this >>> for the community. Feel free to share your specific use cases of what you >>> would like to be able to do. >>> >>> On Tue, Mar 3, 2015 at 11:41 AM, Michael Perzel <[email protected]> >>> wrote: >>> >>>> I tested out the 2 pull requests. I successfully was able to set the >>>> session/monitor state for pools/nodes, non-existent nodes/pools etc. One >>>> thing I noticed is that when a node is set to monitor_state=disabled, >>>> session_state=enabled it results in forced offline. Is this intended >>>> behavior? That set of parameters isn't in the table. I need to do more >>>> testing to see how this effects open connections but as for my use case I >>>> think this fixes my issues. >>>> >>>> Has there been any work in looking at a module modifying a GTM? >>>> >>>> Thanks, >>>> >>>> On Tuesday, February 24, 2015 at 8:40:16 PM UTC-6, Matt Hite wrote: >>>>> >>>>> BTW, once I can get some testers on this change, I can incorporate a >>>>> similar one that works on the pool >>>>> -member level. >>>>> >>>>> On Tue, Feb 24, 2015 at 5:19 PM, Matt Hite <[email protected]> >>>>> wrote: >>>>> >>>>>> I've posted a P.R. which needs some volunteers to test. >>>>>> >>>>>> https://github.com/ansible/ansible-modules-extras/pull/282 >>>>>> >>>>>> On Mon, Feb 23, 2015 at 6:08 PM, Matt Hite <[email protected]> >>>>>> wrote: >>>>>> >>>>>>> I'll get a PR up soon to address this. >>>>>>> >>>>>>> On Sun, Feb 22, 2015 at 6:22 AM, Michael Perzel <[email protected] >>>>>>> > wrote: >>>>>>> >>>>>>>> I opened a new issue at https://github.com/ansible/ >>>>>>>> ansible-modules-extras/issues/276 in the correct repository. >>>>>>>> >>>>>>>> I took a look at ansible-module-extra\network\f5\bigip_node.py >>>>>>>> seems like it would make sense to add a couple functions called >>>>>>>> get/set_node_state. They could be invoked from the else statement that >>>>>>>> updates the attributes. I haven't tested this yet but >>>>>>>> https://devcentral.f5.com/questions/bigsuds-how-to- >>>>>>>> enable-disable-certain-pool-members looks like it has the >>>>>>>> necessary code snippet to do this. >>>>>>>> >>>>>>>> On Sunday, February 22, 2015 at 3:37:54 AM UTC-6, Serge van >>>>>>>> Ginderachter wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> On 21 February 2015 at 20:42, Greg Andrews <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Unfortunately, company policy won't let me share an example. I >>>>>>>>>> wanted to indicate the general idea that we set up keys for ssh >>>>>>>>>> access to >>>>>>>>>> our F5 devices and use the Ansible shell module to run "tmsh" >>>>>>>>>> commands in >>>>>>>>>> them. It's not as nice as a full module, but it seemed easier than >>>>>>>>>> the >>>>>>>>>> other API options available to us. >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Ah, ok, I thought you intended to provide an example. No problem. >>>>>>>>> >>>>>>>>> Did you manage to make those ` command: tmsh` somehow idempotent? >>>>>>>>> >>>>>>>>> -- >>>>>>>> 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 [email protected]. >>>>>>>> To post to this group, send email to [email protected]. >>>>>>>> To view this discussion on the web visit >>>>>>>> https://groups.google.com/d/msgid/ansible-project/ >>>>>>>> 7c4dce9a-95fa-402d-bc52-5c1cb859f453%40googlegroups.com >>>>>>>> <https://groups.google.com/d/msgid/ansible-project/7c4dce9a-95fa-402d-bc52-5c1cb859f453%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>>>>> . >>>>>>>> >>>>>>>> For more options, visit https://groups.google.com/d/optout. >>>>>>>> >>>>>>> >>>>>>> >>>>>> >>>>> -- >>>> 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 [email protected]. >>>> To post to this group, send email to [email protected]. >>>> To view this discussion on the web visit >>>> https://groups.google.com/d/msgid/ansible-project/640d1bc4-9697-46ab-a0ac-d81e0c01ea6e%40googlegroups.com >>>> >>>> <https://groups.google.com/d/msgid/ansible-project/640d1bc4-9697-46ab-a0ac-d81e0c01ea6e%40googlegroups.com?utm_medium=email&utm_source=footer> >>>> . >>>> >>>> For more options, visit https://groups.google.com/d/optout. >>>> >>> >>> -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/4207ec24-5e2f-4ed8-b438-4aa2c572de50%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
