Hide Forgot
Description of problem: API Guide references the ability to live migrate a VM to another cluster. This feature was only available for a specific use case of upgrading RHEL 6 -> 7 hosts [1] While removing it may be considered a regression, I do think there should be some warning/disclaimer about why it is not recommended. Version-Release number of selected component (if applicable): 4.x REST API Guide https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.1/html-single/rest_api_guide/index#services-vm-methods-migrate Actual results: 6.220.10.1. cluster Specifies the cluster the virtual machine should migrate to. This is an optional parameter. By default, the virtual machine is migrated to another host within the same cluster. Expected results: 6.220.10.1. cluster Specifies the cluster the virtual machine should migrate to. This is an optional parameter. By default, the virtual machine is migrated to another host within the same cluster. Warning: Live migration to another cluster is not unsupported and considerations for target cluster hardware architecture and network architecture should be strongly considered before attempting. Additional info: [1] https://access.redhat.com/articles/1390733 [2] https://bugzilla.redhat.com/show_bug.cgi?id=1441632
This section of the API documentation would have been written by a virt SME, so I'm going to defer this one to the 'Virt' team for review first; if a fix is required, it will need to be submitted as a patch to the API code. Apologies if component is incorrect. Please reassign as needed.
WARN: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops@redhat.comINFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason: [Found non-acked flags: '{'rhevm-4.2.z': '?'}', ] For more info please contact: rhv-devops@redhat.com
We deliver the REST API docs here: REST API SDK doc: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/rest_api_guide/ Version 3 REST API https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/version_3_rest_api_guide/ The developer is supposed to enter documentation in the code and then a writer is supposed to review it. See: https://mojo.redhat.com/docs/DOC-1081736#jive_content_id_Process
Michal, the patches are actually a documentation change in the model exactly as Steve is describing. We never changed any java code here.
it's a java code in model;) it was reviewed and merged...so, now the only question is when/who regenerates the api guide? If that's you/doc team then I suggest to move this to VERIFIED
The doc team should update it. I'll take care of it. It would be helpful to have the query so I can find the patch in Gerrit.
I don't think that the status should be changed to VERIFIED before I've reviewed the new text.
(In reply to Steve Goodman from comment #8) > The doc team should update it. I'll take care of it. It would be helpful to > have the query so I can find the patch in Gerrit. it's in the list, see external trackers
This is no published.
Ha ha. Typo. This is NOW published.
Published at https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.2/html-single/rest_api_guide/#services-vm-methods-migrate Section 6.239.10.1. cluster