Release notes

These release notes provide product information about the F5 VNF Manager support for version 1.3.

User documentation

You can find the user documentation on: https://clouddocs.f5.com/cloud/nfv/latest/.

Platform support

F5 VNF Manager version 1.3 requires the following supported platforms:

Platform name Platform ID System Requirements
F5 VNF Manager All versions
  • vCPUs: 4 minimum, 8 recommended
  • RAM: 8GB minimum, 16GB recommended
  • Root Disk Storage: 160GB minimum
  • 64-bit host with RHEL/CentOS 7.4
  • Private network dedicated for communicating with other VNFM components, including cluster members
BIG-IP VE Version 13.1.0.5 Virtual Edition BIG-IP 13.1.0.5 Virtual Edition Release Notes
BIG-IQ Version 6.0.1 BIG-IQ 6.0.1 Release Notes
CentOS-7-x86_64-GenericCloud-1503 GenericCloud-1503 Release Notes

F5 VNF Manager and Virtual Infrastructure Manager (VIM) compatibility matrix:

VNF Manager ID VIM Platform ID VIM System Requirements
F5 VNF Manager 1.1.X Red Hat OpenStack Newton Version 10 Environment requirements
F5 VNF Manager 1.2.0 VMware vSphere ESXi Version 6.5 Requirements and patch notices
F5 VNF Manager 1.2.1 VMware vSphere ESXi Version 6.5 and Red Hat OpenStack Newton Version 10 See previous links for requirements information.
F5 VNF Manager 1.3.0 Red Hat OpenStack Newton Version 10 and Queens Version 13
VMware vSphere ESXi Version 6.5
Queens Version 13 Environment requirements
See previous links for other platform requirements.

Open source components

F5 VNF Manager is built with the following open-source components.

Component Description
Nginx

Nginx is a high-performing Web server. In F5 VNF Manager, it serves two purposes:

  • A proxy for the F5 VNFM REST service and F5 VNFM Console
  • A file server to host F5 VNFM-specific resources, agent packages, and blueprint resources.

File server

The file server served by Nginx, while tied to Nginx by default, is not logically bound to it. Although currently it is accessed directly frequently (via disk rather than via network), we will be working towards having it decoupled from the management environment so that it can be deployed anywhere. The file server served by Nginx, is available at https://{manager_ip}:53333/resources, which is mapped to the /opt/manager/resources/ directory. You must authenticate in order to access the file server. To access subdirectories that include tenant names in their path, you must have privileges on that tenant. These subdirectories include:

  • blueprints
  • uploaded-blueprints
  • deployments
  • tenant-resources

The directories that are stored in snapshots include:

  • blueprints
  • uploaded-blueprints
  • deployments
  • tenant-resources
  • plugins
  • global-resources

Note: The tenant-resources and global-resources directories are not used by F5 VNF Manager; therefore, users can create these directories for storing custom resources.

Gunicorn and Flask Gunicorn is a Web server gateway interface HTTP server. Flask is a Web framework. Together, Gunicorn and Flask provide the F5 VNFM REST service. The REST service is written using Flask, and Gunicorn is the server. Nginx, is the proxy to that server. The F5 VNFM’s REST service is the integrator of all parts of the F5 VNFM environment.
PostgreSQL

PostgreSQL is an object-relational database that can handle workloads ranging from small single-machine applications to large Internet-facing applications. In F5 VNF Manager, PostgreSQL serves two purposes:

  • Provides the main database that stores the application’s model (for example, blueprints, deployments, runtime properties)
  • Provides indexing, and logs’ and events’ storage
Logstash Logstash is a data handler. It can push/pull messages using inputs, and apply filters and output to different outputs. Logstash is used by F5 VNFM to pull log and event messages from RabbitMQ and index them in PostGresSQL.
RabbitMQ

RabbitMQ is a queue-based messaging platform. RabbitMQ is used by F5 VNFM as a message queue for different purposes:

  • Queueing deployment tasks
  • Queueing logs and events
  • Queueing metrics
Pika

Pika is a pure-Python implementation of the AMQP 0-9-1 protocol. The VNF management worker and the host agents are using pika to communicate with RabbitMQ.

Management worker (or agent)

Both the Workflow Executor and the Task Broker that appear in the diagram are part of the F5 VNFM Management Worker.

  • The Workflow Executor receives workflow execution requests, creates the tasks specified by the workflow, submits the tasks for execution by host agents and the Task Broker, and manages workflow state.
  • The Task Broker executes API calls to IaaS providers to create deployment resources, and executes other tasks specified in central_deployment_agent plugins.

Note: All agents (the management worker, and agents deployed on application hosts) are using the same implementation.

Features

Feature Name Description
Install/Uninstall Installs the target deployment, lifecycle operations, and starts all instances. Uninstalls target deployment, frees resources allocated during install, performs uninstall lifecycle operations, stops/deletes deployments and additional blueprints created during install.
Scale out Adds and installs BIG-IP Virtual Editions (VEs) and VNF instances on demand as your network needs resources based on configurable parameters.
Scale in Removes and uninstalls BIG-IP Virtual Editions on demand as your network reduces its need for resources based on configurable parameters.
Heal VEs and layers Creates a new copy of any BIG-IP VEs, layers, and related objects on demand as your network reports dysfunctional instances.
Purge VEs and layers Uninstalls and removes dysfunctional VEs, VNF layer instance(s), and related objects, which you start manually after heal layer workflow runs and problem investigation is complete.
Upgrade Initiates the upgrade process and sets new software reference data. Disables VEs with lower revision numbers. Scaled and healed VEs are installed using the new software reference data.
Update NSD Updates AS3 declaration pushed to the VE as a part of NSD definition.
High Availability (HA) Provides high availability using a cluster of three F5 VNF Managers.
REST API Provides all VNFM functionality using a REST-based API.

What’s new

The following table describes new functionality added in VNF Manager in the designated version release:

Item Description
floating_network_id input This input is now optional for verison 1.3.0 and later and the default value is empty for VNFM projects in OpenStack ONLY. This input is still required for versions 1.2.1 and earlier.
Security groups in OpenStack VIM Setting up security groups in OpenStack ONLY and related security group (sg) inputs are now OPTIONAL for version 1.3.0 and later. There is a new, security_groups, input enabling/disabling security groups for the ALL blueprint solutions, except VNF-BIG-IQ. When set to enabled, appropriate security groups are included for the Nagios, DAG and VNF nodes, but when set to disable the default Security Group created by OpenStack for every instance is disabled along with all other security groups that may exist.
Enhanced VNFM event logs The VNF Manager now contains Nagios logs for heal_ve, heal_layer, and scale-out events. The Nagios logs will detail when and what caused a VE or a layer to heal or to scale out. In the VNF Manager console view these logs in the Deployments Events/Logs pane. You can also pull these heal and scale Nagios log entries using the VNFM API.
Support for OpenStack Queens version 13 Tested and verified that VNF Manager is compatible with OpenStack Queens version 13 in addition to Newton version 10. IMPORTANT: In this version, you must assign security groups with unique names.
Enabling CGNAT capability To support CGNAT capabilities in Gi LAN and Gi Firewall blueprint solutions, this release provides several new Gi LAN and Gi Firewall inputs, and an adjusted vnf_as3_nsd_payload AS3 Declaration definitions. See the Blueprint inputs reference guide for complete information.

Known issues

The following table lists known issues in the designated version release:

Platform name Description
F5 VNF Manager Version 1.3.0
  • VNFM in an OpenStack VIM does not currently support SR-IOV.
  • VNFM does not currently support an OpenStack environment using https for keystone with an internally-signed certificate.
  • When deploying Gi LAN/F blueprints, occasionally these solutions will fail to deploy because the master node remains active.
  • Due to Nagios requiring access to the CentOS repository, currently you cannot deploy Gi LAN and Gi Firewall in a dark environment (without access to the Internet).
  • On failover, connections are reset rather than smoothly transitioned. So application connections will drop and must be reset by the application.
  • If deploying the F5-VNF-BIG-IQ blueprint from a VMware vSphere ESXi VIM, you must NOT use 192.168.1.200 and 192.168.1.245 IP addresses on the same network the F5 VNF Manager is connected, until AFTER you deploy the BIG-IQ blueprint and the BIG-IQ HA pair is online. Once the BIG-IQ HA pair is online, those IP addresses become available.
  • The VNFM image for VMware vSPhere ESXi displays several extraneous workflows (Clear inactive deployment ips, Clear subnets, Update, and Configuration Update) for the main Gi-LAN and Firewall deployments. These workflows are internal and part of the blueprint automation. You are NOT meant to execute these workflows manually. F5 will hide these workflows in the UI, in a future next release.
  • In VMware vSphere ESXi, when using the VNFM REST API, you must set up your networks to use unique port group names, regardless of the directories in which they reside.
  • Intermittently, an incorrect BIG-IP hostname is sent to the BIG-IQ license manager, causing a mismatched BIG-IP instance with their VE representation in VNFM. This issue affects only how the reporting plugin displays BIG-IP VE usage data within a layer, but does not affect any billing information.
  • OpenStack v10 (Newton) has an issue with privileges and connecting devices residing outside the OpenStack environment with those residing inside the OpenStack environment, including F5 VNF Managers. To work around this issue, you must add the VNF Manager to the admin project.
  • Nagios continuously triggers, and then cancels the Heal workflow on DAG instances unnecessarily. However, these actions do not prevent the system from operating.
  • Occasionally, a master or slave node in a VNF group will fail to license due to network congestion, resulting in the NTP server not synchronizing with that BIG-IP. To avoid this issue, use an NTP server that is local to your management network. Or, you can uninstall and reinstall the blueprint.
BIG-IP 13.1.0.5 Virtual Edition Issues list
BIG-IQ 6.0.1 Issues list
CentOS-7-GenericCloud-1503 Issues list
Red Hat OpenStack Newton Issues list for v10 and Issues list for v13
VMware vSphere ESXi 6.5 Issues list

Fixed issues

The following table lists issues that were fixed in the designated version release:

Platform name Fixed in version Description
F5 VNF Manager 1.3.0

To enable VNF Manager for use in a dark environment, the following changes were made:

  • Floating IP assignment for Nagios is now optional when using an OpenStack VIM.
  • Security Groups are now optional when using an OpenStack VIM.
  • Uninstall workflow now removes all nodes successfully.
  • Removed the dependency on Google Fonts in the VNFM user interface.
BIG-IP Virtual Edition 13.1.0.5 Issues list
BIG-IQ 6.0.1 Issues list
CentOS-7-x86_64 GenericCloud-1503 Issues list
Red Hat OpenStack 10.0 and 13.0 Issues list for v10 and Issues list for v13
VMware vSphere ESXi 6.5 Issues list

Installation overview

To install F5 VNF Manager, use the link provided in the email, and use the key provided in the email as customer identification, when obtaining customer support. Additionally, you will need the following F5 product license keys:

Platform name Product license
BIG-IQ 6.0.1 F5-BIQ-VE-LIC-MGR-LIC
BIG-IP 13.1.0.5 Virtual Edition F5-BIG-MSP-LOADV12-LIC
CentOS-7-x86_64-GenericCloud-1503 NA

Upgrade overview

You can upgrade HA clusters two ways:

  • Upgrade on new hosts (recommended method).

  • In-place upgrade (prevents ability to rollback).

    Important

    This method works only if you leave the IP, AMQP credentials and certificates unchanged.

What’s Next?

Set up VNFM