|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||Airship Installer Kali release contains a number of bug fixes and enhancements.||The Kali release brings enhanced support of OpenStack provider network and QOS in the Anuket RI-1 and further alignment to the RC-1 policy settings. As a result, the RC compliance level has increased significantly.|
Testing and build tools were developed and updated to do the following:
* A new reference container was added for the collectd-6.0 version, which is
under development and represents a big API change that is not backwards
compatible. This reference build should facilitate porting the plugins that
were previously developed by the Barometer project.
* Updated to the stable version of collectd to collectd 5.12.
* Removed duplication in the three existing containers (stable, latest and experimental).
The Kali release is the first one since becoming part of Anuket, and focusses on changes that will make testing and integrating easier.
Release notes in progress
|CIRV-SDV||Sridhar Rao||Support Openstack Security Checklist validation against different openstack deployments - Airship, Triple-O, Fuel, etc.||CIRV: Kali Release - Jira (anuket.io)|
Functest Kali was released 7 May 2020. It's worth mentioning that this branch is still active (security fixes, code improvement, etc...)
Functest is, more thant ever, a collection of state-of-the-art virtual infrastructure test suites,
The ViNePERF project is focusing on ways to keep its automated, standards-compliant, testing platform relevant as the industry evolves. In Kali Release, ViNePerf has added support for
|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||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 2||Riccardo Gasparetto Stori|
Enabling operators to deploy cloud native Kubernetes platforms for use by network functions, supporting capabilities required by Telco applications and ensuring conformance to industry standards.
Enabling Network Function developers to ensure Telco applications can consume cloud native Kubernetes platforms capabilities in a standardised fashion.
|Reference Conformance 1|
Cedric Ollivier Could we rather list key successful RC1 experiences? It would be a much stronger marketing message for our enduser
|Reference Conformance 2|
Cedric Ollivier Could we rather list key successful RC2 experiences? It would be a much stronger marketing message for our enduser
|Reference Installer 1||James Gu||Kali release contains a number of bug fixes and enhancements.||The Kali release brings enhanced support of OpenStack provider network and QOS in the Anuket RI-1 as well as further alignment between RI-1 and RC-1 in policy settings.|
|Reference Installer 2 / Kuberef|
Automated e2e deployment of a reference platform based on new versions of RA2/RM on baremetal and infrastructure provider (Equinix Metal) using opensource tooling.
Community Coordination Committee
Cedric Ollivier I don't see why it's part of release highlights. Do we plan to include TSC, Working Groups, TAC, MAC, Board, etc.?