If provided, the annotated Space or Artefact represents a host which is to be installed via Ansible by means of a playbook.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ spaces ∙ ☑ artefacts ∙ ☐ services

If the annotated Space or Artefact represents a host which is to be installed via Ansible by means of a playbook as specified by XMInstallationAnsible/Host,, then this entry defines the host name to be used in inventory and playbook.

If not specified, by default the value of XMInstallationNetwork/HostName is used.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ spaces ∙ ☑ artefacts ∙ ☐ services

Names of host groups this item does belong to, is used in generated inventory to be refered from within playbooks.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ spaces ∙ ☑ artefacts ∙ ☐ services

A playbook expression evaluating to bool which indicates whether the component (volume container) corresponding to this Artefact or Space is to be provisioned.

Used e.g. with database provisioning volumes which are usually required only on initial setup.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ spaces ∙ ☑ artefacts ∙ ☐ services

Optionally denotes the name of an ansible provisioning context, which controls which security assets will be used for deployment. Corresponds to a folder name within a volume that is mounted into the ansible service.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ spaces ∙ ☑ artefacts ∙ ☐ services

Named values that will be passed to ansible as variables available within playbooks. Please note: values are processed as ansible/yaml, so that for string values surrounding double quotes are required.

Applies to

▸ Model level: ☑ logical model ∙ ☐ technical model

▸ Model elements: ☑ packages ∙ ☐ classes ∙ ☐ pattern ends ∙ ☐ attributes ∙ ☐ operations ∙ ☐ association ends ∙ ☐ states