Follow up for the bandwidth series

During the feature freeze day re-check campaign the following two small
nits was found in and now fixed by this patch:

* As the resize REST API action is end user facing we should not mention
source compute in the error message.

* Release notes grammar.

Change-Id: Iccc3676e0b6dcb8e6d26385452249971f4613b69
blueprint: support-move-ops-with-qos-ports
This commit is contained in:
Balazs Gibizer 2019-09-16 17:19:52 +02:00
parent 1a0d80dda2
commit 3dc277be45
2 changed files with 2 additions and 3 deletions

View File

@ -949,8 +949,7 @@ class ServersController(wsgi.Controller):
if source_service.version < MIN_COMPUTE_MOVE_BANDWIDTH:
msg = _("The resize action on a server with ports having "
"resource requests, like a port with a QoS "
"minimum bandwidth policy, is not yet supported "
"on the source compute")
"minimum bandwidth policy, is not yet supported.")
raise exc.HTTPConflict(explanation=msg)
try:

View File

@ -1,7 +1,7 @@
---
features:
- |
Cold migration and resize is now supported for servers with neutron ports
Cold migration and resize are now supported for servers with neutron ports
having resource requests. E.g. ports that have QoS minimum bandwidth rules
attached. Note that the migration is only supported if both the source and
the destination compute services are upgraded to Train and the