2.2   General Impact for vMRF 1.2

This section describes the general impact for the vMRF 1.2 release.

2.2.1   Backward Compatibility

vMRF 1.2 does not have upgrade compatibility with signaling subnet stacks created in previous releases. vMRF configuration can be imported to vMRF 1.2 from previous releases.

2.2.2   Capacity and Performance

No impact.

2.2.3   Operation

The vMRF 1.2 release includes parameter name changes in HOT and example environment files included in the software delivery package. Due to this, the example_environment.yaml from previous vMRF releases cannot be used when creating subnets. Before the deployment of vMRF 1.2, the old vMRF configuration must be backed up to a cluster-external storage, and the old vMRF stack and signaling subnet stack must be deleted. The example_environment.yaml file included in the vMRF 1.2 software delivery package must be prepared with site-specific data, and vMRF 1.2 must be deployed as described in the relevant manual deployment guides. After deployment, the previously exported configuration can be imported.

The following parameter changes are introduced in vMRF1.2:

• mrsv_ prefix parameters have been replaced with mrf_ prefix

The following new features are introduced in vMRF 1.2:

• Network-redundant upgrade method
• Workflow-based VNF Life Cycle Management (VNF-LCM)

2.5.2   Other Network Elements in vMRF 1.2

2.5.2.1   General

The lowest interoperable releases for vMRF 1.2 are described in Table 2.

2.5.2.1.1   Multimedia Telephony Application Server (MTAS)

vMRF 1.2 is compatible with the following MTAS releases: 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, and 4.6.

2.5.2.1.2   Virtual Multimedia Telephony Application Server (vMTAS)

vMRF 1.2 is compatible with the following vMTAS releases: 1.0, 1.1, 1.2, 1.3, 1.4, 1.5, and 1.6.

2.5.2.1.3   OSS-RC

vMRF 1.2 is compatible with the following OSS-RC releases: 17B, 18A.

3.2   Interfaces in vMRF 1.2

This section describes interface changes introduced in vMRF 1.2.

3.2.1   Inter-node Interfaces

There are no changes to the inter-node interfaces in vMRF 1.2.

3.2.2   Operation and Maintenance

This section describes changes to attributes, alarms, events and notifications, triggers, and counters.

3.2.2.1   Configuration

This section lists changes in attributes. There are no changed, deprecated, obsolete, or new attributes.

3.2.2.2   Fault Management

This section lists changes in alarms. There are no new, changed or deleted alarms.

3.2.2.3   Events and Notifications

This section lists changes in events and notifications. There are no new, changed or deleted events and notifications.

3.2.3   Counters

There are no changed, deleted, deprecated, obsolete, or new counters in vMRF 1.2.

5.2   Impact on vMRF Features from vMRF 1.1 to vMRF 1.2

5.2.1   Upgrade Method Enhancements

5.2.1.1   Description

In vMRF 1.2 the network-redundant upgrade method has been introduced. Network-redundant upgrade can be performed when two vMRF VNFs are available in parallel during normal operation. During the upgrade procedure, one of them is upgraded to the new version, while the other one handles traffic uninterrupted.

5.2.2   Workflow-based VNF Life Cycle Management

5.2.2.1   Description

In vMRF 1.2 the workflow-based VNF Life Cycle Management (VNF-LCM) has been introduced as a primary method for VNF cluster management. The following workflow-based procedures are supported in vMRF 1.2:

• Instantiation
• Scaling (scale-in, scale-out)
• Termination

Scaling and termination of a vMRF VNF using VNF-LCM is only supported if the vMRF was instantiated using the LCM workflow. Manual scaling and the removal of the cluster must be performed only if the vMRF VNF was deployed manually.