Ecosystem VM Sections - VoV Deployer

Teradata VantageCore on Virtualization (VoV) Deployer Getting Started

Product
VoV Deployer
Release Number
Deployer 5.0
Published
March 2026
ft:locale
en-US
ft:lastEdition
2026-03-31
dita:mapPath
ijo1771527092730.ditamap
dita:ditavalPath
ayr1485454803741.ditaval
dita:id
ijo1771527092730

For ecosystem VMs (vp, dsu, cmic, qgm, dm, modelops, jupyterhub), properties are typically defined in their respective group_vars directories, and may also be provided in commonITproperties.json under each VM object. Node-specific properties like hostname and IP address are defined in nodeITproperties.json.

Use the following information for vars and properties:

  • Use the vars key within VM objects (for example, byn, tpa) to override or specify VM-specific Ansible variables, such as CPU, memory, or storage.
  • Use the properties key in JSON schemas to define the structure and required fields for each node or group.
  • For Kubernetes deployments, ensure that affinity/anti-affinity and label selectors are reflected in your manifests and referenced in your documentation as shown above.

For network settings use the following:

  • networks.<network>.interface
  • networks.<network>.vlanId

Legacy flat keys (<network>Interface, <network>VlanId) are still supported for compatibility.

Tip: Refer to example property files in inventory/properties/ for complete configuration examples.