[
https://issues.apache.org/jira/browse/DLAB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Fuks updated DLAB-1356:
----------------------------
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"
was:
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"
> [Back-end]: Odahu (Legion) management in DLab
> ---------------------------------------------
>
> Key: DLAB-1356
> URL: https://issues.apache.org/jira/browse/DLAB-1356
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
> Reporter: Vira Vitanska
> Assignee: Oleg Fuks
> Priority: Major
> Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
> Fix For: v.2.3
>
>
> 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"
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
