onionperf more details

metrics/ops/onionperf-ops.mdwn

@@ -7,7 +7,34 @@
 The various moving parts of this project were due to converge in the coming
 months and so it's difficult to document this in the same way as other more
 stable projects. This documents the parts, and their last known state, but
-is more of a snapshot than a source of truth.
+is more of a snapshot than a source of truth. It does not reflect what the
+Ansible playbook would have deployed had we done the upgrades, that would look
+very different.
+
+## Deployed Instances
+
+We currently have four deployed OnionPerf instances:
+
+* op-ab - Scotland (University of Aberdeen)
+* op-hk - Hong Kong (OTF Cloud)
+* op-nl - Netherlands (OTF Cloud)
+* op-us - United States (OTF Cloud)
+
+The first of these may be shut down very soon.
+
+The instances on the OTF cloud do not have a fixed end-date. The virtual
+machines are managed via the eclips.is
+[portal](https://portal.eclips.is/portal/). The sysadmin team have the password
+for this. None of these machines are managed by the sysadmin team, the metrics
+team is responsible for keeping them up to date, and secure enough to be on the
+public Internet.
+
+Login to the instances via SSH is using the `cloud` user, which has SSH keys for
+the admins of the service. The cloud user can sudo to any user using the
+sudo password that is specific to the host.
+
+On each host, a `tmux` session runs as the `cloud` user. This means that sudo
+is not generally needed for routine activities.
 
 ## Changes to OnionPerf since last deployment