Open Stack

Yea, option #2 is what I had in mind. Like you said, I think most of
the code is already present in Ironic, and if it's not already
factored into a reusable thing (eg, ironic/utils or
ironic/driver/utils or such) then it should be.

Cheers,
-Deva

On Tue, Apr 14, 2015 at 1:40 PM, Dmitry Tantsur <divius.inside at gmail.com> wrote:
> Hi,
>
> actually 2 possibilities here:
> 1. discoverd itself handles TFTP
> 2. DiscoverdInspect hanldes TFTP
>
> 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!
>
> Dmitry
>
>
> 2015-04-14 22:27 GMT+02:00 Devananda van der Veen <devananda.vdv at gmail.com>:
>>
>> I'm wondering.... Rather than have a static config, could the
>> DiscoverdInspect interface handle setting up the TFTP config, pulling
>> those images from Glance, etc, when a node is moved into the "inspect"
>> state (assuming such integration was desired by the cloud operator)?
>>
>> -Deva
>>
>> On Fri, Apr 10, 2015 at 12:31 AM, Dmitry Tantsur <dtantsur at redhat.com>
>> wrote:
>> > On 04/10/2015 01:43 AM, Jaromir Coufal wrote:
>> >>
>> >> Hey Dmitry,
>> >
>> >
>> > o/
>> >
>> >>
>> >> I wanted to ask you about ironic-discoverd.
>> >>
>> >> At the moment, after build, the discovery images are copied into local
>> >> folder:
>> >>
>> >> TFTP_ROOT=${TFTP_ROOT:-/tftpboot}
>> >>
>> >> sudo cp -f "$IMAGE_PATH/$DISCOVERY_NAME.kernel"
>> >> "$TFTP_ROOT/discovery.kernel"
>> >> sudo cp -f "$IMAGE_PATH/$DISCOVERY_NAME.initramfs"
>> >> "$TFTP_ROOT/discovery.ramdisk"
>> >>
>> >> I am wondering why is that and if discoverd can work with these images
>> >> if they were loaded into glance.
>> >
>> >
>> > Discoverd is not concerned with TFTP configuration (unlike Ironic), so
>> > you
>> > can put them everywhere, provided that your TFTP still works. Currently
>> > we
>> > use static configuration, as it's the easiest one.
>> >
>> >
>> >> I mean it would be definitely more
>> >> convenient than keeping them locally.
>> >>
>> >> Thanks
>> >> -- Jarda
>> >
>> >
>> >
>> >
>> > __________________________________________________________________________
>> > OpenStack Development Mailing List (not for usage questions)
>> > Unsubscribe:
>> > OpenStack-dev-request at 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-request at lists.openstack.org?subject:unsubscribe
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
>
>
> --
> --
> -- Dmitry Tantsur
> --
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>