Open topic with navigation
All default templates allow you to limit on which hosts a given database TE and SM process can be started. Without specifying host tag constraints, any host in the domain will be a candidate to start an SM or TE. Each host (broker) in the domain can be tagged with a set of key/value pairs. When creating a database from a template, you can optionally specify a host tag constraint — in the following example, the enforcer will query the domain to find a host tagged with "Storefront" and create SM process(es) only on such hosts.
The template language provides the following tag constraint functions:
ge:(greater than or equal)
le:(less than or equal)
All constraints other than
nx: have a parameter. The parameter should follow the colon (:) delimiter. For example,
eq: means the host must have the specified key with value
Some examples for host tag constraints:
os_ram_mband the value for the memory, in MB. This constraint would use the
"ge:16384"function, which means
"greater than or equal to 16g".
BACKUPdoes not exist. This would use the
"nx:BACKUP"function (not exists).