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 
> 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'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,
>> 
>> On Fri, Oct 9, 2015 at 11: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:23 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 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.
>>> 
>>> 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.
>>> 
>>> 
>>> 1. https://bugs.launchpad.net/fuel/+bug/1504338 
>>> 
>>> 
>>> 
>>> - romcheg
>>> 
>>> 
>>> __
>>> 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 
>>> 
>> 
>> 
>> __
>> 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 
>> 
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

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,

On Fri, Oct 9, 2015 at 11: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:23 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 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.
>>
>> 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.
>>
>>
>> 1. https://bugs.launchpad.net/fuel/+bug/1504338
>>
>>
>> - romcheg
>>
>>
>> __
>> 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
>
>
>
> __
> 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

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 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,
>>
>> 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 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.
>>>
>>> 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.
>>>
>>>
>>> 1. https://bugs.launchpad.net/fuel/+bug/1504338
>>>
>>>
>>> - romcheg
>>>
>>>
>>>
>>> __
>>> 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
>>
>>
>>
>> __
>> 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
>
>


-- 
Vitaly Kramskikh,
Fuel UI Tech Lead,
Mirantis, Inc.
__
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

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'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,
> 
> On Fri, Oct 9, 2015 at 11: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:23 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 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.
>> 
>> 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.
>> 
>> 
>> 1. https://bugs.launchpad.net/fuel/+bug/1504338 
>> 
>> 
>> 
>> - romcheg
>> 
>> 
>> __
>> 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 
>> 
> 
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

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 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.
>
> 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.
>
>
> 1. https://bugs.launchpad.net/fuel/+bug/1504338
>
>
> - romcheg
>
>
> __
> 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

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,
> 
> 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 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.
> 
> 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.
> 
> 
> 1. https://bugs.launchpad.net/fuel/+bug/1504338 
> 
> 
> 
> - romcheg
> 
> 
> __
> 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



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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

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:23 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 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.
>>
>> 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.
>>
>>
>> 1. https://bugs.launchpad.net/fuel/+bug/1504338
>>
>>
>> - romcheg
>>
>>
>> __
>> 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
>
>
>
> __
> 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

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 > 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:23 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 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.

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.


1. https://bugs.launchpad.net/fuel/+bug/1504338


- romcheg



__
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



__
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



__
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-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 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.

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.


1. https://bugs.launchpad.net/fuel/+bug/1504338


- romcheg



signature.asc
Description: Message signed with OpenPGP using GPGMail
__
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