OpenStack Compute管理员指南：安装与管理

4星 · 超过85%的资源需积分: 10 187 浏览量更新于2024-07-22 收藏 3.97MB PDF 举报

《OpenStack Compute Administration Manual》是一份详尽的指南，针对的是OpenStack Compute的安装、管理和理解。OpenStack Compute是OpenStack项目中负责提供基础设施即服务（IaaS）的核心组件，特别适用于任何组织构建和管理私有云环境。该手册于2012年9月17日发布的Essex（2012.1）版本，由OpenStack LLC版权所有，其软件遵循Apache License 2.0，这是一种宽松的开源许可协议，允许用户在遵守版权条款的前提下自由使用、修改和分发。在安装部分，手册提供了详细的步骤和配置指导，确保管理员能够顺利地在他们的服务器集群上部署OpenStack Compute服务，包括诸如Nova（计算服务）、Neutron（网络服务）和Glance（镜像服务）等关键组件。管理员可以在这里了解如何设置基础架构，包括硬件需求、网络配置以及存储策略。管理方面，手册深入解析了OpenStack Compute的日常运维，包括创建和管理虚拟机实例、卷、网络和安全组，以及监控和优化性能。此外，它还涵盖了故障排查和恢复的策略，确保系统的稳定性和可用性。理解软件运行机制是另一个核心内容，手册解释了OpenStack Compute的工作原理，包括API的使用、底层技术（如虚拟化技术，如KVM或Xen）以及与OpenStack其他服务的交互。此外，它还讨论了如何扩展和定制OpenStack Compute以满足特定业务需求。值得注意的是，此文档不仅受Apache License 2.0保护，同时也受到Creative Commons Attribution ShareAlike 3.0 License的许可，这意味着用户在引用或修改此文档时必须遵循共享相同的许可证条件，尊重原作者的知识产权。《OpenStack Compute Administration Manual》对于任何希望在企业环境中实施和管理OpenStack Compute的IT专业人员来说，是一份不可或缺的参考资料，它详细阐述了如何构建、维护和优化一个功能强大的云计算平台。

OpenStack Compute

Administration Manual

Sep 17, 2012 Essex (2012.1)

As with most web applications, the architecture is fairly simple:

• Horizon is usually deployed via mod_wsgi in Apache. The code itself is seperated into

a reusable python module with most of the logic (interactions with various OpenStack

APIs) and presentation (to make it easily customizable for different sites).

• A database (configurable to which one). As it relies mostly on the other services for data,

it stores very little data of it's own.

From a network architecture point of view, this service will need to customer accessible

as well as be able to talk to each services public APIs. If you wish to use the administrator

functionality (i.e. for other services), it will also need connectivity to their Admin API

endpoints (which should be non-customer accessible).

Compute

Not much has really changed with Nova's architecture. They have added a few new helper

services for EC2 compatibility and console services.

• nova-api accepts and responds to end user compute and volume API calls. It supports

OpenStack API, Amazon's EC2 API and a special Admin API (for privileged users to

OpenStack Compute

Administration Manual

Sep 17, 2012 Essex (2012.1)

perform administrative actions). It also initiates most of the orchestration activities (such

as running an instance) as well as enforces some policy (mostly quota checks). In the

Essex release, nova-api has been modularized, allowing for implementers to run only

specific APIs.

• The nova-compute process is primarily a worker daemon that creates and terminates

virtual machine instances via hypervisor's APIs (XenAPI for XenServer/XCP, libvirt for

KVM or QEMU, VMwareAPI for VMware, etc.). The process by which it does so is fairly

complex but the basics are simple: accept actions from the queue and then perform

a series of system commands (like launching a KVM instance) to carry them out while

updating state in the database.

• nova-volume manages the creation, attaching and detaching of persistent volumes to

compute instances (similar functionality to Amazon’s Elastic Block Storage). It can use

volumes from a variety of providers such as iSCSI or Rados Block Device in Ceph.

• The nova-network worker daemon is very similar to nova-compute and nova-

volume. It accepts networking tasks from the queue and then performs tasks to

manipulate the network (such as setting up bridging interfaces or changing iptables

rules).

• The nova-schedule process is conceptually the simplest piece of code in OpenStack

Nova: take a virtual machine instance request from the queue and determines where it

should run (specifically, which compute server host it should run on).

• The queue provides a central hub for passing messages between daemons. This is usually

implemented with RabbitMQ today, but could be any AMPQ message queue (such as

Apache Qpid).

• The SQL database stores most of the build-time and run-time state for a cloud

infrastructure. This includes the instance types that are available for use, instances in

use, networks available and projects. Theoretically, OpenStack Nova can support any

database supported by SQL-Alchemy but the only databases currently being widely used

are sqlite3 (only appropriate for test and development work), MySQL and PostgreSQL.

During the last two releases, Nova has augmented it's console services. Console services

allow end users to access their virtual instance's console through a proxy. This involves a

pair of new daemons (nova-console and nova-consoleauth).

Nova interacts with all of the usual suspects: Keystone for authentication, Glance for

images and Horizon for web interface. The Glance interacts is interesting, though. The API

process can upload and query Glance while nova-compute will download images for use in

launching images.

Object Store

The swift architecture is very distributed to prevent any single point of failure as well as to

scale horizontally. It includes the following components:

• Proxy server accepts incoming requests via the OpenStack Object API or just raw HTTP.

It accepts files to upload, modifications to metadata or container creation. In addition, it

will also serve files or container listing to web browsers. The proxy server may utilize an

optional cache (usually deployed with memcache) to improve performance.

OpenStack Compute

Administration Manual

Sep 17, 2012 Essex (2012.1)

• Account servers manage accounts defined with the object storage service.

• Container servers manage a mapping of containers (i.e folders) within the object store

service.

• Object servers manage actual objects (i.e. files) on the storage nodes.

• There are also a number of periodic process which run to perform housekeeping tasks

on the large data store. The most important of these is the replication services, which

ensures consistency and availability through the cluster. Other periodic processes include

auditors, updaters and reapers.

Authentication is handled through configurable WSGI middleware (which will usually be

Keystone).

Image Store

The Glance architecture has stayed relatively stable since the Cactus release. The biggest

architectural change has been the addition of authentication, which was added in the

Diablo release. Just as a quick reminder, Glance has four main parts to it:

• glance-api accepts Image API calls for image discovery, image retrieval and image

storage

• glance-registry stores, processes and retrieves metadata about images (size, type,

etc.)

• A database to store the image metadata. Like Nova, you can choose your database

depending on your preference (but most people use MySQL or SQlite).

• A storage repository for the actual image files. In the diagram, I have shown the most

likely configuration (using Swift as the image repository), but this is configurable. In

addition to Swift, Glance supports normal filesystems, RADOS block devices, Amazon S3

and HTTP. Be aware that some of these choices are limited to read-only usage.

There are also a number of periodic process which run on Glance to support caching.

The most important of these is the replication services, which ensures consistency and

availability through the cluster. Other periodic processes include auditors, updaters and

reapers.

As you can see from the diagram, Glance serves a central role to the overall IaaS picture. It

accepts API requests for images (or image metadata) from end users or Nova components

and can store it's disk files in

Identity

Keystone provides a single point of integration for OpenStack policy, catalog, token and

authentication.

• Keystone handles API requests as well as providing configurable catalog, policy, token

and identity services.

OpenStack Compute

Administration Manual

Sep 17, 2012 Essex (2012.1)

• Each keystone function has a pluggable backend which allows different ways to use the

particular service. Most support standard backends like LDAP or SQL, as well as Key Value

Stores (KVS).

Most people will use this as a point of customization for their current authentication

services.

Future Projects

This completes the tour of the OpenStack Essex architecture. However, OpenStack will not

be stopping here - the following OpenStack release ("Folsom") will welcome another core

service to the fold:

• Network (Quantum) provides "network connectivity as a service" between interface

devices managed by other Openstack services (most likely Nova). The service works by

allowing users to create their own networks and then attach interfaces to them.

Although the release schedule for Folsom is not yet set (probably Fall 2012), I won't wait six

months to update the picture for this.

Why Cloud?

In data centers today, many computers suffer the same underutilization in computing

power and networking bandwidth. For example, projects may need a large amount

of computing capacity to complete a computation, but no longer need the computing

power after completing the computation. You want cloud computing when you want

a service that's available on-demand with the flexibility to bring it up or down through

automation or with little intervention. The phrase "cloud computing" is often represented

with a diagram that contains a cloud-like shape indicating a layer where responsibility

for service goes from user to provider. The cloud in these types of diagrams contains the

services that afford computing power harnessed to get work done. Much like the electrical

power we receive each day, cloud computing provides subscribers or users with access to

a shared collection of computing resources: networks for transfer, servers for storage, and

applications or services for completing tasks.

These are the compelling features of a cloud:

• On-demand self-service: Users can provision servers and networks with little human

intervention.

• Network access: Any computing capabilities are available over the network. Many

different devices are allowed access through standardized mechanisms.

• Resource pooling: Multiple users can access clouds that serve other consumers according

to demand.

• Elasticity: Provisioning is rapid and scales out or in based on need.

• Metered or measured service: Just like utilities that are paid for by the hour, clouds

should optimize resource use and control it for the level of service or type of servers such

as storage or processing.

Cloud computing offers different service models depending on the capabilities a consumer

may require.

OpenStack Compute

Administration Manual

Sep 17, 2012 Essex (2012.1)

• SaaS: Software as a Service. Provides the consumer the ability to use the software in a

cloud environment, such as web-based email for example.

• PaaS: Platform as a Service. Provides the consumer the ability to deploy applications

through a programming language or tools supported by the cloud platform provider. An

example of platform as a service is an Eclipse/Java programming platform provided with

no downloads required.

• IaaS: Infrastructure as a Service. Provides infrastructure such as computer instances,

network connections, and storage so that people can run any software or operating

system.

When you hear terms such as public cloud or private cloud, these refer to the deployment

model for the cloud. A private cloud operates for a single organization, but can be

managed on-premise or off-premise. A public cloud has an infrastructure that is available

to the general public or a large industry group and is likely owned by a cloud services

company. The NIST also defines community cloud as shared by several organizations

supporting a specific community with shared concerns.

Clouds can also be described as hybrid. A hybrid cloud can be a deployment model, as a

composition of both public and private clouds, or a hybrid model for cloud computing may

involve both virtual and physical servers.

What have people done with cloud computing? Cloud computing can help with large-

scale computing needs or can lead consolidation efforts by virtualizing servers to make

more use of existing hardware and potentially release old hardware from service. People

also use cloud computing for collaboration because of its high availability through

networked computers. Productivity suites for word processing, number crunching, and

email communications, and more are also available through cloud computing. Cloud

computing also avails additional storage to the cloud user, avoiding the need for additional

hard drives on each user's desktop and enabling access to huge data storage capacity

online in the cloud.

For a more detailed discussion of cloud computing's essential characteristics and its models

of service and deployment, see http://www.nist.gov/itl/cloud/, published by the US

National Institute of Standards and Technology.

剩余244页未读，继续阅读

qq_26636291

粉丝: 0
资源: 7

OpenStack Compute管理员指南：安装与管理

OpenStack Compute administration Manual

OpenStack Compute Administration Manual.zip

OpenStack Compute调研及安装

OpenStack Compute Administrator Guide 翻译

kitchen-openstack:用于测试厨房的OpenStack Compute驱动程序

OpenStack Compute 管理指南

OpenStack Compute组件详解：架构与功能

OpenStack Compute：虚拟化深度解析与安装指南

openstack compute service list

节点 移除_OpenStack Compute节点彻底移除

最新资源

节点移除_OpenStack Compute节点彻底移除