Closed adiroiban closed 2 years ago
A gitter / matrix bride was setup between Libera #twisted
channel and Gitter https://gitter.im/twisted/twisted
so we kind of have logs for the IRC channel via this bridge
I think that by this time, we need to trigger plan B.
Try to migrate as much as possible from the current machine (which I think it's a 2xCPU bare metal beast) to a new cloud VM with virtual CPUs :)
So... Plan B is Azure as it should be the most probable VM hosting from which we can get some hosting sponsorhip.
Rackspace is out of question as twisted leadership team is active ...so we can't do much for now.
DigitalOcean / Vultr are nice, but setting up billing is complicated...so I think that is OK to go with Azure.
The long term plan is to remove the VM and migrate everything to GitHub / Read The Docs
Thanks @adiroiban ! We can restore other services as time allows. I pinged on IRC but since you may not be there, I'm just wondering if my SSH key is supposed to be on the new host? I tried to ssh in but I couldn't do so as either glyph@ or root@.
I tried to ssh in but I couldn't do so as either glyph@ or root@.
ssh azureuser@twisted-vm.centralus.cloudapp.azure.com
It's in the description 😃
@glyph have you tried ssh azureuser@twisted-vm.centralus.cloudapp.azure.com
?
I have copied the 5 SSH keys that I found on dornkirk
It doesn't work. I could ssh to dornkirk just fine, so perhaps they were corrupted by the addition of some whitespace.
You can grab current SSH keys for me here: https://github.com/glyph.keys
I have updated the SSH keys from GitHub.
There were no whitespaces in the previous keys.
Try now.
Works now.
We are still doing the dornkirk migration as not all the services were migrate.
With the current resources, I think that our only hope to success is go serverless and use as many SaaS service as possible for the infrastructure.
This mean that the whole twisted-infra org should be close/deprecated as we will no longer need to care about the infrastructure.
We will just used other people infrastructure.
We have already started this process, with the git source code hosting with GitHub, and now with the mailinglist.
We are also using Read the Docs to host our documentation.
I guess that moving from Trac Ticket to GitHub Issues is the next big move.
And then look at using GitHub Pages or Netlify to host all our web presentation pages/blog.
So, with that in mind, I will try to create all the "infra" related issues inside repos hosted by https://github.com/twisted
We can still keep this org and repos for historical reasons.
With the current resources, I think that our only hope to success is go serverless and use as many SaaS service as possible for the infrastructure.
Don't we still need a place to keep the SaaS configuration? If we just move from manual configuration on a single host to manual configuration with random bespoke logins on various services it doesn't seem like much of an improvement in terms of administrative overhead.
The SaaS configuration should be kept in the repo source code.
This is what we are already doing for twisted/twisted
The documentation configuration is stored at https://github.com/twisted/twisted/blob/trunk/.readthedocs.yml
The buildbot replacement is stored at https://github.com/twisted/twisted/tree/trunk/.github/workflows and https://github.com/twisted/twisted/tree/trunk/azure-pipelines
And for Github pages or Netlify you have similar stories. The configuration and content is stored in the same repo.
But we should try to use as fewer logins as possible... that is, try to build everything around GitHub infra.
I know that in theory it sound like a terrible idea, but with the limited resources, I think its our only hope to move forward.
And we should have a little configuration as possible :)
And regarding the Azure VM. I have only did the migration as plan B. Since the migration, I have only checked the VM once to enable backup snapshots and since they I have not checked it again. I have not checked to see that the backups really work and I don't know if anyone else had checked this.
I think that this can be closed.
We plan to turn off the VM by the end of this year... without any plans to add more services to the VM.
Codespeed can be implemented in a server-less / container environment.
some legacy mailing list archive were migrated here https://twisted.org/pipermail/ and hosted via GitHub Pages
the full archive is stored on Azure Blob
This is a todo list of things that needs to be done to migrate Dornkirk
Changes for braid are at https://github.com/twisted-infra/braid/pull/279
To access the new VM
Backup at https://twistedbackup.blob.core.windows.net/dornkirk
General tasks
Backup
t-names DNS tasks
Mailing list
bb-master Buildbot
Trac
t-web
amptrac
codespeed
diffresource
Will be decommissioned
highscore
kenaan - IRC / Gitter / Matrix