- service-announce - lists.opendev.org

Enabling Gerrit Hashtags For All Registered Users
by Clark Boylan 28 May '25

28 May '25

For some time now Gerrit has supported HashTags as an alternative to Change Topics. Over time Change Topics have evolved for most Gerrit installations to indicate common sets of work that should be merged together when submitWholeTopic is enabled. In these situations the expectation is that you would use HashTags to annotate Changes with information that we have often used Change Topics for within OpenDev. To catch up with the rest of the Gerrit community OpenDev will enable HashTags by default for all Registered Users on June 3, 2025. This will allow you to edit HashTags on any change as long as you are logged in. Some projects have already enabled this feature for specific groups of users. This change will override those existing rules enabling HashTags for all Registered Users on those projects too. The number of projects this affects is quite small, but let us know if you have any questions or concerns. Clark

1 0

review.opendev.org Gerrit Outage April 21, 2025
by Clark Boylan 11 Apr '25

11 Apr '25

The OpenDev team will shut down Gerrit services on review.opendev.org at 16:00 UTC April 21, 2025 in order to migrate and upgrade the underlying server instance. The work is expected to take about an hour and should largely be transparent to users other than the required outage. One thing users may notice is the IP Addresses for review.opendev.org will change. If you need to update your firewall rules you can do so by allowing TCP port 443 and TCP port 29418 to: 162.253.55.233 2604:e100:1:0:f816:3eff:fe31:926a These IPs belong to the new review03.opendev.org server which will replace review02.opendev.org. Let us know if you have any questions or concerns. Clark

1 0

bindep 2.12.0
by Jeremy Stanley 24 Jan '25

24 Jan '25

I've released bindep 2.12.0 just now. These are the highlights: New Features ------------ * Basic support for PopOS is now included. Upgrade Notes ------------- * Python 2.7 and 3.5 are no longer supported. * Bindep now depends on the distro python library to determine details about the current platform. This library looks at both /etc/os-release and lsb_release to find platform info. The os-release file data is preferred and at times has slightly different data than lsb_release. Every effort has been made to make this transition backward compatible but some things may have been missed. The motivation for this change is that not all distros have lsb_release available and we can let the distro library sort that out for us. -- Jeremy Stanley

1 0

Planned outage for mailing lists on Monday 2024-12-02 15:00-17:00 UTC
by Jeremy Stanley 27 Nov '24

27 Nov '24

The OpenDev Sysadmins will be performing maintenance on our mailing list server between 15:00 and 17:00 UTC on Monday, 2024-12-02. During this time, messages to and from the lists for all our sites will be held temporarily while we make adjustments in the backing database for renaming one of the domains in use. Web archives may be unavailable for part of the time as well. The outage should start some time around 15:00 UTC and is not expected to last more than two hours (but will hopefully conclude far more quickly). Please follow up (either to the service-discuss(a)lists.opendev.org mailing list or to me personally) with any questions you may have on this activity. -- Jeremy Stanley, OpenDev Systems Administrator

1 0

Upgrading OpenDev's Gerrit Server on December 6, 2024 at 16:00 UTC
by Clark Boylan 13 Nov '24

13 Nov '24

The OpenDev team will be upgrading the Gerrit server on review.opendev.org on December 6, 2024 at 16:00 UTC. This will require a short downtime of the service if everything goes well and a longer downtime if we need to revert. We are allocating an hour (16:00 - 17:00 UTC) for this work. We will upgrade from Gerrit 3.9 to 3.10 remaining approximately one release behind the latest Gerrit release as long as the Gerrit 3.11 release happens on time this month. Gerrit 3.10 brings a number of changes including many performance improvements and fewer email notifications. The upstream release notes [0] cover these updates in much more detail if you are interested. Let us know if you have any questions or concerns. [0] https://www.gerritcodereview.com/3.10.html Clark

1 0

Pruning OpenDev's Intermediate Registry on insecure-ci-registry.opendev.org November 15, 2024
by Clark Boylan 06 Nov '24

06 Nov '24

The OpenDev team will begin some long overdue pruning of the storage system behind the intermediate container registry running on insecure-ci-registry.opendev.org on November 15, 2024. The last time we tried this we believe container image client errors were due to the pruning. Unfortunately, we don't have enough information to know if this will happen again. For this reason we will be prepared to replace the entire Swift container on the backend and start over fresh if necessary. We ask that you report any unexpected client behaviors with the intermediate registry on or after November 15, 2024. Additionally, if we do end up replacing the entire backend storage container we will lose all intermediate container image state. If this happens, jobs relying on state in the intermediate registry may fail. In those cases you may need to recheck jobs that build the images or merge additional changes to refresh the content in the intermediate registry. Clark

1 0

Switching OpenDev's Default Zuul Nodeset to ubuntu-noble
by Clark Boylan 15 Aug '24

15 Aug '24

The OpenDev team plans to switch the default nodeset in our Zuul base jobs from ubuntu-jammy to ubuntu-noble on August 21, 2024. The new release has been available for several months now and we have jobs relying on it. One of the last steps in the Noble rollout is to switch the default over. This change will impact any jobs that don't explicitly override the nodeset as they will start running on the newer Ubuntu release after this change. If this creates problems for your jobs you can either override the nodeset to ubuntu-jammy forcing the job to run on the nodes used before this change, or you can update your job to accommodate whatever changes the newer version of Ubuntu requires. If you have any questions or concerns feel free to respond to this email or reach out via IRC. For OpenStack in particular, we've been told that they expect most jobs to already override the nodeset and this change will largely be a noop for them. Clark

1 0

Removal of Inactive Projects from Zuul's Tenant Configuration
by Clark Boylan 10 Jul '24

10 Jul '24

The OpenDev team is going to start removing inactive x/* namespace projects from Zuul's tenant configuration. The two primary motivations behind this are to remove projects that already have broken configurations within Zuul (see the Zuul config errors page [0]), and to avoid projects entering this state in the future as we clean up test nodes like Ubuntu Xenial or CentOS 8 Stream or otherwise modernize the CI system. Removal from Zuul's tenant configuration is a lightweight method of ensuring we're addressing problems with active projects that can be fixed without the added noise from projects that are unlikely to fix things on their own. A first pass at this sort of cleanup is being done with this change [1]. Feel free to chime in if you know there is already work underway to correct x/* projects' config errors, or if you know of any additional projects that should be removed from Zuul. We aim to merge this change on July 16, 2024. It should be noted that if projects do become active again and have volunteers willing to correct the CI configuration state, it is straightforward to add the project back into Zuul enabling that effort to progress. Projects will simply add themselves back to the tenant configuration and then push changes to fix the CI config. [0] https://zuul.opendev.org/t/openstack/config-errors [1] https://review.opendev.org/c/openstack/project-config/+/923509 Clark

1 0

CentOS 8 Stream End of Life and Removal from OpenDev CI
by Clark Boylan 20 Jun '24

20 Jun '24

Hello everyone, I wanted to give you a heads up that CentOS 8 Stream has reached its end of life and the upstream package repos have been removed. Our mirrors have faithfully replicated the empty mirror content (there is only a readme file now [0]). The end result of which is failing CI jobs if the jobs run on CentOS 8 Stream. The OpenDev team intends on removing these nodes from Zuul and Nodepool in the near future as jobs can no longer successfully run on CentOS 8 Stream. Projects should check their CI jobs (on older branches too) and either remove jobs that rely on CentOS 8 Stream or update those jobs to run on a different platform. [0] https://mirror.dfw.rax.opendev.org/centos/8-stream/readme Clark

1 0

Ubuntu Noble Test Nodes Now Available in Zuul
by Clark Boylan 24 May '24

24 May '24

The OpenDev team has added Ubuntu Noble test nodes to Zuul and Nodepool. This means you can start running jobs on the latest Ubuntu release using `nodeset: ubuntu-noble` or `nodeset: ubuntu-noble-arm64`. If you build your own custom nodesets the labels you will want to use are `ubuntu-noble` and `ubuntu-noble-arm64`. We expect these to generally work and have already successfully run a number of builds on the new nodes. That said they are new, and you may need updates to bindep files and/or Ansible roles and playbooks. Let us know if you have any questions or find problems. Clark

1 0

Gerrit Downtime on May 31, 2024 at 16:00 UTC
by Clark Boylan 22 May '24

22 May '24

Hello, The OpenDev team is planning to upgrade Gerrit on review.opendev.org to version 3.9 on May 31, 2024 beginning at 16:00 UTC. In order to perform this upgrade we require a short service outage. We are allocating an hour for this outage, from 16:00 to 17:00 UTC, as that should give us plenty of time to implement the rollback procedure if that becomes necessary. The Gerrit 3.9 release notes can be found here: https://www.gerritcodereview.com/3.9.html. One major feature our users may be interested in is the ability to suggest and apply updates to files via review comments. If you have any questions about the upgrade or the new version of Gerrit, feel free to reach out to the OpenDev team via this email thread or on IRC in #opendev on OFTC. Clark

1 0

Gerrit Outage for Project Renames Monday April 22, 2024 at 20:00 UTC
by Clark Boylan 17 Apr '24

17 Apr '24

The OpenDev team is planning a scheduled Gerrit service outage on review.opendev.org in order to rename projects. This outage will occur on Monday April 22, 2024 at 20:00 UTC until 21:00 UTC. If you have a project you would like to rename please get in touch with the OpenDev team soon (you can respond to this email or find us in #opendev on the OFTC IRC network). Please reach out if you have any questions or concerns. The same methods described above work for that too. Clark

1 0

CVE-2024-31497 and SSH key statistics
by Jeremy Stanley 16 Apr '24

16 Apr '24

For those of you who haven't seen, CVE-2024-31497 in the PuTTY tool was announced in the past day. If you're using a NIST P521 ECDSA key and have ever used it with affected versions of PuTTY, you should remove its access everywhere and consider it potentially disclosed. Details here: https://www.chiark.greenend.org.uk/~sgtatham/putty/wishlist/vuln-p521-bias.… The key type is generally listed as the first field in the corresponding public key file, or in each line of an authorized_keys entry, including those you may have set for your account in our Gerrit server (review.opendev.org) If the type is listed as ecdsa-sha2-nistp521 or sk-ecdsa-sha2-nistp521(a)openssh.com then it's been put at risk if ever used with PuTTY versions 0.68 through 0.80. On a related note, since I wanted to see how popular that key type is among our Gerrit users, I ran some quick statistics. Of the 36976 accounts created there to date, 19888 of them have SSH keys authorized. There are 35057 total authorized keys, which means accounts with SSH keys average 1.76 keys per account. Out of those keys, 44 claim to be NIST P521 type (0.13%) used by 41 different accounts (0.20% of accounts with keys, 0.11% of all accounts). Here's a breakdown of the most popular types for keys authorized in our Gerrit: 95% ssh-rsa 3.2% ssh-ed25519 1.4% ssh-dss 0.38% ecdsa-sha2-nistp256 0.25% ssh-dsa 0.13% ecdsa-sha2-nistp521 0.023% ecdsa-sha2-nistp384 So as you can see, the key type potentially impacted by CVE-2024-31497 isn't all that popular in our circles, but it's definitely nonzero. -- Jeremy Stanley, OpenDev SysAdmin

1 0

git-review 2.4.0
by Jeremy Stanley 18 Mar '24

18 Mar '24

It's my pleasure to announce the release of git-review 2.4.0. These are the corresponding release notes since the previous release: New Features ------------ * By default, git rebase --abort is run automatically following a failed test rebase, letting the user rebase again on their own if that's the state they want to be in. A -K/--keep-rebase option is added to get the old behavior. * For convenience, --wip is now synonymous with the longer --work-in-progress option. * If HEAD already exists on a remote branch, git review will now only warn and prompt for confirmation when pushing, in order to let the Gerrit server decide whether to accept or reject it. * A copy of the Gerrit upstream project's commit-msg hook is now included directly and written to disk by default rather than pulling a remote copy. This approach is safer and more robust, but may break workflows for sites which rely on users retrieving a customized commit-msg hook. For this reason, a command-line override is provided so that users can, for example, execute git review -s --remote-hook to get the old behavior when setting up a new clone. * The GIT_SSH environment variable will now be consulted, if set, in order to determine which ssh executable to call outside of git invocations, for consistency. * A new --hashtags option allows specifying a list of one or more Gerrit hashtag strings, separated by commas. Note that spaces are not allowed either within a hashtag or between separators. * New --message option can be used to include a custom patchset message when pushing. As always, the latest version of git-review is available from PyPI: https://pypi.org/project/git-review Current documentation can be found here: https://docs.opendev.org/opendev/git-review Its source code can be obtained from the OpenDev Collaboratory: https://opendev.org/opendev/git-review Please don't hesitate to follow up through the service-discuss(a)lists.opendev.org mailing list or in the #opendev channel on the OFTC IRC network if you have any questions. -- Jeremy Stanley

1 0

Removal of Ansible 6 support from OpenDev's Zuul Service
by Clark Boylan 14 Feb '24

14 Feb '24

The Zuul project will be removing Ansible 6 support in preparation for the upcoming Zuul 10.0.0 release. The exact timing of this change isn't known yet, but it may happen as early as this week. OpenDev has automated Zuul upgrades that should pull this change into our Zuul deployment not long after upstream merges the change. We have defaulted to Ansible 8 for many months now, and we don't expect this to create many issues. If you do see issues you will need to update to Ansible 8. Zuul will also be adding support for Ansible 9 in preparation for the upcoming Zuul 10.0.0 release. Once these changes are deployed in OpenDev you may want to start testing your jobs with Ansible 9 to ensure there are no problems with that update. At some point further in the future we will be changing the default Ansible version for OpenDev's Zuul to Ansible 9. Let us know if you have any questions or concerns, Clark

1 0

Upgrading mailing lists on 2023-11-02
by Jeremy Stanley 31 Oct '23

31 Oct '23

On Thursday, November 2, 2023 beginning at 15:30 UTC the OpenDev Collaboratory is upgrading the version of Mailman used to host the Airship, Kata, OpenDev, OpenInfra, OpenStack, StarlingX and Zuul mailing list sites from 3.3.8 to 3.3.9 along with related updates to its various component services (django-mailman3 1.3.9->1.3.11, hyperkitty 1.3.7->1.3.8, postorius 1.3.8->1.3.10, mailman-web 0.0.6->0.0.8). There will be brief downtime for the web interface while services are restarted, and some message deliveries may be briefly delayed but will still eventually be processed. One of the updates includes a database migration that implicitly clears the auth sessions table, so users who were logged into the web interface will be effectively logged out and need to log in again before performing authenticated operations. Web interfaces may have a slightly different look and feel after the update, and some new options too. Changelogs can be found here for anyone interested in seeing a list of what's new: https://docs.mailman3.org/projects/mailman/en/latest/src/mailman/docs/NEWS.… https://gitlab.com/mailman/django-mailman3/-/blob/v1.3.11/README.rst https://gitlab.com/mailman/hyperkitty/-/blob/v1.3.8/doc/news.rst https://gitlab.com/mailman/postorius/-/blob/v1.3.10/src/postorius/doc/news.… https://gitlab.com/mailman/mailman-web/-/blob/0.0.8/README.rst -- Jeremy Stanley

1 0

Upgrading review.opendev.org to Gerrit 3.8 on November 17, 2023
by Clark Boylan 30 Oct '23

30 Oct '23

On November 17, 2023 beginning at 15:30 UTC the OpenDev team will upgrade Gerrit at https://review.opendev.org from Gerrit 3.7 to 3.8. This upgrade shouldn't take more than an hour. We have managed to to keep our Gerrit installation about one major release behind upstream's release cadence, and Gerrit 3.9's impending release means it is time for us to upgrade to 3.8. There are a number of new features, bug fixes, and performance improvements in the new version. The Gerrit project publishes detailed release information [0] which you can review if you are interested in what sorts of changes to expect. If you are interested in the upgrade process you can follow that in our planning document [1]. It is worth noting that if all goes well we expect the total Gerrit downtime to be much shorter than an hour (should only take a few minutes). If we need to revert to Gerrit 3.7, we will need to do offline reindexing of our changes which takes about half an hour. We are using an hour long upgrade window to ensure we have time for downgrades should that become necessary. [0] https://www.gerritcodereview.com/3.8.html [1] https://etherpad.opendev.org/p/gerrit-upgrade-3.8 Clark

1 0

Zuul regex deprecation [action required]
by James E. Blair 21 Sep '23

21 Sep '23

Hi, Zuul is making a change that may require action from developers on projects hosted in OpenDev. Here is the release note regarding the change: > Regular expressions using Python syntax are deprecated in favor of RE2 > syntax instead, for additional speed and safety. Negative lookahead > assertions may be replaced using the negate keyword. See Regular > Expressions[1] for more information. > > If Zuul detects a regular expression using Python syntax that is not > supported by RE2, it will register a configuration syntax > warning. These may be viewed on the configuration errors page in the > web interface. > > A future version of Zuul will remove Python regex support completely > and these warnings will become errors. [1] https://zuul-ci.org/docs/zuul/latest/project-config.html#regex It's easy to see if your project on OpenDev is affected. Each tenant has a page where the current configuration errors and warnings are displayed. Visit any page in Zuul for your tenant, and if there is a bell icon in the top right, click on that. For example, the configuration error page for the OpenStack tenant is here: https://zuul.opendev.org/t/openstack/config-errors On that page, look for the "Regex Deprecation" warnings. You can expand the warning to see exactly the file and line number where the warning is found. Almost all of the issues identified so far have been due to the fact that RE2 does not support negative lookahead assertions. In the past, we used these a lot to say things like "run this job on any branch except master" with regexes like "(?!master)". Because this is such a common pattern, we added a feature in Zuul to make this easy. A configuration like: branches: "^(?!master).*$" can now be written as: branches: regex: "^master$" negate: true This simply negates the specified regex. It's not an exact translation of the original regex, but is slightly improved and to the point: anything but exactly "master". Please take a moment and check to see if your project has instances of this warning, and go ahead and fix it. Even if there are a lot of instances, they are likely to be very similar and correcting them may take only a few minutes. Here are two changes where we update the central configuration that applies to all projects: https://review.opendev.org/c/openstack/project-config/+/893702 https://review.opendev.org/c/openstack/openstack-zuul-jobs/+/893792 These provide examples of how to make changes for several common cases; you may be able to simply copy what was done in those changes. If you have any trouble adapting existing regexes to the new format, please contact us in #opendev to discuss the issue. We may be able to find a simple solution, or if there is another special case that is difficult to handle, we may be able to add support to Zuul to mitigate the issue. If you use "update-regexes" as a topic name, it will help people keep track of progress and possible issues. The Zuul project has not yet set a date for when support for the old syntax will be removed. I expect it to be on the order of months, which should give folks plenty of time to make the necessary changes. But please do so early so that we have time to deal with any issues. Thanks, Jim (on behalf of the OpenDev team)

1 0

Removing OpenDev's Fedora Test Images on September 11, 2023
by Clark Boylan 06 Sep '23

06 Sep '23

OpenDev has been unable to update Fedora images in a timely manner leaving us with Fedora 35 and 36 images in our CI system. Fedora 35 and 36 are long past their EOL date, and we have been planning to remove them [0]. Somewhat recently the Fedora project stopped mirroring packages for these releases which resulted in empty mirrors on our end [1]. The end result is that Fedora nodes haven't been very functional within OpenDev since. We have slowly been cleaning up usage of Fedora nodes and recently removed the fedora-latest nodeset from Zuul [2]. The next step is to remove these images from Nodepool entirely. We will do so on Monday September 11, 2023. Chances are any Fedora jobs are already broken, but this is a good reminder to look into correcting any of those jobs by moving them to another platform. [0] https://lists.opendev.org/archives/list/service-discuss@lists.opendev.org/t… [1] http://mirror.dfw.rax.opendev.org/fedora/releases/36/ [2] https://review.opendev.org/c/opendev/base-jobs/+/892380 Clark

1 0

Updating OpenDev Zuul's default Ansible version to Ansible 8
by Clark Boylan 23 Aug '23

23 Aug '23

Currently OpenDev Zuul's default Ansible version is Ansible 6. Zuul has recently added support for Ansible 8, and is dogfooding Ansible 8 in the Zuul tenant for the Zuul project. Yesterday, the OpenDev team updated the Zuul tenant for the OpenDev project to default to Ansible 8 as well. So far we have seen no problems with jobs run in these two tenants related to the Ansible version change. We would like to update the default Ansible version for all of the Zuul tenants in OpenDev's Zuul installation to Ansible 8 in the near future. The reason for this is Zuul will update the default Ansible version to Ansible 8 in Zuul itself. Not long after that change, support for Ansible 6 in Zuul will be removed. Changing things in OpenDev first allows us to do these changes in a controlled manner and get ahead of any potential problems. Assuming the Zuul and OpenDev tenants continue to run without trouble our plan is to switch the nebulous, pyca, pypa, and vexxhost tenants to Ansible 8 by default on August 28, 2023. Then if things continue to run without trouble, we will complete this change by updating the openstack tenant on September 4, 2023. I had initially thought that we would do a more conservative rollout, but initial data indicates this change may be straightforward so we'd prefer a quicker move. Note that if there are major issues we can revert the setting in our Ansible config for any of these tenants and return to a default to Ansible 6 while the issues get addressed. Issues will need to be addressed as Ansible 6 is EOL and Zuul intends to drop support for this version of Ansible. If you would like to test your jobs before the tenant configuration updates go into effect you can do so by setting `ansible-version: '8'` in the configuration of a job [0], push the resulting change to Gerrit, and then wait for Zuul to run the job and provide you with results. It is not necessary to merge the change; Zuul will speculatively test this setting. If you discover any problems through this process please let us know. [0] https://zuul-ci.org/docs/zuul/latest/config/job.html#attr-job.ansible-versi… Clark

1 0

opendevorg docker hub images moving to quay.io
by Clark Boylan 24 May '23

24 May '23

The OpenDev team has decided to move hosting for its container images from docker hub to quay.io. Over the weekend we landed changes to update the publication location for our python base images (opendevorg/python-builder, opendevorg/python-base, opendevorg/uwsgi-base). We will continue to move additional images as quickly as possible. While we publish these images primarily for our own consumption, they are entirely open source and others may be using them as well. If you are using these images, you should update the image source locations to quay.io/opendevorg/$imagename. Once we have updated publishing for our last image, we will begin a 30 day countdown, after which we will clean up images on docker hub to remove any confusion over which images are maintained and up to date. We will send notice for a more specific time frame once it is known. Let us know if you have an questions. Clark

1 1

Etherpad outage April 19, 2023 at 22:00 UTC
by Clark Boylan 17 Apr '23

17 Apr '23

The OpenDev team will be taking etherpad services at https://etherpad.opendev.org offline for approximately 90 minutes beginning at 22:00 UTC on Wednesday April 19, 2023. This is necessary for us to replace the server hosting etherpad and perform necessary data migrations. If you have any questions or concerns please reach out to us and let us know. Clark

1 0

review.opendev.org Downtime for Gerrit Upgrade and Project Renames April 6, 2023
by Clark Boylan 15 Mar '23

15 Mar '23

Hello, The OpenDev team intends to have a Gerrit outage of approximately two hours on April 6, 2023 beginning at 22:00 UTC. The purpose of this outage is to upgrade Gerrit from version 3.6 to 3.7. We will also take advantage of the downtime to perform project renames. For more information on the new version of Gerrit you can refer to the upstream release notes [0]. If you would like to rename a project please get it onto our TODO list on the wiki [1] and push changes according to the documented process [2]. We've chosen this time and date because we expect it to be a quiet period, and it occurs after known releases and events like the PTG. We are happy for you to raise and concerns, questions, comments or feedback with this plan; the earlier the better. [0] https://www.gerritcodereview.com/3.7.html [1] https://wiki.openstack.org/wiki/Meetings/InfraTeamMeeting#Upcoming_Project_… [2] https://docs.opendev.org/opendev/infra-manual/latest/creators.html#project-…

1 0

Intent to grant control of x/virtualpdu to OpenStack community
by Jeremy Stanley 01 Mar '23

01 Mar '23

The OpenStack Ironic project relies on VirtualPDU, which is no longer actively developed. Ironic contributors reached out to the VirtualPDU maintainers with an offer to officially assume maintenance responsibilities in order to avoid forking it, and received a response from one (Mathieu Mitchell) who indicated support for that plan. Unfortunately, communication died off shortly thereafter, and the Ironic team has been unable to raise any of the current maintainers to actually add their access to the x/virtualpdu project in OpenDev's Gerrit. We don't have a documented process since this is the first time it's really come up, but I'm officially announcing that I intend to use my administrative permissions as an OpenDev sysadmin to add membership of an OpenStack Ironic team representative to the following Gerrit groups if no objections are raised before Wednesday, March 8: * virtualpdu-core * virtualpdu-release This will effectively grant full control of the x/virtualpdu repository to OpenStack Ironic contributors. Please follow up to the service-discuss(a)lists.opendev.org or openstack-discuss(a)lists.openstack.org mailing list with any concerns as soon as possible, or you can feel free to reach out to me directly by email or in IRC (fungi in the #opendev channel on the OFTC network). -- Jeremy Stanley

1 0

December 2022 OpenDev Activity Update
by Clark Boylan 14 Dec '22

14 Dec '22

I had meant to send one of these every couple of months, but it has been about six months since I sent the last update email. Apologies for the delay. It has been a busy six months; let's dive in. We bootstrapped the ability to deploy new control plane nodes on Ubuntu Jammy. All newly created servers are built on Jammy unless we have a very good reason to use something older. Additionally, we have updated our base Python Docker images to include support for Python 3.11. Python 3.11 is only a few weeks old, but we are able to deploy software on top of it taking advantage of the performance benefits it provides. Gerrit has been upgraded to 3.6.3. This release is just behind 3.7.0 which was released about a month ago. I believe this is the closest we've been to the latest Gerrit release in about a decade. We do plan to upgrade to 3.7.x, but this upgrade appears to be a bit more involved than the last few. In particular, the upgrade itself needs offline re-indexing, we need to port our label configs to the new submit requirements system, and the web UI is now based on Lit instead of polymer. The Gitea cluster is now running 1.17. This update didn't bring any major user facing changes. The next update to 1.18.x should correct a problem with Gitea misidentifying certain files as being "vendored". Prior to the October PTG event our Meetpad deployment was updated to use the latest stable releases of Jitsi Meet, and we applied a modern configuration to our installation. One major feature this brought is a landing page for meetings where users can configure their name and settings. Importantly, this landing page should prevent browsers' auto mute behavior for auto playing video+audio from breaking calls for our users. We believe this was a major source of users not being able to hear others in calls. Mailing lists for lists.opendev.org and lists.zuul-ci.org have been migrated to a new Mailman 3 server. We are using these two list domains to work out issues while we prepare for migrating the rest of our mailing lists to the new server. This should give us a much more friendly web interface for browsing archives with built in search capability as well as easier to use moderation tools for list moderators. Our Zuul deployment has seen a number of improvements. The ZooKeeper cluster backing Zuul has been upgraded to ZooKeeper 3.7 which brings performance improvements. Zuul supports Ansible 6 now, and all of our tenants are running jobs with this version of Ansible. This version of Ansible fixes pipelining which should provide some improvements to job runtime. Finally, we are upgrading Zuul weekly using automated zero downtime rolling restarts. This ensures we're getting the latest and greatest Zuul features and can provide quick and early feedback to Zuul. Looking ahead to 2023, I expect to see a lot more of what we've done over the last six months. Gerrit will be upgraded to 3.7, Gitea will be upgraded to 1.18, more mailing lists will be migrated to Mailman 3, and more services will be deployed on Jammy running with Python 3.11. See you next year! Clark

1 0