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] > <javascript:>> 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] >> <javascript:>> wrote: >> >>> I'll get a PR up soon to address this. >>> >>> On Sun, Feb 22, 2015 at 6:22 AM, Michael Perzel <[email protected] >>> <javascript:>> 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] <javascript:>. >>>> To post to this group, send email to [email protected] >>>> <javascript:>. >>>> 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. For more options, visit https://groups.google.com/d/optout.
