<div dir="ltr"><div><div><div>Hi,<br><br>according to [1] you should be able to use:<br><br>puppet_modules: "puppet/:/etc/puppet/<span>modules</span>/"<br><br></div>This is valid string yaml parameter that should be parsed just fine.<br><br>[1] <a href="https://github.com/stackforge/fuel-web/blob/master/tasklib/tasklib/actions/puppet.py#L61-L62">https://github.com/stackforge/fuel-web/blob/master/tasklib/tasklib/actions/puppet.py#L61-L62</a><br><br></div>Regards<br>--<br></div>Alex<br><div><div><br></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Nov 24, 2014 at 12:07 PM, Dmitry Ukov <span dir="ltr"><<a href="mailto:dukov@mirantis.com" target="_blank">dukov@mirantis.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hello All,<div>Current implementation of <span style="background:yellow"><span>plugins</span></span> in Fuel unpacks <span style="background:yellow"><span>plugin</span></span> tarball into /var/www/<span style="background:yellow"><span>nailgun</span></span>/<span style="background:yellow"><span>plugins</span></span>/.</div><div>If we implement deployment part of <span style="background:yellow"><span>plugin</span></span> using puppet there is a setting </div><div>puppet_modules:</div><div><br></div><div>This setting should specify path to modules folder. As soon as main deployment part of <span style="background:yellow"><span>plugin</span></span> is implemented as a Puppet module module path setting should be:</div><div><br></div><div>puppet_modules: puppet/</div><div><br></div><div>There is big probability that <span style="background:yellow"><span>plugin</span></span> implementation will require some custom resources and functions which are implemented in fuel-library (e.g. service <span style="background:yellow"><span>config</span></span> resources, <span style="background:yellow"><span>stdlib</span></span> functions e.t.c). So in order to use them <span style="background:yellow"><span>plugin</span></span> developer has to copy them from fuel-library into <span style="background:yellow"><span>plugin</span></span> (if <span style="background:yellow"><span>i'm</span></span> not missing something). This is not really convenient from my perspective.</div><div><br></div><div>I'd like to suggest to treat puppet_modules parameter as an array and pass it to puppet binary as</div><div># puppet apply --<span style="background:yellow"><span>modulepath</span></span>=<modulepath1>:<modulepath2></div><div>This will allow to add /etc/puppet/modules as module path and use resources and functions form fuel-library.</div><div><br></div><div>P.S.:</div><div>puppet_modules: "puppet/:/etc/puppet/<span>moules</span>/: <- is not allowed by <span>yaml</span> parser (and <span>yaml</span> format I believe)<br></div><div><br></div><div>Any suggestions here?</div><span class="HOEnZb"><font color="#888888"><div><div><br></div><div><br></div>-- <br><div>Kind regards<div><span style="background:yellow"><span>Dmitry</span></span> <span style="background:yellow"><span>Ukov</span></span></div><div>IT Engineer</div><div><div><span style="background:yellow"><span>Mirantis</span></span>, Inc.</div></div><div><br></div></div>
</div></font></span></div>
<br>_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</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></blockquote></div><br></div>