Comments on: Resource pools and avoiding HA slot sizing http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/ Thu, 17 May 2012 06:42:15 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: TBL Networks » Cisco Nexus 1000v and vSphere HA Slot Sizes http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/comment-page-1/#comment-845 TBL Networks » Cisco Nexus 1000v and vSphere HA Slot Sizes Fri, 20 Aug 2010 03:18:37 +0000 http://frankdenneman.nl/?p=720#comment-845 [...] http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/ [...] [...] http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/ [...]

]]> By: Virtualization Short Take #36 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/comment-page-1/#comment-351 Virtualization Short Take #36 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers Tue, 09 Mar 2010 15:05:27 +0000 http://frankdenneman.nl/?p=720#comment-351 [...] VCDX #029 Frank Denneman posted a good article on using reservations on resource pools to bypass slot sizing. As Frank points out, it’s not a recommended practice necessarily, but it might be warranted [...] [...] VCDX #029 Frank Denneman posted a good article on using reservations on resource pools to bypass slot sizing. As Frank points out, it’s not a recommended practice necessarily, but it might be warranted [...]

]]> By: Justin http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/comment-page-1/#comment-314 Justin Thu, 04 Mar 2010 14:43:33 +0000 http://frankdenneman.nl/?p=720#comment-314 I utilized this work around with the Cisco Nexus 1000v VSMs. The VSMs come configured with a memory reservation 2GB. With this reservation set, the number of available HA slots in 10 host cluster was very small. I created a resource pool with the necessary memory reservation and moved the VSMs in these resource pools. This solved my issue with the number of available slots in my HA cluster. I utilized this work around with the Cisco Nexus 1000v VSMs. The VSMs come configured with a memory reservation 2GB. With this reservation set, the number of available HA slots in 10 host cluster was very small. I created a resource pool with the necessary memory reservation and moved the VSMs in these resource pools. This solved my issue with the number of available slots in my HA cluster.

]]> By: Craig Stewart http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/comment-page-1/#comment-291 Craig Stewart Thu, 25 Feb 2010 09:45:54 +0000 http://frankdenneman.nl/?p=720#comment-291 Nice workaround Frank. Having just implemented a vSphere cluster we were having HA capacity issues as soon as setting a reservation for a VM. We didn't want to turn off strict admission control and I didn't want to mess with the advanced slot size settings for fear of causing slot fragmentation as mentioned in Duncan's deepdive. So it turns out I used a similar workaround to yourself, however I did this with groups of VM's as opposed to single VM's. So I created resource groups for DEV, UAT, Production, etc and placed VM's within these. The resource groups have reservations and limits, staggered in such a way that DEV is likely to have contention but production is not as it has been assigned more resources. Using shares within the resource group then allows us to prioritise what gets what in a contention scenario within the resource group. This model is working fine for us just now. If however I ever have to isolate a machine on it's own I would definately look to your workaround first before changing advanced slot settings or turning off strict admission control. Nice workaround Frank. Having just implemented a vSphere cluster we were having HA capacity issues as soon as setting a reservation for a VM. We didn’t want to turn off strict admission control and I didn’t want to mess with the advanced slot size settings for fear of causing slot fragmentation as mentioned in Duncan’s deepdive.

So it turns out I used a similar workaround to yourself, however I did this with groups of VM’s as opposed to single VM’s.

So I created resource groups for DEV, UAT, Production, etc and placed VM’s within these. The resource groups have reservations and limits, staggered in such a way that DEV is likely to have contention but production is not as it has been assigned more resources. Using shares within the resource group then allows us to prioritise what gets what in a contention scenario within the resource group. This model is working fine for us just now.

If however I ever have to isolate a machine on it’s own I would definately look to your workaround first before changing advanced slot settings or turning off strict admission control.

]]> By: Frank http://frankdenneman.nl/2010/02/resource-pools-and-avoiding-ha-slot-sizing/comment-page-1/#comment-290 Frank Thu, 25 Feb 2010 07:19:21 +0000 http://frankdenneman.nl/?p=720#comment-290 That is actually pretty cool. Never thought of that. Thanks for the info! That is actually pretty cool. Never thought of that. Thanks for the info!

]]>