| Issue # | Status | Deliverable | Comments |
|---|
| 2776 | Closed | Automation | - Lifecycle Automation: align with RM development on automation (issue #2238), PR#2971
- Deployment automation: give more guidance (issue #2776), PR#2971
|
| 2784 | Closed | Hybrid and multi cloud | - Hybrid multi-cloud orchestration, OMNI project (#2784) → OMNI inactive project, issue closed
- Evaluate other communities: ONAP, GSMA OPG, ... (#2784) → out of RA1 scope, issue closed
|
| 2786 | Backlog | Acceleration | - Development on acceleration focusing on use cases. Identify the acceleration needs and technologies for workloads hosted in Data Centre and for workloads deployed at the edge (#2786)
|
| 2787 | 2860 Closed 2861 Backlog 2874 Backlog
| Storage | - Chapter 3 (issue #2860), PR#2986
Expand the section "Virtual storage" highlighting the storage requirements for workloads and for the infrastructure components. Refer to RM chapter 3. On the "Cloud Topology" section, describe the differences per hosting environments: large DC to edge infrastructures, in conjunction with RM Chapter 3, 3.6.4. Storage scenarios and architecture fit. - Chapter 4 (issue #2861), backlog
Develop on interactions between OpenStack Cinder/Swift and storage backends. Add examples of backend solutions. - Chapter 4 (issue #2874), backlog
In "Edge cloud topology", add a sub section addressing hyperconverged SDS for edge cloud
|
| 2500 | Closed | Edge | - Collect requirements and characteristics from existing production deployments ( Chapters 2 & 4) (issue #2500)
Covered in chapter 4, by PR#2964 New issue in backlog to develop associated requirements in chapter 2 with during Nile release (issue #2989) |
| 2775 | Closed | Cloud Topology | Content improvement (issue #2775):, PR #2964 - Chapter 03: Topology overview, make clearer the redundancy models, eventually with high level diagrams
- Chapter 04: Cloud Topology and Control plane scenarios, in table 4-5, "*" and "**" need to be defined
|
| 2732 | Proofreading | Specification references updates | - Chapter 2 (issue #2877) - Review all the requirements' tables of chapter 2 and add, when it is missing, a specification reference pointing where the requirement is addressed.
|