Page Comparison

Template:

1. What your team has achieved
2. Block issues / help needed

1. What your team has achieved
   
   1. vCPE: 
      1. Confirmed that the following interfaces related to CLAMP have been defined, implemented, and tested internally inside AT&T: SDC-CLAMP, SDC-DCAE, CLAMP-DCAE.
      2. SDC briefly confirmed that the vCPE model can be fully supported. Will hold a meeting with SDC to go through the details.
      3. Discussed with the VNF developers to revise the design to support auto healing closed loop control.
      4. Revised the service model to better emulate the real life situation.
      5. Confirmed the design process of policies for both closed loop and non-closed loop rules.

1. Block issues / help needed

   1. vCPE:
      1. To clarify the format of recipes and what tool to use to create such recipes (The SDC team does not have a answer to this).
      2. To confirm the support of the service model in SDC.
      3. To follow up with different projects to collect information and sample designs for each feature (refer Q22 on Use Case Related Important Questions and Answers)
      4. Need volunteers to work on tasks to implement vCPE.

• Reference VNFs (vFW/vLB)
  • Still working on the installation of the vLB/vDNS VNF in the WindRiver lab
  • Intel team is helping out with VPP LB configuration
  • Debugging patched VPP 1707 release in local OpenStack environment
• Testsuite
  • Implementing Java build for python code
  • Merging above code with oparent
  • Adding verify and merge jobs for python code in new format
  • Adding testing via tox in java based python
• O-Parent
  • Formally requested PTLs to update their POMs to inherit from oparent: https://lists.onap.org/pipermail/onap-discuss/2017-July/002762.html
  • Logged tracking JIRA issues against the O-Parent epic: 

    Jira Legacy
    server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key INT-5

  • Working on scripts to verify oparent implementation across projects
• Release
• Sent out poll to PTLs on interest in using a centrally managed standard docker build process: https://lists.onap.org/pipermail/onap-discuss/2017-July/002792.html
• Migrated docker image build scripts from OPEN-O
• VoLTE Use Case
  • Work done
    • Discussed VoLTE service design with SDC team during virtual developer event.  Agreed that SDC needs to support TOSCA for VoLTE use case
    • Discussed with SO team on TOSCA template support in workflow. Reviewed the new SO architecture design to support TOSCA
    • Reviewed VoLTE use case test strategies with the teams
    • Defined high level VoLTE test cases
  • Blocking Issue 
    • SDC still can not confirm it supports VoLTE template from Open-O in R1
• Developer Lab
  • Blocking Issues
    • Waiting for JIRA SO-21
      Facing permissions to push to Nexus - LF ticket raised #43778
      [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:deploy (injected-nexus-deploy) on project mso: Execution injected-nexus-deploy of goal org.sonatype.plugins:nexus-staging-maven-plugin:1.6.7:deploy failed: 403 - Forbidden -> [Help 1]"
• E2E Integration Lab
  • For CMCC lab, VoLTE case VNF sponsors are concluded. reference here
  • For CMCC lab, VoLTE case DC SDC interconnection sponsors are concluded, reference  here
  • vCPE case and default case (vFW/vLB) no special HW/SW requirements
• Bootstrap
  • Create epic and user stories in JIRA
  • Synchronized latest changes from github to git.onap.org
  • Implement AAI development set of instructions.
  • Add UTs for Policy module
• Yang presented VoLTE test cases.
• Kang has created vCPE test case here: vCPE Design and Test Cases