Re: [openstack-dev] [rally] "Failed to create the requested number of tenants" error

Nate, please try to make this simple check to make sure that everything is set up properly: 1) command "rally deployment check" should print an ascii-table with a list of services available 2) load rally auto-generated openrc file and run some OpenStack CLI command, for example: $ .

Re: [openstack-dev] [Rally] Term "workload" has two clashing meanings

in a main sport.) in sport. By that >> template - crossload is load in two or more areas in order to improve >> durability and performance, especially in a main area. >> Thanks, Roman. >> >> On Mon, Apr 11, 2016 at 6:38 PM, Aleksandr Maretskiy < >> amare

[openstack-dev] [Rally] Term "workload" has two clashing meanings

Hi all, this is about terminology, we have term "workload" in Rally that appears in two clashing meanings: 1. module rally.plugins.workload which collects plugins for cross-VM testing 2. workload replaces term "scenario"

Re: [openstack-dev] [Rally] single router per tenant in network context

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,

Re: [openstack-dev] [Openstack] Error while using Rally with Python

Hi try this: # It is important to have these lines first!!! from rally.common import db db.api.db_options.set_defaults(db.api.CONF, connection='sqlite:///path/to/your/rally.sqlite') # now run your code On Tue, Feb 2, 2016 at 12:47 PM, varun bhatnagar wrote: >

Re: [openstack-dev] [Rally] Failure running rally unit tests

Hi The problem is definitely in mock - some part of keystoneclient package is actually called (having a real api request) but it should be mocked instead. Unit test expects that keystoneclient.v2_0 is discovered, but we have something else instead. In latest rally version this unit test works

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

Hi all, as you know, Rally runs inside docker on Fuel master node, so docker removal (good improvement) is a problem for Rally users. To solve this, I'm planning to make native Rally installation on Fuel master node that is running on CentOS 7, and then make a step-by-step instruction how to

Re: [openstack-dev] [Fuel] Getting rid of Docker containers on the Fuel master node

On Mon, Nov 23, 2015 at 2:27 PM, Bogdan Dobrelya <bdobre...@mirantis.com> wrote: > On 23.11.2015 12:47, Aleksandr Maretskiy wrote: > > Hi all, > > > > as you know, Rally runs inside docker on Fuel master node, so docker > > removal (good improvement) is a problem

Re: [openstack-dev] [rally] Rally boot tests fails with Error Forbidden: It is not allowed to create an interface on external networks

Behzad, please run rally task start with `--debug' option and then provide us with some details (traceback, etc) about this error. Also Yair suggested to put `"auto_assign_nic": true' into scenario config - that is good idea. Get rid of `use_floatingip' - this parameter is not used for this

Re: [openstack-dev] [openstack-operators][Rally] Rally plugins reference is available

Cool! On Fri, Sep 25, 2015 at 3:05 AM, Boris Pavlovic wrote: > Hi stackers, > > As far as you know Rally test cases are created as a mix of plugins. > > At this point of time we have more than 200 plugins for almost all > OpenStack projects. > Before you had to analyze code

Re: [openstack-dev] [opentack-dev][meetings] Proposing changes in Rally meetings

Agreed with everything, but I think it would be a bit better if move one meeting from Monday to another day (Andrey K. is right) On Fri, Apr 17, 2015 at 5:35 PM, Andrey Kurilin akuri...@mirantis.com wrote: - We should start making agenda for each meeting and publish it to Rally wiki +1

Re: [openstack-dev] [docs][rally] Rally template tasks in a nutshell

Great improvement! Thanks! On Tue, Apr 7, 2015 at 1:17 PM, Mikhail Dubov mdu...@mirantis.com wrote: Hi stackers, as you might remember, we have recently added a nice feature to Rally which is the support of *task templates*. Rally uses the template syntax based on *Jinja2*, and thus makes

Re: [openstack-dev] [Openstack-operators] [all][qa][gabbi][rally][tempest] Extend rally verfiy to unify work with Gabbi, Tempest and all in-tree functional tests

The idea is great, but IMHO we can move all project-specific code out of rally, so: * rally plugin should be a part of project (for example, located in functional tests directory) * use {project url} instead of {project name} in rally verify command, example: $ rally verify

Re: [openstack-dev] [openstack-operators][Rally][HA-testing][multi-scenarios-load-gen] Proposal to change Rally input task format

Hi Patch set #3 looks good for me (but I have a proposal about `description' field). Thanks! On Fri, Feb 27, 2015 at 2:02 PM, Mikhail Dubov mdu...@mirantis.com wrote: Hi Boris, nice job! I like how this new task format looks like. I have commented your patch with a couple of suggestions to