On Thu, Jun 25, 2009 at 3:45 PM,  <span dir="ltr">&lt;<a href="mailto:shlomo.swidler@gmail.com">shlomo.swidler@gmail.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div id=":1q0" class="ii gt">4. How will I be able to discover VM images that are appropriate for<br>
my &quot;compute&quot;s? For example, Amazon has public AMIs that I can launch<br>
on my instances, and I can filter the ElasticFox view to only show me<br>
64-bit AMIs or otherwise filter them by AMI name. Is this use case<br>
covered by OVF, or is it more appropriate at the OCCI level?</div></blockquote></div><br>This one I have a better answer for, in that there should be no &quot;start&quot; verb for a template (e.g. AMI), rather only a &quot;clone&quot; verb which returns a Location: to a new compute resource (pre-linked to any storage and network resources as necessary). We could also bundle templates into a pre-defined category, such that machines that are just not startable (e.g. due to permissions, faults, etc.) don&#39;t appear as templates.<br>
<br>Sam<br><br>