Skip to content

Assignment 4 Custos Deployment

Krishna Vamsi Guntupalli edited this page May 6, 2022 · 6 revisions

We give all the credits for the deployment of custos to the teams Terra, CloudElves, DSDummies, Scapsulators. If not their documentation we would not have able to complete this. We used 1 master node and 1 worker node.

Screen Shot 2022-05-06 at 2 48 34 AM Screen Shot 2022-05-06 at 3 10 44 AM

API End Point: https://js-169-255.jetstream-cloud.org/tenant-management/v1.0.0/oauth2/tenant

POST Request:
{
    "client_name":"test3",
    "requester_email":"[email protected]",
    "admin_username":"testa",
    "admin_first_name":"test1",
    "admin_last_name":"test1",
    "admin_email":"[email protected]",
    "contacts":["[email protected]","[email protected]"],
    "redirect_uris":["http://localhost:8080/callback*",
    "https://js-169-255.jetstream-cloud.org/callback*"],
    "scope":"openid profile email org.cilogon.userinfo",
    "domain":"js-169-255.jetstream-cloud.org",
    "admin_password":"test",
    "client_uri":"https://js-169-225.jetstream-cloud.org/",
    "logo_uri":"https://js-169-225.jetstream-cloud.org/",
    "application_type":"web",
    "comment":"Custos super tenant for test"
}
Output:

{
    "client_id": "custos-inzym262r7ygvk5olplr-10000001",
    "client_secret": "DuMhz0Ax4T63SvEXFzyKJcOtXvnZg4XfLgMQOEgH",
    "is_activated": false,
    "client_id_issued_at": 1651819401000,
    "client_secret_expires_at": 0,
    "registration_client_uri": "https://custos.scigap.org/apiserver/tenant-management/v1.0.0/oauth2/tenant?client_id=custos-inzym262r7ygvk5olplr-10000001",
    "token_endpoint_auth_method": "client_secret_basic",
    "msg": "Use Base64 encoded clientId:clientSecret as auth token for authorization, Credentials are activated after admin approval"
}

Challenges:

  • Initially we faced lot of hurdles in setting up a kubernetes cluster using ranches in jetstream2. But finally with the help of team terra we are able to overcome these hurdles and installed it on jetstream1.
  • We faced issues connecting to the the DB, but this got resolved by creating the directories instead of volumes.
  • We faced another issue while launching the postgres server. Again thanks to team terra for helping us by providing the solution to use postgres as username and password.
  • Choosing Jetstream1 over jetstream2 has solved many of the issues which we faced.
  • The documentation is not user friendly. May be if the documentation is more clear, we would not have faced many of the mentioned issues. But thanks to Isuru, Teaching Assistants and all other teams for helping us in resolving the issues.