Changes.
1. Named *Service classes in the impementation package re-named as
*Manager
2. VirtualTopologyProvider is renamed as DefaultVirtualNetworkProvider
Change-Id: Ic8663aee793d0b8f87ffea3df7f71c8ac77362ca
ROUTE_REMOVED is already sent when the state trasits from RESOLVED to UNRESOLVED/INITIAL.
Not necessary to send it again when trasiting from UNRESOLVED to INITIAL.
Also fix bugs
- next hop is erased when updating route that is exactly the same as before
- duplicated log messages when withdrawing routes
Change-Id: I7d60081b83fc2063e451b346ba477330e88bdc28
- Fixed Thomas Vachuska's comment
.Removed DpiStatisticsJson.java and related codes for avoiding confusion within package because this does not need anymore.
.Simplified execute() code and fixed comments in DpiListCommand
.Added javadocs for public methods and fixed typos
- Rebased from master 1.8.0-SNAPSHOT, 2016.10.14
- Upgraded the function and performance.
.changed List<DpiStatistics> to SortedMap<DpiStatistics>
.added DpiStatisticsService interfaces to get DpiStatistics by receivedTime
.added more options of dpis CLI: displays indivisual category by topn
.and some bug fix
- Fix javadocs and ONOS style method name.
- Fix javadocs error.
Change-Id: I07a058e04f63bd9c547a5d605975b214eec0ce1f
Original usage with specifiying a phyiscal port is also in supporting.
Changes.
1. vnet-create-port allow to create virtual port
without a specific virtual port
2. vnet-bind-port command is added to newly bind or to update
3. Virtual binding point is changed from Port to ConnectPoint.
Change-Id: I4c8f9a2b9b2786ba519ead3559d7f005390fee86
Also some small API changes to track app ID of handler registrations, and
improved interface matching in NeighbourPacketManager.
Added CLI to view handler registrations.
Change-Id: I8cd0b91a16d9ec60287b65f9d8fc5e3cd87560e8
The idea is to allow applications to contribute NeighbourMessageHandlers to
handle ARP/NDP packets coming from a particular ConnectPoint, Interface or with
a particular traffic selector. Applications can contribute different handlers
for different ports, because they know how those ports will be used. Also,
multiple applications can contribute handlers for different ports/interfaces
without having to have one ARP handler for the entire network. The framework
provides actions that the handler can choose to take - flood, proxy, reply, drop.
The handler is free to implement some other action if none of these fit what it
needs to do. The framework also handles many of the common tasks for ARP handlers,
like parsing packets, abstracting the differences between ARP and NDP, implementing
actions like replying to a request. This allows handlers to be very simple and
easy to understand and implement.
Change-Id: I313c723e9ebc3d0816eb79870ee0536780e7a640
- Define ConfigOperator for a Port
- Refactor OpticalPortOperator as PortConfigOperator
- Add plug-in mechanism for PortConfigOperator on DeviceManager
- Move OpticalPortConfig, OpticalPortOperator to optical-model bundle
Change-Id: I5d416305b0c1b0e31e0ad64baa92d126303548bc
- tests were failing due to missing resources in incubator/api
- commented out dependency in openstackrouting
- duplicate dependency in apps/faultmanagement
Change-Id: Ie9e9430d5707b0e2ab07338fdb8a5095126102f8
In this submission:
* Setup/teardown multicast route according to SinkAdded/SinkRemoved event
- ingressVlan and egressVlan is configurable through network config
* Change behavior of OFDPA VLAN assignment
- Always use the VLAN in metadata if present
* Bugfix of writing immutable object
NOT in this submission (coming soon):
* Error handling (e.g. link/device failure recovery)
Change-Id: I9be11af04eb2d6456b865c7e59e96cc02370f846
Also created an adapter to adapt the new interface to the old one for
backwards compatibilty with existing FIB components.
Change-Id: If8eb2220d9e4e69af135a8f9469ffda567ed4448
