Skip to end of metadata
Go to start of metadata

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 Amsterdam

    1. No scope changes for Multi VIM/Cloud R2 Architecture
    2. Core components updates for supporting R2 Use Case 
        MULTICLOUD-148 - Getting issue details... STATUS
    3. Stretch goal
      1. Standardized Infrastructure Resource Information Model (Under going)
      2. FCAPS modeling (under going)
      3. TOSCA-based orchestration to deploy workload on multiple clouds (need discussion with Architecture Committee)
      4. MultiCloud support for Azure (under discussion and will not allocate JIRA or repo for tracking purpose)
      5. POC of Containerized VNF through some use cases (will not allocate JIRA or repo; will invite the team to review POC once ready for formal plan of Casablanca)

  2. S3P Updates

    1. Security 

      1. MULTICLOUD-175 - Getting issue details... STATUS

      2. WIP:Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
      3. WIP:Increase test code coverage to reach 50%
    2. Manageability-Logging 
      1. MULTICLOUD-151 - Getting issue details... STATUS
      2. Update log configuration for Multi VIM/Cloud components according to Logging guideline 
      3. Filebeat container packed with Multi VIM existing container for shipping logs to ONAP ELK logging stack.
    3. Resiliency and Scalability  
      1. MULTICLOUD-150 - Getting issue details... STATUS
      2. Depend on kubernetes to manage multiple instances of Multi VIM/Cloud stateless components
      3. Research the configuration in OOM
    4. Usability  
      1. MULTICLOUD-152 - 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. MULTICLOUD-149 - Getting issue details... STATUS
      2. VF-C team will work with Integration team to do performance testing 

  3. IM/DM Alignment

    1. Multi VIM/Cloud internal discussion and team discussion (with VES)
    2. Stretch goal: Draft IM/DM proposals for the modelling subcommittee

  4. API Updates

    1. https://wiki.onap.org/display/DW/Externally+Consumable+APIs


  • No labels