GitHub user marcaurele opened a pull request:
https://github.com/apache/cloudstack/pull/1709
CLOUDSTACK-7982 - KVM live migration
This is the forward port of our KVM live migration implementation in 4.4.2
to the master branch.
Feedback is welcome. I still have to write the documentation to explain
some configuration for libvirt and some config value in CS.
Things left:
- [ ] Write documentation in cloustack-docs-install & open PR with a link
to this one
- [ ] Add to the upgrade SQL file:
```SQL
UPDATE `cloud`.`hypervisor_capabilities`
SET `storage_motion_supported` = 1
WHERE `hypervisor_capabilities`.`hypervisor_type` = 'KVM';
```
- [ ] Update the PR with a final description
Jira: https://issues.apache.org/jira/browse/CLOUDSTACK-7982
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/exoscale/cloudstack acs/CLOUDSTACK-7982
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1709.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1709
----
commit fb78b20cc3fd93a7a7f2ebd55f6141595f5a2abe
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-04-05T12:00:03Z
Merge pull request #12 from
exoscale/exoscale/feature/kvm-vm-move-with-storage
KVM live migration with non shared storage
commit 886ec5aeeeb226550b80366aead3dd783f8873bf
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-15T13:21:38Z
live migration: cancel migration job on timeout exception
Currently if a migration job takes longer than the max time for a CS job,
then the disk at the remote is deleted but the job keeps running. This
leads to a situation were the VM could be moved on the destination
hypervisors but without a visible disk on the filesystem.
This fix attempt to cancel the migration job on the source host before
requesting the disk removal at the destination.
commit 26ac7e270eff601a94e8d109f5f9deb286818bb2
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-16T05:47:35Z
live migration: delete volume only when migration is cancelled successfully
commit cadeea790ab28463c98ca76f55d0785001bf0fe7
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-16T15:23:50Z
live migration: incorrect check on return value
commit afc49f5a6b224a08e1e7ebc6b7b5050bc940ca65
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-17T07:59:39Z
live migration: getting correct TO object
commit 8f33408251768566bc7cec9db08d2e2b4d974ec3
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-17T08:41:35Z
live migration: fix another ClassCast
commit 18c3e4fda864dd1f4fe480dd77bd92474e4c2744
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-17T10:03:55Z
live migration: propagating command result
commit 23d5217ed8db035d1bc52de53f48823f7e2f3b9d
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-20T11:46:40Z
live migration: more debug information
commit 680ab3f5ecadba4cbc60f3a5239316f6e83a4a6d
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-21T07:56:08Z
more debug
commit a8cc823db321c3de1a697b3044981dcfc041ea42
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-21T09:56:32Z
force command as failed
commit 2783515778c55846f9aebe0fef531a5d6c45a809
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-21T14:46:44Z
live migration: adjustment on the response
commit 2f310e5f8d2f8ef20d90578dcc26deb97f11dca6
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-06-22T09:05:55Z
remove debug code
commit 625b46903645aa8235e7bf859ba97908bb986b10
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-07-05T09:26:02Z
Live migration fixes (#20)
Multiple bugs fixes:
* Incorrect disk size: when provisioning the volume at the destination,
the size was taken from the template and not from the original volume
itself.
* Incorrect details when returning an error: now if an exception is
raised by Libvirt at the agent level, the error message is forwarded
correctly all the way into the job response text.
* Incorrect volume state: when a migration failed, the volume state was
inconsistent and stayed in "Migrating", those interfering with future
commands on the VM. As a result, the event message wasn't sent
either.
commit 684dc923af8d853bb2c73ba37ddf347397965ab4
Author: Marc-Aurèle Brothier <m...@brothier.org>
Date: 2016-07-11T13:42:06Z
live migration: add custom config timeout for MigrateWithStorageCommand
(#22)
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
