<!DOCTYPE html><html><head><title></title><style type="text/css">p.MsoNormal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Thu, 16 Apr 2020, at 2:47 AM, Andrew Williams wrote:<br></div><div>> On 2020-04-15 11:15 PM, James Andrewartha wrote:<br></div><div>> > On Wed, 15 Apr 2020, Mark Tearle wrote:<br></div><div>> > <br></div><div>> >> Hi folks<br></div><div>> >><br></div><div>> >> I think mussel is a good candidate as any for getting it off mooneye. Though I feel it would probably be an interim home for<br></div><div>> >> it, and longer term it probably needs it's own VM or something similar.<br></div><div>> > <br></div><div>> > I'm in favour of its own VM, it's quite crusty and could easily fall out<br></div><div>> > of compatibility by accident.<br></div><div>> > <br></div><div>> >> Who's the best contact of the flame users to tell about the move? Andrew?<br></div><div>> > <br></div><div>> > Probably Andrew, I'll try and poke him next time he's on as well.<br></div><div>> <br></div><div>> Yep, the main users are Leighton (old guard), Teik Oh (older guard), and <br></div><div>> me (ancient guard).<br></div><div>> <br></div><div>> I have a live copy of flame (rsynced every night off mooneye) running on <br></div><div>> my home Linux machine, but it's been 20 years or so since I last <br></div><div>> compiled the customised LP-Mud driver from source, and it won't have <br></div><div>> gotten any easier since then. If there's any way of capturing mooneye's <br></div><div>> running disk image, turning it into a VM, and stripping off everything <br></div><div>> except for flame, it would make things much easier.<br></div><div>> <br></div><div>> Andrew<br></div><div>><br></div><div><br></div><div>Hi Andrew<br></div><div><br></div><div>Since your message, here's the progress:<br></div><div><br></div><ul><li>A new VM (maculatus) has been created on UCC's Proxmox cluster (1G RAM, 10G disk)<br></li><li>Background behind the name here - https://wiki.ucc.asn.au/Maculatus<br></li><li>Aside from the DNS and initial install, it has been provisioned with the ucc-ansible-soe<br></li><li>Wheel SSH keys + Andrews ssh keys have been copied to this machine for root<br></li><li>The ucc-ansible-soe is accessible here - https://gitlab.ucc.asn.au/ucc-systems/ucc-ansible-soe<br></li><li>This contains an ansible playbook flame-vm-host.yml which runs a bunch of roles to setup the machine as a wheel only server machine<br></li><li>This playbook has a specific role ucc_setup_flame_environment which does the following additional things<br></li></ul><ol><li>Installs rsync to permit backups<br></li><li>Installs make, gcc and bison which could be useful in future if you intend to recompile the mud driver (more on that later)<br></li><li>Installs the i386 libc6 - this enables the current compiled driver to work (as tested on a copy)<br></li><li>Adds the local flame user (more on that later) and takes a copy of the local root authorized_keys (so wheel + andrew)<br></li><li>Ensures /home/other/flame exists (more on that later)<br></li><li>Adds init script for flame, ucc firewall script, and local webserver (nginx)<br></li><li>Installs ttyd, and configures nginx proxy for web to telnet gateway, at <a href="https://tty.flame.ucc.asn.au/">https://tty.flame.ucc.asn.au/</a><br></li><li>Install nginx proxy for flame web server at <a href="https://www.flame.ucc.asn.au/">https://www.flame.ucc.asn.au/</a> (Currently firewalled to UCC local network only as the flame webserver is slightly broken)<br></li></ol><div><br></div><div>So what needs to happen next:<br></div><ol><li>Flame needs to be copied over to the machine into /usr/flame, tested, and the DNS updated to point flame at maculatus<br></li><li>A cron job needs to be added to drop a backup of flame into /home/other/flame (so it gets picked up by the normal UCC backups), and any other backups need to be tested and made working<br></li><li>We might need to work out why flame has the same uid as andrew and correct this<br></li><li>Email delivery to flame can probably be made to work again with an appropriate bind mount added on the machine (and included in the ansible role)<br></li><li>A decision to decommission the flame-tunnel IP address (all ports to 4242 on flame) as we have the web to telnet gateway setup<br></li><li>I attempted to compile a copy of the driver source that was in the flame directory - gcc barfs out of the box due to changes in varargs. There looks like there are some modern forks of the code out there, but would require further investigation by someone other than me<br></li><li>Fixing up the flame webserver - again someone other than me<br></li><li>Setting up a web to gopher gateway to access the flame gopher server<br></li><li>Fixing up UCC's finger installation (including finger flame@ucc)<br></li></ol><div><br></div><div>Anyhow, items 1 and 2 are the most pressing as these will enable things to be moved off of mooneye. Suggestions on how to co-ordinate this?<br></div><div><br></div><div>Cheers,<br></div><div><br></div><div>Mark<br></div><div>Ps. How do I reset my flame password cleanly? (for sparky)<br></div><div>--<br></div><div>Mark Tearle <mtearle@ucc.asn.au><br></div></body></html>