Igor Ryzhov bcf2208156 isisd: allow arbitrary order of area/interface configuration ... Currently we don't allow to configure the interface before the area is configured. This approach has the following issues: 1. The area config can be deleted even when we have an interface config relying on it. The code is not ready for that - we'll have a whole bunch of stale pointers if user does that. 2. The code doesn't correctly process the event of changing the VRF for an interface. There is no mechanism to ensure that the area exists in the new VRF so currently the circuit still stays in the old VRF. This commit allows an arbitrary order of area/interface configuration. There is no more need to configure the area before configuring the interface. This change fixes both the issues. Signed-off-by: Igor Ryzhov <iryzhov@nfware.com>		2021-04-29 17:05:21 +03:00
..
rt1	tests: extend the isisd SR topotest to test Anycast-SIDs as well	2020-10-23 10:31:39 -03:00
rt2	isisd: uninstall local routes that don't have any valid nexthop	2020-11-23 14:50:32 -03:00
rt3	tests: extend the isisd SR topotest to test Anycast-SIDs as well	2020-10-23 10:31:39 -03:00
rt4	isisd: uninstall local routes that don't have any valid nexthop	2020-11-23 14:50:32 -03:00
rt5	isisd: uninstall local routes that don't have any valid nexthop	2020-11-23 14:50:32 -03:00
rt6	tests: extend the isisd SR topotest to test Anycast-SIDs as well	2020-10-23 10:31:39 -03:00
__init__.py	tests: add topotest for IS-IS SR	2020-04-30 12:15:47 +02:00
test_isis_sr_topo1.py	isisd: allow arbitrary order of area/interface configuration	2021-04-29 17:05:21 +03:00