openstack
/
horizon
Code Issues Proposed changes

Minor release note cleanup 

* Nova 2.9 is confusing. It is not a nova version.
  2.9 is a version of Nova API.
* It is better to say "Create Volume" in which panel.
  "Create Volume in Launch Instance form" would be clear to readers.
* Fix typo in the drop-nova-network release note.

Change-Id: If967892a95a798349591b17c623f289ee882a6fe
This commit is contained in:
Akihiro Motoki 2017-06-25 20:23:34 +09:00
parent e8d1dd99a6
commit 6b261df9ca
3 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
releasenotes/notes/bug-1593903-8fb8721dc2449f71.yaml
View File

@ -2,5 +2,5 @@
features:
- |
Added a locked status column on admin/project instances table. It will
show a locked or unlocked icon if nova 2.9 or above is used. The locked
status is also available on instance details panel.
show a locked or unlocked icon if nova API 2.9 or above is used.
The locked status is also available on instance details panel.

2
releasenotes/notes/bug-1678109-4440ebe90908647d.yaml
View File

@ -2,4 +2,4 @@
features:
- Added a new ``create_volume`` setting under the
``LAUNCH_INSTANCE_DEFAULTS`` dict. This allows you to set the default value
of "Create Volume", when Cinder is available.
of "Create Volume" in "Launch Instance" form, when Cinder is available.

2
releasenotes/notes/drop-nova-network-2186d008f696cfa7.yaml
View File

@ -3,7 +3,7 @@ upgrade:
- |
[:blueprint:`drop-nova-network`]
Horizon nova-network floating IP and security groups supports have been
droppped in Pike release. nova-network has been marked as deprecated
dropped in Pike release. nova-network has been marked as deprecated
in Nova in Newton release and horizon support was dropped in favor of it.
Neutron now becomes a requirement for floating IP and security groups.
Other operations on instances which created with nova-network should