现在我在集会上使用openstack下放标记有问题。
我想对我的煤渣系统进行基准测试。然后我安装 openstack（Queens）/拉力赛（0.11.0），我已经测试过openstack并且拉力赛工作正常。
在这种情况下，我会尝试基准测试
{
"CinderVolumes.create_and_attach_volume": [
{
"args": {
"size": 10,
"image": {
"name": "cirros"
},
"flavor": {
"name": "m1.tiny"
},
"create_volume_params": {
"availability_zone": "nova"
}
},
"runner": {
"type": "constant",
"times": 5,
"concurrency": 1
},
"context": {
"users": {
"tenants": 2,
"users_per_tenant": 2
},
"api_versions": {
"cinder": {
"version": 2,
"service_type": "volumev2"
}
}
}
}
]
}
但是，在这种情况下。像这样的集会返回错误
任务配置无效：`输入任务无效！
子任务CinderVolumes.create_and_attach_volume [0]错误 配置子任务配置：{“版本”：2，“标题”：“ A 较大任务的裁剪版本。“，”说明“：”自动生成 来自单个工作负载的任务”，“子任务”：[{“标题”： “ CinderVolumes.create_and_attach_volume”，“描述”：“创建VM 并为其添加一个卷。”，“方案”： {“ CinderVolumes.create_and_attach_volume”：{“ size”：10，“ image”： {“ name”：“ cirros”}，“ flavor”：{“ name”：“ m1.tiny”}， “ create_volume_params”：{“ availability_zone”：“ nova”}}}，“上下文”： {“用户”：{“租户”：2，“用户_租户”：2}，“ api_versions”： {“ cinder”：{“ version”：2，“ service_type”：“ volumev2”}}}，“ runner”： {“ constant”：{“ times”：5，“ concurrency”：1}}，“ hooks”：[]，“ sla”： {“ failure_rate”：{“ max”：0}}}]}
原因：'cinder'服务不可用。提示：如果是“煤渣” 服务具有非默认service_type，请尝试通过设置 “ api_versions”上下文。
`
我该如何解决这个问题？我会给你更多的信息。
[root@controller ~]# rally deployment check
--------------------------------------------------------------------------------
Platform openstack:
--------------------------------------------------------------------------------
Available services:
+-------------+--------------+-----------+
| Service | Service Type | Status |
+-------------+--------------+-----------+
| __unknown__ | placement | Available |
| __unknown__ | volumev2 | Available |
| __unknown__ | volumev3 | Available |
| glance | image | Available |
| keystone | identity | Available |
| neutron | network | Available |
| nova | compute | Available |
+-------------+--------------+-----------+
[root@controller ~]# openstack catalog list
+-----------+-----------+------------------------------------------------------------------------+
| Name | Type | Endpoints |
+-----------+-----------+------------------------------------------------------------------------+
| keystone | identity | RegionOne |
| | | admin: http://controller:5000/v3/ |
| | | RegionOne |
| | | public: http://controller:5000/v3/ |
| | | RegionOne |
| | | internal: http://controller:5000/v3/ |
| | | |
| cinderv2 | volumev2 | RegionOne |
| | | internal: http://controller:8776/v2/7dd48a8542444579bcec3fe4b638069e |
| | | RegionOne |
| | | public: http://controller:8776/v2/7dd48a8542444579bcec3fe4b638069e |
| | | RegionOne |
| | | admin: http://controller:8776/v2/7dd48a8542444579bcec3fe4b638069e |
| | | |
| nova | compute | RegionOne |
| | | admin: http://controller:8774/v2.1 |
| | | RegionOne |
| | | public: http://controller:8774/v2.1 |
| | | RegionOne |
| | | internal: http://controller:8774/v2.1 |
| | | |
| cinderv3 | volumev3 | RegionOne |
| | | public: http://controller:8776/v3/7dd48a8542444579bcec3fe4b638069e |
| | | RegionOne |
| | | internal: http://controller:8776/v3/7dd48a8542444579bcec3fe4b638069e |
| | | RegionOne |
| | | admin: http://controller:8776/v3/7dd48a8542444579bcec3fe4b638069e |
| | | |
| glance | image | RegionOne |
| | | internal: http://controller:9292 |
| | | RegionOne |
| | | public: http://controller:9292 |
| | | RegionOne |
| | | admin: http://controller:9292 |
| | | |
| placement | placement | RegionOne |
| | | internal: http://controller:8778 |
| | | RegionOne |
| | | public: http://controller:8778 |
| | | RegionOne |
| | | admin: http://controller:8778 |
| | | |
| neutron | network | RegionOne |
| | | internal: http://controller:9696 |
| | | RegionOne |
| | | admin: http://controller:9696 |
| | | RegionOne |
| | | public: http://controller:9696 |
| | | |
+-----------+-----------+------------------------------------------------------------------------+
答案 0 :(得分：1)
我知道这有点晚了，但是对于将来的搜索请求...这不是有关Rally部署的完整信息，而是：
"api_versions": {
"cinder": {
"version": 2,
"service_type": "volumev2"
}
}
这部分和方案很好，但是您需要重新检查该api_versions部分。检查您作为rally deployment check输出的内容。然后以rally plugin show api_versions为例纠正您的情况。我也相信Cinder v2已弃用，无法正常工作。改用v3。
答案 1 :(得分：0)
有一个相应的集会bug