You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 8
Next »
Changes since Beijing
- No scope changes for VF-C R3 Architecture
- R3 Use Case and Functional Requirements
Supporting CCVPN usecase in VF-C
VFC-1021
-
Getting issue details...
STATUS
HPA feature support
VFC-939
-
Getting issue details...
STATUS
Using composite key to specify Cloud Region
VFC-940
-
Getting issue details...
STATUS
- Other updates
OOF integration
VFC-641
-
Getting issue details...
STATUS
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 scale
VFC-955
-
Getting issue details...
STATUS
POC
S3P Updates
Security
VFC-937
-
Getting issue details...
STATUS
- CII Badge:
- WIP:Solve the remaining License and Vulnerability issue form Security subcommittee and Nexus IQ server
VFC-943
-
Getting issue details...
STATUS
- WIP: Cooperation with the MSB project to integrate ISTIO to support communication encrypted and RBAC
VFC-1002
-
Getting issue details...
STATUS
- WIP: Continue to increase test code coverage
- Manageability-Logging
-
VFC-933
-
Getting issue details...
STATUS
- Have finished enable 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
-
VFC-659
-
Getting issue details...
STATUS
- Depend on kubernetes to manage VF-C components resiliency
- Split DB from current VF-C component?So that the VF-C components can support Horizontal scalability
- Usability
-
VFC-664
-
Getting issue details...
STATUS
- Document APIs in Swagger and solve inconsistent problem between code and API
- Improve the deployment and configuration documentation
- Performance and stability
-
VFC-663
-
Getting issue details...
STATUS
- 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.