...
Team members will want to access the OpenStack Horizon dashboard, the Rancher GUI, and their VMs. Because these resources are on private networks, the only means of access is a ssh tunnel through console.sb10.orbit-lab.org. The following are example commands that create these tunnels. If others can provide more efficient methods of creating the tunnels, please share them by editing this page. Please connect through node2-1 rather than node1-1 because node1-1 is the OpenStack controller and it is underpowered. We will remedy this when the new servers arrive.
To access the OpenStack Horizon dashboard
...
| Code Block |
|---|
ssh -A -t <username>@console.sb10.orbit-lab.org -L 8585:localhost:8585 \ ssh -A -t <username>@node1<username>@node2-1 -L 8585:localhost:80 |
The dashboard is listening on port 80, and this command creates a multi-hop ssh tunnel that listens on port 8585, which is a random high number port, on one's local machine and relays through the console to appear at port 80 on node1-1. Team members can then access the dashboard by opening a browser on their local machine and navigating to http://localhost:8585/horizon/auth/login. Before executing the command, though, team members should install their public keys in each machine in the multi-hop tunnel in the ~/.ssh/authorized_keys file.
...
| Code Block |
|---|
ssh -A -t <username>@console.sb10.orbit-lab.org -L 9999:localhost:9999 \ ssh -A -t <username>@node1<username>@node2-1 -L 9999:localhost:9999 \ ssh -A -t <username>@<ip-address-of-sb4-rancher> -L 9999:localhost:8080 |
Pointi Point a browser on your local machine at http://localhost:9999/env/1a7/infra/stack to view the GUI. As before, 9999 is a random high number port and public keys should be installed in each machine in the tunnel.