As described in Runtime Overview, runtimes are the compute resources used to execute processes and logic within jobs and notebooks defined within the Syntasa platform. The defined runtime templates are available for selection in jobs, notebooks, and the interactive mode of apps.
The Runtime Template page is available from the main menu ( ) and then selecting the Runtime menu that is found under Templates. The list shows those runtime templates that have been defined and the current user has access (see Security Overview).
Reviewing existing runtime templates
The Runtime Template page displays a variety of information, some fields are only available based on the value of a dependent field. The below describes the various fields and explains when each is applicable:
- Name - Name of the runtime template given at the time of creating the entry. This is the name that is seen when selecting a runtime template while creating a job, using an app's interactive mode, or attaching a runtime to a notebook.
- Runtime Type - This is chosen when creating a runtime template and cannot be changed. The available values of runtime type depend on the cloud platform the Syntasa environment is installed.
- Image Type - As noted in Runtime Overview, the image is selected when using "container" runtime types; the field will be blank for other runtime types. Also, as with the Runtime Type field, this is non-editable after the runtime template has been created.
- Image Version - When using a "container" runtime type, depending on the image type selected, there may be one or more available versions.
- Tags - Tags are available to categorize most objects throughout the Syntasa platform, e.g, apps, notebooks, dashboards, connections, etc.
- In Use - Indicates if the runtime template is in use, i.e. utilized in an app job or a notebook. Clicking on the Yes/No takes the user into the Runtime Dependencies section of the selected runtime template.
- Default(s) - One runtime template of each runtime type can be indicated as the default runtime for the development and production environments of apps. A single runtime template can be the default for both development and production or the defaults can be separated, for example, a smaller runtime template can be the default for development while a larger runtime template can be the default for production.
- Terminate on Completion - Applicable to "cluster" runtime types, this indicates whether the toggle for the said option is on or off. If on then the cluster will be shut down upon completion of the job.
- Worker Instance Type - Applicable to "cluster" runtime types, this indicates the type(s) of worker nodes as configured within the runtime template.
- Worker Instance Count - Applicable to "cluster" runtime types, this indicates the value of the said option within the configuration of the runtime template.
- Sharing - As described in Security Overview, this indicates the sharing option that is set for the runtime template.
- Owner - Related to the Sharing setting, this is the owner of the runtime template object. By default, this is the user that created the object, but it can be changed.
- Modified By - Displays the name of the user that last modified the runtime template.
- Modified At - Displays the date and time the runtime template was updated, shown in the format according to the language of the browser.
- Created At - Displays the date and time the runtime template was created, shown in the format according to the language of the browser.