2947bbfd25
Get rid of ' characters in errors
2022-03-15 21:13:42 +00:00
2bbcff2ca0
Also assert that targets of an L2XC do not have an address or LCP
2022-03-15 21:07:47 +00:00
5876465327
A few cosmetic changes in logging
2022-03-15 20:57:11 +00:00
6d3de72c00
A completely empty config is a valid config
2022-03-15 20:52:09 +00:00
c5872880fe
Add l2xc support, including extensive tests to validate correct usage of the feature
2022-03-15 20:45:27 +00:00
b9a7bb697e
Add validator to ensure that bridgedomain interfaces occur in at most one bridgedomain. Ironically, this caught a bug in the bridgedomain5 test, where Gi1/0/0 was added twice.
2022-03-15 19:48:32 +00:00
13f211f27a
Make clearer that 'is not allowed' actually means that the address conflicts with another
2022-03-14 00:18:46 +00:00
bb57ed8e52
IP Address validator
...
Returns True if there is at most one occurence of the ip_interface (an IPv4/IPv6 prefix+len)
in the entire config. That said, we need the 'iface_addresses' because VPP is a bit fickle in
this regard.
IP addresses from the same prefix/len can be added to a given interface (ie 192.0.2.1/24 and
192.0.2.2/24), but other than that, any prefix can not occur as a more-specific or less-specific
of any other interface.
So, we will allow:
- any ip_interface that is of equal network/len of existing one(s) _on the same interface_
And, we will reject
- any ip_interface that is a more specific of any existing one
- any ip_interface that is a less specific of any existing one
Update unit tests to ensure ip_interfaces are allowed in all cases.
2022-03-13 23:50:10 +00:00
3f2b80172c
Add another schema validation test
2022-03-13 21:18:08 +00:00
660e240eb7
Add some more garbage fields and tpyoes
2022-03-13 20:38:12 +00:00
2ca7cc3f11
Check for fields that are of the wrong type. Fix bug in ip_interface() validator thanks to this unittest
2022-03-13 20:20:14 +00:00
0f03d6cbaa
Add unit test that ensures exact-match=False can't be on a sub-int with an LCP or address
2022-03-13 20:10:06 +00:00
763c1ca74c
Ensure that LCP names are globally unique (between interface/sub-interface/loopback/bridgedomain)
2022-03-13 19:53:13 +00:00
0d8a28cadd
Enforce that when a bridgedomain has an address (ie a BVI), that it must also have an LCP
2022-03-13 19:32:30 +00:00
8825984d49
Force loopbacks with an address to have an LCP
2022-03-13 19:27:27 +00:00
d693c41c72
Add four simple loopback examples (with and without LCP or address)
2022-03-13 19:19:39 +00:00
1adb91d227
Add LCP/Address example bridgedomains
2022-03-13 19:19:18 +00:00
1340e5db42
Remove the attempted plural 'address(es)', and keep it singular. Fix a typo (addd-ress); update unit tests
2022-03-13 19:08:45 +00:00
878f94b2bd
Add unit tests for bondethernet, including a set of correctly form ones
2022-03-13 19:04:31 +00:00
527b1ca95b
Add a set of bridgedomain unit tests, including a fully formed correct one. Fix one bug found along the way!
2022-03-13 18:55:00 +00:00
5207b920d7
Rename unittest
2022-03-13 18:35:28 +00:00
9aec425bc0
Add unit tests for all interface/sub-interface failure modes
2022-03-13 18:35:11 +00:00
95c8be553f
Simple unit tester, with a few example tests
2022-03-13 17:20:10 +00:00
