os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add clusteradm report

Browse source
This commit is contained in:
Benjamin Kaduk 2015-10-16 02:49:33 +00:00
parent 4d4bb579b1
commit 602ed5461e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=47587
1 changed files with 79 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

79
en_US.ISO8859-1/htdocs/news/status/report-2015-07-2015-09.xml
View file

@ -1601,4 +1601,83 @@
</help>
</project>
<project cat='team'>
<title>&os; Cluster Administration Team</title>
<contact>
<person>
<name>&os; Cluster Administration Team</name>
<!-- email intentionally left incomplete -->
<email>clusteradm@</email>
</person>
</contact>
<body>
<p>The &os; Cluster Administration Team consists of the people
responsible for administering the machines that the project
relies on for its distributed work and communications to be
synchronised.</p>
<p>Our primary cluster has been hosted as a guest in California
for many years. Our ongoing project is relocating the core
functionality to a location in New Jersey with a formal
hosting arrangement. This is an equipment refresh,
consolidation for better use of resources, and for better
continuity of service.</p>
<p>There is a significant amount of behind-the-scenes work to
make this happen. The original cluster was implemented with
a common, shared, assumed-to-be secure network with
ubiquitous NFS everywhere. This structure does not lend
itself well to being distributed across geographically
diverse locations, particularly when Internet transit is
required. The bulk of the work is rebuilding services to be
portable, stand-alone components that do not depend on
shared-network access and are safe enough to use across the
insecure Internet.</p>
<p>Highlights this quarter:</p>
<ul>
<li>Many internal distribution systems switched from rsync to
a distribution mesh using &quot;syncthing&quot;.</li>
<li>We have implemented more code/data signing infrastructure
with out-of-band verification.</li>
<li>New 32-core reference build hosts are online.</li>
<li>Internal admbugs switched from bugzilla 4.4 to 5.0 and
packages were made available for the bugmeister team.</li>
<li>Finally switched from varnish3 to varnish4.</li>
<li>We exorcised hub.FreeBSD.org, the last survivor of the
2012 security incident.</li>
<li>vuxml and the legacy portaudit build system were converted to
components and integrated.</li>
<li>https://download.FreeBSD.org/ is nearing completion (please
do not use until officially announced).</li>
<li>A Taiwan node was brought into service for pkg, ftp,
svn, and vuxml mirroring.</li>
<li>One of the freebsd-update mirrors was converted from
lighttpd to nginx due to a data corruption bug.</li>
<li>Completed detachment of the svn repository from the old
cluster and moved it to its new location.</li>
</ul>
<p>Ongoing:</p>
<ul>
<li>The cluster runs a mixture of 11-current and 10-stable
as part of our &quot;eat our own dogfood&quot; project. For this
to be useful we do monthly cluster refreshes to keep up with
current code.</li>
<li>We build internal base system snapshots every few days
and packages every day.</li>
<li>We also provide support for non-clusteradm-operated
services including jenkins, reviews, portsnap,
freebsd-update, bugzilla, package builders, git, and mercurial.
This varies from as little as maintaining SSL front-ends
through operating servers, distributing data or building
packages/binaries to run.</li>
</ul>
</body>
</project>
</report>