AMS configuration¶
The Anbox Management Service (AMS) provides various configuration items to customise its behaviour. The following table lists the available configuration items and their meaning.
Name |
Description |
---|---|
|
Fingerprint of certificate in the AMS trust store which is trusted when communicating with the stream agent |
|
Token to be used for API authentication with stream agent |
|
URL for stream agent API endpoint |
|
Enable addons globally for applications |
|
Automatically publish the latest version for an application |
|
Automatically update the images and applications to the latest versions |
|
Set a default support ABI architecture globally |
|
Set the maximum number of application versions to publish |
|
APT mirror to use for downloading dependencies inside the container |
|
Platform to be forwarded to the container for running audio/video operations |
|
Enable additional android features |
|
Enable/disable security update for containers |
|
Address used to expose debug information on |
|
Proxy variables inside container |
|
Proxy variables inside container |
|
Proxy variables inside container |
|
Trust password used to add remote clients. AMS does not expose the actual password but only the fact that it is set or not. |
|
CPU limiting strategies used for a container |
|
GPU allocation mode |
|
GPU type. Can be |
|
Allow insecure TLS for accessing image registry |
|
Auth token required to access the image registry |
|
Interval used to check for image updates |
|
Image registry URL |
|
Lock latest image version to align with latest AMS version |
|
APT mirror to use for downloading dependencies inside the instance |
|
Platform to be forwarded to the instance for running audio/video operations |
|
Enable additional android features |
|
Enable/disable security update for instance |
|
Set host URL for AMS to loadbalancer’s URL |
|
Queue size for internal AMS workers |
|
Number of internal workers for AMS |
|
Tag filters used for selecting applications when interacting with the registry |
|
Fingerprint used to verify the ceritifcate of the application registry |
|
Mode used to interact with the registry |
|
Interval used for checking for updates to applications |
|
Application registry URL |
|
Container scheduling startegy |
Node-specific configuration¶
In a cluster setup, there are configuration items that can be customised for each node. The following table lists the available configuration items and their meaning.
Name |
Description |
---|---|
|
Update the CPU allocation rate for the node |
|
Update the number of CPUs for the node |
|
Update the number of GPU encoder slots to configure on the node |
|
Update the number of GPU slots to configure on the node |
|
Update the number of GPU encoder slots |
|
Update the number of the GPU slots available on the Node |
|
Update the memory (in GB) for the node |
|
Update the memory allocation rate for the node |
|
Update the public IP Address of the node |
|
Update the subnet info of the node if the subnet of a node is changed |
|
DEPRECATED Flag in favour of |
|
Flag used to remove the node from scheduler and not schedule containers on it |
See How to 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.