2b38e677b2
These bits are irrelevant for GNPy, but required on the ONOS side. I'm not particularly happy with the format of the links, or the fact that we need them to be done manually. I really wanted to generate them from the underlying GNPy topology, however, that's hard because ONOS needs port information (so that it knows how to configure these ROADMs). FIXME: It might be possible if everything is in the same network instance. In that case, this model would just augment each link with port IDs. However, I'm not really happy with having "unrecognized" elements in the GNPy-specific topology. Or perhaps that's actually OK? Change-Id: I31be96c04f069ab797b9da82993633dc804180e2
GNPy: Optical Route Planning and DWDM Network Optimization
GNPy is an open-source, community-developed library for building route planning and optimization tools in real-world mesh optical networks. We are a consortium of operators, vendors, and academic researchers sponsored via the Telecom Infra Project's OOPT/PSE working group. Together, we are building this tool for rapid development of production-grade route planning tools which is easily extensible to include custom network elements and performant to the scale of real-world mesh optical networks.
Quick Start
Install either via Docker, or as a Python package. Read our documentation, learn from the demos, and get in touch with us.
This example demonstrates how GNPy can be used to check the expected SNR at the end of the line by varying the channel input power:
GNPy can do much more, including acting as a Path Computation Engine, tracking bandwidth requests, or advising the SDN controller about a best possible path through a large DWDM network. Learn more about this in the documentation.