Changes between Version 16 and Version 17 of Nmm2022/Agenda/perfSONARuse

Timestamp:

Jul 13, 2022, 3:12:40 PM (2 years ago)

Author:

admin

Comment:

--

Nmm2022/Agenda/perfSONARuse

@@ -286 +286 @@
 {{{
 sudo esmond_manage add_user_ip_address username PS1_IP
+}}}
+
+Username can be anything and it is only for local reference of the Archive server. Below is the output of the successful command execution.
+
+{{{
+esmond [INFO] Checking/creating column families
+esmond [INFO] Schema check done
+esmond [DEBUG] Opening ConnectionPool
+esmond [INFO] Connected to ['localhost:9160']
+User learn exists
+Setting metadata POST permissions.
+api | ps metadata | Can add ps metadata
+api | ps metadata | Can change ps metadata
+api | ps metadata | Can delete ps metadata
+api | ps point to point subject | Can add ps point to point subject
+api | ps point to point subject | Can change ps point to point subject
+api | ps point to point subject | Can delete ps point to point subject
+api | ps event types | Can add ps event types
+api | ps event types | Can change ps event types
+api | ps event types | Can delete ps event types
+api | ps metadata parameters | Can add ps metadata parameters
+api | ps metadata parameters | Can change ps metadata parameters
+api | ps metadata parameters | Can delete ps metadata parameters
+api | ps network element subject | Can add ps network element subject
+api | ps network element subject | Can change ps network element subject
+api | ps network element subject | Can delete ps network element subject
+Setting timeseries permissions.
+Creating entry for IP [PS1_IP] belonging to [username]
+}}}
+
+In the same way add the user and IP address of the second perfSONAR node.
+
+{{{
 sudo esmond_manage add_user_ip_address username PS2_IP
 }}}
 
-Username can be anything and it is only for local reference of the Archive server.
+Step 7. Now we should let the Archive server know where the pSConfig template lives. Then it can locate the archive and display the data through the MaDDash. Enter the below for that,
+
+{{{
+psconfig remote add "https://MA_IP/psconfig/learn.json"
+}}}
+
+Now restart below services to make the changes to be effect.
+
+{{{
+systemctl restart cassandra
+systemctl restart maddash-server
+systemctl restart psconfig-maddash-agent
+}}}
+
+Step 8. Now you should switch to the perfSONAR nodes. On each node execute the below commands. These make the nodes consume the psconfig template file and executes the tasks on it. It also tells the nodes to send archive data to the Central Measurement Archive.
+
+On Central Measurement Archive,
+
+{{{
+psconfig remote add --configure-archives "https://[MA_IP]/psconfig/learn.json"
+}}}
+
+Then you should restart the below service,
+
+{{{
+systemctl restart psconfig-pscheduler-agent
+}}}
+
+If everything is successful you should see archive data receiving to the Central Measurement Archive server. Visit the url https://[MA_IP]/esmond/perfsonar/archive/ and you should see something like below,
+
+[[Image(https://ws.learn.ac.lk/raw-attachment/wiki/Nmm2022/Agenda/perfSONARuse/ps33.png)]]
+
+Now visit the MaDDash web interface from https://[MA_IP]/maddash-webui. You should be able to Dashboard items like below.
+
+[[Image(https://ws.learn.ac.lk/raw-attachment/wiki/Nmm2022/Agenda/perfSONARuse/ps34.png)]]
+
+Click on a grid item to view the results of a type of test,
+
+[[Image(https://ws.learn.ac.lk/raw-attachment/wiki/Nmm2022/Agenda/perfSONARuse/ps35.png)]]
+
+Hover on the grid to view the test results.
+
+[[Image(https://ws.learn.ac.lk/raw-attachment/wiki/Nmm2022/Agenda/perfSONARuse/ps36.png)]]
+