[jira] [Updated] (DLAB-1587) [Billing report]: Service and
[ https://issues.apache.org/jira/browse/DLAB-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1587: Attachment: Size.mov > [Billing report]: Service and > -- > > Key: DLAB-1587 > URL: https://issues.apache.org/jira/browse/DLAB-1587 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Size.mov > > > *1.* 'It is only demo preview for Dataproc job tracker UI. For real > environment you can use all available tools on Dataproc -> It is only demo > preview for Hadoop UI. For real environment you can use all available tools > on Hadoop. > *2.* 'It is only demo preview for Apache Spark job tracker UI. For real > environment you can use all available tools on Apache Spark job tracker UI' > -> 'It is only demo preview for Apache Spark Master UI. For real environment > you can use all available tools on Apache Spark Master UI' > *3.* Information about demo preview should not be cut for computational > resources > *4.* The modal window should have fixed size -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1587) [Billing report]: Service and
[ https://issues.apache.org/jira/browse/DLAB-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1587: Description: *1.* 'It is only demo preview for Dataproc job tracker UI. For real environment you can use all available tools on Dataproc -> It is only demo preview for Hadoop UI. For real environment you can use all available tools on Hadoop. *2.* 'It is only demo preview for Apache Spark job tracker UI. For real environment you can use all available tools on Apache Spark job tracker UI' -> 'It is only demo preview for Apache Spark Master UI. For real environment you can use all available tools on Apache Spark Master UI' *3.* Information about demo preview should not be cut for computational resources *4.* The modal window should have fixed size was: 1. 'It is only demo preview for Dataproc job tracker UI. For real environment you can use all available tools on Dataproc -> It is only demo preview for Hadoop UI. For real environment you can use all available tools on Hadoop. 2. 'It is only demo preview for Apache Spark job tracker UI. For real environment you can use all available tools on Apache Spark job tracker UI' -> 'It is only demo preview for Apache Spark Master UI. For real environment you can use all available tools on Apache Spark Master UI' 3. Information about demo preview should not be cut for computational resources 4. The modal window should have fixed size > [Billing report]: Service and > -- > > Key: DLAB-1587 > URL: https://issues.apache.org/jira/browse/DLAB-1587 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Size.mov > > > *1.* 'It is only demo preview for Dataproc job tracker UI. For real > environment you can use all available tools on Dataproc -> It is only demo > preview for Hadoop UI. For real environment you can use all available tools > on Hadoop. > *2.* 'It is only demo preview for Apache Spark job tracker UI. For real > environment you can use all available tools on Apache Spark job tracker UI' > -> 'It is only demo preview for Apache Spark Master UI. For real environment > you can use all available tools on Apache Spark Master UI' > *3.* Information about demo preview should not be cut for computational > resources > *4.* The modal window should have fixed size -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1587) [Billing report]: Service and
[ https://issues.apache.org/jira/browse/DLAB-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1587: Attachment: Computational resource.png > [Billing report]: Service and > -- > > Key: DLAB-1587 > URL: https://issues.apache.org/jira/browse/DLAB-1587 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Computational resource.png, Size.mov > > > *1.* 'It is only demo preview for Dataproc job tracker UI. For real > environment you can use all available tools on Dataproc -> It is only demo > preview for Hadoop UI. For real environment you can use all available tools > on Hadoop. > *2.* 'It is only demo preview for Apache Spark job tracker UI. For real > environment you can use all available tools on Apache Spark job tracker UI' > -> 'It is only demo preview for Apache Spark Master UI. For real environment > you can use all available tools on Apache Spark Master UI' > *3.* Information about demo preview should not be cut for computational > resources > *4.* The modal window should have fixed size -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1587) Adjust images for demo-regime
[ https://issues.apache.org/jira/browse/DLAB-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1587: Summary: Adjust images for demo-regime (was: [Billing report]: Service and ) > Adjust images for demo-regime > - > > Key: DLAB-1587 > URL: https://issues.apache.org/jira/browse/DLAB-1587 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Computational resource.png, Size.mov > > > *1.* 'It is only demo preview for Dataproc job tracker UI. For real > environment you can use all available tools on Dataproc -> It is only demo > preview for Hadoop UI. For real environment you can use all available tools > on Hadoop. > *2.* 'It is only demo preview for Apache Spark job tracker UI. For real > environment you can use all available tools on Apache Spark job tracker UI' > -> 'It is only demo preview for Apache Spark Master UI. For real environment > you can use all available tools on Apache Spark Master UI' > *3.* Information about demo preview should not be cut for computational > resources > *4.* The modal window should have fixed size -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1501) [AWS]: Notebook creation fails on external endpoint in the same cloud where SSN is deployed
[ https://issues.apache.org/jira/browse/DLAB-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1501: Summary: [AWS]: Notebook creation fails on external endpoint in the same cloud where SSN is deployed (was: Notebook creation fails on external endpoint in the same cloud where SSN is deployed) > [AWS]: Notebook creation fails on external endpoint in the same cloud where > SSN is deployed > --- > > Key: DLAB-1501 > URL: https://issues.apache.org/jira/browse/DLAB-1501 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.3 > > Attachments: Notebook creation.png > > > *Preconditions:* > # SSN is created on AWS > # External 'endpoint1' is created on AWS > *Steps to reproduce:* > 1. Create notebook on External 'endpoint1' > *Actual result:* > 1. Notebook creation fails > *Expected result:* > # Notebook is created successfully -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1501) Notebook creation fails on external endpoint in the same cloud where SSN is deployed
[ https://issues.apache.org/jira/browse/DLAB-1501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1501: Description: *Preconditions:* # SSN is created on AWS # External 'endpoint1' is created on AWS *Steps to reproduce:* 1. Create notebook on External 'endpoint1' *Actual result:* 1. Notebook creation fails *Expected result:* # Notebook is created successfully was: *Preconditions:* # SSN is created on AWS # External 'endpoint1' is created on AWS *Steps to reproduce:* 1. Create notebook on External 'endpoint1' *Actual result:* 1. Notebook creation fails *Expected result:* # Notebook is created successfully The such case I do not check on GCP. > Notebook creation fails on external endpoint in the same cloud where SSN is > deployed > > > Key: DLAB-1501 > URL: https://issues.apache.org/jira/browse/DLAB-1501 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.3 > > Attachments: Notebook creation.png > > > *Preconditions:* > # SSN is created on AWS > # External 'endpoint1' is created on AWS > *Steps to reproduce:* > 1. Create notebook on External 'endpoint1' > *Actual result:* > 1. Notebook creation fails > *Expected result:* > # Notebook is created successfully -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-24) [GCP]: Fix issue with re-using GCP Service accounts and roles
[ https://issues.apache.org/jira/browse/DLAB-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043910#comment-17043910 ] Vira Vitanska commented on DLAB-24: --- Closed: Commit ID 89efe591c71a4cf6f22a1d3d65c0ef77b026afab > [GCP]: Fix issue with re-using GCP Service accounts and roles > - > > Key: DLAB-24 > URL: https://issues.apache.org/jira/browse/DLAB-24 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old > Environment: GCP >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: 2.3_old, Debian, DevOps, GCP, pull-request-available > Fix For: v.2.3 > > Time Spent: 40m > Remaining Estimate: 0h > > After recreating project with the same name, roles and service accounts are > not valid. To fix it, we should add something unique to names of roles and > service accounts. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Comment Edited] (DLAB-1531) Bucket should be tagged according to template
[
https://issues.apache.org/jira/browse/DLAB-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041958#comment-17041958
]
Vira Vitanska edited comment on DLAB-1531 at 2/24/20 10:25 PM:
---
*AWS*
1. From shared_bucket remove project_tag. Shared-bucket has 4 tags, project
bucket has 5 tags. {color:#00875a}It works for local endpoint and remote
one{color}
1. Added endpoint_tag to shared-bucket
2. Name -> sbn-tag for two buckets
*GCP*
1. to shared bucket added three (tag-name, endpoint-tag, project:dlab, sbn-tag)
2. to project bucket added project-tag
{color:#00875a}For local/remote endpoint it works{color}
*AZURE:*
{color:#00875A} It works for local{color}
was (Author: vvitanska):
*AWS*
1. From shared_bucket remove project_tag. Shared-bucket has 4 tags, project
bucket has 5 tags. {color:#00875a}It works for local endpoint and remote
one{color}
1. Added endpoint_tag to shared-bucket
2. Name -> sbn-tag for two buckets
*GCP*
1. to shared bucket added three (tag-name, endpoint-tag, project:dlab, sbn-tag)
2. to project bucket added project-tag
{color:#00875a}For local/remote endpoint it works{color}
*AZURE:*
{color:#00875a}I could not test I am blocked by ticket{color}
https://issues.apache.org/jira/browse/DLAB-1581
> Bucket should be tagged according to template
> -
>
> Key: DLAB-1531
> URL: https://issues.apache.org/jira/browse/DLAB-1531
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Leonid Frolov
>Priority: Minor
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Attachments: AWS project bucket.png, AWS shared endpoint bucket.png,
> Azure Project bucket.png, Azure shared endpoint bucket.png, GCP.png,
> GCP2.png, GCP3.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> (!) *AWS*
> # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *Azure*
> # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *GCP*
> # All buckets should contain endpoint_tag, product, name,
> {color:#de350b}*?sbn?*{color}
> # What does 'vi-aws-10...' tag mean. Do we need it?
> # In addition 'Project bucket' should contain project_tag.
> About GCP consult with [~omartushevskyi]
>
> *AWS*
> 1. From shared_bucket remove project_tag. Shared-bucket has 4 tags, project
> bucket has 5 tags.
> *AZURE*
> 1. Added endpoint_tag to shared-bucket
> 2. Name -> sbn-tag for two buckets
> *GCP*
> 1. to shared bucket added three tags (tag-name, endpoint-tag, project:dlab,
> sbn-tag)
> 2. to project bucket added project-tag
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1581) [Azure]: Project creation fails on stage of shared storage account/container creation
[ https://issues.apache.org/jira/browse/DLAB-1581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17043929#comment-17043929 ] Vira Vitanska commented on DLAB-1581: - Closed: Commit ID 89efe591c71a4cf6f22a1d3d65c0ef77b026afab > [Azure]: Project creation fails on stage of shared storage account/container > creation > - > > Key: DLAB-1581 > URL: https://issues.apache.org/jira/browse/DLAB-1581 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Critical > Labels: AZURE, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: Azure project creation.png > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > 1. SSN is created > *Steps to reproduce:* > 1. Create project > *Actual result:* > 1. Project creation fails > *Expected result:* > **Project creation ** is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1586) [Branch DLAB-1541]: Stoping/starting/terminating statuses of notebook do not convey to DLab UI
[ https://issues.apache.org/jira/browse/DLAB-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1586: Description: *Preconditions:* 1. Notebook is created from branch DLAB-1541 *Steps to reproduce:* 1. Stop notebook *Actual result:* 1. Stopping status is absent on DLab UI *Expected result:* 1. Stopping status is present on DLab UI The same case is with starting/terminating statuses of notebook. In addition during notebook termination DES does cnange its status fron termination -> terminated and remained terminating. was: *Preconditions:* 1. Notebook is created from branch DLAB-1541 *Steps to reproduce:* 1. Stop notebook *Actual result:* 1. Stopping status is absent on DLab UI *Expected result:* 1. Stopping status is present on DLab UI The same case is with starting/terminating statuses of notebook. > [Branch DLAB-1541]: Stoping/starting/terminating statuses of notebook do not > convey to DLab UI > -- > > Key: DLAB-1586 > URL: https://issues.apache.org/jira/browse/DLAB-1586 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > > *Preconditions:* > 1. Notebook is created from branch DLAB-1541 > *Steps to reproduce:* > 1. Stop notebook > *Actual result:* > 1. Stopping status is absent on DLab UI > *Expected result:* > 1. Stopping status is present on DLab UI > > The same case is with starting/terminating statuses of notebook. > > In addition during notebook termination DES does cnange its status fron > termination -> terminated and remained terminating. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1586) [Branch DLAB-1541]: Stoping/starting/terminating statuses of notebook do not convey to DLab UI
[ https://issues.apache.org/jira/browse/DLAB-1586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1586: Attachment: DES.png > [Branch DLAB-1541]: Stoping/starting/terminating statuses of notebook do not > convey to DLab UI > -- > > Key: DLAB-1586 > URL: https://issues.apache.org/jira/browse/DLAB-1586 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: DES.png > > > *Preconditions:* > 1. Notebook is created from branch DLAB-1541 > *Steps to reproduce:* > 1. Stop notebook > *Actual result:* > 1. Stopping status is absent on DLab UI > *Expected result:* > 1. Stopping status is present on DLab UI > > The same case is with starting/terminating statuses of notebook. > > In addition during notebook termination DES does cnange its status fron > termination -> terminated and remained terminating. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1588) [Billing report]: Value of instance size is absent for DES
Vira Vitanska created DLAB-1588: --- Summary: [Billing report]: Value of instance size is absent for DES Key: DLAB-1588 URL: https://issues.apache.org/jira/browse/DLAB-1588 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 Attachments: Instance size.png, List of resource.png *Preconditions:* 1. SSN is created from marketplace 2. DES is created 3. Billing is available *Steps to reproduce:* 1. Go to billing report page *Actual result:* 1. Instance size is absent for DES *Expected result:* 1. Instance size is present for DES -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1589) [Billing report]: Value of service is absent
Vira Vitanska created DLAB-1589: --- Summary: [Billing report]: Value of service is absent Key: DLAB-1589 URL: https://issues.apache.org/jira/browse/DLAB-1589 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Attachments: Service.png *Preconditions:* 1. SSN is created in marketplace 2. Billing is available 3. Instances are created *Steps to reproduce:* 1. Go to billing report page *Actual result:* 1. Value of service is absent *Expected result:* 1. Value of service is present -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1590) Admin per project
Vira Vitanska created DLAB-1590: --- Summary: Admin per project Key: DLAB-1590 URL: https://issues.apache.org/jira/browse/DLAB-1590 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 As an admin I want to assigned/unassigned user to a project for which I am an admin so that I can easily manage of adding users to a group. *Acceptance criteria:* # Admin can assigned/unassigned user to group of which he is admin # Admin cannot assigned/unassigned user to group of which he is not admin *NOTE:* 1. Could one group has more than one admin? 2. Could one admin has more than one project? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1590) Admin per project
[ https://issues.apache.org/jira/browse/DLAB-1590?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1590: Issue Type: Task (was: Bug) > Admin per project > - > > Key: DLAB-1590 > URL: https://issues.apache.org/jira/browse/DLAB-1590 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > > As an admin I want to assigned/unassigned user to a project for which I am an > admin so that I can easily manage of adding users to a group. > *Acceptance criteria:* > # Admin can assigned/unassigned user to group of which he is admin > # Admin cannot assigned/unassigned user to group of which he is not admin > > *NOTE:* 1. Could one group has more than one admin? > 2. Could one admin has more than one project? > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1591) [Front-end]: Admin per project
Vira Vitanska created DLAB-1591: --- Summary: [Front-end]: Admin per project Key: DLAB-1591 URL: https://issues.apache.org/jira/browse/DLAB-1591 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 As an admin I want to assigned/unassigned user to a project for which I am an admin so that I can easily manage of adding users to a group. *Acceptance criteria:* # Admin can assigned/unassigned user to group of which he is admin # Admin cannot assigned/unassigned user to group of which he is not admin *NOTE:* 1. Could one group has more than one admin? 2. Could one admin has more than one project? -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1591) [Front-end]: Admin per project
[ https://issues.apache.org/jira/browse/DLAB-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1591: --- Assignee: Dmytro Gnatyshyn (was: Oleg Fuks) Labels: AWS AZURE Debian Front-end GCP RedHat (was: AWS AZURE Back-end Debian GCP RedHat) > [Front-end]: Admin per project > -- > > Key: DLAB-1591 > URL: https://issues.apache.org/jira/browse/DLAB-1591 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > > As an admin I want to assigned/unassigned user to a project for which I am an > admin so that I can easily manage of adding users to a group. > *Acceptance criteria:* > # Admin can assigned/unassigned user to group of which he is admin > # Admin cannot assigned/unassigned user to group of which he is not admin > > *NOTE:* 1. Could one group has more than one admin? > 2. Could one admin has more than one project? > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-539) Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.3.2) can't be established on Jupyter
[ https://issues.apache.org/jira/browse/DLAB-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-539: --- Description: *Preconditions:* EMR v.5.19 for Jupyter is created and running. *Steps to reproduce:* # Choose EMR kernel PySpark (Python-3.4 / Spark-2.2.1) for running *Actual result:* EMR kernel is NOT started successfully *Expected result:* EMR kernel is started successfully EMR kernel is not started only for EMR v.5.19. And on the other Jupyter for EMR[5.19] it is the same glitch with starting. was: *Preconditions:* EMR v.5.19 for Jupyter is created and running. *Steps to reproduce:* # Choose EMR kernel PySpark (Python-3.4 / Spark-2.2.1) for running *Actual result:* EMR kernel is NOT started successfully *Expected result:* EMR kernel is started successfully EMR kernel is not started onle for EMR v.5.19. And on the other Jupyter for EMR[5.19] it is the same glitch with starting. > Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.3.2) can't be > established on Jupyter > -- > > Key: DLAB-539 > URL: https://issues.apache.org/jira/browse/DLAB-539 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Anna Orlovska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AWS, DevOps, Known_issues(release2.2) > Fix For: v.2.3 > > Attachments: EMR 519 Jupyter 6.0.2.png, EMR519.png, Status.png > > > *Preconditions:* > EMR v.5.19 for Jupyter is created and running. > *Steps to reproduce:* > # Choose EMR kernel PySpark (Python-3.4 / Spark-2.2.1) for running > *Actual result:* > EMR kernel is NOT started successfully > *Expected result:* > EMR kernel is started successfully > > EMR kernel is not started only for EMR v.5.19. > And on the other Jupyter for EMR[5.19] it is the same glitch with starting. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-539) Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.3.2) can't be established on Jupyter
[ https://issues.apache.org/jira/browse/DLAB-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-539: --- Sprint: Apache DLab release 2.3 > Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.3.2) can't be > established on Jupyter > -- > > Key: DLAB-539 > URL: https://issues.apache.org/jira/browse/DLAB-539 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Anna Orlovska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AWS, DevOps, Known_issues(release2.2) > Fix For: v.2.3 > > Attachments: EMR 519 Jupyter 6.0.2.png, EMR519.png, Status.png > > > *Preconditions:* > EMR v.5.19 for Jupyter is created and running. > *Steps to reproduce:* > # Choose EMR kernel PySpark (Python-3.4 / Spark-2.2.1) for running > *Actual result:* > EMR kernel is NOT started successfully > *Expected result:* > EMR kernel is started successfully > > EMR kernel is not started only for EMR v.5.19. > And on the other Jupyter for EMR[5.19] it is the same glitch with starting. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-625) [Convolution notebook in docker image][Azure]: Add provision script for Debian
[ https://issues.apache.org/jira/browse/DLAB-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-625: --- Fix Version/s: v.2.3 Sprint: Apache DLab release 2.3 > [Convolution notebook in docker image][Azure]: Add provision script for Debian > -- > > Key: DLAB-625 > URL: https://issues.apache.org/jira/browse/DLAB-625 > Project: Apache DLab > Issue Type: Task > Components: DLab Old >Reporter: Demyan Mysakovets >Assignee: Demian Mysakovets >Priority: Major > Labels: 2.3_old, AZURE, Debian, DevOps > Fix For: v.2.3 > > > Add provision script for Debian OS family on Azure cloud provider -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1592) [Back-end]: Available lib list is not get due to request entity too large
Vira Vitanska created DLAB-1592: --- Summary: [Back-end]: Available lib list is not get due to request entity too large Key: DLAB-1592 URL: https://issues.apache.org/jira/browse/DLAB-1592 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 Attachments: Available lib list.png *Preconditions:* # SSN is created on GCP # Endpoint is created on AWS # Notebook is created on AWS *Steps to reproduce:* 1. Go to 'List of resource' page 2. Click action menu for notebook 3. Choose manage libraries 4. Choose 'Select resource' in drop down list *Actual result:* 1. Available lib list is not get successful *Expected result:* 1. Available lib list is get successful Available lib list was get successful after 40 minutes of trying. This bug reproduces especially for RStudio -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1592) [Back-end]: Available lib list is not get due to request entity too large
[ https://issues.apache.org/jira/browse/DLAB-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1592: --- Assignee: Oleg Fuks (was: Leonid Frolov) Labels: AWS AZURE Back-end Debian GCP RedHat (was: AWS AZURE Debian DevOps GCP RedHat) > [Back-end]: Available lib list is not get due to request entity too large > - > > Key: DLAB-1592 > URL: https://issues.apache.org/jira/browse/DLAB-1592 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Available lib list.png > > > *Preconditions:* > # SSN is created on GCP > # Endpoint is created on AWS > # Notebook is created on AWS > *Steps to reproduce:* > 1. Go to 'List of resource' page > 2. Click action menu for notebook > 3. Choose manage libraries > 4. Choose 'Select resource' in drop down list > *Actual result:* > 1. Available lib list is not get successful > *Expected result:* > 1. Available lib list is get successful > > Available lib list was get successful after 40 minutes of trying. > This bug reproduces especially for RStudio -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1436) [AWS]: R_templ.r playbook runs with error on RStudio with TensorFlow template
[ https://issues.apache.org/jira/browse/DLAB-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17046325#comment-17046325 ] Vira Vitanska commented on DLAB-1436: - On hold: It will be fixed by updating TensorFlow version. > [AWS]: R_templ.r playbook runs with error on RStudio with TensorFlow template > - > > Key: DLAB-1436 > URL: https://issues.apache.org/jira/browse/DLAB-1436 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AWS, Debian, DevOps > Fix For: v.2.3 > > Attachments: RStudio-Tensor.png > > > *Preconditions:* > 1. Rstudio-TensorFlow is created > *Steps to reproduce:* > 1. Run R_templ.r playbook on Rstudio-TensorFlow > *Actual result:* > 1. Playbook runs with error > *Expected result:* > Playbook runs successfully > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1436) [AWS]: R_templ.r playbook runs with error on RStudio with TensorFlow template
[ https://issues.apache.org/jira/browse/DLAB-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1436: Fix Version/s: (was: v.2.3) > [AWS]: R_templ.r playbook runs with error on RStudio with TensorFlow template > - > > Key: DLAB-1436 > URL: https://issues.apache.org/jira/browse/DLAB-1436 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AWS, Debian, DevOps > Attachments: RStudio-Tensor.png > > > *Preconditions:* > 1. Rstudio-TensorFlow is created > *Steps to reproduce:* > 1. Run R_templ.r playbook on Rstudio-TensorFlow > *Actual result:* > 1. Playbook runs with error > *Expected result:* > Playbook runs successfully > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1436) [AWS]: R_templ.r playbook runs with error on RStudio with TensorFlow template
[ https://issues.apache.org/jira/browse/DLAB-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1436: Sprint: (was: Apache DLab release 2.3) > [AWS]: R_templ.r playbook runs with error on RStudio with TensorFlow template > - > > Key: DLAB-1436 > URL: https://issues.apache.org/jira/browse/DLAB-1436 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AWS, Debian, DevOps > Attachments: RStudio-Tensor.png > > > *Preconditions:* > 1. Rstudio-TensorFlow is created > *Steps to reproduce:* > 1. Run R_templ.r playbook on Rstudio-TensorFlow > *Actual result:* > 1. Playbook runs with error > *Expected result:* > Playbook runs successfully > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1593) Add functionality to create domains for SSN/Edge nodes
Vira Vitanska created DLAB-1593: --- Summary: Add functionality to create domains for SSN/Edge nodes Key: DLAB-1593 URL: https://issues.apache.org/jira/browse/DLAB-1593 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1594) Add support of Let's Encrypt certificates
Vira Vitanska created DLAB-1594: --- Summary: Add support of Let's Encrypt certificates Key: DLAB-1594 URL: https://issues.apache.org/jira/browse/DLAB-1594 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1595) [Azure]: Remote endpoint creation fails
Vira Vitanska created DLAB-1595: --- Summary: [Azure]: Remote endpoint creation fails Key: DLAB-1595 URL: https://issues.apache.org/jira/browse/DLAB-1595 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 Attachments: azure.jpg *Preconditions:* 1. SSN is created on Azure *Steps to reproduce:* 1. Create remote endpoint on Azure via Jenkins job *Actual result:* 1. Remote endpoint creation fails *Expected result:* 1. Remote endpoint is created -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1553) Project termination should delete only project bucket, but not endpoint bucket
[
https://issues.apache.org/jira/browse/DLAB-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1553:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#de350b}project-local-bucket -remains - {color:#4c9aff}verified now
the bucket deletes{color}{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}project-local-bucket -deletes{color}
- {color:#00875a}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875a}project-remote-bucket deletes {color}
- {color:#de350b}endpoint-remote-shared-bucket deletes{color}
- {color:#de350b} fails the edge (on the same remote endpoint) in the other
project{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#de350b}project-remote-bucket remains{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a} project-remote-bucket deletes{color}
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875A}endpoint-local-shared-bucket{color}
- {color:#00875A}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875A}endpoint-local-shared-bucket remains{color}
- {color:#00875A}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875A}endpoint-local-shared-bucket{color}
- {color:#00875A}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875A}endpoint-local-shared-bucket remains{color}
- {color:#DE350B}project-local-bucket -remains{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875A}endpoint-local-shared-bucket{color}
- {color:#00875A}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875A}project-local-bucket -deletes{color}
- {color:#00875A}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875A}project-remote-bucket{color}
- {color:#00875A}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875A}project-remote-bucket deletes {color}
- {color:#DE350B}endpoint-remote-shared-bucket deletes{color}
- {color:#DE350B} fails the edge (on the same remote endpoint) in the other
project{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875A}endpoint-remote-shared-bucket remains{color}
- {color:#DE350B}project-remote-bucket remains{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875A}endpoint-remote-shared-bucket remains{color}
- {color:#00875A} project-remote-bucket deletes{color}
> Project termination should delete only project bucket, but not endpoint bucket
> --
>
> Key: DLAB-1553
> URL: https://issues.apache.org/jira/browse/DLAB-1553
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color:#00875a}project-local-bucket{color}
> 2. If delete edge on local endpoint
> - {color:#00875a}endpoint-local-shared-bucket remains{color}
> - {color:#00875a}project-local-bucket -deletes{color}
> *SSN is created on GCP:*
> 1. If create edge on local endpoint two b
[jira] [Updated] (DLAB-1553) Project termination should delete only project bucket, but not endpoint bucket
[
https://issues.apache.org/jira/browse/DLAB-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1553:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -remains{color} -
{color:#4c9aff}verified now the bucket deletes{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}project-local-bucket -deletes{color}
- {color:#00875a}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875a}project-remote-bucket deletes {color}
- {color:#de350b}endpoint-remote-shared-bucket deletes{color}
- {color:#de350b} fails the edge (on the same remote endpoint) in the other
project{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#de350b}project-remote-bucket remains{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a} project-remote-bucket deletes{color}
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#de350b}project-local-bucket -remains - {color:#4c9aff}verified now
the bucket deletes{color}{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}project-local-bucket -deletes{color}
- {color:#00875a}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875a}project-remote-bucket deletes {color}
- {color:#de350b}endpoint-remote-shared-bucket deletes{color}
- {color:#de350b} fails the edge (on the same remote endpoint) in the other
project{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#de350b}project-remote-bucket remains{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a} project-remote-bucket deletes{color}
> Project termination should delete only project bucket, but not endpoint bucket
> --
>
> Key: DLAB-1553
> URL: https://issues.apache.org/jira/browse/DLAB-1553
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color:#00875a}project-local-bucket{color}
> 2. If delete edge on local endpoint
> - {color:#00875a}endpoint-local-shared-bucket remains{color}
> - {color:#00875a}project-local-bucket -deletes{c
[jira] [Created] (DLAB-1596) [Azure]: Remote endpoint creation fails if VPC/subnet/resource group is not determined
Vira Vitanska created DLAB-1596: --- Summary: [Azure]: Remote endpoint creation fails if VPC/subnet/resource group is not determined Key: DLAB-1596 URL: https://issues.apache.org/jira/browse/DLAB-1596 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 Attachments: endpoint.jpg *Preconditions:* 1. SSN is created on Azure *Steps to reproduce:* # Create remote endpoint on Azure # VPC/subnet/resource group fields leave empty *Actual result:* 1. Remote endpoint creation fails *Expected result:* 1. Remote endpoint creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1595) [Azure]: Remote endpoint creation fails
[ https://issues.apache.org/jira/browse/DLAB-1595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049094#comment-17049094 ] Vira Vitanska commented on DLAB-1595: - Closed: Commit ID 6975cf02134c8f84b4660b8254b1857a8dd7a0a1 > [Azure]: Remote endpoint creation fails > --- > > Key: DLAB-1595 > URL: https://issues.apache.org/jira/browse/DLAB-1595 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: AZURE, Debian, DevOps, RedHat, pull-request-available > Fix For: v.2.3 > > Attachments: azure.jpg, azure_endpoint_created.PNG > > Time Spent: 20m > Remaining Estimate: 0h > > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create remote endpoint on Azure via Jenkins job > *Actual result:* > 1. Remote endpoint creation fails > *Expected result:* > 1. Remote endpoint is created -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Comment Edited] (DLAB-1531) Bucket should be tagged according to template
[
https://issues.apache.org/jira/browse/DLAB-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041958#comment-17041958
]
Vira Vitanska edited comment on DLAB-1531 at 3/2/20 11:05 AM:
--
*AWS*
1. From shared_bucket remove project_tag. Shared-bucket has 4 tags, project
bucket has 5 tags. {color:#00875a}It works for local endpoint and remote
one{color}
1. Added endpoint_tag to shared-bucket
2. Name -> sbn-tag for two buckets
*GCP*
1. to shared bucket added three (tag-name, endpoint-tag, project:dlab, sbn-tag)
2. to project bucket added project-tag
{color:#00875a}For local/remote endpoint it works{color}
*AZURE:*
{color:#00875a} It works for local and remote endpoints{color}
was (Author: vvitanska):
*AWS*
1. From shared_bucket remove project_tag. Shared-bucket has 4 tags, project
bucket has 5 tags. {color:#00875a}It works for local endpoint and remote
one{color}
1. Added endpoint_tag to shared-bucket
2. Name -> sbn-tag for two buckets
*GCP*
1. to shared bucket added three (tag-name, endpoint-tag, project:dlab, sbn-tag)
2. to project bucket added project-tag
{color:#00875a}For local/remote endpoint it works{color}
*AZURE:*
{color:#00875A} It works for local{color}
> Bucket should be tagged according to template
> -
>
> Key: DLAB-1531
> URL: https://issues.apache.org/jira/browse/DLAB-1531
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Leonid Frolov
>Priority: Minor
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Attachments: AWS project bucket.png, AWS shared endpoint bucket.png,
> Azure Project bucket.png, Azure shared endpoint bucket.png, GCP.png,
> GCP2.png, GCP3.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> (!) *AWS*
> # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *Azure*
> # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *GCP*
> # All buckets should contain endpoint_tag, product, name,
> {color:#de350b}*?sbn?*{color}
> # What does 'vi-aws-10...' tag mean. Do we need it?
> # In addition 'Project bucket' should contain project_tag.
> About GCP consult with [~omartushevskyi]
>
> *AWS*
> 1. From shared_bucket remove project_tag. Shared-bucket has 4 tags, project
> bucket has 5 tags.
> *AZURE*
> 1. Added endpoint_tag to shared-bucket
> 2. Name -> sbn-tag for two buckets
> *GCP*
> 1. to shared bucket added three tags (tag-name, endpoint-tag, project:dlab,
> sbn-tag)
> 2. to project bucket added project-tag
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1531) Bucket should be tagged according to template
[
https://issues.apache.org/jira/browse/DLAB-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049105#comment-17049105
]
Vira Vitanska commented on DLAB-1531:
-
Closed:
Commit ID 6975cf02134c8f84b4660b8254b1857a8dd7a0a1
> Bucket should be tagged according to template
> -
>
> Key: DLAB-1531
> URL: https://issues.apache.org/jira/browse/DLAB-1531
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Leonid Frolov
>Priority: Minor
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Attachments: AWS project bucket.png, AWS shared endpoint bucket.png,
> Azure Project bucket.png, Azure shared endpoint bucket.png, GCP.png,
> GCP2.png, GCP3.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> (!) *AWS*
> # [Remote endpoint]: 'Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *Azure*
> # [Local endpoint]: Shared endpoint bucket' does not have endpoint_tag as
> it has 'Project bucket'
>
> (!) *GCP*
> # All buckets should contain endpoint_tag, product, name,
> {color:#de350b}*?sbn?*{color}
> # What does 'vi-aws-10...' tag mean. Do we need it?
> # In addition 'Project bucket' should contain project_tag.
> About GCP consult with [~omartushevskyi]
>
> *AWS*
> 1. From shared_bucket remove project_tag. Shared-bucket has 4 tags, project
> bucket has 5 tags.
> *AZURE*
> 1. Added endpoint_tag to shared-bucket
> 2. Name -> sbn-tag for two buckets
> *GCP*
> 1. to shared bucket added three tags (tag-name, endpoint-tag, project:dlab,
> sbn-tag)
> 2. to project bucket added project-tag
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1587) Adjust images for demo-regime
[ https://issues.apache.org/jira/browse/DLAB-1587?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049158#comment-17049158 ] Vira Vitanska commented on DLAB-1587: - Closed: Commit ID 6975cf02134c8f84b4660b8254b1857a8dd7a0a1 > Adjust images for demo-regime > - > > Key: DLAB-1587 > URL: https://issues.apache.org/jira/browse/DLAB-1587 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Computational resource.png, Size.mov > > Time Spent: 20m > Remaining Estimate: 0h > > *1.* 'It is only demo preview for Dataproc job tracker UI. For real > environment you can use all available tools on Dataproc -> It is only demo > preview for Hadoop UI. For real environment you can use all available tools > on Hadoop. > *2.* 'It is only demo preview for Apache Spark job tracker UI. For real > environment you can use all available tools on Apache Spark job tracker UI' > -> 'It is only demo preview for Apache Spark Master UI. For real environment > you can use all available tools on Apache Spark Master UI' > *3.* Information about demo preview should not be cut for computational > resources > *4.* The modal window should have fixed size -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1597) [DLAB-1476]: Add progress bar during image load
Vira Vitanska created DLAB-1597: --- Summary: [DLAB-1476]: Add progress bar during image load Key: DLAB-1597 URL: https://issues.apache.org/jira/browse/DLAB-1597 Project: Apache DLab Issue Type: Improvement Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Attachments: progress bar.mp4 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1553) Project termination should delete only project bucket, but not endpoint bucket
[
https://issues.apache.org/jira/browse/DLAB-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1553:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -remains{color} -
{color:#4c9aff}verified now the bucket deletes{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}project-local-bucket -deletes{color}
- {color:#00875a}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875a}project-remote-bucket deletes {color} - verified
- {color:#de350b}endpoint-remote-shared-bucket deletes{color} -
{color:#4c9aff}verified{color}
- {color:#de350b} fails the edge (on the same remote endpoint) in the other
project{color} - {color:#4c9aff}verified{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#de350b}project-remote-bucket remains{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a} project-remote-bucket deletes{color}
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -remains{color} -
{color:#4c9aff}verified now the bucket deletes{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}project-local-bucket -deletes{color}
- {color:#00875a}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875a}project-remote-bucket deletes {color}
- {color:#de350b}endpoint-remote-shared-bucket deletes{color}
- {color:#de350b} fails the edge (on the same remote endpoint) in the other
project{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#de350b}project-remote-bucket remains{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a} project-remote-bucket deletes{color}
> Project termination should delete only project bucket, but not endpoint bucket
> --
>
> Key: DLAB-1553
> URL: https://issues.apache.org/jira/browse/DLAB-1553
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color:#00875a}project-local-bucket{color}
> 2. If delete edge on local endpoint
> - {color:#00875a}endpoint-local-sh
[jira] [Created] (DLAB-1598) Action column should be called 'Actions'
Vira Vitanska created DLAB-1598: --- Summary: Action column should be called 'Actions' Key: DLAB-1598 URL: https://issues.apache.org/jira/browse/DLAB-1598 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Action column should be called 'Actions' for resources_list/projects/environment_management pages -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1599) Adjust billing according to multiple support
Vira Vitanska created DLAB-1599: --- Summary: Adjust billing according to multiple support Key: DLAB-1599 URL: https://issues.apache.org/jira/browse/DLAB-1599 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Attachments: Billing.png -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1553) Project termination should delete only project bucket, but not endpoint bucket
[
https://issues.apache.org/jira/browse/DLAB-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vira Vitanska updated DLAB-1553:
Description:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -remains{color} -
{color:#4c9aff}verified now the bucket deletes{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}project-local-bucket -deletes{color}
- {color:#00875a}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875a}project-remote-bucket deletes {color} - verified
- {color:#de350b}endpoint-remote-shared-bucket deletes{color} -
{color:#4c9aff}verified{color}
- {color:#de350b} fails the edge (on the same remote endpoint) in the other
project{color} - {color:#4c9aff}verified{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#de350b}project-remote-bucket remains{color} -
{color:#4c9aff}verified{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a} project-remote-bucket deletes{color}
was:
*SSN is created on AWS:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -deletes{color}
*SSN is created on GCP:*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}endpoint-local-shared-bucket remains{color}
- {color:#00875a}project-local-bucket -remains{color} -
{color:#4c9aff}verified now the bucket deletes{color}
*SSN is created on AZURE*
1. If create edge on local endpoint two buckets will be created
- {color:#00875a}endpoint-local-shared-bucket{color}
- {color:#00875a}project-local-bucket{color}
2. If delete edge on local endpoint
- {color:#00875a}project-local-bucket -deletes{color}
- {color:#00875a}endpoint-local-shared-bucket remains{color}
*Remote endpoint AWS/Azure/GCP*
1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be created
- {color:#00875a}project-remote-bucket{color}
- {color:#00875a}endpoint-remote-shared-bucket{color}
2. If delete edge on remote endpoint (Azure)
- {color:#00875a}project-remote-bucket deletes {color} - verified
- {color:#de350b}endpoint-remote-shared-bucket deletes{color} -
{color:#4c9aff}verified{color}
- {color:#de350b} fails the edge (on the same remote endpoint) in the other
project{color} - {color:#4c9aff}verified{color}
3. If delete edge on remote endpoint (GCP)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#de350b}project-remote-bucket remains{color}
4. If delete edge on remote endpoint (AWS)
- {color:#00875a}endpoint-remote-shared-bucket remains{color}
- {color:#00875a} project-remote-bucket deletes{color}
> Project termination should delete only project bucket, but not endpoint bucket
> --
>
> Key: DLAB-1553
> URL: https://issues.apache.org/jira/browse/DLAB-1553
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color
[jira] [Commented] (DLAB-1553) Project termination should delete only project bucket, but not endpoint bucket
[
https://issues.apache.org/jira/browse/DLAB-1553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049323#comment-17049323
]
Vira Vitanska commented on DLAB-1553:
-
Closed:
Commit ID 6975cf02134c8f84b4660b8254b1857a8dd7a0a1
> Project termination should delete only project bucket, but not endpoint bucket
> --
>
> Key: DLAB-1553
> URL: https://issues.apache.org/jira/browse/DLAB-1553
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
>Reporter: Vira Vitanska
>Assignee: Mykola Bodnar
>Priority: Major
> Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat,
> pull-request-available
> Fix For: v.2.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> *SSN is created on AWS:*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color:#00875a}project-local-bucket{color}
> 2. If delete edge on local endpoint
> - {color:#00875a}endpoint-local-shared-bucket remains{color}
> - {color:#00875a}project-local-bucket -deletes{color}
> *SSN is created on GCP:*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color:#00875a}project-local-bucket{color}
> 2. If delete edge on local endpoint
> - {color:#00875a}endpoint-local-shared-bucket remains{color}
> - {color:#00875a}project-local-bucket -remains{color} -
> {color:#4c9aff}verified now the bucket deletes{color}
> *SSN is created on AZURE*
> 1. If create edge on local endpoint two buckets will be created
> - {color:#00875a}endpoint-local-shared-bucket{color}
> - {color:#00875a}project-local-bucket{color}
> 2. If delete edge on local endpoint
> - {color:#00875a}project-local-bucket -deletes{color}
> - {color:#00875a}endpoint-local-shared-bucket remains{color}
> *Remote endpoint AWS/Azure/GCP*
> 1. If create edge on remote endpoint AWS/Azure/GCP two buckets will be
> created
> - {color:#00875a}project-remote-bucket{color}
> - {color:#00875a}endpoint-remote-shared-bucket{color}
> 2. If delete edge on remote endpoint (Azure)
> - {color:#00875a}project-remote-bucket deletes {color} - verified
> - {color:#de350b}endpoint-remote-shared-bucket deletes{color} -
> {color:#4c9aff}verified{color}
> - {color:#de350b} fails the edge (on the same remote endpoint) in the other
> project{color} - {color:#4c9aff}verified{color}
> 3. If delete edge on remote endpoint (GCP)
> - {color:#00875a}endpoint-remote-shared-bucket remains{color}
> - {color:#de350b}project-remote-bucket remains{color} -
> {color:#4c9aff}verified{color}
> 4. If delete edge on remote endpoint (AWS)
> - {color:#00875a}endpoint-remote-shared-bucket remains{color}
> - {color:#00875a} project-remote-bucket deletes{color}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org
For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1585) [Branch DLAB-1541]: It is forbidden to create computational resources with the same name for second project
[ https://issues.apache.org/jira/browse/DLAB-1585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049372#comment-17049372 ] Vira Vitanska commented on DLAB-1585: - Closed: Commit ID 6975cf02134c8f84b4660b8254b1857a8dd7a0a1 > [Branch DLAB-1541]: It is forbidden to create computational resources with > the same name for second project > --- > > Key: DLAB-1585 > URL: https://issues.apache.org/jira/browse/DLAB-1585 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: DLab1.png, DLab2.png, DLab3.png, Stop notebook.png > > > *Preconditions:* > # Two projects are created > # Notebook2 with name RS1 are created in two projects > # Cluster with name Cl1 is created in project1 for RS1 > *Steps to reproduce:* > 1. Create cluster with name Cl1 for RS1 in project2 > *Actual result:* > 1. It is forbidden to create a cluster only in project2 (in project1 it is > allowed) > *Expected result:* > 1. It is allowed to create a cluster -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1599) Adjust billing according to multiple support
[ https://issues.apache.org/jira/browse/DLAB-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1599: Description: 1. Add USD to cost > Adjust billing according to multiple support > > > Key: DLAB-1599 > URL: https://issues.apache.org/jira/browse/DLAB-1599 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Billing.png > > > 1. Add USD to cost -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1412) [AWS]: Spark-submit --version runs with error for EMR v.5.19.0
[ https://issues.apache.org/jira/browse/DLAB-1412?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1412: Sprint: (was: Apache DLab release 2.3) > [AWS]: Spark-submit --version runs with error for EMR v.5.19.0 > -- > > Key: DLAB-1412 > URL: https://issues.apache.org/jira/browse/DLAB-1412 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main > Environment: AWS >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Trivial > Labels: AWS, Debian, DevOps > Fix For: v.2.3 > > Attachments: Spark submit version.png, Spark-submit version, > Spark-submit version.png > > > *Preconditions:* > 1. EMR v.5.19.0 is created > *Steps to reproduce:* > # Go to EMR via ssh > # Run a command 'spark-submit --version' > *Actual result:* > 1. Error appears: log4j:ERROR Either File or DatePattern options are not set > for appender [DRFA-stderr]. > log4j:ERROR setFile(null,true) call failed. > java.io.FileNotFoundException: /stdout (Permission denied) > *Expected result:* > 1. There is no any error > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-539) Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.3.2) can't be established on Jupyter
[ https://issues.apache.org/jira/browse/DLAB-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-539: --- Sprint: (was: Apache DLab release 2.3) > Connection to EMR v.5.19 kernel PySpark (Python-3.4 / Spark-2.3.2) can't be > established on Jupyter > -- > > Key: DLAB-539 > URL: https://issues.apache.org/jira/browse/DLAB-539 > Project: Apache DLab > Issue Type: Bug > Components: DLab Old >Reporter: Anna Orlovska >Assignee: Mykola Bodnar >Priority: Minor > Labels: 2.3_old, AWS, DevOps, Known_issues(release2.2) > Fix For: v.2.3 > > Attachments: EMR 519 Jupyter 6.0.2.png, EMR519.png, Status.png > > > *Preconditions:* > EMR v.5.19 for Jupyter is created and running. > *Steps to reproduce:* > # Choose EMR kernel PySpark (Python-3.4 / Spark-2.2.1) for running > *Actual result:* > EMR kernel is NOT started successfully > *Expected result:* > EMR kernel is started successfully > > EMR kernel is not started only for EMR v.5.19. > And on the other Jupyter for EMR[5.19] it is the same glitch with starting. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1565) [DevOps]: Convey billing for remote endpoints
[ https://issues.apache.org/jira/browse/DLAB-1565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1565: --- Assignee: Mykola Bodnar (was: Oleh Martushevskyi) Summary: [DevOps]: Convey billing for remote endpoints (was: [AWS][DevOps]: Convey billing for remote endpoints) > [DevOps]: Convey billing for remote endpoints > - > > Key: DLAB-1565 > URL: https://issues.apache.org/jira/browse/DLAB-1565 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1345) [GCP][DevOps]: Odahu (Legion) management in DLab
[ https://issues.apache.org/jira/browse/DLAB-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1345: Summary: [GCP][DevOps]: Odahu (Legion) management in DLab (was: [DevOps]: Odahu (Legion) management in DLab) > [GCP][DevOps]: Odahu (Legion) management in DLab > > > Key: DLAB-1345 > URL: https://issues.apache.org/jira/browse/DLAB-1345 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Demian Mysakovets >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > Who manages Legion provisioning: > * Admin or DLab user? > 1. Legion cluster will be deployed per project-endpoint > 2. Under Administration page: > 2.1. Add a page: Legion deployment > 2.2. Page should contain grid with following information: > - Project Name > - Endpoint URL > - Legion cluster Name > - Legion cluster status > - Number of Legion cluster nodes > - Actions column: > ## Start/Stop? > ## Terminate? > ## Scale-down > ## Scale-up > 2.3. Create Legion cluster popup: > - Select Project > - Select Endpoint > - Select existing k8s cluster (checkbox, once checked input field shows up > where you can fill in "Legion k8s cluster URL") > - Select number of shapes > - Select instance shape > - Select certificate? +(check with Vitalii Solodinov)+ > ## DLab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible = false) > - NAT gateway > ## Need Legion team to use Edge IP instead (proxy) > - Buckets (visible = false) > ## Bucket for Feedback (use Project bucket) > ### Legion should access bucket name as parameter > ## Bucket for State of Terraform (use Project bucket) > ### Legion should access bucket name as parameter > - Container registry (pass a parameter?) > # Security params (keycloak, oauth and ssh key) > # Repos (docker repo and creds, helm repos) > 3. Under List of Resource page > # Show additional column with Legion icon near every notebook > # When use clicks on it -> popup shows up containing following information: > ## URL for feedback storage > ## URL for Swagger API registry > ## URL for Grafana > ## Etc > # Extend current Actions menu for JupyterLab only with action "Attach Legion" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1599) Adjust billing according to multiple support
[ https://issues.apache.org/jira/browse/DLAB-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1599: Attachment: Azure-undefined.jpg > Adjust billing according to multiple support > > > Key: DLAB-1599 > URL: https://issues.apache.org/jira/browse/DLAB-1599 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Azure-undefined.jpg, Billing.png > > > 1. Add USD to cost -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1599) Adjust billing according to multiple support
[ https://issues.apache.org/jira/browse/DLAB-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1599: Attachment: Azure-undefined2.jpg > Adjust billing according to multiple support > > > Key: DLAB-1599 > URL: https://issues.apache.org/jira/browse/DLAB-1599 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Azure-undefined.jpg, Azure-undefined2.jpg, Billing.png > > > 1. Add USD to cost -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1599) Adjust billing according to multiple support
[ https://issues.apache.org/jira/browse/DLAB-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1599: Description: # Add USD to cost # was:1. Add USD to cost > Adjust billing according to multiple support > > > Key: DLAB-1599 > URL: https://issues.apache.org/jira/browse/DLAB-1599 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Azure-undefined.jpg, Azure-undefined2.jpg, Billing.png > > > # Add USD to cost > # -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1599) Adjust billing according to multiple support
[ https://issues.apache.org/jira/browse/DLAB-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1599: Description: # Add USD to cost # Get rid of 'Cannot read property 'filter' of undefined' in console was: # Add USD to cost # > Adjust billing according to multiple support > > > Key: DLAB-1599 > URL: https://issues.apache.org/jira/browse/DLAB-1599 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Azure-undefined.jpg, Azure-undefined2.jpg, Billing.png > > > # Add USD to cost > # Get rid of 'Cannot read property 'filter' of undefined' in console -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1600) [AWS][DevOps]: Odahu (Legion) management in DLab
Vira Vitanska created DLAB-1600: --- Summary: [AWS][DevOps]: Odahu (Legion) management in DLab Key: DLAB-1600 URL: https://issues.apache.org/jira/browse/DLAB-1600 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Demian Mysakovets Fix For: v.2.3 Who manages Legion provisioning: * Admin or DLab user? 1. Legion cluster will be deployed per project-endpoint 2. Under Administration page: 2.1. Add a page: Legion deployment 2.2. Page should contain grid with following information: - Project Name - Endpoint URL - Legion cluster Name - Legion cluster status - Number of Legion cluster nodes - Actions column: ## Start/Stop? ## Terminate? ## Scale-down ## Scale-up 2.3. Create Legion cluster popup: - Select Project - Select Endpoint - Select existing k8s cluster (checkbox, once checked input field shows up where you can fill in "Legion k8s cluster URL") - Select number of shapes - Select instance shape - Select certificate? +(check with Vitalii Solodinov)+ ## DLab passes this as input parameter for Legion provisioning script - VPC, Subnet will be auto-propagated from Project (visible = false) - NAT gateway ## Need Legion team to use Edge IP instead (proxy) - Buckets (visible = false) ## Bucket for Feedback (use Project bucket) ### Legion should access bucket name as parameter ## Bucket for State of Terraform (use Project bucket) ### Legion should access bucket name as parameter - Container registry (pass a parameter?) # Security params (keycloak, oauth and ssh key) # Repos (docker repo and creds, helm repos) 3. Under List of Resource page # Show additional column with Legion icon near every notebook # When use clicks on it -> popup shows up containing following information: ## URL for feedback storage ## URL for Swagger API registry ## URL for Grafana ## Etc # Extend current Actions menu for JupyterLab only with action "Attach Legion" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1600) [AWS][DevOps]: Odahu (Legion) management in DLab
[ https://issues.apache.org/jira/browse/DLAB-1600?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1600: Labels: AWS Debian DevOps RedHat (was: AWS AZURE Debian DevOps GCP RedHat) > [AWS][DevOps]: Odahu (Legion) management in DLab > > > Key: DLAB-1600 > URL: https://issues.apache.org/jira/browse/DLAB-1600 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Demian Mysakovets >Priority: Major > Labels: AWS, Debian, DevOps, RedHat > Fix For: v.2.3 > > > Who manages Legion provisioning: > * Admin or DLab user? > 1. Legion cluster will be deployed per project-endpoint > 2. Under Administration page: > 2.1. Add a page: Legion deployment > 2.2. Page should contain grid with following information: > - Project Name > - Endpoint URL > - Legion cluster Name > - Legion cluster status > - Number of Legion cluster nodes > - Actions column: > ## Start/Stop? > ## Terminate? > ## Scale-down > ## Scale-up > 2.3. Create Legion cluster popup: > - Select Project > - Select Endpoint > - Select existing k8s cluster (checkbox, once checked input field shows up > where you can fill in "Legion k8s cluster URL") > - Select number of shapes > - Select instance shape > - Select certificate? +(check with Vitalii Solodinov)+ > ## DLab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible = false) > - NAT gateway > ## Need Legion team to use Edge IP instead (proxy) > - Buckets (visible = false) > ## Bucket for Feedback (use Project bucket) > ### Legion should access bucket name as parameter > ## Bucket for State of Terraform (use Project bucket) > ### Legion should access bucket name as parameter > - Container registry (pass a parameter?) > # Security params (keycloak, oauth and ssh key) > # Repos (docker repo and creds, helm repos) > 3. Under List of Resource page > # Show additional column with Legion icon near every notebook > # When use clicks on it -> popup shows up containing following information: > ## URL for feedback storage > ## URL for Swagger API registry > ## URL for Grafana > ## Etc > # Extend current Actions menu for JupyterLab only with action "Attach Legion" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1345) [GCP][DevOps]: Odahu (Legion) management in DLab
[ https://issues.apache.org/jira/browse/DLAB-1345?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1345: Labels: Debian DevOps GCP (was: AWS AZURE Debian DevOps GCP RedHat) > [GCP][DevOps]: Odahu (Legion) management in DLab > > > Key: DLAB-1345 > URL: https://issues.apache.org/jira/browse/DLAB-1345 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Demian Mysakovets >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > > Who manages Legion provisioning: > * Admin or DLab user? > 1. Legion cluster will be deployed per project-endpoint > 2. Under Administration page: > 2.1. Add a page: Legion deployment > 2.2. Page should contain grid with following information: > - Project Name > - Endpoint URL > - Legion cluster Name > - Legion cluster status > - Number of Legion cluster nodes > - Actions column: > ## Start/Stop? > ## Terminate? > ## Scale-down > ## Scale-up > 2.3. Create Legion cluster popup: > - Select Project > - Select Endpoint > - Select existing k8s cluster (checkbox, once checked input field shows up > where you can fill in "Legion k8s cluster URL") > - Select number of shapes > - Select instance shape > - Select certificate? +(check with Vitalii Solodinov)+ > ## DLab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible = false) > - NAT gateway > ## Need Legion team to use Edge IP instead (proxy) > - Buckets (visible = false) > ## Bucket for Feedback (use Project bucket) > ### Legion should access bucket name as parameter > ## Bucket for State of Terraform (use Project bucket) > ### Legion should access bucket name as parameter > - Container registry (pass a parameter?) > # Security params (keycloak, oauth and ssh key) > # Repos (docker repo and creds, helm repos) > 3. Under List of Resource page > # Show additional column with Legion icon near every notebook > # When use clicks on it -> popup shows up containing following information: > ## URL for feedback storage > ## URL for Swagger API registry > ## URL for Grafana > ## Etc > # Extend current Actions menu for JupyterLab only with action "Attach Legion" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1601) [Azure][DevOps]: Odahu (Legion) management in DLab
Vira Vitanska created DLAB-1601: --- Summary: [Azure][DevOps]: Odahu (Legion) management in DLab Key: DLAB-1601 URL: https://issues.apache.org/jira/browse/DLAB-1601 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Demian Mysakovets Fix For: v.2.3 Who manages Legion provisioning: * Admin or DLab user? 1. Legion cluster will be deployed per project-endpoint 2. Under Administration page: 2.1. Add a page: Legion deployment 2.2. Page should contain grid with following information: - Project Name - Endpoint URL - Legion cluster Name - Legion cluster status - Number of Legion cluster nodes - Actions column: ## Start/Stop? ## Terminate? ## Scale-down ## Scale-up 2.3. Create Legion cluster popup: - Select Project - Select Endpoint - Select existing k8s cluster (checkbox, once checked input field shows up where you can fill in "Legion k8s cluster URL") - Select number of shapes - Select instance shape - Select certificate? +(check with Vitalii Solodinov)+ ## DLab passes this as input parameter for Legion provisioning script - VPC, Subnet will be auto-propagated from Project (visible = false) - NAT gateway ## Need Legion team to use Edge IP instead (proxy) - Buckets (visible = false) ## Bucket for Feedback (use Project bucket) ### Legion should access bucket name as parameter ## Bucket for State of Terraform (use Project bucket) ### Legion should access bucket name as parameter - Container registry (pass a parameter?) # Security params (keycloak, oauth and ssh key) # Repos (docker repo and creds, helm repos) 3. Under List of Resource page # Show additional column with Legion icon near every notebook # When use clicks on it -> popup shows up containing following information: ## URL for feedback storage ## URL for Swagger API registry ## URL for Grafana ## Etc # Extend current Actions menu for JupyterLab only with action "Attach Legion" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1601) [Azure][DevOps]: Odahu (Legion) management in DLab
[ https://issues.apache.org/jira/browse/DLAB-1601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1601: Labels: Azure Debian DevOps RedHat (was: Debian DevOps GCP) > [Azure][DevOps]: Odahu (Legion) management in DLab > -- > > Key: DLAB-1601 > URL: https://issues.apache.org/jira/browse/DLAB-1601 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Demian Mysakovets >Priority: Major > Labels: Azure, Debian, DevOps, RedHat > Fix For: v.2.3 > > > Who manages Legion provisioning: > * Admin or DLab user? > 1. Legion cluster will be deployed per project-endpoint > 2. Under Administration page: > 2.1. Add a page: Legion deployment > 2.2. Page should contain grid with following information: > - Project Name > - Endpoint URL > - Legion cluster Name > - Legion cluster status > - Number of Legion cluster nodes > - Actions column: > ## Start/Stop? > ## Terminate? > ## Scale-down > ## Scale-up > 2.3. Create Legion cluster popup: > - Select Project > - Select Endpoint > - Select existing k8s cluster (checkbox, once checked input field shows up > where you can fill in "Legion k8s cluster URL") > - Select number of shapes > - Select instance shape > - Select certificate? +(check with Vitalii Solodinov)+ > ## DLab passes this as input parameter for Legion provisioning script > - VPC, Subnet will be auto-propagated from Project (visible = false) > - NAT gateway > ## Need Legion team to use Edge IP instead (proxy) > - Buckets (visible = false) > ## Bucket for Feedback (use Project bucket) > ### Legion should access bucket name as parameter > ## Bucket for State of Terraform (use Project bucket) > ### Legion should access bucket name as parameter > - Container registry (pass a parameter?) > # Security params (keycloak, oauth and ssh key) > # Repos (docker repo and creds, helm repos) > 3. Under List of Resource page > # Show additional column with Legion icon near every notebook > # When use clicks on it -> popup shows up containing following information: > ## URL for feedback storage > ## URL for Swagger API registry > ## URL for Grafana > ## Etc > # Extend current Actions menu for JupyterLab only with action "Attach Legion" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1602) Fix bug with Step certificates on SSN node
Vira Vitanska created DLAB-1602: --- Summary: Fix bug with Step certificates on SSN node Key: DLAB-1602 URL: https://issues.apache.org/jira/browse/DLAB-1602 Project: Apache DLab Issue Type: Bug Components: DLab Main Environment: Odahu-integration branch Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 Attachments: certificate.jpg After renewing certificate, we restart only provisioning service instead of all java services *Preconditions:* 1. Notebook is in stopped status *Steps to reproduce:* 1. Start notebook in next day *Actual result:* 1. Notebook status is stuck in 'starting' status on DLab UI *Expected result:* 1. Notebook status is in 'running' status on DLab UI -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1603) Add authentication vars for Jupyterlab plugin
Vira Vitanska created DLAB-1603: --- Summary: Add authentication vars for Jupyterlab plugin Key: DLAB-1603 URL: https://issues.apache.org/jira/browse/DLAB-1603 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Demian Mysakovets Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1604) [Back-end]: Cluster name should be unique per project
[ https://issues.apache.org/jira/browse/DLAB-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1604: Summary: [Back-end]: Cluster name should be unique per project (was: [back-end]: Cluster name should be unique per project) > [Back-end]: Cluster name should be unique per project > - > > Key: DLAB-1604 > URL: https://issues.apache.org/jira/browse/DLAB-1604 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > > Work in branch "DLAB-1546" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1604) [back-end]: Cluster name should be unique per project
Vira Vitanska created DLAB-1604: --- Summary: [back-end]: Cluster name should be unique per project Key: DLAB-1604 URL: https://issues.apache.org/jira/browse/DLAB-1604 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 Work in branch "DLAB-1546" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1605) [Front-end]: Cluster name should be unique per project
Vira Vitanska created DLAB-1605: --- Summary: [Front-end]: Cluster name should be unique per project Key: DLAB-1605 URL: https://issues.apache.org/jira/browse/DLAB-1605 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 Work in branch "DLAB-1546" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1605) [Front-end]: Cluster name should be unique per project
[ https://issues.apache.org/jira/browse/DLAB-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1605: --- Assignee: Dmytro Gnatyshyn (was: Oleg Fuks) Labels: AWS AZURE Debian Front-end GCP RedHat (was: AWS AZURE Back-end Debian GCP RedHat) > [Front-end]: Cluster name should be unique per project > -- > > Key: DLAB-1605 > URL: https://issues.apache.org/jira/browse/DLAB-1605 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > > Work in branch "DLAB-1546" -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1089) [RStudio][EMR v.5.19]: Playbook runs with exception on stage GET /environment/
[ https://issues.apache.org/jira/browse/DLAB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1089: --- Assignee: (was: Adams Disturber) > [RStudio][EMR v.5.19]: Playbook runs with exception on stage GET > /environment/ > --- > > Key: DLAB-1089 > URL: https://issues.apache.org/jira/browse/DLAB-1089 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Priority: Minor > Labels: 2.3_old, AWS, Debian, DevOps > Fix For: v.2.3 > > Attachments: RStudio.txt, Rstudio.png > > > *Preconditions:* > 1. EMR519 is in running on RStudio > *Steps to reproduce:* > 1. Run preparation playbook for RStudio > *Actual result:* > 1. Playbook runs with Exception > * GET /environment/ failed: java.util.NoSuchElementException > java.util.NoSuchElementException* > 2. Data is written on S3 bucket > *Expected result:* > 1. Playbook runs without exception > 2. Data is written on S3 bucket -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1074) [RStudio]: Remote kernel list is still available after spark cluster termination
[ https://issues.apache.org/jira/browse/DLAB-1074?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1074: --- Assignee: (was: Adams Disturber) > [RStudio]: Remote kernel list is still available after spark cluster > termination > > > Key: DLAB-1074 > URL: https://issues.apache.org/jira/browse/DLAB-1074 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Priority: Major > Labels: 2.3_old, Debian, DevOps, GCP > Fix For: v.2.3 > > Attachments: Renviron.png, Rprofile.png > > > The bug was found on GCP. Please, please take into consideration if it is > cloud related? > *Preconditions:* > 1. Spark cluster is created on RStudio > *Steps to reproduce:* > 1. Terminate Spark cluster > 2. Go to RStudio UI > 3. Open <.Renviron> file > 4. Open <.Rprofile> file > *Actual result:* > # SPARK_HOME="/opt/vit-3008-pr-project1-de-rs-03-spark1/spark/" is present > in <.Renviron> file > # #SPARK_HOME="/opt/spark/" is commented in <.Renviron> file > # master="spark://172.31.16.44:7077" # Cluster - > "vit-3008-pr-project1-de-rs-03-spark1" is present in <.Rprofile> file > *Expected result:* > 1. SPARK_HOME for deleted Spark cluster is absent in <.Renviron> file > 2. Master for deleted Spark cluster is absent in <.Rprofile> file > > How should it work: > After removing a Spark cluster will be activated the last one, if there is > not any Spark cluster, activate Dataproc, and latest - local. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1089) [RStudio][EMR v.5.19]: Playbook runs with exception on stage GET /environment/
[ https://issues.apache.org/jira/browse/DLAB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1089: Description: *Preconditions:* 1. EMR519 is in running on RStudio *Steps to reproduce:* 1. Run preparation playbook for RStudio *Actual result:* 1. Playbook runs with Exception * GET /environment/ failed: java.util.NoSuchElementException java.util.NoSuchElementException* 2. Data is written on S3 bucket *Expected result:* 1. Playbook runs without exception 2. Data is written on S3 bucket The same situation is on AWS (RedHat) EMR-5.28.0 while running 'Flight data visualization' for Rstudio was: *Preconditions:* 1. EMR519 is in running on RStudio *Steps to reproduce:* 1. Run preparation playbook for RStudio *Actual result:* 1. Playbook runs with Exception * GET /environment/ failed: java.util.NoSuchElementException java.util.NoSuchElementException* 2. Data is written on S3 bucket *Expected result:* 1. Playbook runs without exception 2. Data is written on S3 bucket > [RStudio][EMR v.5.19]: Playbook runs with exception on stage GET > /environment/ > --- > > Key: DLAB-1089 > URL: https://issues.apache.org/jira/browse/DLAB-1089 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Priority: Minor > Labels: 2.3_old, AWS, Debian, DevOps > Fix For: v.2.3 > > Attachments: AWS Redhat EMR528 visualization.jpg, RStudio.txt, > Rstudio.png > > > *Preconditions:* > 1. EMR519 is in running on RStudio > *Steps to reproduce:* > 1. Run preparation playbook for RStudio > *Actual result:* > 1. Playbook runs with Exception > * GET /environment/ failed: java.util.NoSuchElementException > java.util.NoSuchElementException* > 2. Data is written on S3 bucket > *Expected result:* > 1. Playbook runs without exception > 2. Data is written on S3 bucket > > The same situation is on AWS (RedHat) EMR-5.28.0 while running 'Flight data > visualization' for Rstudio -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1089) [RStudio][EMR v.5.19]: Playbook runs with exception on stage GET /environment/
[ https://issues.apache.org/jira/browse/DLAB-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1089: Attachment: AWS Redhat EMR528 visualization.jpg > [RStudio][EMR v.5.19]: Playbook runs with exception on stage GET > /environment/ > --- > > Key: DLAB-1089 > URL: https://issues.apache.org/jira/browse/DLAB-1089 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Priority: Minor > Labels: 2.3_old, AWS, Debian, DevOps > Fix For: v.2.3 > > Attachments: AWS Redhat EMR528 visualization.jpg, RStudio.txt, > Rstudio.png > > > *Preconditions:* > 1. EMR519 is in running on RStudio > *Steps to reproduce:* > 1. Run preparation playbook for RStudio > *Actual result:* > 1. Playbook runs with Exception > * GET /environment/ failed: java.util.NoSuchElementException > java.util.NoSuchElementException* > 2. Data is written on S3 bucket > *Expected result:* > 1. Playbook runs without exception > 2. Data is written on S3 bucket > > The same situation is on AWS (RedHat) EMR-5.28.0 while running 'Flight data > visualization' for Rstudio -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1598) Action column should be called 'Actions'
[ https://issues.apache.org/jira/browse/DLAB-1598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050991#comment-17050991 ] Vira Vitanska commented on DLAB-1598: - Closed: Commit ID 79ca168350915db85b37a84b56f4267891cadd90 > Action column should be called 'Actions' > > > Key: DLAB-1598 > URL: https://issues.apache.org/jira/browse/DLAB-1598 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > > Action column should be called 'Actions' for > resources_list/projects/environment_management pages -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1606) Align header grid for resources_list/projects/environment_management pages
Vira Vitanska created DLAB-1606: --- Summary: Align header grid for resources_list/projects/environment_management pages Key: DLAB-1606 URL: https://issues.apache.org/jira/browse/DLAB-1606 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1607) [GCP]: Enable IP forwarding for Edge node
Vira Vitanska created DLAB-1607: --- Summary: [GCP]: Enable IP forwarding for Edge node Key: DLAB-1607 URL: https://issues.apache.org/jira/browse/DLAB-1607 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 It should be enabled when creating instance using GCP Cloud API -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1608) If custom_tag is not defined the value should be empty
[ https://issues.apache.org/jira/browse/DLAB-1608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1608: Description: It works if create manually notebook. But not works for auto-test. was: It works if create manually notebook. But not work for auto-test. > If custom_tag is not defined the value should be empty > -- > > Key: DLAB-1608 > URL: https://issues.apache.org/jira/browse/DLAB-1608 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Leonid Frolov >Priority: Major > Labels: Debian, DevOps, GCP > Fix For: v.2.3 > > > It works if create manually notebook. > But not works for auto-test. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1608) If custom_tag is not defined the value should be empty
Vira Vitanska created DLAB-1608: --- Summary: If custom_tag is not defined the value should be empty Key: DLAB-1608 URL: https://issues.apache.org/jira/browse/DLAB-1608 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 It works if create manually notebook. But not work for auto-test. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1609) Convey 'Resource Type' value to UI
Vira Vitanska created DLAB-1609: --- Summary: Convey 'Resource Type' value to UI Key: DLAB-1609 URL: https://issues.apache.org/jira/browse/DLAB-1609 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Attachments: Azure project page.png, GCP.png 1. Value of 'Resource Type' is absent for GCP 2. Get rid of ' Cannot read property 'length' of undefined' while visiting project page for Azure -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1610) [Azure][RedHat]: Notebook creation fails
Vira Vitanska created DLAB-1610: --- Summary: [Azure][RedHat]: Notebook creation fails Key: DLAB-1610 URL: https://issues.apache.org/jira/browse/DLAB-1610 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Mykola Bodnar Fix For: v.2.3 Attachments: Jupyter.png, RStudio.png, Zeppelin.png *Preconditions:* 1. SSN is created on Azure (RedHat) *Steps to reproduce:* 1. Create any notebook *Actual result:* 1. Notebook creation fails *Expected result:* 1. Notebook is created successful For Jupyter/Zeppelin the mistake is the same for RStuduio the mistake differs -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1611) [RedHat]: JupyterLab creation fails
Vira Vitanska created DLAB-1611: --- Summary: [RedHat]: JupyterLab creation fails Key: DLAB-1611 URL: https://issues.apache.org/jira/browse/DLAB-1611 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Demian Mysakovets Fix For: v.2.3 Attachments: JupyterLab.png *Preconditions:* 1. SSN is created on AWS/Azure (RedHat) *Steps to reproduce:* 1. Create JupyterLab *Actual result:* 1. JupyterLab creation fails /bin/bash: apt-key: command not found (23) Failed writing body *Expected result:* 1. JupyterLab is created successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Description: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column # Spark cluster volume should NOT be marked as shared resource because it is project resource was: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP upper-lower case.png, Images.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column > # Spark cluster volume should NOT be marked as shared resource because it is > project resource -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Attachment: GCP volume spark cluster.jpg > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP upper-lower case.png, GCP volume spark > cluster.jpg, Images.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column > # Spark cluster volume should NOT be marked as shared resource because it is > project resource -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1612) [GCP]: Notebook creation fails if project name contains upper case
Vira Vitanska created DLAB-1612: --- Summary: [GCP]: Notebook creation fails if project name contains upper case Key: DLAB-1612 URL: https://issues.apache.org/jira/browse/DLAB-1612 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Leonid Frolov Fix For: v.2.3 Attachments: Notebook creation.png *Preconditions:* 1. Project name contains upper case *Steps to reproduce:* 1. Create notebook *Actual result:* 1. Notebook creation fails *Expected result:* 1. Notebook creation is successful -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1613) Investigate what extend of certificate should be used .pkcs12 or .jks
Vira Vitanska created DLAB-1613: --- Summary: Investigate what extend of certificate should be used .pkcs12 or .jks Key: DLAB-1613 URL: https://issues.apache.org/jira/browse/DLAB-1613 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1613) Investigate what extend of certificate should be used .pkcs12 or .jks
[ https://issues.apache.org/jira/browse/DLAB-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1613: Issue Type: Task (was: Bug) > Investigate what extend of certificate should be used .pkcs12 or .jks > - > > Key: DLAB-1613 > URL: https://issues.apache.org/jira/browse/DLAB-1613 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: A > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1613) Investigate what extendence of certificate should be used .pkcs12 or .jks
[ https://issues.apache.org/jira/browse/DLAB-1613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1613: Summary: Investigate what extendence of certificate should be used .pkcs12 or .jks (was: Investigate what extend of certificate should be used .pkcs12 or .jks) > Investigate what extendence of certificate should be used .pkcs12 or .jks > - > > Key: DLAB-1613 > URL: https://issues.apache.org/jira/browse/DLAB-1613 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: A > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1614) Convey Grafana credentials to FE
Vira Vitanska created DLAB-1614: --- Summary: Convey Grafana credentials to FE Key: DLAB-1614 URL: https://issues.apache.org/jira/browse/DLAB-1614 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1606) Align header grid for resources_list/projects/environment_management pages
[ https://issues.apache.org/jira/browse/DLAB-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053271#comment-17053271 ] Vira Vitanska commented on DLAB-1606: - Closed: Commit ID 1e1d4fabe3c57d3245b6e8152071a1c6d8c5efc6 > Align header grid for resources_list/projects/environment_management pages > -- > > Key: DLAB-1606 > URL: https://issues.apache.org/jira/browse/DLAB-1606 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Time Spent: 20m > Remaining Estimate: 0h > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1370) [AWS][Part2]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1370: Description: # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image # 'Shared resource' should be in 'Project' column if it is shared image # Filter does not work by 'Shared resource' in 'Project' column # Filter does not work by 'Service' in 'Service' column was: # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image # 'Shared resource' should be in 'Project' column if it is shared image # Filter does not work by 'Shared resource' in 'Project' column > [AWS][Part2]: Alter billing values according to updates on billing page > --- > > Key: DLAB-1370 > URL: https://issues.apache.org/jira/browse/DLAB-1370 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, AWS, Back-end, Debian, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, Images.png > > > # 'Image' should be used in 'Resource type' column for all images > # User_name should be used in 'User'column if it is custom image > # Project_name should be in 'Project' column if it is custom image > # 'Shared resource' should be in 'Project' column if it is shared image > # Filter does not work by 'Shared resource' in 'Project' column > # Filter does not work by 'Service' in 'Service' column -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1362) [Azure]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1362?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1362: Description: # -'Bucket' should be in 'Resource type' column for all buckets- # -Project_name should be in 'Project' column if it is project_bucket.- # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image. # 'Shared resource' should be in 'Project' column if it is shared image. # Instead of should be its value # There are three storages (sbn-ssn-storage/sbn-pr1-local-storage/sbn-local-shared-storage), but in DLab billing we have only one (sbn-pr1-local-storage) # If project name contains upper case in billing report page appears two different projects (see attachment) # Filter does not work by 'Shared resource' in 'Project' column # Filter does not work by 'Resource Type' in 'Resource Type' column was: # -'Bucket' should be in 'Resource type' column for all buckets- # -Project_name should be in 'Project' column if it is project_bucket.- # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # User_name should be used in 'User'column if it is custom image # Project_name should be in 'Project' column if it is custom image. # 'Shared resource' should be in 'Project' column if it is shared image. # Instead of should be its value # There are three storages (sbn-ssn-storage/sbn-pr1-local-storage/sbn-local-shared-storage), but in DLab billing we have only one (sbn-pr1-local-storage) # If project name contains upper case in billing report page appears two different projects (see attachment) # Filter does not work by 'Shared resource' in 'Project' column > [Azure]: Alter billing values according to updates on billing page > -- > > Key: DLAB-1362 > URL: https://issues.apache.org/jira/browse/DLAB-1362 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, AZURE, Back-end, Debian, RedHat > Fix For: v.2.3 > > Attachments: Azure ssn size1.png, Azure ssn size2.png, Azure storage > account.png, Buckets.png, Images.png, Upper and lower case in Project > name.png, azure ssn size3.png > > > # -'Bucket' should be in 'Resource type' column for all buckets- > # -Project_name should be in 'Project' column if it is project_bucket.- > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # User_name should be used in 'User'column if it is custom image > # Project_name should be in 'Project' column if it is custom image. > # 'Shared resource' should be in 'Project' column if it is shared image. > # Instead of should be its value > # There are three storages > (sbn-ssn-storage/sbn-pr1-local-storage/sbn-local-shared-storage), but in DLab > billing we have only one (sbn-pr1-local-storage) > # If project name contains upper case in billing report page appears two > different projects (see attachment) > # Filter does not work by 'Shared resource' in 'Project' column > # Filter does not work by 'Resource Type' in 'Resource Type' column -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Description: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column # Spark cluster volume should NOT be marked as shared resource because it is project resource and should contain 'Volume' in 'Resource type' column # Size is absent for Dataproc in Instance zie # was: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column # Spark cluster volume should NOT be marked as shared resource because it is project resource > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP upper-lower case.png, GCP volume spark > cluster.jpg, Images.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column > # Spark cluster volume should NOT be marked as shared resource because it is > project resource and should contain 'Volume' in 'Resource type' column > # Size is absent for Dataproc in Instance zie > # -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Attachment: GCP instance size.jpg > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP instance size.jpg, GCP upper-lower > case.png, GCP volume spark cluster.jpg, Images.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column > # Spark cluster volume should NOT be marked as shared resource because it is > project resource and should contain 'Volume' in 'Resource type' column > # Size is absent for Dataproc in Instance zie > # -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Description: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column # Spark cluster volume should NOT be marked as shared resource because it is project resource and should contain 'Volume' in 'Resource type' column # Size is absent for Dataproc in 'Instance size' column # If filter by 'n1-standard-2' empty values should not be shown was: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column # Spark cluster volume should NOT be marked as shared resource because it is project resource and should contain 'Volume' in 'Resource type' column # Size is absent for Dataproc in Instance zie # > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP instance size.jpg, GCP upper-lower > case.png, GCP volume spark cluster.jpg, Images.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column > # Spark cluster volume should NOT be marked as shared resource because it is > project resource and should contain 'Volume' in 'Resource type' column > # Size is absent for Dataproc in 'Instance size' column > # If filter by 'n1-standard-2' empty values should not be shown -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Attachment: USD.png > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP instance size.jpg, GCP upper-lower > case.png, GCP volume spark cluster.jpg, Images.png, USD.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column > # Spark cluster volume should NOT be marked as shared resource because it is > project resource and should contain 'Volume' in 'Resource type' column > # Size is absent for Dataproc in 'Instance size' column > # If filter by 'n1-standard-2' empty values should not be shown -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1361) [GCP]: Alter billing values according to updates on billing page
[ https://issues.apache.org/jira/browse/DLAB-1361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1361: Description: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column # Spark cluster volume should NOT be marked as shared resource because it is project resource and should contain 'Volume' in 'Resource type' column # Size is absent for Dataproc in 'Instance size' column # If filter by 'n1-standard-2' empty values should not be shown # Everywhere should be 'USD' not '$' was: # 'Bucket' should be in 'Resource type' column for all buckets # Project_name should be in 'Project' column if it is project_bucket. # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- # Images are not in billing report page # 'Image' should be used in 'Resource type' column for all images # -User_name should be used in 'User'column if it is custom image- # -Project_name should be in 'Project' column if it is custom image.- # 'Shared resource' should be in 'Project' column if it is shared image. # -If project name contains upper case in billing report page appears two different projects (see attachment)- - This task will be fixed in https://issues.apache.org/jira/browse/DLAB-1535 # Filter does not work by 'Shared resource' in 'Project' column # Spark cluster volume should NOT be marked as shared resource because it is project resource and should contain 'Volume' in 'Resource type' column # Size is absent for Dataproc in 'Instance size' column # If filter by 'n1-standard-2' empty values should not be shown > [GCP]: Alter billing values according to updates on billing page > > > Key: DLAB-1361 > URL: https://issues.apache.org/jira/browse/DLAB-1361 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: 2.3_old, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > Attachments: Buckets.png, GCP instance size.jpg, GCP upper-lower > case.png, GCP volume spark cluster.jpg, Images.png, USD.png > > > # 'Bucket' should be in 'Resource type' column for all buckets > # Project_name should be in 'Project' column if it is project_bucket. > # -'Shared resource' should be in 'Project' column if it is ssn_bucket.- > # Images are not in billing report page > # 'Image' should be used in 'Resource type' column for all images > # -User_name should be used in 'User'column if it is custom image- > # -Project_name should be in 'Project' column if it is custom image.- > # 'Shared resource' should be in 'Project' column if it is shared image. > # -If project name contains upper case in billing report page appears two > different projects (see attachment)- - This task will be fixed in > https://issues.apache.org/jira/browse/DLAB-1535 > # Filter does not work by 'Shared resource' in 'Project' column > # Spark cluster volume should NOT be marked as shared resource because it is > project resource and should contain 'Volume' in 'Resource type' column > # Size is absent for Dataproc in 'Instance size' column > # If filter by 'n1-standard-2' empty values should not be shown > # Everywhere should be 'USD' not '$' -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1589) [Billing report]: Value of service is absent
[ https://issues.apache.org/jira/browse/DLAB-1589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053417#comment-17053417 ] Vira Vitanska commented on DLAB-1589: - Closed: Commit ID 1e1d4fabe3c57d3245b6e8152071a1c6d8c5efc6 > [Billing report]: Value of service is absent > - > > Key: DLAB-1589 > URL: https://issues.apache.org/jira/browse/DLAB-1589 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: Debian, Front-end, GCP > Fix For: v.2.3 > > Attachments: Service.png > > > *Preconditions:* > 1. SSN is created in marketplace > 2. Billing is available > 3. Instances are created > *Steps to reproduce:* > 1. Go to billing report page > *Actual result:* > 1. Value of service is absent > *Expected result:* > 1. Value of service is present -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1609) Convey 'Resource Type' value to UI
[ https://issues.apache.org/jira/browse/DLAB-1609?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053415#comment-17053415 ] Vira Vitanska commented on DLAB-1609: - Closed: Commit ID 1e1d4fabe3c57d3245b6e8152071a1c6d8c5efc6 > Convey 'Resource Type' value to UI > -- > > Key: DLAB-1609 > URL: https://issues.apache.org/jira/browse/DLAB-1609 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AZURE, Debian, Front-end, GCP, RedHat, > pull-request-available > Attachments: Azure project page.png, GCP.png > > Time Spent: 20m > Remaining Estimate: 0h > > 1. Value of 'Resource Type' is absent for GCP > 2. Get rid of ' Cannot read property 'length' of undefined' while visiting > project page for Azure -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1599) Adjust billing according to multiple support
[ https://issues.apache.org/jira/browse/DLAB-1599?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17053418#comment-17053418 ] Vira Vitanska commented on DLAB-1599: - Closed: Commit ID 1e1d4fabe3c57d3245b6e8152071a1c6d8c5efc6 > Adjust billing according to multiple support > > > Key: DLAB-1599 > URL: https://issues.apache.org/jira/browse/DLAB-1599 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > Attachments: Azure-undefined.jpg, Azure-undefined2.jpg, Billing.png > > > # Add USD to cost > # Get rid of 'Cannot read property 'filter' of undefined' in console -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1615) [Azure]: Some billing values are absent
Vira Vitanska created DLAB-1615: --- Summary: [Azure]: Some billing values are absent Key: DLAB-1615 URL: https://issues.apache.org/jira/browse/DLAB-1615 Project: Apache DLab Issue Type: Bug Components: DLab Main Reporter: Vira Vitanska Assignee: Dmytro Gnatyshyn Fix For: v.2.3 Attachments: Billing report.png, USD1.png, USD2.png *Preconditions:* 1. Billing is available on Azure *Steps to reproduce:* 1. Go to billing report page 2. Go to list of resource page 3. Go to detailed billing *Actual result:* # Value of environment name is absent # value of instance size is absent # Value of service is absent # 'USD' is absent on billing report/detailed report/list of resource *Expected result:* # Value of environment name is present # value of instance size is present # Value of service is present # 'USD' is present on billing report/detailed report/list of resource -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1614) [Back-end]: Convey Grafana credentials to FE
[ https://issues.apache.org/jira/browse/DLAB-1614?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1614: Summary: [Back-end]: Convey Grafana credentials to FE (was: Convey Grafana credentials to FE) > [Back-end]: Convey Grafana credentials to FE > > > Key: DLAB-1614 > URL: https://issues.apache.org/jira/browse/DLAB-1614 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Major > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1616) [Front-end]: Convey Grafana credentials to FE
Vira Vitanska created DLAB-1616: --- Summary: [Front-end]: Convey Grafana credentials to FE Key: DLAB-1616 URL: https://issues.apache.org/jira/browse/DLAB-1616 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleg Fuks Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Assigned] (DLAB-1616) [Front-end]: Convey Grafana credentials to FE
[ https://issues.apache.org/jira/browse/DLAB-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska reassigned DLAB-1616: --- Assignee: Dmytro Gnatyshyn (was: Oleg Fuks) Labels: AWS AZURE Debian Front-end GCP RedHat (was: AWS AZURE Back-end Debian GCP RedHat) > [Front-end]: Convey Grafana credentials to FE > - > > Key: DLAB-1616 > URL: https://issues.apache.org/jira/browse/DLAB-1616 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1616) [Front-end]: Convey Grafana credentials
[ https://issues.apache.org/jira/browse/DLAB-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1616: Summary: [Front-end]: Convey Grafana credentials (was: [Front-end]: Convey Grafana credentials to FE) > [Front-end]: Convey Grafana credentials > --- > > Key: DLAB-1616 > URL: https://issues.apache.org/jira/browse/DLAB-1616 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > > # Label and value for user name should be present for Grafana > # Label and value for password should be present for Grafana -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1616) [Front-end]: Convey Grafana credentials to FE
[ https://issues.apache.org/jira/browse/DLAB-1616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1616: Description: # Label and value for user name should be present for Grafana # Label and value for password should be present for Grafana > [Front-end]: Convey Grafana credentials to FE > - > > Key: DLAB-1616 > URL: https://issues.apache.org/jira/browse/DLAB-1616 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat > Fix For: v.2.3 > > > # Label and value for user name should be present for Grafana > # Label and value for password should be present for Grafana -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-1615) [Azure]: Some billing values are absent
[ https://issues.apache.org/jira/browse/DLAB-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1615: Description: *Preconditions:* 1. Billing is available on Azure *Steps to reproduce:* 1. Go to billing report page 2. Go to list of resource page 3. Go to detailed billing *Actual result:* # Value of environment name is absent # value of instance size is absent # Value of service is absent # 'USD' is absent on billing report/detailed report/list of resource *Expected result:* # Value of environment name is present # value of instance size is present # Value of service is present # 'USD' is present on billing report/detailed report/list of resource 2. [Notebook name popup]: If there is too long link label should not be cut was: *Preconditions:* 1. Billing is available on Azure *Steps to reproduce:* 1. Go to billing report page 2. Go to list of resource page 3. Go to detailed billing *Actual result:* # Value of environment name is absent # value of instance size is absent # Value of service is absent # 'USD' is absent on billing report/detailed report/list of resource *Expected result:* # Value of environment name is present # value of instance size is present # Value of service is present # 'USD' is present on billing report/detailed report/list of resource > [Azure]: Some billing values are absent > --- > > Key: DLAB-1615 > URL: https://issues.apache.org/jira/browse/DLAB-1615 > Project: Apache DLab > Issue Type: Bug > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Major > Labels: AZURE, Debian, Front-end, RedHat > Fix For: v.2.3 > > Attachments: Billing report.png, USD1.png, USD2.png > > > *Preconditions:* > 1. Billing is available on Azure > *Steps to reproduce:* > 1. Go to billing report page > 2. Go to list of resource page > 3. Go to detailed billing > *Actual result:* > # Value of environment name is absent > # value of instance size is absent > # Value of service is absent > # 'USD' is absent on billing report/detailed report/list of resource > *Expected result:* > # Value of environment name is present > # value of instance size is present > # Value of service is present > # 'USD' is present on billing report/detailed report/list of resource > > 2. [Notebook name popup]: If there is too long link label should not be cut -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Created] (DLAB-1617) Versions of all python libraries should be in conf file
Vira Vitanska created DLAB-1617: --- Summary: Versions of all python libraries should be in conf file Key: DLAB-1617 URL: https://issues.apache.org/jira/browse/DLAB-1617 Project: Apache DLab Issue Type: Task Components: DLab Main Reporter: Vira Vitanska Assignee: Oleh Martushevskyi Fix For: v.2.3 -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
