openstack/nova
Code Issues Proposed changes

Fix typos in release notes

Browse Source 
This is to fix below typos in release notes:
  Keytone
  specifed
  availabilty
  maange
  expetected
  migratons
  maintanance

Change-Id: Ifbecf095f2f549d4ec40892484ec1b725927fb44
This commit is contained in:
zhufl 2018-03-19 17:33:59 +08:00 committed by Ken'ichi Ohmichi
parent 37b4f77b5e
commit 0e061491aa
7 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
releasenotes/notes/bug-1695861-ebc8a0aa7a87f7e0.yaml
View File

@ -3,7 +3,7 @@ fixes:
- |
Fixes `bug 1695861`_ in which the aggregate API accepted requests that
have availability zone names including ':'. With this fix, a creation
of an availabilty zone whose name includes ':' results in a
of an availability zone whose name includes ':' results in a
``400 BadRequest`` error response.
.. _bug 1695861: https://bugs.launchpad.net/nova/+bug/1695861

2
releasenotes/notes/deprecate-nova-manage-network-commands-212726e67bffdfc4.yaml
View File

@ -4,7 +4,7 @@ deprecations:
The following nova-manage commands are deprecated for removal in the
Nova 15.0.0 Ocata release:
* nova-maange account scrub
* nova-manage account scrub
* nova-manage fixed *
* nova-manage floating *
* nova-manage network *

2
releasenotes/notes/hyperv-uefi-secure-boot-a2a617ac2c313afd.yaml
View File

@ -7,7 +7,7 @@ features:
* Images should be prepared for Generation 2 VMs. The image property
"hw_machine_type=hyperv-gen2" is mandatory.
* The guest OS type must be specified in order to properly spawn the VMs.
It can be specifed through the image property "os_type", and the
It can be specified through the image property "os_type", and the
acceptable values are "windows" or "linux".
* The UEFI Secure Boot feature can be requested through the image property
"os_secure_boot" (acceptable values: "disabled", "optional", "required")

2
releasenotes/notes/instance-path-2efca507456d8a70.yaml
View File

@ -9,6 +9,6 @@ upgrade:
``/opt/stack/data/nova/instances/34198248-5541-4d52-a0b4-a6635a7802dd/``.
In Newton backward compatibility is dropped. For instances that haven't
been restarted since Folsom and earlier maintanance should be scheduled
been restarted since Folsom and earlier maintenance should be scheduled
before upgrade(stop, rename directory to instance.uuid, then start) so Nova
will start using new paths for instances.

2
releasenotes/notes/removing-pci-parent_addr-migration-f7dfa2b441cf30e8.yaml
View File

@ -3,5 +3,5 @@ upgrade:
- In mitaka, an online migration was added to migrate older SRIOV parent
device information from extra_info to a new column. Since two releases
have gone out with that migration, it is removed in Ocata and operators
are expetected to have run it as part of either of the previous two
are expected to have run it as part of either of the previous two
releases, if applicable.

2
releasenotes/notes/server_migrations-30519b35d3ea6763.yaml
View File

@ -2,7 +2,7 @@
features:
- |
Add two new list/show API for server-migration.
The list API will return the in progress live migratons
The list API will return the in progress live migrations
information of a server. The show API will return
a specified in progress live migration of a server.
This has been added in microversion 2.23.

2
releasenotes/notes/validate-expired-user-tokens-57a265cb4ee4ba6f.yaml
View File

@ -8,7 +8,7 @@ features:
has expired. In order to use this functionality a service user needs to
be created. Add service user configurations in ``nova.conf`` under
``service_user`` group and set ``send_service_user_token`` flag to
``True``. The minimum Keytone API version 3.8 and Keystone middleware
``True``. The minimum Keystone API version 3.8 and Keystone middleware
version 4.12.0 is required to use this functionality.
This only currently works with Nova - Cinder and Nova - Neutron API
interactions.