Page History

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. No scope changes for VF-C R2 Architecture
2. Core components updates for supporting R2 Use Case 
    Scaling In/Out  

   Jira
   server ONAP JIRA serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-631

3. Stretch goal
   VF-C GVNFM demo 
   
   

S3P Updates

1. Security 

   1. Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-660

   Security

   2. CII Badge: 
   3. WIP? solve :Solve License and Vulnerability ThreadThread form Security subcommittee and Nexus IQ server
   4. WIP ?:Increase test code coverage to reach 50%
2. Manageability
   
   1. WIP : Integration with Logging to push log data to logging system
   -Logging 
   

   1. Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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.
3. Resiliency and Scalability  
   

   1. Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-664

   2. Document
   Usability
   
   1. Improve VF-C documentation 
   2. WIP: Documented APIs in Swagger and solve inconsistent problem between code and API
   3. Improve the deployment and configuration documentation
5. Performance and stability
   

   1. Jira
      server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb 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:
3.  VNFM Driver northbound APIs:
GVNFM APIs: