f611f3d899
I'm using a second-level module namespace (gnpy.yang) for the same reasons as when shipping the example data via gnpy/example-data/ -- these will be used in the subsequent commits when we actually start adding YANG models. There is also some code (not much now, a lot more in future) for working with these models, and in future also for loading actual data. These *could* be put into gnpy.tools.*, but I think it's more straightforward to just keep them in the YANG namespace. Change-Id: Ic40738ddd8346429bde01e591d19fd2ce8cb687d
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.