Details
-
Feature
-
Should have
-
SRCnet
-
-
-
1.5
-
0.5
-
0
-
Team_PURPLE
-
Sprint 5
-
-
-
-
PI24-PB
Description
Documenting the deployment of this compulsory service is covered in another feature SP-4617. Collaborate there.
Creating a helm chart is covered here: SP-4598
Keeping JIC this should be split into another feature:
A perfSONAR mesh will create automated tests for long term monitoring of networking. This will show if there are intermittent, difficult to detect connection problems.
For this to function all sites in SRCnet0.1 must be represented in the SKA perfSONAR mesh. This will allow testing between all sites to show any intermittent faults.
AC2: All participating SRCnet0.1 sites show functional results through scheduled testing, with the information being readily available locatable.{}
perfSONAR is a toolkit used to test network capabilities through long term scheduled tests. These tests are used to detect intermittent connection issues over long periods, including trends in bandwidth/latency that would be difficult to detect without long term, repeated testing.
The SRCnet0.1 mandates all SRCnet0.1 sites have a perfSONAR node integrated into the SKA mesh to test connections between all SRC sites. This is to rule out networking/hardware issues when troubleshooting future data movement. For the launch of SRCnet0.1, perfSONAR nodes do not have to be dedicated SKA perfSONAR nodes (i.e. they can be shared with other projects). This is to establish a baseline of connection data between sites, with future plans to ensure perfSONAR can also test the performance of the network as close to the data end points as possible.