Versions Compared

Old Version 27

changes.mady.by.user Yan Yang

Saved on

compared with

New Version Current

changes.mady.by.user maopeng zhang

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/OutOut  
      Jira Legacy
      serverSystem Jira
      serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
      keyVFC-631
    3. Stretch goal
      VF-C GVNFM demo 

  2. S3P Updates

    1. Security 

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

      2. CII Badge: 
      3. WIP:Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
      4. WIP:Increase test code coverage to reach 50%
    2. Manageability-Logging 
      1. Jira Legacy
        serverSystem Jira
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyVFC-639
      2. Update log configuration for VF-C components according to Logging guideline 
      3. 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 VF-C stateless components
      2. Research the configuration in OOM
      3. Jira Legacy
        serverSystem Jira
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyVFC-659
      4. Depend on kubernetes to manage multiple instances of VF-C stateless components
      5. Research the configuration in OOM
    4. Usability  
      1. Jira Legacy
        serverSystem Jira
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyVFC-664
      2. Document APIs in Swagger and solve inconsistent problem between code and API
      3. Improve the deployment and configuration documentation
    5. Performance and stability
      1. VF-C team will work with Integration team to do performance testing 
      2. Jira Legacy
        serverSystem Jira
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
        keyVFC-663
      3. VF-C team will work with Integration team to do performance testing 

  3. IM/DM Alignment

    1. VF-C team is participating the modeling discussion about Service/Resource IM/DM
    2. Stretch goal: Align with Service and Resource IM/DM proposed by the modelling subcommittee

  4. API Updates

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