Domino executions (Workspaces, Jobs, Apps, and Launchers) automatically make datasets and their associated snapshots from a project available in a predefined path that follows the conventions described in this topic.
You do not have to use a domino.yaml configuration file to control mounting behavior, as in previous Domino releases.
The following configuration demonstrates how it translates into paths that will be available in executions.
-
Dataset called
clapton(local to the project)-
Snapshot 1 (tagged with
tag1) -
Snapshot 2 (not tagged)
-
-
Dataset called
mingus(local to project)-
Snapshot 1 (tagged with
tag2) -
Snapshot 2 (not tagged)
-
-
Dataset called
ella(shared from another project)-
Snapshot 1 (tagged with
tag3) -
Snapshot 2 (not tagged)
-
-
Dataset called
davis(shared from another project)-
Snapshot 1 (tagged with
tag4) -
Snapshot 2 (not tagged)
-
For a Domino Project, the previous Datasets and Snapshots are available in the following hierarchy:
/domino
|--/datasets
|--/local <== Local datasets and snapshots
|--/clapton <== Read-write dataset for owner and editor, read-only for reader
|--/mingus <== Read-write dataset for owner and editor, read-only for reader
|--/snapshots <== Snapshot folder organized by dataset
|--/clapton <== Read-write for owner and editor, read-only for reader
|--/tag1 <== Mounted under latest tag
|--/1 <== Always mounted under the snapshot number
|--/2
|--/mingus
|--/tag2
|--/1
|--/2
|--/ella <== Read-write shared dataset for owner and editor, Read-only for reader
|--/davis <== Read-write shared dataset for owner and editor, Read-only for reader
|--/snapshots <== Shared datasets snapshots organized by dataset
|--/ella <== Read-write for owner and editor, read-only for reader
|--/tag3 <== Mounted under latest tag
|--/1 <== Always mounted under the snapshot number
|--/2
|--/davis
|--/tag4
|--/1
|--/2
In a Workspace or when launching an execution, go to Settings to find the paths for all mounted datasets and the root for any associated snapshots.
For a Git-based Projects, the datasets and snapshots are available in the following hierarchy:
/mnt
|--/data <== Local datasets and snapshots
|--/clapton <== Read-write dataset for owner and editor, read-only for reader
|--/mingus <== Read-write dataset for owner and editor, read-only for reader
|--/snapshots <== Snapshot folder organized by dataset
|--/clapton <== Read-write for owner and editor, read-only for reader
|--/tag1 <== Mounted under latest tag
|--/1 <== Always mounted under the snapshot number
|--/2
|--/mingus
|--/tag2
|--/1
|--/2
|--/imported
|--/data
|--/ella <== Read-write shared dataset for owner and editor, read-only for reader
|--/davis <== Read-write shared dataset for owner and editor, read-only for reader
|--/snapshots <== Shared dataset snapshots organized by dataset
|--/ella <== Read-write for owner and editor, read-only for reader
|--/tag3 <== Mounted under latest tag
|--/1 <== Always mounted under the snapshot number
|--/2
|--/davis
|--/tag4
|--/1
|--/2In a Workspace or when launching an execution, go to Settings to find the paths for all mounted datasets and the root for any associated snapshots.
