Difference between revisions of "CTWUG Admin"

From CTWUG Wiki
Jump to: navigation, search
 
(67 intermediate revisions by 21 users not shown)
Line 1: Line 1:
These admins are there to help CTWUG, not serve CTWUGPlease bear in mind that we all have regular jobs and cannot always attend to problems immediatelyPlease log problems on the [http://support.ctwug.za.net support] site when an admin cannot attend immediately.
+
=Introduction=
 +
CTWUG needs an active group of administrators to help maintain the complex network of over 400 router devices and accompanying network services.  This task is split between two groups: Services Administrators and Network AdministratorsThe tasks and constituents of each group are detailed below to help you know who to speak to.  Any wugger may apply to become an administrator - please speak to the Technical Officer if you are competent and interested.
  
 +
The Technical Officer is responsible for maintaining the administrator teams, and is the principle guardian of all CTWUG owned infrastructure and data.  If you have any concerns with the administrators listed below, please approach the Technical Officer, or the Committee directly.
  
=Current Admin Team=
+
Please note this document does not fully encompass the administration of privately owned high sites.  Those will have their own administrative policies in addition to what is documented here.
==Head Admins==
 
*[[User:TFyre|TFyre]]
 
*[[User:Rellik|Rellik]]
 
*[[User:TheFox|TheFox]] (On Leave)
 
==Day2Day Admins==
 
*[[User:Dade|Dade]]
 
*[[User:WireIce|WireIce]]
 
*[[User:Pilgrim|Pilgrim]]
 
*[[User:AndyCap|AndyCap]]
 
  
=What is required of these teams=
 
==Head Admins==
 
*Will assist where Day2Day admins cannot sort the problem
 
*Network Routing (OSPF)
 
*Automated Scripts (Firewall/Games/QOS)
 
==Day2Day Admins==
 
*Add Users
 
*Add IP's
 
*Clean up HS's
 
*Troubleshooting/Faultfinding
 
*Check CCQ
 
*Check Signal
 
*[http://wind.ctwug.za.net WIND] Updates (Personal details + DNS)
 
  
===Not Allowed to===
+
=Network Administrators=
*Change backbone settings
+
Network Administrators possess CTWUG Radius logins, providing them administrative access to all router devices involved in carrying transit traffic for CTWUG, ie. OSPF routers.  Additionally they have administrator access to [http://wind.ctwug.za.net/wind/ WiND], and physical access to [[Ctwug_nodes|CTWUG owned high sites]].  No additional access to infrastructure or data is granted by CTWUG.
*Change frequencies
 
  
=Where can admins logon=
+
==Members==
*[[CTWUG_RADIUS|Radius enabled RB's]]
+
* [[User:Aragon]]
 +
* [[User:Dade]]
 +
* [[User:Dan]]
 +
* [[User:Diabolix]]
 +
* [[User:King]]
 +
* [[User:TheFox]]
 +
* [[User:Warlock072]]
 +
* [[User:Hyperlink]]
 +
* [[User:Darkwing]]
 +
* [[User:Graphire]]
 +
* [[User:Jypels]]
 +
* [[User:Dizzle]]
 +
* [[User:JellyBean]]
 +
* [[User:Gekido]]
 +
* [[User:Ogon]]
 +
 
 +
==Responsibilities==
 +
Any tasks outside of the below list will only be performed with express notification to and permission from the high site owner(s) and/or the Committee.
 +
 
 +
===CTWUG owned High Sites===
 +
* User additions and deletions.
 +
* IP address management.
 +
* Physical infrastructure maintenance.
 +
* Radio tuning.
 +
* Routing.
 +
* [[Node certification]].
 +
* Documentation.
 +
 
 +
===Privately owned High Sites===
 +
* Optimising, installing, and disabling CTWUG OSPF configurations.
 +
* [[Node certification]] inspection and reporting.
 +
 
 +
=Services Administrators=
 +
Services Administrators have to maintain all core network services.  These include:
 +
 
 +
* Radius
 +
* DNS
 +
* NTP
 +
* WMS
 +
* The web site
 +
* E-mail
 +
* WiND
 +
* OpenID
 +
* The wiki
 +
 
 +
As a result, they have access to all CTWUG data and infrastructure, including personal information of CTWUG Members.  Their privileges give them the ability to act as Network Administrators, if necessary.  Services Administrators are legally bound by the [[media:CTWUG-NDA.odt|CTWUG NDA]].
 +
 
 +
==Members==
 +
* [[User:Aragon]]
 +
* [[User:Aquarat]]
 +
* [[User:Dade]]
 +
 
 +
==Alumni==
 +
* [[User:Mufasa]]
 +
* [[User:Beetle001]]
 +
* [[User:Diabolix]]
 +
* [[User:Wolf]]
 +
 
 +
=WIND Admins=
 +
WIND Administrators have to maintain the WIND page.  These include:
 +
 
 +
* Nodes (inactive/active)
 +
* DNS Entries
 +
* Links
 +
 
 +
As a result, they have access to user data. Which may contain personal information such as email's and contact numbers.
 +
 
 +
==Members==
 +
 
 +
* [[User:Acidice]]
 +
* [[User:Aragon]]
 +
* [[User:Dade]]
 +
* [[User:Dan]]
 +
* [[User:Diabolix]]
 +
* [[User:Jypels]]
 +
* [[User:King]]
 +
* [[User:Mufasa]]
 +
* [[User:Ogon]]
 +
* [[User:Pmurgs]]
 +
* [[User:razor]]
 +
* [[User:TheFox]]
 +
* [[User:TheG]]
 +
* [[User:Uys]]
 +
* [[User:Warlock072]]
 +
* [[User:JellyBean]]
 +
* [[User:Gekido]]
 +
* [[User:Ogon]]
 +
* [[User:Wolf]]

Latest revision as of 08:34, 30 November 2018

Introduction

CTWUG needs an active group of administrators to help maintain the complex network of over 400 router devices and accompanying network services. This task is split between two groups: Services Administrators and Network Administrators. The tasks and constituents of each group are detailed below to help you know who to speak to. Any wugger may apply to become an administrator - please speak to the Technical Officer if you are competent and interested.

The Technical Officer is responsible for maintaining the administrator teams, and is the principle guardian of all CTWUG owned infrastructure and data. If you have any concerns with the administrators listed below, please approach the Technical Officer, or the Committee directly.

Please note this document does not fully encompass the administration of privately owned high sites. Those will have their own administrative policies in addition to what is documented here.


Network Administrators

Network Administrators possess CTWUG Radius logins, providing them administrative access to all router devices involved in carrying transit traffic for CTWUG, ie. OSPF routers. Additionally they have administrator access to WiND, and physical access to CTWUG owned high sites. No additional access to infrastructure or data is granted by CTWUG.

Members

Responsibilities

Any tasks outside of the below list will only be performed with express notification to and permission from the high site owner(s) and/or the Committee.

CTWUG owned High Sites

  • User additions and deletions.
  • IP address management.
  • Physical infrastructure maintenance.
  • Radio tuning.
  • Routing.
  • Node certification.
  • Documentation.

Privately owned High Sites

  • Optimising, installing, and disabling CTWUG OSPF configurations.
  • Node certification inspection and reporting.

Services Administrators

Services Administrators have to maintain all core network services. These include:

  • Radius
  • DNS
  • NTP
  • WMS
  • The web site
  • E-mail
  • WiND
  • OpenID
  • The wiki

As a result, they have access to all CTWUG data and infrastructure, including personal information of CTWUG Members. Their privileges give them the ability to act as Network Administrators, if necessary. Services Administrators are legally bound by the CTWUG NDA.

Members

Alumni

WIND Admins

WIND Administrators have to maintain the WIND page. These include:

  • Nodes (inactive/active)
  • DNS Entries
  • Links

As a result, they have access to user data. Which may contain personal information such as email's and contact numbers.

Members