<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Mar 17, 2016 at 3:16 PM, Dmitry Tantsur <span dir="ltr"><<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On 03/16/2016 01:39 PM, Evgeniy L wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Dmitry,<br>
<br>
I can try to provide you description on what current Nailgun agent is,<br>
and what are potential requirements we may need from HW discovery system.<br>
<br>
Nailgun agent is a one-file Ruby script [0] which is periodically run<br>
under cron. It collects information about HW using ohai [1], plus it<br>
does custom parsing, filtration, retrieval of HW information. After the<br>
information is collected, it is sent to Nailgun, that is how node gets<br>
discovered in Fuel.<br>
</blockquote>
<br></span>
Quick clarification: does it run on user instances? or does it run on hardware while it's still not deployed to? The former is something that Ironic tries not to do. There is an interest in the latter.</blockquote><div><br></div><div>Both, on user instances (with deployed OpenStack) and on instances which are not deployed and in bootstrap.</div><div>What are the reasons Ironic tries not to do that (running HW discovery on deployed node)?</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
To summarise entire process:<br>
1. After Fuel master node is installed, user restarts the nodes and they<br>
get booted via PXE with bootstrap image.<br>
2. Inside of bootstrap image Nailgun agent is configured and installed.<br>
3. Cron runs Nailgun agent.<br>
3. Information is collected by Nailgun agent.<br>
4. Information is sent to Nailgun.<br>
5. Nailgun creates new node, for which user using UI can define<br>
partitioning schema and networks allocation.<br>
6. After that provisioning/deployment can be run.<br>
</blockquote>
<br></span>
So it looks quite similar to ironic-inspector + IPA, except introspection runs once. Rerunning it would not be impossible to implement, though it will require some changes to inspector, so that it can accept "updates" to a node after the introspection is finished.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Every time Nailgun agent sends a request, we submit information about<br>
the time last request from agent was done, if there was no request for<br>
time N, we mark the node as offline.<br>
</blockquote>
<br></span>
This is similar to IPA heartbeating, I guess.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
With current implementation we have several problems (not all of them<br>
should be addressed by HW discovery system only):<br>
<br>
1. A lot of things are hardcoded on the agent's side, which does<br>
additional filtration based on pre-hardcoded parameters [2], the less<br>
hardcoded logic in agent we have the easier it's to do upgrades and<br>
deliver fixes (upgrade one service is simpler than hundreds of agents).<br>
</blockquote>
<br></span>
Oh, I hear it. In the inspector world we are moving away from processing things on the ramdisk side exactly for this reason: it's too hard to change.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
2. In order to get additional HW information user has to continue<br>
hardcoding it right in Ruby code, as the result, there is no way for<br>
Fuel plugin [3], to get additional hardware specific information, we<br>
need data-driven mechanism to be able to describe, what/how/where<br>
information to get from the node.<br>
</blockquote>
<br></span>
Hmm, interesting. Right now we have a plugin mechanism for the ramdisk. We also have a plugin (extra-hardware) trying to collect as much information as it's feasible (based on <a href="https://github.com/redhat-cip/hardware" rel="noreferrer" target="_blank">https://github.com/redhat-cip/hardware</a>).<br></blockquote><div><br></div><div>Could you please provide a link where I can learn more on plugin mechanism for ramdisk?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
On the other side, there is ongoing work to have an ansible-based deploy ramdisk in Ironic, maybe inspector could benefit from it too. Didn't think about it yet, would be interesting to discuss on the summit.</blockquote><div><br></div><div>And here, I would appreciate if you have any link to get more context (I was able to find only playbook for Ironic installation).</div><div>In Fuel we had an idea to implement tasks (abstract from specific deployment tool) to make configuration and get information about specific hardware.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
3. Hardware gets changed, we have cases when NICs, HDDs, Motherboards<br>
are replaced/removed/added, as the result we should have a tool which<br>
would allow us to see these changes and when they were performed, based<br>
on that we want to be able to notify the user and provide suggestions<br>
how to proceed with these changes.<br>
</blockquote>
<br></span>
This could probably done with a new ironic-inspector plugin.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
4. With 3rd real-world cases, we have a problem of node identification,<br>
when HW gets changed and automatic matching doesn't happen (when we<br>
cannot say for sure that this is the node which we've already had), user<br>
should be able to say, that new node X is in fact offline node Y.<br>
</blockquote>
<br></span>
Very good question. Right now Inspector is using either BMC IP address or MAC's.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
5. Different source of HW information, we want to have a system which<br>
would allow us to have hardware discovery from IPMI, CSV file, Cobbler,<br>
CMDB, etc at the same time.<br>
</blockquote>
<br></span>
Not sure something like that should live within Ironic to be honest. Also worth discussing in details.<span><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
6. Not only hardware gets changed, but operating system (with kernel<br>
versions), for example when we used CentOS as a bootstrap (in bootstrap<br>
we do provisioning/partitioning + initial configuration) and Ubuntu for<br>
running OpenStack, we were getting wide range of weird problems, from<br>
NICs renaming to Disks' ids duplication and deduplication. There should<br>
be a way to track these problems (3rd item), and we should be able to<br>
add operating system specific system to get HW information.<br>
<br>
7. Cron + Agent based mechanism to define if node is offline is not the<br>
best, since it adds race conditions and in fact it only says if there is<br>
connectivity between Nailgun and Nailgun agent.<br>
</blockquote>
<br></span>
We are thinking about using some DLM for that.. No specific plans though, again a topic for the summit.<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
<br>
Will be glad to answer any questions you have, if there are any.<br>
<br>
Thanks,<br>
<br>
[0] <a href="https://github.com/openstack/fuel-nailgun-agent/blob/master/agent" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-nailgun-agent/blob/master/agent</a><br>
[1] <a href="https://docs.chef.io/ohai.html" rel="noreferrer" target="_blank">https://docs.chef.io/ohai.html</a><br>
[2]<br>
<a href="https://github.com/openstack/fuel-nailgun-agent/blob/master/agent#L46-L51" rel="noreferrer" target="_blank">https://github.com/openstack/fuel-nailgun-agent/blob/master/agent#L46-L51</a><br>
[3] <a href="https://wiki.openstack.org/wiki/Fuel/Plugins" rel="noreferrer" target="_blank">https://wiki.openstack.org/wiki/Fuel/Plugins</a><br>
<br>
<br>
On Wed, Mar 16, 2016 at 1:39 PM, Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a><br></span><span>
<mailto:<a href="mailto:dtantsur@redhat.com" target="_blank">dtantsur@redhat.com</a>>> wrote:<br>
<br>
On 03/15/2016 01:53 PM, Serge Kovaleff wrote:<br>
<br>
Dear All,<br>
<br>
Let's compare functional abilities of both solutions.<br>
<br>
Till the recent Mitaka release Ironic-inspector had only<br>
Introspection<br>
ability.<br>
<br>
Discovery part is proposed and implemented by Anton Arefiev. We<br>
should<br>
align expectations and current and future functionality.<br>
<br>
Adding Tags to attract the Inspector community.<br>
<br>
<br>
Hi!<br>
<br>
It would be great to see what we can do to fit the nailgun use case.<br>
Unfortunately, I don't know much about it right now. What are you<br>
missing?<br>
<br>
<br>
Cheers,<br>
Serge Kovaleff<br>
<a href="http://www.mirantis.com" rel="noreferrer" target="_blank">http://www.mirantis.com</a> <<a href="http://www.mirantis.com/" rel="noreferrer" target="_blank">http://www.mirantis.com/</a>><br>
cell: +38 (063) 83-155-70<br>
<br>
On Tue, Mar 15, 2016 at 2:07 PM, Alexander Saprykin<br>
<<a href="mailto:asaprykin@mirantis.com" target="_blank">asaprykin@mirantis.com</a> <mailto:<a href="mailto:asaprykin@mirantis.com" target="_blank">asaprykin@mirantis.com</a>><br></span>
<mailto:<a href="mailto:asaprykin@mirantis.com" target="_blank">asaprykin@mirantis.com</a> <mailto:<a href="mailto:asaprykin@mirantis.com" target="_blank">asaprykin@mirantis.com</a>>>><span><br>
wrote:<br>
<br>
Dear all,<br>
<br>
Thank you for the opinions about this problem.<br>
<br>
I would agree with Roman, that it is always better to reuse<br>
solutions than re-inventing the wheel. We should investigate<br>
possibility of using ironic-inspector and integrating it<br>
into fuel.<br>
<br>
Best regards,<br>
Alexander Saprykin<br>
<br>
2016-03-15 13:03 GMT+01:00 Sergii Golovatiuk<br>
<<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a> <mailto:<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>><br></span>
<mailto:<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a><span><br>
<mailto:<a href="mailto:sgolovatiuk@mirantis.com" target="_blank">sgolovatiuk@mirantis.com</a>>>>:<br>
<br>
My strong +1 to drop off nailgun-agent completely in<br>
favour of<br>
ironic-inspector. Even taking into consideration we'lll<br>
need to<br>
extend ironic-inspector for fuel needs.<br>
<br>
--<br>
Best regards,<br>
Sergii Golovatiuk,<br>
Skype #golserge<br>
IRC #holser<br>
<br>
On Tue, Mar 15, 2016 at 11:06 AM, Roman Prykhodchenko<br>
<<a href="mailto:me@romcheg.me" target="_blank">me@romcheg.me</a> <mailto:<a href="mailto:me@romcheg.me" target="_blank">me@romcheg.me</a>><br></span><span>
<mailto:<a href="mailto:me@romcheg.me" target="_blank">me@romcheg.me</a> <mailto:<a href="mailto:me@romcheg.me" target="_blank">me@romcheg.me</a>>>> wrote:<br>
<br>
My opition on this is that we have too many re-invented<br>
wheels in Fuel and it’s better think about<br>
replacing them<br>
with something we can re-use than re-inventing them<br>
one more<br>
time.<br>
<br>
Let’s take a look at Ironic and try to figure out<br>
how we can<br>
use its features for the same purpose.<br>
<br>
<br>
- romcheg<br>
> 15 бер. 2016 р. о 10:38 Neil Jerram<br>
<<a href="mailto:Neil.Jerram@metaswitch.com" target="_blank">Neil.Jerram@metaswitch.com</a><br>
<mailto:<a href="mailto:Neil.Jerram@metaswitch.com" target="_blank">Neil.Jerram@metaswitch.com</a>><br></span>
<mailto:<a href="mailto:Neil.Jerram@metaswitch.com" target="_blank">Neil.Jerram@metaswitch.com</a><div><div><br>
<mailto:<a href="mailto:Neil.Jerram@metaswitch.com" target="_blank">Neil.Jerram@metaswitch.com</a>>>> написав(ла):<br>
<br>
><br>
> On 15/03/16 07:11, Vladimir Kozhukalov wrote:<br>
>> Alexander,<br>
>><br>
>> We have many other places where use Ruby<br>
(astute, puppet<br>
custom types,<br>
>> etc.). I don't think it is a good reason to<br>
re-write<br>
something just<br>
>> because it is written in Ruby. You are right about<br>
tests, about plugins,<br>
>> but let's look around. Ironic community has already<br>
invented discovery<br>
>> component (btw written in python) and I can't<br>
see any<br>
reason why we<br>
>> should continue putting efforts in nailgun<br>
agent and not<br>
try to switch<br>
>> to ironic-inspector.<br>
><br>
> +1 in general terms. It's strange to me that<br>
there are<br>
so many<br>
> OpenStack deployment systems that each do each<br>
piece of<br>
the puzzle in<br>
> their own way (Fuel, Foreman, MAAS/Juju etc.) -<br>
and which<br>
also means<br>
> that I need substantial separate learning in<br>
order to use<br>
all these<br>
> systems. It would be great to see some<br>
consolidation.<br>
><br>
> Regards,<br>
> Neil<br>
><br>
><br>
><br>
<br>
__________________________________________________________________________<br>
> OpenStack Development Mailing List (not for<br>
usage questions)<br>
> Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage<br>
questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage<br>
questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe:<br>
<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<<a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a>><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
<br>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
</div></div></blockquote><div><div>
<br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br></div></div>