Hi Yair,
The rally version I am using is 0.1.2
> rally --version
0.1.2
Also the task file is as shown below. Do you have an example of the
"network" context to skip creation on the interface on the xternal network?
vagrant@rally:~/rally$ more /vagrant/boot.json
{% set flavor_name = flavor_name or "m1.tiny" %}
{
"NovaServers.boot_server": [
{
"args": {
"flavor": {
"name": "{{flavor_name}}"
},
"image": {
"name": "cirros-0.3.1-x86_64"
},
"use_floatingip": false
},
"runner": {
"type": "constant",
"times": 10,
"concurrency": 2
},
"context": {
"users": {
"tenants": 3,
"users_per_tenant": 2
}
}
}
]
}
regards,
Behzad
Date: Tue, 20 Oct 2015 15:04:46 +0300
From: Yair Fried <yfr...@redhat.com>
To: "OpenStack Development Mailing List (not for usage questions)"
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [rally] Rally boot tests fails with Error
Forbidden: It is not allowed to create an interface on external
networks
Message-ID:
<CAPGkNL3Tf5fwUaAD-E4UonR_HxN=rejjeirq8m630049woa...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
On Tue, Oct 20, 2015 at 2:06 PM, Behzad Dastur <behzad.das...@gmail.com>
wrote:
> I have a contrail/OpenStack cloud deployed on which I am trying to run
> some rally benchmarks. But I am having trouble getting the rally boot
tests
> to run. It throws the "Error Forbidden: It is not allowed to create an
> interface on external network"
>
> It seems it is trying to create an interface on the external network,
> however in this case that operation is not required as the contrail plugin
> handles that.
>
What version of Rally are you using?
Could you please provide your task file? Looks like you are explicitly
telling rally to use your external network for the VMs.
> Is there a way to tell the rally scenario to avoid doing that. SImply
> put the operations that need to happen are:
>
> 1. nova boot (create private network/ or use private network provided)
>
The "network" context should allow you to dynamically create the networks.
Also, all scenarios that boot an instance can propagate boot arguments even
if they aren't explicitly listed (for more details try "$ rally plugin info
<Scenario>"), so you should be able to pass "{networks: {uuid: <netid>}}"
to the scenario.
2. neutron floating ip create, and assign it to the port eg (neutron
> floatingip-create --port-id <private assigned="" portid=""> <public net=""
> id="">)
>
Only in VMTask AFAIK.
> Here is the error log:
>
> 2015-10-20 00:24:12.759 19075 INFO
> rally.plugins.openstack.context.keystone.users
[-] Task 3000fcbd-2762-400d -920f-dfbfb667e7ec | Starting: Enter
context: `users`2015-10-20 00:24:14.711 19075 INFO
rally.plugins.openstack.context.keystone.users
[-] Task 3000fcbd-2762-400d-920f-dfbfb667e7ec | Completed: Enter context:
`users`2015-10-20 00:24:16.222 19264 INFO rally.task.runner [-] Task
3000fcbd-2762-400d-920f-dfbfb667e7ec | ITER: 0 START2015-10-20 00:24:16.227
19264 INFO rally.task.runner [-] Task 3000fcbd-2762-400d-920f-dfbfb667e7ec
| ITER: 1 START2015-10-20 00:24:18.420 19264 INFO rally.task.runner [-]
Task 3000fcbd-2762-400d-920f-dfbfb667e7ec | ITER: 0 END: Error Forbidden:
It is not allowed to create an interface on external network
2de28d39-34f9-48c5-bbac-609e258b7aad (HTTP 403) (Request-ID:
req-fe32bcf8-f624-4a2d-a083-7b6c5d1f24ab)
>
>
> regards,
> Behzad
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
