[openstack-dev] [glance] PTL candidacy for Pike
Hello everyone, I'm asking for the opportunity to continue to serve as the PTL of Glance into the Pike cycle. The Current State of Glance --- This has been an interesting cycle. We accomplished the community goals and eventually merged Community Images (after a thorough and extensive discussion of almost every aspect of the feature), completing half of our Ocata priorities. We also fixed some bugs and implemented some lite specs. As of this date, however, our Rolling Upgrades priority is going to require a FFE, and there's not a chance that we're going to merge anything related to Image Import. That's kind of a mixed record to be running for re-election on, so I figure I should explain what I learned and how I see things shaping up for Pike if I continue as PTL. The Glance Community First, I'd like to discuss the Glance Community. There are several contributors who are active, energetic, knowledgeable, and great to work with. There are some contributors who aren't quite so active, but who attend meetings and help out occasionally reviewing the weekly priority items. Unfortunately, there are some current Glance cores who don't currently fall into either of the above categories. Before the Pike PTG, I'm going to ask people on the core list to consult with their managers and determine whether they have sufficient bandwidth to be effective core contributors to the project. I was hoping that people would naturally do this themselves, but that didn't happen during Ocata ... primarily, I think, because it's an honor to be a core contributor to an OpenStack project, and it's not easy to face up to hanging up your stirrups, or turning in your badge and gun, or whatever the appropriate metaphor is. But for the success of the project, I need an honest self-assessment from the current cores of the amount of time they can commit to Glance. (I didn't want to force the issue because, as is common with the core contributors across all our projects, we're talking about high-quality developers here, and I was hoping they'd be able to find more time to work on Glance. That was a mistake. I'm mentioning it not to embarrass any of the people I'm talking about, but rather as a point of information to anyone reading this who will be a first-time PTL in Pike.) Anyway, my goal is to have the core team reconstituted before the Pike PTG so that we'll have a better idea of what kind of bandwidth the team will have in Pike. I think this will cascade into a better overall Glance community experience because there will be more participation in the weekly meetings and on IRC, making the community feel more vibrant. Further, because those active people are currently reviewing all the time, we haven't had as much bandwidth for bug triaging and bug smashing. We need to change that in Pike. Plus, a larger group of active cores will provide Glance with a bigger pool of PTL candidates for the Queens cycle. Glance Priorities for Pike -- This is how I see things shaping up for Pike. 1. Image Import Now I understand why my predecessors as PTL had such a hard time with this. The situation is that this is an extremely important feature for the OpenStack community in general, but it's not really a priority for anyone in particular. Thus, it's been difficult to keep one or two people, no matter how well-intentioned, working steadily on it (and I don't exempt myself from this statement). Since image import is an important feature for Glance, the entire team needs to be working on it. And we can make it a priority for everyone by committing to *not* merge anything else (other than security bugs) until image import is merged. You can see how this is connected to my discussion above about the core team. I want all active cores to be working on some part of this, and that way we are all accountable to each other much more explicitly than we have been in previous cycles. I'm not even going to enumerate anything else. We'll work on the "community goals", of course, but not until after image import has been merged. And we may have some more to do on the rolling upgrades work. We'll discuss other possible items at the PTG, but at this point I don't want to look past image import. Conclusion -- Well, that's my election platform. I'd like to continue as Glance PTL, and I've outlined above what my plans are for the Pike cycle. Thank you for your consideration, Brian Rosmaita __ 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] [glance] PTL candidacy
I've just put up https://review.openstack.org/#/c/368995/, declaring my candidacy for Glance PTL. Here's the content of that patch for your convenience: Hello everyone, I would like to announce my candidacy for the role of PTL of Glance for the Ocata cycle. Current State of Glance --- This is a good time to be PTL of Glance. The project has recently served as the incubator for a successful project (Searchlight) and a hopefully soon-to-be successful project (Glare), and at this point we can focus on being Glance [0]. In Newton, the Images v1 API is being deprecated [1] and Nova will be using the v2 API by default [2], which allows us to focus even further. Glance has some important efforts in progress that need to be seen through to completion, so given the short upcoming cycle, I anticipate quick agreement in determining our Ocata priorities. In short, I see myself as a "continuity" candidate, building on the good work done by Flavio and Nikhil in the previous cycles. Glance Priorities - This is how I see things shaping up for Ocata. 1. Image Import The Glance image import refactoring proposal [3] has been discussed thoroughly through two cycles by all OpenStack groups and individuals interested in a discoverable, interoperable means of getting end-user created images into OpenStack clouds of various types (public/private, large/small). There are some patches up, and Nikhil has indicated that image import is a priority for post RC-1 time; I want us to continue that work and deliver image import in Ocata. 2. Community Images Implementation of the Community Images spec [4], approved for Newton, has been delayed, in large part due to reviewer bandwidth issues (which I'll address below). It's a much-requested feature, has several patches up, and is a priority to deliver early in Ocata. 3. Rolling Upgrades The OpenStack Innovation Center has been promoting various operator friendly enhancements to OpenStack, one of which is zero-downtime control plane upgrades. Several Glance developers associated with OSIC have been working out a strategy (and some alternatives) to make this happen in Glance [5,6]. I expect we'll be able to converge on a strategy during (or shortly after) the Barcelona Summit with the goal of having a zero-downtime Newton-to-Ocata upgrade available in Ocata. (These three items are high-impact for operators and end users, so are appropriately our top three Ocata priorities. I have serious concerns about Glance being able to deliver more than this in Ocata, so please notice the caveats attached to the following items.) 4. Community Priorities The TC recently adopted "community goals" for each cycle [7], and as a good community citizen, the Glance project will want to adopt these as priorities for Ocata. The goal "remove copies of incubated Oslo code" [8] primarily affects the python-glanceclient. The goal "support python 3.5" [9] is still under discussion in the wider community, with some projects reporting that it will be a stretch to implement in Ocata. It will also be a stretch for Glance given our resource constraints. (I think the major impact for Glance will be in getting the functional tests to pass under Python 3.5, but I haven't done a complete analysis of this.) 5. Other As noted earlier, this is a short cycle. The above is quite a list, though that's mitigated a bit by some of the items already being in progress. There are some other candidates for Glance priorities that we can discuss carefully at the Summit [10], in particular, the Glance Store Refactor and Hierarchical Image Access. Personally, I would like to see us at least (a) come to a consensus on, and (b) articulate clearly the envisioned usage of the glance_store library during the Summit as that will be helpful in guiding the refactoring of its API and guide its future development (whether or not that development happens in Ocata). Hierarchical Image Access would complete the Glance image sharing use cases, and shouldn't be too bad to implement given the changes made for the Community Images implementation, but we need to make a realistic assessment of this at the Summit. Finally, the glance-specs repo contains some approved but not implemented specs and lite-specs. These are useful items (or they wouldn't have been approved in the first place!). They will also have to be the subject of a realistic assessment during the Summit. Glance Community I said earlier that this is a good time to be Glance PTL; it's also a good time to join the Glance community, particularly for ambitious developers who would like to achieve core status on one of the major OpenStack projects. We need more reviewers as, right now, most of the core reviewers for Glance have additional commitments. Although we need more reviewers, I don't want to "clean house" because our core reviewers represent a cross-section of the community and bring a lot of expertise
[openstack-dev] [glance] PTL candidacy
Hi everyone, I'd like to be considered for Glance PTL. First: thanks (again) to Flavio for his leadership over the last cycle. Glance is in pretty good shape right now: we have a coherent team which is focussed on a well defined set of priorities. It's a relatively small team, but we're fortunate to have a good range of strengths; every one brings something valuable. I've been contributing to Glance since Essex. I've probably touched most areas of the code at some point since then, and I hope I've built up a good understanding of the code base, the thinking behind most of it ... and the quirks too. I can't claim to know all the OpenStack code base (who can?) but I've good relationships with folks from a bunch of other projects I can reach out to, especially the ones Glance interacts with (Keystone, Swift, Cinder etc). For several years I was also an operator. Starting from Diablo (back when we were still using integers, not uuids) I was responsible for running Glance in HP's Public Cloud (24x7x365). That gave me a good understanding of the issues operators face and, where I can, I've contributed back based on my experience. As a developer and operator my goal has been the same: to give the best possible experience for users. If elected I will be able to devote myself full time to the project, be available on IRC, and hope to increase my own review rate. Priorities for the Newton cycle: * Image import refactor We need to do everything we can to ensure DefCore can include an image upload capability. * v2 API adoption We need to make it possible to deploy OpenStack without enabling Glance's v1 API. There were some heroic efforts on the Nova side of this during Mitaka (thanks Mike). * Maintain focus. Yes, we will work on other things during the cycle. But we shouldn't commit to anything that could impact on our priorities. It's ok to say "no" now and again. There will be other cycles. Thanks for your consideration. -Stuart __ 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] [Glance] PTL candidacy
Hello everyone, I would like to herewith propose my candidacy for the role of Glance PTL for the Mitaka release cycle. I. Personal Commitment I am a full time upstream OpenStacker at IBM and have recently transitioned into this role with the condition that I will be given 100% time to focus on community issues, development and help solve upstream challenges. I am also committed to giving my full attention to Glance. Not too long ago, I have had a few conversations with the PTLs of other projects for either help them better use Glance or for dissolving the issues they were facing in their projectsw. However, in this cycle I would like to work with some of you in the capacity of inter-project liaisons to help better understand the usage and stability of Glance in respective areas and yet be involved with you in addressing those issues. I know this is added work that must not go unrewarded so, I would like to work out a plan with you that will enable distribution of power (if with more power comes more responsibility, visa versa must true, making it true claim). It has been enabled in Glance to some extent & I have learnt other bigger projects implementing this. I would like to make it a complete reality in Glance. I am also committed to documenting and improving the current specs process and criterion that will enable quicker turnaround time. At IBM, I have the pleasure of being part of team that has some of the most outstanding OpenStackers and I hope to collaborate more with them in Mitaka for solving (hard) problems. II. Liberty a) Stability Over 100 bugs were fixed in Liberty (including python-glanceclient, glance_store and Glance servers) with a relatively small review team. Glance is gradually improving momentum to help the different code proposals get time-justice for code reviews. Some features in Kilo introduced a number security bugs beyond expectations so, the further development of those features has been slowed down and focus has been shifted to fix the functionality, making it more stable and secure. Experimental features showed a smooth progress and close to no issues of such sort. A close eye on the reviews was kept to ensure so. Any spec proposals that showed potential security risks, shake stability or performance or refactor major parts of the code base were given a wait signal. b) Performance I consider them as systematic optimizations and sometimes systematic improvisations. Major disagreements on the path forward for optimizing streaming workflows for images data have been sorted out. Many new proposals were made however, due to lack of early time commitment from developers they were unable to be seen through. Continued feedback should be expected for similar proposals for glance_store in early Mitaka. c) Cross project communications & Process Evolution I have made an attempt to continually evolve our process to make it more engaging and community friendly. Now there are three meetings weekly that are a good place for collaboration on different aspects of Glance. Either me or a member of the Glance community is at the weekly CPL meeting to gather feedback from horizontal teams, cross project decision/efforts etc. as well as input has been provided using Glance’s perspective. I have had regular chats with Nova PTL on the outstanding issues of the Images APIs and adoption of v2 Images API by Nova. Feedback was provided at the DefCore mid-cycle as well as a welcoming hand was presented for attending Glance mid-cycle (even virtually) for those who could not make it. In Mitaka, I hope to continue collaborating with the interested members there as well as in the other projects. I would like to pay close personal attention to the pressing matters that need short team resolution like the adoption of v2 API by Nova and Images API suitable for DefCore. Unfortunately, any of the existing (half) attempts at fixing this issue have been wasted as they were breaking some of the fundamental aspects of project. This matter would need wider input for a fine resolution and a change that would not break the world; of-course compromise is very likely for some but doesn’t need to be fundamentally disjoint with the newly established DefCore standard. It was realized early that a half baked attempt of making such a critical change would break core of Glance so, I have been contemplating on the future of the project. More clarity of thought has been accomplished during the conversations with the TC members, PTLs, Product WG liaisons etc. and I will continue to gather more feedback in Mitaka. It has been a pleasure to be part of (collaborating with) teams that help build very large cloud deployments and I find that experience valuable for solving this complicated matter. Not only upstream but at IBM too, I plan to closely interact with the technical and product leaders of the Public and Private cloud deployment to help solve such issues. My team at IBM enables me to have such interactions with
[openstack-dev] [Glance] PTL Candidacy
Greetings, I'd like to raise my hand and send my candidacy for Glance's PTL position. If you've heard my name, it's entirely possible that you hear it either for my Zaqar's PTL position or my current TC position. Before I go forward with my candidacy, allow me to say that I won't be running for Zaqar's PTL position and that it's my intention to be entirely focused on Glance[0]. I take being a PTL seriously[1] and I strongly believe in the importance of focus when it comes to making progress, which is what I'd like to base my candidacy on. Glance may seem a simple service but it's not as simple as many folks think. It's small compared to many other projects but it's still exciting to work on. Perhaps, even more important than how exciting it is, we should all remember the impact this project has on the rest of the community and how it impacts all the OpenStack deployments out there. In addition to this, Glance remains one of the projects that are considered part of the starting kit and it serves a very important task in a cloud deployment. The reason I'm bringing the above up is because I believe we've derailed a bit from that and that we should bring focus back on what's the most important task for Glance, which is to serve cloud images in a resilent, consistent and reliable way. This is not to say that innovation should be stopped but it certainly shouldn't affect this mission. I believe these are some of the most important topics that our team should focus on (non exhaustive list): - Collaboration with other projects to migrate OpenStack to use Glance's V2 API - Collaborate with the defcore team to define a clear view and support of what Glance provides and is. - Increase V2 stability and awareness. - Improve Glance's gate story to make sure we cover enough scenarios that are representative of existing deployments and use cases. By reading the above four points, it's clear that I think that lot of our work should go on cross-project collaboration. However, I'd like to extend that to cross-team collaboration. One of the things that I believe has affected Glance a lot is the lack of interaction with other teams, especially with OPs, when it came down to working on new features that had an impact on users. Therefore, I'd like to help increasing cross-team collaboration in Glance's team. As far as my involvement in Glance goes, I've been part of the team since I started working on OpenStack. For the upcoming cycle, I'm ready to dedicate my PTL duties entirely on the project and completely focused on what's important to bring back focus and keep the project growing but stable. As some of you know already, I'm also part of the Technical Committee and I'll be up for election next April, which means I'll be part of the TC for, at least, 6 more months. Being part of the TC takes time and this is something you should keep in mind (as much as I do). However, if I were to be elected as Glance's PTL, I'll dedicate all my efforts and time - consider that my current job allows me to be full time upstream - to just these to roles. It'd be a great honor for me to work together with the Glance team and to keep sharing knowledge, experiences and work as I've been doing so far but this time as a PTL. Thanks for reading thus far and for considering this candidacy, Sincerely, Flavio [0] http://lists.openstack.org/pipermail/openstack-dev/2015-September/074212.html [1] http://lists.openstack.org/pipermail/openstack-dev/2015-September/073986.html -- @flaper87 Flavio Percoco pgpWYPRRzJNp0.pgp Description: 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
Re: [openstack-dev] [Glance] PTL Candidacy
confirmed On 04/09/2015 12:55 AM, Nikhil Komawar wrote: Hello everyone, I would like to announce my candidacy as PTL for Glance for Liberty cycle. I have been part of the Glance program since Folsom release and have seen it grow and get better over the years. As the PTL for Kilo, I have helped this program achieve a steady forward momentum. In the process, quite a few developers have joined the program, become core reviewers, and have been providing excellent feedback on reviews, specs and development of libraries. It has been a pleasure to collaborate with everyone and get the newer members up to speed on the Glance project's development patterns and processes. Also, we have been able to accomplish good progress on the newly added features namely Artifacts and the Catalog Index Service. At the same time, other blueprints have had good attention both from code contributors as well as reviewers side. Although we began with a relatively small review team at the advent of Kilo, over a dozen blueprints were implemented for Glance. Additionally, we have been making continued progress in improving the glance_store and python-glance client libraries. Also, we've made a lot of progress in Glance for incubating cross-project changes like adopting graduated oslo policy, support of multiple sort keys and directions in glance and in the client, etc. We have also seen better feedback time on reviews, better awareness on review guidelines, more IRC presence, better collaboration in the meetings and on the Mailing Lists, and prompt attention to security bugs. There have also been improvements in subtle aspects of the program like more Documentation support, feature updates in the client, as well as increased frequency of releases of the libraries. All of this great work has been made possible by the support of a group of really talented and proactive developers who have made the Glance ATCs into a vibrant community. For Liberty I would like to encourage the team to help Artifacts and the Catalog Index Service achieve feature completion early in the first phase of the cycle. This will put us in a good position to address stability concerns and make stability the primary focus of the Liberty cycle. As we have made good progress in reducing the technical debt of promised features and improving cross project experience within Glance, I think it's time to put more focus in stabilizing the code bases. glance_store was introduced in the Juno cycle, saw great improvements in Kilo, but requires more work to become a mature repository. So, for Liberty, as a part of stability goal I would like to work with the team in rising its Development Status to level 4 at the very least. Also, there have been some really great feature proposals in the later phase of Kilo that couldn't be implemented in the short window available. I would like to help these proposal get some feedback as well as work with their respe ctive development teams in building solutions cohesive to the Glance program. During Kilo, Glance made the full transition from the old blueprint style of design specifications to the more rigorous specs-based system. From that experience, the team has learned what did and didn't work well and has asked for a better process for managing blueprints, specs and documentation. I would like to partner with developers as well as operators in understanding and addressing the pain points therein. I would like to partner with a wider group in being able to setup documentation for the same. I would also like to help the team get a healthier review speed and start implementing the rotation policy for core reviewers. I have enjoyed working with all the Glance contributors and have learned a lot while serving as PTL for Kilo. I'd appreciate the opportunity to apply what I've learned to the Liberty release. Thanks for your consideration and support, -Nikhil Komawar __ 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] [Glance] PTL Candidacy
Hello everyone, I would like to announce my candidacy as PTL for Glance for Liberty cycle. I have been part of the Glance program since Folsom release and have seen it grow and get better over the years. As the PTL for Kilo, I have helped this program achieve a steady forward momentum. In the process, quite a few developers have joined the program, become core reviewers, and have been providing excellent feedback on reviews, specs and development of libraries. It has been a pleasure to collaborate with everyone and get the newer members up to speed on the Glance project's development patterns and processes. Also, we have been able to accomplish good progress on the newly added features namely Artifacts and the Catalog Index Service. At the same time, other blueprints have had good attention both from code contributors as well as reviewers side. Although we began with a relatively small review team at the advent of Kilo, over a dozen blueprints were implemented for Glance. Additionally, we have been making continued progress in improving the glance_store and python-glanceclient libraries. Also, we've made a lot of progress in Glance for incubating cross-project changes like adopting graduated oslo policy, support of multiple sort keys and directions in glance and in the client, etc. We have also seen better feedback time on reviews, better awareness on review guidelines, more IRC presence, better collaboration in the meetings and on the Mailing Lists, and prompt attention to security bugs. There have also been improvements in subtle aspects of the program like more Documentation support, feature updates in the client, as well as increased frequency of releases of the libraries. All of this great work has been made possible by the support of a group of really talented and proactive developers who have made the Glance ATCs into a vibrant community. For Liberty I would like to encourage the team to help Artifacts and the Catalog Index Service achieve feature completion early in the first phase of the cycle. This will put us in a good position to address stability concerns and make stability the primary focus of the Liberty cycle. As we have made good progress in reducing the technical debt of promised features and improving cross project experience within Glance, I think it's time to put more focus in stabilizing the code bases. glance_store was introduced in the Juno cycle, saw great improvements in Kilo, but requires more work to become a mature repository. So, for Liberty, as a part of stability goal I would like to work with the team in rising its Development Status to level 4 at the very least. Also, there have been some really great feature proposals in the later phase of Kilo that couldn't be implemented in the short window available. I would like to help these proposal get some feedback as well as work with their respective development teams in building solutions cohesive to the Glance program. During Kilo, Glance made the full transition from the old blueprint style of design specifications to the more rigorous specs-based system. From that experience, the team has learned what did and didn't work well and has asked for a better process for managing blueprints, specs and documentation. I would like to partner with developers as well as operators in understanding and addressing the pain points therein. I would like to partner with a wider group in being able to setup documentation for the same. I would also like to help the team get a healthier review speed and start implementing the rotation policy for core reviewers. I have enjoyed working with all the Glance contributors and have learned a lot while serving as PTL for Kilo. I'd appreciate the opportunity to apply what I've learned to the Liberty release. Thanks for your consideration and support, -Nikhil Komawar __ 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] [Glance] PTL Candidacy
confirmed On 04/02/2015 10:53 AM, Flavio Percoco wrote: Greetings, I'd like to put my name out there for the Glance PTL position. Few words about me: I'm Flavio Percoco (flaper87 on IRC and everywhere). I've been an OpenStack fellow for the last 2 1/2 years. During this time I've spread my efforts on several projects but mainly on Glance, from which you may/may not know me. Glance == Since my early days in OpenStack, I've been part of every core - core in terms of service, not membership - decision in Glance. From what to do with the registry service, glance_store, API stability etc. Throughout these decisions, I've participated in the release process, leading positions and also as a voice for those changes. I'm happy to say that our project has grown a lot and that we're facing new challenges that I'd love to be part of and more importantly, I'd love to help leading those efforts along side our, growing, community. Interesting things happened in Kilo but I'd like to focus now on what's coming next, Liberty. One of the things that is still pending for us is the work on Artifacts. Despite I don't believing that Glance is the best for it to live forever, I'd love to see this work done and for it to grow. The effort that is being put there not only code-wise, feature-wise but also review-wise is already a good enough proof of how the impact this could have in our community. In addition to the above, I'd love our team to improve Glance's API story throughout OpenStack and see such API grow and stabilize. This not only refers to the service itself but the libraries that Glance relies on too. I strongly believe that stability and consistency should be part of our main goals in the upcoming development cycle. New features will be proposed for sure and I'd love us all to review them together and decide together what's best for the project's future baring in mind the goals of the cycle. Community = Thankfully enough, I've had the pleasure to be involved in many areas of our community and this has given me a good knowledge of how our community is structured and how the different parts interact with each other. From the stability team to our infrastructure team going through OpenStack's common ground (Oslo). I'd love to use this broad view in this position as I've been using it as a contributor. In the other hand, I'm also known from being noisy, speaking up and ready to fight whenever it's needed (even when it is not :P). Just like with everything else, I'm looking forward to apply all this to this position as I've done in my current position. Last but no least, I've had the pleasure to be Zaqar's PTL during Kilo (and co-PTL since the beginning), which has as well prepared me for this task. Thanks for reading thus far, I hope you'll consider me as a good candidate for this position. Flavio __ 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] [Glance] PTL Candidacy
Greetings, I'd like to put my name out there for the Glance PTL position. Few words about me: I'm Flavio Percoco (flaper87 on IRC and everywhere). I've been an OpenStack fellow for the last 2 1/2 years. During this time I've spread my efforts on several projects but mainly on Glance, from which you may/may not know me. Glance == Since my early days in OpenStack, I've been part of every core - core in terms of service, not membership - decision in Glance. From what to do with the registry service, glance_store, API stability etc. Throughout these decisions, I've participated in the release process, leading positions and also as a voice for those changes. I'm happy to say that our project has grown a lot and that we're facing new challenges that I'd love to be part of and more importantly, I'd love to help leading those efforts along side our, growing, community. Interesting things happened in Kilo but I'd like to focus now on what's coming next, Liberty. One of the things that is still pending for us is the work on Artifacts. Despite I don't believing that Glance is the best for it to live forever, I'd love to see this work done and for it to grow. The effort that is being put there not only code-wise, feature-wise but also review-wise is already a good enough proof of how the impact this could have in our community. In addition to the above, I'd love our team to improve Glance's API story throughout OpenStack and see such API grow and stabilize. This not only refers to the service itself but the libraries that Glance relies on too. I strongly believe that stability and consistency should be part of our main goals in the upcoming development cycle. New features will be proposed for sure and I'd love us all to review them together and decide together what's best for the project's future baring in mind the goals of the cycle. Community = Thankfully enough, I've had the pleasure to be involved in many areas of our community and this has given me a good knowledge of how our community is structured and how the different parts interact with each other. From the stability team to our infrastructure team going through OpenStack's common ground (Oslo). I'd love to use this broad view in this position as I've been using it as a contributor. In the other hand, I'm also known from being noisy, speaking up and ready to fight whenever it's needed (even when it is not :P). Just like with everything else, I'm looking forward to apply all this to this position as I've done in my current position. Last but no least, I've had the pleasure to be Zaqar's PTL during Kilo (and co-PTL since the beginning), which has as well prepared me for this task. Thanks for reading thus far, I hope you'll consider me as a good candidate for this position. Flavio -- @flaper87 Flavio Percoco pgpl5BUdvwxbO.pgp Description: 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-dev] [Glance] PTL candidacy
Hi, I would like to take this opportunity and announce my candidacy for the role of Glance PTL. I have been part of this program since Folsom release and have had opportunity to work with an awesome team. There have been really challenging changes in the way Glance works and it has been a pleasure to contribute my reviews and code to many of those changes. With the change in mission statement [1], that now provides a direction for other services to upload and discover data assets using Glance, it would be my focus to enable new features like 'Artifacts' to merge smoothly into master. This is a paradigm change in the way Glance is consumed and would be my priority to see this through. In addition, Glance is supporting a few new features like async workers and metadef, as of Juno that could be improved in terms of bugs and their maintainability. Seeing this through would be my next priority. In addition to these, there are a few other challenges which Glance project faces - review/feedback time, triaging ever growing bug list, BP 'validation and followup' etc. I have some ideas to develop more momentum in each of these processes. With the advent of the Artifacts feature, new developers would be contributing to Glance. I would like to encourage and work with them become core members sooner than later. Also, there are many merge propositions which become stale due to lack of reviews from core-reviewers. My plan is to have bi-weekly sync-ups with the core and driver members to keep the review cycle active. As a good learning lesson from Juno, I would like to work closely with all the developers and involved core reviewers to know their sincere intent of accomplishing a feature within the scope of release timeline. There are some really talented people involved in Glance and I would like to keep synthesizing the ecosystem to enable everyone involved to do their best. Lastly, my salutations to Mark. He has provided great direction and leadership to this project. I would like to keep his strategy of rotation of weekly meeting times to accommodate the convenience of people from various time zones. Thanks for reading and I hope you will support my candidacy! [1] https://github.com/openstack/governance/blob/master/reference/programs.yaml#L26 -Nikhil Komawar ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Glance] PTL candidacy
Thanks, Nikhil, for offering to take on this responsibility. I know you've had a lot of experience with Glance in the past and I feel comfortable knowing that you'll be around to keep the project moving forwards! Cheers! On Thu, Sep 25, 2014 at 1:56 PM, Nikhil Komawar nikhil.koma...@rackspace.com wrote: Hi, I would like to take this opportunity and announce my candidacy for the role of Glance PTL. I have been part of this program since Folsom release and have had opportunity to work with an awesome team. There have been really challenging changes in the way Glance works and it has been a pleasure to contribute my reviews and code to many of those changes. With the change in mission statement [1], that now provides a direction for other services to upload and discover data assets using Glance, it would be my focus to enable new features like 'Artifacts' to merge smoothly into master. This is a paradigm change in the way Glance is consumed and would be my priority to see this through. In addition, Glance is supporting a few new features like async workers and metadef, as of Juno that could be improved in terms of bugs and their maintainability. Seeing this through would be my next priority. In addition to these, there are a few other challenges which Glance project faces - review/feedback time, triaging ever growing bug list, BP 'validation and followup' etc. I have some ideas to develop more momentum in each of these processes. With the advent of the Artifacts feature, new developers would be contributing to Glance. I would like to encourage and work with them become core members sooner than later. Also, there are many merge propositions which become stale due to lack of reviews from core-reviewers. My plan is to have bi-weekly sync-ups with the core and driver members to keep the review cycle active. As a good learning lesson from Juno, I would like to work closely with all the developers and involved core reviewers to know their sincere intent of accomplishing a feature within the scope of release timeline. There are some really talented people involved in Glance and I would like to keep synthesizing the ecosystem to enable everyone involved to do their best. Lastly, my salutations to Mark. He has provided great direction and leadership to this project. I would like to keep his strategy of rotation of weekly meeting times to accommodate the convenience of people from various time zones. Thanks for reading and I hope you will support my candidacy! [1] https://github.com/openstack/governance/blob/master/reference/programs.yaml#L26 -Nikhil Komawar ___ 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] [Glance] PTL candidacy
confirmed On 04/02/2014 06:51 PM, Mark Washenberger wrote: Hi all, I'd like to submit myself as a candidate to continue in the role of Glance PTL for the Juno release cycle. A bit of history about me: I joined Rackspace's Team Titan back in February 2011, where were initially focused on filling out the OpenStack 1.1 api for nova. I've been working with Glance apis and core functionality for about 5 cycles now. Since November 2012 I've been an employee of Nebula, working alongside some of the original NASA OpenStack folks and the former Glance PTL Brian Waldon (until he left to go manufacture oreos). As Juno PTL, I expect to proceed much in the same way as during Havana and Icehouse, hopefully with lots of realized opportunities for incremental improvement. I'm very open to any advice, suggestions, or other contributors who want to take on more responsibility in the near future. Thank you, markwash ___ 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] Glance PTL candidacy
Hi all, I'd like to submit myself as a candidate to continue in the role of Glance PTL for the Icehouse release cycle. A bit of history about me: I joined Rackspace's Team Titan back in February 2011, where were initially focused on filling out the OpenStack 1.1 api for nova. I've been working with Glance apis and core functionality for about 4 cycles now. Since November 2012 I've been an employee of Nebula, working alongside some of the original NASA OpenStack folks and the former Glance PTL Brian Waldon. As Icehouse PTL, I expect to proceed much in the same way as during Havana, hopefully with lots of realized opportunities for incremental improvement. That's about the most honest endorsement I can give of myself. I'm very open to any advice, suggestions, or other contributors who want to take on more responsibility in the near future. One thing I learned during Havana was that I was in a better position before becoming PTL to work on the particular items I care most about, so any sensible responsibility sharing that would free me up to continue working on refining code organization and test performance is very welcome. Thank you, markwash ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
