Skip to content

Commit 2f82533

Browse files
authored
more polish of readme
1 parent 3845477 commit 2f82533

1 file changed

Lines changed: 11 additions & 10 deletions

File tree

README.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,17 @@ Namely it shows jobs of a Galaxy instance, their distribution over Pulsar comput
1313

1414
If you are an admin of a Galaxy instance please read the technical process below, if you are not an admin please reach out to them.
1515

16+
### Summary
17+
18+
*Start with writing us an email at galaxy@cesnet.cz that you'd like to join. First we will celebrate and then happily walk you through what needs to be done.*
19+
20+
1) Your Galaxy needs to be sending data to your InfluxDB via [gxadmin scripts](https://github.com/usegalaxy-eu/infrastructure-playbook/tree/master/roles/usegalaxy-eu.job-radar-stats-influxdb)
21+
1) You give us access to read the InfluxDB (we need: `influxdb_password_var_name;influxdb_host;influxdb_port;influxdb_username`) and some basic information about your server (we need: `name;lat;long;`)
22+
1) You send us information about your Pulsar servers (we need: `galaxy;pulsar_id;lat;long;node_count;desc`)
23+
1) Wait few days and your Galaxy and Pulsars show up at [https://gjr.metacentrum.cz](https://gjr.metacentrum.cz)
24+
25+
### Details
26+
1627
GJR periodically requests data from each connected Galaxy through their own `InfluxDB` instance. Schema of this setup:
1728

1829
<img width="583" height="449" alt="image" src="https://github.com/user-attachments/assets/d1429cd4-53da-4c33-a8f0-dec6896d314a" />
@@ -23,16 +34,6 @@ Note: If you do not run InfluxDB for monitoring yet there is a Galaxy [training
2334

2435
<img width="537" height="212" alt="galaxy_data_flow" src="https://github.com/user-attachments/assets/b8d4dc16-8542-4c41-9e1b-b7800781c819" />
2536

26-
27-
### Summary:
28-
29-
*Please write us an email at galaxy@cesnet.cz that you'd like to join and we will walk you through what needs to be done.*
30-
31-
1) Your Galaxy is sending data to your InfluxDB via [gxadmin scripts](https://github.com/usegalaxy-eu/infrastructure-playbook/tree/master/roles/usegalaxy-eu.job-radar-stats-influxdb)
32-
1) You give us access to read the InfluxDB (`influxdb_password_var_name;influxdb_host;influxdb_port;influxdb_username`) and some basic information about your server (`name;lat;long;`)
33-
1) You send us information about all your Pulsar servers (`galaxy;pulsar_id;lat;long;node_count;desc`)
34-
1) Wait few days and your Galaxy and Pulsars show up at [https://gjr.metacentrum.cz](https://gjr.metacentrum.cz)
35-
3637
## How to deploy own GJR
3738

3839
GJR takes data from InfluxDB of a Galaxy instance so first you need to set up InfluxDB for your instance and periodically fill it with necessary data. There is Galaxy tutorial for Galaxy admins how to set up InfluxDB ([https://training.galaxyproject.org/training-material/topics/admin/tutorials/monitoring/slides-plain.html](https://training.galaxyproject.org/training-material/topics/admin/tutorials/monitoring/slides-plain.html)). Ansible infrastructure play-book for filling InfluxDB with neccessary data can be find here: [https://github.com/usegalaxy-eu/infrastructure-playbook/tree/master/roles/usegalaxy-eu.job-radar-stats-influxdb](https://github.com/usegalaxy-eu/infrastructure-playbook/tree/master/roles/usegalaxy-eu.job-radar-stats-influxdb).

0 commit comments

Comments
 (0)