Anuket Project

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 InstallerAirship 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-SDVSridhar Rao
  • Validating Openstack Security Checklist
  • Implement CNTT PDF - GUI tool to create PDF
  • Implement Updates to PDF based on Elbrus Release
Support Openstack Security Checklist validation against different openstack deployments - Airship, Triple-O, Fuel, etc.CIRV: Kali Release - Jira (

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,
including automatic VNF testing. It includes about 3000+ functional tests and 3 hours upstream
API and dataplane benchmarks. It’s completed by Virtual Network Function deployments and testing
to ensure that the platforms meet
Network Functions Virtualization requirements.

Functest actively support OpenStack and Kubernetes testing, respectively from Train to
Wallaby and from v1.18 to v1.21.

ViNePERFSridhar Rao
  • Dataplane performance testing for various internal (within cloud)  and external (pod to pod) scenarios

  • Support Reporting for Openstack and K8S Scenarios
  • Support for latest versions of Different Linux Flavors

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 

  1. Kubernetes dataplane performane benchmarking for North-South Traffic - Single Pod and Multipod.
  2. Enhance reporting to support both Openstack and Kubernetes
  3. Support for Fedora 33, Ubuntu 20.04,
  4. Newer Software versions support included: DPDK:20.05, OVS:2.14.0, VPP:21.01

Reference Model

Walter Kozlowski

  • 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 2Riccardo Gasparetto Stori
  • Explicit definition of Kubernetes release, and API policy
  • Define mandatory features as part of the new Special Interest Group requirements chapter, aiding automatic conformance testing
  • Update to K8s 1.21
  • Added custom resources and controllers
  • Added device plugins and accelerators
  • Differentiating CaaS-on-VM versus Bare Metal deployments

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
  • no change as RA1 remain unchanged about OpenStack API (see existing RC1 test cases)
  • Althought Functest is fully integrated, no new test cases published by the other test frameworks

Cedric Ollivier Could we rather list key successful RC1 experiences? It would be a much stronger marketing message for our enduser

Reference Conformance 2
  • add all new Kubernetes Special Interest Group test cases from Functest
  • add netperf

Cedric Ollivier Could we rather list key successful RC2 experiences? It would be a much stronger marketing message for our enduser

Reference Installer 1James GuKali 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
  • Update of Kubernetes components and addition of new features introduced in RA2
  • Updated RI2 Cookbook to support deployment of new RA2/RM requirements
  • Added support for RI2 deployment on multiple OS (CentOS and Ubuntu based)

Automated e2e deployment of a reference platform based on new versions of RA2/RM on baremetal and infrastructure provider (Equinix Metal) using opensource tooling. 

Anuket RI2 Documentation

RI2 Kuberef Code Repository

Intel's BMRA tooling

Community Coordination Committee

(Overview DOCS)

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.?

Scot Steele
  • The newly-formed CCC took on its first task to assist with community coordination: the preparation of overall documentation for projects participating in the Kali Release.

  • No labels


  1. This is the Kali release scope, right? After M2 milestone - scope freeze?

    1. No, not the scope.  It is the key points worth mentioning, called:

      Kali Release Highlights

      1. (smile)

        I asked because I was looking for Kali release scope and didn't find any, do we have such page?

        1. We also have Release Notes for Kali (for each project).

          I think you have all the information you need to derive a Kali release scope.

  2. Cool, this is the page I' looking for, thank you! and we still using opnfv 

    in URL?

  3. Yes, for RTD, it was more important to make the information available and on-time for Kali - everything else says Anuket (almost).