3 steps to some custom f5 big-ip workflow in vrealize orchestrator
window.___gcfg = (function() )()
In This summer 2016, Blue Medora released the vRealize Orchestrator Plug-set for F5 BIG-IP. It included 58 out-of-the-box workflows, which ranged from simple provisioning tasks, like creating pool people, to more difficult features, like creating an HA pair. While these workflows cover the most typical use installments of F5 BIG-IP, they merely provide simple facts from the wordpress plugin.
Many users do not know this, however the F5 BIG-IP wordpress plugin really exposes the whole IControl REST API. And due to this, that you can do everything imaginable inside the constraints from the F5 BIG-IP environment–not just what’s presented to you.
To show this, I’ll take you step-by-step through the development of a custom workflow that sets the swimming pool of the virtual server.
First, start by opening the API explorer in vRealize Orchestrator after which navigate to F5 Systems. Whenever you expand this branch, you’ll most likely be at a loss for the amount of objects contained beneath it. You will find over 1800 scripting objects here, each correlating to some URL within the REST API. As well as for all these objects, there are many methods readily available for allowing the actions of the workflow.
Figure 1: The LtmVirtual scripting object within the API Explorer.
Let’s imagine, the scripting object that we’re most worried about is “LtmVirtual.” This object may be the plugin’s javascript representation of the virtual server. While its name may appear confusing initially, it’s really produced from the generic Link to virtual servers within the IControl REST API. Therefore, if at any time you’ve trouble choosing the appropriate scripting object when designing your custom workflows, you could reference the IControl Rest documentation and concatenate the connected URL.
Figure 2: The Remainder API documentation for F5 BIG-IP virtual servers.
For our intended example, let’s look a bit more carefully in the “LtmVirtual” scripting object. Within the API explorer, you’ll observe that this object includes a way of setting a swimming pool which this process is only going to require pool name like a parameter. Therefore, as lengthy as there’s an demonstration of an online server, along with the name in our pool, you can produce a workflow that employs this logic.
We’ll begin by creating an action which will accept an “LtmVirtual” scripting object being an input parameter. This allows the finish user to decide on the virtual server they would like to alter when managing a workflow. Next, we’ll create yet another input parameter for that pool name. After which finally, we’ll begin using these two parameters to create an very simple script, using the “setPool” method we discovered within the API explorer.
Figure 3: A script demonstrating how you can set the swimming pool of the virtual server.
After creating this course of action, there’s hardly any work needed in allowing the actual workflow. You just need to drop the experience in to the workflow and fasten the right parameters.
Figure 4: Our custom workflow that sets the swimming pool for any virtual server.
As you have seen, the introduction of a custom F5 BIG-IP workflow is a straightforward three step process: You consult the API Explorer. You develop an action. And lastly, you set that action to some workflow.
window.___gcfg = (function() )()
In This summer 2016, Blue Medora released the vRealize Orchestrator Plug-set for F5 BIG-IP. It included 58 out-of-the-box workflows, which ranged from simple provisioning tasks, like creating pool people, to more difficult features, like creating an HA pair. While these workflows cover the most typical use installments of F5 BIG-IP, they merely provide simple facts from the wordpress plugin.
Many users do not know this, however the F5 BIG-IP wordpress plugin really exposes the whole IControl REST API. And due to this, that you can do everything imaginable inside the constraints from the F5 BIG-IP environment–not just what’s presented to you.
To show this, I’ll take you step-by-step through the development of a custom workflow that sets the swimming pool of the virtual server.
First, start by opening the API explorer in vRealize Orchestrator after which navigate to F5 Systems. Whenever you expand this branch, you’ll most likely be at a loss for the amount of objects contained beneath it. You will find over 1800 scripting objects here, each correlating to some URL within the REST API. As well as for all these objects, there are many methods readily available for allowing the actions of the workflow.
Figure 1: The LtmVirtual scripting object within the API Explorer.
Let’s imagine, the scripting object that we’re most worried about is “LtmVirtual.” This object may be the plugin’s javascript representation of the virtual server. While its name may appear confusing initially, it’s really produced from the generic Link to virtual servers within the IControl REST API. Therefore, if at any time you’ve trouble choosing the appropriate scripting object when designing your custom workflows, you could reference the IControl Rest documentation and concatenate the connected URL.
Figure 2: The Remainder API documentation for F5 BIG-IP virtual servers.
For our intended example, let’s look a bit more carefully in the “LtmVirtual” scripting object. Within the API explorer, you’ll observe that this object includes a way of setting a swimming pool which this process is only going to require pool name like a parameter. Therefore, as lengthy as there’s an demonstration of an online server, along with the name in our pool, you can produce a workflow that employs this logic.
We’ll begin by creating an action which will accept an “LtmVirtual” scripting object being an input parameter. This allows the finish user to decide on the virtual server they would like to alter when managing a workflow. Next, we’ll create yet another input parameter for that pool name. After which finally, we’ll begin using these two parameters to create an very simple script, using the “setPool” method we discovered within the API explorer.
Figure 3: A script demonstrating how you can set the swimming pool of the virtual server.
After creating this course of action, there’s hardly any work needed in allowing the actual workflow. You just need to drop the experience in to the workflow and fasten the right parameters.
Figure 4: Our custom workflow that sets the swimming pool for any virtual server.
As you have seen, the introduction of a custom F5 BIG-IP workflow is a straightforward three step process: You consult the API Explorer. You develop an action. And lastly, you set that action to some workflow.
This really is the approach which was taken when developing the 58 standard workflows that include the vRealize Orchestrator Plug-set for F5 BIG-IP. And basically, this is actually the greatest strength from the wordpress plugin. The tools which were accustomed to get this to wordpress plugin may be used on your part to create something better, stranger, or maybe more elaborate than anything ever intended. The various tools exist. It’s your decision about how they are being used.
Resourse: https://blogs.vmware.com/management/2016/10/
