Description:

As SDNC Systems Engineer, I need SDNC to support QuiesceTraffic LCM command, as described in ONAP Configuration Management Requirements.

Note: current description at ONAP website (http://onap.readthedocs.io/en/latest/submodules/vnfrqts/requirements.git/docs/Chapter7.html#onap-controller-apis-and-behavior) needs to be updated:

• Change “VNF gracefully stop” to “VNF to gracefully stop”
• Replace “StartTraffic” with “ResumeTraffic”

QuiesceTraffic command ONAP description:

QuiesceTraffic: The Controller client is requesting the VNF to gracefully stop traffic (a.k.a. block and drain traffic). The method for quiescing traffic is specific to the VNF architecture. The action is completed when all (in-flight transactions) traffic has stopped. The VNF remains in an active state where the VNF is able to process traffic (initiated using the StartTraffic ResumeTraffic action).

LCM API shall be used by client to invoke QuiesceTraffic LCM action in SDNC, as described in ONAP APPC API Guide document. SDNC controller shall interact with Ansible/Chef server to gracefully stop traffic on the L1-L3 VNF (i.e., no service interruption for traffic in progress).

Assumptions:

L1-L3 VNF In-Place Software Upgrade workflow to be used in Casablanca release to deliver QuiesceTraffic functionality.

APPC’s client library has a separate set of topics for SDNC, allowing it to support L1-L3 VNF LCM commands.

Dependencies:

This command results in an action executed on the L1-L3 VNF using an Ansible playbook or Chef cookbook. VNF vendor is expected to provide QuiesceTraffic (a.k.a. Block&Drain) functionality for L1-L3 VNF.