All,
the description and offer has now been narrowed down to a description of the inter-site connectivity, on the assumption that ESS requires (and will be getting) upstream connectivity to DeIC and SUNET anyway.
Please read and comment; I will send the document to ESS this week.
/Lars
On 20/12/16 16:32, Lars Fischer wrote:
All,
the description and offer has now been narrowed down to a description of the inter-site connectivity, on the assumption that ESS requires (and will be getting) upstream connectivity to DeIC and SUNET anyway.
Please read and comment; I will send the document to ESS this week.
/Lars
Essnet mailing list Essnet@lists.nordu.net https://lists.nordu.net/listinfo/essnet
I think the document makes sense. A few points.
· A 10Gbps monitoring node at each site, with a web-based portal for regular and ad-hoc latency and capacity tests between sites as well as between ESS and sites on the NORDUnet network.
Whats this? Perfsonar?
Should we also elaborate that the path between Lund and Copenhagen will actually be over Öresundsbron? to further cement the fact that we have the shortest possible path there is inbetween these sites. So we can be fully compared to any commercial provider without any problem.
On 21 Dec 2016, at 9:44, Fredrik Korsbäck wrote:
· A 10Gbps monitoring node at each site, with a web-based portal for regular and ad-hoc latency and capacity tests between sites as well as between ESS and sites on the NORDUnet network.
Whats this? Perfsonar?
Yep. By the suggestion of Qvist.
Should we also elaborate that the path between Lund and Copenhagen will actually be over Öresundsbron? to further cement the fact that we have the shortest possible path there is inbetween these sites. So we can be fully compared to any commercial provider without any problem.
Good point.
/Lars
- On p.3, (Delivery) "For more on the specifics on the DeIC and SUNET products, please consult the NRENs.” Could it be a good Idea to have a single point of contact in NORDUnet, and perhaps appoint hugge as the “technial lead” to collect tech info? I think it will be a mess if they should contact each NREN for tech specifics, as it usually causes unnecessary noise/confusion.
-p3. as well. (Cost) "The cost for connectivity to ESS Lund (SUNET) and ESS Copenhagen (DeIC) should be agreed directly with the NRENs." Same take as above, I thought the document should collect and present 1 total cost to ESS? /Ras
On 21 Dec 2016, at 09:44, Fredrik Korsbäck hugge@nordu.net wrote:
On 20/12/16 16:32, Lars Fischer wrote:
All,
the description and offer has now been narrowed down to a description of the inter-site connectivity, on the assumption that ESS requires (and will be getting) upstream connectivity to DeIC and SUNET anyway.
Please read and comment; I will send the document to ESS this week.
/Lars
Essnet mailing list Essnet@lists.nordu.net https://lists.nordu.net/listinfo/essnet
I think the document makes sense. A few points.
· A 10Gbps monitoring node at each site, with a web-based portal for regular and ad-hoc latency and capacity tests between sites as well as between ESS and sites on the NORDUnet network.
Whats this? Perfsonar?
Should we also elaborate that the path between Lund and Copenhagen will actually be over Öresundsbron? to further cement the fact that we have the shortest possible path there is inbetween these sites. So we can be fully compared to any commercial provider without any problem.
-- hugge
Essnet mailing list Essnet@lists.nordu.net https://lists.nordu.net/listinfo/essnet
On 21 Dec 2016, at 10:34, Rasmus Lund wrote:
- On p.3, (Delivery) "For more on the specifics on the DeIC and SUNET
products, please consult the NRENs.” Could it be a good Idea to have a single point of contact in NORDUnet, and perhaps appoint hugge as the “technial lead” to collect tech info? I think it will be a mess if they should contact each NREN for tech specifics, as it usually causes unnecessary noise/confusion.
Problem is, then Hugge has to understand the fibre path or whatever it is DeIC use to deliver in Copenhagen, and then explain it to ESS. It don’t think that’s productive for Hugge or helpful for ESS.
-p3. as well. (Cost) "The cost for connectivity to ESS Lund (SUNET) and ESS Copenhagen (DeIC) should be agreed directly with the NRENs." Same take as above, I thought the document should collect and present 1 total cost to ESS?
Yes, that was the original idea. However, it turns out that we can meet their needs with standard NERN products. In that case having NORDUnet “between” ESS and DeIC (say) adds nothing, and make everything more complicated. So in the end we gave up on that.
/Lars
-
Fredrik Korsbäck -
Lars Fischer -
Rasmus Lund