Update: I didn't migrate it, I just shut it down in place. With luck I can delete it in a few days.

@Andrew I believe this is used by @cscott; might be worth waiting for him to be back before making any decisions.

Hm, is @cscott still out?

<cscott> subbu: i'm not sure i know what parsoid-spof is, either. i'll take a look. what does "spof" stand for, i wonder? that's probably a good clue.
<subbu> single point of failure :)
<subbu> james thought you were using that vm
<cscott> i don't think it was me. i'd hope that i would have remembered what spof stands for, if it were. ;)

I don't think I'm responsible for having created parsoid-spof. Does anyone have an idea what spof stands for? That might be a clue.

I guess if we started it up I might be able to log in and poke around. On the other hand, it's not necessarily guaranteed that I have a log in on the machine...

Maybe https://gerrit.wikimedia.org/r/#/c/70582/ is related? It was written by @Catrope , maybe he remembers what parsoid-spof was.

From https://gerrit.wikimedia.org/r/68133: "parsoid-spof is maintained by the Parsoid team and is updated with the latest Parsoid code frequently. deployment-parsoid2 is not maintained and isn't updated regularly."

I don't think that's been true for a long while.

It was also referenced from $wgVisualEditorParsoidReportProblemURL in https://gerrit.wikimedia.org/r/114100.

I'm pretty sure 'spof' stands for 'single point of failure.'

The instance has been shutdown for a couple of weeks and no one has complained...

You can delete this instance. This is no longer being used .. and clearly no one has shouted at any of us since you disabled this.