September 2021 - Zuul-announce

Nodepol 4.3.0 released
by James E. Blair 09 Sep '21

09 Sep '21

The Zuul team is pleased to announce the release of Nodepool 4.3.0. Download it from PyPI: https://pypi.org/project/nodepool Find container images at: https://hub.docker.com/u/zuul The release notes, included below, are also available in the documentation with hyperlink references: https://zuul-ci.org/docs/nodepool/4.3.0/releasenotes.html New Features ============ * Added the option to set quota on resources on a per-tenant basis (i.e. Zuul tenants). A new top-level config structure tenant-resource-limits has been added under which one can specify a number of tenants, each with max-servers, max-cores, and max-ram limits. These limits are valid globally, i.e., for all providers. This differs from currently existing provider and pool quotas, which only are considered for nodes of the same provider. This feature is optional and tenant quotas are ignored for any NodeRequests that do not deliver tenant information with them. Also no quota is evaluated for tenants that have no limits configured for them.

1 0

Zuul 4.9.0 released
by James E. Blair 09 Sep '21

09 Sep '21

The Zuul team is pleased to announce the release of Zuul 4.9.0. Download it from PyPI: https://pypi.org/project/zuul Find container images at: https://hub.docker.com/u/zuul The release notes, included below, are also available in the documentation with hyperlink references: https://zuul-ci.org/docs/zuul/4.9.0/reference/releasenotes.html New Features ============ * The zuul delete-state command may be used to delete all of the ephemeral state stored by Zuul in ZooKeeper. Normally Zuul is able to detect and correct errors on its own, but in case it is unable to, this may prove a useful utility for manual recovery. * The new commands zuul copy-keys and zuul delete-keys may be useful when renaming projects in order to move the keys from the old to the new project names without service interruption. * Add new statsd gauge metrics of current open node requests exported as zuul.nodepool.tenant.<tenant>.current_requests. This metric tracks the currently open node requests per tenant. It drills down the overall zuul.nodepool.current_requests metric. Upgrade Notes ============= * Zuul no longer reads or writes project private key files from the scheduler’s filesystem. In order to load existing keys into ZooKeeper, run version 4.6.0 of the scheduler at least once, if you haven’t already. * A new command zuul export-keys has been added to export the encrypted keys from ZooKeeper onto the filesystem for backup. Likewise, zuul import-keys will load a previously-exported backup into ZooKeeper. It is recommended that you use these commands in system backup scripts.

1 0

zuul-jobs: potentially breaking change to tox base job
by Sorin Sbarnea 08 Sep '21

08 Sep '21

There is a change at https://review.opendev.org/c/zuul/zuul-jobs/+/807702 which is changing the default tox arguments to add "--skip-missing-interpreters false". This overrides the value from tox.ini file and disallow tox from using another python version than the requested one. The goal of this change is to prevent accidents where some project endup running tox in CI and believe that these jobs are testing one version of python but in fact another version is used instead. We think that this has the potential to affect only users of jobs with `parent: tox`. Users that are using `tox-py3*` zuul-jobs are not affected because we force tox to run using that specific python version. We will wait 2 weeks before merging this change, so people would have time to adapt their configurations. Potentially affected projects from opendev: https://codesearch.opendev.org/?q=skip_missing_interpreters%20%3D%20%5BtT%5… If you find your project on the list above it would be wise to just apply the tox.ini changes mentioned below before we merge that change If you are affected you have two options: - update your tox.ini file and use generic "py" environment on envlist and remove the skip_missing_interpreters entry. - override tox_extra_args in your tox job in order to keep using the old behavior Cheers Sorin Sbarnea

1 0