Install Guide - OpenStack

1 Install GuideOpenStack contributorsJan 20, 2022 CONTENTS1 Notices.. Command prompts..12 Abstract.. Operating systems..33 Get started with The OpenStack services.. The OpenStack architecture.. Conceptual architecture.. Logical architecture..64 Example architecture.. Controller.. Compute.. Block Storage.. Object Storage.. Networking.. Networking Option 1: Provider networks.. Networking Option 2: Self-service networks..145 Security.. Host networking.. Controller node.. Compute node.. Block storage node (Optional).. Verify connectivity.. Network Time Protocol (NTP).. Controller node.. Other nodes.. Verify operation.. OpenStack packages.. OpenStack packages for SUSE.. OpenStack packages for RHEL and CentOS.. OpenStack packages for Ubuntu.. SQL database.. SQL database for SUSE.. SQL database for RHEL and CentOS.

2 SQL database for Ubuntu.. Message queue.. Message queue for SUSE.. Message queue for RHEL and CentOS.. Message queue for Ubuntu.. Memcached.. Memcached for SUSE.. Memcached for RHEL and CentOS.. Memcached for Ubuntu.. Etcd.. Etcd for SUSE.. Etcd for RHEL and CentOS.. Etcd for Ubuntu..456 Install OpenStack Minimal deployment for Wallaby.. Minimal deployment for Victoria.. Minimal deployment for Ussuri.. Minimal deployment for Train.. Minimal deployment for Stein.. Minimal deployment for Rocky.. Minimal deployment for Queens.. Minimal deployment for Pike..507 Launch an Create virtual networks.. Provider network.. Self-service network.. Create avor.. Generate a key pair.. Add security group rules.. Launch an instance.. Launch an instance on the provider network.. Launch an instance on the self-service network.

3 Block Storage.. Block Storage.. Orchestration.. Shared File Systems..788 Firewalls and default ports799 Community support.. Documentation.. The OpenStack wiki.. The Launchpad bugs area.. Documentation feedback.. The OpenStack IRC channel.. OpenStack mailing lists.. OpenStack distribution packages.. Glossary.. 0-9.. A.. B.. C.. D.. E.. F.. G.. H.. I.. J.. K.. L.. M.. N.. O.. P.. Q.. R.. S.. T.. U.. V.. W.. X.. Y.. Z..121 Index123iiiivCHAPTERONECONVENTIONSThe OpenStack documentation uses several typesetting take these forms:Note:A comment with additional information that explains a part of the :Something you must be aware of before :An extra but helpful piece of practical :Helpful information that prevents the user from making :Critical information about the risk of data loss or security prompts$commandAny user, including therootuser, can run commands that are pre xed with the$prompt.

4 #commandTherootuser must run commands that are pre xed with the#prompt. You can also pre x these com-mands with thesudocommand, if available, to run Guide2 Chapter 1. OpenStack system consists of several key services that are separately installed. These services worktogether depending on your cloud needs and include the Compute, Identity, Networking, Image, BlockStorage, Object Storage, Telemetry, Orchestration, and Database services. You can Install any of theseprojects separately and con gure them stand-alone or as connected of con guration options and sample con guration les are Guide documents the installation of OpenStack starting with the Pike release. It covers :This Guide is a work-in-progress and is subject to updates frequently. Pre-release packageshave been used for testing, and some instructions may not work with nal versions. Please help usmake this Guide better by reporting any errors you systemsCurrently, this Guide describes OpenStack installation for the following Linux distributions:openSUSE and SUSE Linux Enterprise ServerYou can Install OpenStack by using packages onopenSUSE Leap , openSUSE Leap 15, SUSE Linux Enterprise Server 12 SP4, SUSE LinuxEnterprise Server 15 through the Open Build Service Cloud Hat Enterprise Linux and CentOSYou can Install OpenStack by using packages available onboth Red Hat Enterprise Linux 7 and 8 and their derivatives through the RDO : OpenStack Wallaby is available for CentOS Stream 8.

5 OpenStack Ussuri and Victoriaare available for both CentOS 8 and RHEL 8. OpenStack Train and earlier are available on bothCentOS 7 and RHEL can walk through an installation by using packages available through Canonicals UbuntuCloud archive repository for Ubuntu + (LTS).Note:The Ubuntu Cloud Archive pockets for Pike and Queens provide OpenStack packages forUbuntu LTS; OpenStack Queens is installable direct using Ubuntu LTS; the Ubuntu3 Install GuideCloud Archive pockets for Rocky and Stein provide OpenStack packages for Ubuntu LTS;the Ubuntu Cloud Archive pocket for Victoria provides OpenStack packages for Ubuntu 2. PrefaceCHAPTERTHREEGET STARTED WITH OPENSTACKThe OpenStack project is an open source cloud computing platform for all types of clouds, which aimsto be simple to implement, massively scalable, and feature rich. Developers and cloud computing tech-nologists from around the world create the OpenStack provides anInfrastructure-as-a-Service (IaaS)solution through a set of interrelated service offers anApplication Programming Interface (API)that facilitates this integration.

6 Depend-ing on your needs, you can Install some or all OpenStack servicesTheOpenStack project navigatorlets you browse the OpenStack services that make up the OpenStackarchitecture. The services are categorized per the service type and release OpenStack architectureThe following sections describe the OpenStack architecture in more detail:5 Install architectureThe following diagram shows the relationships among the OpenStack architectureTo design, deploy, and con gure OpenStack , administrators must understand the logical shown inConceptual architecture, OpenStack consists of several independent parts, named the Open-Stack services. All services authenticate through a common Identity service. Individual services interactwith each other through public APIs, except where privileged administrator commands are , OpenStack services are composed of several processes. All services have at least one APIprocess, which listens for API requests, preprocesses them and passes them on to other parts of theservice.

7 With the exception of the Identity service, the actual work is done by distinct communication between the processes of one service, an AMQP message broker is used. The ser-vices state is stored in a database. When deploying and con guring your OpenStack cloud, you canchoose among several message broker and database solutions, such as RabbitMQ, MySQL, MariaDB,and can access OpenStack via the web-based user interface implemented by the Horizon Dashboard,viacommand-line clientsand by issuing API requests through tools like browser plug-ins orcurl. Forapplications,several SDKsare available. Ultimately, all these access methods issue REST API calls tothe various OpenStack 3. Get started with OpenStackInstall GuideThe following diagram shows the most common, but not the only possible, architecture for an The OpenStack architecture7 Install Guide8 Chapter 3. Get started with OpenStackCHAPTERFOUROVERVIEWTheOpenStack project is an open source cloud computing platform that supports all types of cloudenvironments.

8 The project aims for simple implementation, massive scalability, and a rich set of computing experts from around the world contribute to the provides anInfrastructure-as-a-Service (IaaS)solution through a variety of complementaryservices. Each service offers anApplication Programming Interface (API)that facilitates this Guide covers step-by-step deployment of the major OpenStack services using a functional examplearchitecture suitable for new users of OpenStack with sufficient Linux experience. This Guide is notintended to be used for production system installations, but to create a minimum proof-of-concept for thepurpose of learning about becoming familiar with basic installation, con guration, operation, and troubleshooting of theseOpenStack services, you should consider the following steps toward deployment using a production ar-chitecture: Determine and implement the necessary core and optional services to meet performance and re-dundancy requirements.

9 Increase security using methods such as rewalls, encryption, and service policies. Use a deployment tool such as Ansible, Chef, Puppet, or Salt to automate deployment and manage-ment of the production environment. The OpenStack project has a couple of deployment projectswith speci c guides per version: Wallaby release Victoria release Ussuri release Train release Stein release Rocky release Queens release Pike release9 Install architectureThe example architecture requires at least two nodes (hosts) to launch a basicvirtual machineor services such as Block Storage and Object Storage require additional :The example architecture used in this Guide is a minimum con guration, and is not intendedfor production system installations. It is designed to provide a minimum proof-of-concept for the purposeof learning about OpenStack . For information on creating architectures for speci c use cases, or how todetermine which architecture is required, see theArchitecture Design example architecture differs from a minimal production architecture as follows: Networking agents reside on the controller node instead of one or more dedicated network nodes.

10 Overlay (tunnel) traffic for self-service networks traverses the management network instead of adedicated more information on production architectures for Pike, see theArchitecture Design Guide ,OpenStackNetworking Guide for Pike, andOpenStack Administrator Guides for more information on production architectures for Queens, see theArchitecture Design Guide ,Open-Stack Networking Guide for Queens, andOpenStack Administrator Guides for more information on production architectures for Rocky, see theArchitecture Design Guide ,Open-Stack Networking Guide for Rocky, andOpenStack Administrator Guides for controller node runs the Identity service, Image service, Placement service, management portionsof Compute, management portion of Networking, various Networking agents, and the Dashboard. It alsoincludes supporting services such as an SQL database,message queue, , the controller node runs portions of the Block Storage, Object Storage, Orchestration, andTelemetry controller node requires a minimum of two network compute node runs thehypervisorportion of Compute that operates instances.