doc/en_US.ISO8859-1/htdocs/internal/machines.xml
2014-08-23 01:33:13 +00:00

324 lines
6.9 KiB
XML

<?xml version="1.0" encoding="iso-8859-1"?>
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN"
"http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY title "The FreeBSD.org Network">
]>
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<title>&title;</title>
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
</head>
<body class="navinclude.docs">
<p>This page documents, for those with accounts on the
FreeBSD.org network, just what machine resources are currently
available and the sorts of jobs they are being provided for.</p>
<p>For a list of SSH host keys and their fingerprints for the
public FreeBSD.org machines, please see <a href="ssh-keys.asc">
this file</a>.</p>
<h2>Developer FreeBSD.org hosts</h2>
<p>These systems are available for FreeBSD developer / committer use.
Reference systems can be used for build tests etc.</p>
<table class="tblbasic">
<thead>
<tr>
<th align="left">Host</th>
<th align="left">OS</th>
<th align="left">Type</th>
<th align="left">Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>eris</td>
<td>10-STABLE</td>
<td>ia64</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>flame</td>
<td>10-STABLE</td>
<td>sparc64</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>freefall</td>
<td>11-CURRENT</td>
<td>amd64</td>
<td>Shell Logins.</td>
</tr>
<tr>
<td>pluto</td>
<td>10-STABLE</td>
<td>ia64</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>ref8-amd64</td>
<td>8-STABLE</td>
<td>amd64</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>ref9-amd64</td>
<td>9-STABLE</td>
<td>amd64</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>ref10-amd64</td>
<td>10-STABLE</td>
<td>amd64</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>ref10-i386</td>
<td>10-STABLE</td>
<td>i386</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>ref11-amd64</td>
<td>11-CURRENT</td>
<td>amd64</td>
<td>Reference machine.</td>
</tr>
<tr>
<td>ref11-i386</td>
<td>11-CURRENT</td>
<td>i386</td>
<td>Reference machine.</td>
</tr>
</tbody>
</table>
<h2>Administrative FreeBSD.org hosts</h2>
<p>These systems perform various administrative services. Most have
restricted access.</p>
<table class="tblbasic">
<thead>
<tr>
<th align="left">Host</th>
<th align="left">Purpose</th>
</tr>
</thead>
<tbody>
<tr>
<td>ftp-master</td>
<td>FTP Master (stage server).</td>
</tr>
<tr>
<td>hub</td>
<td>Mailing Lists and Mail services.</td>
</tr>
<tr>
<td>mx1</td>
<td>Inbound Mail services.</td>
</tr>
<tr>
<td>mx2</td>
<td>Outbound Mail services.</td>
</tr>
<tr>
<td>ns0</td>
<td>A FreeBSD.org authoritative DNS Server.</td>
</tr>
<tr>
<td>ns1, ns2</td>
<td>FreeBSD.org recursive DNS Server.</td>
</tr>
<tr>
<td>skunkworks</td>
<td>Perforce server.</td>
</tr>
<tr>
<td>svn</td>
<td>Subversion master repository.</td>
</tr>
<tr>
<td>www</td>
<td>The www.FreeBSD.org Webserver.</td>
</tr>
</tbody>
</table>
<h2>Ports building cluster</h2>
<p>The ports building cluster is primarily managed by the Ports
Management team (portmgr).</p>
<table class="tblbasic">
<thead>
<tr>
<th align="left">Host</th>
<th align="left">OS</th>
<th align="left">Purpose</th>
</tr>
</thead>
<tbody>
<tr valign="top">
<td>beefy<em>[1-4]</em></td>
<td>Intel EM64T MP</td>
<td>iXsystems iX1204, 2xIntel Xeon X5675 (6x2x3.07GHz), 96GB Memory,
4x300Gb SAS disks, Intel PRO/1000 NIC.</td>
</tr>
</tbody>
</table>
<h2>Hardware configurations</h2>
<table class="tblbasic">
<thead>
<tr>
<th align="left">Host</th>
<th align="left">Type</th>
<th align="left">Hardware</th>
</tr>
</thead>
<tbody>
<tr valign="top">
<td>flame</td>
<td>Sun SPARC</td>
<td>Sun Fire V120, UltraSparc-IIe 648MHz, 2GB Memory, sym SCSI controller,
2x 36G SCSI-3 disk, 2x Sun ERI 10/100 Ethernet.</td>
</tr>
<tr valign="top">
<td>freefall</td>
<td>Intel EM64T MP</td>
<td>HP Proliant DL160 G6, 2xIntel Xeon X5650 (6x2x2.67GHz), 24GB Memory,
4x1TB SATA disks, Intel PRO/1000 NIC.</td>
</tr>
<tr valign="top">
<td>ftp-master</td>
<td>Intel EM64T MP</td>
<td>HP Proliant DL160 G6, 2xIntel Xeon X5650 (6x2x2.67GHz), 24GB Memory,
4x1TB SATA disks, Intel PRO/1000 NIC.</td>
</tr>
<tr valign="top">
<td>hub</td>
<td>Intel EM64T MP</td>
<td>HP Proliant DL160 G6, 2xIntel Xeon X5650 (6x2x2.67GHz), 48GB Memory,
4x1TB SATA disks, Intel PRO/1000 NIC.</td>
</tr>
<tr valign="top">
<td>mx1, mx2</td>
<td>AMD64</td>
<td>PowerEdge R415, 2xAMD Opteron 4180 (2x6x2.6GHz), 16GB Memory,
Dell PERC H700 RAID controller, 3x300GB SAS disks in XFS mirror,
QLogic NetXtreme II Gigabit Ethernet adapter.</td>
</tr>
<tr valign="top">
<td>ns0, ns1, ns2</td>
<td>Intel x86</td>
<td>2.8GHz Xeon, 1GB Memory, Compaq Smart Array 5i RAID controller,
2x34GB SCSI Disks in RAID1, Broadcom Gigabit Ethernet.</td>
</tr>
<tr valign="top">
<td>pluto</td>
<td>IA-64 MP</td>
<td>2x900MHz Itanium2 (McKinley) - HP zx1 (pluto) chipset,
2GB Memory, LSILogic 1030 U320 SCSI controller (mpt),
1x36GB 10K RPM U160 SCSI drive, Broadcom BCM5701 Gigabit NIC.</td>
</tr>
<tr valign="top">
<td>ref<em>[8-11]</em>-amd64</td>
<td>Intel EM64T MP</td>
<td>HP Proliant DL160 G6, 2xIntel Xeon X5650 (6x2x2.67GHz), 24GB Memory,
4x1TB SATA disks, Intel PRO/1000 NIC.</td>
</tr>
<tr valign="top">
<td>ref10-i386</td>
<td>Intel EM64T MP</td>
<td>Dell PowerEdge 2950, 2xIntel Xeon L5320 (4x1.86GHz), 8/16GB Memory,
PERC 5/i RAID controller, 6x136GB SAS disks, Broadcom NetXtreme II
BCM5708 NIC.</td>
</tr>
<tr valign="top">
<td>ref11-i386</td>
<td>Intel EM64T MP</td>
<td>Dell PowerEdge 2950, 2xIntel Xeon E5320 (4x1.86GHz), 32GB Memory, PERC 5/i RAID
controller,6x136GB SAS disks, Broadcom NetXtreme II BCM5708
NIC.</td>
</tr>
<tr valign="top">
<td>www</td>
<td>Intel x86</td>
<td>2x dual-core 2.80GHz Xeon, 1.5GB Memory, Compaq Smart Array 5i RAID controller,
2x34GB SCSI Disks in RAID1, 2x Broadcom Gigabit Ethernet NIC.</td>
</tr>
</tbody>
</table>
<p>Machines are generally connected at 1Gbit/sec full-duplex to a dedicated
switch with redundant gigabit uplinks. Internet connectivity
and colocation is provided by <a href="http://www.yahoo.com/">Yahoo!</a>.
All systems have logged serial consoles and remote power management.</p>
<h2>Administrative Policies</h2>
<p>If the machine in question is "owned" by someone specific, please
direct queries to them first when asking about administrative issues,
this includes changes to user accounts or filesystem layout.</p>
<p>All new user accounts must be cleared with the admin staff,
and are given
only to FreeBSD developers, either in the docs, ports or general
src hacking category. Accounts may be given to non-project developers
if they have a specific need to test something of a truly experimental
nature and need access to a FreeBSD machine for the purpose. See
<a href="new-account.html">New Account Creation Procedure page</a> for
details on new accounts. Accounts
are not given to the general public for "vanity domain" mail or
other such uses. It would be a waste of time to ask. Thanks.</p>
<p></p><a href="internal.html">FreeBSD Internal Home</a>
</body>
</html>