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

Version 1 Current »

  • Refactor CLAMP to inherit from oparent
  • Improve Unit Testing(UT) of ONAP on Vagrant
    • Added support for execution of a specific UT provided by the user.
    • Created a Teardown method to clean up installed components after a UT.

                     I could not access to the second one using Windows

Address ranges below are reserved by IANA for private intranets, and not routable to the Internet.

For additional information, see RFC 1918.

10.0.0.0 ~ 10.255.255.255 (10.0.0.0/8 prefix)

172.16.0.0 ~ 172.31.255.255 (172.16.0.0/12 prefix)

192.168.0.0 ~ 192.168.255.255 (192.168.0.0/16 prefix)

  • VoLTE Use Case
    • Presented data center SDN local controller API to set up VXLAN overlay network between data centers.  SDN-C team agreed the interface API
    • Hosted meeting to help CLAMP team understand VES interface and VFC data collection

  • Developer lab
    • Progressed on the closed loop testing by importing bug fixes, but now is blocked by open ticket -SO-21 - MSO returning error to VID during create service instance Open
    • Dependency on ONAP Helpdesk #43204 to solve SO-21 - MSO returning error to VID during create service instance Open

  •  CSIT
  • CI Management
  • E2E Integration Lab
    • Conclude on the mapping of physical labs and R1 three use cases.

      Lab NameSponsorUse CaseContact Point
      China Mobile ONAP LabChina MobileVoLTE
      China Telecom ONAP LabChina TelecomVoLTE/vCPE
      AT&T LabAT&TvCPE/vFW & vLB
      Multi-Geo LabsIntel & WindRivervCPE/vFW & vLB
      WINLABRutgers University & AT&T
      Orange Integration CenterOrange

      Call for vendor volunteers to support E2E integration test in physical labs 

  • Reference VNFs (vFW/vLB)
    • Successful installation of the vFW in the Intel/WindRiver lab
    • Installation of vLB still in progress. Currently debugging VPP and OpenStack configuration with the help of Intel and WindRiver teams
    • Kickoff call for possible collaboration with Intel teams on topics of mutual interest (VPP, VES, ...)
    • Reference VNFs alignment with VNF guidelines (discussed with Steven Wright from the VNF Guidelines team)
  • No labels