[jira] [Issue Comment Deleted] (DLAB-390) [GCP]: Rstudio startiing fails (previously it was stopped)
[ https://issues.apache.org/jira/browse/DLAB-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Demyan Mysakovets updated DLAB-390: --- Comment: was deleted (was: This failure reproduces on Notebooks with clusters. Without cluster Notebook boots properly after being stoped.) > [GCP]: Rstudio startiing fails (previously it was stopped) > -- > > Key: DLAB-390 > URL: https://issues.apache.org/jira/browse/DLAB-390 > Project: Apache DLab > Issue Type: Bug > Environment: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: DevOps > Fix For: v.1.1 > > Attachments: RStudio starting.PNG, jup-error.png > > > *Preconditions:* > RStudio is in 'stopped' status > *Steps to reproduce:* > 1. Start RStudio > *Actual result:* > RStudio starting fails with error > *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 > (tried 100 times)* > !RStudio starting.PNG! > *Expected result:* > RStudio starting 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] [Created] (DLAB-416) Front-end
Vira Vitanska created DLAB-416: -- Summary: Front-end Key: DLAB-416 URL: https://issues.apache.org/jira/browse/DLAB-416 Project: Apache DLab Issue Type: Sub-task Reporter: Vira Vitanska Assignee: Andriana Kovalyshyn -- 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-415) Back-end
Vira Vitanska created DLAB-415: -- Summary: Back-end Key: DLAB-415 URL: https://issues.apache.org/jira/browse/DLAB-415 Project: Apache DLab Issue Type: Sub-task Reporter: Vira Vitanska Assignee: Bohdan Hliva -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-411) Update documentation to release 1.1
[ https://issues.apache.org/jira/browse/DLAB-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-411: --- Summary: Update documentation to release 1.1 (was: Update documentation) > Update documentation to release 1.1 > --- > > Key: DLAB-411 > URL: https://issues.apache.org/jira/browse/DLAB-411 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Priority: Major > Fix For: v.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-395) [Inactivity time]: UI changes for scheduler
[ https://issues.apache.org/jira/browse/DLAB-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-395: --- Description: *1.* Remove note: *'NOTE: to enable the scheduler at least one weekday should be specified.'* *2.* Remove error handling if scheduler is not set: !Error handling.PNG! *3*. The latest unchecked day should have the color as unselected one: !Color days.PNG! *3.* After clicking 'Save' button for 'Inactive time' scheduler popup should be closed *4.* 'Save' button should be enabled only after filing of mandatory field??? *5.* Rename label 'Inactivity time' by 'Scheduler by inactivity, min' *6.* Rename label 'Enable scheduler' by 'Scheduler by time' *7.* If 'inactivity time' is enable the setting scheduler by manual should not be visible (hide it) *8.* The default value for Inactivity time should be 120 *9.* If items are disabled they should have the same color. For now value of 'select offset' has another color: !Select offset disabled.PNG! was: *1.* Remove note: *'NOTE: to enable the scheduler at least one weekday should be specified.'* *2.* Remove error handling if scheduler is not set: !Error handling.PNG! *3*. The latest unchecked day should have the color as unselected one: !Color days.PNG! *3.* After clicking 'Save' button for 'Inactive time' scheduler popup should be closed *4.* 'Save' button should be enabled only after filing of mandatory field??? *5.* Replace label 'Inactivity time' by 'By inactivity time, min' *6.* If 'inactivity time' is enable the setting scheduler by manual should not be visible (hide it) *7.* The default valu for Inactivity time shoild be 120 *8.* If items are disabled they should have the same color. For now value of 'select offset' has another color: !Select offset disabled.PNG! > [Inactivity time]: UI changes for scheduler > --- > > Key: DLAB-395 > URL: https://issues.apache.org/jira/browse/DLAB-395 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Front-end > Fix For: v.1.1 > > Attachments: Color days.PNG, Error handling.PNG, Select offset > disabled.PNG > > > *1.* Remove note: *'NOTE: to enable the scheduler at least one weekday > should be specified.'* > *2.* Remove error handling if scheduler is not set: > !Error handling.PNG! > *3*. The latest unchecked day should have the color as unselected one: > !Color days.PNG! > *3.* After clicking 'Save' button for 'Inactive time' scheduler popup should > be closed > *4.* 'Save' button should be enabled only after filing of mandatory field??? > *5.* Rename label 'Inactivity time' by 'Scheduler by inactivity, min' > *6.* Rename label 'Enable scheduler' by 'Scheduler by time' > *7.* If 'inactivity time' is enable the setting scheduler by manual should > not be visible (hide it) > *8.* The default value for Inactivity time should be 120 > *9.* If items are disabled they should have the same color. For now value of > 'select offset' has another color: > !Select offset disabled.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-412) Add instruction about scheduler by inactivity to user guide
[ https://issues.apache.org/jira/browse/DLAB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-412: --- Issue Type: Sub-task (was: Task) Parent: DLAB-411 > Add instruction about scheduler by inactivity to user guide > - > > Key: DLAB-412 > URL: https://issues.apache.org/jira/browse/DLAB-412 > Project: Apache DLab > Issue Type: Sub-task >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Fix For: v.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-412) Add instruction about scheduler by inactivity to user guide
[ https://issues.apache.org/jira/browse/DLAB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-412: --- Issue Type: Task (was: Epic) > Add instruction about scheduler by inactivity to user guide > - > > Key: DLAB-412 > URL: https://issues.apache.org/jira/browse/DLAB-412 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Fix For: v.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] [Created] (DLAB-412) Add instruction about scheduler by inactivity ti user guide
Vira Vitanska created DLAB-412: -- Summary: Add instruction about scheduler by inactivity ti user guide Key: DLAB-412 URL: https://issues.apache.org/jira/browse/DLAB-412 Project: Apache DLab Issue Type: Epic Reporter: Vira Vitanska Assignee: Vira Vitanska Fix For: v.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-412) Add instruction about scheduler by inactivity to user guide
[ https://issues.apache.org/jira/browse/DLAB-412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-412: --- Summary: Add instruction about scheduler by inactivity to user guide (was: Add instruction about scheduler by inactivity ti user guide ) > Add instruction about scheduler by inactivity to user guide > - > > Key: DLAB-412 > URL: https://issues.apache.org/jira/browse/DLAB-412 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Fix For: v.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] [Created] (DLAB-413) [AWS][EMR]: Replace hyphen by underscore in interpreters name for Zeppelin
Vira Vitanska created DLAB-413: -- Summary: [AWS][EMR]: Replace hyphen by underscore in interpreters name for Zeppelin Key: DLAB-413 URL: https://issues.apache.org/jira/browse/DLAB-413 Project: Apache DLab Issue Type: Task Reporter: Vira Vitanska Assignee: Demyan Mysakovets Fix For: v.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] [Commented] (DLAB-390) [GCP]: Rstudio startiing fails (previously it was stopped)
[ https://issues.apache.org/jira/browse/DLAB-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769349#comment-16769349 ] Demyan Mysakovets commented on DLAB-390: This failure reproduces on Notebooks with clusters. Without cluster Notebook boots properly after being stoped. > [GCP]: Rstudio startiing fails (previously it was stopped) > -- > > Key: DLAB-390 > URL: https://issues.apache.org/jira/browse/DLAB-390 > Project: Apache DLab > Issue Type: Bug > Environment: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: DevOps > Fix For: v.1.1 > > Attachments: RStudio starting.PNG, jup-error.png > > > *Preconditions:* > RStudio is in 'stopped' status > *Steps to reproduce:* > 1. Start RStudio > *Actual result:* > RStudio starting fails with error > *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 > (tried 100 times)* > !RStudio starting.PNG! > *Expected result:* > RStudio starting 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-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: --- Summary: [AWS][EMR]: Replace hyphen by underscore in interpreter name for Zeppelin (was: [AWS][EMR]: Replace hyphen by underscore in interpreters name for Zeppelin) > [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 >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: DevOps > Fix For: v.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] [Resolved] (DLAB-330) [Autotest]: Playbook running for Apache Zeppelin fails due to using of wrong name of EMR kernel
[ https://issues.apache.org/jira/browse/DLAB-330?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska resolved DLAB-330. Resolution: Won't Fix It is only Apache Zeppelin issue from their side. >From our side it will be fixed by task >https://issues.apache.org/jira/browse/DLAB-413 > [Autotest]: Playbook running for Apache Zeppelin fails due to using of wrong > name of EMR kernel > --- > > Key: DLAB-330 > URL: https://issues.apache.org/jira/browse/DLAB-330 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Minor > Labels: DevOps > Fix For: v.1.1 > > Attachments: Autotest.PNG, Py2_preparartion.PNG, Remote kernel.PNG > > > A bug was found on AWS [RedHat] > > *Steps to reproduce:* > 1. Run Autotest for Apache Zeppelin using EMR > > *Actual result:* > Playbook running fails > !Autotest.PNG! > *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] [Created] (DLAB-411) Update documenttion
Vira Vitanska created DLAB-411: -- Summary: Update documenttion Key: DLAB-411 URL: https://issues.apache.org/jira/browse/DLAB-411 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
[GitHub] bhliva merged pull request #3: DLAB-406
bhliva merged pull request #3: DLAB-406 URL: https://github.com/apache/incubator-dlab/pull/3 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-406) [Scheduler on idle]: Prevent scheduler by inactivity execution in case if computational resource are in statuses 'creating', 'terminating', 'configuring'
[ https://issues.apache.org/jira/browse/DLAB-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated DLAB-406: Labels: Back-end pull-request-available (was: Back-end) > [Scheduler on idle]: Prevent scheduler by inactivity execution in case if > computational resource are in statuses 'creating', 'terminating', > 'configuring' > - > > Key: DLAB-406 > URL: https://issues.apache.org/jira/browse/DLAB-406 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, pull-request-available > Fix For: v.1.1 > > > *Preconditions:* > Computational resource is in status creating/configuring/terminating > *Steps to reproduce:* > 1. Execute scheduler by inactivity for notebook > *Actual result:* > Computational resource is in failed status on DLab UI > *Expected result:* > Prevent scheduler by inactivity execution -- 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-406) [Scheduler on idle]: Prevent scheduler by inactivity execution in case if computational resource are in statuses 'creating', 'terminating', 'configuring'
[ https://issues.apache.org/jira/browse/DLAB-406?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bohdan Hliva updated DLAB-406: -- Description: *Preconditions:* Computational resource is in status creating/configuring/terminating *Steps to reproduce:* 1. Execute scheduler by inactivity for notebook *Actual result:* Computational resource is in failed status on DLab UI *Expected result:* Prevent scheduler by inactivity execution was: *Preconditions:* Computational resource is in status creating/configuring/terminating/running *Steps to reproduce:* 1. Execute scheduler by inactivity for notebook *Actual result:* Computational resource is in failed status on DLab UI *Expected result:* Prevent scheduler by inactivity execution > [Scheduler on idle]: Prevent scheduler by inactivity execution in case if > computational resource are in statuses 'creating', 'terminating', > 'configuring' > - > > Key: DLAB-406 > URL: https://issues.apache.org/jira/browse/DLAB-406 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end > Fix For: v.1.1 > > > *Preconditions:* > Computational resource is in status creating/configuring/terminating > *Steps to reproduce:* > 1. Execute scheduler by inactivity for notebook > *Actual result:* > Computational resource is in failed status on DLab UI > *Expected result:* > Prevent scheduler by inactivity execution -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-390) [GCP]: Rstudio startiing fails (previously it was stopped)
[ https://issues.apache.org/jira/browse/DLAB-390?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16769224#comment-16769224 ] Demyan Mysakovets commented on DLAB-390: The same error occurred in Jupyter. !jup-error.png! > [GCP]: Rstudio startiing fails (previously it was stopped) > -- > > Key: DLAB-390 > URL: https://issues.apache.org/jira/browse/DLAB-390 > Project: Apache DLab > Issue Type: Bug > Environment: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: DevOps > Fix For: v.1.1 > > Attachments: RStudio starting.PNG, jup-error.png > > > *Preconditions:* > RStudio is in 'stopped' status > *Steps to reproduce:* > 1. Start RStudio > *Actual result:* > RStudio starting fails with error > *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 > (tried 100 times)* > !RStudio starting.PNG! > *Expected result:* > RStudio starting 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] [Created] (DLAB-409) Add jars to Nexus
Vira Vitanska created DLAB-409: -- Summary: Add jars to Nexus Key: DLAB-409 URL: https://issues.apache.org/jira/browse/DLAB-409 Project: Apache DLab Issue Type: Sub-task Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.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] [Assigned] (DLAB-407) All software versions which are hard-coded should be added in conf file
[ https://issues.apache.org/jira/browse/DLAB-407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-407: -- Assignee: Oleh Martushevskyi > All software versions which are hard-coded should be added in conf file > --- > > Key: DLAB-407 > URL: https://issues.apache.org/jira/browse/DLAB-407 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: DevOps > Fix For: v.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] [Created] (DLAB-407) All software versions which are hard-coded should be added in conf file
Vira Vitanska created DLAB-407: -- Summary: All software versions which are hard-coded should be added in conf file Key: DLAB-407 URL: https://issues.apache.org/jira/browse/DLAB-407 Project: Apache DLab Issue Type: Task Reporter: Vira Vitanska Fix For: v.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] [Resolved] (DLAB-399) Fix issue with connecting to S3 for billing service
[ https://issues.apache.org/jira/browse/DLAB-399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Oleh Martushevskyi resolved DLAB-399. - Resolution: Done > Fix issue with connecting to S3 for billing service > --- > > Key: DLAB-399 > URL: https://issues.apache.org/jira/browse/DLAB-399 > Project: Apache DLab > Issue Type: Sub-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] [Assigned] (DLAB-404) [Scheduler on idle]: Inactivity scheduler for notebook should check if job is running on remote kernels (Data Engine/ Data Engine Service)
[ https://issues.apache.org/jira/browse/DLAB-404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bohdan Hliva reassigned DLAB-404: - Assignee: Oleksandr Isniuk (was: Bohdan Hliva) [~i.oleksandr] it looks like it is more devops task > [Scheduler on idle]: Inactivity scheduler for notebook should check if job is > running on remote kernels (Data Engine/ Data Engine Service) > -- > > Key: DLAB-404 > URL: https://issues.apache.org/jira/browse/DLAB-404 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Back-end > Fix For: v.1.1 > > > *Preconditions:* > 1. Data Engine or Data Engine Service is created > 2. Job is running on remote kernel > 3. Job on local kernel was run more than 10 minutes > *Steps to reproduce:* > 1. Set scheduler by inactivity only for notebook for 10 minutes > *Actual result:* > 1. Notebok is stoping despite job is running on remote kernel > *Expected result:* > 1. Notebook is running > 2. Notebook will stop if any jobs are not running on remote kernel -- 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
