On Tue, 2012-04-24 at 13:26 +0200, Soren Hansen wrote:
> 23. apr. 2012 17.15 skrev Justin Santa Barbara <jus...@fathomdb.com>:
> > With one native API, we can focus all our energies on making sure that API
> > works. Then, knowing that the native API works, we can build other APIs on
> > top through simple translation layers, and they will work also. Other APIs
> > can be built on top in the same way (e.g. OCCI)
>
> Sorry, I'm having trouble here.. Are you suggesting that having two
> sibling frontend API's talking to a shared backend API is poor software
> engineering, but layering similar purposed API's on top of each other
> like this is good software engineering?
Yeah, I'm with you here.
I think the frustration about the native EC2 support boils down to:
a) we haven't (yet) got the clean separation of layers that we'd like
b) not enough people are working on EC2 support
c) there's a concern that OpenStack providers may not enable it
And my reaction to those is:
a) we can fix that
b) starting a new project doesn't help
c) adding an EC2 frontend to deltacloud is a much more sane way of
addressing this
Cheers,
Mark.
_______________________________________________
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
