There are several important settings attached to every project.
In the navigation pane click open a project overview and click Projects.
Click the project whose settings you want to set.
In the navigation pane, click Settings.
Use the Hardware & Environment tab of the project settings to set a specific hardware tier for your project. Hardware tiers describe the compute hardware to use for project executors. Executors can be virtual instances from a cloud services provider or a machine running in your deployment’s on-premises data center. Your administrator configures the hardware tiers available for your deployment.
When you select a hardware tier, it must provide the proper performance for your workflow. However, you must also consider the cost of the hardware in cloud deployments and the impact of your tenancy on local hardware in on-premises deployments. Domino uses this hardware tier for all runs started in the project.
If the hardware tier is changed, it will be the default for future runs in the project. However, if a run starts that requires different hardware, Domino can override the default.
Workspace and jobs volume size
Volumes represent the storage space dedicated to your workspace or job.
The default volume size for all workspaces and jobs in Domino is 10GiB, configurable by an administrator. When you launch a workspace, you be able to select a volume size automatically recommended by Domino based on your project size and previous usage, if your administrator has enabled this feature.
You can change the size of your volume if you find that your workspace (or Job) will require more storage space.
Compute environments are specifications for containers in which projects run. You can create new environments and access public environments shared in your deployment or organization. Whenever a new executor is launched or provisioned for use with a project, Domino loads the compute environment specified in the Hardware & Environment tab of the project settings:
See how to Customize the Domino Software Environment.
Access and sharing
See Sharing and Collaboration for details about how to grant access to your projects.
Projects can be labeled with configurable stages that track their progress through a data science life cycle. If your Domino administrator has configured project stages, you will see the current stage of your project in brackets under the project name in the project menu.
If you are an owner or contributor on the project, you can click the project name to open the menu and change the project stage:
When you track your project through the stages used by your team, it helps your colleagues understand what kind of work is happening in the project and how they can contribute. If you change the stage of a project, this event is listed in the project’s activity feed.
Projects also have a status, which is indicated by the colored pipe next to the project name.
A project’s status can be:
Indicates an active and progressing project.
Indicates an active project that is blocked.
Indicates a completed project.
By default, new projects are set to a green, active status. To modify a project’s status, click the project name at the top of the project menu to access options to mark a project as blocked or complete. When you do so, you can enter a message to describe the blocker or end result of the project. When you change the status of a project, this event is listed in the project’s activity feed with an attached comment thread, so project collaborators can discuss blockers or project conclusions.
Mark a project blocked
Project owners and contributors can mark a project as blocked. Mark a project as blocked when you need assistance from colleagues or administrators to make progress. Domino administrators and your project collaborators will receive an email notification when you mark a project as blocked. Some common cases where raising a blocker can help are:
You need assistance setting up additional tools in a Domino environment.
You need access to new data sources.
You need hardware capabilities not covered by your current hardware tier.
The same menu used to mark a project as blocked can be used to unblock the project, which returns it to a green, active status.
Mark a project complete
Project owners and contributors can mark a project as complete. You can record final conclusions and products in the project’s activity feed, and the project is filtered out of active project views. On your projects overview, select the Show completed projects checkbox to find projects that have been marked as complete.
The same menu used to mark a project as complete can be used to reopen the project, which returns it to a green, active status. A project marked as complete is still a fully functional Domino project. You can modify its files and start Runs in it, but before doing so you might want to reopen the project to indicate that work is continuing.
The Projects page shows active apps, jobs, and workspaces within each project. It also shows stopped workspaces for each project, as these workspaces contribute to a user’s workspace quota and might have to be cleaned up before new workspaces can be created. Click the execution details shown on the project card/project list entry to go directly to the page for this execution type.
Click Activity in the project menu to open the project’s Activity Feed. This page shows the history of activity in the project, including:
Comments left on Jobs or Workspaces
Comments left on files
Project stage changes
Blockers raised or resolved
Files created, edited, or deleted in the Domino UI
Files modified in Workspace sessions
Models or Apps published
Scheduled Jobs published or edited
You can use the menu to filter comments, Jobs, or Workspaces. If you select two successfully completed Runs in the feed, you can use the comparison button next to the filter menu to compare jobs.
You can to import content from one Domino project into another.
The importing project may have access to the exporting project’s files, environment variables, or both, depending on configuration.
During runs with imported files, each project directory is located at
When a run or workspace is started, these files are pulled in alongside the current project’s files.
Imported directories are read-only.
Set up export
From the project overview page, in the navigation pane, go to Settings > Exports. From this interface you can enable exports for the project’s files and environment variables separately, or export the project files as a Python or R package. If none of these are enabled, other projects cannot import anything from this project.
By default, projects will make their latest revision available for export when configured.
You can also make revisions produced by specific runs available for import by tagging those runs with
From the Runs page of a project, select the checkbox for the Runs that you want to export, then click Tag.
Enter the exact string
release to mark the revision created by the selected runs as available for export.
Set up import
page of the project you want to import into, click the Other Projects tab.
Enter the path to the project you want to import, with the format
The following conditions must be true for you to import a project:
You must have Project Importer, Contributor, or Owner permissions on the project.
The project must be configured for export.
After adding a project that exports files, use the Release menu to select the revision of the project files you want to import.