Provisioning on-premises nodes
How to meet the software prerequisites with automatic provisioning
This page documents the preview version (v2.21). Preview includes features under active development and is for development and testing only. For production, use the stable version (v2024.1). To learn more, see Versioning.
v2.20 and earlier
For instructions on preparing nodes for on-premises configurations in v2.20 and earlier, see Create on-premises provider configuration.When YugabyteDB Anywhere (YBA) has access to an SSH user with passwordless sudo privileges (for example, the ec2-user
on AWS EC2 instances), then YBA can provision the VMs automatically.
With Internet or Yum connectivity
If your VM has Internet or Yum connectivity, you must provide to YBA a VM with the following pre-installed:
- Supported Linux OS with an SSH-enabled, root-privileged user. YBA uses this user to automatically perform additional Linux configuration, such as creating the
yugabyte
user, updating the file descriptor settings via ulimits, and so on. - Additional software
Take the time now to prepare the VM.
- Save the SSH-enabled, root-privileged user credentials (username and SSH Private Key Content PEM file).
- Save the VM IP addresses for later when creating the on-premises provider.
Save for later | To configure |
---|---|
SSH-enabled, root-privileged user name | On-premises provider |
SSH-enabled, root-privileged Private Key Content PEM file | On-premises provider |
VM IP addresses | On-premises provider |
No Internet nor Yum connectivity
If your VM doesn't have Internet or Yum connectivity, you must provide to YBA a VM with the following pre-installed:
- Supported Linux OS with an SSH-enabled, root-privileged user. YBA uses this user to automatically perform additional Linux configuration, such as creating the
yugabyte
user, updating the file descriptor settings via ulimits, and so on. - Additional software
- Additional software for airgapped
Take the time now to prepare the VM.
- Save the SSH-enabled, root-privileged user credentials (username and SSH Private Key Content PEM file).
- Save the VM IP or DNS addresses for later when creating the on-premises provider.
Save for later | To configure |
---|---|
SSH-enabled, root-privileged user name | On-premises provider |
SSH-enabled, root-privileged Private Key Content PEM file | On-premises provider |
VM IP addresses | On-premises provider |