[jira] [Deleted] (DLAB-95) Front-end
[ https://issues.apache.org/jira/browse/DLAB-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-95: -- > Front-end > - > > Key: DLAB-95 > URL: https://issues.apache.org/jira/browse/DLAB-95 > Project: Apache DLab > Issue Type: Sub-task >Reporter: Vira Vitanska >Priority: Major > Labels: Front-end > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1516) [Project creation][AWS]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1516: Summary: [Project creation][AWS]: Subnet search should be by CIDR according to VPC (was: [AWS]: Data Engine/ Data Engine Service creation fail only on endpoint) > [Project creation][AWS]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, SG from > logs DE.png, Subnet from logs DE.png > > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1516) [Project creation][AWS]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1516: --- Assignee: Mykola Bodnar (was: Oleh Martushevskyi) > [Project creation][AWS]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, SG from > logs DE.png, Subnet from logs DE.png > > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1516) [AWS][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1516: Summary: [AWS][Project creation]: Subnet search should be by CIDR according to VPC (was: [Project creation][AWS]: Subnet search should be by CIDR according to VPC) > [AWS][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, SG from > logs DE.png, Subnet from logs DE.png > > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1515) Investigate why some templates disappear after endpoint/SSN stopping only for remote GCP endpoint
[ https://issues.apache.org/jira/browse/DLAB-1515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031387#comment-17031387 ] Vira Vitanska commented on DLAB-1515: - The bug is still reproduced on GCP remote endpoint. Reopened: Commit ID c714a53bce1adace749a9821ba706e3bf3d1a093 > Investigate why some templates disappear after endpoint/SSN stopping only for > remote GCP endpoint > - > > Key: DLAB-1515 > URL: https://issues.apache.org/jira/browse/DLAB-1515 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Templates.png > > > *Preconditions:* > # SSN is created on AWS > # Externel endpoint is created on GCP > # One project has edge node on AWS (Local) the other edge on GCP (external > endpoint) > # All instances including SSN are stopped > *Steps to reproduces:* > # Start SSN > # Start endpoint > # Change status endpoint in Mongo > # Start edge node > # Look available template for external endpoint on GCP > *Actual result:* > # Jupyter is available > # RStuduo is available > # Deeplearning is available > # Zeppelin is not available > # Superset is not available > # JupyterLab is not available > # Jupyter with TensorFlow is not available > *Expected result:* > # Jupyter is available > # RStuduo is available > # Deeplearning is available > # Zeppelin is available > # Superset is available > # JupyterLab is available > # Jupyter with TensorFlow is available > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1506) [List of resources]: Endpoint disconnection should not cause disappearing previously available instance
[ https://issues.apache.org/jira/browse/DLAB-1506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031474#comment-17031474 ] Vira Vitanska commented on DLAB-1506: - Closed: Commit ID 74991cc6352e9e55a020c1d0fe1f85344ce2d67b > [List of resources]: Endpoint disconnection should not cause disappearing > previously available instance > --- > > Key: DLAB-1506 > URL: https://issues.apache.org/jira/browse/DLAB-1506 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, Azure, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: List of resources.png > > > *Preconditions:* > # SSN is created in AWS > # External endpoint is created on GCP > # One project is created for two clouds > # notebooks are created for each cloud > *Steps to reproduce:* > # Go to 'Mange environment' popup > # Click 'Endpoints' button > # Click disconnect external endpoint with resources termination > # Go to list of resource > *Actual result:* > 1. Any notebooks are not available in list of resource > *Expected result:* > 1. All notebooks are not available in list of resource > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1507) [List of resources]: Endpoint disconnection should not cause disappearing previously available instance
[ https://issues.apache.org/jira/browse/DLAB-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17031473#comment-17031473 ] Vira Vitanska commented on DLAB-1507: - Closed: Commit ID 74991cc6352e9e55a020c1d0fe1f85344ce2d67b > [List of resources]: Endpoint disconnection should not cause disappearing > previously available instance > --- > > Key: DLAB-1507 > URL: https://issues.apache.org/jira/browse/DLAB-1507 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, Azure, Debian, Front-end, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: List of resources.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created in AWS > # External endpoint is created on GCP > # One project is created for two clouds > # notebooks are created for each cloud > *Steps to reproduce:* > # Go to 'Mange environment' popup > # Click 'Endpoints' button > # Click disconnect external endpoint with resources termination > # Go to list of resource > *Actual result:* > 1. Any notebooks are not available in list of resource > *Expected result:* > 1. All notebooks are not available in list of resource > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1525) Convey instance price by shape per hour for user
Vira Vitanska created DLAB-1525: --- Summary: Convey instance price by shape per hour for user Key: DLAB-1525 URL: https://issues.apache.org/jira/browse/DLAB-1525 Project: Apache DLab Issue Type: Improvement Components: DLab Main Reporter: Vira Vitanska -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1526) Alter Jenkins job according to the second endpoint creation for the same SSN and cloud
Vira Vitanska created DLAB-1526: --- Summary: Alter Jenkins job according to the second endpoint creation for the same SSN and cloud Key: DLAB-1526 URL: https://issues.apache.org/jira/browse/DLAB-1526 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 *Preconditions:* # SSN is created on AWS # Remote endpoint1 is created on GCP *Steps to reproduce:* # Create remote endpoint2 on GCP from Jenkins job *Actual result:* # Remote endpoint1 is deleted on GCP # Remore endpoint2 creation fails on GCP *Expected result:* 1. Remote endpoint1 is still available on GCP 2. Remore endpoint2 creation is successful on GCP Ponder if it is cloud related? Will the same situation be on Azure/AWS during the second endpoint creation? If yes, then fix that on all clouds. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1527) Rarely notebook is not created successful from the first attempt
Vira Vitanska created DLAB-1527: --- Summary: Rarely notebook is not created successful from the first attempt Key: DLAB-1527 URL: https://issues.apache.org/jira/browse/DLAB-1527 Project: Apache DLab Issue Type: Bug Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 Attachments: Azure Jupyter.png, Azure zeppelin.png, GCP DeepLearning.png This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter (Azure)/DeepLearning (GCP) during auto-test. The second attempt was successful by manually creation. *Preconditions:* 1. SSN is created on Azure *Steps to reproduce:* 1. Create Jupyter *Actual result:* Jupyter creation fails: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) *Expected result:* Jupyter creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1528) Computational resources should also contain endpoint name
Vira Vitanska created DLAB-1528: --- Summary: Computational resources should also contain endpoint name Key: DLAB-1528 URL: https://issues.apache.org/jira/browse/DLAB-1528 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 Also take into consideration cloud name limitation. Maybe we should limit endpoint name. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1529) [Billing report page]: Remove extra horizontal line
Vira Vitanska created DLAB-1529: --- Summary: [Billing report page]: Remove extra horizontal line Key: DLAB-1529 URL: https://issues.apache.org/jira/browse/DLAB-1529 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Attachments: Billing.png -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1529) [Billing report page]: Remove extra horizontal lines
[ https://issues.apache.org/jira/browse/DLAB-1529?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1529: Summary: [Billing report page]: Remove extra horizontal lines (was: [Billing report page]: Remove extra horizontal line) > [Billing report page]: Remove extra horizontal lines > > > Key: DLAB-1529 > URL: https://issues.apache.org/jira/browse/DLAB-1529 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Billing.png > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1530) [AWS]: Endpoint_tag is not added to EMR
Vira Vitanska created DLAB-1530: --- Summary: [AWS]: Endpoint_tag is not added to EMR Key: DLAB-1530 URL: https://issues.apache.org/jira/browse/DLAB-1530 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Attachments: EMR1.png, EMR2.png, Spark cluster.png *Preconditions:* 1. EMR is created *Steps to reproduce:* 1. Go to EMR console *Actual result:* 1. Endpoint_tag is absent *Expected result:* 1. Endpoint_tag is present -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1527) Rarely notebook is not created successful from the first attempt
[ https://issues.apache.org/jira/browse/DLAB-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1527: Attachment: Azure TensorFlow.png > Rarely notebook is not created successful from the first attempt > > > Key: DLAB-1527 > URL: https://issues.apache.org/jira/browse/DLAB-1527 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Minor > Labels: AZURE, Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: Azure Jupyter.png, Azure TensorFlow.png, Azure > zeppelin.png, GCP DeepLearning.png > > > This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter > (Azure)/DeepLearning (GCP) during auto-test. The second attempt was > successful by manually creation. > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create Jupyter > *Actual result:* > Jupyter creation fails: > Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource > temporarily unavailable) > *Expected result:* > Jupyter creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1476) Implement demo-regime in marketplace
[ https://issues.apache.org/jira/browse/DLAB-1476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1476: Summary: Implement demo-regime in marketplace (was: Implement demo environment in marketplace) > Implement demo-regime in marketplace > > > Key: DLAB-1476 > URL: https://issues.apache.org/jira/browse/DLAB-1476 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: Back-end, Debian, GCP > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1509) Remove actions from quota popup
[ https://issues.apache.org/jira/browse/DLAB-1509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033459#comment-17033459 ] Vira Vitanska commented on DLAB-1509: - Closed: Commit ID 8f13d950b9e379dd952a4f13b38a2ec033acad9f > Remove actions from quota popup > --- > > Key: DLAB-1509 > URL: https://issues.apache.org/jira/browse/DLAB-1509 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Time Spent: 20m > Remaining Estimate: 0h > > # Change 'Manage environment' -> 'Manage DLab quotas' on popup and button name > # Remove stop/terminate action from popup. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1527) Rarely notebook is not created successful from the first attempt
[ https://issues.apache.org/jira/browse/DLAB-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1527: Description: This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter (Azure)/DeepLearning (GCP)/TenzorFlow (Azure) during auto-test. The second attempt was successful by manually creation. *Preconditions:* 1. SSN is created on Azure *Steps to reproduce:* 1. Create Jupyter *Actual result:* Jupyter creation fails: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) *Expected result:* Jupyter creation is successful was: This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter (Azure)/DeepLearning (GCP) during auto-test. The second attempt was successful by manually creation. *Preconditions:* 1. SSN is created on Azure *Steps to reproduce:* 1. Create Jupyter *Actual result:* Jupyter creation fails: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) *Expected result:* Jupyter creation is successful > Rarely notebook is not created successful from the first attempt > > > Key: DLAB-1527 > URL: https://issues.apache.org/jira/browse/DLAB-1527 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Minor > Labels: AZURE, Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: Azure Jupyter.png, Azure TensorFlow.png, Azure > zeppelin.png, GCP DeepLearning.png > > > This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter > (Azure)/DeepLearning (GCP)/TenzorFlow (Azure) during auto-test. The second > attempt was successful by manually creation. > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create Jupyter > *Actual result:* > Jupyter creation fails: > Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource > temporarily unavailable) > *Expected result:* > Jupyter creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1513) [Libary management]: 'Formatted exploratory name ' request should not be repetitive in list of resources page
[ https://issues.apache.org/jira/browse/DLAB-1513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033492#comment-17033492 ] Vira Vitanska commented on DLAB-1513: - Closed: Commit ID 8f13d950b9e379dd952a4f13b38a2ec033acad9f > [Libary management]: 'Formatted exploratory name ' request should not be > repetitive in list of resources page > - > > Key: DLAB-1513 > URL: https://issues.apache.org/jira/browse/DLAB-1513 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Buttons.png, Library management.png > > Time Spent: 20m > Remaining Estimate: 0h > > This bug reproduces for local and external endpoints > *Preconditions:* > # SSN is created in multiple cloud > # notebook is created > *Steps to reproduce:* > 1. Install any kind of libs for notebook > *Actual result:* > 'Formatted exploratory name ' request is duplicated on list of resources page > *Expected result:* > 'Formatted exploratory name ' request is not on list of resources page > > This request should appear if open 'Manage libraries' popup > > Display 'Close'/'Install' buttons lower. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1499) Noteboks/links are not loaded successfully if project contains more than one edge
[ https://issues.apache.org/jira/browse/DLAB-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1499: Attachment: Reopened redirect_uri.mp4 > Noteboks/links are not loaded successfully if project contains more than one > edge > - > > Key: DLAB-1499 > URL: https://issues.apache.org/jira/browse/DLAB-1499 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Links.png, Reopened redirect_uri.mp4 > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on AWS > # External endpoint is created on GCP > # Notebook1/cluster1 are created on GCP external endpoint > # Notebook2/cluster2 are created on AWs external endpoint > *Steps to reproduce:* > # Refer the notebook1/cluster1 link > # Refer the notebook2/cluster2 link > # > *Actual result:* > 1. Links for one notebook/cluster are loaded successfully > 2. Links for the other notebook/cluster are not loaded successfully > *Expected result:* > 1. All notebook/cluster links are loaded successfully > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1499) Noteboks/links are not loaded successfully if project contains more than one edge
[ https://issues.apache.org/jira/browse/DLAB-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1499: Attachment: Double-redirect.mp4 > Noteboks/links are not loaded successfully if project contains more than one > edge > - > > Key: DLAB-1499 > URL: https://issues.apache.org/jira/browse/DLAB-1499 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Double-redirect.mp4, Links.png, Reopened redirect_uri.mp4 > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on AWS > # External endpoint is created on GCP > # Notebook1/cluster1 are created on GCP external endpoint > # Notebook2/cluster2 are created on AWs external endpoint > *Steps to reproduce:* > # Refer the notebook1/cluster1 link > # Refer the notebook2/cluster2 link > # > *Actual result:* > 1. Links for one notebook/cluster are loaded successfully > 2. Links for the other notebook/cluster are not loaded successfully > *Expected result:* > 1. All notebook/cluster links are loaded successfully > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1499) Noteboks/links are not loaded successfully if project contains more than one edge
[ https://issues.apache.org/jira/browse/DLAB-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17033514#comment-17033514 ] Vira Vitanska commented on DLAB-1499: - *Reopened:* It is still reproduced. Watch video in attachment 'Reopened redirect_uri' *Preconditions:* # SSN is created on GCP # Remote endpoint2 is created on AWS # Local endpoint1 is created on GCP # Jupyter1 is created in Project1 for endpoint1 # Jupyter2 is created in Project1 for endpoint2 *Steps to reproduce:* # Go to links of Jupyer1 # Go to links of Jupyer2 *Actual result:* 1. Links of Jupyer1 are opened successful 2. Links of Jupyer2 are not opened successful *Expected result:* 1. Links of Jupyer1 are opened successful 2. Links of Jupyer2 are opened successful (!) In scope of this task please fix another issue - double redirect for AWS, however links are open successful. Watch video in attachment 'Double redirect' *Preconditions:* # SSN is created on AWS # Remote endpoint2 is created on GCP # Local endpoint1 is created on AWS # Rstudio1 is created in Project1 for endpoint1 # Rstudio2 is created in Project1 for endpoint2 *Steps to reproduce:* # Go to links of Rstudio1 # Go to links of Rstudio2 *Actual result:* 1. Links of Rstudio1 are opened successful, but with double redirect 2. Links of Rstudio2 are not opened successful without double redirect *Expected result:* 1. Links of Rstudio1 are opened successful without double redirect 2. Links of Rstudio2 are opened successful without double redirect > Noteboks/links are not loaded successfully if project contains more than one > edge > - > > Key: DLAB-1499 > URL: https://issues.apache.org/jira/browse/DLAB-1499 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Double-redirect.mp4, Links.png, Reopened redirect_uri.mp4 > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on AWS > # External endpoint is created on GCP > # Notebook1/cluster1 are created on GCP external endpoint > # Notebook2/cluster2 are created on AWs external endpoint > *Steps to reproduce:* > # Refer the notebook1/cluster1 link > # Refer the notebook2/cluster2 link > # > *Actual result:* > 1. Links for one notebook/cluster are loaded successfully > 2. Links for the other notebook/cluster are not loaded successfully > *Expected result:* > 1. All notebook/cluster links are loaded successfully > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1531) Bucket should be tagged according to template
Vira Vitanska created DLAB-1531: --- Summary: Bucket should be tagged according to template Key: DLAB-1531 URL: https://issues.apache.org/jira/browse/DLAB-1531 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 Attachments: AWS project bucket.png, AWS shared endpoint bucket.png, Azure Project bucket.png, Azure shared endpoint bucket.png, GCP.png, GCP2.png, GCP3.png (!) *AWS@Mention someone by typing their name...* # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as it has 'Project bucket' (!) *Azure* # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as it has 'Project bucket' (!) *GCP* # All buckets should contain endpoint_tag, product, name, ???sbn???. # What does 'vi-aws-10...' tag mean. Do we need it? # In addition 'Project bucket' should contain project_tag. About GCP consult with [~omartushevskyi] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1531) Bucket should be tagged according to template
[ https://issues.apache.org/jira/browse/DLAB-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1531: Description: (!) *AWS* # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as it has 'Project bucket' (!) *Azure* # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as it has 'Project bucket' (!) *GCP* # All buckets should contain endpoint_tag, product, name, ???sbn???. # What does 'vi-aws-10...' tag mean. Do we need it? # In addition 'Project bucket' should contain project_tag. About GCP consult with [~omartushevskyi] was: (!) *AWS@Mention someone by typing their name...* # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as it has 'Project bucket' (!) *Azure* # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as it has 'Project bucket' (!) *GCP* # All buckets should contain endpoint_tag, product, name, ???sbn???. # What does 'vi-aws-10...' tag mean. Do we need it? # In addition 'Project bucket' should contain project_tag. About GCP consult with [~omartushevskyi] > Bucket should be tagged according to template > - > > Key: DLAB-1531 > URL: https://issues.apache.org/jira/browse/DLAB-1531 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Minor > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: AWS project bucket.png, AWS shared endpoint bucket.png, > Azure Project bucket.png, Azure shared endpoint bucket.png, GCP.png, > GCP2.png, GCP3.png > > > (!) *AWS* > # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as > it has 'Project bucket' > > (!) *Azure* > # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as > it has 'Project bucket' > > (!) *GCP* > # All buckets should contain endpoint_tag, product, name, ???sbn???. > # What does 'vi-aws-10...' tag mean. Do we need it? > # In addition 'Project bucket' should contain project_tag. > About GCP consult with [~omartushevskyi] -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1531) Bucket should be tagged according to template
[
https://issues.apache.org/jira/browse/DLAB-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1531:
Description:
(!) *AWS*
# [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as
it has 'Project bucket'
(!) *Azure*
# [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as it
has 'Project bucket'
(!) *GCP*
# All buckets should contain endpoint_tag, product, name,
{color:#de350b}*?sbn?*{color}
# What does 'vi-aws-10...' tag mean. Do we need it?
# In addition 'Project bucket' should contain project_tag.
About GCP consult with [~omartushevskyi]
was:
(!) *AWS*
# [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as
it has 'Project bucket'
(!) *Azure*
# [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as it
has 'Project bucket'
(!) *GCP*
# All buckets should contain endpoint_tag, product, name, ???sbn???.
# What does 'vi-aws-10...' tag mean. Do we need it?
# In addition 'Project bucket' should contain project_tag.
About GCP consult with [~omartushevskyi]
> Bucket should be tagged according to template
> -
>
> Key: DLAB-1531
> URL: https://issues.apache.org/jira/browse/DLAB-1531
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Leonid Frolov
>Priority: Minor
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat
> Fix For: v.2.3
>
> Attachments: AWS project bucket.png, AWS shared endpoint bucket.png,
> Azure Project bucket.png, Azure shared endpoint bucket.png, GCP.png,
> GCP2.png, GCP3.png
>
>
> (!) *AWS*
> # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *Azure*
> # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *GCP*
> # All buckets should contain endpoint_tag, product, name,
> {color:#de350b}*?sbn?*{color}
> # What does 'vi-aws-10...' tag mean. Do we need it?
> # In addition 'Project bucket' should contain project_tag.
> About GCP consult with [~omartushevskyi]
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1532) [Azure]: Add endpoint name to container
Vira Vitanska created DLAB-1532: --- Summary: [Azure]: Add endpoint name to container Key: DLAB-1532 URL: https://issues.apache.org/jira/browse/DLAB-1532 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 Attachments: AWS example.png, Azure.png -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1532) [Azure]: Add endpoint name to container
[ https://issues.apache.org/jira/browse/DLAB-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1532: Description: In Azure bucket consists of account and container. Add endpoint name to container. Now we have: # sbn-project_name-container # sbn-shared-container But should be: # sbn-project_name-endpoint_name-container # sbn-endpoint_name-shared-container > [Azure]: Add endpoint name to container > --- > > Key: DLAB-1532 > URL: https://issues.apache.org/jira/browse/DLAB-1532 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Minor > Labels: Azure, Debian, DevOps, RedHat > Fix For: v.2.3 > > Attachments: AWS example.png, Azure.png > > > In Azure bucket consists of account and container. > Add endpoint name to container. > Now we have: > # sbn-project_name-container > # sbn-shared-container > But should be: > # sbn-project_name-endpoint_name-container > # sbn-endpoint_name-shared-container -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1533) [List of resource]: Notebook is not convey to DLab UI in Microsoft Edge browser
Vira Vitanska created DLAB-1533: --- Summary: [List of resource]: Notebook is not convey to DLab UI in Microsoft Edge browser Key: DLAB-1533 URL: https://issues.apache.org/jira/browse/DLAB-1533 Project: Apache DLab Issue Type: Bug Components: DLab Main Environment: Microsoft Edge 44.18362.387.0 Microsoft EdgeHTML 18.18362 Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 *Preconditions:* 1. Notebook is created by user1 Steps to reproduce: 1. Login by user1 in Microsoft Edge browser *Actual result:* 1. Notebook1 is not in List of resource page *Expected result:* 1. Notebook1 is in List of resource page -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1534) Add possibility to choose the same endpoint after edge termination
Vira Vitanska created DLAB-1534: --- Summary: Add possibility to choose the same endpoint after edge termination Key: DLAB-1534 URL: https://issues.apache.org/jira/browse/DLAB-1534 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Do it i separate branch for testing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1535) [Billing report]: The same project should not be portrayed as two projects if contains upper case
Vira Vitanska created DLAB-1535: --- Summary: [Billing report]: The same project should not be portrayed as two projects if contains upper case Key: DLAB-1535 URL: https://issues.apache.org/jira/browse/DLAB-1535 Project: Apache DLab Issue Type: Task Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 If project name contains upper case in billing report page appears two different projects (see attachment) It should be fixed in develop and internal release branch. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Description: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 was: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # If project name contains upper case in billing report page appears two different projects (see attachment) > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP upper-lower case.png, Images.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1536) Remote endpoint-shared-bucket should be created during edge creation
Vira Vitanska created DLAB-1536: --- Summary: Remote endpoint-shared-bucket should be created during edge creation Key: DLAB-1536 URL: https://issues.apache.org/jira/browse/DLAB-1536 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 Now remote endpoint-shared-bucket is created during remote endpoint creation, but should be during edge creation. This implementation should be pushed in develop and in branch for terraform. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1537) Remote project bucket should be deleted as well during edge termination
Vira Vitanska created DLAB-1537: --- Summary: Remote project bucket should be deleted as well during edge termination Key: DLAB-1537 URL: https://issues.apache.org/jira/browse/DLAB-1537 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1538) [Azure]: project creation fails
Vira Vitanska created DLAB-1538: --- Summary: [Azure]: project creation fails Key: DLAB-1538 URL: https://issues.apache.org/jira/browse/DLAB-1538 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 Attachments: Edge creation.png *Preconditions:* 1. SSN is created on Azure *Steps to reproduce:* 1. Create project *Actual result:* 1. Project creation fails Failed to generate variables dictionary. Exception: name 'edge_conf' is not defined"} *Expected result:* 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1538) [Azure]: Project creation fails
[ https://issues.apache.org/jira/browse/DLAB-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1538: Summary: [Azure]: Project creation fails (was: [Azure]: project creation fails) > [Azure]: Project creation fails > --- > > Key: DLAB-1538 > URL: https://issues.apache.org/jira/browse/DLAB-1538 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Critical > Labels: AZURE, Debian, DevOps, RedHat > Fix For: v.2.3 > > Attachments: Edge creation.png > > > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create project > *Actual result:* > 1. Project creation fails > Failed to generate variables dictionary. Exception: name 'edge_conf' is not > defined"} > *Expected result:* > 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[ https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1537: Description: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created Summary: Different bucket behavior during edge termination (was: Remote project bucket should be deleted as well during edge termination) > Different bucket behavior during edge termination > - > > Key: DLAB-1537 > URL: https://issues.apache.org/jira/browse/DLAB-1537 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > *SSN is created on AWS:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (GCP) only one bucket will be created > for this we have task https://issues.apache.org/jira/browse/DLAB-1487 > - project-remote-bucket > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -deletes > 4. If delete edge on remote endpoint (GCP): > - endpoint-remote-shared-bucket remains > - project-remote-bucket remains > > *SSN is created on GCP:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (AWS) only one bucket will be created > for this we have task https://issues.apache.org/jira/browse/DLAB-1487 > - project-remote-bucket > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -remains > 4. If delete edge on remote endpoint (AWS): > - endpoint-remote-shared-bucket remains > - project-remote-bucket deletes (but then appears name in S3) > > *SSN is created on AZURE* > 1. If create edge on local endpoint two buckets will be created -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1539) [GCP]: Value of user_tag should contain username but not random generated value
Vira Vitanska created DLAB-1539: --- Summary: [GCP]: Value of user_tag should contain username but not random generated value Key: DLAB-1539 URL: https://issues.apache.org/jira/browse/DLAB-1539 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 Attachments: Right example.png, Wrong example.png Example: For user - demo1_te...@epam.com the value for user tag should be 'user : demo1-test1'. See attachment -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1540) [GCP][Project creation]: Subnet search should be by CIDR according to VPC
Vira Vitanska created DLAB-1540: --- Summary: [GCP][Project creation]: Subnet search should be by CIDR according to VPC Key: DLAB-1540 URL: https://issues.apache.org/jira/browse/DLAB-1540 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Mykola Bodnar Fix For: v.2.3 *Preconditions:* # SSN is created on GCP # Endpoint is created on AWS # Notebook is created on AWS *Steps to reproduce:* 1. Create any cluster on AWS *Actual result:* 1. Cluster creation fails *Expected result:* 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1516) [AWS][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1516: Attachment: Reopened DLab UI.png > [AWS][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, Reopened > DLab UI.png, SG from logs DE.png, Subnet from logs DE.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1516) [AWS][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1516: Attachment: Reopened logs.png > [AWS][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, Reopened > DLab UI.png, Reopened logs.png, SG from logs DE.png, Subnet from logs DE.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1516) [AWS][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1516: Attachment: Reopened console.png > [AWS][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, Reopened > DLab UI.png, Reopened console.png, Reopened logs.png, SG from logs DE.png, > Subnet from logs DE.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1516) [AWS][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1516: Attachment: Reopened console2.png > [AWS][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, Reopened > DLab UI.png, Reopened console.png, Reopened console2.png, Reopened logs.png, > SG from logs DE.png, Subnet from logs DE.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1516) [AWS][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17034894#comment-17034894 ] Vira Vitanska commented on DLAB-1516: - *Reopened:* This bug is still reproduced. See attachments with start bu name 'Reopened*' > [AWS][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, Reopened > DLab UI.png, Reopened console.png, Reopened console2.png, Reopened logs.png, > SG from logs DE.png, Subnet from logs DE.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1516) [AWS][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1516: Labels: AWS Debian DevOps RedHat pull-request-available (was: AWS AZURE Debian DevOps GCP RedHat pull-request-available) > [AWS][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1516 > URL: https://issues.apache.org/jira/browse/DLAB-1516 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: DE.png, EMR no spot.png, EMR spot.png, EMR.png, Reopened > DLab UI.png, Reopened console.png, Reopened console2.png, Reopened logs.png, > SG from logs DE.png, Subnet from logs DE.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1540) [GCP][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1540: Labels: Debian DevOps GCP (was: AWS AZURE Debian DevOps GCP RedHat pull-request-available) > [GCP][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1540 > URL: https://issues.apache.org/jira/browse/DLAB-1540 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Create any cluster on AWS > *Actual result:* > 1. Cluster creation fails > *Expected result:* > 1. Cluster creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1540) [GCP][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1540: Description: *Preconditions:* # SSN is created on GCP # Remote endpoint is created on GCP *Steps to reproduce:* 1. Create project using external endpoint fromGCP *Actual result:* 1. Project creation fails *Expected result:* 1. Project creation is successful was: *Preconditions:* # SSN is created on GCP # Endpoint is created on AWS # Notebook is created on AWS *Steps to reproduce:* 1. Create any cluster on AWS *Actual result:* 1. Cluster creation fails *Expected result:* 1. Cluster creation is successful > [GCP][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1540 > URL: https://issues.apache.org/jira/browse/DLAB-1540 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > > *Preconditions:* > # SSN is created on GCP > # Remote endpoint is created on GCP > *Steps to reproduce:* > 1. Create project using external endpoint fromGCP > *Actual result:* > 1. Project creation fails > *Expected result:* > 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1540) [GCP][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1540: Attachment: Logs.png > [GCP][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1540 > URL: https://issues.apache.org/jira/browse/DLAB-1540 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: Logs.png > > > *Preconditions:* > # SSN is created on GCP > # Remote endpoint is created on GCP > *Steps to reproduce:* > 1. Create project using external endpoint fromGCP > *Actual result:* > 1. Project creation fails > *Expected result:* > 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1540) [GCP][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1540: Attachment: Console 1.png > [GCP][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1540 > URL: https://issues.apache.org/jira/browse/DLAB-1540 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: Console 1.png, Logs.png > > > *Preconditions:* > # SSN is created on GCP > # Remote endpoint is created on GCP > *Steps to reproduce:* > 1. Create project using external endpoint fromGCP > *Actual result:* > 1. Project creation fails > *Expected result:* > 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1540) [GCP][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1540: Attachment: Console 2.png > [GCP][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1540 > URL: https://issues.apache.org/jira/browse/DLAB-1540 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: Console 1.png, Console 2.png, Logs.png > > > *Preconditions:* > # SSN is created on GCP > # Remote endpoint is created on GCP > *Steps to reproduce:* > 1. Create project using external endpoint fromGCP > *Actual result:* > 1. Project creation fails > *Expected result:* > 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1540) [GCP][Project creation]: Subnet search should be by CIDR according to VPC
[ https://issues.apache.org/jira/browse/DLAB-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1540: Attachment: Console 3.png > [GCP][Project creation]: Subnet search should be by CIDR according to VPC > - > > Key: DLAB-1540 > URL: https://issues.apache.org/jira/browse/DLAB-1540 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: Console 1.png, Console 2.png, Console 3.png, Logs.png > > > *Preconditions:* > # SSN is created on GCP > # Remote endpoint is created on GCP > *Steps to reproduce:* > 1. Create project using external endpoint fromGCP > *Actual result:* > 1. Project creation fails > *Expected result:* > 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1541) It should be possible to create notebook with existing name in another project for the same user
Vira Vitanska created DLAB-1541: --- Summary: It should be possible to create notebook with existing name in another project for the same user Key: DLAB-1541 URL: https://issues.apache.org/jira/browse/DLAB-1541 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 Attachments: Dlab UI.png, f12.png *Preconditions:* 1. Notebook with name 'Notebook1' is created in Project1 by user1 *Steps to reproduce:* 1. Create notebook with name 'Notebook1' in Project2 by user1 *Actual result:* 1. Notebook creation is forbidden *Expected result:* 1. Notebook creation is allowed -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1370) [AWS][Part2]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1370: Description: # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image # 'Shared resource' should be in 'Project' column if it is shared image # Filter does not work by 'Shared resource' in 'Project' column was: # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image. # 'Shared resource' should be in 'Project' column if it is shared image. > [AWS][Part2]: Alter billing values according to updates on billing page > --- > > Key: DLAB-1370 > URL: https://issues.apache.org/jira/browse/DLAB-1370 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, AWS, Back-end, Debian, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, Images.png > > > # 'Image' should be used in 'Resource type' column for all images > # User_name should be used in 'User'column if it is custom image > # Project_name should be in 'Project' column if it is custom image > # 'Shared resource' should be in 'Project' column if it is shared image > # Filter does not work by 'Shared resource' in 'Project' column -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Description: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column was: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP upper-lower case.png, Images.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1362) [Azure]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1362: Description: # -'Bucket' should be in 'Resource type' column for all buckets- # -Project_name should be in 'Project' column if it is project_bucket.- # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image. # 'Shared resource' should be in 'Project' column if it is shared image. # Instead of should be its value # There are three storages (sbn-ssn-storage/sbn-pr1-local-storage/sbn-local-shared-storage), but in DLab billing we have only one (sbn-pr1-local-storage) # If project name contains upper case in billing report page appears two different projects (see attachment) # Filter does not work by 'Shared resource' in 'Project' column was: # -'Bucket' should be in 'Resource type' column for all buckets- # -Project_name should be in 'Project' column if it is project_bucket.- # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image. # 'Shared resource' should be in 'Project' column if it is shared image. # Instead of should be its value # There are three storages (sbn-ssn-storage/sbn-pr1-local-storage/sbn-local-shared-storage), but in DLab billing we have only one (sbn-pr1-local-storage) # If project name contains upper case in billing report page appears two different projects (see attachment) > [Azure]: Alter billing values according to updates on billing page > -- > > Key: DLAB-1362 > URL: https://issues.apache.org/jira/browse/DLAB-1362 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, AZURE, Back-end, Debian, RedHat > Fix For: v.2.3 > > Attachments: Azure ssn size1.png, Azure ssn size2.png, Azure storage > account.png, Buckets.png, Images.png, Upper and lower case in Project > name.png, azure ssn size3.png > > > # -'Bucket' should be in 'Resource type' column for all buckets- > # -Project_name should be in 'Project' column if it is project_bucket.- > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # User_name should be used in 'User'column if it is custom image > # Project_name should be in 'Project' column if it is custom image. > # 'Shared resource' should be in 'Project' column if it is shared image. > # Instead of should be its value > # There are three storages > (sbn-ssn-storage/sbn-pr1-local-storage/sbn-local-shared-storage), but in DLab > billing we have only one (sbn-pr1-local-storage) > # If project name contains upper case in billing report page appears two > different projects (see attachment) > # Filter does not work by 'Shared resource' in 'Project' column -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1542) []: Add possibility to choose the same endpoint after edge termination
Vira Vitanska created DLAB-1542: --- Summary: []: Add possibility to choose the same endpoint after edge termination Key: DLAB-1542 URL: https://issues.apache.org/jira/browse/DLAB-1542 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Do it i separate branch for testing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1542) []: Add possibility to choose the same endpoint after edge termination
[ https://issues.apache.org/jira/browse/DLAB-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1542: --- Assignee: Oleg Fuks (was: Dmytro Gnatyshyn) Labels: AWS AZURE Back-end Debian GCP RedHat (was: AWS AZURE Debian Front-end GCP RedHat) > []: Add possibility to choose the same endpoint after edge termination > -- > > Key: DLAB-1542 > URL: https://issues.apache.org/jira/browse/DLAB-1542 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > > Do it i separate branch for testing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1542) [Back-end]: Add possibility to choose the same endpoint after edge termination
[ https://issues.apache.org/jira/browse/DLAB-1542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1542: Summary: [Back-end]: Add possibility to choose the same endpoint after edge termination (was: []: Add possibility to choose the same endpoint after edge termination) > [Back-end]: Add possibility to choose the same endpoint after edge termination > -- > > Key: DLAB-1542 > URL: https://issues.apache.org/jira/browse/DLAB-1542 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > > Do it i separate branch for testing. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1543) Value of total sum is not sticky in Firefox browser
Vira Vitanska created DLAB-1543: --- Summary: Value of total sum is not sticky in Firefox browser Key: DLAB-1543 URL: https://issues.apache.org/jira/browse/DLAB-1543 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Attachments: Edge.png, Firefox.png # Total sum should be sticky when scrolling only for Firefox v.72.0.2 (64-bit) # Add horizontal lines for Service Charges column for Edge browser v. 44.18362.387.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1543) [Billing report]: Value of total sum is not sticky in Firefox browser
[ https://issues.apache.org/jira/browse/DLAB-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1543: Summary: [Billing report]: Value of total sum is not sticky in Firefox browser (was: Value of total sum is not sticky in Firefox browser) > [Billing report]: Value of total sum is not sticky in Firefox browser > - > > Key: DLAB-1543 > URL: https://issues.apache.org/jira/browse/DLAB-1543 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Edge.png, Firefox.png > > > # Total sum should be sticky when scrolling only for Firefox v.72.0.2 (64-bit) > # Add horizontal lines for Service Charges column for Edge browser v. > 44.18362.387.0 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1544) [Notebook]: Need to change behavior of Show Active button
Vira Vitanska created DLAB-1544: --- Summary: [Notebook]: Need to change behavior of Show Active button Key: DLAB-1544 URL: https://issues.apache.org/jira/browse/DLAB-1544 Project: Apache DLab Issue Type: Improvement Components: DLab Old Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn As a user I want to be notified about failing computational resources in 'show active' mode so that I do not need to switch to 'show all' mode. *Case:* 1. on resources_list page 'show active' button is chosen 2. computational resource is creating 3. creating computational resource fails It should be possibility to 'notify' user about failed computational resource. Because in 'show active' mode this computational resource will not be portayed untill a user change mode to 'show all'. *Acceptance criteria:* 1. user should receive notify about unsuccessful computational resources creating in 'show active' mode on resource list page -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1544) [Notebook]: Need to change behavior of Show Active button
[ https://issues.apache.org/jira/browse/DLAB-1544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1544: Description: As a user I want to be notified about failing notebook in 'show active' mode so that I do not need to switch to 'show all' mode. *Case:* 1. on resources_list page 'show active' button is chosen 2. notebook is creating 3. notebook creation fails It should be possibility to 'notify' user about failed computational resource. Because in 'show active' mode this notebook will not be portrayed until a user change mode to 'show all'. *Acceptance criteria:* 1. user should receive notify about unsuccessful notebook creation in 'show active' mode on resource list page was: As a user I want to be notified about failing computational resources in 'show active' mode so that I do not need to switch to 'show all' mode. *Case:* 1. on resources_list page 'show active' button is chosen 2. computational resource is creating 3. creating computational resource fails It should be possibility to 'notify' user about failed computational resource. Because in 'show active' mode this computational resource will not be portayed untill a user change mode to 'show all'. *Acceptance criteria:* 1. user should receive notify about unsuccessful computational resources creating in 'show active' mode on resource list page Labels: AWS AZURE Debian Front-end GCP RedHat (was: AWS AZURE Debian Front-end GCP RedHat pull-request-available) > [Notebook]: Need to change behavior of Show Active button > - > > Key: DLAB-1544 > URL: https://issues.apache.org/jira/browse/DLAB-1544 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > > As a user I want to be notified about failing notebook in 'show active' mode > so that I do not need to switch to 'show all' mode. > > *Case:* > 1. on resources_list page 'show active' button is chosen > 2. notebook is creating > 3. notebook creation fails > It should be possibility to 'notify' user about failed computational resource. > Because in 'show active' mode this notebook will not be portrayed until a > user change mode to 'show all'. > > *Acceptance criteria:* > 1. user should receive notify about unsuccessful notebook creation in 'show > active' mode on resource list page > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1543) [Billing report]: Value of total sum is not sticky in Firefox browser
[ https://issues.apache.org/jira/browse/DLAB-1543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1543: Attachment: Project is not created.png Description: # Total sum should be sticky when scrolling only for Firefox v.72.0.2 (64-bit) # Add horizontal lines for Service Charges column for Edge browser v. 44.18362.387.0 # If project is not still created all pages are blocked after visiting a 'Billing report' page was: # Total sum should be sticky when scrolling only for Firefox v.72.0.2 (64-bit) # Add horizontal lines for Service Charges column for Edge browser v. 44.18362.387.0 > [Billing report]: Value of total sum is not sticky in Firefox browser > - > > Key: DLAB-1543 > URL: https://issues.apache.org/jira/browse/DLAB-1543 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Edge.png, Firefox.png, Project is not created.png > > > # Total sum should be sticky when scrolling only for Firefox v.72.0.2 (64-bit) > # Add horizontal lines for Service Charges column for Edge browser v. > 44.18362.387.0 > # If project is not still created all pages are blocked after visiting a > 'Billing report' page -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[ https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1537: Description: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created * endpoint-local-shared-bucket * project-local-bucket 2. If create edge on remote endpoint was: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created > Different bucket behavior during edge termination > - > > Key: DLAB-1537 > URL: https://issues.apache.org/jira/browse/DLAB-1537 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > *SSN is created on AWS:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (GCP) only one bucket will be created > for this we have task https://issues.apache.org/jira/browse/DLAB-1487 > - project-remote-bucket > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -deletes > 4. If delete edge on remote endpoint (GCP): > - endpoint-remote-shared-bucket remains > - project-remote-bucket remains > > *SSN is created on GCP:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (AWS) only one bucket will be created > for this we have task https://issues.apache.org/jira/browse/DLAB-1487 > - project-remote-bucket > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -remains > 4. If delete edge on remote endpoint (AWS): > - endpoint-remote-shared-bucket remains > - project-remote-bucket deletes (but then appears name in S3) > > *SSN is created on AZURE* > 1. If create edge on local endpoint two buckets will be created > * endpoint-local-shared-bucket > * project-local-bucket > 2. If create edge on remote endpoint -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1538) [Azure]: Project creation fails
[ https://issues.apache.org/jira/browse/DLAB-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17035343#comment-17035343 ] Vira Vitanska commented on DLAB-1538: - Closed: Commit ID 358f98621da52b1abf600c4e56af8a41dcb83d2a > [Azure]: Project creation fails > --- > > Key: DLAB-1538 > URL: https://issues.apache.org/jira/browse/DLAB-1538 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Critical > Labels: AZURE, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: Edge creation.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create project > *Actual result:* > 1. Project creation fails > Failed to generate variables dictionary. Exception: name 'edge_conf' is not > defined"} > *Expected result:* > 1. Project creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[ https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1537: Description: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created * endpoint-local-shared-bucket * project-local-bucket 2. If create edge on remote endpoint was: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created for this we have task https://issues.apache.org/jira/browse/DLAB-1487 - project-remote-bucket 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created * endpoint-local-shared-bucket * project-local-bucket 2. If create edge on remote endpoint > Different bucket behavior during edge termination > - > > Key: DLAB-1537 > URL: https://issues.apache.org/jira/browse/DLAB-1537 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > *SSN is created on AWS:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (GCP) only one bucket will be created > - project-remote-bucket > Endpoint-remote-shared-bucket is created during endpoint creation. For this > we have task https://issues.apache.org/jira/browse/DLAB-1536 > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -deletes > 4. If delete edge on remote endpoint (GCP): > - endpoint-remote-shared-bucket remains > - project-remote-bucket remains > > *SSN is created on GCP:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (AWS) only one bucket will be created > - project-remote-bucket > Endpoint-remote-shared-bucket is created during endpoint creation. For this > we have task https://issues.apache.org/jira/browse/DLAB-1536 > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -remains > 4. If delete edge on remote endpoint (AWS): > - endpoint-remote-shared-bucket remains > - project-remote-bucket deletes (but then appears name in S3) > > *SSN is created on AZURE* > 1. If create edge on local endpoint two buckets will be created > * endpoint-local-shared-bucket > * project-local-bucket >
[jira] [Updated] (DLAB-1518) [GCP]: Edge creation fails in case if local and external endpoint are on GCP in one project
[ https://issues.apache.org/jira/browse/DLAB-1518?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1518: Summary: [GCP]: Edge creation fails in case if local and external endpoint are on GCP in one project (was: Edge creation fails in case if local and external endpoint are on GCP in one project) > [GCP]: Edge creation fails in case if local and external endpoint are on GCP > in one project > --- > > Key: DLAB-1518 > URL: https://issues.apache.org/jira/browse/DLAB-1518 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: DLab UI.png, Project creation.png > > > *Preconditions:* > # SSN is created on GCP > # External endpoint1 is created on AWS > # External endpoint2 is created on GCP > *Steps to reproduce:* > 1. Create project with 3 endpoints: local (GCP), external (AWS), external > (GCP) > *Actual result:* > # Local creation fails > # External (AWS) creation is successful > # External (GCP) creation fails > *Expected result:* > # External (AWS) creation is successful > # Local creation is successful > # External (GCP) creation is successful > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1545) [Azure]: Edge creation fails in case if local and external endpoint are on GCP in one project
Vira Vitanska created DLAB-1545: --- Summary: [Azure]: Edge creation fails in case if local and external endpoint are on GCP in one project Key: DLAB-1545 URL: https://issues.apache.org/jira/browse/DLAB-1545 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 Attachments: Azure.png *Preconditions:* # SSN is created on Azure # External endpoint1 is created on Azure *Steps to reproduce:* 1. Create project with 2 endpoints: local (Azure), external (Azure) *Actual result:* # One edge creation is successful # The other creation fails *Expected result:* # One edge creation is successful # The other creation is successful too -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[ https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1537: Description: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint - project-remote-bucket was: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created * endpoint-local-shared-bucket * project-local-bucket 2. If create edge on remote endpoint > Different bucket behavior during edge termination > - > > Key: DLAB-1537 > URL: https://issues.apache.org/jira/browse/DLAB-1537 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > *SSN is created on AWS:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (GCP) only one bucket will be created > - project-remote-bucket > Endpoint-remote-shared-bucket is created during endpoint creation. For this > we have task https://issues.apache.org/jira/browse/DLAB-1536 > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -deletes > 4. If delete edge on remote endpoint (GCP): > - endpoint-remote-shared-bucket remains > - project-remote-bucket remains > > *SSN is created on GCP:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (AWS) only one bucket will be created > - project-remote-bucket > Endpoint-remote-shared-bucket is created during endpoint creation. For this > we have task https://issues.apache.org/jira/browse/DLAB-1536 > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -remains > 4. If delete edge on remote endpoint (AWS): > - endpoint-remote-shared-bucket remains > - project-remote-bucket deletes (but then appears name in S3
[jira] [Updated] (DLAB-1545) [Azure]: Edge creation fails in case if local and external endpoint are on AZURE in one project
[ https://issues.apache.org/jira/browse/DLAB-1545?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1545: Summary: [Azure]: Edge creation fails in case if local and external endpoint are on AZURE in one project (was: [Azure]: Edge creation fails in case if local and external endpoint are on GCP in one project) > [Azure]: Edge creation fails in case if local and external endpoint are on > AZURE in one project > --- > > Key: DLAB-1545 > URL: https://issues.apache.org/jira/browse/DLAB-1545 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AZURE, Debian, DevOps, RedHat > Fix For: v.2.3 > > Attachments: Azure.png > > > *Preconditions:* > # SSN is created on Azure > # External endpoint1 is created on Azure > *Steps to reproduce:* > 1. Create project with 2 endpoints: local (Azure), external (Azure) > *Actual result:* > # One edge creation is successful > # The other creation fails > *Expected result:* > # One edge creation is successful > # The other creation is successful too -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Deleted] (DLAB-386) Front-end
[ https://issues.apache.org/jira/browse/DLAB-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-386: --- > Front-end > - > > Key: DLAB-386 > URL: https://issues.apache.org/jira/browse/DLAB-386 > Project: Apache DLab > Issue Type: Sub-task >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: Front-end > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-384) [Front-end]: Improvements for manage role
[ https://issues.apache.org/jira/browse/DLAB-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-384: -- Fix Version/s: v.2.3 Sprint: Apache DLab release 2.3 Assignee: Dmytro Gnatyshyn (was: Bohdan Hliva) Labels: AWS AZURE Debian Front-end GCP RedHat (was: AWS AZURE Debian GCP RedHat) Priority: Minor (was: Major) Summary: [Front-end]: Improvements for manage role (was: Improvements for manage role) > [Front-end]: Improvements for manage role > - > > Key: DLAB-384 > URL: https://issues.apache.org/jira/browse/DLAB-384 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > > Group by shape/template in 'Roles' drop down list -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-385) [Back-end]: Improvements for manage role
[ https://issues.apache.org/jira/browse/DLAB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-385: -- Component/s: DLab Main Fix Version/s: v.2.3 Assignee: Oleg Fuks (was: Bohdan Hliva) Priority: Minor (was: Major) Summary: [Back-end]: Improvements for manage role (was: Back-end) > [Back-end]: Improvements for manage role > > > Key: DLAB-385 > URL: https://issues.apache.org/jira/browse/DLAB-385 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: Back-end > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-385) [Back-end]: Improvements for manage role
[ https://issues.apache.org/jira/browse/DLAB-385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-385: --- Parent: (was: DLAB-384) Issue Type: Improvement (was: Sub-task) > [Back-end]: Improvements for manage role > > > Key: DLAB-385 > URL: https://issues.apache.org/jira/browse/DLAB-385 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: Back-end > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[ https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1537: Description: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS) - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint - project-remote-bucket - endpoint-remote-shared-bucket 3. If delete edge on local endpoint 4. If delete edge on remote endpoint (Azure) was: *SSN is created on AWS:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (GCP) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -deletes 4. If delete edge on remote endpoint (GCP): - endpoint-remote-shared-bucket remains - project-remote-bucket remains *SSN is created on GCP:* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint (AWS) only one bucket will be created - project-remote-bucket Endpoint-remote-shared-bucket is created during endpoint creation. For this we have task https://issues.apache.org/jira/browse/DLAB-1536 3. If delete edge on local endpoint - endpoint-local-shared-bucket remains - project-local-bucket -remains 4. If delete edge on remote endpoint (AWS): - endpoint-remote-shared-bucket remains - project-remote-bucket deletes (but then appears name in S3) *SSN is created on AZURE* 1. If create edge on local endpoint two buckets will be created - endpoint-local-shared-bucket - project-local-bucket 2. If create edge on remote endpoint - project-remote-bucket > Different bucket behavior during edge termination > - > > Key: DLAB-1537 > URL: https://issues.apache.org/jira/browse/DLAB-1537 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > *SSN is created on AWS:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (GCP) only one bucket will be created > - project-remote-bucket > Endpoint-remote-shared-bucket is created during endpoint creation. For this > we have task https://issues.apache.org/jira/browse/DLAB-1536 > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -deletes > 4. If delete edge on remote endpoint (GCP): > - endpoint-remote-shared-bucket remains > - project-remote-bucket remains > > *SSN is created on GCP:* > 1. If create edge on local endpoint two buckets will be created > - endpoint-local-shared-bucket > - project-local-bucket > 2. If create edge on remote endpoint (AWS) only one bucket will be created > - project-remote-bucket > Endpoint-remote-shared-bucket is created during endpoint creation. For this > we have task https://issues.apache.org/jira/browse/DLAB-1536 > 3. If delete edge on local endpoint > - endpoint-local-shared-bucket remains > - project-local-bucket -remains > 4. If
[jira] [Updated] (DLAB-384) [Front-end]: Improvements for manage role
[ https://issues.apache.org/jira/browse/DLAB-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-384: --- Attachment: Example.png > [Front-end]: Improvements for manage role > - > > Key: DLAB-384 > URL: https://issues.apache.org/jira/browse/DLAB-384 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Example.png > > > Group by shape/template in 'Roles' drop down list -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[
https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1537:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 {color:#00875a}It is
fixed now{color}
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 {color:#00875A}It is
fixed now{color}
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint
- project-remote-bucket
- endpoint-remote-shared-bucket
3. If delete edge on local endpoint
4. If delete edge on remote endpoint (Azure)
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint
- project-remote-bucket
- endpoint-remote-shared-bucket
3. If delete edge on local endpoint
4. If delete edge on remote endpoint (Azure)
> Different bucket behavior during edge termination
> -
>
> Key: DLAB-1537
> URL: https://issues.apache.org/jira/browse/DLAB-1537
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat
> Fix For: v.2.3
>
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - endpoint-local-shared-bucket
> - project-local-bucket
> 2. If create edge on remote endpoint (GCP) only one bucket will be created
> - project-remote-bucket
> Endpoint-remote-shared-bucket is created during endpoint creation. For this
> we have task https://issues.apache.org/jira/browse/DLAB-1536
> {color:#00875a}It is fixed now{color}
> 3. If delete edge on local endpoint
> - endpoint-local-shared-bucket remains
> - project-local-bucket -deletes
> 4. If delete edge on remote endpoint (GCP):
> - endpoint-remote-shared-bucket remains
> - project-remote-bucket remains
>
> *SSN is created on GCP:*
> 1. If create edge on local endpoint two buckets will be created
> - endpoint-local-shared-bucket
> - project-local-bucket
> 2. If create edge on remote endpoint (AWS) only one bucket will be created
> - project-remote-bucket
> Endpoint-remote-shared-bucke
[jira] [Created] (DLAB-1548) Alter requests for notebook name creation with the same name in different projects
Vira Vitanska created DLAB-1548:
---
Summary: Alter requests for notebook name creation with the same
name in different projects
Key: DLAB-1548
URL: https://issues.apache.org/jira/browse/DLAB-1548
Project: Apache DLab
Issue Type: Improvement
Components: DLab Main
Reporter: Vira Vitanska
Assignee: Dmytro Gnatyshyn
Fix For: v.2.3
@DELETE
/aws/infrastructure_provision/computational_resources/\{exploratoryName}/\{computationalName}/terminate
->
/aws/infrastructure_provision/computational_resources/\{projectName}/\{exploratoryName}/\{computationalName}/terminate
@DELETE
/azure/infrastructure_provision/computational_resources/\{exploratoryName}/\{computationalName}/terminate
->
/azure/infrastructure_provision/computational_resources/\{projectName}/\{exploratoryName}/\{computationalName}/terminate
@DELETE
/gcp/infrastructure_provision/computational_resources/\{exploratoryName}/\{computationalName}/terminate
->
/gcp/infrastructure_provision/computational_resources/\{projectName}/\{exploratoryName}/\{computationalName}/terminate
@POST
/infrastructure_provision/exploratory_environment/scheduler/\{exploratoryName}/\{computationalName}
->
/infrastructure_provision/exploratory_environment/scheduler/\{projectName}/\{exploratoryName}/\{computationalName}
@DELETE /infrastructure_provision/exploratory_environment/\{name}/stop ->
/infrastructure_provision/exploratory_environment/\{project}/\{name}/stop
@DELETE /infrastructure_provision/exploratory_environment/\{name}/terminate ->
/infrastructure_provision/exploratory_environment/\{project}/\{name}/terminate
@GET
/aws/infrastructure_provision/computational_resources/\{exploratoryName}/\{computationalName}/config
->
/aws/infrastructure_provision/computational_resources/\{projectName}/\{exploratoryName}/\{computationalName}/config
@GET
/azure/infrastructure_provision/computational_resources/\{exploratoryName}/\{computationalName}/config
->
/azure/infrastructure_provision/computational_resources/\{projectName}/\{exploratoryName}/\{computationalName}/config
@GET
/gcp/infrastructure_provision/computational_resources/\{exploratoryName}/\{computationalName}/config
->
/gcp/infrastructure_provision/computational_resources/\{projectName}/\{exploratoryName}/\{computationalName}/config
@POST
/infrastructure_provision/exploratory_environment/scheduler/\{exploratoryName}
->
/infrastructure_provision/exploratory_environment/scheduler/\{projectName}/\{exploratoryName}
@POST /infrastructure_provision/exploratory_environment/lib_install - added
new form parameter "project_name" @GET
/infrastructure_provision/exploratory_environment/lib_groups - new QueryParam
"project_name" @POST
/infrastructure_provision/exploratory_environment/search/lib_list - added new
form parameter "project_name" @PUT
/infrastructure_provision/exploratory_environment/\{name}/reconfigure ->
/infrastructure_provision/exploratory_environment/\{project}/\{name}/reconfigure
@GET /infrastructure_provision/exploratory_environment/\{name}/cluster/config
->
/infrastructure_provision/exploratory_environment/\{project}/\{name}/cluster/config
@POST /infrastructure_provision/exploratory_environment/image - added new form
parameter "project_name" @GET
/infrastructure_provision/exploratory_environment/lib_list/formatted - new
QueryParam "project_name" @GET
/infrastructure_provision/exploratory_environment/lib_list - added new form
parameter "project_name" @GET
/infrastructure_provision/exploratory_environment/scheduler/\{exploratoryName}
->
/infrastructure_provision/exploratory_environment/scheduler/\{projectName}/\{exploratoryName}
@GET
/infrastructure_provision/exploratory_environment/scheduler/\{exploratoryName}/\{computationalName}
->
/infrastructure_provision/exploratory_environment/scheduler/\{projectName}/\{exploratoryName}/\{computationalName}
@PUT
/aws/infrastructure_provision/computational_resources/dataengine/\{exploratoryName}/\{computationalName}/config
->
/aws/infrastructure_provision/computational_resources/dataengine/\{projectName}/\{exploratoryName}/\{computationalName}/config
@PUT
/azure/infrastructure_provision/computational_resources/dataengine/\{exploratoryName}/\{computationalName}/config
->
/azure/infrastructure_provision/computational_resources/dataengine/\{projectName}/\{exploratoryName}/\{computationalName}/config
@PUT
/gcp/infrastructure_provision/computational_resources/dataengine/\{exploratoryName}/\{computationalName}/config
->
/gcp/infrastructure_provision/computational_resources/dataengine/\{projectName}/\{exploratoryName}/\{computationalName}/config
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.a
[jira] [Updated] (DLAB-1517) Available lib list is not get due to request entity too large
[ https://issues.apache.org/jira/browse/DLAB-1517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1517: Description: *Preconditions:* # SSN is created on GCP # Endpoint is created on AWS # Notebook is created on AWS *Steps to reproduce:* 1. Go to 'List of resource' page 2. Click action menu for notebook 3. Choose manage libraries 4. Choose 'Select resource' in drop down list *Actual result:* 1. Available lib list is not get successful *Expected result:* 1. Available lib list is get successful Available lib list was get successful after 40 minutes of trying. This bug reproduces especially for RStudio was: *Preconditions:* # SSN is created on GCP # Endpoint is created on AWS # Notebook is created on AWS *Steps to reproduce:* 1. Go to 'List of resource' page 2. Click action menu for notebook 3. Choose manage libraries 4. Choose 'Select resource' in drop down list *Actual result:* 1. Available lib list is not get successful *Expected result:* 1. Available lib list is get successful - Available lib list was get successful after 40 minutes of trying. > Available lib list is not get due to request entity too large > - > > Key: DLAB-1517 > URL: https://issues.apache.org/jira/browse/DLAB-1517 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: Available lib list.png > > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Go to 'List of resource' page > 2. Click action menu for notebook > 3. Choose manage libraries > 4. Choose 'Select resource' in drop down list > *Actual result:* > 1. Available lib list is not get successful > *Expected result:* > 1. Available lib list is get successful > > Available lib list was get successful after 40 minutes of trying. > This bug reproduces especially for RStudio -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1549) [List of resource]: Prevent lib_groups requests if library managements popup is not opened
Vira Vitanska created DLAB-1549: --- Summary: [List of resource]: Prevent lib_groups requests if library managements popup is not opened Key: DLAB-1549 URL: https://issues.apache.org/jira/browse/DLAB-1549 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Attachments: lib_group.png If available lib list is not gained there are often lib_groups requests on 'List of resources' page. Ger rid of these requests on 'List of resources' page if library managements popup is not open -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1532) [Azure]: Add endpoint name to container
[ https://issues.apache.org/jira/browse/DLAB-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1532: Attachment: Remote endpoint.png > [Azure]: Add endpoint name to container > --- > > Key: DLAB-1532 > URL: https://issues.apache.org/jira/browse/DLAB-1532 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Minor > Labels: Azure, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: AWS example.png, Azure.png, Remote endpoint.png > > Time Spent: 40m > Remaining Estimate: 0h > > In Azure bucket consists of account and container. > Add endpoint name to container. > Now we have: > # sbn-project_name-container > # sbn-shared-container > But should be: > # sbn-project_name-endpoint_name-container > # sbn-endpoint_name-shared-container -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1532) [Azure]: Add endpoint name to container
[ https://issues.apache.org/jira/browse/DLAB-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037039#comment-17037039 ] Vira Vitanska commented on DLAB-1532: - *Reopened:* Endpoint name is absent only for remote endpoint, for local endpoint it is present: !Remote endpoint.png! > [Azure]: Add endpoint name to container > --- > > Key: DLAB-1532 > URL: https://issues.apache.org/jira/browse/DLAB-1532 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Minor > Labels: Azure, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: AWS example.png, Azure.png, Remote endpoint.png > > Time Spent: 40m > Remaining Estimate: 0h > > In Azure bucket consists of account and container. > Add endpoint name to container. > Now we have: > # sbn-project_name-container > # sbn-shared-container > But should be: > # sbn-project_name-endpoint_name-container > # sbn-endpoint_name-shared-container -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1549) [List of resource]: Prevent lib_groups requests if library managements popup is not opened
[ https://issues.apache.org/jira/browse/DLAB-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1549: Description: If available lib list is not gained there are often lib_groups requests on 'List of resources' page. Ger rid of these requests on 'List of resources' page if library managements popup is not open - Also even after notebook termination request are still sending and docker runz with '1'. [~ofuks] should take a look at it. was: If available lib list is not gained there are often lib_groups requests on 'List of resources' page. Ger rid of these requests on 'List of resources' page if library managements popup is not open > [List of resource]: Prevent lib_groups requests if library managements popup > is not opened > -- > > Key: DLAB-1549 > URL: https://issues.apache.org/jira/browse/DLAB-1549 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: lib_group.png > > > If available lib list is not gained there are often lib_groups requests on > 'List of resources' page. > Ger rid of these requests on 'List of resources' page if library managements > popup is not open > - > Also even after notebook termination request are still sending and docker > runz with '1'. > [~ofuks] should take a look at it. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1549) [List of resource]: Prevent lib_groups requests if library managements popup is not opened
[ https://issues.apache.org/jira/browse/DLAB-1549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1549: Attachment: Docker logs after notebook termination.png > [List of resource]: Prevent lib_groups requests if library managements popup > is not opened > -- > > Key: DLAB-1549 > URL: https://issues.apache.org/jira/browse/DLAB-1549 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Docker logs after notebook termination.png, lib_group.png > > > If available lib list is not gained there are often lib_groups requests on > 'List of resources' page. > Ger rid of these requests on 'List of resources' page if library managements > popup is not open > - > Also even after notebook termination request are still sending and docker > runz with '1'. > [~ofuks] should take a look at it. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1532) [Azure]: Add endpoint name to container
[ https://issues.apache.org/jira/browse/DLAB-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1532: Attachment: Reopened2.png > [Azure]: Add endpoint name to container > --- > > Key: DLAB-1532 > URL: https://issues.apache.org/jira/browse/DLAB-1532 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Minor > Labels: Azure, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: AWS example.png, Azure.png, Remote endpoint.png, > Reopened1.png, Reopened2.png > > Time Spent: 40m > Remaining Estimate: 0h > > In Azure bucket consists of account and container. > Add endpoint name to container. > Now we have: > # sbn-project_name-container > # sbn-shared-container > But should be: > # sbn-project_name-endpoint_name-container > # sbn-endpoint_name-shared-container -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Comment Edited] (DLAB-1532) [Azure]: Add endpoint name to container
[ https://issues.apache.org/jira/browse/DLAB-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037039#comment-17037039 ] Vira Vitanska edited comment on DLAB-1532 at 2/14/20 4:27 PM: -- *Reopened:* Endpoint name is absent only for remote endpoint, for local endpoint it is present: !Remote endpoint.png! !Reopened1.png! !Reopened2.png! was (Author: vvitanska): *Reopened:* Endpoint name is absent only for remote endpoint, for local endpoint it is present: !Remote endpoint.png! > [Azure]: Add endpoint name to container > --- > > Key: DLAB-1532 > URL: https://issues.apache.org/jira/browse/DLAB-1532 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Minor > Labels: Azure, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: AWS example.png, Azure.png, Remote endpoint.png, > Reopened1.png, Reopened2.png > > Time Spent: 40m > Remaining Estimate: 0h > > In Azure bucket consists of account and container. > Add endpoint name to container. > Now we have: > # sbn-project_name-container > # sbn-shared-container > But should be: > # sbn-project_name-endpoint_name-container > # sbn-endpoint_name-shared-container -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1532) [Azure]: Add endpoint name to container
[ https://issues.apache.org/jira/browse/DLAB-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1532: Attachment: Reopened1.png > [Azure]: Add endpoint name to container > --- > > Key: DLAB-1532 > URL: https://issues.apache.org/jira/browse/DLAB-1532 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Minor > Labels: Azure, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: AWS example.png, Azure.png, Remote endpoint.png, > Reopened1.png, Reopened2.png > > Time Spent: 40m > Remaining Estimate: 0h > > In Azure bucket consists of account and container. > Add endpoint name to container. > Now we have: > # sbn-project_name-container > # sbn-shared-container > But should be: > # sbn-project_name-endpoint_name-container > # sbn-endpoint_name-shared-container -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1550) [Azure]: Playbook running fails on remote-endpoint-shared-bucket
Vira Vitanska created DLAB-1550: --- Summary: [Azure]: Playbook running fails on remote-endpoint-shared-bucket Key: DLAB-1550 URL: https://issues.apache.org/jira/browse/DLAB-1550 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 Attachments: Azure logs *Preconditions:* 1. Remote endpoint is created on Azure 2. SSN is created on Azure 3. Jupyter is created *Steps to reproduce:* 1. Run 'Flights_data_Preparation_Python2-Spark' for remote-endpoint-shared-bucket *Actual result:* 1. Playbook running fails *Expected result:* 1. Playbook running is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[
https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1537:
Attachment: Azure remote terminate edge.png
> Different bucket behavior during edge termination
> -
>
> Key: DLAB-1537
> URL: https://issues.apache.org/jira/browse/DLAB-1537
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat
> Fix For: v.2.3
>
> Attachments: Azure remote terminate edge.png
>
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - endpoint-local-shared-bucket
> - project-local-bucket
> 2. If create edge on remote endpoint (GCP) only one bucket will be created
> - project-remote-bucket
> Endpoint-remote-shared-bucket is created during endpoint creation. For this
> we have task https://issues.apache.org/jira/browse/DLAB-1536
> *{color:#00875a}It is fixed now{color}*
> 3. If delete edge on local endpoint
> - endpoint-local-shared-bucket remains
> - project-local-bucket -deletes
> 4. If delete edge on remote endpoint (GCP):
> - endpoint-remote-shared-bucket remains
> - project-remote-bucket remains
>
> *SSN is created on GCP:*
> 1. If create edge on local endpoint two buckets will be created
> - endpoint-local-shared-bucket
> - project-local-bucket
> 2. If create edge on remote endpoint (AWS) only one bucket will be created
> - project-remote-bucket
> Endpoint-remote-shared-bucket is created during endpoint creation. For this
> we have task https://issues.apache.org/jira/browse/DLAB-1536
> *{color:#00875a}It is fixed now{color}*
> 3. If delete edge on local endpoint
> - endpoint-local-shared-bucket remains
> - project-local-bucket -remains
> 4. If delete edge on remote endpoint (AWS)
> - endpoint-remote-shared-bucket remains
> - project-remote-bucket deletes (but then appears name in S3)
>
> *SSN is created on AZURE*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color:#00875a}project-local-bucket{color}
> 2. If create edge on remote endpoint
> - {color:#00875a}project-remote-bucket{color}
> - {color:#00875a}endpoint-remote-shared-bucket{color}
> 3. If delete edge on local endpoint
> * {color:#00875a}endpoint-local-shared-bucket remains{color}
> * {color:#00875a}project-local-bucket -deletes{color}
> 4. If delete edge on remote endpoint (Azure)
> * {color:#00875a}endpoint-remote-shared-bucket deletes{color}
> * {color:#de350b}project-remote-bucket deletes and fails the same remote
> edge in othe rproject{color}
> j
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[
https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1537:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If create edge on remote endpoint
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
3. If delete edge on local endpoint
* {color:#00875a}endpoint-local-shared-bucket remains{color}
* {color:#00875a}project-local-bucket -deletes{color}
4. If delete edge on remote endpoint (Azure)
* {color:#00875a}endpoint-remote-shared-bucket deletes{color}
* {color:#de350b}project-remote-bucket deletes and fails the same remote edge
in othe rproject{color}
j
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 {color:#00875a}It is
fixed now{color}
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 {color:#00875A}It is
fixed now{color}
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint
- project-remote-bucket
- endpoint-remote-shared-bucket
3. If delete edge on local endpoint
4. If delete edge on remote endpoint (Azure)
> Different bucket behavior during edge termination
> -
>
> Key: DLAB-1537
> URL: https://issues.apache.org/jira/browse/DLAB-1537
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat
> Fix For: v.2.3
>
> Attachments: Azure remote terminate edge.png
>
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - endpoint-local-shared-bucket
> - project-local-bucket
> 2. If create edge on remote endpoint (GCP) only one bucket will be created
> - project-remote-bucket
> Endpoint-remote-shared-bucket is created during endpoint creation. For this
> we have task https://issues.apache.org/jira/browse/DLAB-1536
> *{color:#00875a}It is fixed now{color}*
> 3. If delete edge on
[jira] [Updated] (DLAB-1547) [AWS]: EMR cluster fails due to wrong tags
[ https://issues.apache.org/jira/browse/DLAB-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1547: Attachment: Reopened.png > [AWS]: EMR cluster fails due to wrong tags > -- > > Key: DLAB-1547 > URL: https://issues.apache.org/jira/browse/DLAB-1547 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Oleh Martushevskyi >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, DevOps, EMR, pull-request-available > Fix For: v.2.3 > > Attachments: Reopened.png, Screenshot 2020-02-13 at 10.35.18.png > > Time Spent: 20m > Remaining Estimate: 0h > > Scripts couldn't find EMR ID because of wrong tags -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1547) [AWS]: EMR cluster fails due to wrong tags
[ https://issues.apache.org/jira/browse/DLAB-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037290#comment-17037290 ] Vira Vitanska commented on DLAB-1547: - *Reopened:* Commit ID 984cded188dfba571a1dd74b9b6a7c38f3ca20a1 *Preconditions:* 1. SSN is created on Azure 2. Endpoint is created on AWS *Steps to reproduce:* 1. Create EMR on remote endpoint on AWS > [AWS]: EMR cluster fails due to wrong tags > -- > > Key: DLAB-1547 > URL: https://issues.apache.org/jira/browse/DLAB-1547 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Oleh Martushevskyi >Assignee: Leonid Frolov >Priority: Major > Labels: AWS, DevOps, EMR, pull-request-available > Fix For: v.2.3 > > Attachments: Reopened.png, Screenshot 2020-02-13 at 10.35.18.png > > Time Spent: 20m > Remaining Estimate: 0h > > Scripts couldn't find EMR ID because of wrong tags -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1487) Shared endpoint bucket should be created during project creation
[ https://issues.apache.org/jira/browse/DLAB-1487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037291#comment-17037291 ] Vira Vitanska commented on DLAB-1487: - Closed: Commit ID 984cded188dfba571a1dd74b9b6a7c38f3ca20a1 > Shared endpoint bucket should be created during project creation > > > Key: DLAB-1487 > URL: https://issues.apache.org/jira/browse/DLAB-1487 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Time Spent: 1h > Remaining Estimate: 0h > > Now shared endpoint bucket is created during SSN deployment. And during > project creation only project bucket is created. > However should be: > # Remove shared endpoint bucket during SSN deployment > # During project creation the following buckets should be created: > * shared endpoint bucket > * project bucket -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1499) Noteboks/links are not loaded successfully if project contains more than one edge
[ https://issues.apache.org/jira/browse/DLAB-1499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17037292#comment-17037292 ] Vira Vitanska commented on DLAB-1499: - Closed: Commit ID 984cded188dfba571a1dd74b9b6a7c38f3ca20a1 > Noteboks/links are not loaded successfully if project contains more than one > edge > - > > Key: DLAB-1499 > URL: https://issues.apache.org/jira/browse/DLAB-1499 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Double-redirect.mp4, Links.png, Reopened redirect_uri.mp4 > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > # SSN is created on AWS > # External endpoint is created on GCP > # Notebook1/cluster1 are created on GCP external endpoint > # Notebook2/cluster2 are created on AWs external endpoint > *Steps to reproduce:* > # Refer the notebook1/cluster1 link > # Refer the notebook2/cluster2 link > # > *Actual result:* > 1. Links for one notebook/cluster are loaded successfully > 2. Links for the other notebook/cluster are not loaded successfully > *Expected result:* > 1. All notebook/cluster links are loaded successfully > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[
https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1537:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If create edge on remote endpoint
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
3. If delete edge on local endpoint
* {color:#00875a}+project-local-bucket -deletes+{color}
* {color:#00875a}endpoint-local-shared-bucket remains{color}
4. If delete edge on remote endpoint (Azure)
- {color:#de350b}project-remote-bucket deletes {color}
- {color:#00875a}endpoint-remote-shared-bucket deletes{color}
- fails the edge (on the same remote endpoint) in other project
5. If delete edge on remote endpoint (GCP)
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
6. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket
- project-remote-bucket
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If create edge on remote endpoint
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
3. If delete edge on local endpoint
* {color:#00875a}endpoint-local-shared-bucket remains{color}
* {color:#00875a}project-local-bucket -deletes{color}
4. If delete edge on remote endpoint (Azure)
* {color:#00875a}endpoint-remote-shared-bucket deletes{color}
* {color:#de350b}project-remote-bucket deletes and fails the same remote edge
in othe rproject{color}
j
> Different bucket behavior during edge termination
> -
>
> Key: DLAB-1537
> URL: https://issues.apache.org/jira/browse/DLAB-1537
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Major
>
[jira] [Updated] (DLAB-1537) Different bucket behavior during edge termination
[
https://issues.apache.org/jira/browse/DLAB-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1537:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If create edge on remote endpoint
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
3. If delete edge on local endpoint
* {color:#00875a}+project-local-bucket -deletes+{color}
* {color:#00875a}endpoint-local-shared-bucket remains{color}
4. If delete edge on remote endpoint (Azure)
- {color:#de350b}project-remote-bucket deletes {color}
- {color:#00875a}endpoint-remote-shared-bucket deletes{color}
- fails the edge (on the same remote endpoint) in other project
5. If delete edge on remote endpoint (GCP)
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
6. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a}project-remote-bucket deletes{color}
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (GCP) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -deletes
4. If delete edge on remote endpoint (GCP):
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- endpoint-local-shared-bucket
- project-local-bucket
2. If create edge on remote endpoint (AWS) only one bucket will be created
- project-remote-bucket
Endpoint-remote-shared-bucket is created during endpoint creation. For this we
have task https://issues.apache.org/jira/browse/DLAB-1536 *{color:#00875a}It is
fixed now{color}*
3. If delete edge on local endpoint
- endpoint-local-shared-bucket remains
- project-local-bucket -remains
4. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket remains
- project-remote-bucket deletes (but then appears name in S3)
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If create edge on remote endpoint
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
3. If delete edge on local endpoint
* {color:#00875a}+project-local-bucket -deletes+{color}
* {color:#00875a}endpoint-local-shared-bucket remains{color}
4. If delete edge on remote endpoint (Azure)
- {color:#de350b}project-remote-bucket deletes {color}
- {color:#00875a}endpoint-remote-shared-bucket deletes{color}
- fails the edge (on the same remote endpoint) in other project
5. If delete edge on remote endpoint (GCP)
- endpoint-remote-shared-bucket remains
- project-remote-bucket remains
6. If delete edge on remote endpoint (AWS)
- endpoint-remote-shared-bucket
- project-remote-bucket
> Different bucket behavior during edge termination
> -
>
>
[jira] [Updated] (DLAB-97) Bucket browser
[ https://issues.apache.org/jira/browse/DLAB-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-97: -- Description: As a user I want to use S3 browser so that I can manage my buckets and objects via DLab UI. *Acceptance criteria:* *1.* User has access endpoint_shared bucket and project bucket (only if he is assigned to this project) *2.* Another user does not have access to project bucket (if he is not assigned to this project) *3.* Administrator has access to all buckets *4.* User can upload and download files to and from bucket *5.* User can create public URLs to share the files *6.* User can set Access Control on buckets and files only for project bucket? was: As a user I want to use S3 browser so that i can manage your buckets and objects via DLab UI. *Acceptance criteria:* *1.* User has access only to shared and own personal buckets (by default) *2.* Another user does not have access to other personal buckets (by default) *3.* Administrator has access to shared, ssn and users personal buckets *4.* User can upload and download files to and from Amazon S3 *5.* User can create public URLs to share the files *6.* User can set Access Control on buckets and files only for his personal bucket > Bucket browser > -- > > Key: DLAB-97 > URL: https://issues.apache.org/jira/browse/DLAB-97 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > > As a user I want to use S3 browser so that I can manage my buckets and > objects via DLab UI. > > *Acceptance criteria:* > *1.* User has access endpoint_shared bucket and project bucket (only if he is > assigned to this project) > *2.* Another user does not have access to project bucket (if he is not > assigned to this project) > *3.* Administrator has access to all buckets > *4.* User can upload and download files to and from bucket > *5.* User can create public URLs to share the files > *6.* User can set Access Control on buckets and files only for project bucket? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1551) [Front-end]: Bucket browser
[ https://issues.apache.org/jira/browse/DLAB-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1551: --- Fix Version/s: v.2.3 Sprint: Apache DLab release 2.3 Assignee: Dmytro Gnatyshyn Labels: AWS AZURE Debian Front-end GCP RedHat (was: AWS AZURE Debian GCP RedHat) > [Front-end]: Bucket browser > --- > > Key: DLAB-1551 > URL: https://issues.apache.org/jira/browse/DLAB-1551 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > > As a user I want to use S3 browser so that I can manage my buckets and > objects via DLab UI. > > *Acceptance criteria:* > *1.* User has access endpoint_shared bucket and project bucket (only if he is > assigned to this project) > *2.* Another user does not have access to project bucket (if he is not > assigned to this project) > *3.* Administrator has access to all buckets > *4.* User can upload and download files to and from bucket > *5.* User can create public URLs to share the files > *6.* User can set Access Control on buckets and files only for project bucket? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1551) [Front-end]: Bucket browser
Vira Vitanska created DLAB-1551: --- Summary: [Front-end]: Bucket browser Key: DLAB-1551 URL: https://issues.apache.org/jira/browse/DLAB-1551 Project: Apache DLab Issue Type: New Feature Components: DLab Old Reporter: Vira Vitanska As a user I want to use S3 browser so that I can manage my buckets and objects via DLab UI. *Acceptance criteria:* *1.* User has access endpoint_shared bucket and project bucket (only if he is assigned to this project) *2.* Another user does not have access to project bucket (if he is not assigned to this project) *3.* Administrator has access to all buckets *4.* User can upload and download files to and from bucket *5.* User can create public URLs to share the files *6.* User can set Access Control on buckets and files only for project bucket? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-97) [Back-end]: Bucket browser
[ https://issues.apache.org/jira/browse/DLAB-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-97: - Fix Version/s: v.2.3 Sprint: Apache DLab release 2.3 Assignee: Oleg Fuks Labels: AWS AZURE Back-end Debian GCP RedHat (was: AWS AZURE Debian GCP RedHat) Summary: [Back-end]: Bucket browser (was: Bucket browser) > [Back-end]: Bucket browser > -- > > Key: DLAB-97 > URL: https://issues.apache.org/jira/browse/DLAB-97 > Project: Apache DLab > Issue Type: New Feature > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > > As a user I want to use S3 browser so that I can manage my buckets and > objects via DLab UI. > > *Acceptance criteria:* > *1.* User has access endpoint_shared bucket and project bucket (only if he is > assigned to this project) > *2.* Another user does not have access to project bucket (if he is not > assigned to this project) > *3.* Administrator has access to all buckets > *4.* User can upload and download files to and from bucket > *5.* User can create public URLs to share the files > *6.* User can set Access Control on buckets and files only for project bucket? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1552) [DevOps]: [Back-end]: Bucket browser
Vira Vitanska created DLAB-1552: --- Summary: [DevOps]: [Back-end]: Bucket browser Key: DLAB-1552 URL: https://issues.apache.org/jira/browse/DLAB-1552 Project: Apache DLab Issue Type: New Feature Components: DLab Old Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 As a user I want to use S3 browser so that I can manage my buckets and objects via DLab UI. *Acceptance criteria:* *1.* User has access endpoint_shared bucket and project bucket (only if he is assigned to this project) *2.* Another user does not have access to project bucket (if he is not assigned to this project) *3.* Administrator has access to all buckets *4.* User can upload and download files to and from bucket *5.* User can create public URLs to share the files *6.* User can set Access Control on buckets and files only for project bucket? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
