How to gain access to the backend infrastructure for Nectar resources at UoA.
- Request access from CeR Nectar Operator(s). You will be asked to provide your public ssh key.
- Backend login is by ssh key only. You'll need to set up ssh forwarding on your local machine. If you're using MacOS, for example, add or modify the file ~/.ssh/config, and add the following to it:
- When access is granted, you can ssh into the Nectar NAT gateway at 188.8.131.52. If your key is your default key locally in ~/.ssh/id_rsa.pub, you should be able to type just 'ssh firstname.lastname@example.org'. If you are using a key by a different name/path, you must specify that key (including path if not local) with the '-i' flag. Note: in MacOS, we needed to run ssh-add after each restart before connecting.
- Once inside, you should be able to ssh root@ip to any Nectar server, and your key will be automatically forwarded for authentication.
Access to Backend Web UI Interfaces
- Instead of logging in with 'ssh email@example.com' as in the above procedure, use the following to tunnel port 8000: "ssh -D 8000 firstname.lastname@example.org".
- Next, setup a SOCKS proxy in your browser to use 127.0.0.1 : 8000. It's easy to keep a browser such as Firefox installed for only this purpose if you find you're using this a lot. As an example, here are the settings in Firefox:
(Preferences → Advanced → Network Settings)
- As long as you ssh with the -D 8000 option now, you can access the backend web UIs of Nectar. Some examples are below:
Nagios - https://10.31.80.8/nagios3/
Ganglia - https://10.31.80.8/ganglia/
HAPRoxy (for DB) - http://10.31.80.36:3307/
Kibana - https://10.31.80.9/kibana
RabbitMQ - http://10.31.80.51:15672/