Original Publication Date: 08/28/2017
This release note documents version 2.3.0 of iWorkflow. iWorkflow 2.3.0 is available as a an ISO or Virtual Edition image.
Cloud administrators can use iWorkflow to supply tenants with on-demand access to resources such as networks, servers, storage, applications, and services. These cloud resources can be located on BIG-IP devices in a private local network, a public third-party cloud service, or a combination of both.
Tenants have restricted and dedicated access to resources based on their unique tenant role and user account. Cloud space can be expanded, retracted, and reallocated to tenants as needed, providing flexible resource balancing.
To properly display, the iWorkflow system requires that your screen resolution is set to 1280x1024 or higher.
This release supports the following browsers and versions:
K11198324: F5 iWorkflow compatibility matrix provides a summary of version compatibility for specific features between the iWorkflow system and supported cloud providers and BIG-IP releases.
|ID Number||Functional Area||Description||Workaround (if available)|
|663064||iWorkflow||When a Service Template has a table for which the provider has supplied pre-defined tenant viewable or editable rows, Cisco APIC and VMware NSX users will not be able to view or edit the rows in the APIC or NSX UI.||After deployment from NSX/APIC, user can login to iWorkflow as a tenant and modify service settings with access to all options.|
|676254||iWorkflow||When provisioning a tenant network via provision-tenant-network API provisioning may fail with message: "Configuration error: Can't associate folder does not exist". This is only known to impact BIG-IP 12.0.0.||Retrying the tenant network provisioning will complete successfully if the DSC cluster is still in sync and more than 30 seconds have passed since formation.|
|676609||iWorkflow||When creating a Service Template while iWorkflow is configured in an HA cluster, the Service Template may not be replicated to one or more of the iWorkflow HA peer devices. The symptom of this issue is having a Service Template that exists on one iWorkflow HA peer and not on other iWorkflow HA peers. This was observed once in test automation.||Delete the Service Template from the iWorkflow HA peer that has the Service Template available. Recreate the Service Template on the same iWorkflow HA peer. Validate that the Service Template is then available on each iWorkflow HA peer.|
|677053||iWorkflow||iWorkflow 2.3.0 does not support setting multi-tenant mode on devices managed by vCMP connector.||Uncheck the Multi-tenant checkbox on the vCMP device in Devices panel and then deploy services to the device.|
|677325||iWorkflow||Deletion of an ACI Tenant that has both L2-L3 and L4-L7 items configured causes issues.||Delete the L2-L3 and L4-L7 items associated with the ACI Tenant, clean up the devices, and then tear down the cluster.|
|677560||iWorkflow||It is possible to overload NSX with back to back POST's when creating Virtual Servers. When this happens, the Virtual Servers will not get created on NSX.||When making back to back POST's to create Virtual Servers, wait about 10 seconds.|
|678401||iWorkflow||In the Service Tier Information from iApp Template or Service Template, there is a section either named Server Tier or Name. This field must not have white space. If there is white space, tenants will not be able to view the Virtual Server blade and an error pops up in the UI. Making calls to /mgmt/cm/cloud/tenants/tenant/virtual-servers also returns a code 400.||When you type a Server Tier Name, do not use white space.|
If you deprovision a tenant network after you have deployed L4-L7 services on that tenant network, the partition created for that tenant, along with the nodes and a route domain might not be removed as part of the deprovisioning process.The leftover partition and network objects do not prevent you from creating a new tenant network for the same tenant or deploying other L4-L7 services.
|After deprovisioning a multi-tenancy tenant network, if there are leftover partitions and network objects, you can re-use the partition to create another tenant network for a given tenant. If you decide you must remove these items:
|Phone - North America:||1-888-882-7535 or (206) 272-6500|
|Phone - Outside North America, Universal Toll-Free:||+800 11 ASK 4 F5 or (800 11275 435)|
|Fax:||See Regional Support for your area.|
For additional information, please visit http://www.f5.com.
You can find additional support resources and technical documentation through a variety of sources.
Free self-service tools give you 24x7 access to a wealth of knowledge and technical support. Whether it is providing quick answers to questions, training your staff, or handling entire implementations from design to deployment, F5 services teams are ready to ensure that you get the most from your F5 technology.
AskF5 is your storehouse for thousands of knowledgebase articles that help you manage your F5 products more effectively. Whether you want to browse periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
The F5 DevCentral community helps you get more from F5 products and technologies. You can connect with user groups, learn about the latest F5 tools, and discuss F5 products and technology.
To subscribe, click AskF5 Publication Preference Center, enter your email address, select the publications you want, and click the Submit button. You will receive a confirmation email. You can unsubscribe at any time by clicking the Unsubscribe link at the bottom of the email, or on the AskF5 Publication Preference Center screen.