Anuket Project

Skip to end of metadata
Go to start of metadata

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

Compare with Current View Page History

« Previous Version 7 Next »

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.

ViNePerfSridhar Rao 
  1. Support for Kubernetes dataplane benchmarking - east-west traffic - is added.
  2. Two new tools (stress generator for kubernetes dataplane benchmarking and cloud information collector tool to automate the testing) are added.
  3. Support for building using newer version of DPDK/OVS-DPDK is added.
  4. Minor bug fixes (Qemu build, VPP Build, T-Rex)
  1. The DPDK-Based East-West dataplane benchmarking, using traffic generators such as T-Rex and DPPD-Prox, will be extremely valuable for testing
  2. The two tools support automation of dataplane benchmarking in kubernetes environment.
  3. Support for newer versions of DPDK is very important to evaluate the switching based on that (DPDK)


ThothSridhar Rao 
  1. 6 Models under VM failure prediction is included (4 LSTM-variations, CNN and Decision Tree).
  2. Two research studies (ML Problems and Techniques for NFV and OSS projects for ML in NFV) are included.
  3. Two tools (Model Selector and Data Extractor) are included.
  1. ModelSelector suggests the best model to start with, based on the data and problem in hand. This can be very useful and save significant time to the users.
  2. The research studies gives the thorough information about the state-of-art for ML in NFV.
  3. The Virtual-Machine FP models improves the performance compared to the existing models.

Anuket Reference ModelWalter.kozlowski 
  1. Multi-cloud interaction summary table and examples section "Requirements, Reference Architecture & Industry Standards Intersect" added
  2. Single pane requirements added (for Multi-Cloud)
  3. Software supply chain security updated
  4. Regulatory directives for cybersecurity added
  5. Storage: Tenant Reference, storage types, use cases and stereotypes updated
  6. Infrastructure LCM Automation section added
  7. General PaaS Services contents updated (Logging, Monitoring, LB requirements)
  8. Specs for infrastructure monitoring from ETSI GS NFV-TST 008 V3.5.1 added
  1. Givese CSPa a base to adopt and sponsor a set of standards that are necessary to support the interactions with Cloud Providers.

Anuket Kubernetes Reference ArchitectureRiccardo Gasparetto 
  1. Added CNF workload guidelines, aligned with CNCF CNF certification test list
  2. added CNF packaging specifications
  3. Added Edge Cloud Hardware requirements
  4. Updated to Kubernetes 1.23
  5. Added Host OS requirements
  1. Enables CNF providers to follow industry guidelines to ensure containerised workloads follow cloud native best practices and can run on Anuket compliant cloud infrastructure. These CNFs can be then easily deployed by operators.
  2. Standardised deployment practices include packaging.
  3. Relaxes strict requirements on hardware performance allowing constrained edge deployments - important for 5G.
  4. Kubernetes 1.23, the latest supported release of Kubernetes, includes important new features relevant to telcos such as IPv4/IPv6 Dual-stack, HorizontalPodAutoscaler v2 and Generic Ephemeral Volumes. Support is also extended until Dec. 22.
  5. Host OS requirement allow cloud providers to identify the minimum OS & kernel capabilities required to run Anuket compliant Kubernetes platforms, and leverage the latest security and other improvements.

OpenStack Reference ArchitectureKarine Sevilla 
  1. Addition or update of specifications reference in tables of requirements
  2. Edge : OpenStack services deployment, storage scenarios, image caching considerations
  3. Storage: developments aligned with Reference Model
  4. LCM automation: installers description, automation of underlying resources provisioning 
  1. The reader will easily find details of configurations or specific information with pointers to sections addressing the requirements. It simplifies the use of the specification.
  2.  Guidance for edge deployments, including relaxation of 
  3. Inputs for the choice of storage solution per workload requirements
  4. Guidance for automation, examples of tools



RI2/Kuberef
  1. Align requirements covered in RI2 with RA2 Lakelse, and support 16 new requirements in RI2.
  2. Did some bug fix and automate some prepare steps in kuberef.
Automated e2e deployment of a reference platform based on  RA2 Lakelse on baremetal, infrastructure provider (Equinix Metal) and virtualized infrastructure using opensource tooling. 
  • No labels