On Thu, Jan 21, 2010 at 5:45 AM, David Lutterkort <span dir="ltr">&lt;<a href="mailto:lutter@redhat.com">lutter@redhat.com</a>&gt;</span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im"><br></div>That&#39;s exactly the intent behind discovery. In addition, you should<br>
never have to make decisions based on the name of the provider - you<br>
should always be able to make them based on metadata you get from the<br>
concrete driver. IOW, if you want to know if you can inject user data,<br>
don&#39;t check whether you&#39;re talking to EC2, check for well-known metadata<br>
in the API description.<br>
<div class="im"><br></div></blockquote><div><br></div><div>Right, so perhaps I was getting things confused in my mind. So  what you are suggesting is that some file injection feature is part of the api - but in an optional section. And the api would provide a way to query what in the optional section is available?</div>
<div><br></div><div>What would be nice would be to pick either the Rackspace or the EC2 way of injection, and make that the &quot;normal&quot; way - and emulate it if really needed (in the driver if necessary) for the other (I think that would be possible to do the EC2 way in Rackspace without too much trouble). In time cloud providers would possibly provide it anyway.</div>
<div><br></div><div>If its discovering 2 different ways to do file injection, I don&#39;t think I would like that (unless 1 type is a super set of the other type - if you follow what I mean). </div><div><br></div><div><br>
</div></div>