Versions Compared

Old Version 20

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
      serverONAP JIRA
      serverId425b2b0a-557c-3c0c-b515-579789cceedb
      keyVFC-631
    3. Stretch goal
      VF-C GVNFM demo 

  2. S3P Updates

    1. Security 

      1. Jira
        serverONAP JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        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
        serverONAP JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        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 ScalabilityScalability  
      1. Jira
        serverONAP JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyVFC-659
      2. Depend on kubernetes to manage multiple instances of stateless VF-C componentsstateless components
      3. Research the configuration in OOM
    4. Usability  
      1. Jira
        serverONAP JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyVFC-664
      Usability
      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. Jira
        serverONAP JIRA
        columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
        serverId425b2b0a-557c-3c0c-b515-579789cceedb
        keyVFC-663
      2. 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 Strech goal: Align with Service and Resource IM/DM which is proposed by the modelling subcommittee's proposed informatio
      ONAP R2+ Service IM Clean version
      Run Time Model Clean Version

  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