This project provides a set of working lifecycle manager Network Service and VNF examples. This branch supports version 2.0 of StratOSS Lifecycle Manager only. Worked examples for other versions of SLM are available on other branches in this project.

An example VoIP Network Service is provided that uses a set of open source VNFs. The VoIP service includes a Voice (SIP & RTP) Gateway that load balances voice traffic across a dynamic pool of IPPBX servers. To test the service a SIP performance test VNF is also included that can simulate voice traffic and demonstrate IPPBX cluster behaviour.

The following Opensource VNFs are included:

• Voice Gateway: SIP/RTP load balancer
• VoIP PBX Server: VoIP server, servicing conference requests
• SIPP traffic simulator: VoIP traffic simulator.

Supporting Openstack network VNFs wrapped with the LM standard lifecycle model can be included in other VNFs or Network Service projects. They are as follows:

• Router: Openstack neutron router
• Tenant Network: Openstack neutron tenant network
• Provider Network: Openstack neutron Provider Network

The diagram below shows a logical VoIP Network Service deployment with some behavioural use cases that must be automated by the lifecycle manager.

1. Stand up the VoIP network service VNFs and perform required initial integrations to have a working gateway with a single initial VoIP server in its pool to service external calls.
2. Run a SIP VNF and attach it to the VoIP Network service to simulate users. Load metrics generate by the gateway can show current user sessions being serviced by the network service.
3. Add SIP VNFs to simulate additional users. Increased load metrics trigger a scale policy in the VoIP Server pool, adding a new VoIP server and adding itself to the gateway dispatch list so it can load balance and route calls.
4. If an infrastructure failure occurs in the VoIP Server pool a policy is triggered that will heal and recover the network service.

The use case behaviour from above is translated into the lifecycle manager's programming model of lifecycle dependencies, relationships and policies. The diagram below shows the main artefacts of the lifecycle VoIP service model.

The following lifecycle manager model artefacts are in place to automate the behaviour described above.

• VoIP Server dependency on GW external address: The VoIP servers need the gateway external IP address and CIDR to handle NAT SIP requests.
• VoIP Server scaling policy: Load metrics from the gateway trigger policies defined against the VoIP server cluster to scale in and out.
• DispatchList Relationship: New VoIP servers as a result of the scaling policy trigger a lifecycle relationship that adds information about the new VoIP server to the gateway dispatch pool or removes VoIP servers that no longer exist.
• SIPP dependency on GW external address: The SIPP VNF needs the external IP address of the gateway to send simulated traffic to.

These progamming artefacts are captured in all of the VoIP Network Service models/packages included in this project.

Two flavours of the VoIP Network Service are provided:

• Single VIM deployment with Tenant Networking: A basic VoIP service that runs in a single OpenStack region using tenant networking.
• Multiple VIMs with Provider Networking: An multi VIM version of the VoIP service deployed across Openstack and Kubernetes data centres.