<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>partition-alignment on Virtual Andy</title>
    <link>https://dev.ahill.net/category/partition-alignment/</link>
    <description>Recent content in partition-alignment on Virtual Andy</description>
    <generator>Hugo -- 0.120.4</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Jan 2009 23:01:24 +0000</lastBuildDate>
    <atom:link href="https://dev.ahill.net/category/partition-alignment/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>VI3 Value Added: System Deployment</title>
      <link>https://dev.ahill.net/2009/01/03/system-deployment/</link>
      <pubDate>Sat, 03 Jan 2009 23:01:24 +0000</pubDate>
      <guid>https://dev.ahill.net/2009/01/03/system-deployment/</guid>
      <description>One of the things I have to do as a Virtual Infrastructure Administrator is evangelize value added with virtual machines. What are my stakeholders going to get out of this? Where&amp;rsquo;s the value added? Why should we use a virtual machines instead of physical machines? Here&amp;rsquo;s my explanation of some advantages and value added using VMware Virtual Infrastructure 3 from a system deployment standpoint.
This post will show a &amp;ldquo;before and after&amp;rdquo; view of system deployment.</description>
    </item>
  </channel>
</rss>
