(architecture) Migrate to a new server architecture. #11
Labels
No labels
Kind
Down
Kind/Maintenance
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No milestone
No project
No assignees
1 participant
Notifications
Total time spent: 1 day
Due date
strix
1 day
Dependencies
No dependencies set.
Reference: ixvd/hub#11
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
We're leaving behind our dedicated server and moving to multiple hetzner cloud instances.
For some status updates, look at:
https://boards.ixvd.net/b/e4kbqe2vTP4HeYH6s/neb-migration
What does this mean for you?
nothing.
We're only moving our services to other servers, not removing any essential services.
Will there be any downtime?
Probably, and probably a lot of it.
We're trying to keep it minimal but since our budget is not massive it's going to hit some obstacles that will break things.
How long will it take?
This migration will take approximately a week.
This includes the planning, designing and the actual migration of services.
What will be migrated first?
First of all, internally the backup tools will be migrated to work distributed.
Then we will start with the most used services; git, the status page and the homepage.
Will everything stay the same after the migration?
No. We're first trying to make everything work on different servers and then we're going to redesign things like the HTTP reverse proxy.
Minecraft servers are going to be removed due to inactivity.
after this migration
ixvd/neongwill be deprecated and will likely be replaced with a new ansible compatible toollingnew tooling available in
ixvd/neb.The new infrastructure will also use a new backup tool, restic, to save on disk space!
Generated keys for servers and enrolled them into the
automationuser.backups are tested and are working!
I might change the restic backups to first backup locally and then cron-omatically rsync them to the storagebox
Status of migration:
Scripts and tooling are almost done.
Migration for services to servers are not done, that's still pending.
I've added a due date for when I'm cancelling the current server.
I'm doing service migration tomorrow 😪💤
Nginx config has now been implemented!
I still have to migrate all services 😢
ntfy and gatus have been migrated 🥳
taking a lil' break :P
4 stacks to go, i'll do this tomorrow evening i think
kid's server files have been pushed
services have been migrated over.
Hope when we go live everything works 🤞
might push back the cancellation a couple of days since all services have been migrated!
next server to be deployed should be
apoc, so we can still use GIT.apoc is migrated!!!
wekan seems to be broken but that's okay
Not done yet, but all servers are live and all DNS points to them
everything seems to be working, adding my final piece of time and closing