search

openalto / ietf-hackathon

3 stars 7 forks source link

FTS global resource control (design) (API and Control) Task 1.2 #47

Open MattSlm opened 2 years ago

MattSlm commented 2 years ago

Task 1.2 of the FTS ALTO extension as described here

MattSlm commented 2 years ago

Summary:

  1. ALTO client as a service in FTS fetches routing information (Path vector) as ANEs and updates DB.
  2. ALTO client as a service in FTS fetches link bandwidths as cost metrics and updates them.
  3. Admin can submit ALTO server configurations/ Link capacity limits/ (Upper bound of bandwidth shares per VO -> Links are shared with other applications) via REST API docs - examples.
  4. Transfer service creates subscription requests per each connection - ALTO client service fetches the path vectors and link bandwidths and subscribe for changes (if not already being monitored)
  5. Upon arrival of an update to a path vector or a link's capacity alto client updates DB.
  6. Optimizer changes: (like storage capacity limits) ??
MattSlm commented 2 years ago

Configure ALTO server (configuration file)

Location: fts3/src/config/serverconfigreader.cpp

Example:

( "IP,i", po::valuestd::string( &(_vars["IP"]) )->default_value(FTS3_CONFIG_SERVERCONFIG_IP_DEFAULT), "IP address that the server is bound to" )

Question: Proper name for ALTO Server’s IP address