Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI.
It still can not work. My local.conf is: [[post-config|\$CINDER_CONF]] [DEFAULT] enabled_backends=huawei_18000 [huawei_18000] volume_driver=cinder.volume.drivers.huawei.HuaweiVolumeDriver cinder_huawei_conf_file=/etc/cinder/cinder_huawei_conf.xml And the resulted cinder.conf is: [DEFAULT] default_volume_type = default enabled_backends = default [default] volume_group = stack-volumes-default volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver volume_backend_name = default Looks like it did not work as I expected. Is there anything I am wrong? Thanks and regards, Liu -邮件原件- 发件人: Mike Perez [mailto:thin...@gmail.com] 发送时间: 2015年1月24日 3:08 收件人: OpenStack Development Mailing List (not for usage questions) 主题: Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI. On 11:30 Fri 23 Jan , Bharat Kumar wrote: Liu, Yes, by default DevStack configures cinder with LVM. But we can customize DevStack to configure cinder with our own backend (real storage backend). Below is the link to the path, enables Automatic Configuration of GlusterFS for Cinder using devstack: https://review.openstack.org/#/c/133102/ And also below it the link to Configure CEPH with Cinder using devstack: https://review.openstack.org/#/c/65113/ Above two are old way of real storage plugin implementation. Sean Dague proposed a new way of devstack plugin implementation. Have a look at below two links: https://review.openstack.org/#/c/142805/ https://review.openstack.org/#/c/142805/7/doc/source/plugins.rst Just want to clarify that you don't have to make any changes in upstream devstack to configure devstack to use your volume driver. Information for configuring Devstack to use your driver as mentioned earlier can be found here: https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_configure_DevStack_so_my_Driver_Passes_Tempest.3F -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI.
On 09:40 Sun 25 Jan , liuxinguo wrote: It still can not work. My local.conf is: [[post-config|\$CINDER_CONF]] [DEFAULT] enabled_backends=huawei_18000 [huawei_18000] volume_driver=cinder.volume.drivers.huawei.HuaweiVolumeDriver cinder_huawei_conf_file=/etc/cinder/cinder_huawei_conf.xml And the resulted cinder.conf is: [DEFAULT] default_volume_type = default enabled_backends = default [default] volume_group = stack-volumes-default volume_driver = cinder.volume.drivers.lvm.LVMISCSIDriver volume_backend_name = default Looks like it did not work as I expected. Is there anything I am wrong? Your local.conf is missing the first line needed in local.conf: [[local|localrc]] Please reread the instructions in the Cinder thirdparty doc: https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_configure_DevStack_so_my_Driver_Passes_Tempest.3F You're also encouraged to use the third party meeting for help: https://wiki.openstack.org/wiki/Meetings/ThirdParty -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI.
On 11:30 Fri 23 Jan , Bharat Kumar wrote: Liu, Yes, by default DevStack configures cinder with LVM. But we can customize DevStack to configure cinder with our own backend (real storage backend). Below is the link to the path, enables Automatic Configuration of GlusterFS for Cinder using devstack: https://review.openstack.org/#/c/133102/ And also below it the link to Configure CEPH with Cinder using devstack: https://review.openstack.org/#/c/65113/ Above two are old way of real storage plugin implementation. Sean Dague proposed a new way of devstack plugin implementation. Have a look at below two links: https://review.openstack.org/#/c/142805/ https://review.openstack.org/#/c/142805/7/doc/source/plugins.rst Just want to clarify that you don't have to make any changes in upstream devstack to configure devstack to use your volume driver. Information for configuring Devstack to use your driver as mentioned earlier can be found here: https://wiki.openstack.org/wiki/Cinder/tested-3rdParty-drivers#How_do_I_configure_DevStack_so_my_Driver_Passes_Tempest.3F -- Mike Perez __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI.
Another ‘sample’ you can use is here: https://github.com/rasselin/os-ext-testing-data/blob/master/etc/jenkins_jobs/config/dsvm-cinder-driver.yaml.sample#L2 Ramy From: Bharat Kumar [mailto:bharat.kobag...@redhat.com] Sent: Thursday, January 22, 2015 10:01 PM To: openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI. On 01/22/2015 05:39 PM, Duncan Thomas wrote: 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 liuxin...@huawei.commailto:liuxin...@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? Liu, Yes, by default DevStack configures cinder with LVM. But we can customize DevStack to configure cinder with our own backend (real storage backend). Below is the link to the path, enables Automatic Configuration of GlusterFS for Cinder using devstack: https://review.openstack.org/#/c/133102/ And also below it the link to Configure CEPH with Cinder using devstack: https://review.openstack.org/#/c/65113/ Above two are old way of real storage plugin implementation. Sean Dague proposed a new way of devstack plugin implementation. Have a look at below two links: https://review.openstack.org/#/c/142805/ https://review.openstack.org/#/c/142805/7/doc/source/plugins.rst Thanks and regards, Liu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribehttp://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribemailto:openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Warm Regards, Bharat Kumar Kobagana Software Engineer OpenStack Storage – RedHat India Mobile - +91 9949278005 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI.
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 liuxin...@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-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Cinder][3rd CI] Confused about “*real* storage backend”requirement for 3rd CI.
On 01/22/2015 05:39 PM, Duncan Thomas wrote: 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 liuxin...@huawei.com mailto:liuxin...@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? Liu, Yes, by default DevStack configures cinder with LVM. But we can customize DevStack to configure cinder with our own backend (real storage backend). Below is the link to the path, enables Automatic Configuration of GlusterFS for Cinder using devstack: https://review.openstack.org/#/c/133102/ And also below it the link to Configure CEPH with Cinder using devstack: https://review.openstack.org/#/c/65113/ Above two are old way of real storage plugin implementation. Sean Dague proposed a new way of devstack plugin implementation. Have a look at below two links: https://review.openstack.org/#/c/142805/ https://review.openstack.org/#/c/142805/7/doc/source/plugins.rst Thanks and regards, Liu __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Duncan Thomas __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Warm Regards, Bharat Kumar Kobagana Software Engineer OpenStack Storage – RedHat India Mobile - +91 9949278005 __ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
