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

Sangeetha Hariharan commented on CLOUDSTACK-5809:
-------------------------------------------------

There is another use case where we are not allowed to deploy Vms because of 
"Maximum number of resources of type 'primary_storage' for account 
name=test-TestParallelVolumeSnasohots-M2LYLO in domain id=1 has been exceeded."

Set up - Advanced zone set up with 2 Xenserver hosts.

The default value for 'primary_storage' is 200 gb for account.

I tried to deploy 11 user Vms using the default "CentOS 5.6" template which has 
virtual size = 20 GB and actual size=1.7 G.

Only 10 Vms get deployed. 

When I try to deploy another VM it fails because of "Maximum number of 
resources of type 'primary_storage' for account 
name=test-TestParallelVolumeSnasohots-M2LYLO in domain id=1 has been exceeded."

mysql> select * from resource_count where account_id=3
    -> ;
+----+------------+-----------+-------------------+--------------+
| id | account_id | domain_id | type              | count        |
+----+------------+-----------+-------------------+--------------+
| 41 |          3 |      NULL | user_vm           |           10 |
| 42 |          3 |      NULL | public_ip         |           11 |
| 43 |          3 |      NULL | volume            |           10 |
| 44 |          3 |      NULL | snapshot          |            0 |
| 45 |          3 |      NULL | template          |            0 |
| 46 |          3 |      NULL | project           |            0 |
| 47 |          3 |      NULL | network           |            1 |
| 48 |          3 |      NULL | vpc               |            0 |
| 49 |          3 |      NULL | cpu               |           10 |
| 50 |          3 |      NULL | memory            |         1280 |
| 51 |          3 |      NULL | primary_storage   | 214748364800 |
| 52 |          3 |      NULL | secondary_storage |            0 |
+----+------------+-----------+-------------------+--------------+
12 rows in set (0.00 sec)

Actual Space taken up on the primary:

[root@Rack3Host5 primary]# ls -lth
total 4.4G
-rw-r--r--. 1 root root 119M Jan 14 21:30 
af626686-9040-44f4-8c41-85d7e51407c9.vhd
-rw-r--r--. 1 root root 192M Jan 14 21:30 
f6a2debe-2989-497b-9cfd-801687d45df6.vhd
-rw-r--r--. 1 root root 195M Jan 14 21:30 
7641171e-0b2b-437b-b4c0-912f6230f45c.vhd
-rw-r--r--. 1 root root 115M Jan 14 21:30 
882d7487-af73-4bd1-93f4-28bd0ce8b053.vhd
-rw-r--r--. 1 root root 119M Jan 14 21:30 
330936b3-a0e7-42bc-91ee-d90e4caa0bf5.vhd
-rw-r--r--. 1 root root   11 Jan 14 21:30 
hb-78964203-a98f-4359-ac6c-923241ed838a
-rw-r--r--. 1 root root 119M Jan 14 21:30 
7f2aa352-3535-4504-a75c-3392b380fef0.vhd
-rw-r--r--. 1 root root 115M Jan 14 21:30 
a588f9ec-8f9c-4ff4-8c5a-fe426c041f74.vhd
-rw-r--r--. 1 root root 119M Jan 14 21:30 
0aa24cbb-7565-4d61-be1d-ca9dbb5e48f2.vhd
-rw-r--r--. 1 root root   11 Jan 14 21:30 
hb-419fed86-8a7f-4a2a-9d29-cae55fa9232d
-rw-r--r--. 1 root root 119M Jan 14 21:30 
92f7aef7-2f69-43cf-8fb1-447a630c381b.vhd
-rw-r--r--. 1 root root 118M Jan 14 21:30 
bcc373e4-df48-41b4-99e6-1a50da63019d.vhd
-rw-r--r--. 1 root root 119M Jan 14 21:30 
2acdb609-a6b4-4997-84a8-f9664c0377ad.vhd
-rw-r--r--. 1 root root 121M Jan 14 21:30 
b4ee0eaa-78e0-473c-8642-acf8a64aa267.vhd
-rw-r--r--. 1 root root  93M Jan 14 21:30 
c26d3c46-80d1-4284-b23e-911939f0431e.vhd
-rw-r--r--. 1 root root  46K Jan 14 20:53 
a36b2afa-a588-43f6-9bd6-62f665a27397.vhd
-rw-r--r--. 1 root root 7.3K Jan 14 20:53 filelog.txt
-rw-r--r--. 1 root root 1.7G Jan 14 20:48 
63959b05-1e9b-41b5-a7a8-7ad691ce706a.vhd
-rw-r--r--. 1 root root 9.5K Jan 14 20:46 
3b872148-72f9-4426-8faa-b38c1fbaac8c.vhd
-rw-r--r--. 1 root root 2.5G Jan 14 19:38 
8226938d-a816-47c1-8545-cae1f8a9ccba.vhd




> Not able to deploy Vm becasue of crossing pool.storage.allocate 
> d.capacity.disablethreshold even though the threshold has not been reached in 
> the primary store.
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-5809
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5809
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the 
> default.) 
>          Components: Management Server
>    Affects Versions: 4.3.0
>         Environment: Build from 4.3
>            Reporter: Sangeetha Hariharan
>             Fix For: 4.3.0
>
>
> Not able to deploy Vm because of crossing pool.storage.allocate 
> d.capacity.disablethreshold even though the threshold has not been reached in 
> the primary store.
> Steps to reproduce the problem:
> Xenserver set up with 2 Xensserver hosts:
> In my case , Primary storage NFS has 222GB . (storage.overprovisioning.factor 
> is set to 2).
> I tried to deploy 20 Vms with the same template that has Virtual size of 
> 20.00 GB and actual size is about 10 GB. 
> I was allowed to deploy only 17 Vms after which Vm deployment fails because 
> of the following exception because of crossing pool.storage.allocate 
> d.capacity.disablethreshold :
> 2014-01-06 17:34:21,881 DEBUG [c.c.s.StorageManagerImpl] 
> (Job-Executor-32:ctx-2a944d7f ctx-6e9eaab0) Checking pool 1 for storage, 
> totalSize: 2
> 37777190912, usedBytes: 88645566464, usedPct: 0.3728093772325169, disable 
> threshold: 0.85
> 2014-01-06 17:34:21,885 DEBUG [c.c.s.StorageManagerImpl] 
> (Job-Executor-32:ctx-2a944d7f ctx-6e9eaab0) Checking pool: 1 for volume 
> allocation [V
> ol[24|vm=24|ROOT]], maxSize : 475554381824, totalAllocatedSize : 
> 394411376640, askingSize : 21474836480, allocated disable threshold: 0.85
> 2014-01-06 17:34:21,886 DEBUG [c.c.s.StorageManagerImpl] 
> (Job-Executor-32:ctx-2a944d7f ctx-6e9eaab0) Insufficient un-allocated 
> capacity on: 1
> for volume allocation: [Vol[24|vm=24|ROOT]] since its allocated percentage: 
> 0.8745292421128761 has crossed the allocated pool.storage.allocate
> d.capacity.disablethreshold: 0.85, skipping this pool
> Since Xenserver uses thin provisioning ,  the base copy of the template in 
> primary is 10 GB. All the vhd entries of the Vms are very small and point to 
> the base copy. We need to allocate only 10 GB space ( 20 GB (virtual size of 
> template) - 10 gb ( actual size of tenplate)  for each of these Vms , in 
> addition to 10 GB for the base template copy.
> But we are allocating 20 GB for each of the Vms deployed.
> Reported Primary Storage capacity - 82 % - 367.32 GB / 442.89 GB



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to