I suppose this part is what I mean wrt whirr: For clouds that does not provide a specific application service on their > platform, we would work with Apache sibling projects such as Hadoop, CouchDB > and Cassandra for data store, or ActiveMQ and Qpid for queueing for example, > to close the gap. >
whirr would seem to be an ideal way for them to achieve this, right? I've also reached out, too. -Adrian On Fri, Aug 20, 2010 at 9:21 AM, Tom White <[email protected]> wrote: > Adrian, > > Thanks for the pointer. It looks like Nuvem is focusing on defining > common service APIs (e.g. a key-value store API), with a variety of > underlying implementations. Whirr is focusing on running services > (like Hadoop, ZooKeeper) on variety of cloud providers; it doesn't aim > to provide common APIs for these services. But you're right that there > may be some overlap. Worth reaching out, I suspect. > > Cheers, > Tom > > On Fri, Aug 20, 2010 at 9:06 AM, Adrian Cole <[email protected]> wrote: > > Except the fact that we don't expose existing service apis, there seems > to be a high overlap. Perhaps they didn't know about whirr, yet? > > > > -Adrian > > > > http://wiki.apache.org/incubator/Nuvem >
