Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyCLAMP-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
      languagebash
      titleVES Data
  4. DCAE TCA sends an event to Policy through DMaaP. This is tested as described in 

    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyDCAEGEN2-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. 

    • APPC is working on some changes and will be able to test next week. 
    • There should be a MultiVIM VM in the stack but we don't see any. Refer
      Jira
      serverONAP JIRA
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyINT-258
       to track this problem.

In addition, the bottom of Policy R1 Amsterdam Functional Test Cases shows important sample data for vCPE test cases.