[jira] [Created] (DLAB-2071) [Azure]: It's impossible to do any action via ungit
Vira Vitanska created DLAB-2071:
---
Summary: [Azure]: It's impossible to do any action via ungit
Key: DLAB-2071
URL: https://issues.apache.org/jira/browse/DLAB-2071
Project: Apache DLab
Issue Type: Bug
Components: Data Lab Main
Affects Versions: v.2.4
Reporter: Vira Vitanska
Attachments: image-2020-09-22-13-46-33-992.png
*Preconditions:*
# Jupyter (or the other notebook) is created
# Git credentials are added (gitlab)
*Steps to reproduce:*
1. Clone repo via ungit
*Actual result:*
# There is an error
{code:java}
File "/root/scripts/common_download_git_certfile.py", line 53, in
if AzureActions().download_from_container(resource_group_name,
ssn_storage_account_name, container_name, gitlab_certfile):
NameError: name 'ssn_storage_account_name' is not defined
{code}
*Expected result:*
# There isn't any error
--
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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error
[
https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1867:
Attachment: (was: Azure Rstudio local.png)
> [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with
> error
> ---
>
> Key: DLAB-1867
> URL: https://issues.apache.org/jira/browse/DLAB-1867
> Project: Apache DLab
> Issue Type: Bug
> Components: Data Lab Main
> Environment: Branch-515
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AZURE, Debian, DevOps, Known_issues(release2.4)
> Attachments: image-2020-09-22-13-23-03-877.png
>
>
> *Preconditions:*
> 1. RStudio is created on Azure
> *Steps to reproduce:*
> 1. Run Flight_data_Preparation_R
> *Actual result:*
> 1. Playbook runs with error:
> Error in read.df(bucket_path("carriers.csv"), "csv", header = "true", :
> could not find function "read.df"
> *Expected result:*
> # Playbook runs successfully
>
>
--
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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error
[
https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1867:
Attachment: (was: EMR.png)
> [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with
> error
> ---
>
> Key: DLAB-1867
> URL: https://issues.apache.org/jira/browse/DLAB-1867
> Project: Apache DLab
> Issue Type: Bug
> Components: Data Lab Main
> Environment: Branch-515
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AZURE, Debian, DevOps, Known_issues(release2.4)
> Attachments: image-2020-09-22-13-23-03-877.png
>
>
> *Preconditions:*
> 1. RStudio is created on Azure
> *Steps to reproduce:*
> 1. Run Flight_data_Preparation_R
> *Actual result:*
> 1. Playbook runs with error:
> Error in read.df(bucket_path("carriers.csv"), "csv", header = "true", :
> could not find function "read.df"
> *Expected result:*
> # Playbook runs successfully
>
>
--
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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error
[
https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1867:
Description:
*Preconditions:*
1. RStudio is created on Azure
*Steps to reproduce:*
1. Run Flight_data_Preparation_R
*Actual result:*
1. Playbook runs with error:
Error in read.df(bucket_path("carriers.csv"), "csv", header = "true", :
could not find function "read.df"
*Expected result:*
# Playbook runs successfully
was:
*Preconditions:*
1. RStudio iscreated on Azure
*Steps to reproduce:*
1. Run Flight_data_Preparation_R for local/remote kernels
*Actual result:*
1. Playbook runs with error:
Java version 8 is required for this package; found version: 11.0.7
*Expected result:*
# Playbook runs successfully
> [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with
> error
> ---
>
> Key: DLAB-1867
> URL: https://issues.apache.org/jira/browse/DLAB-1867
> Project: Apache DLab
> Issue Type: Bug
> Components: Data Lab Main
> Environment: Branch-515
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AZURE, Debian, DevOps, Known_issues(release2.4)
> Attachments: image-2020-09-22-13-23-03-877.png
>
>
> *Preconditions:*
> 1. RStudio is created on Azure
> *Steps to reproduce:*
> 1. Run Flight_data_Preparation_R
> *Actual result:*
> 1. Playbook runs with error:
> Error in read.df(bucket_path("carriers.csv"), "csv", header = "true", :
> could not find function "read.df"
> *Expected result:*
> # Playbook runs successfully
>
>
--
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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error
[
https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1867:
Attachment: (was: Spark-local.png)
> [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with
> error
> ---
>
> Key: DLAB-1867
> URL: https://issues.apache.org/jira/browse/DLAB-1867
> Project: Apache DLab
> Issue Type: Bug
> Components: Data Lab Main
> Environment: Branch-515
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AZURE, Debian, DevOps, Known_issues(release2.4)
> Attachments: image-2020-09-22-13-23-03-877.png
>
>
> *Preconditions:*
> 1. RStudio is created on Azure
> *Steps to reproduce:*
> 1. Run Flight_data_Preparation_R
> *Actual result:*
> 1. Playbook runs with error:
> Error in read.df(bucket_path("carriers.csv"), "csv", header = "true", :
> could not find function "read.df"
> *Expected result:*
> # Playbook runs successfully
>
>
--
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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error
[ https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1867: Attachment: image-2020-09-22-13-23-03-877.png > [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with > error > --- > > Key: DLAB-1867 > URL: https://issues.apache.org/jira/browse/DLAB-1867 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main > Environment: Branch-515 >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AZURE, Debian, DevOps, Known_issues(release2.4) > Attachments: Azure Rstudio local.png, EMR.png, Spark-local.png, > image-2020-09-22-13-23-03-877.png > > > *Preconditions:* > 1. RStudio iscreated on Azure > *Steps to reproduce:* > 1. Run Flight_data_Preparation_R for local/remote kernels > *Actual result:* > 1. Playbook runs with error: > Java version 8 is required for this package; found version: 11.0.7 > *Expected result:* > # Playbook runs successfully > > -- 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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error for local/remote kernels
[ https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1867: Attachment: (was: AWS-RStudio-hadoop.png) > [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with > error for local/remote kernels > > > Key: DLAB-1867 > URL: https://issues.apache.org/jira/browse/DLAB-1867 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main > Environment: Branch-515 >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AZURE, Debian, DevOps, Known_issues(release2.4) > Attachments: Azure Rstudio local.png, EMR.png, Spark-local.png > > > *Preconditions:* > 1. RStudio iscreated on Azure > *Steps to reproduce:* > 1. Run Flight_data_Preparation_R for local/remote kernels > *Actual result:* > 1. Playbook runs with error: > Java version 8 is required for this package; found version: 11.0.7 > *Expected result:* > # Playbook runs successfully > > -- 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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error for local/remote kernels
[ https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1867: Labels: AZURE Debian DevOps Known_issues(release2.4) (was: AZURE Debian DevOps) > [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with > error for local/remote kernels > > > Key: DLAB-1867 > URL: https://issues.apache.org/jira/browse/DLAB-1867 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main > Environment: Branch-515 >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AZURE, Debian, DevOps, Known_issues(release2.4) > Attachments: Azure Rstudio local.png, EMR.png, Spark-local.png > > > *Preconditions:* > 1. RStudio iscreated on Azure > *Steps to reproduce:* > 1. Run Flight_data_Preparation_R for local/remote kernels > *Actual result:* > 1. Playbook runs with error: > Java version 8 is required for this package; found version: 11.0.7 > *Expected result:* > # Playbook runs successfully > > -- 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
[jira] [Updated] (DLAB-1867) [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error
[ https://issues.apache.org/jira/browse/DLAB-1867?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1867: Summary: [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error (was: [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with error for local/remote kernels) > [Branch-515][Azure][RStudio]: Playbook Flight_data_Preparation_R run with > error > --- > > Key: DLAB-1867 > URL: https://issues.apache.org/jira/browse/DLAB-1867 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main > Environment: Branch-515 >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AZURE, Debian, DevOps, Known_issues(release2.4) > Attachments: Azure Rstudio local.png, EMR.png, Spark-local.png > > > *Preconditions:* > 1. RStudio iscreated on Azure > *Steps to reproduce:* > 1. Run Flight_data_Preparation_R for local/remote kernels > *Actual result:* > 1. Playbook runs with error: > Java version 8 is required for this package; found version: 11.0.7 > *Expected result:* > # Playbook runs successfully > > -- 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
[jira] [Updated] (DLAB-2067) [DevOps]: Replace old name by new one in all sources
[ https://issues.apache.org/jira/browse/DLAB-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2067: Description: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. In sources instead of 'dlab' use 'data-lab'. was: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. > [DevOps]: Replace old name by new one in all sources > > > Key: DLAB-2067 > URL: https://issues.apache.org/jira/browse/DLAB-2067 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. > In sources instead of 'dlab' use 'data-lab'. -- 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
[jira] [Updated] (DLAB-2066) [Back-end]: Replace old name by new one in all sources
[ https://issues.apache.org/jira/browse/DLAB-2066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2066: Description: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. In sources instead of 'dlab' use 'data-lab'. was: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. > [Back-end]: Replace old name by new one in all sources > -- > > Key: DLAB-2066 > URL: https://issues.apache.org/jira/browse/DLAB-2066 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. > In sources instead of 'dlab' use 'data-lab'. -- 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
[jira] [Updated] (DLAB-2068) [Front-end]: Replace old name by new one in all sources
[ https://issues.apache.org/jira/browse/DLAB-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2068: Description: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. In sources instead of 'dlab' use 'data-lab'. was: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. > [Front-end]: Replace old name by new one in all sources > --- > > Key: DLAB-2068 > URL: https://issues.apache.org/jira/browse/DLAB-2068 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. > In sources instead of 'dlab' use 'data-lab'. -- 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
[jira] [Assigned] (DLAB-2067) [DevOps]: Replace old name by new one in all sources
[ https://issues.apache.org/jira/browse/DLAB-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-2067: --- Assignee: Mykola Bodnar (was: Leonid Frolov) > [DevOps]: Replace old name by new one in all sources > > > Key: DLAB-2067 > URL: https://issues.apache.org/jira/browse/DLAB-2067 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. -- 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
[jira] [Updated] (DLAB-772) [Data Lab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags
[ https://issues.apache.org/jira/browse/DLAB-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-772: --- Epic Name: [Data Lab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags (was: [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags) Summary: [Data Lab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags (was: [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags) > [Data Lab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, > Custom Tags > - > > Key: DLAB-772 > URL: https://issues.apache.org/jira/browse/DLAB-772 > Project: Apache DLab > Issue Type: Epic > Components: Data Lab Main >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > *_Types of tags:_* > * *_Data Lab Tag / SBN name:_* > o _auto-assigned tag (current behavior)_ > * *_endpoint_tag:_* > o _manual input from Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_project_tag:_* > o _manual input from Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_user_tag:_* > o _Autogenerated_ > o _format: [user_n...@domain.com]_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_custom_tag:_* > o _manual input from Web UI, can be changed from Web UI_ > o _can be changed on Web UI, should be visible on Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > __ > # _Admin created Endpoint1 with *endpoint_tag:Endpoint1*_ > # _All resources within Endpoint (notebook, cluster) > obtain*endpoint_tag:Endpoint1*_ > # _Admin created Project1 with *project_tag:Project1* and assign Endpoint1 > to that project_ > # _All resources within Endpoint (notebook, cluster) obtain additional tag > *project_tag:Project1*_ > # _User1 created notebook within Project1 with custom*custom_tag:Custom1*_ > # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project1, > user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], > custom_tag:custom1*_ > # _Admin created Project 2 with *project_tag:Project2* and assign Endpoint1 > to that project_ > # _All resources within Endpoint (notebook, cluster) obtain additional tag > *project_tag:Project2*_ > # _User1 creates notebook within Project2 with custom*custom_tag:Custom2*_ > # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project2, > user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], > custom_tag:custom2*_ -- 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
[jira] [Updated] (DLAB-772) [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags
[ https://issues.apache.org/jira/browse/DLAB-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-772: --- Description: *_Types of tags:_* * *_Data Lab Tag / SBN name:_* o _auto-assigned tag (current behavior)_ * *_endpoint_tag:_* o _manual input from Web UI_ o _assigned to notebooks, clusters, including Service data engines_ * *_project_tag:_* o _manual input from Web UI_ o _assigned to notebooks, clusters, including Service data engines_ * *_user_tag:_* o _Autogenerated_ o _format: [user_n...@domain.com]_ o _assigned to notebooks, clusters, including Service data engines_ * *_custom_tag:_* o _manual input from Web UI, can be changed from Web UI_ o _can be changed on Web UI, should be visible on Web UI_ o _assigned to notebooks, clusters, including Service data engines_ __ # _Admin created Endpoint1 with *endpoint_tag:Endpoint1*_ # _All resources within Endpoint (notebook, cluster) obtain*endpoint_tag:Endpoint1*_ # _Admin created Project1 with *project_tag:Project1* and assign Endpoint1 to that project_ # _All resources within Endpoint (notebook, cluster) obtain additional tag *project_tag:Project1*_ # _User1 created notebook within Project1 with custom*custom_tag:Custom1*_ # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project1, user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], custom_tag:custom1*_ # _Admin created Project 2 with *project_tag:Project2* and assign Endpoint1 to that project_ # _All resources within Endpoint (notebook, cluster) obtain additional tag *project_tag:Project2*_ # _User1 creates notebook within Project2 with custom*custom_tag:Custom2*_ # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project2, user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], custom_tag:custom2*_ was: *_Types of tags:_* * *_DLab Tag / SBN name:_* o _auto-assigned tag (current behavior)_ * *_endpoint_tag:_* o _manual input from Web UI_ o _assigned to notebooks, clusters, including Service data engines_ * *_project_tag:_* o _manual input from Web UI_ o _assigned to notebooks, clusters, including Service data engines_ * *_user_tag:_* o _Autogenerated_ o _format: [user_n...@domain.com]_ o _assigned to notebooks, clusters, including Service data engines_ * *_custom_tag:_* o _manual input from Web UI, can be changed from Web UI_ o _can be changed on Web UI, should be visible on Web UI_ o _assigned to notebooks, clusters, including Service data engines_ __ # _Admin created Endpoint1 with *endpoint_tag:Endpoint1*_ # _All resources within Endpoint (notebook, cluster) obtain*endpoint_tag:Endpoint1*_ # _Admin created Project1 with *project_tag:Project1* and assign Endpoint1 to that project_ # _All resources within Endpoint (notebook, cluster) obtain additional tag *project_tag:Project1*_ # _User1 created notebook within Project1 with custom*custom_tag:Custom1*_ # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project1, user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], custom_tag:custom1*_ # _Admin created Project 2 with *project_tag:Project2* and assign Endpoint1 to that project_ # _All resources within Endpoint (notebook, cluster) obtain additional tag *project_tag:Project2*_ # _User1 creates notebook within Project2 with custom*custom_tag:Custom2*_ # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project2, user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], custom_tag:custom2*_ > [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom > Tags > - > > Key: DLAB-772 > URL: https://issues.apache.org/jira/browse/DLAB-772 > Project: Apache DLab > Issue Type: Epic > Components: Data Lab Main >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > *_Types of tags:_* > * *_Data Lab Tag / SBN name:_* > o _auto-assigned tag (current behavior)_ > * *_endpoint_tag:_* > o _manual input from Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_project_tag:_* > o _manual input from Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_user_tag:_* > o _Autogenerated_ > o _format: [user_n...@domain.com]_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_custom_tag:_* > o _manual input from Web UI, can be changed from Web UI_ > o _can be changed on Web UI, should be visible on Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > __ > # _Admin created Endpoint1 with *endpoint_tag:Endpoint1*_ > # _All resources within
[jira] [Updated] (DLAB-629) Implement Data Lab main Component
[ https://issues.apache.org/jira/browse/DLAB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-629: --- Epic Name: Implement Data Lab main Component (was: Implement DLab main Component) Summary: Implement Data Lab main Component (was: Implement DLab main Component) > Implement Data Lab main Component > - > > Key: DLAB-629 > URL: https://issues.apache.org/jira/browse/DLAB-629 > Project: Apache DLab > Issue Type: Epic > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-772) [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags
[ https://issues.apache.org/jira/browse/DLAB-772?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-772: --- Epic Name: [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags (was: [DLab tags]: DLab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags) Summary: [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags (was: [DLab tags]: DLab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom Tags) > [DLab tags]: Data Lab tag, Cloud Endpoint Tag, Project Tag, User Tag, Custom > Tags > - > > Key: DLAB-772 > URL: https://issues.apache.org/jira/browse/DLAB-772 > Project: Apache DLab > Issue Type: Epic > Components: Data Lab Main >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > *_Types of tags:_* > * *_DLab Tag / SBN name:_* > o _auto-assigned tag (current behavior)_ > * *_endpoint_tag:_* > o _manual input from Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_project_tag:_* > o _manual input from Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_user_tag:_* > o _Autogenerated_ > o _format: [user_n...@domain.com]_ > o _assigned to notebooks, clusters, including Service data engines_ > * *_custom_tag:_* > o _manual input from Web UI, can be changed from Web UI_ > o _can be changed on Web UI, should be visible on Web UI_ > o _assigned to notebooks, clusters, including Service data engines_ > __ > # _Admin created Endpoint1 with *endpoint_tag:Endpoint1*_ > # _All resources within Endpoint (notebook, cluster) > obtain*endpoint_tag:Endpoint1*_ > # _Admin created Project1 with *project_tag:Project1* and assign Endpoint1 > to that project_ > # _All resources within Endpoint (notebook, cluster) obtain additional tag > *project_tag:Project1*_ > # _User1 created notebook within Project1 with custom*custom_tag:Custom1*_ > # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project1, > user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], > custom_tag:custom1*_ > # _Admin created Project 2 with *project_tag:Project2* and assign Endpoint1 > to that project_ > # _All resources within Endpoint (notebook, cluster) obtain additional tag > *project_tag:Project2*_ > # _User1 creates notebook within Project2 with custom*custom_tag:Custom2*_ > # _That notebook obtains: *endpoint_tag:Endpoint1, project_tag:Project2, > user_tag:[user_na...@domain.com|mailto:user_na...@domain.com], > custom_tag:custom2*_ -- 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
[jira] [Updated] (DLAB-507) Upgrade Data Lab
[ https://issues.apache.org/jira/browse/DLAB-507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-507: --- Epic Name: Upgrade Data Lab (was: Upgrade DLab) Summary: Upgrade Data Lab (was: Upgrade DLab) > Upgrade Data Lab > > > Key: DLAB-507 > URL: https://issues.apache.org/jira/browse/DLAB-507 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- 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
[jira] [Updated] (DLAB-506) Data Lab tech-debt
[ https://issues.apache.org/jira/browse/DLAB-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-506: --- Summary: Data Lab tech-debt (was: Data Lab-debt) > Data Lab tech-debt > -- > > Key: DLAB-506 > URL: https://issues.apache.org/jira/browse/DLAB-506 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- 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
[jira] [Updated] (DLAB-506) Data Lab-debt
[ https://issues.apache.org/jira/browse/DLAB-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-506: --- Epic Name: Data Lab tech-debt (was: DLab tech-debt) Summary: Data Lab-debt (was: Tech-debt) > Data Lab-debt > - > > Key: DLAB-506 > URL: https://issues.apache.org/jira/browse/DLAB-506 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- 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
[jira] [Updated] (DLAB-1569) [Data Lab+Odahu]: User is not allowed to create computational resource
[ https://issues.apache.org/jira/browse/DLAB-1569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1569: Summary: [Data Lab+Odahu]: User is not allowed to create computational resource (was: [Dlab+Odahu]: User is not allowed to create computational resource) > [Data Lab+Odahu]: User is not allowed to create computational resource > -- > > Key: DLAB-1569 > URL: https://issues.apache.org/jira/browse/DLAB-1569 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.5 > > Attachments: odahu.png > > > *Preconditions:* > # SSN is created from odahu-integration branch > # Notebook is in running status > *Steps to reproduce:* > 1. Create computational resource > *Actual result:* > 1. User is not allowed to create computational resource > Expected result: > 1. User is allowed to create computational resource > -- 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
[jira] [Updated] (DLAB-1356) [Back-end]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1356: Description: Who manages Legion provisioning: * Admin or Data Lab 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)+- ## Data Lab 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 Data Lab > - > > Key: DLAB-1356 > URL: https://issues.apache.org/jira/browse/DLAB-1356 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.5 > > > Who manages Legion provisioning: > * Admin or Data Lab 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)+- > ## Data Lab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from
[jira] [Updated] (DLAB-556) [Create DataLabcli]: Create python common logger
[ https://issues.apache.org/jira/browse/DLAB-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-556: --- Summary: [Create DataLabcli]: Create python common logger (was: [Create dlabcli]: Create python common logger) > [Create DataLabcli]: Create python common logger > > > Key: DLAB-556 > URL: https://issues.apache.org/jira/browse/DLAB-556 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Old >Reporter: Vira Vitanska >Priority: Major > Labels: 2.3_old, AWS, AZURE, Debian, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-1356) [Back-end]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1356: Summary: [Back-end]: Odahu (Legion) management in Data Lab (was: [Back-end]: Odahu (Legion) management in DLab) > [Back-end]: Odahu (Legion) management in Data Lab > - > > Key: DLAB-1356 > URL: https://issues.apache.org/jira/browse/DLAB-1356 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.5 > > > 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
[jira] [Updated] (DLAB-564) [Create DataLabcli]: Unit tests
[ https://issues.apache.org/jira/browse/DLAB-564?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-564: --- Summary: [Create DataLabcli]: Unit tests (was: [Create dlabcli]: Unit tests) > [Create DataLabcli]: Unit tests > --- > > Key: DLAB-564 > URL: https://issues.apache.org/jira/browse/DLAB-564 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Old >Reporter: Vira Vitanska >Priority: Minor > Labels: AWS, AZURE, Debian, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-566) [Create DataLabcli]: Migration on wiki
[ https://issues.apache.org/jira/browse/DLAB-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-566: --- Summary: [Create DataLabcli]: Migration on wiki (was: [Create dlabcli]: Migration on wiki) > [Create DataLabcli]: Migration on wiki > -- > > Key: DLAB-566 > URL: https://issues.apache.org/jira/browse/DLAB-566 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Priority: Minor > Labels: 2.3_old > -- 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
[jira] [Updated] (DLAB-567) [Create DataLabcli]: Rebuild dockers script (versioning)
[ https://issues.apache.org/jira/browse/DLAB-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-567: --- Summary: [Create DataLabcli]: Rebuild dockers script (versioning) (was: [Create dlabcli]: Rebuild dockers script (versioning) ) > [Create DataLabcli]: Rebuild dockers script (versioning) > - > > Key: DLAB-567 > URL: https://issues.apache.org/jira/browse/DLAB-567 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Old >Reporter: Vira Vitanska >Priority: Minor > Labels: 2.3_old, AWS, AZURE, Debian, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-1048) [Terraform]: Add possibility to login Data Lab via 443 port
[ https://issues.apache.org/jira/browse/DLAB-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1048: Description: As an user I want to use TLS/SSL during login Data Lab, so that I can be provided by communications security. Currently user can login Data Lab via 80 port. Please, add possibility to login via 443 port. was: As an user I want to use TLS/SSL during login DLab, so that I can be provided by communications security. Currently user can login DLab via 80 port. Please, add possibility to login via 443 port. > [Terraform]: Add possibility to login Data Lab via 443 port > --- > > Key: DLAB-1048 > URL: https://issues.apache.org/jira/browse/DLAB-1048 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: 2.3_old, AWS, Debian, DevOps > > As an user I want to use TLS/SSL during login Data Lab, so that I can be > provided by communications security. > Currently user can login Data Lab via 80 port. > Please, add possibility to login via 443 port. -- 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
[jira] [Updated] (DLAB-568) [Create DataLabcli]: Provide possibility to manage infrastructure flows (control deployment procedure)
[ https://issues.apache.org/jira/browse/DLAB-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-568: --- Summary: [Create DataLabcli]: Provide possibility to manage infrastructure flows (control deployment procedure) (was: [Create dlabcli]: Provide possibility to manage infrastructure flows (control deployment procedure)) > [Create DataLabcli]: Provide possibility to manage infrastructure flows > (control deployment procedure) > -- > > Key: DLAB-568 > URL: https://issues.apache.org/jira/browse/DLAB-568 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Priority: Minor > Labels: AWS, AZURE, Debian, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-1111) [DevOps]: Embed shared image functionality on Data Lab UI
[ https://issues.apache.org/jira/browse/DLAB-?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-: Summary: [DevOps]: Embed shared image functionality on Data Lab UI (was: [DevOps]: Embed shared image functionality on DLab UI) > [DevOps]: Embed shared image functionality on Data Lab UI > - > > Key: DLAB- > URL: https://issues.apache.org/jira/browse/DLAB- > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Priority: Major > Labels: 2.3_old, AWS, AZURE, Debian, DevOps, GCP, RedHat > > As an admin I want to turn on/off of using shared image in project setting so > that I can easily switch without changing configuration files via SSH. -- 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
[jira] [Updated] (DLAB-1048) [Terraform]: Add possibility to login Data Lab via 443 port
[ https://issues.apache.org/jira/browse/DLAB-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1048: Summary: [Terraform]: Add possibility to login Data Lab via 443 port (was: [Terraform]: Add possibility to login DLab via 443 port) > [Terraform]: Add possibility to login Data Lab via 443 port > --- > > Key: DLAB-1048 > URL: https://issues.apache.org/jira/browse/DLAB-1048 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: 2.3_old, AWS, Debian, DevOps > > As an user I want to use TLS/SSL during login DLab, so that I can be > provided by communications security. > Currently user can login DLab via 80 port. > Please, add possibility to login via 443 port. -- 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
[jira] [Updated] (DLAB-1110) [Back-end][Part1]: Embed shared image functionality on Data Lab UI
[ https://issues.apache.org/jira/browse/DLAB-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1110: Summary: [Back-end][Part1]: Embed shared image functionality on Data Lab UI (was: [Back-end][Part1]: Embed shared image functionality on DLab UI) > [Back-end][Part1]: Embed shared image functionality on Data Lab UI > -- > > Key: DLAB-1110 > URL: https://issues.apache.org/jira/browse/DLAB-1110 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Time Spent: 20m > Remaining Estimate: 0h > > As an admin I want to turn on/off of using shared image in project setting so > that I can easily switch without changing configuration files via SSH. -- 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
[jira] [Updated] (DLAB-1154) [Data Lab-terraform][KeyCloak]: Convey SBN value during deploy SSN
[ https://issues.apache.org/jira/browse/DLAB-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1154: Summary: [Data Lab-terraform][KeyCloak]: Convey SBN value during deploy SSN (was: [DLAB-terraform][KeyCloak]: Convey SBN value during deploy SSN) > [Data Lab-terraform][KeyCloak]: Convey SBN value during deploy SSN > -- > > Key: DLAB-1154 > URL: https://issues.apache.org/jira/browse/DLAB-1154 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: 2.3_old, AWS, AZURE, Debian, DevOps, GCP, RedHat > Attachments: SBN.png > > > DLAB-terraform branch. -- 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
[jira] [Updated] (DLAB-1283) User1 is auto logged out DLab on cloud1 after manually logout Data Lab on cloud2 only in the same browser
[ https://issues.apache.org/jira/browse/DLAB-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1283: Description: *Preconditions:* # User1 is logged in Data Lab1 on cloud1 on Chrome browser # User1 is logged in Data Lab2 on cloud2 on Chrome browser *Steps to reproduce:* 1. User1 logs out Data Lab1 on cloud1 on Chrome browser *Actual result:* # User1 is auto logged out Data Lab2 on cloud2 on Chrome browser *Expected result:* # User1 is still logged in Data Lab2 on cloud2 on Chrome browser was: *Preconditions:* # User1 is logged in DLab1 on cloud1 on Chrome browser # User1 is logged in DLab2 on cloud2 on Chrome browser *Steps to reproduce:* 1. User1 logs out DLab1 on cloud1 on Chrome browser *Actual result:* # User1 is auto logged out DLab2 on cloud2 on Chrome browser *Expected result:* # User1 is still logged in DLab2 on cloud2 on Chrome browser > User1 is auto logged out DLab on cloud1 after manually logout Data Lab on > cloud2 only in the same browser > - > > Key: DLAB-1283 > URL: https://issues.apache.org/jira/browse/DLAB-1283 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: 2.3_old, AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: AWS log out.png, Azure log out.png, Error 400.png > > > *Preconditions:* > # User1 is logged in Data Lab1 on cloud1 on Chrome browser > # User1 is logged in Data Lab2 on cloud2 on Chrome browser > *Steps to reproduce:* > 1. User1 logs out Data Lab1 on cloud1 on Chrome browser > *Actual result:* > # User1 is auto logged out Data Lab2 on cloud2 on Chrome browser > *Expected result:* > # User1 is still logged in Data Lab2 on cloud2 on Chrome browser -- 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
[jira] [Updated] (DLAB-1355) Investigate possibility of using SageMaker in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1355: Summary: Investigate possibility of using SageMaker in Data Lab (was: Investigate possibility of using SageMaker in DLab) > Investigate possibility of using SageMaker in Data Lab > -- > > Key: DLAB-1355 > URL: https://issues.apache.org/jira/browse/DLAB-1355 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Volodymyr Veres >Priority: Major > Labels: AWS > -- 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
[jira] [Updated] (DLAB-1283) User1 is auto logged out DLab on cloud1 after manually logout Data Lab on cloud2 only in the same browser
[ https://issues.apache.org/jira/browse/DLAB-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1283: Summary: User1 is auto logged out DLab on cloud1 after manually logout Data Lab on cloud2 only in the same browser (was: User1 is auto logged out DLab on cloud1 after manually logout Dlab on cloud2 only in the same browser) > User1 is auto logged out DLab on cloud1 after manually logout Data Lab on > cloud2 only in the same browser > - > > Key: DLAB-1283 > URL: https://issues.apache.org/jira/browse/DLAB-1283 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: 2.3_old, AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: AWS log out.png, Azure log out.png, Error 400.png > > > *Preconditions:* > # User1 is logged in DLab1 on cloud1 on Chrome browser > # User1 is logged in DLab2 on cloud2 on Chrome browser > *Steps to reproduce:* > 1. User1 logs out DLab1 on cloud1 on Chrome browser > *Actual result:* > # User1 is auto logged out DLab2 on cloud2 on Chrome browser > *Expected result:* > # User1 is still logged in DLab2 on cloud2 on Chrome browser -- 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
[jira] [Updated] (DLAB-1342) [KeyCloak] :Create script for client termination which are deployed by Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1342: Summary: [KeyCloak] :Create script for client termination which are deployed by Data Lab (was: [KeyCloak] :Create script for client termination which are deployed by DLab) > [KeyCloak] :Create script for client termination which are deployed by Data > Lab > --- > > Key: DLAB-1342 > URL: https://issues.apache.org/jira/browse/DLAB-1342 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: 2.3_old, AWS, AZURE, Debian, DevOps, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-1354) Investigate possibility of using databricks in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1354: Summary: Investigate possibility of using databricks in Data Lab (was: Investigate possibility of using databricks in DLab) > Investigate possibility of using databricks in Data Lab > --- > > Key: DLAB-1354 > URL: https://issues.apache.org/jira/browse/DLAB-1354 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Volodymyr Veres >Priority: Major > Labels: AWS, AZURE, GCP > -- 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
[jira] [Updated] (DLAB-1525) Display instance price for shape per hour on Data Lab Web UI
[ https://issues.apache.org/jira/browse/DLAB-1525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1525: Summary: Display instance price for shape per hour on Data Lab Web UI (was: Display instance price for shape per hour on DLab Web UI) > Display instance price for shape per hour on Data Lab Web UI > > > Key: DLAB-1525 > URL: https://issues.apache.org/jira/browse/DLAB-1525 > Project: Apache DLab > Issue Type: Improvement > Components: Data Lab Main >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, Github_issue, RedHat > > As a user I want to know price for shape per hour, so that I will be > confident in my shape choice. > > *Acceptance criteria:* > # The price is in drop down list, where are shapes > # The currency is USD > [https://github.com/apache/incubator-dlab/issues/751] -- 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
[jira] [Updated] (DLAB-1723) [Branch-1571]: Image is present neither in Data Lab report nor in S3 (file.csv)
[ https://issues.apache.org/jira/browse/DLAB-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1723: Description: *Preconditions:* 1. Environment is created on AWS 2. Shared image per all cloud/shared image per project/custom image are created 3. Billing is available *Steps to reproduce:* 1. Go to "Billing report" page 2. Go to S3 bucket *Actual result:* 1. Images are absent in billing report 2. Images are absent in S3 bucket *Expected result:* 1. Images are present in billing report 2. Images are present in S3 bucket was: *Preconditions:* 1. Environment is created on AWS 2. Shared image per all cloud/shared image per project/custom image are created 3. Billing is available *Steps to reproduce:* 1. Go to "Billing report" page 2. Go to S3 bucket *Actual result:* 1. Images are absent in billing report 2. Images are absent in S3 bucket Expected result: 1. Images are present in billing report 2. Images are present in S3 bucket > [Branch-1571]: Image is present neither in Data Lab report nor in S3 > (file.csv) > --- > > Key: DLAB-1723 > URL: https://issues.apache.org/jira/browse/DLAB-1723 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main >Affects Versions: v.2.4 >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AWS, Debian, DevOps, Known_issues(release2.3), > Known_issues(release2.4), RedHat > > *Preconditions:* > 1. Environment is created on AWS > 2. Shared image per all cloud/shared image per project/custom image are > created > 3. Billing is available > *Steps to reproduce:* > 1. Go to "Billing report" page > 2. Go to S3 bucket > *Actual result:* > 1. Images are absent in billing report > 2. Images are absent in S3 bucket > *Expected result:* > 1. Images are present in billing report > 2. Images are present in S3 bucket -- 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
[jira] [Updated] (DLAB-1895) Data Lab instance status should be synced up with cloud status
[ https://issues.apache.org/jira/browse/DLAB-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1895: Summary: Data Lab instance status should be synced up with cloud status (was: DLab instance status should be synced up with cloud status) > Data Lab instance status should be synced up with cloud status > -- > > Key: DLAB-1895 > URL: https://issues.apache.org/jira/browse/DLAB-1895 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Critical > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > > If change instance status from cloud console the Dlab instance status is not > updated: > # Edge node > # Notebook > # Cluster (master) > Please investigate the reaso -- 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
[jira] [Updated] (DLAB-1895) Data Lab instance status should be synced up with cloud status
[ https://issues.apache.org/jira/browse/DLAB-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1895: Description: If change instance status from cloud console the Data Lab instance status is not updated: # Edge node # Notebook # Cluster (master) Please investigate the reason was: If change instance status from cloud console the Data Lab instance status is not updated: # Edge node # Notebook # Cluster (master) Please investigate the reaso > Data Lab instance status should be synced up with cloud status > -- > > Key: DLAB-1895 > URL: https://issues.apache.org/jira/browse/DLAB-1895 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Critical > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > > If change instance status from cloud console the Data Lab instance status is > not updated: > # Edge node > # Notebook > # Cluster (master) > Please investigate the reason -- 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
[jira] [Updated] (DLAB-1723) [Branch-1571]: Image is present neither in Data Lab report nor in S3 (file.csv)
[ https://issues.apache.org/jira/browse/DLAB-1723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1723: Summary: [Branch-1571]: Image is present neither in Data Lab report nor in S3 (file.csv) (was: [Branch-1571]: Image is present neither in DLab report nor in S3 (file.csv)) > [Branch-1571]: Image is present neither in Data Lab report nor in S3 > (file.csv) > --- > > Key: DLAB-1723 > URL: https://issues.apache.org/jira/browse/DLAB-1723 > Project: Apache DLab > Issue Type: Bug > Components: Data Lab Main >Affects Versions: v.2.4 >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AWS, Debian, DevOps, Known_issues(release2.3), > Known_issues(release2.4), RedHat > > *Preconditions:* > 1. Environment is created on AWS > 2. Shared image per all cloud/shared image per project/custom image are > created > 3. Billing is available > *Steps to reproduce:* > 1. Go to "Billing report" page > 2. Go to S3 bucket > *Actual result:* > 1. Images are absent in billing report > 2. Images are absent in S3 bucket > Expected result: > 1. Images are present in billing report > 2. Images are present in S3 bucket -- 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
[jira] [Updated] (DLAB-1895) Data Lab instance status should be synced up with cloud status
[ https://issues.apache.org/jira/browse/DLAB-1895?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1895: Description: If change instance status from cloud console the Data Lab instance status is not updated: # Edge node # Notebook # Cluster (master) Please investigate the reaso was: If change instance status from cloud console the Dlab instance status is not updated: # Edge node # Notebook # Cluster (master) Please investigate the reaso > Data Lab instance status should be synced up with cloud status > -- > > Key: DLAB-1895 > URL: https://issues.apache.org/jira/browse/DLAB-1895 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Critical > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > > If change instance status from cloud console the Data Lab instance status is > not updated: > # Edge node > # Notebook > # Cluster (master) > Please investigate the reaso -- 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
[jira] [Updated] (DLAB-1880) Investigate ABAC in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1880: Summary: Investigate ABAC in Data Lab (was: Investigate ABAC in DLab) > Investigate ABAC in Data Lab > > > Key: DLAB-1880 > URL: https://issues.apache.org/jira/browse/DLAB-1880 > Project: Apache DLab > Issue Type: Task > Components: Data Lab Main >Reporter: Vira Vitanska >Assignee: Volodymyr Veres >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-500) [Azure]: Add support of installing Data Lab into two VPCs
[ https://issues.apache.org/jira/browse/DLAB-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-500: --- Summary: [Azure]: Add support of installing Data Lab into two VPCs (was: [Azure]: Add support of installing DLab into two VPCs) > [Azure]: Add support of installing Data Lab into two VPCs > - > > Key: DLAB-500 > URL: https://issues.apache.org/jira/browse/DLAB-500 > Project: Apache DLab > Issue Type: Improvement > Components: Data Lab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AZURE, Debian, RedHat > -- 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
[jira] [Updated] (DLAB-502) [GCP]: Implement Data Lab installation via private IP
[ https://issues.apache.org/jira/browse/DLAB-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-502: --- Description: As a user I want to install Data Lab via private IP *Acceptance criteria:* 1. All instances should have only private IP was: As a user I want to install DLab via private IP *Acceptance criteria:* 1. All instances should have only private IP > [GCP]: Implement Data Lab installation via private IP > - > > Key: DLAB-502 > URL: https://issues.apache.org/jira/browse/DLAB-502 > Project: Apache DLab > Issue Type: Improvement > Components: Data Lab Old >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, GCP > > As a user I want to install Data Lab via private IP > > *Acceptance criteria:* > 1. All instances should have only private IP -- 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
[jira] [Updated] (DLAB-502) [GCP]: Implement Data Lab installation via private IP
[ https://issues.apache.org/jira/browse/DLAB-502?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-502: --- Summary: [GCP]: Implement Data Lab installation via private IP (was: [GCP]: Implement DLab instalation via private IP) > [GCP]: Implement Data Lab installation via private IP > - > > Key: DLAB-502 > URL: https://issues.apache.org/jira/browse/DLAB-502 > Project: Apache DLab > Issue Type: Improvement > Components: Data Lab Old >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, GCP > > As a user I want to install DLab via private IP > > *Acceptance criteria:* > 1. All instances should have only private IP -- 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
[jira] [Updated] (DLAB-499) [GCP]: Add support of installing Data Lab into two VPCs
[ https://issues.apache.org/jira/browse/DLAB-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-499: --- Summary: [GCP]: Add support of installing Data Lab into two VPCs (was: [GCP]: Add support of installing DLab into two VPCs) > [GCP]: Add support of installing Data Lab into two VPCs > --- > > Key: DLAB-499 > URL: https://issues.apache.org/jira/browse/DLAB-499 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, GCP > -- 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
[jira] [Updated] (DLAB-296) DLab REST API to manage Data Lab without UI
[ https://issues.apache.org/jira/browse/DLAB-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-296: --- Summary: DLab REST API to manage Data Lab without UI (was: DLab REST API to manage DLab without UI) > DLab REST API to manage Data Lab without UI > --- > > Key: DLAB-296 > URL: https://issues.apache.org/jira/browse/DLAB-296 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > As a user I want to manage DLab without UI so that I can reduce time for some > operations -- 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
[jira] [Updated] (DLAB-396) Refactor Data Lab deploying with 2 VPCs
[ https://issues.apache.org/jira/browse/DLAB-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-396: --- Summary: Refactor Data Lab deploying with 2 VPCs (was: Refactor Dlab deploying with 2 VPCs) > Refactor Data Lab deploying with 2 VPCs > --- > > Key: DLAB-396 > URL: https://issues.apache.org/jira/browse/DLAB-396 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > > Add to .ini some argument to define that vpc connection already created(not > just peering) > Check route tables and ability to use own route table > Refactor logic of ssn_prepare.py > Remove aws_notebook_subnet_id mock (co-work with java) > Ability to add names to peering connection and second VPC > Problems with terminating of secondary VPC if EMR was provisioned > Take a look on case with predefined 1st VPC and wrong VPC CIDR -- 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
[jira] [Updated] (DLAB-296) DLab REST API to manage Data Lab without UI
[ https://issues.apache.org/jira/browse/DLAB-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-296: --- Description: As a user I want to manage Data Lab without UI so that I can reduce time for some operations (was: As a user I want to manage DLab without UI so that I can reduce time for some operations) > DLab REST API to manage Data Lab without UI > --- > > Key: DLAB-296 > URL: https://issues.apache.org/jira/browse/DLAB-296 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > As a user I want to manage Data Lab without UI so that I can reduce time for > some operations -- 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
[jira] [Updated] (DLAB-296) Data Lab REST API to manage Data Lab without UI
[ https://issues.apache.org/jira/browse/DLAB-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-296: --- Summary: Data Lab REST API to manage Data Lab without UI (was: DLab REST API to manage Data Lab without UI) > Data Lab REST API to manage Data Lab without UI > --- > > Key: DLAB-296 > URL: https://issues.apache.org/jira/browse/DLAB-296 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > As a user I want to manage Data Lab without UI so that I can reduce time for > some operations -- 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
[jira] [Updated] (DLAB-292) Have a default limit on how many environments can be created by the user. Data Lab admins can allow for a larger number upon proper justification
[ https://issues.apache.org/jira/browse/DLAB-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-292: --- Summary: Have a default limit on how many environments can be created by the user. Data Lab admins can allow for a larger number upon proper justification (was: Have a default limit on how many environments can be created by the user. Dlab admins can allow for a larger number upon proper justification) > Have a default limit on how many environments can be created by the user. > Data Lab admins can allow for a larger number upon proper justification > - > > Key: DLAB-292 > URL: https://issues.apache.org/jira/browse/DLAB-292 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AZURE, Debian, RedHat > > Currently admin can configure what instance shape can be allowed to create > for particular user or group, but it does not limit by quontity (only by > money) > > As an admin I want to manage how many quantities of instances can be allowed > to create per user/group > > *Acceptance criteria:* > # admin can set/alter sum of instances quantities which are allowed for > creating for user/group > # user is supposed to create only the sum of instances quantities (less or > equal the sum) which are allowed for creating for user/group > # user is not allowed to create more instances than it is permitted for him -- 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
[jira] [Updated] (DLAB-293) Implement job status tracker on Data Lab Web UI
[ https://issues.apache.org/jira/browse/DLAB-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-293: --- Description: As a user I want to know job status (completed/failed) in case of instance stops/terminates by scheduler. *Acceptance criteria:* # Failed status is conveyed on Data Lab ui if job status is failed # Completed status is conveyed on Data Lab ui if job status is successful Github issue: [https://github.com/apache/incubator-dlab/issues/749] was: As a user I want to know job status (completed/failed) in case of instance stops/terminates by scheduler. *Acceptance criteria:* # Failed status is conveyed on DLab ui if job status is failed # Completed status is conveyed on DLab ui if ijob status is successful Github issue: [https://github.com/apache/incubator-dlab/issues/749] > Implement job status tracker on Data Lab Web UI > --- > > Key: DLAB-293 > URL: https://issues.apache.org/jira/browse/DLAB-293 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, Github_issue, RedHat > > As a user I want to know job status (completed/failed) in case of instance > stops/terminates by scheduler. > > *Acceptance criteria:* > # Failed status is conveyed on Data Lab ui if job status is failed > # Completed status is conveyed on Data Lab ui if job status is successful > Github issue: [https://github.com/apache/incubator-dlab/issues/749] -- 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
[jira] [Updated] (DLAB-293) Implement job status tracker on Data Lab Web UI
[ https://issues.apache.org/jira/browse/DLAB-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-293: --- Summary: Implement job status tracker on Data Lab Web UI (was: Implement job status tracker on DLab Web UI) > Implement job status tracker on Data Lab Web UI > --- > > Key: DLAB-293 > URL: https://issues.apache.org/jira/browse/DLAB-293 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, Github_issue, RedHat > > As a user I want to know job status (completed/failed) in case of instance > stops/terminates by scheduler. > > *Acceptance criteria:* > # Failed status is conveyed on DLab ui if job status is failed > # Completed status is conveyed on DLab ui if ijob status is successful > Github issue: [https://github.com/apache/incubator-dlab/issues/749] -- 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
[jira] [Updated] (DLAB-65) Upgrade Data Lab
[ https://issues.apache.org/jira/browse/DLAB-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-65: -- Description: As a user I want to have possibility to upgrade current Data Lab version, so that I do not need fully redeploy. *Acceptance criteria:* 1. user can upgrade Data Lab 2. all previously data (billing/instances) do not removed/changed after upgrading Github issue: [https://github.com/apache/incubator-dlab/issues/746] was: As a user I want to have possibility to upgrade current DLab version, so that I do not need fully redeploy. *Acceptance criteria:* 1. user can upgrade DLab 2. all previously data (billing/instances) do not removed/changed after upgrading Github issue: [https://github.com/apache/incubator-dlab/issues/746] > Upgrade Data Lab > > > Key: DLAB-65 > URL: https://issues.apache.org/jira/browse/DLAB-65 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, Github_issue, RedHat > > As a user I want to have possibility to upgrade current Data Lab version, so > that I do not need fully redeploy. > > *Acceptance criteria:* > 1. user can upgrade Data Lab > 2. all previously data (billing/instances) do not removed/changed after > upgrading > Github issue: [https://github.com/apache/incubator-dlab/issues/746] -- 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
[jira] [Updated] (DLAB-50) Register all AMIs on AWS's Marketplace and use it for further Data Lab SSN instances
[ https://issues.apache.org/jira/browse/DLAB-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-50: -- Description: As a user I want to storage all AMIs on Marketplace of AWS, so that I can use it for further creation of Data Lab SSN instances. (was: As a user I want to storage all AMIs on Marketplace of AWS, so that I can use it for further creation of DLab SSN instances.) > Register all AMIs on AWS's Marketplace and use it for further Data Lab SSN > instances > > > Key: DLAB-50 > URL: https://issues.apache.org/jira/browse/DLAB-50 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > > As a user I want to storage all AMIs on Marketplace of AWS, so that I can use > it for further creation of Data Lab SSN instances. -- 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
[jira] [Updated] (DLAB-65) Upgrade Data Lab
[ https://issues.apache.org/jira/browse/DLAB-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-65: -- Summary: Upgrade Data Lab (was: Upgrade DLab) > Upgrade Data Lab > > > Key: DLAB-65 > URL: https://issues.apache.org/jira/browse/DLAB-65 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, Github_issue, RedHat > > As a user I want to have possibility to upgrade current DLab version, so that > I do not need fully redeploy. > > *Acceptance criteria:* > 1. user can upgrade DLab > 2. all previously data (billing/instances) do not removed/changed after > upgrading > Github issue: [https://github.com/apache/incubator-dlab/issues/746] -- 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
[jira] [Updated] (DLAB-50) Register all AMIs on AWS's Marketplace and use it for further Data Lab SSN instances
[ https://issues.apache.org/jira/browse/DLAB-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-50: -- Summary: Register all AMIs on AWS's Marketplace and use it for further Data Lab SSN instances (was: Register all AMIs on AWS's Marketplace and use it for further DLAB SSN instances) > Register all AMIs on AWS's Marketplace and use it for further Data Lab SSN > instances > > > Key: DLAB-50 > URL: https://issues.apache.org/jira/browse/DLAB-50 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > > As a user I want to storage all AMIs on Marketplace of AWS, so that I can use > it for further creation of DLab SSN instances. -- 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
[jira] [Updated] (DLAB-1239) Swagger UI integration in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1239: Summary: Swagger UI integration in Data Lab (was: Swagger UI integration in DLab) > Swagger UI integration in Data Lab > -- > > Key: DLAB-1239 > URL: https://issues.apache.org/jira/browse/DLAB-1239 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Bohdan Hliva >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Currently DLab has endpoints that return API description for 2 kind of APIs: > - DLab api (for third party integrations: ui, mobile devices etc) > - Endpoint API (api for environment provisioning that is used by DLab itself) > > There are 2 endpoint that expose configurations for swagger ui in openapi > format: > * /assets/endpoint-api.json > * /assets/dlab-api.json > On DLab UI it should be a btn that will open API description inside swagger > UI. > > Links: > [https://github.com/swagger-api/swagger-ui] > -- 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
[jira] [Updated] (DLAB-1239) Swagger UI integration in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1239: Description: Currently Data Lab has endpoints that return API description for 2 kind of APIs: - Data Lab api (for third party integrations: ui, mobile devices etc) - Endpoint API (api for environment provisioning that is used by Data Lab itself) There are 2 endpoint that expose configurations for swagger ui in open api format: * /assets/endpoint-api.json * /assets/dlab-api.json On Data Lab UI it should be a btn that will open API description inside swagger UI. Links: [https://github.com/swagger-api/swagger-ui] was: Currently DLab has endpoints that return API description for 2 kind of APIs: - DLab api (for third party integrations: ui, mobile devices etc) - Endpoint API (api for environment provisioning that is used by DLab itself) There are 2 endpoint that expose configurations for swagger ui in openapi format: * /assets/endpoint-api.json * /assets/dlab-api.json On DLab UI it should be a btn that will open API description inside swagger UI. Links: [https://github.com/swagger-api/swagger-ui] > Swagger UI integration in Data Lab > -- > > Key: DLAB-1239 > URL: https://issues.apache.org/jira/browse/DLAB-1239 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Bohdan Hliva >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: pull-request-available > Time Spent: 10m > Remaining Estimate: 0h > > Currently Data Lab has endpoints that return API description for 2 kind of > APIs: > - Data Lab api (for third party integrations: ui, mobile devices etc) > - Endpoint API (api for environment provisioning that is used by Data Lab > itself) > > There are 2 endpoint that expose configurations for swagger ui in open api > format: > * /assets/endpoint-api.json > * /assets/dlab-api.json > On Data Lab UI it should be a btn that will open API description inside > swagger UI. > > Links: > [https://github.com/swagger-api/swagger-ui] > -- 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
[jira] [Updated] (DLAB-1187) Сreate instruction how to add new template to Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1187: Summary: Сreate instruction how to add new template to Data Lab (was: Сreate instruction how to add new template to DLab) > Сreate instruction how to add new template to Data Lab > -- > > Key: DLAB-1187 > URL: https://issues.apache.org/jira/browse/DLAB-1187 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > -- 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
[jira] [Updated] (DLAB-446) Add parameter SSN size in Data Lab deploy script
[ https://issues.apache.org/jira/browse/DLAB-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-446: --- Description: As a user I want to choose the size of SSN during Data Lab deploying. Add parameter which responses for size of SSN during Data Lab deploying. *Acceptance criteria:* 1. There is parameter [key: value] for SSN size in deploy script was: As a user I want to choose the size of SSN during DLab deploying. Add parameter which responses for size of SSN during DLab deploying. *Acceptance criteria:* 1. There is parameter [key: value] for SSN size in deploy script > Add parameter SSN size in Data Lab deploy script > > > Key: DLAB-446 > URL: https://issues.apache.org/jira/browse/DLAB-446 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > > As a user I want to choose the size of SSN during Data Lab deploying. > Add parameter which responses for size of SSN during Data Lab deploying. > *Acceptance criteria:* > 1. There is parameter [key: value] for SSN size in deploy script -- 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
[jira] [Updated] (DLAB-588) Daily scheduler for Data Lab instance stopping
[ https://issues.apache.org/jira/browse/DLAB-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-588: --- Description: As a user I want to have possibility automatically stopping Data Lab environment at particulat time. *Acceptance criteria:* # Particular time is configurable # If one of nodes is in running status a scheduler trigger at particular time and environment will be stopped # If one of nodes is in creating status a scheduler does not trigger and will check the status of instance creation in some time. If a status of creating instance changes for a running one the environment will be stopped was: As a user I want to have possibility automatically stopping DLab environment at particulat time. *Acceptance criteria:* # Particular time is configurable # If one of nodes is in running status a scheduler trigger at particular time and environment will be stopped # If one of nodes is in creating status a sscheduler does not trigger and will check the status of instance creation in some time. If a status of creating instance changes for a running one the environment will be stopped > Daily scheduler for Data Lab instance stopping > -- > > Key: DLAB-588 > URL: https://issues.apache.org/jira/browse/DLAB-588 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > > As a user I want to have possibility automatically stopping Data Lab > environment at particulat time. > > *Acceptance criteria:* > # Particular time is configurable > # If one of nodes is in running status a scheduler trigger at particular > time and environment will be stopped > # If one of nodes is in creating status a scheduler does not trigger and > will check the status of instance creation in some time. If a status of > creating instance changes for a running one the environment will be stopped -- 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
[jira] [Updated] (DLAB-446) Add parameter SSN size in Data Lab deploy script
[ https://issues.apache.org/jira/browse/DLAB-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-446: --- Summary: Add parameter SSN size in Data Lab deploy script (was: Add parameter SSN size in DLab deploy script) > Add parameter SSN size in Data Lab deploy script > > > Key: DLAB-446 > URL: https://issues.apache.org/jira/browse/DLAB-446 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > > As a user I want to choose the size of SSN during DLab deploying. > Add parameter which responses for size of SSN during DLab deploying. > *Acceptance criteria:* > 1. There is parameter [key: value] for SSN size in deploy script -- 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
[jira] [Updated] (DLAB-588) Daily scheduler for Data Lab instance stopping
[ https://issues.apache.org/jira/browse/DLAB-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-588: --- Summary: Daily scheduler for Data Lab instance stopping (was: Daily scheduler for DLab instance stopping) > Daily scheduler for Data Lab instance stopping > -- > > Key: DLAB-588 > URL: https://issues.apache.org/jira/browse/DLAB-588 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > > As a user I want to have possibility automatically stopping DLab environment > at particulat time. > > *Acceptance criteria:* > # Particular time is configurable > # If one of nodes is in running status a scheduler trigger at particular > time and environment will be stopped > # If one of nodes is in creating status a sscheduler does not trigger and > will check the status of instance creation in some time. If a status of > creating instance changes for a running one the environment will be stopped -- 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
[jira] [Updated] (DLAB-1752) Distinguish Data Lab and project shared image
[ https://issues.apache.org/jira/browse/DLAB-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1752: Summary: Distinguish Data Lab and project shared image (was: Distinguish DLab and project shared image) > Distinguish Data Lab and project shared image > - > > Key: DLAB-1752 > URL: https://issues.apache.org/jira/browse/DLAB-1752 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > > If admin creates or edits a project he can choose: > * to use DLab shared image > * to use project shared image. > Now we have only one 'use shared image', that means to use DLab shared image. > Two radio buttons should be on DLab UI: > * use DLab shared image > * use project shared image -- 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
[jira] [Updated] (DLAB-1752) Distinguish Data Lab and project shared image
[ https://issues.apache.org/jira/browse/DLAB-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1752: Description: If admin creates or edits a project he can choose: * to use Data Lab shared image * to use project shared image. Now we have only one 'use shared image', that means to use Data Lab shared image. Two radio buttons should be on Data Lab UI: * use Data Lab shared image * use project shared image was: If admin creates or edits a project he can choose: * to use DLab shared image * to use project shared image. Now we have only one 'use shared image', that means to use DLab shared image. Two radio buttons should be on DLab UI: * use DLab shared image * use project shared image > Distinguish Data Lab and project shared image > - > > Key: DLAB-1752 > URL: https://issues.apache.org/jira/browse/DLAB-1752 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > > If admin creates or edits a project he can choose: > * to use Data Lab shared image > * to use project shared image. > Now we have only one 'use shared image', that means to use Data Lab shared > image. > Two radio buttons should be on Data Lab UI: > * use Data Lab shared image > * use project shared image -- 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
[jira] [Updated] (DLAB-57) Add ability to share AMI(s) created by user across Data Lab project
[ https://issues.apache.org/jira/browse/DLAB-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-57: -- Summary: Add ability to share AMI(s) created by user across Data Lab project (was: Add ability to share AMI(s) created by user across DLab project ) > Add ability to share AMI(s) created by user across Data Lab project > > > Key: DLAB-57 > URL: https://issues.apache.org/jira/browse/DLAB-57 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, Github_issue, RedHat > Fix For: v.2.5 > > > As a user I want to choose to make custom AMi of notebook public or not > public, so that I can shared my own custom AMI with other users by my desire. > > *Acceptance criteria:* > 1. to add possibility for choosing during creation AMI: > - available for all users/make shared > 2. my personal data on notebook should not to be shared > Github issue: [https://github.com/apache/incubator-dlab/issues/745] -- 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
[jira] [Updated] (DLAB-249) [DevOps]: Add support of local repository for Data Lab
[ https://issues.apache.org/jira/browse/DLAB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-249: --- Summary: [DevOps]: Add support of local repository for Data Lab (was: [DevOps]: Add support of local repository for DLab) > [DevOps]: Add support of local repository for Data Lab > -- > > Key: DLAB-249 > URL: https://issues.apache.org/jira/browse/DLAB-249 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, Github_issue, RedHat > Attachments: local.png > > > As a user I want to create instance from local repository, so that I can > prevent some random issues during creation. > > 1. It should be the single source from which changes will be performed. > 2. Go and distribute all traffic through this sandbox > Github issue: [https://github.com/apache/incubator-dlab/issues/737] -- 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
[jira] [Updated] (DLAB-965) Fix issue with Java SSL certificate for Data Lab Java services
[ https://issues.apache.org/jira/browse/DLAB-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-965: --- Summary: Fix issue with Java SSL certificate for Data Lab Java services (was: Fix issue with Java SSL certificate for DLab Java services) > Fix issue with Java SSL certificate for Data Lab Java services > -- > > Key: DLAB-965 > URL: https://issues.apache.org/jira/browse/DLAB-965 > Project: Apache DLab > Issue Type: Task >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: DevOps > -- 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
[jira] [Updated] (DLAB-944) [K8S]: Change container OS of docker images for Data Lab Java services
[ https://issues.apache.org/jira/browse/DLAB-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-944: --- Summary: [K8S]: Change container OS of docker images for Data Lab Java services (was: [K8S]: Change container OS of docker images for DLab Java services) > [K8S]: Change container OS of docker images for Data Lab Java services > -- > > Key: DLAB-944 > URL: https://issues.apache.org/jira/browse/DLAB-944 > Project: Apache DLab > Issue Type: Task >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: DevOps > > Currently, we are using Ubuntu 16.04. Size of such image is very large. > We should change it to something like Alpine or CoreOS -- 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
[jira] [Updated] (DLAB-941) [K8S]: Investigate and implement ConfigMaps for Data Lab Java services
[ https://issues.apache.org/jira/browse/DLAB-941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-941: --- Summary: [K8S]: Investigate and implement ConfigMaps for Data Lab Java services (was: [K8S]: Investigate and implement ConfigMaps for DLab Java services) > [K8S]: Investigate and implement ConfigMaps for Data Lab Java services > -- > > Key: DLAB-941 > URL: https://issues.apache.org/jira/browse/DLAB-941 > Project: Apache DLab > Issue Type: Task >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: DevOps > -- 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
[jira] [Updated] (DLAB-942) [K8S]: Investigate and implement Kubernetes secrets for Data Lab services
[ https://issues.apache.org/jira/browse/DLAB-942?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-942: --- Summary: [K8S]: Investigate and implement Kubernetes secrets for Data Lab services (was: [K8S]: Investigate and implement Kubernetes secrets for DLab services) > [K8S]: Investigate and implement Kubernetes secrets for Data Lab services > - > > Key: DLAB-942 > URL: https://issues.apache.org/jira/browse/DLAB-942 > Project: Apache DLab > Issue Type: Task >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: DevOps > -- 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
[jira] [Updated] (DLAB-985) Fix issue with MongoDB Data Lab parameters
[ https://issues.apache.org/jira/browse/DLAB-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-985: --- Summary: Fix issue with MongoDB Data Lab parameters (was: Fix issue with MongoDB DLab parameters) > Fix issue with MongoDB Data Lab parameters > -- > > Key: DLAB-985 > URL: https://issues.apache.org/jira/browse/DLAB-985 > Project: Apache DLab > Issue Type: Task >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: DevOps > -- 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
[jira] [Updated] (DLAB-1497) Create CI solution for Data Lab docker images, jars
[ https://issues.apache.org/jira/browse/DLAB-1497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1497: Summary: Create CI solution for Data Lab docker images, jars (was: Create CI solution for DLab docker images, jars) > Create CI solution for Data Lab docker images, jars > --- > > Key: DLAB-1497 > URL: https://issues.apache.org/jira/browse/DLAB-1497 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.5 > > -- 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
[jira] [Updated] (DLAB-2029) [Plugin architecture][Front-end]: Implement possibility to turn on billing after Data Lab deployment
[ https://issues.apache.org/jira/browse/DLAB-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2029: Summary: [Plugin architecture][Front-end]: Implement possibility to turn on billing after Data Lab deployment (was: [Plugin architecture][Front-end]: Implement possibility to turn on billing after DLab deployment) > [Plugin architecture][Front-end]: Implement possibility to turn on billing > after Data Lab deployment > > > Key: DLAB-2029 > URL: https://issues.apache.org/jira/browse/DLAB-2029 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.5 > > > Embed and run billing as a service. -- 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
[jira] [Updated] (DLAB-1495) Prepare environment (VPC, Subnet, etc) for Data Lab production services (Keycloak, Nexus, Step-CA)
[ https://issues.apache.org/jira/browse/DLAB-1495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1495: Summary: Prepare environment (VPC, Subnet, etc) for Data Lab production services (Keycloak, Nexus, Step-CA) (was: Prepare environment (VPC, Subnet, etc) for DLab production services (Keycloak, Nexus, Step-CA)) > Prepare environment (VPC, Subnet, etc) for Data Lab production services > (Keycloak, Nexus, Step-CA) > -- > > Key: DLAB-1495 > URL: https://issues.apache.org/jira/browse/DLAB-1495 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, Azure, Debian, DevOps, GCP, RedHat > Fix For: v.2.5 > > -- 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
[jira] [Updated] (DLAB-2061) [Plugin architecture][DevOps]: Implement possibility to turn on billing after Data Lab deployment
[ https://issues.apache.org/jira/browse/DLAB-2061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2061: Summary: [Plugin architecture][DevOps]: Implement possibility to turn on billing after Data Lab deployment (was: [Plugin architecture][DevOps]: Implement possibility to turn on billing after DLab deployment) > [Plugin architecture][DevOps]: Implement possibility to turn on billing after > Data Lab deployment > - > > Key: DLAB-2061 > URL: https://issues.apache.org/jira/browse/DLAB-2061 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.5 > > > Embed and run billing as a service. -- 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
[jira] [Updated] (DLAB-1601) [Azure][DevOps]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1601: Summary: [Azure][DevOps]: Odahu (Legion) management in Data Lab (was: [Azure][DevOps]: Odahu (Legion) management in DLab) > [Azure][DevOps]: Odahu (Legion) management in Data Lab > -- > > Key: DLAB-1601 > URL: https://issues.apache.org/jira/browse/DLAB-1601 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Azure, Debian, DevOps, RedHat > Fix For: v.2.5 > > > 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
[jira] [Updated] (DLAB-2028) [Plugin architecture][Back-end]: Implement possibility to turn on billing after Data Lab deployment
[ https://issues.apache.org/jira/browse/DLAB-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2028: Summary: [Plugin architecture][Back-end]: Implement possibility to turn on billing after Data Lab deployment (was: [Plugin architecture][Back-end]: Implement possibility to turn on billing after DLab deployment) > [Plugin architecture][Back-end]: Implement possibility to turn on billing > after Data Lab deployment > --- > > Key: DLAB-2028 > URL: https://issues.apache.org/jira/browse/DLAB-2028 > 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.5 > > > Embed and run billing as a service. -- 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
[jira] [Updated] (DLAB-1601) [Azure][DevOps]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1601: Description: Who manages Legion provisioning: * Admin or Data Lab 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)+ ## Data Lab 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" > [Azure][DevOps]: Odahu (Legion) management in Data Lab > -- > > Key: DLAB-1601 > URL: https://issues.apache.org/jira/browse/DLAB-1601 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Azure, Debian, DevOps, RedHat > Fix For: v.2.5 > > > Who manages Legion provisioning: > * Admin or Data Lab 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)+ > ## Data Lab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible = false) > -
[jira] [Updated] (DLAB-1600) [AWS][DevOps]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1600: Summary: [AWS][DevOps]: Odahu (Legion) management in Data Lab (was: [AWS][DevOps]: Odahu (Legion) management in DLab) > [AWS][DevOps]: Odahu (Legion) management in Data Lab > > > Key: DLAB-1600 > URL: https://issues.apache.org/jira/browse/DLAB-1600 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.5 > > > 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
[jira] [Updated] (DLAB-1600) [AWS][DevOps]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1600: Description: Who manages Legion provisioning: * Admin or Data Lab 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)+ ## Data Lab 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" > [AWS][DevOps]: Odahu (Legion) management in Data Lab > > > Key: DLAB-1600 > URL: https://issues.apache.org/jira/browse/DLAB-1600 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.5 > > > Who manages Legion provisioning: > * Admin or Data Lab 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)+ > ## Data Lab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible = false) > - NAT
[jira] [Created] (DLAB-2070) Replace old name by new one in Jira
Vira Vitanska created DLAB-2070: --- Summary: Replace old name by new one in Jira Key: DLAB-2070 URL: https://issues.apache.org/jira/browse/DLAB-2070 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Vira Vitanska Fix For: v.2.5 -- 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
[jira] [Updated] (DLAB-2070) Replace old name by new one in Jira
[ https://issues.apache.org/jira/browse/DLAB-2070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2070: Story Points: 2 > Replace old name by new one in Jira > --- > > Key: DLAB-2070 > URL: https://issues.apache.org/jira/browse/DLAB-2070 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > Fix For: v.2.5 > > -- 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
[jira] [Updated] (DLAB-1345) [GCP][DevOps]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1345: Summary: [GCP][DevOps]: Odahu (Legion) management in Data Lab (was: [GCP][DevOps]: Odahu (Legion) management in DLab) > [GCP][DevOps]: Odahu (Legion) management in Data Lab > - > > Key: DLAB-1345 > URL: https://issues.apache.org/jira/browse/DLAB-1345 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Demian Mysakovets >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.5 > > > 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
[jira] [Updated] (DLAB-1345) [GCP][DevOps]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1345: Description: Who manages Legion provisioning: * Admin or Data Lab 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)+ ## Data Lab 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" > [GCP][DevOps]: Odahu (Legion) management in Data Lab > - > > Key: DLAB-1345 > URL: https://issues.apache.org/jira/browse/DLAB-1345 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Demian Mysakovets >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.5 > > > Who manages Legion provisioning: > * Admin or Data Lab 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)+ > ## Data Lab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible = false) > - NAT
[jira] [Updated] (DLAB-1357) [Front-end]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1357: Summary: [Front-end]: Odahu (Legion) management in Data Lab (was: [Front-end]: Odahu (Legion) management in DLab) > [Front-end]: Odahu (Legion) management in Data Lab > --- > > Key: DLAB-1357 > URL: https://issues.apache.org/jira/browse/DLAB-1357 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.5 > > > 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
[jira] [Updated] (DLAB-1357) [Front-end]: Odahu (Legion) management in Data Lab
[ https://issues.apache.org/jira/browse/DLAB-1357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1357: Description: Who manages Legion provisioning: * Admin or Data Lab 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)+ ## Data Lab 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" > [Front-end]: Odahu (Legion) management in Data Lab > --- > > Key: DLAB-1357 > URL: https://issues.apache.org/jira/browse/DLAB-1357 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.5 > > > Who manages Legion provisioning: > * Admin or Data Lab 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)+ > ## Data Lab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible =
[jira] [Updated] (DLAB-1338) Data Lab + Odahu
[ 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 Data Lab 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)+ ## Data Lab 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 Data Lab and Legion: # Use same realm for Data Lab and Legion ## I should be able to login to Data Lab 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? 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" *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? > Data Lab + Odahu > > > 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: >
[jira] [Updated] (DLAB-1338) Data Lab + Odahu
[ https://issues.apache.org/jira/browse/DLAB-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1338: Epic Name: Data Lab + Odahu (was: DLab + Odahu) Summary: Data Lab + Odahu (was: DLab + Odahu) > Data Lab + Odahu > > > 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-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-2069) Replace old name by new one for in confluence
Vira Vitanska created DLAB-2069: --- Summary: Replace old name by new one for in confluence Key: DLAB-2069 URL: https://issues.apache.org/jira/browse/DLAB-2069 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Vira Vitanska Fix For: v.2.5 A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. -- 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
[jira] [Updated] (DLAB-2064) Replace old name by new one in all documentations
[ https://issues.apache.org/jira/browse/DLAB-2064?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2064: Description: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. was: A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab' > Replace old name by new one in all documentations > - > > Key: DLAB-2064 > URL: https://issues.apache.org/jira/browse/DLAB-2064 > 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.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. -- 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
[jira] [Updated] (DLAB-2063) Investigate if it's possible to change repo name
[ https://issues.apache.org/jira/browse/DLAB-2063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2063: Description: A new name has been approved 'Apache Data Lab'. So we should change from 'incubator-dlab' to 'incubator-data-lab'. was: A new name has been approved 'Apache Data Lab'. So we should change from 'incubator-dlab' to 'incubator-data-lab ' > Investigate if it's possible to change repo name > - > > Key: DLAB-2063 > URL: https://issues.apache.org/jira/browse/DLAB-2063 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > A new name has been approved 'Apache Data Lab'. > So we should change from 'incubator-dlab' to 'incubator-data-lab'. -- 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
[jira] [Assigned] (DLAB-2068) [Front-end]: Replace old name by new one in all sources
[ https://issues.apache.org/jira/browse/DLAB-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-2068: --- Assignee: Dmytro Gnatyshyn (was: Oleg Fuks) > [Front-end]: Replace old name by new one in all sources > --- > > Key: DLAB-2068 > URL: https://issues.apache.org/jira/browse/DLAB-2068 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. -- 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
[jira] [Updated] (DLAB-2068) [Front-end]: Replace old name by new one in all sources
[ https://issues.apache.org/jira/browse/DLAB-2068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-2068: Labels: AWS AZURE Debian Front-end GCP RedHat (was: AWS AZURE Back-end Debian GCP RedHat) > [Front-end]: Replace old name by new one in all sources > --- > > Key: DLAB-2068 > URL: https://issues.apache.org/jira/browse/DLAB-2068 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. -- 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
[jira] [Created] (DLAB-2068) [Front-end]: Replace old name by new one in all sources
Vira Vitanska created DLAB-2068: --- Summary: [Front-end]: Replace old name by new one in all sources Key: DLAB-2068 URL: https://issues.apache.org/jira/browse/DLAB-2068 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.5 A new name has been approved 'Apache Data Lab'. So we should change from 'Apache DLab' to 'Apache Data Lab'. -- 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
[jira] [Assigned] (DLAB-2067) [DevOps]: Replace old name by new one in all sources
[ https://issues.apache.org/jira/browse/DLAB-2067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-2067: --- Assignee: Leonid Frolov (was: Oleg Fuks) > [DevOps]: Replace old name by new one in all sources > > > Key: DLAB-2067 > URL: https://issues.apache.org/jira/browse/DLAB-2067 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.5 > > > A new name has been approved 'Apache Data Lab'. > So we should change from 'Apache DLab' to 'Apache Data Lab'. -- 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
