Is anyone from PL able to shed any light on the below issues??? Cheers Gavin
On Wednesday, 24 July 2013 12:00:54 UTC+1, Gavin Williams wrote: > > Balto > > Apologies, my previous response may have been misleading... On further > investigation, I can confirm that basic device connectivity and fact > gathering works, however I am also unable to actually do anything with the > F5 device... > > Whilst Puppet reports that the resource actions are happening, nothing is > happening with the device... > > In an attempt to debug further, I've swapped out the v10 Gem with a v11 > Gem, and also enabled MCP Audit logging on one of our test F5 devices... > I did have to make a slight tweak to device.rb, as defined > here<https://gist.github.com/fatmcgav/6069595#file-device-rb> > . > > I'm attempting to use the 'f5_rule' resource as defined in the > puppetlabs-f5 Readme examples. > I can now see Puppet handshaking with the F5, requesting all the fact > information, and getting to the Rules... > > An example log of this is: > https://gist.github.com/fatmcgav/6069595#file-f5-debug-log > The 'get_list' call works as expected, however the 'create' call is > missing information... > > Compare the above log, to an example from a simple test client I knocked > up to add a rule: > https://gist.github.com/fatmcgav/6069595#file-f5-test-client-debug-log > The important changes there are on Lines 6 & 7. These are the values of > the rules construct that was passed through to from the client... > > {"rule_name" => "Demo3", "rule_definition" => "when HTTP_REQUEST {}"} >> > > At this point, I'm at a complete loss as to why the Puppet call isn't > working, but an identical call from a test client is... It appears that > somewhere between Puppet invoking the 'transport[wsdl].create([rule])' and > the command reaching the F5, the contents of '[rule]' are lost... > > Balto: Are you able to provide details of the ticket raised by Puppet for > supporting Puppet 3.x? > > Cheers > Gavin > > On Tuesday, 23 July 2013 19:22:53 UTC+1, Balto Star wrote: >> >> Not sure how you got it to work. We had zero success getting >> puppetlabs-f5 module working with Puppet 3.2.x. We debugged down into the >> ruby libs but with no success. Next we contacted puppet labs support and >> they set it up in their lab and concluded that puppetlabs-f5 is not >> supported beyond puppet 2.7.x. There is an open ticket to upgrade to Puppet >> 3.x but no ETA as of yet. >> >> >> On Tuesday, July 23, 2013 8:20:11 AM UTC-7, Gavin Williams wrote: >>> >>> Balto >>> >>> I must admit that since posting, I've had very little time to spend on >>> updating the Puppetlabs-F5 module to support the full v11 functionality... >>> >>> However I'm intrigued by your problem description - AFAIK there should >>> be nothing stopping the puppetlabs-f5 module working with Puppet > 2.7, and >>> for that matter I've successfully tested some of the basic functionality >>> with a 3.1 Master... >>> >>> Regards >>> Gavin >>> >>> On Tuesday, 23 July 2013 03:07:17 UTC+1, Balto Star wrote: >>>> >>>> Gavin, Josh : Has the effort to update the puppetlabs-f5 module to >>>> support f5 v11 devices gained any traction ? >>>> >>>> I am working with BIG-IP 10.2.4 Build 577.0 Final , and found out the >>>> hard way that puppetlabs-f5 module is not supported beyond Puppet v2.7.22 >>>> >>>> I am now doing a POC for puppetlabs-f5 module based on a Puppet v2.7.22 >>>> master/agent server. I got some basic stuff working but it's been >>>> difficult to find good docs on how to configure the vast array of f5 >>>> functionality. Additionally, I have been unable to locate anyone in the >>>> community who is working with puppetlabs-f5 module in production. >>>> >>>> Thanks for any info. >>>> >>>> >>>> On Saturday, April 27, 2013 7:44:33 PM UTC-7, JoshBeci wrote: >>>>> >>>>> Hi Gavin, >>>>> >>>>> I'll offer assistance with testing and some code where I can. >>>>> I'm still getting up to speed with Puppet but we also have a need to >>>>> have Puppet working with our V11 devices, also. >>>>> >>>>> Thanks, >>>>> Josh Becigneul >>>>> >>>>> On Tuesday, April 23, 2013 7:36:10 AM UTC-4, Gavin Williams wrote: >>>>>> >>>>>> Afternoon all, >>>>>> >>>>>> I thought I'd drop an email here just to get peoples views/opinions >>>>>> etc... >>>>>> >>>>>> Anyhow, I'm about to need to Puppetize our F5 v11 devices, >>>>>> specifically the iApp functionality. >>>>>> Now currently, the Puppetlabs-F5 module primarily supports v10 >>>>>> devices... >>>>>> >>>>>> Now I'm happy to work on adding support for V11, however just wanted >>>>>> to check that there wasn't anything already in progress, etc... >>>>>> Also wanted to check what is considered to be the best method to add >>>>>> v11 support... >>>>>> >>>>>> My current thought is to add 'confine: ' to the existing providers >>>>>> based on the F5 operatingsystemrelease fact, and then create new >>>>>> providers >>>>>> for v11... >>>>>> >>>>>> Thoughts? >>>>>> >>>>>> Cheers >>>>>> Gavin >>>>>> >>>>> -- You received this message because you are subscribed to the Google Groups "Puppet Developers" 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]. Visit this group at http://groups.google.com/group/puppet-dev. For more options, visit https://groups.google.com/groups/opt_out.
