From Fedora Project Wiki
(→‎arm-qa machines: update for freshly installed f19 nodes)
m (both machines are running f21, not f20)
 
(3 intermediate revisions by one other user not shown)
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 2 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 7: Line 7:
These machines are useable for testing packages, building test fixes, etc
These machines are useable for testing packages, building test fixes, etc


Access to these machines is controlled by the 'arm-qa' fas group.
Access to these machines is controlled by the 'qa' fas group.
All members of that group have ssh access to bastion-comm01.fedoraproject.org
All members of that group have ssh access to the arm machines.  
and from there to the arm machines.  


Currently The machines are:  
Currently The machines are:  


arm03-qa00.arm.fedoraproject.org
arm03-qa00.cloud.fedoraproject.org


arm03-qa01.arm.fedoraproject.org
arm03-qa01.cloud.fedoraproject.org


arm03-qa02.arm.fedoraproject.org
Currently both are armv7hfp and running fedora 21.
 
arm03-qa03.arm.fedoraproject.org
 
Currently all 4 are armv7hfp, qa00 and qa01 are fedora 19 while qa02 and qa03 are fedora 18.  


== access ==
== access ==
Line 27: Line 22:
In order to access the machines:  
In order to access the machines:  


* Ensure you have been added to the arm-qa fas group.  
* Ensure you have been added to the qa fas group.  


* Ensure you have uploaded a ssh public key to fas.  
* Ensure you have uploaded a ssh public key to fas.  
* Add the following to your ~/.ssh/config file:
<p>
Host arm03-qa* arm03-qa*.arm.fedoraproject.org
  HostName %h
  ProxyCommand ssh -q yourfasid@bastion-comm01.fedoraproject.org /usr/bin/nc %h 22
</p>


* ssh to the machine you wish to access.  
* ssh to the machine you wish to access.  
Line 43: Line 30:
== sudo ==
== sudo ==


All accounts with access to the machine can use sudo. Follow these steps:
All accounts with access to the machine can use sudo.  
 
* Enroll a yubikey or googleauthenticator. see: https://fedoraproject.org/wiki/Infrastructure_Two_Factor_Auth
 
* Login to the arm machine
 
* run 'newgrp arm-qa' (this is to work around bug 750361)
 
* run your sudo command and enter your fas password and 2nd factor.  


== Contact ==
== Contact ==


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

Latest revision as of 15:48, 9 June 2015

arm-qa machines

There are currently 2 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

Currently both are armv7hfp and running fedora 21.

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.

Contact

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