pycontrolv2 is not working

I forgot to address your last question: The reason why we don't include the WSDLs is that it's brittle and could break forward or backward compatibility. We ran into this the first time around and the choice of a 'pure' proxy implementation with some decent caching is one of several reasons why we went with Suds. There's room to debate this - for example, our .Net and Java implementations use generated classes and don't parse the WSDLs on load. The downside is here is that you've generated classes against a specific version of WSDL, and you need to remember to upgrade if we change our WSDLs on the BigIP (e.g. the many additions to 10.1 WSDLs).

 

 

With a pure proxy this is never an issue. Just use fromurl=True and pull down the WSDLs from the source. For me, this made a bunch of sense.

 

 

PS: There's been much talk of pickling suds clients on the Suds list. This is currently on the roadmap but Python's pickle mechanism doesn't make this particularly easy and the Suds author has to make substantial changes to get it working properly. When this finally happens it's absolutely ideal: Create yoru clients and pickle them onto disk.

 

 

-Matt