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 15
Next »
Reference Model
| Issue # | Deliverable | Comments |
|---|
| 2794 | Hybrid Multi-Cloud | Updates to: - multi-cloud summary table and examples (PR#2676)
- storage for multi-cloud (Issue#2578)
- hybrid / multi-cloud security and regulatory
- APIs
- single pane requirements (a minimum set) (Issue #2797)
- multi cloud use cases (as examples to drive requirements)
- specialised clouds (e.g. game clouds)
|
| 2793 | Security | Developments on:
- SBOM, alignment with LFN security forum
- Security for hybrid and multi-cloud
- Monitoring
|
| 2795 | Storage | Updates to storage: - Storage principles (Issue#2666)
- Storage for multi-cloud (Issue#2578)
- Storage scenarios (Issue#2747)
|
| 2087 | Automation | - IaC - LCM
- Design and build consideration (with Automation) - collaboration with RAs and RIs. Principles, guidelines (to be shared between RM and RAs). Declarative approach to automation.
- Automation
- 9.5.1.1. Hardware Configuration CI/CD
- 9.5.1.2. Networking Automation
- 9.5.1.3. Software Development CI/CD1.
|
| 2785 | General PaaS Services | Section 5.1.5 lists a set of General PaaS Services. We need to specify requirements for each of these services -- an issue will be opened for each service. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Reference Architecture 1
| Issue # | Deliverable | Comments |
|---|
| 2776 | Automation | - Lifecycle Automation: align with RM development on automation (issue #2238)
- Deployment automation: give more guidance
|
| 2784 | Hybrid and multi cloud | - Hybrid multi-cloud orchestration
- Evaluate other communities: ONAP, GSMA OPG, ...
|
| 2786 | 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
|
| 2787 | Storage | - Alignment with RM on storage. References to RM sections must be added.
- Develop on interactions between OpenStack Cinder/Swift and storage backends
|
| 2500 | Edge | - Collect requirements and characteristics from existing production deployments ( Chapters 2 & 4)
|
| 2775 | Cloud Topology | Content improvement: - 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 | Specification references updates | - Chapter 2: add specification content references into requirements' tables
- Other chapters: add requirements matching content
|
Reference Architecture 2
| # | Deliverable | Comments |
|---|
| 2511 | Application Packaging specs | - Add HELM or other CNF packaging specs
- Clarify relationship with TOSCA and ONAP packaging
|
| 2509 | 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
|
| 2788 | Monitoring & telemetry | - Input from Barometer re: metrics and architecture
- add requirements for monitoring
- add specs on caas cluster monitoring & telemetry
|
| 2790 | Service Mesh | - clarify l2/3 vs l7 service mesh
- add service mesh requirements in ch2
- add service mesh specs in ch4
|
| 2792 | CaaS Manager interface | - define API for CaaS manager interface
- define required CaaS LCM operation through API
- API to allow flavours and profiles of clusters
|
| 2798 | Host OS | - restore host OS requirements
- refresh host OS and kernel specs for CNF support
|
| 2259 | references updates | - align ch4 specs and ch2 requirement references
|
|
|
|
|
|
|
|
|
|
