...
The use cases to be enabled by this project are as follows:
| ID | Description |
|---|---|
| 1 | Dynamic composition and deployment of NFV virtual infrastructure instances in-band, as part of network service instantiation, or out-of-band, as part of NFV infrastructure management. Examples of virtual infrastructures include OpenStack and Kubernetes instances. |
| 2 | Dynamic composition and rightsizing of virtual infrastructure resources for use during VNF homing and placement. |
| 3 | On-demand scaling of virtual infrastructure capacity. |
| 4 | On-demand scaling of virtual infrastructure resources, within a given virtual infrastructure instance. |
| 5 | Dynamic resource sharing, balancing and reuse between multiple and different virtual infrastructure instances. |
The benefits of using composable disaggregated NFV infrastructure (NFV-I) are as follows:
...
The following functionality will provided:
Deliverables | MVP | |
|---|---|---|
| 1 | DMTF Redfish® API adapter (management/composition) | Yes |
| 2 | Redfish® API based automated resource composition and instantiation | Yes |
| 3 | Redfish® API based automated virtual infrastructure composition and scaling | - |
| 4 | TOSCA based resource, IaaS and PaaS composition and instantiation | - |
| 5 | CLIs/SDKs for programmatic access | Yes |
| 6 | HPA support | |
| 7 | AAI integration (inventory/capacity information) | Yes |
| 8 | DCAE integration (telemetry) | - |
| 9 | Orchestration integration (composition/scaling) | - |
| 10 | Multi-Cloud integration (infrastructure adaptation) | Yes |
| 11 | OOF integration (optimization) | - |
...
The following diagram illustrates how project functionality fits in with the rest of ONAP components. The "CDI Infrastructure Management Adapter" component, shown in the diagram, contains the bulk of the implementation and consists of "glue code" required to interaction between ONAP components' native interfaces, DMTF Redfish APIs and TOSCA templates.
The project depends on the following ONAP components:
| Component | Dependency | |
|---|---|---|
| 1 | AAI | Inventory and capacity data integration |
| 2 | DCAE | Telemetry integration |
| 3 | SO | Resource and/or virtual infrastructure environment optimization and scaling during instantiation |
| 4 | APPC | Resource and/or virtual infrastructure environment optimization and scaling during operation and remediation |
| 5 | VF-C | Resource and/or virtual infrastructure environment optimization and scaling during instantiation, operation and remediation |
| 6 | OOF | Resource optimization |
This project aligns with the following standards and information models:
...
Use the above information to create a key project facts section on your project page
Key Project Facts:
Facts | Info |
|---|---|
| PTL (first and last name) | TBD |
| Jira Project Name | TBD |
| Jira Key | TBD |
| Project ID | TBD |
| Link to Wiki Space | TBD |
Release Components Name:
Note: refer to existing project for details on how to fill out this table
Components Name | Components Repository name | Maven Group ID | Components Description |
|---|---|---|---|
| org.onap. | |||
Resources committed to the Release:
...
Note 2: It is critical to complete all the information requested, that will help to fast forward the onboarding process.
Role | First Name Last Name | Linux Foundation ID | Email Address | Location |
|---|---|---|---|---|
| PTL | ||||
| Committers | ||||
| Contributors | ||||