[GitHub] cloudstack issue #1037: Fix for CLOUDSTACK-8937 - XenServer migrations with ...
Github user atrbgithub commented on the issue: https://github.com/apache/cloudstack/pull/1037 I believe this can be closed now. https://github.com/apache/cloudstack/pull/1336 and https://github.com/apache/cloudstack/pull/1596 address this problem. --- 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. ---
[GitHub] cloudstack issue #925: Fix for CLOUDSTACK-8937 - XenServer migrations with s...
Github user atrbgithub commented on the issue: https://github.com/apache/cloudstack/pull/925 I believe this can be closed now. https://github.com/apache/cloudstack/pull/1336 and https://github.com/apache/cloudstack/pull/1596 address this problem. --- 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. ---
[GitHub] cloudstack pull request: Fix for CLOUDSTACK-8937 - XenServer migra...
Github user atrbgithub commented on the pull request: https://github.com/apache/cloudstack/pull/1037#issuecomment-162829832 Hi @wilderrodrigues To test this you would need to have 2 or more cloudstack management servers operating in a cluster with Xen hosts. Before applying this fix, when you try to live migrate vm's between hosts (root disks on local storage or primary storage), occasionally this will fail. It is random depending on which management servers are allocated the job. After applying the change in the pull request, migrations should no longer fail. Hope that is ok. 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 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. ---
[GitHub] cloudstack pull request: Fix for CLOUDSTACK-8937 - XenServer migra...
Github user atrbgithub commented on the pull request: https://github.com/apache/cloudstack/pull/925#issuecomment-154042688 Fix for master branch has been proposed here https://github.com/apache/cloudstack/pull/1037 --- 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. ---
[GitHub] cloudstack pull request: Fix for CLOUDSTACK-8937 - XenServer migra...
GitHub user atrbgithub opened a pull request: https://github.com/apache/cloudstack/pull/1037 Fix for CLOUDSTACK-8937 - XenServer migrations with storage failing i⦠â¦n clustered management server environment This pull request relates to the following Jira bug report: https://issues.apache.org/jira/browse/CLOUDSTACK-8937 A previous fix was proposed for the 4.5 branch here: https://github.com/apache/cloudstack/pull/925 This was tested within a working environment and everything appeared to work fine. @remibergsma Unfortunately I have not been able to test this within a running environment. Everything appears to compile ok and tests pass. I believe you are much further along in the Cloudstack automated testing arena, so I'm not sure if this is something you would be able to test at some point in the future? If not I will be able to test it when my current workload permits and report back here with my findings. You can merge this pull request into a Git repository by running: $ git pull https://github.com/autotraderuk/cloudstack 4.6-CS-8937 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/1037.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 #1037 commit 1e505e08883f4735c70e9d0de03d24efe990ed2a Author: atrbgithub Date: 2015-11-05T11:53:55Z Fix for CLOUDSTACK-8937 - XenServer migrations with storage failing in clustered management server environment --- 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. ---
[GitHub] cloudstack pull request: Fix for CLOUDSTACK-8937 - XenServer migra...
Github user atrbgithub commented on the pull request: https://github.com/apache/cloudstack/pull/925#issuecomment-150595815 Hi Remi, I've forced-pushed the commit (amended the commit message and re-pushed) and it looks like the tests are running once more. I had a look at making a similar change to the 4.6 branch however it looks like a lot of refactoring has taken place between the 4.5 branch and master. Please see https://github.com/apache/cloudstack/commit/30e72e4a156a224f109f67b277e1e439bdcc9158 for example. We're currently running with 4.5.2 (live and test) internally and this change appears to have fixed the issues we were seeing. Perhaps if there is ever a 4.5.3 release, this could be included with it. It's possible we could upgrade our internal test environment to master to see how the migrations are working now with the refactored code, but I won't get chance to do this for another few weeks unfortunately. --- 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. ---
[GitHub] cloudstack pull request: CLOUDSTACK-8976 - Sorting of security gro...
Github user atrbgithub commented on the pull request: https://github.com/apache/cloudstack/pull/937#issuecomment-149964321 @DaanHoogland Sorry about that. Sorted now. --- 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. ---
[GitHub] cloudstack pull request: Sorting of security groups
Github user atrbgithub commented on the pull request: https://github.com/apache/cloudstack/pull/937#issuecomment-149888063 Hi @DaanHoogland , I've raised jira ticket for this request: https://issues.apache.org/jira/browse/CLOUDSTACK-8976 Cheers! --- 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. ---
[GitHub] cloudstack pull request: Sorting of security groups
GitHub user atrbgithub opened a pull request: https://github.com/apache/cloudstack/pull/937 Sorting of security groups Simple change to sort the security groups in alphabetical order within the instance creation wizard. This makes it much easier to find a security group when the user is presented with a long list. You can merge this pull request into a Git repository by running: $ git pull https://github.com/autotraderuk/cloudstack sec-group-sorting Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/937.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 #937 commit ff7a5bbd9b615818bb4b4691df0fc8d9170a0c5d Author: atrbgithub Date: 2015-10-16T20:13:51Z Sorting of security groups --- 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. ---
[GitHub] cloudstack pull request: Fix for CLOUDSTACK-8937 - XenServer migra...
GitHub user atrbgithub opened a pull request: https://github.com/apache/cloudstack/pull/925 Fix for CLOUDSTACK-8937 - XenServer migrations with storage failing i⦠â¦n clustered management server environment This pull request relates to the following Jira bug report: https://issues.apache.org/jira/browse/CLOUDSTACK-8937 This has been tested by checking out the tagged 4.5.2 release, making the changes detailed, compiling and then copying the webapps/client/WEB-INF/lib/cloud-plugin-hypervisor-xenserver-4.5.2.jar file into a 4.5.2 cluster of 4 management servers. The cluster is running two xenserver pods, the hosts of which are running Xenserver 6.5. Live migrations have then been tested with vm's which have single and multiple disks on local storage. Tests have only been performed on live migrations within the same pod. Prior to this fix, migrations would intermittently fail (details in the above jira link). With this fix in place, no further issues have been seen. You can merge this pull request into a Git repository by running: $ git pull https://github.com/autotraderuk/cloudstack 4.5-CS-8937 Alternatively you can review and apply these changes as the patch at: https://github.com/apache/cloudstack/pull/925.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 #925 --- 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. ---
