The following example might be used for a lab as it deploys the 3 hybrid nodes with two of the VMs on the same host and the third VM on a second host using the small configuration.

Note	In case you are using resource pools, please note that individual ESXi host targetting is not allowed and vCenter is responsible for assigning the VM to a host in the resource pool. If vCenter is not configured with resource pools, then the exact ESXi host path must be passed.

*******
vCenter Example
********
 
//#********* Crosswork Cluster Data *********#
 
Cw_VM_Image = ""
ClusterIPStack = "IPv4"
ManagementVIP = "17.25.87.94"
ManagementIPNetmask = "255.255.255.192"
ManagementIPGateway = "17.25.87.65"
DataVIP = "192.168.123.94"
DataIPNetmask = "255.255.255.0"
DataIPGateway = "0.0.0.0"
DNS = "17.70.168.183"
DomainName = "somedomain.com"
CWPassword = "AStr0ngPa33!"
VMSize = "Small"
NTP = "ntp.com"
BackupMinPercent = 50
ThinProvisioned = true
ManagerDataFsSize = 450
WorkerDataFsSize = 450

#********* Crosswork VM Data Map *********

CwVMs = {
"0" = {
VMName = "vm1",
ManagementIPAddress = "17.25.87.82",
DataIPAddress = "192.168.123.82",
NodeType = "Hybrid"
},
"1" = {
VMName = "vm2",
ManagementIPAddress = "17.25.87.83",
DataIPAddress = "192.168.123.83",
NodeType = "Hybrid"
},
"2" = {
VMName = "vm3",
ManagementIPAddress = "17.25.87.84",
DataIPAddress = "192.168.123.84",
NodeType = "Hybrid"
}
}


#********* vCenter Resource Data with Cw VM assignment *********

VcenterDC = {
VcenterAddress = "17.25.87.90",
VcenterUser = "administrator@vsphere.local",
VcenterPassword = "vcenterPass",
DCname = "dc-cr",
MgmtNetworkName = "VM Network",
DataNetworkName = "DPortGroup10",
DCfolder = "",
VMs = [{
HostedCwVMs = ["0","1"],
Host = "17.25.87.93",
Datastore = "datastore3",
HSDatastore = "ssddatastore",
},
{
HostedCwVMs = ["2"],
Host = "17.25.87.92",
Datastore = "datastore2"
HSDatastore = "ssddatastore",
}
]
}

The following example might be used for a lab as it deploys the 3 hybrid nodes with two of the VMs on the same host and the third VM on a second host using the small configuration.

//*******
//CSP Example
//********
 
//#********* Crosswork Cluster Data  *********#
 
  ClusterName = "day0-cluster"
  Cw_VM_Image           = ""
  ManagementVIP     = "17.25.87.94"
  ManagementIPNetmask = "255.255.255.192"
  ManagementIPGateway = "17.25.87.65"
  DataVIP           = "192.168.123.94"
  DataIPNetmask       = "255.255.255.0"
  DataIPGateway       = "0.0.0.0"
  DNS                 = "17.70.168.183"
  DomainName            = "somedomain.com"
  CWPassword            = "AStr0ngPa33!"
  VMSize                = "Small"
  NTP                   = "ntp.com"
  ClusterIPStack        = "IPv4"
  BackupMinPercent      = 50
  ThinProvisioned     = false
  ManagerDataFsSize = 450
  WorkerDataFsSize  = 450

  RamDiskSize = 0
 
#********* Crosswork VM Data Map *********
 
CwVMs = {
  "0" = {
    VMName                = "vm1",
    ManagementIPAddress = "17.25.87.82",
    DataIPAddress       = "192.168.123.82",
    NodeType               = "Hybrid"
  },
  "1" = {
    VMName                = "vm2",
    ManagementIPAddress = "17.25.87.83",
    DataIPAddress       = "192.168.123.83",
    NodeType               = "Hybrid"
  },
  "2" = {
    VMName                = "vm3",
    ManagementIPAddress = "17.25.87.84",
    DataIPAddress       = "192.168.123.84",
    NodeType               = "Hybrid"
  }
}
 
 
#********* CSP Resource Data with Cw VM assignment *********
 
CSPCluster = {
  hosts = [{
    name = "host1",
    protocol = "https",
    server = "10.0.0.102",
    username = "admin",
    password = "Spass",
    insecure = true
  },
  {
    name = "host2",
    protocol = "https",
    server = "10.0.0.108",
    username = "admin",
    password = "Spass",
    insecure = true
  }]
  VMs = [{
    HostedCwVMs = ["0","1"],
    Host = "host1",
    MgmtNetworkName = "Eth1-1",
    DataNetworkName = "Eth1-2"
  },
    {
      HostedCwVMs = ["2"],
      Host = "host2",
      MgmtNetworkName = "Eth0-1",
      DataNetworkName = "Eth9-1" 
    }
  ]
}

The cluster installer tool, by default, selects the first VM (VM 0) as the seed node. You can set the seed node explicitly by adding the following section to the manifest template (.tfvars file) indicating the unique key of the seed node.

Note	You are recommended not to modify the default seed node value unless advised to do so by the Cisco Customer Experience team.

cluster_settings = {
#Default Minimum number of nodes in inventory
    min_inventory     = 3
#Default Max number of nodes in inventory
    max_inventory     = 9
#Default Min number of manager nodes
    min_mngr_nodes    = 2
#Default Max number of manager nodes
    max_mngr_nodes    = 3
#Default seed node key name
    default_seed_node = "0"
}