Github user asfgit closed the pull request at:
https://github.com/apache/cloudstack/pull/548
---
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
Github user bhaisaab commented on the pull request:
https://github.com/apache/cloudstack/pull/548#issuecomment-134926126
LGTM
---
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
enab
Github user remibergsma commented on the pull request:
https://github.com/apache/cloudstack/pull/548#issuecomment-129227023
Who wants to step in and finish this work? It seems the original author is
not able to finish it. If no one steps in, we'll have to close the PR without
merging
Github user DaanHoogland commented on the pull request:
https://github.com/apache/cloudstack/pull/548#issuecomment-124869177
code changes good or not, let's not accept any changes without (unit) tests
any more.
---
If your project is set up for it, you can reply to this email and hav
Github user sureshanaparti commented on the pull request:
https://github.com/apache/cloudstack/pull/548#issuecomment-124476270
Code changes to update the volume chain info are perfect.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitH
Github user sateesh-chodapuneedi commented on the pull request:
https://github.com/apache/cloudstack/pull/548#issuecomment-122199556
LGTM.
I see this patch is updating chain information for all 3 cases of storage
migration,
1) volume migration
2) vm migration with storage
GitHub user likitha opened a pull request:
https://github.com/apache/cloudstack/pull/548
CLOUDSTACK-8602. MigrateVirtualMachineWithVolume leaves old chain datâ¦
â¦a for volume.
Update chain info of a volume after migration.
You can merge this pull request into a Git repo
