Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    markcorsi
    @markcorsi
    After locking up the machine for nearly an hour, kubernetes finally came up. There are now only one pod for each of the yaml files I modified. However, the problem still exists. It still loops back to localhost. Here are the pods:
    root@ip-172-31-73-161:~# kubectl -n vinlab get pod
    NAME READY STATUS RESTARTS AGE
    redis-deployment-756b4b8956-55p5v 1/1 Running 2 13d
    id-generator-deployment-7454b7bf6d-qrmh7 2/2 Running 4 13d
    minio-deployment-556459976d-6sxvk 1/1 Running 2 13d
    svclb-vinlab-lb-hrdsk 1/1 Running 2 13d
    vinlab-api-deployment-d4fbc5c5f-whcs7 1/1 Running 13 13d
    orthanc-deployment-fb799595-2zqqb 1/1 Running 2 13d
    vinlab-uploader-deployment-785449b44f-xlkn4 1/1 Running 2 13d
    apigateway-deployment-d6dcc5d8f-8zt4d 1/1 Running 3 13d
    es-deployment-779db4985d-vgv2m 1/1 Running 2 13d
    vinlab-dashboard-deployment-df449f65-8sgjq 1/1 Running 0 80m
    vinlab-viewer-deployment-69c76f4ff9-spd6s 1/1 Running 0 80m
    keycloak-deployment-68b78d9b67-gnfqv 1/1 Running 3 13d
    And here is the loopback url:
    You should be able to see this process yourself by going to:
    Thanks for all the help up till now. Any other ideas?
    simisimi
    @iamatsundere
    Hm, I think there is an issue somewhere
    Maybe you can go to the Keycloak url, choose vinlab-frontend and change all the URL fields to *
    But I think it is not the root cause
    markcorsi
    @markcorsi
    Hi - I think there was something weird with Kubernetes and the acceptance of the new yaml files. Last night, the machine locked up entirely and we were forced to reboot it from the AWS console. When It came up, everything is now working! Thanks for the help!!
    markcorsi
    @markcorsi
    Now that I am into the setup screens, I have found some issues that I don't understand and I can't find the explanations in the documentation. I set up a project and went into the 'data' screen. The 'import data' button is greyed out. How do I import the first studies into the project? Also, on the settings tab in the workflow section. The project owner is listed but there are no reviewers nor annotators. I have three users all of whom have reviewer and annotator roles but when I click the search box under reviewer, the pop up box says 'no data'. When I try to save the settings, the reviewer box is hilighted in red with a 'Please select users' message. Under the 'Tasks' tab, I do not see any way of setting up new tasks. I think some of the above issues are interrelated. Can you please walk me through them? I have been through the instructions at: https://vinbigdata-medical.github.io/vindr-lab/user-guide/project/ but was unable to find solutions to these issues. Is there any place else I should look? Thanks again!
    simisimi
    @iamatsundere
    Thanks for replying, it is good to see it works normally, at least in the services-to-services interface
    About your issue, just re-confirm that your user have role: Project Owner in the Keycloak
    About the Import data button, please send us some screenshot
    simisimi
    @iamatsundere
    About getting users in the Settings tab, I think you've changed the password of the Keycloak's master account. If it's true, you will have to change the password of Keycloak account in the setting of vindr-lab-api too.
    Hope it'll help you.
    Nghia
    @Lego1st
    About the way of setting up new tasks, please refer to the following section https://vinbigdata-medical.github.io/vindr-lab/user-guide/project/#assignment
    markcorsi
    @markcorsi
    Regarding your second comment above. I assume you mean: vinlab-api.deployment.yaml
    markcorsi
    @markcorsi
    Another question is, once I make a change to the yaml files, how do I force kubernetes to accept those new parameters? The only way I have found so far is a hard reboot from the AWS console and that is equivalent to hitting the power button so not super desirable. Soft reboots leave behind the old configuration 'pod' for some reason.
    simisimi
    @iamatsundere
    Normally, you just use kubectl -n vinlab apply -f vinlab-viewer.deployment.yaml, then check it again by kubectl -n vinlab get pod
    simisimi
    @iamatsundere

    Regarding your second comment above. I assume you mean: vinlab-api.deployment.yaml

    Sure it is

    Daphne Soegijono
    @dsoegijono
    I received a demo login that I requested, but the demo site doesn't seem to be reachable? https://demo-lab.vindr.ai/
    Nghia
    @Lego1st

    I received a demo login that I requested, but the demo site doesn't seem to be reachable? https://demo-lab.vindr.ai/

    Sorry for that conveinient, I will check it out and come back to you later.

    Daphne Soegijono
    @dsoegijono
    Thank you
    1 reply