Versions Compared

Old Version 1

changes.mady.by.user Helen Chen

Saved on

compared with

New Version Current

changes.mady.by.user Victor Morales

Saved on

Key

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

...

  1. What has your team achieved in past one week?
  2. Block issues / help needed from the community
  • Test
    • Begin work on adding vcpe VFs to the robot testsuite. Distribution failing currently in sdc.
    • Working on adding oparent version for python
  • Reference VNFs
    • Update installation scripts due to some recent cloud-init failure in Rackspace
    • No issue or blocker to report
  • vCPE Use Case
    • Installed Freeradius (vAAA), Bind (vDNS), and KEA (vDHCP)
    • On-boarded and distributed Heat templates via SDC: all the VMs were installed in Rackspace
    • Discussed with SO to understand the general process of associating a workflow with a service. The parameters passed to SO API are the key to specify which workflow to use. For vCPE, the initial understanding is that if the service level workflow is invoked from VID, there is no need to specify workflow inside SDC.
    • Discussed workflow design with SO team. Current SO is v1.0. It's generic service level workflow does not support the features required by vCPE. SO will be updated to v1.1 soon (hopefully by this Fri). The new version of generic service level workflow has more features needed by vCPE. We will have follow up meetings with SO to further study the workflow design.
    • Confirmed with Policy that it is feasible to use the Policy GUI to create closed loop control policy rules and load them into Policy engine directly.
    • vCPE Integration Test Case created. Feel free to update the wiki page with your input.


  • VoLTE Use Case
    • A&AI schema change to support ESR is done; schema change to support VFC is being tested now and close to finish
    • SDC finalized the import and export file format
    • SDC team listed the steps to design VoLTE E2E service with SDC GUI, and gave a partial demo. Support of VNF onboarding with TOSCA template is being developed
    • Discussed with SO team on VoLTE workflow design and SO interface 


  • Release / O-Parent
    • Independent Versioning and Release Process
      • Process documentations shared community for preview; expected to roll out this week
      • O-Parent has released its first artifact per above process; CLAMP trial in process pending a dependency on Policy 
      • Change in version manifest and version checking strategy
        • Version manifest and Maven plugin for version checks are moved to Integration repo, and will be completely outside of O-Parent and out-of-band from the normal build process.
        • The version-check Maven plugin will be an optional command-line tool for teams to check for updated dependencies.  Instructions for using the Maven plugin will be documented once it is finalized
    • Ongoing help to the community on Jenkins jobs, CSIT, O-Parent implementation

  • E2E Integration Lab

    • VMware has finished deploying VIO 4.0 (complain with Ocata) as TIC edge, including 9 nodes. VNF vendors will begin to integrate VNFs with VIO in TIC Edge in this week
    • Nokia has deployed S-VNMF in TIC core and begin to deploy vISCSCF and vTAS via S-VNFM
    • Huawei and ZTE has already deployed vMME(ZTE) and vPCRF(HUAWEI) in TIC core. HUAWEI is integrating vHSS with WindRiver Titanium.
  • Bootstrap
    • Complete the Unit Test coverage.
    • Add MultiCloud support.