Digital Distributed Containers
| Digital Distributed Container subscription is required. |
Base image definition
The first section allows to configure the base engine image to use when create a new container.
Base image for containers |
The image to use as the base image for containers. Unless you have pulled the Trisotech Engine image to a local registry, you should use |
Authorization |
The username/password to use for accessing the base image. When using the Trisotech registry, you are not required to provide any additional authorization, your License acts as your authorization. |
A Test button can be used to validate the connectivity to the base image.
| An incorrect base image will prevent building any type of container in the Digital Enterprise Suite. |
| Single Service containers are built asynchronously and will not report image pull errors to the user deploying the service. It will however log an error on the console. |
Token usage
The Digital Distributed Container Token section displays the number of licensed tokens for Digital Distributed Containers (DDC) and the number of tokens currently in use. A token is consumed for each DDC deployment in production. The number of available tokens is established in your Trisotech license.
Deployed Container
This section shows the details of deployed Digital Distributed Containers (DDC). The values presented in the table are based on deployment runtime environment information that are defined when configuring the usage report options in the DDC. If the DDC are not properly configured, the information in the table may be incomplete or inaccurate.
| The table could be empty or missing some containers if the DDC are deployed in an environment with restricted network access preventing the reporting of container status to the Digital Enterprise Suite. |
The information presented in the table is not real-time and is based on the last report received from the DDC. The report is sent hourly. The following information is available.
Column |
Description |
Production |
Checked if the container is deployed in a production environment. |
Deployment |
The name of the deployment composed of the deployment, namespace and cluster name of the DDC. When multiple pods are running with the same deployment, namespace and cluster name, they are considered to be part of the same deployment and can be expanded to obtain the details of each pod. |
Tags |
User provided tags configured in the deployment. |
Services |
The services deployed in the DDC. When multiple services are deployed in the container, the details of each deployed service can be obtained by clicking on the label. |
Source Environment |
The environment from which the DDC was built. |
Executions per hour |
The number of new service started in the DDC in the last report. |
Status |
The status as of the last report by the DDC. If no report has been received in the last hour, the DDC is assumed to be offline. |
Digital Distributed Containers that have been offline for three hours are automatically removed from the table.