[openstack-dev] [OpenStack-Dev] [Cinder] Cinder driver verification

Avishay Traeger AVISHAY at il.ibm.com
Thu Feb 13 17:51:45 UTC 2014


"Walter A. Boring IV" <walter.boring at hp.com> wrote on 02/13/2014 06:59:38 
PM:
> What I would do different for the Icehouse release is this:
> 
> If a driver doesn't pass the certification test by IceHouse RC1, then we 

> have a bug filed
> against the driver.   I would also put a warning message in the log for 
> that driver that it
> doesn't pass the certification test.  I would not remove it from the 
> codebase.
> 
> Also:
>     if a driver hasn't even run the certification test by RC1, then we 
> mark the driver as
> uncertified and deprecated in the code and throw an error at driver init 

> time.
> We can have a option in cinder.conf that says 
> ignore_uncertified_drivers=False.
> If an admin wants to ignore the error, they set the flag to True, and we 

> let the driver init at next startup.
> The admin then takes full responsibility for running uncertified code.
> 
>    I think removing the drivers outright is premature for Icehouse, 
> since the certification process is a new thing.
> For Juno, we remove any drivers that are still marked as uncertified and 

> haven't run the tests.
> 
> I think the purpose of the tests is to get vendors to actually run their 

> code through tempest and
> prove to the community that they are willing to show that they are 
> fixing their code.  At the end of the day,
> it better serves the community and Cinder if we have many working 
drivers.
> 
> My $0.02,
> Walt


I like this.  Make that $0.04 now :)

Avishay




More information about the OpenStack-dev mailing list