Requirements concerning M.C.
NF: Non-functional requirement
F: Functional requirement
UC: Use-case
O: Other requirements
ID | catalog | How MultiCloud is concerned |
NF1 | S3P | "All communication shall be able to be encrypted and have common rolebased access control and authorization. " |
NF2 | Security | "TLS for security of HTTP connections" |
NF3 | Architecture Alignment | K8S plugin |
F1 | Centralized Representation and Consistent ID of Cloud Regions | ONAP need centralized representation and consistent ID of cloud regions to enable multiple cloud/VIM orchestration, and multicloud is the consumer of the ID |
F2 | EA/Cloud Infrastructure for Distributed Edge Clouds | MultiCloud services deployed on edge cloud offers values such as near real-time latency and aggregating for less bandwidth consumption in case of close loop automation Primary use case – Multi Cloud to be deployed as part of ONAP Central (Edge Scoping MVP for Casablanca - ONAP Enhancements)
|
F3 | HPA | SRIOV |
UC1 | vFW | Heat based orchestration, SO will leverage MutliVIM/Cloud for stack CRUD in C Release |
UC2 | vDNS | Heat based orchestration, SO will leverage MutliVIM/Cloud for stack CRUD in C Release |
O1 | Infrastructure upgrade | Integration Lab will be upgraded to Pike-based Titanium Cloud |
O2 | Infrastructure expansion | Orange lab is pike-based, new placement API available for HPA discovery |
O3 | Infrastructure expansion | Azure support |
Proposals:
Proposals for Casablanca | Correlation | Briefing | Prioritizing | Effort level estimation | Resource commitment |
Upgrade plugin for Wind River | O1 | Upgrade plugin for Wind River's new release of Titanium Cloud | High | low | Wind River as MVP |
New plugin for Pike | O2 | New plugin for Pike since pike based Titanium Cloud and pike based Orange Lab | High | medium | Wind River as MVP, Intel as MVP |
Consistent ID of cloud region enablement | F1, F2 | Support the functional requirement of "Centralized Representation and Consistent ID of a Cloud Region for ONAP" | High | Low to Medium | Wind River as MVP, VMware as MVP, Azure side support this as well. |
Deploy MultiCloud service to edge cloud with AAI in centralized ONAP | F2 | multicloud services deployed on edge clouds while AAI in central ONAP | low | low | Wind River as a stretch goal |
HEAT orchestration enhancement | UC1, UC2 | Enable M.C. to update AAI inventory after heat orchestration/scaling/termination is done via M.C. plugin | low | low | Wind River as a stretch goal, others? |
Cloud Region decommission | F1 | With centralized cloud region realized, it is good to decommission the cloud region with a single click | low | low | Wind River as a stretch goal |
Security enhancement: TLS based endpoint | NF2 | Enable secured endpoints for MultiCloud services | Medium | low | Wind River as a MVP |
Security enhancement: Integration with AAF | NF2 | Role based access control | Medium or High | High | Wind River as a stretch goal, but subject to TSC's decision |
Kubernetes plugin MVP | NF3 | Create a MVP that allows to use Kubernetes as MultilCloud plugin | Low | Low | Intel as a MVP |
Pike support & Traits | F3 | Support OpenStack Pike release and traits feature | High | High | Wind River as MVP, Intel as MVP |
| SRIOV-NIC support | F3 | HPA feature in OOF facilitates placing VDUs on the site that has compute nodes supporting needed SRIOV-NIC cards. Operators like to have flexibility of placing the workloads on non SRIOV-NIC machines in case there are no matching profiles. In HEAT templates, there is a challenge to have this kind of flexibility. | Medium or High | High | |
| Use OOF flavors | F3 | Using flavors returned by OOF and pass them as parameters to HEAT command line | Low | Medium | |
Aggregated Infrastructure Telemetry Streams | F2 | High | Medium | Intel as MVP | |
IaaS intent-based framework to support cloud agnostic intent for Compute/Network/Storage | F2 | High | High | VMware, Wind River, Intel, Amdocs (Microsoft) as MVP | |
Distributed Edge Cloud Infrastructure Capability Discovery adhering to the Infrastructure Modelling enhancements for Distributed Cloud | F2 | High | Low | VMware, Wind River, Intel, Amdocs (Microsoft) as MVP |