<!DOCTYPE html PUBLIC '-//W3C//DTD HTML 4.01 Transitional//EN'>
<html><head><meta http-equiv="Content-Type" content="text/html;charset=utf-8">
<style>BODY{font:10pt Tahoma,Verdana,sans-serif} .MsoNormal{line-height:120%;margin:0}</style></head><body>
Yes, thank you.<br><br>Best regards,<br><br>Tristan van Bokkem<br>Datacenter Operations<br><br>Contact:<br>E-mail Personal: <a href="mailto:tristanvanbokkem@i3d.net">tristanvanbokkem@i3d.net</a><br>E-mail Support: <a href="mailto:info@i3d.net">info@i3d.net</a><br>E-mail NOC: <a href="mailto:noc@i3d.net">noc@i3d.net</a><br>Website: <a href="http://www.i3d.net" target="_blank">http://www.i3d.net</a> Office:<br>Interactive 3D B.V.<br>Meent 93b<br>3011 JG Rotterdam<br>The Netherlands<br><br>Visit www.smartdc.net – SmartDC is our in-house 36,000 sq. ft. datacenter in Rotterdam, The Netherlands. High density hosting – multiple fiber carriers in-house – Level3 PoP.<br><br>Interactive 3D (i3D.net) is a company registered in The Netherlands at Meent 93b, Rotterdam. Registration #: 14074337 - VAT # NL 8202.63.886.B01. Interactive 3D (i3D.net) is CDSA certified on content protection and security. We are ranked in the Deloitte Technology Fast 50 as one of the fastest growing technology companies.<br><blockquote style="padding-left: 5px; margin-left: 5px; border-left: #0000ff 2px solid; margin-right: 0px"><hr><b>From:</b> Darren Birkett [mailto:darren.birkett@gmail.com]<br><b>To:</b> Michael Stein [mailto:Michael.Stein@q9.com]<br><b>Cc:</b> Diego Parrilla Santamaría [mailto:diego.parrilla.santamaria@gmail.com], i3D.net - Tristan van Bokkem [mailto:tristanvanbokkem@i3d.nl], openstack@lists.launchpad.net<br><b>Sent:</b> Tue, 21 Feb 2012 15:36:23 +0100<br><b>Subject:</b> Re: [Openstack] Howto Nova setup with HA?<br><br>2012/2/21 Michael Stein <<a href="mailto:Michael.Stein@q9.com">Michael.Stein@q9.com</a>>:<br>
> I think that the idea behind Nova and “cloud” computing, in general, is that<br>
> applications, middle-ware, databases and other services, will be delivered<br>
> across multiple availability zones and provide HA via application-layer<br>
> replication. The concept of failure is assumed and designed for by any<br>
> forward thinking “cloud” designer. I think less time need to be spent on<br>
> preserving nodes that maintain the “holy grail” of functionality and<br>
> availability and more time needs to be spent on making apps cloud-friendly.<br>
<br>
Agreed, but you're talking about HA at a different layer - within the<br>
applications that will sit on top of the cloud infrastructure. Whilst<br>
that's absolutely valid, and a message that needs to be spread more<br>
amongst those designing apps for the cloud, it's not addressing the<br>
concerns of the OP.<br>
<br>
We still need to be thinking about HA of the cloud infrastructure<br>
components themselves, so that there are less failures for the app<br>
designers to have to tolerate in the first place.<br>
<br>
Darren<br>
</blockquote><style>
</style>
</body></html>