Does anyone have an questions about F5 iWorkflow?

Great question, Yann. We started developing our orchestration and integration features and services as part of BIG-IQ - specifically, as the BIG-IQ "Cloud" module, which you mentioned. We have since spilt this functionality out form BIG-IQ, we've added considerably more extensibility/programmability to it, and now we've announced that it will be released separately as the F5 iWorkflow platform. This will be where we focus Programmability & Orchestration (P&O hereafter). Why? Unlike traditional device management system, iWorkflow is policy-centric and presents an integration point for Management and Orchestrations systems, including SDN Controllers. It serves a different set of use case from that of BIG-IQ Centralized Management. Hence, it made sense to separate. iWorkflow support infrastructure integrations with SDN controllers and infrastructure management solutions, in addition to DevOps tools like Chef, Puppet, and Ansible, to name just a few. You can read more about the product split here: https://devcentral.f5.com/articles/the-intrinsic-asymmetric-division-of-big-iq I hope that answers your question sufficiently! Best regards, Nathan