Page History

10/

...

9/2017

Closed loop control test is decomposed into the following items.

1. Design and load policy rules t to policy engine. Ideally this should be done by CLAMP. Currently CLAMP is working on Jorge Hernandez created a closed loop for vCPE. Policy is tested by posting a DCAE TCA event on DMaaP. Policy reacted by sending an event to APPC to trigger VNF restart. The message format needs to be fixed, see

   Jira
   server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CLAMPPOLICY-59300

   . The workaround is to use Policy GUI. Jorge Hernandez will work on this.Preload AAI with vCPE data. The purpose is to lookup vServer using vGMUX VNF ID. Scott Seabolt (APPC) will provide a sample data to Venkata Harish Kajur (AAI) to show the named query. Venkata Harish Kajur will then create a script to preload such data to AAI for the testing.And the topics need to be added to APPC properties, see 

   Jira
   server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key APPC-265

   .

2. Scripts are created to preload AAI. Scott Seabolt tested them in the integration environment. Both preloading and named query works.
   closed-loop.zip contains  contains the necessary data (json) as well as shell scripts to load the Integration vGMUX.  Note the attached files load data specific the the "vCPE_Infrastructure_vGMUX_demo_app" VNF.  If you'd like to load a different VNF each of the json files owuld need to be modified to reflect the new VNF.
   

   1. put_closed_loop.sh

      • usage: put_closed_loop.sh A&AI-IP
   2. verify.sh
      
      • usage: verify.sh A&AI-IP
3. VES collector is working. Waiting for sample VES data from Eric Multanen. See 

   Jira
   server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key DCAEGEN2-135

   . Once the data is available, the TCA policy on Policy R1 Amsterdam Functional Test Cases may need to be adjusted and then TCA testing can be performed.
4. vGMUX cannot be properly instantiated. Eric Multanen, Marco Platania, and Kang Xi are working to solve it.

Meeting recording is here: 

https://zoom.us/recording/play/i3Eceu20OwK3_MiECV08u6lsGEy_QRp6q6-NEqJg-NWas_9Ap1s16Rk1clAWSmgL

10/6/2017

Closed loop control test is decomposed into the following items.

1. Design and load policy rules to policy engine. Ideally this should be done by CLAMP. Currently CLAMP is working on

   Jira
   server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key CLAMP-59

   . The workaround is to use Policy GUI. Jorge Hernandez will work on this.

2. Preload AAI with vCPE data. The purpose is to lookup vServer using vGMUX VNF ID. Scott Seabolt (APPC) will provide a sample data to Venkata Harish Kajur (AAI) to show the named query. Venkata Harish Kajur will then create a script to preload such data to AAI for the testing.

3. vGMUX sends packet loss VES to DCAE VES collector.

   • Kang Xi created a vGMUX instance in the open lab but the VPP-based VNF inside the VM is not functioning. According to Eric Multanen, most likely it is caused by network issues. Eric is working on this. Kang will also inform Danny Zhou and Johnson Li about this.

   • The following VES data caused an error. The most possible reason is that the data itself is incorrect. Vijay Venkatesh Kumar is looking into that.

     Code Block
     language bash title VES Data
     curl -H "Accept: application/json" -H "Content-Type: application/json" -d '{"event":{"measurementsForVfScalingFields":{"measurementInterval":10,"measurementsForVfScalingVersion":1.1,"vNicUsageArray":[{"multicastPacketsIn":0,"bytesIn":4300,"unicastPacketsIn":0,"multicastPacketsOut":0,"broadcastPacketsOut":0,"packetsOut":0,"bytesOut":0,"broadcastPacketsIn":0,"packetsIn":101,"unicastPacketsOut":0,"vNicIdentifier":"eth1"}]},"commonEventHeader":{"reportingEntityName":"zdfw1fwl01fwl01","startEpochMicrosec":1500379662497999,"lastEpochMicrosec":1500379672497999,"eventId":"1","sourceName":"zdfw1fwl01fwl01","sequence":1,"priority":"Normal","functionalRole":"vFirewall","domain":"measurementsForVfScaling","reportingEntityId":"No UUID available","sourceId":"75ec15e4-1a9a-4ee3-bb3c-31556903558d","version":1.2}}}' 10.12.25.84:8080/eventListener/v5

4. DCAE TCA sends an event to Policy through DMaaP. This is tested as described in 

   Jira
   server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key DCAEGEN2-124

5. Policy process the event from DCAE, and then sends a “restart” event to APPC through DMaaP. Jorge Hernandez will work on this.

6. APPC captures the event from Policy, performs a named query to AAI to get the vServer ID based on the VNF ID, and then restarts the VM through MultiVIM. 

...