Merge "Add some release notes for Rocky release"
This commit is contained in:
commit
ca6adcbc3a
|
@ -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
|
||||
<https://bugs.launchpad.net/blazar/+bug/1786031>`_.
|
|
@ -0,0 +1,5 @@
|
|||
---
|
||||
other:
|
||||
- |
|
||||
The DevStack plugin now supports installing blazar-dashboard when both
|
||||
blazar and horizon services are enabled in ``local.conf``.
|
|
@ -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
|
|
@ -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.
|
Loading…
Reference in New Issue