Deploy VMware Blockchain Nodes Using VMware Blockchain Orchestrator on vSphere

Using the VMware Blockchain Orchestrator, you can deploy VMware Blockchain nodes on your os environment.

Prerequisites

Verify that your VMware Blockchain Orchestrator appliance is successfully deployed. See Deploy a VMware Blockchain Orchestrator Appliance on vSphere.
Verify that you familiarize yourself with the VMware Blockchain Orchestrator descriptor files. See Configuring the Infrastructure Descriptor Parameters on vSphere and Configuring the Deployment Descriptor Parameters on vSphere.
Verify that you have reserved IP addresses in vSphere for the Replica and Client nodes.
These reserved IP addresses must be specified in the providedIp fields for each Replica and Client node in the descriptor file.
If you are using a USB HSM to secure and encrypt data, verify that the ESXi host and the ESXi host name where the physical USB device is connected are known. The USB HSM VM can identify and attach itself to the ESXi host.

Procedure

Power on the VMware Blockchain Orchestrator appliance.
SSH into the VMware Blockchain Orchestrator appliance.
Enter the login credentials for the blockchain user account.
Navigate to the /home/blockchain directory.

List the contents of the /home/blockchain directory.

ls -l

Option	Description
/home/blockchain/orchestrator-runtime	Directory consists of all the docker-compose files and descriptor files. You can run the VMware Blockchain Orchestrator script from this directory.
docker-compose-orchestrator-prereqs.yml	Runs the Docker configuration service and provisioning service containers. The prerequisite service starts when the VM is powered on. The prerequisite service times out if the VM does not have connectivity when powered on and must be manually restarted.
docker-compose-orchestrator.yml	Runs the VMware Blockchain Orchestrator script to deploy VMware Blockchain nodes.
infrastructure-descriptor-v1.schema	Directory stores the infrastructure definitions of all the available parameters to manually configure to deploy VMware Blockchain nodes.
deployment-descriptor-v1.schema	Directory stores the deployment definitions of all the available parameters to manually configure to deploy VMware Blockchain nodes.

To configure the descriptor files and set the parameter values, you must create directories to store the descriptor files.

Create a directory for the descriptor files.

See the sample directory structure.

Option	Description
/home/blockchain/descriptors	Directory stores the infrastructure and deployment descriptor JSON files. VMware Blockchain Orchestrator uses the parameter values set in the infrastructure and deployment descriptor files during provisioning.
/home/blockchain/output	Directory stores the deployment details, such as IP address, Replica and Client node names, blockchain ID, and consortium ID.
INFRA_DESC_FILENAME=infrastructure_descriptor.json	File provides infrastructure details for deployment that VMware Blockchain Orchestrator uses to prescribe the parameters and connect to vCenter Server.
DEPLOY_DESC_FILENAME=deployment_descriptor.json	File provides deployment details for Replica and Client nodes. If you deploy Full Copy Client nodes, the deployment details are included in this file. For example, the file also consists of zone names, client group names, and IP addresses.

Verify that the Docker containers are running.

cd ~blockchain/orchestrator-runtime
docker ps -a

The Docker containers that are running appear.

blockchain@localhost [ ~ ]$ docker ps -a
CONTAINER ID        IMAGE                                                                                COMMAND                  CREATED             STATUS              PORTS                                            NAMES
a20b7fbeacff        athena-docker-local.artifactory.eng.vmware.com/persephone-configuration:0.0.0.2323   "java -Dspring.confi…"   2 minutes ago       Up 2 minutes        0.0.0.0:9003->9003/tcp, 0.0.0.0:8000->9023/tcp   orchestrator-runtime_config-service_1
10cdca6852d8        athena-docker-local.artifactory.eng.vmware.com/persephone-provisioning:0.0.0.2323    "java -Dspring.confi…"   2 minutes ago       Up 2 minutes        8000/tcp, 0.0.0.0:9002->9002/tcp                 orchestrator-runtime_persephone-provisioning_1

If the Docker containers are not running, then restart the Docker containers.
1. Log into the VMware Blockchain Orchestrator appliance.
2. Restart the system service, which in turn starts the Docker containers.
```
systemctl restart blockchain.service
```

Create the infrastructure and deployment descriptor files in the descriptor directory.

VMware Blockchain Orchestrator uses the variables defined in these descriptor files to provision the VMware Blockchain nodes.

Sample infrastructure_descriptor.json file to deploy a vCenter Server, datastore, and cluster.

{
  "organization": {
    "damlSdk": 2.4.0",
    "dockerImage": "1.8.0.0.53",
    "generatePassword": true,
    "generateDamlDbPassword": true
    "secureStore": {
      "storeType": "DISK",
      "url": "file:///config/url/file.json"
  },
  "zones": [
    {
      "name": "replicas",
      "vCenter": {
        "url": "https://vcsa.corp.local/",
        "userName": "[email protected]",
        "password": "VMware1",
        "resourcePool": "replicas",
        "storage": "RegionA01-ISCSI01-COMP02",
        "folder": "blockchain"
      },
      "network": {
        "name": "VM-RegionA01-vDS-COMP",
        "gateway": "192.168.10.1",
        "subnet": 24,
        "nameServers": [
          "192.168.10.10"
        ]
    },
      "containerRegistry": {
      "url": "https://vmwaresaas.jfrog.io/vmwblockchain",
      "userName": "vmbc-jfrog-reader@vmware",
      "password": "<password>"
      },
      "pullMetricsEndpoint": {
         "userName": "metricsUser",
         "password": "metricsPassword",
         "tlsCertificateData": "<public-key-string>",
         "tlsKeyData": "<private-key-string>"
      },
    }
  ]
}

Sample deployment_descriptor.json file deploys four Replica nodes, two Full Copy Client nodes, and two Client nodes.

{
  "replicas": [
    {
    "zoneName": "replicas",
    "providedIp": "192.168.10.12"
    },
    {
    "zoneName": "replicas",
    "providedIp": "192.168.10.13"
    },
    {
    "zoneName": "replicas",
    "providedIp": "192.168.10.14"
    },
    {
    "zoneName": "replicas",
    "providedIp": "192.168.10.15"
    }
  ], 
  "replicaNodeSpec":{
    "cpuCount": 2,
    "memoryGb": 16,
    "diskSizeGb": 64
  },
  "fullCopyClients": [
    {
      "accessKey": "ACCESS_KEY_1",
      "bucketName": "s3BUCKET_1",
      "protocol": "s3",
      "secretKey": "SECRET_KEY_1",
      "url": "109.72.217.75:9000",

      "zoneName": "replicas",     
      "providedIp": "192.168.10.16" 
    }, 
    {
      "accessKey": "ACCESS_KEY_1",
      "bucketName": "BUCKET_1",
      "protocol": "HTTP/HTTP",
      "secretKey": "SECRET_KEY_1",
      "url": "blockchain.s3.amazonaws.com",

      "zoneName": "replicas",
      "providedIp": "192.168.10.17" 
        }
  ],
  "clients": [
    {
      "zoneName": "replicas",
      "providedIp": "192.168.10.18"
      "damlDbPassword": "<password>",
      "groupName": "Group1",
      "tlsLedgerData": {
        "pem" : "pem1",
        "crt" : "crt1",
        "cacrt": "cacrt1",
        "clientAuth" : "REQUIRE"
      }
    },
    {
      "zoneName": "replicas",
      "providedIp": "192.168.10.19"
      "damlDbPassword": "<password>",
      "groupName": "Group2",
      "tlsLedgerData": {
        "pem" : "pem1",
        "crt" : "crt1",
        "cacrt": "cacrt1",
        "clientAuth" : "OPTIONAL"
      }
  ],
  "clientNodeSpec":{
    "cpuCount": 4,
    "memoryGb": 32,
    "diskSizeGb": 100
  },
  "blockchain": {
    "consortiumName": "finance",
    "blockchainType": "Daml"
  }
}

Sample rocksdb_checkpoint_infrastructure_descriptor.json file to deploy new blockchain nodes with customized parameters for RocksDB checkpoint-based backup.

{
    "organization": {
      ...
      "advancedFeatures" : {
           ...
           "ENABLE_DB_CHECKPOINT_BACKUP": true
           "NUM_DB_SNAPSHOTS": "2",
           "DB_SNAPSHOT_INTERVAL_HOURS": "6"
      }
    },
    ...
}

Validate your infrastructure descriptor file semantics against the infrastructure-descriptor-v1.schema.
Validate your deployment descriptor file semantics against the deployment-descriptor-v1.schema.

Validate that the credentials, network name, and folder name are correctly populated to avoid errors.

ORCHESTRATOR_DESCRIPTORS_DIR=/home/blockchain/descriptors  
INFRA_DESC_FILENAME=infrastructure_descriptor.json 
DEPLOY_DESC_FILENAME=deployment_descriptor.json 
ORCHESTRATOR_OUTPUT_DIR=/home/blockchain/output 
ORCHESTRATOR_DEPLOYMENT_TYPE=VALIDATE 
docker-compose -f docker-compose-orchestrator.yml up

Encrypt and redirect the infrastructure and the deployment descriptor files for added security.
1. Encrypt the infrastructure_descriptor.json file.
```
$HOME/descriptors > ansible-vault encrypt infrastructure_descriptor.json
New Vault password:
Confirm New Vault password:
Encryption successful
```
2. Encrypt the deployment_descriptor.json file.
```
$HOME/descriptors > ansible-vault encrypt deployment_descriptor.json
New Vault password:
Confirm New Vault password:
Encryption successful
```
3. Configure the two environment variable values.
  - ORCHESTRATOR_OUTPUT_DIR - The output directory where the output file is written.
  - ORCHESTRATOR_DEPLOYMENT_TYPE - Set deployment type to PROVISION.
4. Run the secure-orchestrator.sh script from the orchestrator_runtime directory.
```
ORCHESTRATOR_OUTPUT_DIR=$HOME/output 
ORCHESTRATOR_DEPLOYMENT_TYPE=PROVISION 
./secure-orchestrator.sh
```
  The script creates temporary files.
  - /dev/shm/orchestrator-awsIGoa0JA/infra_descriptor
  - /dev/shm/orchestrator-awsIGoa0JA/deployment_descriptor
5. Redirect the decrypted infrastructure_descriptor.json to the infrastructure_descriptor file location.
  Use the vault password used to encrypt the infrastructure_descriptor.json file.
```
ansible-vault view $HOME/descriptors/infrastructure_descriptor.json > /dev/shm/orchestrator-awsIGoa0JA/infra_descriptor
```
6. Redirect the decrypted deployment_descriptor.json to the deployment_descriptor file location.
  Use the vault password used to encrypt the deployment_descriptor.json file.
```
ansible-vault view $HOME/descriptors/deployment_descriptor.json > /dev/shm/orchestrator-awsIGoa0JA/deployment_descriptor
```
  After the script completes running, the temporary files are deleted.
7. (Optional) If the script fails or the secure_orchestrator.sh script is terminated, delete the temporary folder under the /dev/shm/orchestrator-* directory.

Run the VMware Blockchain Orchestrator deployment script.

For a new deployment, run the command.

ORCHESTRATOR_DESCRIPTORS_DIR=/home/blockchain/descriptors 
INFRA_DESC_FILENAME=infrastructure_descriptor.json 
DEPLOY_DESC_FILENAME=deployment_descriptor.json 
ORCHESTRATOR_OUTPUT_DIR=/home/blockchain/output 
docker-compose -f docker-compose-orchestrator.yml up

For a USB HSM deployment, run the command.

CONFIG_SERVICE_IP=$(hostname -I | awk '{print $1}') 
docker-compose -f docker-compose-orchestrator.yml up

(Optional) During deployment, view the VM creation and IP allocation from the vSphere Client under the Workloads > <Workload_Name> > VMs tab.

The deployment of the VMware Blockchain nodes can take up to five minutes.

(Optional) If you have enabled the pullMetricsEndpoint parameter, you can run the command and retrieve the monitoring metrics data.

# If using username/password use http
curl -i -u '<username>:<password>' http://<VM-IP>:9273/metrics
# If using TLS use https
curl -i -l -u '<username>:<password>' https://<VM-IP>:9273/metrics -k

Results

After a successful deployment, the VMware Blockchain Orchestrator creates and saves the deployment results in the /home/blockchain/output directory.

Note:

If your deployment fails, identify the error and fix it before redeploying the VMware Blockchain nodes.

Example

Sample output file.

Starting deployment type: PROVISION, at 2022-08-21T07:06:15.432477
Consortium Name: consortium-1, Consortium Id: 07cf1de7-8070-4841-8093-78e2175bb016
Blockchain Version: 1.8.0.0.53
Deployment Request Id: 4403db4a-be17-4c57-b9bc-31a56115968b
DAML message type: null
Blockchain Id: d8931719-4dd1-4151-893d-88a6f517c4b2
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: /blocks/sddc6-vmware-vpn-onprem-3/segments/0a48dc00/addresses/0a48dca2, key: PRIVATE_IP, value: 10.72.220.162
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: DAML_SDK_VERSION, value: 1.0.1
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: DataDeviceId, value: 2001
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: ENCRYPT_SECRETS, value: True
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: NODE_LOGIN, value: password
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: NODE_USER, value: vmbc
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: REMOVE_ROOT, value: True
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: SIGNATURE_SAVE, value: SIGNATURE
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: vmId, value: d8931719-4dd1-4151-893d-88a6f517c4b2-534031e0-049e-4130-9f8f-f24b36518f4e
Node Id: 534031e0-049e-4130-9f8f-f24b36518f4e, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45397, key: vmInstance, value: vm-45397
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: /blocks/sddc6-vmware-vpn-onprem-3/segments/0a48dc00/addresses/0a48dca3, key: PRIVATE_IP, value: 10.72.220.163
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: DAML_SDK_VERSION, value: 1.0.1
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: DataDeviceId, value: 2001
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: ENCRYPT_SECRETS, value: True
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: NODE_LOGIN, value: password
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: NODE_USER, value: vmbc
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: REMOVE_ROOT, value: True
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: SIGNATURE_SAVE, value: SIGNATURE
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: vmId, value: d8931719-4dd1-4151-893d-88a6f517c4b2-62e2aac4-bc3a-434d-8a67-31277cf5429d
Node Id: 62e2aac4-bc3a-434d-8a67-31277cf5429d, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45399, key: vmInstance, value: vm-45399
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: /blocks/sddc6-vmware-vpn-onprem-3/segments/0a48dc00/addresses/0a48dca4, key: PRIVATE_IP, value: 10.72.220.164
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: CLIENT_BACKUP_ENABLED, value: false
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: CLIENT_CONFIG_PROPERTIES, value: {
}
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: CLIENT_ENDPOINT, value: https://10.72.220.164:6865
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: CLIENT_GROUP_ID, value: e5b1e624-ae3b-4a28-b197-067d28044cf2
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: CLIENT_GROUP_NAME, value: Group1
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: CLIENT_POSTGRES_PROPERTIES, value: {
  "values": {
    "max_connections": "300",
    "shared_buffers": "4GB",
    "effective_cache_size": "12GB",
    "maintenance_work_mem": "1GB",
    "checkpoint_completion_target": "0.9",
    "wal_buffers": "16MB",
    "default_statistics_target": "100",
    "random_page_cost": "4",
    "effective_io_concurrency": "2",
    "work_mem": "40MB",
    "min_wal_size": "2GB",
    "max_wal_size": "8GB",
    "max_worker_processes": "4",
    "max_parallel_workers_per_gather": "2",
    "max_parallel_workers": "4",
    "max_parallel_maintenance_workers": "2"
  }
}
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: DAML_DB_PASSWORD, value: mypass
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: DAML_SDK_VERSION, value: 1.0.1
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: DataDeviceId, value: 2001
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: ENCRYPT_SECRETS, value: True
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: NODE_LOGIN, value: password
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: NODE_USER, value: vmbc
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: REMOVE_ROOT, value: True
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: SIGNATURE_SAVE, value: SIGNATURE
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: vmId, value: d8931719-4dd1-4151-893d-88a6f517c4b2-8dcb089f-8d0a-4f24-acda-fad1ef13ed3b
Node Id: 8dcb089f-8d0a-4f24-acda-fad1ef13ed3b, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45400, key: vmInstance, value: vm-45400
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: /blocks/sddc6-vmware-vpn-onprem-3/segments/0a48dc00/addresses/0a48dca6, key: PRIVATE_IP, value: 10.72.220.166
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: DAML_SDK_VERSION, value: 1.0.1
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: DataDeviceId, value: 2001
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: ENCRYPT_SECRETS, value: True
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: NODE_LOGIN, value: password
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: NODE_USER, value: vmbc
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: REMOVE_ROOT, value: True
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: SIGNATURE_SAVE, value: SIGNATURE
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: vmId, value: d8931719-4dd1-4151-893d-88a6f517c4b2-95a8a4e1-69c9-4c38-ba1f-4b9e67931483
Node Id: 95a8a4e1-69c9-4c38-ba1f-4b9e67931483, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45396, key: vmInstance, value: vm-45396
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: /blocks/sddc6-vmware-vpn-onprem-3/segments/0a48dc00/addresses/0a48dca5, key: PRIVATE_IP, value: 10.72.220.165
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: DAML_SDK_VERSION, value: 1.0.1
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: DataDeviceId, value: 2001
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: ENCRYPT_SECRETS, value: True
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: NODE_LOGIN, value: password
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: NODE_USER, value: vmbc
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: REMOVE_ROOT, value: True
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: SIGNATURE_SAVE, value: SIGNATURE
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: vmId, value: d8931719-4dd1-4151-893d-88a6f517c4b2-f163dd94-e1b5-45f7-9bc0-32e397f2127c
Node Id: f163dd94-e1b5-45f7-9bc0-32e397f2127c, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-45398, key: vmInstance, value: vm-45398
Blockchain Id: d8931719-4dd1-4151-893d-88a6f517c4b2, completion status: SUCCESS
RequestId: 4403db4a-be17-4c57-b9bc-31a56115968b succeeded
Deployment finished at 2022-03-21T07:08:46.595558 with status SUCCESS

What to do next

Verify that the Replica node includes all the parameter values set in the deployment descriptor. See Validate a Replica Node in VMware Blockchain Orchestrator on vSphere.