[openstack-dev] [cinder] Rebranded Volume Drivers
Nikesh Kumar Mahalka
nikeshmahalka at vedams.com
Thu Jun 11 23:51:59 UTC 2015
We now have a working CI on below patches:
@jgriffith: we will sure start to give back to community.Thanks for
pointing this out.
On Thu, Jun 4, 2015 at 1:46 PM, Alex Meade <mr.alex.meade at gmail.com> wrote:
> Agreed, I'd also like to mention that rebranded arrays may differ slightly
> in functionality as well so the CIs would need to run against a physical
> rebranded device. These differences also justify the need for letting
> rebranded drivers in.
> On Thu, Jun 4, 2015 at 4:41 PM, Mike Perez <thingee at gmail.com> wrote:
>> Sounds like the community would like CI's regardless, and I agree.
>> Just because the driver code works for one backend solution, doesn't
>> mean it's going to work with some other.
>> Lets continue with code reviews with these patches only if they have a
>> CI reporting, unless someone has a compelling reason we should not let
>> any rebranded drivers in.
>> Mike Perez
>> On Wed, Jun 3, 2015 at 10:32 AM, Mike Perez <thingee at gmail.com> wrote:
>> > There are a couple of cases  I'm seeing where new Cinder volume
>> > drivers for Liberty are rebranding other volume drivers. This involves
>> > inheriting off another volume driver's class(es) and providing some
>> > config options to set the backend name, etc.
>> > Two problems:
>> > 1) There is a thought of no CI  is needed, since you're using
>> > another vendor's driver code which does have a CI.
>> > 2) IMO another way of satisfying a check mark of being OpenStack
>> > supported and disappearing from the community.
>> > What gain does OpenStack get from these kind of drivers?
>> > Discuss.
>> >  - https://review.openstack.org/#/c/187853/
>> >  - https://review.openstack.org/#/c/187707/4
>> >  - https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers
>> > --
>> > Mike Perez
>> OpenStack Development Mailing List (not for usage questions)
>> OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> 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