- Handled situations where ovsdb, integration bridge, or vxlan port are
already connected or exists when the application activated
- Don't make use of mastership for ovsdb device, it does not work well in
device disconnected or re-connected situations
Change-Id: I002948f4a06126430f6019c79a0d84df16c9399c
Followings are changed
- Changed nodeStore from eventually consistent map to consistent map
- Removed ovsdb connection management(ovsdb controller has connection status)
- Not only one leader but all onos instances make ovsdb session
Following jobs are done
- Reads compute node and ovsdb access info from network config
- Initiates ovsdb connection to the nodes
- Creates integration bridge on each ovsdbs
- Creates vxlan tunnel port on each integration bridges
Change-Id: I8df4061fcb1eae9b0abd545b7a3f540be50607a9
need deploy three applications, but now vtn/vtnweb/vtnrsc as three
bundles are packaged as a single application. instead to install three
application. of cource if the other apps want to depend on any one of
three bundles, it can do.
Change-Id: I3535b36ac082dbb90cb714ba83d2336c950a22a1
- parameterize the UDP port of the RADIUS server
- clean up some unused constants
- refactor config code to reduce repetitive code
Change-Id: I797dabd12c8ccd522f1ab0812c2b03da7264f2c0
DONE
- Remove original configuration subsystem
- Implement new SegmentRoutingConfig
- Update SegmentRoutingManager and DeviceConfiguration
TODO
- Extract adjacencySid array from JsonNode
- Extract subnets and prefixes from port subject
Change-Id: Ic7fec102f4427a30eec99ebf6c7c5584652a6280
Another improment is: if we config interfaces for local subnet
in network-cfg.json, sdn-ip will classify the traffic correctly
Change-Id: I94d80bc5a7c29b70e6c8546d99b71850cfb3f14d
* IntentSynchronizer can now handle any intent rather than having use
case specific APIs
* IntentSynchronizer does not generate or store intents anymore, it only
perform synchronization
* SdnIpFib generates and manages the procative route-based intents
* ReactiveRoutingFib generates and manages the reactive intents
* Unit tests have been tightned up to only test single components, rather
than multiple components together
* PeerConnectivityManager uses meaningful keys when creating intents
Change-Id: I4bb036ec8d056f43ece46f7dfc71d5e5a136b77d
- cleaned up exception handling a little
- reformatting of the code to be easier to read and group similar code together
- fixed some style problems found by IntelliJ
Change-Id: I932ac48d82b598b1f59c906477fb5e4deded413f
- optimized lookup of state machines
- modified getter/setter method names to match ONOS project standards
- made StateMachine local members private and add accesor methods
- added unit tests for StateMachine lookups
Change-Id: I5704ddc4d8b1b3c887be1262f2edd78965e4a8bf
This will be used by publishers to advertise multicast information
and by consumers to realise it on the dataplane.
This is currently an app but it may be moved to incubation.
Change-Id: I6e350989207ce2207bf70da22ca15c8237b1d240
