Versions Compared

Old Version 1

changes.mady.by.user Catherine Lefevre

Saved on

compared with

New Version Current

changes.mady.by.user Helen Chen

Saved on

Key

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

Template:

  1. What has your team achieved in past one week?
  2. Block issues / help needed from the community


vCPE use case:

  • Service flow updated to eliminate "homing emulator" and the corresponding "homing" step.
  • Discussed with SDC and SO regarding use case design issues. Clarified that the use case requires both generic and custom flows. Scheduled a follow-up meeting with SDC to discuss specific design process and issues and possibly a demo. Help is needed from SO regarding custom workflow design process.
  • vCPE-Infra Heat template on-boarding via SDC successfully tested with ONAP code in release-1.0.0 branch.
  • vCPE-Infra on-boarding doesn't work with ONAP code in master branch. This is blocked by known issue with VID.
  • Marco reached out to Danny for an ETA about vCPE component installation.
  • vCPE test case needs to be done this week.


VoLTE use case

  • SDC WAN service definition was reviewed. Only basic properties will be used in WAN service template for R1
  • SDC import and export Tosca CSAR file structure was reviewed
  • A&AI schema change for the use case was reviewed
  • Test cases for VoLTE was updated


Reference VNFs (vFW/vLB)

  • Both vFW and vLB installed and executed correctly in the following labs:
    • Rackspace
    • Private OpenStack Liberty lab
    • Private OpenStack Mitaka lab
    • WindRiver lab
  • Issues with vDNS scaling scenario solved with help of Intel VPP team.
  • No current issue to report.


Developer Lab

  • Installed ONAP1.1 in WindRiver lab, all ONAP components passed sanity test 
  • Managed to pass vFW onboarding and service creation, and blocked on service instantiation. It seems the problem is in MSO, reported the issue on wiki
  • Need 2~3 engineers help the weekly installation and sanity test. (After RC0, we need to do it daily)


Release / O-Parent

  • Ongoing work on independent versioning/release process
  • Initial implementation of dependency version checks and SNAPSHOT dependency warnings
  • Set up site (javadoc) deployment support config in O-Parent
  • Cleaned up accidental release artifacts from Nexus
  • Ongoing assistance to project teams on docker build jobs, CSIT, build environment setup (redis, memcached), etc.


Bootstrap

  • Created UTs for APPC, DCAE and VID modules.
  • Refactored AAI source code module.
  • Fixed the process to setup Titan Graphical Database.
  • Added an article about how to use the scripts and functions without the requirement of Vagrant.


E2E Integration Lab

  • VMware is deploying VIO as TIC edge, including 9 nodes. Guest OS( ESXi ) is almost be done, next step they will deploy VIO software.
  • Huawei and ZTE have already deployed S-VNFM and begin to try to instantiate vMME/vHSS/vPCRF in TIC core to do the integration test with WindRiver Titanium Cloud.
  • Nokia has allocated dedicated resources to do the installation of S-VNFM and integration with WindRiver Titanium Cloud in TIC core, will begin from mid of this week.