[jira] [Updated] (DLAB-1338) DLab + Legion

["Vira Vitanska (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DLAB-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vira Vitanska updated DLAB-1338:
--------------------------------
    Description: 
Who manages Legion provisioning:
 * Admin or DLab user?

1. Legion cluster will be deployed per project-endpoint
 2. Under Administration page:
   2.1. Add a page: Legion deployment
   2.2. Page should contain grid with following information:
 - Project Name
 - Endpoint URL
 - Legion cluster Name
 - Legion cluster status
 - Number of Legion cluster nodes
 - Actions column:
 ## Start/Stop?
 ## Terminate?
 ## Scale-down
 ## Scale-up

   2.3. Create Legion cluster popup:
 - Select Project
 - Select Endpoint
 - Select existing k8s cluster (checkbox, once checked input field shows up where you can fill in "Legion k8s cluster URL")
 - Select number of shapes
 - Select instance shape
 - Select certificate? +(check with Vitalii Solodinov)+
 ## DLab passes this as input parameter for Legion provisioning script
 - VPC, Subnet will be auto-propagated from Project (visible = false)
 - NAT gateway
 ## Need Legion team to use Edge IP instead (proxy)
 - Buckets (visible = false)
 ## Bucket for Feedback (use Project bucket)
 ### Legion should access bucket name as parameter
 ## Bucket for State of Terraform (use Project bucket)
 ### Legion should access bucket name as parameter
 - Container registry (pass a parameter?)

 # Security params (keycloak, oauth and ssh key)
 # Repos (docker repo and creds, helm repos)

3. Under List of Resource page
 # Show additional column with Legion icon near every notebook
 # When use clicks on it -> popup shows up containing following information:
 ## URL for feedback storage
 ## URL for Swagger API registry
 ## URL for Grafana
 ## Etc
 # Extend current Actions menu for JupyterLab only with action "Attach Legion"

4. Billing
 # Add billing info to Billing report
 ## For each type of Legion resource - there should be a separate line-item in billing report
 # Extend in-grid billing with Legion billing data

5. Security - for authentication/authorization to work across Dlab and Legion:

# Use same realm for Dlab and Legion
 ## I should be able to login to DLab and I should not be asked to login going forward.

 

Questions:
 * If there are two users, two JupyterLabs connected to single Legion cluster, how Legion resources are allocated across two users?

> DLab + Legion
> -------------
>
>                 Key: DLAB-1338
>                 URL: https://issues.apache.org/jira/browse/DLAB-1338
>             Project: Apache DLab
>          Issue Type: Epic
>            Reporter: Vira Vitanska
>            Priority: Major
>
> Who manages Legion provisioning:
>  * Admin or DLab user?
> 1. Legion cluster will be deployed per project-endpoint
>  2. Under Administration page:
>    2.1. Add a page: Legion deployment
>    2.2. Page should contain grid with following information:
>  - Project Name
>  - Endpoint URL
>  - Legion cluster Name
>  - Legion cluster status
>  - Number of Legion cluster nodes
>  - Actions column:
>  ## Start/Stop?
>  ## Terminate?
>  ## Scale-down
>  ## Scale-up
>    2.3. Create Legion cluster popup:
>  - Select Project
>  - Select Endpoint
>  - Select existing k8s cluster (checkbox, once checked input field shows up where you can fill in "Legion k8s cluster URL")
>  - Select number of shapes
>  - Select instance shape
>  - Select certificate? +(check with Vitalii Solodinov)+
>  ## DLab passes this as input parameter for Legion provisioning script
>  - VPC, Subnet will be auto-propagated from Project (visible = false)
>  - NAT gateway
>  ## Need Legion team to use Edge IP instead (proxy)
>  - Buckets (visible = false)
>  ## Bucket for Feedback (use Project bucket)
>  ### Legion should access bucket name as parameter
>  ## Bucket for State of Terraform (use Project bucket)
>  ### Legion should access bucket name as parameter
>  - Container registry (pass a parameter?)
>  # Security params (keycloak, oauth and ssh key)
>  # Repos (docker repo and creds, helm repos)
> 3. Under List of Resource page
>  # Show additional column with Legion icon near every notebook
>  # When use clicks on it -> popup shows up containing following information:
>  ## URL for feedback storage
>  ## URL for Swagger API registry
>  ## URL for Grafana
>  ## Etc
>  # Extend current Actions menu for JupyterLab only with action "Attach Legion"
> 4. Billing
>  # Add billing info to Billing report
>  ## For each type of Legion resource - there should be a separate line-item in billing report
>  # Extend in-grid billing with Legion billing data
> 5. Security - for authentication/authorization to work across Dlab and Legion:
> # Use same realm for Dlab and Legion
>  ## I should be able to login to DLab and I should not be asked to login going forward.
>  
> Questions:
>  * If there are two users, two JupyterLabs connected to single Legion cluster, how Legion resources are allocated across two users?



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org