iControl 11.3 SDK

We are still in the process of publishing it. I've got the client libraries completed but there's like 1000+ new methods so it's taken some time to get the wiki documentation worked out and didn't want to publicize anything until that happened. I'll see if I can get the SDK .zip file uploaded that contains the offline docs and wsdl files tomorrow to get you started. BTW, what are you doing with the WSDL files? Are they for a language import?

 

-Joe

 

Thanks Joe. I actually downloaded the WSDL files from my LTM running 11.3. They are in /usr/local/www/iControl/wsdl/. Looking forward to the actual SDK, what a mess 11.X has made of iControl :) Hopefully it will all be worth it!

 

-Derek

 

I'll work on getting it published as soon as possible. What do you mean by a "mess"? Would love to hear any and all feedback you have.

 

-Joe

 

By mess I mean retiring iControl methods that have worked from 9.0 - 10.2. It's like F5 decided to completely re-do iControl in 11.x.

 

 

Now we have iControl/LocalLB/NATv2, NodeAddressv2, etc. We have lots of methods that were depricated as of 11.0 so ... a mess if you're trying to support v9, v10 and v11 of iControl. I'm not saying progress is bad, but right now iControl in v11 seems a bit crazy. From v11.0 to v11.3 there are significant changes, etc. It seems like iControl in v11 is in a state of constant flux. Like I said, hope it's worth it! If the end result is something more elegant and well refined that will last up to TMOS 14.x then maybe it's worth the pain.

 

 

All of the *V2 interfaces were created due to underlying changes in the way objects are defined. We strive to maintain backward/forward compatibility but there are some situations where the product changes and the API just doesn't work the same way.

 

Our deprecation policy is to allow for "at least" one year after a method has been deprecated that it still be supported in the product. In most cases, we have to do a bunch of hoops and assumptions under the seems to tie the old versions to the new underlying implementation. As far as I know, aside from when we did a full flush of our APIs to v9, the deprecated methods are still in there. That's not to say they won't go away, but that they might. We recommend you migrate to the new interfaces when you can and when it makes sense.

 

Sorry for your frustration but we do do our best to make it so you can use a common API across all our software versions - which isn't an easy task.

 

BTW, I just pushed out the iControl 11.3 API references along with the .Net and Java libs to the iControl Assembly labs project!

 

-Joe

 

Thanks Joe! iControl has been very good at not changing too much over the years, and with all the new stuff under the hood in v11 I can see why the new methods needed to be implemented. Over all I've been pretty impressed with iControl, so don't let my teeny frustrations with v11 get you down :)

 

 

-Derek