On Tue, Dec 8, 2009 at 10:06 AM, Bob McWhirter <bmcwhirt@redhat.com> wrote:So, EC2 doesn'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 'fake' file injection, by only having the driver inject it into the instance boot metadata. It'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'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, "injection" is only partially defined to mean "push as far as possible for this provider". And I think that's fine. -Bob On Dec 7, 2009, at 7:46 PM, Michael Neale wrote: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: www.michaelneale.net blog: michaelneale.blogspot.com _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel_______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-develWhat about using ace/puppet or something similar for this kind of configuration? Then we don't have to depend on the provider of the cloud, just that we have some basic components installed on our instance(s). Rightscale has a similar concept to this with their server templates and 'rightScripts', and we did the same thing in the oVirt project to configure/setup an 'appliance' server.