Add release notes for Rocky

Change-Id: I904531ad129d02fd08ae093b16594f0eee3126a4
This commit is contained in:
Shu Muto 2018-07-25 16:07:14 +09:00
parent 635be679e5
commit 7c71127d9a
2 changed files with 31 additions and 0 deletions

View File

@ -1,6 +1,7 @@
---
features:
- |
[`blueprint add-cluster-resize-action <https://blueprints.launchpad.net/senlin-dashboard/+spec/add-cluster-resize-action>`_]
Resize action for cluster is added. This action is added
as row action for each cluster in Clusters table view.
Although, this action is only for Angularized clusters panel.

View File

@ -0,0 +1,30 @@
---
fixes:
- >
[`bug/1777545 <https://bugs.launchpad.net/senlin-dashboard/+bug/1777545>`_]
Fixed issue the deleted item is selected again with batch delete.
Item selections on table view for batch actions are not cleared
after execution of actions. To ensure to clear item selections,
`hzTable:clearSelection` event is emitted.
- >
[`bug/1746706 <https://bugs.launchpad.net/senlin-dashboard/+bug/1746706>`_]
Reproduced navigations when refreshing details view. Previously the fix
for [`bug/1681627 <https://bugs.launchpad.net/horizon/+bug/1681627>`_]
allowed us to reload or directly open Angular-based detail page (ngdetail),
but the navigation menu was not reproduced correctly.
- >
Fixed `type` for profile. Senlin API uses `type_name` for type, but
dashboard did not process `type_name`. So this issue caused error to
handle Profile object.
- >
[`bug/1754416 <https://bugs.launchpad.net/senlin-dashboard/+bug/1754416>`_]
`region_name` was not passed on when using the senlin-dashboard.
This makes the client always fallback on the first region. This issue was
fixed.
- >
[`bug/1754183 <https://bugs.launchpad.net/senlin-dashboard/+bug/1754183>`_]
Horizon by default sets the Project dashboard as default for non-admin
users. The _50_senlin.py file that comes with the Senlin dashboard also
has 'DEFAULT = True' set. Because 'cluster' comes before 'project'
alphabetically, this defaults all non-admin users to getting the cluster
dashboard on login. This issue was fixed.