Page History

Changes since Amsterdam

1. Minimal (from an architecture perspective).  We still sit between the vendors and SDC to help package VNFs and perform pre-onboarding validation.

2. Scope increases include incorporating ICE tools into the "marketplace" and experimental integration with OPNFV Dovetail.

S3P Updates

1. Focus on enhanced security

   1. CII Badge: Image Removed
   2. Added https support (via nginx)
   3. Support for SOL-004
2. Code Cleanup
3. Documented APIs in Swagger (see #4)

IM/DM Alignment

1. VNF Package modeling sub-team
   1. models based on TOSCA, ETSI, and SDC models
      1. https://wiki.onap.org/display/DW/Design+Time+Model+Clean+Version
      2. Image Removed
   2. Contribution to ETSI NFV

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

   2. CII Badge: Image Added
   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
      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 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. 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 ETSI SOL003 and SOL005.

API Updates

1. APIs are stable - documented in Swagger
2. swagger.yaml
3. swagger.json