Name of Use Case:

vFW/vDNS

Use Case Authors:

AT&T

Description:

The vFW/vDNS use case as implemented currently and described in the demo configuration here:

Installing and Running the ONAP Demos

UCA-17 - Getting issue details... STATUS

Users and Benefit:

Allows for quick and easy demos without any infrastructure or lab constrains.

Can be easily automated for daily integration testing.

VNF:

vFW

vPacketGenerator

vDataSink

vDNS

vLoadBalancer

all VPP based.

Work Flows:

Instantiation
Performance based control loop

In this section we will show the work flows for the vFW and vDNS use case. Two section: one is the reference from the original prototype and the second is the new sequence diagram for Release 1.

0. Original Sequence Diagram (R0)

0.1 Onboarding (Old Flow)

0.2 Instantiation (old flow)

0.3 Control Loop for vFW (Old Flow)

0.4 Control Loop vDNS (Old Flow)

Release 1 Flows:

The order of flows would not be how CI testing would flow. that would be VNF Certification, Onboarding, CLAMP, Instantiation, Closed Loop vFW , Closed Loop vDNS and then Delete of vFW and vDNS.

1.1 Onboarding

1.2 Instantiation

1.3. Closed Loop vFW

1.4 Close Loop vDNS

1.5 CLAMP creation of control loops (new in R1)

1.6 VNF Certification (new in R1)

Control Automation:

See: Installing and Running the ONAP Demos

Override the default ssh key in the env file to be able to ssh to any of the 3 VMs instantiated by the demo.

Project Impact:

No additional work.

Work Commitment: