Please create vps for hosting irc bots for #debian, botfleet.debian.net
Please provide the specifications that you require:
- CPU: single
- RAM: 2GB
- Disk space: 10GB
- Desired hostname: botfleet.debian.net
- Public SSH key: ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQDTC1v0PPrblxD1BN1mZBPLIdd4ROUP4/0CfZBxfM1ilGE/rJFgYu8iunOn36WYK/TbY8S54IlP6WUdL5v0EqbI8twag9DTClBTVCFpuYWo7bNL5FByWhW3opq/LtxU//g4YAT4+a7nMzEwDURbsGWdns8w26Ex7DE0p3BqmPCTcCP1R0o5eqeoP9prgPMohXxUFsXQuuczzi+E4uHBsBZ8q+56gE5ZFv3beD+crQthzaD5Up8Mmlzp98jW5yhrLr9kpNm0qQViO0lPq2qMTY5VWlfhA2OniCi8+PtzD5r9JADYOPlBVZ3or/hFuTsSbxVlfDTNUQrv2tCAQqV90DRh stuart@debian.org
Please provide details as applicable:
What will this instance be used for, who will be the target audience?
Hosting IRC bots that look after #debian, #debian-next and other user-facing channels.
- Hosting debchange, the bot that deals with moderation in #debian, #debian-next, ... on OFTC and libera.chat
- Hosting dselect, a backup for the factoid bot (same channels)
- (Potentially) Hosting judd, a window to the UDD, that provides package and bug details (same channels). This one is dependent on testing whether using the udd mirror is sufficiently fast for the bots purposes when colocated with the mirror, which would allow us to drop hosting our own UDD mirror as we currently do for the bot.
IRC is still one of our main help conduits to helping users and the bots provide important services to both the regulars offering help and those seeking help. These three bots are
For the purposes of hosting this machine as close as possible to the udd mirror, its config might be relevant: https://salsa.debian.org/debian.net-team/infra/-/blob/master/vms/udd-mirror.debian.net.yml
Who will maintain this service? Will it be team maintained?
- stuart
- others TBA; moving these onto project-hosted infrastructure is part of plan to reduce this single point of failure
What will you use for backups?
rsync
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)
Yes
-
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