SUSE OpenStack Cloud Crowbar OpenStack User Guide OpenStack User Guide SUSE OpenStack Cloud Crowbar Publication Date: 07/29/2021 SUSE LLC 1800 South Novell Place Provo, UT 84606 USA https://documentation.suse.com Contents 1 Glance User Guide 1 1.1 Image Identifiers 1 1.2 Image Statuses 1 1.3 Task Statuses 4 1.4 Image Statuses 4 1.5 Task Statuses 7 1.6 Disk and Container Formats 7 Disk Format 7 • Container Format 8 1.7 Common Image Properties 9 architecture 9 • instance_uuid 10 • kernel_id 10 • ramdisk_id 10 • os_distro 10 • os_version 10 1.8 Metadata Definition Concepts 10 Terminology 11 1.9 Using Glance’s Image Public APIs 14 Glance and the Images APIs: Past, Present, and Future 15 • Authentication 17 • Using v1.X 17 • Image Membership Changes in Version 2.0 28 • Images v2 Tasks API 29 • API Message Localization 31 1.10 Using Glance’s Client Tools 32 1.11 Using Glance’s Metadata Definitions Catalog Public APIs 32 Authentication 33 • Using v2.X 33 • API Message Localization 44 1.12 Image Signature Verification 45 Requirements 45 • Configuration 45 • Using the Signature Verification 46 • Example Usage 48 • Other Links 49 iii OpenStack User Guide 2 Ironic User Guide 50 2.1 Why Provision Bare Metal 50 2.2 Conceptual Architecture 50 2.3 Logical Architecture 53 2.4 Key Technologies for Bare Metal Hosting 55 Preboot Execution Environment (PXE) 55 • Dynamic Host Configuration Protocol (DHCP) 56 • Network Bootstrap Program (NBP) 56 • Trivial File Transfer Protocol (TFTP) 56 • Intelligent Platform Management Interface (IPMI) 56 2.5 Ironic Deployment Architecture 56 2.6 Understanding Bare Metal Deployment 57 Deploy Process 59 • Example 1: PXE Boot and iSCSI Deploy Process 61 • Example 2: PXE Boot and Direct Deploy Process 61 3 Horizon User Guide 62 3.1 OpenStack Dashboard User Documentation 62 Log in to the dashboard 62 • Upload and manage images 68 • Configure access and security for instances 75 • Launch and manage instances 79 • Create and manage networks 85 • Create and manage object containers 88 • Create and manage volumes 91 • Create and manage shares 95 • Launch and manage stacks 99 • Create and manage databases 106 • View and manage load balancers v2 110 • Supported Browsers 112 4 Keystone User Guide 116 4.1 User Documentation 116 API Examples using Curl 116 5 Magnum User Documentation 143 5.1 Introduction 143 5.2 Terminology 143 5.3 Overview 144 iv OpenStack User Guide 5.4 ClusterTemplate 144 Labels 149 5.5 Cluster 152 Infrastructure 152 • Life cycle 153 5.6 Python Client 158 Installation 158 • Verifying installation 158 • Using the command-line client 158 5.7 Horizon Interface 159 5.8 Cluster Drivers 160 Directory structure 160 • Sample cluster driver 161 • Installing a cluster driver 162 5.9 Cluster Type Definition 162 The Heat Stack Template 162 • The Template Definition 162 • The Definition Entry Point 162 • Installing Cluster Templates 163 5.10 Heat Stack Templates 164 5.11 Choosing a COE 165 5.12 Native Clients 166 5.13 Kubernetes 167 External load balancer for services 170 5.14 Swarm 171 5.15 Mesos 173 Building Mesos image 177 • Using Marathon 178 5.16 Transport Layer Security 179 Deploying a secure cluster 179 • Interfacing with a secure cluster 182 • User Examples 184 • Storing the certificates 186 5.17 Networking 187 5.18 High Availability 189 v OpenStack User Guide 5.19 Scaling 189 Performance tuning for periodic task 189 • Containers and nodes 190 5.20 Storage 192 Ephemeral storage 193 • Persistent storage 194 5.21 Image Management 198 Kubernetes on Fedora Atomic 199 • Kubernetes on CoreOS 200 • Kubernetes on Ironic 201 • Swarm on Fedora Atomic 201 • Mesos on Ubuntu 201 5.22 Notification 202 Auditing with CADF 202 • Supported Events 206 • Example Notification - Cluster Create 206 5.23 Container Monitoring 207 Container Monitoring in Kubernetes 208 5.24 Kubernetes External Load Balancer 208 Steps for the cluster administrator 209 • Steps for the users 210 • How it works 213 5.25 Terminology 215 5.26 Overview 216 5.27 ClusterTemplate 217 Labels 221 5.28 Cluster 224 Infrastructure 224 • Life cycle 226 5.29 Python Client 230 Installation 230 • Verifying installation 230 • Using the command-line client 231 5.30 Horizon Interface 231 5.31 Cluster Drivers 232 Directory structure 232 • Sample cluster driver 233 • Installing a cluster driver 234 vi OpenStack User Guide 5.32 Cluster Type Definition 234 The Heat Stack Template 234 • The Template Definition 234 • The Definition Entry Point 234 • Installing Cluster Templates 235 5.33 Heat Stack Templates 236 5.34 Choosing a COE 237 5.35 Native Clients 238 5.36 Kubernetes 239 External load balancer for services 242 5.37 Swarm 243 5.38 Mesos 245 Building Mesos image 249 • Using Marathon 250 5.39 Transport Layer Security 251 Deploying a secure cluster 251 • Interfacing with a secure cluster 254 • User Examples 256 • Storing the certificates 258 5.40 Networking 259 5.41 High Availability 261 5.42 Scaling 261 Performance tuning for periodic task 261 • Containers and nodes 262 5.43 Storage 264 Ephemeral storage 265 • Persistent storage 266 5.44 Image Management 270 Kubernetes on Fedora Atomic 271 • Kubernetes on CoreOS 272 • Kubernetes on Ironic 273 • Swarm on Fedora Atomic 273 • Mesos on Ubuntu 273 5.45 Notification 274 Auditing with CADF 274 • Supported Events 278 • Example Notification - Cluster Create 278 5.46 Container Monitoring 279 Container Monitoring in Kubernetes 280 vii OpenStack User Guide 5.47 Kubernetes External Load Balancer 280 Steps for the cluster administrator 281 • Steps for the users 282 • How it works 285 6 Nova User Guide 288 6.1 Tools for using Nova 288 6.2 Writing to the API 288 Glossary 290 viii OpenStack User Guide 1 Glance User Guide 1.1 Image Identifiers Images are uniquely identied by way of a URI that matches the following signature: <Glance Server Location>/v1/images/<ID> where <Glance Server Location> is the resource location of the Glance service that knows about an image, and <ID> is the image’s identier. Image identiers in Glance are uuids, making them globally unique. 1.2 Image Statuses Images in Glance can be in one the following statuses: queued The image identier has been reserved for an image in the Glance registry. No image data has been uploaded to Glance and the image size was not explicitly set to zero on creation. saving Denotes that an image’s raw data is currently being uploaded to Glance. When an image is registered with a call to POST /images and there is an x-image-meta-location header present, that image will never be in the saving status (as the image data is already available in some other location). active Denotes an image that is fully available in Glance. This occurs when the image data is uploaded, or the image size is explicitly set to zero on creation. deactivated Denotes that access to image data is not allowed to any non-admin user. Prohibiting downloads of an image also prohibits operations like image export and image cloning that may require image data. killed Denotes that an error occurred during the uploading of an image’s data, and that the image is not readable. 1 Image Identifiers SUSE OpenStack Cl… deleted Glance has retained the information about the image, but it is no longer available to use. An image in this state will be removed automatically at a later date. pending_delete This is similar to deleted , however, Glance has not yet removed the image data. An image in this state is not recoverable. 2 Image Statuses SUSE OpenStack Cl… FIGURE 1.1: THIS IS A REPRESENTATION OF HOW THE IMAGE MOVE FROM ONE STATUS TO THE NEXT. 3 Image Statuses SUSE OpenStack Cl… 1.3 Task Statuses Tasks in Glance can be in one the following statuses: pending The task identier has been reserved for a task in the Glance. No processing has begun on it yet. processing The task has been picked up by the underlying executor and is being run using the backend Glance execution logic for that task type. success Denotes that the task has had a successful run within Glance. The result eld of the task shows more details about the outcome. failure Denotes that an error occurred during the execution of the task and it cannot continue processing. The message eld of the task shows what the error was. 1.4 Image Statuses Images in Glance can be in one the following statuses: queued The image identier has been reserved for an image in the Glance registry. No image data has been uploaded to Glance and the image size was not explicitly set to zero on creation. saving Denotes that an image’s raw data is currently being uploaded to Glance. When an image is registered with a call to POST /images and there is an x-image-meta-location header present, that image will never be in the saving status (as the image data is already available in some other location). active Denotes an image that is fully available in Glance. This occurs when the image data is uploaded, or the image size is explicitly set to zero on creation. deactivated 4 Task Statuses SUSE OpenStack Cl… Denotes that access to image data is not allowed to any non-admin user. Prohibiting downloads of an image also prohibits operations like image export and image cloning that may require image data. killed Denotes that an error occurred during the uploading of an image’s data, and that the image is not readable. deleted Glance has retained the information about the image, but it is no longer available to use.