01:09:23 Shawn P McKee: The last half of this meeting is network focused 01:09:44 Shawn P McKee: Sorry for the noice (wrong target) 01:10:33 Maarten: It’s still true. :-) 01:55:57 Doug Southworth: Sounds good! 01:56:10 Mario Lassnig: break until 16:45 CEST 02:16:57 Petr Vokac: I'll write it 02:17:10 Petr Vokac: What do you collect for failed transfers 02:17:27 Petr Vokac: Do you collect size of partially transferred file? 02:17:31 Mihai Patrascoiu: They still go in the Transfer Complete 02:44:18 Paul Millar (DESY): My question is: does NetSage have knowledge of network topology? Could we use this to help identify performance bottlenecks? 02:47:18 Doug Southworth: It doesn't have a knowledge of topology in the sense of hop-by-hop routing, but we do have flow information by organization, continent, country, and link used, so we do have some insight into where performance starts to fail even if we can't pinpoint the specific source. The more data sources NetSage has access to, the greater the ability to understand where performance is suffering. If we can only see the flow from one point then that process becomes more difficult. 02:49:15 Doug Southworth: The ability to look at end-to-end performance, however, can point to the need to look more deeply at a specific end-to-end pairing, and which tools would be of use in that situation. For instance, if NetSage notes poor performance between JISC and APAN, then perhaps that's a case where perfSONAR could be of use in pinpointing the exact location of the problem. 02:53:40 Maarten: Hi Doug, would you like every WLCG site to join the NetSAGE infrastructure? Would it be ready for all those extra data flows? 02:57:47 Maarten: Maybe just the N biggest sites rather? 02:59:45 Doug Southworth: We'd definitely like to have that discussion. Capacity won't be a problem as the current infrastructure is quite scalable and has room to grow. It would probably make sense to start with the N biggest sites and work our way down, but we should be able to accommodate all of them as we have opportunity to collect flow data from them. 03:27:06 Mattias Wadenstein: NDGF's network load map, no fancy hover stuff, you have to click in order to get to the plots: http://stats.nordu.net/stat-q/load-map/ndgf,,traffic,peak 03:27:47 Mario Lassnig: thanks mattias 03:29:20 Alessandra Forti: @mattias you are right I missed that clicking on the link you get the plot 03:29:49 Alessandra Forti: I was clicking on the site and it was just giving me the static map 03:32:54 Marian Babik: https://public-brian.geant.org/d/home/home?orgId=5 03:32:55 Mattias Wadenstein: Some of the squares (se-ndgf and no-ndgf) links to other maps too, for the cases where there is more than one site in the country. the UI is useful, but not exactly intuative 03:34:09 Rick Havern: https://tools.geant.org/portal/ 03:34:33 Rick Havern: See BRIAN