SUSE Telco Cloud 3.7
Publication Date: 2026-05-27
- SUSE Telco Cloud 3.7 Documentation
- I Concept & Architecture
- II Quick Starts
- III Components
- 6 Rancher
- 7 Rancher Dashboard Extensions
- 8 Rancher Turtles
- 9 Fleet
- 10 SUSE Linux Micro
- 11 Metal3
- 12 Edge Image Builder
- 13 Edge Networking
- 14 RKE2
- 15 SUSE Storage
- 16 SUSE Security
- 17 MetalLB
- 18 Endpoint Copier Operator
- 19 Edge Virtualization
- 20 System Upgrade Controller
- 21 Upgrade Controller
- 21.1 How does SUSE Telco Cloud use Upgrade Controller?
- 21.2 Upgrade Controller vs System Upgrade Controller
- 21.3 Installing the Upgrade Controller
- 21.4 Installing the Upgrade Controller via Edge Image Builder
- 21.5 How does the Upgrade Controller work?
- 21.6 Kubernetes API extensions
- 21.7 Tracking the upgrade process
- 21.8 Known Limitations
- IV Requirements & Assumptions
- V Setting up the management cluster
- VI Telco features configuration
- 34 Kernel image for real time
- 35 Kernel arguments for low latency and high performance
- 36 CPU Pinning on Host
- 37 CPU Pinning on Kubernetes
- 38 Network Parameters
- 39 CNI Configuration
- 40 SR-IOV
- 41 DPDK
- 42 vRAN Acceleration (
Intel ACC100/VRB1/VRB2) - 43 Huge pages
- 44 NUMA-aware scheduling
- 45 Metal LB
- 46 Private registry configuration
- 47 Precision Time Protocol
- 47.1 Introduction
- 47.2 Prerequisites
- 47.3 Scenario 1a - Ordinary Clock (PTP-only)
- 47.4 Scenario 1b - Ordinary Clock (Hybrid mode: PTP & SyncE)
- 47.5 Scenario 2a - Boundary Clock (PTP-only) with Multiport Single NIC including propagation to Ordinary Clock server
- 47.6 Scenario 2b - Boundary Clock (Hybrid mode: PTP & SyncE) with Multiport Single NIC including propagation to Ordinary Clock server
- 47.7 Scenario 3a - Boundary Clock (PTP-only) Multi-NIC with internal timing module (DPLL GNR-D based)
- 47.8 Scenario 3b - Boundary Clock (Hybrid mode: PTP & SyncE) Multi-NIC with internal timing module (DPLL GNR-D based)
- 48 SCTP - Stream Control Transmission Protocol
- VII Fully automated directed network provisioning
- 49 Introduction
- 50 Prepare downstream cluster image for connected scenarios
- 51 Prepare downstream cluster image for air-gap scenarios
- 52 Downstream cluster provisioning with Directed network provisioning (single-node)
- 53 Downstream cluster provisioning with Directed network provisioning (multi-node)
- 54 Advanced Network Configuration
- 55 Telco features (DPDK, SR-IOV, CPU isolation, huge pages, NUMA, etc.)
- 56 Private registry
- 57 Downstream cluster provisioning in air-gapped scenarios
- VIII Day 2 Operations
- IX How-To Guides
- 61 MetalLB on K3s (using Layer 2 Mode)
- 62 MetalLB on K3s (using Layer 3 Mode)
- 63 MetalLB in front of the Kubernetes API server
- 64 Air-gapped deployments with Edge Image Builder
- 64.1 Intro
- 64.2 Prerequisites
- 64.3 Libvirt Network Configuration
- 64.4 Base Directory Configuration
- 64.5 Base Definition File
- 64.6 Rancher Installation
- 64.7 SUSE Security Installation
- 64.8 SUSE Storage Installation
- 64.9 KubeVirt and CDI Installation
- 64.10 SUSE Private Registry Installation
- 64.11 Metal3 Installation
- 64.12 Troubleshooting
- 65 Building Updated SUSE Linux Micro Images with Kiwi
- 66 SUSE Storage V2 Data Engine
- 67 Using clusterclass to deploy downstream clusters
- 68 Longhorn Volume Encryption
- X Tips and Tricks
- XI Troubleshooting
- XII Appendix
List of Figures
- 47.1 PTP software on a node whose NIC integrates a manageable DPLL
- 47.2 PTP software on a node whose NIC has no manageable DPLL
- 47.3 PTP software on a node with an on-board DPLL shared across NICs
- 47.4 Time distribution with PTP only
- 47.5 Time and frequency distribution with PTP and SyncE (optional enhancement)
- 47.6 Ordinary Clock (OC) — G.8275.1 (Layer 2 multicast)
- 47.7 Ordinary Clock (OC) — G.8275.2 (Layer 3 unicast)
- 47.8 Boundary Clock (PTP-only), single NIC, with propagation to an Ordinary Clock
- 47.9 Boundary Clock (PTP-only), multi-NIC GNR-D node with on-board DPLL, with propagation to an Ordinary Clock
- 59.1 Deploy Bundle through Rancher UI
- 59.2 Successfully deployed Bundle
- 59.3 Logs for successfully upgraded Longhorn chart
List of Tables
- 24.1 Inbound Network Rules for Management Nodes
- 24.2 Inbound Network Rules for Baseboard Management Controllers
- 24.3 Inbound Network Rules for Downstream Nodes -
Metal3/IronicProvisioning phase - 24.4 Inbound Network Rules for Downstream Nodes
- 24.5 Inbound Network Rules for Management/Downstream Nodes - external metrics exposure from
cilium-operatorenabled - 47.1 Model 1 — ITU-T G.8275.1
- 47.2 Model 2 — ITU-T G.8275.2
- 47.3 Boundary Clock (BC server)
- 47.4 Ordinary Clock (OC server)
- 47.5 GNR-D Boundary Clock
- 58.1 Clusters and methods to upgrade downstream clusters
List of Examples
- 21.1 Running Upgrade Plan example:
- 21.2 Successful
UpgradePlanexample: - 47.1 Ordinary Clock configuration — ITU-T G.8275.1
- 47.2 Ordinary Clock configuration — ITU-T G.8275.2
- 47.3 Boundary Clock configuration
- 47.4 Ordinary Clock configuration
- 47.5
01-gnrd-startup-setup.sh - 47.6
/etc/ts2phc-cf-all.cfg—ts2phcconfiguration file - 47.7
/etc/ptp4l-nac.conf— integrated controller (/dev/ptp1) - 47.8
/etc/ptp4l-aic1.conf— add-in card 1 (/dev/ptp2) - 47.9
/etc/ptp4l-aic2.conf— add-in card 2 (/dev/ptp3) - 47.10
get_pmc_values.sh— query the Grandmaster values from aptp4linstance - 47.11
04-ptp-forward-GM.sh— forward the Grandmaster values to the add-in instances