<?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: Graphical Front-End for Storage VMotion</title>
	<atom:link href="http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/</link>
	<description>The weblog of an IT pro specializing in virtualization, storage, and servers</description>
	<lastBuildDate>Wed, 08 Feb 2012 17:13:47 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: slowe</title>
		<link>http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/comment-page-1/#comment-39278</link>
		<dc:creator>slowe</dc:creator>
		<pubDate>Wed, 11 Jun 2008 00:59:44 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/#comment-39278</guid>
		<description>Conrad,

Thanks for your perspective. It&#039;s easy to forget the other considerations that come into play sometimes.</description>
		<content:encoded><![CDATA[<p>Conrad,</p>
<p>Thanks for your perspective. It&#8217;s easy to forget the other considerations that come into play sometimes.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Conrad Golightly</title>
		<link>http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/comment-page-1/#comment-39274</link>
		<dc:creator>Conrad Golightly</dc:creator>
		<pubDate>Wed, 11 Jun 2008 00:09:57 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/#comment-39274</guid>
		<description>By the way, I don&#039;t pretend to work for or speak for VMware, just presenting a different (if not necessarily correct, in this case) perspective.</description>
		<content:encoded><![CDATA[<p>By the way, I don&#8217;t pretend to work for or speak for VMware, just presenting a different (if not necessarily correct, in this case) perspective.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Conrad Golightly</title>
		<link>http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/comment-page-1/#comment-39273</link>
		<dc:creator>Conrad Golightly</dc:creator>
		<pubDate>Wed, 11 Jun 2008 00:08:04 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/#comment-39273</guid>
		<description>IT lifecycle management is one of the things I do at my primary job, and after some discussions with engineers at numerous companies that make excellent software I frequently use, my answer to your question &quot;Now, if a single developer could write a GUI for Storage VMotion, why didnâ€™t VMware take care of this themselves?&quot; is this:  VMware&#039;s engineers probably did not feel that they could provide the quality of code in this release that their customers are used to seeing in the normal interface.  The organizations on the leading edge of IT are the ones with users comfortable with doing extensive technical troubleshooting, and CLI tools are the best usage of developer time for major features that are new to a product; adding VMware-grade GUI support to this tool in this release would likely have added significant time to the release.  If you really do need storage VMotion right now, chances are good that the people in your organization responsible for storage can use the CLI.</description>
		<content:encoded><![CDATA[<p>IT lifecycle management is one of the things I do at my primary job, and after some discussions with engineers at numerous companies that make excellent software I frequently use, my answer to your question &#8220;Now, if a single developer could write a GUI for Storage VMotion, why didnâ€™t VMware take care of this themselves?&#8221; is this:  VMware&#8217;s engineers probably did not feel that they could provide the quality of code in this release that their customers are used to seeing in the normal interface.  The organizations on the leading edge of IT are the ones with users comfortable with doing extensive technical troubleshooting, and CLI tools are the best usage of developer time for major features that are new to a product; adding VMware-grade GUI support to this tool in this release would likely have added significant time to the release.  If you really do need storage VMotion right now, chances are good that the people in your organization responsible for storage can use the CLI.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Natiboy</title>
		<link>http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/comment-page-1/#comment-39214</link>
		<dc:creator>Natiboy</dc:creator>
		<pubDate>Thu, 05 Jun 2008 17:35:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/#comment-39214</guid>
		<description>Because since EMC&#039;s aquisition the VC product development has shifted to the similar models of EMC --&#039;The Software Company&#039;  -- junky.

ECC, Navisphere, and other tools all have less and less  Enterprise feel every time they release.  I think it should just work. Like the hypervisor.</description>
		<content:encoded><![CDATA[<p>Because since EMC&#8217;s aquisition the VC product development has shifted to the similar models of EMC &#8211;&#8217;The Software Company&#8217;  &#8212; junky.</p>
<p>ECC, Navisphere, and other tools all have less and less  Enterprise feel every time they release.  I think it should just work. Like the hypervisor.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Clint</title>
		<link>http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/comment-page-1/#comment-35384</link>
		<dc:creator>Clint</dc:creator>
		<pubDate>Sun, 10 Feb 2008 06:54:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/#comment-35384</guid>
		<description>It has been my opinion for a while as great as Virtualization and in particular VMware is, it seems that VMware does not always think Enterprise when developing some of their tools.

It would seem that little things like a solid GUI for a GREAT feature would be a no brainer.

As Rich mentioned hopefully they will add this in a patch, but to me it seems that they are getting a reputation of needing a few patches after each major release before it is ready for prime time.</description>
		<content:encoded><![CDATA[<p>It has been my opinion for a while as great as Virtualization and in particular VMware is, it seems that VMware does not always think Enterprise when developing some of their tools.</p>
<p>It would seem that little things like a solid GUI for a GREAT feature would be a no brainer.</p>
<p>As Rich mentioned hopefully they will add this in a patch, but to me it seems that they are getting a reputation of needing a few patches after each major release before it is ready for prime time.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rich</title>
		<link>http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/comment-page-1/#comment-35366</link>
		<dc:creator>Rich</dc:creator>
		<pubDate>Sat, 09 Feb 2008 13:02:18 +0000</pubDate>
		<guid isPermaLink="false">http://blog.scottlowe.org/2008/02/09/graphical-front-end-for-storage-vmotion/#comment-35366</guid>
		<description>Scott,

I agree. Even if adding the Windows Remote CLI install to the VC 2.5 install was all that was done, well, that would make sense. Then building a GUI for it, or hooks that call svmotion from the VI client would be too easy. I have to believe that an upcoming patch will add this feature. Please, VMware ?!</description>
		<content:encoded><![CDATA[<p>Scott,</p>
<p>I agree. Even if adding the Windows Remote CLI install to the VC 2.5 install was all that was done, well, that would make sense. Then building a GUI for it, or hooks that call svmotion from the VI client would be too easy. I have to believe that an upcoming patch will add this feature. Please, VMware ?!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

