Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

2016-07-24 Thread Gary Kotton 
+1

On 7/22/16, 9:49 PM, "Brandon Logan"  wrote:

+1



On Fri, 2016-07-22 at 09:19 -0500, Darek Śmigiel wrote:

> I’m not a core, so treat this as +0 but I think Jakub will be good

> addition to core team.

> 

> 

> So +1

> 

> > On Jul 22, 2016, at 3:20 AM, Martin Hickey

> >  wrote:

> > 

> > +1

> > 

> > Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri, Jul

> > 22, 2016 at 2:36 AM, Doug Wiegley 

> > 

> > From: Oleg Bondarev 

> > To: "OpenStack Development Mailing List (not for usage questions)"

> > 

> > Date: 22/07/2016 09:13

> > Subject: Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for

> > testing core

> > 

> > 

> > 

> > 

> > 

> > 

> > 

> > +1

> > 

> > On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley

> >  wrote:

> > +1

> > On Jul 21, 2016, at 5:13 PM, Kevin Benton

> >  wrote:

> > 

> > +1

> > 

> > On Thu, Jul 21, 2016 at 2:41 PM, Carl

> > Baldwin  wrote:

> > +1 from me

> > 

> > On Thu, Jul 21, 2016 at 1:35 PM, Assaf

> > Muller  wrote:

> > As Neutron's so called testing

> > lieutenant I would like to propose

> > Jakub Libosvar to be a core in the

> > testing area.

> > 

> > Jakub has demonstrated his inherent

> > interest in the testing area over

> > the last few years, his reviews are

> > consistently insightful and his

> > numbers [1] are in line with others

> > and I know will improve if given

> > the responsibilities of a core

> > reviewer. Jakub is deeply involved

> > with

> > the project's testing

> > infrastructures and CI systems.

> > 

> > As a reminder the expectation from

> > cores is found here [2], and

> > specifically for cores interesting

> > in helping out shaping Neutron's

> > testing story:

> > 

> > * Guide community members to craft a

> > testing strategy for features [3]

> > * Ensure Neutron's testing

> > infrastructures are sufficiently

> > sophisticated to achieve the above.

> > * Provide leadership when

> > determining testing Do's & Don'ts

> > [4]. What

> > makes for an effective test?

> > * Ensure the gate stays consistently

> > green

> > 

> > And more tactically we're looking at

> > finishing the Tempest/Neutron

> > tests dedup [5] and to provide

> > visual graphing for historical

> > control

> > and data plane performance results

> > similar to [6].

> > 

> >

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

2016-07-22 Thread Bhatia, Manjeet S 
Ofcourse insightful reviewers will make development fast.

So ++

From: Darek Śmigiel [mailto:smigiel.dari...@gmail.com]
Sent: Friday, July 22, 2016 7:20 AM
To: OpenStack Development Mailing List (not for usage questions) 
<openstack-dev@lists.openstack.org>
Subject: Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

I’m not a core, so treat this as +0 but I think Jakub will be good addition to 
core team.

So +1

On Jul 22, 2016, at 3:20 AM, Martin Hickey 
<martin.hic...@ie.ibm.com<mailto:martin.hic...@ie.ibm.com>> wrote:

+1

Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri, Jul 22, 2016 at 
2:36 AM, Doug Wiegley 
<doug...@parksidesoftware.com<mailto:doug...@parksidesoftware.com>>

From: Oleg Bondarev <obonda...@mirantis.com<mailto:obonda...@mirantis.com>>
To: "OpenStack Development Mailing List (not for usage questions)" 
<openstack-dev@lists.openstack.org<mailto:openstack-dev@lists.openstack.org>>
Date: 22/07/2016 09:13
Subject: Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testing core




+1

On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley 
<doug...@parksidesoftware.com<mailto:doug...@parksidesoftware.com>> wrote:
+1
On Jul 21, 2016, at 5:13 PM, Kevin Benton 
<ke...@benton.pub<mailto:ke...@benton.pub>> wrote:

+1

On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin 
<c...@ecbaldwin.net<mailto:c...@ecbaldwin.net>> wrote:
+1 from me

On Thu, Jul 21, 2016 at 1:35 PM, Assaf Muller 
<as...@redhat.com<mailto:as...@redhat.com>> wrote:
As Neutron's so called testing lieutenant I would like to propose
Jakub Libosvar to be a core in the testing area.

Jakub has demonstrated his inherent interest in the testing area over
the last few years, his reviews are consistently insightful and his
numbers [1] are in line with others and I know will improve if given
the responsibilities of a core reviewer. Jakub is deeply involved with
the project's testing infrastructures and CI systems.

As a reminder the expectation from cores is found here [2], and
specifically for cores interesting in helping out shaping Neutron's
testing story:

* Guide community members to craft a testing strategy for features [3]
* Ensure Neutron's testing infrastructures are sufficiently
sophisticated to achieve the above.
* Provide leadership when determining testing Do's & Don'ts [4]. What
makes for an effective test?
* Ensure the gate stays consistently green

And more tactically we're looking at finishing the Tempest/Neutron
tests dedup [5] and to provide visual graphing for historical control
and data plane performance results similar to [6].

[1] http://stackalytics.com/report/contribution/neutron/90
[2] http://docs.openstack.org/developer/neutron/policies/neutron-teams.html
[3] 
http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron
[4] https://assafmuller.com/2015/05/17/testing-lightning-talk/
[5] https://etherpad.openstack.org/p/neutron-tempest-defork
[6] https://www.youtube.com/watch?v=a0qlsH1hoKs=youtu.be=24m22s

__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: 
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe<http://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://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<mailto: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://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<mailto:openstack-dev-requ...@lists.openstack.org>?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev


__
OpenStack Developme

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

2016-07-22 Thread Brandon Logan 
+1

On Fri, 2016-07-22 at 09:19 -0500, Darek Śmigiel wrote:
> I’m not a core, so treat this as +0 but I think Jakub will be good
> addition to core team.
> 
> 
> So +1
> 
> > On Jul 22, 2016, at 3:20 AM, Martin Hickey
> >  wrote:
> > 
> > +1
> > 
> > Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri, Jul
> > 22, 2016 at 2:36 AM, Doug Wiegley 
> > 
> > From: Oleg Bondarev 
> > To: "OpenStack Development Mailing List (not for usage questions)"
> > 
> > Date: 22/07/2016 09:13
> > Subject: Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for
> > testing core
> > 
> > 
> > 
> > 
> > 
> > 
> > 
> > +1
> > 
> > On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley
> >  wrote:
> > +1
> > On Jul 21, 2016, at 5:13 PM, Kevin Benton
> >  wrote:
> > 
> > +1
> > 
> > On Thu, Jul 21, 2016 at 2:41 PM, Carl
> > Baldwin  wrote:
> > +1 from me
> > 
> > On Thu, Jul 21, 2016 at 1:35 PM, Assaf
> > Muller  wrote:
> > As Neutron's so called testing
> > lieutenant I would like to propose
> > Jakub Libosvar to be a core in the
> > testing area.
> > 
> > Jakub has demonstrated his inherent
> > interest in the testing area over
> > the last few years, his reviews are
> > consistently insightful and his
> > numbers [1] are in line with others
> > and I know will improve if given
> > the responsibilities of a core
> > reviewer. Jakub is deeply involved
> > with
> > the project's testing
> > infrastructures and CI systems.
> > 
> > As a reminder the expectation from
> > cores is found here [2], and
> > specifically for cores interesting
> > in helping out shaping Neutron's
> > testing story:
> > 
> > * Guide community members to craft a
> > testing strategy for features [3]
> > * Ensure Neutron's testing
> > infrastructures are sufficiently
> > sophisticated to achieve the above.
> > * Provide leadership when
> > determining testing Do's & Don'ts
> > [4]. What
> > makes for an effective test?
> > * Ensure the gate stays consistently
> > green
> > 
> > And more tactically we're looking at
> > finishing the Tempest/Neutron
> > tests dedup [5] and to provide
> > visual graphing for historical
> > control
> > and data plane performance results
> > similar to [6].
> > 
> > [1]
> > 
> > http://stackalytics.com/report/contribution/neutron/90
> > [2]
> > 
> > http://docs.openstack.org/developer/neutron/policies/neutron-teams.html
> > [3]
> > 
> > http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron
> > [4]
> > 
> > https://assafmuller.com/2015/05/17/testing-lightning-talk/
> > [5]
> > 
> > https://etherpad.openstack.org/p/neutron-tempest-defork
> > [6]
> > 
> > https://www.youtube.com/watch?v=a0qlsH1hoKs=youtu.be=24m22s
> >

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

2016-07-22 Thread Darek Śmigiel 
I’m not a core, so treat this as +0 but I think Jakub will be good addition to 
core team.

So +1

> On Jul 22, 2016, at 3:20 AM, Martin Hickey  wrote:
> 
> +1
> 
> Oleg Bondarev ---22/07/2016 09:13:16---+1 On Fri, Jul 22, 2016 
> at 2:36 AM, Doug Wiegley 
> 
> From: Oleg Bondarev 
> To: "OpenStack Development Mailing List (not for usage questions)" 
> 
> Date: 22/07/2016 09:13
> Subject: Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testing 
> core
> 
> 
> 
> 
> +1
> 
> On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley  > wrote:
> +1
> On Jul 21, 2016, at 5:13 PM, Kevin Benton  > wrote:
> 
> +1
> 
> On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin  > wrote:
> +1 from me
> 
> On Thu, Jul 21, 2016 at 1:35 PM, Assaf Muller  > wrote:
> As Neutron's so called testing lieutenant I would like to propose
> Jakub Libosvar to be a core in the testing area.
> 
> Jakub has demonstrated his inherent interest in the testing area over
> the last few years, his reviews are consistently insightful and his
> numbers [1] are in line with others and I know will improve if given
> the responsibilities of a core reviewer. Jakub is deeply involved with
> the project's testing infrastructures and CI systems.
> 
> As a reminder the expectation from cores is found here [2], and
> specifically for cores interesting in helping out shaping Neutron's
> testing story:
> 
> * Guide community members to craft a testing strategy for features [3]
> * Ensure Neutron's testing infrastructures are sufficiently
> sophisticated to achieve the above.
> * Provide leadership when determining testing Do's & Don'ts [4]. What
> makes for an effective test?
> * Ensure the gate stays consistently green
> 
> And more tactically we're looking at finishing the Tempest/Neutron
> tests dedup [5] and to provide visual graphing for historical control
> and data plane performance results similar to [6].
> 
> [1] http://stackalytics.com/report/contribution/neutron/90 
> 
> [2] http://docs.openstack.org/developer/neutron/policies/neutron-teams.html 
> 
> [3] 
> http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron
>  
> 
> [4] https://assafmuller.com/2015/05/17/testing-lightning-talk/ 
> 
> [5] https://etherpad.openstack.org/p/neutron-tempest-defork 
> 
> [6] https://www.youtube.com/watch?v=a0qlsH1hoKs=youtu.be=24m22s 
> 
> 
> __
> 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 
> 
> 
> 
> __
> 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 
> 
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe:

Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for testingcore

2016-07-22 Thread Martin Hickey 

+1



From:   Oleg Bondarev 
To: "OpenStack Development Mailing List (not for usage questions)"

Date:   22/07/2016 09:13
Subject:Re: [openstack-dev] [Neutron] Proposing Jakub Libosvar for
testing core



+1

On Fri, Jul 22, 2016 at 2:36 AM, Doug Wiegley  wrote:
  +1

On Jul 21, 2016, at 5:13 PM, Kevin Benton  wrote:

+1

On Thu, Jul 21, 2016 at 2:41 PM, Carl Baldwin 
wrote:
 +1 from me

 On Thu, Jul 21, 2016 at 1:35 PM, Assaf Muller 
 wrote:
   As Neutron's so called testing lieutenant I would like to
   propose
   Jakub Libosvar to be a core in the testing area.

   Jakub has demonstrated his inherent interest in the testing area
   over
   the last few years, his reviews are consistently insightful and
   his
   numbers [1] are in line with others and I know will improve if
   given
   the responsibilities of a core reviewer. Jakub is deeply
   involved with
   the project's testing infrastructures and CI systems.

   As a reminder the expectation from cores is found here [2], and
   specifically for cores interesting in helping out shaping
   Neutron's
   testing story:

   * Guide community members to craft a testing strategy for
   features [3]
   * Ensure Neutron's testing infrastructures are sufficiently
   sophisticated to achieve the above.
   * Provide leadership when determining testing Do's & Don'ts [4].
   What
   makes for an effective test?
   * Ensure the gate stays consistently green

   And more tactically we're looking at finishing the
   Tempest/Neutron
   tests dedup [5] and to provide visual graphing for historical
   control
   and data plane performance results similar to [6].

   [1] http://stackalytics.com/report/contribution/neutron/90
   [2]
   
http://docs.openstack.org/developer/neutron/policies/neutron-teams.html

   [3]
   
http://docs.openstack.org/developer/neutron/devref/development.environment.html#testing-neutron

   [4] https://assafmuller.com/2015/05/17/testing-lightning-talk/
   [5] https://etherpad.openstack.org/p/neutron-tempest-defork
   [6]
   https://www.youtube.com/watch?v=a0qlsH1hoKs=youtu.be=24m22s


   
__

   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



__

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

__
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