From cboylan at sapwetik.org Mon Apr 1 21:01:12 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 01 Apr 2019 17:01:12 -0400 Subject: [OpenStack-Infra] Meeting agenda for April 2, 2019 Message-ID: <6b456687-9b9e-482f-a367-96380bd9887b@www.fastmail.com> == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:puppet-4 and topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev *** https://storyboard.openstack.org/#!/story/2004627 * General topics ** PTG planning (clarkb 20190402) *** https://etherpad.openstack.org/2019-denver-ptg-infra-planning *** [https://www.openstack.org/ptg#tab_schedule Draft schedule] Now scheduled for Thursday and Friday. ** LetsEncrypt Progress (clarkb 20190402) ** Trusty Upgrade Progress (clarkb 20190402) *** Need to take the plunge on lists.o.o once mailman is confirmed to work on test node * Open discussion From eumel at arcor.de Tue Apr 2 10:28:31 2019 From: eumel at arcor.de (Frank Kloeker) Date: Tue, 02 Apr 2019 12:28:31 +0200 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <20190325221402.GD1161@fedora19.localdomain> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> Message-ID: <26189c0004b71b6eb244f70a3ed86b91@arcor.de> Am 2019-03-25 23:14, schrieb Ian Wienand: > On Fri, Mar 15, 2019 at 11:01:44AM +0100, Andreas Jaeger wrote: >> Anybody remembers or can reach out to Zanata folks for help on >> fixing this for good, please? > > From internal communication with people previously involved with > Zanata, it seems the team has disabanded and there is no current > support or, at this time, planned future development. So > unfortunately it seems there are no "Zanata folks" at this point :( Hi Ian, thanks for the update. That's also my information as the Zanata team peeled off in the autumn last year. The OpenStack I18n team was aware about the fact, that we will run into an unsupported platform in the near future and started an investigation about the renew of translation platform on [1]. Unfortunately at the moment it's only a list with explored products or projects. Zanata was the best choice and a change of the platform will produce a lot of work. To pull over the project to the OSF could be also an option, but I think there are no Java developers around to maintain the code. My recommendation would be to leave it as it is and to decide how to proceed. kind regards Frank [1] https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation-platform From cboylan at sapwetik.org Thu Apr 4 18:39:36 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Thu, 04 Apr 2019 14:39:36 -0400 Subject: [OpenStack-Infra] Plan for upgrading lists.openstack.org Message-ID: <4d4c9121-b204-4a59-a14b-6d0b3c087b78@www.fastmail.com> Hello everyone, Over the past few days I've been working to test that my test lists.openstack.org server (booted from snapshot of the prod server then upgraded in place with do-release-upgrade) works as expected. I think I've got everything nailed down but our plan for dealing with dmarc_moderation_action configuration items in mailman. I've been taking notes on an etherpad [0] if you are curious about the process and what has been tested. Under list item 5.2.6 on the etherpad I have listed out ideas for how we can handle dmarc_moderation_action. I'd like to have a rough plan for that before we upgrade, and I'd like to upgrade soon so any input is much appreciated. If you can please look over that list and give your thoughts on this thread or on the etherpad. [0] https://etherpad.openstack.org/p/lists.o.o-trusty-to-xenial Thank you, Clark From cboylan at sapwetik.org Fri Apr 5 18:12:34 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 05 Apr 2019 14:12:34 -0400 Subject: [OpenStack-Infra] Plan for upgrading lists.openstack.org In-Reply-To: <4d4c9121-b204-4a59-a14b-6d0b3c087b78@www.fastmail.com> References: <4d4c9121-b204-4a59-a14b-6d0b3c087b78@www.fastmail.com> Message-ID: <84b42d4f-e457-44dd-a618-92b9cdae4578@www.fastmail.com> On Thu, Apr 4, 2019, at 11:39 AM, Clark Boylan wrote: > Hello everyone, > > Over the past few days I've been working to test that my test > lists.openstack.org server (booted from snapshot of the prod server > then upgraded in place with do-release-upgrade) works as expected. I > think I've got everything nailed down but our plan for dealing with > dmarc_moderation_action configuration items in mailman. I've been > taking notes on an etherpad [0] if you are curious about the process > and what has been tested. > > Under list item 5.2.6 on the etherpad I have listed out ideas for how > we can handle dmarc_moderation_action. I'd like to have a rough plan > for that before we upgrade, and I'd like to upgrade soon so any input > is much appreciated. If you can please look over that list and give > your thoughts on this thread or on the etherpad. > > [0] https://etherpad.openstack.org/p/lists.o.o-trusty-to-xenial > After a discussion on IRC [1] I think we are going to decouple the Xenial upgrade from needing to properly sort out the dmarc handling by our mailman server. We can upgrade from trusty to xenial without regression then sort out if we want to reject email that would fail dmarc or munge/wrap afterwards. [1] http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2019-04-04.log.html#t2019-04-04T23:21:55 Clark From iwienand at redhat.com Mon Apr 8 07:13:58 2019 From: iwienand at redhat.com (Ian Wienand) Date: Mon, 8 Apr 2019 17:13:58 +1000 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <26189c0004b71b6eb244f70a3ed86b91@arcor.de> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> Message-ID: <20190408071358.GA2779@fedora19.localdomain> On Tue, Apr 02, 2019 at 12:28:31PM +0200, Frank Kloeker wrote: > The OpenStack I18n team was aware about the fact, that we will run into an > unsupported platform in the near future and started an investigation about > the renew of translation platform on [1]. > [1] https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation-platform I took an action item to do some investigation in the infra meeting. >From the notes above, for last iteration it looks like it came down to Zanata v Poodle. However when I look at [1] Poodle doesn't look terribly active. It looks like Fedora haven't made any choices around which way to go, but weblate has been suggested [2]. Looking at weblate, it seems to have a few things going for it from the infra point of view * it seems active * it's a python/django app which fits our deployments and general skills better than java * has a docker project [3] so has interest in containerisation * we currently put translations in, and propose them via jobs triggered periodically using the zanata CLI tool as described at [4]. weblate has a command-line client that looks to me like it can do roughly what we do now [5] ... essentially integrate with jobs to upload new translations into the tool, and extract the translations and put them into gerrit. * That said, it also seems we could integrate with it more "directly" [6]; it seems it can trigger imports of translations from git repos via webhooks (focused on github, but we could do similar with a post job) and also propose updates directly to gerrit (using git-review; documentation is light on this feature but it is there). It looks like (if I'm reading it right) we could move all configuration in a .weblate file per-repo, which suits our distributed model. > My recommendation would be to leave it as it is and to decide how to > proceed. Overall, yeah, if it ain't broke, don't fix it :) The other thing is, I noticed that weblate has hosted options. If the CI integration is such that it's importing via webhooks, and proposing reviews then it seems like this is essentially an unprivileged app. We have sunk a lot of collective time and resources into Zanata deployment and we should probably do a real cost-benefit analysis once we have some more insights. -i [1] https://github.com/translate/pootle/commits/master [2] https://lists.fedoraproject.org/archives/list/trans at lists.fedoraproject.org/thread/PZUT5ABMNDVYBD7OUBEGVXM7YVW6RZKQ/#4J7BJQWOJDEBACSHDIB6MYWEEXHES6CW [3] https://github.com/WeblateOrg/docker [4] https://docs.openstack.org/i18n/latest/infra.html [5] https://docs.weblate.org/en/latest/wlc.html [6] https://docs.weblate.org/en/latest/admin/continuous.html From tbachman at yahoo.com Mon Apr 8 13:05:48 2019 From: tbachman at yahoo.com (Thomas Bachman) Date: Mon, 8 Apr 2019 13:05:48 +0000 (UTC) Subject: [OpenStack-Infra] Problems building pinned master branch References: <1445195670.18427164.1554728748438.ref@mail.yahoo.com> Message-ID: <1445195670.18427164.1554728748438@mail.yahoo.com> I'm hoping that this is the right list for the topic, and apologize in advance if this is too broad an audience. Our project -- group-based-policy -- is behind the upstream master branches, and as a result, we've been pinning our master branch to the last supported release (in our case, stable/queens). This has been working for some time, but ran into troubles with this patch: -------------- next part -------------- An HTML attachment was scrubbed... URL: From tbachman at yahoo.com Mon Apr 8 13:14:24 2019 From: tbachman at yahoo.com (Thomas Bachman) Date: Mon, 8 Apr 2019 13:14:24 +0000 (UTC) Subject: [OpenStack-Infra] Problems building pinned master branch In-Reply-To: <1445195670.18427164.1554728748438@mail.yahoo.com> References: <1445195670.18427164.1554728748438.ref@mail.yahoo.com> <1445195670.18427164.1554728748438@mail.yahoo.com> Message-ID: <1663329278.18447982.1554729264936@mail.yahoo.com> Apparently I'm still learning how to use email (drat those hot-keys!). This is the patch: https://review.openstack.org/#/c/647475/ You can see that the patch initially passed CI on 3/25/2019, but then when the patch was going to be merged (no changes in the code), the merge job failed. The way it failed is also interesting -- the error in the pep8 job indicates that the DB migration script isn't available, which is part of the python code (i.e. suggesting that our repo's package isn't even installed?): http://logs.openstack.org/75/647475/1/gate/openstack-tox-pep8/5543fd1/job-output.txt.gz#_2019-03-28_23_14_40_267120 The py27 job suggests the same: http://logs.openstack.org/75/647475/1/gate/openstack-tox-py27/8a13368/job-output.txt.gz#_2019-03-28_23_14_59_087759 Does anyone know of any changes between 3/25/2019 and 3/28/2019 that would result in our package not being included? Again, please let me know if this is the wrong list for such issues, and thanks in advance for any/all help! cheers, -Thomas On Monday, April 8, 2019, 9:05:48 AM EDT, Thomas Bachman wrote: I'm hoping that this is the right list for the topic, and apologize in advance if this is too broad an audience. Our project -- group-based-policy -- is behind the upstream master branches, and as a result, we've been pinning our master branch to the last supported release (in our case, stable/queens). This has been working for some time, but ran into troubles with this patch: -------------- next part -------------- An HTML attachment was scrubbed... URL: From tbachman at yahoo.com Mon Apr 8 13:54:17 2019 From: tbachman at yahoo.com (Thomas Bachman) Date: Mon, 8 Apr 2019 13:54:17 +0000 (UTC) Subject: [OpenStack-Infra] Problems building pinned master branch In-Reply-To: <1663329278.18447982.1554729264936@mail.yahoo.com> References: <1445195670.18427164.1554728748438.ref@mail.yahoo.com> <1445195670.18427164.1554728748438@mail.yahoo.com> <1663329278.18447982.1554729264936@mail.yahoo.com> Message-ID: <1127342315.18454020.1554731657463@mail.yahoo.com> Just to add a bit more info to this, in case it's helpful -- this same patch had been backported to all our stable branches (pike, ocata, and even newton). The branches from pike and below were fine, but queens and master (which is pinned to queens) were failing. We also were able to make queens pass by changing a script that we were using to attempt to ensure that the requirements.txt from the appropriate branch was getting used: https://github.com/openstack/group-based-policy/blob/master/tools/tox_install.sh In this case, we changed to what the other stable branches were doing, which was just a pip install: https://review.openstack.org/#/c/648962/ However, the same change didn't fix the master branch. Please don't hold the fact that I still use yahoo email, don't know to how use copy/paste hot-keys correctly, and work on a project that is pinned to stable/queens against me :-). cheers, -Thomas On Monday, April 8, 2019, 9:14:25 AM EDT, Thomas Bachman wrote: Apparently I'm still learning how to use email (drat those hot-keys!). This is the patch: https://review.openstack.org/#/c/647475/ You can see that the patch initially passed CI on 3/25/2019, but then when the patch was going to be merged (no changes in the code), the merge job failed. The way it failed is also interesting -- the error in the pep8 job indicates that the DB migration script isn't available, which is part of the python code (i.e. suggesting that our repo's package isn't even installed?): http://logs.openstack.org/75/647475/1/gate/openstack-tox-pep8/5543fd1/job-output.txt.gz#_2019-03-28_23_14_40_267120 The py27 job suggests the same: http://logs.openstack.org/75/647475/1/gate/openstack-tox-py27/8a13368/job-output.txt.gz#_2019-03-28_23_14_59_087759 Does anyone know of any changes between 3/25/2019 and 3/28/2019 that would result in our package not being included? Again, please let me know if this is the wrong list for such issues, and thanks in advance for any/all help! cheers, -Thomas On Monday, April 8, 2019, 9:05:48 AM EDT, Thomas Bachman wrote: I'm hoping that this is the right list for the topic, and apologize in advance if this is too broad an audience. Our project -- group-based-policy -- is behind the upstream master branches, and as a result, we've been pinning our master branch to the last supported release (in our case, stable/queens). This has been working for some time, but ran into troubles with this patch: -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Mon Apr 8 15:36:02 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 08 Apr 2019 11:36:02 -0400 Subject: [OpenStack-Infra] Problems building pinned master branch In-Reply-To: <1663329278.18447982.1554729264936@mail.yahoo.com> References: <1445195670.18427164.1554728748438.ref@mail.yahoo.com> <1445195670.18427164.1554728748438@mail.yahoo.com> <1663329278.18447982.1554729264936@mail.yahoo.com> Message-ID: On Mon, Apr 8, 2019, at 6:14 AM, Thomas Bachman wrote: > > Apparently I'm still learning how to use email (drat those hot-keys!). > > This is the patch: > > https://review.openstack.org/#/c/647475/ > > You can see that the patch initially passed CI on 3/25/2019, but then > when the patch was going to be merged (no changes in the code), the > merge job failed. The way it failed is also interesting -- the error in > the pep8 job indicates that the DB migration script isn't available, > which is part of the python code (i.e. suggesting that our repo's > package isn't even installed?): > > http://logs.openstack.org/75/647475/1/gate/openstack-tox-pep8/5543fd1/job-output.txt.gz#_2019-03-28_23_14_40_267120 > > The py27 job suggests the same: > > http://logs.openstack.org/75/647475/1/gate/openstack-tox-py27/8a13368/job-output.txt.gz#_2019-03-28_23_14_59_087759 > > Does anyone know of any changes between 3/25/2019 and 3/28/2019 that > would result in our package not being included? Again, please let me > know if this is the wrong list for such issues, and thanks in advance > for any/all help! I'm not aware of any changes on our end. There have been a few recent tox releases [0] which may be relevant. When I run the tox -epep8 command locally with tox 3.5.3 I see that '-e git+https://git.openstack.org/openstack/group-based-policy at 77a7df0a7093f8c3e245481b237738bef838079d#egg=group_based_policy' shows up, but is not present on the zuul job log. I then upgraded tox to 3.8.6 (latest) and reran it (using the -r flag to reinstall deps) and see the same successful result with that package being installed. As a result I don't think tox is at fault here. I do think your answer is in tracking down why that package isn't installed. Normally tox would install it as a separate last step of the package installation process. [0] https://pypi.org/project/tox/#history Hope this helps, Clark From cboylan at sapwetik.org Mon Apr 8 19:01:14 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 08 Apr 2019 15:01:14 -0400 Subject: [OpenStack-Infra] Meeting Agenda for April 9, 2019 Message-ID: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:puppet-4 and topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev *** https://storyboard.openstack.org/#!/story/2004627 *** ok to merge git->https changes (ianw 20190409) * General topics ** PTG planning (clarkb 20190409) *** https://etherpad.openstack.org/2019-denver-ptg-infra-planning *** Given condensed schedule do we want to make a schedule unconference style when we get there based on progress on OpenDev and other work or do we want to try and write up a more solid schedule the week before the summit (week after opendev git transition)? ** LetsEncrypt Progress (clarkb 20190409) *** https://review.openstack.org/#/c/636759/ has one +2 ** Trusty Upgrade Progress (clarkb 20190409) *** Thoughts on upgrading lists.openstack.org this Friday the 12th of April? ** Zanata checkin (ianw 20190409) * Open discussion From cboylan at sapwetik.org Fri Apr 12 17:52:27 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 12 Apr 2019 13:52:27 -0400 Subject: [OpenStack-Infra] lists upgrade seems to be complete Message-ID: <9f1c4849-afde-4fe7-8952-5fa4b43e9c51@www.fastmail.com> This message acts both as an indication that the upgrade was completed and a sanity check that our lists are functioning. Clark From anteaya at anteaya.info Fri Apr 12 18:33:31 2019 From: anteaya at anteaya.info (Anita Kuno) Date: Fri, 12 Apr 2019 14:33:31 -0400 Subject: [OpenStack-Infra] lists upgrade seems to be complete In-Reply-To: <9f1c4849-afde-4fe7-8952-5fa4b43e9c51@www.fastmail.com> References: <9f1c4849-afde-4fe7-8952-5fa4b43e9c51@www.fastmail.com> Message-ID: <0d39e4b7-8832-2434-5810-7cfc093fff7e@anteaya.info> On 2019-04-12 1:52 p.m., Clark Boylan wrote: > This message acts both as an indication that the upgrade was completed and a sanity check that our lists are functioning. > > Clark > > _______________________________________________ > OpenStack-Infra mailing list > OpenStack-Infra at lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-infra > Received. Thanks to Clark and Jeremy for doing this upgrade. Seems to be working for me. Anita From cboylan at sapwetik.org Mon Apr 15 19:14:58 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 15 Apr 2019 15:14:58 -0400 Subject: [OpenStack-Infra] Meeting Agenda for April 16, 2019 Message-ID: == Agenda for next meeting == * Announcements * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:puppet-4 and topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev *** https://storyboard.openstack.org/#!/story/2004627 *** Setting specific time for maintenance work to start *** Are we ready? What do we need to do between now and Friday? *** Should we include the one requested repo rename below in this process or do that later? * General topics ** LetsEncrypt Progress (clarkb 20190416) *** graphite.opendev.org is now LetsEncypted. Next steps are restarting services when certs update and testing of that process. ** Trusty Upgrade Progress (clarkb 20190416) *** lists.openstack.org has been upgraded. ** Removal of ugo+rw chmod from default job definitions (zbr 20190415) *** Mainly this insanely unsafe chmod does prevent ansible from loading ansible.cfg files from our repos. That is happening from "Change zuul-cloner permissions" task which is run even for basic jobs like openstack-tox-py* ones. * Open discussion From mihai.rusan at gmail.com Tue Apr 16 06:26:57 2019 From: mihai.rusan at gmail.com (Mihai Rusan) Date: Tue, 16 Apr 2019 09:26:57 +0300 Subject: [OpenStack-Infra] Offering help / sysadmin background with heavy emphasis on systems automation (Ansible) Message-ID: Hello, I'm Mihai, over 5+ years of sysadmin background and embracing Ansible and cloud infrastructure. Happy to help, I'm living in Romania, Europe. Time zone EEST UTC+3. Regards, Mihai -------------- next part -------------- An HTML attachment was scrubbed... URL: From cboylan at sapwetik.org Tue Apr 16 23:56:14 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 16 Apr 2019 19:56:14 -0400 Subject: [OpenStack-Infra] Freezing new project creation in Gerrit Message-ID: Hello config-core reviewers, We'd like to freeze new project creation through the end of the week so that we can get through the OpenDev git transition without a constantly changing list of projects that may be renamed. This will allow us to review the lists and be confident they are static prior to the transition. So with that in mind please hold back from approving new projects in project-config/gerrit/projects.yaml until we are clear of the transition. Thank you, Clark From cboylan at sapwetik.org Wed Apr 17 00:14:03 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 16 Apr 2019 20:14:03 -0400 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 Message-ID: The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC. Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues. For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped. As always we are happy to answer any questions you might have or address any concerns. Feel free to reach out. Thank you for your patience, Clark From cboylan at sapwetik.org Wed Apr 17 00:23:56 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Tue, 16 Apr 2019 20:23:56 -0400 Subject: [OpenStack-Infra] =?utf-8?q?Offering_help_/_sysadmin_background_w?= =?utf-8?q?ith_heavy_emphasis_on_systems_automation_=28Ansible=29?= In-Reply-To: References: Message-ID: <7699a9e7-458c-4949-8456-73c26982248b@www.fastmail.com> On Mon, Apr 15, 2019, at 11:27 PM, Mihai Rusan wrote: > Hello, > > I'm Mihai, over 5+ years of sysadmin background and embracing Ansible > and cloud infrastructure. > > Happy to help, I'm living in Romania, Europe. Time zone EEST UTC+3. Hello and thank you for the offer to help. This week is a bit busy for us as we are planning a large git repository hosting migration, apologies if responses are a bit slow. That said we are in the middle of a large transition from puppet based deployments to ansible and docker based deployments. We have written up a specification for this work which can be found at https://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html. I mention this as you mentioned ansible so I thought it might be interesting to you. The other specifications on that site should give you an idea of the other work we have in progress as well as other items may interest you too. If that spec or others look interesting feel free to reach out to myself or this list and we can take it from there. You may also want to hop into #openstack-infra on freenode's IRC servers and say hello as well as listen in as we discuss things. That should give you a good flavor for the day to day efforts. The last thing I'll mention is that a good portion of our day to day efforts involve reviewing code changes to our configuration management tooling. https://review.openstack.org/#/q/project:openstack-infra/system-config+status:open will list out a good portion of those changes if you'd like to take a look and see what that entails. Feel free to do a review or two as well :) Hope this helps, Clark From aj at suse.com Wed Apr 17 05:48:37 2019 From: aj at suse.com (Andreas Jaeger) Date: Wed, 17 Apr 2019 07:48:37 +0200 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: References: Message-ID: <257e9f8a-9368-8a08-a77d-bf30fe5b6b9e@suse.com> On 17/04/2019 02.14, Clark Boylan wrote: > The infra/OpenDev team continues to make good progress towards this transition and plans to perform the transition on April 19, 2019 as previously scheduled. We will begin the transition at 15:00UTC and users should plan for intermittent Gerrit and git repo outages through the day. We expect most of those will be closer to 15:00UTC than 23:00UTC. > > Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues. I wonder about these three, are they missing in some governance repo list? openstack/governance-website -> x/... openstack/interop-workloads -> x/interop-workloads openstack/openstack-map -> x/openstack-map > For the airship, starlingx, and zuul repo renames the repositories listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org were used placing repos in airship/, starlingx/ and zuul/ namespaces. Any repo name prefix (like stx- and airship-) is dropped. Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From frickler at offenerstapel.de Wed Apr 17 08:22:22 2019 From: frickler at offenerstapel.de (Jens Harbott) Date: Wed, 17 Apr 2019 08:22:22 +0000 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: <257e9f8a-9368-8a08-a77d-bf30fe5b6b9e@suse.com> References: <257e9f8a-9368-8a08-a77d-bf30fe5b6b9e@suse.com> Message-ID: <1555489342.4997.36.camel@offenerstapel.de> On Wed, 2019-04-17 at 07:48 +0200, Andreas Jaeger wrote: > On 17/04/2019 02.14, Clark Boylan wrote: > > The infra/OpenDev team continues to make good progress towards this > > transition and plans to perform the transition on April 19, 2019 as > > previously scheduled. We will begin the transition at 15:00UTC and > > users should plan for intermittent Gerrit and git repo outages > > through the day. We expect most of those will be closer to 15:00UTC > > than 23:00UTC. > > > > Fungi has generated a master list of project renames for the > > openstack namespaces: http://paste.openstack.org/show/749402/. If > > you have a moment please quickly review these planned renames for > > any obvious errors or issues. > > I wonder about these three, are they missing in some governance repo > list? > > openstack/governance-website -> x/... > openstack/interop-workloads -> x/interop-workloads > openstack/openstack-map -> x/openstack-map openstack/openstack -> x/openstack also seems unintended and possibly confusing. > > For the airship, starlingx, and zuul repo renames the repositories > > listed at git.airshipit.org, git.starlingx.io, and git.zuul-ci.org > > were used placing repos in airship/, starlingx/ and zuul/ > > namespaces. Any repo name prefix (like stx- and airship-) is > > dropped. > > Andreas From thierry at openstack.org Wed Apr 17 09:39:30 2019 From: thierry at openstack.org (Thierry Carrez) Date: Wed, 17 Apr 2019 11:39:30 +0200 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: <257e9f8a-9368-8a08-a77d-bf30fe5b6b9e@suse.com> References: <257e9f8a-9368-8a08-a77d-bf30fe5b6b9e@suse.com> Message-ID: <8667149f-736b-a8bd-8f8a-ce7809b496e0@openstack.org> Andreas Jaeger wrote: > On 17/04/2019 02.14, Clark Boylan wrote: >> Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues. > > I wonder about these three, are they missing in some governance repo list? > > openstack/governance-website -> x/... This one is driving governance.openstack.org/ so it is an oversight that it does not appear anywhere. We can add it to the TC-owned repos, or to the Meta SIG repos, so that it can be kept under openstack/. > openstack/openstack-map -> x/openstack-map This one is owned by the OSF to drive the openstack.org/software website and the OpenStack Map content. I would move it to osf/openstack-map. A few others: openstack/four-opens should also be under osf/. openstack/edge-computing-group should probably be added as a FEMDC SIG repo and stay under openstack/. openstack/arch-wg should be added under TC-owned repos and stay under openstack/. If that works for everyone, I'll propose the corresponding changes. -- Thierry Carrez (ttx) From thierry at openstack.org Wed Apr 17 09:41:54 2019 From: thierry at openstack.org (Thierry Carrez) Date: Wed, 17 Apr 2019 11:41:54 +0200 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: References: Message-ID: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> Clark Boylan wrote: > Fungi has generated a master list of project renames for the openstack namespaces: http://paste.openstack.org/show/749402/. If you have a moment please quickly review these planned renames for any obvious errors or issues. One thing that bothers me is the massive openstack-infra/ -> openstack/ rename, with things like: openstack-infra/gerrit -> openstack/gerrit Shouldn't that be directly moved to opendev/gerrit? Moving it to openstack/ sounds like a step backward. -- Thierry Carrez (ttx) From cdent+os at anticdent.org Wed Apr 17 09:54:04 2019 From: cdent+os at anticdent.org (Chris Dent) Date: Wed, 17 Apr 2019 10:54:04 +0100 (BST) Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> References: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> Message-ID: On Wed, 17 Apr 2019, Thierry Carrez wrote: > Clark Boylan wrote: >> Fungi has generated a master list of project renames for the openstack >> namespaces: http://paste.openstack.org/show/749402/. If you have a moment >> please quickly review these planned renames for any obvious errors or >> issues. > > One thing that bothers me is the massive openstack-infra/ -> openstack/ > rename, with things like: > > openstack-infra/gerrit -> openstack/gerrit > > Shouldn't that be directly moved to opendev/gerrit? Moving it to openstack/ > sounds like a step backward. Yeah, agree, that does seem the wrong direction. The impression I had was that one of the outcomes of this would be that what's in openstack/* would be a more clear picture of the thing which is OpenStack. -- Chris Dent ٩◔̯◔۶ https://anticdent.org/ freenode: cdent tw: @anticdent From corvus at inaugust.com Wed Apr 17 14:20:18 2019 From: corvus at inaugust.com (James E. Blair) Date: Wed, 17 Apr 2019 07:20:18 -0700 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> (Thierry Carrez's message of "Wed, 17 Apr 2019 11:41:54 +0200") References: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> Message-ID: <87r2a0af31.fsf@meyer.lemoncheese.net> Thierry Carrez writes: > Clark Boylan wrote: >> Fungi has generated a master list of project renames for the >> openstack namespaces: http://paste.openstack.org/show/749402/. If >> you have a moment please quickly review these planned renames for >> any obvious errors or issues. > > One thing that bothers me is the massive openstack-infra/ -> > openstack/ rename, with things like: > > openstack-infra/gerrit -> openstack/gerrit > > Shouldn't that be directly moved to opendev/gerrit? Moving it to > openstack/ sounds like a step backward. My understanding is this is due to openstack-infra being TC-governed and opendev not quite having gotten around to establishing an official non-TC governance yet. I think the intent is to eventually do that. We could probably anticipate that a bit if we would like and go ahead and sort openstack-infra things into different buckets. At the end of this, I think we will all have more hats, with overlap between opendev and openstack. Some current infra activities and repos are openstack-specific and should be re-homed into openstack; others serve all projects and should be in opendev; yet more are just things that are incidentally related to what we do and should be on their own. I've produced a list based on my estimation of what things will look like at the end of the process. This is just a starting point if we would like to explore this option. We could refine the list and use it, or we could choose to stick with the status quo temporarily and move the infra repos out of openstack at a later time when things are more clear. https://etherpad.openstack.org/p/6CmVhW40m0 -Jim From thierry at openstack.org Wed Apr 17 14:54:46 2019 From: thierry at openstack.org (Thierry Carrez) Date: Wed, 17 Apr 2019 16:54:46 +0200 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: <87r2a0af31.fsf@meyer.lemoncheese.net> References: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> <87r2a0af31.fsf@meyer.lemoncheese.net> Message-ID: James E. Blair wrote: > My understanding is this is due to openstack-infra being TC-governed and > opendev not quite having gotten around to establishing an official > non-TC governance yet. I think the intent is to eventually do that. We > could probably anticipate that a bit if we would like and go ahead and > sort openstack-infra things into different buckets. At the end of this, > I think we will all have more hats, with overlap between opendev and > openstack. Some current infra activities and repos are > openstack-specific and should be re-homed into openstack; others serve > all projects and should be in opendev; yet more are just things that are > incidentally related to what we do and should be on their own. > > I've produced a list based on my estimation of what things will look > like at the end of the process. This is just a starting point if we > would like to explore this option. We could refine the list and use it, > or we could choose to stick with the status quo temporarily and move the > infra repos out of openstack at a later time when things are more clear. > > https://etherpad.openstack.org/p/6CmVhW40m0 I understand it conflates two separate issues (rename and governance), and we clearly don't want to delay the rename due to premature governance discussions. My personal view on this is that we can split openstack-infra things between openstack/ and opendev/ following your etherpad plan, and officialize the governance part later. Technically, things split under opendev/ would still be under the OpenStack infra team and the OpenStack TC until the governance is officially split out. That avoids unnecessary renames and crowding our new clean openstack/ space with stuff we know will move away soon. We'll obviously have to edit the projects.yaml to account for the repo renames under the Infrastructure team, but we have to do that anyway. -- Thierry Carrez (ttx) From cboylan at sapwetik.org Wed Apr 17 15:22:19 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Wed, 17 Apr 2019 11:22:19 -0400 Subject: [OpenStack-Infra] =?utf-8?q?OpenDev_git_hosting_migration_and_Ger?= =?utf-8?q?rit_downtime_April_19=2C_2019?= In-Reply-To: References: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> <87r2a0af31.fsf@meyer.lemoncheese.net> Message-ID: <1d7d345b-4baa-44ef-8009-3e1ca6c97e97@www.fastmail.com> On Wed, Apr 17, 2019, at 7:54 AM, Thierry Carrez wrote: > James E. Blair wrote: > > My understanding is this is due to openstack-infra being TC-governed and > > opendev not quite having gotten around to establishing an official > > non-TC governance yet. I think the intent is to eventually do that. We > > could probably anticipate that a bit if we would like and go ahead and > > sort openstack-infra things into different buckets. At the end of this, > > I think we will all have more hats, with overlap between opendev and > > openstack. Some current infra activities and repos are > > openstack-specific and should be re-homed into openstack; others serve > > all projects and should be in opendev; yet more are just things that are > > incidentally related to what we do and should be on their own. > > > > I've produced a list based on my estimation of what things will look > > like at the end of the process. This is just a starting point if we > > would like to explore this option. We could refine the list and use it, > > or we could choose to stick with the status quo temporarily and move the > > infra repos out of openstack at a later time when things are more clear. > > > > https://etherpad.openstack.org/p/6CmVhW40m0 > > I understand it conflates two separate issues (rename and governance), > and we clearly don't want to delay the rename due to premature > governance discussions. > > My personal view on this is that we can split openstack-infra things > between openstack/ and opendev/ following your etherpad plan, and > officialize the governance part later. Technically, things split under > opendev/ would still be under the OpenStack infra team and the OpenStack > TC until the governance is officially split out. That avoids unnecessary > renames and crowding our new clean openstack/ space with stuff we know > will move away soon. > > We'll obviously have to edit the projects.yaml to account for the repo > renames under the Infrastructure team, but we have to do that anyway. This plan works for me. I did note a few items in the x/ namespace that probably do make sense under openstack/. We'll also need to make a decision on storyboard. Any suggestions for storyboard? fungi in particular may have thoughts on that. Clark From fungi at yuggoth.org Wed Apr 17 16:51:49 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Wed, 17 Apr 2019 16:51:49 +0000 Subject: [OpenStack-Infra] OpenDev git hosting migration and Gerrit downtime April 19, 2019 In-Reply-To: <1d7d345b-4baa-44ef-8009-3e1ca6c97e97@www.fastmail.com> References: <49af298f-bbc7-13ce-4071-fa54d440589c@openstack.org> <87r2a0af31.fsf@meyer.lemoncheese.net> <1d7d345b-4baa-44ef-8009-3e1ca6c97e97@www.fastmail.com> Message-ID: <20190417165149.wyjpcdjzqukrfwx5@yuggoth.org> On 2019-04-17 11:22:19 -0400 (-0400), Clark Boylan wrote: [...] > This plan works for me. I did note a few items in the x/ namespace > that probably do make sense under openstack/. We'll also need to > make a decision on storyboard. Any suggestions for storyboard? > fungi in particular may have thoughts on that. I brought it up in IRC and seems like we're leaning toward wanting storyboard repos in the opendev namespace (at least for the foreseeable future): http://eavesdrop.openstack.org/irclogs/%23storyboard/%23storyboard.2019-04-17.log.html#t2019-04-17T15:42:47 -- 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 petersen at redhat.com Thu Apr 18 09:50:20 2019 From: petersen at redhat.com (Jens-Ulrik Petersen) Date: Thu, 18 Apr 2019 17:50:20 +0800 Subject: [OpenStack-Infra] [OpenStack-I18n] Zanata broken on Bionic In-Reply-To: References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> Message-ID: Hi Ian, Just saw your email now - sorry if they reply reaches you too late... Perhaps you can try zanata-python-client and see if it meets your needs. Jens On Fri, Mar 15, 2019 at 8:31 PM Ian Y. Choi wrote: > Hello Carlos, > > I am not sure which team you are working currently, but heard that you are > working in a tooling team a few months ago - would u help to resolve this? > I can’t forget your name - we met on Tokyo Summit in 2015, and many > OpenStack team members appreciate your lots of effort on Zanata + OpenStack. > > Andreas, is it the same person as who I ask to? :) Hopefully it isn’t > wrong. > > > With many thanks, > > /Ian > > > On Friday, March 15, 2019, Andreas Jaeger wrote: > >> All translation jobs are failing since zanata-cli fails, looking at the >> error it looks like Java11 is too new for zanata-cli. >> >> I tested the most recent zanata-cli package 4.6.2 (from last year), and >> it failed as well. >> >> Logs: >> >> http://logs.openstack.org/periodic/git.openstack.org/openstack/python-keystoneclient/master/propose-translation-update/8c7d3e8/job-output.txt.gz#_2019-03-15_07_56_38_362424 >> >> I see two options: >> 1) Downgrading java to openjdk8 in the used bionic image >> 2) Going back to Xenial for the job >> >> Alex Eng is not working on Zanata anymore and was our contact in the >> past - I remember another person involved but forgot his name ;( Anybody >> remembers or can reach out to Zanata folks for help on fixing this for >> good, please? >> >> I've pushed https://review.openstack.org/643539 for going back to >> Xenial as temporary workaround. But we should figure out the real fix, >> >> Andreas > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From eumel at arcor.de Fri Apr 19 16:57:13 2019 From: eumel at arcor.de (Frank Kloeker) Date: Fri, 19 Apr 2019 18:57:13 +0200 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <20190408071358.GA2779@fedora19.localdomain> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> <20190408071358.GA2779@fedora19.localdomain> Message-ID: <637bb834fdbf28b90c9703630aa1b17c@arcor.de> Am 2019-04-08 09:13, schrieb Ian Wienand: > On Tue, Apr 02, 2019 at 12:28:31PM +0200, Frank Kloeker wrote: >> The OpenStack I18n team was aware about the fact, that we will run >> into an >> unsupported platform in the near future and started an investigation >> about >> the renew of translation platform on [1]. >> [1] >> https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation-platform > > I took an action item to do some investigation in the infra meeting. > From the notes above, for last iteration it looks like it came down to > Zanata v Poodle. However when I look at [1] Poodle doesn't look > terribly active. > > It looks like Fedora haven't made any choices around which way to > go, but weblate has been suggested [2]. > > Looking at weblate, it seems to have a few things going for it from > the infra point of view > > * it seems active > * it's a python/django app which fits our deployments and general > skills better than java > * has a docker project [3] so has interest in containerisation > * we currently put translations in, and propose them via jobs > triggered periodically using the zanata CLI tool as described at > [4]. weblate has a command-line client that looks to me like it can > do roughly what we do now [5] ... essentially integrate with jobs to > upload new translations into the tool, and extract the translations > and put them into gerrit. > * That said, it also seems we could integrate with it more "directly" > [6]; it seems it can trigger imports of translations from git repos > via webhooks (focused on github, but we could do similar with a post > job) and also propose updates directly to gerrit (using git-review; > documentation is light on this feature but it is there). It looks > like (if I'm reading it right) we could move all configuration in a > .weblate file per-repo, which suits our distributed model. Hi Ian, thanks for taking a first look on Weblate. It looks also interesting to me. I tried a first test installation and there are also some advantages from I18n perspective: * automatic syntax check on translation strings [1]. In the past we had often format errors on Python strings, which are not easy to spot. Also when we started with hard syntax check on sphinx-build few weeks ago, it seems that we can cover such kind of errors in Weblate UI * Machine Translating backends [2]. It's not a shame to use Google Translate instead a paper dictionary. I think it's usual in most of the translation teams. Zanata started to develop such kind of stuff, which is in Weblate already included. Most of the MT services are paid service. I would try to get in touch with Deepl (a German company) to sponsor us. Or there is also a way to implement our own MT service, if there is a OpenStack project or SIG, which is looking for a senseful use case in AI. Weblate holds his own VCS and commits each translation into the local repo. Sync with upstream can be automtically or by hand with wlc client. I saw also Gerrit backend, without any further documentation. I think it's a lots of work. First step would be write down all that workflows and use cases what we need for a migration. > The other thing is, I noticed that weblate has hosted options. If the > CI integration is such that it's importing via webhooks, and proposing > reviews then it seems like this is essentially an unprivileged app. > We have sunk a lot of collective time and resources into Zanata > deployment and we should probably do a real cost-benefit analysis once > we have some more insights. Following the prize table on [3] we're far away from the Enterprise account with only 20 repos. Self-hosting and installation of the plain app is not a big deal, I think. Most of the work will be setup projects and sync translations in and out. On the other hand that could be easier with technics what you mentioned. Frank [1] https://docs.weblate.org/en/weblate-3.5.1/user/checks.html#check-python-format [2] https://docs.weblate.org/en/latest/admin/machine.html [3] https://weblate.org/en/hosting/ From cboylan at sapwetik.org Sat Apr 20 04:18:30 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Sat, 20 Apr 2019 00:18:30 -0400 Subject: [OpenStack-Infra] Post opendev git repo hosting status repo Message-ID: <8ad20ab9-96c8-41c6-888a-ae67402f8470@www.fastmail.com> Hello infra! We've completed the initial work to do this migration. YAY. But there are a few things to keep in mind while we clean up after ourselves. This was a bit of an inception moment where we rely on Gerrit to drive our infrastructure but we renamed and moved Gerrit. This means that the ansible crons on bridge.o.o are disabled. Please DO NOT reenable the run_all.sh cron until we are ready. We should also avoid creating new projects until we are happy with things and have run_all.sh running again. config-core please DO NOT merge new project additions until we are ready. In general though bug fixes to zuul jobs should be fine (and I expect we'll have to start here in order to merge other code). And we'll fix more bugs from there. Thanks again to everyone that helped and for your patience otherwise. This was the work of many people. Also I'll respond to this when we think we are ready to go on the things I asked us to leave alone for now. With that, its been a really long day, and I should get some rest. Clark From cboylan at sapwetik.org Sat Apr 20 21:25:08 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Sat, 20 Apr 2019 17:25:08 -0400 Subject: [OpenStack-Infra] Post opendev git repo hosting status repo In-Reply-To: <8ad20ab9-96c8-41c6-888a-ae67402f8470@www.fastmail.com> References: <8ad20ab9-96c8-41c6-888a-ae67402f8470@www.fastmail.com> Message-ID: <0ac69311-1f9b-4265-96f5-06b6bb8adff7@www.fastmail.com> On Fri, Apr 19, 2019, at 9:18 PM, Clark Boylan wrote: > Hello infra! > > We've completed the initial work to do this migration. YAY. But there > are a few things to keep in mind while we clean up after ourselves. > > This was a bit of an inception moment where we rely on Gerrit to drive > our infrastructure but we renamed and moved Gerrit. This means that the > ansible crons on bridge.o.o are disabled. Please DO NOT reenable the > run_all.sh cron until we are ready. > > We should also avoid creating new projects until we are happy with > things and have run_all.sh running again. config-core please DO NOT > merge new project additions until we are ready. > > In general though bug fixes to zuul jobs should be fine (and I expect > we'll have to start here in order to merge other code). And we'll fix > more bugs from there. Thanks again to everyone that helped and for your > patience otherwise. This was the work of many people. > > Also I'll respond to this when we think we are ready to go on the > things I asked us to leave alone for now. We have reenabled the run_all.sh cron on bridge.openstack.org after iterating through each playbook it runs and examining the results. Things looked happy so we are back to operating with normal deployment procedures. That said we would like to keep a freeze on new project creations for a little while longer. We found some bugs around creating and renaming projects particularly if the new target org (or namespace) does not already exist. This means config-core and infra-root please avoid creating new projects until we are ready. I will followup to this message with a note when we have reached that point. Thank you, Clark From aj at suse.com Sun Apr 21 16:53:48 2019 From: aj at suse.com (Andreas Jaeger) Date: Sun, 21 Apr 2019 18:53:48 +0200 Subject: [OpenStack-Infra] Nodepool image building broken after OpenDev change? Message-ID: Looking at http://nl01.openstack.org/image-list it looks like no new images were build after the OpenDev changes on Friday. No urgency on this for now - but sending it here as discussed on #openstack-infra so that it is not forgotten. Hope somebody picks it up ;) Thanks! Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From aj at suse.com Sun Apr 21 17:04:42 2019 From: aj at suse.com (Andreas Jaeger) Date: Sun, 21 Apr 2019 19:04:42 +0200 Subject: [OpenStack-Infra] Nodepool image building broken after OpenDev change? In-Reply-To: References: Message-ID: On 21/04/2019 18.53, Andreas Jaeger wrote: > Looking at http://nl01.openstack.org/image-list it looks like no new > images were build after the OpenDev changes on Friday. > > No urgency on this for now - but sending it here as discussed on > #openstack-infra so that it is not forgotten. Hope somebody picks it up ;) Hope this fixes it: https://review.opendev.org/654257 Please check images once that is in, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From aj at suse.com Mon Apr 22 10:31:41 2019 From: aj at suse.com (Andreas Jaeger) Date: Mon, 22 Apr 2019 12:31:41 +0200 Subject: [OpenStack-Infra] openstack/openstack still broken Message-ID: <588ae73f-aea0-d6fd-2921-9af9aadbfd05@suse.com> My changes to update openstack/openstack merged but I still see a problem: https://opendev.org/openstack/openstack gives still a 500 internal error I wonder whether github.com/openstack/openstack is correct or got confused by the org changes as well. Have a look at project-config as one example... Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From aj at suse.com Mon Apr 22 10:32:27 2019 From: aj at suse.com (Andreas Jaeger) Date: Mon, 22 Apr 2019 12:32:27 +0200 Subject: [OpenStack-Infra] Nodepool image building broken after OpenDev change? In-Reply-To: References: Message-ID: On 21/04/2019 19.04, Andreas Jaeger wrote: > On 21/04/2019 18.53, Andreas Jaeger wrote: >> Looking at http://nl01.openstack.org/image-list it looks like no new >> images were build after the OpenDev changes on Friday. >> >> No urgency on this for now - but sending it here as discussed on >> #openstack-infra so that it is not forgotten. Hope somebody picks it up ;) > > Hope this fixes it: > https://review.opendev.org/654257 > > Please check images once that is in, I see new images for bionic and others. Hope that the remaining images build today as well (my change merged too late for all images to get the new content), Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From cboylan at sapwetik.org Mon Apr 22 23:16:19 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Mon, 22 Apr 2019 19:16:19 -0400 Subject: [OpenStack-Infra] Meeting Agenda for April 23, 2019 Message-ID: <578edb1c-ccde-42b6-9f6d-f449d0d7e62f@www.fastmail.com> == Agenda for next meeting == * Announcements ** Summit and PTG next week. No meeting April 30. * Actions from last meeting * Specs approval * Priority Efforts (Standing meeting agenda items. Please expand if you have subtopics.) ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/task-tracker.html A Task Tracker for OpenStack] ** [http://specs.openstack.org/openstack-infra/infra-specs/specs/update-config-management.html Update Config Management] *** topic:puppet-4 and topic:update-cfg-mgmt *** Zuul as CD engine ** OpenDev *** Catch up on what needs to be done now that we've migrated. * General topics ** LetsEncrypt Progress (clarkb 20190423) *** git.airshipit.org, git.starlingx.io and survey.openstack.org expire soon. Harder to LE these due to where dns is hosted. Should we buy 2 year certs and then call it a day? ** Trusty Upgrade Progress (clarkb 20190423) ** PTG planning (clarkb 20190423) *** https://etherpad.openstack.org/2019-denver-ptg-infra-planning * Open discussion From sgw at linux.intel.com Tue Apr 23 23:54:46 2019 From: sgw at linux.intel.com (Saul Wold) Date: Tue, 23 Apr 2019 16:54:46 -0700 Subject: [OpenStack-Infra] StarlingX / Infra teams sync-up at PTG Message-ID: <1b8469d0-387f-4853-b487-f9519dcc5130@linux.intel.com> Infra Team, The StarlingX Project would like to request a 30-60 minute sync up to talk about some of the challenges that StarlingX faces with regards to build and test infrastructure. As StarlingX is an integration project that creates a Linux Distribution with a Cloud infrastructure on top of it, this makes it more challenging to both build and test. The current OpenStack Foundation infrastructure is good as building and testing projects such as Nova, Neutron, ... It could be used to build and test the individual components of the StarlingX Flock, such as Fault and others. It's not well suited to build the complete StarlingX ISO and test that ISO. We want to explore what the existing resources that are available and understand how and what we can add to the infrastructure to enable the build and testing that StarlingX will require. We hope that we can find an hour timeslot during the PTG that we can talk further about this with both teams. Our timeslots overlap Thrusday afternoon and Friday so we could put it on our adgendas. Please let us know if you have available time slots. Thanks Sau! StarlingX TSC From corvus at inaugust.com Wed Apr 24 02:55:56 2019 From: corvus at inaugust.com (James E. Blair) Date: Tue, 23 Apr 2019 19:55:56 -0700 Subject: [OpenStack-Infra] Announcing Gertty 1.6.0 Message-ID: <87h8aokt6r.fsf@meyer.lemoncheese.net> Announcing Gertty 1.6.0 ======================= Gertty is a console-based interface to the Gerrit Code Review system. Gertty is designed to support a workflow similar to reading network news or mail. It syncs information from Gerrit to local storage to support disconnected operation and easy manipulation of local git repos. It is fast and efficient at dealing with large numbers of changes and projects. The full README may be found here: https://opendev.org/ttygroup/gertty/src/branch/master/README.rst Changes since 1.5.0: ==================== * The default config file location is now ~/.config/gertty/gertty.yaml (but Gertty will fall back on the previous default of ~/.gertty.yaml if it is not found) * The source code is now hosted in OpenDev (https://opendev.org) * Gertty supports (and should be run with) python3 * Added tab display support * Reviewkeys are enabled in diffs * Added a new option (off by default) to close the change after reviewing * Added inline comments to the change overview screen * The size column graph is more configurable * Reviewkeys now support sending a message * Added more example configurations As well as several bug fixes and stability improvements. Thanks to the following people whose changes are included in this release: Clint Byrum Dominique Martinet Doug Wiegley Emilien Macchi Ian Wienand John L. Villalovos Logan V Major Hayden Masayuki Igawa Matthias Runge Natal Ngétal Nate Johnston Nguyen Hung Phuong Robert Collins Tobias Henkel Tristan Cacqueray From cboylan at sapwetik.org Wed Apr 24 15:50:06 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Wed, 24 Apr 2019 11:50:06 -0400 Subject: [OpenStack-Infra] [Starlingx-discuss] StarlingX / Infra teams sync-up at PTG In-Reply-To: <1b8469d0-387f-4853-b487-f9519dcc5130@linux.intel.com> References: <1b8469d0-387f-4853-b487-f9519dcc5130@linux.intel.com> Message-ID: On Tue, Apr 23, 2019, at 4:55 PM, Saul Wold wrote: > > > Infra Team, > > The StarlingX Project would like to request a 30-60 minute sync up to > talk about some of the challenges that StarlingX faces with regards to > build and test infrastructure. > > As StarlingX is an integration project that creates a Linux Distribution > with a Cloud infrastructure on top of it, this makes it more challenging > to both build and test. The current OpenStack Foundation infrastructure > is good as building and testing projects such as Nova, Neutron, ... It > could be used to build and test the individual components of the > StarlingX Flock, such as Fault and others. It's not well suited to build > the complete StarlingX ISO and test that ISO. > > We want to explore what the existing resources that are available and > understand how and what we can add to the infrastructure to enable the > build and testing that StarlingX will require. > > We hope that we can find an hour timeslot during the PTG that we can > talk further about this with both teams. Our timeslots overlap Thrusday > afternoon and Friday so we could put it on our adgendas. > > Please let us know if you have available time slots. I'm thinking the best day for us is Friday (we'll want to dig into our team specific items on Thursday). Does Just after the lunch break on Friday (say 1:30pm) in the Infra/QA room work? If so we'll see you there. I'll go ahead and add you to our etherpad [0] as I'm editing that today too. [0] https://etherpad.openstack.org/p/2019-denver-ptg-infra-planning Clark From cboylan at sapwetik.org Wed Apr 24 16:13:57 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Wed, 24 Apr 2019 12:13:57 -0400 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together Message-ID: Hello Infra! Monday evening is looking like a good night to have a low key informal team gathering. The only official event on the calendar is the Marketplace Mixer which runs until 7pm. Weather permitting I'd like to head back to Lowry Beer Garden (where we've gone at past PTGs). It is a bit out of the way from the conference center so we will need to coordinate uber/lyft transport but that hasn't been a problem in the past. Lets meet at 6:30pm (I can send specific location once onsite) and head over to Lowry. If the weather looks terrible I can call ahead and see if their indoor area is open and if they say it is "meh" we'll find something closer to the conference center. Also, they close at 9pm which should force us to get some sleep :) Finally, Monday is a good day because it is gertty's birthday. Hope to see you then. Clark From cboylan at sapwetik.org Wed Apr 24 16:31:05 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Wed, 24 Apr 2019 12:31:05 -0400 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together In-Reply-To: References: Message-ID: <4be21a02-4e7e-4ee0-a604-10898d419282@www.fastmail.com> On Wed, Apr 24, 2019, at 9:14 AM, Clark Boylan wrote: > Hello Infra! > > Monday evening is looking like a good night to have a low key informal > team gathering. The only official event on the calendar is the > Marketplace Mixer which runs until 7pm. Weather permitting I'd like to > head back to Lowry Beer Garden (where we've gone at past PTGs). It is a > bit out of the way from the conference center so we will need to > coordinate uber/lyft transport but that hasn't been a problem in the > past. > > Lets meet at 6:30pm (I can send specific location once onsite) and head > over to Lowry. If the weather looks terrible I can call ahead and see > if their indoor area is open and if they say it is "meh" we'll find > something closer to the conference center. Also, they close at 9pm > which should force us to get some sleep :) > > Finally, Monday is a good day because it is gertty's birthday. Hope to > see you then. > Also Tuesday night is the official Party event. Sign up at https://www.eventbrite.com/e/the-denver-party-during-open-infrastructure-summit-tickets-58863817262 with password "denver". If you are like me and don't want to give out a phone number just enter "555-555-5555" in that field. These details apparently went out to attendees already but I didn't get said email so posting it here just in case it is useful for others too. Clark From pabelanger at redhat.com Wed Apr 24 16:49:42 2019 From: pabelanger at redhat.com (Paul Belanger) Date: Wed, 24 Apr 2019 12:49:42 -0400 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together In-Reply-To: <4be21a02-4e7e-4ee0-a604-10898d419282@www.fastmail.com> References: <4be21a02-4e7e-4ee0-a604-10898d419282@www.fastmail.com> Message-ID: <20190424164942.GC32664@localhost.localdomain> On Wed, Apr 24, 2019 at 12:31:05PM -0400, Clark Boylan wrote: > On Wed, Apr 24, 2019, at 9:14 AM, Clark Boylan wrote: > > Hello Infra! > > > > Monday evening is looking like a good night to have a low key informal > > team gathering. The only official event on the calendar is the > > Marketplace Mixer which runs until 7pm. Weather permitting I'd like to > > head back to Lowry Beer Garden (where we've gone at past PTGs). It is a > > bit out of the way from the conference center so we will need to > > coordinate uber/lyft transport but that hasn't been a problem in the > > past. > > > > Lets meet at 6:30pm (I can send specific location once onsite) and head > > over to Lowry. If the weather looks terrible I can call ahead and see > > if their indoor area is open and if they say it is "meh" we'll find > > something closer to the conference center. Also, they close at 9pm > > which should force us to get some sleep :) > > > > Finally, Monday is a good day because it is gertty's birthday. Hope to > > see you then. > > > > Also Tuesday night is the official Party event. Sign up at https://www.eventbrite.com/e/the-denver-party-during-open-infrastructure-summit-tickets-58863817262 with password "denver". If you are like me and don't want to give out a phone number just enter "555-555-5555" in that field. > > These details apparently went out to attendees already but I didn't get said email so posting it here just in case it is useful for others too. > Since I won't be in Denver next week, have a great time. The beer garden is a great choice. - Paul From cboylan at sapwetik.org Wed Apr 24 21:38:42 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Wed, 24 Apr 2019 17:38:42 -0400 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together In-Reply-To: References: Message-ID: <3add5880-c768-45b1-9dc8-ecf067ee2f91@www.fastmail.com> On Wed, Apr 24, 2019, at 9:14 AM, Clark Boylan wrote: > Hello Infra! > > Monday evening is looking like a good night to have a low key informal > team gathering. The only official event on the calendar is the > Marketplace Mixer which runs until 7pm. Weather permitting I'd like to > head back to Lowry Beer Garden (where we've gone at past PTGs). It is a > bit out of the way from the conference center so we will need to > coordinate uber/lyft transport but that hasn't been a problem in the > past. > > Lets meet at 6:30pm (I can send specific location once onsite) and head > over to Lowry. If the weather looks terrible I can call ahead and see > if their indoor area is open and if they say it is "meh" we'll find > something closer to the conference center. Also, they close at 9pm > which should force us to get some sleep :) > > Finally, Monday is a good day because it is gertty's birthday. Hope to > see you then. Hey, it was pointed out that there is a really good chance that Zuul will be confirmed as a top level OSF project at the board meeting on Sunday. This seems like an excellent thing to celebrate as well, and given the overlap between Zuul and Infra teams I think we should celebrate that together. Don’t want to put the cart before the horse though, so we can wait until we know for sure before we put a label on it. But please go ahead and mark Monday evening for Zuul too just in case. Also looking at the weather more closely it will be about 50F/11C with rain and wind Monday evening, so Lowry may not be the best choice. It has been pointed out that For The Win Denver would be willing to take us as an informal group and we can play arcade games indoors instead. They have food and drinks too. As things firm up I'll send an update to this email with concrete time and location details. Clark From whayutin at redhat.com Thu Apr 25 02:39:32 2019 From: whayutin at redhat.com (Wesley Hayutin) Date: Wed, 24 Apr 2019 20:39:32 -0600 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together In-Reply-To: <3add5880-c768-45b1-9dc8-ecf067ee2f91@www.fastmail.com> References: <3add5880-c768-45b1-9dc8-ecf067ee2f91@www.fastmail.com> Message-ID: Just some local input.. That is a long way to go from downtown. There are plenty of outdoor venues with great beer a little closer. You might want to try a personal favorite [1], there are ton of other breweries around odell as well. Hard to go wrong there. Either way, enjoy your time in Denver! [1] https://www.odellbrewing.com/taproom-denver/ On Wed, Apr 24, 2019 at 3:43 PM Clark Boylan wrote: > On Wed, Apr 24, 2019, at 9:14 AM, Clark Boylan wrote: > > Hello Infra! > > > > Monday evening is looking like a good night to have a low key informal > > team gathering. The only official event on the calendar is the > > Marketplace Mixer which runs until 7pm. Weather permitting I'd like to > > head back to Lowry Beer Garden (where we've gone at past PTGs). It is a > > bit out of the way from the conference center so we will need to > > coordinate uber/lyft transport but that hasn't been a problem in the > > past. > > > > Lets meet at 6:30pm (I can send specific location once onsite) and head > > over to Lowry. If the weather looks terrible I can call ahead and see > > if their indoor area is open and if they say it is "meh" we'll find > > something closer to the conference center. Also, they close at 9pm > > which should force us to get some sleep :) > > > > Finally, Monday is a good day because it is gertty's birthday. Hope to > > see you then. > > Hey, it was pointed out that there is a really good chance that Zuul will > be confirmed as a top level OSF project at the board meeting on Sunday. > This seems like an excellent thing to celebrate as well, and given the > overlap between Zuul and Infra teams I think we should celebrate that > together. > > Don’t want to put the cart before the horse though, so we can wait until > we know for sure before we put a label on it. But please go ahead and mark > Monday evening for Zuul too just in case. > > Also looking at the weather more closely it will be about 50F/11C with > rain and wind Monday evening, so Lowry may not be the best choice. It has > been pointed out that For The Win Denver would be willing to take us as an > informal group and we can play arcade games indoors instead. They have food > and drinks too. > > As things firm up I'll send an update to this email with concrete time and > location details. > > 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 xmzheng at cn.ibm.com Thu Apr 25 09:16:24 2019 From: xmzheng at cn.ibm.com (Xiao Mei GZ Zheng) Date: Thu, 25 Apr 2019 09:16:24 +0000 Subject: [OpenStack-Infra] Post opendev git repo hosting status repo In-Reply-To: <0ac69311-1f9b-4265-96f5-06b6bb8adff7@www.fastmail.com> References: <0ac69311-1f9b-4265-96f5-06b6bb8adff7@www.fastmail.com>, <8ad20ab9-96c8-41c6-888a-ae67402f8470@www.fastmail.com> Message-ID: An HTML attachment was scrubbed... URL: From fungi at yuggoth.org Thu Apr 25 12:51:24 2019 From: fungi at yuggoth.org (Jeremy Stanley) Date: Thu, 25 Apr 2019 12:51:24 +0000 Subject: [OpenStack-Infra] Post opendev git repo hosting status repo In-Reply-To: References: <0ac69311-1f9b-4265-96f5-06b6bb8adff7@www.fastmail.com> <8ad20ab9-96c8-41c6-888a-ae67402f8470@www.fastmail.com> Message-ID: <20190425125124.qwxkzt5hqcylkknb@yuggoth.org> On 2019-04-25 09:16:24 +0000 (+0000), Xiao Mei GZ Zheng wrote: > Is there any suggestion for the bug in CI system since OpenDev git hosting > migration? Thanks. > > + git clone git://git.openstack.org/openstack-infra/devstack-gate > Cloning into 'devstack-gate'... > fatal: unable to connect to git.openstack.org: > git.openstack.org[0: 23.253.125.17]: errno=No route to host > git.openstack.org[1: 2001:4800:7817:103:be76:4eff:fe04:e3e3]: errno=Cannot assign requested address [...] Yes, as announced in advance of the change, we are no longer able to support traditional git:// protocol connections. If you switch your clone URLs to https:// or http:// then they should otherwise work as before. -- 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 sgw at linux.intel.com Thu Apr 25 14:19:34 2019 From: sgw at linux.intel.com (Saul Wold) Date: Thu, 25 Apr 2019 07:19:34 -0700 Subject: [OpenStack-Infra] [Starlingx-discuss] StarlingX / Infra teams sync-up at PTG In-Reply-To: References: <1b8469d0-387f-4853-b487-f9519dcc5130@linux.intel.com> Message-ID: On 4/24/19 8:50 AM, Clark Boylan wrote: > > > On Tue, Apr 23, 2019, at 4:55 PM, Saul Wold wrote: >> >> >> Infra Team, >> >> The StarlingX Project would like to request a 30-60 minute sync up to >> talk about some of the challenges that StarlingX faces with regards to >> build and test infrastructure. >> >> As StarlingX is an integration project that creates a Linux Distribution >> with a Cloud infrastructure on top of it, this makes it more challenging >> to both build and test. The current OpenStack Foundation infrastructure >> is good as building and testing projects such as Nova, Neutron, ... It >> could be used to build and test the individual components of the >> StarlingX Flock, such as Fault and others. It's not well suited to build >> the complete StarlingX ISO and test that ISO. >> >> We want to explore what the existing resources that are available and >> understand how and what we can add to the infrastructure to enable the >> build and testing that StarlingX will require. >> >> We hope that we can find an hour timeslot during the PTG that we can >> talk further about this with both teams. Our timeslots overlap Thrusday >> afternoon and Friday so we could put it on our adgendas. >> >> Please let us know if you have available time slots. > > I'm thinking the best day for us is Friday (we'll want to dig into our team specific items on Thursday). Does Just after the lunch break on Friday (say 1:30pm) in the Infra/QA room work? If so we'll see you there. I'll go ahead and add you to our etherpad [0] as I'm editing that today too. > Clark, We just confirmed the time in the StarlingX TSC. A few of us will break off and join you in the Infra/QA Room at 1:30 for about 30 minutes. Looking forward to a great Summit / PTG and meeting with you guys. Sau! > [0] https://etherpad.openstack.org/p/2019-denver-ptg-infra-planning > > Clark > > _______________________________________________ > Starlingx-discuss mailing list > Starlingx-discuss at lists.starlingx.io > http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss > From eumel at arcor.de Fri Apr 26 15:56:31 2019 From: eumel at arcor.de (Frank Kloeker) Date: Fri, 26 Apr 2019 17:56:31 +0200 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <637bb834fdbf28b90c9703630aa1b17c@arcor.de> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> <20190408071358.GA2779@fedora19.localdomain> <637bb834fdbf28b90c9703630aa1b17c@arcor.de> Message-ID: Am 2019-04-19 18:57, schrieb Frank Kloeker: > Am 2019-04-08 09:13, schrieb Ian Wienand: >> On Tue, Apr 02, 2019 at 12:28:31PM +0200, Frank Kloeker wrote: >>> The OpenStack I18n team was aware about the fact, that we will run >>> into an >>> unsupported platform in the near future and started an investigation >>> about >>> the renew of translation platform on [1]. >>> [1] >>> https://blueprints.launchpad.net/openstack-i18n/+spec/renew-translation-platform >> >> I took an action item to do some investigation in the infra meeting. >> From the notes above, for last iteration it looks like it came down to >> Zanata v Poodle. However when I look at [1] Poodle doesn't look >> terribly active. >> >> It looks like Fedora haven't made any choices around which way to >> go, but weblate has been suggested [2]. >> >> Looking at weblate, it seems to have a few things going for it from >> the infra point of view >> >> * it seems active >> * it's a python/django app which fits our deployments and general >> skills better than java >> * has a docker project [3] so has interest in containerisation >> * we currently put translations in, and propose them via jobs >> triggered periodically using the zanata CLI tool as described at >> [4]. weblate has a command-line client that looks to me like it can >> do roughly what we do now [5] ... essentially integrate with jobs to >> upload new translations into the tool, and extract the translations >> and put them into gerrit. >> * That said, it also seems we could integrate with it more "directly" >> [6]; it seems it can trigger imports of translations from git repos >> via webhooks (focused on github, but we could do similar with a post >> job) and also propose updates directly to gerrit (using git-review; >> documentation is light on this feature but it is there). It looks >> like (if I'm reading it right) we could move all configuration in a >> .weblate file per-repo, which suits our distributed model. > > > Hi Ian, > > thanks for taking a first look on Weblate. It looks also interesting > to me. I tried a first test installation and there are also some > advantages from I18n perspective: > * automatic syntax check on translation strings [1]. In the past we > had often format errors on Python strings, which are not easy to spot. > Also when we started with hard syntax check on sphinx-build few weeks > ago, it seems that we can cover such kind of errors in Weblate UI > * Machine Translating backends [2]. It's not a shame to use Google > Translate instead a paper dictionary. I think it's usual in most of > the translation teams. Zanata started to develop such kind of stuff, > which is in Weblate already included. Most of the MT services are paid > service. I would try to get in touch with Deepl (a German company) to > sponsor us. Or there is also a way to implement our own MT service, if > there is a OpenStack project or SIG, which is looking for a senseful > use case in AI. > > Weblate holds his own VCS and commits each translation into the local > repo. Sync with upstream can be automtically or by hand with wlc > client. I saw also Gerrit backend, without any further documentation. > > I think it's a lots of work. First step would be write down all that > workflows and use cases what we need for a migration. > >> The other thing is, I noticed that weblate has hosted options. If the >> CI integration is such that it's importing via webhooks, and proposing >> reviews then it seems like this is essentially an unprivileged app. >> We have sunk a lot of collective time and resources into Zanata >> deployment and we should probably do a real cost-benefit analysis once >> we have some more insights. > > Following the prize table on [3] we're far away from the Enterprise > account with only 20 repos. Self-hosting and installation of the plain > app is not a big deal, I think. Most of the work will be setup > projects and sync translations in and out. On the other hand that > could be easier with technics what you mentioned. Just as a follow up: I've wrote down all required steps and ideas for a migration to Weblate on [1]. There are some issues adressed but thats not unsolvable (i.e. invent openstackid as a OpenId provider). First big steps are almost done. Gerrit integration is working out of the box [2]. The workflow will be much easier in the future. Beside proposals every 24 hours, also ad hoc proposals are possible. So translations will be get faster into repos. The other way around is also tested: Webhook with Github is working to push translations to Weblate. I saw Gitea has a simlar feature - so that should also work out and faster as the current way. A rough installation procedere is on [3], including a semi automatation to setup projects. kind regards Frank [1] https://etherpad.openstack.org/p/I18n-weblate-migration [2] https://review-dev.openstack.org/#/c/107999/ [3] https://github.com/eumel8/ansible-weblate From corvus at inaugust.com Fri Apr 26 16:31:45 2019 From: corvus at inaugust.com (James E. Blair) Date: Fri, 26 Apr 2019 09:31:45 -0700 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: (Frank Kloeker's message of "Fri, 26 Apr 2019 17:56:31 +0200") References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> <20190408071358.GA2779@fedora19.localdomain> <637bb834fdbf28b90c9703630aa1b17c@arcor.de> Message-ID: <87h8akiv7y.fsf@meyer.lemoncheese.net> Frank Kloeker writes: > Just as a follow up: I've wrote down all required steps and ideas for > a migration to Weblate on [1]. Thanks for that! Will this be a topic at the PTG? > There are some issues adressed but thats not unsolvable (i.e. invent > openstackid as a OpenId provider). We may want to think about deploying this in OpenDev, so the openstackid provider may not be as critical (likely one option among many). Though we still may want to wait until it's a choice before we deploy it. > First big steps are almost done. Gerrit integration is working out of > the box [2]. The workflow will be much easier in the future. Beside > proposals every 24 hours, also ad hoc proposals are possible. So > translations will be get faster into repos. > The other way around is also tested: Webhook with Github is working to > push translations to Weblate. I saw Gitea has a simlar feature - so > that should also work out and faster as the current way. > A rough installation procedere is on [3], including a semi > automatation to setup projects. We are no longer replicating all projects to Github, so I don't think we want to build any tooling that depends on that. We could do something with Gitea, however, I'd prefer to continue treating it as a simple read-only mirror at the moment. So for getting data into Weblate, I think we should look at using Zuul for that. Post-merge jobs could push changes to Weblate fairly easily. It looks like that's one of the options in the etherpad, with "wlc pull". -Jim From cboylan at sapwetik.org Fri Apr 26 22:18:59 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Fri, 26 Apr 2019 18:18:59 -0400 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together In-Reply-To: References: <3add5880-c768-45b1-9dc8-ecf067ee2f91@www.fastmail.com> Message-ID: <55c34b63-19e2-4420-965f-ac1b4ed4c5c5@www.fastmail.com> On Wed, Apr 24, 2019, at 7:40 PM, Wesley Hayutin wrote: > Just some local input.. > That is a long way to go from downtown. There are plenty of outdoor > venues with great beer a little closer. You might want to try a > personal favorite [1], there are ton of other breweries around odell as > well. Hard to go wrong there. Either way, enjoy your time in Denver! > > [1] https://www.odellbrewing.com/taproom-denver/ Yup, I know it is a bit of a trek, but we've gone to Lowry's each of the last two PTGs in Denver. It would be great to get back. That said the forecast for Monday night/Tuesday morning continues to look less and less pleasant so I think for Monday night team activities our best bet may be to stick closer to the event venue and be indoors. As I mentioned before I'll send concrete details once onsite, but I would expect we go to FTW Denver at this point. Clark From eumel at arcor.de Sat Apr 27 01:56:21 2019 From: eumel at arcor.de (Frank Kloeker) Date: Sat, 27 Apr 2019 03:56:21 +0200 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <87h8akiv7y.fsf@meyer.lemoncheese.net> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> <20190408071358.GA2779@fedora19.localdomain> <637bb834fdbf28b90c9703630aa1b17c@arcor.de> <87h8akiv7y.fsf@meyer.lemoncheese.net> Message-ID: <7e77db30a3b868c6b83bb214e6524c0f@arcor.de> Am 2019-04-26 18:31, schrieb corvus at inaugust.com: > Frank Kloeker writes: > >> Just as a follow up: I've wrote down all required steps and ideas for >> a migration to Weblate on [1]. > > Thanks for that! Will this be a topic at the PTG? Not yet. I've just created our team Etherpad [1] and I think it makes sense to discuss this onsite. Proposed day is Thursday, May 2, no time specs so far. >> There are some issues adressed but thats not unsolvable (i.e. invent >> openstackid as a OpenId provider). > > We may want to think about deploying this in OpenDev, so the > openstackid > provider may not be as critical (likely one option among many). Though > we still may want to wait until it's a choice before we deploy it. For the OpenID provider python-social-auth is used. I made a pull request on [2] and asked Jimmy and Sebastian for help. That seems to me to be the best experts for this OpenStackID. >> First big steps are almost done. Gerrit integration is working out of >> the box [2]. The workflow will be much easier in the future. Beside >> proposals every 24 hours, also ad hoc proposals are possible. So >> translations will be get faster into repos. >> The other way around is also tested: Webhook with Github is working to >> push translations to Weblate. I saw Gitea has a simlar feature - so >> that should also work out and faster as the current way. >> A rough installation procedere is on [3], including a semi >> automatation to setup projects. > > We are no longer replicating all projects to Github, so I don't think > we > want to build any tooling that depends on that. We could do something > with Gitea, however, I'd prefer to continue treating it as a simple > read-only mirror at the moment. So for getting data into Weblate, I > think we should look at using Zuul for that. Post-merge jobs could > push > changes to Weblate fairly easily. It looks like that's one of the > options in the etherpad, with "wlc pull". Github was only an example. If a test repo like gtest would be synced from review-dev to Gitea we can test the webhook. But what I said, it should work in the same similarity. The biggest problem at the moment are pot files. Weblate expects this in the source repo which we haven't. But Weblate has it's own local repos. It's not clear at the moment how we design the workflow. Zuul can also push changes on rst files in the Weblate repo and Weblate can build pot files there. It's to think about it. kind regards Frank [1] https://etherpad.openstack.org/p/docs-i18n-ptg-train [2] https://github.com/python-social-auth/social-core/pull/359 From aj at suse.com Sun Apr 28 08:01:46 2019 From: aj at suse.com (Andreas Jaeger) Date: Sun, 28 Apr 2019 10:01:46 +0200 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <7e77db30a3b868c6b83bb214e6524c0f@arcor.de> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> <20190408071358.GA2779@fedora19.localdomain> <637bb834fdbf28b90c9703630aa1b17c@arcor.de> <87h8akiv7y.fsf@meyer.lemoncheese.net> <7e77db30a3b868c6b83bb214e6524c0f@arcor.de> Message-ID: <9b3d34bd-4107-d849-6212-ca69653f6e57@suse.com> On 27/04/2019 03.56, Frank Kloeker wrote: > [...] > The biggest problem at the moment are pot files. Weblate expects this in > the source repo which we haven't. But Weblate has it's own local repos. > It's not clear at the moment how we design the workflow. Zuul can also > push changes on rst files in the Weblate repo and Weblate can build pot > files there. It's to think about it. Pot files are generated files, so there's always an extra step to create them and keep them in sync. I see the following options: * Ensure that users update pot files. That will leads to many conflicts and rebases, so is out. * Have a job that writes to gerrit. We're not doing anything like that in OpenStack by policy. * Have a separate place that stores pot files. We use with translate.o.o the third way and store the pot files directly in translate.o.o. We could generate a special "pot-files repo" that is used for syncing. Pushing rst files to Weblate could work as well - but we also have repos like tripleo-ui that use JSON and not rst, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From aj at suse.com Sun Apr 28 07:55:58 2019 From: aj at suse.com (Andreas Jaeger) Date: Sun, 28 Apr 2019 07:55:58 +0000 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <7e77db30a3b868c6b83bb214e6524c0f@arcor.de> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> <20190408071358.GA2779@fedora19.localdomain> <637bb834fdbf28b90c9703630aa1b17c@arcor.de> <87h8akiv7y.fsf@meyer.lemoncheese.net> <7e77db30a3b868c6b83bb214e6524c0f@arcor.de> Message-ID: On 27/04/2019 03.56, Frank Kloeker wrote: > [...] > The biggest problem at the moment are pot files. Weblate expects this in > the source repo which we haven't. But Weblate has it's own local repos. > It's not clear at the moment how we design the workflow. Zuul can also > push changes on rst files in the Weblate repo and Weblate can build pot > files there. It's to think about it. Pot files are generated files, so there's always an extra step to create them and keep them in sync. I see the following options: * Ensure that users update pot files. That will leads to many conflicts and rebases, so is out. * Have a job that writes to gerrit. We're not doing anything like that in OpenStack by policy. * Have a separate place that stores pot files. We use with translate.o.o the third way and store the pot files directly in translate.o.o. We could generate a special "pot-files repo" that is used for syncing. Pushing rst files to Weblate could work as well - but we also have repos like tripleo-ui that use JSON and not rst, Andreas -- Andreas Jaeger aj@{suse.com,opensuse.org} Twitter: jaegerandi SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GF: Felix Imendörffer, Mary Higgins, Sri Rasiah HRB 21284 (AG Nürnberg) GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126 From cboylan at sapwetik.org Sun Apr 28 17:27:39 2019 From: cboylan at sapwetik.org (Clark Boylan) Date: Sun, 28 Apr 2019 13:27:39 -0400 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together In-Reply-To: <55c34b63-19e2-4420-965f-ac1b4ed4c5c5@www.fastmail.com> References: <3add5880-c768-45b1-9dc8-ecf067ee2f91@www.fastmail.com> <55c34b63-19e2-4420-965f-ac1b4ed4c5c5@www.fastmail.com> Message-ID: On Fri, Apr 26, 2019, at 3:19 PM, Clark Boylan wrote: > On Wed, Apr 24, 2019, at 7:40 PM, Wesley Hayutin wrote: > > Just some local input.. > > That is a long way to go from downtown. There are plenty of outdoor > > venues with great beer a little closer. You might want to try a > > personal favorite [1], there are ton of other breweries around odell as > > well. Hard to go wrong there. Either way, enjoy your time in Denver! > > > > [1] https://www.odellbrewing.com/taproom-denver/ > > Yup, I know it is a bit of a trek, but we've gone to Lowry's each of > the last two PTGs in Denver. It would be great to get back. That said > the forecast for Monday night/Tuesday morning continues to look less > and less pleasant so I think for Monday night team activities our best > bet may be to stick closer to the event venue and be indoors. > > As I mentioned before I'll send concrete details once onsite, but I > would expect we go to FTW Denver at this point. Zuul has been confirmed. Given that, I'm more than happy to have an Infra + Zuul team gathering Monday evening. We can celebrate Gertty's birthday and Zuul's confirmation :) Let's meet in front of the big blue bear statue at the convention center at 6:45pm Monday evening. From there we'll go to FTW Denver. Unfortunately, the weather calls for heavy rain and possibly snow Monday night so Lowry seems like a bad choice Monday. I'm told that we can wait inside of the convention center near the bear (it is public space) which is probably a good idea if it is pouring rain. Looking forward to seeing you there! Clark From anteaya at anteaya.info Sun Apr 28 18:59:52 2019 From: anteaya at anteaya.info (Anita Kuno) Date: Sun, 28 Apr 2019 14:59:52 -0400 Subject: [OpenStack-Infra] Low Key Monday Evening Get Together In-Reply-To: References: <3add5880-c768-45b1-9dc8-ecf067ee2f91@www.fastmail.com> <55c34b63-19e2-4420-965f-ac1b4ed4c5c5@www.fastmail.com> Message-ID: <36e81af4-95ff-7f8b-3712-e089825c4891@anteaya.info> On 2019-04-28 1:27 p.m., Clark Boylan wrote: > Zuul has been confirmed. Congratulations Zuul team. Hope you have a lovely celebration. Anita From eumel at arcor.de Mon Apr 29 02:18:30 2019 From: eumel at arcor.de (Frank Kloeker) Date: Mon, 29 Apr 2019 04:18:30 +0200 Subject: [OpenStack-Infra] Zanata broken on Bionic In-Reply-To: <9b3d34bd-4107-d849-6212-ca69653f6e57@suse.com> References: <2f1d4457-284b-8378-d05a-3de74f6d2e85@suse.com> <20190325221402.GD1161@fedora19.localdomain> <26189c0004b71b6eb244f70a3ed86b91@arcor.de> <20190408071358.GA2779@fedora19.localdomain> <637bb834fdbf28b90c9703630aa1b17c@arcor.de> <87h8akiv7y.fsf@meyer.lemoncheese.net> <7e77db30a3b868c6b83bb214e6524c0f@arcor.de> <9b3d34bd-4107-d849-6212-ca69653f6e57@suse.com> Message-ID: <22c98d8d164cf310f303bd63d7abd48e@arcor.de> Am 2019-04-28 10:01, schrieb Andreas Jaeger: > On 27/04/2019 03.56, Frank Kloeker wrote: >> [...] >> The biggest problem at the moment are pot files. Weblate expects this >> in >> the source repo which we haven't. But Weblate has it's own local >> repos. >> It's not clear at the moment how we design the workflow. Zuul can also >> push changes on rst files in the Weblate repo and Weblate can build >> pot >> files there. It's to think about it. > > Pot files are generated files, so there's always an extra step to > create > them and keep them in sync. > > I see the following options: > * Ensure that users update pot files. That will leads to many conflicts > and rebases, so is out. > * Have a job that writes to gerrit. We're not doing anything like that > in OpenStack by policy. > * Have a separate place that stores pot files. > > We use with translate.o.o the third way and store the pot files > directly > in translate.o.o. We could generate a special "pot-files repo" that is > used for syncing. Yes, I read it in the documentation. Weblate has internal git repos and the use case was to generate a master component for the external sync and then create from them other components in the same project. I think it was nearly what we want. It's somewhere here: https://docs.weblate.org/en/latest/devel/translations.html https://docs.weblate.org/en/latest/vcs.html > Pushing rst files to Weblate could work as well - but we also have > repos > like tripleo-ui that use JSON and not rst, That's supported, but tripleo-ui goes deprecated: https://docs.weblate.org/en/latest/formats.html#json-files https://review.opendev.org/#/c/641744/ Frank From amoralej at redhat.com Tue Apr 30 14:50:43 2019 From: amoralej at redhat.com (Alfredo Moralejo Alonso) Date: Tue, 30 Apr 2019 16:50:43 +0200 Subject: [OpenStack-Infra] Move packstack from openstack to redhat-openstack organization in github Message-ID: Hi, After migration to opendev an moving openstack/packstack to x/packstack, mirroring to github has been lost as announced in [1]. Could we get the repository moved to redhat-openstack organization in github?, we'd like to get redirection from old repo to the new one what's require to transfer the repo using github iiuc. Best regards, Alfredo [1] http://lists.openstack.org/pipermail/openstack-discuss/2019-April/005629.html -------------- next part -------------- An HTML attachment was scrubbed... URL: