From 7e7c17d6461de9cbe76924fbbe943d217cdaa2d3 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Wed, 20 Nov 2024 19:00:32 +0000 Subject: [PATCH] deploy: 4696e16e437c0c1f874c211b6aee28681b585b81 --- atip-architecture.html | 2 +- atip-automated-provisioning.html | 2 +- atip-features.html | 2 +- atip-lifecycle.html | 2 +- atip-management-cluster.html | 2 +- atip-requirements.html | 2 +- atip.html | 2 +- components-akri.html | 2 +- components-eib.html | 2 +- components-elemental.html | 2 +- components-fleet.html | 2 +- components-k3s.html | 2 +- components-kubevirt.html | 2 +- components-longhorn.html | 2 +- components-metal3.html | 6 +- components-metallb.html | 2 +- components-neuvector.html | 2 +- components-nmc.html | 6 +- components-rancher-dashboard-extensions.html | 2 +- components-rancher.html | 2 +- components-rke2.html | 2 +- components-slmicro.html | 2 +- components-system-upgrade-controller.html | 2 +- components-upgrade-controller.html | 2 +- day-2-operations.html | 2 +- day2-downstream-clusters.html | 2 +- day2-mgmt-cluster.html | 2 +- day2-migration.html | 2 +- guides-metallb-k3s.html | 2 +- guides-metallb-kubernetes.html | 2 +- ...d-deployments-with-edge-image-builder.html | 2 +- id-appendix.html | 2 +- id-components-used.html | 2 +- id-how-to-guides.html | 2 +- id-nvidia-gpus-on-sle-micro.html | 2 +- id-product-documentation.html | 2 +- id-quick-starts.html | 6 +- id-release-notes.html | 2 +- id-suse-edge-3-1-0-documentation.html | 78 +++++++++++++++++++ id-suse-edge-documentation.html | 78 ------------------- id-third-party-integration.html | 2 +- index.html | 4 +- integrations-nats.html | 2 +- quickstart-eib.html | 20 ++--- quickstart-elemental.html | 6 +- quickstart-metal3.html | 10 +-- 46 files changed, 144 insertions(+), 144 deletions(-) create mode 100644 id-suse-edge-3-1-0-documentation.html delete mode 100644 id-suse-edge-documentation.html diff --git a/atip-architecture.html b/atip-architecture.html index 7fea9260..310de9f8 100644 --- a/atip-architecture.html +++ b/atip-architecture.html @@ -74,5 +74,5 @@ useBR: false }); -
Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
SUSE Edge Documentation / Product Documentation / Concept & Architecture

30 Concept & Architecture

 

SUSE ATIP is a platform designed for hosting modern, cloud native, Telco applications at scale from core to edge.

This page explains the architecture and components used in ATIP. Knowledge of this helps deploy and use ATIP.

30.1 ATIP Architecture

 

The following diagram shows the high-level architecture of ATIP:

product atip architecture1

30.2 Components

 

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

  • Management stack: This is the part of ATIP that is used to manage the provision and lifecycle of the runtime stacks. It includes the following components:

    • Multi-cluster management in public and private cloud environments with Rancher (Chapter 4, Rancher)

    • Bare-metal support with Metal3 (Chapter 8, Metal3), MetalLB (Chapter 17, MetalLB) and CAPI (Cluster API) infrastructure providers

    • Comprehensive tenant isolation and IDP (Identity Provider) integrations

    • Large marketplace of third-party integrations and extensions

    • Vendor-neutral API and rich ecosystem of providers

    • Control the SLE Micro transactional updates

    • GitOps Engine for managing the lifecycle of the clusters using Git repositories with Fleet (Chapter 6, Fleet)

  • Runtime stack: This is the part of ATIP that is used to run the workloads.

    • Kubernetes with secure and lightweight distributions like K3s (Chapter 13, K3s) and RKE2 (Chapter 14, RKE2) (RKE2 is hardened, certified and optimized for government use and regulated industries).

    • NeuVector (Chapter 16, NeuVector) to enable security features like image vulnerability scanning, deep packet inspection and automatic intra-cluster traffic control.

    • Block Storage with Longhorn (Chapter 15, Longhorn) to enable a simple and easy way to use a cloud native storage solution.

    • Optimized Operating System with SLE Micro (Chapter 7, SLE Micro) to enable a secure, lightweight and immutable (transactional file system) OS for running containers. SLE Micro is available on aarch64 and x86_64 architectures, and it also supports Real-Time Kernel for Telco and edge use cases.

30.3 Example deployment flows

 

The following are high-level examples of workflows to understand the relationship between the management and the runtime components.

Directed network provisioning is the workflow that enables the deployment of a new downstream cluster with all the components preconfigured and ready to run workloads with no manual intervention.

30.3.1 Example 1: Deploying a new management cluster with all components installed

 

Using the Edge Image Builder (Chapter 9, Edge Image Builder) to create a new ISO image with the management stack included. You can then use this ISO image to install a new management cluster on VMs or bare-metal.

product atip architecture2
Note
Note

For more information about how to deploy a new management cluster, see the ATIP Management Cluster guide (Chapter 32, Setting up the management cluster).

Note
Note

For more information about how to use the Edge Image Builder, see the Edge Image Builder guide (Chapter 3, Standalone clusters with Edge Image Builder).

30.3.2 Example 2: Deploying a single-node downstream cluster with Telco profiles to enable it to run Telco workloads

 

Once we have the management cluster up and running, we can use it to deploy a single-node downstream cluster with all Telco capabilities enabled and configured using the directed network provisioning workflow.

The following diagram shows the high-level workflow to deploy it:

product atip architecture3
Note
Note

For more information about how to deploy a downstream cluster, see the ATIP Automated Provisioning guide. (Chapter 34, Fully automated directed network provisioning)

Note
Note

For more information about Telco features, see the ATIP Telco Features guide. (Chapter 33, Telco features configuration)

30.3.3 Example 3: Deploying a high availability downstream cluster using MetalLB as a Load Balancer

 

Once we have the management cluster up and running, we can use it to deploy a high availability downstream cluster with MetalLB as a load balancer using the directed network provisioning workflow.

The following diagram shows the high-level workflow to deploy it:

product atip architecture4
Note
Note

For more information about how to deploy a downstream cluster, see the ATIP Automated Provisioning guide. (Chapter 34, Fully automated directed network provisioning)

Note
Note

For more information about MetalLB, see here: (Chapter 17, MetalLB)