cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.
Date Mon, 19 Dec 2016 07:25:58 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15760437#comment-15760437
] 

ASF GitHub Bot commented on CLOUDSTACK-9681:
--------------------------------------------

GitHub user anshul1886 opened a pull request:

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

    CLOUDSTACK-9681: Make the migration of volume to go through allocator…

    … so that appropraite checks are made
    
    Also, make detached disk to go through findStoragePoolsForMigration API from UI

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

    $ git pull https://github.com/anshul1886/cloudstack-1 CLOUDSTACK-9681

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

    https://github.com/apache/cloudstack/pull/1835.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 #1835
    
----
commit 04857656cf1902b7d9686970cde03be7b0dc9e89
Author: Anshul Gangwar <anshul.gangwar@accelerite.com>
Date:   2016-12-19T06:59:51Z

    CLOUDSTACK-9681: Make the migration of volume to go through allocator so that appropraite
checks are made
    Also, make detached disk to go through findStoragePoolsForMigration API from UI

----


> able to migrate data volume even  logical volume size more than the destination pool
size.
> ------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9681
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9681
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Anshul Gangwar
>            Assignee: Anshul Gangwar
>
> 1. Create a advanced zone 
> 2. Add multiple primary storage's in the same cluster
> 3. add a storage tag to one primary storage(eg:ps3) here total disk capacity is 27 gb
and storage provisioning factor set to 1 and 
> pool.storage.allocated.capacity.disablethresholdto 1
> pool.storage.capacity.disablethreshold to 1 
> 4. create a computer offering by mentioning above storage tag
> 5.deploy a vm using above computer offering
> 6.once it successful,create a data disk(5gb) 
> 7. make sure its ready  and   resize the data disk from 5gb to 100 gb 
> 8.migrate the volume from ps2 to ps3 even though it says not suitable.
> here source volume size > destination storage pool size.
> actual result: 
> volume migration successful  even though volume size is greater than  destination primary
storage size instead of failing migration operation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message