Open Stack

Please take a look at
https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers to learn how
to configure devstack to use your driver rather than LVM.

On 22 January 2015 at 13:28, liuxinguo <liuxinguo at huawei.com> wrote:

>  Hi Mike,
>
>
>
> I received a email named “All Cinder Drivers Must Have a Third Party CI
> By March 19th 2015” and I feel confused about the “*real* storage backend”
> .
>
>
>
> One of the requirements is: Run Tempest [5][6] volume tests against the
> devstack environment that's hooked up to your *real* storage backend.
>
>
>
> ·         And my confusion is:
>
> ·         Every time the CI is triggered by a newly came patch, the 3rd
> CI will build a new devstack environment and create a default cinder.conf
> file whick will set the backend to “lvmdriver-1” automatically. And the
> tempest will run against “lvmdriver-1”. So what’s the meaning for a *real*
> storage backend since the cinder.conf will be set to use “lvmdriver-1”
> automatically for every newly came patch ? And how should I configure the
> cinder.conf file to run the tempest for the newly came driver patch came
> from different venders since different venders need different configuration
> for cinder.conf file and need different storage backend. I mean, does our
> CI should run tempest against our *real* storage backend for every newly
> came driver patch in cinder?
>
>
>
> Thanks and regards,
>
> Liu
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 
Duncan Thomas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150122/e64740af/attachment.html>