<div dir="ltr"><div><div><div><div><div>Hi,<br><br></div>actually 2 possibilities here:<br></div>1. discoverd itself handles TFTP<br></div>2. DiscoverdInspect hanldes TFTP<br><br></div>I vote for the 2nd, as we have all required code in Ironic already. I guess initial question was about the 1st case, which I doubt is worth supporting. Anyway, nice idea for an improvement!<br><br></div>Dmitry<br><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">2015-04-14 22:27 GMT+02:00 Devananda van der Veen <span dir="ltr"><<a href="mailto:devananda.vdv@gmail.com" target="_blank">devananda.vdv@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'm wondering.... Rather than have a static config, could the<br>
DiscoverdInspect interface handle setting up the TFTP config, pulling<br>
those images from Glance, etc, when a node is moved into the "inspect"<br>
state (assuming such integration was desired by the cloud operator)?<br>
<br>
-Deva<br>
<div class="HOEnZb"><div class="h5"><br>
On Fri, Apr 10, 2015 at 12:31 AM, Dmitry Tantsur <<a href="mailto:dtantsur@redhat.com">dtantsur@redhat.com</a>> wrote:<br>
> On 04/10/2015 01:43 AM, Jaromir Coufal wrote:<br>
>><br>
>> Hey Dmitry,<br>
><br>
><br>
> o/<br>
><br>
>><br>
>> I wanted to ask you about ironic-discoverd.<br>
>><br>
>> At the moment, after build, the discovery images are copied into local<br>
>> folder:<br>
>><br>
>> TFTP_ROOT=${TFTP_ROOT:-/tftpboot}<br>
>><br>
>> sudo cp -f "$IMAGE_PATH/$DISCOVERY_NAME.kernel"<br>
>> "$TFTP_ROOT/discovery.kernel"<br>
>> sudo cp -f "$IMAGE_PATH/$DISCOVERY_NAME.initramfs"<br>
>> "$TFTP_ROOT/discovery.ramdisk"<br>
>><br>
>> I am wondering why is that and if discoverd can work with these images<br>
>> if they were loaded into glance.<br>
><br>
><br>
> Discoverd is not concerned with TFTP configuration (unlike Ironic), so you<br>
> can put them everywhere, provided that your TFTP still works. Currently we<br>
> use static configuration, as it's the easiest one.<br>
><br>
><br>
>> I mean it would be definitely more<br>
>> convenient than keeping them locally.<br>
>><br>
>> Thanks<br>
>> -- Jarda<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" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
<br>
__________________________________________________________________________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div>--<br></div>-- Dmitry Tantsur<br><div>--<br></div></div></div>
</div>