<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.11" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Virtual Machine Sprawl: What Does It Cost You?</title>
	<link>http://www.linux-mag.com/id/7119/</link>
	<description>Open Source, Open Standards</description>
	<pubDate>Sat, 04 Jul 2009 18:12:59 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.11</generator>

	<item>
		<title>by: Ken Hess</title>
		<link>http://www.linux-mag.com/id/7119/#comment-1579</link>
		<pubDate>Sun, 12 Oct 2008 14:05:56 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7119/#comment-1579</guid>
					<description>The difference is that when you have physical machines, you can see them, touch them, and inventory them by several different methods: Visually, ping, management application, etc. Virtual machines that are off can't be inventoried so easily. It's also easy to remove them from a VM inventory but have them still exist and burning a license.
VM management is a real problem, especially in larger environments where you have multiple people creating and maintaining them--possibly in different parts of the world.

Spreadsheets or text files are not a good solution unless you have only a couple dozen systems.</description>
		<content:encoded><![CDATA[<p>The difference is that when you have physical machines, you can see them, touch them, and inventory them by several different methods: Visually, ping, management application, etc. Virtual machines that are off can&#8217;t be inventoried so easily. It&#8217;s also easy to remove them from a VM inventory but have them still exist and burning a license.<br />
VM management is a real problem, especially in larger environments where you have multiple people creating and maintaining them&#8211;possibly in different parts of the world.</p>
<p>Spreadsheets or text files are not a good solution unless you have only a couple dozen systems.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: mysteriousplanet</title>
		<link>http://www.linux-mag.com/id/7119/#comment-1575</link>
		<pubDate>Fri, 10 Oct 2008 09:28:28 +0000</pubDate>
		<guid>http://www.linux-mag.com/id/7119/#comment-1575</guid>
					<description>If people manage there servers properly then there will be no problem.

All servers should be treated the same as regards to management. A virtual server is a real server, from a logical perspective, the host server is too, it's just an application hosting machine.
People should always keep records of there systems and track the licensing correctly. If they don't they are not really managing their environment very well, so this is really a complete non-issue, virtual or otherwise makes no difference.

I can't understand why people seem to fall into the marketing crap of inventory systems when they can do it all for free themselves by just keeping a record of a build when they build or change it... keep a record of the licenses and the hardware setup, even in something as simple as a text file or spreadsheet... it's not hard and it's free!</description>
		<content:encoded><![CDATA[<p>If people manage there servers properly then there will be no problem.</p>
<p>All servers should be treated the same as regards to management. A virtual server is a real server, from a logical perspective, the host server is too, it&#8217;s just an application hosting machine.<br />
People should always keep records of there systems and track the licensing correctly. If they don&#8217;t they are not really managing their environment very well, so this is really a complete non-issue, virtual or otherwise makes no difference.</p>
<p>I can&#8217;t understand why people seem to fall into the marketing crap of inventory systems when they can do it all for free themselves by just keeping a record of a build when they build or change it&#8230; keep a record of the licenses and the hardware setup, even in something as simple as a text file or spreadsheet&#8230; it&#8217;s not hard and it&#8217;s free!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
