You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To test the score uploads and downloads, ego, song and score services must be running and healthy. Since the score service responds with presigned s3 urls that use the minio-api as the service name, the urls would not be resolvable outside of the defined `docker-swarm-network`. To fix this, a convienece docker image state was created in the Dockerfile (target is called `genomic-transfer-helper`) which pulls the appropriate song-client and score-client distributions and configures them with the right JWT. The following instructions will allow you to download and upload using this tool:
19
+
1. Log in to the EGO-UI service. The default local url is http://localhost:9002
20
+
2. Log out
21
+
3. By default, new users obtain the role `USER`. In order to proceed, the `ADMIN` role is needed. To do this, run the following command
22
+
```
23
+
docker exec -it $(docker service ps ego-db --no-trunc --format '{{ .Name }}.{{.ID}}' | head -1) psql -U postgres ego -c "UPDATE egouser set type='ADMIN' where email='<the-email-you-logged-in-with-previously>' and providertype='<one of: GOOGLE,LINKEDIN,FACEBOOK,GITHUB,ORCID>';"
24
+
```
25
+
5. Log in again into EGO-UI (http://localhost:9002) and now you should be able to use the UI
26
+
6. Select `Users` in the side bar, and then select your user record. On the right most pane, click the `Edit` button at the top and then click the `+ Add` button for the `Groups` section, and add your self to the `dcc-admin` group. Then click the `Save` button at the top. This will give you the neccessary permissions to use song and score.
27
+
7. Log out
28
+
8. Start the browsers inspector tool (this will be different for each browser) and filter for XHR requests.
29
+
9. Log in to the EGO-UI. Once logged in, refer to response for the `ego-token?client_id=ego-ui` request. This is the JWT
30
+
10. Copy and paste the JWT from the previous step into the file `./jwt.txt`.
31
+
11. Run `make start-transfer-shell`. This will automatically run the `genomic-transfer-helper` and load the contents of `jwt.txt` as the JWT to allow authorized access to song and score.
32
+
12. Once logged into the container, you can use the score and song clients. Run `./song-client/bin/sing ping` and `curl $(curl -sL http://score-api:8080/download/ping)` to do a health check.
33
+
17
34
## Tips
18
35
### Checking for OOM messages when a container/service is killed
19
36
Sometimes, if the reserved/limit memory is too low, a container will get killed by the kernel. To find out if this is the case, run
Copy file name to clipboardExpand all lines: src/main/resources/application.yml
+2-2
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ compose:
24
24
network: dms-swarm-network
25
25
26
26
docker:
27
-
#NOTE: Indicates if this application is RUNNING-AS a docker container on the host machine, or running on baremetal on the host machine. This is mostly to help resolve the what URLs the DMS uses to interact with the services. If its RUNNING-AS a docker container, then it will be in the dms dswarm network, and so it can use the service names as the domain in the urls, since docker will resolve the IP. If its not, then the url for the service will be used.
27
+
#NOTE: Indicates if this application is RUNNING-AS a docker container on the host machine. If false, then it is running on bare-metal on the host machine. This is mostly to help resolve the what URLs the DMS uses to interact with the services. If its RUNNING-AS a docker container, then it will be in the dms swarm network, and so it can use the service names as the domain in the urls, since docker will resolve the IP. If its not, then the url for the service will be used.
28
28
run-as: false
29
-
# If blank, will use the system default docker daemon
29
+
# If blank, will use the system default docker daemon. Useful for using a remote docker daemon.
0 commit comments