From 3dc277be453ea6631229a06eef658fce874299fb Mon Sep 17 00:00:00 2001 From: Balazs Gibizer Date: Mon, 16 Sep 2019 17:19:52 +0200 Subject: [PATCH] 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 --- nova/api/openstack/compute/servers.py | 3 +-- ...g-neutron-ports-with-resource-request-6d23be654a253625.yaml | 2 +- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/nova/api/openstack/compute/servers.py b/nova/api/openstack/compute/servers.py index 48b89e73df..2148fc99ff 100644 --- a/nova/api/openstack/compute/servers.py +++ b/nova/api/openstack/compute/servers.py @@ -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: diff --git a/releasenotes/notes/support-cold-migrating-neutron-ports-with-resource-request-6d23be654a253625.yaml b/releasenotes/notes/support-cold-migrating-neutron-ports-with-resource-request-6d23be654a253625.yaml index 11c9c17700..f26d0646ff 100644 --- a/releasenotes/notes/support-cold-migrating-neutron-ports-with-resource-request-6d23be654a253625.yaml +++ b/releasenotes/notes/support-cold-migrating-neutron-ports-with-resource-request-6d23be654a253625.yaml @@ -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