summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/fix-virtual-device-role-tagging-7cfdb14f2ba4fbcf.yaml10
-rw-r--r--releasenotes/notes/notification-transformation-ocata-ec42281e9df6019c.yaml23
-rw-r--r--releasenotes/notes/scheduler-can-discover-hosts-4b799cbd14dbc7dc.yaml13
3 files changed, 46 insertions, 0 deletions
diff --git a/releasenotes/notes/fix-virtual-device-role-tagging-7cfdb14f2ba4fbcf.yaml b/releasenotes/notes/fix-virtual-device-role-tagging-7cfdb14f2ba4fbcf.yaml
new file mode 100644
index 0000000000..7448664bae
--- /dev/null
+++ b/releasenotes/notes/fix-virtual-device-role-tagging-7cfdb14f2ba4fbcf.yaml
@@ -0,0 +1,10 @@
+fixes:
+ - |
+ In the context of virtual device role tagging at server create time, the
+ 2.42 microversion restores the tag attribute to networks and
+ block_device_mapping_v2. A bug has caused the tag attribute to no longer be
+ accepted starting with version 2.33 for block_device_mapping_v2 and
+ starting with version 2.37 for networks. In other words, block devices
+ could only be tagged in version 2.32 and network interfaces between
+ versions 2.32 and 2.36 inclusively. Starting with 2.42, both network
+ interfaces and block devices can be tagged again.
diff --git a/releasenotes/notes/notification-transformation-ocata-ec42281e9df6019c.yaml b/releasenotes/notes/notification-transformation-ocata-ec42281e9df6019c.yaml
new file mode 100644
index 0000000000..8ef14f0f7e
--- /dev/null
+++ b/releasenotes/notes/notification-transformation-ocata-ec42281e9df6019c.yaml
@@ -0,0 +1,23 @@
+---
+features:
+ - |
+
+ The following legacy notifications have been transformed to
+ a new versioned payload:
+
+ * aggregate.create
+ * aggregate.delete
+ * instance.create
+ * instance.finish_resize
+ * instance.power_off
+ * instance.resume
+ * instance.shelve_offload
+ * instance.shutdown
+ * instance.snapshot
+ * instance.unpause
+ * instance.unshelve
+
+ Every versioned notification has a sample file stored under
+ doc/notification_samples directory. Consult
+ http://docs.openstack.org/developer/nova/notifications.html for more information.
+
diff --git a/releasenotes/notes/scheduler-can-discover-hosts-4b799cbd14dbc7dc.yaml b/releasenotes/notes/scheduler-can-discover-hosts-4b799cbd14dbc7dc.yaml
new file mode 100644
index 0000000000..e153b7ac6e
--- /dev/null
+++ b/releasenotes/notes/scheduler-can-discover-hosts-4b799cbd14dbc7dc.yaml
@@ -0,0 +1,13 @@
+---
+features:
+ - As new hosts are added to Nova, the `nova-manage cell_v2
+ discover_hosts` command must be run in order to map them into
+ their cell. For deployments with proper automation, this is a
+ trivial extra step in that process. However, for smaller or
+ non-automated deployments, there is a new configuration variable
+ for the scheduler process which will perform this discovery
+ periodically. By setting
+ `scheduler.discover_hosts_in_cells_interval` to a positive value,
+ the scheduler will handle this for you. Note that this process
+ involves listing all hosts in all cells, and is likely to be too
+ heavyweight for large deployments to run all the time.