You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Rename 'Product' chapter to 'SUSE Telco Cloud'
* Update the architecture diagram
* Correct the product positioning statement, not to be limited to edge
* Remove k3s from SUSE Telco Cloud offering
Copy file name to clipboardExpand all lines: asciidoc/product/atip-architecture.adoc
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,23 +11,23 @@ ifdef::env-github[]
11
11
:warning-caption: :warning:
12
12
endif::[]
13
13
14
-
SUSE Edge for Telco is a platform designed for hosting modern, cloud native, Telco applications at scale from core to edge.
14
+
SUSE Telco Cloud is a platform designed for hosting modern, cloud native, Telco applications at scale from core to edge.
15
15
16
-
This page explains the architecture and components used in SUSE Edge for Telco.
16
+
This page explains the architecture and components used in SUSE Telco Cloud.
17
17
18
18
19
-
=== SUSE Edge for Telco Architecture
19
+
=== SUSE Telco Cloud Architecture
20
20
21
-
The following diagram shows the high-level architecture of SUSE Edge for Telco:
21
+
The following diagram shows the high-level architecture of SUSE Telco Cloud:
22
22
23
-
image::product-atip-architecture1.svg[]
23
+
image::product-atip-architecture1.png[]
24
24
25
25
26
26
=== Components
27
27
28
28
There are two different blocks, the management stack and the runtime stack:
29
29
30
-
* *Management stack*: This is the part of SUSE Edge for Telco that is used to manage the provision and lifecycle of the runtime stacks. It includes the following components:
30
+
* *Management stack*: This is the part of SUSE Telco Cloud that is used to manage the provision and lifecycle of the runtime stacks. It includes the following components:
31
31
** Multi-cluster management in public and private cloud environments with <<components-rancher,Rancher>>
32
32
** Bare-metal support with <<components-metal3,Metal^3^>>, <<components-metallb,MetalLB>> and `CAPI` (Cluster API) infrastructure providers
33
33
** Comprehensive tenant isolation and `IDP` (Identity Provider) integrations
@@ -36,8 +36,8 @@ There are two different blocks, the management stack and the runtime stack:
36
36
** Control the SUSE Linux Micro transactional updates
37
37
** GitOps Engine for managing the lifecycle of the clusters using Git repositories with <<components-fleet,Fleet>>
38
38
39
-
* *Runtime stack*: This is the part of SUSE Edge for Telco that is used to run the workloads.
40
-
** Kubernetes with secure and lightweight distributions like <<components-k3s,K3s>> and <<components-rke2,RKE2>> (`RKE2` is hardened, certified and optimized for government use and regulated industries).
39
+
* *Runtime stack*: This is the part of SUSE Telco Cloud that is used to run the workloads.
40
+
** <<components-rke2,RKE2>> serves as the security-hardened, lightweight Kubernetes distribution, optimized for edge and compliance-focused telecom environments.
41
41
** <<components-suse-security,SUSE Security>> to enable security features like image vulnerability scanning, deep packet inspection and automatic intra-cluster traffic control.
42
42
** Block Storage with <<components-suse-storage,SUSE Storage>> to enable a simple and easy way to use a cloud native storage solution.
43
43
** Optimized Operating System with <<components-slmicro,SUSE Linux Micro>> to enable a secure, lightweight and immutable (transactional file system) OS for running containers. SUSE Linux Micro is available on {aarch64} and {x86-64} architectures, and it also supports `Real-Time Kernel` for Telco and edge use cases.
@@ -54,7 +54,7 @@ Using the <<components-eib,Edge Image Builder>> to create a new `ISO` image with
54
54
55
55
image::product-atip-architecture2.png[]
56
56
57
-
NOTE: For more information about how to deploy a new management cluster, see the <<atip-management-cluster,SUSE Edge for Telco Management Cluster guide>>.
57
+
NOTE: For more information about how to deploy a new management cluster, see the <<atip-management-cluster,SUSE Telco Cloud Management Cluster guide>>.
58
58
59
59
NOTE: For more information about how to use the Edge Image Builder, see the <<quickstart-eib,Edge Image Builder guide>>.
60
60
@@ -67,9 +67,9 @@ The following diagram shows the high-level workflow to deploy it:
67
67
68
68
image::product-atip-architecture3.png[]
69
69
70
-
NOTE: For more information about how to deploy a downstream cluster, see the <<atip-automated-provisioning,SUSE Edge for Telco Automated Provisioning guide.>>
70
+
NOTE: For more information about how to deploy a downstream cluster, see the <<atip-automated-provisioning,SUSE Telco Cloud Automated Provisioning guide.>>
71
71
72
-
NOTE: For more information about Telco features, see the <<atip-features,SUSE Edge for Telco Telco Features guide.>>
72
+
NOTE: For more information about Telco features, see the <<atip-features,SUSE Telco Cloud Telco Features guide.>>
73
73
74
74
==== Example 3: Deploying a high availability downstream cluster using MetalLB as a Load Balancer
75
75
@@ -79,6 +79,6 @@ The following diagram shows the high-level workflow to deploy it:
79
79
80
80
image::product-atip-architecture4.png[]
81
81
82
-
NOTE: For more information about how to deploy a downstream cluster, see the <<atip-automated-provisioning,SUSE Edge for Telco Automated Provisioning guide.>>
82
+
NOTE: For more information about how to deploy a downstream cluster, see the <<atip-automated-provisioning,SUSE Telco Cloud Automated Provisioning guide.>>
83
83
84
84
NOTE: For more information about `MetalLB`, see <<components-metallb,here:>>
Copy file name to clipboardExpand all lines: asciidoc/product/atip.adoc
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
1
[#atip]
2
-
= SUSE Edge for Telco
2
+
= SUSE Telco Cloud
3
3
:experimental:
4
4
5
5
ifdef::env-github[]
@@ -12,9 +12,9 @@ ifdef::env-github[]
12
12
endif::[]
13
13
:toc: preamble
14
14
15
-
SUSE Edge for Telco (formerly known as Adaptive Telco Infrastructure Platform/ATIP) is a Telco-optimized edge computing platform that enables telecom companies to innovate and accelerate the modernization of their networks.
15
+
SUSE Telco Cloud (formerly known as SUSE Edge for Telco, or Adaptive Telco Infrastructure Platform) is a telecom-optimized computing platform that enables telecom operators and teelcom network vendors to innovate and accelerate the modernization of their networks.
16
16
17
-
SUSE Edge for Telco is a complete Telco cloud stack for hosting CNFs such as 5G Packet Core and Cloud RAN.
17
+
SUSE Telco Cloud is a complete Telco cloud stack for hosting CNFs, including 5G Packet Core, Cloud RAN, OSS and BSS.
18
18
19
19
- Automates zero-touch rollout and lifecycle management of complex edge stack configurations at Telco scale.
20
20
- Continuously assures quality on Telco-grade hardware, using Telco-specific configurations and workloads.
0 commit comments