OpenStack image

[Matthew Dillon]

Ok, I'm going to have to do this differently.  I can't synchronize
FreeBSD's dhclient app because it has diverged from both OpenBSD and
DragonFly's dhclient massively.  All three have features that the others
don't have.

What I have done instead is attempted to port the RFC 3442 support from the
FreeBSD dhclient into ours.  I have committed this to our master branch and
a snapshot image should automatically generate overnight, which you will be
able to find here.  It will be dated June 3rd or later when it generates.
Or you can compile it manually if you already have DragonFly running
somewhere.  It will need testing.

http://mirror-master.dragonflybsd.org/snapshots/x86_64/

-Matt


On Fri, Jun 2, 2017 at 9:58 AM, Matthew Dillon <dillon at backplane.com> wrote:

> Well, no particular plans but it looks like we may be able to synchronize
> the dhclient program from FreeBSD without too much trouble.   I'm assuming
> that FreeBSD does work for you?  It seems to have RFC3442 support.
>
> -Matt
>
> On Fri, Jun 2, 2017 at 9:12 AM, Christian Böhme <christian.boehme@
> cloudandheat.com> wrote:
>
>> Hello all,
>>
>> our company would like to offer DragonFly BSD as a guest operating system
>> in our OpenStack installations.
>>
>> However, our efforts so far to make such an image ourselves have failed,
>> because the ISC DHCP client version shipped with the current DragonFly BSD
>> release available from https://www.dragonflybsd.org/download/
>> (MD5 (dfly-x86_64-4.8.0_REL.iso) = e6811893c02e99ca7dd8f3c1d6e92ae3)
>> does not seem to support the  classless-static-routes  DHCP option
>> (RFC 3442), which is needed by the guest in each OpenStack VM in order
>> for it to locate the OpenStack compute metadata service, the latter
>> providing the guest with all the instance-specific information and
>> prerequisites to have it accessed remotely by the user.
>>
>> Are there any plans to upgrade to a DHCP client supporting RFC 3442 or,
>> better yet, provide an OpenStack image?
>>
>>
>> Best Regards,
>> Christian Böhme
>>
>> --
>>
>> Developer Systemintegration
>>
>> CLOUD&HEAT
>> The Cloud that heats homes worldwide
>>
>> Firmen- und Rechnungsanschrift:
>> CLOUD & HEAT Technologies GmbH
>>
>> Zeitenströmung
>> Königsbrücker Str. 96 - Halle 15
>> 01099 Dresden, Germany
>>
>> Lieferanschrift Produktion:
>> CLOUD & HEAT Technologies GmbH
>>
>> Zeitenströmung
>> Königsbrücker Str. 96 - Halle 16A
>> 01099 Dresden, Germany
>>
>> Tel: +49 351 479 3670-202
>> Fax: +49 351 479 3670-110
>>
>> E-Mail: christian.boehme at cloudandheat.com <mailto:christian.boehme at cloud
>> andheat.com>
>> Web: https://www.cloudandheat.com
>>
>> Besuchen Sie uns:
>> Facebook <https://www.facebook.com/CloudandHeat>
>> Google+ <https://plus.google.com/+Cloudandheat>
>> LinkedIn <https://www.linkedin.com/company/cloud-&-heat-technologies-gmbh
>> >
>> Twitter <https://twitter.com/CLOUDandHEAT>
>> Xing <https://www.xing.com/companies/cloud%2526heattechnologiesgmbh>
>> Youtube <https://www.youtube.com/cloudandheat>
>>
>> Handelsregister: Amtsgericht Dresden
>> Registernummer: HRB 30549
>> USt.-Ident.-Nr.: DE281093504
>> Geschäftsführer: Nicolas Röhrs
>>
>> Gemeinsam mit uns nachhaltig sein!
>> Nicht jede E-Mail muss gedruckt werden.
>>
>> Hinweis: Diese E-Mail und / oder die Anhänge ist / sind vertraulich und
>> ausschließlich für den bezeichneten Adressaten bestimmt. Die Weitergabe
>> oder Kopieren dieser E-Mail ist strengstens verboten. Wenn Sie diese E-Mail
>> irrtümlich erhalten haben, informieren Sie bitte unverzüglich den Absender
>> und vernichten Sie die Nachricht und alle Anhänge. Vielen Dank.
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dragonflybsd.org/pipermail/users/attachments/20170602/e22a8bfa/attachment-0001.html>