Test Machine Resources For Package Maintainers
In some cases Fedora Package maintainers may not have access to all supported architectures or releases of Fedora that they maintain packages for. In order to assist with this, some community members are providing access to test machines/instances that they maintain to allow Fedora package maintainers to test, build, compile or debug their packages.
DNS NAME | fedora version | arch | cpu | memory | disk | contact
- mavra.scrye.com - rawhide - ppc32 - G4 466Mhz - 768MB ram - 30GB disk - firstname.lastname@example.org
- thulsadoom.scrye.com / f12-test.scrye.com - rawhide - x86_64 kvm instance - 1.86Mhz - 2GB ram - 60GB disk - email@example.com
- revan.scrye.com / f11-test.scrye.com - f11 - x86_64 kvm instance - 1.86Mhz - 1024MB ram - 12GB disk - firstname.lastname@example.org
- lucius.scrye.com / f10-test.scrye.com - f10 - x86_64 kvm instance - 1.86Mhz - 512MB ram - 10GB disk - email@example.com
- narcissa.scrye.com / f9-test.scrye.com - f9 - x86_64 kvm instance - 1.86Mhz - 512MB ram - 10GB disk - firstname.lastname@example.org
- draco.scrye.com / epel5-test.scrye.com - centos5 - i686 kvm instance - 1.86Mhz - 2GB ram - 100GB disk - email@example.com
Q: Who has access to these instances?
A: Anyone who is in the Fedora "packager" group. Use your ssh key from the fedora account system to login. Package maintainers have 'sudo' access.
Q: What kinds of things can I do on these machines?
A: Any of the following:
- mock build packages
- install and test packages
- build packages locally to try and fix problems or compile errors
- Check locations of files, layout or versions to help solve a Fedora bug.
- Basically anything that is directly related to Fedora Maintainer tasks.
Q: What should I not do?
A: Any of the following:
- Things that are not related to your job as maintainer of Fedora packages.
- Probing or accessing any other system.
- publishing data or content to the internet.
Q: Can I upgrade/downgrade $basepackage, or reboot the instances?
A: If you need to do this, please contact the maintainer of the instance and arrange it.
Q: Can I leave any data on these instances?
A: No. They could be re-installed at most any time, or rebooted, or suffer a data loss. Please scp or rsync your work off often, and when done, please revert any package installs/downgrades/upgrades.
Q: Aren't you worried that someone will misuse these instances?
A: No. We trust the packagers to maintain and build our packages in Fedora, why would we not trust them to use test instances correctly? Additionally, the instances are all isolated from any local machines, ssh agent forwarding is disabled, and they only allow incoming ssh and a handfull of outgoing traffic.
Q: Can I use one of these instances to maintain my packages from?
A: No. ssh agent forwarding is disabled for security reasons, so you will not be able to do cvs checkins from these instances. Additionally, they could be re-installed or files could be wiped at any time. You should not use these as a place to maintain your packages from.
Q: I would like to contibute a host/instance/machine to allow people to test things, how can I do that?
A: I would be happy to help you in setting up a machine as the above test instances are. Contact me (firstname.lastname@example.org) for more info on how to set up the hosts.
Q: I would like to donate some secondary arch hardware/machine resources to this effort. How can I do that?
A: See the previous question if you just want to bring up your own test machines at your site. If you would like me to host/manage your machines, please contact me (email@example.com) and we can see if we can work something out. In particular I would love a ppc64 host to allow maintainers to use.