Creating a Notebook Session

Create a Data Science notebook session to access a JupyterLab interface that uses a customizable compute, storage, and network configuration.

Before you begin:

To use a runtime configuration, identify the custom environment variables and any Git repository URLs that you want you want to use.

Note

The network configuration of a notebook session can't be changed when the notebook session is reactivated. If a notebook session was configured to use a default network, you can't deactivate the notebook session then select custom networking when you reactivate it.

Networking Setup for Using Oracle Managed Features

To use any of the Oracle managed features inside the Notebook, Notebook Lifecycle Scripts, AI Quick Actions, Environment Explorer and Example Notebooks, the Notebook subnet must have permissions to access OCI Object Storage.

If you select Default Networking for your Notebook, your Notebook subnet has access to Object Storage. If you select Custom Networking, you need to set up Object Storage access with either the Service Gateway or Nat Gateway. You can set up Service Gateway to access all services or region specific Object Storage. For more information, see Creating a Service Gateway and Overview of Service Gateways in the Networking documentation. Or, you can set up the Nat Gateway to allow public internet access. For more information, see Nat Gateway in the Networking documentation.

If you use Internet Gateway, you can't connect to the public internet with your Notebook. This is because the Internet Gateway expects the resources behind it to be a public subnet with public IPs which Data Science Notebooks don't use. Nor is the Notebook going to work with connecting to Oracle managed features.

Setting up Storage Mounts

To use storage mounts, you must have an Object Storage bucket or OCI File Storage Service (FSS) mount target and export path.

To use FSS, you must first create the file system and the mount point. Use the custom networking option and ensure that the mount target and the notebook are configured with the same subnet. Configure security list rules for the subnet with the specific ports and protocols.

Ensure that service limits are allocated to file-system-count and mount-target-count.

You must set up policies to use either Object Storage or File Storage Service (FSS) for storage mounts in the notebook.

Using OCI File Storage

Set up Storage Mounts when using OCI File Storage.

Setting Up Storage Mounts

Navigate to the compartment of your choice.
Create a file system under OCI File Storage service along with an export.
Select an existing mount target or create a new one.
You have a file system, and export, and mount target created.
Set up custom networking.

You can create a new subnet or use an existing one. Ensure the mount target and the notebook are configured with the same subnet.
Configure the security list rules of the subnet used as specified in Configuring VCN Security Rules for File Storage.
Note

Before mounting a file system, you must configure security rules in the VCN Subnet to allow network traffic to and from the mount target. You can set up security rules in subnet security lists, network security groups, or by using a combination of both. For more information, see Configuring VCN Security Rules for File Storage.
- Stateful ingress to TCP ports 111, 2048, 2049, and 2050, and UDP ports 111 and 2048.
- Stateful egress for TCP source ports 111, 2048, 2049, and 2050, and UDP source port 111.

Using OCI Object Storage

Set up Storage Mounts when using OCI Object Storage.

Storage mounts for object storage use resource principals based authorization to communicate between notebook and required bucket.

To use the default network option for a notebook, the managed egress works without the need to configure any extra network rules.

To use the custom network option for a notebook, some more network setup is required.

Setting Up Storage Mounts

In the choice of your VCN, create the service gateway.
For the required private subnet, add Service Gateway to the route table configurations.
Change the egress rules of security list of the required subnet to allow traffic to all services in the regional Oracle network.