Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-11 Thread Roman Prykhodchenko
Since there are already two services Fuel Client has to interact with, I filed a bug, for using service discovery: https://bugs.launchpad.net/fuel/+bug/1504471 > 9 жовт. 2015 р. о 11:25 Roman Prykhodchenko написав(ла): > > In that case I would suggest to also use Keystone service directory for

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Roman Prykhodchenko
In that case I would suggest to also use Keystone service directory for discovering services. > 9 жовт. 2015 р. о 11:00 Evgeniy L написав(ла): > > >> 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. > > I don'

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Vitaly Kramskikh
+1, that would allow to install plugins from Fuel UI 2015-10-09 15:53 GMT+07:00 Sergii Golovatiuk : > +1 to Roman. > > -- > Best regards, > Sergii Golovatiuk, > Skype #golserge > IRC #holser > > On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko > wrote: > >> I’d say even if it will be a separ

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Evgeniy L
>> 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. I don't think that application such as Nailgun should be responsible for proxying requests, we solved similar problem for OSTF with adding proxy rule in Nginx. Thanks

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Andriy Popovych
Actually it's an old issue https://blueprints.launchpad.net/fuel/+spec/plugin-manager-as-separate-service On 10/09/2015 11:53 AM, Sergii Golovatiuk wrote: +1 to Roman. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko mailto:m

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Sergii Golovatiuk
+1 to Roman. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Fri, Oct 9, 2015 at 10:45 AM, Roman Prykhodchenko wrote: > 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. > > 9 жовт. 2015 р. о 10:2

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Roman Prykhodchenko
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. > 9 жовт. 2015 р. о 10:23 Evgeniy L написав(ла): > > Hi, > > +1, but I think it's better to spawn separate service, instead of adding it > to Nailgun. > > Thanks, >

Re: [openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-09 Thread Evgeniy L
Hi, +1, but I think it's better to spawn separate service, instead of adding it to Nailgun. Thanks, On Fri, Oct 9, 2015 at 1:40 AM, Roman Prykhodchenko wrote: > Folks, > > it’s time to speak about Fuel Plugins and the way they are managed. > > Currently we have some methods in Fuel Client that

[openstack-dev] [Fuel] Plugins related functionality in Fuel Client

2015-10-08 Thread Roman Prykhodchenko
Folks, it’s time to speak about Fuel Plugins and the way they are managed. 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