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® Rancher Prime: Continuous Delivery (Fleet)
- 11 SUSE Linux Micro
- 12 Metal3
- 13 Edge Image Builder
- 14 Edge Networking
- 15 RKE2
- 16 SUSE Storage
- 17 SUSE Security
- 18 MetalLB
- 19 Endpoint Copier Operator
- 20 Edge Virtualization
- 21 System Upgrade Controller
- 22 Upgrade Controller
- 22.1 How does SUSE Telco Cloud use Upgrade Controller?
- 22.2 Upgrade Controller vs System Upgrade Controller
- 22.3 Installing the Upgrade Controller
- 22.4 Installing the Upgrade Controller via Edge Image Builder
- 22.5 How does the Upgrade Controller work?
- 22.6 Kubernetes API extensions
- 22.7 Tracking the upgrade process
- 22.8 Known Limitations
- IV Requirements & Assumptions
- V Setting up the management cluster
- VI Telco features configuration
- 35 Kernel image for real time
- 36 Kernel arguments for low latency and high performance
- 37 CPU Pinning on Host
- 38 CPU Pinning on Kubernetes
- 39 Network Parameters
- 40 CNI Configuration
- 41 SR-IOV
- 42 DPDK
- 43 vRAN Acceleration (
Intel ACC100/VRB1/VRB2) - 44 Huge pages
- 45 NUMA-aware scheduling
- 46 Metal LB
- 47 Private registry configuration
- 48 Precision Time Protocol
- 48.1 Introduction
- 48.2 Prerequisites
- 48.3 Scenario 1a - Ordinary Clock (PTP-only)
- 48.4 Scenario 1b - Ordinary Clock (Hybrid mode: PTP & SyncE)
- 48.5 Scenario 2a - Boundary Clock (PTP-only) with Multiport Single NIC including propagation to Ordinary Clock server
- 48.6 Scenario 2b - Boundary Clock (Hybrid mode: PTP & SyncE) with Multiport Single NIC including propagation to Ordinary Clock server
- 48.7 Scenario 3a - Boundary Clock (PTP-only) Multi-NIC with internal timing module (DPLL GNR-D based)
- 48.8 Scenario 3b - Boundary Clock (Hybrid mode: PTP & SyncE) Multi-NIC with internal timing module (DPLL GNR-D based)
- 49 SCTP - Stream Control Transmission Protocol
- VII Fully automated directed network provisioning
- 50 Introduction
- 51 Prepare downstream cluster image for connected scenarios
- 52 Prepare downstream cluster image for air-gap scenarios
- 53 Downstream cluster provisioning with Directed network provisioning (single-node)
- 54 Downstream cluster provisioning with Directed network provisioning (multi-node)
- 55 Advanced Network Configuration
- 56 Telco features (DPDK, SR-IOV, CPU isolation, huge pages, NUMA, etc.)
- 57 Private registry
- 58 Downstream cluster provisioning in air-gapped scenarios
- VIII Day 2 Operations
- IX How-To Guides
- 62 MetalLB on K3s (using Layer 2 Mode)
- 63 MetalLB on K3s (using Layer 3 Mode)
- 64 MetalLB in front of the Kubernetes API server
- 65 Air-gapped deployments with Edge Image Builder
- 65.1 Intro
- 65.2 Prerequisites
- 65.3 Libvirt Network Configuration
- 65.4 Base Directory Configuration
- 65.5 Base Definition File
- 65.6 Rancher Installation
- 65.7 SUSE Security Installation
- 65.8 SUSE Storage Installation
- 65.9 KubeVirt and CDI Installation
- 65.10 SUSE Private Registry Installation
- 65.11 Metal3 Installation
- 65.12 Troubleshooting
- 66 Building Updated SUSE Linux Micro Images with Kiwi
- 67 SUSE Storage V2 Data Engine
- 68 Using clusterclass to deploy downstream clusters
- 69 Longhorn Volume Encryption
- X Tips and Tricks
- XI Troubleshooting
- XII Appendix
List of Figures
- 48.1 PTP software on a node whose NIC integrates a manageable DPLL
- 48.2 PTP software on a node whose NIC has no manageable DPLL
- 48.3 PTP software on a node with an on-board DPLL shared across NICs
- 48.4 Time distribution with PTP only
- 48.5 Time and frequency distribution with PTP and SyncE (optional enhancement)
- 48.6 Ordinary Clock (OC) — G.8275.1 (Layer 2 multicast)
- 48.7 Ordinary Clock (OC) — G.8275.2 (Layer 3 unicast)
- 48.8 Boundary Clock (PTP-only), single NIC, with propagation to an Ordinary Clock
- 48.9 Boundary Clock (PTP-only), multi-NIC GNR-D node with on-board DPLL, with propagation to an Ordinary Clock
- 60.1 Deploy Bundle through Rancher UI
- 60.2 Successfully deployed Bundle
- 60.3 Logs for successfully upgraded Longhorn chart
List of Tables
- 25.1 Inbound Network Rules for Management Nodes
- 25.2 Inbound Network Rules for Baseboard Management Controllers
- 25.3 Inbound Network Rules for Downstream Nodes -
Metal3/IronicProvisioning phase - 25.4 Inbound Network Rules for Downstream Nodes
- 25.5 Inbound Network Rules for Management/Downstream Nodes - external metrics exposure from
cilium-operatorenabled - 48.1 Model 1 — ITU-T G.8275.1
- 48.2 Model 2 — ITU-T G.8275.2
- 48.3 Boundary Clock (BC server)
- 48.4 Ordinary Clock (OC server)
- 48.5 GNR-D Boundary Clock
- 59.1 Clusters and methods to upgrade downstream clusters
List of Examples
- 22.1 Running Upgrade Plan example:
- 22.2 Successful
UpgradePlanexample: - 48.1 Ordinary Clock configuration — ITU-T G.8275.1
- 48.2 Ordinary Clock configuration — ITU-T G.8275.2
- 48.3 Boundary Clock configuration
- 48.4 Ordinary Clock configuration
- 48.5
01-gnrd-startup-setup.sh - 48.6
/etc/ts2phc-cf-all.cfg—ts2phcconfiguration file - 48.7
/etc/ptp4l-nac.conf— integrated controller (/dev/ptp1) - 48.8
/etc/ptp4l-aic1.conf— add-in card 1 (/dev/ptp2) - 48.9
/etc/ptp4l-aic2.conf— add-in card 2 (/dev/ptp3) - 48.10
get_pmc_values.sh— query the Grandmaster values from aptp4linstance - 48.11
04-ptp-forward-GM.sh— forward the Grandmaster values to the add-in instances