We're using toastfs-dev.mit.edu (18.181.0.87). This is a VM server set up by vasilvv, which is currently being maintained by cela.

There are six virtual machines running:
 - strawberry-habanero.mit.edu: 18.181.0.90
 - cheesy-fries.mit.edu:        18.181.0.91
 - king-cakes.mit.edu:          18.181.0.92
 - eggs-benedict.mit.edu:       18.181.0.97
 - huevos-rancheros.mit.edu:    18.181.0.104
 - ole-miss.mit.edu:            18.181.0.106
(Thank vasilvv for the VM naming scheme.)

The first three (strawberry-habanero, cheesy-fries, king-cakes) are allocated to the Spike development effort. Talk to parkah for access, or cela if parkah is unavailable. Last time I (cela) checked, king-cakes.mit.edu was being used as a load balancer, and the other two were servers.

The last three (eggs-benedict, huevos-rancheros, ole-miss) are allocated to the Provisioning effort. These are likely to be used as a kubernetes/ceph cluster. Talk to cela for access.

To work with VMs: use virsh
 - list              (running VMs)
 - list --all        (all VMs)
 - edit VM           (modify config)
 - start VM          (boot VM)
 - destroy VM        (force-stop VM; inverse of start)
 - shutdown VM       (nicely-stop VM)
 - reset VM          (force-reboot VM)
 - reboot VM         (nicely-reboot VM)
 - create CFG        (create template for VM; not the inverse of destroy)
 - attach-disk SERVER /srv/DISK.iso hdc --type cdrom --mode readonly        (insert CD to running machine)

VNC ports:
 - eggs-benedict: 5904
 - huevos-rancheros: 5905
 - ole-miss: 5906

Use -L 5904:127.0.0.1:5904 in ssh line; vncviewer 127.0.0.1:5904