ℹ️ Info
Outcome: A completed worksheet of names, network values, credentials, and generated keys used throughout the lab.
Before you begin: Obtain the DataEngine Site Survey details from your VAST Sales Engineer.
ℹ️ Info
If you are a VAST customer or partner, please contact your Sales Engineer for assistance filling out a DataEngine Site Survey document which will gather all of the below information as well as other critical environmental details.
Initial Configuration Values
Before starting the Initial VAST configuration, you will need to fill in several values throughout the process. Decide most of these values in advance to ensure consistent naming and speed up the process.
Input name | Example | Your value |
|---|---|---|
VAST Identity provider name | de-lab-provider | |
AD/LDAP Identity Provider name | ||
DataEngine tenant name | de-lab-tenant | |
DataEngine VIP pool name | de-lab-vippool | |
DataEngine VIP pool Gateway Address | ||
DataEngine VIP pool start IP | 172.200.205.13 | |
DataEngine VIP pool end IP | 172.200.205.18 | |
DataEngine VIP pool subnet CIDR | 16 | |
DataEngine VIP pool VLAN Tag | ||
DataEngine pool DNS name | de-lab-vippool | |
DataEngine S3 view policy name | de-lab-s3-policy | |
DataEngine NFS view policy name | de-lab-csi-policy | |
Docker repository view path | /de-lab-docker/images | |
DataEngine local/ldap/ad group name | de-lab-group | |
DataEngine local group GID | 854321 | |
DataEngine local/ldap/ad username | de-lab-user | |
DataEngine local user temporary password | <choose-a-strong-password> | |
Data Engine user S3 access key (generated) | (generated in a later step) | |
Data Engine user S3 secret key (generated) | (generated in a later step) |
CSI Configuration Values
Values used only by the VAST CSI driver: its tenant, VIP pool, view policy, roles, and manager accounts. Skip this table if you are not installing the CSI driver.
Input name | Example | Your value |
|---|---|---|
Trash folder GID | 0 | |
CSI tenant name | de-lab-csi-tenant | |
CSI VIP pool name | de-lab-csi-vippool | |
CSI VIP pool Gateway Address | ||
CSI VIP pool start IP | 172.200.205.19 | |
CSI VIP pool end IP | 172.200.205.24 | |
CSI VIP pool subnet CIDR | 16 | |
CSI VIP pool VLAN Tag | ||
CSI VIP pool DNS name | de-lab-csi-vippool | |
CSI view policy name | de-lab-csi-policy | |
CSI tenant-admin role name | de-lab-csi-tenant-admin | |
CSI service-account role name | de-lab-csi-service-account | |
CSI tenant-admin manager username | de-lab-csi-admin | |
CSI tenant-admin manager password | <choose-a-strong-password> | |
CSI driver manager username | de-lab-csi-driver | |
CSI driver manager password | <choose-a-strong-password> |
DataEngine to Kubernetes and registry
Unique values for connecting VAST DataEngine to a Kubernetes cluster and registry. You may reuse DataEngine tenant, S3 view policy, bucket owner user, and DataEngine VIP pool from the table above. Certificates come from ~/.kubeconfig/rke2.yaml (certificate-authority-data, client-certificate-data, client-key-data).
Input name | Example | Your value |
|---|---|---|
Kafka broker view path | /de-lab-broker | |
Kafka broker S3 bucket name | de-lab-broker | |
Kafka VIP pool name | de-lab-broker-vippool | |
Kafka VIP pool Gateway Address | ||
Kafka VIP pool start IP | 172.200.205.19 | |
Kafka VIP pool end IP | 172.200.205.24 | |
Kafka VIP pool subnet CIDR | 16 | |
Kafka VIP pool VLAN Tag | ||
Kafka VIP pool DNS name | de-lab-csi-vippool | |
Default topic name | de-default-topic | |
Topic partitions | 1 | |
Deadletter topic name | de-deadletter-topic | |
Topic partitions | 1 | |
Kubernetes cluster name | de-lab-rke2 | |
Kubernetes API server URL | https://10.144.19.2:6443 | |
Kubeconfig CA certificate (certificate-authority-data) | ||
Kubeconfig client certificate (client-certificate-data) | ||
Kubeconfig private key (client-key-data) | ||
DataEngine namespace | vast-pipelines | |
Container registry name | de-lab-registry | |
Container registry base URL | http://10.144.19.8 | |
Container registry authentication method | None |
Worksheet completion check
Before continuing, fill in every value required by your chosen path. Leave generated access keys blank until the procedure creates them, then store them in an approved secret manager.