August 1st to 7th, 2017

Owned by cl664y@att.com
Last updated: Aug 10, 2017 by Chengli Wang
3 min read

Template:

  •  

    •  

      1. What your team has achieved

      2. Block issues / help needed



  • Reference VNFs (vFW/vLB)

    • vLB/vDNS demo with patched VPP 1707 not working consistently in local OpenStack

    • Next steps:

      • Work out a stable vLB/vDNS installation process with Intel/VPP team

      • Test the VNF in local environment, WindRiver lab, and Rackspace

  • Test

    • Provided assistance on CSIT questions and implementation

    • Created ONAP Helpdesk #43963 for external repo not connectable. Will merge changes in once ticket closes, but this is blocker.

    • Added tox support to python based build

    • Have sample of oparent integration mostly building (up to test)

  • vCPE use case

    • Working on the Heat template that spin up the use case networks and VMs

    • Reviewed detailed network design/configuration, need to clarify the network configuration between vGMUX-vGs

    • Revised service model to mimic real life scenario better

    • Discussed service model with SDC, no main issues identified

    • Discussed service model and work flows with SO. Will continue the discussion with the goal of creating sample designs.

    • Had a preliminary discussion with SDNC team to review features required. Will continue the discussion this week.

    • Please review and update the design and test cases and sign up for the working items: vCPE Design and Test Cases

  • VoLTE use case

    • SDC/SO/Modeling teams have agreed upon the approach to support TOSCA template as input for VoLTE use case

    • Reviewed an example of VoLTE TOSCA template from Open-O

    • Discussed two blocking issues reported from DCAE team (how to do service registration/discovery in both VM and container environment)

    • Finished the draft of VoLTE integration test cases

    • SDC TOSCA template details have not been finalized, teams will have two more meetings to discuss this week 

  • Release / O-Parent

    • Artifact versioning:

      • ONAP will support individual artifacts having their own versions and release schedules

      • Implementation details ongoing; should be finalized shortly :
                

        1. Move the declared artifact version list outside the build in order to avoid SNAPSHOT dependencies.

        2. Provide a tool (plugin or script) to automatically warn against outdated dependencies vs. the declared version list.

        3. Define the official ONAP version string (e.g. "ONAP R1 Amsterdam Release") inside the oparent artifact or POM.

        4. Require that all artifacts be built against the latest oparent release version for the ONAP release.  Note that the oparent artifact version itself might be something like 1.0.2 which is distinct from the official ONAP version string contained within.

    • Helped prepare custom Jenkins slave VM images via packer for team requiring custom build environment

    • Code reviews and assistance on ci-management JJB submissions made by the community

  • Intel Developer Labs:

    • The Intel Hudson cloud (currently in use) has ~6TB storage, it is close to capacity.

    • The Intel Pharos ONAP cloud (POD-25) is installed as of last week - this cloud includes 74TB of combined local and shared storage.

    • POD-25 is awaiting IT approval for the external connections.  The external connection is expected to be approved this week.

    • Once the external connection is approved we will begin to move the development to Pharos POD-25

    • The goal is to complete the move (move all ONAP developers from Hudson to Pharos) by the end of Aug.

    • A request has been submitted to IT to connect POD-25 to POD-14 via a tunnel to allow a VXLAN connection, for deployment testing.

  • Bootstrap

    • Created Unit Tests that covers lib/aai script

    • Refactor the current Unit Tests.

  • E2E Integration Lab

    • For VoLTE case, CMCC lab is redesigning and reconstructing network topology, will conclude before next week ideally.

    • There are some discussion on how to integrate with each other between VoLTE case sponsors. They need reach some consensus before actions.

    • For vCPE case, WindRiver and Intel Multi-geo lab will be the chosen to do the E2E test.  Since there is no special requirements for hardware, it will be ready after intel team delivering relevant VPPs.

  • Developer Lab