Skip to main content

Data Drives

Overview​

A Data Drive is a named collection of data sources with their mount points pre-configured. Drives let you attach the same combination of sources to multiple runs without rebuilding the configuration each time. The drive becomes a single mountable resource. Mount it at myDrive, and every contained source appears under its own sub-path beneath myDrive.

The create a Data Drive dialog​

New Data Drive on the create card of the Data and Sensors page opens the Create a Data Drive dialog. The dialog holds:

  • Data Drive Name sets the name of the drive, unique across your account.
  • New Data Source Mount Point () opens the mount picker, which takes one data source you have already connected, including the Signaloid Cloud Storage, and a mount location for it relative to the drive. A drive holds any number of mount points.
  • Create Data Drive saves the drive.

For the walkthrough that creates a drive and mounts it on a run, see How to Bundle Data Sources into a Data Drive.

Figure 1. Creating a Data Drive with two mount points and saving the configuration.

Inspecting and editing a Data Drive​

Each drive appears as a card on the Data and Sensors page. The card shows:

  • The drive name, with a tooltip that surfaces the unique source ID.
  • A chip per source category (S3 buckets, sensor gateways, Signaloid Cloud Storage). A drive with no sources shows a warning chip that reads No Source Mount Points Set.
  • The created and last-updated timestamps.

The card has two actions:

  • Edit Configuration reopens the dialog as Modify Data Drive, with every existing source pre-filled. You can add new mount points, mark existing ones for removal, and rename the drive, then click Save.
  • Disconnect () removes the drive from your account after a confirmation. The underlying data sources are left untouched.
Figure 2. Editing a Data Drive and removing a mount point.
Figure 3. Disconnecting a Data Drive from its card on the Data and Sensors page.

Mounting a Data Drive​

A drive shows up in the same picker as individual data sources, both in the Code Playground's Mount Data Source dialog and on a connected repository's Mount Data Source button. The Compute Engine API also accepts the drive by ID.

Mounting a drive at, say, myDriveMount, exposes each contained source under its own sub-path: myDriveMount/<sourceMountPoint>.

Last updated on