Open Stack

Originally I wrote the connector side of brick to be the LUN discovery 
shared code between Cinder and Nova.
I tried to make a patch in Havana that would remove do this but it 
didn't make it in.

The upside to brick not making it in Nova is that it has given us some 
time to rethink things a bit.  What I would actually
like to see happen now is to create a new cinder/storage agent instead 
of just a brick library.   The agent would run on every cinder node,
nova node and potentially ironic nodes to do LUN discovery. Duncan and I 
are looking into this for the Kilo release.

The other portion of brick that exists in Cinder today some of the LVM 
code.   This makes a lot of sense to have in an agent as well for
each nova compute node to manage ephemeral storage used for boot disks 
for nova vms.  This would help remove some of the remaining
storage code from nova itself that does this.

Duncan and I will be at the Paris summit.   We would both welcome any 
interest to work on this concept of a new storage agent (which would
contain the existing brick code).


My $0.02,
Walt

> On 09/16/2014 11:55 PM, Ben Nemec wrote:
>> Based on my reading of the wiki page about this it sounds like it should
>> be a sub-project of the Storage program.  While it is targeted for use
>> by multiple projects, it's pretty specific to interacting with Cinder,
>> right?  If so, it seems like Oslo wouldn't be a good fit.  We'd just end
>> up adding all of cinder-core to the project anyway. :-)
> +1 I think the same arguments and conclusions we had on glance-store
> make sense here. I'd probably go with having it under the Block Storage
> program.
>
> Flavio
>
>> -Ben
>>
>> On 09/16/2014 12:49 PM, Ivan Kolodyazhny wrote:
>>> Hi Stackers!
>>>
>>> I'm working on moving Brick out of Cinder for K release.
>>>
>>> There're a lot of open questions for now:
>>>
>>>     - Should we move it to oslo or somewhere on stackforge?
>>>     - Better architecture of it to fit all Cinder and Nova requirements
>>>     - etc.
>>>
>>> Before starting discussion, I've created some proof-of-concept to try it. I
>>> moved Brick to some lib named oslo.storage for testing only. It's only one
>>> of the possible solution to start work on it.
>>>
>>> All sources are aviable on GitHub [1], [2].
>>>
>>> [1] - I'm not sure that this place and name is good for it, it's just a PoC.
>>>
>>> [1] https://github.com/e0ne/oslo.storage
>>> [2] https://github.com/e0ne/cinder/tree/brick - some tests still failed.
>>>
>>> Regards,
>>> Ivan Kolodyazhny
>>>
>>> On Mon, Sep 8, 2014 at 4:35 PM, Ivan Kolodyazhny <e0ne at e0ne.info> wrote:
>>>
>>>> Hi All!
>>>>
>>>> I would to start moving Cinder Brick [1] to oslo as was described on
>>>> Cinder mid-cycle meetup [2]. Unfortunately I missed meetup so I want be
>>>> sure that nobody started it and we are on the same page.
>>>>
>>>> According to the Juno 3 release, there was not enough time to discuss [3]
>>>> on the latest Cinder weekly meeting and I would like to get some feedback
>>>> from the all OpenStack community, so I propose to start this discussion on
>>>> mailing list for all projects.
>>>>
>>>> I anybody didn't started it and it is useful at least for both Nova and
>>>> Cinder I would to start this work according oslo guidelines [4] and
>>>> creating needed blueprints to make it finished until Kilo 1 is over.
>>>>
>>>>
>>>>
>>>> [1] https://wiki.openstack.org/wiki/CinderBrick
>>>> [2] https://etherpad.openstack.org/p/cinder-meetup-summer-2014
>>>> [3]
>>>> http://lists.openstack.org/pipermail/openstack-dev/2014-September/044608.html
>>>> [4] https://wiki.openstack.org/wiki/Oslo/CreatingANewLibrary
>>>>
>>>> Regards,
>>>> Ivan Kolodyazhny.
>>>>
>>>
>>>
>>> _______________________________________________
>>> OpenStack-dev mailing list
>>> OpenStack-dev at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>>
>>
>> _______________________________________________
>> OpenStack-dev mailing list
>> OpenStack-dev at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>>
>