Good point, Thorsten.  I think the &#39;bootstrap script&#39; is the highest value add.  Not  a replacement for puppet/etc, but these services need to be installed before they can be used.  Having an injection/exec feature allows you to overlay an embryo image with whatever you want to finish the job, albeit chef, puppet, apt-get whatever.  <br>
<br>FWIW, jclouds is exposing this so that we don&#39;t depend so heavily on specific cloud support and images.  If the vendor doesn&#39;t support injection, we simply ssh in, push the file, and exec it.  Outside windows, accomplishing this cross-cloud isn&#39;t rocket science for most cases.<br>
<br>my 2p.<br>-Adrian<br><br><br><br><div class="gmail_quote">On Tue, Dec 8, 2009 at 8:03 AM, Thorsten von Eicken <span dir="ltr">&lt;<a href="mailto:tve@rightscale.com">tve@rightscale.com</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;">



  

<div bgcolor="#ffffff" text="#000000">
For EC2 you might consider supporting
<a href="http://alestic.com/2009/06/ec2-user-data-scripts" target="_blank">&lt;http://alestic.com/2009/06/ec2-user-data-scripts&gt;</a>, which is a
nice way to go.<br><font color="#888888">
Thorsten</font><div><div></div><div class="h5"><br>
<br>
Bob McWhirter wrote:
<blockquote type="cite">
  <pre>So, EC2 doesn&#39;t allow (this week) the specific injection of files into  
instances.

It does allow placement of up to 16k into a location that can be  
fetched by instance upon boot.

With EC2, we could &#39;fake&#39; file injection, by only having the driver  
inject it into the instance boot metadata.

It&#39;d be up to the image to actually do the pull at boot time.

I think this would allow supporting this functionality, and not being  
limited by what EC2 can (or can&#39;t) do.

A 20-line bash init.d script could be provided for people using EC2 to  
enable pulling from the metadata at boottime and injecting the file(s)  
locally.

Ultimately, &quot;injection&quot; is only partially defined to mean &quot;push as far  
as possible for this provider&quot;.  And I think that&#39;s fine.

	-Bob


On Dec 7, 2009, at 7:46 PM, Michael Neale wrote:

  </pre>
  <blockquote type="cite">
    <pre>Hi All.

Would people consider an addition to the instance creation part of
deltacloud API to allow the injection of files/content to specified
paths? (an extra optional field(s) on the POST)?

(this is the sort of thing that we need to have in some kind of
semi-formal RFC wiki setup for people to point at and shout).


-- 
Michael D Neale
home: <a href="http://www.michaelneale.net" target="_blank">www.michaelneale.net</a>
blog: <a href="http://michaelneale.blogspot.com" target="_blank">michaelneale.blogspot.com</a>
_______________________________________________
deltacloud-devel mailing list
<a href="mailto:deltacloud-devel@lists.fedorahosted.org" target="_blank">deltacloud-devel@lists.fedorahosted.org</a>
<a href="https://fedorahosted.org/mailman/listinfo/deltacloud-devel" target="_blank">https://fedorahosted.org/mailman/listinfo/deltacloud-devel</a>
    </pre>
  </blockquote>
  <pre>_______________________________________________
deltacloud-devel mailing list
<a href="mailto:deltacloud-devel@lists.fedorahosted.org" target="_blank">deltacloud-devel@lists.fedorahosted.org</a>
<a href="https://fedorahosted.org/mailman/listinfo/deltacloud-devel" target="_blank">https://fedorahosted.org/mailman/listinfo/deltacloud-devel</a>

  </pre>
</blockquote>
</div></div></div>

<br>_______________________________________________<br>
deltacloud-devel mailing list<br>
<a href="mailto:deltacloud-devel@lists.fedorahosted.org">deltacloud-devel@lists.fedorahosted.org</a><br>
<a href="https://fedorahosted.org/mailman/listinfo/deltacloud-devel" target="_blank">https://fedorahosted.org/mailman/listinfo/deltacloud-devel</a><br></blockquote></div><br>