[jira] [Commented] (CLOUDSTACK-6797) volume resize hsould not be allowed for detached volumes

2014-06-02 Thread Min Chen (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14016003#comment-14016003
 ] 

Min Chen commented on CLOUDSTACK-6797:
--

Consulted with Alex, newly created volumes should also be counted in allocated 
space even if it is not attached to a VM. So #1 you mentioned here may be a bug 
in our product.

 volume resize hsould not be allowed for detached volumes
 

 Key: CLOUDSTACK-6797
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6797
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0, 4.4.0
Reporter: prashant kumar mishra
Assignee: Min Chen
Priority: Critical
 Fix For: 4.4.0

 Attachments: Logs_db.rar, screenshot-1.jpg, screenshot-2.jpg


 =since resize space is counted in allocated space even though it cant be 
 attach to VM , other storage operation will fail because threshold value 
 If resize is allowed in volume  detach
 ==
 1-since there is no check for how much can be increased , suppose user has 
 resized it to 1000GB
 2-when user try to attach volume to vm it will fail since available space is 
 not sufficient . 
 3-even though user is not able to use the resized volume ,CS will count  
 1000GB in allocated storage .
 4-Dash will show allocated percentage 100%
 5-Because threshold values , we cant  perform any operation to that PS
 If resize is allowed online ( volume  Attach) state it will fail in first 
 place and will not cause any problem



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6797) volume resize hsould not be allowed for detached volumes

2014-05-30 Thread prashant kumar mishra (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14013481#comment-14013481
 ] 

prashant kumar mishra commented on CLOUDSTACK-6797:
---

1-newly created volume don't get counted in allocated space until it is 
attached to a vm , so it is not going to affect storage operation even we 
create  huge disk .
2-resized disk  get counted it allocated space , so if user create huge disk , 
it will affects all storage operation .
3-there should be some checks  for max size .






 volume resize hsould not be allowed for detached volumes
 

 Key: CLOUDSTACK-6797
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6797
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0, 4.4.0
Reporter: prashant kumar mishra
Assignee: Min Chen
Priority: Critical
 Fix For: 4.4.0

 Attachments: Logs_db.rar, screenshot-1.jpg, screenshot-2.jpg


 =since resize space is counted in allocated space even though it cant be 
 attach to VM , other storage operation will fail because threshold value 
 If resize is allowed in volume  detach
 ==
 1-since there is no check for how much can be increased , suppose user has 
 resized it to 1000GB
 2-when user try to attach volume to vm it will fail since available space is 
 not sufficient . 
 3-even though user is not able to use the resized volume ,CS will count  
 1000GB in allocated storage .
 4-Dash will show allocated percentage 100%
 5-Because threshold values , we cant  perform any operation to that PS
 If resize is allowed online ( volume  Attach) state it will fail in first 
 place and will not cause any problem



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6797) volume resize hsould not be allowed for detached volumes

2014-05-28 Thread Animesh Chaturvedi (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011666#comment-14011666
 ] 

Animesh Chaturvedi commented on CLOUDSTACK-6797:


Min do you mind checking this 

 volume resize hsould not be allowed for detached volumes
 

 Key: CLOUDSTACK-6797
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6797
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0, 4.4.0
Reporter: prashant kumar mishra
Assignee: Min Chen
Priority: Critical
 Fix For: 4.4.0

 Attachments: Logs_db.rar, screenshot-1.jpg, screenshot-2.jpg


 =since resize space is counted in allocated space even though it cant be 
 attach to VM , other storage operation will fail because threshold value 
 If resize is allowed in volume  detach
 ==
 1-since there is no check for how much can be increased , suppose user has 
 resized it to 1000GB
 2-when user try to attach volume to vm it will fail since available space is 
 not sufficient . 
 3-even though user is not able to use the resized volume ,CS will count  
 1000GB in allocated storage .
 4-Dash will show allocated percentage 100%
 5-Because threshold values , we cant  perform any operation to that PS
 If resize is allowed online ( volume  Attach) state it will fail in first 
 place and will not cause any problem



--
This message was sent by Atlassian JIRA
(v6.2#6252)


[jira] [Commented] (CLOUDSTACK-6797) volume resize hsould not be allowed for detached volumes

2014-05-28 Thread Min Chen (JIRA)

[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-6797?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14011871#comment-14011871
 ] 

Min Chen commented on CLOUDSTACK-6797:
--

This is as designed. We don't do size checking even for createVolume even if 
user is creating an empty volume. What is missing in CloudStack is a monitoring 
and alert system to system admin for such cases to increase storage to satisfy 
user's need. We should not provide a certain Disk offering that we can not 
fulfill. As long as a disk offering is provided to user, we cannot throw out 
error to prevent users from using it.

 volume resize hsould not be allowed for detached volumes
 

 Key: CLOUDSTACK-6797
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6797
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.2.0, 4.4.0
Reporter: prashant kumar mishra
Assignee: Min Chen
Priority: Critical
 Fix For: 4.4.0

 Attachments: Logs_db.rar, screenshot-1.jpg, screenshot-2.jpg


 =since resize space is counted in allocated space even though it cant be 
 attach to VM , other storage operation will fail because threshold value 
 If resize is allowed in volume  detach
 ==
 1-since there is no check for how much can be increased , suppose user has 
 resized it to 1000GB
 2-when user try to attach volume to vm it will fail since available space is 
 not sufficient . 
 3-even though user is not able to use the resized volume ,CS will count  
 1000GB in allocated storage .
 4-Dash will show allocated percentage 100%
 5-Because threshold values , we cant  perform any operation to that PS
 If resize is allowed online ( volume  Attach) state it will fail in first 
 place and will not cause any problem



--
This message was sent by Atlassian JIRA
(v6.2#6252)