Skip to end of metadata
Go to start of metadata
You are viewing an old version of this page. View the current version.
Compare with Current
View Page History
« Previous
Version 50
Next »
Reference Model
Issue # | Status | Deliverable | Comments |
---|
2794 | Closed | Hybrid Multi-Cloud | - Multi-cloud interaction summary table and examples (Issue#2806 CLOSED) - PR#2824 - approved and merged, closing unmbrella Issue#2794
Hybrid / multi-cloud security and regulatory (Issue #2804 BACKLOG), reviewed Sec 8.2.8 (Aspects of Multi-Cloud Security), and Requirements in Sec 7, no gaps found, review to be continued post Moselle - Single pane requirements (a minimum set) (Issue #2797 CLOSED), Chapter 8 in the new Requirements section - PR#2902; approved and merged
|
2793 | Closed | Security | |
2795 | Closed | Storage | - RST Updates - Virtual Storage - Tenant Reference PR#2969 approved and merged
|
2087 | Closed | Infrastructure LCM Automation | |
2785 | Closed | General PaaS Services | - Load Balancer Requirements, (Issue 2906 CLOSED), PR#2907 approved and merged
- Logging, (Issue #2960 CLOSED), PR#2961 - approved and merged,
- Monitoring (Issue #2957 CLOSED), PR#2958 approved and merged
|
2896 | Closed | Metrics | - Should we flesh out the specs for infrastructure monitoring? (question form RA-2); PR#2983 Internal Performance Metrics approved and merged
|
Reference Architecture 1
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 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.
|
Reference Architecture 2
# | Status | Deliverable | Comments |
---|
2511 | Closed | Application Packaging specs | - Add HELM or other CNF packaging specs
- Clarify relationship with TOSCA and ONAP packaging
|
2788 | Open Moved to backlog | Monitoring & telemetry | - Input from Barometer re: metrics and architecture
- add requirements for monitoring
- add specs on caas cluster monitoring & telemetry
|
2790 | Open Moved to backlog | Service Mesh | - clarify l2/3 vs l7 service mesh
- add service mesh requirements in ch2
- add service mesh specs in ch4
|
2792 | Open Moved to backlog | CaaS Manager interface | - define API for CaaS manager interface
- define required CaaS LCM operation through API
- API to allow flavours and profiles of clusters
|
2807 2259 2798 2509
| 2807 - Closed 2259 - Open - Moved to backlog 2798 - Closed 2509 - Closed | Updates & fixes | - Align with RM
- Host OS
- restore host OS requirements
- refresh host OS and kernel specs for CNF support
- align ch4 specs and ch2 requirement references
- K8s 1.23
- update references to k8s 1.23
- remove deprecated features and APIs
- add relevant new features and APIs
- align conformance testing ref ch6
|