Hostname specification

Mon, 01 Jan 0001 00:00:00 +0000

There are four main ways to set a server’s hostname:

Manual entry: the user enters a hostname when ordering a server. This is the default.
Resource pool: a pool of hostnames associated with the environment.
Hostname template: a template that generates hostnames dynamically, covered here.
Orchestration action: a pre-create resource orchestration action runs code to determine the hostname. See Plugins.

Using hostname templates

The Hostname Template parameter specifies how hostnames are generated for new servers. Instead of a static hostname pool, a hostname template dynamically generates hostnames from order attributes, such as a group code, an environment code, a location code, and a user-provided purpose (for example, “web”).

Annotations specification

Mon, 01 Jan 0001 00:00:00 +0000

Annotations, also called server notes, can be set for new servers in three ways:

Manual entry: the user enters annotations when ordering a server. This is the default.
Parameter template: an admin sets the Annotation parameter to a parameter template that generates the annotation, covered below.
Orchestration action: a pre-create resource orchestration action runs code to determine the annotation.

Annotations are supported on many resource handlers, where they map to the platform’s native notes, description, or tag field. For example, VMware uses the native Notes field, and AWS applies an Annotation tag when the handler is set to add Name and Annotation tags to new servers (enable Add Name & Annotation tags to new servers in the handler’s Edit Settings; the Name and Annotation entries then appear on its Tags tab). Annotations sync back to the server after creation.

Parameter templates on CloudBolt Documentation

Hostname specification

Using hostname templates

Annotations specification