2023.1 Series Release Notes

8.0.0

Deprecation Notes

  • The CPUFilter, RamFilter and DiskFilter are now deprecated. They will be removed in a future release and should no longer be used. Their functionality has been replaced with a placement native approach.

7.0.0

Upgrade Notes

  • The default value of [oslo_policy] policy_file config option has been changed from policy.json to policy.yaml. Operators who are utilizing customized or previously generated static policy JSON files (which are not needed by default), should generate new policy files or convert them in YAML format. Use the oslopolicy-convert-json-to-yaml tool to convert a JSON to YAML formatted policy file in backward compatible way.

Deprecation Notes

  • Use of JSON policy files was deprecated by the oslo.policy library during the Victoria development cycle. As a result, this deprecation is being noted in the Wallaby cycle with an anticipated future removal of support by oslo.policy. As such operators will need to convert to YAML policy files. Please see the upgrade notes for details on migration of any custom policy files.

6.0.0

Prelude

Introduce a CNI plugin for docker. The new CNI plugin will eventually replace kuryr-libnetwork (which is the current network plugin Zun is currently using for docker).

New Features

  • Introduce a CNI plugin for docker. In before, Zun was using libnetwork as the networking model for docker containers. Starting from this release, Zun introduces an alternative CNI plugin which implements the CNI networking model for docker containers. The new CNI plugin will become the default network plugin and the old libnetwork plugin will be deprecated.

Upgrade Notes

  • Deployers who are choosing CNI plugin don’t need to deploy kuryr-libnetwork and etcd.

5.0.0

Prelude

Starting from this release, Zun adds support for CRI-compatible runtime. Zun uses CRI runtime to realize the concept of capsule (pod). As a result, users can use Zun API to create pods in Kata container via a CRI runtime.

New Features

  • Introduce a CNI plugin for Zun. The plugin is a binary called zun-cni. This binary is an executable that sends CNI commands to a daemon process zun-cni-daemon which provides the actual implementation for CNI.

  • Introduce a CRI driver that is responsible for interfacing with CRI runtime to manage the pods.

  • Add support for requesting specific host to run a container. By default, host can be specified by administrators only.

  • Add support for specifying entrypoint with the container which is used to overwrite the entrypoint of the docker image.

Upgrade Notes

  • Starting from this release, container driver is loaded from entry point. Deployers should specify the entry point (i.e. docker) in config option container_driver under [DEFAULT] session.

  • Python 2.7 support has been dropped. Last release of Zun to support py2.7 is OpenStack Train. The minimum version of Python now supported by Zun is Python 3.6.

Deprecation Notes

  • Specifying container driver class via config option container_driver is deprecated. Use driver name in entry point zun.container.driver instead.

4.0.0

Prelude

This release supports placement integration.

New Features

  • In this release, Zun compute agent will report local resource availability/utilization to placement API. In addition, Zun scheduler will get allocation candidates from placement API and claim container allocation in placement.

Upgrade Notes

  • Since this release, operators need to configure each compute node that runs both Zun compute agent and Nova compute agent as follows:

    [compute]
host_shared_with_nova = true

    By setting host_shared_with_nova to true, Zun compute agent and Nova compute agent will share a resource provider for the compute node in placement. In particular, both Nova instances and Zun containers might claim allocation on the same resource provider. By default, host_shared_with_nova is false which means Zun compute agent will create its own resource provider for the compute node.

3.0.0.0rc1

Prelude

Added new tool zun-status upgrade check.

New Features

  • New framework for zun-status upgrade check command is added. This framework allows adding various checks which can be run before a Zun upgrade to ensure if the upgrade can be performed safely.

Upgrade Notes

  • Operator can now use new CLI tool zun-status upgrade check to check if Zun deployment can be safely upgraded from N-1 to N release.

2.0.0

New Features

  • Migrate all upstream gates to Zuulv3 native format.