Difference: ComputingT2SDN (2 vs. 3)

Revision 32014-08-07 - samir

Line: 1 to 1
 In 2014 the bandwidth available to many CMS T2 sites has been upgraded to about 100 Gbps. To use these links efficiently and still not overload Internet2 the ideal is that we take advantage of smarter network technologies such as openflow.

Currently Internet2 has a mesh with points of presence all over the US. Clients can control what their paths are to destinations through a remote API named OESS. However, before any action through the API it is important to collect information and analyze the data according to a favorable algorithm to take decisions to ensure optimal and distributed usage of the network.

Line: 68 to 68
  Paths between site A and B will at first be set by humans. The way to do it will be in a configuration file, in the INI style of Config::Simple. The agent will then poll the different paths and run the algorithm to take decisions.
Added:
>
>

Link usage analysis

We will assume that whatever circuit established will be bi-directional, therefore we will use this to our advantage when calculating link occupancy, so if A <-> B is :

  • A -> B - 10 Gbps
  • A <- B - 15 Gbps
  • Link occupancy will be considered the biggest value.

Example from the testing phase : 


ok 2 - it loaded the config file
in : 4880768648.32 out : 23459754131.92 Occupancy : 23459754131.92
in : 4923468309.12 out : 23343333114.4 Occupancy : 23343333114.4
in : 4923468309.12 out : 23343333114.4 Occupancy : 23343333114.4
in : 26732614349.12 out : 6674543318.08 Occupancy : 26732614349.12
in : 25724523544.64 out : 5172133386.72 Occupancy : 25724523544.64
in : 11104883426.7378 out : 5572073934.03555 Occupancy : 11104883426.7378
in : 464418907.68 out : 1221074236.24 Occupancy : 1221074236.24
in : 3608908918.24 out : 1939667358.24 Occupancy : 3608908918.24
in : 2275492791.2 out : 3712034803.36 Occupancy : 3712034803.36
 

Actions - OESS

Azher deployed one OESS instance. Once the previous parts are written, a possibility is to do a small demo with the local equipment, having 2 links between 2 local servers and shifting the load between the links.

View topic | History: r4 < r3 < r2 < r1 | More topic actions...
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback