[jira] [Updated] (DLAB-662) Opening access to Legion nexus
[ https://issues.apache.org/jira/browse/DLAB-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-662: --- Fix Version/s: (was: v.2.2) > Opening access to Legion nexus > -- > > Key: DLAB-662 > URL: https://issues.apache.org/jira/browse/DLAB-662 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Priority: Major > Labels: DevOps > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-662) Opening access to Legion nexus
[ https://issues.apache.org/jira/browse/DLAB-662?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-662: --- Sprint: (was: Apache DLab release 2.2) > Opening access to Legion nexus > -- > > Key: DLAB-662 > URL: https://issues.apache.org/jira/browse/DLAB-662 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Priority: Major > Labels: DevOps > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-587) Investigate possibility to add interpreter to Apache zeppelin via Zeppelin UI
[ https://issues.apache.org/jira/browse/DLAB-587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-587: --- Sprint: (was: Apache DLab release 2.2) > Investigate possibility to add interpreter to Apache zeppelin via Zeppelin UI > -- > > Key: DLAB-587 > URL: https://issues.apache.org/jira/browse/DLAB-587 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > > As a user I want to have a possibility to install interpreter via Zeppelin UI > > *Acceptance criteria:* > # If user installs interpreter via Zeppelin UI new interpreter is added > # User can choose edded interpreter for a running code -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-323) [2 VPCs]: Tags are absent for second vpc/peering connection/route table
[ https://issues.apache.org/jira/browse/DLAB-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-323: --- Sprint: (was: Apache DLab release 2.3) > [2 VPCs]: Tags are absent for second vpc/peering connection/route table > --- > > Key: DLAB-323 > URL: https://issues.apache.org/jira/browse/DLAB-323 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old > Environment: AWS >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > > *Steps to reproduce:* > 1. create SSN with 2 VPCs > > *Actual result:* > names are absent for second vpc/peering connection/route table > > *Expected result:* > names are present for second vpc/peering connection/route table -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-478) During DLab page open replace 'Loading...'
[ https://issues.apache.org/jira/browse/DLAB-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-478: --- Sprint: (was: Apache DLab release 2.3) > During DLab page open replace 'Loading...' > -- > > Key: DLAB-478 > URL: https://issues.apache.org/jira/browse/DLAB-478 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Front-end > Fix For: v.2.3 > > Attachments: Screenshot_1.png > > > Investigate what image to give or move 'Loading...' in the center of page -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-547) OpenLDAP servers shouldn't be accessible from internet
[ https://issues.apache.org/jira/browse/DLAB-547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-547: --- Sprint: (was: Apache DLab release 2.3) > OpenLDAP servers shouldn't be accessible from internet > -- > > Key: DLAB-547 > URL: https://issues.apache.org/jira/browse/DLAB-547 > Project: Apache DLab > Issue Type: Task >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Fix For: v.2.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-327) Docker's errors occur while creating EMR spot instance in any notebook
[ https://issues.apache.org/jira/browse/DLAB-327?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-327: --- Sprint: (was: Apache DLab release 2.3) > Docker's errors occur while creating EMR spot instance in any notebook > -- > > Key: DLAB-327 > URL: https://issues.apache.org/jira/browse/DLAB-327 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old > Environment: AWS >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Trivial > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Screenshot (66).png > > > A bug was found on AWS. > *Preconditions:* > any notebook is created (Jupyter/zeppelin/rstudio) > *Steps to reproduce:* > # create EMR with spot > # check Docker's logs whether are there any errors. > *Actual result:* > EMR is being created, but there are some strange Docker's fatal errors. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-334) [AWS][GCP][RStudio]: Sometimes cluster termination/RStudio stoping with related clusrter fails
[ https://issues.apache.org/jira/browse/DLAB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-334: --- Sprint: (was: Apache DLab release 2.3) > [AWS][GCP][RStudio]: Sometimes cluster termination/RStudio stoping with > related clusrter fails > -- > > Key: DLAB-334 > URL: https://issues.apache.org/jira/browse/DLAB-334 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old > Environment: AWS, GCP > RStudio >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Minor > Labels: Debian, DevOps, GCP, GCP_demo, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: AWS console.PNG, EMR termination.PNG > > > *Preconditions:* > 1. EMR or Spark standalone cluster is created > *Steps to reproduce:* > 1. terminate EMR or Spark standalone cluster > *Actual result:* > 1. EMR/Saprk standalone termination fails on DLab UI > 2. EMR/Saprk is terminated on AWS console > !EMR termination.PNG! > !AWS console.PNG! > > *Expected result:* > 1. EMR/Saprk standalone termination is successful on DLab UI > 2. EMR/Saprk is terminated on AWS console > ***Why command is done for jupyter s*udo: rm -rf > /home/dlab-user/.local/share/jupyter/kernels/*_vit_2112-vira_vitanska-des-rs-519spo-cust-5ca34*? > Also the bug was reproduced if stop RStudio with related clusters (GCP) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-289) [Azure][AWS]: Zeppelin/Rstudio creations from custom image fails on removing cluster kernels
[ https://issues.apache.org/jira/browse/DLAB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-289: --- Sprint: (was: Apache DLab release 2.3) > [Azure][AWS]: Zeppelin/Rstudio creations from custom image fails on removing > cluster kernels > > > Key: DLAB-289 > URL: https://issues.apache.org/jira/browse/DLAB-289 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: AZURE, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Image.PNG, Rstudio.PNG, Rstudio.PNG, > Zep-r3-xlarge-spark-default-local.PNG, Zeppelin-r3-xlarge .PNG, spark > executor after standalone creation.PNG > > > The bug was found on *Azure(RedHat)*. This bug reproduces if create notebook > from custom image which (the last) was created during spark cluster running. > *Preconditions:* > Custom image for Zeppelin is created when spark cluster is running > *Steps to reproduce:* > # Terminate Zeppelin with spark cluster or only cluster > # Create Zeppelin from custom image > *Actual result:* > Zeppelin fails with error: > Failed to remove cluster kernels > Please, see attachment > !Image.PNG! > *Expected result:* > Zeppelin is created -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-428) [AWS]: IAM resources are not deleted during SSN termination by Jenkins job
[ https://issues.apache.org/jira/browse/DLAB-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-428: --- Sprint: (was: Apache DLab release 2.3) > [AWS]: IAM resources are not deleted during SSN termination by Jenkins job > --- > > Key: DLAB-428 > URL: https://issues.apache.org/jira/browse/DLAB-428 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > > *Preconditions:* > 1. Environment is created > *Steps to reproduce:* > 1. Terminate SSN by Jenkins Job > *Actual result:* > IAM resources are not deleted > *Expected result:* > All IAM resources are deleted -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-443) Some files.log for notebooks are empty
[ https://issues.apache.org/jira/browse/DLAB-443?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-443: --- Sprint: (was: Apache DLab release 2.3) > Some files.log for notebooks are empty > -- > > Key: DLAB-443 > URL: https://issues.apache.org/jira/browse/DLAB-443 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: logs.png > > > *Preconditions:* > 1. Notebooks are created > *Steps to reproduce:* > 1. Go to /var/opt/dlab/log/notebook > 2. Execute ls -la > *Actual result:* > Some files.log are empty > !logs.png! > *Expected result:* > Files.log are empty -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-519) No library can be chosen from R packages group for installing on demo-environment
[ https://issues.apache.org/jira/browse/DLAB-519?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-519: --- Sprint: (was: Apache DLab release 2.3) > No library can be chosen from R packages group for installing on > demo-environment > - > > Key: DLAB-519 > URL: https://issues.apache.org/jira/browse/DLAB-519 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old > Environment: Demo environment from release 2.1 >Reporter: Anna Orlovska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, DevOps > Fix For: v.2.2, v.2.3 > > Attachments: aws-rstudio-tensorflow.png, > problem_with_library_installation_from_R_group_demo_env.png > > > *Preconditions:* > Notebook (Zeppelin or R-Studio or R-Studio with Tensor Flow) is created and > running. > *Steps to reproduce:* > 1. Manage libraries for notebook. > 2. Select appropriate notebook in “Select resource” combo-box. > 3. Select “R packages” in “Select group”. > 4. Enter library name (for example: AbSim, htmlTable, orsifronts) in the > appropriate field. > *Expected result:* > Entered library is displayed and can be chosen for installing. > *Actual result:* > Message “No match found” is displayed. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-316) [Reverse proxy]: Links Back to master/Application Datail UI/sparkR/stdout/stderr (Data Engine), logs/kill application are not opened successfully
[ https://issues.apache.org/jira/browse/DLAB-316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-316: --- Sprint: (was: Apache DLab release 2.3) > [Reverse proxy]: Links Back to master/Application Datail > UI/sparkR/stdout/stderr (Data Engine), logs/kill application are not opened > successfully > -- > > Key: DLAB-316 > URL: https://issues.apache.org/jira/browse/DLAB-316 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: 2018-08-16_19-38-17.mp4, reverse spark1.PNG, reverse > spark2.PNG > > > *Preconditions:* > Master spark UI is opened > > *Steps to reproduce:* > # Go to application ID link > # Go to application detail UI link > # Go to description link > # Go to again to description link > # Go to stdout link > # Go to back to master link > > *Actual result:* > Back to master link is not opened successfully > > > *Expected result:* > Back to master link is opened successfully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-584) [Azure]: Investigate reverse proxy performance after instance creation/starting
[ https://issues.apache.org/jira/browse/DLAB-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-584: --- Sprint: (was: Apache DLab release 2.3) > [Azure]: Investigate reverse proxy performance after instance > creation/starting > --- > > Key: DLAB-584 > URL: https://issues.apache.org/jira/browse/DLAB-584 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AZURE, Debian, RedHat > Fix For: v.2.3 > > > Link downloads too long time where reverse proxy is used in case: > - after notebook creation > - after notebook starting. > Please, investigate it. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-604) Autotests fail on GCP during creation DataProc
[ https://issues.apache.org/jira/browse/DLAB-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-604: --- Sprint: (was: Apache DLab release 2.3) > Autotests fail on GCP during creation DataProc > -- > > Key: DLAB-604 > URL: https://issues.apache.org/jira/browse/DLAB-604 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Affects Versions: v.2.2 >Reporter: Anna Orlovska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: DevOps, GCP > Fix For: v.2.2, v.2.3 > > Attachments: autotest_failed_on_DataProc.png > > > *Step to reproduce:* > Run autotests on GCP > *Expected result:* > Tests are finished successfully. > *Actual result:* > Tests are failed during creation DataProc. DataProce uses version 1.1. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-614) [GCP]: Sometimes Data Engine Service creation fails on Zeppelin
[ https://issues.apache.org/jira/browse/DLAB-614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-614: --- Sprint: (was: Apache DLab release 2.3) > [GCP]: Sometimes Data Engine Service creation fails on Zeppelin > --- > > Key: DLAB-614 > URL: https://issues.apache.org/jira/browse/DLAB-614 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, GCP > Fix For: v.2.2, v.2.3 > > Attachments: Dataproc creation.png > > > *Preconditions:* > 1. Zeooelin is created > *Steps to reproduce:* > 1. Create Dataproc v.1.2 or v.1.4 > *Actual result:* > Dataproc creation fails: > [dlab-user@172.31.16.2] out: ImportError: ``requests >= 2.18.0`` is required > by the ``google.resumable_media.requests`` subpackage. > It can be installed via > pip install google-resumable-media[requests]. > *Expected result:* > Dataproc is created successful -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-595) Reconfiguration local spark reduces spark driver memory
[ https://issues.apache.org/jira/browse/DLAB-595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-595: --- Sprint: (was: Apache DLab release 2.3) > Reconfiguration local spark reduces spark driver memory > --- > > Key: DLAB-595 > URL: https://issues.apache.org/jira/browse/DLAB-595 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Minor > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: Spark driver memory.png > > > *Preconditions:* > Notebook is created > > *Steps to reproduce:* > Reconfigure local spark by valid parameters > > *Actual result:* > Spark driver memory is less than before reconfiguration > > *Expected result:* > Spark driver memory is the same as before reconfiguration -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-588) Daily scheduler for DLab instance stopping
[ https://issues.apache.org/jira/browse/DLAB-588?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-588: --- Sprint: (was: Apache DLab release 2.3) > Daily scheduler for DLab instance stopping > -- > > Key: DLAB-588 > URL: https://issues.apache.org/jira/browse/DLAB-588 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > As a user I want to have possibility automatically stopping DLab environment > at particulat time. > > *Acceptance criteria:* > # Particular time is configurable > # If one of nodes is in running status a scheduler trigger at particular > time and environment will be stopped > # If one of nodes is in creating status a sscheduler does not trigger and > will check the status of instance creation in some time. If a status of > creating instance changes for a running one the environment will be stopped -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-413) [AWS][EMR]: Replace hyphen by underscore in interpreter name for Zeppelin
[ https://issues.apache.org/jira/browse/DLAB-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-413: --- Sprint: (was: Apache DLab release 2.3) > [AWS][EMR]: Replace hyphen by underscore in interpreter name for Zeppelin > - > > Key: DLAB-413 > URL: https://issues.apache.org/jira/browse/DLAB-413 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-617) Spaces are absent between labels and values on Notebook popup
[ https://issues.apache.org/jira/browse/DLAB-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-617: --- Sprint: (was: Apache DLab release 2.3) > Spaces are absent between labels and values on Notebook popup > - > > Key: DLAB-617 > URL: https://issues.apache.org/jira/browse/DLAB-617 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Trivial > Labels: AZURE, Front-end, pull-request-available > Fix For: v.2.3 > > Attachments: Bug is still reproduced.png, Space.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Precondirions:* > # SSN is created on Azure > # Any notebook is created > *Steps to reproduce:* > # Go to 'resource list' page > # Click on Notebbok name > *Actual result:* > Spaces are present between labels and values on Notebook popup > *Expected result:* > Spaces are absent between labels and values on Notebook popup -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-522) [AWS]: Refactor Endpoint/Route table creation for SSN
[ https://issues.apache.org/jira/browse/DLAB-522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-522: --- Sprint: (was: Apache DLab release 2.3) > [AWS]: Refactor Endpoint/Route table creation for SSN > -- > > Key: DLAB-522 > URL: https://issues.apache.org/jira/browse/DLAB-522 > Project: Apache DLab > Issue Type: Bug >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Fix For: v.2.2, v.2.3 > > > Currently, we are looking for route table with specific tags. > We should check the existence of route table for VPC and S3 endpoint. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-297) [Azure]: Playbook running on Apache Zeppelin fails due to impossible connection to blob via wasbs protocol
[ https://issues.apache.org/jira/browse/DLAB-297?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-297: --- Sprint: (was: Apache DLab release 2.3) > [Azure]: Playbook running on Apache Zeppelin fails due to impossible > connection to blob via wasbs protocol > -- > > Key: DLAB-297 > URL: https://issues.apache.org/jira/browse/DLAB-297 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AZURE, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: WASBS1.PNG, wasbs.txt > > > *Preconditions:* > Zeppelin is created > *Steps to reproduce:* > 1. run playbook on Apache Zeppelin > *Actual result:* > playbook running fails due to impossible connection to blob via wasbs > protocol > > *Expected result:* > playbook runs successfully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-299) [Autotest][AWS][GCP][Zeppelin]: Autotest running fails on step of establish a new connection
[
https://issues.apache.org/jira/browse/DLAB-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-299:
---
Sprint: (was: Apache DLab release 2.3)
> [Autotest][AWS][GCP][Zeppelin]: Autotest running fails on step of establish a
> new connection
>
>
> Key: DLAB-299
> URL: https://issues.apache.org/jira/browse/DLAB-299
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Demyan Mysakovets
>Priority: Major
> Labels: Debian, DevOps, GCP, RedHat
> Fix For: v.2.2, v.2.3
>
> Attachments: GCP Zeppelin Autotest.PNG, Zeppelin autotest (1).PNG
>
>
> *Steps to reproduce:*
> # Run integration test for Zeppelin on AWS/GCP
>
> *Actual result:*
> Integration test fails with error
> ('Error!', "HTTPConnectionPool(host='172.31.99.176', port=8080): Max retries
> exceeded with url: /api/notebook/import (Caused by
> NewConnectionError(' 0x7f1740919b10>: Failed to establish a new connection: [Errno 111] Connection
> refused',))")
> AutoTests_AWS/299
> AutoTests_AWS/278
> AutoTests_GCP/122
> *Expected result:*
> Integration test runs successfully
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-585) Adjust Zeppelin status after computational resource configuration
[ https://issues.apache.org/jira/browse/DLAB-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-585: --- Sprint: (was: Apache DLab release 2.3) > Adjust Zeppelin status after computational resource configuration > - > > Key: DLAB-585 > URL: https://issues.apache.org/jira/browse/DLAB-585 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > After computational resource configuration, Zeppelin stops and starts. > Please, convey the actual Zeppelin status on UI. And in this case if Zeppelin > is in stopping/starting status the other actions for Zeppelin is disabled > from DLab UI. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-317) [Java dependencies]: After some java library ('com.github.paulcwarren:spring-content-s3 v.0.4.0') installation it is impossible to gain access to S3 only on Apache Zeppelin
[
https://issues.apache.org/jira/browse/DLAB-317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-317:
---
Sprint: (was: Apache DLab release 2.3)
> [Java dependencies]: After some java library
> ('com.github.paulcwarren:spring-content-s3 v.0.4.0') installation it is
> impossible to gain access to S3 only on Apache Zeppelin notebook
> -
>
> Key: DLAB-317
> URL: https://issues.apache.org/jira/browse/DLAB-317
> Project: Apache DLab
> Issue Type: Bug
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Oleksandr Isniuk
>Priority: Minor
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat
> Fix For: v.2.2, v.2.3
>
> Attachments: S3.PNG, com.github.paulcwarren
> spring-content-s3v.0.4.0.PNG
>
>
> *Preconditions:*
> 1. Apache Zeppelin is created
> 2. 'Manage libraries' popup is open
>
> *Steps to reproduce:*
> # Install library *com.github.paulcwarren:spring-content-s3* v.0.4.0 from
> 'Java' on Apache Zeppelin
> # Run plabook for Apache Zeppelin
>
> *Actual result:*
> Playbook (usin local or remote kernel -spark) fails with error:
> !S3.PNG!
> *Expected result:*
> Playbook runs successfully
>
> Note: Please view ivysettings.xml (it's added in project), in this file you
> can filter some dependencies
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-510) [GCP]: Wrong format key if edit instance via GCP console
[ https://issues.apache.org/jira/browse/DLAB-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-510: --- Sprint: (was: Apache DLab release 2.3) > [GCP]: Wrong format key if edit instance via GCP console > > > Key: DLAB-510 > URL: https://issues.apache.org/jira/browse/DLAB-510 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.2, v.2.3 > > Attachments: Wrong format.PNG > > > *Preconditions:* > 1. Environment is created > > *Steps to reproduce:* > # Go to GCP console > # Choose instane (in running status) > # Click 'Edit' button > > *Actual result:* > 1. Message appears 'Wrong format key' > 2. 'Save' button is disabled > !Wrong format.PNG! > > *Expected result:* > 1. Message does not appear 'Wrong format key' > 2. 'Save' button is enabled -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-338) [Volodymyr][Documentation]: Solution architecture diagram for GCP
[ https://issues.apache.org/jira/browse/DLAB-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-338: --- Sprint: (was: Apache DLab release 2.3) > [Volodymyr][Documentation]: Solution architecture diagram for GCP > - > > Key: DLAB-338 > URL: https://issues.apache.org/jira/browse/DLAB-338 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Dmytro Liaskovskyi >Priority: Major > Labels: DevOps, GCP, GCP_demo > Fix For: v.2.3 > > > Assign to Volodymyr Veres -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-472) [Administration page]: Add possibility to filter items by values in grid
[ https://issues.apache.org/jira/browse/DLAB-472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-472: --- Sprint: (was: Apache DLab release 2.3) > [Administration page]: Add possibility to filter items by values in grid > > > Key: DLAB-472 > URL: https://issues.apache.org/jira/browse/DLAB-472 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-310) Create image should be disabled during installing lib
[ https://issues.apache.org/jira/browse/DLAB-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-310: --- Sprint: (was: Apache DLab release 2.3) > Create image should be disabled during installing lib > - > > Key: DLAB-310 > URL: https://issues.apache.org/jira/browse/DLAB-310 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: AWS, AZURE, Front-end, GCP, RedHat, debian > Fix For: v.2.3 > > > Please, prevent possibility to create custom image in case if library is in > installing status. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-333) [AWS][RStudio]: Sparklyr (r packages) lib is not installed neither DLab UI no terminal
[ https://issues.apache.org/jira/browse/DLAB-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-333: --- Sprint: (was: Apache DLab release 2.3) > [AWS][RStudio]: Sparklyr (r packages) lib is not installed neither DLab UI no > terminal > -- > > Key: DLAB-333 > URL: https://issues.apache.org/jira/browse/DLAB-333 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old > Environment: AWS > RedHat >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Sparklyr DLab UI.PNG, shiny log.PNG, sparklyr.PNG, via > console.txt, via terminal.txt > > > *Preconditions:* > 1. Rstudio is created > *Steps to reproduce:* > 1. install 'sparklyr' from r-packages on Rstudio > *Actual result:* > 1. sparklyr installation fails > 2. sparklyr is not installed on notebook > !sparklyr.PNG! > > *Expected result:* > 1. sparklyr installation is successful > 2. sparklyr isinstalled on notebook > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-628) [GCP][Data Engine Service]: R kernel Dataproc 1.3 runs successfully but with exception
[ https://issues.apache.org/jira/browse/DLAB-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-628: --- Sprint: (was: Apache DLab release 2.3) > [GCP][Data Engine Service]: R kernel Dataproc 1.3 runs successfully but with > exception > -- > > Key: DLAB-628 > URL: https://issues.apache.org/jira/browse/DLAB-628 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: Debian, DevOps, GCP, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Rstudio_DP13.png > > > *Preconditions:* > Dataproc v.1.3 is created on RStudio v.1.1.463 > *Steps to reproduce:* > 1. Run Flight data preparation R for remote kernel Dataproc v.1.3 on RStudio > *Actual result:* > Playbook runs successfully but with exception > *Expected result:* > Playbook runs successfully without any exception > Please, view attachment -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-331) [Azure]: Adjust deploy script
[ https://issues.apache.org/jira/browse/DLAB-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-331: --- Sprint: (was: Apache DLab release 2.3) > [Azure]: Adjust deploy script > - > > Key: DLAB-331 > URL: https://issues.apache.org/jira/browse/DLAB-331 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AZURE, Debian, DevOps, RedHat > Fix For: v.2.3 > > > Move script from post-build to deploy script. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-448) Add possibility of filtering list of installed libraries
[ https://issues.apache.org/jira/browse/DLAB-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-448: --- Sprint: (was: Apache DLab release 2.3) > Add possibility of filtering list of installed libraries > - > > Key: DLAB-448 > URL: https://issues.apache.org/jira/browse/DLAB-448 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Anna Orlovska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: add_filtr_to_library_list.png > > > As a user I want to have possibility to filter the list of installed > libraries. > > *Acceptance criteria:* > There is possibility to filter installed libraries list by Name, Group, > Destination, Resource type and Status. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-311) First rendering of notification dialogs works with delay
[ https://issues.apache.org/jira/browse/DLAB-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-311: --- Sprint: (was: Apache DLab release 2.3) > First rendering of notification dialogs works with delay > > > Key: DLAB-311 > URL: https://issues.apache.org/jira/browse/DLAB-311 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Environment 2.PNG, Environment.PNG, SSN monitor.PNG > > > A bug reproduces only at first time or after clear browsing data. > *Precondirions:* > 1.Edge is running > 2. 'Manage environment' popup is open > *Steps to reproduce:* > 1. Click 'stop' or 'terminate' for running environment > *Actual result:* > Name of user environment displays with delay > Please, see attachment > !Environment.PNG! > *Expected result:* > Name of user environment displays simultaneously with dialog window > !Environment 2.PNG! > _ > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-446) Add parameter SSN size in DLab deploy script
[ https://issues.apache.org/jira/browse/DLAB-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-446: --- Sprint: (was: Apache DLab release 2.3) > Add parameter SSN size in DLab deploy script > > > Key: DLAB-446 > URL: https://issues.apache.org/jira/browse/DLAB-446 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > As a user I want to choose the size of SSN during DLab deploying. > Add parameter which responses for size of SSN during DLab deploying. > *Acceptance criteria:* > 1. There is parameter [key: value] for SSN size in deploy script -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-324) 'No-check-certificate' should be removed after updating brunelvis.org's certificate
[ https://issues.apache.org/jira/browse/DLAB-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-324: --- Sprint: (was: Apache DLab release 2.3) > 'No-check-certificate' should be removed after updating brunelvis.org's > certificate > --- > > Key: DLAB-324 > URL: https://issues.apache.org/jira/browse/DLAB-324 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: Jupyter.PNG > > > The certificate from the website [https://brunelvis.org/] issued > Link_github > When the certificate will be updated, we should remove --no-check-certificate > > > Note: Earlier [release 1.9] the bug was reproduced on AWS when Jupyter failed > through inability verifying brunelvis.org's certificate -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-591) Buckets and some VPC are not deleted after deleting SSN on GCP by Jenkins Job
[ https://issues.apache.org/jira/browse/DLAB-591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-591: --- Sprint: (was: Apache DLab release 2.3) > Buckets and some VPC are not deleted after deleting SSN on GCP by Jenkins Job > - > > Key: DLAB-591 > URL: https://issues.apache.org/jira/browse/DLAB-591 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Anna Orlovska >Assignee: Demyan Mysakovets >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.2, v.2.3 > > > *Preconditions:* > SSN is created. > *Steps to reproduce:* > # Terminate SSN with “GCP_Terminate_environment-develop” Jenkins Job. > # Verify absence of VPC in GCP Console. > *Expected result:* > Corresponding to SSN VPC are absent. > *Actual result:* > Corresponding to SSN VPC are present. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-525) [Java library]: Add support of repository for spark-packages.org
[ https://issues.apache.org/jira/browse/DLAB-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-525: --- Sprint: (was: Apache DLab release 2.3) > [Java library]: Add support of repository for spark-packages.org > > > Key: DLAB-525 > URL: https://issues.apache.org/jira/browse/DLAB-525 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, GCP > Fix For: v.2.3 > > Attachments: Curator-client.PNG, avro library.png > > > Add support for repository of spark-packages.org in order to install bundle > libraries from DLab UI > Spark-packages.org link: [https://spark-packages.org/] > [https://dl.bintray.com/spark-packages/] > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-322) Refactor libraries for Notebooks and clusters
[ https://issues.apache.org/jira/browse/DLAB-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-322: --- Sprint: (was: Apache DLab release 2.3) > Refactor libraries for Notebooks and clusters > - > > Key: DLAB-322 > URL: https://issues.apache.org/jira/browse/DLAB-322 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2, v.2.3 > > > *Pre-conditions:* > 1. DataEngine Service is created on AWS/GCP > *Steps to reproduce:* > 1. install available lib list for computational resources > *Actual result:* > available lib list uses 3.5 for pip3 > *Expected result:* > available lib list uses 3.4 for pip3 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-329) Information about exceptions is absent during provisioning resources
[ https://issues.apache.org/jira/browse/DLAB-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-329: --- Sprint: (was: Apache DLab release 2.3) > Information about exceptions is absent during provisioning resources > > > Key: DLAB-329 > URL: https://issues.apache.org/jira/browse/DLAB-329 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Cidr.PNG > > > *Steps to reproduce:* > # Create SSN on AWS with allowed_ip_cidr without defined parameters > aws_subnet_id and aws_sg_ids > > feature-branches/job/aws_vitv/36 > *Expected result:* > SSN is created -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-432) Investigate why different versions of Apache Toree are for Jupyter for local and remote kernels
[ https://issues.apache.org/jira/browse/DLAB-432?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-432: --- Sprint: (was: Apache DLab release 2.3) > Investigate why different versions of Apache Toree are for Jupyter for local > and remote kernels > --- > > Key: DLAB-432 > URL: https://issues.apache.org/jira/browse/DLAB-432 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > Py-DLAB/infrastructure-provisioning/src/general/scripts/os/jupyter_install_dataengine_kernels.py:48 > Py-DLAB/infrastructure-provisioning/src/jupyter/scripts/configure_jupyter_node.py:61 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-288) [EMR]: Java library installation fails only on DLab UI if install java library with other lib group from the first attempt
[ https://issues.apache.org/jira/browse/DLAB-288?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-288: --- Sprint: (was: Apache DLab release 2.3) > [EMR]: Java library installation fails only on DLab UI if install java > library with other lib group from the first attempt > -- > > Key: DLAB-288 > URL: https://issues.apache.org/jira/browse/DLAB-288 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: docker logs.png, image-2019-01-17-12-44-25-319.png, > master-emr519.png, provis.png, self-ser.png > > > A bug was found during java libs installation on EMR v.5.19/v5.12 > *Preconditions:* > EMR v.5.19 or v.5.12 is created > *Steps to reproduce:* > 1. install libraries together: > - htop (apt/yum) > - pronto (pip2) > - access (pip3) > - rmarkdown (r packages) > - pivottables (other) > - com.atlassian.asap:asap-client-core:2.21.7 (java) > - com.eurodyn.qlack2.util:qlack2-util-testing:2.3.9(java) > 2. click 'Install' button > *Actual result:* > 1. all libraries are installed except for java on DLab UI > !image-2019-01-17-12-44-25-319.png! > 2. in path /opt/jars/java/ gava library is installed > *Expected result:* > All groups of libraies are successful installed -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-315) Links for Application Master/history (tracking url) are not opened successfully on EMR 5.12.0/5.19.0
[ https://issues.apache.org/jira/browse/DLAB-315?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-315: --- Sprint: (was: Apache DLab release 2.3) > Links for Application Master/history (tracking url) are not opened > successfully on EMR 5.12.0/5.19.0 > > > Key: DLAB-315 > URL: https://issues.apache.org/jira/browse/DLAB-315 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: EMR.PNG, EMR512.PNG, EMR560 via tunnel.PNG > > > *Preconditions:* > Emr 5.12.0 is created on notebook > > *Steps to reproduce:* > # Go to EMR master UI > # Go to Application Master > *Actual result:* > Link for Application Master isn't opened successfully > > *Expected result:* > Link for Application Master is opened successfully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-511) [GCP]: Instance connection is unsuccessful via GCP console due to failed to read key
[ https://issues.apache.org/jira/browse/DLAB-511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-511: --- Sprint: (was: Apache DLab release 2.3) > [GCP]: Instance connection is unsuccessful via GCP console due to failed to > read key > > > Key: DLAB-511 > URL: https://issues.apache.org/jira/browse/DLAB-511 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.2, v.2.3 > > Attachments: Connection.PNG > > > *Preconditions:* > # Edge is created > # GCP console is open > > *Steps to reproduce:* > # Click SSH drop down list related SSN or Edge > # Choose 'open in browser window using provided private SSH key' > # Choose your key.pem > > *Actual result:* > 1. Connection is not successful > 2. Error message appears 'Select a private ECDSA or RSA key file to sign into > the VM or connect with a generated SSH key.' > > *Expected result:* > 1. Connection is successful -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-473) Remove 'Caffe' from Deep Learning
[ https://issues.apache.org/jira/browse/DLAB-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-473: --- Sprint: (was: Apache DLab release 2.3) > Remove 'Caffe' from Deep Learning > - > > Key: DLAB-473 > URL: https://issues.apache.org/jira/browse/DLAB-473 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Anna Orlovska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP > Fix For: v.2.2, v.2.3 > > Attachments: failed_data_viz_Caffe_on_DeLer.png > > > The last 'Caffe' release was on April 18, 2017. > For now caffe is not run successful on Deeplearning. > Therefore it was decided to remove 'Caffe' from Deeplearning > *Preconditions:* > Deep Learning is created and running. > *Steps to reproduce:* > 1. Open notebook URL in browser. > 2. Upload file “Caffe.ipynb”. > 3. Choose Local PySpark (Python-2.7 / Spark-2.3.2 ) kernel. > 4. Run playbook. > *Expected result:* > Playbook is run successfully. > *Actual result:* > Playbook doesn’t run successfully. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-520) [GCP][Autotest][Rstudio]: Autotest fails on process of creation directory in SSN
[ https://issues.apache.org/jira/browse/DLAB-520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-520: --- Sprint: (was: Apache DLab release 2.3) > [GCP][Autotest][Rstudio]: Autotest fails on process of creation directory in > SSN > > > Key: DLAB-520 > URL: https://issues.apache.org/jira/browse/DLAB-520 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: Debian, DevOps, GCP > Fix For: v.2.2, v.2.3 > > Attachments: Autotest GCP.PNG > > > *Steps to reproduce:* > Run autotest for RStudio on GCP > > *Actual result:* > Autotest fails on process of creation directory in SSN > AutoTests_GCP/131 > > *Expected result:* > Autotest run successfully > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-308) [Local spark]: Spark.executor.memory should be allocated depending on notebook instance shape
[ https://issues.apache.org/jira/browse/DLAB-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-308: --- Sprint: (was: Apache DLab release 2.3) > [Local spark]: Spark.executor.memory should be allocated depending on > notebook instance shape > - > > Key: DLAB-308 > URL: https://issues.apache.org/jira/browse/DLAB-308 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2, v.2.3 > > > *Preconditions:* > Notebook is created > *Steps to reproduce:* > 1. run playbok on local kernel > *Actual result:* > 1. the value of spark.executor.memory is less than 75% from total (if > instance shape is up to 8 GB) > 2. the value of spark.executor.memory is less than formula value: total value > minus 3500MB (if instance shape is over than 8 GB) > *Expected result:* > 1. the value of spark.executor.memory is equal 75% from total (if instance > shape is up to 8 GB) > 2. the value of spark.executor.memory is equal formula value: total value > minus 3500MB (if instance shape is over than 8 GB) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-314) Custom parameters (for local/remote sparks) should be added to Zeppelin Interpreters
[
https://issues.apache.org/jira/browse/DLAB-314?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-314:
---
Sprint: (was: Apache DLab release 2.3)
> Custom parameters (for local/remote sparks) should be added to Zeppelin
> Interpreters
>
>
> Key: DLAB-314
> URL: https://issues.apache.org/jira/browse/DLAB-314
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Old
>Reporter: Vira Vitanska
>Assignee: Oleh Martushevskyi
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat
> Fix For: v.2.3
>
>
> *Preconditions:*
> 1. Apache zeppelin is created
> *Steps to reproduce:*
> 1. reconfigure local spark/remote spark with next parameters:
> [
> {
> "Classification": "spark-defaults",
> "Properties":
> { "spark.shuffle.compress": "true", "spark.network.timeout": "120s" }
> }
> ]
> *Actual result:*
> Custom parameters are absent in zeppelin Interpreters
> *Expected result:*
> Custom parameters are present in zeppelin Interpreters
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-479) [Autotest][GCP][Data Engine Service]: The python script execution wasn`t successful on Jupyter
[ https://issues.apache.org/jira/browse/DLAB-479?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-479: --- Sprint: (was: Apache DLab release 2.3) > [Autotest][GCP][Data Engine Service]: The python script execution wasn`t > successful on Jupyter > -- > > Key: DLAB-479 > URL: https://issues.apache.org/jira/browse/DLAB-479 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Minor > Labels: Debian, DevOps, GCP > Fix For: v.2.2, v.2.3 > > > *Steps to reproduce:* > 1. Run autotest for Data Engene Service for Jupyter > > *Actual result:* > Autotest execution fails: > +AutoTests_GCP/130/+ > > *Expected result:* > Autotest execution is successful > > Playbook running for Data Engene Service for Jupyter is successful if run by > manually -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-326) Investigate why the same CIDR was allocated for two users during edges creation
[ https://issues.apache.org/jira/browse/DLAB-326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-326: --- Sprint: (was: Apache DLab release 2.3) > Investigate why the same CIDR was allocated for two users during edges > creation > --- > > Key: DLAB-326 > URL: https://issues.apache.org/jira/browse/DLAB-326 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.3 > > Attachments: Edge user2 created.PNG, Edge.PNG, edge-user1-fails.txt > > > A bug was found on AWS [RedHat] during creation edges. > *Preconditions:* > only SSN is created > *Steps to reproduce:* > 1. simultaneously create two edges > *Actual result:* > 1. one of edge is created > 2. the other edge fails during creation > !Edge.PNG! > *Expected result:* > 1. two edges are created successfully -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-536) Shell interpreter is absent for some Apache Zeppelin shapes
[ https://issues.apache.org/jira/browse/DLAB-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-536: --- Sprint: (was: Apache DLab release 2.3) > Shell interpreter is absent for some Apache Zeppelin shapes > --- > > Key: DLAB-536 > URL: https://issues.apache.org/jira/browse/DLAB-536 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Affects Versions: v.2.1 >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Shell interpreter.png > > > *Preconditions:* > 1. Apache Zeppelin is created > Steps to reproduce: > 1. Go to Zeppelin interpreter > *Actual result:* > Shell interpreter is absent > *Expected result:* > Shell interpreter is present > Even if Shell interpreter is present the command running fails using the > shell for example on GCP: > !Shell interpreter.png! -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-452) [GCP][Data Engine Service]: Kernel R of dataproc 1.2 is not run successfully on Zeppelin 0.8.0
[ https://issues.apache.org/jira/browse/DLAB-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-452: --- Sprint: (was: Apache DLab release 2.3) > [GCP][Data Engine Service]: Kernel R of dataproc 1.2 is not run successfully > on Zeppelin 0.8.0 > -- > > Key: DLAB-452 > URL: https://issues.apache.org/jira/browse/DLAB-452 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, GCP, RedHat > Fix For: v.2.2, v.2.3 > > Attachments: Py2_preparation_DP12.png, R_data_preparation_DP12.png, > R_data_preparation_local_kernel.png > > > *Preconditions:* > Dataproc 1.2 is created on Apache Zeppelin 0.8.0 > *Steps to reproduce:* > 1. Run r data preparation for remote kernel Py2 or Py3 > *Actual result:* > Playbook runs with error > *Expected result:* > Playbook runs successfully > ***If Dataproc 1.2 is created (running/stopped) local kernel (Py2/Py3) is not > run successfully. It is the same error as for remote kernel. If Dataproc 1.2 > is terminated local kernel (Py2/Py3) is run successfully. > ***Dataproc 1.3 runs successfully. > > If runs Py2 data preparation on dataproc 1.2 a playbook runs successfully but > wit exception. For local kernel it is the same. If Dataproc 1.2 is terminated > local kernel (Py2) is run without exception. > > Please, view attachments. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-592) [GCP]: Upgrade Dataproc to 1.2 and 1.3
[ https://issues.apache.org/jira/browse/DLAB-592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-592: --- Issue Type: Task (was: Sub-task) Parent: (was: DLAB-254) > [GCP]: Upgrade Dataproc to 1.2 and 1.3 > -- > > Key: DLAB-592 > URL: https://issues.apache.org/jira/browse/DLAB-592 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, GCP, pull-request-available > Fix For: v.2.2 > > Attachments: DP14_preemptible.PNG, Dataproc1.4 on zeppelin.PNG, > SparkR kernel on Jupyter.PNG > > Time Spent: 1h > Remaining Estimate: 0h > > *Preconditions:* > Dataproc v.1.1 is created on Jupyter > > *Steps to reproduce:* > 1. Go to Jupyter UI > 2. Chose SparkR kernel for > > *Actual result:* > SparkR kernel dies > !SparkR kernel on Jupyter.PNG! > > *Expected result:* > SparkR kernel is ready for running > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-255) Update Apache Zeppelin version
[ https://issues.apache.org/jira/browse/DLAB-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-255: --- Issue Type: Task (was: Sub-task) Parent: (was: DLAB-254) > Update Apache Zeppelin version > --- > > Key: DLAB-255 > URL: https://issues.apache.org/jira/browse/DLAB-255 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > Attachments: Azure Data Lake.txt, Azure adl.PNG, DP1.2-Zeppelin-local > kernel.png, Rspark.png, Zeppelin scala.txt, Zeppelin_py2_Dataptoc-1-2.png, > Zeppelin_sparkR.txt > > > By date 25/01/2019 version of Apache Zeppelin version is 8.0.0 > Update to version 8.1.0 (in this version job url track is fixed) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-256) Update nodejs & npm for notebooks
[ https://issues.apache.org/jira/browse/DLAB-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-256: --- Fix Version/s: (was: v.2.3) > Update nodejs & npm for notebooks > - > > Key: DLAB-256 > URL: https://issues.apache.org/jira/browse/DLAB-256 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > > Currently version node js for SSN is 8.14 and for notebook is 6.16 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-256) Update nodejs & npm for notebooks
[ https://issues.apache.org/jira/browse/DLAB-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-256: --- Issue Type: Task (was: Sub-task) Parent: (was: DLAB-254) > Update nodejs & npm for notebooks > - > > Key: DLAB-256 > URL: https://issues.apache.org/jira/browse/DLAB-256 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > Currently version node js for SSN is 8.14 and for notebook is 6.16 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-255) Update Apache Zeppelin version
[ https://issues.apache.org/jira/browse/DLAB-255?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-255: --- Fix Version/s: (was: v.2.3) > Update Apache Zeppelin version > --- > > Key: DLAB-255 > URL: https://issues.apache.org/jira/browse/DLAB-255 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Attachments: Azure Data Lake.txt, Azure adl.PNG, DP1.2-Zeppelin-local > kernel.png, Rspark.png, Zeppelin scala.txt, Zeppelin_py2_Dataptoc-1-2.png, > Zeppelin_sparkR.txt > > > By date 25/01/2019 version of Apache Zeppelin version is 8.0.0 > Update to version 8.1.0 (in this version job url track is fixed) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-427) Investigate possibility to not specify repository creds in plain text
[ https://issues.apache.org/jira/browse/DLAB-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-427: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Investigate possibility to not specify repository creds in plain text > - > > Key: DLAB-427 > URL: https://issues.apache.org/jira/browse/DLAB-427 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian > Fix For: v.2.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Deleted] (DLAB-254) Update 3-d party software to new stable versions
[ https://issues.apache.org/jira/browse/DLAB-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-254: --- > Update 3-d party software to new stable versions > > > Key: DLAB-254 > URL: https://issues.apache.org/jira/browse/DLAB-254 > Project: Apache DLab > Issue Type: New Feature >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-728) Integration with KeyCloak
[ https://issues.apache.org/jira/browse/DLAB-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-728: --- Summary: Integration with KeyCloak (was: Investigation: Integration with KeyCloak) > Integration with KeyCloak > -- > > Key: DLAB-728 > URL: https://issues.apache.org/jira/browse/DLAB-728 > Project: Apache DLab > Issue Type: Task > Components: Authentication and authorization >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-400) Use s3 client region that specified in billing.yml
[ https://issues.apache.org/jira/browse/DLAB-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-400: --- Fix Version/s: v.2.2 > Use s3 client region that specified in billing.yml > -- > > Key: DLAB-400 > URL: https://issues.apache.org/jira/browse/DLAB-400 > Project: Apache DLab > Issue Type: Sub-task > Components: DLab Old >Reporter: Bohdan Hliva >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Debian, backend > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-400) Use s3 client region that specified in billing.yml
[ https://issues.apache.org/jira/browse/DLAB-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-400: --- Sprint: Apache DLab release 2.2 > Use s3 client region that specified in billing.yml > -- > > Key: DLAB-400 > URL: https://issues.apache.org/jira/browse/DLAB-400 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Bohdan Hliva >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Debian, backend > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-400) Use s3 client region that specified in billing.yml
[ https://issues.apache.org/jira/browse/DLAB-400?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-400: --- Issue Type: Task (was: Sub-task) Parent: (was: DLAB-249) > Use s3 client region that specified in billing.yml > -- > > Key: DLAB-400 > URL: https://issues.apache.org/jira/browse/DLAB-400 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Bohdan Hliva >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Debian, backend > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Deleted] (DLAB-658) Provision service
[ https://issues.apache.org/jira/browse/DLAB-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-658: --- > Provision service > - > > Key: DLAB-658 > URL: https://issues.apache.org/jira/browse/DLAB-658 > Project: Apache DLab > Issue Type: Sub-task >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Deleted] (DLAB-335) [K8s]: Automate DLab SSN deployment
[ https://issues.apache.org/jira/browse/DLAB-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska deleted DLAB-335: --- > [K8s]: Automate DLab SSN deployment > --- > > Key: DLAB-335 > URL: https://issues.apache.org/jira/browse/DLAB-335 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-745) Introduce Edge node per project
[ https://issues.apache.org/jira/browse/DLAB-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-745: --- Sprint: Apache DLab release 2.2 (was: Apache DLab release 2.3) > Introduce Edge node per project > --- > > Key: DLAB-745 > URL: https://issues.apache.org/jira/browse/DLAB-745 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > Fix For: v.2.2 > > > As as user I want to create instance when I am assigned on a project. > Now subnet, edge are created per user during edge creation. > And user can create notebook only after his edge node creation. > Remove edge node per user and add posibility to create notebook if user is > assigned at least per one project. > Subnet, and edge node, and shared_project_bucket should be created per > project. > Shared_project_bucket is shared within this project > Shared_bucket is created on step of SSN creation. Shared_bucket is shared > between the projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-745) Introduce Edge node per project
[ https://issues.apache.org/jira/browse/DLAB-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-745: --- Fix Version/s: (was: v.2.3) v.2.2 > Introduce Edge node per project > --- > > Key: DLAB-745 > URL: https://issues.apache.org/jira/browse/DLAB-745 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > Fix For: v.2.2 > > > As as user I want to create instance when I am assigned on a project. > Now subnet, edge are created per user during edge creation. > And user can create notebook only after his edge node creation. > Remove edge node per user and add posibility to create notebook if user is > assigned at least per one project. > Subnet, and edge node, and shared_project_bucket should be created per > project. > Shared_project_bucket is shared within this project > Shared_bucket is created on step of SSN creation. Shared_bucket is shared > between the projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-756) SSN on k8s
Vira Vitanska created DLAB-756: -- Summary: SSN on k8s Key: DLAB-756 URL: https://issues.apache.org/jira/browse/DLAB-756 Project: Apache DLab Issue Type: Epic Reporter: Vira Vitanska -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-755) Create/Edit/Delete project API
[ https://issues.apache.org/jira/browse/DLAB-755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-755: --- Component/s: (was: Project) DLab Main > Create/Edit/Delete project API > -- > > Key: DLAB-755 > URL: https://issues.apache.org/jira/browse/DLAB-755 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-761) UI
Vira Vitanska created DLAB-761: -- Summary: UI Key: DLAB-761 URL: https://issues.apache.org/jira/browse/DLAB-761 Project: Apache DLab Issue Type: Sub-task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleksandr Isniuk Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-728) Integration with KeyCloak
[ https://issues.apache.org/jira/browse/DLAB-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-728: --- Fix Version/s: (was: v.2.2) > Integration with KeyCloak > -- > > Key: DLAB-728 > URL: https://issues.apache.org/jira/browse/DLAB-728 > Project: Apache DLab > Issue Type: Epic > Components: Authentication and authorization >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-728) Integration with KeyCloak
[ https://issues.apache.org/jira/browse/DLAB-728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-728: --- Sprint: (was: Apache DLab release 2.2) > Integration with KeyCloak > -- > > Key: DLAB-728 > URL: https://issues.apache.org/jira/browse/DLAB-728 > Project: Apache DLab > Issue Type: Epic > Components: Authentication and authorization >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-750) [AWS]: Investigate how to billing is working (in terms of integration with athena)
[ https://issues.apache.org/jira/browse/DLAB-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-750: --- Description: Investigate how to billing is working (in terms of integration with athena) > [AWS]: Investigate how to billing is working (in terms of integration with > athena) > -- > > Key: DLAB-750 > URL: https://issues.apache.org/jira/browse/DLAB-750 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Back-end, Debian, RedHat > Fix For: v.2.2 > > > Investigate how to billing is working (in terms of integration with athena) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-750) [AWS]: Fix billing
[ https://issues.apache.org/jira/browse/DLAB-750?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-750: --- Summary: [AWS]: Fix billing (was: [AWS]: Investigate how to billing is working (in terms of integration with athena)) > [AWS]: Fix billing > -- > > Key: DLAB-750 > URL: https://issues.apache.org/jira/browse/DLAB-750 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, Back-end, Debian, RedHat > Fix For: v.2.2 > > > Investigate how to billing is working (in terms of integration with athena) -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-757) Replace security service with KeyCloak on back-end side
[ https://issues.apache.org/jira/browse/DLAB-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-757: --- Issue Type: Task (was: Sub-task) Parent: (was: DLAB-728) > Replace security service with KeyCloak on back-end side > --- > > Key: DLAB-757 > URL: https://issues.apache.org/jira/browse/DLAB-757 > Project: Apache DLab > Issue Type: Task > Components: Cloud endpoint >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-757) Replace security service with KeyCloak on back-end side
[ https://issues.apache.org/jira/browse/DLAB-757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-757: --- Sprint: Apache DLab release 2.2 > Replace security service with KeyCloak on back-end side > --- > > Key: DLAB-757 > URL: https://issues.apache.org/jira/browse/DLAB-757 > Project: Apache DLab > Issue Type: Task > Components: Cloud endpoint >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-754) Project management
Vira Vitanska created DLAB-754: -- Summary: Project management Key: DLAB-754 URL: https://issues.apache.org/jira/browse/DLAB-754 Project: Apache DLab Issue Type: Epic Components: Project Reporter: Vira Vitanska -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-630) [Admin]: Ability to create a project
[ https://issues.apache.org/jira/browse/DLAB-630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-630: --- Component/s: (was: DLab Main) Project > [Admin]: Ability to create a project > > > Key: DLAB-630 > URL: https://issues.apache.org/jira/browse/DLAB-630 > Project: Apache DLab > Issue Type: New Feature > Components: Project >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, GCP > Fix For: v.2.2 > > > As an Admin I want to create project(s) and view them, so that I can add > group/user(s) per project, assign roles per project, view what group/users > are in the project. > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located in ‘Project’ tab on ‘Administration’ page > # At least one endpoint is created > > *Description:* > Current functionality of 'Manage roles' moves to 'Project' tab and renames > ‘Manage project’. > Admin can create a project clicking 'Create project' button. ‘Manage > project’ popup appears which consists of: > *Step 1 (mandatory)* > - Project name - should be unique within all DLab [editable] > - Endpoint name - [editable] > - Endpoint - dropdown (AWS Account 1, AWS Account 2, GCP Account 1) [part of > config file] > - Project Tag: autogenerated, based on project name: dlab_project_name > (validation if tag already exists within projects in same account) [ editable] > *Step 2* > * Add a group (mandatory) > *Step 3* > * Assign shape/template (mandatory) > *Step 4* > * Add user(s) (optional) > * ‘Back’ button > * ‘Cancel’ button > * ‘Create’ button > If Admin clicks ‘Back’ button he returns to Step 3 > If Admin clicks ‘Cancel’ button the project is not added and ‘Manage project’ > popup is open. > If Admin clicks ‘Create button the project is added, appears in grid among > the other project, and ‘Manage project’ popup is open. > Grid on ‘Manage project’ consists of: > * Progect_name > * Group_name > * Roles > * Users > * Action > > *Acceptance criteria:* > # Admin is able to create a project > # Admin is able to return to the previous step on the project creation step > if admin has not clicked ‘Create’ button. > # Admin is able to view all existing project(s) > # The project_shared_bucket is created on Project creation step-> > # User has his home directory, BUT this folder will be accessible for > everyone [(v1) - SHORT TERM] > # User should have proper permission scheme applied later *[(v2) - LONG > TERM]* > # Example: project_bucket: home/user1, home/user2, shared > # Cloud Role is assigned per project NOT per user > # Roles per project is created - automatically > # It is forbidden to access to other user notebooks within same project on > identity provider level - [(v1) - SHORT TERM] > # Users works under his own identity. All actions are logged from that > username - *[(v2) - LONG TERM]* > # All edge nodes within project subnet - [(v1) - SHORT TERM] > # VPC is created - manually > 13.1. Multiple projects per 1 VPC > 13.2. Rare case: 1 Project ! VPC > # Subnet: > 14.1. We define Subnet CIDR via WebUI - automatically > 14.2. Subnet per 1 project -> Subnet CIDR to be defined on UI -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-743) Implement wizard project creation
[ https://issues.apache.org/jira/browse/DLAB-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-743: --- Component/s: (was: DLab Main) Project > Implement wizard project creation > - > > Key: DLAB-743 > URL: https://issues.apache.org/jira/browse/DLAB-743 > Project: Apache DLab > Issue Type: Improvement > Components: Project >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.2 > > > As an Admin I want to create a project via wizard template so that i can > create project without reading extra instructions > *Preconditions:* > # Admin is logged-in DLab > # Admin is located on ‘Administration’ page > *Acceptance criteria**:* > Given that I'm an Admin in a role of project creation > When I open the 'Project' page > Then the system shows me project creation steps > When I fill the name project and endpoints (I can choose of existing > endpoint(s) or create new) > And I click 'Next' button or step2 > Then the system shows me group creation and role adjusting > When I fill the 2st step of role I can choose of existing group or create > one, and adjust role and add user (optional) > And I click the 'Create' button > Then the system shows me a grid of existing project -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-745) Introduce Edge node per project
[ https://issues.apache.org/jira/browse/DLAB-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-745: --- Component/s: (was: DLab Main) Project > Introduce Edge node per project > --- > > Key: DLAB-745 > URL: https://issues.apache.org/jira/browse/DLAB-745 > Project: Apache DLab > Issue Type: Task > Components: Project >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: AWS, AZURE, Debian, GCP, RedHat > Fix For: v.2.2 > > > As as user I want to create instance when I am assigned on a project. > Now subnet, edge are created per user during edge creation. > And user can create notebook only after his edge node creation. > Remove edge node per user and add posibility to create notebook if user is > assigned at least per one project. > Subnet, and edge node, and shared_project_bucket should be created per > project. > Shared_project_bucket is shared within this project > Shared_bucket is created on step of SSN creation. Shared_bucket is shared > between the projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-759) [AWS]: Terraform (Helm) for SSN services deployment into k8s
Vira Vitanska created DLAB-759: -- Summary: [AWS]: Terraform (Helm) for SSN services deployment into k8s Key: DLAB-759 URL: https://issues.apache.org/jira/browse/DLAB-759 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleksandr Isniuk Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-762) Billing
Vira Vitanska created DLAB-762: -- Summary: Billing Key: DLAB-762 URL: https://issues.apache.org/jira/browse/DLAB-762 Project: Apache DLab Issue Type: Sub-task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleksandr Isniuk Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-605) Add NTP server to Nexus
[ https://issues.apache.org/jira/browse/DLAB-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-605: --- Sprint: (was: Apache DLab release 2.2) Fix Version/s: (was: v.2.2) > Add NTP server to Nexus > --- > > Key: DLAB-605 > URL: https://issues.apache.org/jira/browse/DLAB-605 > Project: Apache DLab > Issue Type: Task >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-408) Add docker images to Nexus
[ https://issues.apache.org/jira/browse/DLAB-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-408: --- Sprint: (was: Apache DLab release 2.2) Fix Version/s: (was: v.2.2) > Add docker images to Nexus > --- > > Key: DLAB-408 > URL: https://issues.apache.org/jira/browse/DLAB-408 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-427) Investigate possibility to not specify repository creds in plain text
[ https://issues.apache.org/jira/browse/DLAB-427?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-427: --- Sprint: (was: Apache DLab release 2.2) Fix Version/s: (was: v.2.2) > Investigate possibility to not specify repository creds in plain text > - > > Key: DLAB-427 > URL: https://issues.apache.org/jira/browse/DLAB-427 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-633) [Admin]: Ability to edit a project
[ https://issues.apache.org/jira/browse/DLAB-633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-633: --- Component/s: (was: DLab Main) Project > [Admin]: Ability to edit a project > -- > > Key: DLAB-633 > URL: https://issues.apache.org/jira/browse/DLAB-633 > Project: Apache DLab > Issue Type: New Feature > Components: Project >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, GCP > Fix For: v.2.2 > > > As an Admin I want to edit project(s), so that I can add or remove user(s). > > *Preconditions:* > # Admin is logged-in DLab > # Admin is located in ‘Project’ tab on ‘Administration’ page > # At least one project is created > > *Description:* > If Admin clicks action menu for related project ‘Manage project’ popup > appears. > Admin can remove the user from a project hitting on removing icon for > appropriate user and in ‘users’ column and confirm the action. > Admin can add user typing the username in users column and confirm the action. > > *Acceptance criteria:* > # Admin is able to remove user from a project > # Admin is able to add user to a project -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-752) [AWS]: Terraform for k8s SSN auto-creation and configuration
[ https://issues.apache.org/jira/browse/DLAB-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-752: --- Summary: [AWS]: Terraform for k8s SSN auto-creation and configuration (was: Create Terraform scripts to automate K8S deployment) > [AWS]: Terraform for k8s SSN auto-creation and configuration > > > Key: DLAB-752 > URL: https://issues.apache.org/jira/browse/DLAB-752 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-757) Replace security service with KeyCloak on back-end side
Vira Vitanska created DLAB-757: -- Summary: Replace security service with KeyCloak on back-end side Key: DLAB-757 URL: https://issues.apache.org/jira/browse/DLAB-757 Project: Apache DLab Issue Type: Sub-task Components: Cloud endpoint Reporter: Vira Vitanska Assignee: Bohdan Hliva Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-760) Mongo (HA mode)
Vira Vitanska created DLAB-760: -- Summary: Mongo (HA mode) Key: DLAB-760 URL: https://issues.apache.org/jira/browse/DLAB-760 Project: Apache DLab Issue Type: Sub-task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleksandr Isniuk Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-758) Replace security service with KeyCloak on front-end side
[ https://issues.apache.org/jira/browse/DLAB-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-758: --- Issue Type: Task (was: Sub-task) Parent: (was: DLAB-728) > Replace security service with KeyCloak on front-end side > > > Key: DLAB-758 > URL: https://issues.apache.org/jira/browse/DLAB-758 > Project: Apache DLab > Issue Type: Task > Components: Cloud endpoint >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-758) Replace security service with KeyCloak on front-end side
[ https://issues.apache.org/jira/browse/DLAB-758?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-758: --- Sprint: Apache DLab release 2.2 > Replace security service with KeyCloak on front-end side > > > Key: DLAB-758 > URL: https://issues.apache.org/jira/browse/DLAB-758 > Project: Apache DLab > Issue Type: Task > Components: Cloud endpoint >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-379) Investigate possibility to access EMR endpoint from SSN
[ https://issues.apache.org/jira/browse/DLAB-379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-379: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Investigate possibility to access EMR endpoint from SSN > --- > > Key: DLAB-379 > URL: https://issues.apache.org/jira/browse/DLAB-379 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-423) Add support of another repository to Dataengine-service
[ https://issues.apache.org/jira/browse/DLAB-423?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-423: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Add support of another repository to Dataengine-service > --- > > Key: DLAB-423 > URL: https://issues.apache.org/jira/browse/DLAB-423 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-425) Parameterize repository configuration
[ https://issues.apache.org/jira/browse/DLAB-425?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-425: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Parameterize repository configuration > - > > Key: DLAB-425 > URL: https://issues.apache.org/jira/browse/DLAB-425 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-347) Add support of DLab repository to DeepLearning
[ https://issues.apache.org/jira/browse/DLAB-347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-347: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Add support of DLab repository to DeepLearning > -- > > Key: DLAB-347 > URL: https://issues.apache.org/jira/browse/DLAB-347 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-408) Add docker images to Nexus
[ https://issues.apache.org/jira/browse/DLAB-408?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-408: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Add docker images to Nexus > --- > > Key: DLAB-408 > URL: https://issues.apache.org/jira/browse/DLAB-408 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps > Fix For: v.2.3 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-354) Nexus certificate should be added to trusted CA repository
[ https://issues.apache.org/jira/browse/DLAB-354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-354: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Nexus certificate should be added to trusted CA repository > -- > > Key: DLAB-354 > URL: https://issues.apache.org/jira/browse/DLAB-354 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-350) Add support of DLab repository to Tensor + Rstudio
[ https://issues.apache.org/jira/browse/DLAB-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-350: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Add support of DLab repository to Tensor + Rstudio > -- > > Key: DLAB-350 > URL: https://issues.apache.org/jira/browse/DLAB-350 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-368) Investigate possibility to keep conf files in one place
[ https://issues.apache.org/jira/browse/DLAB-368?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-368: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Investigate possibility to keep conf files in one place > --- > > Key: DLAB-368 > URL: https://issues.apache.org/jira/browse/DLAB-368 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-357) Add waiter for Nexus service
[ https://issues.apache.org/jira/browse/DLAB-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-357: --- Parent: (was: DLAB-249) Issue Type: Task (was: Sub-task) > Add waiter for Nexus service > > > Key: DLAB-357 > URL: https://issues.apache.org/jira/browse/DLAB-357 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Oleh Martushevskyi >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps > Fix For: v.2.2 > > > In order to not use try - except, waiter should be added to get status of > Nexus service -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
