<div dir="ltr"><div>I've just print tree with hidden files, so actually it's ok with fpb:<br><br><span style="font-family:monospace,monospace">root@55725ffa6e80:~# tree -a test/<br>test/<br>|-- .gitignore<br>|-- LICENSE<br>|-- README.md<br>|-- deployment_scripts<br>| `-- deploy.sh<br>|-- environment_config.yaml<br>|-- metadata.yaml<br>|-- pre_build_hook<br><b>|-- repositories<br>| |-- centos<br>| | `-- .gitkeep<br>| `-- ubuntu<br>| `-- .gitkeep<br></b>`-- tasks.yaml</span><br><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-04-02 17:01 GMT+03:00 Przemyslaw Kaminski <span dir="ltr"><<a href="mailto:pkaminski@mirantis.com" target="_blank">pkaminski@mirantis.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Well then either we need to fix fuel-plugin-builder to accept such<br>
situations.<br>
<br>
Actually it is an issue with fpb since git does not accepty empty<br>
directories [1] so pulling fresh from such repo will result in<br>
'repositories' dir missing even when the developer had it.<br>
<br>
I hope no files were accidentaly forgotten during commit there?<br>
<br>
P.<br>
<br>
[1]<br>
<a href="http://stackoverflow.com/questions/115983/how-can-i-add-an-empty-directory-to-a-git-repository" target="_blank">http://stackoverflow.com/questions/115983/how-can-i-add-an-empty-directory-to-a-git-repository</a><br>
<span class=""><br>
On 04/02/2015 03:46 PM, Sergey Kulanov wrote:<br>
> Hi, Przemyslaw<br>
><br>
> 1) There should be two repositories folders. Please check the correct<br>
> structure (marked with bold):<br>
> mkdir -p repositories/{ubuntu,centos}<br>
><br>
><br>
> root@55725ffa6e80:~/fuel-plugin-cinder-netapp# tree<br>
> .<br>
> |-- LICENSE<br>
> |-- README.md<br>
> |-- cinder_netapp-1.0.0.fp<br>
> |-- deployment_scripts<br>
> | |-- puppet<br>
> | | `-- plugin_cinder_netapp<br>
> | | `-- manifests<br>
> | | `-- init.pp<br>
> | `-- site.pp<br>
> |-- environment_config.yaml<br>
> |-- metadata.yaml<br>
> |-- pre_build_hook<br>
</span>> *|-- repositories<br>
> | |-- centos<br>
> | `-- ubuntu<br>
> *`-- tasks.yaml<br>
<span class="">><br>
> Then you can build the plugin.<br>
><br>
> 2) Actually, this should not be the issue while creating plugins from<br>
> scratch using fpb tool itself [1]:<br>
><br>
> fpb --create test<br>
><br>
> root@55725ffa6e80:~# tree test<br>
> test<br>
> |-- LICENSE<br>
> |-- README.md<br>
> |-- deployment_scripts<br>
> | `-- deploy.sh<br>
> |-- environment_config.yaml<br>
> |-- metadata.yaml<br>
> |-- pre_build_hook<br>
> |-- repositories<br>
> | |-- centos<br>
> | `-- ubuntu<br>
> `-- tasks.yaml<br>
><br>
><br>
><br>
> [1]. <a href="https://pypi.python.org/pypi/fuel-plugin-builder/1.0.2" target="_blank">https://pypi.python.org/pypi/fuel-plugin-builder/1.0.2</a><br>
><br>
><br>
> 2015-04-02 16:30 GMT+03:00 Przemyslaw Kaminski <<a href="mailto:pkaminski@mirantis.com">pkaminski@mirantis.com</a><br>
</span>> <mailto:<a href="mailto:pkaminski@mirantis.com">pkaminski@mirantis.com</a>>>:<br>
<div><div class="h5">><br>
> Investigating the cinder-netapp plugin [1] (a 'certified' one) shows<br>
> fuel-plugin-build error:<br>
><br>
> (fuel)vagrant@ubuntu-14:/sources/fuel-plugin-cinder-netapp$ fpb --build<br>
> .<br>
><br>
><br>
> Unexpected error<br>
> Cannot find directories ./repositories/ubuntu for release<br>
> "{'repository_path': 'repositories/ubuntu', 'version': '2014.2-6.0',<br>
> 'os': 'ubuntu', 'mode': ['ha', 'multinode'], 'deployment_scripts_path':<br>
> 'deployment_scripts/'}"<br>
> (fuel)vagrant@ubuntu-14:/sources/fuel-plugin-cinder-netapp$ ls<br>
> deployment_scripts environment_config.yaml LICENSE metadata.yaml<br>
> pre_build_hook README.md tasks.yaml<br>
> (fuel)vagrant@ubuntu-14:/sources/fuel-plugin-cinder-netapp$ ag<br>
> 'repositories'<br>
> metadata.yaml<br>
> 18: repository_path: repositories/ubuntu<br>
> 23: repository_path: repositories/centos<br>
><br>
> Apparently some files are missing from the git repo or the manifest is<br>
> incorrect. Does anyone know something about this?<br>
><br>
> P.<br>
><br>
> [1] <a href="https://github.com/stackforge/fuel-plugin-cinder-netapp" target="_blank">https://github.com/stackforge/fuel-plugin-cinder-netapp</a><br>
><br>
> On 04/01/2015 03:48 PM, Przemyslaw Kaminski wrote:<br>
> > Hello,<br>
> ><br>
> > I've been investigating bug [1] concentrating on the<br>
> > fuel-plugin-external-glusterfs.<br>
> ><br>
> > First of all: [2] there are no core reviewers for Gerrit for this repo<br>
> > so even if there was a patch to fix [1] no one could merge it. I saw<br>
> > also fuel-plugin-external-nfs -- same issue, haven't checked other<br>
> > repos. Why is this? Can we fix this quickly?<br>
> ><br>
> > Second, the plugin throws:<br>
> ><br>
> > DEPRECATION WARNING: The plugin has old 1.0 package format, this<br>
> format<br>
> > does not support many features, such as plugins updates, find<br>
> plugin in<br>
> > new format or migrate and rebuild this one.<br>
> ><br>
> > I don't think this is appropriate for a plugin that is listed in the<br>
> > official catalog [3].<br>
> ><br>
> > Third, I created a supposed fix for this bug [4] and wanted to test it<br>
> > with the fuel-qa scripts. Basically I built an .fp file with<br>
> > fuel-plugin-builder from that code, set the GLUSTER_PLUGIN_PATH<br>
> variable<br>
> > to point to that .fp file and then ran the<br>
> > group=deploy_ha_one_controller_glusterfs tests. The test failed [5].<br>
> > Then I reverted the changes from the patch and the test still failed<br>
> > [6]. But installing the plugin by hand shows that it's available there<br>
> > so I don't know if it's broken plugin test or am I still missing<br>
> something.<br>
> ><br>
> > It would be nice to get some QA help here.<br>
> ><br>
> > P.<br>
> ><br>
> > [1] <a href="https://bugs.launchpad.net/fuel/+bug/1415058" target="_blank">https://bugs.launchpad.net/fuel/+bug/1415058</a><br>
> > [2] <a href="https://review.openstack.org/#/admin/groups/577,members" target="_blank">https://review.openstack.org/#/admin/groups/577,members</a><br>
> > [3] <a href="https://fuel-infra.org/plugins/catalog.html" target="_blank">https://fuel-infra.org/plugins/catalog.html</a><br>
> > [4] <a href="https://review.openstack.org/#/c/169683/" target="_blank">https://review.openstack.org/#/c/169683/</a><br>
> > [5]<br>
> ><br>
> <a href="https://www.dropbox.com/s/1mhz8gtm2j391mr/fail_error_deploy_ha_one_controller_glusterfs_simple-2015_04_01__11_39_11.tar.xz?dl=0" target="_blank">https://www.dropbox.com/s/1mhz8gtm2j391mr/fail_error_deploy_ha_one_controller_glusterfs_simple-2015_04_01__11_39_11.tar.xz?dl=0</a><br>
> > [6]<br>
> ><br>
> <a href="https://www.dropbox.com/s/ehjox554xl23xgv/fail_error_deploy_ha_one_controller_glusterfs_simple-2015_04_01__13_16_11.tar.xz?dl=0" target="_blank">https://www.dropbox.com/s/ehjox554xl23xgv/fail_error_deploy_ha_one_controller_glusterfs_simple-2015_04_01__13_16_11.tar.xz?dl=0</a><br>
> ><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe:<br>
> <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
</div></div>> <<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<div class="HOEnZb"><div class="h5">> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
><br>
><br>
><br>
> --<br>
> Sergey<br>
> DevOps Engineer<br>
> IRC: SergK<br>
> Skype: Sergey_kul<br>
><br>
><br>
> __________________________________________________________________________<br>
> OpenStack Development Mailing List (not for usage questions)<br>
> Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><big><big><span style="font-size:13px">Sergey<br></span></big></big><font size="1"><span>DevOps Engineer <br></span><span>IRC: SergK<br></span><span>Skype: Sergey_kul</span></font></div></div></div></div>
</div>