From nguyentrihai93 at gmail.com Sat Sep 1 01:48:06 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Sat, 1 Sep 2018 10:48:06 +0900 Subject: [OpenStack-Infra] [octavia][goal][python3] starting zuul migration for octavia In-Reply-To: References: Message-ID: Please process the removing job settings for octavia repositories https://review.openstack.org/#/c/595783/ On Thu, Aug 23, 2018 at 10:23 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the octavia repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/neutron-lbaas > - openstack/neutron-lbaas-dashboard > - openstack/octavia > - openstack/octavia-dashboard > - openstack/octavia-tempest-plugin > - openstack/python-octaviaclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Sat Sep 1 05:10:54 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Sat, 1 Sep 2018 14:10:54 +0900 Subject: [OpenStack-Infra] [swift][goal][python3] starting zuul migration for swift In-Reply-To: References: Message-ID: Please process the removing patch. https://review.openstack.org/#/c/596224/ On Fri, Aug 24, 2018 at 4:48 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the swift repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-swiftclient > - openstack/swift > - openstack/swift-bench > - openstack/swift-specs > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From aj at suse.com Sat Sep 1 05:38:17 2018 From: aj at suse.com (Andreas Jaeger) Date: Sat, 1 Sep 2018 07:38:17 +0200 Subject: [OpenStack-Infra] Migrating job configs into infra repositories In-Reply-To: <1535740903.1341276.1492864688.575F1FED@webmail.messagingengine.com> References: <1535740903.1341276.1492864688.575F1FED@webmail.messagingengine.com> Message-ID: <5ac3413d-b150-af0a-7092-40a8dd2b1fa2@suse.com> On 2018-08-31 20:41, Clark Boylan wrote: > Hello, > > OpenStack is currently in the process of migrating project CI job configs into individual repos. Part of the motivation for this was to remove us (the Infra team) as a roadblock to getting job config changes merged. This is particular important for OpenStack as it is trying to update its job configs to be python3 first so there will be a fair bit of job churn over the Stein cycle. > > This is great for OpenStack, but the question has come up about whether or not we (the Infra team) want to do similar for our projects. > > My initial thought is that it isn't as urgent for us because infra-core already manage both the separate repos and the central job config. This means we can manage the job churn ourselves regardless of the location. Considering the other items we currently have on our place (namely Winterscale and config management updates) I'm willing to defer on this for now. > > If you think we should make moving job config into our repos a priority please let me know. More than happy to accommodate this work, but we will likely need a volunteer to help do it. (I don't expect we'll be able to piggy back off of the OpenStack work as we have many non standard jobs from OpenStack's perspective). Moving the jobs in repo is not that difficult - updating them all to use python3 will be. The scripts by Doug will help us a lot. Still, for our 158 repositories, I don't see the benefit at the moment since it's the same team dealing with it and as Clark said we have some other things on the plate. We can do this for repos where - and once - it makes sense one by one over time as we did already, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From doug at doughellmann.com Sat Sep 1 12:11:21 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Sat, 01 Sep 2018 08:11:21 -0400 Subject: [OpenStack-Infra] [goals][python3][interop] starting zuul migration for InteropWG In-Reply-To: <1535667459-sup-2168@lrrr.local> References: <1535667459-sup-2168@lrrr.local> Message-ID: <1535803860-sup-8406@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-30 18:17:42 -0400: > The migration of Zuul project settings for the > InteropWG repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/interop > - openstack/python-tempestconf > - openstack/refstack > - openstack/refstack-client All of the import patches have been merged and we are ready to proceed with approving https://review.openstack.org/#/c/598377/ From doug at doughellmann.com Tue Sep 4 15:52:24 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 04 Sep 2018 11:52:24 -0400 Subject: [OpenStack-Infra] [goals][python3][cloudkitty] starting zuul migration for cloudkitty In-Reply-To: <1535720569-sup-902@lrrr.local> References: <1535720569-sup-902@lrrr.local> Message-ID: <1536076327-sup-8328@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-31 09:03:07 -0400: > The migration of Zuul project settings for the > cloudkitty repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/cloudkitty > - openstack/cloudkitty-dashboard > - openstack/cloudkitty-specs > - openstack/cloudkitty-tempest-plugin > - openstack/python-cloudkittyclient The import patches have all merged and we are ready to proceed with https://review.openstack.org/#/c/598929/ Doug From doug at doughellmann.com Tue Sep 4 15:53:20 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 04 Sep 2018 11:53:20 -0400 Subject: [OpenStack-Infra] [goals][python3][barbican] starting zuul migration for barbican Message-ID: <1536076398-sup-1193@lrrr.local> The migration of Zuul project settings for the barbican repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/barbican - openstack/barbican-specs - openstack/barbican-tempest-plugin - openstack/castellan-ui - openstack/python-barbicanclient From doug at doughellmann.com Wed Sep 5 13:48:22 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 05 Sep 2018 09:48:22 -0400 Subject: [OpenStack-Infra] [goals][python3][adjutant] starting zuul migration for adjutant In-Reply-To: <1535716657-sup-8713@lrrr.local> References: <1535716657-sup-8713@lrrr.local> Message-ID: <1536155288-sup-1778@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-31 07:57:42 -0400: > The migration of Zuul project settings for the > adjutant repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/adjutant > - openstack/adjutant-ui > - openstack/python-adjutantclient The import patches have all merged and we are ready to approve https://review.openstack.org/#/c/598620/ From doug at doughellmann.com Wed Sep 5 13:50:22 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Wed, 05 Sep 2018 09:50:22 -0400 Subject: [OpenStack-Infra] [goals][python3][release] ready to proceed with release team zuul cleanup Message-ID: <1536155377-sup-1051@lrrr.local> The release team has approved all of the zuul migration patches and we are ready to proceed with approving https://review.openstack.org/#/c/598314/ Doug From ianyrchoi at gmail.com Thu Sep 6 02:06:34 2018 From: ianyrchoi at gmail.com (Ian Y. Choi) Date: Thu, 6 Sep 2018 11:06:34 +0900 Subject: [OpenStack-Infra] [storyboard] [I18n] Can Storyboard web pages be translatable to multiple languages? Message-ID: Hello, I wanna ask whether https://storyboard.openstack.org/ web pages can be translatable to multiple languages (e.g., Chinese, Japanese, Korean, German, French, Spanish, ...) or not. I have thought such idea on my mind from some time period ago, and I think now would be a good timing for raising this question since it seems that more project repositories are migrating to Storyboard, and internationalization of Storyboard is one of criteria for I18n team to decide to migrate to Storyboard (FYI: discussion on I18n team - [1]). From my very brief investigation, it seems that adding I18n support on html pages like [2], extracting translation source strings to pot files, syncing with Zanata [3] with powerful infra support [4] would make Storyboard translatable with translating to multiple languages by I18n team. Am I understanding correctly and can I18n team get help on such effort? With many thanks, /Ian [1] http://lists.openstack.org/pipermail/openstack-i18n/2018-September/003307.html [2] http://git.openstack.org/cgit/openstack-infra/storyboard-webclient/tree/src/app/stories/template/list.html#n26 [3] http://translate.openstack.org/ [4] https://docs.openstack.org/i18n/latest/infra.html From nguyentrihai93 at gmail.com Thu Sep 6 11:30:16 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 6 Sep 2018 20:30:16 +0900 Subject: [OpenStack-Infra] [senlin][goal][python3] beginning zuul migration for senlin In-Reply-To: References: Message-ID: Please process this: https://review.openstack.org/#/c/597502/ On Wed, Aug 29, 2018 at 9:44 PM Nguyễn Trí Hải wrote: > The migration of Zuul project settings for the > senlin repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/python-senlinclient > - openstack/senlin > - openstack/senlin-dashboard > - openstack/senlin-tempest-plugin > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Sep 6 17:33:19 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 6 Sep 2018 17:33:19 +0000 Subject: [OpenStack-Infra] [OpenStack-I18n] [storyboard] [I18n] Can Storyboard web pages be translatable to multiple languages? In-Reply-To: References: Message-ID: <20180906173318.7z5ojmvgfieq6jq6@yuggoth.org> On 2018-09-06 11:06:34 +0900 (+0900), Ian Y. Choi wrote: > I wanna ask whether https://storyboard.openstack.org/ web pages > can be translatable to multiple languages (e.g., Chinese, > Japanese, Korean, German, French, Spanish, ...) or not. [...] As also discussed in #storyboard I think this is an interesting idea, particularly for organizations who may want to use StoryBoard deployments where most users are fluent in one of those other languages (and perhaps not at all with English). I do think interface translation is potentially useful for the OpenStack community's storyboard.openstack.org service too, though we'll want to keep in mind that for most of the projects hosted there English is explicitly preferred to increase collaboration (same as with most OpenStack community mailing lists, IRC channels, code review and so on). We may discover that we need to find ways to point out to people, particularly those arriving there for the first time, that they should file stories in English if at all possible even though the interface may be presented in their personally preferred language instead. I've added this topic to https://etherpad.openstack.org/p/sb-stein-ptg-planning and am looking forward to seeing you in Denver! -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From tim.okonski at broadcom.com Tue Sep 4 23:36:31 2018 From: tim.okonski at broadcom.com (Tim O'Konski) Date: Tue, 4 Sep 2018 16:36:31 -0700 Subject: [OpenStack-Infra] I need to be re-instated (I only have a openstack community user ID, currently) with industry access as per my company co-worker Message-ID: Dear OpenStack Infra Team: As I'm helping Angela Smith, my co-worker at Broadcom with updating the CI setup, I need to be given back my membership status on the Infra Team of OpenStack. For example: https://review.openstack.org/#/admin/groups/10,members My name isn't here, however when I go to look at my login, this is here: All looks well here (i.e. just above). Can you please add me back in to the industry members list? Andy an other missing capabilities? Also, if there are any sample (i.e. working, with the large number of configuration parameters filled in with a working CI) that you can give me access to, it would be very much appreciated as there is out of date/misleading documentation on the site currently (i.e. for example: https://docs.openstack.org/infra/system-config/running-your-own.html That currently has a large warning indication box at the top: Running your own CI infrastructure UPDATED: 2018-09-03 21:43 Warning Parts of this file are out of date What parts? I find no versioning or other indicators as to the spurious and/or incorrect information. How do other's go about the process of creating a new (i.e. Zuul 2) CI? *- Tim O'Konski / Senior Software Engineer / Broadcom / tim.okonski at broadcom.com * PS We had a long running (and one of the most consistent) CI's running back when we were working for Brocade before we were acquired by Broadcom. -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image.png Type: image/png Size: 213326 bytes Desc: not available URL: From doug at doughellmann.com Thu Sep 6 18:47:24 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 06 Sep 2018 14:47:24 -0400 Subject: [OpenStack-Infra] [goals][python3][kolla] ready to proceed with cleanup for kolla Message-ID: <1536259622-sup-2580@lrrr.local> The kolla team has approved all of their zuul migration imports and we are ready to proceed with approving https://review.openstack.org/#/c/597590/ Doug From doug at doughellmann.com Thu Sep 6 18:48:19 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Thu, 06 Sep 2018 14:48:19 -0400 Subject: [OpenStack-Infra] [goals][python3][ec2-api] ready to proceed with cleanup for ec2-api Message-ID: <1536259680-sup-1809@lrrr.local> The ec2-api team has merged all of their zuul migration import patches and we are ready to approve https://review.openstack.org/#/c/597582/ From cboylan at sapwetik.org Thu Sep 6 18:54:24 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 06 Sep 2018 11:54:24 -0700 Subject: [OpenStack-Infra] I need to be re-instated (I only have a openstack community user ID, currently) with industry access as per my company co-worker In-Reply-To: References: Message-ID: <1536260064.3978302.1499324800.666BB579@webmail.messagingengine.com> On Tue, Sep 4, 2018, at 4:36 PM, Tim O'Konski wrote: > Dear OpenStack Infra Team: > > > As I'm helping Angela Smith, my co-worker at Broadcom with updating the CI > setup, I need to be given back my membership status on the Infra Team of > OpenStack. For example: > > https://review.openstack.org/#/admin/groups/10,members This group is for first party OpenStack community infrastructure CI tools. Upstream Zuul and previously Upstream Jenkins for example. All registered users are allowed to comment on any change but if you want to leave +/-1 Verified votes as a third party CI you will need to negotiate those permissions with the individual projects you are reporting to. When they are happy with your results they add your account to the project specific CI groups like https://review.openstack.org/#/admin/groups/511,members to enable that. > > My name isn't here, however when I go to look at my login, this is here: > > > > > All looks well here (i.e. just above). > > Can you please add me back in to the industry members list? Andy an other > missing capabilities? As mentioned above you should be good to start reporting, you'll just have to vote Verified 0 until the target projects are comfortable giving you greater vote permissions. Typically a good idea to communicate with the projects either way so that they understand what you are testing. > > Also, if there are any sample (i.e. working, with the large number of > configuration parameters filled in with a working CI) that you can give me > access to, it would be very much appreciated as there is out of > date/misleading documentation on the site currently (i.e. for example: > > https://docs.openstack.org/infra/system-config/running-your-own.html > > That currently has a large warning indication box at the top: > > Running your own CI infrastructure > > > > UPDATED: 2018-09-03 21:43 > > > Warning > > Parts of this file are out of date > What parts? I find no versioning or other indicators as to the spurious > and/or incorrect information. > > How do other's go about the process of creating a new (i.e. Zuul 2) CI? https://docs.openstack.org/infra/system-config/third_party.html should be mostly up to date docs (especially for zuulv2) third party testing setup docs. Hope this helps, Clark From nguyentrihai93 at gmail.com Fri Sep 7 11:20:12 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Fri, 7 Sep 2018 20:20:12 +0900 Subject: [OpenStack-Infra] starting zuul migration for watcher team repositories In-Reply-To: References: Message-ID: All the "import zuul job settings from project-config" patches in watcher repositories are merged. Please process this: https://review.openstack.org/#/c/593340/ On Sun, Aug 19, 2018 at 1:09 AM Nguyễn Trí Hải wrote: > The Zuul project settings for the watcher repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-watcherclient > - openstack/watcher > - openstack/watcher-dashboard > - openstack/watcher-specs > - openstack/watcher-tempest-plugin > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Fri Sep 7 17:44:39 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 07 Sep 2018 10:44:39 -0700 Subject: [OpenStack-Infra] PTG team dinner Message-ID: <1536342279.2183317.1500497176.7A7B0D93@webmail.messagingengine.com> Hello Infra, Looking at some of the other evening items scheduled for the PTG, I think our best bet will be Monday evening. We will be heading to the Lowry Beer Garden. This beer garden requires a car ride to get to, so we can meet in the lobby of the PTG hotel and group up for taxi/uber/lyft travel. Let's meet at 6pm. This venue worked great in the past for large groups, we should be able to walk right in and grab a row of tables. Food is counter service and we'll be on our own for that but prices are reasonable. Finally, weather looks great too. Excited to see you all there, Clark From kennelson11 at gmail.com Fri Sep 7 21:07:42 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Fri, 7 Sep 2018 14:07:42 -0700 Subject: [OpenStack-Infra] [Storyboard] PTG Planning & Upcoming Meeting Cancelled Message-ID: Hello! With the PTG in just a few days, I wanted to give some info and updates so that you are prepared. 1. This coming week's regular meeting on Wednesday will be cancelled. 2. I am planning on booking Blanca Peak for the whole afternoon on Tuesday for discussions. Just waiting for this patch to merge[0]. If we need more time we can schedule something later in the week. See you there! 3. Here [1] is the etherpad that we've been collecting discussion topics into. If there is anything you want to add, feel free. -Kendall (diablo_rojo) [0] https://review.openstack.org/#/c/600665/ [1]https://etherpad.openstack.org/p/sb-stein-ptg-planning -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Sun Sep 9 03:13:54 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Sat, 08 Sep 2018 21:13:54 -0600 Subject: [OpenStack-Infra] [goals][python3][qa] starting zuul migration for qa team Message-ID: <1536462827-sup-9185@lrrr.local> The migration of Zuul project settings for the Quality Assurance repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack-dev/bashate - openstack-dev/devstack - openstack-dev/devstack-plugin-cookiecutter - openstack-dev/devstack-vagrant - openstack-dev/grenade - openstack-dev/hacking - openstack/coverage2sql - openstack/devstack-plugin-ceph - openstack/devstack-plugin-container - openstack/devstack-tools - openstack/eslint-config-openstack - openstack/karma-subunit-reporter - openstack/openstack-health - openstack/os-performance-tools - openstack/os-testr - openstack/patrole - openstack/qa-specs - openstack/stackviz - openstack/tempest - openstack/tempest-lib - openstack/tempest-plugin-cookiecutter - openstack/tempest-stress From doug at doughellmann.com Sun Sep 9 17:19:03 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Sun, 09 Sep 2018 11:19:03 -0600 Subject: [OpenStack-Infra] [goals][python3][cinder] starting zuul migration for cinder Message-ID: <1536513540-sup-9007@lrrr.local> The migration of Zuul project settings for the cinder repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/cinder - openstack/cinder-specs - openstack/cinder-tempest-plugin - openstack/os-brick - openstack/python-brick-cinderclient-ext - openstack/python-cinderclient From adam at sotk.co.uk Mon Sep 10 13:43:18 2018 From: adam at sotk.co.uk (Adam Coldrick) Date: Mon, 10 Sep 2018 14:43:18 +0100 Subject: [OpenStack-Infra] [StoryBoard] Project Update/Some New Things Message-ID: <1536586998.2089.20.camel@sotk.co.uk> Hi all, Its been a long while since a "project update" type email about StoryBoard, but over the past few months we merged some patches which either are worth mentioning or changed things in ways that would benefit from some explanation. # Linking to projects by name Keen observers might've noticed that StoryBoard recently grew the ability to link to projects by name, rather than by ID number. All the links to projects in the UI have been replaced with links in this form, and its probably a good idea for folk to start using them in any documentation they have. These links look like https://storyboard.openstack.org/#!/project/openstack-infra/storyboard # Linking to project groups by name More recently (yesterday) it also became possible to similarly link to project groups by name rather than ID number. Links to project groups in the UI have been replaced with links in this form, and again if you have any documentation using the ID links it might be nice to update to using the name. These links look like https://storyboard.openstack.org/#!/project_group/storyboard # Finding stories from a task ID It is now possible to navigate to a story given just a task ID, if for whatever reason that's all the information you have available. A link like https://storyboard.openstack.org/#!/task/12389 will work. This will redirect to the story containing the task, and is the first part of work to support linking directly to an individual task in a story. # UI updates There have been some visual changes in the webclient's user interface to attempt to make things generally feel nicer. This work is also not totally finished and there are further changes planned. One big change is that the "Profile" button in the sidebar used for setting preferences and managing access tokens has gone away. The URLs used to access this functionality are unchanged, but the links in the UI can now be found by clicking the user name in the top-right to open the dropdown menu, which previously only contained the log out button. # Bugfixes Various minor bugs and annoyances have also been addressed. For example search should behave somewhat more predictably than it did at the start of the year, syntax highlighting actually works again, and the markdown parser should be less aggressive in its swallowing of line breaks. Stay tuned in the future for more fixes and features, and feel free to pop into #storyboard with any questions or comments you may have. We're always open to suggestions and even more open to patches! We also have a PTG session on Tuesday afternoon, currently intended to be in Blanca Peak. Feel free to drop by to join the discussions and/or add to the etherpad[0]. Best regards, Adam (SotK) [0]: https://etherpad.openstack.org/p/sb-stein-ptg-planning From fungi at yuggoth.org Mon Sep 10 14:34:49 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 10 Sep 2018 14:34:49 +0000 Subject: [OpenStack-Infra] [StoryBoard] Project Update/Some New Things In-Reply-To: <1536586998.2089.20.camel@sotk.co.uk> References: <1536586998.2089.20.camel@sotk.co.uk> Message-ID: <20180910143449.ycbttjla2tn4ysql@yuggoth.org> On 2018-09-10 14:43:18 +0100 (+0100), Adam Coldrick wrote: [...] > # Linking to projects by name > > Keen observers might've noticed that StoryBoard recently grew the ability > to link to projects by name, rather than by ID number. All the links to > projects in the UI have been replaced with links in this form, and its > probably a good idea for folk to start using them in any documentation > they have. These links look like > > https://storyboard.openstack.org/#!/project/openstack-infra/storyboard [...] Worth noting, this has made it harder to find the numeric project ID without falling back on the API. Change https://review.openstack.org/600893 merged to the releases repository yesterday allowing deliverable repositories to be referenced by their StoryBoard project name rather than only the ID number. If there are other places in tooling and automation where we relied on the project ID number, work should be done to update those similarly. > # Finding stories from a task ID > > It is now possible to navigate to a story given just a task ID, if for > whatever reason that's all the information you have available. A link like > > https://storyboard.openstack.org/#!/task/12389 > > will work. This will redirect to the story containing the task, and is the > first part of work to support linking directly to an individual task in a > story. [...] As an aside, I think this makes it possible now for us to start hyperlinking Task footers in commit messages within the Gerrit change view. I'll try and figure out what we need to adjust in our Gerrit commentlink and its-storyboard plugin configs to make that happen. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From doug at doughellmann.com Mon Sep 10 15:18:58 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Mon, 10 Sep 2018 09:18:58 -0600 Subject: [OpenStack-Infra] [sig][goal][python3] starting zuul migration for SIG repos In-Reply-To: <1534798936-sup-7767@lrrr.local> References: <1534798936-sup-7767@lrrr.local> Message-ID: <1536592699-sup-6941@lrrr.local> Excerpts from Doug Hellmann's message of 2018-08-20 17:02:39 -0400: > The migration of Zuul project settings for the > SIG repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/governance-sigs > - openstack/anchor > - openstack/ossa > - openstack/security-analysis > - openstack/security-doc > - openstack/security-specs > - openstack/syntribos > - openstack/syntribos-openstack-templates > - openstack/syntribos-payloads > - openstack/self-healing-sig > - openstack/operations-guide > - openstack/api-sig All of the import patches for these repositories have merged and we are ready to approve the cleanup patch https://review.openstack.org/#/c/598360 From doug at doughellmann.com Mon Sep 10 19:49:33 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Mon, 10 Sep 2018 13:49:33 -0600 Subject: [OpenStack-Infra] [goals][python3][nova] starting zuul migration for nova Message-ID: <1536608970-sup-6603@lrrr.local> The migration of Zuul project settings for the nova repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/nova - openstack/nova-specs - openstack/os-traits - openstack/os-vif - openstack/osc-placement - openstack/placement - openstack/python-novaclient From doug at doughellmann.com Tue Sep 11 12:23:46 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 11 Sep 2018 06:23:46 -0600 Subject: [OpenStack-Infra] [goals][python3][trove] starting zuul migration for trove Message-ID: <1536668622-sup-439@lrrr.local> The migration of Zuul project settings for the trove repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/python-troveclient - openstack/trove - openstack/trove-dashboard - openstack/trove-specs - openstack/trove-tempest-plugin From kennelson11 at gmail.com Tue Sep 11 17:47:13 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Tue, 11 Sep 2018 11:47:13 -0600 Subject: [OpenStack-Infra] [Storyboard] PTG Planning & Upcoming Meeting Cancelled In-Reply-To: References: Message-ID: Update! We will be in Vail this afternoon. Lunch ends at 1:30 so we hope to be starting conversations by 1:45. -Kendall (diablo_rojo) On Fri, Sep 7, 2018 at 2:07 PM Kendall Nelson wrote: > Hello! > > With the PTG in just a few days, I wanted to give some info and updates so > that you are prepared. > > 1. This coming week's regular meeting on Wednesday will be cancelled. > > 2. I am planning on booking Blanca Peak for the whole afternoon on Tuesday > for discussions. Just waiting for this patch to merge[0]. If we need more > time we can schedule something later in the week. See you there! > > 3. Here [1] is the etherpad that we've been collecting discussion topics > into. If there is anything you want to add, feel free. > > -Kendall (diablo_rojo) > > [0] https://review.openstack.org/#/c/600665/ > [1]https://etherpad.openstack.org/p/sb-stein-ptg-planning > -------------- next part -------------- An HTML attachment was scrubbed... URL: From doug at doughellmann.com Tue Sep 11 20:46:09 2018 From: doug at doughellmann.com (Doug Hellmann) Date: Tue, 11 Sep 2018 14:46:09 -0600 Subject: [OpenStack-Infra] [goals][python3][charms] starting migration for charms team Message-ID: <1536698762-sup-6494@lrrr.local> The migration of Zuul project settings for the OpenStack Charms repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/charm-aodh - openstack/charm-barbican - openstack/charm-barbican-softhsm - openstack/charm-ceilometer - openstack/charm-ceilometer-agent - openstack/charm-ceph - openstack/charm-ceph-fs - openstack/charm-ceph-mon - openstack/charm-ceph-osd - openstack/charm-ceph-proxy - openstack/charm-ceph-radosgw - openstack/charm-cinder - openstack/charm-cinder-backup - openstack/charm-cinder-ceph - openstack/charm-cloudkitty - openstack/charm-deployment-guide - openstack/charm-designate - openstack/charm-designate-bind - openstack/charm-glance - openstack/charm-glance-simplestreams-sync - openstack/charm-glusterfs - openstack/charm-gnocchi - openstack/charm-guide - openstack/charm-hacluster - openstack/charm-heat - openstack/charm-interface-bgp - openstack/charm-interface-bind-rndc - openstack/charm-interface-ceph-client - openstack/charm-interface-ceph-mds - openstack/charm-interface-designate - openstack/charm-interface-gnocchi - openstack/charm-interface-hacluster - openstack/charm-interface-keystone - openstack/charm-interface-keystone-admin - openstack/charm-interface-keystone-credentials - openstack/charm-interface-keystone-domain-backend - openstack/charm-interface-manila-plugin - openstack/charm-interface-mysql-shared - openstack/charm-interface-neutron-plugin - openstack/charm-interface-neutron-plugin-api-subordinate - openstack/charm-interface-odl-controller-api - openstack/charm-interface-openstack-ha - openstack/charm-interface-ovsdb-manager - openstack/charm-interface-rabbitmq - openstack/charm-interface-service-control - openstack/charm-ironic - openstack/charm-keystone - openstack/charm-keystone-ldap - openstack/charm-layer-ceph-base - openstack/charm-layer-openstack - openstack/charm-layer-openstack-api - openstack/charm-layer-openstack-principle - openstack/charm-lxd - openstack/charm-manila - openstack/charm-manila-generic - openstack/charm-manila-glusterfs - openstack/charm-mistral - openstack/charm-murano - openstack/charm-neutron-api - openstack/charm-neutron-api-genericswitch - openstack/charm-neutron-api-odl - openstack/charm-neutron-dynamic-routing - openstack/charm-neutron-gateway - openstack/charm-neutron-openvswitch - openstack/charm-nova-cloud-controller - openstack/charm-nova-compute - openstack/charm-nova-compute-proxy - openstack/charm-odl-controller - openstack/charm-openstack-dashboard - openstack/charm-openvswitch-odl - openstack/charm-panko - openstack/charm-percona-cluster - openstack/charm-rabbitmq-server - openstack/charm-specs - openstack/charm-swift-proxy - openstack/charm-swift-storage - openstack/charm-tempest - openstack/charm-trove - openstack/charms.ceph - openstack/charms.openstack From cboylan at sapwetik.org Wed Sep 12 21:26:09 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Wed, 12 Sep 2018 14:26:09 -0700 Subject: [OpenStack-Infra] Continued discussion of Winterscale naming In-Reply-To: <1535566015.1818990.1490374560.5A36A045@webmail.messagingengine.com> References: <20180821183306.yy72bamjfhttxnec@yuggoth.org> <1535566015.1818990.1490374560.5A36A045@webmail.messagingengine.com> Message-ID: <1536787569.2960018.1506136224.5BAC2590@webmail.messagingengine.com> On Wed, Aug 29, 2018, at 11:06 AM, Clark Boylan wrote: > On Tue, Aug 21, 2018, at 11:33 AM, Jeremy Stanley wrote: > > The Infra team has been brainstorming and collecting feedback in > > https://etherpad.openstack.org/p/infra-services-naming as to what > > actual name/domain the Winterscale effort will use. If you've not > > been following along, the earlier discussions can be found in the > > following mailing list threads: > > > > http://lists.openstack.org/pipermail/openstack-infra/2018-May/005957.html > > http://lists.openstack.org/pipermail/openstack-infra/2018-July/006010.html > > > > So far the "short list" at the bottom of the pad seems to contain > > only one entry: OpenDev. > > > > The OpenStack Foundation has offered to let us take control of > > opendev.org for this purpose if we would like. They have it mainly > > as a defensive registration to protect the OpenDev Conference brand, > > but use a separate opendevconf.org domain for that at present. The > > opendev.org domain is just sitting parked on the same nameservers as > > openstack.org right now, not in use for anything. The brand itself > > has a positive connotation in the community so far, and the OpenDev > > Conferences share a lot of similar goals (bringing communities of > > people together to collaborate openly on design and development > > activities) so this even provides some useful synergy around the > > name and possible promotional tie-ins with the events if we like. > > > > I know lots of us are eager to move forward on the rebranding, so I > > wanted to wake this discussion back up and try to see if we can > > drive it to a conclusion. As we continue to take on hosting for > > additional large projects, having somewhere for them to send the > > contributors and users in their community which has a distinct > > identity unclouded by OpenStack itself will help make our services > > much more welcoming. If you don't particularly like the OpenDev idea > > or have alternatives you think might achieve greater consensus > > within our team and present a better image to our extended > > community, present and future, please update the above mentioned pad > > or follow up to this mailing list thread. Thanks! > > I am a fan of OpenDev. I think it gives a path forward that works for > the immediate future and long term. https://review.opendev.org seems > like a reasonable place to do code review for a project :) > > I do think it would be good to continue collecting input particularly > from those involved in the day to day infra activities. If we can reach > rough consensus over the next week or so that would give us the > opportunity to use time at the PTG to do a rough sketch of how we can > start "migrating" to the new name. > > Your feedback much appreciated. > It has been about 3 weeks and the feedback so far has largely been positive. The one concern we have seen raised is that this may be confusing with the OpenDev conference. Fungi makes a great argument that cross promoting between the conference and the development tooling can be a net positive since many of our goals overlap. Finding that argument compelling myself, and not seeing any counterarguments I think we should move forward with using the OpenDev name and opendev.org domain for the team and services that we host. Long story short let's go ahead and use this name and start making progress on this effort. Next stop: etherpad.opendev.org. Thank you, Clark From pabelanger at redhat.com Thu Sep 13 01:57:30 2018 From: pabelanger at redhat.com (Paul Belanger) Date: Wed, 12 Sep 2018 21:57:30 -0400 Subject: [OpenStack-Infra] Continued discussion of Winterscale naming In-Reply-To: <1536787569.2960018.1506136224.5BAC2590@webmail.messagingengine.com> References: <20180821183306.yy72bamjfhttxnec@yuggoth.org> <1535566015.1818990.1490374560.5A36A045@webmail.messagingengine.com> <1536787569.2960018.1506136224.5BAC2590@webmail.messagingengine.com> Message-ID: <20180913015730.GA15974@localhost.localdomain> On Wed, Sep 12, 2018 at 02:26:09PM -0700, Clark Boylan wrote: > On Wed, Aug 29, 2018, at 11:06 AM, Clark Boylan wrote: > > On Tue, Aug 21, 2018, at 11:33 AM, Jeremy Stanley wrote: > > > The Infra team has been brainstorming and collecting feedback in > > > https://etherpad.openstack.org/p/infra-services-naming as to what > > > actual name/domain the Winterscale effort will use. If you've not > > > been following along, the earlier discussions can be found in the > > > following mailing list threads: > > > > > > http://lists.openstack.org/pipermail/openstack-infra/2018-May/005957.html > > > http://lists.openstack.org/pipermail/openstack-infra/2018-July/006010.html > > > > > > So far the "short list" at the bottom of the pad seems to contain > > > only one entry: OpenDev. > > > > > > The OpenStack Foundation has offered to let us take control of > > > opendev.org for this purpose if we would like. They have it mainly > > > as a defensive registration to protect the OpenDev Conference brand, > > > but use a separate opendevconf.org domain for that at present. The > > > opendev.org domain is just sitting parked on the same nameservers as > > > openstack.org right now, not in use for anything. The brand itself > > > has a positive connotation in the community so far, and the OpenDev > > > Conferences share a lot of similar goals (bringing communities of > > > people together to collaborate openly on design and development > > > activities) so this even provides some useful synergy around the > > > name and possible promotional tie-ins with the events if we like. > > > > > > I know lots of us are eager to move forward on the rebranding, so I > > > wanted to wake this discussion back up and try to see if we can > > > drive it to a conclusion. As we continue to take on hosting for > > > additional large projects, having somewhere for them to send the > > > contributors and users in their community which has a distinct > > > identity unclouded by OpenStack itself will help make our services > > > much more welcoming. If you don't particularly like the OpenDev idea > > > or have alternatives you think might achieve greater consensus > > > within our team and present a better image to our extended > > > community, present and future, please update the above mentioned pad > > > or follow up to this mailing list thread. Thanks! > > > > I am a fan of OpenDev. I think it gives a path forward that works for > > the immediate future and long term. https://review.opendev.org seems > > like a reasonable place to do code review for a project :) > > > > I do think it would be good to continue collecting input particularly > > from those involved in the day to day infra activities. If we can reach > > rough consensus over the next week or so that would give us the > > opportunity to use time at the PTG to do a rough sketch of how we can > > start "migrating" to the new name. > > > > Your feedback much appreciated. > > > > It has been about 3 weeks and the feedback so far has largely been positive. The one concern we have seen raised is that this may be confusing with the OpenDev conference. Fungi makes a great argument that cross promoting between the conference and the development tooling can be a net positive since many of our goals overlap. > > Finding that argument compelling myself, and not seeing any counterarguments I think we should move forward with using the OpenDev name and opendev.org domain for the team and services that we host. > > Long story short let's go ahead and use this name and start making progress on this effort. Next stop: etherpad.opendev.org. > > Thank you, > Clark > +1 for etherpad.opendev.org - Paul From nguyentrihai93 at gmail.com Thu Sep 13 05:05:27 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 13 Sep 2018 14:05:27 +0900 Subject: [OpenStack-Infra] starting zuul migration for tacker team repositories In-Reply-To: References: Message-ID: Please process removing patch: https://review.openstack.org/#/c/593027/ On Fri, Aug 17, 2018 at 9:19 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the tacker repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-tackerclient > - openstack/tacker > - openstack/tacker-horizon > - openstack/tacker-specs > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Thu Sep 13 06:03:32 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Thu, 13 Sep 2018 15:03:32 +0900 Subject: [OpenStack-Infra] [goals][python3][karbor] starting migration for kabor team Message-ID: The migration of Zuul project settings for the OpenStack Charms repositories has begun. Please do not approve any changes to openstack-infra/project-config/zuul.d/projects.yaml for the following repositories: - openstack/karbor - openstack/karbor-dashboard - openstack/python-karborclient -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Mon Sep 17 01:14:13 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Mon, 17 Sep 2018 10:14:13 +0900 Subject: [OpenStack-Infra] [goal][python3][dragonflow] starting zuul migration for dragonflow In-Reply-To: References: Message-ID: We can process this: https://review.openstack.org/#/c/597475/ On Wed, Aug 29, 2018 at 9:34 PM Nguyễn Trí Hải wrote: > The migration of Zuul project settings for the > dragonflow repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/dragonflow > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Mon Sep 17 23:09:03 2018 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 17 Sep 2018 16:09:03 -0700 Subject: [OpenStack-Infra] Control Plane Server Upgrade Sprint Planning Message-ID: <1537225743.63161.1511445720.6BC69C13@webmail.messagingengine.com> Hello everyone, We still have a few Trusty servers hanging around. We should work to upgrade them either to Xenial (using puppet deployment) or Bionic (using ansible and containers?). We've made good progress in the past using a sprint type setup where the majority of us are focused on making progress on this sort of work. Can we plan another sprint to complete this task? Looking at a calendar I think many of us are still recovering from PTG travel this week, week after next is Ansiblefest, then I have a local Portland conference the week after that. Long story short October 15-19 may be our best week for this. Does that week work? Any other suggestions? I think we can (and should) work on this outside of the sprint as well and I will be trying to upgrade the etherpad servers in the near future. Let me know if you are working on upgrading any servers/services and I will do what I can to help review changes and make that happen as well. Thank you, Clark From nguyentrihai93 at gmail.com Tue Sep 18 06:14:39 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Tue, 18 Sep 2018 15:14:39 +0900 Subject: [OpenStack-Infra] starting zuul migration for masakari team repositories In-Reply-To: References: Message-ID: It's ready to process: https://review.openstack.org/#/c/592992/ On Fri, Aug 17, 2018 at 9:20 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the masakari repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/masakari > - openstack/masakari-dashboard > - openstack/masakari-monitors > - openstack/masakari-specs > - openstack/python-masakariclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Tue Sep 18 14:09:45 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Tue, 18 Sep 2018 23:09:45 +0900 Subject: [OpenStack-Infra] [blazar][goal][python3] starting zuul migration for blazar In-Reply-To: References: Message-ID: Please process this: https://review.openstack.org/#/c/596250/ Thanks. On Fri, Aug 24, 2018 at 5:06 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the blazar repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/blazar > - openstack/blazar-dashboard > - openstack/blazar-nova > - openstack/blazar-tempest-plugin > - openstack/python-blazarclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From iwienand at redhat.com Tue Sep 18 19:48:50 2018 From: iwienand at redhat.com (Ian Wienand) Date: Wed, 19 Sep 2018 05:48:50 +1000 Subject: [OpenStack-Infra] Control Plane Server Upgrade Sprint Planning In-Reply-To: <1537225743.63161.1511445720.6BC69C13@webmail.messagingengine.com> References: <1537225743.63161.1511445720.6BC69C13@webmail.messagingengine.com> Message-ID: <20180918194849.GB1239@fedora19.localdomain> On Mon, Sep 17, 2018 at 04:09:03PM -0700, Clark Boylan wrote: > October 15-19 may be our best week for this. Does that week work? Post school-holidays here so SGTM :) > Let me know if you are working on upgrading any servers/services and > I will do what I can to help review changes and make that happen as > well. I will start on graphite.o.o as I now have some experience getting it listening on ipv6 :) I think it's mostly package install and few templating bits, ergo it might work well as ansible roles (i.e. don't have to rewrite tricky logic). I'll see how it starts to look ... -i From joshua.hesketh at gmail.com Wed Sep 19 01:02:20 2018 From: joshua.hesketh at gmail.com (Joshua Hesketh) Date: Wed, 19 Sep 2018 11:02:20 +1000 Subject: [OpenStack-Infra] Control Plane Server Upgrade Sprint Planning In-Reply-To: <1537225743.63161.1511445720.6BC69C13@webmail.messagingengine.com> References: <1537225743.63161.1511445720.6BC69C13@webmail.messagingengine.com> Message-ID: On Tue, Sep 18, 2018 at 9:09 AM Clark Boylan wrote: > Hello everyone, > > We still have a few Trusty servers hanging around. We should work to > upgrade them either to Xenial (using puppet deployment) or Bionic (using > ansible and containers?). We've made good progress in the past using a > sprint type setup where the majority of us are focused on making progress > on this sort of work. Can we plan another sprint to complete this task? > > Looking at a calendar I think many of us are still recovering from PTG > travel this week, week after next is Ansiblefest, then I have a local > Portland conference the week after that. Long story short October 15-19 may > be our best week for this. Does that week work? Any other suggestions? > FYI I'm on vacation most of October so will only be around very intermittently and unable to help sorry. > I think we can (and should) work on this outside of the sprint as well and > I will be trying to upgrade the etherpad servers in the near future. Let me > know if you are working on upgrading any servers/services and I will do > what I can to help review changes and make that happen as well. > > Thank you, > Clark > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra -------------- next part -------------- An HTML attachment was scrubbed... URL: From bokke at google.com Wed Sep 19 15:54:40 2018 From: bokke at google.com (David van der Bokke) Date: Wed, 19 Sep 2018 08:54:40 -0700 Subject: [OpenStack-Infra] git-review tagging schedule In-Reply-To: References: <20180822181855.ctuepr6ahiblt2ij@yuggoth.org> Message-ID: Checking to see when this is going to get tagged? Thanks On Tue, Aug 28, 2018 at 9:23 AM David van der Bokke wrote: > So it looks like the gerrit team is actually waiting for this to get to > tagged before putting the refs/publish removal into a new release but would > like to do it before the end of the quarter. > > On Wed, Aug 22, 2018 at 11:20 AM Jeremy Stanley wrote: > >> On 2018-08-22 10:11:20 -0700 (-0700), David van der Bokke wrote: >> > Thanks Jeremy. I am trying to get an exact date from the Gerrit >> > team, but I can say that tagging/releasing a new git-review is a >> > likely precursor given that the team had actually removed the ref >> > and subsequently reverted the change after discovering that >> > git-review needed an update for it. >> >> Thanks! That definitely helps. When they added it in Gerrit 2.3 >> the release notes[*] indicated refs/for was deprecated, so the >> update proposed to git-review to switch back was really the first >> we'd heard of it being un-deprecated again (I'm not finding a >> similar release note about it, and the ACLs release note in 2.16 >> about refs/for still talks about people using refs/publish too). >> >> [*] >> https://gerrit.googlesource.com/gerrit/+/v2.15.3/ReleaseNotes/ReleaseNotes-2.3.txt#21 >> -- >> Jeremy Stanley >> _______________________________________________ >> OpenStack-Infra mailing list >> OpenStack-Infra at lists.openstack.org >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Wed Sep 19 16:09:55 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 19 Sep 2018 16:09:55 +0000 Subject: [OpenStack-Infra] git-review tagging schedule In-Reply-To: References: <20180822181855.ctuepr6ahiblt2ij@yuggoth.org> Message-ID: <20180919160954.ska7tjl72livjmx3@yuggoth.org> On 2018-09-19 08:54:40 -0700 (-0700), David van der Bokke wrote: > Checking to see when this is going to get tagged? Thanks [...] Ironically, we were discussing it in IRC (#openstack-infra on Freenode) just as you sent this. We're trying to work out whether https://review.openstack.org/601251 should probably be included for similar reasons, but otherwise are ready to release it in the next hour or so I think. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From fungi at yuggoth.org Wed Sep 19 18:08:43 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 19 Sep 2018 18:08:43 +0000 Subject: [OpenStack-Infra] git-review tagging schedule In-Reply-To: <20180919160954.ska7tjl72livjmx3@yuggoth.org> References: <20180822181855.ctuepr6ahiblt2ij@yuggoth.org> <20180919160954.ska7tjl72livjmx3@yuggoth.org> Message-ID: <20180919180843.dppz3xljzg6unmto@yuggoth.org> On 2018-09-19 16:09:55 +0000 (+0000), Jeremy Stanley wrote: > On 2018-09-19 08:54:40 -0700 (-0700), David van der Bokke wrote: > > Checking to see when this is going to get tagged? Thanks > [...] > > Ironically, we were discussing it in IRC (#openstack-infra on > Freenode) just as you sent this. We're trying to work out whether > https://review.openstack.org/601251 should probably be included for > similar reasons, but otherwise are ready to release it in the next > hour or so I think. We got the simplest and/or most urgent changes flushed into the master branch and released git-review 1.27.0 a few moments ago. As usual, signed Python packages for it can be found at http://tarballs.openstack.org/git-review/ and it's also the current version served from https://pypi.org/project/git-review/ at this point. There are still quite a few other pending improvements under review we'd like to wrap into another release very soon, but this should at least un-block the transition in Gerrit. Thanks again for taking git-review's behaviors into account when deprecating functionality in Gerrit (it's very much appreciated!), and apologies the release discussions dragged on a bit. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From kennelson11 at gmail.com Thu Sep 20 21:15:25 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Thu, 20 Sep 2018 14:15:25 -0700 Subject: [OpenStack-Infra] [StoryBoard] PTG Summary Message-ID: Hello Lovers of Task Tracking! So! We talked about a lot of things, and I went to a lot of rooms to talk about StoryBoard related things and it was already a week ago so bear with me. We had a lot of good discussions as we were able to include SotK in discussions via videocalling. We also had the privilege of our outreachy intern to come all the way from Cairo to Denver to join us :) Onto the summaries! Story Attachments ============== This topic has started coming up with increasing regularity. Currently, StoryBoard doesn’t support attachments, but it’s a feature that several projects claim to be blocking their migration. The current work around is either to trim down logs and paste the relevant section, or to host the file elsewhere and link to its location. After consulting with the infrastructure team, we concluded that currently, there is no donated storage. The next step is for me to draft a spec detailing our requirements and implementation details and then to include infra on the review to help them have something concrete to go to vendors with. For notes on the proposed method see the etherpad[1]. One other thing discussed during this topic was how we could maybe migrate the current attachments. This isn’t supported by the migration script at this point, but it’s something we could write a separate script for. It should be separate because it would be a painfully slow process and we wouldn’t want to slow down the migration script more than it already is by the Launchpad API. The attachments script would be run after the initial migration; that being said, everything still persists in Launchpad so things can still be referenced there. Handling Duplicate Stories ==================== This is also an ongoing topic for discussion. Duplicate stories if not handled properly could dilute the database as we get more projects migrated over. The plan we settled on is to add a ‘Mark as Duplicate’ button to the webclient and corresponding functions to the API. The user would be prompted for a link to the master story. The master story would get a new timeline event that would have the link to the duplicate and the duplicate story would have all tasks auto marked as invalid (aside from those marked as merged) so that the story then shows as inactive. The duplicate story could also get a timeline event that explains what happened and links to the master story. I’ve yet to create a story for all of this, but it’s on my todo list. Handling Thousands of Comments Per Story ================================== There’s this special flower story[2] that has literally thousands of comments on it because of all of the gerrit comments being added to the timeline for all the patches for all the tasks. Rendering of the timeline portion of the webpage in the webclient is virtually impossible. It will load the tasks and then hang forever. The discussion around this boiled down to this: other task trackers also can’t handle this and there is a better way to divvy up the story into several stories and contain them in a worklist for future, similar work. For now, users can select what they want to load in their timeline views for stories, so by unmarking all of the timeline events in their preferences, the story will load completely sans timeline details. Another solution we discussed to help alleviate the timeline load on stories with lots of tasks is to have a task field that links to the review, rather than a comment from gerrit every time a new patch gets pushed. Essentially we want to focus on cleaning up the timeline rather than just going straight to a pagination type of solution. It was also concluded that we want to add another user preference for page sizes of 1000. Tasks have not been created in the story related to this issue yet[3], but its on my todo list. Project Group Descriptions ===================== There was a request to have project group descriptions, but currently there is nothing in the API handling this. Discussion concluded with agreement that this shouldn’t be too difficult. All that needs to happen is a few additions to the API and the connection to managing group definitions in project-config. I still need to make a story for this. Translating storyboard-webclient ========================= There was an infrastructure mailing list thread a little while back that kicked off discussion on this topic. It was received as an interesting idea and could help with the adoption of StoryBoard outside of OpenStack. The biggest concern was communicating to users that are seeing the webclient rendered in some other language that they still need to create tasks/stories/worklists/boards in English or whatever the default language is for the organization that is hosting StoryBoard. This could be a banner when someone logs in, or something on user’s dashboards. One of the things that needs to happen first is to find libraries for javascript and angular for signaling what strings need to be translated. We didn’t really outline next steps past that as it’s not super high priority, but it’s definitely an effort we would support if someone wanted to start driving it forward. Easier Rollback for Webclient Continuous Deployment ========================================= With the puppet-storyboard module we deploy from tarballs instead of from git right now, and we don't preserve earlier tarballs which makes it difficult to rollback changes when we find issues. There wasn’t a ton of discussion besides, yes we need to figure this out. Pre-zuulv3 we uploaded tarballs with the git sha, if we apply that to publish-openstack-javascript-content, that might help the situation. Managing Project Coresec Groups ========================== The vast majority of work on private stories has been implemented. Stories can be marked as private and users can subscribe other users to those private stories so that only those people can see them. The only convenience that is currently lacking is adding groups of users (manually or automatically if in a template story). Groups of users are currently only managed by StoryBoard admins. We would like to make this managed in a repository or by proxying gerrit group management. This shouldn’t be too complicated a change, it would only require some sort of flag being set for a group definition and then some database migration to sync those groups into the StoryBoard database. If you have opinions on this topic, it’s not all set in stone and we would love to hear your thoughts! Searching ======== It’s become apparent that while the search and type ahead features of StoryBoard work better than most users think at first glance, it’s an issue that users struggle with searching as much as they do. We talked about possible solutions for this aside from writing documentation to cover searching in the webclient. The solution we talked about most was that it might be easier for our users if we used the gerrit query language as that is what the majority of our users are already familiar with. The next step here is to write a spec for using the gerrit query language- or some other language if users disagree about using the gerrit language. Show all OpenStack Repos in StoryBoard? ================================ Are we getting to the point where it would be helpful for the users of StoryBoard to be able to add tasks to stories for all the repos not already migrated to StoryBoard? This would be incredibly helpful for things like release goal tracking where many repos that haven’t been migrated had tasks that were assigned to governance instead of the actual repo so as to be able to track everything in a single story. This is something we will want to take up with the TC during a set of office hours in the next week or so. Summary & Continuing Conversations ============================= My brain is mush. Hopefully I covered the majority of the important topics and did them justice! Anyone that was there, please feel free to correct me. Anyone that wasn’t there that is interested in getting involved with any of this, please join us in #storyboard on IRC or email us with the [Storyboard] tag to the dev or infra mailing lists. We also have weekly meetings[4] on Wednesdays at 19:00 UTC, please join us! I've got a lot of stories to make/update and tasks to add.. Thanks! -Kendall Nelson (diablo_rojo) [1] https://etherpad.openstack.org/p/sb-stein-ptg-planning [2] https://storyboard.openstack.org/#!/story/2002586 [3] https://storyboard.openstack.org/#!/story/2003525 [4] http://eavesdrop.openstack.org/#StoryBoard_Meeting -------------- next part -------------- An HTML attachment was scrubbed... URL: From dangtrinhnt at gmail.com Fri Sep 21 02:28:43 2018 From: dangtrinhnt at gmail.com (Trinh Nguyen) Date: Fri, 21 Sep 2018 11:28:43 +0900 Subject: [OpenStack-Infra] [openstack-dev] [StoryBoard] PTG Summary In-Reply-To: References: Message-ID: Hi Kendall, I couldn't attend the PTG but those are exactly what I love to have in Storyboard, especially "Project Group Descriptions" and "Story Attachments". Thanks for the effort! *Trinh Nguyen *| Founder & Chief Architect *E:* dangtrinhnt at gmail.com | *W:* *www.edlab.xyz * On Fri, Sep 21, 2018 at 6:15 AM Kendall Nelson wrote: > Hello Lovers of Task Tracking! > > So! We talked about a lot of things, and I went to a lot of rooms to talk > about StoryBoard related things and it was already a week ago so bear with > me. > > We had a lot of good discussions as we were able to include SotK in > discussions via videocalling. We also had the privilege of our outreachy > intern to come all the way from Cairo to Denver to join us :) > > Onto the summaries! > > Story Attachments > > ============== > > This topic has started coming up with increasing regularity. Currently, > StoryBoard doesn’t support attachments, but it’s a feature that several > projects claim to be blocking their migration. The current work around is > either to trim down logs and paste the relevant section, or to host the > file elsewhere and link to its location. After consulting with the > infrastructure team, we concluded that currently, there is no donated > storage. The next step is for me to draft a spec detailing our requirements > and implementation details and then to include infra on the review to help > them have something concrete to go to vendors with. For notes on the > proposed method see the etherpad[1]. > > One other thing discussed during this topic was how we could maybe migrate > the current attachments. This isn’t supported by the migration script at > this point, but it’s something we could write a separate script for. It > should be separate because it would be a painfully slow process and we > wouldn’t want to slow down the migration script more than it already is by > the Launchpad API. The attachments script would be run after the initial > migration; that being said, everything still persists in Launchpad so > things can still be referenced there. > > Handling Duplicate Stories > > ==================== > > This is also an ongoing topic for discussion. Duplicate stories if not > handled properly could dilute the database as we get more projects migrated > over. The plan we settled on is to add a ‘Mark as Duplicate’ button to the > webclient and corresponding functions to the API. The user would be > prompted for a link to the master story. The master story would get a new > timeline event that would have the link to the duplicate and the duplicate > story would have all tasks auto marked as invalid (aside from those marked > as merged) so that the story then shows as inactive. The duplicate story > could also get a timeline event that explains what happened and links to > the master story. I’ve yet to create a story for all of this, but it’s on > my todo list. > > Handling Thousands of Comments Per Story > > ================================== > > There’s this special flower story[2] that has literally thousands of > comments on it because of all of the gerrit comments being added to the > timeline for all the patches for all the tasks. Rendering of the timeline > portion of the webpage in the webclient is virtually impossible. It will > load the tasks and then hang forever. The discussion around this boiled > down to this: other task trackers also can’t handle this and there is a > better way to divvy up the story into several stories and contain them in a > worklist for future, similar work. For now, users can select what they want > to load in their timeline views for stories, so by unmarking all of the > timeline events in their preferences, the story will load completely sans > timeline details. Another solution we discussed to help alleviate the > timeline load on stories with lots of tasks is to have a task field that > links to the review, rather than a comment from gerrit every time a new > patch gets pushed. Essentially we want to focus on cleaning up the timeline > rather than just going straight to a pagination type of solution. It was > also concluded that we want to add another user preference for page sizes > of 1000. Tasks have not been created in the story related to this issue > yet[3], but its on my todo list. > > Project Group Descriptions > > ===================== > > There was a request to have project group descriptions, but currently > there is nothing in the API handling this. Discussion concluded with > agreement that this shouldn’t be too difficult. All that needs to happen is > a few additions to the API and the connection to managing group definitions > in project-config. I still need to make a story for this. > > Translating storyboard-webclient > > ========================= > > There was an infrastructure mailing list thread a little while back that > kicked off discussion on this topic. It was received as an interesting idea > and could help with the adoption of StoryBoard outside of OpenStack. The > biggest concern was communicating to users that are seeing the webclient > rendered in some other language that they still need to create > tasks/stories/worklists/boards in English or whatever the default language > is for the organization that is hosting StoryBoard. This could be a banner > when someone logs in, or something on user’s dashboards. One of the things > that needs to happen first is to find libraries for javascript and angular > for signaling what strings need to be translated. We didn’t really outline > next steps past that as it’s not super high priority, but it’s definitely > an effort we would support if someone wanted to start driving it forward. > > Easier Rollback for Webclient Continuous Deployment > > ========================================= > > With the puppet-storyboard module we deploy from tarballs instead of from > git right now, and we don't preserve earlier tarballs which makes it > difficult to rollback changes when we find issues. There wasn’t a ton of > discussion besides, yes we need to figure this out. Pre-zuulv3 we uploaded > tarballs with the git sha, if we apply that to > publish-openstack-javascript-content, that might help the situation. > > Managing Project Coresec Groups > > ========================== > > The vast majority of work on private stories has been implemented. Stories > can be marked as private and users can subscribe other users to those > private stories so that only those people can see them. The only > convenience that is currently lacking is adding groups of users (manually > or automatically if in a template story). Groups of users are currently > only managed by StoryBoard admins. We would like to make this managed in a > repository or by proxying gerrit group management. This shouldn’t be too > complicated a change, it would only require some sort of flag being set for > a group definition and then some database migration to sync those groups > into the StoryBoard database. If you have opinions on this topic, it’s not > all set in stone and we would love to hear your thoughts! > > > Searching > > ======== > > It’s become apparent that while the search and type ahead features of > StoryBoard work better than most users think at first glance, it’s an issue > that users struggle with searching as much as they do. We talked about > possible solutions for this aside from writing documentation to cover > searching in the webclient. The solution we talked about most was that it > might be easier for our users if we used the gerrit query language as that > is what the majority of our users are already familiar with. The next step > here is to write a spec for using the gerrit query language- or some other > language if users disagree about using the gerrit language. > > > Show all OpenStack Repos in StoryBoard? > > ================================ > > Are we getting to the point where it would be helpful for the users of > StoryBoard to be able to add tasks to stories for all the repos not already > migrated to StoryBoard? This would be incredibly helpful for things like > release goal tracking where many repos that haven’t been migrated had tasks > that were assigned to governance instead of the actual repo so as to be > able to track everything in a single story. This is something we will want > to take up with the TC during a set of office hours in the next week or so. > > > Summary & Continuing Conversations > > ============================= > > My brain is mush. Hopefully I covered the majority of the important topics > and did them justice! Anyone that was there, please feel free to correct > me. Anyone that wasn’t there that is interested in getting involved with > any of this, please join us in #storyboard on IRC or email us with the > [Storyboard] tag to the dev or infra mailing lists. We also have weekly > meetings[4] on Wednesdays at 19:00 UTC, please join us! > > > I've got a lot of stories to make/update and tasks to add.. > > > Thanks! > > -Kendall Nelson (diablo_rojo) > > [1] https://etherpad.openstack.org/p/sb-stein-ptg-planning > > [2] https://storyboard.openstack.org/#!/story/2002586 > > [3] https://storyboard.openstack.org/#!/story/2003525 > > [4] http://eavesdrop.openstack.org/#StoryBoard_Meeting > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > -------------- next part -------------- An HTML attachment was scrubbed... URL: From angelgmartin at gmail.com Tue Sep 18 09:30:03 2018 From: angelgmartin at gmail.com (Angel Garcia) Date: Tue, 18 Sep 2018 11:30:03 +0200 Subject: [OpenStack-Infra] COA purchase Wrong redirection Message-ID: Hello, I'm trying to purchase a COA and when try to select the "Ubuntu" option , instead of redirect me to the right place always is opening the mail app (outlook, thunderbird, ..., etc) with the "info at openstack.org" set in the "To" place , so I can not purchase the exam . Sorry if it's not the right place to complain. Thanks in advance. Looking forward to hearing from you. Kind Regards, Angel -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Fri Sep 21 20:17:42 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Fri, 21 Sep 2018 20:17:42 +0000 Subject: [OpenStack-Infra] COA purchase Wrong redirection In-Reply-To: References: Message-ID: <20180921195948.f4zm2le7r6swau4l@yuggoth.org> On 2018-09-18 11:30:03 +0200 (+0200), Angel Garcia wrote: > I'm trying to purchase a COA and when try to select the "Ubuntu" option , > instead of redirect me to the right place always is opening the mail app > (outlook, thunderbird, ..., etc) with the "info at openstack.org" set in the > "To" place , so I can not purchase the exam . I'm told this was corrected yesterday and you should retry now if you have not already > Sorry if it's not the right place to complain. [...] According to the COA admins, info at openstack.org is the appropriate contact address for such matters (at least for now). -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From nguyentrihai93 at gmail.com Sat Sep 22 01:21:31 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Sat, 22 Sep 2018 10:21:31 +0900 Subject: [OpenStack-Infra] [tricircle][goal][python3] starting zuul migration for tricircle In-Reply-To: References: Message-ID: Please process the removing patch: https://review.openstack.org/#/c/596203/ On Fri, Aug 24, 2018 at 4:32 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the tricircle repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/python-tricircleclient > - openstack/tricircle > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From nguyentrihai93 at gmail.com Sun Sep 23 09:21:53 2018 From: nguyentrihai93 at gmail.com (=?UTF-8?B?Tmd1eeG7hW4gVHLDrSBI4bqjaQ==?=) Date: Sun, 23 Sep 2018 18:21:53 +0900 Subject: [OpenStack-Infra] [karbor][goal][python3] beginning zuul migration for karbor In-Reply-To: References: Message-ID: The removing patch is ready to process: https://review.openstack.org/#/c/594834/ On Wed, Aug 22, 2018 at 3:20 PM Nguyễn Trí Hải wrote: > The Zuul project settings for the karbor repositories > has begun. Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml for > the following repositories: > > - openstack/karbor > - openstack/karbor-dashboard > - openstack/python-karborclient > > -- > > Nguyen Tri Hai / Ph.D. Student > > ANDA Lab., Soongsil Univ., Seoul, South Korea > > > > *[image: > http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] > * > -- Nguyen Tri Hai / Ph.D. Student ANDA Lab., Soongsil Univ., Seoul, South Korea *[image: http://link.springer.com/chapter/10.1007/978-3-319-26135-5_4] * -------------- next part -------------- An HTML attachment was scrubbed... URL: From bachman at noironetworks.com Mon Sep 24 15:43:35 2018 From: bachman at noironetworks.com (Thomas Bachman) Date: Mon, 24 Sep 2018 11:43:35 -0400 Subject: [OpenStack-Infra] Tag deletion in upstream repo Message-ID: Hi all, Sorry for the list-wide distribution on this -- I wasn't sure where to start. I have a question about process/procedure. I've carelessly created a tag against the wrong branch in an upstream repo -- in this case, the 0.16.0 tag in the python-group-based-policy-client repo. Is there a process for tag deletion in upstream repos? cheers, -Thomas -------------- next part -------------- An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Mon Sep 24 16:56:53 2018 From: fungi at yuggoth.org (Jeremy Stanley) Date: Mon, 24 Sep 2018 16:56:53 +0000 Subject: [OpenStack-Infra] Tag deletion in upstream repo In-Reply-To: References: Message-ID: <20180924165652.j6ljn45wmvx2abee@yuggoth.org> On 2018-09-24 11:43:35 -0400 (-0400), Thomas Bachman wrote: > Sorry for the list-wide distribution on this -- I wasn't sure > where to start. I have a question about process/procedure. I've > carelessly created a tag against the wrong branch in an upstream > repo -- in this case, the 0.16.0 tag in the > python-group-based-policy-client repo. Is there a process for tag > deletion in upstream repos? One of the reasons we strongly remind project drivers to carefully check what they're tagging before pushing is that Git tags (aside from so-called "lightweight tags" which are really just symlinks) effectively aren't deletable. Consider them permanent once pushed. It's true that you _can_ delete a tag from a remote, but such deletions don't propagate via pull or remote update. As a result, downstream consumers who have pulled the tag in question (including our CI system) won't see the removal of that tag and will continue to behave as if it's still present. If at all possible, consider solutions which involve pushing an even newer tag in the wake of the accidental one, so that the previous tag will at least appear to be obsolete. -- Jeremy Stanley -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 963 bytes Desc: not available URL: From kennelson11 at gmail.com Thu Sep 27 20:04:28 2018 From: kennelson11 at gmail.com (Kendall Nelson) Date: Thu, 27 Sep 2018 13:04:28 -0700 Subject: [OpenStack-Infra] [StoryBoard] PTG Summary In-Reply-To: References: Message-ID: Updates! On Thu, Sep 20, 2018 at 2:15 PM Kendall Nelson wrote: > Hello Lovers of Task Tracking! > > So! We talked about a lot of things, and I went to a lot of rooms to talk > about StoryBoard related things and it was already a week ago so bear with > me. > > We had a lot of good discussions as we were able to include SotK in > discussions via videocalling. We also had the privilege of our outreachy > intern to come all the way from Cairo to Denver to join us :) > > Onto the summaries! > > Story Attachments > > ============== > > This topic has started coming up with increasing regularity. Currently, > StoryBoard doesn’t support attachments, but it’s a feature that several > projects claim to be blocking their migration. The current work around is > either to trim down logs and paste the relevant section, or to host the > file elsewhere and link to its location. After consulting with the > infrastructure team, we concluded that currently, there is no donated > storage. The next step is for me to draft a spec detailing our requirements > and implementation details and then to include infra on the review to help > them have something concrete to go to vendors with. For notes on the > proposed method see the etherpad[1]. > > One other thing discussed during this topic was how we could maybe migrate > the current attachments. This isn’t supported by the migration script at > this point, but it’s something we could write a separate script for. It > should be separate because it would be a painfully slow process and we > wouldn’t want to slow down the migration script more than it already is by > the Launchpad API. The attachments script would be run after the initial > migration; that being said, everything still persists in Launchpad so > things can still be referenced there. > > Handling Duplicate Stories > > ==================== > > This is also an ongoing topic for discussion. Duplicate stories if not > handled properly could dilute the database as we get more projects migrated > over. The plan we settled on is to add a ‘Mark as Duplicate’ button to the > webclient and corresponding functions to the API. The user would be > prompted for a link to the master story. The master story would get a new > timeline event that would have the link to the duplicate and the duplicate > story would have all tasks auto marked as invalid (aside from those marked > as merged) so that the story then shows as inactive. The duplicate story > could also get a timeline event that explains what happened and links to > the master story. I’ve yet to create a story for all of this, but it’s on > my todo list. > Turns out there is a story already[5]. > > Handling Thousands of Comments Per Story > > ================================== > > There’s this special flower story[2] that has literally thousands of > comments on it because of all of the gerrit comments being added to the > timeline for all the patches for all the tasks. Rendering of the timeline > portion of the webpage in the webclient is virtually impossible. It will > load the tasks and then hang forever. The discussion around this boiled > down to this: other task trackers also can’t handle this and there is a > better way to divvy up the story into several stories and contain them in a > worklist for future, similar work. For now, users can select what they want > to load in their timeline views for stories, so by unmarking all of the > timeline events in their preferences, the story will load completely sans > timeline details. Another solution we discussed to help alleviate the > timeline load on stories with lots of tasks is to have a task field that > links to the review, rather than a comment from gerrit every time a new > patch gets pushed. Essentially we want to focus on cleaning up the timeline > rather than just going straight to a pagination type of solution. It was > also concluded that we want to add another user preference for page sizes > of 1000. Tasks have not been created in the story related to this issue > yet[3], but its on my todo list. > Updates story[6]. > Project Group Descriptions > > ===================== > > There was a request to have project group descriptions, but currently > there is nothing in the API handling this. Discussion concluded with > agreement that this shouldn’t be too difficult. All that needs to happen is > a few additions to the API and the connection to managing group definitions > in project-config. I still need to make a story for this. > Created a story for this[7]. > Translating storyboard-webclient > > ========================= > > There was an infrastructure mailing list thread a little while back that > kicked off discussion on this topic. It was received as an interesting idea > and could help with the adoption of StoryBoard outside of OpenStack. The > biggest concern was communicating to users that are seeing the webclient > rendered in some other language that they still need to create > tasks/stories/worklists/boards in English or whatever the default language > is for the organization that is hosting StoryBoard. This could be a banner > when someone logs in, or something on user’s dashboards. One of the things > that needs to happen first is to find libraries for javascript and angular > for signaling what strings need to be translated. We didn’t really outline > next steps past that as it’s not super high priority, but it’s definitely > an effort we would support if someone wanted to start driving it forward. > I made a story[8] for this even though its pretty far down the list of priorities. > Easier Rollback for Webclient Continuous Deployment > > ========================================= > > With the puppet-storyboard module we deploy from tarballs instead of from > git right now, and we don't preserve earlier tarballs which makes it > difficult to rollback changes when we find issues. There wasn’t a ton of > discussion besides, yes we need to figure this out. Pre-zuulv3 we uploaded > tarballs with the git sha, if we apply that to > publish-openstack-javascript-content, that might help the situation. > Made a story for this[9]. > Managing Project Coresec Groups > > ========================== > > The vast majority of work on private stories has been implemented. Stories > can be marked as private and users can subscribe other users to those > private stories so that only those people can see them. The only > convenience that is currently lacking is adding groups of users (manually > or automatically if in a template story). Groups of users are currently > only managed by StoryBoard admins. We would like to make this managed in a > repository or by proxying gerrit group management. This shouldn’t be too > complicated a change, it would only require some sort of flag being set for > a group definition and then some database migration to sync those groups > into the StoryBoard database. If you have opinions on this topic, it’s not > all set in stone and we would love to hear your thoughts! > This is the story tracking private stories work[10]. > Searching > > ======== > > It’s become apparent that while the search and type ahead features of > StoryBoard work better than most users think at first glance, it’s an issue > that users struggle with searching as much as they do. We talked about > possible solutions for this aside from writing documentation to cover > searching in the webclient. The solution we talked about most was that it > might be easier for our users if we used the gerrit query language as that > is what the majority of our users are already familiar with. The next step > here is to write a spec for using the gerrit query language- or some other > language if users disagree about using the gerrit language. > > > Show all OpenStack Repos in StoryBoard? > > ================================ > > Are we getting to the point where it would be helpful for the users of > StoryBoard to be able to add tasks to stories for all the repos not already > migrated to StoryBoard? This would be incredibly helpful for things like > release goal tracking where many repos that haven’t been migrated had tasks > that were assigned to governance instead of the actual repo so as to be > able to track everything in a single story. This is something we will want > to take up with the TC during a set of office hours in the next week or so. > > > Summary & Continuing Conversations > > ============================= > > My brain is mush. Hopefully I covered the majority of the important topics > and did them justice! Anyone that was there, please feel free to correct > me. Anyone that wasn’t there that is interested in getting involved with > any of this, please join us in #storyboard on IRC or email us with the > [Storyboard] tag to the dev or infra mailing lists. We also have weekly > meetings[4] on Wednesdays at 19:00 UTC, please join us! > > > I've got a lot of stories to make/update and tasks to add.. > > > Thanks! > > -Kendall Nelson (diablo_rojo) > > [1] https://etherpad.openstack.org/p/sb-stein-ptg-planning > > [2] https://storyboard.openstack.org/#!/story/2002586 > > [3] https://storyboard.openstack.org/#!/story/2003525 > > [4] http://eavesdrop.openstack.org/#StoryBoard_Meeting > > I'm also trying to organize all of the work we are doing in a board. I'm in the middle of an overhaul atm, but if you want to follow our work, you will be able to see it here[11]..eventually. -Kendall (diablo_rojo) [5] https://storyboard.openstack.org/#!/story/2002136 [6] https://storyboard.openstack.org/#!/story/2003525 [7] https://storyboard.openstack.org/#!/story/2003886 [8] https://storyboard.openstack.org/#!/story/2003887 [9] https://storyboard.openstack.org/#!/story/2003888 [10] https://storyboard.openstack.org/#!/story/2000568 [11] https://storyboard.openstack.org/#!/board/1 -------------- next part -------------- An HTML attachment was scrubbed... URL: From support at openstack.zendesk.com Thu Sep 27 15:48:10 2018 From: support at openstack.zendesk.com (OpenStack Foundation) Date: Thu, 27 Sep 2018 15:48:10 +0000 Subject: [OpenStack-Infra] COA purchase Wrong redirection In-Reply-To: References: <20180921195948.f4zm2le7r6swau4l@yuggoth.org> Message-ID: ##- Please type your reply above this line -## You are registered as a cc on this help desk request and are thus receiving email notifications on all updates to the request. Reply to this email to add a comment to the request. ---------------------------------------------- Jimmy McArthur, Sep 27, 10:48 CDT Angel, I apologize for the delayed response. This issue should be fixed now. Thank you, Jimmy McArthur ---------------------------------------------- Pance Panceto, Sep 18, 04:30 CDT Hello, I'm trying to purchase a COA and when try to select the "Ubuntu" option , instead of redirect me to the right place always is opening the mail app (outlook, thunderbird, ..., etc) with the "info at openstack.org" set in the "To" place , so I can not purchase the exam . Sorry if it's not the right place to complain. Thanks in advance. Looking forward to hearing from you. Kind Regards, Angel -------------------------------- This email is a service from OpenStack Foundation Support. [L7XY5L-62YP] -------------- next part -------------- An HTML attachment was scrubbed... URL: From gouthampravi at gmail.com Sat Sep 29 01:33:07 2018 From: gouthampravi at gmail.com (Goutham Pacha Ravi) Date: Fri, 28 Sep 2018 18:33:07 -0700 Subject: [OpenStack-Infra] starting zuul migration for manila team repositories In-Reply-To: References: Message-ID: All of the import patches for these repositories have merged and we are ready to approve the cleanup patch: https://review.openstack.org/#/c/593898/ Thanks for the help Doug, Andreas! -- Goutham Pacha Ravi On Mon, Aug 20, 2018 at 1:48 PM Goutham Pacha Ravi wrote: > > The migration of Zuul project settings for the > manila repositories has begun. > Please do not approve any changes to > openstack-infra/project-config/zuul.d/projects.yaml > for the following repositories: > > - openstack/manila > - openstack/manila-image-elements > - openstack/manila-specs > - openstack/manila-tempest-plugin > - openstack/manila-test-image > - openstack/manila-ui > - openstack/python-manilaclient > > A WIP change for project-config is at [1]. Will remove the W-1 on that > once all of [2] changes have merged. > > -- > Goutham Pacha Ravi > > [1] https://review.openstack.org/#/c/593898/ > [2] https://review.openstack.org/#/q/topic:python3-first+project:%22%255E(openstack/manila.*%257Copenstack/python-manilaclient)%22