Skip to content

Latest commit

 

History

History
85 lines (52 loc) · 3.56 KB

connecting.md

File metadata and controls

85 lines (52 loc) · 3.56 KB
Raw

Connecting to a Setup

VPN Connection

A L2TP/IPsec VPN will be automatically set up on the bastion host. This VPN can be used to access ESXi hosts, as well as vCenter and OpenShift from your local computer if they were deployed to private networks.

In case of private networks, you can also set up an SSH tunnel or a reverse proxy on the bastion server to connect to the vCenter and/or OpenShift instance from your local computer. However, those methods aren't implemented by this repository.

Alternatively, it is possible to SSH to the bastion server and issue vCenter or OpenShift commands from there (see below).

Connecting to the Router/Bastion

The bastion host's IP address is printed out by Ansible after it becomes available. You will already have the right SSH key for a password-less access in your ~./ssh directory.

ssh root@<bastion>

Connecting to ESXi hosts

From the bastion host, you can reach the ESXi host(s). Assuming you haven't change the private subnet 172.16.0.0/24, the IP address of the first ESXi host is 172.16.0.4 (i.e. subnet + 3):

ssh -i ~/.ssh/esxi_key [email protected]

If you're using VPN to access the ESXi hosts, you will need to copy the SSH key over to your local machine.

Useful commands:

  • List all VMs

    vim-cmd vmsvc/getallvms

  • Get the power state of a VM

    vim-cmd vmsvc/power.getstate <vm_id>

Connecting to vCenter

Connect with a browser through HTTPS to the vCenter IP address printed out by the Ansible script and accept the self-signed CA certificate. Use the vCenter credentials saved to <temp_directory>/vcenter.txt — a username (usually [email protected]) and a randomly generated password.

If you prefer the command line, one of the methods is using the govc utility. It can be ran from the bastion host or from the local machine (when deploying with public IP addresses, or using VPN).

  1. Install govc
curl -L -o - "https://github.com/vmware/govmomi/releases/latest/download/govc_$(uname -s)_$(uname -m).tar.gz" | tar -C /usr/local/bin -xvzf - govc
  1. Set connection parameters — IP address, username, password and CA certificate (or ignore the certificate). Example:
export GOVC_URL='https://172.16.3.2'
export GOVC_USERNAME='[email protected]'
export GOVC_PASSWORD='<password>'
export GOVC_INSECURE=true

Useful govc commands

  • Viewing the inventory, including VMs:

    govc tree

  • Viewing the devices of a VM:

    govc device.info -vm my-cluster-sno_vm

Connecting to OpenShift

Use a kubeconfig file that has the assisted installer cluster ID for its file extension, created in the temp directory. For instance, <temp_directory>/kubeconfig.41610064-a819-4e66-9bb5-7c938e96ca38. In addition, a <temp_directory>/kubeadmin-password file will contain the password for accessing the cluster console with username kubeadmin (e.g.tmp/kubeadmin-password.41610064-a819-4e66-9bb5-7c938e96ca38).

The files will be saved into the local temp directory in case of public networks, and to a directory on the bastion server in case of private networks. When using VPN, you will need to copy the kubeconfig file to your local machine.

In order to SSH to an OpenShift node, use ssh -i /path/to/key core@<openshift_node>. The SSH key be located in the local temp directory in case of public network, and in the remote (bastion) temp directory in case of private networks. Its full path will be printed to the console by Ansible.