[jira] [Updated] (CLOUDSTACK-3542) Ceph RBD provides wrong usage info to CloudStack

2013-08-14 Thread Prasanna Santhanam (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-3542:
---

Labels: ceph doc rbd  (was: ceph rbd)

 Ceph RBD provides wrong usage info to CloudStack
 

 Key: CLOUDSTACK-3542
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3542
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Storage Controller
Affects Versions: 4.1.0
 Environment: Ubuntu 12.04.2
Reporter: Indra Pramana
Assignee: sadhu suresh
  Labels: ceph, doc, rbd

 I am installing CloudStack 4.1.0 to use Ceph RBD as primary storage. I failed 
 to create VM instance using the RBD as primary storage because Ceph provides 
 wrong disk usage information. See below:
 root@hv-kvm-02:~# virsh pool-info bab81ce8-d53f-3a7d-b8f6-841702f65c89
 Name:   bab81ce8-d53f-3a7d-b8f6-841702f65c89
 UUID:   bab81ce8-d53f-3a7d-b8f6-841702f65c89
 State:  running
 Persistent: no
 Autostart:  no
 Capacity:   5.47 TiB
 Allocation: 34819.02 TiB -- wrong information
 Available:  5.47 TiB
 Record on the storage_pool table on cloud database:
 +-+-+--+---+--++++---++---+++-+-+-+-+-+---+
 | id  | name| uuid | pool_type
  | port | data_center_id | pod_id | cluster_id | available_bytes   | 
 capacity_bytes | host_address  | user_info
   | path   | created | removed
  | update_time | status  | storage_provider_id | scope |
 +-+-+--+---+--++++---++---+++-+-+-+-+-+---+
 | 209 | sc-image| bab81ce8-d53f-3a7d-b8f6-841702f65c89 | RBD  
  | 6789 |  6 |  6 |  6 | 38283921137336466 |  
 6013522722816 | ceph-mon.xxx.com | admin:xxx | sc1| 
 2013-07-13 08:58:27 | NULL| NULL| Up  |   
  NULL | NULL  |
 ===
 2013-07-15 11:27:31,632 DEBUG [cloud.alert.AlertManagerImpl] 
 (CapacityChecker:null) System Alert: Low Available Storage in cluster 
 Cluster-01 pod Pod-01 of availability zone 01
 2013-07-15 11:27:31,632 DEBUG [cloud.alert.AlertManagerImpl] 
 (CapacityChecker:null) Available storage space is low, total: 13282342 MB, 
 used: 36510398411 MB (274879.22%)
 ===
 As a result, VM instance creation fails since it's not able to find available 
 storage pool.
 ===
 2013-07-15 11:15:28,313 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-3:job-168) Checking pool: 208 for volume allocation 
 [Vol[227|vm=225|ROOT]], maxSize : 15828044742656, totalAllocatedSize : 
 1769538048, askingSize : 8589934592, allocated disable threshold: 0.85
 2013-07-15 11:15:28,313 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) 
 Checking if storage pool is suitable, name: sc-image ,poolId: 209
 2013-07-15 11:15:28,313 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is 
 localStorageAllocationNeeded? false
 2013-07-15 11:15:28,313 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is 
 storage pool shared? true
 2013-07-15 11:15:28,317 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-3:job-168) Checking pool 209 for storage, totalSize: 
 6013522722816, usedBytes: 38283921137336466, usedPct: 6366.305226067051, 
 disable threshold: 0.85
 2013-07-15 11:15:28,317 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-3:job-168) Insufficient space on pool: 209 since its usage 
 percentage: 6366.305226067051 has crossed the 
 pool.storage.capacity.disablethreshold: 0.85
 2013-07-15 11:15:28,317 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-3:job-168) 
 FirstFitStoragePoolAllocator returning 1 suitable storage pools
 2013-07-15 11:15:28,317 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-3:job-168) Checking suitable pools for volume (Id, Type): 
 (228,DATADISK)
 2013-07-15 11:15:28,317 DEBUG [cloud.deploy.FirstFitPlanner] 
 

[jira] [Updated] (CLOUDSTACK-3542) Ceph RBD provides wrong usage info to CloudStack

2013-08-14 Thread Prasanna Santhanam (JIRA)

 [ 
https://issues.apache.org/jira/browse/CLOUDSTACK-3542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Prasanna Santhanam updated CLOUDSTACK-3542:
---

Component/s: (was: Storage Controller)
 Doc

 Ceph RBD provides wrong usage info to CloudStack
 

 Key: CLOUDSTACK-3542
 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3542
 Project: CloudStack
  Issue Type: Bug
  Security Level: Public(Anyone can view this level - this is the 
 default.) 
  Components: Doc
Affects Versions: 4.1.0
 Environment: Ubuntu 12.04.2
Reporter: Indra Pramana
Assignee: sadhu suresh
  Labels: ceph, doc, rbd

 I am installing CloudStack 4.1.0 to use Ceph RBD as primary storage. I failed 
 to create VM instance using the RBD as primary storage because Ceph provides 
 wrong disk usage information. See below:
 root@hv-kvm-02:~# virsh pool-info bab81ce8-d53f-3a7d-b8f6-841702f65c89
 Name:   bab81ce8-d53f-3a7d-b8f6-841702f65c89
 UUID:   bab81ce8-d53f-3a7d-b8f6-841702f65c89
 State:  running
 Persistent: no
 Autostart:  no
 Capacity:   5.47 TiB
 Allocation: 34819.02 TiB -- wrong information
 Available:  5.47 TiB
 Record on the storage_pool table on cloud database:
 +-+-+--+---+--++++---++---+++-+-+-+-+-+---+
 | id  | name| uuid | pool_type
  | port | data_center_id | pod_id | cluster_id | available_bytes   | 
 capacity_bytes | host_address  | user_info
   | path   | created | removed
  | update_time | status  | storage_provider_id | scope |
 +-+-+--+---+--++++---++---+++-+-+-+-+-+---+
 | 209 | sc-image| bab81ce8-d53f-3a7d-b8f6-841702f65c89 | RBD  
  | 6789 |  6 |  6 |  6 | 38283921137336466 |  
 6013522722816 | ceph-mon.xxx.com | admin:xxx | sc1| 
 2013-07-13 08:58:27 | NULL| NULL| Up  |   
  NULL | NULL  |
 ===
 2013-07-15 11:27:31,632 DEBUG [cloud.alert.AlertManagerImpl] 
 (CapacityChecker:null) System Alert: Low Available Storage in cluster 
 Cluster-01 pod Pod-01 of availability zone 01
 2013-07-15 11:27:31,632 DEBUG [cloud.alert.AlertManagerImpl] 
 (CapacityChecker:null) Available storage space is low, total: 13282342 MB, 
 used: 36510398411 MB (274879.22%)
 ===
 As a result, VM instance creation fails since it's not able to find available 
 storage pool.
 ===
 2013-07-15 11:15:28,313 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-3:job-168) Checking pool: 208 for volume allocation 
 [Vol[227|vm=225|ROOT]], maxSize : 15828044742656, totalAllocatedSize : 
 1769538048, askingSize : 8589934592, allocated disable threshold: 0.85
 2013-07-15 11:15:28,313 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) 
 Checking if storage pool is suitable, name: sc-image ,poolId: 209
 2013-07-15 11:15:28,313 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is 
 localStorageAllocationNeeded? false
 2013-07-15 11:15:28,313 DEBUG 
 [storage.allocator.AbstractStoragePoolAllocator] (Job-Executor-3:job-168) Is 
 storage pool shared? true
 2013-07-15 11:15:28,317 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-3:job-168) Checking pool 209 for storage, totalSize: 
 6013522722816, usedBytes: 38283921137336466, usedPct: 6366.305226067051, 
 disable threshold: 0.85
 2013-07-15 11:15:28,317 DEBUG [cloud.storage.StorageManagerImpl] 
 (Job-Executor-3:job-168) Insufficient space on pool: 209 since its usage 
 percentage: 6366.305226067051 has crossed the 
 pool.storage.capacity.disablethreshold: 0.85
 2013-07-15 11:15:28,317 DEBUG 
 [storage.allocator.FirstFitStoragePoolAllocator] (Job-Executor-3:job-168) 
 FirstFitStoragePoolAllocator returning 1 suitable storage pools
 2013-07-15 11:15:28,317 DEBUG [cloud.deploy.FirstFitPlanner] 
 (Job-Executor-3:job-168) Checking suitable pools for volume (Id, Type): 
 (228,DATADISK)
 2013-07-15 11:15:28,317 DEBUG [cloud.deploy.FirstFitPlanner]