(from:
From: Rikimaru Honjo <honjo.rikimaru@*>
Message-ID: <a2777c81-cbd8-7c10-cf08-92f37699e717@*>
Date: Thu, 28 Mar 2019 16:23:35 +0900
To: openstack-discuss@*
List-Id: Discussion of OpenStack use and development <openstack-discuss.lists.openstack.org>
)
By the way, I confirmed the detail of the solution provided by Matt after that.
As a result, I found that the solution requires a special nova-conductor process "nova-conductor-powervm".
Also, further interesting info:
(from: cbd8-7c10- cf08-92f37699e7 17@*> discuss. lists.openstack .org>
From: Rikimaru Honjo <honjo.rikimaru@*>
Message-ID: <a2777c81-
Date: Thu, 28 Mar 2019 16:23:35 +0900
To: openstack-discuss@*
List-Id: Discussion of OpenStack use and development <openstack-
)
By the way, I confirmed the detail of the solution provided by Matt after that. -powervm" .
As a result, I found that the solution requires a special nova-conductor process "nova-conductor
https:/ /github. com/openstack/ nova-powervm/ blob/newton- eol/README. rst#live- migration
I think that it is troublesome for users...
Current PowerVMLiveMigr ateData was moved to nova tree in the following patch. /review. openstack. org/#/c/ 391284/
https:/
Best regards,