Hi Przemyslaw, I would be glad to be core reviewer to fuel-plugin-glusterfs as long as seems than I was only one person who push some commits to it.
On Thu, Apr 2, 2015 at 10:47 AM, Przemyslaw Kaminski <pkamin...@mirantis.com > wrote: > Since there is no reply here I have taken steps to become core reviewer > of the (orphaned) repos [1], [2], [3], [4]. > > Should anyone want to take responsibility for them please write me. > > I have also taken steps to get the fuel-qa script working and will make > sure tests pass with new manifests. I will also update manifests' > version so that there will be no deprecation warnings. > > P. > > [1] > > https://review.openstack.org/#/admin/projects/stackforge/fuel-plugin-external-glusterfs,access > [2] > > https://review.openstack.org/#/admin/projects/stackforge/fuel-plugin-group-based-policy,access > [3] > > https://review.openstack.org/#/admin/projects/stackforge/fuel-plugin-external-nfs,access > [4] > > https://review.openstack.org/#/admin/projects/stackforge/fuel-plugin-cinder-netapp,access > > On 04/01/2015 03:48 PM, Przemyslaw Kaminski wrote: > > Hello, > > > > I've been investigating bug [1] concentrating on the > > fuel-plugin-external-glusterfs. > > > > First of all: [2] there are no core reviewers for Gerrit for this repo > > so even if there was a patch to fix [1] no one could merge it. I saw > > also fuel-plugin-external-nfs -- same issue, haven't checked other > > repos. Why is this? Can we fix this quickly? > > > > Second, the plugin throws: > > > > DEPRECATION WARNING: The plugin has old 1.0 package format, this format > > does not support many features, such as plugins updates, find plugin in > > new format or migrate and rebuild this one. > > > > I don't think this is appropriate for a plugin that is listed in the > > official catalog [3]. > > > > Third, I created a supposed fix for this bug [4] and wanted to test it > > with the fuel-qa scripts. Basically I built an .fp file with > > fuel-plugin-builder from that code, set the GLUSTER_PLUGIN_PATH variable > > to point to that .fp file and then ran the > > group=deploy_ha_one_controller_glusterfs tests. The test failed [5]. > > Then I reverted the changes from the patch and the test still failed > > [6]. But installing the plugin by hand shows that it's available there > > so I don't know if it's broken plugin test or am I still missing > something. > > > > It would be nice to get some QA help here. > > > > P. > > > > [1] https://bugs.launchpad.net/fuel/+bug/1415058 > > [2] https://review.openstack.org/#/admin/groups/577,members > > [3] https://fuel-infra.org/plugins/catalog.html > > [4] https://review.openstack.org/#/c/169683/ > > [5] > > > https://www.dropbox.com/s/1mhz8gtm2j391mr/fail_error_deploy_ha_one_controller_glusterfs_simple-2015_04_01__11_39_11.tar.xz?dl=0 > > [6] > > > https://www.dropbox.com/s/ehjox554xl23xgv/fail_error_deploy_ha_one_controller_glusterfs_simple-2015_04_01__13_16_11.tar.xz?dl=0 > > > > __________________________________________________________________________ > 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