Migrate services from barnard.kosmos.org to VMs #259

New Issue

raucao · 2020-12-09T14:58:50Z

raucao commented

2020-12-09 14:58:50 +00:00

botka_freenode
hal8000
hal8000_xmpp
wormhole
kredits-github
kredits-ipfs-pinner (+ go-ipfs, basically ipfs-2 and/or -3)
Sockethub
LDAP

* [x] botka_freenode * [x] hal8000 * [x] hal8000_xmpp * [x] wormhole * [x] kredits-github * [x] kredits-ipfs-pinner (+ go-ipfs, basically `ipfs-2` and/or `-3`) * [x] Sockethub * [x] LDAP

raucao added the

ops

label 2020-12-09 14:58:50 +00:00

raucao commented

2020-12-09 15:30:23 +00:00

Update: VM nodejs-1 is running/prepared on 10.147.20.3.

Update: VM `nodejs-1` is running/prepared on `10.147.20.3`.

greg commented

2020-12-11 13:44:00 +00:00

I have added sockethub to the list of services in the issue

👍 1

greg referenced this issue from a commit

2020-12-11 17:57:02 +00:00

Add nodejs-1 client and node file Refs #259

greg referenced this issue

2020-12-11 18:01:42 +00:00

Add nodejs-1 client and node file #264

greg referenced this issue from a commit

2020-12-11 18:02:12 +00:00

Add nodejs-1 client and node file Refs #259

raucao commented

2020-12-17 13:12:30 +00:00

Found another one: kredits-github. :)

raucao commented

2020-12-17 13:14:38 +00:00

Also just happened on barnard, but we'll come across it (or not) automatically when moving dirsrv:

"FATAL: NoMethodError: dirsrv_instance[master] (kosmos-dirsrv::default line 29) had an error: NoMethodError: undefined method `root_directory' for Chef::Resource::Execute"

Also just happened on barnard, but we'll come across it (or not) automatically when moving dirsrv: > "FATAL: NoMethodError: dirsrv_instance[master] (kosmos-dirsrv::default line 29) had an error: NoMethodError: undefined method `root_directory' for Chef::Resource::Execute"

raucao commented

2021-01-04 16:31:13 +00:00

Just apt-updated nodejs-1, tried to reboot and now it won't boot up anymore, taking up full CPU resources while trying to do so. I have shut it off for now. No idea what's going on, because there's no console output.

Just apt-updated `nodejs-1`, tried to reboot and now it won't boot up anymore, taking up full CPU resources while trying to do so. I have shut it off for now. No idea what's going on, because there's no console output.

raucao commented

2021-01-05 10:28:27 +00:00

Created nodejs-2 with private IP 10.1.1.229 and deleted the broken VM. Then deployed kredits-github to it.

centaurus is running nginx on the host, so we cannot use HTTP/S forwarding with HAProxy, as we do on draco. It's possible to do this in Nginx nowadays (see here and here), but I didn't want to get into that right now, because we should discuss it first for that server, and we shouldn't do the exact same thing with 2 different programs IMO. So the traffic forwarding is done from draco to the VM on centaurus for now.

Created `nodejs-2` with private IP `10.1.1.229` and deleted the broken VM. Then deployed `kredits-github` to it. `centaurus` is running nginx on the host, so we cannot use HTTP/S forwarding with HAProxy, as we do on `draco`. It's possible to do this in Nginx nowadays (see [here](https://docs.nginx.com/nginx/admin-guide/load-balancer/tcp-udp-load-balancer/) and [here](https://nginx.org/en/docs/stream/ngx_stream_ssl_preread_module.html)), but I didn't want to get into that right now, because we should discuss it first for that server, and we shouldn't do the exact same thing with 2 different programs IMO. So the traffic forwarding is done from `draco` to the VM on `centaurus` for now.

raucao referenced this issue

2021-01-05 10:31:45 +00:00

Create new nodejs VM, move kredits-github to it #277

greg referenced this issue

2021-09-26 12:00:53 +00:00

Move LDAP server to new VM #227

raucao referenced this issue

2022-04-26 18:13:25 +00:00

Move dirsrv (LDAP) primary node to new VM #401

raucao referenced a pull request that will close this issue

2022-11-04 13:45:51 +00:00

Migrate hal8000 to new kredits and nodejs VM #445