Re: [Openstack-operators] Problem setting up Rally with Keystone V3

st regards, Boris Pavlovic On Tue, Nov 28, 2017 at 6:25 AM, Aleksander Okonski < aleksander@gmail.com> wrote: > Hello, > > I am currently trying to set up Rally so that it will connect with an > OpenStack deployment. I am able to set up Rally with no problem (via the > i

Re: [Openstack-operators] [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing

ads in parallel (and generate more realistic load) -. So it would be really nice if you can share gaps that you faced that are blocking you to use directly Rally.. Thanks! Best regards, Boris Pavlovic On Tue, Oct 31, 2017 at 10:50 PM, Sam P wrote: > Hi All, > > Sending out a gen

Re: [Openstack-operators] regression testing before upgrade (operators view)

ssing? Best regards, Boris Pavlovic On Tue, Aug 29, 2017 at 2:24 AM, George Shuklin wrote: > Hello everyone. > > Does someone do regression testing before performing upgrade (within same > major version)? How do you do this? Do you know any tools for such tests? I > started to researc

Re: [Openstack-operators] [openstack-dev] [QA][LCOO] MEX-ops-meetup: OpenStack Extreme Testing

/implementation/hook_and_trigger_plugins.html Best regards, Boris Pavlovic On Mon, Aug 14, 2017 at 2:35 AM, Sam P wrote: > Hi All, > > This is a follow up for OpenStack Extreme Testing session[1] > we did in MEX-ops-meetup. > > Quick intro for those who were not there: > In t

Re: [Openstack-operators] [openstack-dev] [Performance][Proposal] Moving IRC meeting from 15:00 UTC to 16:00 UTC

+1 from me On Fri, Dec 4, 2015 at 8:16 AM, Joshua Harlow wrote: > +1 from me :) > > Dina Belova wrote: > >> Dear performance folks, >> >> There is a suggestion to move our meeting time from 15:00 UTC (Tuesdays >> ) to >> 16:00 U

Re: [Openstack-operators] [openstack-tc] [Performance] Where to place OpenStack performance documentation?

Dina, Is it possible just to get for performance team official status? However, for now we can use "rally" namespace if you would like. Like OSprofiler is for part of Rally for now... Best regards, Boris Pavlovic On Tue, Dec 1, 2015 at 4:57 AM, Dina Belova wrote: > Thierry,

Re: [Openstack-operators] Measuring how fast is my Cloud with OpenStack

Obed, Tim, Here is the chain of patches related to VM workloads that should cover second point: https://review.openstack.org/#/q/status:open+project:openstack/rally+branch:master+topic:bp/vm-workloads-framework,n,z Best regards, Boris Pavlovic On Tue, Nov 24, 2015 at 2:56 PM, Boris Pavlovic

Re: [Openstack-operators] Measuring how fast is my Cloud with OpenStack

Obed, Rally team is working on supporting point 2. We will allow you to run distributed loads in cloud like: IPerf, SPEC, HPCC and so on However we are moving very slowly, and for now you can use https://github.com/openstack/shaker Best regards, Boris Pavlovic On Tue, Nov 24, 2015 at 9:27

Re: [Openstack-operators] [openstack-dev][tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

Hi stackers, I updated OSprofiler spec: https://review.openstack.org/#/c/103825/ reviews are required. Best regards, Boris Pavlovic On Mon, Nov 9, 2015 at 2:57 AM, Boris Pavlovic wrote: > Hi stackers, > > Intro > --- > > It's not a big secret that OpenStack

Re: [Openstack-operators] [openstack-dev][tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

which requires actually 3 UUIDs. Putting 3 UUIDs in each log message seems to me very expensive and in case of logs not so useful. So I believe that we should keep those things separated from each other. At least for now. Best regards, Boris Pavlovic On Mon, Nov 9, 2015 at 8:37 AM, Joshua Harlow wrote

Re: [Openstack-operators] [openstack-dev] [tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

Gord, Something is definitely got there broken (after time that I didn't work on OSprofiler) and we should address that. Best regards, Boris Pavlovic On Mon, Nov 9, 2015 at 4:44 AM, gord chung wrote: > regarding ceilometer+oslo.messaging backend[1]. i feel like i should > menti

[Openstack-operators] [openstack-dev][tc][all][osprofiler] OSprofiler is dead, long live OSprofiler

he way somebody would like to join this effort?) Best regards, Boris Pavlovic ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

Re: [Openstack-operators] [Large Deployments Team][Tags] Ops Tag for "Scale"

aster/certification/openstack - Deployment Reference Architecture - Somebody should find enough resources to run at least for each release those tests on real hardware And create depending on this few scale tags: works-on-X-scale Best regards, Boris Pavlovic On Sat, Sep 26, 2015 at 5:19 PM, Boris Pav

[Openstack-operators] [openstack-dev][openstack-operators][Rally] Rally plugins reference is available

ch was the pain in neck. So finally we have auto generated plugin reference: https://rally.readthedocs.org/en/latest/plugin/plugin_reference.html Best regards, Boris Pavlovic ___ OpenStack-operators mailing list OpenStack-operators@lists.openstac

[Openstack-operators] [openstack-dev][openstack-operators][tc][tags] Rally tags

.openstack.org/#/c/225176/5 which will be the standard way to check whatever cloud is ready for production based on volume, performance & scale testing. Thoughts? Best regards, Boris Pavlovic ___ OpenStack-operators mailing list Open

Re: [Openstack-operators] [nova] Backlog Specs: a way to send requirements to the developer community

ces by hands". - "I would like to have restorable resources. Users that deleted by accident resources like VM, should be able to restore them during some fixed amount of time like 5 minutes." It's impossible hard task to create proper spec but it's super simple to provide s

Re: [Openstack-operators] [nova] Backlog Specs: a way to send requirements to the developer community

I would like to spend maximum 5 minutes to provide info about: - use case - problem description - possible solution [optional] What about making nova template simpler? And actually doing this across all projects? Best regards, Boris Pavlovic On Fri, May 15, 2015 at 11:46 AM, John Garbutt wro

Re: [Openstack-operators] [nova] Backlog Specs: a way to send requirements to the developer community

ere is the sample of feature request: https://rally.readthedocs.org/en/latest/feature_request/launch_specific_benchmark.html Best regards, Boris Pavlovic On Thu, May 14, 2015 at 9:03 PM, Boris Pavlovic wrote: > John, > > I believe that backlog should be different much simpler then specs.

[Openstack-operators] [openstack-dev][openstack-ops][rally][announce] What's new in Rally v0.0.3

/release_notes/v0.0.3.html Best regards, Boris Pavlovic ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack-dev][openstack-operators][rally] What's new in Rally v0.0.2

r as project is quite bugless and stable we don't need feature freeze at all, so I don't think that it will be hard to achieve this goal. Best regards, Boris Pavlovic ___ OpenStack-operators mailing list OpenStack-operators

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

st path-finder here: https://github.com/openstack/ceilometer/tree/master/ceilometer/tests/gabbi 3. What changes if any are needed in Gabbi to make this happen? More or less no changes. It can be run via testr/nose that is enough. Best regards, Boris Pavlovic On Mon, Mar 9, 2015 at 5:05 PM, Davanum

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

lugin (in most case it will be just functional test conf generation) 4) Reusing already existing code Most of the code that we need is already implemented in Rally, it requires just small refactoring and generalization. Thoughts? Best regards, Boris Pavlovic

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

nput task format.. Best regards, Boris Pavlovic ___ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

[Openstack-operators] [openstack-dev][openstack-operators][rally][docker] Rally docker images are available on Docker hub now!

the same as release tag 2) Master image - it is updated on every merge to Rally repo. By the way, there is a nice tutorial about how to use Rally in container: https://hub.docker.com/u/rallyforge/rally/ Best regards, Boris Pavlovic ___ OpenStack

Re: [Openstack-operators] Resources owned by a project/tenant are not cleaned up after that project is deleted from keystone

=nova.get_timestampt_of_last_cleanup, update_last_update_timestampt=nova.update_timestampt_of_last_cleanup, tenant_cleanup=nova.tenant_cleanup users_cleanup=nova.users_cleanup ) keystone_janitor.spawn() ​Best regards, Boris Pavlovic