Manage a notebook instance
Notebook instances provide you with a dedicated environment to develop and experiment with your AI models. After creating a notebook instance, follow these steps to seamlessly manage your instances:
Step 1: Accessing Notebook Instances
- Dashboard: From the Greennode AP Platform dashboard, locate the "Notebook Instances" section.
- Instance List: You'll see a list of your existing notebook instances, including their names, creation dates, status (e.g., running, stopped), and configuration.
Step 2: Accessing Running Instances
After creating your notebook instance, you can access it by clicking on the provided link. This link will take you directly to the Jupyter notebook interface where you can begin working on your projects.
- Open JupyterLab: Once an instance is running, click the "Open JupyterLab" button to launch the JupyterLab interface in your web browser.
- Work in JupyterLab: Use Jupyter notebooks to write and execute code, experiment with your models, and analyze data.
Step 3: Starting and Stopping Instances
Start Instance
Once your notebook instance is created, it will automatically start. If a notebook is currently stopped, locate your instance in the table and click on the "Start" button. This will initialize the instance with the settings you've chosen. Follow these steps below:
- Locate the instance you want to start in the instance list.
- Click the "Start" button or toggle switch next to the instance name.
- Wait for the instance status to change to "Running."
Stop Instance
If you need to pause your work or save on resources, you can stop your notebook instance. Simply select the instance you wish to stop and click the "Stop" button. This will halt the instance until you start it again.
- Locate the instance you want to stop in the instance list.
- Click the "Stop" button or toggle switch next to the instance name.
- Wait for the instance status to change to "Stopped."
Important Considerations:
- Billing: Notebook instances incur charges while they are running. Be sure to stop instances when you are not actively using them to avoid unnecessary costs.
- Data Persistence: Data stored on the instance's local storage will not persist when the instance is stopped. Therefore, remember to store your data on other space for backup solution (e.g., s3 bucket) before stopping the instance.
Step 4: Delete Instances
When a notebook instance is no longer needed, you can delete it to free up resources and manage costs. To delete an instance, choose the instance and click the "Delete" button. A confirmation dialog will appear to ensure you do not accidentally delete the wrong instance. Please note that once a notebook instance is deleted, it cannot be recovered.
Related Articles
Install a Notebook Instance
This guide will assist you in creating a notebook instance on the Greennode AI Platform for your data science and machine learning projects, where data scientists and engineers can write, execute, and iterate on code. It usually includes features for ...Connect to a notebook instance
Greennode AI Platform offers three methods to connect to notebook instances: Code Editor: Directly access and edit code within the platform's web-based code editor. TCP Port: Connect to the notebook instance using a specified TCP port. SSH: Connect ...Create a notebook instance with custom container
Custom images allow you to create a notebook environment that is precisely tailored to your specific needs. You can pre-install specific libraries, frameworks, or tools that are not included in the standard application-supported images. This saves ...Create a notebook instance with pre-built container
A pre-built notebook instance is a managed environment where you can easily run Jupyter notebooks with access to Greennode AI resources. These instances are pre-configured with the computational resources you choose and can be used for data analysis, ...Local Storage Limits for Notebook, Model Training, and Online Prediction
To ensure optimal performance and cost-efficiency, our platform provides a certain amount of local storage included with each compute instance you create. However, exceeding this storage limit can impact your workflow and results. This guide will ...
