...
Deliverables of Release One:
Note: this section is for brainstorming and informational purpose, and subject to change during release planning stage
In R1, we target to support
- Maintain OpenStack APIs as the primary interface (Nova, Neutron, etc) to mitigate the risk and impact to other projects
- As of this date, we expect to support Vanilla OpenStack based on Ocata, and commercial OpenStack based on Mitaka (see below)
- Other OpenStack distributions in theory should work, but need other cloud providers to commit resources in the scope of R1 (Redhat, Mirantis, Canonical, etc)
- Provide support for 4 cloud providers and align with R1 use case
- Vanilla OpenStack, VMware Integrated OpenStack, Wind River Titanium Server, and Microsoft Azure (Azure to provide HEAT to ARM translator)
- Minimal goal: any single cloud provider from above across multi-sites (TIC edge and TIC core)
- including implementation of the adapters for above clouds
- Stretch goal: mix-match
- Minimal goal: any single cloud provider from above across multi-sites (TIC edge and TIC core)
- Vanilla OpenStack, VMware Integrated OpenStack, Wind River Titanium Server, and Microsoft Azure (Azure to provide HEAT to ARM translator)
- Minimal
- Implementation of the adapters for VMware, OpenStack (Wind River), and Microsoft Azure.
- Demo use case within a single site, supported by any single cloud provider.
- For vVoLTE or vCPE, enable single cloud provider across multi-site
- Stretch goal
- For vVoLTE or vCPE, enable mix
- of different cloud providers across multi-
- sites
- For vVoLTE or vCPE, enable mix
Architecture Alignment:
- How does this project fit into the rest of the ONAP Architecture?
...