Anuket Project

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

Project, Workstream, or Committee

Best contact for follow-up questions 

New Features and Capabilities

(approximately one paragraph summary)

What is the significance of the Kali Release for your  users, and to Anuket overall?

(approximately one paragraph summary)

Notes, links to more information, etc.

AIRSHIP Installer


Barometer


CIRV-SDVSridhar Rao


Functest


ViNePERFSridhar Rao


Reference Model
  • New flexible, hierarchical model (infrastructure profiles and extensions, workload profiles and flavours) to support evolving technologies and a variety of deployment styles
  • Hybrid Multi-Cloud model (Data Centre to Central Office, to Edge), including Telco Edge Model
  • Abstraction and normalisation of hardware acceleration
  • New security requirements including IaC Security, DevSecOps best practices for Infrastructure, Zero Trust, Open Source Software Security
Driving Anuket Reference Model and hence Reference Architectures, Compliance and Implementations projects (as well as other Anuket projects) to support currently predominant real-life implementations, where multiple technologies and deployment styles (e.g. IaaS, CaaS, PaaS, Edge, use of public clouds) need to co-exist and be securely and efficiently managed. This is driven by the move towards containerisation and motivated mainly by 5G, Edge and IoT use cases. This work in RM was done in a strong collaboration with other Anuket streams, and with external organisations including LFN XGVELA and ODIM projects, GSMA OP (Operator Platform), GSMA 5GST (5G Security Taskforce), CNCF and ORAN (Open RAN Alliance). Even more intensive collaboration efforts are planned for the upcoming Lakelse release.
Reference Arch 1
  • Cloud Topology changes including Distributed control and Edge Content
  • Major enhancements to the Security Requirements aligned with RM
  • Aligned with the hierarchical profiles introduced in RM
  • Changes to address concerns, for example, in the areas of networking
The Reference Architecture for IaaS orchestrated by OpenStack now includes major enhancements to the security requirements and practices, and coverage of cloud topologies including the Edge.
Reference Arch 2Tom Kivlin


Reference Conform 1


Reference Conform 2


Reference Installer 1James Gu


Reference Installer 2


Community Coordination Committee

(Overview DOCS)

Scot Steele


  • No labels