| 20 | |
| 21 | == Issue reporting == |
| 22 | |
| 23 | If you have a !FlowVisor issue, such as an unexpected FV crash, we'd like to work with you and ONL to try to identify the cause and resolve it. |
| 24 | |
| 25 | First, send mail to flowvisor@onlab.us and gpo-infra@geni.net, so we can discuss and research the root cause of the outage. |
| 26 | |
| 27 | Once the cause is identified, make a !FlowVisor ticket to track the issue; https://github.com/OPENNETWORKINGLAB/flowvisor/wiki/Filing-New-Issues-or-bugs describes how to do that most effectively. |
| 28 | |
| 29 | ONL will then prioritize and address the ticket accordingly, and work towards a resolution. |
| 30 | |
| 31 | You can also, of course, make tickets to track other !FlowVisor issues, bugs, feature requests, etc. |