What is a Workspace?
NOTE: As of October 22, 2022, DSim Cloud limits the number of workspaces to 1 active workspace per user during Metrics's free trial period. This means that you will only be able to do one simulation at a time. You can still have multiple paused and destroyed workspaces.
We will be removing this limitation once the free trial period is over.
A workspace is a construct providing a flow that is equivalent to local interactive simulation work.
It synchronizes a local directory (“source of truth”) to a remote directory and accepts commands to be executed on this remote directory.
The remote directory is persistently updated with the results of command execution (e.g. waveform DBs, new files, elaborated design, logs, etc. called artifacts) and with sync updates from the local directory.
The focus of workspaces is to support interactive command execution.
The local directory that is used to initialize an interactive workspace becomes the origin directory of the workspace.
This makes it the “source of truth” for the workspace, where every change is synchronized to the remote work directory, and so every command is executed as if it was performed locally.
The origin directory also defines the root of the remote work directory of the workspace. Users should choose their origin directory so it scopes their work effectively, see more at How To: Decide what should be your DSim Cloud workspace origin directory.
The remote directory is a cloud-hosted file system that contains all of the files required by the user. It contains a combination of files synchronized from the user origin directory and a Metrics-provided packages directory.
The remote directory is always found in the remote path:
Remote Work Directory
The synchronized remote version of the origin directory contains the files synced from the origin directory as well as any files created by remote commands (artifacts).
The remote work directory is persistent and stored for the user until the workspace is explicitly destroyed. The contents are only modified by user interaction, whether implicit (by syncing) or explicit (executing commands, or an explicit purge command).
This directory is always found in the remote path:
Remote Packages Directory
Predefined tools and IP libraries are available on the remote directory, these can be accessed when executing commands on the remote compute.
The directory is always found in the remote path:
Users will have full read, write and execute permissions to the
/tmpdirectories on the remote directory only. Users will have read-only access to other areas of the remote directory as Metrics permits. Users will not be permitted to manage OS-level packages or perform any operations that require root access.