Skip to content

Commit 4b355e2

Browse files
committed
Update product name to SUSE Telco Cloud
* 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
1 parent d3cf36d commit 4b355e2

File tree

5 files changed

+18
-18
lines changed

5 files changed

+18
-18
lines changed

asciidoc/edge-book/edge.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -167,10 +167,10 @@ include::../day2/mgmt-cluster.adoc[leveloffset=+1]
167167
include::../day2/downstream-clusters.adoc[leveloffset=+1]
168168
169169
//--------------------------------------------
170-
// Product Documentation
170+
// SUSE Telco Cloud Documentation
171171
//--------------------------------------------
172172
173-
= Product Documentation
173+
= SUSE Telco Cloud Documentation
174174
175175
[partintro]
176176
Find the SUSE Edge for Telco documentation here
325 KB
Loading

asciidoc/images/product-atip-architecture1.svg

Lines changed: 1 addition & 1 deletion
Loading

asciidoc/product/atip-architecture.adoc

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -11,23 +11,23 @@ ifdef::env-github[]
1111
:warning-caption: :warning:
1212
endif::[]
1313

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.
1515

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.
1717

1818

19-
=== SUSE Edge for Telco Architecture
19+
=== SUSE Telco Cloud Architecture
2020

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:
2222

23-
image::product-atip-architecture1.svg[]
23+
image::product-atip-architecture1.png[]
2424

2525

2626
=== Components
2727

2828
There are two different blocks, the management stack and the runtime stack:
2929

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:
3131
** Multi-cluster management in public and private cloud environments with <<components-rancher,Rancher>>
3232
** Bare-metal support with <<components-metal3,Metal^3^>>, <<components-metallb,MetalLB>> and `CAPI` (Cluster API) infrastructure providers
3333
** Comprehensive tenant isolation and `IDP` (Identity Provider) integrations
@@ -36,8 +36,8 @@ There are two different blocks, the management stack and the runtime stack:
3636
** Control the SUSE Linux Micro transactional updates
3737
** GitOps Engine for managing the lifecycle of the clusters using Git repositories with <<components-fleet,Fleet>>
3838

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.
4141
** <<components-suse-security,SUSE Security>> to enable security features like image vulnerability scanning, deep packet inspection and automatic intra-cluster traffic control.
4242
** Block Storage with <<components-suse-storage,SUSE Storage>> to enable a simple and easy way to use a cloud native storage solution.
4343
** 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
5454

5555
image::product-atip-architecture2.png[]
5656

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>>.
5858

5959
NOTE: For more information about how to use the Edge Image Builder, see the <<quickstart-eib,Edge Image Builder guide>>.
6060

@@ -67,9 +67,9 @@ The following diagram shows the high-level workflow to deploy it:
6767

6868
image::product-atip-architecture3.png[]
6969

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.>>
7171

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.>>
7373

7474
==== Example 3: Deploying a high availability downstream cluster using MetalLB as a Load Balancer
7575

@@ -79,6 +79,6 @@ The following diagram shows the high-level workflow to deploy it:
7979

8080
image::product-atip-architecture4.png[]
8181

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.>>
8383

8484
NOTE: For more information about `MetalLB`, see <<components-metallb,here:>>

asciidoc/product/atip.adoc

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
[#atip]
2-
= SUSE Edge for Telco
2+
= SUSE Telco Cloud
33
:experimental:
44

55
ifdef::env-github[]
@@ -12,9 +12,9 @@ ifdef::env-github[]
1212
endif::[]
1313
:toc: preamble
1414

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.
1616

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.
1818

1919
- Automates zero-touch rollout and lifecycle management of complex edge stack configurations at Telco scale.
2020
- Continuously assures quality on Telco-grade hardware, using Telco-specific configurations and workloads.

0 commit comments

Comments
 (0)