If you’re looking to understand what all the noise is about, here are some links to help get you started:
The iWorkflow Wiki home page
This is where we will post all of the API documentation and example code to help you achieve new levels of programmable infrastructure driven automation and orchestration. DevCentral - An F5 Technical Community
iWorkflow 101 Series
The first episode titled “The Architecture Explained” has been posted. Read this to understand the various elements that will help you speed application deployments, simplify architecture, and reduce exposure to operational risk. DevCentral - An F5 Technical Community
Any other questions? Please don’t hesitate to ask!
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: The intrinsic asymmetric division of BIG-IQ - F5 Technical Articles - DevCentral - An F5 Technical Community I hope that answers your question sufficiently! Best regards, Nathan
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: DevCentral - An F5 Technical Community I hope that answers your question sufficiently! Best regards, Nathan
It seems to align well with the DevOps mania, but it’s difficult to evaluate what it exactly does without seeing the end-user experience.
Would it be possible to answer the following two questions in a 10-minute video/demo format? I’m sure a supplementary demo will be appreciated by those who do not have prior BigIP automation experience.
What are the back-end tasks that a knowledgeable engineer has to execute in preparation for the use of iWorkFlow (creation of iApps, definitions of configuration deployment options, etc.)
What is the overall look and feel of the iWorkFlow front-end tool for the end-users? (Please deploy something using just the iWorkFlow tool)
It seems to align well with the DevOps mania, but it’s difficult to evaluate what it exactly does without seeing the end-user experience.
Would it be possible to answer the following two questions in a 10-minute video/demo format? I’m sure a supplementary demo will be appreciated by those who do not have prior BigIP automation experience.
What are the back-end tasks that a knowledgeable engineer has to execute in preparation for the use of iWorkFlow (creation of iApps, definitions of configuration deployment options, etc.)
What is the overall look and feel of the iWorkFlow front-end tool for the end-users? (Please deploy something using just the iWorkFlow tool)
Hannes Rapp, thank you for your questions. In this brief period, between now and the release of iWorkflow in mid-June, we are working on precisely this kind of content. You’ll see additional iWorkflow 101 episodes that will include video demonstrations of this functionality. I hope to release a few episodes before the actual product release so make sure you come back soon! Nathan
Hannes Rapp, thank you for your questions. In this brief period, between now and the release of iWorkflow in mid-June, we are working on precisely this kind of content. You’ll see additional iWorkflow 101 episodes that will include video demonstrations of this functionality. I hope to release a few episodes before the actual product release so make sure you come back soon! Nathan
BIG-IQ is still doing plenty! The “BIG-IQ Cloud” functionality became the foundation of what has now evolved into iWorkflow (it does a little more than just that) but the other BIG-IQ functions (other than BIG-IQ Cloud) are all still there. You’re interested mostly in the programmability side?
BIG-IQ is still doing plenty! The “BIG-IQ Cloud” functionality became the foundation of what has now evolved into iWorkflow (it does a little more than just that) but the other BIG-IQ functions (other than BIG-IQ Cloud) are all still there. You’re interested mostly in the programmability side?
No, I was just confused about these terminologies. It would be much clearer to rename what’s left of the previous BIG-IQ back to “admin server”, it would seem.
No, I was just confused about these terminologies. It would be much clearer to rename what’s left of the previous BIG-IQ back to “admin server”, it would seem.
Nathan, I have gone through the series on the wiki, and I like what I see, I was wondering if there is going to be an evaluation license for iworkflow, or a demo license?
Thanks for the feedback! More episodes are on the way.
Yes, there is an evaluation license for iWorkflow. You can get one from your F5 sales team or from you F5 value added reseller. Either of these can generate an evaluation license key for you.
Hard to gauge from here (am on on vacation…) but maybe a time sync? I had this once on my laptop environment where the clocks skew when coming in and out of hibernation, so after waking up my laptop I had to reboot both the VM’s and they were happy again.
Did you run this by your F5 Account team? They are there to support you through evaluations.
The “BIG-IQ Cloud” functionality became the foundation of what has now evolved into iWorkflow (it does a little more than just that) but the other BIG-IQ functions (other than BIG-IQ Cloud) are all still there. You’re interested mostly in the programmability side?