This page describes possible options of implementing QoS guarantees on Ethernet circuits in Geant network. We investigated two possible options. First options is to use the OTN layer to provision the circuit through the backbone, this option will be further described in section 1. Second option are MPLS-TE tunnels over IP/MPLS layer and will be described in section 2.
Use of the OTN layer
TODO: add OTN solution description MHY
This chapter will describe the deployment of CCS over the OTN layer in Geant network.
OTN CCS should provide the guaranteed QoS for GTS testbed's links. In order to do so, one OpenNSA instances needs to be deployed over the OTN switch in each GTS location plus over each intermediate switch between GTS locations in the Geant OTN topology. Unlike in IP/MPLS where LSPs creates virtual full mesh, in OTN network the OpenNSA has to configure each OTN switch along the circuit patch, not only devices where circuit terminates. OpenNSA will then configure each OTN switch participating on the circuit as well as handle the time slots assignment based on requested bandwidth. Minimal (and also default, when no bandwidth is specified) bandwidth of one circuit will be 1.25 Gbps. This is also a granularity of possible settings.
In order to provide VLAN delineated circuits OTN devices in GTS locations have to be equipped by line cards supporting L2 features. (Possibly PXM cards for DTN-X platform.)
GTS data plane requirements per location.
The GTS needs quiet a lot of dedicated 10GE ports per locations for data plane connections. Requirements for one pod are summarized in the following table. There are always three numbers separated by "/", the meaning is the following: current(minimal)/expected soon/planned long term.
| Equipment type | Number of these type of device in the pod | Number of 10GE ports/device | Total number of 10GE ports | |
|---|---|---|---|---|
| Servers | 4/8/8 | 1/1/2 | 4/8/16 | |
| Corsa OF switch | 1/1/1 | 4/4/4 | 4/4/4 | |
| External links | 1/2/2 | ---- | 1/2/2 | |
| Total: | 9/14/22 |
In addition to these numbers, in CSF location 2 more ports are needed for GW links.
Based in these numbers it seems that having one PXM card in a locations could become a bottle next for scaling up in the future as the PXM card is 16x10GE.
Steps needed for deploy the OTN based CCS for GTS
- Learn the Geant OTN topology and prepare the OpenNSA topology to cover Amsterdam, Bratislava, Prague, Hamburg, London, Milan, Madrid and Paris.
- Deploy PXM cards in locations listed above. (Mean place an order for more, since Geant has not enough of them.)
- Implement OTN OpenNSA backend for Infinera DTN-X with PXM.
- Connect GTS equipment data plane ports to PXM.
- Reconfigure GTS
Ad 1: Geant OTN topology
Ad 5: Reconfigure GTS
Thanks to current abstract names of NSI STPs, it could be possible to just deactivate existing testbeds, reconfigure GTS for use of OTN and then activate testbeds again with links in OTN.
Use of the MPLS-TE
Nemanja Ninković TODO: - Describe the QoS configuration for junipers we prepared (shaping and policing on client ports and BW reservation on LSPs; provide upgraded configlets; // Basically copy in content from documentation we already have and imroove it + plus add the brief description of possibilities with current line cards deployed in geant (consult Niall if needed)// )