Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Current »

Template:

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

  • Test
    • Conducted CSIT Q&A session to answer questions from the community
    • Working with ATT and Amdocs lead initiative to stabilize the master branch of ONAP 1.1. See [onap-discuss]  Stabilized ONAP master branch
  • Creation of Jira Filters & Dashboard:
  • Release / O-Parent
    • Artifact versioning:

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

        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.
      • Work on defining JJB jobs and process for project teams to version bump and release their own artifacts
        • Blocking Issue: Need input/response from LF staff on a process to officially release artifacts (i.e. to actual Releases repo, not just to Staging)
      • Investigated tools to help with with Maven artifact version dependencies:
        • Use maven-enforcer-plugin to avoid SNAPSHOT dependencies
        • Help Needed: Need help finding or creating a Maven plugin that can check against an explicit artifact version list such as the ONAP version manifest
    • Ongoing work on docker image build guidelines/approach for OPEN-O seeded microservices
    • Ongoing code reviews and assistance to the community on ci-management and environment issues
  • Bootstrap:
    • It was create a helper script for Windows users
    • The documentation can be generated in HTML format thru Sphinix tool.
    • MSO and Policy Unit tests were improved.
  • E2E Integration Lab
    • CMCC lab reconstruction is almost done. 
    • Remotely access environment is set up, still being test
    • WindRiver is deploying Titanium Cloud as TIC core. will to be done by the end of this week.
  • Reference VNFs
    • Architectural changes to the vLB/vDNS VNF
    • Installation and test in private OpenStack lab
    • Soon we'll schedule a meeting with Intel/Cisco teams for discussing possible improvements
  • vCPE use case
    • Created heat templates and installation scripts for the vCPE VMs
    • Tested successfully in Rackspace, test is going on in private OpenStack labs
    • Need to talk to Danny to see how to onboard configuration of vCPE components into install scripts
    • Discussed the set up of each virtual network and the specific requirements to SDNC.
    • Discussed work flow design with SO. It was clarifies that Dewayne will create tosca templates for selected VNFs and the rest VNFs will keep using heat.
    • An urgent task is to identify people to work on the workflow design. 
    VoLTE use case
    • Worked with DCAE team to resolve blocking issues
    • Reviewd VoLTE use case in community
    • Reviewed Usecase UI support for VoLTE use case with Usecase UI team
    • Reviewed ESR interface to support VoLTE use case with ESR team

  • No labels