From 03ee019544492f3fde8f277df6ccbccd18ec7b5f Mon Sep 17 00:00:00 2001 From: Masahito Muroi Date: Wed, 8 Aug 2018 21:13:51 +0900 Subject: [PATCH] Add some release notes for Rocky release Change-Id: Iea71e6892923cbcc56c0e722217f38a5fc944747 --- .../notes/bug-1786031-800a33c681fafdc0.yaml | 8 ++++++++ .../notes/devstack-dashboard-1b96128952e64c1f.yaml | 5 +++++ .../notes/periodic-healing-143ed251d990580b.yaml | 14 ++++++++++++++ ...ate-used-extra-capability-6d7bc7fa23c91295.yaml | 7 +++++++ 4 files changed, 34 insertions(+) create mode 100644 releasenotes/notes/bug-1786031-800a33c681fafdc0.yaml create mode 100644 releasenotes/notes/devstack-dashboard-1b96128952e64c1f.yaml create mode 100644 releasenotes/notes/periodic-healing-143ed251d990580b.yaml create mode 100644 releasenotes/notes/update-used-extra-capability-6d7bc7fa23c91295.yaml diff --git a/releasenotes/notes/bug-1786031-800a33c681fafdc0.yaml b/releasenotes/notes/bug-1786031-800a33c681fafdc0.yaml new file mode 100644 index 00000000..19fa747d --- /dev/null +++ b/releasenotes/notes/bug-1786031-800a33c681fafdc0.yaml @@ -0,0 +1,8 @@ +--- +issues: + - | + When the update lease API returns any error regardless of the reason, the + lease status goes into ERROR. If the reason is wrong input, e.g. invalid + format or not enough hosts available, updating the lease again with correct + information will fix the ERROR status. For more details, see `bug 1786031 + `_. diff --git a/releasenotes/notes/devstack-dashboard-1b96128952e64c1f.yaml b/releasenotes/notes/devstack-dashboard-1b96128952e64c1f.yaml new file mode 100644 index 00000000..a45bf388 --- /dev/null +++ b/releasenotes/notes/devstack-dashboard-1b96128952e64c1f.yaml @@ -0,0 +1,5 @@ +--- +other: + - | + The DevStack plugin now supports installing blazar-dashboard when both + blazar and horizon services are enabled in ``local.conf``. diff --git a/releasenotes/notes/periodic-healing-143ed251d990580b.yaml b/releasenotes/notes/periodic-healing-143ed251d990580b.yaml new file mode 100644 index 00000000..de4a8496 --- /dev/null +++ b/releasenotes/notes/periodic-healing-143ed251d990580b.yaml @@ -0,0 +1,14 @@ +--- +features: + - | + Resource monitoring supports periodic healing from the Rocky release. It + only heals reservations starting within a configurable time window in order + to avoid unnecessary reservation healing, e.g. when resources become + available again at a later date. The interval is defined with the + ``[physical:host]/healing_interval`` configuration option. The default + value is 60 minutes. For more details, please see the `Resource + Monitoring`_ section in the Blazar documentation. The previous mode of + operation, which heals all reservations regardless of their start date, can + be used by setting ``[physical:host]/healing_interval`` to ``0``. + + .. _`Resource Monitoring`: https://docs.openstack.org/blazar/latest/user/resource-monitoring.html diff --git a/releasenotes/notes/update-used-extra-capability-6d7bc7fa23c91295.yaml b/releasenotes/notes/update-used-extra-capability-6d7bc7fa23c91295.yaml new file mode 100644 index 00000000..783a9ea3 --- /dev/null +++ b/releasenotes/notes/update-used-extra-capability-6d7bc7fa23c91295.yaml @@ -0,0 +1,7 @@ +--- +features: + - | + The update host API denies update requests trying to change extra + capabilities in use by any pending or active reservation. This avoids + mismatches between updated extra capabilities and resource_properties + specified before the update host request.