You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@dlab.apache.org by "Vira Vitanska (Jira)" <ji...@apache.org> on 2020/04/14 06:22:00 UTC
[jira] [Commented] (DLAB-1639) Investigate why notebook
template/computational resource are not always available after provisioning
starting
[ https://issues.apache.org/jira/browse/DLAB-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082897#comment-17082897 ]
Vira Vitanska commented on DLAB-1639:
-------------------------------------
Closed:
Commit ID 8c28e7a9b0b4a308215452df2890502a921d35eb.
> Investigate why notebook template/computational resource are not always available after provisioning starting
> -------------------------------------------------------------------------------------------------------------
>
> Key: DLAB-1639
> URL: https://issues.apache.org/jira/browse/DLAB-1639
> Project: Apache DLab
> Issue Type: Task
> Components: DLab Main
> Reporter: Vira Vitanska
> Assignee: Oleg Fuks
> Priority: Critical
> Labels: AWS, AZURE, Back-end, Debian, GCP, RedHat
> Fix For: v.2.3
>
>
> Edge node is created on remote AWS endpoint. After restarting provisioning not always notebook and computational resources are available. Please, investigate it and fix it.
> Especially on remote GCP/Azure endpoints.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@dlab.apache.org
For additional commands, e-mail: dev-help@dlab.apache.org