openstack team mailing list archive

[Doug Davis <dug@xxxxxxxxxx>]

+1 if you want people to care about something then it should be part of 
the main repo and part of the regular regression testing. 

thanks
-Doug
______________________________________________________
STSM |  Standards Architect  |  IBM Software Group
(919) 254-6905  |  IBM 444-6905  |  dug@xxxxxxxxxx
The more I'm around some people, the more I like my dog.



Russell Bryant <rbryant@xxxxxxxxxx> 
Sent by: openstack-bounces+dug=us.ibm.com@xxxxxxxxxxxxxxxxxxx
04/23/2012 02:16 PM

To
openstack@xxxxxxxxxxxxxxxxxxx
cc

Subject
Re: [Openstack] Canonical AWSOME






On 04/23/2012 10:42 AM, Doug Hellmann wrote:
> 
> 
> On Mon, Apr 23, 2012 at 8:39 AM, Thierry Carrez <thierry@xxxxxxxxxxxxx
> <mailto:thierry@xxxxxxxxxxxxx>> wrote:
> 
>     Philipp Wollermann wrote:
>     > What's the advantage of replacing the native EC2 compatibility
>     layer with AWSOME from a user / operator point of view?
> 
>     One thing that was mentioned is that the proxy could be run on top 
of a
>     public cloud that chose to only deploy OpenStack API support.

This makes sense.

> It also makes project management easier, as the people interested in
> maintaining it can focus on the separate repository.

I'm not sure I buy into this, though.  Why is it harder for people that
are interested in EC2 support to work in the existing nova repo?  If
people want to collaborate before pushing into mainline, that can be
done via feature branches, too.

It risks making EC2 development harder, as well.  Pulling it out of nova
completely risks allowing the people that don't care about EC2 to care
even less.  It could make it easier for people to make changes that make
EC2 compatibility harder to maintain.

-- 
Russell Bryant

_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to     : openstack@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openstack
More help   : https://help.launchpad.net/ListHelp