- Architecture
Changes since Amsterdam
VF-C still works with other projects to implements LCM and FCAPS of VNF and NS.
No scope changes
S3P Updates
- SecurityNo scope changes for VF-C R2 Architecture
- Core components updates for supporting R2 Use Case
Scaling In/OutJira Legacy server System Jira serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176 key VFC-631 - Stretch goal
VF-C GVNFM demo
S3P Updates
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 - CII Badge:
- WIP:Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
- WIP:Increase test code coverage to reach 50%
- Manageability-Logging- WIP-Logging
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 - Update log configuration for VF-C components according to Logging guideline
- Filebeat container packed with VF-C existing container for shipping logs to ONAP ELK logging stack.
- Resiliency and Scalability
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 - Depend on kubernetes to manage multiple instances of stateless VF-C components
- stateless components
- Research the configuration in OOM
- Usability
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 - Document APIs in Swagger and solve inconsistent problem between code and API
- Improve the deployment and configuration documentation
- Performance and stability
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 - VF-C team will work with Integration team to do performance testing
IM/DM Alignment
- Align Service and Resource IM with following:
- ONAP R2+ Service IM Clean version Run Time Model Clean Version
VF-C team is participating the modeling discussion about Service/Resource IM/DM- Align Service and Resource IM with following:
- Stretch goal: Align with Service and Resource IM/DM proposed by the modelling subcommittee
API Updates
- Update APIs referenced to align with ETSI SOL003 and SOL005.
- NSLCM northbound APIs V2
- NSLCM southbound APIs
Grant V2
package V2 GVNFM northbound APIs V2