Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
| RELEASE | VERSION | RELEASE DATE | DOCUMENTATION |
|---|---|---|---|
| Avocet | <add> | Dec 5th, 2014 |
|
Release date: 17th June, 2014
1. Component Changes
| Component | Version | Change type |
|---|---|---|
| RAMCloud | 1.0 + fixes | New component |
| ZooKeeper | 3.4.6 | New version |
| Cassandra | 1.2.4 | Component Removed |
| Titan | 0.2.1 | Component Removed |
2. New features and enhancements
| Type | Description | |
|---|---|---|
| Network View Abstraction | Replicated Topology view on each instance | |
| Intent API | New | Flow Setup API from Release 0.1.0 replaced by Intent API |
| RAMCloud Data Store | New | Low-latency in-memory persistence of network state |
| REST API | Enhancement | REST API cleaned up and refactored |
| CLI | New | A simple Command-Line Interface tool for interacting with ONOS |
| Configuration | New | Configuration of ONOS and related modules (RAMCloud, Hazelcast, Zookeeper) centralized to single file. |
| GUI | New | A web-based GUI to view the topology. Click here for details on GUI. |
3. Feature limitations
| Feature | Limitation |
|---|---|
| Proxy ARP | Not supported |
| Flow Synchronizer | Not supported |
| Reactive Forwarding | Not supported |
| Flow Match/Action | Reduced capability |
4. Other limitations
| Limitation # | Limitation | Impact |
|---|---|---|
| 1 | Intents installed on an ONOS instance do not get replicated to other instances. | If the ONOS node on which intent is installed goes down, then the installed intent will not persist i.e. it will not be available on any other instance in the cluster. |
| 2 | Limited performance and scalability data is available. | Limited performance and scale data available for reference or benchmarking |
| 3 | Limited fault tolerance scenarios have been tested. | Fault tolerance features have been tested with ONOS process termination in multiple ONOS instance scenarios. However, Ramcloud and Zookeeper-related failure modes have not been comprehensively tested in this release. |
5. Fixed issues from Release 0.1.0
| Issue # | Issue | Discovered in Release | Status |
|---|---|---|---|
| 0.1.0-6 | Simultaneous start of ONOS instances can cause some of the ONOS nodes to hang. | 0.1.0 | Fixed |
6. Known Issues
| Issue # | Issue Description | Workaround | Fix |
|---|---|---|---|
JIRA None | Intents re-routing may fail in the scenario where the "switch link up/down" and "ONOS mastership change" events occur in close combination. Test reports indicate that this failure is easier to replicate when link events and ONOS mastership changes occur within approximately 30 seconds or lesser of each other. | None Identified | Next Release |
B.
Issue # | Issue | Workaround | Will be fixed? (Target Release) |
|---|---|---|---|
| JIRA 1365 | In a stress test scenario with large number of "link up/down" and "mastership change" events, links are not being shown (i.e. discovered) in the network graph. The issue is currently being debugged to identify root cause. | None Identified | Debugging in progress to identify root cause. |
Release date: December 18th, 2013
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 |