| Anuket Kubernetes Reference Architecture (RA2) |
Riccardo Gasparetto Stori |
Added CNF workload guidelines, aligned with CNCF CNF certification test listadded CNF packaging specificationsAdded Edge Cloud Hardware requirementsUpdated to Kubernetes 1.23Added Host OS requirements |
Enables CNF providers to follow industry guidelines to ensure containerised workloads follow cloud native best practices and can run on Anuket compliant cloud infrastructure. These CNFs can be then easily deployed by operators.Standardised deployment practices include packaging.Relaxes strict requirements on hardware performance allowing constrained edge deployments - important for 5G.Kubernetes 1.23, the latest supported release of Kubernetes, includes important new features relevant to telcos such as IPv4/IPv6 Dual-stack, HorizontalPodAutoscaler v2 and Generic Ephemeral Volumes. Support is also extended until Dec. 22.Host OS requirement allow cloud providers to identify the minimum OS & kernel capabilities required to run Anuket compliant Kubernetes platforms, and leverage the latest security and other improvements. |
| Anuket Reference Model (RM) |
Walter Kozlowski |
Multi-cloud interaction summary table and examples section "Requirements, Reference Architecture & Industry Standards Intersect" addedSingle pane requirements added (for Multi-Cloud)Software supply chain security updatedRegulatory directives for cybersecurity addedStorage: Tenant Reference, storage types, use cases and stereotypes updatedInfrastructure LCM Automation section addedGeneral PaaS Services contents updated (Logging, Monitoring, LB requirements)Specs for infrastructure monitoring from ETSI GS NFV-TST 008 V3.5.1 added |
Gives Communication Service Providers (CSPs) a base to adopt and sponsor a set of standards that are necessary to support the interactions with Cloud Providers.Provides CSPs with a minimum set of requirements for operations in a Hybrid, Edge, and Multi-Cloud environment.Software supply chain security is crucial and is made complex by the greater attack surface provided by the many different supply chains in virtualised, containerised, and edge environments. This section will help the operators to implement the best practices to address these risks.Provides leading examples of regulatory frameworks relevant for Cloud Infrastructure in the telecom environment. This new section will provide important guidance for the operators.Provides a relatively simple way for the storage consumer to specify / select their storage needs.Provides operators with a structured framework and best practice principles for Automation of Infrastructure Life-cycle.Provides a telecom operator (CSPs) with a set of new or updated requirements for selected non-Telco PaaS Services.Fleshes out the specs for infrastructure monitoring from ETSI GS NFV-TST 008 V3.5.1, to be used by RA-1 and RA-2. |
| OpenStack Reference Architecture (RA1) |
Karine Sevilla |
Addition or update of specifications reference in tables of requirementsEdge : OpenStack services deployment, storage scenarios, image caching considerationsStorage: developments aligned with Reference ModelLCM automation: installers description, automation of underlying resources provisioning |
The reader will easily find details of configurations or specific information with pointers to sections addressing the requirements. It simplifies the use of the specification. Guidance for edge deployments, including relaxation of Inputs for the choice of storage solution per workload requirementsGuidance for automation, examples of tools |
| RI2/Kuberef |
Dan Xu |
Align requirements covered in RI2 with RA2 Lakelse, and support 16 new requirements in RI2.Did some bug fix and automate some prepare steps in kuberef. |
Automated e2e deployment of a reference platform based on RA2 Lakelse on baremetal, infrastructure provider (Equinix Metal) and virtualized infrastructure using opensource tooling. |
