<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">In that case I would suggest to also use Keystone service directory for discovering services.<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">9 жовт. 2015 р. о 11:00 Evgeniy L <<a href="mailto:eli@mirantis.com" class="">eli@mirantis.com</a>> написав(ла):</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">>> <span style="font-size:12.8px" class="">I’d say even if it will be a separate service it’s better to proxy requests through Nailgun’s API to have a single entry point.</span><div class=""><span style="font-size:12.8px" class=""><br class=""></span></div><div class=""><span style="font-size:12.8px" class="">I don't think that application such as Nailgun should be responsible for proxying</span></div><div class=""><span style="font-size:12.8px" class="">requests, we solved similar problem </span><span style="font-size:12.8px" class="">for OSTF with adding proxy rule in Nginx.</span></div><div class=""><span style="font-size:12.8px" class=""><br class=""></span></div><div class=""><span style="font-size:12.8px" class="">Thanks,</span></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Oct 9, 2015 at 11:45 AM, Roman Prykhodchenko <span dir="ltr" class=""><<a href="mailto:me@romcheg.me" target="_blank" class="">me@romcheg.me</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class="">I’d say even if it will be a separate service it’s better to proxy requests through Nailgun’s API to have a single entry point.<div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">9 жовт. 2015 р. о 10:23 Evgeniy L <<a href="mailto:eli@mirantis.com" target="_blank" class="">eli@mirantis.com</a>> написав(ла):</div><div class=""><div class="h5"><br class=""><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">+1, but I think it's better to spawn separate service, instead of adding it to Nailgun.</div><div class=""><br class=""></div><div class="">Thanks,</div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Oct 9, 2015 at 1:40 AM, Roman Prykhodchenko <span dir="ltr" class=""><<a href="mailto:me@romcheg.me" target="_blank" class="">me@romcheg.me</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Folks,<br class="">
<br class="">
it’s time to speak about Fuel Plugins and the way they are managed.<br class="">
<br class="">
Currently we have some methods in Fuel Client that allow to install, remove and do some other things to plugins. Everything looks great except that functionality requires Fuel Client to be installed on a master node and be running under a root user. It’s time for us to grow up and realize that nothing can require Fuel Client to be installed on a specific computer and of course we cannot require root permissions for any actions.<br class="">
<br class="">
I’d like to move all that code to Nailgun, utilizing mules and hide it behind Nailgun’s API as soon as possible. For that I filed a bug [1] and I’d like to ask Fuel Enhancements subgroup of developers to take a close look at it.<br class="">
<br class="">
<br class="">
1. <a href="https://bugs.launchpad.net/fuel/+bug/1504338" rel="noreferrer" target="_blank" class="">https://bugs.launchpad.net/fuel/+bug/1504338</a><br class="">
<br class="">
<br class="">
- romcheg<br class="">
<br class="">
<br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" target="_blank" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></div></div></blockquote></div><br class=""></div></div><br class="">__________________________________________________________________________<br class="">
OpenStack Development Mailing List (not for usage questions)<br class="">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org/?subject:unsubscribe" rel="noreferrer" target="_blank" class="">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="">
<br class=""></blockquote></div><br class=""></div>
__________________________________________________________________________<br class="">OpenStack Development Mailing List (not for usage questions)<br class="">Unsubscribe: <a href="mailto:OpenStack-dev-request@lists.openstack.org" class="">OpenStack-dev-request@lists.openstack.org</a>?subject:unsubscribe<br class=""><a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class=""></div></blockquote></div><br class=""></div></body></html>