Page Comparison

Changes since Amsterdam

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

2. No scope changes

S3P Updates

1. SecurityNo scope changes for VF-C R2 Architecture
2. Core components updates for supporting R2 Use Case 
    Scaling In/Out  

   Jira Legacy
   server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key VFC-631

3. Stretch goal
   VF-C GVNFM demo 
   
   

S3P Updates

1. Security 

   1. 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

   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-Logging 
   

   1. 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-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.
   Usability
   
   1. Improve VF-C documentation 
   2. Documente
3. Resiliency and Scalability  
   

   1. 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-659

   2. Depend on kubernetes to manage multiple instances of VF-C stateless components
   3. Research the configuration in OOM
4. Usability  
   

   1. 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-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. 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-663

   2. VF-C team will work with Integration team to do performance testing 
      
      

IM/DM Alignment

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

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
   
   

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
GVNFM northbound APIs V2