My approach to this problem was to separate subnet definitions, via the JSON file include mechanism, from the overall service configuration. The service configuration doesn't change, so I just need to validate the subnets file before updating, which can now be done in a hitless fashion.
So, +2 for includes! cheers, Klaus On Fri, Aug 27, 2021 at 6:45 AM Veronique Lefebure < veronique.lefeb...@cern.ch> wrote: > YES :-) > > That's the work around. Thanks !! > > On 27/08/2021 15:42, Andrei Pavel wrote: > > ip link add xxxxx type bridge > _______________________________________________ > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. > > Kea-users mailing list > Kea-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/kea-users >
_______________________________________________ ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list Kea-users@lists.isc.org https://lists.isc.org/mailman/listinfo/kea-users
