From Fedora Project Wiki
(update for current setup)
(update info)
Line 1: Line 1:
= arm-qa machines =
= arm-qa machines =


There are currently 4 SOC's (System On Chip) setup as arm QA machines in one of the calxeda chassis maintained by Fedora Infrastructure.  
There are currently 3 SOC's (System On Chip) setup as arm QA machines in one of the calxeda chassis maintained by Fedora Infrastructure.  


These instances have 4GB of memory, and 300GB drives.
These instances have 4GB of memory, and 300GB drives.
Line 14: Line 14:
arm03-qa00.cloud.fedoraproject.org
arm03-qa00.cloud.fedoraproject.org


arm03-qa01.cloud.fedoraproject.org
arm03-qa01.cloud.fedoraproject.org (down as of 2014-05-09 with disk issues)


arm03-qa02.cloud.fedoraproject.org
arm03-qa02.cloud.fedoraproject.org


arm03-qa03.cloud.fedoraproject.org
Currently all 3 are armv7hfp and running fedora 20.
 
Currently all 4 are armv7hfp and running fedora 20.


== access ==
== access ==

Revision as of 16:03, 9 May 2014

arm-qa machines

There are currently 3 SOC's (System On Chip) setup as arm QA machines in one of the calxeda chassis maintained by Fedora Infrastructure.

These instances have 4GB of memory, and 300GB drives.

These machines are useable for testing packages, building test fixes, etc

Access to these machines is controlled by the 'qa' fas group. All members of that group have ssh access to the arm machines.

Currently The machines are:

arm03-qa00.cloud.fedoraproject.org

arm03-qa01.cloud.fedoraproject.org (down as of 2014-05-09 with disk issues)

arm03-qa02.cloud.fedoraproject.org

Currently all 3 are armv7hfp and running fedora 20.

access

In order to access the machines:

  • Ensure you have been added to the qa fas group.
  • Ensure you have uploaded a ssh public key to fas.
  • ssh to the machine you wish to access.

sudo

All accounts with access to the machine can use sudo. Follow these steps:

  • Login to the arm machine
  • run 'newgrp qa' (this is to work around bug 750361)
  • run your sudo command

Contact

In the event you need a machine rebooted or reinstalled, please ask in #fedora-admin or #fedora-noc or file a infrastructure ticket.