Applies To:
Show Versions
F5 iWorkflow
- 2.2.0
Summary:
This release note documents version 2.2.0 of iWorkflow. iWorkflow 2.2.0 is available as an ISO or Virtual Edition image.
Contents:
Product description
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.
Screen resolution requirement
To properly display, the iWorkflow system requires that your screen resolution is set to 1280x1024 or higher.
Browser support
This release supports the following browsers and versions:
- Microsoft Internet Explorer version 11 and later.
- Mozilla Firefox version 29.x and later.
- Google Chrome version 34.x and later.
iWorkflow compatibility
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.
User documentation for this release
For a comprehensive list of documentation that is relevant to this release, refer to the F5 iWorkflow 2.2.0 Knowledge Center page. For additional documentation, refer to the iWorkflow Ops Guide and API Reference on the DevCentral Wiki: iWorkflow page.
Software installation
- F5® iWorkflow™ and Citrix XenServer: Setup guide.
- F5® iWorkflow™ and Linux KVM: Setup guide.
- F5® iWorkflow™ and Microsoft Hyper-V: Setup guide.
- F5® iWorkflow™ and VMware ESXi: Setup guide.
Licensing and initial configuration
- F5® iWorkflow™: Administration guide.
- F5® iWorkflow™: Cisco APIC Administration guide.
- F5® iWorkflow™: VMware NSX Administration guide.
New in version 2.2.0
Enable multi-tenant BIG-IP cloud functionality
Introduces support for multi-tenant capabilities of the BIG-IP Cloud connector. This allows the creation and management of information in isolated containers so that access control can be granted to groups of users. Within iWorkflow, cloud connector implementations require various degrees of multi-tenancy isolation. The new multi-tenant capabilities also allows iWorkflow to consume a partition of the BIG-IP, instead the entire device or virtual instance.Extend iApps service catalog improvements to provider tenant
This release supports a network administrator to make updates/upgrades to the service catalogs for the tenant user to consume. A network administrator can now modify/update existing catalog entries field as "tenant viewable," or change variables and implement service catalog versioning for the tenant user to consume. Also allows the network administrator to upgrade the underlying iApps version itself to a new version of an iApps.Enable iWorkflow POCs in Amazon Public Cloud by publishing an iWorkflow image in AWS
This release supports the network administrator to install an Amazon Machine Image (AMI) of iWorkflow in Amazon Public Cloud for POCs.Support for VMware NSX-V VXLAN-to-VLAN software bridge with physical BIG-IP High-Availability (HA) in iWorkflow NSX integration mode
This release adds VMware NSX-V VXLAN-to-VLAN software bridge support with Active/Standby HA physical BIG-IP (Appliance/vCMP).Fixes
| ID Number | Functional Area | Description |
|---|---|---|
| 654092 | iWorkflow | If a hostname is not provided during the initial setup of the logical device cluster, the device is not associated with the connector; therefore, when the service template is deployed, there is a "no connector association error." The service should get associated with the connector and the service deployment should be successful, even if no hostname is provided. |
Known issues
| ID Number | Functional Area | Description | Workaround (if available) |
|---|---|---|---|
| 637133 | iWorkflow | While deleting an iApp and its associated network objects, self IPs and VLANs cannot be removed if iApps pool members still exist. | For the Cisco APIC device package, clean up is a "best effort" endeavor. If, in the rare case, a clean up of a deployed graph fails, the admininstrator must complete the removal of the partition manually. This includes removing any iApps objects, any L2-L3 objects remaining in the partition, and finally removing the empty partition. |
| 642390 | iWorkflow | iApps AppSvcs V2.0 deployment may fail with an error message such as: "The requested Virtual Server (/apic-BOS-BOSctx1-15351/HTTP102a-1-graph-vCMPPodA-5484.app) was not found" in the restjavad.0.log. The error can occur even if the virtual server is successfully deployed. | Replace the body of the method handle_opt_remove_on_redeploy() in AppSvc V2.0 with a dummy implementation: proc handle_opt_remove_on_redeploy { name checkvalue option module } { return 0 }. The workaround disables code that checks to make sure a module has not been de-provisioned underneath/between deployments of the template. |
| 644006 | iWorkflow | Attempting to delete a Tenant or graph containing AppSvc V2.0 using Cisco APIC results in failure. The error message indicates that the iApps cannot be removed because the property "Strict Updates" is enabled. | Replace the body of the method handle_opt_remove_on_redeploy() in AppSvc V2.0 with a dummy implementation: proc handle_opt_remove_on_redeploy { name checkvalue option module } { return 0 }. The workaround disables code that checks to make sure a module has not been de-provisioned underneath/between deployments of the template. |
| 647103 | iWorkflow | If the logging level in the /etc/restjavad.log.conf is set to FINER or FINEST, it will cause the L4-L7 service placement to fail. | Set the logging level in /etc/restjavad.log.conf to FINE or INFO. |
| 658727 | iWorkflow | When using the API to create a Provider Template, it is possible for a malformed template to fail. The Tenant Template will not be created and an error will be logged to the restjavad log. | When using the API to create a Provider Template, the caller should check for the existence of the Tenant Template specified by ProviderIAppTemplateWorkerState.tenantTemplateReference. If the Tenant Template does not exist, then the creation of the Provider Template has failed. Check the restjavad log. |
| 660183 | iWorkflow | If a vCMP host is removed from the Devices panel, and if a BIG-IP VLAN (--Create API --> /mgmt/device/big-ip/net/vlan/create) is used to create a VLAN on the vCMP guest (residing on that host), the creation of a VLAN on the guest will fail with error. The GET on https://<iWF>/mgmt/device/big-ip/net/vlan/create/<taskID> will show the FAILED status. |
A vCMP host should never be removed from the Devices panel because it is required in order to manage networks on the vCMP guests that reside on the host. Discover the vCMP host in the Devices panel by providing a vCMP host IP address and administrator credentials. |
| 660265 | iWorkflow | If attempting to disjoin an existing vCMP guest A/S cluster, it will fail. Error message: "found connector associated." | Deprovision both the vCMP guests. |
| 661807 | iWorkflow | When attempting to create a virtual server based on the appsvcs_integration_v2.0.003 with the NSX Cloud Connector, the placement of the iApps service will fail because the "State" column in the "pool__Members" table is not populated. | In the API, when creating a Provider Template based on the appsvcs_integration_v2.0.003, specify a "provider" value "enabled" and remove "defaultValue" for the "State" column definition of the "pool__Members" table. In the UI, deselect the "Column Tenant Editable" option for the "State" column definition for the "pool_Members" table. |
| 662160 | iWorkflow | When a service is undeployed, LTM nodes corresponding to the service are not removed. The deletion of a partition containing the orphaned nodes will fail. LTM nodes are not deleted on service undeployment because its possible that the nodes are being used by another virtual server. |
Delete the LTM node in the partition first and then attempt to delete the partition. |
| 662645 | iWorkflow | Service placement will attempt to create/use a new tenant partition, but placement will fail during partition validation. Services already placed cannot migrate to a new partition. | Reset the deviceConfigBoundaryId to its previous value and retry service placement. |
| 662917 | iWorkflow | When you have large number of iApps services based off of appsvcs_integration_v2.0.003 deployed through iWorkflow onto BIG-IPs in a HA configuration, and one or more of these services are in a Placement status of ERROR, deleting the services will delete them from iWorkflow, but not BIG-IP. | Log in to the BIG-IP system and delete the service. |
| 663061 | iWorkflow | Cisco APIC and VMware NSX users will not be able to re-deploy L4-L7 services when upgrading an existing service to use a newer version of a Service Template. | Remove the existing service and deploy a newer version of the Service Template. |
| 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. | None. |
| 644186 | iWorkflow | There is an inconsistency in the behavior of API and UI when a delete is performed on the vCMP guest in cm-cloud-managed device group. If delete is performed on the API (/mgmt/shared/resolver/device-groups/cm-cloud-managed-devices/devices/<deviceID>), the guest on the vCMP host does not get deleted, but the device in cm-cloud-managed group (Devices panel) is deleted. If the device is deleted using the Devices panel in UI, the guest on vCMP host as well as the device from cm-cloud-managed device group is deleted. | Delete should be issued on the corresponding node, which represents the vCMP guest (API: /mgmt/cm/cloud/connectors/vcmp/<connectorID>/nodes/<nodeId>). This will delete the guest from the vCMP host as well as remove the device from the cm-cloud-managed devices group. |
Contacting F5 Networks
| Phone: | (206) 272-6888 |
| Fax: | (206) 272-6802 |
| Web: | http://support.f5.com |
| Email: | support@f5.com |
For additional information, please visit http://www.f5.com.
Additional resources
You can find additional support resources and technical documentation through a variety of sources.
- The F5 Networks Technical Support web site: http://www.f5.com/support/
- The AskF5 web site: http://support.f5.com/kb/en-us.html
- The F5 DevCentral web site: http://devcentral.f5.com/
- AskF5 TechNews
F5 Networks Technical Support
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
AskF5 is your storehouse for thousands of solutions to help you manage your F5 products more effectively. Whether you want to search the knowledge base periodically to research a solution, or you need the most recent news about your F5 products, AskF5 is your source.
F5 DevCentral
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.
AskF5 TechNews
- Weekly HTML TechNews
- The weekly TechNews HTML email includes timely information about known issues, product releases, hotfix releases, updated and new solutions, and new feature notices. To subscribe, click TechNews Subscription, complete the required fields, and click the Subscribe button. You will receive a confirmation. Unsubscribe at any time by clicking the Unsubscribe link at the bottom of the TechNews email.
- Periodic plain text TechNews
- F5 Networks sends a timely TechNews email any time a product or hotfix is released. (This information is always included in the next weekly HTML TechNews email.) To subscribe, send a blank email to technews-subscribe@lists.f5.com from the email address you are using to subscribe. Unsubscribe by sending a blank email to technews-unsubscribe@lists.f5.com.
