[openstack-dev] [Rally] PTL candidacy

[Andrey Kurilin]

Hi stackers,

I'm happy to announce my candidacy for Rally PTL for the Ocata release
cycle.

Quick introduction of myself:
 - My contribution to OpenStack started > 2.5 years ago
 - My first commit to Rally was merged ~ 2,5 years ago
 - I became Rally core ~2.3 years ago

My goals for the Ocata cycle:

 - simplify review process of Rally plugins(more democracy!)
 - do regular 3 weeks releases
 - provide up-to-dated release schedule
 - finish validation refactoring to be more flexible
 - port rally verification component to plugin base to support different
verifiers
 - provide subunit output for Rally Task
 - continue work on Rally as a Service
 - make rally certification even more user-friendly and cover more use-cases
 - update docs to cover all aspects of Rally
 - finish work on new entity - hooks, which allow to execute something on
   specified points of scenario execution
 - port all plugins to support Keystone V3 and make V3 as default version
 - provide a way to deliver rally plugins as python packages
 - split Rally Core and OpenStack related plugins into 2 repos
 - nested atomics
 - trends reports for rally verification


-- 
Best regards,
Andrey Kurilin.
__
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-dev] [Rally] PTL candidacy

[Boris Pavlovic]

Hi stackers,

I'm announcing my candidacy for PTL for rally for the Newton release cycle.

My goals are the same:

- Work on road map to capture everybody's use cases and align them
- Continue working on improving our review process and CI
- Concentrate efforts on addressing tech debt
  (fixing bugs, cleaning up architecture and making it more testable)
- Make contribution to Rally even more open (make road map more open)
- Do the regular 1 per 2 weeks releases

Plans for the next releases:

- Finish work that addresses Rally scalability issues
  (only one task left storing chunks of results to DB)
- Finish distributed runner
  (we did all changes in framework except storing results in chunks, we
will need just to
   implement new runner plugin)
- Finish generalization of Rally
  (make Rally suitable for testing of everything, not only OpenStack)
- Split Rally Core & Rally OpenStack plugins into 2 repos
- Finish work on workload framework
  (create tests for network and disk testing)
- Improve Rally Certification Tasks
- Finish work on rally task v2 format
- Implement mutliscenario load
- Rally as a Service
- Rally task Trends and Compare reports
- Rally export results functionality (CLI and plugins for many systems)
- Disaster cleanup
  (be able to cleanup env no matter what happened)
-  many other interesting tasks


Best regards,
Boris Pavlovic
__
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

Re: [openstack-dev] [Rally] PTL candidacy

[Ramit Surana]

Hi Boris,

Thanks for sharing the insights on Rally.It is a really cool and innovative
project.Its efficiency and architecture is really good. I will be soon be
trying to contribute to this project.

Thanks.

On Wed, Sep 16, 2015 at 12:33 PM, Boris Pavlovic  wrote:

> Hi stackers,
>
> My name is Boris.
>
> Few years ago I started Rally to help OpenStack community to simplify
> performance/load/scale/volume testing of OpenStack and actually make it
> simple to answer on question: "How OpenStack perform (in ones very specific
> case)".
>
> Rally team did a terrific job to make from just a small initial 100 line
> script, project that you can see now.
>
> It covers most of the user cases, has plugins for most of the projects,
> high quality of code & docs, as well it's simple to install/use/integrate
> and it works quite stable.
>
> However we are in the middle of our path and there are plenty of places
> that should be improved:
>
> * New input task format - that address all current issues
>
> https://github.com/openstack/rally/blob/master/doc/specs/in-progress/new_rally_input_task_format.rst
>
> * Multi scenario load generation
>  That will allow us to do the monitoring with testing, HA testing
> under load and
>   load from many "different" types of workloads.
>
> * Scaling up Rally DB
>  This will allow users to run non stop  workloads for days or generte
> really huge
>  distributed load for a quite long amount of time
>
> * Distributed load generation
>  Generation of really huge load like 100k rps
>
> * Workloads framework
> Benchmarking that measures performance of Servers, VMs, Network and
> Volumes
>
> * ...infinity list from here:
> https://docs.google.com/spreadsheets/u/1/d/16DXpfbqvlzMFaqaXAcJsBzzpowb_XpymaK2aFY2gA2g/edit#gid=0
>
>
> In other words I would like to continue to work as PTL of Rally until we
> get all this done.
>
>
> Best regards,
> Boris Pavlovic
>
> __
> 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
>
>


-- 
Regards,
Ramit Surana
skype : ramitsurana
LinkedIn : /in/ramitsurana
__
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-dev] [Rally] PTL candidacy

[Boris Pavlovic]

Hi stackers,

My name is Boris.

Few years ago I started Rally to help OpenStack community to simplify
performance/load/scale/volume testing of OpenStack and actually make it
simple to answer on question: "How OpenStack perform (in ones very specific
case)".

Rally team did a terrific job to make from just a small initial 100 line
script, project that you can see now.

It covers most of the user cases, has plugins for most of the projects,
high quality of code & docs, as well it's simple to install/use/integrate
and it works quite stable.

However we are in the middle of our path and there are plenty of places
that should be improved:

* New input task format - that address all current issues

https://github.com/openstack/rally/blob/master/doc/specs/in-progress/new_rally_input_task_format.rst

* Multi scenario load generation
 That will allow us to do the monitoring with testing, HA testing under
load and
  load from many "different" types of workloads.

* Scaling up Rally DB
 This will allow users to run non stop  workloads for days or generte
really huge
 distributed load for a quite long amount of time

* Distributed load generation
 Generation of really huge load like 100k rps

* Workloads framework
Benchmarking that measures performance of Servers, VMs, Network and
Volumes

* ...infinity list from here:
https://docs.google.com/spreadsheets/u/1/d/16DXpfbqvlzMFaqaXAcJsBzzpowb_XpymaK2aFY2gA2g/edit#gid=0


In other words I would like to continue to work as PTL of Rally until we
get all this done.


Best regards,
Boris Pavlovic
__
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

Re: [openstack-dev] [Rally] PTL candidacy

[Elizabeth K. Joseph]

On Wed, Apr 8, 2015 at 8:02 AM, Boris Pavlovic bpavlo...@mirantis.com wrote:
 Hi,

 As far as https://review.openstack.org/#/c/169357/ Rally is part of
 OpenStack, I would like to announce my candidacy for Rally  / Benchmark as a
 Services.

Tristan has informed me that we've confirmed with Thierry that
recently-added projects Rally and Security won't run elections this
time around and will keep their current PTLs.

-- 
Elizabeth Krumbach Joseph || Lyz || pleia2

__
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-dev] [Rally] PTL candidacy

[Boris Pavlovic]

Hi,

As far as https://review.openstack.org/#/c/169357/ Rally is part of
OpenStack, I would like to announce my candidacy for Rally  / Benchmark as
a Services.


I started this project in 2013 and for almost two years together we made
nice project and build even nicer project's community.

I would like to hold the position of PTL and improve Rally quality and
cover all use cases:
https://docs.google.com/a/mirantis.com/spreadsheets/d/16DXpfbqvlzMFaqaXAcJsBzzpowb_XpymaK2aFY2gA2g/edit#gid=0


Best regards,
Boris Pavlovic
__
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

Re: [openstack-dev] [Rally] PTL Candidacy

[Hugh Saunders]

+1 Boris has the enthusiasm, and time to take Rally forwards. He is
especially good at encouraging people to get involved.

Ensure that everybody's use cases are fully covered - this must be
balanced against the need for focus and clear scope.

--
Hugh Saunders


On 21 July 2014 19:38, Boris Pavlovic bpavlo...@mirantis.com wrote:

 Hi,

 I would like to propose my candidacy for Rally PTL.

 I started this project to make benchmarking of OpenStack simple as
 possible. This means not only load generation, but as well OpenStack
 specific benchmark framework, data analyze and integration with gates. All
 these things should make it simple for developers and operators to
 benchmark (perf, scale, stress test) OpenStack, share experiments 
 results, and have a fast way to find what produce bottleneck or just to
 ensure that OpenStack works well under load that they are expecting.

 I am current non official PTL and in my responsibilities are such things
 like:
 1) Adoption of Rally architecture to cover everybody's use cases
 2) Building  managing work of community
 3) Writing a lot of code
 4) Working on docs  wiki
 5) Helping newbies to join Rally team

 As a PTL I would like to continue work and finish my initial goal:
 1) Ensure that everybody's use cases are fully covered
 2) There is no monopoly in project
 3) Run Rally in gates of all OpenStack projects (currently we have check
 jobs in Keystone, Cinder, Glance  Neutron)
 4) Continue work on making project more mature. It covers such topics like
 increasing unit and functional test coverage and making Rally absolutely
 safe to run against any production cloud)


 Best regards,
 Boris Pavlovic

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Rally] PTL Candidacy

[Sergey Lukjanov]

ack

On Mon, Jul 21, 2014 at 10:38 PM, Boris Pavlovic bpavlo...@mirantis.com wrote:
 Hi,

 I would like to propose my candidacy for Rally PTL.

 I started this project to make benchmarking of OpenStack simple as possible.
 This means not only load generation, but as well OpenStack specific
 benchmark framework, data analyze and integration with gates. All these
 things should make it simple for developers and operators to benchmark
 (perf, scale, stress test) OpenStack, share experiments  results, and have
 a fast way to find what produce bottleneck or just to ensure that OpenStack
 works well under load that they are expecting.

 I am current non official PTL and in my responsibilities are such things
 like:
 1) Adoption of Rally architecture to cover everybody's use cases
 2) Building  managing work of community
 3) Writing a lot of code
 4) Working on docs  wiki
 5) Helping newbies to join Rally team

 As a PTL I would like to continue work and finish my initial goal:
 1) Ensure that everybody's use cases are fully covered
 2) There is no monopoly in project
 3) Run Rally in gates of all OpenStack projects (currently we have check
 jobs in Keystone, Cinder, Glance  Neutron)
 4) Continue work on making project more mature. It covers such topics like
 increasing unit and functional test coverage and making Rally absolutely
 safe to run against any production cloud)


 Best regards,
 Boris Pavlovic

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data Processing)
Principal Software Engineer
Mirantis Inc.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Rally] PTL Candidacy

[Sergey Lukjanov]

Folks, please, don't +1 it. If we'll have = 2 candidates, we'll have
CIVS elections.

On Tue, Jul 22, 2014 at 2:09 PM, Hugh Saunders h...@wherenow.org wrote:
 +1 Boris has the enthusiasm, and time to take Rally forwards. He is
 especially good at encouraging people to get involved.

 Ensure that everybody's use cases are fully covered - this must be
 balanced against the need for focus and clear scope.

 --
 Hugh Saunders


 On 21 July 2014 19:38, Boris Pavlovic bpavlo...@mirantis.com wrote:

 Hi,

 I would like to propose my candidacy for Rally PTL.

 I started this project to make benchmarking of OpenStack simple as
 possible. This means not only load generation, but as well OpenStack
 specific benchmark framework, data analyze and integration with gates. All
 these things should make it simple for developers and operators to benchmark
 (perf, scale, stress test) OpenStack, share experiments  results, and have
 a fast way to find what produce bottleneck or just to ensure that OpenStack
 works well under load that they are expecting.

 I am current non official PTL and in my responsibilities are such things
 like:
 1) Adoption of Rally architecture to cover everybody's use cases
 2) Building  managing work of community
 3) Writing a lot of code
 4) Working on docs  wiki
 5) Helping newbies to join Rally team

 As a PTL I would like to continue work and finish my initial goal:
 1) Ensure that everybody's use cases are fully covered
 2) There is no monopoly in project
 3) Run Rally in gates of all OpenStack projects (currently we have check
 jobs in Keystone, Cinder, Glance  Neutron)
 4) Continue work on making project more mature. It covers such topics like
 increasing unit and functional test coverage and making Rally absolutely
 safe to run against any production cloud)


 Best regards,
 Boris Pavlovic

 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev



 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev




-- 
Sincerely yours,
Sergey Lukjanov
Sahara Technical Lead
(OpenStack Data Processing)
Principal Software Engineer
Mirantis Inc.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Rally] PTL Candidacy

[Marco Morais]

Since Rally is the first OpenStack project that I contributed to, I can 
personally vouch for Boris' magical abilities to welcome new contributors and 
set the technical direction for the project.  If you spend some time in the 
#openstack-rally irc you quickly realize that boris-42 is available across 
multiple timezones to answer questions, delegate bugs and features, and provide 
a vision for what Rally should be.
--
Regards,
Marco

From: Boris Pavlovic bpavlo...@mirantis.commailto:bpavlo...@mirantis.com
Reply-To: OpenStack Development Mailing List (not for usage questions) 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Date: Monday, July 21, 2014 at 11:38 AM
To: OpenStack Development Mailing List 
openstack-dev@lists.openstack.orgmailto:openstack-dev@lists.openstack.org
Subject: [openstack-dev] [Rally] PTL Candidacy

Hi,

I would like to propose my candidacy for Rally PTL.

I started this project to make benchmarking of OpenStack simple as possible. 
This means not only load generation, but as well OpenStack specific benchmark 
framework, data analyze and integration with gates. All these things should 
make it simple for developers and operators to benchmark (perf, scale, stress 
test) OpenStack, share experiments  results, and have a fast way to find what 
produce bottleneck or just to ensure that OpenStack works well under load that 
they are expecting.

I am current non official PTL and in my responsibilities are such things like:
1) Adoption of Rally architecture to cover everybody's use cases
2) Building  managing work of community
3) Writing a lot of code
4) Working on docs  wiki
5) Helping newbies to join Rally team

As a PTL I would like to continue work and finish my initial goal:
1) Ensure that everybody's use cases are fully covered
2) There is no monopoly in project
3) Run Rally in gates of all OpenStack projects (currently we have check jobs 
in Keystone, Cinder, Glance  Neutron)
4) Continue work on making project more mature. It covers such topics like 
increasing unit and functional test coverage and making Rally absolutely safe 
to run against any production cloud)


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

[openstack-dev] [Rally] PTL Candidacy

[Boris Pavlovic]

Hi,

I would like to propose my candidacy for Rally PTL.

I started this project to make benchmarking of OpenStack simple as
possible. This means not only load generation, but as well OpenStack
specific benchmark framework, data analyze and integration with gates. All
these things should make it simple for developers and operators to
benchmark (perf, scale, stress test) OpenStack, share experiments 
results, and have a fast way to find what produce bottleneck or just to
ensure that OpenStack works well under load that they are expecting.

I am current non official PTL and in my responsibilities are such things
like:
1) Adoption of Rally architecture to cover everybody's use cases
2) Building  managing work of community
3) Writing a lot of code
4) Working on docs  wiki
5) Helping newbies to join Rally team

As a PTL I would like to continue work and finish my initial goal:
1) Ensure that everybody's use cases are fully covered
2) There is no monopoly in project
3) Run Rally in gates of all OpenStack projects (currently we have check
jobs in Keystone, Cinder, Glance  Neutron)
4) Continue work on making project more mature. It covers such topics like
increasing unit and functional test coverage and making Rally absolutely
safe to run against any production cloud)


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

Re: [openstack-dev] [Rally] PTL Candidacy

[Yingjun Li]

+1

On Jul 22, 2014, at 2:38, Boris Pavlovic bpavlo...@mirantis.com wrote:

 Hi, 
 
 I would like to propose my candidacy for Rally PTL.
 
 I started this project to make benchmarking of OpenStack simple as possible. 
 This means not only load generation, but as well OpenStack specific benchmark 
 framework, data analyze and integration with gates. All these things should 
 make it simple for developers and operators to benchmark (perf, scale, stress 
 test) OpenStack, share experiments  results, and have a fast way to find 
 what produce bottleneck or just to ensure that OpenStack works well under 
 load that they are expecting. 
 
 I am current non official PTL and in my responsibilities are such things like:
 1) Adoption of Rally architecture to cover everybody's use cases
 2) Building  managing work of community
 3) Writing a lot of code
 4) Working on docs  wiki 
 5) Helping newbies to join Rally team 
 
 As a PTL I would like to continue work and finish my initial goal:
 1) Ensure that everybody's use cases are fully covered
 2) There is no monopoly in project
 3) Run Rally in gates of all OpenStack projects (currently we have check jobs 
 in Keystone, Cinder, Glance  Neutron)
 4) Continue work on making project more mature. It covers such topics like 
 increasing unit and functional test coverage and making Rally absolutely safe 
 to run against any production cloud)
 
 
 Best regards,
 Boris Pavlovic
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Rally] PTL Candidacy

[Duncan Thomas]

On 21 July 2014 21:38, Boris Pavlovic bpavlo...@mirantis.com wrote:
 Hi,

 I would like to propose my candidacy for Rally PTL.

I've been working  with Boris on both Rally and the associated
OSProfiler code, and I can confirm he is dedicated, very open to ideas
and contributions, and I heartily recommend him for PTL.

___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

Re: [openstack-dev] [Rally] PTL Candidacy

[Joshua Harlow]

+1

I've been helping out with the osprofiler code (and tiny parts of rally) and 
boris would be a welcome PTL imho.

-Josh

On Jul 21, 2014, at 11:38 AM, Boris Pavlovic bpavlo...@mirantis.com wrote:

 Hi, 
 
 I would like to propose my candidacy for Rally PTL.
 
 I started this project to make benchmarking of OpenStack simple as possible. 
 This means not only load generation, but as well OpenStack specific benchmark 
 framework, data analyze and integration with gates. All these things should 
 make it simple for developers and operators to benchmark (perf, scale, stress 
 test) OpenStack, share experiments  results, and have a fast way to find 
 what produce bottleneck or just to ensure that OpenStack works well under 
 load that they are expecting. 
 
 I am current non official PTL and in my responsibilities are such things like:
 1) Adoption of Rally architecture to cover everybody's use cases
 2) Building  managing work of community
 3) Writing a lot of code
 4) Working on docs  wiki 
 5) Helping newbies to join Rally team 
 
 As a PTL I would like to continue work and finish my initial goal:
 1) Ensure that everybody's use cases are fully covered
 2) There is no monopoly in project
 3) Run Rally in gates of all OpenStack projects (currently we have check jobs 
 in Keystone, Cinder, Glance  Neutron)
 4) Continue work on making project more mature. It covers such topics like 
 increasing unit and functional test coverage and making Rally absolutely safe 
 to run against any production cloud)
 
 
 Best regards,
 Boris Pavlovic
 ___
 OpenStack-dev mailing list
 OpenStack-dev@lists.openstack.org
 http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev