...
Project, Workstream, or committee | Best contact for followup questions (Use @ notation) | What has changed? | Why is this significant/beneficial to a user/consumer of Anuket? | Notes, links to more information, etc. |
---|---|---|---|---|
Barometer | ||||
VinePerf | ||||
CIRV | ||||
Airship | ||||
RM | Walter.kozlowski |
| The telco cloud is evolving towards a hybrid multi-cloud deployment model. The RM Lakelse defines a generic abstract powerful model that is of value to the Reference Architectures and other standard bodies engaged in this endavor. The current model and related reference architectures provide and will continue to provide advanced guidelines for multi-cloud deployments in the industry. The growing interest in security, especially related to 5G and automation, was reflected in the Lakelse release. The infrastructure security guidelines in RM have been referenced by GSMA 5G documents making RM work widely accessible for the telecommunication industry participants. | |
RA1 | Karine Sevilla |
| RA1 now supports a more recent OpenStack release in addition to the widely used Train release version. The increasing use of accelerators (software and hardware-based), required for 5G, IoT, and ML among others, requires support for their management. Cyborg provides an abstraction for the specific devices (a la the Acceleration Abstraction Layer in O-RAN) and, thus, allows for their generic management. Publishing of the RA-1 by GSMA makes it more widely available as an industry standard. | |
RA2 | Riccardo Gasparetto |
| As Kubernetes releases have a fast pace, users can refer to RA2 specifications to increase their conformance to an ever evolving platform. The new chapters and specifications on security and multitenancy are completing core parts of the Cloud Native Telco Cloud architecture. Linking to Conformance testing helps final users benchmark implementations of the platform and ensure consistency with the Architecture. | |
RC1 | ||||
RC2 | ||||
RI2 |