RELEASE | VERSION | RELEASE DATE | DOCUMENTATION |
---|---|---|---|
Avocet | <add> | Dec 5th, 2014 |
|
Avocet Release
Release date: December 5th, 2014
1. Component Changes
Component | Version | Change type |
---|---|---|
Floodlight | 0.9 | New component |
Cassandra | 1.2.4 | New Component |
Titan | 0.2.1 | New Component |
ZooKeeper | 3.4.5 | New Component |
Hazelcast | 3.0.2 | New Component |
2. New features and enhancements
Type | Description | |
---|---|---|
Network Graph Abstraction | New feature | This feature maintains full view of the network where network state is represented as Graph (Switch, port, device and link). Application writes to this graph and programs the data plane. |
Horizontal Scale Out | New feature | This feature provides means for customers to horizontally grow network clusters as an ONOS instance is responsible for maintaining a part of network graph. Control capacity can grow with network size or application need. |
High Availability/Fault Tolerance | New Feature | This feature provides seamless Master Controller Election on ONOS Node/instance failure as well as selecting alternate paths on data plane link/port failure. |
Flow Setup API | New feature | Ability to setup and manage flow paths by computing shortest path from source to destination. |
Network Topology Discovery | New feature | Ability to discover all network topology and present it as a graph. |
Device Discovery | New feature | Ability to discover hosts and their attachment points. |
Proxy ARP service | New feature | Ability to intercept ARP broadcasts and respond to host location if discovered. |
Flow Synchronizer | New feature | The truth of flow state is in network graph. Maintains the consistency between switches and network graph. |
Reactive Forwarding | New feature | Ability to setup temporary flow paths by intercepting packet ins and enabling reactive flow setup |
REST API | New feature | A RESTful API to read the network graph and setup flow paths. |
GUI | New feature | A sample WEB UI to show the topology and ONOS instances in a graph |
3. Feature limitations
Feature | Limitation |
---|---|
Reactive Forwarding | Experimental code - may not work in all scenarios |
4. Other Limitations
Issue | Impact |
---|---|
The only ONOS API available for applications to use is Titan/Blueprints API. | This is very low level and requires knowledge of our schema details. ONOS Team is working towards the API Design we want to present to applications and building out the existing API to be inline with this design. |
Code does not conform to Coding Style guide recommendations. | Developers will encounter code that does not conform to coding guidelines. Refer to coding guidelines instead of using existing code as reference. |
5. Issues fixed
Not applicable
6. Known Issues
Number | Issue | Impact |
---|---|---|
1. | After restart, ONOS can not remove the flow entry from the database after the flow entry in the switch expires | Inconsistent flow entries in the switch |
2. | Addflow Wrapper Script has issues when -"-m onos" command-line flag is not used | when web/add_flow.py script is used without "-m onos" command-line flag, flow entries may be not correct |
3. | Duplicate packets may be seen on reactive flows. | may cause some traffic overhead and some packet loss |
4. | Occasionally packets are dropped while setting up a reactive flow. | short traffic interruption |
5. | Device discovery (a dependency of reactive forwarding) does not work correctly if the topology has not been fully discovered. | Reactive forwarding may not work right after ONOS startup when the topology is being discovered or if topology changes. |
6. | Simultaneous start of ONOS instances can cause some ONOS node to hang | Not all ONOS nodes functional at the start |