Pike-1 release notes
This adds release notes for Pike-1 release. Change-Id: Ie8a4820c743e62046f767e87c81ff79cb9882b79
This commit is contained in:
parent
6bd3016ed0
commit
0b25901aac
@ -0,0 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
When a cluster or a node is deleted, the action records associated with
|
||||
them are now automatically deleted from database.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
A new configuration option check_interval_max is added (default=3600) for
|
||||
cluster health check intervals.
|
@ -0,0 +1,4 @@
|
||||
---
|
||||
other:
|
||||
- |
|
||||
DB layer operations now feature some retries if there are transient errors.
|
4
releasenotes/notes/doc-fixes-e60bb1a486f67e0c.yaml
Normal file
4
releasenotes/notes/doc-fixes-e60bb1a486f67e0c.yaml
Normal file
@ -0,0 +1,4 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Various bug fixes to the user manual and sample profiles/policies.
|
@ -0,0 +1,4 @@
|
||||
---
|
||||
deprecations:
|
||||
- |
|
||||
The support to py3.4 is dropped. Please use py3.5 instead.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
When an action was marked as RETRY, its status is reset to READY for a
|
||||
reschedule. A bug related to this behavior is now fixed.
|
4
releasenotes/notes/fix-cooldown-5082711989ecd536.yaml
Normal file
4
releasenotes/notes/fix-cooldown-5082711989ecd536.yaml
Normal file
@ -0,0 +1,4 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed immature return from policy cooldown check.
|
@ -0,0 +1,6 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed a bug related to desired_capacity when creating a cluster. The old
|
||||
behavior was having it default to 1, however, the correct behavior should
|
||||
be having it default to min_size if provided.
|
@ -0,0 +1,4 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed a problem related to duplicated event dumps during action execution.
|
@ -0,0 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
When a node cannot be added to a load-balancer although desired, or it can
|
||||
not be removed from a load-balancer when requested, the node will be
|
||||
marked as in WARNING status.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed error in the return value of node-check which prevents node-recover
|
||||
from being triggered.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed a problem when claiming a cluster from health registry if service
|
||||
engine is stopped (killed) and restarted quickly.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed an error in updating stack tags when the stack joins or leaves a
|
||||
cluster.
|
@ -0,0 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
When an engine is detected to be dead, the actions (and the clusters/nodes
|
||||
locked by those actions) are now unlocked. Such clusters and nodes can be
|
||||
operated again.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
other:
|
||||
- |
|
||||
Sample health policy file was using 60 seconds as the interval which could
|
||||
be misleading. This has been tuned to 600 seconds.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
The load-balancing policy now properly supports the CLUSTER_RECOVER action
|
||||
and NODE_RECOVER action.
|
@ -0,0 +1,6 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
API microversion 1.6 comes with an optional parameter 'check' that tells
|
||||
the engine to perform a health check before doing actual recovery.
|
||||
This applies to both clusters and nodes.
|
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed error that raises when no operation is provided during node health
|
||||
recovery.
|
5
releasenotes/notes/nova-az-fccf8db758642d34.yaml
Normal file
5
releasenotes/notes/nova-az-fccf8db758642d34.yaml
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
fixes:
|
||||
- |
|
||||
Fixed an error introduced by openstacksdk when checking/setting the
|
||||
availability zone of a nova server.
|
@ -0,0 +1,7 @@
|
||||
---
|
||||
features:
|
||||
- |
|
||||
A new feature is introduced in API microversion 1.6 which permits a cluster
|
||||
update operation to change the profile used by the cluster only without
|
||||
actually updating the existing nodes (if any). The new profile will be used
|
||||
when new nodes are created as members of the cluster.
|
5
releasenotes/notes/resize-params-ab4942dc11f05d9a.yaml
Normal file
5
releasenotes/notes/resize-params-ab4942dc11f05d9a.yaml
Normal file
@ -0,0 +1,5 @@
|
||||
---
|
||||
other:
|
||||
- |
|
||||
The parameter checking for cluster-resize operation is revised so that
|
||||
min_step will be ignored if the ajustment type is not CHANGE_IN_PERCENTAGE.
|
Loading…
Reference in New Issue
Block a user