RE: VMWare storage overprovisioning

2014-01-09 Thread François Bousquet 
Hello Nitin,

What is the purpose of overprovisioning if we cannot deploy a server when 
allocated storage is over pool.storage.allocated.capacity.disablethreshold 
reguardless of storage.overprovisioning.factor ?

The way I understand and experience it with my CloudStack 4.1.1 setup, I cannot 
exceed 100% on allocated space even if my overprovisioning factor is more than 
1.

Can you please clarify how this is supposed to work?

Thanks

François




-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, October 24, 2013 13:13
To: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning



On 24/10/13 1:22 AM, Noel King noelk...@gmail.com wrote:

Hi

Thanks for this have reverted it back to .85, does this mean that this
value pool.storage.capacity.disablethreshold is factoring in the
overprovisioning value?

No. It is the real usage of the disk equivalent of df -h.


Is there a way to allow
pool.storage.allocated.capacity.disablethreshold
utilise the overprovisining factor and stop blocking VM creation when
we reach the 85% threshold

Nope. Do read
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Understanding+Dashbo
ard
To understand allocated and real usage that CS captures


Thanks
Noel


On 24 October 2013 01:32, Nitin Mehta nitin.me...@citrix.com wrote:

 Advise you to not keep pool.storage.capacity.disablethreshold as 1
(100%).
 This captures the actual usage of the storage and you do not want it to
 reach 100% especially possible when you have over provisioned.

 On 23/10/13 1:14 PM, Noel King noelk...@gmail.com wrote:

 Hi
 
 I am seeing an issue here with Cloudstack and VMWare storage and hope
you
 can help.  VMWare is using dynamic storage so for a template of 20GB in
 reality only 3GB is being used, VMWare currently has the size of the
VM of
 3GB and increases storage allocation to the VM as it requires it.
However
 Cloudstack thinks 20GB has been consumed
 
 So to overcome this we set
 
 storage.overprovisioning.factor to 5
 
 But we still had issues when we hit 85% (which is not 85% based on
VMWare
 storage allocation).  The following values were set to .85 and
increasing
 these has offered little benefit up to 100%
 
 
- pool.storage.capacity.disablethreshold
- pool.storage.allocated.capacity.disablethreshold
 
 
 Any advise on other settings on Cloudstack 4.1.1 that could help us.
 
 Kind regards
 
 Noel



*** This 
e-mail and attachments are confidential, legally privileged, may be subject to 
copyright and sent solely for the attention of the addressee(s). Any 
unauthorized use or disclosure is prohibited. Statements and opinions expressed 
in this e-mail may not represent those of Radialpoint. 
~~ Le contenu du présent 
courriel est confidentiel, privilégié et peut être soumis à des droits 
d'auteur. Il est envoyé à l'intention exclusive de son ou de ses destinataires. 
Il est interdit de l'utiliser ou de le divulguer sans autorisation. Les 
opinions exprimées dans le présent courriel peuvent diverger de celles de 
Radialpoint.

Re: VMWare storage overprovisioning

2014-01-09 Thread Nitin Mehta 
When you increase the factor, the allocated percentage decreases and hence
you can fit in more vms.

Say allocated = 100% = 100gb out of 100gb total space and overprovisioning
factor = 2 and at this moment you can't deploy more vms.
Say you change overprovisioning to 3 and allocated now becomes = 100/150 =
67%, so you can fit more vms.


Thanks,
-Nitin

On 09/01/14 7:59 AM, François Bousquet
francois.bousq...@radialpoint.com wrote:

Hello Nitin,

What is the purpose of overprovisioning if we cannot deploy a server when
allocated storage is over
pool.storage.allocated.capacity.disablethreshold reguardless of
storage.overprovisioning.factor ?

The way I understand and experience it with my CloudStack 4.1.1 setup, I
cannot exceed 100% on allocated space even if my overprovisioning factor
is more than 1.

Can you please clarify how this is supposed to work?

Thanks

François




-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, October 24, 2013 13:13
To: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning



On 24/10/13 1:22 AM, Noel King noelk...@gmail.com wrote:

Hi

Thanks for this have reverted it back to .85, does this mean that this
value pool.storage.capacity.disablethreshold is factoring in the
overprovisioning value?

No. It is the real usage of the disk equivalent of df -h.


Is there a way to allow
pool.storage.allocated.capacity.disablethreshold
utilise the overprovisining factor and stop blocking VM creation when
we reach the 85% threshold

Nope. Do read
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Understanding+Dashb
o
ard
To understand allocated and real usage that CS captures


Thanks
Noel


On 24 October 2013 01:32, Nitin Mehta nitin.me...@citrix.com wrote:

 Advise you to not keep pool.storage.capacity.disablethreshold as 1
(100%).
 This captures the actual usage of the storage and you do not want it to
 reach 100% especially possible when you have over provisioned.

 On 23/10/13 1:14 PM, Noel King noelk...@gmail.com wrote:

 Hi
 
 I am seeing an issue here with Cloudstack and VMWare storage and hope
you
 can help.  VMWare is using dynamic storage so for a template of 20GB
in
 reality only 3GB is being used, VMWare currently has the size of the
VM of
 3GB and increases storage allocation to the VM as it requires it.
However
 Cloudstack thinks 20GB has been consumed
 
 So to overcome this we set
 
 storage.overprovisioning.factor to 5
 
 But we still had issues when we hit 85% (which is not 85% based on
VMWare
 storage allocation).  The following values were set to .85 and
increasing
 these has offered little benefit up to 100%
 
 
- pool.storage.capacity.disablethreshold
- pool.storage.allocated.capacity.disablethreshold
 
 
 Any advise on other settings on Cloudstack 4.1.1 that could help us.
 
 Kind regards
 
 Noel



***
This e-mail and attachments are confidential, legally privileged, may be
subject to copyright and sent solely for the attention of the
addressee(s). Any unauthorized use or disclosure is prohibited.
Statements and opinions expressed in this e-mail may not represent those
of Radialpoint. ~~ Le
contenu du présent courriel est confidentiel, privilégié et peut être
soumis à des droits d'auteur. Il est envoyé à l'intention exclusive de
son ou de ses destinataires. Il est interdit de l'utiliser ou de le
divulguer sans autorisation. Les opinions exprimées dans le présent
courriel peuvent diverger de celles de Radialpoint.

RE: VMWare storage overprovisioning

2014-01-09 Thread François Bousquet 
To whatever value I set storage.overprovisioning.factor I reach a point where I 
can no longer deploy because of 
pool.storage.allocated.capacity.disablethreshold (even if it is set to the 
highest value: 1).

See my current capacity:

 list capacity
count = 10
capacity:
+---+---+-+--+--+--+
|  capacityused | capacitytotal | percentused |zoneid   
 | type | zonename |
+---+---+-+--+--+--+
|  163879845888 |  412184322048 |39.76| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  0   |  YUL03   |
| 99500 | 210600|47.25| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  1   |  YUL03   |
| 6021762252800 | 6026644422656 |99.92| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  3   |  YUL03   |
|   5   |  245  | 2.04| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  4   |  YUL03   |
|   17  |  181  | 9.39| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  5   |  YUL03   |
|   3   |  100  |  3  | 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  7   |  YUL03   |
|  123  |  2281 | 5.39| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  8   |  YUL03   |
|   1931476992  |  42949672960  | 4.5 | 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  9   |  YUL03   |
|  223942279168 | 4329031335936 | 5.17| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  6   |  YUL03   |
| 1590080569344 | 6069594095616 | 26.2| 
4ee38c78-482d-4a0e-bba7-1079f54e772b |  2   |  YUL03   |
+---+---+-+--+--+--+

6026644422656 (~6 TB) is my real capacity but only (~1.59 TB) are being used 
(type=2) however, the allocated space (here at 99.92%) is not changed by the 
overprovisioning factor (currently at 4).

The result is I cannot allocate more space than I have, even with 
overprovisioning factor set higher than 1.

This is CloudStack 4.1.1.

Is this a normal behavior?

Thanks for your input.

François



-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, January 09, 2014 13:27
To: François Bousquet
Cc: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning

When you increase the factor, the allocated percentage decreases and hence you 
can fit in more vms.

Say allocated = 100% = 100gb out of 100gb total space and overprovisioning 
factor = 2 and at this moment you can't deploy more vms.
Say you change overprovisioning to 3 and allocated now becomes = 100/150 = 67%, 
so you can fit more vms.


Thanks,
-Nitin

On 09/01/14 7:59 AM, François Bousquet
francois.bousq...@radialpoint.com wrote:

Hello Nitin,

What is the purpose of overprovisioning if we cannot deploy a server
when allocated storage is over
pool.storage.allocated.capacity.disablethreshold reguardless of
storage.overprovisioning.factor ?

The way I understand and experience it with my CloudStack 4.1.1 setup,
I cannot exceed 100% on allocated space even if my overprovisioning
factor is more than 1.

Can you please clarify how this is supposed to work?

Thanks

François




-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, October 24, 2013 13:13
To: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning



On 24/10/13 1:22 AM, Noel King noelk...@gmail.com wrote:

Hi

Thanks for this have reverted it back to .85, does this mean that this
value pool.storage.capacity.disablethreshold is factoring in the
overprovisioning value?

No. It is the real usage of the disk equivalent of df -h.


Is there a way to allow
pool.storage.allocated.capacity.disablethreshold
utilise the overprovisining factor and stop blocking VM creation when
we reach the 85% threshold

Nope. Do read
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Understanding+Da
shb
o
ard
To understand allocated and real usage that CS captures


Thanks
Noel


On 24 October 2013 01:32, Nitin Mehta nitin.me...@citrix.com wrote:

 Advise you to not keep pool.storage.capacity.disablethreshold as 1
(100%).
 This captures the actual usage of the storage and you do not want it
to  reach 100% especially possible when you have over provisioned.

 On 23/10/13 1:14 PM, Noel King noelk...@gmail.com wrote:

 Hi
 
 I am seeing an issue here with Cloudstack and VMWare storage and
 hope
you
 can help.  VMWare is using dynamic storage so for a template of
 20GB
in
 reality only 3GB is being used, VMWare currently has the size of
 the
VM of
 3GB and increases storage allocation to the VM as it requires it.
However
 Cloudstack thinks 20GB has been consumed
 
 So to overcome this we set
 
 storage.overprovisioning.factor to 5
 
 But we still had issues when we hit 85% (which is not 85% based on
VMWare
 storage allocation).  The following values were set to .85 and
increasing

Re: VMWare storage overprovisioning

2014-01-09 Thread Nitin Mehta 
Storage overprovisioning in CS is enabled for NFS and VMFS only. If its
not chaining the allocated space I assume that you aren't using NFS/VMFS
else its a bug.


Thanks,
-Nitin

On 09/01/14 1:14 PM, François Bousquet
francois.bousq...@radialpoint.com wrote:

To whatever value I set storage.overprovisioning.factor I reach a point
where I can no longer deploy because of
pool.storage.allocated.capacity.disablethreshold (even if it is set to
the highest value: 1).

See my current capacity:

 list capacity
count = 10
capacity:
+---+---+-+---
---+--+--+
|  capacityused | capacitytotal | percentused |zoneid
   | type | zonename |
+---+---+-+---
---+--+--+
|  163879845888 |  412184322048 |39.76|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  0   |  YUL03   |
| 99500 | 210600|47.25|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  1   |  YUL03   |
| 6021762252800 | 6026644422656 |99.92|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  3   |  YUL03   |
|   5   |  245  | 2.04|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  4   |  YUL03   |
|   17  |  181  | 9.39|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  5   |  YUL03   |
|   3   |  100  |  3  |
4ee38c78-482d-4a0e-bba7-1079f54e772b |  7   |  YUL03   |
|  123  |  2281 | 5.39|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  8   |  YUL03   |
|   1931476992  |  42949672960  | 4.5 |
4ee38c78-482d-4a0e-bba7-1079f54e772b |  9   |  YUL03   |
|  223942279168 | 4329031335936 | 5.17|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  6   |  YUL03   |
| 1590080569344 | 6069594095616 | 26.2|
4ee38c78-482d-4a0e-bba7-1079f54e772b |  2   |  YUL03   |
+---+---+-+---
---+--+--+

6026644422656 (~6 TB) is my real capacity but only (~1.59 TB) are being
used (type=2) however, the allocated space (here at 99.92%) is not
changed by the overprovisioning factor (currently at 4).

The result is I cannot allocate more space than I have, even with
overprovisioning factor set higher than 1.

This is CloudStack 4.1.1.

Is this a normal behavior?

Thanks for your input.

François



-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, January 09, 2014 13:27
To: François Bousquet
Cc: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning

When you increase the factor, the allocated percentage decreases and
hence you can fit in more vms.

Say allocated = 100% = 100gb out of 100gb total space and
overprovisioning factor = 2 and at this moment you can't deploy more vms.
Say you change overprovisioning to 3 and allocated now becomes = 100/150
= 67%, so you can fit more vms.


Thanks,
-Nitin

On 09/01/14 7:59 AM, François Bousquet
francois.bousq...@radialpoint.com wrote:

Hello Nitin,

What is the purpose of overprovisioning if we cannot deploy a server
when allocated storage is over
pool.storage.allocated.capacity.disablethreshold reguardless of
storage.overprovisioning.factor ?

The way I understand and experience it with my CloudStack 4.1.1 setup,
I cannot exceed 100% on allocated space even if my overprovisioning
factor is more than 1.

Can you please clarify how this is supposed to work?

Thanks

François




-Original Message-
From: Nitin Mehta [mailto:nitin.me...@citrix.com]
Sent: Thursday, October 24, 2013 13:13
To: users@cloudstack.apache.org
Subject: Re: VMWare storage overprovisioning



On 24/10/13 1:22 AM, Noel King noelk...@gmail.com wrote:

Hi

Thanks for this have reverted it back to .85, does this mean that this
value pool.storage.capacity.disablethreshold is factoring in the
overprovisioning value?

No. It is the real usage of the disk equivalent of df -h.


Is there a way to allow
pool.storage.allocated.capacity.disablethreshold
utilise the overprovisining factor and stop blocking VM creation when
we reach the 85% threshold

Nope. Do read
https://cwiki.apache.org/confluence/display/CLOUDSTACK/Understanding+Da
shb
o
ard
To understand allocated and real usage that CS captures


Thanks
Noel


On 24 October 2013 01:32, Nitin Mehta nitin.me...@citrix.com wrote:

 Advise you to not keep pool.storage.capacity.disablethreshold as 1
(100%).
 This captures the actual usage of the storage and you do not want it
to  reach 100% especially possible when you have over provisioned.

 On 23/10/13 1:14 PM, Noel King noelk...@gmail.com wrote:

 Hi
 
 I am seeing an issue here with Cloudstack and VMWare storage and
 hope
you
 can help.  VMWare is using dynamic storage so for a template of
 20GB
in
 reality only 3GB is being used, VMWare currently has the size of
 the
VM of
 3GB and increases storage allocation to the VM as it requires it.
However
 Cloudstack thinks 20GB has

Re: VMWare storage overprovisioning

2013-10-24 Thread Noel King 
Hi

Thanks for this have reverted it back to .85, does this mean that this
value pool.storage.capacity.disablethreshold is factoring in the
overprovisioning value?

Is there a way to allow pool.storage.allocated.capacity.disablethreshold
utilise the overprovisining factor and stop blocking VM creation when we
reach the 85% threshold

Thanks
Noel


On 24 October 2013 01:32, Nitin Mehta nitin.me...@citrix.com wrote:

 Advise you to not keep pool.storage.capacity.disablethreshold as 1 (100%).
 This captures the actual usage of the storage and you do not want it to
 reach 100% especially possible when you have over provisioned.

 On 23/10/13 1:14 PM, Noel King noelk...@gmail.com wrote:

 Hi
 
 I am seeing an issue here with Cloudstack and VMWare storage and hope you
 can help.  VMWare is using dynamic storage so for a template of 20GB in
 reality only 3GB is being used, VMWare currently has the size of the VM of
 3GB and increases storage allocation to the VM as it requires it.  However
 Cloudstack thinks 20GB has been consumed
 
 So to overcome this we set
 
 storage.overprovisioning.factor to 5
 
 But we still had issues when we hit 85% (which is not 85% based on VMWare
 storage allocation).  The following values were set to .85 and increasing
 these has offered little benefit up to 100%
 
 
- pool.storage.capacity.disablethreshold
- pool.storage.allocated.capacity.disablethreshold
 
 
 Any advise on other settings on Cloudstack 4.1.1 that could help us.
 
 Kind regards
 
 Noel

VMWare storage overprovisioning

2013-10-23 Thread Noel King 
Hi

I am seeing an issue here with Cloudstack and VMWare storage and hope you
can help.  VMWare is using dynamic storage so for a template of 20GB in
reality only 3GB is being used, VMWare currently has the size of the VM of
3GB and increases storage allocation to the VM as it requires it.  However
Cloudstack thinks 20GB has been consumed

So to overcome this we set

storage.overprovisioning.factor to 5

But we still had issues when we hit 85% (which is not 85% based on VMWare
storage allocation).  The following values were set to .85 and increasing
these has offered little benefit up to 100%


   - pool.storage.capacity.disablethreshold
   - pool.storage.allocated.capacity.disablethreshold


Any advise on other settings on Cloudstack 4.1.1 that could help us.

Kind regards

Noel

Re: VMWare storage overprovisioning

2013-10-23 Thread Nitin Mehta 
Advise you to not keep pool.storage.capacity.disablethreshold as 1 (100%).
This captures the actual usage of the storage and you do not want it to
reach 100% especially possible when you have over provisioned.

On 23/10/13 1:14 PM, Noel King noelk...@gmail.com wrote:

Hi

I am seeing an issue here with Cloudstack and VMWare storage and hope you
can help.  VMWare is using dynamic storage so for a template of 20GB in
reality only 3GB is being used, VMWare currently has the size of the VM of
3GB and increases storage allocation to the VM as it requires it.  However
Cloudstack thinks 20GB has been consumed

So to overcome this we set

storage.overprovisioning.factor to 5

But we still had issues when we hit 85% (which is not 85% based on VMWare
storage allocation).  The following values were set to .85 and increasing
these has offered little benefit up to 100%


   - pool.storage.capacity.disablethreshold
   - pool.storage.allocated.capacity.disablethreshold


Any advise on other settings on Cloudstack 4.1.1 that could help us.

Kind regards

Noel