[openstack-dev] [puppet] PTL candidacy
Hey folks, I would like to nominate myself for the PTL role in the Puppet Openstack Team for the Pike release cycle. I served as the PTL during the Ocata cycle and would like to continue to serve for the Pike release cycle. As part of the Ocata cycle we have made some excellent progress around ensuring a consistent experience when using the modules. Additionally we have made continued progress around test coverage. For the Pike cycle, I believe we have a few places to continue to focus. - Ensuring the modules are updated for Pike changes. - Continuing to focus on CI integration both upstream and downstream. - Improving documentation around established patterns and best practices. - Working on the feedback loop between the puppet modules and upstream services. - Improving the deprecation cycle to ensure we are catching deprecations in the current cycle rather than after configurations have already been removed. I look forward to working with all of you. As always, I'm open to any suggestions or ideas for additional places to improve our processes and modules. Thanks, Alex Schultz irc: mwhahaha https://review.openstack.org/423514 __ 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] [puppet] PTL candidacy
I would like to nominate myself for the PTL role in the Puppet Openstack Team for the Ocata release cycle. I have been involved in the puppet team since Liberty as both a contributor and a downstream consumer. It has been a pleasure working with the community to improve and make the Puppet Openstack projects one of the most mature ways to deploy OpenStack. For the Ocata cycle, I believe we have a few places to continue to focus. - Continuing the work that Emilien has promoted, we need to continue to focus on CI integration both upstream and downstream. - We need to ensure that the new modules in the project continue to mature and are included in CI. - Improving documentation around established patterns and best practices. - Ensuring the modules are updated for Ocata changes. I look forward to working with all of you. I'm open to any suggestions or ideas for additional places to improve our processes and modules. Thanks, Alex Schultz irc: mwhahaha https://review.openstack.org/370279 __ 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] [puppet] PTL candidacy
On 03/13/2016 05:44 PM, Emilien Macchi wrote: This is my candidacy for PTL role in the Puppet OpenStack team for the Newton release cycle. https://review.openstack.org/#/c/292145/ Puppet OpenStack is a great example of project where collaboration works between developers and operators. Expect me to continue being a liaison between different groups so our community can successfully build production-ready OpenStack Clouds deployed with our modules. I'll continue to facilitate our team work, to coordinate cross-project tasks, to mentor our contributors who want to learn more and also the most important for me: keep being open. I had the tremendous pleasure [1] to lead our team during the last cycle and I would like to continue my role of PTL during Newton. Thank you for your consideration, [1] http://my1.fr/blog/puppet-openstack-mitaka-success -- Emilien Macchi __ 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 Make sure you also submit to the git repo: https://github.com/openstack/election __ 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] [puppet] PTL candidacy
This is my candidacy for PTL role in the Puppet OpenStack team for the Newton release cycle. https://review.openstack.org/#/c/292145/ Puppet OpenStack is a great example of project where collaboration works between developers and operators. Expect me to continue being a liaison between different groups so our community can successfully build production-ready OpenStack Clouds deployed with our modules. I'll continue to facilitate our team work, to coordinate cross-project tasks, to mentor our contributors who want to learn more and also the most important for me: keep being open. I had the tremendous pleasure [1] to lead our team during the last cycle and I would like to continue my role of PTL during Newton. Thank you for your consideration, [1] http://my1.fr/blog/puppet-openstack-mitaka-success -- Emilien Macchi __ 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] [puppet] PTL Candidacy
( Also posted on https://review.openstack.org/222767 ) Moving Puppet OpenStack modules under the big tent was an amazing opportunity for us to make sure our project remains Open [1]. Liberty was our first cycle where we were part of OpenStack and we can be proud of what we achieved together [2]. We've built a community coming from two different worlds: developers and operators. We need to keep that, because I think that's what is making the difference today when you're deploying OpenStack: you need a short loop feedback between both worlds. Being OpenStack is not easy, and we have great challenges in front of us. * Documentation I would like to put emphasis on having more documentation so we can more easily welcome new contributors and hopefuly get more adoption. I truly believe more documentation will help our contributors to get quickly involved and eventually give a chance to scale-up our team. Our users deserve more guidance to understand best practices when using our modules, that should also be part of this effort. * Continuous Integration We did a lot of work on CI, on both beaker & integration jobs. I would like to continue integration work and test more OpenStack modules. I would like to continue collaboration with Tempest team and keep using it for testing. I'm also interested by multi-node and upgrade testing, that would make stronger how we develop the modules. * Release management I would like to reach a better release velocity by trying to stay close to OpenStack releases (especially from packaging). As soon as major distributions release stable packaging, I think we should provide a release. * Community I would like to continue the collaboration with other projects, mostly OpenStack Infrastructure (for Continuous Integration work), TripleO, Fuel, Kolla (container integration), Documentation, Tempest (for puppet-openstack-integration work) and packagers (Ubuntu Cloud Archive and RDO teams). This collaboration is making OpenStack better and is the reason for our success today. We need to continue that way by coordinating groups and maintaining good communications. I had the immense pleasure to lead our team during the last few months and I would like to continue my role of PTL for the next cycle. Thank you for your time and consideration, [1] https://wiki.openstack.org/wiki/Open [2] http://my1.fr/blog/liberty-cycle-retrospective-in-puppet-openstack/ -- Emilien Macchi https://wiki.openstack.org/wiki/User:Emilienm signature.asc Description: OpenPGP digital 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
Re: [openstack-dev] [puppet] PTL Candidacy
Emilien Macchi wrote: As we want to move under the big tent, we decided in the last Puppet OpenStack meeting that we need a PTL for the next Cycle. I would like to announce my candidacy. Emilien, Though I've only been involved with the project for a short time, it is clear that you are an extremely qualified PTL candidate. FWIW, a +1 from me. Regards, Richard signature.asc Description: OpenPGP digital 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-dev] [puppet] PTL Candidacy
Hi, As we want to move under the big tent, we decided in the last Puppet OpenStack meeting that we need a PTL for the next Cycle. I would like to announce my candidacy. Qualifications -- I joined eNovance in 2012 and mainly worked in OpenStack deployments before I started working on OpenStack automation in 2013 for internal needs. Since the beginning, all my Puppet work has been upstream (Puppetlabs or Stackforge) and I strongly believe our community modules are the way to go for a production-ready OpenStack environment. My general knowledge in OpenStack and my background in deployments allow me to understand all components from high level so I can see how to deploy them with Puppet. Today, I'm leading Puppet OpenStack work at Red Hat and my team and I are working and focusing on upstream modules. Our involvement in Puppet OpenStack is because we are developing an open-source product which deploys OpenStack by using our modules, so each feature we need, is in Stackforge modules that can be leverage by the rest of the community. I'm also highly involved in Puppet integration for TripleO which is a great new opportunity to test different use-cases of deployments. Work in Puppet OpenStack * For more than one year, I've been a top contributor to the Puppet OpenStack modules: http://stackalytics.com/report/contribution/puppet-group/365 * I started puppet-ironic, puppet-heat, puppet-ceilometer (with Francois Charlier), puppet-tuskar, puppet-trove (with Sebastien Badia), puppet-gnocchi, puppet-tripleo modules. * I participate at meetings, help people on the mailing-list, contribute to discussions about our community, and regularly am a speaker at meetups and summits. Plans for Liberty - * CI I would like to continue the work done by nibalizer to have acceptance tests in our modules. I'm very interested in using TripleO jobs to gate our modules, I think it's a good use case, and everything is already in place. * Reviews Some patches would require some specific reviews, from OpenStack developers and operators. We'll find a way to document or automate the way we review these patches. I truly think our modules work because of the invaluable feedback we from both operators and also from OpenStack developers. * Release management As we move under the big tent, I would like to start following OpenStack release processes and emphasize bug triage. We will do our best to keep our launchpad updated so we can improve the way to we work together as a community. * Community I would like to ensure we organize regular meetings (IRC/video) with our community to provide support and to make bug triage as a team. We also will take care of welcoming newcomers and try to help them if they want to contribute. * My expectation of core-team As members of the core team, or those wanting to be, it's my hope that we: participate at our meetings, make good reviews, discuss on the mailing list regarding important topics, and help in fixing bugs. * Big tent This is a first for all of us, and I'll do my best to have Puppet OpenStack project involved in OpenStack's Big Tent. I accept this challenge and I strongly believe that, as a team, we can make it and succeed *without breaking our way to work together*. * Code Regarding our modules, we will continue our daily work on bugs/features/tests patches, but we should also continue the work on openstacklib to ensure everything is consistent across our modules. * Meetups/Summit As usual, we will ensure to have design sessions and an area where we can discuss together about Puppet OpenStack. I'll do my best to acquire all the resources we would need to effectively plan the upcoming cycle. Thank you for your time and consideration. Best regards, -- Emilien Macchi signature.asc Description: OpenPGP digital 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
