[ 
https://issues.apache.org/jira/browse/DLAB-1560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vira Vitanska updated DLAB-1560:
--------------------------------
    Description: 
1. Change bucket names 

2.  Notebook/computational resources names

3. Add the third link for Deep Learning and Jupyter with TensorFlow: 
'TensorBoard'

4. Prevent 'cloud Endpoint API'
----
(i) *NOTE* *1.* On Zeppelin/Superset we cannot configure/reconfigure spark (I 
do not rememver how about Jupyterlab)
 *2.*  GPU notebook has the third url for TensorBoard (deepLearning, 
TensorFlow/Jupyter with TensorFlow, Rstudio with TensorFlow)

 

  was:
1. Change bucket names 

2.  Notebook/computational resources names

3. Add the third link for Deep Learning and Jupyter with TensorFlow: 
'TensorBoard'

4. Prevent 'cloud Endpoint API'

 


> Change bucket names and notebook/computational resources names
> --------------------------------------------------------------
>
>                 Key: DLAB-1560
>                 URL: https://issues.apache.org/jira/browse/DLAB-1560
>             Project: Apache DLab
>          Issue Type: Task
>          Components: DLab Main
>            Reporter: Vira Vitanska
>            Assignee: Oleg Fuks
>            Priority: Major
>              Labels: Back-end, Debian, GCP
>             Fix For: v.2.3
>
>         Attachments: Tensor.png
>
>
> 1. Change bucket names 
> 2.  Notebook/computational resources names
> 3. Add the third link for Deep Learning and Jupyter with TensorFlow: 
> 'TensorBoard'
> 4. Prevent 'cloud Endpoint API'
> ----
> (i) *NOTE* *1.* On Zeppelin/Superset we cannot configure/reconfigure spark (I 
> do not rememver how about Jupyterlab)
>  *2.*  GPU notebook has the third url for TensorBoard (deepLearning, 
> TensorFlow/Jupyter with TensorFlow, Rstudio with TensorFlow)
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to