OpenStack Kilo 安装指南 for CentOS

需积分: 10 57 浏览量更新于2024-07-20 收藏 1.39MB PDF 举报

"openstack kilo centos.pdf 是一份针对Red Hat Enterprise Linux 7, CentOS 7 和 Fedora 21的OpenStack Kilo版本安装指南，由OpenStack Foundation于2015年7月7日发布。" OpenStack Kilo是OpenStack开源云平台的一个重要版本，它包含了多个关键项目，这些项目可以根据云环境的需求单独安装并协同工作。以下是Kilo版本中的主要项目及其功能： 1. **Compute (Nova)**：负责管理和调度虚拟机实例的生命周期，提供计算服务。 2. **Identity Service (Keystone)**：提供认证、授权和目录服务，是OpenStack中的核心组件，管理用户、项目和角色的关系。 3. **Networking (Neutron)**：提供网络连接和隔离服务，支持多种网络模型，如VLAN、GRE、VXLAN等。 4. **Image Service (Glance)**：存储和检索虚拟机镜像，支持多种格式，如qcow2、vmdk等。 5. **Block Storage (Cinder)**：提供块级存储服务，用于虚拟机实例的持久化磁盘。 6. **Object Storage (Swift)**：设计用于大规模、分布式、冗余的存储系统，适合存储大量非结构化数据。 7. **Telemetry (Ceilometer)**：收集和处理各种OpenStack服务的度量数据，用于计费、监控和性能分析。 8. **Orchestration (Heat)**：基于模板的自动化部署和服务编排工具，可以创建和管理复杂的云应用。 9. **Database (Trove)**：提供了数据库即服务，能够方便地部署和管理数据库实例。该指南详细介绍了如何利用Fedora 21以及Red Hat Enterprise Linux 7及其EPEL仓库提供的软件包来安装OpenStack Kilo。它不仅提供了安装步骤，还包含配置选项的解释和示例配置文件，帮助用户在独立或互联环境中设置和配置各个OpenStack项目。在安装过程中，用户需要理解并准备以下事项： - 硬件需求：足够的内存、CPU和存储空间，以及网络设备。 - 配置网络：设定好网络环境，包括内网、外网和管理网络。 - 安装基础操作系统：确保系统是最新的，并且满足OpenStack的依赖要求。 - 安装和配置各个服务：按照指南的步骤，逐一安装和配置各个OpenStack组件。 - 验证安装：通过OpenStack命令行客户端或Web界面验证各个服务是否正常运行。此外，由于该指南是在2015年发布的，对于最新的OpenStack版本可能不适用，因此在实际操作时，用户需要考虑更新的版本和可能的兼容性问题，以及查阅最新的官方文档以获取最新的信息和支持。

Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -Kilo -

OpenStack Installation Guide for

Red Hat Enterprise Linux, CentOS,

and Fedora

July 7, 2015 kilo

Figure1.6.Minimal architecture example with legacy networking (nova-

network)—Network layout

OpenStack Installation Guide for

Red Hat Enterprise Linux, CentOS,

and Fedora

July 7, 2015 kilo

2. Basic environment

Table of Contents

Before you begin .......................................................................................................... 11

Security ......................................................................................................................... 12

Networking ................................................................................................................... 13

Network Time Protocol (NTP) ........................................................................................ 25

OpenStack packages ..................................................................................................... 27

SQL database ................................................................................................................ 28

Message queue ............................................................................................................. 30

Note

The trunk version of this guide focuses on the future Kilo release and will not

work for the current Juno release. If you want to install Juno, you must use the

Juno version of this guide instead.

This chapter explains how to configure each node in the example architectures including

the two-node architecture with legacy networking and three-node architecture with Open-

Stack Networking (neutron).

Note

Although most environments include Identity, Image service, Compute, at least

one networking service, and the dashboard, the Object Storage service can op-

erate independently. If your use case only involves Object Storage, you can skip

to Chapter9, “Add Object Storage” [111] after configuring the appropriate

nodes for it. However, the dashboard requires at least the Image service and

Compute.

Note

You must use an account with administrative privileges to configure each node.

Either run the commands as the root user or configure the sudo utility.

Note

The systemctl enable call on openSUSE outputs a warning message when the

service uses SysV Init scripts instead of native systemd files. This warning can be

ignored.

Before you begin

For best performance, we recommend that your environment meets or exceeds the hard-

ware requirements in Figure1.2, “Minimal architecture example with OpenStack Network-

ing (neutron)—Hardware requirements” [4] or Figure1.5, “Minimal architecture example

OpenStack Installation Guide for

Red Hat Enterprise Linux, CentOS,

and Fedora

July 7, 2015 kilo

with legacy networking (nova-network)—Hardware requirements” [8]. However, Open-

Stack does not require a significant amount of resources and the following minimum re-

quirements should support a proof-of-concept environment with core services and several

CirrOS instances:

• Controller Node: 1 processor, 2 GB memory, and 5 GB storage

• Network Node: 1 processor, 512 MB memory, and 5 GB storage

• Compute Node: 1 processor, 2 GB memory, and 10 GB storage

To minimize clutter and provide more resources for OpenStack, we recommend a minimal

installation of your Linux distribution. Also, we strongly recommend that you install a 64-

bit version of your distribution on at least the compute node. If you install a 32-bit version

of your distribution on the compute node, attempting to start an instance using a 64-bit im-

age will fail.

Note

A single disk partition on each node works for most basic installations. Howev-

er, you should consider Logical Volume Manager (LVM) for installations with op-

tional services such as Block Storage.

Many users build their test environments on virtual machines (VMs). The primary benefits of

VMs include the following:

• One physical server can support multiple nodes, each with almost any number of net-

work interfaces.

• Ability to take periodic "snap shots" throughout the installation process and "roll back" to

a working configuration in the event of a problem.

However, VMs will reduce performance of your instances, particularly if your hypervisor

and/or processor lacks support for hardware acceleration of nested VMs.

Note

If you choose to install on VMs, make sure your hypervisor permits promiscuous

mode and disables MAC address filtering on the external network.

For more information about system requirements, see the OpenStack Operations Guide.

Security

OpenStack services support various security methods including password, policy, and en-

cryption. Additionally, supporting services including the database server and message bro-

ker support at least password security.

To ease the installation process, this guide only covers password security where applicable.

You can create secure passwords manually, generate them using a tool such as pwgen, or

by running the following command:

$ openssl rand -hex 10

OpenStack Installation Guide for

Red Hat Enterprise Linux, CentOS,

and Fedora

July 7, 2015 kilo

For OpenStack services, this guide uses SERVICE_PASS to reference service account pass-

words and SERVICE_DBPASS to reference database passwords.

The following table provides a list of services that require passwords and their associated

references in the guide:

Table2.1.Passwords

Password name Description

Database password (no variable used) Root password for the database

ADMIN_PASS Password of user admin

CEILOMETER_DBPASS Database password for the Telemetry service

CEILOMETER_PASS Password of Telemetry service user ceilometer

CINDER_DBPASS Database password for the Block Storage service

CINDER_PASS Password of Block Storage service user cinder

DASH_DBPASS Database password for the dashboard

DEMO_PASS Password of user demo

GLANCE_DBPASS Database password for Image service

GLANCE_PASS Password of Image service user glance

HEAT_DBPASS Database password for the Orchestration service

HEAT_DOMAIN_PASS Password of Orchestration domain

HEAT_PASS Password of Orchestration service user heat

KEYSTONE_DBPASS Database password of Identity service

NEUTRON_DBPASS Database password for the Networking service

NEUTRON_PASS Password of Networking service user neutron

NOVA_DBPASS Database password for Compute service

NOVA_PASS Password of Compute service user nova

RABBIT_PASS Password of user guest of RabbitMQ

SAHARA_DBPASS Database password of Data processing service

SWIFT_PASS Password of Object Storage service user swift

TROVE_DBPASS Database password of Database service

TROVE_PASS Password of Database service user trove

OpenStack and supporting services require administrative privileges during installation and

operation. In some cases, services perform modifications to the host that can interfere with

deployment automation tools such as Ansible, Chef, and Puppet. For example, some Open-

Stack services add a root wrapper to sudo that can interfere with security policies. See the

Cloud Administrator Guide for more information. Also, the Networking service assumes de-

fault values for kernel network parameters and modifies firewall rules. To avoid most issues

during your initial installation, we recommend using a stock deployment of a supported dis-

tribution on your hosts. However, if you choose to automate deployment of your hosts, re-

view the configuration and policies applied to them before proceeding further.

Networking

After installing the operating system on each node for the architecture that you choose to

deploy, you must configure the network interfaces. We recommend that you disable any

automated network management tools and manually edit the appropriate configuration

剩余177页未读，继续阅读

傻呆

粉丝: 150
资源: 13

OpenStack Kilo 安装指南 for CentOS

OpenStack Kilo—CentOS安装指南 中文版

openstack_rocky.tar.gz

Failed to start openstack-keystone.service: Unit not found.

Job for openstack-keystone.service failed because the control process exited with error code

下载openstack-train.tar.gz

<class 'openstack.identity.v3.user.User'>是什么数据类型

openstack云平台搭建

怎么解决tar (child): openstack_ansible.tar(2).gz: Cannot open: No such file or directory tar (child): Error is not recoverable: exiting now tar: Child returned status 2 tar: Error is not recoverable: exiting now

最新资源

OpenStack Kilo—CentOS安装指南中文版