Re: [openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

[Hugh Saunders]

Thanks for all your hard work on OSA Andy :)

On Thu, 30 Aug 2018 at 18:41 Andy McCrae  wrote:

> Now that Rocky is all but ready it seems like a good time! Since changing
> roles I've not been able to keep up enough focus on reviews and other
> obligations - so I think it's time to step aside as a core reviewer.
>
> I want to say thanks to everybody in the community, I'm really proud to
> see the work we've done and how the OSA team has grown. I've learned a
> tonne from all of you - it's definitely been a great experience.
>
> Thanks,
> Andy
> __
> 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

Re: [openstack-dev] [openstack-ansible] Stepping down from OpenStack-Ansible core

[Hugh Saunders]

All the best Major, thanks for all your work on OSA :)

On Mon, 26 Mar 2018 at 14:05 Major Hayden  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Hey there,
>
> As promised, I am stepping down from being an OpenStack-Ansible core
> reviewer since I am unable to meet the obligations of the role with my new
> job. :(
>
> Thanks to everyone who has mentored me along the way and put up with my
> gate job breakages. I have learned an incredible amount about OpenStack,
> Ansible, complex software deployments, and open source communities. I
> appreciate everyone's support as I worked through the creation of the
> ansible-hardening role as well as adding CentOS support for
> OpenStack-Ansible.
>
> - --
> Major Hayden
> -BEGIN PGP SIGNATURE-
>
> iQIzBAEBCAAdFiEEG/mSZJWWADNpjCUrc3BR4MEBH7EFAlq4774ACgkQc3BR4MEB
> H7E+gA/9HJEDibsQhdy191NbxbhF75wUup3gRDHhGPI6eFqHo/Iz8Q5Kv9Z9CXbo
> rkBGMebbGzoKwiLnKbFWr448azMJkj5/bTRLHb1eDQg2S2xaywP2L4e0CU+Gouto
> DucmGT6uLg+LKdQByYTB8VAHelub4DoxV2LhwsH+uYgWp6rZ2tB2nEIDTYQihhGx
> /WukfG+3zA99RZQjWRHmfnb6djB8sONzGIM8qY4qDUw9Xjp5xguHOU4+lzn4Fq6B
> cEpsJnztuEYnEpeTjynu4Dc8g+PX8y8fcObhcj+1D0NkZ1qW7sdX6CA64wuYOqec
> S552ej/fR5FPRKLHF3y8rbtNIlK5qfpNPE4UFKuVLjGSTSBz4Kp9cGn2jNCzyw5c
> aDQs/wQHIiUECzY+oqU1RHZJf9/Yq1VVw3vio+Dye1IMgkoaNpmX9lTcNw9wb1i7
> lac+fm0e438D+c+YZAttmHBCCaVWgKdGxH7BY84FoQaXRcaJ9y3ZoDEx6Rr8poBQ
> pK4YjUzVP9La2f/7S1QemX2ficisCbX+MVmAX9G4Yr9U2n98aXVWFMaF4As1H+OS
> zm9r9saoAZr6Z8BxjROjoClrg97RN1zkPseUDwMQwlJwF3V33ye3ib1dYWRr7BSm
> zAht+Jih/JE6Xtp+5UEF+6TBCYFVtXO8OHzCcac14w9dy1ur900=
> =fx64
> -END PGP SIGNATURE-
>
> __
> 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

Re: [openstack-dev] [openstack-ansible] Propose Marc Gariepy as core reviewer

[Hugh Saunders]

+1

On Fri, 3 Feb 2017 at 19:50 Steve Lewis  wrote:

> On Fri, Feb 3, 2017 at 5:33 AM, Jesse Pretorius <
> jesse.pretor...@rackspace.co.uk> wrote:
>
> I’d like to propose Marc Gariepy [1] as a core reviewer for
> OpenStack-Ansible.
>
>
> +1.
> --
> SteveL
> __
> 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

Re: [openstack-dev] [openstack-ansible] Nominating Jean-Philippe Evrard for core in openstack-ansible and all openstack-ansible-* roles

[Hugh Saunders]

+1 JP :)

On Tue, 12 Jul 2016 at 19:34 Truman, Travis 
wrote:

> Jean-Philippe has been providing great code reviews and patches for some
> time. His recent commitment to running bug triage every week shows his
> willingness to step up and take responsibilities within the community. He’s
> also found an opportunity to innovate by introducing an improved bug triage
> process. He can often be found in #openstack-ansible as *evrardjp *providing
> support to deployers in a welcoming and friendly manner.
>
> In short, just the kind of contribution our community desires from core
> reviewers.
>
> Thanks for all that you do for the community Jean-Philippe,
> Travis Truman
>
>
>
>
>
> __
> 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-dev] [defcore] Determine latest set of tests for a given release

[Hugh Saunders]

Hi All,
Whats the most reliable way to determine the latest set of required defcore
tests for a given release?

For example, I would currently use 2015.07/2015.07.required.txt but I don't
want to have to update that url each time there is a defcore release.

I could parse 20*.json in the root of the defcore repo, but that seems
brittle.

Thanks.

--
Hugh Saunders




-- 
--
Hugh Saunders
__
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] [defcore] Determine latest set of tests for a given release

[Hugh Saunders]

Hi Mark,
Thanks for your useful and timely response.

I did look at the refstack client, but it seems that it requires a test
list url as input, I was wondering how to programmatically get the
appropriate test list url. It sounds like there isn't a single url that
points to an index of defcore release json files, so I'd need to parse all
the .json files in the root of the repo, then find the latest file that has
status approved and the release I'm interested in.

Thanks again.

--
Hugh Saunders
-- 
--
Hugh Saunders
__
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] [os-ansible-deployment] Core team nomination

[Hugh Saunders]

+1

--
Hugh Saunders

On 13 June 2015 at 18:18, Kevin Carter kevin.car...@rackspace.com wrote:

 Hello,

 I would like to nominate Ian Cordasco (sigmavirus24 on IRC) for the
 os-ansible-deployment-core team. Ian has been contributing to the OSAD
 project for some time now and has always had quality reviews[0], he's
 landing great patches[1], he's almost always in the meetings, and is simply
 an amazing person to work with. His open source first attitude, security
 mindset, and willingness to work cross project is invaluable and will only
 stand to better the project and the deployers whom consume it.

 Please respond with +1/-1s and or any other concerns.

 As a reminder, we are using the voting process outlined at [
 https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess ] to
 add members to our core team.

 Thank you.

 --

 Kevin Carter

 [0]
 https://review.openstack.org/#/q/status:closed+owner:%22Ian+Cordasco%22+project:stackforge/os-ansible-deployment,n,z
 [1]
 https://review.openstack.org/#/q/status:merged+owner:%22Ian+Cordasco%22+project:stackforge/os-ansible-deployment,n,z

 __
 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

Re: [openstack-dev] [os-ansible-deployment] Nominating Nolan Brubaker for core team

[Hugh Saunders]

Great proposal, Nolan will be an asset to the core team.

+1

--
Hugh Saunders

On 25 March 2015 at 15:24, Kevin Carter kevin.car...@rackspace.com wrote:

 Greetings,

 I would like to nominate Nolan Brubaker (palendae on IRC) for the
 os-ansible-deployment-core team. Nolan has been involved with the project
 for the last few months and has been an active reviewer with solid reviews.
 IMHO, I think he is ready to receive core powers on the repository.

 References:
   [
 https://review.openstack.org/#/q/project:stackforge/os-ansible-deployment+reviewer:%22nolan+brubaker%253Cnolan.brubaker%2540rackspace.com%253E%22,n,z
 ]

 Please respond with +1/-1s or any other concerns.

 As a reminder, we are using the voting process outlined at [
 https://wiki.openstack.org/wiki/Governance/Approved/CoreDevProcess ] to
 add members to our core team.

 —

 Kevin Carter

 __
 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

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] Proposing Kun to Rally Core.

[Hugh Saunders]

+1
Kun has been very active on gerrit, and contributed good patches, so will
be a great addition to the core team.


--
Hugh Saunders


On 24 March 2014 07:31, Boris Pavlovic bpavlo...@mirantis.com wrote:

 Hi stackers,


 I would like to propose Kun Huang to Rally Core team.
 As you saw already, he is doing a lot of good reviews, and catch a lot of
 nits and bugs, so he will be a good core reviewer.

 Here is detailed statistics for the latest 30 days:
 http://stackalytics.com/report/contribution/rally/30

 Thoughts?


 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] Proposing changes in Rally core team

[Hugh Saunders]

Thanks Boris, Sergey, Oleg  Ilya,
Rally can be hard to keep up with (rebase, rebase, rebase, merge) but that
development pace also makes it exciting, each time you run rally, something
will have improved! This morning I was awed by Pierre's atomic actions
patches - great!

Thanks for appointing me as a core team member, I will keep an eye on
reviews and trello, see you all in IRC.

--
Hugh Saunders


On 5 February 2014 12:35, Boris Pavlovic bo...@pavlovic.me wrote:

 Hugh,

 welcome to Rally core team!


 Best regards,
 Boris Pavlovic



 On Wed, Feb 5, 2014 at 3:17 PM, Ilya Kharin ikha...@mirantis.com wrote:

 +1 for Hugh


 On Wed, Feb 5, 2014 at 2:22 PM, Sergey Skripnick sskripn...@mirantis.com
  wrote:


 +1 for Hugh, but IMO no need to rush with Alexei's removal

 Hi stackers,

 I would like to:

 1) Nominate Hugh Saunders to Rally core, he is doing a lot of good
 reviews (and always testing patches=) ):
 http://stackalytics.com/report/reviews/rally/30

 2) Remove Alexei from core team, because unfortunately he is not able to
 work on Rally at this moment. Thank you Alexei for all work that you have
 done.


 Thoughts?


 Best regards,
 Boris Pavlovic


 --
 Regards,
 Sergey Skripnick

 ___
 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



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

Re: [openstack-dev] [rally] Naming of a deployment

[Hugh Saunders]

On 15 January 2014 21:14, Ilya Kharin ikha...@mirantis.com wrote:

 Hi, guys,

 In Rally there is an entity that represents installed instance of
 OpenStack.
 What you think about a proper name for the entity? (a Deployment, a
 Cluster, an Installation, an Instance or something else)


I vote for Deployment.
Instance would be easily confused with a VM instance.
Cluster implies multiple nodes so doesn't cover the all-in-one/devstack
case.
Installation is very similar to deployment but deployment is already in use
throughout rally.

However I don't think it matters that much as long as the name is used
consistently.

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