...
A virtual private network (VPN) connection is required recommended to access the cluster. This adds an extra layer of security. The Talapas VPN should provide all the same capabilities as UO VPN as well as adding access to Talapas.
...
Use “uovpn.uoregon.edu/talapas
" as the connection URL and your duckid and password. Advanced users might want to use OpenConnect, OpenConnect VPN client. This would support connection using a command such as,
Code Block |
---|
sudo openconnect --useragent="AnyConnect Linux" --protocol=anyconnect uovpn.uoregon.edu/talapas |
Note: On some platforms, you may also need to specify --useragent="AnyConnect Linux"
Do not repeatedly attempt to log in when you’re getting error messages. As with other uses of your DuckID at UO, if you generate a large number of login failures, all DuckID access (including things like e-mail) will be locked University-wide. Similarly, be aware of automated processes like cron jobs that might trigger this situation without your notice.
...
Note that inbound access to the new cluster is only allowed for SSH and Open OnDemand. All other ports are blocked.
Load balancer
The preferred method of access is via If you can’t use the VPN, you can also connect to the login loadbalancer at login.talapas.uoregon.edu
The new cluster has 3 4 login nodes. A load balancer is used to redirect SSH connections to different login nodes to spread the load. The load balancers choice of login node is “sticky” in that repeated connections from your IP address will go to the same login node - as long as there has been some activity within the last 24 hours.
...