Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

+1 to drop nailgun-agent and replace it with python script with ohai call or ironic-inspector! On Tue, Mar 15, 2016 at 1:07 PM, Alexander Saprykin wrote: > Dear all, > > Thank you for the opinions about this problem. > > I would agree with Roman, that it is always better

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Dear all, Thank you for the opinions about this problem. I would agree with Roman, that it is always better to reuse solutions than re-inventing the wheel. We should investigate possibility of using ironic-inspector and integrating it into fuel. Best regards, Alexander Saprykin 2016-03-15

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

My strong +1 to drop off nailgun-agent completely in favour of ironic-inspector. Even taking into consideration we'lll need to extend ironic-inspector for fuel needs. -- Best regards, Sergii Golovatiuk, Skype #golserge IRC #holser On Tue, Mar 15, 2016 at 11:06 AM, Roman Prykhodchenko

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

My opition on this is that we have too many re-invented wheels in Fuel and it’s better think about replacing them with something we can re-use than re-inventing them one more time. Let’s take a look at Ironic and try to figure out how we can use its features for the same purpose. - romcheg >

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

On 15/03/16 07:11, Vladimir Kozhukalov wrote: > Alexander, > > We have many other places where use Ruby (astute, puppet custom types, > etc.). I don't think it is a good reason to re-write something just > because it is written in Ruby. You are right about tests, about plugins, > but let's look

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Alexander, We have many other places where use Ruby (astute, puppet custom types, etc.). I don't think it is a good reason to re-write something just because it is written in Ruby. You are right about tests, about plugins, but let's look around. Ironic community has already invented discovery

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Hi Alexander, thanks for bringing this up. >From your list of problems the only problem which I see is 1st, 2nd and 3rd are solvable even with current implementation. Also I don't think that we should continue developing our own HW discovery mechanism, we should consider switching to

Re: [openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

On 03/14/2016 04:13 PM, Alexander Saprykin wrote: > Hi, > > We have fuel-nailgun-agent project which was initially written on Ruby. > It is 900 lines of code single script, that collects and provides to the > nailgun information about node's hardware. > > In the past several iteration we had to

[openstack-dev] [Fuel] Rewriting nailgun agent on Python proposal

Hi, We have fuel-nailgun-agent project which was initially written on Ruby. It is 900 lines of code single script, that collects and provides to the nailgun information about node's hardware. In the past several iteration we had to introduce new modifications to that script we discovered couple