<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>JimMoyle.com &#187; RackSpace</title>
	<atom:link href="http://www.jimmoyle.com/tag/rackspace/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.jimmoyle.com</link>
	<description>An insight into the world of desktop and application delivery</description>
	<lastBuildDate>Fri, 02 Sep 2011 09:26:22 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
		<item>
		<title>What is needed from a IaaS cloud provider for us to cloudburst.</title>
		<link>http://www.jimmoyle.com/2010/05/what-is-needed-from-a-iaas-cloud-provider-for-us-to-cloudburst/</link>
		<comments>http://www.jimmoyle.com/2010/05/what-is-needed-from-a-iaas-cloud-provider-for-us-to-cloudburst/#comments</comments>
		<pubDate>Mon, 10 May 2010 16:47:58 +0000</pubDate>
		<dc:creator>Jim Moyle</dc:creator>
				<category><![CDATA[Cloud]]></category>
		<category><![CDATA[Amazon]]></category>
		<category><![CDATA[BriForum]]></category>
		<category><![CDATA[Cloudbursting]]></category>
		<category><![CDATA[EC2]]></category>
		<category><![CDATA[RackSpace]]></category>
		<category><![CDATA[SoftLayer]]></category>

		<guid isPermaLink="false">http://www.jimmoyle.com/2010/05/what-is-needed-from-a-iaas-cloud-provider-for-us-to-cloudburst/</guid>
		<description><![CDATA[As I’m pulling together my session for BriForum I need to choose which Cloud provider to use for the demo.  I’ve come up with a list of seven pre-requisites I need and thought I’d share them with you.  I’ve refined this list as I’ve experimented with various providers to try and judge their suitability.  This [...]]]></description>
			<content:encoded><![CDATA[<p>As I’m pulling together my <a href="http://www.jimmoyle.com/2010/04/briforum-2010/">session</a> for <a href="http://briforum.com">BriForum</a> I need to choose which Cloud provider to use for the demo.  I’ve come up with a list of seven pre-requisites I need and thought I’d share them with you.  I’ve refined this list as I’ve experimented with various providers to try and judge their suitability.  This list has been compiled for what I consider to be the minimum for a production IaaS offering.  Don’t take it as gospel though, your needs may be different, regard it as a starting point.</p>
<h3>1. Open API</h3>
<p>This is needed to automate the start-up, configuration and termination of cloud instances.  Without automation the cloud infrastructure is no use to you, a manual web page driven administration process is not going to win a provider any points with me.  As a secondary point, it’s even better if they provide tools that integrate with these API’s.  Making me write tools, is again, not going to win any points.</p>
<h3>2. Secure IP connectivity</h3>
<p>By this I mean the ability to secure the connection between a cloud <strong>IP subnet</strong> and private infrastructure.  If I need to create instances on demand I need to be able to securely access the subnet they are on and hide those machine from the ‘net,  only being able to access machine securely on an individual basis will not do.</p>
<h3>3. Decent guest start-up time</h3>
<p>By this I mean under ten minutes guaranteed.  If you only promise between 15 and 45 minutes (RackSpace) then it’s too slow.  Also as billing usually starts from the request not the availability I don’t want to be paying for time I’m not using.  The solution for this would be to move to a billing from availability model, this would motivate providers to get guests up quickly.</p>
<h3>4. Support for new Guest versions is quickly adopted</h3>
<p>If a new hypervisor, or a new OS version comes out I want to be able to take advantage of those features quickly, I especially don’t want my local infrastructure to be held up by interoperability problems with cloud services if they are behind the upgrade curve.  When you are waiting on a large corporation to upgrade and your business is too small to put pressure on them to make you a special case then you are going to get pretty angry pretty quickly.  There is at least on cloud provider (I’m looking at you Amazon EC2) which doesn’t support Windows 7 or Windows Server 2008 R2 and it’s <strong>nine</strong> months after RTM.</p>
<h3>5. Hypervisor Access</h3>
<p>I need to be able to upload my own virtual machine appliances, whether they are from a third party or one I’ve made onsite.  I also need to be able to manage the hypervisor layer with the same tools and using the same skills that I already have in house.</p>
<h3>6. Keyboard Video Mouse console access</h3>
<p>There is a reason that servers have KVM boards, it’s that not all problems happen after you have RDP or SSH access.  You lose a whole lot of troubleshooting information if you lose visibility of the console.</p>
<h3>7. Hourly billing</h3>
<p>All instances should be able to be billed hourly, I don’t mind if you have monthly charges as well, but hourly should always be available, if I need a resource permanently, I might as well host it myself.  Give us the option to try out, demo and burst into the full range of your offerings.</p>
<p>So have I found a provider that fits the bill?  The short answer is no.  The slightly longer answer is that I’ve found one who are really close, close enough that I’m happy to use it.  That provider is <a href="http://www.softlayer.com/">SoftLayer</a>.</p>
<p>I reserve the right to change my mind at any time as providers change their offerings. <img src='http://jimmoyle.com/wordpress/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
			<wfw:commentRss>http://www.jimmoyle.com/2010/05/what-is-needed-from-a-iaas-cloud-provider-for-us-to-cloudburst/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

