[openstack-dev] [tc][nova][mogan] How to show respect to the original authors?
niu.zglinux at gmail.com
Fri Sep 22 13:48:01 UTC 2017
Thanks Sean for the suggestion, os-brick is indeed a good example for
sharing codes. Will discuss with the team to see if it's possible to move
that code into such a library.
On Fri, Sep 22, 2017 at 9:26 PM, Sean McGinnis <sean.mcginnis at gmx.com>
> > >
> > > Luckily, since these things are part of the ABI of Nova, they are
> > > versioned in many cases, and in all have a well defined interfaces on
> > > one side. Seems like it should be relatively straight forward to wrap
> > > the other side of them and call it a library.
> > >
> > > ____________________________________________________________
> > > OpenStack Development Mailing List (not for usage questions)
> > > Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
> > > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
> > >
> > Sounds great if we can call these ABI as a library, but seems still need
> > some refactoring on Nova side to make other projects be able to leverage
> I wouldn't drop the idea because of that. In the case of the os-brick
> library, there was common code for interacting with local storage
> management in both Cinder and Nova. We recognized this and started the
> os-brick library to move that code into one place.
> Cinder started using it right away, but it was at least a couple cycles
> before Nova started looking at it. I think that's perfectly fine. If
> you are able to start a library for your own use, and it has good and
> useful common functionality, then Nova can make the decision later if
> they want to take advantage of it.
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev