Changes since Beijing
- No scope changes for VF-C R3 Architecture
- R3 Use Case and Functional Requirements
Supporting CCVPN usecase in VF-CJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-1021
HPA feature supportJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-939
Using composite key to specify Cloud RegionJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-940 - Other updates
OOF integrationJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-641
New DB microservice. This stand-alone DB microservice is used to provide common DB for different VF-C component, So VF-C components can be stateless and can scaleJira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-955
POC
S3P Updates
Security
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-937 - CII Badge:
- WIP:Solve the remaining License and Vulnerability issue form Security subcommittee and Nexus IQ server
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-943 - WIP: Cooperation with the MSB project to integrate ISTIO to support communication encrypted and RBAC
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId 425b2b0a-557c-3c0c-b515-579789cceedb key VFC-1002 - WIP: Continue to increase test code coverage
- Manageability-Logging
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 - Update log configuration for VF-C components according to Logging guideline
933 - Have finished enable filebeat Filebeat container packed with VF-C existing container for shipping logs to ONAP ELK logging stack.
- Will try best to update log format to compile with logging specification V1.2
- Resiliency and Scalability
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 - Depend on kubernetes to manage multiple instances of VF-C stateless componentscomponents resiliency
- Split DB from current VF-C component?So that the VF-C components can support Horizontal scalabilityResearch the configuration in OOM
- Usability
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 - Document APIs in Swagger and solve inconsistent problem between code and API
- Improve the deployment and configuration documentation
- Performance and stability
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 - VF-C team will work with Integration team to do performance testing
IM/DM Alignment
- VF-C team is participating the modeling discussion about Service/Resource IM/DM
- Stretch goal: Align with Service and Resource IM/DM proposed by the modelling subcommittee
API Updates
- Update APIs referenced to ETSI SOL003 and SOL005.