[jira] [Deleted] (DLAB-505) Git
[ https://issues.apache.org/jira/browse/DLAB-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-505: --- > Git > --- > > Key: DLAB-505 > URL: https://issues.apache.org/jira/browse/DLAB-505 > Project: Apache DLab > Issue Type: Epic >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-663) Terraform
[ https://issues.apache.org/jira/browse/DLAB-663?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-663: --- Component/s: (was: DLab Old) DLab Main > Terraform > - > > Key: DLAB-663 > URL: https://issues.apache.org/jira/browse/DLAB-663 > Project: Apache DLab > Issue Type: Epic > Components: DLab Main >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, 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] [Updated] (DLAB-176) [AWS][Azure][RedHat]: Notebook creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Environment: AWS, Azure, Redhat
Labels: AWS AZURE DevOps RedHat (was: AWS DevOps RedHat)
> [AWS][Azure][RedHat]: Notebook creation fails on process of sparkR
> installation
> ---
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
> Environment: AWS, Azure, Redhat
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, AZURE, DevOps, RedHat
> Fix For: v.2.3
>
> Attachments: Azure notebook creation.png, Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio/tensorflof with rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio is created
> The bug is reproduced in develop/feature/projects/roject_tmp branches
--
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-176) [AWS][Azure][RedHat]: Notebook creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Attachment: Azure notebook creation.png
> [AWS][Azure][RedHat]: Notebook creation fails on process of sparkR
> installation
> ---
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.3
>
> Attachments: Azure notebook creation.png, Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio/tensorflof with rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio is created
> The bug is reproduced in develop/feature/projects/roject_tmp branches
--
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-176) [AWS][Azure][RedHat]: Notebook creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Summary: [AWS][Azure][RedHat]: Notebook creation fails on process of sparkR
installation (was: Jupyter creation fails on process of sparkR installation)
> [AWS][Azure][RedHat]: Notebook creation fails on process of sparkR
> installation
> ---
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.3
>
> Attachments: Azure notebook creation.png, Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio/tensorflof with rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio is created
> The bug is reproduced in develop/feature/projects/roject_tmp branches
--
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
[GitHub] [incubator-dlab] bohdana-kuzmenko opened a new pull request #147: Add k8s cluster status check
bohdana-kuzmenko opened a new pull request #147: Add k8s cluster status check URL: https://github.com/apache/incubator-dlab/pull/147 Add params builder This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Deleted] (DLAB-198) [Jenkins]:Create jobs for master v.2.0 [branch v.2.0.1] and develop v.2.1 [branch develop] for AWS/Azure/GCP].1
[ https://issues.apache.org/jira/browse/DLAB-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-198: --- > [Jenkins]:Create jobs for master v.2.0 [branch v.2.0.1] and develop v.2.1 > [branch develop] for AWS/Azure/GCP].1 > --- > > Key: DLAB-198 > URL: https://issues.apache.org/jira/browse/DLAB-198 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: AWS, AZURE, DevOps, GCP > > # Create jobs (create environment/terminate environment) master v.2.0 from > branch v2.0.1 for AWS, Azure, GCP in Jenkins > # Create jobs (create environment/terminate environmrnt) develop v.2.1 from > branch develop for AWS, Azure, GCP in 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] [Deleted] (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 deleted DLAB-685: --- > Implement proxy server Component > > > Key: DLAB-685 > URL: https://issues.apache.org/jira/browse/DLAB-685 > Project: Apache DLab > Issue Type: Epic >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-756) SSN on k8s
[ https://issues.apache.org/jira/browse/DLAB-756?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-756: --- Component/s: Kubernetes > SSN on k8s > -- > > Key: DLAB-756 > URL: https://issues.apache.org/jira/browse/DLAB-756 > 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-754) Project management
[ https://issues.apache.org/jira/browse/DLAB-754?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-754: --- Component/s: (was: Project) DLab Main > Project management > -- > > Key: DLAB-754 > URL: https://issues.apache.org/jira/browse/DLAB-754 > Project: Apache DLab > Issue Type: Epic > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >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-745) Introduce Edge node per project
[ https://issues.apache.org/jira/browse/DLAB-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-745: --- Component/s: (was: Project) DLab Main > Introduce Edge node per project > --- > > Key: DLAB-745 > URL: https://issues.apache.org/jira/browse/DLAB-745 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Debian, GCP, RedHat > Fix For: v.2.2 > > > As as user I want to create instance when I am assigned on a project. > Now subnet, edge are created per user during edge creation. > And user can create notebook only after his edge node creation. > Remove edge node per user and add posibility to create notebook if user is > assigned at least per one project. > Subnet, and edge node, and shared_project_bucket should be created per > project. > Shared_project_bucket is shared within this project > Shared_bucket is created on step of SSN creation. Shared_bucket is shared > between the projects. -- 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-636) [Back-end]: Ability to terminate a project for admin user
[ https://issues.apache.org/jira/browse/DLAB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-636: --- Labels: AWS Debian GCP RedHat (was: Debian) > [Back-end]: Ability to terminate a project for admin user > - > > Key: DLAB-636 > URL: https://issues.apache.org/jira/browse/DLAB-636 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Debian, GCP, RedHat > Fix For: v.2.2 > > > As an Admin I want to terminate project(s), so that I can rid of unnecessary > resources. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located in ‘Project’ tab on ‘Administration’ page > # ‘Manage project’ popup is open > > *Description:* > If Admin clicks termination icon in action column confirmation dialog appears > ‘Project name’ will be decommissioned. Do you want to proceed? > If Admin clicks ‘Yes’ a project is terminated, confirmation dialog is closed. > If Admin clicks ‘No’ a project is not terminated, confirmation dialog is > closed. > *Acceptance criteria:* > # Admin is able to terminate a project > # Terminated project is absent among the other project > # All resources are killed except for VPC (or check if any other project > exists in same VPC, if not - delete VPC) and bucket. -- 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: --- Labels: AWS Debian GCP RedHat (was: Debian GCP) > [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: DLab Main >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: AWS, Debian, GCP, RedHat > 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-636) [Back-end]: Ability to terminate a project for admin user
[ https://issues.apache.org/jira/browse/DLAB-636?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-636: --- Component/s: (was: Project) DLab Main > [Back-end]: Ability to terminate a project for admin user > - > > Key: DLAB-636 > URL: https://issues.apache.org/jira/browse/DLAB-636 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Debian > Fix For: v.2.2 > > > As an Admin I want to terminate project(s), so that I can rid of unnecessary > resources. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located in ‘Project’ tab on ‘Administration’ page > # ‘Manage project’ popup is open > > *Description:* > If Admin clicks termination icon in action column confirmation dialog appears > ‘Project name’ will be decommissioned. Do you want to proceed? > If Admin clicks ‘Yes’ a project is terminated, confirmation dialog is closed. > If Admin clicks ‘No’ a project is not terminated, confirmation dialog is > closed. > *Acceptance criteria:* > # Admin is able to terminate a project > # Terminated project is absent among the other project > # All resources are killed except for VPC (or check if any other project > exists in same VPC, if not - delete VPC) and bucket. -- 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: AWS Debian GCP RedHat (was: Debian GCP) > [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: DLab Main >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: AWS, Debian, GCP, RedHat > 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. > # 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 -- 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: --- Component/s: DLab Main > [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: DLab Main >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, GCP > 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: --- Component/s: (was: 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 >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, GCP > 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-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: --- Component/s: (was: Project) DLab Main > [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: DLab Main >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, GCP > 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. > # 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 -- 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-863) Add GIT plugin to JupyterLab
Vira Vitanska created DLAB-863: -- Summary: Add GIT plugin to JupyterLab Key: DLAB-863 URL: https://issues.apache.org/jira/browse/DLAB-863 Project: Apache DLab Issue Type: Task Components: Legion Reporter: Vira Vitanska Assignee: Kirill Makhonin Fix For: v.2.2 As a user of JupyterLab interface, I want to have an easy access to GIT repository, including pull, push, commit actions. -- 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] [Commented] (DLAB-830) [Project status]: Convey project status to FE
[ https://issues.apache.org/jira/browse/DLAB-830?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881188#comment-16881188 ] Vira Vitanska commented on DLAB-830: Closed: Commit ID 36680a6952375045d13b42a406f14ce0a616b00c > [Project status]: Convey project status to FE > - > > Key: DLAB-830 > URL: https://issues.apache.org/jira/browse/DLAB-830 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > > Convey project status: > - creating > - active > - failed > - terminating > - terminated > - stopped - not active > - stopping -- 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-830) [Project status]: Convey project status to FE
[ https://issues.apache.org/jira/browse/DLAB-830?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-830: --- Description: Convey project status: - creating - active - failed - terminating - terminated - stopped - not active - stopping was: Convey project status: - creating - active - failed - terminating - terminated - stopped - stopping > [Project status]: Convey project status to FE > - > > Key: DLAB-830 > URL: https://issues.apache.org/jira/browse/DLAB-830 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > > Convey project status: > - creating > - active > - failed > - terminating > - terminated > - stopped - not active > - stopping -- 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] [Commented] (DLAB-805) Adopt cluster creation for new back-end API
[ https://issues.apache.org/jira/browse/DLAB-805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881184#comment-16881184 ] Vira Vitanska commented on DLAB-805: Closed: Commit ID 36680a6952375045d13b42a406f14ce0a616b00c > Adopt cluster creation for new back-end API > --- > > Key: DLAB-805 > URL: https://issues.apache.org/jira/browse/DLAB-805 > Project: Apache DLab > Issue Type: Task >Reporter: Dmytro Liaskovskyi >Assignee: Andriana Kovalyshyn >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] [Created] (DLAB-862) EMR creation fails on process of uploading user key
Vira Vitanska created DLAB-862: -- Summary: EMR creation fails on process of uploading user key Key: DLAB-862 URL: https://issues.apache.org/jira/browse/DLAB-862 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Mykola Fix For: v.2.2 Attachments: EMR creation.png *Preconditions:* 1. Jupyter/rsudio/zeppelin is created *Steps to reproduce:* 1. Create EMR with valid data Actual result: EMR creation fails on process of uploading user key *Expected result:* EMR creation is successful -- 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] [Commented] (DLAB-856) [AWS]: User can not create Data Engine Service
[ https://issues.apache.org/jira/browse/DLAB-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881179#comment-16881179 ] Vira Vitanska commented on DLAB-856: Closed: Commit ID 36680a6952375045d13b42a406f14ce0a616b00c > [AWS]: User can not create Data Engine Service > -- > > Key: DLAB-856 > URL: https://issues.apache.org/jira/browse/DLAB-856 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AWS >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Back-end, Debian, RedHat > Fix For: v.2.2 > > > *Preconditions:* > 1. Notebook (Zeppelin/Rstudio or Jupyter) is created > 2. EMR popup creation is open > *Steps to reproduce:* > 1. Put valid data for EMR creation > 2. Click 'Create' button > *Actual result:* > EMR creation popup is not closed > EMR is not created > *Expected Result:* > EMR creation popup is closed > EMR is created -- 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] [Commented] (DLAB-840) User is not allowed to create computational resources
[ https://issues.apache.org/jira/browse/DLAB-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881178#comment-16881178 ] Vira Vitanska commented on DLAB-840: Closed: Commit ID 36680a6952375045d13b42a406f14ce0a616b00c > User is not allowed to create computational resources > - > > Key: DLAB-840 > URL: https://issues.apache.org/jira/browse/DLAB-840 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > > *Preconditions:* > 1. Notebook is created for user1 > 2. User1 has permission for computational resources creation > 3. User1 is located on 'Resources list' page > *Steps to reproduce:* > 1. Click action menu for neotebook > 2. Choose 'Add compute' > *Actual result:* > 1. Message appears : 'Computational resource creations are not available. > Please, check your permissions.' > 2. It is not allowed to create computational resources > *Expected result:* > It is allowed to create computational resources -- 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
[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #146: Skip empty values
OlehMartushevskyi merged pull request #146: Skip empty values URL: https://github.com/apache/incubator-dlab/pull/146 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] bohdana-kuzmenko opened a new pull request #146: Skip empty values
bohdana-kuzmenko opened a new pull request #146: Skip empty values URL: https://github.com/apache/incubator-dlab/pull/146 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #145: Add auto-approve
OlehMartushevskyi merged pull request #145: Add auto-approve URL: https://github.com/apache/incubator-dlab/pull/145 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] bohdana-kuzmenko opened a new pull request #145: Add auto-approve
bohdana-kuzmenko opened a new pull request #145: Add auto-approve URL: https://github.com/apache/incubator-dlab/pull/145 Update args string builder This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] bohdana-kuzmenko opened a new pull request #144: Move target
bohdana-kuzmenko opened a new pull request #144: Move target URL: https://github.com/apache/incubator-dlab/pull/144 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #144: Move target
OlehMartushevskyi merged pull request #144: Move target URL: https://github.com/apache/incubator-dlab/pull/144 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #143: Dlab terraform cli
OlehMartushevskyi merged pull request #143: Dlab terraform cli URL: https://github.com/apache/incubator-dlab/pull/143 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] bohdana-kuzmenko opened a new pull request #143: Dlab terraform cli
bohdana-kuzmenko opened a new pull request #143: Dlab terraform cli URL: https://github.com/apache/incubator-dlab/pull/143 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #142: Replace positional args with optional
OlehMartushevskyi merged pull request #142: Replace positional args with optional URL: https://github.com/apache/incubator-dlab/pull/142 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] bohdana-kuzmenko opened a new pull request #142: Replace positional args with optional
bohdana-kuzmenko opened a new pull request #142: Replace positional args with optional URL: https://github.com/apache/incubator-dlab/pull/142 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-745) Introduce Edge node per project
[ https://issues.apache.org/jira/browse/DLAB-745?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881119#comment-16881119 ] Vira Vitanska commented on DLAB-745: Closed: Commit ID 36680a6952375045d13b42a406f14ce0a616b00c > Introduce Edge node per project > --- > > Key: DLAB-745 > URL: https://issues.apache.org/jira/browse/DLAB-745 > Project: Apache DLab > Issue Type: Task > Components: Project >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Debian, GCP, RedHat > Fix For: v.2.2 > > > As as user I want to create instance when I am assigned on a project. > Now subnet, edge are created per user during edge creation. > And user can create notebook only after his edge node creation. > Remove edge node per user and add posibility to create notebook if user is > assigned at least per one project. > Subnet, and edge node, and shared_project_bucket should be created per > project. > Shared_project_bucket is shared within this project > Shared_bucket is created on step of SSN creation. Shared_bucket is shared > between the projects. -- 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-745) Introduce Edge node per project
[ https://issues.apache.org/jira/browse/DLAB-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-745: --- Labels: AWS Debian GCP RedHat (was: AWS AZURE Debian GCP RedHat) > Introduce Edge node per project > --- > > Key: DLAB-745 > URL: https://issues.apache.org/jira/browse/DLAB-745 > Project: Apache DLab > Issue Type: Task > Components: Project >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Debian, GCP, RedHat > Fix For: v.2.2 > > > As as user I want to create instance when I am assigned on a project. > Now subnet, edge are created per user during edge creation. > And user can create notebook only after his edge node creation. > Remove edge node per user and add posibility to create notebook if user is > assigned at least per one project. > Subnet, and edge node, and shared_project_bucket should be created per > project. > Shared_project_bucket is shared within this project > Shared_bucket is created on step of SSN creation. Shared_bucket is shared > between the projects. -- 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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Description:
*Preconditions:*
Edge/project is created
*Steps to reproduce:*
1. create jupyter/zeppelin/rstudio/tensorflof with rstudio notebook
*Actual result:*
Jupyter/zeppelin/rstudio/tensorflof with rstudio creation fails wit error:
*Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
*Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
/usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
*Expected result:*
Jupyter/zeppelin/rstudio/tensorflof with rstudio is created
The bug is reproduced in develop/feature/projects/roject_tmp branches
was:
*Preconditions:*
Edge/project is created
*Steps to reproduce:*
1. create jupyter/zeppelin/rstudio notebook
*Actual result:*
Jupyter/zeppelin/rstudio creation fails wit error:
*Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
*Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
/usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
*Expected result:*
Jupyter/zeppelin/rstudio is created
The bug is reproduced in develop/feature/projects/roject_tmp branches
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.3
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio/tensorflof with rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio/tensorflof with rstudio is created
> The bug is reproduced in develop/feature/projects/roject_tmp branches
--
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] [Commented] (DLAB-853) Adding/removing group from project should not change project status
[ https://issues.apache.org/jira/browse/DLAB-853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16881108#comment-16881108 ] Vira Vitanska commented on DLAB-853: Closed: Commit id 36680a6952375045d13b42a406f14ce0a616b00c > Adding/removing group from project should not change project status > --- > > Key: DLAB-853 > URL: https://issues.apache.org/jira/browse/DLAB-853 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > > *Preconditions:* > 1. Project is created > 2. Admin is located on 'project' page > *Steps to reproduce:* > 1. Click edit action for project > 2. Add or remove group > 3. Click update > *Actual result:* > Project status changes from 'Active' to 'Creating' > *Expected result:* > Project status does not changed -- 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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Description:
*Preconditions:*
Edge/project is created
*Steps to reproduce:*
1. create jupyter/zeppelin/rstudio notebook
*Actual result:*
Jupyter/zeppelin/rstudio creation fails wit error:
*Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
*Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
/usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
*Expected result:*
Jupyter/zeppelin/rstudio is created
The bug is reproduced in develop/feature/projects/roject_tmp branches
was:
*Preconditions:*
Edge/project is created
*Steps to reproduce:*
1. create jupyter/zeppelin/rstudio notebook
*Actual result:*
Jupyter/zeppelin/rstudio creation fails wit error:
*Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
*Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
/usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
*Expected result:*
Jupyter/zeppelin/rstudio is created
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.3
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio is created
> The bug is reproduced in develop/feature/projects/roject_tmp branches
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Fix Version/s: (was: v.2.1)
v.2.3
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.3
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio is created
>
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleh Martushevskyi updated DLAB-176:
Sprint: Apache DLab release 2.1, Apache DLab release 2.2 (was: Apache DLab
release 2.1)
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.1
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio is created
>
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Labels: AWS DevOps RedHat (was: AWS AZURE DevOps GCP RedHat)
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.1
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio is created
>
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Component/s: (was: DLab Old)
DLab Main
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, DevOps, RedHat
> Fix For: v.2.1
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio is created
>
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Description:
*Preconditions:*
Edge/project is created
*Steps to reproduce:*
1. create jupyter/zeppelin/rstudio notebook
*Actual result:*
Jupyter/zeppelin/rstudio creation fails wit error:
*Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
*Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
/usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
*Expected result:*
Jupyter/zeppelin/rstudio is created
was:
*Preconditions:*
Edge is created
*Steps to reproduce:*
1. create jupyter notebook
*Actual result:*
Jupyter creation fails wit error:
*Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
*Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
/usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
*Expected result:*
Jupyter is created
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, AZURE, DevOps, GCP, RedHat
> Fix For: v.2.1
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio is created
>
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Attachment: Notebook creation.png
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, AZURE, DevOps, GCP, RedHat
> Fix For: v.2.1
>
> Attachments: Notebook creation.png
>
>
> *Preconditions:*
> Edge/project is created
> *Steps to reproduce:*
> 1. create jupyter/zeppelin/rstudio notebook
> *Actual result:*
> Jupyter/zeppelin/rstudio creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
> *Expected result:*
> Jupyter/zeppelin/rstudio is created
>
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska reassigned DLAB-176:
--
Assignee: Oleh Martushevskyi (was: Oleksandr Isniuk)
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Critical
> Labels: AWS, AZURE, DevOps, GCP, RedHat
> Fix For: v.2.1
>
>
> *Preconditions:*
> Edge is created
>
> *Steps to reproduce:*
> 1. create jupyter notebook
>
> *Actual result:*
> Jupyter creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
>
> *Expected result:*
> Jupyter is created
>
--
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-176) Jupyter creation fails on process of sparkR installation
[
https://issues.apache.org/jira/browse/DLAB-176?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-176:
---
Labels: AWS AZURE DevOps GCP RedHat (was: AWS AZURE Debian DevOps GCP
RedHat)
> Jupyter creation fails on process of sparkR installation
>
>
> Key: DLAB-176
> URL: https://issues.apache.org/jira/browse/DLAB-176
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Oleksandr Isniuk
>Priority: Critical
> Labels: AWS, AZURE, DevOps, GCP, RedHat
> Fix For: v.2.1
>
>
> *Preconditions:*
> Edge is created
>
> *Steps to reproduce:*
> 1. create jupyter notebook
>
> *Actual result:*
> Jupyter creation fails wit error:
> *Requested: cd /usr/local/spark/R/lib/SparkR; R -e "devtools::install('.')"*
> *Executed: sudo -S -p 'sudo password:' /bin/bash -l -c "cd
> /usr/local/spark/R/li b/SparkR; R -e \"devtools::install('.')\""*
>
> *Expected result:*
> Jupyter is created
>
--
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
[GitHub] [incubator-dlab] OlehMartushevskyi merged pull request #141: Dlab terraform cli
OlehMartushevskyi merged pull request #141: Dlab terraform cli URL: https://github.com/apache/incubator-dlab/pull/141 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-861) Investigate K8S network policies
Vira Vitanska created DLAB-861: -- Summary: Investigate K8S network policies Key: DLAB-861 URL: https://issues.apache.org/jira/browse/DLAB-861 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi -- 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-860) Automate keycloak configuration
Vira Vitanska created DLAB-860: -- Summary: Automate keycloak configuration Key: DLAB-860 URL: https://issues.apache.org/jira/browse/DLAB-860 Project: Apache DLab Issue Type: Task Components: DLab Main 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] [Created] (DLAB-859) Python wrapper for terraform
Vira Vitanska created DLAB-859: -- Summary: Python wrapper for terraform Key: DLAB-859 URL: https://issues.apache.org/jira/browse/DLAB-859 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Bohdana Kuzmenko 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
RE: [MENTORS]: DLab PMC report timeline for July 2019
Hi Mentors, Sorry for writing to you, however we need your help with Dlab Podling report signing. DLab Mentors or the other Mentors, could you sign off DLab Podling report for July if you have free time? https://cwiki.apache.org/confluence/display/INCUBATOR/July2019 Thanks in advance. Best regards, Vira Vitanska -Original Message- From: Justin Mclean Sent: Thursday, July 4, 2019 12:55 PM To: dev@dlab.apache.org Subject: Re: [MENTORS]: DLab PMC report timeline for July 2019 Hi, I can see you you did have reports for both June and July proposed on list but they were not submitted, and while that's not the mentors job to submit them, it also looks like that some of your mentors may not be paying attention. If so be sure to include that in your report in the relevant section and/or ask your mentors if they can continue to help you and/or ask for some more mentors on the general@incubator list. Thanks, Justin - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
