[openstack-dev] [Heat] PTL Candidacy
Hi everyone, I'm happy to announce my candidacy for PTL of Heat for the Newton cycle. The project and the community are in a good place in my opinion currently, both diverse and active. As much as possible I'd like to continue encourage and improve that. Heat is being used more and more by projects inside OpenStack. As we know first hand, being broken by other projects is not a great experience, so I want to make sure we don't do this. I believe it goes by being proactive (taking care of compatibility, making sure gates are not broken before merging) and reactive (handle issues promptly, not being afraid of reverts). On the other hand, I also want to reach application deployment outside of OpenStack itself, with a focus on documentation, and improving our heat-templates repository. I don't believe we should work much on particular features outside of continuing our resource coverage. Pushing convergence, and working on scalability and performance sounds like what we should aim for in the near future. All of that said, being PTL is also a lot about release coordination, which I hope to learn with the help of our successful lineage of PTLs. Thanks! -- Thomas __ 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] [Heat] PTL candidacy
Dear all, I am announcing my candidacy for PTL role in heat for Newton release. I started to work in heat from Juno release and got opportunities to work on various features in Heat services and it's echo-system like CI, documentation. It helped me to get confident with heat service and community. Based on this, I would like to announce my candidacy and will assure to continue the team success formula "consensus building". My goal is to increase the existing user and developer experiences in heat to the next height, by working with us on following aspects in Newton release: Features: * Work with Product WG to understand their road-map and bring the required features in heat. It helps to align with big-tent's over-all road-map. * Complete the Convergence initiative and bring greater value out-of it. It helps for greater scalability. * Heat is being consumed in OpenStack by TripleO, Tacker, Magnum, Murano, etc. Provide best support to these project communities for their needs in heat project. It helps to expand the foot-print of heat and enhance these services. * Implement existing and new blue-prints. It helps to strengthen heat's muscular power. * Implement hot-parser in similar line with XML parser, YAML parser, etc. It helps those open-source and closed-source solutions use the HOT template. (Once python flavor is established, other language such as java-script could be aimed.) * Over the releases, heat-templates git repo is grown up with many templates and some of them might be absolute as well. Investigate templates in this repo and make them organized based on heat features, use-cases, etc. Also make sure all are *valid* templates. It helps to make it better manageable and usable. CI: == * Continue the test-case improvements and identify the gaps/improvements in build jobs and test automations and fix them. It helps to reduce the turn-around time of authors and improves the existing heat quality further. Documentations: === * Make Orchestration api-refs, developer and user guides to be in sync with heat master code base. It helps to easy/enhance the heat user's life. Thanks for your considerations, Kanagaraj Manickam IRC: KanagarajM Launchpad: kanagaraj-manickam __ 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] [Heat] PTL Candidacy
+1 I am very happy to work with you:) At 2015-04-07 10:50:23, Steve Baker sba...@redhat.com wrote: I'd like to announce my candidacy for the Heat PTL in Liberty. As I was the PTL during Icehouse, this will be Heat's first rerun PTL under our convention for rotating leaders. Even if elected I would hope that we continue to find Heat PTL new-blood for future cycles. Towards the end of the Kilo cycle we started to get some momentum on landing the changes required for the Convergence effort. The aim will be to get much of the first-phase features landing early in Liberty, and spend the rest of the cycle focusing on convergence features which provide the most user benefit. There are important maintenance tasks in the Liberty cycle which will need continued effort, including functional/integration testing, content for the template-writer's guide, and general usability improvements. It seems that our merge throughput would be higher if our existing review attention were more coordinated. Nova has had some success with priorities, and Swift works well with a PTL curated etherpad of suggested reviews. I'd like to discuss the options with other heat cores, and am currently suggesting something like the Swift approach. As the Big Tent process continues to mature I'd like to ensure that Heat is well positioned to qualify for the appropriate tags as they are defined. Also it would be worth looking into whether there should be heat-related tags available for projects with sufficiently mature resource implementations. I'll be continuing Heat's tradition of the leadership emerging from a shared consensus, leaving the PTL as a point of coordination within the project, and a point of communication to the greater ecosystem. I look forward to the opportunity to do this! Steve __ 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] [Heat] PTL Candidacy
confirmed On 04/06/2015 10:50 PM, Steve Baker wrote: I'd like to announce my candidacy for the Heat PTL in Liberty. As I was the PTL during Icehouse, this will be Heat's first rerun PTL under our convention for rotating leaders. Even if elected I would hope that we continue to find Heat PTL new-blood for future cycles. Towards the end of the Kilo cycle we started to get some momentum on landing the changes required for the Convergence effort. The aim will be to get much of the first-phase features landing early in Liberty, and spend the rest of the cycle focusing on convergence features which provide the most user benefit. There are important maintenance tasks in the Liberty cycle which will need continued effort, including functional/integration testing, content for the template-writer's guide, and general usability improvements. It seems that our merge throughput would be higher if our existing review attention were more coordinated. Nova has had some success with priorities, and Swift works well with a PTL curated etherpad of suggested reviews. I'd like to discuss the options with other heat cores, and am currently suggesting something like the Swift approach. As the Big Tent process continues to mature I'd like to ensure that Heat is well positioned to qualify for the appropriate tags as they are defined. Also it would be worth looking into whether there should be heat-related tags available for projects with sufficiently mature resource implementations. I'll be continuing Heat's tradition of the leadership emerging from a shared consensus, leaving the PTL as a point of coordination within the project, and a point of communication to the greater ecosystem. I look forward to the opportunity to do this! Steve __ 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 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] [Heat] PTL Candidacy
I'd like to announce my candidacy for the Heat PTL in Liberty. As I was the PTL during Icehouse, this will be Heat's first rerun PTL under our convention for rotating leaders. Even if elected I would hope that we continue to find Heat PTL new-blood for future cycles. Towards the end of the Kilo cycle we started to get some momentum on landing the changes required for the Convergence effort. The aim will be to get much of the first-phase features landing early in Liberty, and spend the rest of the cycle focusing on convergence features which provide the most user benefit. There are important maintenance tasks in the Liberty cycle which will need continued effort, including functional/integration testing, content for the template-writer's guide, and general usability improvements. It seems that our merge throughput would be higher if our existing review attention were more coordinated. Nova has had some success with priorities, and Swift works well with a PTL curated etherpad of suggested reviews. I'd like to discuss the options with other heat cores, and am currently suggesting something like the Swift approach. As the Big Tent process continues to mature I'd like to ensure that Heat is well positioned to qualify for the appropriate tags as they are defined. Also it would be worth looking into whether there should be heat-related tags available for projects with sufficiently mature resource implementations. I'll be continuing Heat's tradition of the leadership emerging from a shared consensus, leaving the PTL as a point of coordination within the project, and a point of communication to the greater ecosystem. I look forward to the opportunity to do this! Steve __ 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] [Heat] PTL Candidacy
Hello all, I'd like announce my candidacy for Heat PTL. It's been a pleasure to be part of such a great team for about a year now, and that's the main driver for me to want to represent all of you. I trust that as a team we'll continue do a good job delivering nice software, and I hope I could become the team delegate for the next 6 months. If I had to choose my slogan for this period, it would be Less features, more users. I think we've reached the point where Heat fills a solid portion of the use cases it aimed at the beginning, so we should focus on everything else: * It starts by more functional testing, via more tempests and grenade integration to make sure upgrades are fine. I hope it'll continue to improve our stability * Then I'd like to look at performance, to make sure we're good enough so that people doesn't notice Heat when deploying it * We should also maintain our efforts on documentation * Finally, we should support template authors, by talking to the OpenStack community (TripleO, Trove, Murano,...) but also outside to application developers. I hope we can push contributions to heat-templates (or another repository) for better community interaction. I'm willing to learn if I'll actually have some time to do more than one of those things while holding the position! My commits: https://review.openstack.org/#/q/owner:therve,n,z And my reviews: https://review.openstack.org/#/q/reviewer:therve,n,z Thanks, -- Thomas ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Heat] PTL Candidacy
confirmed On 04/02/2014 11:06 AM, Thomas Herve wrote: Hello all, I'd like announce my candidacy for Heat PTL. It's been a pleasure to be part of such a great team for about a year now, and that's the main driver for me to want to represent all of you. I trust that as a team we'll continue do a good job delivering nice software, and I hope I could become the team delegate for the next 6 months. If I had to choose my slogan for this period, it would be Less features, more users. I think we've reached the point where Heat fills a solid portion of the use cases it aimed at the beginning, so we should focus on everything else: * It starts by more functional testing, via more tempests and grenade integration to make sure upgrades are fine. I hope it'll continue to improve our stability * Then I'd like to look at performance, to make sure we're good enough so that people doesn't notice Heat when deploying it * We should also maintain our efforts on documentation * Finally, we should support template authors, by talking to the OpenStack community (TripleO, Trove, Murano,...) but also outside to application developers. I hope we can push contributions to heat-templates (or another repository) for better community interaction. I'm willing to learn if I'll actually have some time to do more than one of those things while holding the position! My commits: https://review.openstack.org/#/q/owner:therve,n,z And my reviews: https://review.openstack.org/#/q/reviewer:therve,n,z Thanks, signature.asc Description: OpenPGP digital signature ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Heat] PTL Candidacy
Greetings, fellow Heatists. My name is not Steve and I would like to announce my candidacy for the position of Orchestration PTL. Most of you, I hope, already know me. I've been working on Heat full-time essentially since the project started, and I've been a member of the core team since before that was a thing. I'm pretty familiar with both the Heat code and the strategic direction of the program. I've also regularly filled in for past PTLs in various capacities (e.g. on the Technical Committee, in project meetings, and chairing Heat team meetings), so I feel as prepared as one could for being an OpenStack PTL without actually having been one. Heat has always been a project where the core team members make decisions by consensus, the PTL does *not* have the last word on any decision, and the role is rotated through the core team. I'd like to keep it that way. The term Program Technical Lead is a misnomer to me, because we expect leadership from everyone in the team, and especially the core team. (And, not incidentally, because the responsibilities of the PTL are not primarily technical.) With the move to a directly-elected Technical Committee, I think it's time to revisit the role of the PTLs in OpenStack, and understanding that role from the inside will help me to give better input into that process. So the main change I want to make to the project is to make sure that the _next_ PTL has less work to do. PTLs exist primarily to ensure that the program remains accountable to the wider OpenStack community, and I am happy to take on that accountability because I have complete faith in the core team. If elected, it would be my intention to serve for only a single development cycle, as previous Heat PTLs have done. I think that has proven to be a successful model for building leadership depth, maintaining team culture, avoiding burnout and maintaining long-term productivity. I'd also like to encourage anyone thinking of running next time to consider bringing forward their plans and stepping up now, because choice is healthy :) Finally, I'd like to take this opportunity to thank the Steves - Dake, Hardy and Baker - for all their hard work in this role over the past three release cycles. Great work guys! cheers, Zane. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Heat] PTL candidacy
I would like to formally announce my candidacy for Heat PTL. It has been my extreme pleasure to work with the fine Heat development community since this past December. My interest in Heat started with using it as one of the many cogs in the TripleO deployment machine. However, I have grown to really appreciate just how much work it takes to ship a stable orchestration engine. I see PTL as a communication focal point and an enabling position for the development community around Heat. As a good friend once describe a similar position to me, the PTL is the servant of the servants. Of course, one duty of that servant is to relieve the others of turmoil when there is need for a PTL hammer swing. I have clashed at times with the other Heat developers, but I think that is a sign of a healthy dialog, and not a sign of trouble at all. We are all expressing our opinions in a healthy manner, and that should lead to a better code base and more rational decisions. In Icehouse, I see Heat becoming more user driven. We have seen several real users pop up here late in the Havana cycle, and I think we will see quite a few more over the next cycle. I'd like to address any concerns they have while deploying Havana, and make Icehouse the most boring, and thus useful release of Heat ever. Will we ship features? Oh yes of course we will ship features. We are integrating Heat with all of the other relevant projects and there will have to be a feature explosion to accommodate all of that. But primarily, we need to take care of the users, and ship a stable, useful Orchestration system and supporting tools. So, I humbly prostrate myself upon the Heat developers and ask that you consider me for such a position. Some facts for those who are data driven: * http://russellbryant.net/openstack-stats/heat-reviewers-90.txt shows me as 4th in review volumeover the last 90 days. * The same link also shows that if you sort by ascending +/-% of core devs, I am by far the meanest core reviewer. More time spent in release meetings as PTL probably means you will have to deal with less of my incessant nit picking. * https://bugs.launchpad.net/heat/+bugs?search=Searchfield.bug_reporter=clint-fewbar I have opened 22 bugs that are still open (and many that are closed.) I have quite a bit of motivation to aid the Heat development community in getting not only my bugs, but as many of the bugs in Heat addressed as possible. * My name is not, in fact, Steve. You may consider this a pro, or a con. Clint Byrum Senior Server/Cloud Software Engineer - HP ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Heat] PTL candidacy
Hi I would like to announce my candidacy for the Orchestration (Heat) PTL. I have been a software engineer for 16 years and have been developing on Heat for over 12 months. In this period Heat has grown from a small project to being part of the OpenStack ecosystem with a healthy growth in contributors and users. During this time my Heat related development has led to productive relationships with contributors from other projects including Horizon, Infrastructure, Documentation, QA, TripleO and DevStack. The Heat core team has always performed well without the need for prescriptive leadership. Consequently, I feel that this role's primary function is to act as the point of contact with the greater OpenStack community. There is also a need to facilitate the process of reaching consensus, and to advocate for areas which are being neglected. I'm already familiar with most of the tasks of a PTL while filling in for others on several occasions and doing release management for python-heatclient and heat-cfntools. Some of my activity artifacts: https://review.openstack.org/#/q/owner:sbaker%2540redhat.com,n,z https://review.openstack.org/#/q/reviewer:sbaker%2540redhat.com,n,z http://russellbryant.net/openstack-stats/heat-reviewers-180.txt Icehouse During the next cycle, I see these activities as among those the team need to consider: - Growing the core team to match the level of new contributions - Focus on documentation including a comprehensive template writers guide - Resource implementations for all the things, ideally contributed from outside the core developers - Finishing the HOT template format design and implementation - Evaluating the suitability of TaskFlow[1] for Heat - Native autoscaling, with associated autoscaling API. - For projects and cloud providers that adopt Heat, ensuring their needs are being met - Ensuring all Heat features can be used without making any reference to CloudFormation/AWS - Make Heat templates multi-region and multi-cloud aware Finally, despite the overwhelming correlation, and my temporary desire for it to remain so, it is not considered mandatory for the Heat PTL to be called Steve. [1] https://wiki.openstack.org/wiki/TaskFlow ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
