[GitHub] cloudstack issue #1709: CLOUDSTACK-7982 - KVM live migration

2016-11-20 Thread rhtyd
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1709 @marcaurele can you check the Travis failure? Thanks. --- 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

[GitHub] cloudstack pull request #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-24 Thread marcaurele
Github user marcaurele commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/1709#discussion_r84632272 --- Diff: plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java --- @@ -943,6 +962,11 @@ public boolean configu

[GitHub] cloudstack pull request #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-21 Thread mlsorensen
Github user mlsorensen commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/1709#discussion_r84509497 --- Diff: core/src/com/cloud/agent/api/CancelMigrationCommand.java --- @@ -0,0 +1,35 @@ +// Licensed to the Apache Software Foundation (ASF) under

[GitHub] cloudstack pull request #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-21 Thread wido
Github user wido commented on a diff in the pull request: https://github.com/apache/cloudstack/pull/1709#discussion_r84501931 --- Diff: plugins/hypervisors/kvm/src/com/cloud/hypervisor/kvm/resource/LibvirtComputingResource.java --- @@ -943,6 +962,11 @@ public boolean configure(fin

[GitHub] cloudstack issue #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-21 Thread rhtyd
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1709 @marcaurele I had another look, you're right -- we don't have any way to see mgmt server log for Travis runs. I think rebase/squash and do a push -f to re-kick Travis run. --- If your project is

[GitHub] cloudstack issue #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-21 Thread marcaurele
Github user marcaurele commented on the issue: https://github.com/apache/cloudstack/pull/1709 @rhtyd I found the log but it doesn't give the mgmt server log output, only the job's output which got a `Command failed due to Internal Server Error` in an API response. I'll rebase & squash

[GitHub] cloudstack issue #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-20 Thread rhtyd
Github user rhtyd commented on the issue: https://github.com/apache/cloudstack/pull/1709 @marcaurele yes, click on the details, go to the failing job and open the raw build log/output for debugging. Can you rebase again please, squash the changes. I can help run tests on this PR. --

[GitHub] cloudstack issue #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-17 Thread marcaurele
Github user marcaurele commented on the issue: https://github.com/apache/cloudstack/pull/1709 Is there a way to get the management server log of the travis job? --- 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 proj

[GitHub] cloudstack pull request #1709: CLOUDSTACK-7982 - KVM live migration

2016-10-16 Thread marcaurele
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

Re: CLOUDSTACK-7982 - KVM live migration

2016-08-16 Thread Rajani Karuturi
You are now on the Jira contributors list. You should be able to assign issues. Thanks, ~ Rajani http://cloudplatform.accelerite.com/ On August 12, 2016 at 5:57 PM, ma...@exoscale.ch (ma...@exoscale.ch) wrote: Need some Jira love... Can someone give me the rights to assign myself to this JIRA iss

CLOUDSTACK-7982 - KVM live migration

2016-08-12 Thread ma...@exoscale.ch
Need some Jira love... Can someone give me the rights to assign myself to this JIRA issue, or to assign myself directly. Thanks https://issues.apache.org/jira/browse/CLOUDSTACK-7982 There are new configuration items and some explainations to be documented. I thought to write it in the documenta