Kerberos would be a good idea to integrate with the rest of skynet, but it isn't supported. They have something called netkey/SecureNet, I don't know if that would be workable. Until then, you can email firstname.lastname@example.org to ask for an account.
The VM's IP address address is 22.214.171.124. Probably the easiest way to use it is to bring up a remote GUI window by doing the following. You'll need to make the following tunnels (copied from my root's .ssh/config):
Host skynet.ie # Plan 9 ncpu (for drawterm) LocalForward 17013 126.96.36.199:17013 # Plan 9 cpu (for dt2k) LocalForward 17010 188.8.131.52:17010 # Plan 9 authentication LocalForward 567 184.108.40.206:567
Then you can use the drawterm program as follows:
drawterm -a localhost -c localhost -u your_login
assuming the other end of your tunnels is localhost.
To use the thing, you might want to start with "Using rio" and "UNIX to Plan 9 command translation" from the documentation. You can use VNC as well if you read man vncs.
It's not possible to access the Internet from the VM. The VM isn't on a routable IP address. An ssh tunnel through an account on skynet.ie won't work because that sshd demands protocol version 2 but Plan 9 only got something >= 1.5. This could be fixed by changing "Protocol 2" to "Protocol 2,1" in /etc/ssh/sshd_config, but as version 1 was disabled for security reasons, I'm happy to leave it alone.
It's either a good thing or a bad thing, depending on your point of view, but Plan 9 was designed to run very large networks (e.g. AT&T). So they designed their own way to do single sign-on (the auth server you had to make a tunnel for), MTA, httpd, DNS server, etc. Most of the software running on the Skynet cluster has a Plan 9 equivalent, but the point is that it is an equivalent, the exact same package probably won't work, so it's different to administer.
Notes for Admins
The following Wiki pages will tell you what little I know about the administration of this VM:
Drawterm to your terminal. In particular, anyone restarting the vm (e.g. using "xm destroy" followed by "xm create") will have to run the few commands at the end of this page to run the authentication server (although the cpu servers seem to start automatically). To do: add this to /bin/cpurc.