Versions Compared

Old Version 14

changes.mady.by.user Kang Xi

Saved on

compared with

New Version 15

changes.mady.by.user Kang Xi

Saved on

Key

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

...

  1. Design and load policy rules to policy engine. 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
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyPOLICY-300
    . And the topics need to be added to APPC properties, see 
    Jira
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyAPPC-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 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
    serverONAP JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    serverId425b2b0a-557c-3c0c-b515-579789cceedb
    keyDCAEGEN2-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.
  5. Confirmed that the multi-cloud services are running inside the open-o VM as multiple containers
    1. The VM is vm1-openo-server with IP 10.12.25.113
    2. Service ports are listed below. More details of each service are described on Setup MultiCloud Development Env 
      1. broker: 9001
      2. VIO plugin: 9004
      3. Ocata plugin: 9006
      4. WindRiver plugin: 9005


Meeting recording is here: 

...