Feature #3080
Feature #3076: migrate to new (2018-03) server "host2.osmocom.org"
migrate nginx dispatcher to new server
Start date:
03/19/2018
Due date:
% Done:
90%
Spec Reference:
Description
This is likely the last step after everything else has been migrated.
History
#1 Updated by laforge over 1 year ago
- Priority changed from Normal to Low
#2 Updated by laforge over 1 year ago
- Status changed from New to Stalled
I would say it's mostly done. Was surprisingly easy.
What's pending is of course to change the "upstream" locations as we migrate more services to docker-compose on the new machine.
#3 Updated by laforge about 1 year ago
- Status changed from Stalled to In Progress
- % Done changed from 0 to 40
we're running a dispatcher now on the new matchine, handing off requests in to the docker containers. not-yet-migrated services are handed off to the old machine.
The dispatcher on the old machine is doign the inverse:- hand-off migrated services to the new machine
- hand-off to internal jails for not-yet-migrated services
This means we should be able to switch the DNS records at some point without any interruption.
#4 Updated by laforge about 1 year ago
- Status changed from In Progress to Stalled
- Assignee set to laforge
- % Done changed from 40 to 90
this is rather complete. DNS zones has been updated.
cgit CNAME host2 git CNAME host2 jenkins CNAME host2 registry CNAME host2 www CNAME host2 live CNAME host2 security CNAME host2 simtrace CNAME host2 sdr CNAME host2 cos CNAME host2 op25 CNAME host2 projects CNAME host2 bb CNAME host2 baseband CNAME host2 gmr CNAME host2 qc CNAME host2 openbsc CNAME host2 tetra CNAME host2 patchwork CNAME host2 gerrit CNAME host2
Only critical domain names remain on old machine for now:
- ftp.osmocom.org (ftp, not just http)
- lists.osmocom.org (smtp/mailman side, not just http)
- dect.osmocom.org (it's own entire universe)
