[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2018-01-02 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9681:


rhtyd commented on issue #1835: CLOUDSTACK-9681: Make the migration of volume 
to go through allocator…
URL: https://github.com/apache/cloudstack/pull/1835#issuecomment-354760635
 
 
   Ping, any updates? I'll remove this from 4.11 milestone due to lack of 
engagement and discussions.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2017-12-17 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9681:


rhtyd commented on issue #1835: CLOUDSTACK-9681: Make the migration of volume 
to go through allocator…
URL: https://github.com/apache/cloudstack/pull/1835#issuecomment-352288706
 
 
   @anshul1886 ping, can you fix the build failures? 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2017-11-28 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9681:


rhtyd commented on issue #1835: CLOUDSTACK-9681: Make the migration of volume 
to go through allocator…
URL: https://github.com/apache/cloudstack/pull/1835#issuecomment-347541157
 
 
   @anshul1886 please check/fix build failures


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2017-11-23 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9681:


blueorangutan commented on issue #1835: CLOUDSTACK-9681: Make the migration of 
volume to go through allocator…
URL: https://github.com/apache/cloudstack/pull/1835#issuecomment-346700104
 
 
   Packaging result: ✖centos6 ✔centos7 ✖debian. JID-1291


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2017-11-23 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9681:


blueorangutan commented on issue #1835: CLOUDSTACK-9681: Make the migration of 
volume to go through allocator…
URL: https://github.com/apache/cloudstack/pull/1835#issuecomment-346697556
 
 
   @rhtyd a Jenkins job has been kicked to build packages. I'll keep you posted 
as I make progress.


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2017-11-23 Thread ASF GitHub Bot (JIRA) 

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

ASF GitHub Bot commented on CLOUDSTACK-9681:


rhtyd commented on issue #1835: CLOUDSTACK-9681: Make the migration of volume 
to go through allocator…
URL: https://github.com/apache/cloudstack/pull/1835#issuecomment-346697453
 
 
   @blueorangutan package 


This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> 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.4.14#64029)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2016-12-18 Thread BRASCLOUD (JIRA) 

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

BRASCLOUD commented on CLOUDSTACK-9681:
---

## Todo texto digitado acima será adicionado no ticket [[[36]]] ##



Olá, Anshul Gangwar (JIRA).



O seu ticket foi aberto com sucesso em nosso Suporte.


[1]#36 - [jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even 
logical volume size more than the destination pool size.

Criado por Anshul Gangwar (JIRA) em 19/12/2016 05:52:49




Para visualizar o ticket completo, [2]clique aqui








[3]Acelerato

[1] https://brascloud.acelerato.com/tickets/36
[2] https://brascloud.acelerato.com/tickets/36
[3] http://www.acelerato.com


> 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)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2016-12-18 Thread BRASCLOUD (JIRA) 

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

BRASCLOUD commented on CLOUDSTACK-9681:
---

## Todo texto digitado acima será adicionado no ticket [[[31]]] ##



Olá, Anshul Gangwar (JIRA).



O seu ticket foi aberto com sucesso em nosso Suporte.


[1]#31 - [jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even 
logical volume size more than the destination pool size.

Criado por Anshul Gangwar (JIRA) em 19/12/2016 05:26:01




Para visualizar o ticket completo, [2]clique aqui








[3]Acelerato

[1] https://brascloud.acelerato.com/tickets/31
[2] https://brascloud.acelerato.com/tickets/31
[3] http://www.acelerato.com


> 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)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2016-12-18 Thread ASF GitHub Bot (JIRA) 

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-9681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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 
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)

[jira] [Commented] (CLOUDSTACK-9681) able to migrate data volume even logical volume size more than the destination pool size.

2016-12-18 Thread BRASCLOUD (JIRA) 

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

BRASCLOUD commented on CLOUDSTACK-9681:
---

## Todo texto digitado acima será adicionado no ticket [[[15]]] ##



Olá, Anshul Gangwar (JIRA).



O seu ticket foi aberto com sucesso em nosso Suporte.


[1]#15 - [jira] [Created] (CLOUDSTACK-9681) able to migrate data volume even 
logical volume size more than the destination pool size.

Criado por Anshul Gangwar (JIRA) em 19/12/2016 04:24:15




Para visualizar o ticket completo, [2]clique aqui








[3]Acelerato

[1] https://brascloud.acelerato.com/tickets/15
[2] https://brascloud.acelerato.com/tickets/15
[3] http://www.acelerato.com


> 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)