Step #8: Dataset and Workspace Removal
Now that the usage models and behaviors of both datasets and workspaces have been explored, any and all of what we have created can be deleted.
First, take inventory of the datasets you would like to consider deleting - in this case, anything owned by your user is under consideration.
$ ngc dataset list --owned
+--------------------+------------+--------------------+--------------------+------------------+--------+-----------+-----------+--------------+-------+---------+
| Id | Integer Id | Name | Description | ACE | Shared | Size | Status | Created Date | Owned | Pre-pop |
+--------------------+------------+--------------------+--------------------+------------------+--------+-----------+-----------+--------------+-------+---------+
| 8brma-E4RX6xVMmpP7 | 99967 | linux-kernel-from- | | nv-launchpad-bc- | No | 1.02 GB | COMPLETED | 2022-05-03 | Yes | No |
| OfpQ | | workspace | | sjc-ace | | | | 20:45:49 UTC | | |
| r3KPjT13TgCFw3a8Jv | 99885 | s3-dl-from-cli | | nv-launchpad-bc- | No | 260.82 MB | COMPLETED | 2022-05-02 | Yes | No |
| ljow | | | | sjc-ace | | | | 17:29:25 UTC | | |
| D9xMj6VNR- | 99209 | linux-kernel-from- | | nv-launchpad-bc- | No | 1.03 GB | COMPLETED | 2022-04-19 | Yes | No |
| OitmadRHwFig | | web-ui | | sjc-ace | | | | 17:27:47 UTC | | |
| cHCMiESgRVeduwq8vF | 99164 | linux-kernel-from- | | nv-launchpad-bc- | No | 1.03 GB | COMPLETED | 2022-04-18 | Yes | No |
| fIRQ | | cli | | sjc-ace | | | | 21:11:38 UTC | | |
| CzgFjq__SSqAb46hSj | 99150 | linux-nvbug-triage | | nv-launchpad-bc- | No | 1.03 GB | COMPLETED | 2022-04-18 | Yes | No |
| k5Nw | | | | sjc-ace | | | | 14:47:47 UTC | | |
| a5LuVPZPQhO7SUWMIz | 98828 | linux-kernel | My favorite kernel | nv-launchpad-bc- | No | 1.03 GB | COMPLETED | 2022-04-14 | Yes | No |
| cpZw | | | | sjc-ace | | | | 22:32:50 UTC | | |
+--------------------+------------+--------------------+--------------------+------------------+--------+-----------+-----------+--------------+-------+---------+
To delete a single dataset, copy the Integer Id of the dataset, and provide it as an argument to the ngc dataset remove command, which will ask you to interactively confirm your request before continuing.
$ ngc dataset remove 99164
----------------------------------------------------
Dataset Information
Id: 99164
Name: linux-kernel-from-cli
Prepopulated: No
Created By: Joseph Handzik
Email: jhandzik@nvidia.com
ACE: nv-launchpad-bc-sjc-ace
Size: 1.03 GB
Total Files: 75028
Status: UPLOAD_COMPLETE
Description:
Owned: Yes
Shared with:
----------------------------------------------------
Are you sure you would like to remove the dataset(s)? [y/n]y
Dataset: 99164 removed from org: jknmqmbjmdk8.
You can also provide numerical ranges and lists - for the remaining two datasets created through the CLI, provide their two Integer Id values and add the -y argument to bypass the interactive confirmation.
$ ngc dataset remove -y 99967,99885
----------------------------------------------------
Dataset Information
Id: 99967
Name: linux-kernel-from-workspace
Prepopulated: No
Created By: Joseph Handzik
Email: jhandzik@nvidia.com
ACE: nv-launchpad-bc-sjc-ace
Size: 1.02 GB
Total Files: 75029
Status: UPLOAD_COMPLETE
Description:
Owned: Yes
Shared with:
----------------------------------------------------
Dataset: 99967 removed from org: jknmqmbjmdk8.
----------------------------------------------------
Dataset Information
Id: 99885
Name: s3-dl-from-cli
Prepopulated: No
Created By: Joseph Handzik
Email: jhandzik@nvidia.com
ACE: nv-launchpad-bc-sjc-ace
Size: 260.82 MB
Total Files: 495
Status: UPLOAD_COMPLETE
Description:
Owned: Yes
Shared with:
----------------------------------------------------
Dataset: 99885 removed from org: jknmqmbjmdk8.
The dataset list command should provide many fewer results now.
$ ngc dataset list --owned
+--------------+------------+--------------------+-------------+------------------+--------+---------+-----------+--------------+-------+---------+
| Id | Integer Id | Name | Description | ACE | Shared | Size | Status | Created Date | Owned | Pre-pop |
+--------------+------------+--------------------+-------------+------------------+--------+---------+-----------+--------------+-------+---------+
| D9xMj6VNR- | 99209 | linux-kernel-from- | | nv-launchpad-bc- | No | 1.03 GB | COMPLETED | 2022-04-19 | Yes | No |
| OitmadRHwFig | | web-ui | | sjc-ace | | | | 17:27:47 UTC | | |
+--------------+------------+--------------------+-------------+------------------+--------+---------+-----------+--------------+-------+---------+
Cleaning up the workspaces that are no longer needed works similarly - let’s list them again.
$ ngc workspace list --owned
+------------------------+--------------------+-------------+----------------------+------------------+--------+---------------------+-------+------+
| Id | Name | Description | ACE | Creator Username | Shared | Created Date | Owned | Size |
+------------------------+--------------------+-------------+----------------------+------------------+--------+---------------------+-------+------+
| JyrRwRmXQCuptjLaCFumkQ | workspace-from-cli | | nv-launchpad-bc-sjc- | Joseph Handzik | No | 2022-05-02 19:34:40 | Yes | 0 B |
| | | | ace | | | UTC | | |
| a6CxaJmmQgK1OIcXR8-d5A | s3-demo-workspace | | nv-launchpad-bc-sjc- | Joseph Handzik | No | 2022-04-19 19:29:12 | Yes | 0 B |
| | | | ace | | | UTC | | |
+------------------------+--------------------+-------------+----------------------+------------------+--------+---------------------+-------+------+
We only have a single workspace to remove - target it with the Id value as an argument to the ngc workspace remove command.
$ ngc workspace remove -y JyrRwRmXQCuptjLaCFumkQ
Successfully removed workspace with ID or name: 'JyrRwRmXQCuptjLaCFumkQ' from org: 'jknmqmbjmdk8'.
A double-check with ngc workspace list will confirm the removal.
$ ngc workspace list --owned
+------------------------+-------------------+-------------+----------------------+------------------+--------+---------------------+-------+------+
| Id | Name | Description | ACE | Creator Username | Shared | Created Date | Owned | Size |
+------------------------+-------------------+-------------+----------------------+------------------+--------+---------------------+-------+------+
| a6CxaJmmQgK1OIcXR8-d5A | s3-demo-workspace | | nv-launchpad-bc-sjc- | Joseph Handzik | No | 2022-04-19 19:29:12 | Yes | 0 B |
| | | | ace | | | UTC | | |
+------------------------+-------------------+-------------+----------------------+------------------+--------+---------------------+-------+------+
To use the Web UI to remove datasets, navigate to the Datasets page from the Base Command Dashboard.
Click on any of the datasets to inspect them further. Let’s start with the s3-dl-from-workspace dataset that was recently created.
To delete the dataset, click the vertical ellipsis and then click the Delete Dataset button that appears.
A dialog box will appear, asking you to confirm your decision. Click the Delete Dataset button to proceed.
The dataset will be deleted - you may need to refresh the page to see it removed from the table.
Repeat for as many datasets as you would like to delete - below is a screenshot of all datasets created through the web UI having been deleted. Each dataset will need to be navigated into to be deleted - for deleting multiple datasets, the command line provides a faster mechanism, as shown in the previous section.
To delete a workspace, navigate to the Workspaces page from the link below the Base Command sidebar section.
Click on the workspace-from-web-ui table row - from the resulting screen, click the vertical ellipsis (just like we did with the dataset workflow earlier in this section) to expose the Delete Workspace button. Click it to begin the deletion process.
A dialog box will pop up to request confirmation to delete the workspace - click Delete Workspace to proceed.
As with the dataset deletion process previously, you may need to refresh the page to see the workspace row removed from the table on the Workspaces page. The screenshot below confirms that the workspace was deleted.
