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

Add initial clusteradm charter.

Browse source 
Approved by:	core
This commit is contained in:
Peter Wemm 2013-04-19 21:50:39 +00:00
parent ebf6664e8b
commit 1c25ec5f76
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41462
3 changed files with 113 additions and 3 deletions
en_US.ISO8859-1/htdocs
administration.xml
internal
Makefileclusteradm.xml

10
en_US.ISO8859-1/htdocs/administration.xml
View file

@ -357,14 +357,18 @@
<h3><a name="t-clusteradm">Cluster Administrators</a> <h3><a name="t-clusteradm">Cluster Administrators</a>
<!-- admins mail aliases intentionally left incomplete --> <!-- admins mail aliases intentionally left incomplete -->
&lt;clusteradm@&gt;</h3> &lt;admins@&gt;</h3>
<p>The Cluster Administrators consists of the people responsible for <p>The Cluster Administrators consists of the people responsible for
administrating the machines that the project relies on for its administrating the machines that the project relies on for its
distributed work and communication to be synchronised. It distributed work and communication to be synchronised. It
consists mainly of those people who have physical access to the servers. consists mainly of those people who have physical access to the servers.
Issues concerning the projects infrastructure or setting up new Issues concerning the projects infrastructure or setting up new
machines should be directed to the cluster administrators.</p> machines should be directed to the cluster administrators. This
team is led by the lead cluster administrator whose duties and
responsbilities are described in the <a
href="internal/clusteradm.html">cluster administration charter</a>
in greater detail.</p>
<ul> <ul>
<li>&a.bhaga; &lt;<a href="mailto:bhaga@FreeBSD.org">bhaga@FreeBSD.org</a>&gt;</li> <li>&a.bhaga; &lt;<a href="mailto:bhaga@FreeBSD.org">bhaga@FreeBSD.org</a>&gt;</li>
@ -372,7 +376,7 @@
<li>&a.bz; &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;</li> <li>&a.bz; &lt;<a href="mailto:bz@FreeBSD.org">bz@FreeBSD.org</a>&gt;</li>
<li>&a.gjb; &lt;<a href="mailto:gjb@FreeBSD.org">gjb@FreeBSD.org</a>&gt;</li> <li>&a.gjb; &lt;<a href="mailto:gjb@FreeBSD.org">gjb@FreeBSD.org</a>&gt;</li>
<li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li> <li>&a.kensmith; &lt;<a href="mailto:kensmith@FreeBSD.org">kensmith@FreeBSD.org</a>&gt;</li>
<li>&a.peter; &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt;</li> <li>&a.peter; &lt;<a href="mailto:peter@FreeBSD.org">peter@FreeBSD.org</a>&gt; (Lead)</li>
<li>&a.sbruno; &lt;<a href="mailto:sbruno@FreeBSD.org">sbruno@FreeBSD.org</a>&gt;</li> <li>&a.sbruno; &lt;<a href="mailto:sbruno@FreeBSD.org">sbruno@FreeBSD.org</a>&gt;</li>
<li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li> <li>&a.simon; &lt;<a href="mailto:simon@FreeBSD.org">simon@FreeBSD.org</a>&gt;</li>
<li>&a.zi; &lt;<a href="mailto:zi@FreeBSD.org">zi@FreeBSD.org</a>&gt;</li> <li>&a.zi; &lt;<a href="mailto:zi@FreeBSD.org">zi@FreeBSD.org</a>&gt;</li>

1
en_US.ISO8859-1/htdocs/internal/Makefile
View file

@ -9,6 +9,7 @@
DOCS= about.xml DOCS= about.xml
DOCS+= bylaws.xml DOCS+= bylaws.xml
DOCS+= clusteradm.xml
DOCS+= core-vote.xml DOCS+= core-vote.xml
DOCS+= data.xml DOCS+= data.xml
DOCS+= developer.xml DOCS+= developer.xml

105
en_US.ISO8859-1/htdocs/internal/clusteradm.xml Normal file
View file

@ -0,0 +1,105 @@
<?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/doc/share/xml/xhtml10-freebsd.dtd" [
<!ENTITY title "Charter for the Cluster Administrators">
]>
<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>Lead cluster administrator is a delegated officer role (aka. "hat")
that answers to the &os; Core Team and ultimately the &os; community
at large. This person shall have the operational authority over the
&os; cluster infrastructure (to the extent that the Core Team can
delegate this authority) and will be responsible for the following in
general:</p>
<ul>
<li>Ensure the reliable operation of the Project's equipment and
network resources.</li>
<li>Ensure that the Project's resources are suitably and effectively
used to serve the Project's interests.</li>
<li>Ensure that reasonable security precautions and mitigations are
implemented within the constraints of the nature of a highly
distributed project.</li>
<li>Delegate to and coordinating with both the site-specific admin
teams and the admins at large.</li>
<li>Ensure that standard operating procedures, rules, guidelines etc
are documented and understandable.</li>
<li>Take measures to ensure that a competent administrator would be
expected to be able to adopt a predecessor's work in a reasonable
amount of time.</li>
<li>Contingency planning and implementation to ensure continuity
across site specific problems (including donated site withdrawal or
outages).</li>
<li>Keep the interested parties (Core Team, Security Team, &os;
Foundation, Port Management Team, etc), project members and community
members appropriately informed.</li>
<li>Give timely and authoritive answers to questions, or a direct
referral to the appropriate party.</li>
<li>Aid other hat wearers and cluster administrators to get their job
done.</li>
<li>Where practical and appropriate, use the Project's own product as
a proving ground.</li>
<li>Make sure that it is easy for developers to know what hardware
resources they have access to for project purposes.</li>
</ul>
<p>The lead cluster administrator answers to the &os; Core Team. If a
party is unhappy with a position that the hat wearer takes and is
unable to change their mind, they may take the issue to the Core Team.
The Core Team has the final say in the matter. If the lead cluster
administrator is a member of the Core Team then a complaint may be
made in confidence via the core secretary or another member if
desired.</p>
<p>Any of the following still require a sign-off from the Core Team:</p>
<ul>
<li>New public facing services.</li>
<li>Planned withdrawal of public facing services.</li>
<li>New team members.</li>
</ul>
<p>Notable interaction with other hats:</p>
<ul>
<li>The lead cluster administrator will consult with the Security
Officer and the Security Team where appropriate but will be
responsible for making decisions. However, the Security Officer may
respond to security emergencies involving project infrastructure as
necessary.</li>
<li>The Port Management Team has a large resource footprint and
arrangements will be made with them to effectively operate their
resources within the constraints of the overall cluster
operation.</li>
</ul>
<p>Earmarked resources:</p>
<p>Some site resources are provided for specific purposes. Any such
earmarking or use restrictions will be documented to make sure such
resources are used as intended.</p>
</body>
</html>