容器指南 - SUSE Linux Enterprise Server 15 SP2

SUSE Linux Enterprise Server 15 SP2 容器指南

容器指南 SUSE Linux Enterprise Server 15 SP2 本文档仍在不断完善中 内容如有更改, 恕不另行通知 出版日期 : 2022 年 5 月 03 日 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com 版权所有 2006 2022 SUSE LLC 和贡献者 保留所有权利

根据 GNU 自由文档许可证 (GNU Free Documentation License) 版本 1.2 或 ( 根据您的选择 ) 版本 1.3 中的 条款, 在此授予您复制 分发和 / 或修改本文档的许可权限 ; 本版权声明和许可证附带不可变部分 许可证 版本 1.2 的副本包含在题为 GNU 自由文档许可证 的部分 有关 SUSE 商标, 请参见 https://www.suse.com/company/legal/ 所有其他第三方商标是其各自所有者 的财产 商标符号 ( 等 ) 代表 SUSE 及其关联公司的商标 星号 (*) 代表第三方商标 本指南力求涵盖所有细节, 但这不能确保本指南准确无误 SUSE LLC 及其关联公司 作者和译者对于可能 出现的错误或由此造成的后果皆不承担责任

目录 关于本指南 vi 1 必需的经验 vi 2 提供反馈 vi 3 文档约定 vii 1 简介 1 1.1 术语 1 2 构建容器 2 2.1 客户可使用的构建工具 2 Docker 2 Podman 2 Buildah 3 2.2 内部 SUSE 构建工具 3 Open Build Service 3 KIWI 3 2.3 构建官方 SLE 映像 4 3 获取容器 5 3.1 SUSE Linux Enterprise 基本映像 5 3.2 SUSE 容器属性 5 储存库名称 5 标签 5 标记 7 3.3 SUSE 注册表 8 3.4 比较容器 9 3.5 本地注册表 9 Portus 9 iv 容器指南

4 支持计划 10 4.1 SUSE 主机环境上的受支持容器 10 第一层 10 第二层 10 第三层 11 4.2 支持的容器主机环境 11 第一层 11 第二层 11 第三层 11 第四层 12 A GNU 许可证 13 v 容器指南

关于本指南 本指南提供 SUSE 容器生态系统的简介 1 必需的经验 为使这些准则的范围可以管理, 本文做了以下技术假设 : 您拥有一些计算机经验, 熟悉常见的技术术语 您熟悉系统的文档和其运行的网络 您基本了解 Linux 系统 2 提供反馈 欢迎您提供针对本文档的反馈及改进建议! 我们提供了多种反馈渠道 : 服务请求和支持有关产品可用的服务和支持选项, 请参见 https://www.suse.com/support/ 要创建服务请求, 需在 SUSE Customer Center 中获取一个订阅 请转到 https:// scc.suse.com/support/requests 并登录, 然后单击新建 Bug 报告在 https://bugzilla.suse.com/ 中报告文档问题 要简化此过程, 可以使用本文档 HTML 版本中的标题旁边的报告文档 Bug 链接 这样, 就会在 Bugzilla 中预先选择正确的产品和类别, 并添加当前章节的链接 然后, 您便可以立即开始键入 Bug 报告 需要一个 Bugzilla 帐户 贡献 要帮助改进本文档, 请使用本文档 HTML 版本中的标题旁边的编辑源代码链接 这些链接会将您转到 GitHub 上的源代码, 在其中可以创建拉取请求 需要一个 GitHub 帐户 有关本文档使用的文档环境的详细信息, 请参见储存库的 README (https://github.com/ SUSE/doc-sle/blob/master/README.adoc) vi 必需的经验 SLES 15 SP2

邮件另外, 您也可以将有关本文档中的错误以及相关反馈发送至 :doc-team@suse.com 请确保反馈中含有文档标题 产品版本和文档发布日期 请引用相关的章节号和标题 ( 或者包含 URL), 并提供问题的简要说明 3 文档约定 本文档中使用了以下通知和排版约定 : /etc/passwd : 目录名称和文件名 PLACEHOLDER :PLACEHOLDER 将会替换为实际的值 PATH : 环境变量 PATH ls --help : 命令 选项和参数 user : 用户和组 package name : 软件包名称 Alt Alt F1 : 按键或组合键 ; 这些键以大写形式显示, 如在键盘上一样 文件 文件 另存为 : 菜单项, 按钮 AMD/Intel 本段内容仅与 AMD64/Intel 64 体系结构相关 箭头标记文本块的开始位置和结束位置 IBM Z, POWER 本段内容仅与 IBM Z 和 POWER 体系结构相关 箭头标记文本块的开始位置和结束位置 跳舞的企鹅 ( 企鹅一章, 其他手册 ): 此内容参见自其他手册中的一章 必须使用 root 特权运行的命令 您往往还可以在这些命令前加上 sudo 命令, 以非特权用户身份来运行它们 root # command tux > sudo command 可以由非特权用户运行的命令 vii 文档约定 SLES 15 SP2

tux > command 注意 警告 : 警告通知 在继续操作之前, 您必须了解的不可或缺的信息 向您指出有关安全问题 潜在数 据丢失 硬件损害或物理危害的警告 重要 : 重要通知 在继续操作之前, 您必须了解的重要信息 注意 : 注意通知 额外信息, 例如有关软件版本差异的信息 提示 : 提示通知 有用信息, 例如指导方针或实用性建议 viii 文档约定 SLES 15 SP2

1 简介 1.1 术语 容器 容器是将代码及其所有依赖项全部打包在一起的一个标准软件单位 这样做可让容器及其应用程序在各种计算环境中快速且可靠地运行 容器可包含应用程序运行所需的所有组件 多个容器可在单个主机操作系统实例上运行, 但各容器之间相互独立 从容器中的程序角度来看, 它是在主机操作系统上运行的唯一程序 与虚拟机不同, 容器没有自己的内核 操作系统实例上的所有容器共享主机操作系统的内核 容器映像容器映像是一个不可更改的静态文件, 它包含可执行代码, 因此可以在 IT 基础设施上运行独立的进程 映像由系统库 系统工具以及在容器化平台上运行程序所需的其他平台设置组成 容器映像通过在父映像或基本映像上构建的文件系统层进行编译 基本映像基本映像为最小的初始映像 在 Dockerfile 中, 基本映像由 FROM scratch 指令进行识别 父映像充当其他容器映像基础的映像 换言之, 如果某个映像不是基本映像, 则它派生自父映像 在 Dockerfile 中,FROM 指令指向父映像 大多数 Docker 容器都是使用父映像创建的 容器编制编制是一种部署 管理 扩缩和安排多个群集中各个容器工作的自动过程 可使用 Kubernetes (https://kubernetes.io/) 等专用工具来执行编制 容器平台 SUSE CaaS Platform 就是一个容器平台 1 术语 SLES 15 SP2

2 构建容器 本章提供了用于创建容器的工具的概述 下文提到的大部分工具都包含在 SUSE Linux Enterprise Server 15 SP2 Containers Module 中 您可以在 SUSE Customer Center (https://scc.suse.com/packages?name=suse%20linux%20enterprise %20Server&version=15.2&arch=x86_64&query=&module=1963) 的 Containers Module 中查看完整的软件包列表 2.1 客户可使用的构建工具 2.1.1 Docker Docker 是一个用于创建和管理容器的系统 其核心是 Docker 开源引擎, 这是一种轻量级虚拟化解决方案, 可在单台主机上同时运行多个容器 Docker 容器使用 Dockerfile 进行定义 Dockerfile 说明如何汇编容器的私用文件系统 该文件还包含说明如何运行容器的元数据 大部分 Dockerfile 从父映像启动 有关如何创建自定义 SUSE Linux Enterprise Docker 基本映像的简要说明, 请参见 容器指南 2.1.2 Podman Podman 是 Pod Manager 工具的简称, 其功能不仅仅只是构建映像 它是一个无守护程序的容器引擎, 用于在 Linux 系统上开发 管理和运行 Open Containers Initiative (OCI), 可作为 Docker 的直接替代方案 Podman 是 opensuse Kubic( 基于 opensuse 构建的 Kubernetes 认证发行套件 ) 中的默认容器运行时 您可以使用 Podman 通过 Dockerfile 和一系列与 Docker 类似的命令来创建符合 OCI 规范的容器映像 例如, 除了不使用 Docker 守护程序外,podman build 命令所执行的任务与 docker build 完全相同 Podman 的另一项重要功能是无根容器构建 由于 Podman 依赖于用户名称空间 ( 用于为 Linux 进程提供隔离机制 ), 因此无需 root 特权便能创建和运行容器 有关如何安装和使用 Podman 的说明, 请参见 Podman 文档 (https://podman.io/) 2 客户可使用的构建工具 SLES 15 SP2

2.1.3 Buildah Buildah 可帮助您构建 OCI 容器映像 Buildah 是 Podman 的互补工具 ( 请参见第 2.1.2 节 Podman ),podman build 使用它来执行容器映像构建 Buildah 可让您从头开始构建映像, 也可使用 Dockerfile 从现有映像构建映像 使用 Buildah 命令行工具和基于 OCI 的底层技术 ( 例如 containers/image 和 containers/storage ) 构建的 OCI 映像具有可移植性, 因此可以在 Docker 环境中运行 有关如何安装和使用 Buildah 的说明, 请参见 Buildah 文档 (https://buildah.io/) (https://github.com/containers/buildah/blob/master/docs/tutorials) 和教程 2.2 内部 SUSE 构建工具 2.2.1 Open Build Service Open Build Service (OBS) 提供了免费的基础结构, 可用于构建和储存 RPM 软件包 ( 包括各种容器格式 ) OBS 容器注册表 (https://registry.opensuse.org/cgi-bin/cooverview) 提供由 OBS 构建的所有容器映像的详细列表, 使用命令完成将映像提取到您的本地 Docker 环境的操作 您可以根据特定需求修改 OBS opensuse 容器映像模板 (https://build.opensuse.org/ image_templates), 这是创建您自己的容器分支的最简单方法 您可以使用 Dockerfile 通过本机 Docker 工具从现有映像构建容器映像 也可以使用 KIWI 映像构建解决方案从头开始构建映像 https://openbuildservice.org/2018/05/09/container-building-and-distribution/ 上提供了有关如何在 OBS 上构建映像的说明 2.2.2 KIWI KIWI Next Generation 是一种用于构建映像的多功能工具 除容器映像 常规安装 ISO 映像以及适用于虚拟机的映像之外,KIWI 还可构建通过 PXE 或 Vagrant 盒子引导的映像 KIWI 中的主要构建基块是映像 XML 描述, 一个包含 config.xml 或.kiwi 文件以及脚本或配置数据的 3 Buildah SLES 15 SP2

目录 使用 KIWI 创建映像的过程是完全自动化的, 不需要任何用户交互 映像创建过程所需的 任何信息由主要配置文件 config.xml 提供 可以使用 config.sh 和 images.sh 脚本自 定义映像 注意 请务必区分 KIWI NG( 当前版本 9.20.9) 及其不再维护的旧版本 (7.x.x 或更早版本, 现 在称为 KIWI 旧版 (https://documentation.suse.com/kiwi/) ) 有关如何安装 KIWI 以及使用 KIWI 构建映像的特定信息, 请参见 KIWI 文档 (http:// osinside.github.io/kiwi/) KIWI GitHub 储存库 (https://github.com/osinside/kiwidescriptions) 上提供了一系列示例映像描述 KIWI 手册页提供了使用该工具的相关信息 要访问手册页, 请安装 kiwi-man-pages 软件包 2.3 构建官方 SLE 映像 只有使用内部构建服务构建的映像才会被视为官方映像 https://build.opensuse.org 上未提供官方 SLE 容器映像, 从该网站导出的 RPM 与内部 RPM 并不相同 这意味着无法在 https://build.opensuse.org 上构建官方支持的映像 4 构建官方 SLE 映像 SLES 15 SP2

3 获取容器 本章提供获取容器映像的相关信息 3.1 SUSE Linux Enterprise 基本映像 SUSE 提供了大量官方基本容器映像, 您可以基于这些映像来构建自定义容器 每个 SLE 基本映像都包含一个不带内核的 SLE 版本 基本映像中包含的操作系统是不具有任何功能的空环境 您可从 https://registry.suse.com 获取基本映像 有关 SUSE 注册表的信息, 请参见第 3.3 节 SUSE 注册表 SUSE 注册表中的映像均为正式发布 ( 生产 ) 的版本以及 SLES 12 和 SLES 15 的 LTSS (https://www.suse.com/products/long-term-service-pack-support/) 版本 SUSE 注册表中的 SUSE Linux Enterprise 基本映像可接收安全更新, 并涵盖在 SUSE 支持计划中 有关这些支持计划的详细信息, 请参见第 4 章 支持计划 3.2 SUSE 容器属性 SUSE 容器映像带有标识符, 可帮助您选择满足您需求的适合映像 从储存库中提取容器映像并 在其上运行 podman inspect 之后, 便可访问下面列出的各个标识符 3.2.1 储存库名称 储存库名称以产品名称开头, 例如 :suse/sle/( ) opensuse/tumbleweed/( ) caasp/( ) 适用于所有服务包的 SLE 15 容器位于名称空间 suse/sle15 中 此规则也适用于 SLE 的未来版本 ( 例如 suse/sle16 ) 但对于 SLE 12 而言, 每个服务包都有一个独立的储存库名称, 例如 suse/sle12sp3 suse/sle12sp4 suse/sle12sp5 3.2.2 标签 标签有助于识别映像 所有 SLE 容器映像标签均以 com.suse.<product>.<containername> 开头, 后跟进一步的规范 opensuse 容器映像可通过以 org.opencontainers 开头的标签来识别 5 SUSE Linux Enterprise 基本映像 SLES 15 SP2

重要 :com.suse.sle.base 标签受到保护 通过将每一层添加到基本映像, 可使用派生映像中的标签重写基本容器中定义的标签 为了保护映像来源的相关信息, 已将标签 com.suse.sle.base 添加到 SLE 容器映像 此标签会指出 SUSE 是相关映像的供应商 由于标签受到保护, 它不会被基本映像的任何修改所重写 与之相反,openSUSE 基本映像中的标签则并未受到保护 例如,org.opencontainers.image.title 始终包含最后添加层的标题 下面是所有当前定义的标签的列表 : 表 3.1..当前定义的标签 必须由 派生映 像提供 标签 OCI 批注说明示例 是 org.opencontainers. org. 映像标题 SUSE Linux image.title com.suse.sle. opencontainers. Enterprise 15 基本容 base.title image.title 器 是 org.opencontainers. org. 映像的简短说 包含基于 SUSE Linux image.description com. opencontainers. 明 Enterprise 15 的容器 suse.sle.base.description image. 最小环境的映像 description 是 org.opencontainers. org. 映像版本 <codestream>.<sp>. image.version com.suse. opencontainers. <cicnt>.<bldcnt> sle.base.version image.version 15.0.4.2 是 org.opencontainers. org. 映像构建的时 2018-07-27T14:12:30Z image.created com.suse. opencontainers. 间戳 sle.base.created image.created 6 标签 SLES 15 SP2

必须由 派生映 像提供 标签 OCI 批注说明示例 否 org.opencontainers. org. 映像供应商 SUSE LLC image.vendor com.suse. opencontainers. sle.base.vendor image.vendor 否 org.opencontainers. org. 更多信息 https:// image.url com.suse.sle. opencontainers. www.suse.com/ base.url image.url products/server/ 是 org.openbuildservice. org. 映像 OBS URL obs://build.suse.de/ disturl com.suse.sle.base. openbuildservice. SUSE:SLE-15: disturl disturl Update:CR/ images/2951b67133 dd6384cacb2820317 4e030-sles15-image 是 org.opensuse.reference org.opensuse. 指向此特定映 registry.suse.com/ com.suse.sle.base. reference 像的参考 suse/sle15:4.2 reference 不得更改您使 用 docker pull <ref.name> 命令获取的映 像 3.2.3 标记 标记用于添加阐述性信息 与标签不同, 标记可以自由定义 标记通常包含容器映像特定版本的相关信息 如果某个标记存在于多个映像中, 则将使用最新的映像 由映像维护者决定指派给容器映像的标记 7 标记 SLES 15 SP2

常规标记格式为 : 储存库名称 : 映像版本规范 ( 通常为版本号 ) 例如,SUSE Linux Enterprise Server 15 SP1 的最新发布映像的标记将为 suse/sle15:15.1 下表显示在 registry.suse.com 上找到的示例 SLE 容器映像标记 其中一些标记会定期更新, 因此它们不会批注确切的映像版本, 而是会充当占位符 定期更新的标记以粗体标示 表 3.2..当前使用的标记示例 储存库名称 :Tag suse/sle12sp3: latest suse/sle12sp3: 2.0.2 suse/sle15: latest suse/sle15: 15.1 suse/sle15: 15.1.1.1 suse/sle15: 15.1.1.0 说明 SUSE Linux Enterprise 12 SP3 的最新发布映像 与 latest 相同 仅为向后兼容而保留 SUSE Linux Enterprise 15 编码流的最新发布映像 在本例中, 与 15.1 和 15.1.1.1 相同 SLE 15 SP1 的最新发布映像 与 15.1.1.0 相同, 但包含一些更新的软件包 第一个 SUSE Linux Enterprise 15 SP1 映像 3.3 SUSE 注册表 官方 SUSE 注册表可从 https://registry.suse.com 获取 它包含经过测试和更新的 SUSE Linux Enterprise 和 SLES 基本容器映像 SUSE 注册表中的所有映像都要经历一个固定的维护过程 使用最新的安全修复定期更新映像 SUSE 注册表可以免费使用, 同时还提供有额外功能, 可通过在容器主机上的客户订阅获得这些功能 需要订阅容器映像才能收到更新 当前,SUSE 注册表没有 UI 或映像列表 8 SUSE 注册表 SLES 15 SP2

3.4 比较容器 container-diff (https://github.com/googlecontainertools/container-diff#container-diff) 工具可用于分析和比较容器映像 container-diff 可根据多个不同准则检查映像, 其中包括 : Docker 映像历史映像文件系统 DEB 软件包 RPM 软件包 PyPI 软件包 NPM 软件包 您可以检查单个映像, 也可以在两个映像上执行 diff 操作 container-diff 支持位于本地 Docker 守护程序和远程注册表中的 Docker 映像 还可以结合.tar.tar.gz 和.tgz 存档使用工具 另一方面, container-diff 软件包属于 SUSE Linux Enterprise Server 15 SP2 Containers Module 的一部分 您也可以单独安装该软件包 有关安装该软件包的说明, 请参见 containerdiff 文档 (https://github.com/googlecontainertools/container-diff#installation) 3.5 本地注册表 3.5.1 Portus Portus (http://port.us.org/) 是一种本地应用程序, 可为 Docker 注册表提供图形界面和授权机制 有关 Portus 功能的详细说明, 请参见 http://port.us.org/features.html 您可以使用标准 Docker 容器在 Kubernetes 群集内或在裸机上部署 Portus 有关部署选项以及如何在开发环境中开始使用 Portus 的说明, 请参见 http://port.us.org/docs/deploy.html 9 比较容器 SLES 15 SP2

4 支持计划 本章说明 SLES 容器支持计划的工作原理 有三项 SUSE 容器支持的指导原则 1. 容器映像生命周期遵循相关产品的生命周期 例如,SLES 15 SP2 容器映像遵循 SLES 15 SP2 生命周期 2. 容器发布状态还与相关产品的状态相匹配 例如, 如果 SLES 15 SP2 处于 Alpha Beta RC 或 GA 阶段, 则相关容器具有同样的发布状态 3. 容器是使用相关产品中的软件包构建的 例如,SLES 15 SP2 容器映像是使用与 SLES 15 SP2 主版本相同的软件包构建的 4.1 SUSE 主机环境上的受支持容器 下列支持选项 ( 层 ) 适用于 SUSE 主机环境上的 SUSE Linux Enterprise Server 和 SUSE CaaS Platform 容器 4.1.1 第一层 由 SUSE 提供的容器由 SUSE 提供的容器受到完全支持 此层级适用于容器 主机环境以及支持所涵盖的所有产品 该支持包括标准支持和长期服务包支持 (https://www.suse.com/products/longterm-service-pack-support/) (LTSS) 4.1.2 第二层 由签署了确保联合工程协作协议的合作伙伴提供的容器此层级面向重要的独立软件供应商 (ISV) 签署了联合工程协作协议的合作伙伴容器受到完全支持 此层级适用于协议涵盖的容器 主机环境以及支持 ( 包括标准支持和 LTSS) 下的所有产品 协议未涵盖的产品属于第三层 10 SUSE 主机环境上的受支持容器 SLES 15 SP2

4.1.3 第三层 所有其他第三方容器 SUSE 容器主机环境受到完全支持 但是, 与容器供应商所维护的第三方容器相关的问题由相关容器供应商负责处理 4.2 支持的容器主机环境 下文述及的支持选项 ( 层 ) 适用于以下容器选项 : SUSE Linux Enterprise 基本容器由 SUSE 提供的容器派生自 SLE 基本容器的第三方容器环境使用 KIWI 通过 SLE 软件包构建的第三方容器 4.2.1 第一层 SUSE 产品此层级适用于 SUSE Linux Enterprise Server SUSE CaaS Platform 和 SUSE Cloud Application Platform 由 SUSE 提供的容器和主机环境以及支持所涵盖的所有产品受到完全支持 该支持包括标准支持和 LTSS 4.2.2 第二层 签署了确保联合工程协作协议的第三方供应商签署了联合工程协作协议的合作伙伴容器和主机环境受到完全支持 此层级适用于协议涵盖的容器 主机环境以及支持 ( 包括标准支持和 LTSS) 下的所有产品 4.2.3 第三层 未签署协议的选定第三方供应商 11 第三层 SLES 15 SP2

此层级面向由 RHEL OpenShift 或 Ubuntu 提供的环境 虽然基于 SUSE 的容器受到完全支持, 主机环境中的问题仍必须由主机环境供应商负责处理 SUSE 支持来自 SUSE 基本容器的组件, 还支持来自 SUSE 储存库的软件包 容器中的其他组件和应用程序则不受 SUSE 支持 构建派生容器需要 SLE 订阅 4.2.4 第四层 任何其他容器主机环境上述支持层中未提及的任何容器主机环境受到有限支持 相关细节请与 SUSE 支持团队讨论, 该团队可能会就问题和建议的备用解决方案进行会审 在任何其他情况下, 主机环境中的问题都必须由主机环境供应商负责处理 12 第四层 SLES 15 SP2

A GNU 许可证 本附录包含 GNU 自由文档许可证版本 1.2 GNU Free Documentation License Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. 0. PREAMBLE The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others. This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software. We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference. 1. APPLICABILITY AND DEFINITIONS This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law. A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language. A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them. The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none. The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words. A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque". Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/ or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only. The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text. A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition. The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License. 2. VERBATIM COPYING You may copy and distribute the Document in any medium, either commercially or non-commercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3. You may also lend copies, under the same conditions stated above, and you may publicly display copies. 13 SLES 15 SP2

3. COPYING IN QUANTITY If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects. If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages. If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using publicstandard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public. It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document. 4. MODIFICATIONS You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version: A. Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission. B. List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement. C. State on the Title page the name of the publisher of the Modified Version, as the publisher. D. Preserve all the copyright notices of the Document. E. Add an appropriate copyright notice for your modifications adjacent to the other copyright notices. F. Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below. G. Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice. H. Include an unaltered copy of this License. I. Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence. J. Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission. K. For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein. L. Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles. M. Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version. N. Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section. O. Preserve any Warranty Disclaimers. If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles. You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard. You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one. The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version. 5. COMBINING DOCUMENTS You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers. The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the 14 SLES 15 SP2

name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work. In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements". 6. COLLECTIONS OF DOCUMENTS You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects. You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document. 7. AGGREGATION WITH INDEPENDENT WORKS A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document. If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate. 8. TRANSLATION 10. FUTURE REVISIONS OF THIS LICENSE The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/. Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation. ADDENDUM: How to use this License for your documents Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front- Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled GNU Free Documentation License. Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail. If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title. 9. TERMINATION You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance. If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the with...texts. line with this: with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST. If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation. If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software. 15 SLES 15 SP2