• Re: NodeX to Node/X directories

    From Tracker1@1:103/705 to deon on Wed Jan 27 16:25:41 2021
    On 1/26/2021 10:04 PM, deon wrote:
    Yeah, I didn't bother with multiple instances as it just
    seems to complicate some things.. I am running the ircd and
    the two different web UIs on separate entries though as

    Ahh, I actually found it quite easy - leveraging the "hostname"
    in the ini files.

    So my game servers "hostnames" are bbs_game-1, bbs_game-2 -
    which is generated by the swarm. If I changed replicas to 3,
    the 3rd one would be called bbs_game-3, etc

    Gotcha, doing similar for running the different websites, vs
    using the multi-host support in sync... Same host server though.

    With haproxy in front (and connected to the swarm network), I
    can either redirect traffic dirrectly to a specific instance
    - eg "bbs_game-1", or to any instance using "bbs_game".

    So, sbbs.ini is renamed to sbbs.bbs_game-1.ini, etc and only
    bbs_game-1 starts the services.

    Cool... might look into that if I start getting more door traffic.

    I've not run into any issues so far.

    (For this to work across hosts, you need a shared filesystem,
    which is probably a little more complex for some, but NFS should
    work. I'm not a fan of NFS, so I use a proprietary cross host
    filesystem.)

    Just curious, what FS sharing are you using? And have you had
    issues with multi-node DOSemu doors... I haven't even started
    setting up any doors yet.

    Are you using a base volume container for the network mount(s)
    on the docker host systems? Or mounting on the host?
    --
    Michael J. Ryan (tracker1)
    +o roughneckbbs.com
    ---
    ■ Synchronet ■ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From deon@1:103/705 to Tracker1 on Thu Jan 28 22:04:36 2021
    Re: Re: NodeX to Node/X directories
    By: Tracker1 to deon on Wed Jan 27 2021 04:25 pm

    Just curious, what FS sharing are you using? And have you had
    issues with multi-node DOSemu doors... I haven't even started
    setting up any doors yet.

    Are you using a base volume container for the network mount(s)
    on the docker host systems? Or mounting on the host?

    I'm using scale, where its a visible filesystem on the host (all hosts), with each running continer effectively a directory, eg: /scale/docker/sbbs.

    I've also used portworx (a while ago), where each container gets a volume as its starts - but I stopped using it because it was kinda buggy (and I kept having to fsck the volumes - which was a challenge). I also lost some data - it didnt handle nodes going offline very well (and it's supposed to).

    On the Pi's I've used gluster, in fact I was using gluster on the Intel server as well, but it kept core dumping - on the Pi its a lot more reliable, although it doesnt do the I/O. I keep hearing that gluster is dead now but I dont think its actually true.

    For dosemu, I havent seen any issues with multinode, but then Ive only tried multinode on a couple of doors. I only just recently set it up, and the new work that's been commited recently has made it super easy. (Kudos to Rob and Mike(?) I think who's worked on that.)

    ...����

    ... A fool must now and then be right by chance.

    ---
    � Synchronet � Alterant | an SBBS in Docker on Pi!
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Michael J. Ryan@1:103/705 to GitLab issue in main/sbbs on Mon Feb 1 15:26:39 2021
    close https://gitlab.synchro.net/main/sbbs/-/issues/199
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to deon on Thu Feb 4 06:16:31 2021
    On 1/28/2021 4:04 AM, deon wrote:
    Just curious, what FS sharing are you using? And have you had
    issues with multi-node DOSemu doors... I haven't even started
    setting up any doors yet.

    Are you using a base volume container for the network mount(s)
    on the docker host systems? Or mounting on the host?

    I'm using scale, where its a visible filesystem on the host (all
    hosts), with each running continer effectively a directory,
    eg: /scale/docker/sbbs.

    I've also used portworx (a while ago), where each container gets
    a volume as its starts - but I stopped using it because it was
    kinda buggy (and I kept having to fsck the volumes - which was
    a challenge). I also lost some data - it didnt handle nodes
    going offline very well (and it's supposed to).

    On the Pi's I've used gluster, in fact I was using gluster on
    the Intel server as well, but it kept core dumping - on the Pi
    its a lot more reliable, although it doesnt do the I/O. I keep
    hearing that gluster is dead now but I dont think its actually
    true.

    Gotcha... I'm just using a single host with host volumes. Mostly
    using Docker to ease deployments/movement/backup etc... I was able to completely switch hosts/environments a couple times without issue.

    I'm also going to be fronting a website outside/ahead of the BBS host itself... so that will work slightly differently.

    For dosemu, I havent seen any issues with multinode, but then Ive
    only tried multinode on a couple of doors. I only just recently
    set it up, and the new work that's been commited recently has made
    it super easy. (Kudos to Rob and Mike(?) I think who's worked on
    that.)

    Yeah, haven't tried setting up any doors yet at all, though it's on my
    list of things to do... Web messages, chat/telegram and IRC are higher
    on my list though.

    As is getting my old mods (last updated around 2004 mostly) updated and running on a current version.
    --
    Michael J. Ryan (tracker1)
    +o roughneckbbs.com
    ---
    ■ Synchronet ■ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.12-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From deon@1:103/705 to Tracker1 on Fri Feb 5 08:46:24 2021
    Re: Re: NodeX to Node/X directories
    By: Tracker1 to deon on Thu Feb 04 2021 06:16 am

    Gotcha... I'm just using a single host with host volumes. Mostly
    using Docker to ease deployments/movement/backup etc... I was able to completely switch hosts/environments a couple times without issue.

    Yup, Ive done the same over the years.

    I now run everything in a 3 host swarm - which is great, because I can take 1 out of the loop, update it or generally do stuff to it, and the containers float to another host. (I do nothing to them specifically.) Swarm take care of which host to load the container and the networking. (Hence the cross host filesystem so that the other host sees the containers data.)

    When I'm finished, I make the host available again, and as containers are restarted they start on the newly up'ed host. The additional instances of replicated containers restart to, and the network takes care of giving them work.

    ...����

    ... Superior ability breeds superior ambition. Spock, stardate 3141.9.

    ---
    � Synchronet � Alterant | an SBBS in Docker on Pi!
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Tracker1@1:103/705 to deon on Sun Feb 21 02:28:12 2021
    FYI, if you're connecting to Doorparty, the dpc2 connector is
    now being published on Docker Hub for easier use.

    https://hub.docker.com/repository/docker/bbsio/doorparty/

    I also have Synchronet going in, but haven't setup daily builds.
    --
    Michael J. Ryan (tracker1)
    +o roughneckbbs.com
    ---
    ■ Synchronet ■ Roughneck BBS - roughneckbbs.com
    --- SBBSecho 3.13-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)