cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From likitha <...@git.apache.org>
Subject [GitHub] cloudstack pull request: CLOUDSTACK-8598. CS reports volume migrat...
Date Tue, 30 Jun 2015 08:48:44 GMT
GitHub user likitha opened a pull request:

    https://github.com/apache/cloudstack/pull/543

    CLOUDSTACK-8598. CS reports volume migration as successful but the vo…

    …lume is not migrated in vCenter..
    
    For the following disk operations - migration, snapshot creation, resize, detach and template
creation, CS should do an exact disk match between volume path and vCenter disk name.
    If the exact matching fails to find a disk, CS should fall back to the old method of partial
matching on a trimmed disk.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/likitha/cloudstack CLOUDSTACK-8598

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/cloudstack/pull/543.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 #543
    
----
commit f5db6a81f83ee42e7a557c0c099ea3463857c554
Author: Likitha Shetty <likitha.shetty@citrix.com>
Date:   2015-04-09T05:25:12Z

    CLOUDSTACK-8598. CS reports volume migration as successful but the volume is not migrated
in vCenter..
    For the following disk operations - migration, snapshot creation, resize, detach and template
creation, CS should do an exact disk match between volume path and vCenter disk name.
    If the exact matching fails to find a disk, CS should fall back to the old method of partial
matching on a trimmed disk.

----


---
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 infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

Mime
View raw message