Re: [OpenStack-Infra] Help to remove the old account of IBM Storwize CI(ibm-storwize-ci)
On 2015-07-10 12:49:01 +0800 (+0800), StorwizeCI wrote: [...] > Old Account information:(Need to be removed) > Username: ibm-storwize-ci [...] I've switched this account to inactive status in Gerrit now. Thanks for reaching out to us. -- Jeremy Stanley ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] New storyboard core reviewers
Hi! As you know, StoryBoard development was mostly abandoned by its original development team, following the Infra team decision to no longer make it its long-term strategy for OpenStack task tracking. However, development was recently rebooted by two new contributors: Adam Coldrick (SotK) and Zara Zaimeche (Zara_). Their contributions are now blocked by the lack of core reviewers. I approved what I could (in openstack-infra/storyboard). Their changes and reviews sound solid. But that is not really the question: since they are the only two active developers on StoryBoard today, I think both should be core reviewers for those repositories. The alternative is to put them into a world of change approval misery as they try to convince people who have moved away from StoryBoard to pay enough attention to it to allow them to merge their changes. There is only so much pain you can endure: it will ultimately result in them forking their future development on another platform. To avoid that, I'd rather reboot the team completely and give them the keys. Thoughts ? -- Thierry Carrez (ttx) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] New storyboard core reviewers
I think we need to actually define the project's relationship to OpenStack first. As of Vancouver, there was no decision made on whether to move forward on StoryBoard, Maniphest, or something else. This lack of any kind of forward commitment, both in resources and mandate, or even the lack of ability of anyone to make a decision on this, is exactly why I left in disgust. So let me rehash the questions that were left unanswered in Vancouver. - Is OpenStack going to use StoryBoard? If not, where is the alternative and who is working on it? - Who is actually going to work on storyboard? - Is StoryBoard going to continue under infra? It is quite telling (and I predicted this, just check the storyboard meeting logs form last April) that there has been zero progress on any storyboard alternatives since Vancouver. So: If StoryBoard is not going to be used for OpenStack moving forward, then no: We should not approve new cores, instead we should move the project to the attic. Since OpenStack isn't using it, we should not waste cycles or resources on it, though I encourage the CodeThink team to fork their own. If StoryBoard _is_ going to be used for OpenStack, then I personally feel it should NOT be under the infra program, as membership of that program has done nothing but slow down progress. In fact, I'm pretty certain that had StoryBoard been incubated in stackforge instead, it would have make much more progress, and I would still be working on it. Michael On Fri, Jul 10, 2015 at 7:10 AM Thierry Carrez wrote: > Hi! > > As you know, StoryBoard development was mostly abandoned by its original > development team, following the Infra team decision to no longer make it > its long-term strategy for OpenStack task tracking. > > However, development was recently rebooted by two new contributors: Adam > Coldrick (SotK) and Zara Zaimeche (Zara_). Their contributions are now > blocked by the lack of core reviewers. I approved what I could (in > openstack-infra/storyboard). Their changes and reviews sound solid. But > that is not really the question: since they are the only two active > developers on StoryBoard today, I think both should be core reviewers > for those repositories. > > The alternative is to put them into a world of change approval misery as > they try to convince people who have moved away from StoryBoard to pay > enough attention to it to allow them to merge their changes. There is > only so much pain you can endure: it will ultimately result in them > forking their future development on another platform. To avoid that, I'd > rather reboot the team completely and give them the keys. > > Thoughts ? > > -- > Thierry Carrez (ttx) > > ___ > OpenStack-Infra mailing list > OpenStack-Infra@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] New storyboard core reviewers
Thierry Carrez writes: > As you know, StoryBoard development was mostly abandoned by its original > development team, following the Infra team decision to no longer make it > its long-term strategy for OpenStack task tracking. > > However, development was recently rebooted by two new contributors: Adam > Coldrick (SotK) and Zara Zaimeche (Zara_). Their contributions are now > blocked by the lack of core reviewers. I approved what I could (in > openstack-infra/storyboard). Their changes and reviews sound solid. But > that is not really the question: since they are the only two active > developers on StoryBoard today, I think both should be core reviewers > for those repositories. > > The alternative is to put them into a world of change approval misery as > they try to convince people who have moved away from StoryBoard to pay > enough attention to it to allow them to merge their changes. There is > only so much pain you can endure: it will ultimately result in them > forking their future development on another platform. To avoid that, I'd > rather reboot the team completely and give them the keys. I think that sounds good. My main concern is that storyboard stay stable and usable at least as long as we are using it. If they can support that, I'm happy to add them to core. I suspect this won't be a problem since they are also using it in production. -Jim ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] New storyboard core reviewers
On Fri, Jul 10, 2015 at 8:29 AM Michael Krotscheck wrote: > > It is quite telling (and I predicted this, just check the storyboard > meeting logs form last April) that there has been zero progress on any > storyboard alternatives since Vancouver. > I stand corrected on this (via IRC). There appears to be movement on Maniphest, with some work outstanding for the OAuth integration. Michael ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] New storyboard core reviewers
James E. Blair wrote: > I think that sounds good. My main concern is that storyboard stay > stable and usable at least as long as we are using it. If they can > support that, I'm happy to add them to core. I suspect this won't be a > problem since they are also using it in production. I think it's fair for infra-core to quickly revert commits that would break our production instance. That sounds like a reasonable compromise: let devs make fast progress but still keep our continuous deployment to storyboard.o.o. -- Thierry Carrez (ttx) ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] PuppetBoard
Elizabeth K. Joseph writes: > > On Wed, Jul 8, 2015 at 4:06 AM, Takeshi Larsson > wrote: > > Hows this going? Have you had any thoughts on which way you want to go? > > I'm the "not really a developer" for panopuppet and I was wondering if there > > was something you felt was missing from panopuppet or what it is you are > > "looking" for? > > Thanks for taking the time to reach out to us, it's great to hear from > a contributor to a project we're looking at. Decision-wise, right now > we're continuing to use PuppetBoard and we haven't made a move yet. > > All we need is a read-only dashboard so anyone in our community can > watch puppet changes land and have the data to debug accordingly to > submit a new patch when things fail. The dashboard is public so anyone > on the internet can view it, which means it has to give useful data, > but can't leak sensitive data. We don't do any configuration via the > dashboard, that's all in git and goes through our standard code review > process. > > The main concern about the single developer situation is that this is > the second time we've had to look at changing the dashboard due to > loss of development efforts. It would be great if we could move to a > project that has a stronger community so that when that single > developer has a change in family status/get a new job/focuses > elsewhere, we aren't stuck again. > Hi, Ofcourse I am interested in all potential parties so replying to the mailing list seemed like the most responsible thing to do. I've seen your puppetboard and noticed that you only have 100-200 nodes and is nothing that puppetboard cannot handle. PanoPuppet was written because at work we have more than 3000 nodes and puppetboard could not handle showing that amount of nodes. It was written to work at my current place of employment to function with cross function teams with advanced query building to find just the nodes you need or are responsible for. I was trying to make it as "enterprise" ready as possible. So that there was a solution that could fill the needs of the puppet opensource users. PanoPuppet much like puppetboard is a read-only dashboard. The data shown in puppetboard is pretty much what PanoPuppet offers except that PanoPuppet offers better tools for analytics, debugging and PuppetDB Query Building. It seems that your workflow is pretty much the same as it as where I work. We use hiera and we commit everything for review and have CI's checking for various errors etc and also human reviewal before allowing it to reach our master branch. The single developer project is ofcourse a major factor to your choice of dashboard. And I am aware of PuppetBoards choice to add more core developers to their project that happened several months ago and I have yet to see any kind of major PR or commits to happen. I on the other hand get to work on PanoPuppet at work and keep it FOSS and also I spend a couple of hours at home tinkering with it. This is to satisfy the needs of my colleagues at work but also some of my users (most of which have over 10k nodes) using it. They constantly email me with new feature requests or bugs they have found. While I understand the worry about losing the only developer, I can tell you, I'm 24 years old without kids and not looking to get any for a couple of years. So as long as the company I work need PanoPuppet or there are others who need PanoPuppet I will probably be available for a couple of years and hopefully during that time some more developers might want to hop on. I've spoken to Spencer on irc about Puppetboard and while I can consider helping out Puppetboard I am not sure I will stop developing PanoPuppet to help out with Puppetboard. Even though Puppetboard has a much bigger customer base having been available longer than PanoPuppet, PanoPuppet was not created to take over any other projects and was a way for me to learn more python and perhaps even decision making based on opinions of the few PanoPuppet users. My user base seems to be growing, more people seem to be trying PanoPuppet out which I think is great. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
[OpenStack-Infra] leguin.freenode.net and the å of doom
leguin is transmitting its MOTD (containing "Umeå" twice) in ISO 8859-1. This is causing havoc with one of OpenStack's python scripts, which is happy with all the other servers that are sending valid UTF-8. I think we would rejoice if someone could run iconv on the motd file or whatever is necessary to normalize the character encoding sent to clients. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
Re: [OpenStack-Infra] leguin.freenode.net and the å of doom
RT has assigned ticket number [freenode.net #158989] for this, should anyone need to follow up. ___ OpenStack-Infra mailing list OpenStack-Infra@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra
