{
    "__version": "2.13.0",
    "__comments": [
        "Sample template to upgrade a vCenter Server Appliance 6.0 with an external Platform Services Controller to a vCenter Server Appliance 6.7 with an external Platform Services Controller on a vCenter Server instance.",
         "Starting with vSphere 6.7, VMware announced a simplified vCenter Single Sign-On domain architecture by enabling vCenter Enhanced Linked Mode support for vCenter Server Appliance installations with an embedded Platform Services Controller.",
        "You can use the vCenter Server converge utility to change the deployment topology from an external Platform Services Controller to an embedded Platform Services Controller with support for vCenter Enhanced Linked Mode.",
        "As of this release, the external Platform Services Controller architecture is deprecated and will not be available in future releases. For more information, see https://kb.vmware.com/s/article/60229 "
        ],
    "new_vcsa": {
        "vc": {
            "__comments": [
                "'datacenter' must end with a datacenter name, and only with a datacenter name. ",
                "'target' must end with an ESXi hostname, a cluster name, or a resource pool name. ",
                "The item 'Resources' must precede the resource pool name. ",
                "All names are case-sensitive. ",
                "For details and examples, refer to template help, i.e. vcsa-deploy {install|upgrade|migrate} --template-help"
            ],
            "hostname": "<FQDN or IP address of the vCenter Server instance>",
            "username": "<The user name of a user with administrative privileges or the Single Sign-On administrator on vCenter.>",
            "password": "<The password of a user with administrative privileges or the Single Sign-On administrator on vCenter. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>",
            "deployment_network": "VM Network",
            "datacenter": [
                "Folder 1 (parent of Folder 2)",
                "Folder 2 (parent of Your Datacenter)",
                "Your Datacenter"
            ],
            "datastore": "<A specific datastore accessible to the ESXi host or DRS cluster in the 'target' path.>",
            "target": [
                "Folder A (parent of Folder B)",
                "Folder B (parent of Your ESXi Host, or Cluster)",
                "Your ESXi Host, or Cluster"
            ]
        },
        "appliance": {
            "__comments": [
                "You must provide the 'deployment_option' key with a value, which will affect the VCSA's configuration parameters, such as the VCSA's number of vCPUs, the memory size, the storage size, and the maximum numbers of ESXi hosts and VMs which can be managed. For a list of acceptable values, run the supported deployment sizes help, i.e. vcsa-deploy --supported-deployment-sizes"
            ],
            "thin_disk_mode": true,
            "deployment_option": "management-small",
            "name": "vCenter-Server-Appliance"
        },
        "os": {
            "ssh_enable": false
        },
        "temporary_network": {
            "ip_family": "<ipv4 or ipv6>",
            "mode": "static",
            "ip": "<Static IP address. Remove this if using dhcp.>",
            "dns_servers": [
                "<DNS Server IP Address. Remove this if using dhcp.>"
            ],
            "prefix": "<Network prefix length. Use only when the mode is 'static'. Remove if the mode is 'dhcp'. This is the number of bits set in the subnet mask; for instance, if the subnet mask is 255.255.255.0, there are 24 bits in the binary version of the subnet mask, so the prefix length is 24. If used, the values must be in the inclusive range of 0 to 32 for IPv4 and 0 to 128 for IPv6.>",
            "gateway": "<Gateway IP address. Remove this if using dhcp.>"
        },
        "user_options": {
            "vcdb_migrateSet": "<Set the data migration option. Available options are 'core', 'all', 'core_events_tasks', 'transfer_events_tasks_after_upgrade', and  'transfer_stats_events_tasks_after_upgrade'. Note that the last two options, 'transfer_events_tasks_after_upgrade', and 'transfer_stats_events_tasks_after_upgrade', are available only if the database for the source VCSA (the VCSA to be upgraded) is external.>"
        }
    },
    "source_vc": {
        "description": {
            "__comments": [
                "This section describes the source appliance which you want to",
                "upgrade and the ESXi host on which the appliance is running. If you are using vSphere",
                "Update Manager (VUM), and want automated Migration Assistant installation and ",
                "execution on the Windows VUM machine, add the 'source_vum' section. Read more about the 'source_vum' section",
                "in template help, i.e. vcsa-deploy upgrade --template-help"
            ]
        },
        "managing_esxi_or_vc": {
            "hostname": "<FQDN or IP address of the ESXi or vCenter on which the source vCenter Server Appliance resides.>",
            "username": "<Username of a user with administrative privilege on the ESXi host or vCenter Server. For example 'root' for ESXi and 'administrator@<SSO domain name>' for vCenter >",
            "password": "<Password of the administrative user on the ESXi host or vCenter Server. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>"
        },
        "vc_vcsa": {
            "hostname": "<FQDN or IP address of the source vCenter Server Appliance>",
            "username": "administrator@<SSO domain name>",
            "password": "<vCenter Single Sign-On administrator password. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>",
            "root_password": "<Appliance root password. If left blank, or omitted, you will be prompted to enter it at the command console during template verification.>"
        }
    }
}