Versions Compared

Old Version 21

changes.mady.by.user Yan Yang

Saved on

compared with

New Version 22

changes.mady.by.user Yan Yang

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  1. Changes since Amsterdam

    1. No scope changes for VF-C R2 Architecture
    2. Core components updates for supporting R2 Use Case 
       Scaling In/Out
    3. Stretch goal
      VF-C GVNFM demo 

  2. S3P Updates

    1. Security 
      Jira Legacy
      serverSystem Jira
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyVFC-660

      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 
      Jira Legacy
      serverSystem Jira
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyVFC-639

      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 and Scalability
      1. Depend on kubernetes to manage multiple instances of stateless VF-C components
    4. Usability  
      Jira Legacy
      serverSystem Jira
      columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyVFC-664

      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. Strech Stretch goal: Align Service and Resource IM/DM which is proposed by the modelling subcommittee's proposed informatio
      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