|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||Emma Foley |
Added unixsock plugin to one-click install.
Add ansible playbook for building the containers locally.
Since the anuket dockerhub repository was created, and containers are being pushed to there, instructions and build scripts have been updated to reflect this.
Testing playbooks were added to compare collectd5 vs collectd6, for the purpose of helping to review new PRs by comparing the generated metrics between versions.
Remove dpdkstats and dpdkevents from Barometer.
Enable the Logparser plugin by default when using one-click install.
Added a playbook to compare collectd 5 and collectd 6. The playbook uses existing ansible roles to build both collectd 5 and collectd 6 container images, creates a common configuration, then runs the containers and shows the outputs to let the user inspect the metrics and whether they match.
Ansible playbook updates
Added unixsock plugin to one-click install, which allows the user to interact with collectd using the
collectdctl command in the bar-collectd-* containers. The unixsock plugin is useful for debugging issues in collectd, and can be used to verify that metrics are being collected without having to create CSV files or log into the container.
Added a playbook and role for building the collectd containers locally. This automates the actions described in the docker install guide. The
barometer-collectd-latest and the
barometer-collectd-experimental containers are now easier to build locally. The
barometer-collectd-experimental containers can also be built with arbirtary PRs applied, to aid in testing locally.
The logparser plugin is now rendered for all flavours. The Logparser plugin has been part of collectd since 5.11, however, the ansible playbooks had it marked as experimental, and would not deploy it by default.
Build script updates
Normal Bug Fixes
The dpdkstats and dpdkevents plugins were removed from Barometer. These plugins are still available in collectd, however, will not be deployed by Barometer. It is recommended that the DPDK telemetry plugin be used instead.
The main efforts this cycle were in improved automation, enabling easier testing and configuration of the metrics collection on the host.
The containers were updated to more modern OSes, and reduced in size to make them quicker and easier to deploy.
- Traffic generator:
- Support for DPPD-Prox is added. This is the sixth traffic generator supported by ViNeperf.
- T-Rex statistics are improved to provide better latency results.
- ViNePerf container and corresponding pod-deployment file is included.
- A tool to deploy pods via helm-charts is added. This tool also extracts all the deployed pods and corresponding service information.
- Deployment of different CNIs (userspace, sriov, calico, cilium, multus, and danm) are supported.
- Custom DPPD-Prox and T-Rex containers are added - source files.
- L2l3fwd and VPP containers are included to support service-chain testing usecases.
- Additional Features
- Run ViNePerf as pod in Kubernetes. Results-only on-screen output mode is added for this use case.
- Dedicated 'k8s' mode is included for Kubernetes data plane testing.
- More changes made to be consistent with the name change from VSwitchPerf to ViNePerf.
- K8S Dataplane Benchmarking work is accepted to be published in IEEE Globecom 2021.
- User can use DPPD-Prox with ViNePerf. DPPD-Prox users can take advantage of ViNePerf's ability to setup DUTs, manage Trafficgenerator, manage tests, manage load-generators, and collect and analyze results.
- ViNePerf has significantly enhanced its framework to support Kubernetes usecases. Users interested in Kubernetes Network performance testing can use ViNePerf.
- Reorganization and Enhancement of Platform Description File - The single large PDF is broken down into multiple logical entities to include both Openstack and Kubernetes support.
- Kubernetes Post-Deployment Validation. Includes 12 custom post-deployment validations.
Kubernetes Post-Deployment validation can be used at different stages of Kubernetes cluster lifecycle.
The enhanced PDF can be used for multiple automation purposes.
|RM ||Walter Kozlowski|
- Hybrid Multi-cloud actor and interaction model has been significantly evolved
- Storage section has been further developed improving consumption and production models
- Security alignment with industry standards, in collaboration with GMSMA FASG and LFN Security Forum
- Alignment of Acceleration Abstraction model with ORAN
- Reference Model Kali release contents was published as GSMA NG Permanent Reference Document NG.126 ver 2.0
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.
- The latest release of RA1 specifications conforms to the OpenStack Wallaby release.
- This has allowed the introduction of Cyborg, the general-purpose acceleration resources ((i.e., various types of accelerators such as GPU, FPGA, ASIC, NP, SoCs, etc.) management framework, as an optional service.
- Submitted RA-1 KAli release specifications were submitted for publication as a GSMA Permanent Reference Document.
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 Stori|
- The specifications were updated to the latest release of Kubernetes, 1.22
- Many improvements on critical telco areas like Multitenancy, CNF and cluster Lifecycle management
- Alignment with RM on security and other topics
- Linked specifications with RC2/ Kuberef tests in order to track what requirements drive conformance testing of Kubenetes clusters.
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.
- Update of Kubernetes components and features
- Update of RI2/Kuberef Cookbook to reflect new changes
- Support for RI2 deployment on VMs
|Automated e2e deployment of a reference platform based on RA2 Kali on baremetal, infrastructure provider (Equinix Metal) and virtualized infrastructure using opensource tooling. |