Provisioning on-premises nodes

How to meet the software prerequisites with assisted manual provisioning

Use Assisted Manual Provisioning in the following case:

  • You can allow SSH to a root-priveleged user, AND
  • You can't provide YBA with SSH login credentials for that user; however you can enter the password manually interactively.

SSH is required only during initial provisioning of the nodes. After a node is provisioned, you can disable SSH.

In this provisioning workflow, after creating the VMs, installing YBA, and creating an on-premises provider, YBA creates a script (provision_instance.py) for you to use to provision the nodes interactively. The script signs in to each of your VMs with SSH credentials that you provide (including username and password), and prepares the VM.

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:

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