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 16 Next »

  1. Architecture Changes since Amsterdam

    1. VF-C still works with other projects to implements LCM and FCAPS of VNF and NS.

    2. No scope changes

  2. S3P Updates

    1. Security-

      1. CII Badge: 
      2. WIP:Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
      3. WIP:Increase test code coverage to reach 50%
    2. Manageability-Logging- WIP
      1. Update log configuration for VF-C components according to Logging guideline 
      2. Filebeat container packed with VF-C existing container for shipping logs to ONAP ELK logging stack.
    3. Resiliency
      1. Depend on kubernetes to manage multiple instances of stateless VF-C components
    4. Usability
      1. Document APIs in Swagger and solve inconsistent problem between code and API
    5. Performance and stability
      1. VF-C team will work with Integration team to do performance testing 

  3. IM/DM Alignment

    1. Align Service and Resource IM with following:
      1. ONAP R2+ Service IM Clean version
      2. Run Time Model Clean Version

  4. API Updates

    1. Update APIs to align with ETSI SOL003 and SOL005.
      1. NSLCM northbound APIs V2
      2. NSLCM southbound APIs 
          Grant V2
          package V2
      3. GVNFM northbound APIs V2
         
  • No labels