Rally：OpenStack性能测试工具详解与步骤

openstack

需积分: 49 54 浏览量更新于2023-03-16 3 收藏 1.65MB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

Rally是专为OpenStack设计的性能测试工具，版本为0.4.1dev5，由OpenStack基金会提供支持，于2016年5月17日发布。这个工具的主要目标是帮助评估OpenStack在大规模部署下的性能、验证和基准测试，以及进行压力测试，确保其在高负载环境下的稳定性和性能表现。Rally通过自动化和统一的方式，实现了多节点OpenStack的部署、云验证和各种场景的测试。 1. 概述： Rally的核心理念在于提供一个通用的平台，用户可以借此考察OpenStack在大规模环境中的实际运行情况，比如在上千台服务器的集群中如何处理复杂工作负载。它旨在作为OpenStack持续集成/持续交付（CI/CD）系统的基础工具，不断优化服务质量水平协议（SLA）、提升性能和增强稳定性。 2. 安装与配置：用户指南详细介绍了Rally的安装步骤，确保读者可以在不同的操作系统上顺利部署和配置Rally，以便开始使用其提供的功能。 3. 逐步操作指南：从这里开始，文档指导用户如何通过命令行界面（CLI）进行操作，包括设置环境、创建和执行测试场景、监控测试结果等，让新手也能快速上手。 4. 用户故事：这部分列出了Rally可以解决的各种典型问题和场景，例如测试API响应时间、负载均衡、数据库性能等，以帮助用户理解如何针对特定需求编写测试用例。 5. Rally插件：插件机制使得Rally具有高度可扩展性，用户可以自定义插件来添加新的测试场景或功能，满足个性化的性能测试需求。 6. Rally插件参考：提供了关于如何开发和使用插件的深入指南，包括API文档和示例，以帮助开发者充分利用Rally的功能。 7. 数据库升级/降级：文档还涉及数据库管理，包括如何处理Rally自身的数据库升级和降级操作，确保数据一致性及迁移过程中的顺畅。 8. 贡献Rally：对于对Rally有兴趣的开发者，这部分提供了关于如何参与到Rally项目的贡献指南，包括代码提交、bug报告和参与社区讨论。 9. Rally与OpenStack Gates：描述了Rally如何与OpenStack项目中的自动化测试框架集成，确保Rally测试的可靠性。 10. 请求新特性：文档最后提供了一个途径，让用户提出新特性的需求和改进意见，促进Rally的持续改进。 11. 项目信息：包括Rally的开源许可证、开发者联系信息以及项目网站等，为用户提供进一步的支持和资源链接。 12. 版本更新与发布说明：最后，文档会列出该版本的具体更改和新功能，以帮助用户了解他们所使用的Rally版本的最新进展。 Rally作为一个强大的OpenStack性能测试工具，为用户提供了一套全面且可扩展的测试解决方案，适用于不断追求性能优化和稳定性的OpenStack环境。

资源详情

资源推荐

Rally Documentation, Release 0.4.1 dev51

1.3 Rally step-by-step

In the following tutorial, we will guide you step-by-step through different use cases that might occur in Rally, starting

with the easy ones and moving towards more complicated cases.

1.3.1 Step 0. Installation

The easiest way to install Rally is by running its installation script:

wget -q -O- https://raw.githubusercontent.com/openstack/rally/master/install_rally.sh | bash

# or using curl:

curl https://raw.githubusercontent.com/openstack/rally/master/install_rally.sh | bash

If you execute the script as regular user, Rally will create a new virtual environment in ~/rally/ and install in it

Rally, and will use sqlite as database backend. If you execute the script as root, Rally will be installed system wide.

For more installation options, please refer to the installation page.

Note: Rally requires Python version 2.7 or 3.4.

Now that you have rally installed, you are ready to start benchmarking OpenStack with it!

1.3.2 Step 1. Setting up the environment and running a benchmark from samples

• Registering an OpenStack deployment in Rally

• Benchmarking

• Report generation

In this demo, we will show how to perform some basic operations in Rally, such as registering an OpenStack cloud,

benchmarking it and generating benchmark reports.

We assume that you have a Rally installation and an already existing OpenStack deployment with Keystone available

at <KEYSTONE_AUTH_URL>.

Registering an OpenStack deployment in Rally

First, you have to provide Rally with an OpenStack deployment it is going to benchmark. This should be done either

through OpenRC ﬁles or through deployment conﬁguration ﬁles. In case you already have an OpenRC, it is extremely

simple to register a deployment with the deployment create command:

$ . openrc admin admin

$ rally deployment create --fromenv --name=existing

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

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

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

Using deployment : <Deployment UUID>

...

Alternatively, you can put the information about your cloud credentials into a JSON conﬁguration ﬁle (let’s call it

existing.json). The deployment create command has a slightly different syntax in this case:

12 Chapter 1. Contents

Rally Documentation, Release 0.4.1 dev51

$ rally deployment create --file=existing.json --name=existing

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

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

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

Using deployment : <Deployment UUID>

...

Note the last line in the output. It says that the just created deployment is now used by Rally; that means that all the

benchmarking operations from now on are going to be performed on this deployment. Later we will show how to

switch between different deployments.

Finally, the deployment check command enables you to verify that your current deployment is healthy and ready to be

benchmarked:

$ rally deployment check

keystone endpoints are valid and following services are available:

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

| services | type | status |

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

| cinder | volume | Available |

| cinderv2 | volumev2 | Available |

| ec2 | ec2 | Available |

| glance | image | Available |

| heat | orchestration | Available |

| heat-cfn | cloudformation | Available |

| keystone | identity | Available |

| nova | compute | Available |

| novav21 | computev21 | Available |

| s3 | s3 | Available |

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

Benchmarking

Now that we have a working and registered deployment, we can start benchmarking it. The sequence of benchmarks

to be launched by Rally should be speciﬁed in a benchmark task conﬁguration ﬁle (either in JSON or in YAML format).

Let’s try one of the sample benchmark tasks available in samples/tasks/scenarios, say, the one that boots and deletes

multiple servers (samples/tasks/scenarios/nova/boot-and-delete.json):

{

"NovaServers.boot_and_delete_server": [

{

"args": {

"flavor": {

"name": "m1.tiny"

"image": {

"name": "^cirros.

uec$"

"force_delete": false

"runner": {

"type": "constant",

"times": 10,

"concurrency": 2

1.3. Rally step-by-step 13

Rally Documentation, Release 0.4.1 dev51

"context": {

"users": {

"tenants": 3,

"users_per_tenant": 2

}

]

}

To start a benchmark task, run the task start command (you can also add the -v option to print more logging informa-

tion):

$ rally task start samples/tasks/scenarios/nova/boot-and-delete.json

--------------------------------------------------------------------------------

Preparing input task

--------------------------------------------------------------------------------

Input task is:

--------------------------------------------------------------------------------

Task 6fd9a19f-5cf8-4f76-ab72-2e34bb1d4996: started

--------------------------------------------------------------------------------

Benchmarking... This can take a while...

To track task status use:

rally task status

rally task detailed

--------------------------------------------------------------------------------

Task 6fd9a19f-5cf8-4f76-ab72-2e34bb1d4996: finished

--------------------------------------------------------------------------------

test scenario NovaServers.boot_and_delete_server

args position 0

args values:

{u'args': {u'flavor': {u'name': u'm1.tiny'},

u'force_delete': False,

u'image': {u'name': u'^cirros.

uec$'}},

u'context': {u'users': {u'project_domain': u'default',

u'resource_management_workers': 30,

u'tenants': 3,

u'user_domain': u'default',

u'users_per_tenant': 2}},

u'runner': {u'concurrency': 2, u'times': 10, u'type': u'constant'}}

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

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

| nova.boot_server | 7.99 | 9.047 | 11.862 | 9.747 | 10.805 | 100.0% | 10 |

| nova.delete_server | 4.427 | 4.574 | 4.772 | 4.677 | 4.725 | 100.0% | 10 |

| total | 12.556 | 13.621 | 16.37 | 14.252 | 15.311 | 100.0% | 10 |

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

Load duration: 70.1310448647

Full duration: 87.545541048

14 Chapter 1. Contents

Rally Documentation, Release 0.4.1 dev51

HINTS:

To plot HTML graphics with this data, run:

rally task report 6fd9a19f-5cf8-4f76-ab72-2e34bb1d4996 --out output.html

To get raw JSON output of task results, run:

rally task results 6fd9a19f-5cf8-4f76-ab72-2e34bb1d4996

Using task: 6fd9a19f-5cf8-4f76-ab72-2e34bb1d4996

Note that the Rally input task above uses regular expressions to specify the image and ﬂavor name to be used for

server creation, since concrete names might differ from installation to installation. If this benchmark task fails, then

the reason for that might a non-existing image/ﬂavor speciﬁed in the task. To check what images/ﬂavors are available

in the deployment you are currently benchmarking, you might use the rally show command:

$ rally show images

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

| UUID | Name | Size (B) |

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

| 8dfd6098-0c26-4cb5-8e77-1ecb2db0b8ae | CentOS 6.5 (x86_64) | 344457216 |

| 2b8d119e-9461-48fc-885b-1477abe2edc5 | CirrOS 0.3.4 (x86_64) | 13287936 |

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

$ rally show flavors

Flavors for user `admin` in tenant `admin`:

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

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

| 1 | m1.tiny | 1 | 512 | | 1 |

| 2 | m1.small | 1 | 2048 | | 20 |

| 3 | m1.medium | 2 | 4096 | | 40 |

| 4 | m1.large | 4 | 8192 | | 80 |

| 5 | m1.xlarge | 8 | 16384 | | 160 |

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

Report generation

One of the most beautiful things in Rally is its task report generation mechanism. It enables you to create illustrative

and comprehensive HTML reports based on the benchmarking data. To create and open at once such a report for the

last task you have launched, call:

rally task report --out=report1.html --open

This will produce an HTML page with the overview of all the scenarios that you’ve included into the last benchmark

task completed in Rally (in our case, this is just one scenario, and we will cover the topic of multiple scenarios in one

task in the next step of our tutorial):

1.3. Rally step-by-step 15

剩余204页未读，继续阅读

nk9841

粉丝: 0
资源: 1

会员权益专享

Rally：OpenStack性能测试工具详解与步骤

性能测试工具CBench

通过 Rally 进行 OpenStack Tempest 测试.md

openstack rally2.1.0性能测试说明

openstack 性能测试 Rally

OpenStack自动化安装工具介绍

openstack平台测试结果分析

openSTack manual 整合调优

openstack提高vcpu性能

debug openStack

openstack zun组件使用

openstack怎么使用

openstack 主机数据采集

docker和openstack结合使用

openstack 一键部署

搭建openstack使用的开源软件

openstack 如何使用open vSwitch

openstack 基本使用

openstack和docker结合使用的例子

使用kolla-ansible 单节点部署OpenStack

云计算openstack基础运维

会员权益专享

最新资源