You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 14
Next »
Changes since Amsterdam
- No scope changes for Multi VIM/Cloud R2 Architecture
- Core components updates for supporting R2 Use Case
MULTICLOUD-148
-
Getting issue details...
STATUS
- Stretch goal
- Standardized Infrastructure Resource Information Model (Under going)
- FCAPS modeling (under going)
- TOSCA-based orchestration to deploy workload on multiple clouds (need discussion with Architecture Sub-committee)
- MultiCloud support for Azure (under discussion and will not allocate JIRA or input code into epo for tracking purpose)
- 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)
S3P Updates
Security
MULTICLOUD-175
-
Getting issue details...
STATUS
- CII Badge:
![Badge level for project 1706 is passing](https://bestpractices.coreinfrastructure.org/projects/1706/badge)
- WIP:Solve License and Vulnerability Thread form Security subcommittee and Nexus IQ server
- WIP:Increase test code coverage to reach 50%
- Manageability-Logging
-
MULTICLOUD-151
-
Getting issue details...
STATUS
- Update log configuration for Multi VIM/Cloud components according to Logging guideline
- Filebeat container packed with Multi VIM existing container for shipping logs to ONAP ELK logging stack.
- Resiliency and Scalability
-
MULTICLOUD-150
-
Getting issue details...
STATUS
- Depend on kubernetes to manage multiple instances of Multi VIM/Cloud stateless components
- add Multi VIM service and recovery capability
- depends on geographic scaling
- Usability
-
MULTICLOUD-152
-
Getting issue details...
STATUS
- No UI and tutorial documentation need more work
- Performance and stability
-
MULTICLOUD-149
-
Getting issue details...
STATUS
- Multi VIM/Cloud team will work with Integration team to do performance testing
IM/DM Alignment
-
MULTICLOUD-153
-
Getting issue details...
STATUS
-
MULTICLOUD-154
-
Getting issue details...
STATUS
API Updates