AMS configuration¶
The Anbox Management Service (AMS) provides various configuration items to customize its behavior. The following table lists the available configuration items and their meaning.
Name |
Description |
---|---|
|
Fingerprint of the certificate in the AMS trust store that is trusted for communicating with the Stream Agent. |
|
Token used for API authentication with Stream Agent. |
|
URL for Stream Agent’s API endpoint. |
|
Comma-separated list of addons that every application managed by AMS uses. See Enable an addon globally. |
|
If set to |
|
If set to |
|
Default Android ABI that applications should use. See Android ABIs for a list of available ABIs. |
|
Maximum number of published versions allowed for application. If the number of application versions exceeds this configuration, AMS automatically cleans up older versions. |
|
(Deprecated) APT mirror to use within the containers. Use |
|
(Deprecated) The name of the platform that Anbox Cloud uses by default to launch containers. Use |
|
(Deprecated) Comma-separated list of features to enable. Use |
|
(Deprecated) If set to |
|
The address used to serve debugging information. |
|
(read only) The address on which AMS listens. |
|
Maximum number of requests allowed on the HTTPS endpoint. |
|
HTTP proxy for HTTP requests performed by AMS. |
|
HTTPS proxy for HTTPS requests performed by AMS. |
|
Comma-separated list of hosts that bypass the configured proxy. |
|
Trust password used to add remote clients. AMS does not expose the actual password but only whether it is set. |
|
The mode AMS uses to limit CPU access for an instance. Possible values are: |
|
Type of GPU. Possible values are: |
|
If set to |
|
Authentication details for AMS to access the image server. To avoid exposing credentials, a boolean value indicating if the item is set is returned. |
|
Frequency of image updates (for example: 1h, 30m). |
|
URL of the image server. |
|
If set to |
|
APT mirror to be used inside instances. |
|
The platform that Anbox Cloud uses by default to launch instances. |
|
Comma-separated list of features to enable. |
|
The network proxy to be used inside instances. This value must be provided in the format |
|
If set to |
|
URL of the load balancer in front of AMS. This URL is provided to instances started by AMS to allow them to communicate with AMS via the load balancer instead of direct communication with an individual AMS instance. |
|
Maximum size of the queue containing requests to start and stop instances per LXD node. Changing this value requires a restart of AMS. |
|
Number of workers processing instance start and stop requests. Changing this value requires a restart of AMS. |
|
Comma-separated list of tags to filter for when applications are fetched from AAR. If empty, no filter is applied. See Anbox Application Registry. |
|
Fingerprint of the certificate that the AAR uses to TLS-secure its HTTPS endpoint. This is used by AMS for mutual TLS authentication with the registry. See Anbox Application Registry. |
|
Mode in which the AAR client in AMS operates: |
|
Frequency of AAR updates (for example: 1h, 30m). See Anbox Application Registry. |
|
URL of the AAR. See Anbox Application Registry. |
|
Strategy that the internal instance scheduler in AMS uses to distribute instances across available LXD nodes: |
Node-specific configuration¶
In a cluster setup, there are configuration items that can be customized for each node. The following table lists the available configuration items and their meaning.
Name |
Description |
---|---|
|
CPU allocation rate used for over-committing resources. See Over-committing resources. |
|
Number of CPUs dedicated to instances. |
|
Number of GPU encoder slots available on the node. Default values: 0 for nodes without GPU; 32 for nodes with NVIDIA GPU; 5 for nodes with AMD; 10 for nodes with Intel GPU. See GPU slots. |
|
Number of GPU slots to configure on the node. |
|
Number of GPU encoder slots. |
|
Number of GPU slots available on the node. |
|
Update the memory (in GB) for the node. |
|
Memory allocation rate used for over-committing resources. See Over-committing resources. |
|
The public, reachable address of the node. |
|
The network subnet of the machine hosting the node. |
|
DEPRECATED Flag in favour of |
|
When set to |
See Configure cluster nodes for instructions on how to set these configuration items.
Objects managed by AMS¶
AMS manages various objects such as applications, images, instances, nodes and addons.
The object names must adhere to the following criteria:
Minimum character limit: 3
Maximum character limit: 255
Can contain:
Alphabets (a-z, A-Z)
Numbers (0-9)
Allowed special characters:
-
(hyphen),_
(underscore),:
(colon),.
(period).
When you create an instance, the same criteria apply to the following options as well:
boot_activity
platform
boot_package
The object ids are generated by AMS and have a length of 20 characters.