Changes:
- Adds mirroring behaviour;
- Adds mirroring description;
- Adds mirroring name;
- Implements for Ovsdb the mirroring;
- Adds OvsdbMirror entity;
- Adds constants related to Mirror table;
- Fix one issue related to Mirror table
- Extends OvsdbClientService introducing mirroring;
- Implements mirroring functionality in DefaulOvsdbClient;
- Support for different types of device id
Change-Id: Ie291f49b3c61b7998010f555ae11deb8c021063d
When tableStore or rowStore is null, getBridges() should not return (null),
that will cause NullPointerException in its two usages:
(getBRidges only has these two usages now, but it is very foundational.)
1. OvsdbBridgeConfig.java, line 113-115:
Set<OvsdbBridge> bridges = client.getBridges();
return bridges.stream()......
2. OvsdbControllerConfig.java, line 92:
.filter(cs ->
cs.getBridges().stream()
.anyMatch(b -> dpidMatches(b, ofDeviceId)))
......
Change-Id: Ice14a8991f5022a5041cf48f5c8431712f946228
- Added tunnel interface configuratoin to interfaceConfig and
deprecated tunnelConfig
- OVSDB client service provides interface create/remove APIs instead
of tunnel interface create/remove, and this APIs can be used to
create/remove various types of interfaces like tunnel, patch, tap and so on
- Use tunnel description when create tunnel interface so that we can extend
more config options later
- Some cleaup OVSDB client
Change-Id: I4653595504a27b18384a92ebe4b31ce9d99237cd
OVSDB provides lots of bridge configuration options but the exisisting
bridge config implementation only allows some of them by overloading
addBridge method. Also some of the bridge properties were set static
and unable to configure. This patch fixes these limitations.
- Added some bridge config options to the bridge description
- Deprecated multiple overloaded addBridge methods
- Some code clean up
Change-Id: Ibc828177b210bd4b215aea0b63cc359776c13e03
- Using osgi_jar for all modules except apps
- Adding target for installation of core modules to .m2 repo
Change-Id: I65d9e3a9567918e275191724842d7d9b1f485128
- Update br-int rather than do nothing if it already exists
- Make only the leader performs node bootstrap
- Check mastership on HOST event not flow rule populator
- Install/uninstall flow rules for vSG always from master, or the rules
stay in PENDING_ADDED state
Change-Id: I4bd5cf6f84bf36f2617288b2d843435819c76ba8
