<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: [Gestalt] vBlock, great product, just not for you</title>
	<atom:link href="http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/</link>
	<description>Your P.I. on virtualization</description>
	<lastBuildDate>Tue, 07 Feb 2012 11:19:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Top 5 Planet V12n blog posts week 15 &#124; Download VDI Solutions</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-1232</link>
		<dc:creator>Top 5 Planet V12n blog posts week 15 &#124; Download VDI Solutions</dc:creator>
		<pubDate>Mon, 25 Oct 2010 18:41:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-1232</guid>
		<description>[...] van Zanten &#8211; [Gestalt] vBlock, great product, just not for youWhat I don’t understand though is where the bottleneck is in a Vblock type 1 to use only 48GB? [...]</description>
		<content:encoded><![CDATA[<p>[...] van Zanten &#8211; [Gestalt] vBlock, great product, just not for youWhat I don’t understand though is where the bottleneck is in a Vblock type 1 to use only 48GB? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My take on the stack wars &#8211; Gestalt IT</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-888</link>
		<dc:creator>My take on the stack wars &#8211; Gestalt IT</dc:creator>
		<pubDate>Tue, 27 Apr 2010 20:33:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-888</guid>
		<description>[...] there is one major problem, and that is flexibility. One of the bigger concerns came up during the Gestalt IT tech field day vBlock session at Cisco. With the vBlock, I have a fixed configuration and it will run smoothly and within certain [...]</description>
		<content:encoded><![CDATA[<p>[...] there is one major problem, and that is flexibility. One of the bigger concerns came up during the Gestalt IT tech field day vBlock session at Cisco. With the vBlock, I have a fixed configuration and it will run smoothly and within certain [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: My take on the stack wars &#171; BasRaayman&#39;s technical diatribe</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-887</link>
		<dc:creator>My take on the stack wars &#171; BasRaayman&#39;s technical diatribe</dc:creator>
		<pubDate>Mon, 26 Apr 2010 09:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-887</guid>
		<description>[...] there is one major problem, and that is flexibility. One of the bigger concerns came up during the Gestalt IT tech field day vBlock session at Cisco. With the vBlock, I have a fixed configuration and it will run smoothly and within certain [...]</description>
		<content:encoded><![CDATA[<p>[...] there is one major problem, and that is flexibility. One of the bigger concerns came up during the Gestalt IT tech field day vBlock session at Cisco. With the vBlock, I have a fixed configuration and it will run smoothly and within certain [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Geerlings</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-886</link>
		<dc:creator>Paul Geerlings</dc:creator>
		<pubDate>Fri, 23 Apr 2010 19:23:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-886</guid>
		<description>First of all i would like to say that I like the concept of VCE Vblocks and i can see its potential.&lt;br&gt;Customers want simplicity in their support, they absolutly hate it when their suppliers point at each other in case of problems.&lt;br&gt;&lt;br&gt;Second, i can understand Duncan&#039;s remarks on the vSphere design part.&lt;br&gt;&lt;br&gt;It looks like the &quot;V&quot; part in VCE initiative is a bit underexposed, or at least it was when designing the Vblock 1 minimum config. The Vblock 1 minimum UCS Configuration offers only 2 chassis with blades, which, imho, is similar to offering a storage array with only the possibility to support Raid 0 or 1 (just a little comparisson to appeal to the EMC guys).&lt;br&gt;&lt;br&gt;So on that part of the configuration it does not look like VMware was in the drivers seat, which is not tobe expected when you are in a threesome with Giants like EMC and Cisco. Allthough.. looking at the blade configuration there must have been an idea behind this, why else would one choose for the chassis configuration with 6x48GB RAM blades and 2x96GB RAM blades...? I can&#039;t imagine that it was done to provide an entry level vblock :-) Can anyone shed some light on this ?&lt;br&gt;&lt;br&gt;Furthermore i am missing the numbers on IOPS, how can they say &quot;we support a 1000 vms in our vblock X&quot; when they don&#039;t know what is running in the VMs? I found that there is a so-called &quot;Vblock validated Applications list&quot; but that still doesnot say much about the load.&lt;br&gt;&lt;br&gt;To the Author, Gabe, thanx for sharing the Vblock story.&lt;br&gt;One remark about the table, shouldn&#039;t the RAM size of the vblock 1 minimum UCS configuration be 960GB instead of 480GB? &lt;br&gt;I also have a remark on the Bottleneck you describe, the last paragraph about the vCenter cluster design, I think when &lt;br&gt;you have only two chassis you should always span your vSphere cluster(s) across both the chassis. Building a vSphere cluster inside one chassis is comparable to using Raid 0 in a storage array (but without the speed advantage :-)). Another thing is, if you build your cluster in one chassis the fysical placement of your HA primary is the least of your worries, in fact its not one at all.</description>
		<content:encoded><![CDATA[<p>First of all i would like to say that I like the concept of VCE Vblocks and i can see its potential.<br />Customers want simplicity in their support, they absolutly hate it when their suppliers point at each other in case of problems.</p>
<p>Second, i can understand Duncan&#39;s remarks on the vSphere design part.</p>
<p>It looks like the &#8220;V&#8221; part in VCE initiative is a bit underexposed, or at least it was when designing the Vblock 1 minimum config. The Vblock 1 minimum UCS Configuration offers only 2 chassis with blades, which, imho, is similar to offering a storage array with only the possibility to support Raid 0 or 1 (just a little comparisson to appeal to the EMC guys).</p>
<p>So on that part of the configuration it does not look like VMware was in the drivers seat, which is not tobe expected when you are in a threesome with Giants like EMC and Cisco. Allthough.. looking at the blade configuration there must have been an idea behind this, why else would one choose for the chassis configuration with 6x48GB RAM blades and 2x96GB RAM blades&#8230;? I can&#39;t imagine that it was done to provide an entry level vblock <img src='http://www.gabesvirtualworld.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' />  Can anyone shed some light on this ?</p>
<p>Furthermore i am missing the numbers on IOPS, how can they say &#8220;we support a 1000 vms in our vblock X&#8221; when they don&#39;t know what is running in the VMs? I found that there is a so-called &#8220;Vblock validated Applications list&#8221; but that still doesnot say much about the load.</p>
<p>To the Author, Gabe, thanx for sharing the Vblock story.<br />One remark about the table, shouldn&#39;t the RAM size of the vblock 1 minimum UCS configuration be 960GB instead of 480GB? <br />I also have a remark on the Bottleneck you describe, the last paragraph about the vCenter cluster design, I think when <br />you have only two chassis you should always span your vSphere cluster(s) across both the chassis. Building a vSphere cluster inside one chassis is comparable to using Raid 0 in a storage array (but without the speed advantage <img src='http://www.gabesvirtualworld.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> ). Another thing is, if you build your cluster in one chassis the fysical placement of your HA primary is the least of your worries, in fact its not one at all.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Top 5 Planet V12n blog posts week 15 &#124; VMvisor</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-883</link>
		<dc:creator>Top 5 Planet V12n blog posts week 15 &#124; VMvisor</dc:creator>
		<pubDate>Mon, 19 Apr 2010 12:34:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-883</guid>
		<description>[...] van Zanten &#8211; [Gestalt] vBlock, great product, just not for youWhat I donâ€™t understand though is where the bottleneck is in a Vblock type 1 to use only 48GB? [...]</description>
		<content:encoded><![CDATA[<p>[...] van Zanten &#8211; [Gestalt] vBlock, great product, just not for youWhat I donâ€™t understand though is where the bottleneck is in a Vblock type 1 to use only 48GB? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Scott Lowe</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-881</link>
		<dc:creator>Scott Lowe</dc:creator>
		<pubDate>Sat, 17 Apr 2010 01:34:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-881</guid>
		<description>All, I&#039;ve spoken with a couple members of the Vblock product team and I have some additional information to share.&lt;br&gt;&lt;br&gt;First, with regard to the Cisco VIC (aka &quot;Palo&quot;)--it is available today on the Vblock BoM. The Cisco UCS M2 blades (with the Intel &quot;Westmere&quot; processors) are on the exception list and in the process of being validated by Vblock product engineering. This means that you *can* get Cisco VIC and Westmere in Vblock configurations and have it officially supported as a Vblock.&lt;br&gt;&lt;br&gt;As for the design recommendations for running VMware vSphere on a Vblock (especially a Type 1, where the RAM difference in the blades seems to be a point of contention) I am working with Vblock product management to make that information available. I will post something on my site as soon as that information is available. I can&#039;t make any promises with regard to timelines, but rest assured that I will make it available as quickly as humanly possible.&lt;br&gt;&lt;br&gt;Thanks to everyone for their outstanding comments--I know that the VCE Coalition and the Vblock product management teams are keen to hear your feedback.</description>
		<content:encoded><![CDATA[<p>All, I&#39;ve spoken with a couple members of the Vblock product team and I have some additional information to share.</p>
<p>First, with regard to the Cisco VIC (aka &#8220;Palo&#8221;)&#8211;it is available today on the Vblock BoM. The Cisco UCS M2 blades (with the Intel &#8220;Westmere&#8221; processors) are on the exception list and in the process of being validated by Vblock product engineering. This means that you *can* get Cisco VIC and Westmere in Vblock configurations and have it officially supported as a Vblock.</p>
<p>As for the design recommendations for running VMware vSphere on a Vblock (especially a Type 1, where the RAM difference in the blades seems to be a point of contention) I am working with Vblock product management to make that information available. I will post something on my site as soon as that information is available. I can&#39;t make any promises with regard to timelines, but rest assured that I will make it available as quickly as humanly possible.</p>
<p>Thanks to everyone for their outstanding comments&#8211;I know that the VCE Coalition and the Vblock product management teams are keen to hear your feedback.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Louw Pretorius</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-880</link>
		<dc:creator>Louw Pretorius</dc:creator>
		<pubDate>Fri, 16 Apr 2010 15:17:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-880</guid>
		<description>I agree with the technical deficiencies of the vBlock design and that it is a product that sells to Executives.  &lt;br&gt;&lt;br&gt;1. I think that what the VCE alliance might be doing is to start lego-style vBlock components - as they stated  - to later easier integrate with the Cloud and to automate the whole cloud-idea and to facilitate long-term planning especially with a view to &quot;auto-cloud&quot; your infrastructure.  &lt;br&gt;&lt;br&gt;2. Imagine the next stage: mini-vBlocks bought for the VMware-GO initiative that auto-moves vm&#039;s from the web to your datacenter and no configuration is needed - it&#039;s all done from VMware-GO - hence auto-Cloud&lt;br&gt;&lt;br&gt;3. Imagine the next stage: branch-vBlocks with build-in WAN-optimization and View-clients - again, auto-configured from web-based shopping list&lt;br&gt;&lt;br&gt;4. Imagine the next stage: vBlocks with built-in email functionality - also auto-provisioned from your GO-shopping webpage.  &lt;br&gt;&lt;br&gt;I think it&#039;s an imaginative and long-view initiative - i would think 5-7 yrs&lt;br&gt;&lt;br&gt;My 2c&lt;br&gt;Louw Pretorius</description>
		<content:encoded><![CDATA[<p>I agree with the technical deficiencies of the vBlock design and that it is a product that sells to Executives.  </p>
<p>1. I think that what the VCE alliance might be doing is to start lego-style vBlock components &#8211; as they stated  &#8211; to later easier integrate with the Cloud and to automate the whole cloud-idea and to facilitate long-term planning especially with a view to &#8220;auto-cloud&#8221; your infrastructure.  </p>
<p>2. Imagine the next stage: mini-vBlocks bought for the VMware-GO initiative that auto-moves vm&#39;s from the web to your datacenter and no configuration is needed &#8211; it&#39;s all done from VMware-GO &#8211; hence auto-Cloud</p>
<p>3. Imagine the next stage: branch-vBlocks with build-in WAN-optimization and View-clients &#8211; again, auto-configured from web-based shopping list</p>
<p>4. Imagine the next stage: vBlocks with built-in email functionality &#8211; also auto-provisioned from your GO-shopping webpage.  </p>
<p>I think it&#39;s an imaginative and long-view initiative &#8211; i would think 5-7 yrs</p>
<p>My 2c<br />Louw Pretorius</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: The Case for the Vblock &#171; Jason Nash&#8217;s Blog</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-879</link>
		<dc:creator>The Case for the Vblock &#171; Jason Nash&#8217;s Blog</dc:creator>
		<pubDate>Fri, 16 Apr 2010 01:14:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-879</guid>
		<description>[...] 15, 2010 by nashwj    Yesterday there was a very good debate on Twitter and here about what a Vblock is, and more importantly, what it isn&#8217;t. Lately I&#8217;ve been so busy I [...]</description>
		<content:encoded><![CDATA[<p>[...] 15, 2010 by nashwj    Yesterday there was a very good debate on Twitter and here about what a Vblock is, and more importantly, what it isn&#8217;t. Lately I&#8217;ve been so busy I [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Etherealmind</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-877</link>
		<dc:creator>Etherealmind</dc:creator>
		<pubDate>Thu, 15 Apr 2010 10:48:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-877</guid>
		<description>When the workload is unknown, we would do what we always do, buy more than we need. In the case of vBlock, that means just buying more memory, more spindles or more CPU&#039;s. However, the minimum and maximum parameters have been laid out for hte platform. &lt;br&gt;&lt;br&gt;Compare this with your current systems, which have been purchased bit by bit and each one &quot;tested&quot; in the live environment before buying the next piece.&lt;br&gt;&lt;br&gt;I think VCE is trying to change the way you purchase equipment. Buy one big lump of hardware that will provide your IT for say 1 year ( or two or three) and then run it. Buy more blades, buy more memory, buy more spindles as you need. Then plan for another big purchase when next years budget is approved. &lt;br&gt;&lt;br&gt;VCE is a marketing / business topic, not a technical topic. For me, it&#039;s solves the problem of raising hundreds of purchase orders in a year and all of the those approvals and budgets.</description>
		<content:encoded><![CDATA[<p>When the workload is unknown, we would do what we always do, buy more than we need. In the case of vBlock, that means just buying more memory, more spindles or more CPU&#39;s. However, the minimum and maximum parameters have been laid out for hte platform. </p>
<p>Compare this with your current systems, which have been purchased bit by bit and each one &#8220;tested&#8221; in the live environment before buying the next piece.</p>
<p>I think VCE is trying to change the way you purchase equipment. Buy one big lump of hardware that will provide your IT for say 1 year ( or two or three) and then run it. Buy more blades, buy more memory, buy more spindles as you need. Then plan for another big purchase when next years budget is approved. </p>
<p>VCE is a marketing / business topic, not a technical topic. For me, it&#39;s solves the problem of raising hundreds of purchase orders in a year and all of the those approvals and budgets.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: andriven</title>
		<link>http://www.gabesvirtualworld.com/gestalt-vblock-great-product-just-not-for-you/#comment-876</link>
		<dc:creator>andriven</dc:creator>
		<pubDate>Thu, 15 Apr 2010 09:16:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.gabesvirtualworld.com/?p=1121#comment-876</guid>
		<description>Aaron&#039;s comment sums up my thoughts precisely -- I make my living giving guarantees based on technical data (to put it a very high level). I need to understand the architecture if I&#039;m going to put my neck on the line with a customer-facing recommendation (I&#039;m actually in the middle of a painful experience here with one of the VCE companies actually -- what&#039;s stated in documentation and was presented to the customer is not actually functional as promised now that we&#039;re into final implementation phases).</description>
		<content:encoded><![CDATA[<p>Aaron&#39;s comment sums up my thoughts precisely &#8212; I make my living giving guarantees based on technical data (to put it a very high level). I need to understand the architecture if I&#39;m going to put my neck on the line with a customer-facing recommendation (I&#39;m actually in the middle of a painful experience here with one of the VCE companies actually &#8212; what&#39;s stated in documentation and was presented to the customer is not actually functional as promised now that we&#39;re into final implementation phases).</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Minified using disk: basic
Page Caching using disk: enhanced

Served from: www.gabesvirtualworld.com @ 2012-02-09 10:00:44 -->
