[jira] [Created] (DLAB-665) Investigate Terraform compatibility with Dlab needs
Vira Vitanska created DLAB-665: -- Summary: Investigate Terraform compatibility with Dlab needs Key: DLAB-665 URL: https://issues.apache.org/jira/browse/DLAB-665 Project: Apache DLab Issue Type: Sub-task Components: AWS, Azure, GCP Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-682) Implement terraform execution job
Vira Vitanska created DLAB-682: -- Summary: Implement terraform execution job Key: DLAB-682 URL: https://issues.apache.org/jira/browse/DLAB-682 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-672) Create python terraform manager
Vira Vitanska created DLAB-672: -- Summary: Create python terraform manager Key: DLAB-672 URL: https://issues.apache.org/jira/browse/DLAB-672 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-671) Create terraform python template engine
Vira Vitanska created DLAB-671: -- Summary: Create terraform python template engine Key: DLAB-671 URL: https://issues.apache.org/jira/browse/DLAB-671 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-673) Create terraform manager unit tests
Vira Vitanska created DLAB-673: -- Summary: Create terraform manager unit tests Key: DLAB-673 URL: https://issues.apache.org/jira/browse/DLAB-673 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-670) Generation terraform automation
Vira Vitanska created DLAB-670: -- Summary: Generation terraform automation Key: DLAB-670 URL: https://issues.apache.org/jira/browse/DLAB-670 Project: Apache DLab Issue Type: Task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-674) Implement terraform validate automation
Vira Vitanska created DLAB-674: -- Summary: Implement terraform validate automation Key: DLAB-674 URL: https://issues.apache.org/jira/browse/DLAB-674 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-677) Implement terraform exception handling
Vira Vitanska created DLAB-677: -- Summary: Implement terraform exception handling Key: DLAB-677 URL: https://issues.apache.org/jira/browse/DLAB-677 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-676) Implement terraform parameters parser
Vira Vitanska created DLAB-676: -- Summary: Implement terraform parameters parser Key: DLAB-676 URL: https://issues.apache.org/jira/browse/DLAB-676 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-678) Implement terraform infrastructure
Vira Vitanska created DLAB-678: -- Summary: Implement terraform infrastructure Key: DLAB-678 URL: https://issues.apache.org/jira/browse/DLAB-678 Project: Apache DLab Issue Type: Task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-663) Terraform
Vira Vitanska created DLAB-663: -- Summary: Terraform Key: DLAB-663 URL: https://issues.apache.org/jira/browse/DLAB-663 Project: Apache DLab Issue Type: Epic Components: AWS, Azure, GCP Reporter: Vira Vitanska Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-675) Implement terraform run automation
Vira Vitanska created DLAB-675: -- Summary: Implement terraform run automation Key: DLAB-675 URL: https://issues.apache.org/jira/browse/DLAB-675 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-666) Terraform templates creation
Vira Vitanska created DLAB-666: -- Summary: Terraform templates creation Key: DLAB-666 URL: https://issues.apache.org/jira/browse/DLAB-666 Project: Apache DLab Issue Type: Task Components: AWS, Azure, GCP Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-680) Implement terraform state storage
Vira Vitanska created DLAB-680: -- Summary: Implement terraform state storage Key: DLAB-680 URL: https://issues.apache.org/jira/browse/DLAB-680 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-679) Create Dlab terraform architecture
Vira Vitanska created DLAB-679: -- Summary: Create Dlab terraform architecture Key: DLAB-679 URL: https://issues.apache.org/jira/browse/DLAB-679 Project: Apache DLab Issue Type: Sub-task Components: AWS Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-669) Implement terraform Azure templates for DLab components
Vira Vitanska created DLAB-669: -- Summary: Implement terraform Azure templates for DLab components Key: DLAB-669 URL: https://issues.apache.org/jira/browse/DLAB-669 Project: Apache DLab Issue Type: Sub-task Components: Azure Reporter: Vira Vitanska Assignee: Andrew Yatskovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-693) Implement Legion platform provisioning on GKE with Terraform
Vira Vitanska created DLAB-693: -- Summary: Implement Legion platform provisioning on GKE with Terraform Key: DLAB-693 URL: https://issues.apache.org/jira/browse/DLAB-693 Project: Apache DLab Issue Type: Bug Components: Legion Reporter: Vira Vitanska Assignee: Aliaksandr Semianets Fix For: v.2.2 As a DevOps engineer I would like to have terraform based solution for infrastructure management so I can deployes GKE cluster with Legion and all dependencies on top of that. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-694) Upgrade Airflow to latest version(1.10) compatible with k8s scheduler
Vira Vitanska created DLAB-694: -- Summary: Upgrade Airflow to latest version(1.10) compatible with k8s scheduler Key: DLAB-694 URL: https://issues.apache.org/jira/browse/DLAB-694 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Aliaksandr Semianets Fix For: v.2.2 Upgrade Airflow to latest version(1.10) compatible with k8s scheduler to : # get rid off Celery scheduler # package DAGs with dependencies into docker containers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-695) Create Legion plugin for JupyterLab
Vira Vitanska created DLAB-695: -- Summary: Create Legion plugin for JupyterLab Key: DLAB-695 URL: https://issues.apache.org/jira/browse/DLAB-695 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 As a User of local or cloud deployed JupyterLab I want to: For local mode: # Start local build # Get locally builded images # Deploy & undeploy locally builded images locally # Monitor state of local deployments For cloud mode: # Authorize / UnAuthorize on cloud # Get cluster trainings # Create cluster trainings # Create & remove cluster deployments # Monitor cluster deployments (name, model, scale) # Scale cluster deployments All mods (local & cloud) should be individually configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-692) Self-service
Vira Vitanska created DLAB-692: -- Summary: Self-service Key: DLAB-692 URL: https://issues.apache.org/jira/browse/DLAB-692 Project: Apache DLab Issue Type: Sub-task Components: DLab Old Reporter: Vira Vitanska Assignee: Demyan Mysakovets Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-693) Implement Legion platform provisioning on GKE with Terraform
[ https://issues.apache.org/jira/browse/DLAB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-693: --- Issue Type: Task (was: Bug) > Implement Legion platform provisioning on GKE with Terraform > > > Key: DLAB-693 > URL: https://issues.apache.org/jira/browse/DLAB-693 > Project: Apache DLab > Issue Type: Task > Components: Legion >Reporter: Vira Vitanska >Assignee: Aliaksandr Semianets >Priority: Major > Labels: K8S_to_PaaS > Fix For: v.2.2 > > > As a DevOps engineer I would like to have terraform based solution for > infrastructure management so I can deployes GKE cluster with Legion and all > dependencies on top of that. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-701) Legion pods authentication with IAM roles at GCP
Vira Vitanska created DLAB-701: -- Summary: Legion pods authentication with IAM roles at GCP Key: DLAB-701 URL: https://issues.apache.org/jira/browse/DLAB-701 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Dmitriy Karbyshev Fix For: v.2.2 As a Developer I would like to be able to authorize legion components such as fluentd with iam roles specific to the component so I don't have to setup predefined keys in configs. Details: We have kube2iam implementation at K8S cluster at AWS which provides AWS credentials to the PODs from EC2 Metadata. We need to implement the same feature at GKE cluster as well. As for now we grant access to fluentd, airflow and jenkins which store data at per cluster s3 bucket. The same approach should be transferred to GCP and automated with terraform. AC: * kube2iam analog for GCP is implemented with terraform * required IAM roles and policies are implemented with terraform * fluentd, legion models, jenkins, airflow can get access to GCS storage with IAM roles -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-656) [K8s]: Prepare docker images for every services of SSN
[ https://issues.apache.org/jira/browse/DLAB-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-656: --- Component/s: (was: DLab Old) DLab Main > [K8s]: Prepare docker images for every services of SSN > -- > > Key: DLAB-656 > URL: https://issues.apache.org/jira/browse/DLAB-656 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-658) Provision service
[ https://issues.apache.org/jira/browse/DLAB-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-658: --- Component/s: (was: DLab Old) DLab Main > Provision service > - > > Key: DLAB-658 > URL: https://issues.apache.org/jira/browse/DLAB-658 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-659) Billing service
[ https://issues.apache.org/jira/browse/DLAB-659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-659: --- Component/s: (was: DLab Old) DLab Main > Billing service > --- > > Key: DLAB-659 > URL: https://issues.apache.org/jira/browse/DLAB-659 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-661) Mongo service
[ https://issues.apache.org/jira/browse/DLAB-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-661: --- Component/s: (was: DLab Old) DLab Main > Mongo service > - > > Key: DLAB-661 > URL: https://issues.apache.org/jira/browse/DLAB-661 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-660) Security service
[ https://issues.apache.org/jira/browse/DLAB-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-660: --- Component/s: (was: DLab Old) DLab Main > Security service > > > Key: DLAB-660 > URL: https://issues.apache.org/jira/browse/DLAB-660 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-657) UI service
[ https://issues.apache.org/jira/browse/DLAB-657?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-657: --- Component/s: (was: DLab Old) DLab Main > UI service > -- > > Key: DLAB-657 > URL: https://issues.apache.org/jira/browse/DLAB-657 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-702) Manual setup and configure KeyCloack
Vira Vitanska created DLAB-702: -- Summary: Manual setup and configure KeyCloack Key: DLAB-702 URL: https://issues.apache.org/jira/browse/DLAB-702 Project: Apache DLab Issue Type: Task Components: Authentication and authorization Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-683) Implement infrastructure Component
[ https://issues.apache.org/jira/browse/DLAB-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-683: --- Epic Name: Implement infrastructure Component (was: Implement DLab Component) > Implement infrastructure Component > -- > > Key: DLAB-683 > URL: https://issues.apache.org/jira/browse/DLAB-683 > Project: Apache DLab > Issue Type: Epic > Components: DLab Main >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-703) Setup and configure AD with federation using AWS services
[ https://issues.apache.org/jira/browse/DLAB-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-703: --- Component/s: Infrastructure > Setup and configure AD with federation using AWS services > - > > Key: DLAB-703 > URL: https://issues.apache.org/jira/browse/DLAB-703 > Project: Apache DLab > Issue Type: Task > Components: Infrastructure >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-683) Implement DLab main Component
[ https://issues.apache.org/jira/browse/DLAB-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-683: --- Summary: Implement DLab main Component (was: Implement DLab infrastructure Component) > Implement DLab main Component > - > > Key: DLAB-683 > URL: https://issues.apache.org/jira/browse/DLAB-683 > Project: Apache DLab > Issue Type: Epic > Components: DLab Main >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-683) Implement infrastructure Component
[ https://issues.apache.org/jira/browse/DLAB-683?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-683: --- Summary: Implement infrastructure Component (was: Implement DLab main Component) > Implement infrastructure Component > -- > > Key: DLAB-683 > URL: https://issues.apache.org/jira/browse/DLAB-683 > Project: Apache DLab > Issue Type: Epic > Components: DLab Main >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-629) Implement DLab 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 DLab main Component (was: Implement project infrastructure Component) > Implement DLab main Component > - > > Key: DLAB-629 > URL: https://issues.apache.org/jira/browse/DLAB-629 > Project: Apache DLab > Issue Type: Epic > Components: Project >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-703) Setup and configure AD with federation using AWS services
Vira Vitanska created DLAB-703: -- Summary: Setup and configure AD with federation using AWS services Key: DLAB-703 URL: https://issues.apache.org/jira/browse/DLAB-703 Project: Apache DLab Issue Type: Task Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-687) Implement Kubernetes Component
[ https://issues.apache.org/jira/browse/DLAB-687?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-687: --- Summary: Implement Kubernetes Component (was: Implement Kubernetes infrastructure Component) > Implement Kubernetes Component > -- > > Key: DLAB-687 > URL: https://issues.apache.org/jira/browse/DLAB-687 > Project: Apache DLab > Issue Type: Epic > Components: Kubernetes >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-656) Prepare docker images for every services of SSN
[ https://issues.apache.org/jira/browse/DLAB-656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-656: --- Summary: Prepare docker images for every services of SSN (was: [K8s]: Prepare docker images for every services of SSN) > Prepare docker images for every services of SSN > --- > > Key: DLAB-656 > URL: https://issues.apache.org/jira/browse/DLAB-656 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-686) Implement cloud endpoint Component
[ https://issues.apache.org/jira/browse/DLAB-686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-686: --- Summary: Implement cloud endpoint Component (was: Implement cloud endpoint infrastructure Component) > Implement cloud endpoint Component > -- > > Key: DLAB-686 > URL: https://issues.apache.org/jira/browse/DLAB-686 > Project: Apache DLab > Issue Type: Epic > Components: Cloud endpoint >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-685) Implement proxy server Component
[ https://issues.apache.org/jira/browse/DLAB-685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-685: --- Summary: Implement proxy server Component (was: Implement proxy server infrastructure Component) > Implement proxy server Component > > > Key: DLAB-685 > URL: https://issues.apache.org/jira/browse/DLAB-685 > Project: Apache DLab > Issue Type: Epic > Components: Proxy server >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-629) Implement DLab main Component
[ https://issues.apache.org/jira/browse/DLAB-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-629: --- Summary: Implement DLab main Component (was: Implement project infrastructure Component) > Implement DLab main Component > - > > Key: DLAB-629 > URL: https://issues.apache.org/jira/browse/DLAB-629 > Project: Apache DLab > Issue Type: Epic > Components: Project >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-707) Add installation section to documentation
Vira Vitanska created DLAB-707: -- Summary: Add installation section to documentation Key: DLAB-707 URL: https://issues.apache.org/jira/browse/DLAB-707 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 We have to add next information into "installation" section: # Prerequirements 1.1. External Docker Registry - required for model storing 1.2. Monitoring (prometheus) chart - optional for components metrics 1.3. Performance metrics (statsd to prometheus) - optional for model metrics storing 1.4. Authorization - optional for WEB authorization # Step-by-step guide for available platforms # Detailed description of HELM charts (legion and legion infra), their values and examples of configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-709) Monitoring of core legion services
Vira Vitanska created DLAB-709: -- Summary: Monitoring of core legion services Key: DLAB-709 URL: https://issues.apache.org/jira/browse/DLAB-709 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 As a developer, I want that legion core services will be integrated with Prometheus. Core services: * edge * edi * airflow * operators? (use k8s resources for model training) * grafana * toolchains * jenkins -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-694) Upgrade Airflow to latest version(1.10) compatible with k8s scheduler
[ https://issues.apache.org/jira/browse/DLAB-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-694: --- Labels: 1.0.0 feature (was: Spike feature) > Upgrade Airflow to latest version(1.10) compatible with k8s scheduler > - > > Key: DLAB-694 > URL: https://issues.apache.org/jira/browse/DLAB-694 > Project: Apache DLab > Issue Type: New Feature > Components: Legion >Reporter: Vira Vitanska >Assignee: Aliaksandr Semianets >Priority: Major > Labels: 1.0.0, feature > Fix For: v.2.2 > > > Upgrade Airflow to latest version(1.10) compatible with k8s scheduler to : > # get rid off Celery scheduler > # package DAGs with dependencies into docker containers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-704) Update changelog file for 1.0.0 release
Vira Vitanska created DLAB-704: -- Summary: Update changelog file for 1.0.0 release Key: DLAB-704 URL: https://issues.apache.org/jira/browse/DLAB-704 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-706) Add network connectivity requirements for HELM chart
Vira Vitanska created DLAB-706: -- Summary: Add network connectivity requirements for HELM chart Key: DLAB-706 URL: https://issues.apache.org/jira/browse/DLAB-706 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 We have to describe what components have to have connection with which service (source namespaces, pods and target namespaces, pods and ports). First assumptions are: # Kubernetes Ingress pod to EDGE/EDI pods port 80 # Prometheus metrics collector to EDGE/EDI/Operator pods port XXX # EDGE pods to model pods -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-695) Create Legion plugin for JupyterLab
[ https://issues.apache.org/jira/browse/DLAB-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-695: --- Labels: 1.0.0 feature (was: feature) > Create Legion plugin for JupyterLab > --- > > Key: DLAB-695 > URL: https://issues.apache.org/jira/browse/DLAB-695 > Project: Apache DLab > Issue Type: New Feature > Components: Legion >Reporter: Vira Vitanska >Assignee: Kirill Makhonin >Priority: Major > Labels: 1.0.0, feature > Fix For: v.2.2 > > > As a User of local or cloud deployed JupyterLab I want to: > For local mode: > # Start local build > # Get locally builded images > # Deploy & undeploy locally builded images locally > # Monitor state of local deployments > For cloud mode: > # Authorize / UnAuthorize on cloud > # Get cluster trainings > # Create cluster trainings > # Create & remove cluster deployments > # Monitor cluster deployments (name, model, scale) > # Scale cluster deployments > All mods (local & cloud) should be individually configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-705) Add detailed documentation about feedback gathering
Vira Vitanska created DLAB-705: -- Summary: Add detailed documentation about feedback gathering Key: DLAB-705 URL: https://issues.apache.org/jira/browse/DLAB-705 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 As a user of Legion platform I want to have information how I can use feedback mechanism and how it works under the hood. Also examples should be presented. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-708) Make Legion neutral to particular Docker repository
Vira Vitanska created DLAB-708: -- Summary: Make Legion neutral to particular Docker repository Key: DLAB-708 URL: https://issues.apache.org/jira/browse/DLAB-708 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 Legion platform has to be neutral to Docker repository and does not stick to particular repository like Nexus. So, to make it possible the following tasks should be completed: # refactor code to make docker repository for ML models fully configurable # add CR and operator for managing Docker Registry credentials -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-710) Deploy Legion to managed K8S cluster
Vira Vitanska created DLAB-710: -- Summary: Deploy Legion to managed K8S cluster Key: DLAB-710 URL: https://issues.apache.org/jira/browse/DLAB-710 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Aliaksandr Semianets Fix For: v.2.2 As a DevOps engineer I would like to have automation for K8S setup on managed services at GCP\AWS\Azure cloud providers so I can deploy Legion to any k8s cluster matching requirements. This work will require several steps such as: # implement Terraform modules for each cloud provide which will setup managed K8S as a service # Update Legion deployment scripts to make use of the new infra setup -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-698) Replace manually created EDGE router with more standardized solution
[ https://issues.apache.org/jira/browse/DLAB-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-698: --- Labels: 1.0.0 improvement (was: improvement) > Replace manually created EDGE router with more standardized solution > > > Key: DLAB-698 > URL: https://issues.apache.org/jira/browse/DLAB-698 > Project: Apache DLab > Issue Type: Improvement > Components: Legion >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: 1.0.0, improvement > Fix For: v.2.2 > > > We have to replace our EDGE (that is OpenResty + python code) with istio > > Tasks: > * Istio deployment > * Rename `model-id` with `model-name` > * Remove edge deployment > * Legion operator supports istio -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-693) Implement Legion platform provisioning on GKE with Terraform
[ https://issues.apache.org/jira/browse/DLAB-693?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-693: --- Labels: 1.1.0 K8S_to_PaaS (was: K8S_to_PaaS) > Implement Legion platform provisioning on GKE with Terraform > > > Key: DLAB-693 > URL: https://issues.apache.org/jira/browse/DLAB-693 > Project: Apache DLab > Issue Type: Task > Components: Legion >Reporter: Vira Vitanska >Assignee: Aliaksandr Semianets >Priority: Major > Labels: 1.1.0, K8S_to_PaaS > Fix For: v.2.2 > > > As a DevOps engineer I would like to have terraform based solution for > infrastructure management so I can deployes GKE cluster with Legion and all > dependencies on top of that. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-701) Legion pods authentication with IAM roles at GCP
[ https://issues.apache.org/jira/browse/DLAB-701?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-701: --- Labels: 1.1.0 K8S_to_PaaS feature (was: K8S_to_PaaS feature) > Legion pods authentication with IAM roles at GCP > > > Key: DLAB-701 > URL: https://issues.apache.org/jira/browse/DLAB-701 > Project: Apache DLab > Issue Type: Task > Components: Legion >Reporter: Vira Vitanska >Assignee: Dmitriy Karbyshev >Priority: Major > Labels: 1.1.0, K8S_to_PaaS, feature > Fix For: v.2.2 > > > As a Developer I would like to be able to authorize legion components such as > fluentd with iam roles specific to the component so I don't have to setup > predefined keys in configs. > Details: > We have kube2iam implementation at K8S cluster at AWS which provides AWS > credentials to the PODs from EC2 Metadata. We need to implement the same > feature at GKE cluster as well. > As for now we grant access to fluentd, airflow and jenkins which store data > at per cluster s3 bucket. > The same approach should be transferred to GCP and automated with terraform. > AC: > * kube2iam analog for GCP is implemented with terraform > * required IAM roles and policies are implemented with terraform > * fluentd, legion models, jenkins, airflow can get access to GCS storage > with IAM roles -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-712) Review common project documentation (components, description and etc)
Vira Vitanska created DLAB-712: -- Summary: Review common project documentation (components, description and etc) Key: DLAB-712 URL: https://issues.apache.org/jira/browse/DLAB-712 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-717) Updating version of appVersion in HELM chart
Vira Vitanska created DLAB-717:
--
Summary: Updating version of appVersion in HELM chart
Key: DLAB-717
URL: https://issues.apache.org/jira/browse/DLAB-717
Project: Apache DLab
Issue Type: Task
Components: Legion
Reporter: Vira Vitanska
Assignee: Kirill Makhonin
Fix For: v.2.2
Field {{appVersion}} should be linked to appropriate version of Legion
application.
We have to add updating of this value to releasing pipeline.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-717) Updating version of appVersion in HELM chart
[
https://issues.apache.org/jira/browse/DLAB-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska reassigned DLAB-717:
--
Assignee: Aliaksandr Semianets (was: Kirill Makhonin)
> Updating version of appVersion in HELM chart
> -
>
> Key: DLAB-717
> URL: https://issues.apache.org/jira/browse/DLAB-717
> Project: Apache DLab
> Issue Type: Task
> Components: Legion
>Reporter: Vira Vitanska
>Assignee: Aliaksandr Semianets
>Priority: Major
> Labels: 1.0.0, feature
> Fix For: v.2.2
>
>
> Field {{appVersion}} should be linked to appropriate version of Legion
> application.
> We have to add updating of this value to releasing pipeline.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-715) Pin Golang dependencies in legion-aws containers
[
https://issues.apache.org/jira/browse/DLAB-715?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska reassigned DLAB-715:
--
Assignee: Vitalii Solodilov (was: Kirill Makhonin)
> Pin Golang dependencies in legion-aws containers
>
>
> Key: DLAB-715
> URL: https://issues.apache.org/jira/browse/DLAB-715
> Project: Apache DLab
> Issue Type: Task
> Components: Legion
>Reporter: Vira Vitanska
>Assignee: Vitalii Solodilov
>Priority: Major
> Labels: 1.0.0, feature, security
> Fix For: v.2.2
>
>
> We have to pin all third-party dependencies (like {{aws/aws-sdk-go}}) in all
> our products.
> Usually, we use dep for this purposes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-713) Set up explicit timeouts for model API
[ https://issues.apache.org/jira/browse/DLAB-713?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-713: -- Assignee: Vitalii Solodilov (was: Kirill Makhonin) > Set up explicit timeouts for model API > -- > > Key: DLAB-713 > URL: https://issues.apache.org/jira/browse/DLAB-713 > Project: Apache DLab > Issue Type: Task > Components: Legion >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: 1.0.0, improvement > Fix For: v.2.2 > > > We need to setup explicit timeouts on next levels: > * Ingress annotations > * Proxy configuration > * Flask configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-720) Cleanup legion_airflow dependencies in Pipfile
Vira Vitanska created DLAB-720: -- Summary: Cleanup legion_airflow dependencies in Pipfile Key: DLAB-720 URL: https://issues.apache.org/jira/browse/DLAB-720 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Aliaksandr Semianets Fix For: v.2.2 As a DevOps engineer I would like to cleanup package dependencies for legion_airflow so I don't install unnecessary packages -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-721) Auto cleanup of build images on Kubernetes nodes
Vira Vitanska created DLAB-721: -- Summary: Auto cleanup of build images on Kubernetes nodes Key: DLAB-721 URL: https://issues.apache.org/jira/browse/DLAB-721 Project: Apache DLab Issue Type: Bug Components: Legion Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 As we build model images on k8s worker nodes, we must delete a built model docker image. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-723) Runc vulnerability CVE-2019-5736
Vira Vitanska created DLAB-723: -- Summary: Runc vulnerability CVE-2019-5736 Key: DLAB-723 URL: https://issues.apache.org/jira/browse/DLAB-723 Project: Apache DLab Issue Type: Bug Components: Legion Reporter: Vira Vitanska Assignee: Aliaksandr Semianets Fix For: v.2.2 Read more: * [https://seclists.org/oss-sec/2019/q1/119] * [https://github.com/docker/docker-ce/releases/tag/v18.09.2] * [https://habr.com/ru/company/flant/blog/439964/] * [https://kubernetes.io/blog/page/2/] Need to wait [https://github.com/kubernetes/kops/pull/6460/files] \ [https://github.com/kubernetes/kops/pull/6461/files] merging and upgrade kops. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-700) Reduce count of HTTP proxies during model API invocation
[ https://issues.apache.org/jira/browse/DLAB-700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-700: --- Labels: 1.0.0 improvement performence (was: improvement performence) > Reduce count of HTTP proxies during model API invocation > > > Key: DLAB-700 > URL: https://issues.apache.org/jira/browse/DLAB-700 > Project: Apache DLab > Issue Type: Improvement > Components: Legion >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: 1.0.0, improvement, performence > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-706) Add network connectivity requirements for HELM chart
[ https://issues.apache.org/jira/browse/DLAB-706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-706: --- Issue Type: Sub-task (was: Task) Parent: DLAB-712 > Add network connectivity requirements for HELM chart > > > Key: DLAB-706 > URL: https://issues.apache.org/jira/browse/DLAB-706 > Project: Apache DLab > Issue Type: Sub-task > Components: Legion >Reporter: Vira Vitanska >Assignee: Kirill Makhonin >Priority: Major > Labels: 1.0.0, documentaion, feature, security > Fix For: v.2.2 > > > We have to describe what components have to have connection with which > service (source namespaces, pods and target namespaces, pods and ports). > First assumptions are: > # Kubernetes Ingress pod to EDGE/EDI pods port 80 > # Prometheus metrics collector to EDGE/EDI/Operator pods port XXX > # EDGE pods to model pods -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-713) Set up explicit timeouts for model API
Vira Vitanska created DLAB-713: -- Summary: Set up explicit timeouts for model API Key: DLAB-713 URL: https://issues.apache.org/jira/browse/DLAB-713 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 We need to setup explicit timeouts on next levels: * Ingress annotations * Proxy configuration * Flask configuration -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-716) Add NOTES to HELM chart
Vira Vitanska created DLAB-716:
--
Summary: Add NOTES to HELM chart
Key: DLAB-716
URL: https://issues.apache.org/jira/browse/DLAB-716
Project: Apache DLab
Issue Type: Task
Components: Legion
Reporter: Vira Vitanska
Assignee: Kirill Makhonin
Fix For: v.2.2
As a User of HELM chart I want to get information:
* How I can reach installed systems
* Which functions are working and which not with refers to documentation about
function and its configuration
* General links to documentation
* Quick description of next steps to use this platform ({{legionctl login...}}
and etc.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-715) Pin Golang dependencies in legion-aws containers
Vira Vitanska created DLAB-715:
--
Summary: Pin Golang dependencies in legion-aws containers
Key: DLAB-715
URL: https://issues.apache.org/jira/browse/DLAB-715
Project: Apache DLab
Issue Type: Task
Components: Legion
Reporter: Vira Vitanska
Assignee: Kirill Makhonin
Fix For: v.2.2
We have to pin all third-party dependencies (like {{aws/aws-sdk-go}}) in all
our products.
Usually, we use dep for this purposes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-718) Add linting to HELM charts
Vira Vitanska created DLAB-718: -- Summary: Add linting to HELM charts Key: DLAB-718 URL: https://issues.apache.org/jira/browse/DLAB-718 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Dmitriy Karbyshev Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-725) Add legion-snippets and link to legion help into local jupyter-notebook server
Vira Vitanska created DLAB-725:
--
Summary: Add legion-snippets and link to legion help into local
jupyter-notebook server
Key: DLAB-725
URL: https://issues.apache.org/jira/browse/DLAB-725
Project: Apache DLab
Issue Type: Task
Components: Legion
Reporter: Vira Vitanska
Assignee: Kirill Makhonin
Fix For: v.2.2
In order to simplify legion usage inside of Jupyter notebooks we can add code
snippets with required legion functions (like import {{legion.model}}
{{legion.model.init}} and {{legion.model.export}}) into Jupyter notebook
interface.
Also we may add button that will execute {{legionctl build}} inside Jupyter
notebook without switching to console.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-711) Legion-airflow deployment with terraform
Vira Vitanska created DLAB-711: -- Summary: Legion-airflow deployment with terraform Key: DLAB-711 URL: https://issues.apache.org/jira/browse/DLAB-711 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Aliaksandr Semianets Fix For: v.2.2 Legion-airflow component should be adopted to the new approach with infrastructure management with Terraform. As soon as we start using Legion on GKE we should be able to deploy Airflow component the same way we do for the Legion itself. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-714) Jupyter notebook for Legion quick start with usage examples
Vira Vitanska created DLAB-714: -- Summary: Jupyter notebook for Legion quick start with usage examples Key: DLAB-714 URL: https://issues.apache.org/jira/browse/DLAB-714 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 As a DS engineer I want to have examples in Jupyter notebook about what I can do with model (deploy, call, undeploy) locally and on a cluster. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-719) Add ability to set tags for model training process
Vira Vitanska created DLAB-719:
--
Summary: Add ability to set tags for model training process
Key: DLAB-719
URL: https://issues.apache.org/jira/browse/DLAB-719
Project: Apache DLab
Issue Type: Task
Components: Legion
Reporter: Vira Vitanska
Assignee: Vitalii Solodilov
Fix For: v.2.2
We have to set tags in free form during Legion model training (like
{{model.set_tag("dataset", "a.csv")}}.
Each training can contain more than one metric. Each metric is a key-value pair
of strings.
This tags should be linked to train metrics (it will be nice if they being
persisted in prometheus as one entity).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-722) Upgrade flask to the 1.0+ version
[ https://issues.apache.org/jira/browse/DLAB-722?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-722: --- Issue Type: Task (was: Bug) > Upgrade flask to the 1.0+ version > - > > Key: DLAB-722 > URL: https://issues.apache.org/jira/browse/DLAB-722 > Project: Apache DLab > Issue Type: Task > Components: Legion >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: 1.0.0, improvement > Fix For: v.2.2 > > > Changelog: [http://flask.pocoo.org/docs/1.0/changelog/] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-722) Upgrade flask to the 1.0+ version
Vira Vitanska created DLAB-722: -- Summary: Upgrade flask to the 1.0+ version Key: DLAB-722 URL: https://issues.apache.org/jira/browse/DLAB-722 Project: Apache DLab Issue Type: Bug Components: Legion Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 Changelog: [http://flask.pocoo.org/docs/1.0/changelog/] -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-723) Runc vulnerability CVE-2019-5736
[ https://issues.apache.org/jira/browse/DLAB-723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-723: --- Issue Type: Task (was: Bug) > Runc vulnerability CVE-2019-5736 > > > Key: DLAB-723 > URL: https://issues.apache.org/jira/browse/DLAB-723 > Project: Apache DLab > Issue Type: Task > Components: Legion >Reporter: Vira Vitanska >Assignee: Aliaksandr Semianets >Priority: Major > Labels: 1.0.0, security > Fix For: v.2.2 > > > Read more: > * [https://seclists.org/oss-sec/2019/q1/119] > * [https://github.com/docker/docker-ce/releases/tag/v18.09.2] > * [https://habr.com/ru/company/flant/blog/439964/] > * [https://kubernetes.io/blog/page/2/] > Need to wait [https://github.com/kubernetes/kops/pull/6460/files] \ > [https://github.com/kubernetes/kops/pull/6461/files] merging and upgrade kops. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-724) Make error reports more informative during model HTTP invoke #61
Vira Vitanska created DLAB-724: -- Summary: Make error reports more informative during model HTTP invoke #61 Key: DLAB-724 URL: https://issues.apache.org/jira/browse/DLAB-724 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 We need to add more details: * on nginx side when we cannot connect to upstream * on python serve side when we cannot provide answer (wrong input, error on model side and so on) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-697) Training and deploying MLflow models
Vira Vitanska created DLAB-697: -- Summary: Training and deploying MLflow models Key: DLAB-697 URL: https://issues.apache.org/jira/browse/DLAB-697 Project: Apache DLab Issue Type: Sub-task Components: Legion Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-661) Mongo service
[ https://issues.apache.org/jira/browse/DLAB-661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-661: -- Assignee: Demyan Mysakovets (was: Oleksandr Isniuk) > Mongo service > - > > Key: DLAB-661 > URL: https://issues.apache.org/jira/browse/DLAB-661 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Deleted] (DLAB-697) Training and deploying MLflow models
[ https://issues.apache.org/jira/browse/DLAB-697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-697: --- > Training and deploying MLflow models > > > Key: DLAB-697 > URL: https://issues.apache.org/jira/browse/DLAB-697 > Project: Apache DLab > Issue Type: Sub-task >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: feature > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-696) Add ability to train and deploy MLflow models
[ https://issues.apache.org/jira/browse/DLAB-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-696: -- Assignee: Vitalii Solodilov (was: Kirill Makhonin) > Add ability to train and deploy MLflow models > -- > > Key: DLAB-696 > URL: https://issues.apache.org/jira/browse/DLAB-696 > Project: Apache DLab > Issue Type: Task > Components: Legion >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: feature > Fix For: v.2.2 > > > As a user, I want to train models that I've developed using MLflow library. > This action should not require any changes in model's source code. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-699) Add support of numpy values in JSON serialization during model response building
[ https://issues.apache.org/jira/browse/DLAB-699?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-699: --- Issue Type: New Feature (was: Task) > Add support of numpy values in JSON serialization during model response > building > > > Key: DLAB-699 > URL: https://issues.apache.org/jira/browse/DLAB-699 > Project: Apache DLab > Issue Type: New Feature > Components: Legion >Reporter: Vira Vitanska >Priority: Major > Labels: feature > Fix For: v.2.2 > > > Currently developers have to add casting to int/float types in apply function > which return numpy objects because of the fact that by default python's json > package cannot serialize numpy types -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-694) Upgrade Airflow to latest version(1.10) compatible with k8s scheduler
[ https://issues.apache.org/jira/browse/DLAB-694?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-694: --- Issue Type: New Feature (was: Task) > Upgrade Airflow to latest version(1.10) compatible with k8s scheduler > - > > Key: DLAB-694 > URL: https://issues.apache.org/jira/browse/DLAB-694 > Project: Apache DLab > Issue Type: New Feature > Components: Legion >Reporter: Vira Vitanska >Assignee: Aliaksandr Semianets >Priority: Major > Labels: Spike, feature > Fix For: v.2.2 > > > Upgrade Airflow to latest version(1.10) compatible with k8s scheduler to : > # get rid off Celery scheduler > # package DAGs with dependencies into docker containers -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-700) Reduce count of HTTP proxies during model API invocation
Vira Vitanska created DLAB-700: -- Summary: Reduce count of HTTP proxies during model API invocation Key: DLAB-700 URL: https://issues.apache.org/jira/browse/DLAB-700 Project: Apache DLab Issue Type: Improvement Components: Legion Reporter: Vira Vitanska Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-695) Create Legion plugin for JupyterLab
[ https://issues.apache.org/jira/browse/DLAB-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-695: --- Issue Type: New Feature (was: Task) > Create Legion plugin for JupyterLab > --- > > Key: DLAB-695 > URL: https://issues.apache.org/jira/browse/DLAB-695 > Project: Apache DLab > Issue Type: New Feature > Components: Legion >Reporter: Vira Vitanska >Assignee: Kirill Makhonin >Priority: Major > Labels: feature > Fix For: v.2.2 > > > As a User of local or cloud deployed JupyterLab I want to: > For local mode: > # Start local build > # Get locally builded images > # Deploy & undeploy locally builded images locally > # Monitor state of local deployments > For cloud mode: > # Authorize / UnAuthorize on cloud > # Get cluster trainings > # Create cluster trainings > # Create & remove cluster deployments > # Monitor cluster deployments (name, model, scale) > # Scale cluster deployments > All mods (local & cloud) should be individually configurable. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-696) Add ability to train and deploy MLflow models
[ https://issues.apache.org/jira/browse/DLAB-696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-696: --- Issue Type: New Feature (was: Task) > Add ability to train and deploy MLflow models > -- > > Key: DLAB-696 > URL: https://issues.apache.org/jira/browse/DLAB-696 > Project: Apache DLab > Issue Type: New Feature > Components: Legion >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: feature > Fix For: v.2.2 > > > As a user, I want to train models that I've developed using MLflow library. > This action should not require any changes in model's source code. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Deleted] (DLAB-692) Self-service
[ https://issues.apache.org/jira/browse/DLAB-692?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-692: --- > Self-service > > > Key: DLAB-692 > URL: https://issues.apache.org/jira/browse/DLAB-692 > Project: Apache DLab > Issue Type: Sub-task >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-698) Replace manually created EDGE router with more standardized solution
Vira Vitanska created DLAB-698: -- Summary: Replace manually created EDGE router with more standardized solution Key: DLAB-698 URL: https://issues.apache.org/jira/browse/DLAB-698 Project: Apache DLab Issue Type: Improvement Reporter: Vira Vitanska Assignee: Vitalii Solodilov Fix For: v.2.2 We have to replace our EDGE (that is OpenResty + python code) to more simplest or standardized solution. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-699) Add support of numpy values in JSON serialization during model response building
Vira Vitanska created DLAB-699: -- Summary: Add support of numpy values in JSON serialization during model response building Key: DLAB-699 URL: https://issues.apache.org/jira/browse/DLAB-699 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Fix For: v.2.2 Currently developers have to add casting to int/float types in apply function which return numpy objects because of the fact that by default python's json package cannot serialize numpy types -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-698) Replace manually created EDGE router with more standardized solution
[ https://issues.apache.org/jira/browse/DLAB-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-698: --- Component/s: Legion > Replace manually created EDGE router with more standardized solution > > > Key: DLAB-698 > URL: https://issues.apache.org/jira/browse/DLAB-698 > Project: Apache DLab > Issue Type: Improvement > Components: Legion >Reporter: Vira Vitanska >Assignee: Vitalii Solodilov >Priority: Major > Labels: improvement > Fix For: v.2.2 > > > We have to replace our EDGE (that is OpenResty + python code) to more > simplest or standardized solution. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-630) [Admin]: Ability to create a Project
[ https://issues.apache.org/jira/browse/DLAB-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-630: --- Summary: [Admin]: Ability to create a Project (was: Ability to create a Project) > [Admin]: Ability to create a Project > > > Key: DLAB-630 > URL: https://issues.apache.org/jira/browse/DLAB-630 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-630) [Admin]: Ability to create a Project
[ https://issues.apache.org/jira/browse/DLAB-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-630: --- Labels: Debian (was: ) Description: As an Admin I want to create project(s) and view them, so that I can add group/user(s) per project, assign roles per project, view what group/users are in the project. *Preconditions:* # Admin is logged-in DLab # Admin is located in ‘Project’ tab on ‘Administration’ page # At least one endpoint is created *Description:* Current functionality of 'Manage roles' moves to 'Project' tab and renames ‘Manage project’. Admin can create a project clicking 'Create project' button. ‘Manage project’ popup appears which consists of: *Step 1 (mandatory)* - Project name - should be unique within all DLab [editable] - Endpoint name - [editable] - Endpoint - dropdown (AWS Account 1, AWS Account 2, GCP Account 1) [part of config file] - Project Tag: autogenerated, based on project name: dlab_project_name (validation if tag already exists within projects in same account) [ editable] *Step 2* * Add a group (mandatory) *Step 3* * Assign shape/template (mandatory) *Step 4* * Add user(s) (optional) * ‘Back’ button * ‘Cancel’ button * ‘Create’ button If Admin clicks ‘Back’ button he returns to Step 3 If Admin clicks ‘Cancel’ button the project is not added and ‘Manage project’ popup is open. If Admin clicks ‘Create button the project is added, appears in grid among the other project, and ‘Manage project’ popup is open. Grid on ‘Manage project’ consists of: * Progect_name * Group_name * Roles * Users * Action *Acceptance criteria:* # Admin is able to create a project # Admin is able to return to the previous step on the project creation step if admin has not clicked ‘Create’ button. # Admin is able to view all existing project(s) # The project_shared_bucket is created on Project creation step-> # User has his home directory, BUT this folder will be accessible for everyone [(v1) - SHORT TERM] # User should have proper permission scheme applied later *[(v2) - LONG TERM]* # Example: project_bucket: home/user1, home/user2, shared # Cloud Role is assigned per project NOT per user # Roles per project is created - automatically # It is forbidden to access to other user notebooks within same project on identity provider level - [(v1) - SHORT TERM] # Users works under his own identity. All actions are logged from that username - *[(v2) - LONG TERM]* # All edge nodes within project subnet - [(v1) - SHORT TERM] # VPC is created - manually 13.1. Multiple projects per 1 VPC 13.2. Rare case: 1 Project ! VPC # Subnet: 14.1. We define Subnet CIDR via WebUI - automatically 14.2. Subnet per 1 project -> Subnet CIDR to be defined on UI > [Admin]: Ability to create a Project > > > Key: DLAB-630 > URL: https://issues.apache.org/jira/browse/DLAB-630 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian > Fix For: v.2.2 > > > As an Admin I want to create project(s) and view them, so that I can add > group/user(s) per project, assign roles per project, view what group/users > are in the project. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located in ‘Project’ tab on ‘Administration’ page > # At least one endpoint is created > > *Description:* > Current functionality of 'Manage roles' moves to 'Project' tab and renames > ‘Manage project’. > Admin can create a project clicking 'Create project' button. ‘Manage > project’ popup appears which consists of: > *Step 1 (mandatory)* > - Project name - should be unique within all DLab [editable] > - Endpoint name - [editable] > - Endpoint - dropdown (AWS Account 1, AWS Account 2, GCP Account 1) [part of > config file] > - Project Tag: autogenerated, based on project name: dlab_project_name > (validation if tag already exists within projects in same account) [ editable] > *Step 2* > * Add a group (mandatory) > *Step 3* > * Assign shape/template (mandatory) > *Step 4* > * Add user(s) (optional) > * ‘Back’ button > * ‘Cancel’ button > * ‘Create’ button > If Admin clicks ‘Back’ button he returns to Step 3 > If Admin clicks ‘Cancel’ button the project is not added and ‘Manage project’ > popup is open. > If Admin clicks ‘Create button the project is added, appears in grid among > the other project, and ‘Manage project’ popup is open. > Grid on ‘Manage project’ consists of: > * Progect_name > * Group_name > * Roles > * Users > * Action > > *Acceptance criteria:* > # Admin is able to create a project > # Admin is able to return to the previous step on the project creation step > if admin has not clicked ‘Create’ button. > #
[jira] [Created] (DLAB-633) Ability to edit a project
Vira Vitanska created DLAB-633: -- Summary: Ability to edit a project Key: DLAB-633 URL: https://issues.apache.org/jira/browse/DLAB-633 Project: Apache DLab Issue Type: Bug Components: GCP Reporter: Vira Vitanska Assignee: Vira Vitanska Fix For: v.2.2 As an Admin I want to edit project(s), so that I can add or remove user(s). *Preconditions:* # Admin is logged-in DLab # Admin is located in ‘Project’ tab on ‘Administration’ page # At least one project is created *Description:* If Admin clicks action menu for related project ‘Manage project’ popup appears. Admin can remove the user from a project hitting on removing icon for appropriate user and in ‘users’ column and confirm the action. Admin can add user typing the username in users column and confirm the action. *Acceptance criteria:* # Admin is able to remove user from a project # Admin is able to add user to a project -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-633) [Admin}]: Ability to edit a project
[ https://issues.apache.org/jira/browse/DLAB-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-633: --- Summary: [Admin}]: Ability to edit a project (was: Ability to edit a project) > [Admin}]: Ability to edit a project > --- > > Key: DLAB-633 > URL: https://issues.apache.org/jira/browse/DLAB-633 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, Project > Fix For: v.2.2 > > > As an Admin I want to edit project(s), so that I can add or remove user(s). > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located in ‘Project’ tab on ‘Administration’ page > # At least one project is created > > *Description:* > If Admin clicks action menu for related project ‘Manage project’ popup > appears. > Admin can remove the user from a project hitting on removing icon for > appropriate user and in ‘users’ column and confirm the action. > Admin can add user typing the username in users column and confirm the action. > > *Acceptance criteria:* > # Admin is able to remove user from a project > # Admin is able to add user to a project -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-633) [Admin]: Ability to edit a project
[ https://issues.apache.org/jira/browse/DLAB-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-633: --- Summary: [Admin]: Ability to edit a project (was: [Admin}]: Ability to edit a project) > [Admin]: Ability to edit a project > -- > > Key: DLAB-633 > URL: https://issues.apache.org/jira/browse/DLAB-633 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, Project > Fix For: v.2.2 > > > As an Admin I want to edit project(s), so that I can add or remove user(s). > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located in ‘Project’ tab on ‘Administration’ page > # At least one project is created > > *Description:* > If Admin clicks action menu for related project ‘Manage project’ popup > appears. > Admin can remove the user from a project hitting on removing icon for > appropriate user and in ‘users’ column and confirm the action. > Admin can add user typing the username in users column and confirm the action. > > *Acceptance criteria:* > # Admin is able to remove user from a project > # Admin is able to add user to a project -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-642) Viewing Administration page
[ https://issues.apache.org/jira/browse/DLAB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-642: --- Description: As an Admin I want to have all necessary instruments so that I can do administrative operations. *Preconditions:* # Admin is logged-in DLab # Admin is located on ‘Administration’ page *Acceptance criteria**:* ‘Administration’ page consists of: # Navigation menu in the left side: 1.1. ‘List of Resources’ 1.2. ‘Administration’ 1.3. ‘Billing Report’ # Tabs: 2.1. ‘Endpoint’ [(v2) - LONG TERM] 2.2. ‘Project’ # Buttons: 3.1. ‘SSN monitor’ 3.2. ‘Manage environment’ 3.3. ‘Backup’ 3.4. ‘Refresh’ > Viewing Administration page > --- > > Key: DLAB-642 > URL: https://issues.apache.org/jira/browse/DLAB-642 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, Project > Fix For: v.2.2 > > > As an Admin I want to have all necessary instruments so that I can do > administrative operations. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located on ‘Administration’ page > > *Acceptance criteria**:* > ‘Administration’ page consists of: > # Navigation menu in the left side: > 1.1. ‘List of Resources’ > 1.2. ‘Administration’ > 1.3. ‘Billing Report’ > # Tabs: > 2.1. ‘Endpoint’ [(v2) - LONG TERM] > 2.2. ‘Project’ > # Buttons: > 3.1. ‘SSN monitor’ > 3.2. ‘Manage environment’ > 3.3. ‘Backup’ > 3.4. ‘Refresh’ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-642) Viewing and switching between tabs on Administration page
[ https://issues.apache.org/jira/browse/DLAB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-642: --- Summary: Viewing and switching between tabs on Administration page (was: Viewing Administration page) > Viewing and switching between tabs on Administration page > - > > Key: DLAB-642 > URL: https://issues.apache.org/jira/browse/DLAB-642 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, Project > Fix For: v.2.2 > > > As an Admin I want to have all necessary instruments so that I can do > administrative operations. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located on ‘Administration’ page > > *Acceptance criteria**:* > ‘Administration’ page consists of: > # Navigation menu in the left side: > 1.1. ‘List of Resources’ > 1.2. ‘Administration’ > 1.3. ‘Billing Report’ > # Tabs: > 2.1. ‘Endpoint’ [(v2) - LONG TERM] > 2.2. ‘Project’ > # Buttons: > 3.1. ‘SSN monitor’ > 3.2. ‘Manage environment’ > 3.3. ‘Backup’ > 3.4. ‘Refresh’ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-642) Extension of Administration page
[ https://issues.apache.org/jira/browse/DLAB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-642: --- Description: As an Admin I want to have all necessary instruments so that I can do administrative operations. *Preconditions:* # Admin is logged-in DLab # Admin is located on ‘Administration’ page *Acceptance criteria**:* ‘Administration’ page consists of navigation menu in the left side: 1. ‘List of Resources’ 2. ‘Administration’: 2.1. 'Endpoint' [(v2) - LONG TERM] 2.2. 'Projects' 2.3. 'Environment management' 3. ‘Billing Report’ There are the following buttons on 'Environment management' page: - ‘SSN monitor’ - ‘Manage environment’ - ‘Backup’ - ‘Refresh’ was: As an Admin I want to have all necessary instruments so that I can do administrative operations. *Preconditions:* # Admin is logged-in DLab # Admin is located on ‘Administration’ page *Acceptance criteria**:* ‘Administration’ page consists of: # Navigation menu in the left side: 1.1. ‘List of Resources’ 1.2. ‘Administration’: 1.2.1. 'Endpoint' [(v2) - LONG TERM] 1.2.2. 'Projects' 1.2.3. 'Environment management' 1.3. ‘Billing Report’ There are the following buttons on 'Environment management' page: - ‘SSN monitor’ - ‘Manage environment’ - ‘Backup’ - ‘Refresh’ > Extension of Administration page > - > > Key: DLAB-642 > URL: https://issues.apache.org/jira/browse/DLAB-642 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, Project > Fix For: v.2.2 > > > As an Admin I want to have all necessary instruments so that I can do > administrative operations. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located on ‘Administration’ page > > *Acceptance criteria**:* > ‘Administration’ page consists of navigation menu in the left side: > 1. ‘List of Resources’ > 2. ‘Administration’: > 2.1. 'Endpoint' [(v2) - LONG TERM] > 2.2. 'Projects' > 2.3. 'Environment management' > 3. ‘Billing Report’ > There are the following buttons on 'Environment management' page: > - ‘SSN monitor’ > - ‘Manage environment’ > - ‘Backup’ > - ‘Refresh’ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-642) Extension of Administration page
[ https://issues.apache.org/jira/browse/DLAB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-642: --- Description: As an Admin I want to have all necessary instruments so that I can do administrative operations. *Preconditions:* # Admin is logged-in DLab # Admin is located on ‘Administration’ page *Acceptance criteria**:* ‘Administration’ page consists of navigation menu in the left side: 1. ‘List of Resources’ 2. ‘Administration’: 2.1. 'Endpoint' [(v2) - LONG TERM] 2.2. 'Projects' 2.3. 'Environment management' 3. ‘Billing Report’ There are the following buttons on 'Environment management' page: - ‘SSN monitor’ - ‘Manage environment’ - ‘Backup’ - ‘Refresh’ was: As an Admin I want to have all necessary instruments so that I can do administrative operations. *Preconditions:* # Admin is logged-in DLab # Admin is located on ‘Administration’ page *Acceptance criteria**:* ‘Administration’ page consists of navigation menu in the left side: 1. ‘List of Resources’ 2. ‘Administration’: 2.1. 'Endpoint' [(v2) - LONG TERM] 2.2. 'Projects' 2.3. 'Environment management' 3. ‘Billing Report’ There are the following buttons on 'Environment management' page: - ‘SSN monitor’ - ‘Manage environment’ - ‘Backup’ - ‘Refresh’ > Extension of Administration page > - > > Key: DLAB-642 > URL: https://issues.apache.org/jira/browse/DLAB-642 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, Project > Fix For: v.2.2 > > > As an Admin I want to have all necessary instruments so that I can do > administrative operations. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located on ‘Administration’ page > > *Acceptance criteria**:* > ‘Administration’ page consists of navigation menu in the left side: > 1. ‘List of Resources’ > 2. ‘Administration’: > 2.1. 'Endpoint' [(v2) - LONG TERM] > 2.2. 'Projects' > 2.3. 'Environment management' > 3. ‘Billing Report’ > There are the following buttons on 'Environment management' page: > - ‘SSN monitor’ > - ‘Manage environment’ > - ‘Backup’ > - ‘Refresh’ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-642) Extension of Administration page
[ https://issues.apache.org/jira/browse/DLAB-642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-642: --- Description: As an Admin I want to have all necessary instruments so that I can do administrative operations. *Preconditions:* # Admin is logged-in DLab # Admin is located on ‘Administration’ page *Acceptance criteria**:* ‘Administration’ page consists of navigation menu in the left side: 1. ‘List of Resources’ 2. ‘Administration’: 2.1. 'Endpoint' [(v2) - LONG TERM] 2.2. 'Projects' 2.3. 'Environment management' 3. ‘Billing Report’ There are the following buttons on 'Environment management' page: - ‘SSN monitor’ - ‘Manage environment’ - ‘Backup’ - ‘Refresh’ was: As an Admin I want to have all necessary instruments so that I can do administrative operations. *Preconditions:* # Admin is logged-in DLab # Admin is located on ‘Administration’ page *Acceptance criteria**:* ‘Administration’ page consists of navigation menu in the left side: 1. ‘List of Resources’ 2. ‘Administration’: 2.1. 'Endpoint' [(v2) - LONG TERM] 2.2. 'Projects' 2.3. 'Environment management' 3. ‘Billing Report’ There are the following buttons on 'Environment management' page: - ‘SSN monitor’ - ‘Manage environment’ - ‘Backup’ - ‘Refresh’ > Extension of Administration page > - > > Key: DLAB-642 > URL: https://issues.apache.org/jira/browse/DLAB-642 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, Project > Fix For: v.2.2 > > > As an Admin I want to have all necessary instruments so that I can do > administrative operations. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located on ‘Administration’ page > > *Acceptance criteria**:* > ‘Administration’ page consists of navigation menu in the left side: > 1. ‘List of Resources’ > 2. ‘Administration’: > 2.1. 'Endpoint' [(v2) - LONG TERM] > 2.2. 'Projects' > 2.3. 'Environment management' > 3. ‘Billing Report’ > There are the following buttons on 'Environment management' page: > - ‘SSN monitor’ > - ‘Manage environment’ > - ‘Backup’ > - ‘Refresh’ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-645) Front-end
Vira Vitanska created DLAB-645: -- Summary: Front-end Key: DLAB-645 URL: https://issues.apache.org/jira/browse/DLAB-645 Project: Apache DLab Issue Type: Sub-task Components: GCP Reporter: Vira Vitanska Assignee: Andriana Kovalyshyn Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-653) Possibility to create analytical tool
[ https://issues.apache.org/jira/browse/DLAB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-653: --- Description: As a User I want to create analytical tools so that I can use and manage them for analytical calculations. *Preconditions:* # User is logged-in DLab # User is located in ‘List of Resources’ page *Description:* If User clicks ‘+ Create new’ button ‘Analytical tool’ popup appears which consists of: * ‘Select template’ - drop down list * ‘Name’ - textbox it should be unique within endpoint and user * ‘Instance shape’ (AWS)/‘Virtual machine size’ (Azure) drop down list * ‘Project’ - drop down list * ‘Endpoint’ - drop down list * two buttons ‘Cancel’ and ‘Create’ All fields are mandatory. If User clicks ‘Create’ button the analytical tool is creating and ‘Analytical tool’ popup is closed. If User clicks ‘Cancel’ button the analytical tool is not created and ‘Analytical tool’ popup is closed. *Acceptance criteria:* # User is able to create analytical tool # User is able to choose in what project analytical tool will be created # During the first notebook template creation shared AMI is created. Shared AMI is per Endpoint and per Cloud # User can create notebook from custom AMI. Custom AMI is per user and per Cloud # It is not allowed for other user to access to notebooks within same project on identity provider level - [(v1) - SHORT TERM] # Users works under his own identity. All actions are logged from that username *[(v2) - LONG TERM]* was: As a User I want to create analytical tools so that I can use and manage them for analytical calculations. *Preconditions:* # User is logged-in DLab # User is located in ‘List of Resources’ page *Description:* If User clicks ‘+ Create new’ button ‘Analytical tool’ popup appears which consists of: * ‘Select template’ - drop down list * ‘Name’ - textbox it should be unique within endpoint and user * ‘Instance shape’ (AWS)/‘Virtual machine size’ (Azure) drop down list * ‘Project’ - drop down list * ‘Endpoint’ - drop down list * two buttons ‘Cancel’ and ‘Create’ All fields are mandatory. If User clicks ‘Create’ button the analytical tool is creating and ‘Analytical tool’ popup is closed. If User clicks ‘Cancel’ button the analytical tool is not created and ‘Analytical tool’ popup is closed. *Acceptance criteria:* # User is able to create analytical tool # User is able to choose in what project analytical tool will be created # During the first notebook template creation shared AMI is created. Shared AMI is per Endpoint and per Cloud # User can create notebook from custom AMI. Custom AMI is per user and per Cloud # It is not allowed for other user to access to notebooks within same project on identity provider level - [(v1) - SHORT TERM] # Users works under his own identity. All actions are logged from that username [(v2) - LONG TERM] > Possibility to create analytical tool > - > > Key: DLAB-653 > URL: https://issues.apache.org/jira/browse/DLAB-653 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, Project > Fix For: v.2.2 > > > As a User I want to create analytical tools so that I can use and manage them > for analytical calculations. > > *Preconditions:* > # User is logged-in DLab > # User is located in ‘List of Resources’ page > > *Description:* > If User clicks ‘+ Create new’ button ‘Analytical tool’ popup appears which > consists of: > * ‘Select template’ - drop down list > * ‘Name’ - textbox it should be unique within endpoint and user > * ‘Instance shape’ (AWS)/‘Virtual machine size’ (Azure) drop down list > * ‘Project’ - drop down list > * ‘Endpoint’ - drop down list > * two buttons ‘Cancel’ and ‘Create’ > All fields are mandatory. > If User clicks ‘Create’ button the analytical tool is creating and > ‘Analytical tool’ popup is closed. > If User clicks ‘Cancel’ button the analytical tool is not created and > ‘Analytical tool’ popup is closed. > > *Acceptance criteria:* > # User is able to create analytical tool > # User is able to choose in what project analytical tool will be created > # During the first notebook template creation shared AMI is created. Shared > AMI is per Endpoint and per Cloud > # User can create notebook from custom AMI. Custom AMI is per user and per > Cloud > # It is not allowed for other user to access to notebooks within same > project on identity provider level - [(v1) - SHORT TERM] > # Users works under his own identity. All actions are logged from that > username *[(v2) - LONG TERM]* -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (DLAB-632) Back-end
Vira Vitanska created DLAB-632: -- Summary: Back-end Key: DLAB-632 URL: https://issues.apache.org/jira/browse/DLAB-632 Project: Apache DLab Issue Type: Sub-task Components: GCP Reporter: Vira Vitanska Assignee: Bohdan Hliva -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
