2024.1 Series Release Notes


New Features

  • Added support for manage volume operation.

  • Added support to manipulate resource locks from the shared file system service.

  • Added support to restrict the visibility and deletion of the shared file system share access rules.

  • Added support for volume snapshot manage and volume snapshot unmanage.

  • Methods openstack.block_storage.v3.volume.Volume.init_attachment and block_storage.init_volume_attachment now return the results of the POST request instead of None. This replicates the behaviour of cinderclient; the returned data is used by nova and ironic for managing volume attachments.


New Features

  • The stack_events method and StackEvent Class have been added to retrieve stack events

  • Adds suspend_stack and resume_stack to support stack non-lifecycle operations.

  • Added support for volume transfer create, find, delete, get, list and accept.


New Features

  • Added support for the MetadefProperty Image resource.

  • Add support for the new VMove resource for the instance HA service (Masakari).

  • Add hardware_offload_type attribute to port resource. Users can set this attribute to a valid value defined in neutron_lib.constants.VALID_HWOL_TYPES, set “None” or leave it undefined.

  • Add export_stack to print stack infomation in a json format

  • Added support for:

    • Create Attachment

    • Update Attachment

    • List Attachment

    • Get Attachment

    • Delete Attachment

    • Complete Attachment

  • Added support for specifying the subnetpool to use when creating subnets (subnetpool_name_or_id)

Upgrade Notes

  • The cloud-layer caching functionality has been removed in favour of the proxy-layer caching functionality first introduced in openstacksdk 1.0.0. This migration to proxy-layer caching was designed to be transparent to end-users and there should be no user-facing impact from this removal.

  • Many cloud administrators use universal cloud-wide credentials. This is supported in keystone via ‘inherited’ roles that can be applied cloud- or domain-wide.

    In previous releases, these credentials could not be usefully defined within `clouds.yaml` because `clouds.yaml` supports only specifying a single domain and project for auth purposes. This project or domain could not be overridden on the commandline.

Bug Fixes

  • [bug 2010898] Fix Swift endpoint url handling to determine info/caps url

  • When some config settings are specified multiple times, the order of precendence has been changed to prefer command-line or env settings over those found in `clouds.yaml`. The same reordering has been done when a setting is specified multiple times within `clouds.yaml`; now a higher-level setting will take precedence over that specified within the auth section.

    Affected settings are:

    • domain_id

    • domain_name

    • user_domain_id

    • user_domain_name

    • project_domain_id

    • project_domain_name

    • auth-token

    • project_id

    • tenant_id

    • project_name

    • tenant_name