[GitHub] [incubator-dlab] ppapou commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted
ppapou commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted URL: https://github.com/apache/incubator-dlab/pull/641#discussion_r390458264 ## File path: services/self-service/src/main/java/com/epam/dlab/backendapi/domain/ProjectDTO.java ## @@ -21,7 +21,7 @@ @NotNull private final Set groups; @NotNull - @Pattern(regexp = "^ssh-.*\\n", message = "Wrong key format. Key should be in openSSH format") + @Pattern(regexp = "^ssh-.*\\n", message = "format is incorrect. Please use the openSSH format") Review comment: Please see prev response This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] ppapou commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted
ppapou commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted URL: https://github.com/apache/incubator-dlab/pull/641#discussion_r390457393 ## File path: services/self-service/src/main/java/com/epam/dlab/backendapi/domain/CreateProjectDTO.java ## @@ -15,7 +15,7 @@ private final Set groups; @NotNull final Set endpoints; @NotNull - @Pattern(regexp = "^ssh-.*\\n?", message = "Wrong key format. Key should be in openSSH format") + @Pattern(regexp = "^ssh-.*\\n?", message = "format is incorrect. Please use the openSSH format") Review comment: No, we don't. The original error message: ''' "code": 400, "message": "key format is incorrect. Please use the openSSH format" ''' This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] ofuks commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted
ofuks commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted URL: https://github.com/apache/incubator-dlab/pull/641#discussion_r390447319 ## File path: services/self-service/src/main/java/com/epam/dlab/backendapi/domain/ProjectDTO.java ## @@ -21,7 +21,7 @@ @NotNull private final Set groups; @NotNull - @Pattern(regexp = "^ssh-.*\\n", message = "Wrong key format. Key should be in openSSH format") + @Pattern(regexp = "^ssh-.*\\n", message = "format is incorrect. Please use the openSSH format") Review comment: The same here This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[GitHub] [incubator-dlab] ofuks commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted
ofuks commented on a change in pull request #641: [DLAB-1555] the warning message is adjusted URL: https://github.com/apache/incubator-dlab/pull/641#discussion_r390447184 ## File path: services/self-service/src/main/java/com/epam/dlab/backendapi/domain/CreateProjectDTO.java ## @@ -15,7 +15,7 @@ private final Set groups; @NotNull final Set endpoints; @NotNull - @Pattern(regexp = "^ssh-.*\\n?", message = "Wrong key format. Key should be in openSSH format") + @Pattern(regexp = "^ssh-.*\\n?", message = "format is incorrect. Please use the openSSH format") Review comment: Do we need space before "format"? This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1520) [Back-end]: Remove actions from quota popup
[ https://issues.apache.org/jira/browse/DLAB-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055984#comment-17055984 ] Vira Vitanska commented on DLAB-1520: - Closed: Failed edge node is conveyed for quota popup Commit ID 71c38dcb04d69d17f0724a4659d2507cab638aff > [Back-end]: Remove actions from quota popup > --- > > Key: DLAB-1520 > URL: https://issues.apache.org/jira/browse/DLAB-1520 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat > Fix For: v.2.3 > > > # Change 'Manage environment' -> 'Manage DLab quotas' on popup and button name > # Remove stop/terminate action from popup > # If all edge nodes are in terminated status in the same project do not > convey this project to 'Manage DLab quotas' popup. Ponder about failed edge > node -- 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-1527) Rarely notebook is not created successful from the first attempt
[ https://issues.apache.org/jira/browse/DLAB-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055686#comment-17055686 ] Vira Vitanska edited comment on DLAB-1527 at 3/10/20, 2:09 PM: --- Reopened: 10/03/2020 Azure for Zeppelin/RStudio: apt-get -y install nodejs [dlab-user@172.31.16.7] out: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) [dlab-user@172.31.16.7] out: E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? was (Author: vvitanska): Reopened: 10/03/2020 Azure for Zeppelin: apt-get -y install nodejs [dlab-user@172.31.16.7] out: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) [dlab-user@172.31.16.7] out: E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? > Rarely notebook is not created successful from the first attempt > > > Key: DLAB-1527 > URL: https://issues.apache.org/jira/browse/DLAB-1527 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AZURE, Debian, DevOps, GCP, pull-request-available > Fix For: v.2.3 > > Attachments: Azure Jupyter.png, Azure TensorFlow.png, Azure > zeppelin.png, GCP DeepLearning.png, Reopened Azure.jpg > > Time Spent: 40m > Remaining Estimate: 0h > > This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter > (Azure)/DeepLearning (GCP)/TenzorFlow (Azure) during auto-test. The second > attempt was successful by manually creation. > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create Jupyter > *Actual result:* > Jupyter creation fails: > Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource > temporarily unavailable) > *Expected result:* > Jupyter 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-1510) Augment the project page
[ https://issues.apache.org/jira/browse/DLAB-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055951#comment-17055951 ] Vira Vitanska commented on DLAB-1510: - *Closed:* Commit ID 71c38dcb04d69d17f0724a4659d2507cab638aff > Augment the project page > > > Key: DLAB-1510 > URL: https://issues.apache.org/jira/browse/DLAB-1510 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Time Spent: 20m > Remaining Estimate: 0h > > # Stop edge node action should stop all its resources as well. It should be > the same functionality as it was in 'Manage environment' popup > Do not forget that stopping edge node depends on instance statuses. -- 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
[GitHub] [incubator-dlab] DG1202 merged pull request #642: [DLAB-384]: Grouped roles
DG1202 merged pull request #642: [DLAB-384]: Grouped roles URL: https://github.com/apache/incubator-dlab/pull/642 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Updated] (DLAB-384) [Front-end]: Improvements for manage role
[ https://issues.apache.org/jira/browse/DLAB-384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated DLAB-384: Labels: AWS AZURE Debian Front-end GCP RedHat pull-request-available (was: AWS AZURE Debian Front-end GCP RedHat) > [Front-end]: Improvements for manage role > - > > Key: DLAB-384 > URL: https://issues.apache.org/jira/browse/DLAB-384 > Project: Apache DLab > Issue Type: Improvement > Components: DLab Old >Reporter: Vira Vitanska >Assignee: Dmytro Gnatyshyn >Priority: Minor > Labels: AWS, AZURE, Debian, Front-end, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Example.png > > > Group by shape/template in 'Roles' drop down list -- 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
[GitHub] [incubator-dlab] DG1202 opened a new pull request #642: [DLAB-384]: Grouped roles
DG1202 opened a new pull request #642: [DLAB-384]: Grouped roles URL: https://github.com/apache/incubator-dlab/pull/642 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services - To unsubscribe, e-mail: dev-unsubscr...@dlab.apache.org For additional commands, e-mail: dev-h...@dlab.apache.org
[jira] [Commented] (DLAB-1502) Create script to clear all created resources via DLab on external endpoint
[ https://issues.apache.org/jira/browse/DLAB-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055826#comment-17055826 ] Oleh Martushevskyi commented on DLAB-1502: -- Shared bucket should be created when deploying endpoint. All other resources should be removed after project termination. > Create script to clear all created resources via DLab on external endpoint > --- > > Key: DLAB-1502 > URL: https://issues.apache.org/jira/browse/DLAB-1502 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleh Martushevskyi >Priority: Major > Labels: AWS, AZURE, Debian, DevOps, GCP, RedHat > Fix For: v.2.3 > > > Bucket, images, vpc, subnet are left after endpoint/ssn termination via > Jenkins job, however they should be cleared. -- 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-1524) [Connect endpoint]: Add validation for empty field
[ https://issues.apache.org/jira/browse/DLAB-1524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17053773#comment-17053773 ] Vira Vitanska edited comment on DLAB-1524 at 3/10/20, 9:51 AM: --- *Reopened:* 1. *Endpoint name field - empty, other fields are valid*. Change error message from 'Oops! name Endpoint name field cannot be blank,name Endpoint name field cannot be empty' to 'Oops! Endpoint name field cannot be empty!' 2. *Endpoint url name is empty, other fields are valid*. Change error message from 'Oops! url endpoint field is in improper format!' to 'Oops! Endpoint url field cannot be empty!' 3. *Endpoint name and url are empty other field - valid.* Change error message from 'Oops! name Endpoint name field cannot be blank,name Endpoint name field cannot be empty,url endpoint field is in improper format!' to 'Oops! Endpoint name field cannot be empty! Endpoint url field cannot be empty! 4. *Endpoint name is empty, endpoint url is not valid.* Change error message from 'Oops! name Endpoint name field cannot be empty,name Endpoint name field cannot be blank,url endpoint field is in improper format!' to 'Oops! Endpoint name field cannot be empty! Endpoint url field is in improper format!' 5. Add validation for endpoint account. If endpoint account field is empty, convey error message: 'Oops! Endpoint account field cannot be empty!' was (Author: vvitanska): *Reopened:* 1. *Endpoint name field - empty, other fields are valid*. Change error message from 'Oops! name Endpoint name field cannot be blank,name Endpoint name field cannot be empty' to 'Oops! Endpoint name field cannot be empty' 2. *Endpoint url name is empty, other fields are valid*. Change error message from 'Oops! url endpoint field is in improper format!' to 'Oops! Endpoint url field cannot be empty!' 3. *Endpoint name and url are empty other field - valid.* Change error message from 'Oops! name Endpoint name field cannot be blank,name Endpoint name field cannot be empty,url endpoint field is in improper format!' to 'Oops! Endpoint name field cannot be empty' 4. *Endpoint name is empty, endpoint url is not valid.* Change error message from 'Oops! name Endpoint name field cannot be empty,name Endpoint name field cannot be blank,url endpoint field is in improper format!' to 'Oops! Endpoint name field cannot be empty' It should be check starting from endpoint name. If endpoint name is empty and endpoint url is empty the error message should be for endpoint name. 5. *What about endpoint account*? > [Connect endpoint]: Add validation for empty field > --- > > Key: DLAB-1524 > URL: https://issues.apache.org/jira/browse/DLAB-1524 > Project: Apache DLab > Issue Type: Task > Components: DLab Main >Reporter: Vira Vitanska >Assignee: Oleg Fuks >Priority: Minor > Labels: AWS, AZURE, Back-end, Debian, DevOps, GCP, RedHat, > pull-request-available > Fix For: v.2.3 > > Attachments: Reopened Name empty other fields valid.png, Reopened > account is empty other fields are valid.png, Reopened name and url empty > other field valid.png, Reopened url empty other fields valid.png, reopened > Endpoint Reopened name is empty, endpoint url is not valid.png > > Time Spent: 20m > Remaining Estimate: 0h > > If endpoint name or url are empty and user sens regrets convey error message > * 'Endpoint name field cannot be empty' > * 'Endpoint url field cannot be empty' -- 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-1618) Adjust role page according to requirements
[ https://issues.apache.org/jira/browse/DLAB-1618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1618: Description: # Changes are not confirmed in role if users column is empty # 'Success! Group data successfully updated, but users did't delete from group!' -> 'Success! Group data is updated successfully, but user isn't delete from group!' # 'Success! Group data successfully updated!' -> 'Success! Group data is updated successfully!' # If add a new user and don't reload page and delete this added user the confirmation message is absent # If confirm a user removing and don't reload page and delete the other user of this group in confirmation message should not contain the previous deleted user If there is any changes should be visible hint for confirmation was: # Changes are not confirmed in role if users column is empty # 'Success! Group data successfully updated, but users did't delete from group!' -> 'Success! Group data is updated successfully, but user isn't delete from group!' # 'Success! Group data successfully updated!' -> 'Success! Group data is updated successfully!' # If add a new user and don't reload page and delete this added user the confirmation message is absent # If confirm a user removing and don't reload page and delete the other user of this group in confirmation message should not contain the previous deleted user Distinguish action confirmation for user and role: # If admin clicks icon termination for user appears confirmation dialog. If admin hits 'No' - User is not deleted, if 'Yes' -> ''Success! Group data is updated successfully!'' # If admin adds user(s) clicks icon adds -> ''Success! Group data is updated successfully!" # Admin can add several users separated by commas # If admin checks off/unchecks points for role -> ''Success! Group data is updated successfully!" > Adjust role page according to requirements > -- > > Key: DLAB-1618 > URL: https://issues.apache.org/jira/browse/DLAB-1618 > 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: Changes are not confirmed.jpg, Information message.jpg > > > # Changes are not confirmed in role if users column is empty > # 'Success! Group data successfully updated, but users did't delete from > group!' -> 'Success! Group data is updated successfully, but user isn't > delete from group!' > # 'Success! Group data successfully updated!' -> 'Success! Group data is > updated successfully!' > # If add a new user and don't reload page and delete this added user the > confirmation message is absent > # If confirm a user removing and don't reload page and delete the other user > of this group in confirmation message should not contain the previous deleted > user > > If there is any changes should be visible hint for confirmation -- 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-1527) Rarely notebook is not created successful from the first attempt
[ https://issues.apache.org/jira/browse/DLAB-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vira Vitanska updated DLAB-1527: Attachment: Reopened Azure.jpg > Rarely notebook is not created successful from the first attempt > > > Key: DLAB-1527 > URL: https://issues.apache.org/jira/browse/DLAB-1527 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AZURE, Debian, DevOps, GCP, pull-request-available > Fix For: v.2.3 > > Attachments: Azure Jupyter.png, Azure TensorFlow.png, Azure > zeppelin.png, GCP DeepLearning.png, Reopened Azure.jpg > > Time Spent: 40m > Remaining Estimate: 0h > > This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter > (Azure)/DeepLearning (GCP)/TenzorFlow (Azure) during auto-test. The second > attempt was successful by manually creation. > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create Jupyter > *Actual result:* > Jupyter creation fails: > Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource > temporarily unavailable) > *Expected result:* > Jupyter 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-1527) Rarely notebook is not created successful from the first attempt
[ https://issues.apache.org/jira/browse/DLAB-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055686#comment-17055686 ] Vira Vitanska commented on DLAB-1527: - Reopened: 10/03/2020 Azure for Zeppelin: apt-get -y install nodejs [dlab-user@172.31.16.7] out: E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) [dlab-user@172.31.16.7] out: E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it? > Rarely notebook is not created successful from the first attempt > > > Key: DLAB-1527 > URL: https://issues.apache.org/jira/browse/DLAB-1527 > Project: Apache DLab > Issue Type: Bug >Reporter: Vira Vitanska >Assignee: Mykola Bodnar >Priority: Minor > Labels: AZURE, Debian, DevOps, GCP, pull-request-available > Fix For: v.2.3 > > Attachments: Azure Jupyter.png, Azure TensorFlow.png, Azure > zeppelin.png, GCP DeepLearning.png, Reopened Azure.jpg > > Time Spent: 40m > Remaining Estimate: 0h > > This bug was found on Azure/GCP for notebooks Zeppelin (Azure)/Jupyter > (Azure)/DeepLearning (GCP)/TenzorFlow (Azure) during auto-test. The second > attempt was successful by manually creation. > *Preconditions:* > 1. SSN is created on Azure > *Steps to reproduce:* > 1. Create Jupyter > *Actual result:* > Jupyter creation fails: > Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource > temporarily unavailable) > *Expected result:* > Jupyter 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
