TUT-1389: SLE Container Images!

TUT-1389: SLE Container Images!

Everything you need to know about getting started with

SLES Container images and registry.suse.com

TUT-1389

Jeff Lindholm

Sales Engineering Manager SUSE

Agenda

1. SUSE Linux Enterprise Container Images!

2.

Why Linux containers are the path forward…

3. Customizing SUSE Linux Enterprise containers

4. SUSE Container Registry

Guest OS

Containers enable microservices model

Build and Deliver Cloud Native Applications

Large numbers of small containers require efficiency of shared OS Kernel

Continuous delivery demands fast start and stop capability

Server

Guest OS Guest OS

VM VM VM

Hypervisor

Host OS Container Runtime

OS Kernel

A Bit of History….

SLES11 – LXC – Full Linux Distribution Containers, cgroups!

SLES12 – Application Containers…!

SLE Containers Module - docker community project

dockerhub and private container registry

SLE 11/12 container images delivered in signed RPMs

Container images signed and verified with sle2docker

Introduction of Kubernetes - SUSE Container as a Service Platform

SLES15 – Multi-modal Linux Distribution

Common Code Base

All Architectures (x86-64, Arm, POWER, IBM Z)

Traditional Infrastructure

Multiple use cases

Manual and automatic installation

Variety of updates, upgrades, legacy

Variable packaging and installation

May become huge in size and

management

Software-defined

Infrastructure

Single use case, multiple systems

Automatic and centralized installation

Always up-to-date

Fit one purpose

Small as possible for size and

management

How Do Containers Help Transform IT?

Accelerate application development and delivery

Build and deliver new cloud native

applications

Works on my

machine

today

Works on my

machine

tomorrow

QA environment

Works on “our”

“your” machine

Works on my machine

Accelerate Application Development and Delivery

Q&A Session 34pt

Demo - Linux Containers 101

Vocabulary…Mutual Understanding 

Container Image: An image is a read-only template used to create a virtual machine on the host server. A Docker image is

made by a series of layers built one over the other. Each layer corresponds to a permanent change, for example an update of an application. The changes are stored in a file called a Dockerfile. For more details seethe official Docker documentation.

Dockerfile: A Dockerfile stores changes made on top of the base image.Docker Open Source Enginereads instructions in the Dockerfile and builds a new image according to the instructions.

Container: A container is a running instance based on a particular DockerImage. Each container can be distinguished by a unique container ID.

Registry: A registry is storage for container images. It typically contains several repositories There are two types of registry:

Hello Docker!

Your First Dockerfile…simple container with additional SLE packages

Q&A Session 34pt

Use cases and Roadmap…Coming Soon…!

SUSE Registry and Container Images

Integrated with SUSE Customer Center

Authorization, Distribution (CDN), Upload Process, Chain of Trust Images Managed via SUSE Management Tool and SUSE Manager Maintenance flow for container images

SUSE

Registry

SUSE Registry and Container Images

Integrated with SUSE Customer Center

Authorization, Distribution (CDN), Upload Process, Chain of Trust Images Managed via SUSE Management Tool and SUSE Manager Maintenance flow for container images

Use Cases

SUSE Public Container Registry.. All things software defined:

SUSE Linux Enterprise Server (Default Images)

SUSE Container as a Service Platform (Kubernetes)

SUSE Cloud Application Platform (Cloud Foundry)

SUSE Enterprise Storage (Ceph Storage Infrastructure)

General Disclaimer

This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing

decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of

merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are