> cloud-init has specific code to handle EC2 and OpenStack, but the images 
> themselves are quite generic.
Actually, ours would be generic too, if it wasn't for the ec2 startup
scripts (which cloud-init could handle in the future).

Anders


On 3 December 2012 19:01, Clint Byrum <[email protected]> wrote:
> Excerpts from Thomas Goirand's message of 2012-12-02 05:25:10 -0800:
>> On 12/02/2012 07:29 PM, Marco d'Itri wrote:
>> > Are the EC2 images also usable as is on other Amazon-like cloud
>> > infrastructures? If they are not, then I do not see the point of using
>> > our own resources for the benefit of a specific cloud provider.
>> They are normally useable with Openstack, which is in Wheezy.
>> If you want to try Openstack though, it might be more easy to
>> do so with our latest release (eg: 2012.2.1) only available in
>> our Git on Alioth:
>>
>> https://wiki.debian.org/OpenStackHowto/Folsom
>>
>> Following this howto, one should be up-and-running with
>> Openstack within 30 minutes (plus of course the time it
>> would take to install Wheezy on a few servers).
>>
>> I would also like to highlight that Canonical releases some LTS
>> images specifically made to run on EC2 or on Openstack (and
>> maybe, with a stronger focus on Openstack). I see no reason
>> why Debian wouldn't do it as well.
>>
>
> The Ubuntu cloud images:
>
> https://cloud-images.ubuntu.com/
>
> Are even more generic than that. They are meant to run on
> "virtualization". They make a nice starting point for simply downloading
> and booting a server image in KVM for instance.
>
> cloud-init has specific code to handle EC2 and OpenStack, but the images
> themselves are quite generic.
>
>
> --
> To UNSUBSCRIBE, email to [email protected]
> with a subject of "unsubscribe". Trouble? Contact [email protected]
> Archive: http://lists.debian.org/[email protected]
>


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: 
http://lists.debian.org/CAMcOGXE=W5RHsJ+UthSJBzEPzyuxqcvwuALu3EZt-ZyFm1=f...@mail.gmail.com

Reply via email to