be547a9cf8
This patch fixes the os-reset_status api call notifications for volumes, snapshots and backups and deprecates the existing notifications scheme for os-reset_status. Existing notifications for volumes are going to a publisher_id of 'volumeStatusUpdate'. Notifications for snapshots were going to 'volumeStatusUpdate'. Notifications for backups were going to 'backupStatusUpdate'. This patch changes notifications for volumes to go to the 'volume' publisher_id as all other volume actions in cinder. This patch changes notifications for snapshots to go to the 'snapshot' publisher_id as all other snapshot actions in cinder. This patch changes notifications for backups to go to the 'backup' publisher_id as all other backups actions in cinder. Change-Id: I2550b00127ee2533b0ab12c4efb4927dbcaaa190 Closes-Bug: 1863806
27 lines
1.1 KiB
YAML
27 lines
1.1 KiB
YAML
---
|
|
deprecations:
|
|
- |
|
|
In this release, sending ``os-reset_status`` notifications to the
|
|
following *nonstandard* publisher_ids is DEPRECATED:
|
|
|
|
* 'volumeStatusUpdate' for volume status resets
|
|
* 'volumeStatusUpdate' for snapshot status resets
|
|
* 'backupStatusUpdate' for backup status resets
|
|
|
|
The notifications continue to be published to the above during the
|
|
deprecation period. Beginning with this release, the ``os-reset_status``
|
|
notifications are also sent to the following *standard* publisher_ids:
|
|
|
|
* 'volume' for volume status resets
|
|
* 'snapshot' for snapshot status resets
|
|
* 'backup' for backup status resets
|
|
|
|
This will allow consumers of these notifications to make a smooth
|
|
transition. In the Victoria release, ``os-reset_status`` notifications
|
|
will *only* be sent to the standard publisher_ids.
|
|
fixes:
|
|
- |
|
|
``os-reset_status`` notifications for volumes, snapshots and backups will
|
|
now go to the standard publisher id for volume, snapshot and backup like
|
|
all other notifications for volume, snapshot and backup.
|