[jira] [Updated] (DLAB-295) Edge Node - why we need it?
[ https://issues.apache.org/jira/browse/DLAB-295?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-295: --- Description: As a user I want to use pre-configured login/password instead of using edge node in order to create/configure notebook for user in subnet. The most controversial feature is “edge node” and the need ssh tunnel to access notebook. There was valid comment that all notebooks (jupyter/zeppelin/rstudio) can be started off with pre-configured login/password which will gave same level of security, but much easy access process. Perhaps it’s something worth to consider. was: As a user I want to use pre-configured login/password instead of using edge node in order to create/configure notebook for user in subnet. Kostia was on conference with DLab and below are the comments: The most controversial feature is “edge node” and the need ssh tunnel to access notebook. There was valid comment that all notebooks (jupyter/zeppelin/rstudio) can be started off with pre-configured login/password which will gave same level of security, but much easy access process. Perhaps it’s something worth to consider. > Edge Node - why we need it? > --- > > Key: DLAB-295 > URL: https://issues.apache.org/jira/browse/DLAB-295 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Critical > Labels: Debian, RedHat > > As a user I want to use pre-configured login/password instead of using edge > node in order to create/configure notebook for user in subnet. > > The most controversial feature is “edge node” and the need ssh tunnel to > access notebook. There was valid comment that all notebooks > (jupyter/zeppelin/rstudio) can be started off with pre-configured > login/password which will gave same level of security, but much easy access > process. Perhaps it’s something worth to consider. -- This message was sent by Atlassian 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-97) Bucket browser
[ https://issues.apache.org/jira/browse/DLAB-97?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-97: -- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > Bucket browser > -- > > Key: DLAB-97 > URL: https://issues.apache.org/jira/browse/DLAB-97 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to use S3 browser so that i can manage your buckets and > objects via DLab UI. > > *Acceptance criteria:* > *1.* user has access only to shared and own personal buckets (by default) > *2.* other user does not have acces to other personal buckets (by default) > *3.* administrator has access to shared, ssn and users personal buckets > *4.* user can upload and download files to and from Amazon S3 > *5.* user can create public URLs to share the files > *6.* user can set Access Control on buckets and files only for his personal > bucket -- This message was sent by Atlassian 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-65) Upgrade DLab
[ https://issues.apache.org/jira/browse/DLAB-65?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-65: -- Labels: Debian RedHat (was: DevOps) Component/s: GCP Azure AWS > Upgrade DLab > > > Key: DLAB-65 > URL: https://issues.apache.org/jira/browse/DLAB-65 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to have possibility to upgrade current DLab version so that > I do not need fully redeploy. > > *Acceptance criteria:* > 1. user can upgrade DLab > 2. all previously data (billing/instances) do not removed/changed after > upgrading -- This message was sent by Atlassian 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-507) Upgrade DLab
Vira Vitanska created DLAB-507: -- Summary: Upgrade DLab Key: DLAB-507 URL: https://issues.apache.org/jira/browse/DLAB-507 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-101) Integration with Grafana for monitoring and troubleshooting of cluster performance
[ https://issues.apache.org/jira/browse/DLAB-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-101: --- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > Integration with Grafana for monitoring and troubleshooting of cluster > performance > -- > > Key: DLAB-101 > URL: https://issues.apache.org/jira/browse/DLAB-101 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to use Grafana so that I can monitor and troubleshoot of > cluster performance. > > *Acceptance criteria:* > # "Grafana" link should be on cluster name of popup > # if user clicks on "Grafana" link window of grafana metrics dashboard and > graph editor will open in new tab for computational resource performance > > > _Link for open-source project [https://grafana.com/]_ > _Link for GitHub: > [github.com/grafana/grafana|https://github.com/grafana/grafana/]_ -- This message was sent by Atlassian 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-28) Grafana
[ https://issues.apache.org/jira/browse/DLAB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-28: -- Epic Name: Grafana > Grafana > --- > > Key: DLAB-28 > URL: https://issues.apache.org/jira/browse/DLAB-28 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Minor > -- This message was sent by Atlassian 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-28) Grafana
[ https://issues.apache.org/jira/browse/DLAB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-28: -- Labels: (was: Debian RedHat) Description: (was: As a user I want to create instances using Low Priority VM's so that I can reduce financial charges. *Acceptance criteria:* 1. it should be check box for Low Priority VM's on computational resources creation popup 2. check box for Low Priority VM's should be checked off by default 3. if user unchecks check box for Low Priority VM's and hits 'Create' button a computational resource will be created without Low Priority VM's 4. if user checks off check box for Low Priority VM's and hits 'Create' button a computational resource will be created with Low Priority VM's) Component/s: (was: Azure) Issue Type: Epic (was: New Feature) Summary: Grafana (was: [Azure]: Low Priority VM's) > Grafana > --- > > Key: DLAB-28 > URL: https://issues.apache.org/jira/browse/DLAB-28 > Project: Apache DLab > Issue Type: Epic >Reporter: Vira Vitanska >Priority: Minor > -- This message was sent by Atlassian 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-84) WEB UI file manager for Notebook
[ https://issues.apache.org/jira/browse/DLAB-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-84: -- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > WEB UI file manager for Notebook > > > Key: DLAB-84 > URL: https://issues.apache.org/jira/browse/DLAB-84 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to have a possibility to do file manipulations ((pre)view, > upload and modify) on notebook via WEB UI so that I can quickly and more > convenient do this actions. > > *Acceptance criteria:* > 1. there is a 'files manager' button on action menu per notebook > 2. user can copy file in files manager > 3. user can paste file in files manager > 4. user can delete file in files manager > 5. user can rename file in files manager > 6. user can extract file in files manager > 7. user can create directory in files manager > 8. user can create file in files manager > 9. user can edit file in files manager > 10. user can upload file(s) in files manage > > You can use this link to find some solution > [https://kishstats.com/python/2018/03/15/flask-amazon-s3-series.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-83) [GCP]: Display Spark/Dataproc job tracker URL on Web UI
[ https://issues.apache.org/jira/browse/DLAB-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-83: -- Labels: DevOps debian (was: DevOps) Component/s: GCP > [GCP]: Display Spark/Dataproc job tracker URL on Web UI > --- > > Key: DLAB-83 > URL: https://issues.apache.org/jira/browse/DLAB-83 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: DevOps, debian > > As a user I want to see a link for computational resources job tracker on WEB > UI via reverse proxy so that I can go to computational resources job tracker > quickly and do not need go to GCP console in order to know master IP > > *Acceptance criteria:* > 1. a link for computational resources job tracker displays on computational > resources popup > 2. if click a link for computational resources job tracker a new tab > browser opens where is a computational resources job tracker -- This message was sent by Atlassian 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-57) Shared for all users custom AMI
[ https://issues.apache.org/jira/browse/DLAB-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-57: -- Labels: Debian RedHat (was: ) Component/s: Azure AWS > Shared for all users custom AMI > --- > > Key: DLAB-57 > URL: https://issues.apache.org/jira/browse/DLAB-57 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to choose of making custom AMi of notebook public or not > public, so that I can shared my own custom AMI with other users by my desire. > > *Acceptance criteria:* > 1. to add possibility for choosing during creation AMI: > - available for all users/make shared > 2. my personal data on notebook should not to be shared -- This message was sent by Atlassian 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-62) Images
[ https://issues.apache.org/jira/browse/DLAB-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-62: -- Labels: (was: DevOps) Description: (was: As an admin I want to use defined list of subnet during DLab SSN deploy on GCP.) Issue Type: Epic (was: Improvement) Summary: Images (was: [GCP]: Add private subnets and subnets pool configurable) > Images > -- > > Key: DLAB-62 > URL: https://issues.apache.org/jira/browse/DLAB-62 > 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-82) [Azure]: Display Spark job tracker URL on Web UI
[ https://issues.apache.org/jira/browse/DLAB-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-82: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: Azure Summary: [Azure]: Display Spark job tracker URL on Web UI (was: Azure: Display Spark job tracker URL on Web UI) > [Azure]: Display Spark job tracker URL on Web UI > > > Key: DLAB-82 > URL: https://issues.apache.org/jira/browse/DLAB-82 > Project: Apache DLab > Issue Type: New Feature > Components: Azure >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > As a user I want to see a link for Spark job tracker on WEB UI via reverse > proxy so that I can go to Spark job tracker quickly and do not need go to > Azure console in order to know master IP. > > *Acceptance criteria:* > 1. a link for Spark job tracker displays on Spark popup > 2. if click a link for Spark job tracker a new tab browser opens where is a > Spark master UI -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-389) Refactor playbook for Jupyter with TensorFlow
[ https://issues.apache.org/jira/browse/DLAB-389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-389: --- Fix Version/s: (was: v.2.2) > Refactor playbook for Jupyter with TensorFlow > - > > Key: DLAB-389 > URL: https://issues.apache.org/jira/browse/DLAB-389 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > 1. Labels should be under images > 2. If result is equal and more than 75% define as dog or cat, if result is > less than 75% define as undefined -- This message was sent by Atlassian 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-296) DLab REST API to manage DLab without UI
[ https://issues.apache.org/jira/browse/DLAB-296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-296: --- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > DLab REST API to manage DLab without UI > --- > > Key: DLAB-296 > URL: https://issues.apache.org/jira/browse/DLAB-296 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to manage DLab without UI so that I can reduce time for some > operations -- This message was sent by Atlassian 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-69) Possibility to delete custom image
[ https://issues.apache.org/jira/browse/DLAB-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-69: -- Labels: Debian RedHat (was: ) Component/s: Azure AWS > Possibility to delete custom image > -- > > Key: DLAB-69 > URL: https://issues.apache.org/jira/browse/DLAB-69 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, RedHat > > As a user I want to delete notebook custom image so that it gives > opportunities to delete snapshots by automatically after notebook termination. > > *Acceptance criteria:* > # on main Dlab menu it should be new page for deleting custom image > # user can choose existed custom image for deleting from drop down list > # after confirmation of custom image deleting a shosen custom image is > deleted and is not available -- This message was sent by Atlassian 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-61) Image instance should contain only libraries (dependencies)
[ https://issues.apache.org/jira/browse/DLAB-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-61: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: Azure AWS > Image instance should contain only libraries (dependencies) > --- > > Key: DLAB-61 > URL: https://issues.apache.org/jira/browse/DLAB-61 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure > Environment: AWS > Azure > ***Currently custom AMi is implemented on AWS and Azure >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, DevOps, RedHat > > *Preconditions:* > Playbooks, folders are on Notebook > > *Steps to reproduce:* > # Create custom AMI1 from Notebook1 > # Create Notebook2 from custom AMI1 > # Go to Notebook2 UI > > *Actual result:* > Playbooks, folders from notebook1 are on Notebook2 > > *Expected result:* > Playbooks, folders from notebook1 are absent on Notebook2 > > > > Currently personal user data, like folders, playbooks are also part of custom > 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-54) [GCP][Notebooks]: Add AMIs
[ https://issues.apache.org/jira/browse/DLAB-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-54: -- Labels: Debian DevOps (was: DevOps) Component/s: GCP Azure AWS > [GCP][Notebooks]: Add AMIs > -- > > Key: DLAB-54 > URL: https://issues.apache.org/jira/browse/DLAB-54 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps > > As a user I want to create Notebook using shared AMI, so that I can reduce > time of notebook creation. > *Acceptance criteria:* > 1. during the first Notebook template creation a shared AMI is created > 2. other user or the same user creates the same notebook template using > shared AMI -- This message was sent by Atlassian 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-50) Register all AMIs on AWS's Marketplace and use it for further DLAB SSN instances
[ https://issues.apache.org/jira/browse/DLAB-50?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-50: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: AWS > Register all AMIs on AWS's Marketplace and use it for further DLAB SSN > instances > > > Key: DLAB-50 > URL: https://issues.apache.org/jira/browse/DLAB-50 > Project: Apache DLab > Issue Type: Task > Components: AWS >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > As a user I want to storage all AMIs on Marketplace of AWS, so that I can use > it for further creation of DLab SSN instances. -- This message was sent by Atlassian 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-62) Images
[ https://issues.apache.org/jira/browse/DLAB-62?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-62: -- Epic Name: Images > Images > -- > > Key: DLAB-62 > URL: https://issues.apache.org/jira/browse/DLAB-62 > 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-43) New API to FIX/REPAIR provisioned resources
[ https://issues.apache.org/jira/browse/DLAB-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-43: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > New API to FIX/REPAIR provisioned resources > --- > > Key: DLAB-43 > URL: https://issues.apache.org/jira/browse/DLAB-43 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > As a user I want to use API that could fix/repair/create mapping if following > resources are either missing or corrupted: > - Subnet > - Role > - Profiles > - Policy > - Security Groups > - Bucket -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-42) New API to obtain STATUS of provisioned resources
[ https://issues.apache.org/jira/browse/DLAB-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-42: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > New API to obtain STATUS of provisioned resources > - > > Key: DLAB-42 > URL: https://issues.apache.org/jira/browse/DLAB-42 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > As a user I want to use API in order to obtain status of provisioned > resources. > > *Acceptance criteria:* > 1. API should retrieve and return STATUS of following resources: > 1.1. subnet > 1.2. role > 1.3. profiles > 1.4. policy > 1.5. security Groups > 1.6. bucket -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-5) [AWS]: Flexible disk size for instances
[ https://issues.apache.org/jira/browse/DLAB-5?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-5: - Labels: Debian RedHat (was: ) Component/s: AWS > [AWS]: Flexible disk size for instances > --- > > Key: DLAB-5 > URL: https://issues.apache.org/jira/browse/DLAB-5 > Project: Apache DLab > Issue Type: New Feature > Components: AWS >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > > As a user I want to choose volume type, size, lops during > Notebook/computational resource creation or change the parameters of already > existed Notebook so that I can add more space by necessary on AWS. > > *Acceptance criteria:* > # during creation Notebook/computational resource it should be 3 drop down > list, from which user can choose values of volume type, size, lops > # in case of existed Noteboocomputational resource it should be 'Volume' > button on action menu. If user click 'Volume' button a new 'Volume' popup > open and user can see volume type, size, lops of current > Notebook/computational resource and change values > > _*** Investigate how to move to Amazon EFS._ -- This message was sent by Atlassian 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-32) Copy all relevant logs to a single persistent place
[ https://issues.apache.org/jira/browse/DLAB-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-32: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Copy all relevant logs to a single persistent place > --- > > Key: DLAB-32 > URL: https://issues.apache.org/jira/browse/DLAB-32 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, DevOps, RedHat > > As a user I want automatically to have a copy of relevant logs (computational > resources) to a single persistent place so that I do not have to copy logs > by manually. > > *Acceptance criteria:* > # computational resources logs are copied automatically > _***Spark and Yarn ones. As now they are lost upon cluster shutdown, while > often being indispensable for later troubleshooting, so we had to copy them > to S3 manually._ > _If programmatic shutdown gets implemented, you may want to provide > parameters to govern saving logs as well._ -- This message was sent by Atlassian 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: --- Epic Name: 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-28) [Azure]: Low Priority VM's
[ https://issues.apache.org/jira/browse/DLAB-28?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-28: -- Labels: Debian RedHat (was: ) Component/s: Azure > [Azure]: Low Priority VM's > -- > > Key: DLAB-28 > URL: https://issues.apache.org/jira/browse/DLAB-28 > Project: Apache DLab > Issue Type: New Feature > Components: Azure >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, RedHat > > As a user I want to create instances using Low Priority VM's so that I can > reduce financial charges. > > *Acceptance criteria:* > 1. it should be check box for Low Priority VM's on computational resources > creation popup > 2. check box for Low Priority VM's should be checked off by default > 3. if user unchecks check box for Low Priority VM's and hits 'Create' button > a computational resource will be created without Low Priority VM's > 4. if user checks off check box for Low Priority VM's and hits 'Create' > button a computational resource will be created with Low Priority VM's -- This message was sent by Atlassian 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-279) Investigate if content of available lib list should depend on cloud and OS
[ https://issues.apache.org/jira/browse/DLAB-279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-279: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Investigate if content of available lib list should depend on cloud and OS > -- > > Key: DLAB-279 > URL: https://issues.apache.org/jira/browse/DLAB-279 > Project: Apache DLab > Issue Type: Bug > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, DevOps, RedHat > > There is some list of libraries which is available for one cloud/OS and is > not available for other one. > *For example:* > RStudio ['apt/yum']: 'tkinter' is present in available lib list for AWS > (RedHat) and the same lib is absent for AWS [Debian], GCP, Azure; > RStudio ['apt/yum']: 'python-mysqldb' is present in available lib list for > AWS (Debian) and the same lib is absent for AWS [RedHat], GCP, Azure; > RStudio ['apt/yum']: 'tabix' is present in available lib list for AWS > (Debian) and the same lib is absent for AWS [RedHat], GCP, Azure. > > *Preconditions:* > # Library RStudio ['apt/yum']: 'tkinter' is installed on Rstudio for AWS > [RedHat] > # Rstudio is created on AWS [Debian] > # Rstudio is created on GCP [Debian] > # Rstudio is created on Azure [Debian][RedHat] > *Steps to reproduce:* > # Install Library RStudio ['apt/yum'] on AWS [Debian] via Dlab UI > # Install Library RStudio ['apt/yum'] on GCP [Debian] via Dlab UI > # Install Library RStudio ['apt/yum'] on on Azure [Debian][RedHat] via Dlab > UI > *Actual result:* > # Library RStudio ['apt/yum'] on AWS [Debian] is not in available lib list > # Library RStudio ['apt/yum'] on GCP [Debian] is not in available lib list > # Library RStudio ['apt/yum'] on Azure [Debian][RedHat] is not in available > lib list > *Expected result:* > # Library RStudio ['apt/yum'] on AWS [Debian] is installed > # Library RStudio ['apt/yum'] on GCP [Debian] is installed > # Library RStudio ['apt/yum'] on Azure [Debian][RedHat] is installed -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-282) Access to S3 bucket should be restricted from AWS Web Console
[ https://issues.apache.org/jira/browse/DLAB-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-282: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: AWS > Access to S3 bucket should be restricted from AWS Web Console > - > > Key: DLAB-282 > URL: https://issues.apache.org/jira/browse/DLAB-282 > Project: Apache DLab > Issue Type: Task > Components: AWS >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > > As a user I want that only I (except for admin) have access to my personal > bucket from AWS Web Console. > You need to assign proper policy to individual bucket. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-13) [GCP]: Flexible disk size for instances
[ https://issues.apache.org/jira/browse/DLAB-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-13: -- Labels: Debian (was: ) Component/s: GCP > [GCP]: Flexible disk size for instances > --- > > Key: DLAB-13 > URL: https://issues.apache.org/jira/browse/DLAB-13 > Project: Apache DLab > Issue Type: New Feature > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian > > As a user I want to choose disk size during Notebook/computational resource > creation or change the parameter of already existed Notebook/computational > resource so that I can add more space by necessary on GCP. > > *Acceptance criteria:* > # during creation Notebook/computational resource it should be new drop down > list, from which user can choose value of disk size > # in case of existed Notebook/computational resource it should be 'Volume' > button on action menu. If user click 'Volume' button a new 'Volume' popup > open and user can see disk size of current Notebook/computational resource > and change value -- This message was sent by Atlassian 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-40) Flexible disk size
[ https://issues.apache.org/jira/browse/DLAB-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-40: -- Epic Name: Flexible disk size > Flexible disk size > -- > > Key: DLAB-40 > URL: https://issues.apache.org/jira/browse/DLAB-40 > Project: Apache DLab > Issue Type: Epic > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > > As a user I want to use Angular 6.x in Dlab so that I can use updated > material components. > Currently Angular 5.x is used in DLab. > > *Acceptance criteria:* > 1. angular 6.x is used 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-40) Flexible disk size
[ https://issues.apache.org/jira/browse/DLAB-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-40: -- Labels: (was: Front-end) Component/s: GCP Azure AWS Issue Type: Epic (was: Task) Summary: Flexible disk size (was: Migration to Angular 6.x) > Flexible disk size > -- > > Key: DLAB-40 > URL: https://issues.apache.org/jira/browse/DLAB-40 > Project: Apache DLab > Issue Type: Epic > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > > As a user I want to use Angular 6.x in Dlab so that I can use updated > material components. > Currently Angular 5.x is used in DLab. > > *Acceptance criteria:* > 1. angular 6.x is used 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-286) [Spark reconfiguration]: Add validation for Spark parameters from UI side
[ https://issues.apache.org/jira/browse/DLAB-286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-286: --- Labels: Debian Front-end RedHat (was: ) Component/s: GCP Azure AWS > [Spark reconfiguration]: Add validation for Spark parameters from UI side > - > > Key: DLAB-286 > URL: https://issues.apache.org/jira/browse/DLAB-286 > Project: Apache DLab > Issue Type: New Feature > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, Front-end, RedHat > > During Spark reconfiguration user can enter wrong parameters for spark, > please investigate how it can be validated. -- This message was sent by Atlassian 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-96) Using a personal access token and transferring it during deploy
[ https://issues.apache.org/jira/browse/DLAB-96?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-96: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: AWS > Using a personal access token and transferring it during deploy > --- > > Key: DLAB-96 > URL: https://issues.apache.org/jira/browse/DLAB-96 > Project: Apache DLab > Issue Type: Task > Components: AWS >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps, RedHat > Attachments: API.PNG > > > As a user I want to use personal access token and transfer it during deploy. > > For example, go to this link > [https://help.github.com/articles/creating-a-personal-access-token-for-the-command-line/] -- This message was sent by Atlassian 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-45) It should possible to delete any/all libs in failed state
[ https://issues.apache.org/jira/browse/DLAB-45?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-45: -- Labels: Debian RedHat (was: ) Component/s: GCP Azure AWS > It should possible to delete any/all libs in failed state > - > > Key: DLAB-45 > URL: https://issues.apache.org/jira/browse/DLAB-45 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, RedHat > > As a user I want to have possibility to delete failed libraries. > > *Acceptance criteria:* > 1. there is 'Delete' button nearby failed library > 2. if user chooses 'Delete' button failed library is deleted from instance -- This message was sent by Atlassian 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-88) SNS terminate fails on process of notebook's vpc deletion
[ https://issues.apache.org/jira/browse/DLAB-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-88: -- Component/s: (was: GCP) (was: Azure) > SNS terminate fails on process of notebook's vpc deletion > - > > Key: DLAB-88 > URL: https://issues.apache.org/jira/browse/DLAB-88 > Project: Apache DLab > Issue Type: Bug > Components: AWS >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, RedHat > Attachments: Notebook's vpc.PNG > > > *Preconditions:* > SSN is created with two VPCs /subnets/SG by default (parameters are not > defined) > > *Steps to reproduce:* > 1. Terminate SSN using job > [http://35.166.222.81/job/aws_isn_terminate-1847/] > > *Actual result:* > SSN termination fails with error: > *The vpc 'vpc-0fc801d1f2f8321de' has dependencies and cannot be deleted* > *!Notebook's vpc.PNG!* > > *Expected result:* > SSN is 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] [Updated] (DLAB-63) Investigate how to stop slaves after stopping master via cloud console
[ https://issues.apache.org/jira/browse/DLAB-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-63: -- Labels: Debian DevOps RedHat (was: DevOps) Description: As a user I want that slaves will be stopped automatically after stopping master via cloud console, so that it reduce charges for running slaves. *Acceptance criteria:* 1. Slaves instances are automatically stopped after master node is stopped via cloud console was: As a user I want that slaves will be stopped automatically after stopping master via AWS console, so that it reduce charges for running slaves. *Acceptance criteria:* 1. Slaves instances are automatically stopped after master node is stopped via AWS console Component/s: GCP Azure AWS > Investigate how to stop slaves after stopping master via cloud console > -- > > Key: DLAB-63 > URL: https://issues.apache.org/jira/browse/DLAB-63 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, DevOps, RedHat > > As a user I want that slaves will be stopped automatically after stopping > master via cloud console, so that it reduce charges for running slaves. > > *Acceptance criteria:* > 1. Slaves instances are automatically stopped after master node is stopped > via cloud console -- This message was sent by Atlassian 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-63) Investigate how to stop slaves after stopping master via cloud console
[ https://issues.apache.org/jira/browse/DLAB-63?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-63: -- Summary: Investigate how to stop slaves after stopping master via cloud console (was: [AWS]: Investigate how to stop slaves after stopping master via AWS console) > Investigate how to stop slaves after stopping master via cloud console > -- > > Key: DLAB-63 > URL: https://issues.apache.org/jira/browse/DLAB-63 > Project: Apache DLab > Issue Type: Task >Reporter: Vira Vitanska >Priority: Minor > Labels: DevOps > > As a user I want that slaves will be stopped automatically after stopping > master via AWS console, so that it reduce charges for running slaves. > > *Acceptance criteria:* > 1. Slaves instances are automatically stopped after master node is stopped > via AWS console -- This message was sent by Atlassian 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-55) [GCP]: Add functionality to check maitenance events for VMs with GPU
[ https://issues.apache.org/jira/browse/DLAB-55?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-55: -- Labels: Debian DevOps (was: DevOps) Component/s: GCP > [GCP]: Add functionality to check maitenance events for VMs with GPU > > > Key: DLAB-55 > URL: https://issues.apache.org/jira/browse/DLAB-55 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps > > Investigate what will be with VMs based on GPU during maitenance events. > > _***According to GCP rules they are limited in several regions ._ > _There is maithenance in them once a week . So when it does it in the > corresponding API within 60 seconds there is a corresponding message that you > will take away the video card._ -- This message was sent by Atlassian 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-49) [GCP]: Add script to deploy own GitLab server
[ https://issues.apache.org/jira/browse/DLAB-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-49: -- Labels: Debian DevOps (was: DevOps) Component/s: GCP > [GCP]: Add script to deploy own GitLab server > - > > Key: DLAB-49 > URL: https://issues.apache.org/jira/browse/DLAB-49 > Project: Apache DLab > Issue Type: Task > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps > > As a user I want to deploy own Gitlab server on GCP via Jenkins. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-24) [GCP]: Fix scripts for undelete and update roles if deploy failed during first start with the same name
[ https://issues.apache.org/jira/browse/DLAB-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-24: -- Labels: Debian DevOps (was: DevOps) Component/s: GCP > [GCP]: Fix scripts for undelete and update roles if deploy failed during > first start with the same name > --- > > Key: DLAB-24 > URL: https://issues.apache.org/jira/browse/DLAB-24 > Project: Apache DLab > Issue Type: Bug > Components: GCP > Environment: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps > > A bug reproduces if deploy previously failed SSN using the same name. > > *Preconditions:* > SSN creation with name 'test1' failed > > *Steps to reproduce:* > # Create again SSN with the same name 'test1' > > *Actual result:* > SSN recreation with name 'test1' failed due to undeleted roles > > *Expected result:* > SSN recreation with name 'test1' is succesful -- This message was sent by Atlassian 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-22) Need to change behavior of Show Active button
[ https://issues.apache.org/jira/browse/DLAB-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-22: -- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > Need to change behavior of Show Active button > - > > Key: DLAB-22 > URL: https://issues.apache.org/jira/browse/DLAB-22 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, Front-end, RedHat > > As a user I want to be notified about failing computational resources in > 'show active' mode so that I do not need to switch to 'show all' mode. > > *Case:* > 1. on resources_list page 'show active' button is chosen > 2. computational resource is creating > 3. creating computational resource fails > It should be possibility to 'notify' user about failed computational resource. > Because in 'show active' mode this computational resource will not be > portayed untill a user change mode to 'show all'. > > *Acceptance criteria:* > 1. user should receive notify about unsuccessful computational resources > creating in 'show active' mode on resource list page > -- This message was sent by Atlassian JIRA (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-21) [GCP]: Data Engibe Service creation fails after environment has been recreated
[ https://issues.apache.org/jira/browse/DLAB-21?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-21: -- Summary: [GCP]: Data Engibe Service creation fails after environment has been recreated (was: [GCP]: Dataproc creation fails after environment has been recreated) > [GCP]: Data Engibe Service creation fails after environment has been recreated > -- > > Key: DLAB-21 > URL: https://issues.apache.org/jira/browse/DLAB-21 > Project: Apache DLab > Issue Type: Bug > Components: GCP > Environment: GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, DevOps > Attachments: Dataproc.PNG, Dataproc.txt > > > A bug was found on GCP on Jupyter > > *Preconditions:* > 1. User1 environment has been created after admin's termination > 2. Jupyter is running on user1 environment > > *Steps to reproduce:* > # Create Dataproc on Jupyter > > *Actual result:* > Dataproc creation fails through *Service Accounts must have either > 'Dataproc/Dataproc Worker' role or all permissions granted by the > role**!Dataproc.PNG!* > *!Dataproc.PNG!* > *Expected result:* > Dataproc 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-20) [GCP]: User1 can read/write from/to personal bucket user2
[ https://issues.apache.org/jira/browse/DLAB-20?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-20: -- Labels: Debian DevOps (was: DevOps) Component/s: GCP > [GCP]: User1 can read/write from/to personal bucket user2 > - > > Key: DLAB-20 > URL: https://issues.apache.org/jira/browse/DLAB-20 > Project: Apache DLab > Issue Type: Bug > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian, DevOps > > *Preconditions:* > Two users have environments on one SSN > *Steps to reproduce:* > 1. Run preparation playbook for Jupyter by user1 using personal bucket user2 > 2. Run visualization playbook for Jupyter by user1 using personal bucket user2 > *Actual result:* > User1 is able to read/write from/to personal bucket user2 > *Expected result:* > It is forbidden for user1 to read/write from/to personal bucket user2 -- This message was sent by Atlassian 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-17) Prepare manual (runbook) for troubleshooting
[ https://issues.apache.org/jira/browse/DLAB-17?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-17: -- Labels: Debian DevOps RedHat (was: DevOps) Component/s: GCP Azure AWS > Prepare manual (runbook) for troubleshooting > > > Key: DLAB-17 > URL: https://issues.apache.org/jira/browse/DLAB-17 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Minor > Labels: Debian, DevOps, RedHat > > As a user I want to have a list of troubleshooting concerning creation of > SSN, docker during DLab using and deploy so that can easily to eliminate some > issues connected with DLab. > > *Acceptance criteria:* > 1. troubleshooting concerning creation of SSN, docker during DLab deploy are > listed in runbook > -- This message was sent by Atlassian 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-376) Add name of active page to DLab menu bar
[ https://issues.apache.org/jira/browse/DLAB-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-376: --- Labels: Debian Front-end RedHat (was: Front-end) > Add name of active page to DLab menu bar > > > Key: DLAB-376 > URL: https://issues.apache.org/jira/browse/DLAB-376 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Anna Orlovska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Debian, Front-end, RedHat > Fix For: v.2.2 > > Attachments: DLab_menu_bar.png > > > The name of active page should be displayed on DLab menu bar. > !DLab_menu_bar.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-376) Add name of active page to DLab menu bar
[ https://issues.apache.org/jira/browse/DLAB-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-376: --- Component/s: GCP Azure AWS > Add name of active page to DLab menu bar > > > Key: DLAB-376 > URL: https://issues.apache.org/jira/browse/DLAB-376 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Anna Orlovska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Front-end > Fix For: v.2.2 > > Attachments: DLab_menu_bar.png > > > The name of active page should be displayed on DLab menu bar. > !DLab_menu_bar.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-323) [2 VPCs]: Tags are absent for second vpc/peering connection/route table
[ https://issues.apache.org/jira/browse/DLAB-323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-323: --- Component/s: (was: GCP) (was: Azure) > [2 VPCs]: Tags are absent for second vpc/peering connection/route table > --- > > Key: DLAB-323 > URL: https://issues.apache.org/jira/browse/DLAB-323 > Project: Apache DLab > Issue Type: Bug > Components: AWS > Environment: AWS >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.2 > > > *Steps to reproduce:* > 1. create SSN with 2 VPCs > > *Actual result:* > names are absent for second vpc/peering connection/route table > > *Expected result:* > names are present for second vpc/peering connection/route table -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-429) Investigate compatibility and co-working Nginx and Squid
[ https://issues.apache.org/jira/browse/DLAB-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-429: --- Component/s: GCP Azure AWS > Investigate compatibility and co-working Nginx and Squid > > > Key: DLAB-429 > URL: https://issues.apache.org/jira/browse/DLAB-429 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Priority: Major > Labels: DevOps > Fix For: v.2.2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-384) Improvements for manage role
[ https://issues.apache.org/jira/browse/DLAB-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-384: -- Assignee: Bohdan Hliva > Improvements for manage role > > > Key: DLAB-384 > URL: https://issues.apache.org/jira/browse/DLAB-384 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Debian, RedHat > Fix For: v.2.2 > > > As an admin I want to have more user friendly actions for role management. > 1. Add buttons 'Apply' 'Cancel' > 2. Remove 'apply' icon from action > 3. Remove 'View full billing reports for all user' from 'Roles' drop down list > 4. Move 'Allow to execute adminastrative operation' from 'Roles' drop down > list to action grid > 5. Group by shape/template in 'Roles' 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-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: --- Labels: DevOps (was: ) > [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 > Labels: DevOps > 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-331) [Azure]: Adjust deploy script
[ https://issues.apache.org/jira/browse/DLAB-331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-331: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: Azure > [Azure]: Adjust deploy script > - > > Key: DLAB-331 > URL: https://issues.apache.org/jira/browse/DLAB-331 > Project: Apache DLab > Issue Type: Task > Components: Azure >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Major > Labels: Debian, DevOps, RedHat > Fix For: v.2.2 > > > Move script from post-build to deploy script. -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-329) Information about exceptions is absent during provisioning resources
[ https://issues.apache.org/jira/browse/DLAB-329?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-329: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: AWS > Information about exceptions is absent during provisioning resources > > > Key: DLAB-329 > URL: https://issues.apache.org/jira/browse/DLAB-329 > Project: Apache DLab > Issue Type: Bug > Components: AWS >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: Debian, DevOps, RedHat > Fix For: v.2.2 > > Attachments: Cidr.PNG > > > *Steps to reproduce:* > # Create SSN on AWS with allowed_ip_cidr without defined parameters > aws_subnet_id and aws_sg_ids > > feature-branches/job/aws_vitv/36 > *Expected result:* > SSN is created -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-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: --- Fix Version/s: v.2.2 > [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 > Fix For: v.2.2 > > 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-375) [Admin page]: Merge 'Health status' and 'Environment Management' pages
[ https://issues.apache.org/jira/browse/DLAB-375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated DLAB-375: Labels: Debian Front-end RedHat pull-request-available (was: Debian Front-end RedHat) > [Admin page]: Merge 'Health status' and 'Environment Management' pages > -- > > Key: DLAB-375 > URL: https://issues.apache.org/jira/browse/DLAB-375 > Project: Apache DLab > Issue Type: Improvement > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Debian, Front-end, RedHat, pull-request-available > Fix For: v.2.2 > > > As an admin I want to have administration page in one place. > 1. *Move 'Health status' page to 'Environment Management' pages adding > buttons on the right top:* > 1.1. 'Manage roles' > 1.2. 'SSN Monitor' > 1.3. 'Manage environment' > 1.4. 'Backup' > 2. *If Admin click on icon 'health status' the 'Environment Management' page > opens with the following sorted:* > 2.1 by current user and edge > 2.2. reupload key/ recreate edge should be only for current user (the > actions should not be displays for other user if even Admin is logged in) > 3. *If user is logged in (Not Admin) can see:* > 3.1. only own environment NOT other users > 3.2. only user's edge status with appropriate actions: > stop/start/recreate/reupload key -- This message was sent by Atlassian 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-506) Teck-debt
Vira Vitanska created DLAB-506: -- Summary: Teck-debt Key: DLAB-506 URL: https://issues.apache.org/jira/browse/DLAB-506 Project: Apache DLab Issue Type: Epic Reporter: Vira Vitanska -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] AndrianaKovalyshyn opened a new pull request #21: [DLAB-375][Admin page]: Merge Health status and Environment Management pages
AndrianaKovalyshyn opened a new pull request #21: [DLAB-375][Admin page]: Merge Health status and Environment Management pages URL: https://github.com/apache/incubator-dlab/pull/21 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-390) [GCP]: Notebook starting fails (previously it was stopped)
[ https://issues.apache.org/jira/browse/DLAB-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-390: --- Labels: Debian DevOps (was: DevOps) Description: First of all the bug was found during starting RStudio. And now the bug reproduced for Jupyter, Zeppelin randomly. Notebook after starting fails or if starting is successful it is impossible to go to UI Notebook *Preconditions:* RStudio is in 'stopped' status *Steps to reproduce:* 1. Start RStudio *Actual result:* RStudio starting fails with error *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 (tried 100 times)* !RStudio starting.PNG! *Expected result:* RStudio starting is successful was: First of all the bug was found during starting RStudio. And now the bug reproduced for Jupyter, Zeppelin randomly. Notebook after starting fails or if starting is successful it is impossible to go to UI Notebook *Preconditions:* RStudio is in 'stopped' status *Steps to reproduce:* 1. Start RStudio *Actual result:* RStudio starting fails with error *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 (tried 100 times)* !RStudio starting.PNG! *Expected result:* RStudio starting is successful __ First of all the bug was found during starting RStudio. Now the bug is reproduced for Jupyter/Zeppelin after restarting notebook (it is impossible to go to Notebook UI). Please. see comments Component/s: GCP Summary: [GCP]: Notebook starting fails (previously it was stopped) (was: [GCP]: It is impossible to go to UI notebook after its starting (previously it was stopped)) > [GCP]: Notebook starting fails (previously it was stopped) > -- > > Key: DLAB-390 > URL: https://issues.apache.org/jira/browse/DLAB-390 > Project: Apache DLab > Issue Type: Bug > Components: GCP > Environment: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Blocker > Labels: Debian, DevOps > Fix For: v.2.2 > > Attachments: Notebook UI.PNG, RStudio starting.PNG, jup-error.png > > > First of all the bug was found during starting RStudio. And now the bug > reproduced for Jupyter, Zeppelin randomly. Notebook after starting fails or > if starting is successful it is impossible to go to UI Notebook > *Preconditions:* > RStudio is in 'stopped' status > *Steps to reproduce:* > 1. Start RStudio > *Actual result:* > RStudio starting fails with error > *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 > (tried 100 times)* > !RStudio starting.PNG! > *Expected result:* > RStudio starting is successful -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-390) [GCP]: It is impossible to go to UI notebook after its starting (previously it was stopped)
[ https://issues.apache.org/jira/browse/DLAB-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-390: --- Description: First of all the bug was found during starting RStudio. And now the bug reproduced for Jupyter, Zeppelin randomly. Notebook after starting fails or if starting is successful it is impossible to go to UI Notebook *Preconditions:* RStudio is in 'stopped' status *Steps to reproduce:* 1. Start RStudio *Actual result:* RStudio starting fails with error *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 (tried 100 times)* !RStudio starting.PNG! *Expected result:* RStudio starting is successful __ First of all the bug was found during starting RStudio. Now the bug is reproduced for Jupyter/Zeppelin after restarting notebook (it is impossible to go to Notebook UI). Please. see comments was: First of all the bug was found during starting rstudio. Now the bug reproduced for Jupyter, Zeppelin randomly. *Preconditions:* RStudio is in 'stopped' status *Steps to reproduce:* 1. Start RStudio *Actual result:* RStudio starting fails with error *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 (tried 100 times)* !RStudio starting.PNG! *Expected result:* RStudio starting is successful __ First of all the bug was found during starting RStudio. Now the bug is reproduced for Jupyter/Zeppelin after restarting notebook (it is impossible to go to Notebook UI). Please. see comments > [GCP]: It is impossible to go to UI notebook after its starting (previously > it was stopped) > --- > > Key: DLAB-390 > URL: https://issues.apache.org/jira/browse/DLAB-390 > Project: Apache DLab > Issue Type: Bug > Environment: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Blocker > Labels: DevOps > Fix For: v.2.2 > > Attachments: Notebook UI.PNG, RStudio starting.PNG, jup-error.png > > > First of all the bug was found during starting RStudio. And now the bug > reproduced for Jupyter, Zeppelin randomly. Notebook after starting fails or > if starting is successful it is impossible to go to UI Notebook > *Preconditions:* > RStudio is in 'stopped' status > *Steps to reproduce:* > 1. Start RStudio > *Actual result:* > RStudio starting fails with error > *fabric.exceptions.NetworkError: Timed out trying to connect to 172.31.16.14 > (tried 100 times)* > !RStudio starting.PNG! > *Expected result:* > RStudio starting is successful > __ > First of all the bug was found during starting RStudio. Now the bug is > reproduced for Jupyter/Zeppelin after restarting notebook (it is impossible > to go to Notebook UI). Please. see comments -- This message was sent by Atlassian 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-245) Add a local git hook script for checking commit message
[ https://issues.apache.org/jira/browse/DLAB-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-245: --- Component/s: GCP Azure AWS > Add a local git hook script for checking commit message > --- > > Key: DLAB-245 > URL: https://issues.apache.org/jira/browse/DLAB-245 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Bohdan Hliva >Priority: Major > Labels: Back-end > Fix For: v.2.1 > > Attachments: Test1.PNG, install_commit_msg_hook.txt > > > As a DLab contributor I want to use local git hook script in order to > restrict commits different than the format proposed > Acceptance criteria: > 1. local git hook script is created > 2. instruction is written how to install script > 3. if commits are different than the format proposed a user see appropriate > error message and commits are not allowed to do > 4. if commits are the same as the format proposed so user is allowed to commit -- This message was sent by Atlassian 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-505) Git
Vira Vitanska created DLAB-505: -- Summary: Git Key: DLAB-505 URL: https://issues.apache.org/jira/browse/DLAB-505 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-504) Jenkins
Vira Vitanska created DLAB-504: -- Summary: Jenkins Key: DLAB-504 URL: https://issues.apache.org/jira/browse/DLAB-504 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-182) Persist/Restore reply to self-service from provisioning-service in case self-service is unavailable
[ https://issues.apache.org/jira/browse/DLAB-182?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-182: --- Labels: Back-end Debian RedHat (was: Back-end) Component/s: GCP Azure AWS > Persist/Restore reply to self-service from provisioning-service in case > self-service is unavailable > --- > > Key: DLAB-182 > URL: https://issues.apache.org/jira/browse/DLAB-182 > 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 > > > Health check should be used to verify availability of self-service -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-198) [Jenkins]:Create jobs for master v.2.0 [branch v.2.0.1] and develop v.2.1 [branch develop] for AWS/Azure/GCP].1
[ https://issues.apache.org/jira/browse/DLAB-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-198: --- Component/s: GCP Azure AWS > [Jenkins]:Create jobs for master v.2.0 [branch v.2.0.1] and develop v.2.1 > [branch develop] for AWS/Azure/GCP].1 > --- > > Key: DLAB-198 > URL: https://issues.apache.org/jira/browse/DLAB-198 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Minor > Labels: DevOps > Fix For: v.2.1 > > > # Create jobs (create environment/terminate environment) master v.2.0 from > branch v2.0.1 for AWS, Azure, GCP in Jenkins > # Create jobs (create environment/terminate environmrnt) develop v.2.1 from > branch develop for AWS, Azure, GCP in Jenkins -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-503) DLab promotion
Vira Vitanska created DLAB-503: -- Summary: DLab promotion Key: DLAB-503 URL: https://issues.apache.org/jira/browse/DLAB-503 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-306) Increase rating of DLab promotion page
[ https://issues.apache.org/jira/browse/DLAB-306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-306: --- Component/s: GCP Azure AWS > Increase rating of DLab promotion page > -- > > Key: DLAB-306 > URL: https://issues.apache.org/jira/browse/DLAB-306 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Major > Labels: Front-end > Fix For: v.2.1 > > > [http://dlab.opensource.epam.com/] -- This message was sent by Atlassian 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-502) [GCP]: Implement DLab instalation via private IP
Vira Vitanska created DLAB-502: -- Summary: [GCP]: Implement DLab instalation via private IP Key: DLAB-502 URL: https://issues.apache.org/jira/browse/DLAB-502 Project: Apache DLab Issue Type: Improvement Components: GCP Reporter: Vira Vitanska As a user I want to install DLab via private IP *Acceptance criteria:* 1. All instances should have only private IP -- This message was sent by Atlassian 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-501) Private IP
Vira Vitanska created DLAB-501: -- Summary: Private IP Key: DLAB-501 URL: https://issues.apache.org/jira/browse/DLAB-501 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-312) [GCP]: Autotest fails due to can not uploading data to personal bucket
[ https://issues.apache.org/jira/browse/DLAB-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-312: --- Fix Version/s: v.2.1 > [GCP]: Autotest fails due to can not uploading data to personal bucket > -- > > Key: DLAB-312 > URL: https://issues.apache.org/jira/browse/DLAB-312 > Project: Apache DLab > Issue Type: Bug > Components: GCP >Reporter: Vira Vitanska >Assignee: Demyan Mysakovets >Priority: Major > Labels: Debian, DevOps > Fix For: v.2.1 > > > *Steps to reproduce:* > 1. Run autotest for GCP > *Actual result:* > Autotest fails with error: > *Fatal error: local() encountered an error (return code 1) while executing > 'gsutil -m cp /tmp/airports.csv gs://it63-dlab-test-bucket/rstudio_dataset/* > [job/AutoTests_GCP/111/|http://35.166.222.81/job/AutoTests_GCP/111/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-499) Add support of installing DLab into two VPCs
Vira Vitanska created DLAB-499: -- Summary: Add support of installing DLab into two VPCs Key: DLAB-499 URL: https://issues.apache.org/jira/browse/DLAB-499 Project: Apache DLab Issue Type: Improvement Components: GCP 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-499) Add support of installing DLab into two VPCs
[ https://issues.apache.org/jira/browse/DLAB-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-499: --- Labels: Debian (was: Debian RedHat) > Add support of installing DLab into two VPCs > > > Key: DLAB-499 > URL: https://issues.apache.org/jira/browse/DLAB-499 > Project: Apache DLab > Issue Type: Improvement > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-499) [GCP]: Add support of installing DLab into two VPCs
[ https://issues.apache.org/jira/browse/DLAB-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-499: --- Summary: [GCP]: Add support of installing DLab into two VPCs (was: Add support of installing DLab into two VPCs) > [GCP]: Add support of installing DLab into two VPCs > --- > > Key: DLAB-499 > URL: https://issues.apache.org/jira/browse/DLAB-499 > Project: Apache DLab > Issue Type: Improvement > Components: GCP >Reporter: Vira Vitanska >Priority: Major > Labels: Debian > -- This message was sent by Atlassian JIRA (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-500) [Azure]: Add support of installing DLab into two VPCs
Vira Vitanska created DLAB-500: -- Summary: [Azure]: Add support of installing DLab into two VPCs Key: DLAB-500 URL: https://issues.apache.org/jira/browse/DLAB-500 Project: Apache DLab Issue Type: Improvement Components: Azure 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-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-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-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] [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-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-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-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-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] [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-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-175) [AWS]: EMR creation fails
[ https://issues.apache.org/jira/browse/DLAB-175?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-175: --- Labels: Debian DevOps RedHat (was: DevOps) Component/s: AWS > [AWS]: EMR creation fails > - > > Key: DLAB-175 > URL: https://issues.apache.org/jira/browse/DLAB-175 > Project: Apache DLab > Issue Type: Bug > Components: AWS >Reporter: Vira Vitanska >Assignee: Oleksandr Isniuk >Priority: Critical > Labels: Debian, DevOps, RedHat > Fix For: v.2.1 > > > *Preconditions:* > Environment is created > > *Steps to reproduce:* > 1. Create EMR > > *Actual result:* > EMR creation fails: > *File "/usr/lib/python2.7/UserDict.py", line 40, in __getitem__* > *raise KeyError(key)* > > *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-174) URL should be in one row on Notebook name popup
[ https://issues.apache.org/jira/browse/DLAB-174?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-174: --- Labels: Debian Front-end RedHat (was: Front-end) Component/s: GCP Azure AWS > URL should be in one row on Notebook name popup > --- > > Key: DLAB-174 > URL: https://issues.apache.org/jira/browse/DLAB-174 > 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 > > Attachments: image-2018-12-19-22-19-27-389.png > > > *Preconditions:* > Notebook with long name is created > > *Steps to reproduce:* > # Click Notebook name popup > > *Actual result:* > Ungit link is portrayed in two rows > !image-2018-12-19-22-19-27-389.png! > *Expected result:* > 1. ungit link should not be splitted in 2 lines (ungit link is portrayed only > in one row)/ > 2. url is cutted -- This message was sent by Atlassian 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-192) [BE]: Attribution and proper use of Apache Software Foundation trademarks
[ https://issues.apache.org/jira/browse/DLAB-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-192: --- Component/s: GCP Azure AWS > [BE]: Attribution and proper use of Apache Software Foundation trademarks > - > > Key: DLAB-192 > URL: https://issues.apache.org/jira/browse/DLAB-192 > Project: Apache DLab > Issue Type: Task > Components: AWS, Azure, GCP >Reporter: Vira Vitanska >Assignee: Oleksandr Chaparin >Priority: Major > Labels: Back-end > Fix For: v.2.1 > > > Over the last few months I’ve been facing with a significant number of slide > decks and white papers, prepared by our experts for the clients, and used in > the pre-sales and other meetings. While not in 100% of the cases, but yet a > common scheme is to mis-attribute the FOSS projects and technologies used in > our solution. This is specifically noticeable in the case of Apache Software > Foundation projects, because they are the most widely used technologies in > our immediate area of expertise. > it is pretty important to use the proper attribution and trademarked names. > The rule of thumb is to always prepend the project name with Apache i.e. it > is always Apache Hadoop, Apache Parquet, Apache Hive, Apache Spark, Apache > Zeppelin and so on. The more information and helpful resource could be found > at [1] > [1] [https://kb.epam.com/display/EPMCBDCC/Trademark+attributions] -- This message was sent by Atlassian 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
[jira] [Updated] (DLAB-239) [GCP]: Error message is beyond of "Add computational resources" popup
[ https://issues.apache.org/jira/browse/DLAB-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-239: --- Labels: Debian Front-end (was: Front-end) Component/s: GCP > [GCP]: Error message is beyond of "Add computational resources" popup > - > > Key: DLAB-239 > URL: https://issues.apache.org/jira/browse/DLAB-239 > Project: Apache DLab > Issue Type: Bug > Components: GCP >Reporter: Vira Vitanska >Assignee: Andriana Kovalyshyn >Priority: Minor > Labels: Debian, Front-end > Fix For: v.2.1 > > Attachments: image-2018-12-20-10-39-28-981.png > > > *Preconditions:* > 1. Notebook is created > 2. "Add computational resources" popup is opne > *Steps to reproduce:* > 1. choose Dataproc cluster in "Select cluster type" drop down list > 2. check off "Preemptible node count" check box > 3. enter not valid vulue for "Preemptible node count"? for example 23 > *Actual result:* > error message "Only integer values greater than or equal to 0 and less than > 11 are allowed" beyond of "Add computational resources" popup > !image-2018-12-20-10-39-28-981.png! > *Expected result:* > error message "Only integer values greater than or equal to 0 and less than > 11 are allowed" appers under "Preemptible node count" 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-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-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-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-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-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-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-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-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
