You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

  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 - 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
    3. 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 

  2. S3P Updates

    1. Security 

      1. VFC-937 - Getting issue details... STATUS

      2. CII Badge: 
      3. WIP:Solve the remaining License and Vulnerability issue form Security subcommittee and Nexus IQ server    VFC-943 - Getting issue details... STATUS
      4. WIP: Cooperation with the MSB project to integrate ISTIO to support communication encrypted and RBAC   VFC-1002 - Getting issue details... STATUS
      5. WIP: Continue to increase test code coverage
    2. Manageability-Logging 
      1. VFC-933 - Getting issue details... STATUS
      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-659 - Getting issue details... STATUS
      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-664 - Getting issue details... STATUS
      2. Document APIs in Swagger and solve inconsistent problem between code and API
      3. Improve the deployment and configuration documentation
    5. Performance and stability
      1. VFC-663 - Getting issue details... STATUS
      2. VF-C team will work with Integration team to do performance testing 

  3. IM/DM Alignment

    1. VF-C team is participating the modeling discussion about Service/Resource IM/DM
    2. Stretch goal: Align with Service and Resource IM/DM proposed by the modelling subcommittee

  4. API Updates

    1. Update APIs referenced to ETSI SOL003 and SOL005.
  • No labels