Hi,

network context creates router for each network automatically, so you can
not reduce the number of routers with this context
https://github.com/openstack/rally/blob/master/rally/plugins/openstack/context/network/networks.py#L79

However you can create and use own network context plugin, inherited from
https://github.com/openstack/rally/blob/master/rally/plugins/openstack/context/network/networks.py#L31
and override its setup() method - create single router per tenant and then
attach it to each created network, like here
https://github.com/openstack/rally/blob/master/rally/plugins/openstack/wrappers/network.py#L342-L343

Ask me if you need more help


On Tue, Mar 15, 2016 at 7:58 PM, Akshay Kumar Sanghai <
akshaykumarsang...@gmail.com> wrote:

> Hi,
> I have a openstack setup with 1 controller node, 1 network node and 2
> compute nodes. I want to perform scale testing of the setup in the
> following manner:
>
> - Create 10 tenants
> - Create 1 router per tenant
> - Create 100 neutron networks across 10 tenants attached to the router
> - Create 500 VMs spread across 10 tenants attached to the networks
>
> I used the boot_server scenario and defined the number of networks and
> tenants in the network and users context respectively. But I want only one
> router to be created per tenant. In the current case, one router is created
> per network.
>
> Do i have an option to accomplish this using the existing rally code? Or
> should i go ahead and make some change in the network context for my use
> case?
>
> Thanks,
> Akshay
>
> __________________________________________________________________________
> 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
>
>
__________________________________________________________________________
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

Reply via email to