Page Comparison

Changes since Amsterdam

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

S3P Updates

1. Security 

   Jira Legacy
   server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key VFC-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- 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 and Scalability
   
   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 
      
      

IM/DM Alignment

1. Strech goal: Align Service and Resource IM/DM which is proposed the modelling subcommittee's proposed informatio
   
   1. ONAP R2+ Service IM Clean version
   2. Run Time Model Clean Version
      
      

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