OpenStack Queens for RHEL and CentOS安装指南

OpenStack for RHEL and CentOS Installation Guide

V20180818

Verify operation of the Image service using CirrOS, a small Linux image that helps you test your OpenStack deployment.

For more information about how to download and build images, see OpenStack Virtual Machine Image Guide. For information about how to manage images,

see the OpenStack End User Guide.

Note

Perform these commands on the controller node.

Install wget if your distribution does not include it.

3.Upload the image to the Image service using the QCOW2 disk format, bare container format, and public visibility so all projects can access it:

$ openstack image create "cirros" \

--file cirros-0.4.0-x86_64-disk.img \

--disk-format qcow2 --container-format bare \

--public

+------------------+------------------------------------------------------+

| Field | Value |

+------------------+------------------------------------------------------+

| checksum | 133eae9fb1c98f45894a4e60d8736619 |

| min_ram | 0 |

| name | cirros |

| owner | ae7a98326b9c455588edd2656d723b9d |

| protected | False |

| schema | /v2/schemas/image |

| size | 13200896 |

| status | active |

| tags | |

| updated_at | 2015-03-26T16:52:10Z |

| virtual_size | None |

Note

OpenStack generates IDs dynamically, so you will see different values in the example command output.

4.Confirm upload of the image and validate attributes:

$ openstack image list

+--------------------------------------+--------+--------+

| ID | Name | Status |

+--------------------------------------+--------+--------+

| 38047887-61a7-41ea-9b49-27987d5e8bb9 | cirros | active |

+--------------------------------------+--------+--------+

nova installation for Queens

•Object Storage

•Networking

•Networking Option 1: Provider networks

•Networking Option 2: Self-service networks

•Compute service overview

•Install and configure controller node

•Install and configure controller node for Ubuntu

•Prerequisites

•Install and configure components

•Finalize installation

•Install and configure components

•Finalize installation

•Install and configure a compute node

•Install and configure a compute node for Ubuntu

•Install and configure components

•Finalize installation

•Add the compute node to the cell database

•Install and configure a compute node for Red Hat Enterprise Linux and CentOS

•Install and configure components

•Finalize installation

Overview

The OpenStack project is an open source cloud computing platform that supports all types of cloud environments. The project aims for simple

implementation, massive scalability, and a rich set of features. Cloud computing experts from around the world contribute to the project.

OpenStack provides an Infrastructure-as-a-Service (IaaS) solution through a variety of complementary services. Each service offers an Application

Programming Interface (API) that facilitates this integration.

This guide covers step-by-step deployment of the major OpenStack services using a functional example architecture suitable for new users of OpenStack with

sufficient Linux experience. This guide is not intended to be used for production system installations, but to create a minimum proof-of-concept for the

purpose of learning about OpenStack.

After becoming familiar with basic installation, configuration, operation, and troubleshooting of these OpenStack services, you should consider the following

steps toward deployment using a production architecture:

Important

The example architecture used in this guide is a minimum configuration, and is not intended for production system installations. It is designed to provide a

minimum proof-of-concept for the purpose of learning about OpenStack. For information on creating architectures for specific use cases, or how to

determine which architecture is required, see the Architecture Design Guide.

This 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.

• Overlay (tunnel) traffic for self-service networks traverses the management network instead of a dedicated network.

For more information on production architectures, see the Architecture Design Guide, OpenStack Operations Guide, and OpenStack Networking Guide.

Hardware requirements

The compute node runs the hypervisor portion of Compute that operates instances. By default, Compute uses the kernel-based VM (KVM) hypervisor. The

compute node also runs a Networking service agent that connects instances to virtual networks and provides firewalling services to instances via security

groups.

You can deploy more than one compute node. Each node requires a minimum of two network interfaces.

Block Storage

The optional Block Storage node contains the disks that the Block Storage and Shared File System services provision for instances.

For simplicity, service traffic between compute nodes and this node uses the management network. Production environments should implement a separate

storage network to increase performance and security.

You can deploy more than one block storage node. Each node requires a minimum of one network interface.

Object Storage

The provider networks option deploys the OpenStack Networking service in the simplest way possible with primarily layer-2 (bridging/switching) services and

VLAN segmentation of networks. Essentially, it bridges virtual networks to physical networks and relies on physical network infrastructure for layer-3 (routing)

services. Additionally, a DHCP<Dynamic Host Configuration Protocol (DHCP) service provides IP address information to instances.

The OpenStack user requires more information about the underlying network infrastructure to create a virtual network to exactly match the infrastructure.

Warning

This option lacks support for self-service (private) networks, layer-3 (routing) services, and advanced services such as Load-Balancer-as-a-Service (LBaaS)

and FireWall-as-a-Service (FWaaS). Consider the self-service networks option below if you desire these features.

Networking Option 2: Self-service networks