/
VF-C R3 Architecture Review

VF-C R3 Architecture Review

Aug 21, 2018

  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  https://lf-onap.atlassian.net/browse/VFC-1021
       HPA feature support  https://lf-onap.atlassian.net/browse/VFC-939
       Using composite key to specify Cloud Region  https://lf-onap.atlassian.net/browse/VFC-940

    3. Other updates 
      OOF integration  https://lf-onap.atlassian.net/browse/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 scalehttps://lf-onap.atlassian.net/browse/VFC-955
      POC:  PNF Orchestration Support  https://lf-onap.atlassian.net/browse/VFC-1022
                 Standard NS Descriptor Support   https://lf-onap.atlassian.net/browse/VFC-1041


  2. S3P Updates

    1. Security 

      1. https://lf-onap.atlassian.net/browse/VFC-937

      2. CII Badge: 

      3. WIP:Solve the remaining License and Vulnerability issue form Security subcommittee and Nexus IQ server   https://lf-onap.atlassian.net/browse/VFC-943

      4. WIP: Cooperation with the MSB project to integrate ISTIO to support communication encrypted and RBAC  https://lf-onap.atlassian.net/browse/VFC-1002

      5. WIP: Continue to increase test code coverage

    2. Manageability-Logging 

      1. https://lf-onap.atlassian.net/browse/VFC-933

      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. https://lf-onap.atlassian.net/browse/VFC-952

      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. https://lf-onap.atlassian.net/browse/VFC-935

      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. https://lf-onap.atlassian.net/browse/VFC-953

      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