/
VF-C R3 Architecture Review

VF-C R3 Architecture Review

Owned by Yan Yang
Last updated: Aug 21, 2018
2 min read

  1. Changes since Beijing

    1. No scope changes for VF-C R3 Architecture

    2.  R3 Use Case and Functional Requirements
       Supporting CCVPN usecase in VF-C  VFC-1021: Support CCVPN use case in VF-CClosed
       HPA feature support  VFC-939: HPA feature support Closed
       Using composite key to specify Cloud Region  VFC-940: Using composite key to specify Cloud Region Closed

    3. Other updates 
      OOF integration  VFC-641: Integration with OOFClosed
      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 scaleVFC-955: Create One Single DB MicroservceClosed
      POC:  PNF Orchestration Support  VFC-1022: POC: PNF Orchestration SupportClosed
                 Standard NS Descriptor Support   VFC-1041: POC: Standard NS Descriptor support in VF-CClosed


  2. S3P Updates

    1. Security 

      1. VFC-937: Support platform Maturity Requirements-Security Level 1+Closed

      2. CII Badge: 

      3. WIP:Solve the remaining License and Vulnerability issue form Security subcommittee and Nexus IQ server   VFC-943: No critical or high known vulnerabilities > 60 days Closed

      4. WIP: Cooperation with the MSB project to integrate ISTIO to support communication encrypted and RBAC  VFC-1002: Istio IntegrationClosed

      5. WIP: Continue to increase test code coverage

    2. Manageability-Logging 

      1. VFC-933: Support platform Maturity Requirements-Manageability Level 1+Closed

      2.  Have finished enable filebeat container packed with VF-C existing container for shipping logs to ONAP ELK logging stack.

      3.  Will try best to update log format to compile with logging specification V1.2

    3. Resiliency and Scalability  

      1. VFC-952: Support platform Maturity Requirements-Scalability level 1Closed

      2. Depend on kubernetes to manage VF-C components resiliency

      3. Split DB from current VF-C component.So that the VF-C components can support Horizontal scalability

    4. Usability  

      1. VFC-935: Support platform Maturity Requirements- Usability Level 1Closed

      2. Follow the new guidelines for providing API documentation

      3. Document APIs in Swagger and solve inconsistent problem between code and API

      4. Improve the user guide and deployment documentation

    5. Performance and stability

      1. VFC-953: Support platform Maturity Requirements-Performance Level 1Closed

      2. VF-C team will work with Integration team to do performance test and 72 stability soak test


  3. IM/DM Alignment

    1. VF-C team is participating the modeling discussion about Service/Resource IM/DM

    2. In R2, VF-C have aligned with R2 DM proposed by the modelling subcommittee, In R3, will continue to align R2+ DM updates.


  4. API Updates

                 VF-C R3 API Update

  1.  

    1. Update GVNFM Northbound APIs to align ETSI SOL003.

    2. Add OOF Integraton Callback API