[jira] [Updated] (DLAB-33) [Data Engine]: Add Spot instances functionality
[ https://issues.apache.org/jira/browse/DLAB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-33: -- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > [Data Engine]: Add Spot instances functionality > --- > > Key: DLAB-33 > URL: https://issues.apache.org/jira/browse/DLAB-33 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, RedHat > > As a user i want to use spot functionality during Spark cluster creation so > that I can reduce financial charges on AWS/GCP/MS Azure. > > *Acceptance criteria:* > 1. it should be check box for spot instance on Spark cluster creation popup > 2. check box for Low spot instance should be checked off by default > 3. if user unchecks check box for spot instance and hits 'Create' button a > Spark cluster will be created without spot price > 4. if user checks off check box for spot instance and hits 'Create' button a > Spark cluster will be created with spot price -- This message was sent by Atlassian 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-158) [Azure]: Billing is not available
[ https://issues.apache.org/jira/browse/DLAB-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-158: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: Azure > [Azure]: Billing is not available > - > > Key: DLAB-158 > URL: https://issues.apache.org/jira/browse/DLAB-158 > Project: Apache DLab > Issue Type: Bug > Components: Azure >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Critical > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > *Preconditions:* > Environment is created a day ago > *Steps to reproduce:* > 1. go to "Billing report" > *Actual result:* > Billing information is absent on "Billing report" page and "Billing detail" > popup > *Expected result:* > Billing information is present on "Billing report" page and "Billing detail" > 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-240) [Billing Report]: User's value in dropdown list should be in lower case
[ https://issues.apache.org/jira/browse/DLAB-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-240: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: Azure AWS > [Billing Report]: User's value in dropdown list should be in lower case > --- > > Key: DLAB-240 > URL: https://issues.apache.org/jira/browse/DLAB-240 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > Attachments: image-2018-12-20-10-48-01-520.png > > > *Preconditions:* > 1. environment is created > 2. billing is available > 3. "Billing Report" page is open > Steps to reproduce: > 1. click "select user" drop down list > *Actual result:* > User's value is in lower and upper case > !image-2018-12-20-10-48-01-520.png! > > *Expected result:* > User's value is in lower case -- This message was sent by Atlassian 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: --- Summary: Refactor libraries for Notebooks and clusters (was: [AWS][GCP]: Refactor libraries for Notebooks and clusters) > 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: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.2 > > > *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-38) [Implementation]: SSO on GCP
[ https://issues.apache.org/jira/browse/DLAB-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-38: -- Labels: Debian (was: Debian RedHat) > [Implementation]: SSO on GCP > > > Key: DLAB-38 > URL: https://issues.apache.org/jira/browse/DLAB-38 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian > > As a user I want to have SSO on DLAB for GCP, so that I would like to login > to DLab through it. > > *Acceptance criteria:* > 1. there are two buttons on login page: 'Login' and ''Login with GCP' > 2. if user enters username and password he should choose 'Login' button. > After clicking login button after that user is logged in DLab > 3. if user does not enter username and password he should choose 'Login with > GCP' button after that user is logged in DLab -- This message was sent by Atlassian 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-434) [Billing]: Filter by shared resource does not work
[ https://issues.apache.org/jira/browse/DLAB-434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-434: --- Labels: Debian Front-end RedHat pull-request-available (was: Front-end pull-request-available) Component/s: Azure AWS > [Billing]: Filter by shared resource does not work > -- > > Key: DLAB-434 > URL: https://issues.apache.org/jira/browse/DLAB-434 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Debian, Front-end, RedHat, pull-request-available > Attachments: Shared resource.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > 1. Billing is available > 2. Billing report page is opened > *Steps to reproduce:* > 1. Filter by shared resource > *Actual result:* > Filter output is emty > !Shared resource.png! > *Expected result:* > Filter output includes only values for shared resource > ___ > Shared resource in dropdown list should start from upper case -- This message was sent by Atlassian 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-364) Replace picker date component on 'Billing report' page
[ https://issues.apache.org/jira/browse/DLAB-364?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-364: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: Azure AWS > Replace picker date component on 'Billing report' page > -- > > Key: DLAB-364 > URL: https://issues.apache.org/jira/browse/DLAB-364 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.2 > > > Current picker date component has been not supported yet. > Find new one and replace picker date component by another. -- This message was sent by Atlassian 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-249) [DevOps]: Add support of local repository for DLab
[ https://issues.apache.org/jira/browse/DLAB-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-249: --- Labels: Debian DevOps (was: DevOps) Component/s: AWS > [DevOps]: Add support of local repository for DLab > -- > > Key: DLAB-249 > URL: https://issues.apache.org/jira/browse/DLAB-249 > Project: Apache DLab > Issue Type: New Feature > Components: AWS >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps > Fix For: v.2.2 > > Attachments: local.png > > > 1. It should be the single source from which changes will be performed. > 2. Go and distribute all traffic through this sandbox -- This message was sent by Atlassian 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-468) Libraries management
[ https://issues.apache.org/jira/browse/DLAB-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-468: --- Summary: Libraries management (was: Library management) > Libraries management > > > Key: DLAB-468 > URL: https://issues.apache.org/jira/browse/DLAB-468 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-468) Libraries management
[ https://issues.apache.org/jira/browse/DLAB-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-468: --- Epic Name: Libraries management (was: Library management) > Libraries management > > > Key: DLAB-468 > URL: https://issues.apache.org/jira/browse/DLAB-468 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-481) Data engine
[ https://issues.apache.org/jira/browse/DLAB-481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-481: --- Summary: Data engine (was: Data Engine) > Data engine > --- > > Key: DLAB-481 > URL: https://issues.apache.org/jira/browse/DLAB-481 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-56) Ability to support more than one Data engine of different versions
[ https://issues.apache.org/jira/browse/DLAB-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-56: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS Summary: Ability to support more than one Data engine of different versions (was: Ability to support more than one spark cluster of different versions) > Ability to support more than one Data engine of different versions > -- > > Key: DLAB-56 > URL: https://issues.apache.org/jira/browse/DLAB-56 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > As a user I want to choose from DLAB UI what version of Spark cluster can be > deployed on notebook, so that I am not connected only with one version of > Spark cluster. > > *Acceptance criteria:* > # in drop down list for spark cluster on create computational resources > popup there are more than one spark cluster for choice > # user can deploy different version of Spark cluster on one notebook > > _***Currently we support only 1 version of spark cluster_ -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-108) [RStudio]: Terminating spark cluster behaves wrong for resources with similar name
[ https://issues.apache.org/jira/browse/DLAB-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-108: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > [RStudio]: Terminating spark cluster behaves wrong for resources with similar > name > -- > > Key: DLAB-108 > URL: https://issues.apache.org/jira/browse/DLAB-108 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleh Moskovych >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > Attachments: image-2018-12-20-13-15-16-285.png, > image-2018-12-20-13-15-43-310.png > > > When there more than 1 spark cluster created with similar name (e.g. cluster, > cluster1) on RStudo action terminating for cluster also removed remote > kernels for cluster1 from kernels list) > *Preconditions:* > 1. two spark clusters are created on RStudio with names "spark" and "spark1" > *Steps to reproduce:* > 1. terminate cluster with name "spark" > *Actual result:* > 1. cluster with name "spark" is terminated > 2. remote kernel of cluster with name "spark" is deleted from kernels list > 3. cluster with name "spark1" is running > 4. remote kernel of cluster with name "spark1" is deleted from kernels list > *Expected result:* > 1. cluster with name "spark" is terminated > 2. remote kernel of cluster with name "spark" is deleted from kernels list > 3. cluster with name "spark1" is running > 4. remote kernel of cluster with name "spark1" is available in kernels list -- This message was sent by Atlassian 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-153) Cost details dialog fixes. Date should be in one line on billing detail popup
[ https://issues.apache.org/jira/browse/DLAB-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-153: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: Azure AWS > Cost details dialog fixes. Date should be in one line on billing detail popup > - > > Key: DLAB-153 > URL: https://issues.apache.org/jira/browse/DLAB-153 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *Preconditions:* > # Billing is available > # 'Resources_list' page is open > > *Steps to reproduce:* > 1. Click billing detail of notebook > > *Actual result:* > Start date is in two rows > End date is in one row > > *Expected result:* > Start date is in one row (increase column width for start date) > End date is in one row > Column widths of start/end date are equal > -- This message was sent by Atlassian 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-23) [GCP]: Billing
[ https://issues.apache.org/jira/browse/DLAB-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-23: -- Labels: Back-end Debian (was: Back-end) Component/s: GCP > [GCP]: Billing > -- > > Key: DLAB-23 > URL: https://issues.apache.org/jira/browse/DLAB-23 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian > Fix For: v.2.2 > > > As a user I want to see charges of instances so that I can monitor financial > situation. > > *Acceptance criteria:* > # it should be billing report page > # user can filter values on billing report page > # user can export data from billing report page > # user can see billing details > -- This message was sent by Atlassian 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-465) [Azure]: Inactivity file does not have ID for Data Engine Cluster
[ https://issues.apache.org/jira/browse/DLAB-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-465: --- Summary: [Azure]: Inactivity file does not have ID for Data Engine Cluster (was: Inactivity file does not have ID for Data Engine Cluster) > [Azure]: Inactivity file does not have ID for Data Engine Cluster > - > > Key: DLAB-465 > URL: https://issues.apache.org/jira/browse/DLAB-465 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.2 > > Attachments: Data Engine Starting.PNG, Inactivity.PNG > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > Data Engine Cluster is created > > *Steps to reproduce:* > # Go to /opt/inactivity > # Run ls -la > > *Actual result:* > File name for Data Engine Cluster is '_inactivity' > > *Expected result:* > File name for Data Engine Cluster is 'ID_inactivity' > > _ > The bug was found if start data Engine Cluster fron DLab UI (previously Data > Engine Cluster was stopped from DLab UI) > *Data Engine cluster starting fails (it was previously stopped):* > !Data Engine Starting.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-482) [GCP][Data Engine]: Spark Configuration fails on process of installing kernels
[ https://issues.apache.org/jira/browse/DLAB-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-482: --- Labels: Debian DevOps (was: DevOps) > [GCP][Data Engine]: Spark Configuration fails on process of installing > kernels > > > Key: DLAB-482 > URL: https://issues.apache.org/jira/browse/DLAB-482 > Project: Apache DLab > Issue Type: Bug > Components: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Critical > Labels: Debian, DevOps > Attachments: Spark configuration.PNG > > > The bug was found on notebooks: Jupyter, Rstudio, Apache Zeppelin > > *Preconditions:* > 1. Notebook is created > > *Steps to repdoduce:* > # Create Data Engine on Notebook > > *Actual result:* > Data Engine configuration fails: > !Spark configuration.PNG! > > Expected result: > Data Engine is 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-482) [GCP][Data Engine]: Spark Configuration fails on process of installing kernels
[ https://issues.apache.org/jira/browse/DLAB-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-482: --- Description: The bug was found on notebooks: Jupyter, RStudio, Apache Zeppelin *Preconditions:* 1. Notebook is created *Steps to repdoduce:* # Create Data Engine on Notebook *Actual result:* Data Engine configuration fails: !Spark configuration.PNG! *Expected result:* Data Engine is created successfully was: The bug was found on notebooks: Jupyter, Rstudio, Apache Zeppelin *Preconditions:* 1. Notebook is created *Steps to repdoduce:* # Create Data Engine on Notebook *Actual result:* Data Engine configuration fails: !Spark configuration.PNG! Expected result: Data Engine is created successfully > [GCP][Data Engine]: Spark Configuration fails on process of installing > kernels > > > Key: DLAB-482 > URL: https://issues.apache.org/jira/browse/DLAB-482 > Project: Apache DLab > Issue Type: Bug > Components: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Critical > Labels: Debian, DevOps > Attachments: Spark configuration.PNG > > > The bug was found on notebooks: Jupyter, RStudio, Apache Zeppelin > > *Preconditions:* > 1. Notebook is created > > *Steps to repdoduce:* > # Create Data Engine on Notebook > > *Actual result:* > Data Engine configuration fails: > !Spark configuration.PNG! > > *Expected result:* > Data Engine is 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-208) [GCP]: 'View Full billing Report For All Users' value should be absent in 'role' drop down list on 'Manage Roles' popup
[ https://issues.apache.org/jira/browse/DLAB-208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-208: --- Component/s: (was: Azure) (was: AWS) > [GCP]: 'View Full billing Report For All Users' value should be absent in > 'role' drop down list on 'Manage Roles' popup > --- > > Key: DLAB-208 > URL: https://issues.apache.org/jira/browse/DLAB-208 > Project: Apache DLab > Issue Type: Bug > Components: GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Minor > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > *Preconditions:* > # SSN is created > # 'Manage roles' popup is open > > *Steps to reproduce:* > # Click 'role' drop down list > > *Actual result:* > 'View Full billing Report For All Users' is present in drop down list > *Expected result:* > 'View Full billing Report For All Users' is absent in drop down list -- This message was sent by Atlassian 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-474) TensorFlow+RStudio
[ https://issues.apache.org/jira/browse/DLAB-474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-474: --- Summary: TensorFlow+RStudio (was: TensorFlow RStudio) > TensorFlow+RStudio > -- > > Key: DLAB-474 > URL: https://issues.apache.org/jira/browse/DLAB-474 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-467) Data engine service
[ https://issues.apache.org/jira/browse/DLAB-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-467: --- Epic Name: Data engine service (was: Billing report) Summary: Data engine service (was: Artifactory) > Data engine service > --- > > Key: DLAB-467 > URL: https://issues.apache.org/jira/browse/DLAB-467 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Major > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-33) [Data Engine]: Add Spot instances functionality
[ https://issues.apache.org/jira/browse/DLAB-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-33: -- Summary: [Data Engine]: Add Spot instances functionality (was: [Apache Spark Standalone]: Add Spot instances functionality) > [Data Engine]: Add Spot instances functionality > --- > > Key: DLAB-33 > URL: https://issues.apache.org/jira/browse/DLAB-33 > Project: Apache DLab > Issue Type: New Feature >Reporter: Vira Vitanska >Priority: Minor > > As a user i want to use spot functionality during Spark cluster creation so > that I can reduce financial charges on AWS/GCP/MS Azure. > > *Acceptance criteria:* > 1. it should be check box for spot instance on Spark cluster creation popup > 2. check box for Low spot instance should be checked off by default > 3. if user unchecks check box for spot instance and hits 'Create' button a > Spark cluster will be created without spot price > 4. if user checks off check box for spot instance and hits 'Create' button a > Spark cluster will be created with spot price -- This message was sent by Atlassian 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-321) [GCP][Spark Standalone cluster]: Playbook running fails using spark cluster kernel due to 'Class com.google.cloud.hadoop.fs.gcs.GoogleHadoopFileSystem not found'
[ https://issues.apache.org/jira/browse/DLAB-321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-321: --- Labels: Debian DevOps (was: DevOps) Component/s: GCP > [GCP][Spark Standalone cluster]: Playbook running fails using spark cluster > kernel due to 'Class com.google.cloud.hadoop.fs.gcs.GoogleHadoopFileSystem > not found' > - > > Key: DLAB-321 > URL: https://issues.apache.org/jira/browse/DLAB-321 > Project: Apache DLab > Issue Type: Bug > Components: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Critical > Labels: Debian, DevOps > Fix For: v.2.2 > > Attachments: GCP.PNG, GCP_autotest.PNG > > > *Steps to reproduce:* > # Run autotest on GCP for Data Engine or Create Spark cluster on > Jupyter/Zeppelin/Rstudio and run playbook by manual > > *Actual result:* > playbook running fails with error: > !GCP_autotest.PNG! > [AutoTests_GCP/91/console|http://35.166.222.81/view/AutoTests/job/AutoTests_GCP/91/console] > *Expected result:* > Autotest 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-483) Data engine service
Vira Vitanska created DLAB-483: -- Summary: Data engine service Key: DLAB-483 URL: https://issues.apache.org/jira/browse/DLAB-483 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-270) [Manage Environment]: Extra space between user and total budget
[ https://issues.apache.org/jira/browse/DLAB-270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-270: --- Component/s: (was: GCP) > [Manage Environment]: Extra space between user and total budget > --- > > Key: DLAB-270 > URL: https://issues.apache.org/jira/browse/DLAB-270 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *Preconditions:* > 1. Edge for one user is created > 2. "Environment Health Status" page is open > *Steps to reproduce:* > 1. click "Manage Environment" button > *Actual result:* > distance between user and total budget is too extra > !Manage environment.PNG! > *Expected result:* > decrease distance between user and total budget -- This message was sent by Atlassian 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-258) [Billing Report]: 'Creating Image' should be the same style as on the other pages
[ https://issues.apache.org/jira/browse/DLAB-258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-258: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: Azure AWS > [Billing Report]: 'Creating Image' should be the same style as on the other > pages > - > > Key: DLAB-258 > URL: https://issues.apache.org/jira/browse/DLAB-258 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Trivial > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > Attachments: image-2019-01-16-18-13-02-712.png, > image-2019-01-16-18-13-29-517.png, image-2019-01-16-18-13-39-451.png > > > *Preconditions:* > Notebook is created > *Steps to reproduce:* > 1. create image from Notebook > 2. go to 'Billing reports' > *Actual result:* > !image-2019-01-16-18-13-02-712.png! > !image-2019-01-16-18-13-39-451.png! > *Expected result:* > !image-2019-01-16-18-13-29-517.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-393) [Billing]: Value for shared resources should be named in user dropdown list
[ https://issues.apache.org/jira/browse/DLAB-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-393: --- Labels: Back-end Debian RedHat pull-request-available (was: Back-end pull-request-available) Component/s: Azure AWS > [Billing]: Value for shared resources should be named in user dropdown list > --- > > Key: DLAB-393 > URL: https://issues.apache.org/jira/browse/DLAB-393 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Minor > Labels: Back-end, Debian, RedHat, pull-request-available > Fix For: v.2.2 > > Attachments: Billing.PNG > > Time Spent: 20m > Remaining Estimate: 0h > > There empty values in user dropdown list for SBN, SSN-bucket, shared-bucket. > Value of 'Shared resource' should be in this empty values. > !Billing.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-292) Have a default limit on how many environments can be created by the user. Dlab admins can allow for a larger number upon proper justification
[ https://issues.apache.org/jira/browse/DLAB-292?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-292: --- Component/s: (was: GCP) > Have a default limit on how many environments can be created by the user. > Dlab admins can allow for a larger number upon proper justification > - > > Key: DLAB-292 > URL: https://issues.apache.org/jira/browse/DLAB-292 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > Currently admin can configure what instance shape can be allowed to create > for particular user or group, but it does not limit by quontity (only by > money) > > As an admin I want to manage how many quantities of instances can be allowed > to create per user/group > > *Acceptance criteria:* > # admin can set/alter sum of instances quantities which are allowed for > creating for user/group > # user is supposed to create only the sum of instances quantities (less or > equal the sum) which are allowed for creating for user/group > # user is not allowed to create more instances than it is permitted for him -- This message was sent by Atlassian 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-207) [AWS]: Shape 'C4.xlarge' for computational resource is absent in 'role' drop down list on 'Manage roles' popup
[ https://issues.apache.org/jira/browse/DLAB-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-207: --- Component/s: (was: GCP) (was: Azure) > [AWS]: Shape 'C4.xlarge' for computational resource is absent in 'role' drop > down list on 'Manage roles' popup > -- > > Key: DLAB-207 > URL: https://issues.apache.org/jira/browse/DLAB-207 > Project: Apache DLab > Issue Type: Bug > Components: AWS >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Bak-end, Debian, RedHat > Fix For: v.2.1 > > > *Preconditions:* > # SSN is created on AWS > # 'Manage roles' popup is open > > *Steps to reproduce:* > 1. Click 'role' drop down list > > *Actual result:* > Shape 'C4.xlarge' is absent in 'role' drop down list > *Expected result:* > Shape 'C4.xlarge' is present in 'role' drop down list > -- This message was sent by Atlassian 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-294) The warning updates for user only after second login if admin adjusts the quota
[ https://issues.apache.org/jira/browse/DLAB-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-294: --- Component/s: (was: GCP) > The warning updates for user only after second login if admin adjusts the > quota > --- > > Key: DLAB-294 > URL: https://issues.apache.org/jira/browse/DLAB-294 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *Preconditions:* > 1. two users have environments > 2. quota is set for budjet (user has already used his quota) > *Steps to reproduce:* > 1. update quota (increase limit) > *Actual result:* > 1. after the first login the warning is not updated (it is previous quota > value) > 2. after the second login the warning is updated > !warning.PNG! > *Expected result:* > after the first login the warning is updated > * > Rename button from 'Create' to 'Apply' on 'Manage environment' 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-465) [Azure]: Inactivity file does not have ID for Data Engine Cluster
[ https://issues.apache.org/jira/browse/DLAB-465?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-465: --- Component/s: (was: GCP) (was: AWS) > [Azure]: Inactivity file does not have ID for Data Engine Cluster > - > > Key: DLAB-465 > URL: https://issues.apache.org/jira/browse/DLAB-465 > Project: Apache DLab > Issue Type: Bug > Components: Azure >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.2 > > Attachments: Data Engine Starting.PNG, Inactivity.PNG > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > Data Engine Cluster is created > > *Steps to reproduce:* > # Go to /opt/inactivity > # Run ls -la > > *Actual result:* > File name for Data Engine Cluster is '_inactivity' > > *Expected result:* > File name for Data Engine Cluster is 'ID_inactivity' > > _ > The bug was found if start data Engine Cluster fron DLab UI (previously Data > Engine Cluster was stopped from DLab UI) > *Data Engine cluster starting fails (it was previously stopped):* > !Data Engine Starting.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-38) [Implementation]: SSO on GCP
[ https://issues.apache.org/jira/browse/DLAB-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-38: -- Component/s: GCP > [Implementation]: SSO on GCP > > > Key: DLAB-38 > URL: https://issues.apache.org/jira/browse/DLAB-38 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to have SSO on DLAB for GCP, so that I would like to login > to DLab through it. > > *Acceptance criteria:* > 1. there are two buttons on login page: 'Login' and ''Login with GCP' > 2. if user enters username and password he should choose 'Login' button. > After clicking login button after that user is logged in DLab > 3. if user does not enter username and password he should choose 'Login with > GCP' button after that user is logged in DLab -- This message was sent by Atlassian 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-285) [GCP]: Add possibility to create Notebook/ Data engine from images
[ https://issues.apache.org/jira/browse/DLAB-285?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-285: --- Summary: [GCP]: Add possibility to create Notebook/ Data engine from images (was: [GCP]: Add possibility to create Notebook/Spark cluster standalone from images) > [GCP]: Add possibility to create Notebook/ Data engine from images > -- > > Key: DLAB-285 > URL: https://issues.apache.org/jira/browse/DLAB-285 > Project: Apache DLab > Issue Type: New Feature >Reporter: Vira Vitanska >Priority: Major > Labels: DevOps > > As a user I want to create Notebook/Spark cluster standalone from image on GCP > *Acceptance criteria:* > 1. during notebook creation creates shared image which can be used to create > the next notebook of the same template > 2. Spark cluster standalone creation use Notebook's image -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-280) Remote kernel list for spark cluster is not updated after stop/start spark cluster
[ https://issues.apache.org/jira/browse/DLAB-280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-280: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Remote kernel list for spark cluster is not updated after stop/start spark > cluster > -- > > Key: DLAB-280 > URL: https://issues.apache.org/jira/browse/DLAB-280 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > Remote spark kernels are available in list for stopped spark cluster. > *Preconditions:* > Spark cluster is stopped on running notebook > *Steps to reproduce:* > 1. Go to link of notebook > 2. Choose list of kernels > *Actual result:* > Remote spark kernels are available in kernel list for stopped spark cluster > *Expected result:* > Remote spark kernels are removed from kernel list for stopped spark cluster -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-119) [Front-end]: Add possibility to tune EMR cluster
[ https://issues.apache.org/jira/browse/DLAB-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-119: --- Component/s: AWS > [Front-end]: Add possibility to tune EMR cluster > > > Key: DLAB-119 > URL: https://issues.apache.org/jira/browse/DLAB-119 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Front-end > Fix For: v.2.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-118) Tune EMR parameters
[ https://issues.apache.org/jira/browse/DLAB-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-118: --- Component/s: AWS > Tune EMR parameters > --- > > Key: DLAB-118 > URL: https://issues.apache.org/jira/browse/DLAB-118 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS >Reporter: Vira Vitanska >Assignee: Oleh Moskovych >Priority: Major > Labels: DevOps > Fix For: v.2.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-119) [Front-end]: Add possibility to tune EMR cluster
[ https://issues.apache.org/jira/browse/DLAB-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-119: --- Labels: Debian Front-end RedHat (was: Front-end) > [Front-end]: Add possibility to tune EMR cluster > > > Key: DLAB-119 > URL: https://issues.apache.org/jira/browse/DLAB-119 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.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-121) Add possibility to tune spark cluster: backend
[ https://issues.apache.org/jira/browse/DLAB-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-121: --- Component/s: GCP Azure AWS > Add possibility to tune spark cluster: backend > -- > > Key: DLAB-121 > URL: https://issues.apache.org/jira/browse/DLAB-121 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end > Fix For: v.2.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-118) Tune EMR parameters
[ https://issues.apache.org/jira/browse/DLAB-118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-118: --- Labels: Debian DevOps RedHat (was: DevOps) > Tune EMR parameters > --- > > Key: DLAB-118 > URL: https://issues.apache.org/jira/browse/DLAB-118 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS >Reporter: Vira Vitanska >Assignee: Oleh Moskovych >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.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-120) Manage Spark properties
[ https://issues.apache.org/jira/browse/DLAB-120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-120: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Manage Spark properties > --- > > Key: DLAB-120 > URL: https://issues.apache.org/jira/browse/DLAB-120 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.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-121) Add possibility to tune spark cluster: backend
[ https://issues.apache.org/jira/browse/DLAB-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-121: --- Labels: Back-end Debian RedHat (was: Back-end) > Add possibility to tune spark cluster: backend > -- > > Key: DLAB-121 > URL: https://issues.apache.org/jira/browse/DLAB-121 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.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-486) Update documentation
Vira Vitanska created DLAB-486: -- Summary: Update documentation Key: DLAB-486 URL: https://issues.apache.org/jira/browse/DLAB-486 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-338) [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: --- Component/s: GCP > [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: GCP >Reporter: Vira Vitanska >Assignee: Dmytro Liaskovskyi >Priority: Major > Fix For: v.2.2 > > > 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-233) Autofocus should be on Cluster configuration template, JSON" after checking off "cluster configurations" check box"
[ https://issues.apache.org/jira/browse/DLAB-233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-233: --- Component/s: GCP Azure AWS > Autofocus should be on Cluster configuration template, JSON" after checking > off "cluster configurations" check box" > --- > > Key: DLAB-233 > URL: https://issues.apache.org/jira/browse/DLAB-233 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > As a user I want to have autofocus on "Cluster configuration template, JSON" > text box if I check off "custer configuration" check box > *Acceptance criteria:* > 1. if user checks off "custer configuration" check box a scrollbar goes down > by automatically in front of "Cluster configuration template, JSON" text box -- This message was sent by Atlassian 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-181) Review documentation concerning DLab deployment on AWS
[ https://issues.apache.org/jira/browse/DLAB-181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-181: --- Component/s: AWS > Review documentation concerning DLab deployment on AWS > -- > > Key: DLAB-181 > URL: https://issues.apache.org/jira/browse/DLAB-181 > Project: Apache DLab > Issue Type: Task > Components: AWS >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end > Fix For: v.2.1 > > > As a user I want easily and quickly deploy DLab by myself on AWS using > appropriate documentation: > - [https://github.com/epam/DLab/blob/master/README.md#Configuration_files] > - [https://kb.epam.com/display/EPMCBDCC/Deployment+checklist] > > *Acceptance criteria:* > 1. All prerequisites should be counted which are needed before DLab deploy -- This message was sent by Atlassian 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-257) [AWS][EMR]: Add link to AWS documentation
[ https://issues.apache.org/jira/browse/DLAB-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-257: --- Labels: Debian Front-end RedHat (was: Front-end) > [AWS][EMR]: Add link to AWS documentation > - > > Key: DLAB-257 > URL: https://issues.apache.org/jira/browse/DLAB-257 > Project: Apache DLab > Issue Type: Task > Components: AWS >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > Add the following text > To view example JSON of configurations refer for AWS official documentation > [https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-configure-apps.html] -- This message was sent by Atlassian 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: --- Parent Issue: DLAB-487 (was: 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.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-116) Tune Spark/EMR parameters from web UI on instance creation step
[ https://issues.apache.org/jira/browse/DLAB-116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-116: --- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > Tune Spark/EMR parameters from web UI on instance creation step > --- > > Key: DLAB-116 > URL: https://issues.apache.org/jira/browse/DLAB-116 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > Fix For: v.2.1 > > > As a user I want to tune Spark/EMR parameters from web UI. > > *Acceptance criteria:* > 1. it should be check box for configuration on computational creation popup > 2. if user checks off configuration check box parameters a text box appears > in the right side of computational creation popup > 3. in parameters a text box a user can put Spark/EMR parameters > > _You can view example JSON of configurations using this link > [https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-configure-apps.html]_ > -- This message was sent by Atlassian 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-117) Back-end
[ https://issues.apache.org/jira/browse/DLAB-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-117: --- Component/s: GCP Azure AWS > Back-end > > > Key: DLAB-117 > URL: https://issues.apache.org/jira/browse/DLAB-117 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end > Fix For: v.2.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-487) Update documentation to release 2.2
Vira Vitanska created DLAB-487: -- Summary: Update documentation to release 2.2 Key: DLAB-487 URL: https://issues.apache.org/jira/browse/DLAB-487 Project: Apache DLab Issue Type: Task Components: AWS, Azure, GCP Reporter: Vira Vitanska Fix For: v.2.2 -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [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: --- Component/s: GCP Azure AWS > Update Apache Zeppelin version > --- > > Key: DLAB-255 > URL: https://issues.apache.org/jira/browse/DLAB-255 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: DevOps > Fix For: v.2.2 > > > 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-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 updated DLAB-254: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > 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 > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-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: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Update nodejs & npm for notebooks > - > > Key: DLAB-256 > URL: https://issues.apache.org/jira/browse/DLAB-256 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.2 > > > 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-449) Issues after updating angular and dependencies
[ https://issues.apache.org/jira/browse/DLAB-449?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-449: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Issues after updating angular and dependencies > -- > > Key: DLAB-449 > URL: https://issues.apache.org/jira/browse/DLAB-449 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.2 > > Attachments: 1.png, 10.png, 11.png, 12.png, 13.png, 14.png, 15.png, > 1a.PNG, 2.png, 3.png, 4.png, 5.png, 5a.PNG, 6.png, 7.png, 8.png, 9.png, > Library.PNG > > > # +*Manage roles:*+ > * Add space between buttons 'Back/'Cancel/'Next' and 'Back/'Cancel/'Create' > !1.png! > * Fonts for user's label (manage roles page ) and library's label (manage > libraries page) should be the same > !1a.PNG! > * Extra scrollbar for users column: > !3.png! > 2. +*Manage Libraries:*+ > * Add space before 'Enter library name' > !8.png! > !9.png! > * Add space between library name and version > !Library.PNG! > 3. +*Login:*+ > * Align Login in button 'Login' > !4.png! > * Convey error message: 'Username or password are not valid' > !5.png! > * Convey error message: 'Please contact AWS administrator to create > corresponding IAM User' > !5a.PNG! > * Convey error message: 'Please contact AWS administrator to activate your > Access Key' > 4. +*EMR Cluster:*+ > * error message for spot instance is beyond of popup > !13.png! > * add space between Apache Spark Master/ EMR Master and url > !15.png! > 5. +*Align confirmation dialog, add header and delete icon for:*+ > * group deletion (manage roles) > * spark/emr stopping/deletion on resource list page and environment > management page > * account deletion for manage git credentials > * user's environment stop/termination on Manage environment popup > 5. +*Filter shape in dtopdown list shoul start from lower case on 'resources > list' and 'billing report' pages:*+ > !6.png! > !11.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-309) Update user guide according to relese v.2.1
[ https://issues.apache.org/jira/browse/DLAB-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-309: --- Component/s: GCP Azure AWS > Update user guide according to relese v.2.1 > --- > > Key: DLAB-309 > URL: https://issues.apache.org/jira/browse/DLAB-309 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Fix For: v.2.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-485) Instance tuning
Vira Vitanska created DLAB-485: -- Summary: Instance tuning Key: DLAB-485 URL: https://issues.apache.org/jira/browse/DLAB-485 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-226) EMR configuration fails due to of limited quantity nginx restart per 10 seconds
[ https://issues.apache.org/jira/browse/DLAB-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-226: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: AWS > EMR configuration fails due to of limited quantity nginx restart per 10 > seconds > --- > > Key: DLAB-226 > URL: https://issues.apache.org/jira/browse/DLAB-226 > Project: Apache DLab > Issue Type: Bug > Components: AWS >Reporter: Vira Vitanska >Assignee: Oleh Moskovych >Priority: Critical > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > > *Preconditions:* > Environment is created > > *Steps ro reproduce:* > 1. Create EMR with seven or more nodes > > *Actual result:* > EMR configuration fails > > *Expected result:* > EMR is created -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-123) Possibility to update spark configuration: backend
[ https://issues.apache.org/jira/browse/DLAB-123?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-123: --- Component/s: GCP Azure AWS > Possibility to update spark configuration: backend > -- > > Key: DLAB-123 > URL: https://issues.apache.org/jira/browse/DLAB-123 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.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-488) Update software
Vira Vitanska created DLAB-488: -- Summary: Update software Key: DLAB-488 URL: https://issues.apache.org/jira/browse/DLAB-488 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] [Created] (DLAB-484) Reverse proxy
Vira Vitanska created DLAB-484: -- Summary: Reverse proxy Key: DLAB-484 URL: https://issues.apache.org/jira/browse/DLAB-484 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-124) API for getting spark configuration
[ https://issues.apache.org/jira/browse/DLAB-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-124: --- Component/s: GCP Azure AWS > API for getting spark configuration > --- > > Key: DLAB-124 > URL: https://issues.apache.org/jira/browse/DLAB-124 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > API needed for getting spark configurations (exploratory and computational) -- This message was sent by Atlassian 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-117) Back-end
[ https://issues.apache.org/jira/browse/DLAB-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-117: --- Labels: Back-end Debian RedHat (was: Back-end) > Back-end > > > Key: DLAB-117 > URL: https://issues.apache.org/jira/browse/DLAB-117 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.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-257) [AWS][EMR]: Add link to AWS documentation
[ https://issues.apache.org/jira/browse/DLAB-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-257: --- Component/s: AWS > [AWS][EMR]: Add link to AWS documentation > - > > Key: DLAB-257 > URL: https://issues.apache.org/jira/browse/DLAB-257 > Project: Apache DLab > Issue Type: Task > Components: AWS >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Front-end > Fix For: v.2.1 > > > Add the following text > To view example JSON of configurations refer for AWS official documentation > [https://docs.aws.amazon.com/emr/latest/ReleaseGuide/emr-configure-apps.html] -- This message was sent by Atlassian 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 2.1
[ https://issues.apache.org/jira/browse/DLAB-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-411: --- Component/s: GCP Azure AWS > Update documentation to release 2.1 > --- > > Key: DLAB-411 > URL: https://issues.apache.org/jira/browse/DLAB-411 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-253) GCP
[ https://issues.apache.org/jira/browse/DLAB-253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-253: --- Labels: Debian DevOps (was: DevOps) Component/s: GCP > GCP > --- > > Key: DLAB-253 > URL: https://issues.apache.org/jira/browse/DLAB-253 > Project: Apache DLab > Issue Type: Sub-task > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: 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-252) Azure
[ https://issues.apache.org/jira/browse/DLAB-252?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-252: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: Azure > Azure > - > > Key: DLAB-252 > URL: https://issues.apache.org/jira/browse/DLAB-252 > Project: Apache DLab > Issue Type: Sub-task > Components: Azure >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, 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] [Assigned] (DLAB-411) Update documentation to release 2.1
[ https://issues.apache.org/jira/browse/DLAB-411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-411: -- Assignee: Bohdan Hliva > Update documentation to release 2.1 > --- > > Key: DLAB-411 > URL: https://issues.apache.org/jira/browse/DLAB-411 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-272) API for updating user group
[ https://issues.apache.org/jira/browse/DLAB-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-272: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > API for updating user group > --- > > Key: DLAB-272 > URL: https://issues.apache.org/jira/browse/DLAB-272 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > Update API for user group -- This message was sent by Atlassian 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-356) Unable to resolve host localhost.localdomain on notebook
[ https://issues.apache.org/jira/browse/DLAB-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-356: --- Labels: Debian DevOps RedHat (was: DevOps) Fix Version/s: v.2.1 Component/s: GCP Azure AWS > Unable to resolve host localhost.localdomain on notebook > > > Key: DLAB-356 > URL: https://issues.apache.org/jira/browse/DLAB-356 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP > Environment: Azure >Reporter: Anna Orlovska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > Attachments: fault1.png, fault2.png, fault3.png > > > The bug was found on Jupyter, Apache Zeppelin/Rstudio notebooks on Azure. > Sometimes the bug is produced after notebook starting (if notebook was > previously stopped) > *Preconditions:* > Apache Zeppelin is stopped > *Steps to reproduce:* > 1. Start Apache Zeppelin > 2. Go to Apache Zeppelin UI > *Expected result:* > Apache Zeppelin UI is available > *Actual result:* > Apache Zeppelin UI is not available > !fault1.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-430) [AWS][RedHat]: Notebook creation fails due to AWS was not able to validate the provided access credentials
[ https://issues.apache.org/jira/browse/DLAB-430?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-430: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: AWS > [AWS][RedHat]: Notebook creation fails due to AWS was not able to validate > the provided access credentials > -- > > Key: DLAB-430 > URL: https://issues.apache.org/jira/browse/DLAB-430 > Project: Apache DLab > Issue Type: Bug > Components: AWS >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Blocker > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > Attachments: Notebook creation.PNG > > > *Preconditions:* > 1. Edge is created > *Steps to reproduce:* > 1. Create any template of Notebook > *Actual result:* > Notebook creation fails: > !Notebook creation.PNG! > *Expected result:* > Notebook is succesfully 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-150) Back-end
[ https://issues.apache.org/jira/browse/DLAB-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-150: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > Back-end > > > Key: DLAB-150 > URL: https://issues.apache.org/jira/browse/DLAB-150 > Project: Apache DLab > Issue Type: Sub-task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.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-205) Instance shapes should be filtered by clouds
[ https://issues.apache.org/jira/browse/DLAB-205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-205: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > Instance shapes should be filtered by clouds > > > Key: DLAB-205 > URL: https://issues.apache.org/jira/browse/DLAB-205 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > Attachments: image-2018-12-19-23-43-13-404.png > > > *Preconditions:* > # Edge is created on AWS > # 'Environment health status' page is open > > *Steps to reproduce:* > # Click 'Roles' button > # Click '$anyuser' drop down list > # Click 'Role' drop down list > > *Actual result:* > Appears shapes for AWS, Azure, GCP > !image-2018-12-19-23-43-13-404.png! > > *Expected result:* > Appears shapes for AWS -- This message was sent by Atlassian 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-149) Remove 'add compute' button for user who is not allowed to create computational resources
[ https://issues.apache.org/jira/browse/DLAB-149?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-149: --- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > Remove 'add compute' button for user who is not allowed to create > computational resources > - > > Key: DLAB-149 > URL: https://issues.apache.org/jira/browse/DLAB-149 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Debian, RedHat > Fix For: v.2.1 > > > *Preconditions:* > # environment is created > # user is not allowed to create computetional resources > # notebook is created > > *Steps to reproduce:* > # Go to 'resources list' page > # Click action menu for notebook > # Choose 'add compute' > > *Actual result:* > Appears popup and it is impossible to close it > > *Expected result:* > 'Add compute' button is absent > -- This message was sent by Atlassian 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-161) The same style should be on all DLab pages
[ https://issues.apache.org/jira/browse/DLAB-161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-161: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > The same style should be on all DLab pages > -- > > Key: DLAB-161 > URL: https://issues.apache.org/jira/browse/DLAB-161 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > Billing is avalable > > *Steps to reproduce:* > # Go to 'resources_list' page > # Go to 'billing_report' page > # Go to 'environment_management' page > > *Actual result:* > There are different styles on all pages > *Expected result:* > There is the same style on all pages > You can use style which is on "resources list" 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-222) [Azure][AWS]: Integration test fails to execute goal org.apache.maven.plugins:maven
[ https://issues.apache.org/jira/browse/DLAB-222?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-222: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: Azure AWS > [Azure][AWS]: Integration test fails to execute goal > org.apache.maven.plugins:maven > --- > > Key: DLAB-222 > URL: https://issues.apache.org/jira/browse/DLAB-222 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > *Steps to reproduce:* > 1. Run autotest for Azure > > *Actual result:* > Autotest fails with error: > *Execution default-test of goal > org.apache.maven.plugins:maven-surefire-plugin:2.17:test failed* > [http://35.166.222.81/job/AutoTests_Azure/196/console] > [http://35.166.222.81/job/AutoTests_AWS/265/console] > > *Expected result:* > 1. Autotest 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-262) [Confirmation dialog]: Prevent cluster header in case of notebook termination and no cluster is available on notebook
[ https://issues.apache.org/jira/browse/DLAB-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-262: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > [Confirmation dialog]: Prevent cluster header in case of notebook termination > and no cluster is available on notebook > - > > Key: DLAB-262 > URL: https://issues.apache.org/jira/browse/DLAB-262 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > Attachments: image-2019-01-16-18-24-40-464.png > > > *Preconditions:* > 1. notebook is in running status > 2. cluster is not deployed on notebook or is only in terminated status > *Steps to reproduce:* > 1. click action menu for notebook > 2. choose terminate notebook > *Actual result:* > confirmation dialog appears with cluster head > !image-2019-01-16-18-24-40-464.png! > *Expected result:* > confirmation dialog appears without cluster head -- This message was sent by Atlassian 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-202) [Azure]: Error handling is absent for wrong username/password
[ https://issues.apache.org/jira/browse/DLAB-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-202: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: Azure > [Azure]: Error handling is absent for wrong username/password > - > > Key: DLAB-202 > URL: https://issues.apache.org/jira/browse/DLAB-202 > Project: Apache DLab > Issue Type: Bug > Components: Azure >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > *Preconditions:* > SSN is created > > *Steps to reproduce:* > 1. Login DLab with wrong username or password > > *Actual result:* > Error handling is absent > > *Expected result:* > Error handling is 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-209) [Azure]: Sometimes Images/instances creation fails due to one IP is allocated to two instances simultaneously
[ https://issues.apache.org/jira/browse/DLAB-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-209: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: Azure > [Azure]: Sometimes Images/instances creation fails due to one IP is allocated > to two instances simultaneously > - > > Key: DLAB-209 > URL: https://issues.apache.org/jira/browse/DLAB-209 > Project: Apache DLab > Issue Type: Bug > Components: Azure >Reporter: Vira Vitanska >Assignee: Denys Shliakhov >Priority: Minor > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > Attachments: image-2018-12-19-23-53-04-831.png > > > *Steps to reproduce:* > 1. Run autotest on Azure > > *Actual result:* > Creation image fails with error: > !image-2018-12-19-23-53-04-831.png! > [http://35.166.222.81/job/AutoTests_Azure/189/consoleFull] > *Expected result:* > Autotest 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-197) Error message for existing image name is absent during creation image on the other Notebbok
[ https://issues.apache.org/jira/browse/DLAB-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-197: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: Azure AWS > Error message for existing image name is absent during creation image on the > other Notebbok > --- > > Key: DLAB-197 > URL: https://issues.apache.org/jira/browse/DLAB-197 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *Preconditions:* > 1. Two different Notebooks are created > *Steps to reproduce:* > 1. For one Notebook create image with valid name 'ami1' > 2. For the second Notebook create image with the same name 'ami1' > *Actual result:* > Error message about concerning message is absent > *Expected result:* > Error message about concerning message is 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-204) Value of used space is not true on HDD tab
[ https://issues.apache.org/jira/browse/DLAB-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-204: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > Value of used space is not true on HDD tab > -- > > Key: DLAB-204 > URL: https://issues.apache.org/jira/browse/DLAB-204 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > Attachments: image-2018-12-19-23-37-20-249.png, > image-2018-12-19-23-37-39-528.png > > > A bug was found on AWS. > > *Preconditions:* > 1. Edge is created > 2. 'Health status' page is open > > *Steps to reproduce:* > # Click 'SSN Monitor' button > # Go to HDD tab > > *Actual result:* > 1. Disk value of 'used space' is more than 'total space' > !image-2018-12-19-23-37-20-249.png! > !image-2018-12-19-23-37-39-528.png! > *Expected result:* > 1. Disk value of 'used space' is less than 'total space' > 2. Disk value of 'used space' matches the result value to command *df* -- This message was sent by Atlassian 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-171) Remove header in case of absent computational resources on confirmation dialog
[ https://issues.apache.org/jira/browse/DLAB-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-171: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Remove header in case of absent computational resources on confirmation dialog > -- > > Key: DLAB-171 > URL: https://issues.apache.org/jira/browse/DLAB-171 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > Only notebook is created > > *Steps to reproduce:* > # Click action menu of Notebook > # Choose stop or terminate action > > *Actual result:* > Header for computational resources is present > *Expected result:* > "Stop notebook: name_notebook" is present > Message "Notebook server will be stopped." is present > Header for computational resources is absent > Message "You have no active resources" is present > Message "Do you want to proceed?" is present > "No" and "Yes" buttons are present > "Notebook server will be stopped" should be center aligned -- This message was sent by Atlassian 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-167) [Add computational resources]: Alter and prevent passing some values to front-end side
[ https://issues.apache.org/jira/browse/DLAB-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-167: --- Summary: [Add computational resources]: Alter and prevent passing some values to front-end side (was: [Add computational resources]: Alter and prevent passing some values to frtont-end side) > [Add computational resources]: Alter and prevent passing some values to > front-end side > -- > > Key: DLAB-167 > URL: https://issues.apache.org/jira/browse/DLAB-167 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end > Fix For: v.2.1 > > > # Remove descriptions: "Apache Spark standalone cluster", "Image for EMR > provisioning" > # Rename templates names from "Apache Spark cluster" to "Apache Spark > standalone cluster" and from "EMR cluster" to "AWS EMR cluster" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-189) [Java]: Add Swagger tool to DLab
[ https://issues.apache.org/jira/browse/DLAB-189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-189: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > [Java]: Add Swagger tool to DLab > > > Key: DLAB-189 > URL: https://issues.apache.org/jira/browse/DLAB-189 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Minor > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > As a user I want use Swagger in order to call API DLab instae of using DLab > UI. > > *Acceptance criteria:* > # to apply swagger to DLab user uses the next link as > example > Official documentation: [https://swagger.io|https://swagger.io/] -- This message was sent by Atlassian 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-179) Information for not existing page and not having permission to page access
[ https://issues.apache.org/jira/browse/DLAB-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-179: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Information for not existing page and not having permission to page access > -- > > Key: DLAB-179 > URL: https://issues.apache.org/jira/browse/DLAB-179 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > Information which user sees in case: > - If page does not exist user sees 'page not found' > - If page exists but user has not access to it user sees 'Permission denied' -- This message was sent by Atlassian 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-195) [Integration tests]: Add possibility to choose notebook shapes, EMR version, spot instances before tests' starting
[ https://issues.apache.org/jira/browse/DLAB-195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-195: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > [Integration tests]: Add possibility to choose notebook shapes, EMR version, > spot instances before tests' starting > -- > > Key: DLAB-195 > URL: https://issues.apache.org/jira/browse/DLAB-195 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Chaparin >Priority: Minor > Labels: Back-end, Debian, RedHat > Fix For: v.2.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-140) Do not allow to create AMI's with same name: add extra checks by Status during AMI creation
[ https://issues.apache.org/jira/browse/DLAB-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-140: --- Component/s: Azure AWS > Do not allow to create AMI's with same name: add extra checks by Status > during AMI creation > --- > > Key: DLAB-140 > URL: https://issues.apache.org/jira/browse/DLAB-140 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure >Reporter: Vira Vitanska >Assignee: Vira Vitanska >Priority: Major > Fix For: v.2.1 > > > We should filter AMI which is in status 'created' and 'creating' so that the > name of creating AMI will be checked and will be not to allowed to create AMI > with the same name. > > *Acceptance criteria:* > 1.If custom AMI has 'creating' status and user puts the same name (as in > 'creating' AMI) appears error message concerning using this name > -- This message was sent by Atlassian 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-183) Rendering issues on 'Reporting' page (only in Firefox browser)
[ https://issues.apache.org/jira/browse/DLAB-183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-183: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Rendering issues on 'Reporting' page (only in Firefox browser) > -- > > Key: DLAB-183 > URL: https://issues.apache.org/jira/browse/DLAB-183 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > Attachments: image-2018-12-19-22-40-08-460.png > > > *Preconditions:* > # Environment is creted more than one day ago > *Steps to reproduce:* > # Got to 'Reporting' page > *Actual result:* > Two vertical lines are absent for 'status' column > !image-2018-12-19-22-40-08-460.png! > *Expected result:* > Two vertical lines are present for 'status' column -- This message was sent by Atlassian 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-237) Reconfiguration local spark on notebook deletes paths to jars in spark-defaults.conf
[ https://issues.apache.org/jira/browse/DLAB-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-237: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Reconfiguration local spark on notebook deletes paths to jars in > spark-defaults.conf > > > Key: DLAB-237 > URL: https://issues.apache.org/jira/browse/DLAB-237 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > Attachments: image-2018-12-20-10-35-10-904.png, > image-2018-12-20-10-35-25-732.png > > > *Preconditions:* > 1. Spark Standalone is created on Notebook > *Steps to reproduce:* > 1. reconfigure local spark on Notebook: > "spark.maxRemoteBlockSizeFetchToMem": "Int.MaxValue - 512" > *Actual result:* > paths to jars are deleted in spark-defaults.conf > !image-2018-12-20-10-35-10-904.png! > !image-2018-12-20-10-35-25-732.png! > *Expected result:* > paths to jars are NOT deleted in spark-defaults.conf -- This message was sent by Atlassian 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-238) [Azure]: Custom parameters are not written in spark-defaults.conf if create custom Spark Standalone (NOT via regonfiguration)
[
https://issues.apache.org/jira/browse/DLAB-238?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-238:
---
Labels: Back-end Debian RedHat (was: Back-end)
Component/s: Azure
> [Azure]: Custom parameters are not written in spark-defaults.conf if create
> custom Spark Standalone (NOT via regonfiguration)
> -
>
> Key: DLAB-238
> URL: https://issues.apache.org/jira/browse/DLAB-238
> Project: Apache DLab
> Issue Type: Bug
> Components: Azure
>Reporter: Vira Vitanska
>Assignee: Bohdan Hliva
>Priority: Major
> Labels: Back-end, Debian, RedHat
> Fix For: v.2.1
>
> Attachments: image-2018-12-20-10-37-08-978.png
>
>
> The bug was found on Azure on Jupyter.
> Preconditions:
> 1. Notebook is created
> Steps to reproduce:
> 1. Create custom Spark Standalone:
> [
> {
> "Classification": "spark-defaults",
> "Properties":
> { "spark.reducer.maxSizeInFlight": "48m" }
> }
> ]
> *Actual result:*
> Custom Spark Standalone is created as default Spark Standalone
> !image-2018-12-20-10-37-08-978.png!
> *Expected result:*
> Custom Spark Standalone is created with custom parameters
--
This message was sent by Atlassian 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-166) [Add computational resources]: UI improvements
[ https://issues.apache.org/jira/browse/DLAB-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-166: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > [Add computational resources]: UI improvements > -- > > Key: DLAB-166 > URL: https://issues.apache.org/jira/browse/DLAB-166 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *1.* Rename label from "Your bid for spot instance, %" to "Spot instance bit, > %" > *2.* "Configurations" check box rename to "Cluster configuration template, > JSON" > *3.* Divide 'Add computational resources' into two columns: > *3.1.* for Spark cluster move "Total node number" and "Node shape" into the > second (right) side. "Cluster configuration template, JSON" check box with > input value should be above all drop downs list > *3.2.* for EMR cluster move "Total instance number", "Master instance shape" > and "Slave instance shape"into the second (right) side. "Cluster > configuration template, JSON" check box with input value should be above all > drop downs list and "Spot instance bit, %" -- This message was sent by Atlassian 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-165) Extra vertical scrollbar for six users on Manage popup"
[ https://issues.apache.org/jira/browse/DLAB-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-165: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Extra vertical scrollbar for six users on Manage popup" > --- > > Key: DLAB-165 > URL: https://issues.apache.org/jira/browse/DLAB-165 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Trivial > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *Preconditions:* > Six users has at least one running instance > *Steps to reproduce:* > 1. Go to Health status page > 2. Click on 'Manage enironment button > *Actual result:* > Extra vertical scrollbar appears > *Expected result:* > There is no extra vertical scrollbar -- This message was sent by Atlassian 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-191) Integration test should support scenarios when Notebook X is started on platform Y
[ https://issues.apache.org/jira/browse/DLAB-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-191: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > Integration test should support scenarios when Notebook X is started on > platform Y > -- > > Key: DLAB-191 > URL: https://issues.apache.org/jira/browse/DLAB-191 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Chaparin >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.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-167) [Add computational resources]: Alter and prevent passing some values to front-end side
[ https://issues.apache.org/jira/browse/DLAB-167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-167: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > [Add computational resources]: Alter and prevent passing some values to > front-end side > -- > > Key: DLAB-167 > URL: https://issues.apache.org/jira/browse/DLAB-167 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end, Debian, RedHat > Fix For: v.2.1 > > > # Remove descriptions: "Apache Spark standalone cluster", "Image for EMR > provisioning" > # Rename templates names from "Apache Spark cluster" to "Apache Spark > standalone cluster" and from "EMR cluster" to "AWS EMR cluster" -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-164) Notebook termination should convey the future status of previously stopped cluster on confirmation dialog
[ https://issues.apache.org/jira/browse/DLAB-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-164: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Notebook termination should convey the future status of previously stopped > cluster on confirmation dialog > - > > Key: DLAB-164 > URL: https://issues.apache.org/jira/browse/DLAB-164 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *Preconditions:* > 1. spark standalone cluster is in stopped status > 2. "Resources list" page is open > *Steps to reproduce:* > 1. click action menu for notebook > 2. choose terminate notebook > *Actual result:* > In confirmation dialog is absent that stopped cluster will be terminated > *Expected result:* > In confirmation dialog informst that stopped cluster will be terminated -- This message was sent by Atlassian 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-498) 2VPCs
Vira Vitanska created DLAB-498: -- Summary: 2VPCs Key: DLAB-498 URL: https://issues.apache.org/jira/browse/DLAB-498 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-178) All DLab resources should be tagged as product:DLab
[ https://issues.apache.org/jira/browse/DLAB-178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-178: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > All DLab resources should be tagged as product:DLab > --- > > Key: DLAB-178 > URL: https://issues.apache.org/jira/browse/DLAB-178 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > > Now we have (key) user:tag. > New tag should be added: Product:DLab -- This message was sent by Atlassian 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-187) Page is blocked during uploading a key
[ https://issues.apache.org/jira/browse/DLAB-187?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-187: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Page is blocked during uploading a key > -- > > Key: DLAB-187 > URL: https://issues.apache.org/jira/browse/DLAB-187 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Debian, Front-end, RedHat > Fix For: v.2.1 > > > *Preconditions:* > # Only SSN is created > # User is logged in DLab > > *Steps to reproduce:* > # Go to 'Billing Report' or 'Environment Management' page > # Click beyond of reuploading key popup > > *Actual result:* > 'Billing Report' or 'Environment Management' page is blocked during > > *Expected result:* > 'Billing Report' or 'Environment Management' page isn't blocked during -- This message was sent by Atlassian 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-236) Spark Standalone reconfiguration fails if spark name is a part of another spark name on one notebook
[ https://issues.apache.org/jira/browse/DLAB-236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-236: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Spark Standalone reconfiguration fails if spark name is a part of another > spark name on one notebook > > > Key: DLAB-236 > URL: https://issues.apache.org/jira/browse/DLAB-236 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > > h4. Description > When there more than 1 spark cluster created with similar name (e.g. spa, > spark) on on notebook action reconfigure for spark with name "spa" fails > *Preconditions:* > 1. two Spark Standalones are created on one notebook with names "spa" "spark" > *Steps to reproduce:* > 1. reconfigure Spark Standalone with name "spa": > "spark.maxRemoteBlockSizeFetchToMem": "Int.MaxValue - 512" > *Actual result:* > Spark Standalone reconfiguration fails > *Expected result:* > Spark Standalone reconfiguration 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-264) Allow port range 4040-4045 for notebooks
[ https://issues.apache.org/jira/browse/DLAB-264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-264: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Allow port range 4040-4045 for notebooks > > > Key: DLAB-264 > URL: https://issues.apache.org/jira/browse/DLAB-264 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > > For every Spark context, we have Spark UI located on ports 4040 - ... > In order to have ability to access UIs, we should add appropriate rules to SG -- This message was sent by Atlassian 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-224) Create instruction how to deploy DLab from scratch
[ https://issues.apache.org/jira/browse/DLAB-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-224: --- Component/s: GCP Azure AWS > Create instruction how to deploy DLab from scratch > -- > > Key: DLAB-224 > URL: https://issues.apache.org/jira/browse/DLAB-224 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: DevOps > Fix For: v.2.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
