Test Machine Resources For Package Maintainers

From FedoraProject

Revision as of 20:02, 10 September 2017 by Kevin (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Contents

Overview

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.

Available Machines/Instances

hostname fedora version arch cpu memory disk contact
rawhide-test.fedorainfracloud.org rawhide x86_64 cloud instance 3.466Ghz 4GB ram 40GB disk admin@fedoraproject.org
f27-test.fedorainfracloud.org f27 x86_64 cloud instance 3.466Ghz 4GB ram 40GB disk admin@fedoraproject.org
f26-test.fedorainfracloud.org f26 x86_64 cloud instance 3.466Ghz 4GB ram 40GB disk admin@fedoraproject.org
f25-test.fedorainfracloud.org f25 x86_64 cloud instance 3.466Ghz 4GB ram 40GB disk admin@fedoraproject.org
el7-test.fedorainfracloud.org centos7 x86_64 cloud instance 3.466Ghz 4GB ram 40GB disk admin@fedoraproject.org
el6-test.fedorainfracloud.org centos6 x86_64 cloud instance 3.466Ghz 4GB ram 40GB disk admin@fedoraproject.org
ppc64-test.fedorainfracloud.org f25 ppc64 cloud instance 3.425Ghz 4GB ram 40GB disk admin@fedoraproject.org
ppc64le-test.fedorainfracloud.org f25 ppc64le cloud instance 3.425Ghz 4GB ram 40GB disk admin@fedoraproject.org
arm03-packager00.cloud.fedoraproject.org f25 armv7 SOC - 4GB ram 300GB disk admin@fedoraproject.org
arm03-packager01.cloud.fedoraproject.org f25 armv7 SOC - 4GB ram 300GB disk admin@fedoraproject.org
arm03-qa00.cloud.fedoraproject.org f25 armv7 SOC - 4GB ram 300GB disk admin@fedoraproject.org
arm03-qa01.cloud.fedoraproject.org f25 armv7 SOC - 4GB ram 300GB disk admin@fedoraproject.org
Note.png
machine names and location has changed as of 2017-02-27

FAQ

Q: What precautions should I take on these machines.

A: Since all Fedora packagers or qa members have root access on these machines, do not enter any sensitive information, including FAS credentials on these machines. These systems should never ask you for your FAS password (sudo is NOPASSWD). Authentication is only done via the SSH key you have set in FAS. In particular, it is recommended to disable SSH agent forwarding on these machines on the client side (agent forwarding is disabled on the server, but any user on the system could potentially reenable it). To do this, add the following to your ~/.ssh/config:

Host *.fedorainfracloud.org
  ForwardAgent no

Q: Who has access to these instances?

A: Anyone who is in the Fedora "packager" group. or anyone in the Fedora "qa" group for the qa machines. 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 git 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 messed up one of the existing instances. What do I do?

A: Don't panic. Just inform the owner of that instance and they will spin up another instance. It's not a problem.

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 (kevin@scrye.com) for more info on how to set up the hosts. If you want to know some details about the setup, take a look at the ansible playbooks used for these machines at https://www.scrye.com/~kevin/fedora/scrye-ansible/. To make them work you need a special FAS account that is in the group thirdparty, though.

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 (kevin@scrye.com) and we can see if we can work something out.

Q: What should the ssh host keys be for these instances?

A1: https://admin.fedoraproject.org/ssh_known_hosts has all the ssh host keys

IPV6 info

Sadly, ipv6 isn't currently available due to a provider issue. Will get it enabled as soon as we can offer it.