<div dir="ltr"><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 20, 2018 at 2:13 AM, Christian Kratzer <span dir="ltr"><<a href="mailto:ck@cksoft.de" target="_blank">ck@cksoft.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<span class=""><br>
<br>
On Fri, 19 Jan 2018, David Hankins wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I'm looking at implementing this quarter a competing implementation of;<br>
<br>
<a href="https://lists.isc.org/pipermail/kea-dev/2017-December/000840.html" rel="noreferrer" target="_blank">https://lists.isc.org/pipermai<wbr>l/kea-dev/2017-December/<wbr>000840.html</a><br>
<br>
Basically I'm after the same thing; I want ISC Kea to perform DHCPv4 and<br>
DHCPv6 protocol implementations, and I just want to provide an interface to<br>
internal backend systems curating configuration intent in Python runtime.<br>
<br>
I was about to send an email to kea-dev announcing my intentions, but I<br>
see there's already been some work in this area.<br>
<br>
Where's it at, what's the current status, and how can we best move forward<br>
together?<br>
</blockquote>
<br></span>
instead of putting effort into implementing yet another binding for a language<br>
why not implement the hooks as configurable rest calls and then have something<br>
like python/flask to connect to or whatever else you prefer.<br>
<br></blockquote><div><br></div><div><div class="gmail_default" style="font-family:monospace,monospace">This is an excellent question that deserves some discussion; I think such a hook would have merit in some deployment environments. I could see a REST interface having traction in high-latency-tolerant and low-traffic deployments, but I would prefer myself to use a gRPC or Thrift interface with integrated service discovery (something like BNS or ZooKeeper).</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">There is always a "strange attractor" that software engineers analyze when asking and answering the question, "in our micro-service architecture, should we draw the box around these functions, or these other functions?" Integrating a function inside one instance of a multi-service architecture versus breaking it out into a separate micro service.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">The tradeoffs are increased dependencies and potentially latency versus service simplicity.</div><div class="gmail_default" style="font-family:monospace,monospace"><br></div><div class="gmail_default" style="font-family:monospace,monospace">In this case, I think there are use cases for a native hook for which the added dependency and latency aren't worthwhile tradeoffs. For example, where all elements of configuration for a given host can be arrived at algorithmically (mathematically) from packet contents alone. I think there are also cases where host configuration is itself a seriously complicated question, involving additional backend queries, and a micro-service approach is appropriate.</div></div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I was planning on on doing that to the previously announced hook library. Priorities<br>
are on other projects atm but that would be my way of proceding once I migrate<br>
my customer from classic isc dhcp to kea.<br>
<br>
Greetings<span class="HOEnZb"><font color="#888888"><br>
Christian<br>
<br>
-- <br>
Christian Kratzer CK Software GmbH<br>
Email: <a href="mailto:ck@cksoft.de" target="_blank">ck@cksoft.de</a> Wildberger Weg 24/2<br>
Phone: <a href="tel:%2B49%207032%20893%20997%20-%200" value="+4970328939970" target="_blank">+49 7032 893 997 - 0</a> D-71126 Gaeufelden<br>
Fax: <a href="tel:%2B49%207032%20893%20997%20-%209" value="+4970328939979" target="_blank">+49 7032 893 997 - 9</a> HRB 245288, Amtsgericht Stuttgart<br>
Mobile: <a href="tel:%2B49%20171%201947%20843" value="+491711947843" target="_blank">+49 171 1947 843</a> Geschaeftsfuehrer: Christian Kratzer<br>
Web: <a href="http://www.cksoft.de/" rel="noreferrer" target="_blank">http://www.cksoft.de/</a></font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><font face="monospace, monospace">Infrastructure Management Services</font></div><div><font face="monospace, monospace">Twitter, Inc.</font></div></div></div></div></div></div></div>
</div></div>