+1 on extensibility.<br><br>Messaging or network shared memory (cache) would be relevant next resources in my book.<br><br>-Adrian Cole<br>jclouds<br><br><div class="gmail_quote">On Fri, May 15, 2009 at 6:09 PM, Sam Johnston <span dir="ltr">&lt;<a href="mailto:samj@samj.net">samj@samj.net</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Evening all,<br><br><a href="http://csrc.nist.gov/groups/SNS/cloud-computing/index.html" target="_blank">According to NIST</a>:<br>
<br><blockquote style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;" class="gmail_quote">
<i>Cloud computing is a pay-per-use model for enabling available, convenient, on-demand <br>network access to a shared pool of configurable computing resources <b>(e.g., networks, <br>servers, storage, applications, services)</b> that can be rapidly provisioned and released with <br>

minimal management effort or service provider interaction. This cloud model promotes <br>availability and is comprised of five key characteristics, three delivery models, and four <br>deployment models.</i><br></blockquote>

<br>Is it obvious to anyone else what the next resource extensions after compute, network and storage should be? Is there still someone who needs convincing that we need to have extensibility at the heart of the protocol and build incrementally?<br>
<font color="#888888">
<br>Sam<br><br>
</font><br>_______________________________________________<br>
occi-wg mailing list<br>
<a href="mailto:occi-wg@ogf.org">occi-wg@ogf.org</a><br>
<a href="http://www.ogf.org/mailman/listinfo/occi-wg" target="_blank">http://www.ogf.org/mailman/listinfo/occi-wg</a><br>
<br></blockquote></div><br>