Containers within the CNTT reference model
summary
CNTT publishes a technology‑agnostic Reference Model and a Kubernetes Reference Architecture (RA2) with concrete requirements — e.g. Kubernetes must run one of the three latest minor versions with TopologyManager and CPUManager enabled, Device Plugin and IPv6 dual‑stack supported — and debates CNI multiplexer choices. OPNFV builds the reference implementation “cube‑ref” using Intel’s BMRA with Kubespray and Bifrost provisioning and runs a first RC2 conformance suite (Kubernetes conformance, X‑ray, kube‑hunter, kube‑bench, VIMS) in community labs; a CNTT/OPNFV merger targets Jan 2021.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:54What is CNTT (Cloud infrastructure Telco Taskforce)?
- 3:55How does CNTT work?
- 9:15Reference Architecture for Kubernetes - Scope
- 10:16Reference Architecture for Kubernetes - RM Requirements
- 12:55Reference Architecture for Kubernetes - the dirty details
- 17:53Reference Implementation for Kubernetes - Overview
- 21:47Reference Implementation for Kubernetes - Current Baseline Host Provisioning Ansible playbooks orchestrating Bifrost for provisioning & configuring hosts
- 24:18Reference Compliance for Kubernetes - what is being tested Approach
- 26:48One more thing... CNTT and OPNFV are merging
related talks
01h 21mIntro + Deep Dive: Cloud Native Network Function (CNF) Testbed
17mIntro to CNCF’s Telecom Initiatives
20mCN Network Function (CNF) WG: K8s Best Practices for Telco Apps
27mBirds of a Feather: Telecom User Group
01h 25mIntro + Deep Dive BoF: Telecom User Group and Cloud Native Network Functions (CNF) Testbed
33mCNCF TAG-Runtime: Cloud Native Open...
11mKeynote: A Brief Update on Cloud Native Telecom
27mCNCF TAG Network and Cloud Native Network Landscape