openstack team mailing list archive

[Eric Windisch <eric@xxxxxxxxxxxxxxxx>]

EC2 is strategically important.  I don't believe that building "gold images" is the right focus for OpenStack.  

Anyone wanting to use config-drive would need to support it in their images, that is a no-brainer. It should not be required that images launching in Nova via the EC2 API support config-drive. The EC2 metadata service must remain.

The EC2 API is intended to mimic EC2 behavior and provide compatibility. The OpenStack implementations should not diverge or break that compatibility.  

--  
Eric Windisch


On Tuesday, April 10, 2012 at 2:05 PM, Justin Santa Barbara wrote:

> Config drive can support all EC2 functionality, I believe.
>  
> Images would need to be respun for OpenStack with config-drive, unless we populated the config drive in a way that worked with cloud-init.  (Scott?)  
>  
> Personally, I'd rather our effort went into producing great images for OpenStack, than into compatibility with last-generation clouds.  Any idea what the "important" EC2 images are?  Are there a handful of images that we could duplicate and then just forget about EC2?  
>  
>  
> On Tue, Apr 10, 2012 at 10:30 AM, Joshua Harlow <harlowja@xxxxxxxxxxxxx (mailto:harlowja@xxxxxxxxxxxxx)> wrote:
> > Except for the fact that the config drive is non-EC2 right?
> >  
> > That might blow it out of the water to start, as I know a lot of people want the EC2 equivalents/compat.
> >  
> > But maybe if done right it shouldn’t matter (ie cloud-init could instead of calling out to urls could also call out to “local files” on a config drive).
> >  
> > I just worry that config drive is openstack api only, afaik.  
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to : openstack@xxxxxxxxxxxxxxxxxxx (mailto:openstack@xxxxxxxxxxxxxxxxxxx)
> Unsubscribe : https://launchpad.net/~openstack
> More help : https://help.launchpad.net/ListHelp
>  
>