New VM for meetbot
Please provide the specifications that you require:
A CX11 from Hetzner will do very nicely, this thing doesn't need anything much.
- Desired hostname: meetbot2.debian.net
- Public SSH key:
ssh-rsa AAAAB3NzaC1yc2EAAAABIwAAAQEApY3j8pYCpsN/PPZBU8mSdVBV7st3YNqxXp4eMVzkyKF0TwywG5A5Nj6hOquHFR/R19Kf0dfHSr2vLrjJXzH5efl+KGzGReo8rwm1vMZOrzK5lrWgzHlZTRF/CbZbQ1ov2UnCPZnmr+anH/KfJ0Easp751/neZ24oCbf7BOO2E4L8v72utsvEkXu0YRTaKqkZ+slDuDQdtisS6nH3ecnZy3JIy0NZEJFBnB0/Xz3v4Mci5kw5DCVU5jyIH/bUEYTBDQg5WH3Kuwb+SY/bwXgNmZDE4qVFCY73m6JcOWFKMWY3sBFiRRFdVHa32EdMQxdQpOns0uzG06OtGDQFlSuAlw==
Please provide details as applicable:
What will this instance be used for, who will be the target audience? meetbot.debian.net has to move, the host it is on goes away.
Who will maintain this service? Will it be team maintained? At a minimum, me, for root (plus .debian.net team, ay). Richard Darst usually runs the meetbot.
What will you use for backups?
back-what?
Will you be adding this service to https://wiki.debian.org/Services along with a service page under that name space? (this is not essential, but see this as a reminder to do so if appropriate for the service)
-
I agree to follow the Debian.net Rules
Check-list for Debian.Net Team
-
Select an appropriate platform for the request. -
Spin up a VM in the appropriate platform. -
Hetzner Only: Add IPv4 and IPv6 reverse-DNS entries. -
Add the Debian.Net Team's SSH keys to root's authorized_keys
. -
Set PasswordAuthentication no
insshd_config
, restartsshd
. -
Add an account for the requester adduser --disabled-password USER
. -
Grant sudo access to the requester adduser USER sudo
. -
Unset the user's password, so they can set it themselves: passwd -d USER
-
Add the requester's SSH keys to their account's authorized_keys
. -
Provide IPv4 and IPv6 addresses in a comment, so the requester can create DNS records. -
Add the instance to the infrastructure repo
Edited by Stefano Rivera