<html><head></head><body><div style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:16px;"><div style="font-family:courier new, courier, monaco, monospace, sans-serif;font-size:16px;"><div><div>Hi,<br><div><br><div>We have a "home-made" HA with two servers running KEA 1.2.0 for about one year without any troubles.<br><div><br><div>However, in our scenario:<br><div>- We don't use any DBs, just memfiles;<br><div>- We have no dynamic pools, just reservations based on "circuit-id" (option 82) for IPv4 and "interface-id" (option 18) for IPv6.<br><div><br>For this use, both servers can have almost the same kea.conf file and there's no need to keep lease CSV files in sync. <br></div></div></div></div></div></div></div></div><div><br></div><div>--</div><div class="ydp21e46207signature"><div style="font-size:16px;"><div>Joelson Vendramin</div></div></div></div>
<div><br></div><div><br></div>
</div><div id="ydpff6bdccayahoo_quoted_6232876186" class="ydpff6bdccayahoo_quoted">
<div style="font-family:'Helvetica Neue', Helvetica, Arial, sans-serif;font-size:13px;color:#26282a;">
<div>
Em quinta-feira, 10 de maio de 2018 10:45:58 BRT, Tomek Mrugalski <tomasz@isc.org> escreveu:
</div>
<div><br></div>
<div><br></div>
<div><div dir="ltr">On 10.05.2018 14:55, Marcos Renato da Silva Junior wrote:<br clear="none">> I understood that Kea still does not have failover or any other type <br clear="none">> of high availability (I have version 1.1.0 and use memfile).<br clear="none">1.1.0 is EOLed since Dec 2017. That means that if you encounter a bug,<br clear="none">you're on your own. ISC will not be fixing anything in versions that are<br clear="none">too old. If I were in your position, I'd seriously consider moving to<br clear="none">1.4.0 once it becomes available. It will have a HA support that works<br clear="none">with memfile.<br clear="none"><br clear="none">On 10.05.2018 15:24, Sutherland, Robert wrote:<br clear="none">> We hoping that the configuration can be stored in the database in a <br clear="none">> future release.<br clear="none">Correct. That's currently under consideration for 1.5. If you are<br clear="none">interested in this functionality and are willing to help fund its <br clear="none">development and/or test it, please contact me off-line. We do have an <br clear="none">early description of the solution here:<br clear="none"><br clear="none"><a shape="rect" href="http://kea.isc.org/wiki/CentralizedConfigNetconf" rel="nofollow" target="_blank">http://kea.isc.org/wiki/CentralizedConfigNetconf</a><br clear="none"><br clear="none">For various reasons we had to mix two aspects together: configuration <br clear="none">storage in DB and netconf. If you don't care about netconf, pay <br clear="none">attention only to the DB sections.<br clear="none"><br clear="none">On 10.05.2018 15:28, Munroe Sollog wrote:<br clear="none">> We currently use kea in an HA (slightly unsupported setup) and I <br clear="none">> believe 1.4 will include the rest of the missing pieces for HA (due <br clear="none">> in a few weeks). We have 3 servers in a galera mysql cluster and<br clear="none">> two dhcp server. We are double VRRP'ing between them so both IPs<br clear="none">> always stay up. Using 1.3, while some metrics have been screwed up,<br clear="none">> the core functionality has been rock solid for ~6 months.<br clear="none">Great to hear about the rock solid part.<br clear="none"><br clear="none">The metric fix is coming up in 1.4-beta.<br clear="none"><br clear="none">Tomek<div class="ydpff6bdccayqt1638215119" id="ydpff6bdccayqtfd55840"><br clear="none">_______________________________________________<br clear="none">Kea-users mailing list<br clear="none"><a shape="rect" href="mailto:Kea-users@lists.isc.org" rel="nofollow" target="_blank">Kea-users@lists.isc.org</a><br clear="none"><a shape="rect" href="https://lists.isc.org/mailman/listinfo/kea-users" rel="nofollow" target="_blank">https://lists.isc.org/mailman/listinfo/kea-users</a><br clear="none"></div></div></div>
</div>
</div></div></body></html>