openstack
/
senlin
Code Issues Proposed changes

Merge "Add release notes for Stein"

This commit is contained in:
Zuul 2019-02-26 18:56:32 +00:00 committed by Gerrit Code Review
parent 5a819ccf16 070ad9d7a0
commit e4fbf8d86f
11 changed files with 78 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
releasenotes/notes/action-purge-11db5d8018b8389a.yaml
View File

@ -1,4 +1,4 @@
---
features:
- A action_purge subcommand is added to senlin-manage tool for purging actions
- A ``action_purge`` subcommand is added to ``senlin-manage`` tool for purging actions
from the actions table.

7
releasenotes/notes/action-update-api-fc51b1582c0b5902.yaml Normal file
View File

@ -0,0 +1,7 @@
---
features:
- |
[`blueprint action-update <https://blueprints.launchpad.net/senlin/+spec/action-update>`_]
A new action update API is added to allow the action status to be updated.
The only valid status value for update is CANCELLED.

6
releasenotes/notes/bug-1789488-75ee756a53722cd1.yaml Normal file
View File

@ -0,0 +1,6 @@
---
fixes:
- |
[`bug 1789488 <https://bugs.launchpad.net/senlin/+bug/1789488>`_]
Perform deep validation of profile and policy schemas so that errors in
spec properties are detected.

6
releasenotes/notes/bug-1811161-c6416ad27ab0a2ce.yaml Normal file
View File

@ -0,0 +1,6 @@
---
fixes:
- |
[`bug 1811161 <https://bugs.launchpad.net/senlin/+bug/1811161>`_]
Perform policy post-op even if action failed. This allows the health policy
to reenable health checks even if an action that failed.

6
releasenotes/notes/bug-1811294-262d4b9cced3f505.yaml Normal file
View File

@ -0,0 +1,6 @@
---
fixes:
- |
[`bug 1811294 <https://bugs.launchpad.net/senlin/+bug/1811294>`_]
Set owner field for actions created to wait for lifecycle completion. This
allows these actions to be cleaned up when the engine is restarted.

7
releasenotes/notes/bug-1813089-db57e7bdfd3983ac.yaml Normal file
View File

@ -0,0 +1,7 @@
---
fixes:
- |
[`bug 1813089 <https://bugs.launchpad.net/senlin/+bug/1813089>`_]
This change picks the address when adding a node to a load balancer based on
the subnet ip version. This fix adds supports for nodes with
dual stack network.

6
releasenotes/notes/bug-1815540-2664a975db5fafc8.yaml Normal file
View File

@ -0,0 +1,6 @@
---
features:
- |
[`bug 1815540 <https://bugs.launchpad.net/senlin/+bug/1815540>`_]
Cluster recovery and node recovery API request bodies are changed to only accept a
single operation. Optional parameters for this operation are set in operation_params.

5
releasenotes/notes/bug-1817379-23dd2c925259d5f2.yaml Normal file
View File

@ -0,0 +1,5 @@
---
fixes:
- |
[`bug 1817379 <https://bugs.launchpad.net/senlin/+bug/1817379>`_]
Delete ports before recovering a node.

3
releasenotes/notes/cluster-scale-action-conflict-0e1e64591e943e25.yaml
View File

@ -9,6 +9,7 @@ prelude: >
scaling action cannot be processed due to cooldown.
features:
- |
[`blueprint scaling-action-acceptance <https://blueprints.launchpad.net/senlin/+spec/scaling-action-acceptance>`_]
Scaling actions (IN or OUT) now validate that there is no conflicting
action already being processed and will return an error via the API
informing the end user if a conflict is detected. A conflicting action is
@ -16,6 +17,6 @@ features:
`CLUSTER_SCALE_OUT` is attempted while there is already cluster scaling
action in the action table in a pending status (READY, RUNNING, WAITING,
ACTION_WAITING_LIFECYCLE_COMPLETION).
Additinally the cooldown will be checked and enforced when a scaling
Additionally the cooldown will be checked and enforced when a scaling
action is requested. If the cooldown is being observed the requester will
be informed of this when submitting the action via an error.

15
releasenotes/notes/fail-fast-on-locked-resource-eee28572dc40009a.yaml Normal file
View File

@ -0,0 +1,15 @@
---
prelude: >
This release alters the behavior of cluster and node APIs which create, update or
delete either resource. In the previous release those API calls would be
accepted even if the target resource was already locked by another action.
The old implementation would wait until the other action released the lock
and then continue to execute the desired action. With the new implementation
any API calls for cluster or node that modify said resource will be rejected
with 409 conflict.
features:
- |
[`blueprint fail-fast-locked-resource <https://blueprints.launchpad.net/senlin/+spec/fail-fast-locked-resource>`_]
POST, PATCH or DELETE API calls for clusters or nodes that require a lock are
rejected with 409 resource conflict if another action is already holding a
lock on the target resource.

17
releasenotes/notes/health-policy-mutiple-detection-types-10bfdc80771278cb.yaml Normal file
View File

@ -0,0 +1,17 @@
---
prelude: >
Health policy v1.1 implements multiple detection modes. This implementation
is incompatible with health policy v1.0.
features:
- |
[`blueprint multiple-detection-modes <https://blueprints.launchpad.net/senlin/+spec/multiple-detection-modes>`_]
Health policy v1.1 now supports multiple detection types. The user can
combine node status poll and node poll url types in the health policy in
order to have both checked before a node is considered unhealthy.
upgrade:
- |
This release makes changes to the health policy properties that are
incompatible with health policy v1.0. Any existing policies of type
health policy v1.0 must be removed before upgrading to this release.
After upgrading, the health policies conforming to v1.0 must be recreated
following health policy v1.1 format.