The application template is a set of services and storage volumes. The application template can greatly simplify the core configuration.

• Source of the application template:

  • Create template manually: Create an application template and configure services and storage volumes in it.
  • Save as of the core version: In details of a core, save a version as an application template.

• Use of the application template:

  • Create a core based on the application template: When a single core is created, you can select Create a core based on the application template.
  • Register to activate the core based on the application template: If the application template can be bound during batch registration of device, when the device is activated, it will create a core based on the template bound.
  • Batch deploy a core based on the application template: If an application template is selected in a deployment task, the deployment task will batch deploy the core based on the configuration of the application template.

• Configuration of the application template:

  • Configuration of the application template is basically the same as configuration of the core, and the main differences are:

    • There is no agent module in the application template.
    • The application template does not support versions at present.

• Add the function of storage volume configuration supporting predefined macros:

  • Define the meaning of macro in the environment variable “service”, and use the predefined macro in the configuration file of “storage volume”. In this way, the predefined macro will be automatically replaced with the corresponding environment variable in the container system.
  • The Baidu OpenEdge framework (official modules after version 0.1.6) automatically injects many environment variables starting with BAETYL when starting the container, and they can be read directly through predefined macros. Such as: The BAETYL_HOST_ID can be used as the fingerprint of the device to identify the device or solve configuration conflicts.
  • User’s predefined macros should not start with BAETYL so as to avoid conflicts with predefined macros in the system. If the two have conflicts, the predefined macros in the system will be used.