Jump to contentJump to page navigation: previous page [access key p]/next page [access key n]
SUSE OpenStack Cloud 8

Planning an Installation with Cloud Lifecycle Manager Edit source

Publication Date: 07/29/2021
I Planning
1 Registering SLES
1.1 Registering SLES during the Installation
1.2 Registering SLES from the Installed System
1.3 Registering SLES during Automated Deployment
2 Hardware and Software Support Matrix
2.1 OpenStack Version Information
2.2 Supported Hardware Configurations
2.3 Support for Core and Non-Core OpenStack Features
2.4 Cloud Scaling
2.5 Supported Software
2.6 Notes About Performance
2.7 KVM Guest OS Support
2.8 ESX Guest OS Support
2.9 Ironic Guest OS Support
3 Recommended Hardware Minimums for the Example Configurations
3.1 Recommended Hardware Minimums for an Entry-scale KVM
3.2 Recommended Hardware Minimums for an Entry-scale ESX KVM Model
3.3 Recommended Hardware Minimums for an Entry-scale ESX, KVM with Dedicated Cluster for Metering, Monitoring, and Logging
3.4 Recommended Hardware Minimums for an Ironic Flat Network Model
3.5 Recommended Hardware Minimums for an Entry-scale Swift Model
4 High Availability
4.1 High Availability Concepts Overview
4.2 Highly Available Cloud Infrastructure
4.3 High Availability of Controllers
4.4 High Availability Routing - Centralized
4.5 High Availability Routing - Distributed
4.6 Availability Zones
4.7 Compute with KVM
4.8 Nova Availability Zones
4.9 Compute with ESX Hypervisor
4.10 Cinder Availability Zones
4.11 Object Storage with Swift
4.12 Highly Available Cloud Applications and Workloads
4.13 What is not Highly Available?
4.14 More Information
II Cloud Lifecycle Manager Overview
5 Input Model
5.1 Introduction to the Input Model
5.2 Concepts
6 Configuration Objects
6.1 Cloud Configuration
6.2 Control Plane
6.3 Load Balancers
6.4 Regions
6.5 Servers
6.6 Server Groups
6.7 Server Roles
6.8 Disk Models
6.9 Memory Models
6.10 CPU Models
6.11 Interface Models
6.12 NIC Mappings
6.13 Network Groups
6.14 Networks
6.15 Firewall Rules
6.16 Configuration Data
6.17 Pass Through
7 Other Topics
7.1 Services and Service Components
7.2 Name Generation
7.3 Persisted Data
7.4 Server Allocation
7.5 Server Network Selection
7.6 Network Route Validation
7.7 Configuring Neutron Provider VLANs
7.8 Standalone Cloud Lifecycle Manager
8 Configuration Processor Information Files
8.1 address_info.yml
8.2 firewall_info.yml
8.3 route_info.yml
8.4 server_info.yml
8.5 service_info.yml
8.6 control_plane_topology.yml
8.7 network_topology.yml
8.8 region_topology.yml
8.9 service_topology.yml
8.10 private_data_metadata_ccp.yml
8.11 password_change.yml
8.12 explain.txt
8.13 CloudDiagram.txt
8.14 HTML Representation
9 Example Configurations
9.1 SUSE OpenStack Cloud Example Configurations
9.2 Alternative Configurations
9.3 KVM Examples
9.4 ESX Examples
9.5 Swift Examples
9.6 Ironic Examples
10 Modifying Example Configurations for Compute Nodes
10.1 SLES Compute Nodes
11 Modifying Example Configurations for Object Storage using Swift
11.1 Object Storage using Swift Overview
11.2 Allocating Proxy, Account, and Container (PAC) Servers for Object Storage
11.3 Allocating Object Servers
11.4 Creating Roles for Swift Nodes
11.5 Allocating Disk Drives for Object Storage
11.6 Swift Requirements for Device Group Drives
11.7 Creating a Swift Proxy, Account, and Container (PAC) Cluster
11.8 Creating Object Server Resource Nodes
11.9 Understanding Swift Network and Service Requirements
11.10 Understanding Swift Ring Specifications
11.11 Designing Storage Policies
11.12 Designing Swift Zones
11.13 Customizing Swift Service Configuration Files
12 Alternative Configurations
12.1 Using a Dedicated Cloud Lifecycle Manager Node
12.2 Configuring SUSE OpenStack Cloud without DVR
12.3 Configuring SUSE OpenStack Cloud with Provider VLANs and Physical Routers Only
12.4 Considerations When Installing Two Systems on One Subnet

Copyright © 2006– 2021 SUSE LLC and contributors. All rights reserved.

Except where otherwise noted, this document is licensed under Creative Commons Attribution 3.0 License :

For SUSE trademarks, see http://www.suse.com/company/legal/. All other third-party trademarks are the property of their respective owners. Trademark symbols (®, ™ etc.) denote trademarks of SUSE and its affiliates. Asterisks (*) denote third-party trademarks.

All information found in this book has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors nor the translators shall be held liable for possible errors or the consequences thereof.

Print this page