Domino Volumes for NetApp ONTAP (NetApp Volumes) let Domino practitioners share data more easily across projects by storing files on external NetApp-backed storage. They enhance performance, eliminate duplication, and provide snapshot-based recovery. Data Sources
User code that runs in Domino can use Domino Data Sources or third-party drivers to interact with external databases, APIs, and file systems to which the Domino-hosting cluster can connect. Users can read and write from these external systems, and they can import data into Domino from such systems by saving files to their project writing files to an output Dataset. External Data Volumes
External Data Volumes (EDVs) mount remote file systems into executions, so users read and write files on storage that Domino does not own. Domino Datasets
You can configure Domino executions to mount Domino datasets for input and output. Datasets are network volumes mounted in the execution environment. Mounting an input Dataset lets executions start quickly. It also gives them access to large quantities of data because the data is not transferred to the local execution volume until user code performs read operations from the mounted volume. Any data written to an output Dataset is saved by Domino as a new snapshot. Domino Project file storage
Every execution occurs in a Project. Based on the Domino File System, the files for the active revision of the project are automatically loaded into the local execution volume for a Job or Workspace. These files are retrieved from the Domino File Store, and any changes to these files are written back to the Domino File Store as a new revision of the project’s files. The following diagram shows the series of operations that happens when a user starts an execution (Job or Workspace) in Domino, and illustrates when and how various data systems can be used. The numbers on the diagram’s arrows match these steps:
1
A client launches the execution
A client launches a Job or Workspace from the Domino application. The operation is scoped to a specific project, environment, and hardware tier.
2
Domino builds the pod specification
Domino constructs a specification for an execution pod from the user’s input. The pod holds containers for the user environment, the executor utility, and the HTTP(S) interface, all pulled from the Docker registry.
3
Kubernetes schedules the pod
Domino brokers assignment of the execution pod to Kubernetes with the node label and resource requests the user chose. An ephemeral execution volume is attached to the target node and mounted in the pod.
4
The executor utility syncs project files and Datasets
The executor utility pulls project files from the Domino File Store into the execution volume mounted in the user environment. Datasets are attached as a network file system. When the Job or Workspace syncs, Domino writes changes back to these stores.
5
User code reaches external data
User code that runs inside the Workspace or Job can read and write external databases, APIs, and file systems.