Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project NameEnter the name of the project
Multi VIM/CloudBeijing
Project Lifecycle StateCoreIncubation
Participating Company Amdocs, AT&T, ChinaMobile, Huawei, Intel, Lumina Networks, Microsoft, Mirantis, VMware, WindRiver, ZTE

...

1 Event/Alert/Metrics federation (S3p)

2 Elastic API exposure (Towards model-driven)

3 Parallelism improvement of Multi Cloud Services (S3p)Services

4 Logging Enablement  (S3p)

5 Standardized Infrastructure Resource Information Model (Towards model-driven)

6 FCAPS modeling (Towards model-driven)

7 Image service (Function enhancement)

Enabling

5 Image service

6 8 Clustering service interfaces for query and placement of a group of resources (Function enhancement)

9 7 HPA resource discovery and representation for HPA awareness orchestration (Function enhancement)

10 TOSCA-based orchestration to deploy workload on multiple clouds

11 MultiCloud Plugin for K8S (Function enhancement)

12 MultiCloud support for Azure (Function enhancement)

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

This release we targeted to implement MVP features and finish regression of all existing use cases. The longer goal is to intergate with different dependent modules to consume the advanced features.

1 Standardized Infrastructure Resource Information Model (Towards model-driven)

2 FCAPS modeling (Towards model-driven)

3 TOSCA-based orchestration to deploy workload on multiple clouds (Towards model-driven)

4 MultiCloud support for Azure (Function enhancement)

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

...

Sub-components are repositories and are consolidated in a single centralized place. Edit the Release Components name for your project in the centralized page.

...

Please refer to below graph for a high level project scope architecture. the Fcaps part will involve data collection and event/metrics/alerts federation part as below graph.

Please refer to below chart for the even-driven framework.

...

Risk identifiedMitigation PlanContingency Plan
APPC event integrationkeep the existing waywork together on vm polling part of code
OOF event integrationkeep the existing waywork together on Clustering query and resource graphs update
DCAE integrationkeep the existing wayidentify examples of alert/metrics
AAI integrationkeep the existing wayidentify examples of HPA
  • Resources

Fill out the Resources Committed to the Release centralized page.

  • Release Milestone

...