openstack team mailing list archive

[Erik Carlin <erik.carlin@xxxxxxxxxxxxx>]

>From a Rackspace perspective, we do not want to expose block operations in the compute API.  The plan has been to expose the attach/detach as nova API extensions, and that still makes sense, but will there be a separate, independent block service and API?

Erik

From: Chuck Thier <cthier@xxxxxxxxx<mailto:cthier@xxxxxxxxx>>
Date: Fri, 8 Jul 2011 13:15:56 -0500
To: Jorge Williams <jorge.williams@xxxxxxxxxxxxx<mailto:jorge.williams@xxxxxxxxxxxxx>>
Cc: "<openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>>" <openstack@xxxxxxxxxxxxxxxxxxx<mailto:openstack@xxxxxxxxxxxxxxxxxxx>>
Subject: Re: [Openstack] Refocusing the Lunr Project

Hey Jorge,

That is up to the Nova team, though I imagine that it will continue down the road that it had been progressing (as an extension to the current openstack api).

--
Chuck

On Fri, Jul 8, 2011 at 12:37 PM, Jorge Williams <jorge.williams@xxxxxxxxxxxxx<mailto:jorge.williams@xxxxxxxxxxxxx>> wrote:
Chuck,

What does this mean in terms of APIs?  Will there be a separate Volume API?  Will volumes be embedded in the compute API?

-jOrGe W.


On Jul 8, 2011, at 10:40 AM, Chuck Thier wrote:

Openstack Community,

Through the last few months the Lunr team has learned many things.  This
week, it has become clear to us that it would be better to integrate
with the existing Nova Volume code. It is upon these reflections that we
have decided to narrow the focus of the Lunr Project.

Lunr will continue to focus on delivering an open commodity storage
platform that will integrate with the Nova Volume service.  This will
be accomplished by implementing a Nova Volume driver. We will work
with the Nova team, and other storage vendors, to drive the features
needed to provide a flexible volume service.

I believe that this new direction will ensure a bright future for storage
in Nova, and look forward to continuing to work with everyone in making this
possible.

Sincerely,

Chuck Thier (@creiht)
Lunr Team Lead _______________________________________________
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

This email may include confidential information. If you received it in error, please delete it.

_______________________________________________ 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
This email may include confidential information. If you received it in error, please delete it.