Difference between revisions of "CTWUG Admin"

From CTWUG Wiki
Jump to: navigation, search
(Head Admin(s))
 
(45 intermediate revisions by 17 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.
  
'''Please Note:''' We are busy re-arranging the admin teams and so this page could be wildly inaccurate. Please check with [[User:BigMike|BigMike]], [[User:Pilgrim|Pilgrim]] or [[User:TFyre|TFyre]] if you have any questions. ([[User:BigMike|BigMike]] 9/4/2012)
+
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.
  
In alphabetical order:
 
  
==Head Admins==
+
=Network Administrators=
*[[User:BigMike|BigMike]]
+
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.
*[[User:Pilgrim|Pilgrim]]
 
*[[User:TFyre|TFyre]]
 
  
==Day2Day Admins==
+
==Members==
*[[User:TheFox|TheFox]]
+
* [[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]]
  
==Previous Day2Day Admins/Status Unknown Admins==
+
==Responsibilities==
*[[User:Dade|Dade]]
+
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.
*[[User:Morkhans|Morkhans]]
 
*[[User:NyvenZA|NyvenZA]]
 
*[[User:Elvis|Elvis]]
 
*[[User:Hunted|Hunted]]
 
*[[User:Rellik|Rellik]]
 
  
==OSPF Admins==
+
===CTWUG owned High Sites===
*[[User:BigMike|BigMike]]
+
* User additions and deletions.
*[[User:Diabolix|Diabolix]]
+
* IP address management.
*[[User:Pilgrim|Pilgrim]]
+
* Physical infrastructure maintenance.
*[[User:Rellik|Rellik]]
+
* Radio tuning.
*[[User:TFyre|TFyre]]
+
* Routing.
*[[User:TheFox|TheFox]]
+
* [[Node certification]].
 +
* Documentation.
  
==Gaming Admins==
+
===Privately owned High Sites===
*[[User:TheFox|TheFox]]
+
* Optimising, installing, and disabling CTWUG OSPF configurations.
*[[User:Graphire|Graphire]]
+
* [[Node certification]] inspection and reporting.
  
==Hardware Admins==
+
=Services Administrators=
*[[User:Stolla|Stolla]]
+
Services Administrators have to maintain all core network services.  These include:
*[[User:Wetkit|Wetkit]]
 
  
==Trainee/Potential Admins==
+
* Radius
*[[User:Graphire|Graphire]]
+
* DNS
*[[User:Warlock072|Warlock072]]
+
* NTP
*[[User:King|King]]
+
* WMS
*[[User:NoWires|NoWires]]
+
* The web site
 +
* E-mail
 +
* WiND
 +
* OpenID
 +
* The wiki
  
==Areas==
+
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]].
We are currently exploring the idea of splitting responsibilities across geographical areas. This would allow us to have smaller meetings and keep the interest going, while still maintaining a central set of values/procedures/knowledge.
 
  
Things to do/think about:
+
==Members==
* Area breakdown
+
* [[User:Aragon]]
* Structure
+
* [[User:Aquarat]]
* Overlap with general structure
+
* [[User:Dade]]
  
===Southern Suburbs===
+
==Alumni==
====Head Admin(s)====
+
* [[User:Mufasa]]
====Day2Day Admins====
+
* [[User:Beetle001]]
 +
* [[User:Diabolix]]
 +
* [[User:Wolf]]
  
===Northern Suburbs===
+
=WIND Admins=
====Head Admin(s)====
+
WIND Administrators have to maintain the WIND page.  These include:
*[[User:Diabolix|Diabolix]]
 
  
====Day2Day Admins====
+
* Nodes (inactive/active)
 +
* DNS Entries
 +
* Links
  
===Helderberg===
+
As a result, they have access to user data. Which may contain personal information such as email's and contact numbers.
====Head Admin(s)====
 
*[[User:BigMike|BigMike]]
 
====Day2Day Admins====
 
*[[User:CuttingEdge|CuttingEdge]]
 
*[[User:Marais|Marais]]
 
*[[User:MadMax|MadMax]]
 
  
===Stellenbosch===
+
==Members==
====Head Admin(s)====
 
*[[User:Jaja|Jaja]]
 
====Day2Day Admins====
 
  
===Fishoek/Kommetjie===
+
* [[User:Acidice]]
====Head Admin(s)====
+
* [[User:Aragon]]
*[[User:Pmurgs|Pmurgs]]
+
* [[User:Dade]]
*[[User:Georg|Georg]]
+
* [[User:Dan]]
====Day2Day Admins====
+
* [[User:Diabolix]]
 
+
* [[User:Jypels]]
=Duties/Responsibilities=
+
* [[User:King]]
==Head Admins==
+
* [[User:Mufasa]]
*Will assist where Day2Day admins cannot sort the problem
+
* [[User:Ogon]]
*Mentoring and recruitment of new admins
+
* [[User:Pmurgs]]
*Organising admin meets
+
* [[User:razor]]
*Promote communication between area admins
+
* [[User:TheFox]]
*Automated Scripts (Firewall/Games/QOS)
+
* [[User:TheG]]
 
+
* [[User:Uys]]
==OSPF Admins==
+
* [[User:Warlock072]]
 
+
* [[User:JellyBean]]
==Gaming Admins==
+
* [[User:Gekido]]
 
+
* [[User:Ogon]]
==Day2Day Admins==
+
* [[User:Wolf]]
*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===
 
*Change backbone settings
 
*Change frequencies
 
 
 
=Where can admins logon=
 
*[[CTWUG_RADIUS|Radius enabled RB's]]
 

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