You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/notebooks/configure-manage-azure-notebooks-projects.md
+8-9Lines changed: 8 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,13 +37,13 @@ The **Run** drop-down list on the project dashboard is where you select the comp
37
37
38
38

39
39
40
-
You can bypass these limitations by using a different virtual machine that you've provisioned in an Azure subscription. You must install and run JupyterHub on that virtual machine. The Data Science Virtual Machine images (any operating system) are good choices because they include JupyterHub by default.
40
+
You can bypass these limitations by using a different virtual machine that you've provisioned in an Azure subscription. You must install and run JupyterHub on that virtual machine. The Data Science Virtual Machine for Linux (Ubuntu) image is a good choice because it is supported, it has a compatible JupyterHub by default, and it will be automatically discovered.
41
41
42
42
Once you have a suitably configured Azure virtual machine, select the **Direct Compute** option in the drop-down list, which prompts you for a name (to show in the list), the VM's IP address and port (typically 8000, the default port to which JupyterHub listens), and the VM credentials:
43
43
44
44

45
45
46
-
If the following conditions are true, the drop-down list also shows [Data Science Virtual Machine (DSVM)](/azure/machine-learning/data-science-virtual-machine) instances. (If any of these conditions aren't met, you can still connect to the DSVM using the Direct Compute option and entering the values obtained from the Azure portal.)
46
+
If the following conditions are true, the drop-down list also shows [Data Science Virtual Machine (DSVM)](/azure/machine-learning/data-science-virtual-machine) instances. (If any of these conditions aren't met, you can still connect to the DSVM using the Direct Compute option and enter the values obtained from the Azure portal.)
47
47
48
48
- You're signed into Azure Notebooks with an account that uses Azure Active Directory (AAD), such as a company account.
49
49
- Your account is connected to an Azure subscription.
@@ -53,18 +53,17 @@ If the following conditions are true, the drop-down list also shows [Data Scienc
53
53
54
54
When you select a DSVM instance, Azure Notebooks may prompt you for the specific machine credentials used when you created the VM.
55
55
56
-
To create a new DSVM instance, follow the instructions on [Create an Ubuntu Data Science VM](/azure/machine-learning/data-science-virtual-machine/dsvm-ubuntu-intro). Use the **Data Science Virtual Machine for Linux (Ubuntu)** image if you want the DSVM to appear in the drop-down list in Azure Notebooks. If for other reasons you need to use the Windows or CentOS image, you can use the **Direct Compute** option to connect to the DSVM manually.
56
+
To create a new DSVM instance, follow the instructions on [Create an Ubuntu Data Science VM](/azure/machine-learning/data-science-virtual-machine/dsvm-ubuntu-intro). Use the **Data Science Virtual Machine for Linux (Ubuntu)** image if you want the DSVM to appear in the drop-down list in Azure Notebooks.
57
57
58
-
> [!IMPORTANT]
59
-
> When using Direct Compute or Data Science virtual machines, the notebooks you run on them must be entirely self-contained. At present, Azure Notebooks copies only the *.ipynb* file to the VM but doesn't copy any other files in the project. As a result, notebooks running on other VMs fail to find other project files.
58
+
> When a project is run on a VM the files will be mounted on the root directory of the Jupyter Server replacing the default Azure Notebooks files.
60
59
>
61
-
> You can work around this behavior in two ways:
60
+
> If you would like to get the default files back then you will need to shutdown the compute.
62
61
>
63
-
> 1. Copy project files manually to the VM.
62
+
> 
64
63
>
65
-
> 2. Embed the files within a setup notebook that you run first before the primary notebook. In the setup notebook, create a code cell for each file where the cell contains the file contents. Then at the top of each cell, insert the command `%%writefile <filename>`, where `<filename>` is the name of the file to receive the contents. When you run the notebook, it creates all those files on the VM. For an example, see the [setup.ipynb file in the Microsoft Pet Detector demo](https://github.com/Microsoft/connect-petdetector/blob/master/setup.ipynb) (GitHub).
64
+
> Then the default files will reappear if you go to JupyterHub directly.
66
65
>
67
-
> 
0 commit comments