headers
Julian De Marchi | 23 May 2007 06:19
Picon

Re: "Roles", was PROJECT: Bug Tracking

Robin wrote:
> OK, here's a list of the folks who've volunteered for the teams so far:
> 
> admins
>    krystal <at> devnull.net
>    shdwdrgn <at> sourpuss.net
>    julian <at> jdcomputers.com.au
> 
> architects
>    krystal <at> devnull.net
>    shdwdrgn <at> sourpuss.net
>    thatoneguy <at> aaronjangel.us
> 
> auditor
> 
> bugmeister
>    shdwdrgn <at> sourpuss.net
> 
> dbadmins
>    thatoneguy <at> aaronjangel.us
> 
> hostmasters
>    krystal <at> devnull.net (root, opennic.glue, .null)
>    dennisthetiger <at> gmail.com (root, opennic.glue, .fur)
>    shdwdrgn <at> sourpuss.net (.oss)
> 
> list admins
> 
> pr reps      
> webmasters
(Continue reading)

Permalink | Reply |
headers
Robin | 23 May 2007 17:31

Re: "Roles", was PROJECT: Bug Tracking

I've got a lot more experience with OTRS as a ticket tracking system 
(since I set it up and use it for our ISP), but I've never seen Request 
Tracker.

I should probably learn Nagios anyway, though, and since we don't have a 
volunteer for auditor I suppose I can see about getting it set up on 
zero to monitor the other servers.

I have a rough audit script that reads in the config files (from which 
the scripts build our root zone and decide which servers to show on the 
web page) and does SOA queries against all the servers for each OpenNIC 
zone.  I need to clean up its output so it can give a synopsis of which 
machines are serving what data corectly, at which point I'll set it up 
to run on a schedule and email its output to a mailing list.

-robin

Julian De Marchi wrote:
> ...
> Just putting some more ideas into the pot for support and monitoring.
>
> Request Tracker 3.0 to run a support system, where we all share equal 
> responsibilities for support issues and monitor the RT for support 
> tickets. I feel that using RT will give everyone an idea of what the 
> common issues for OpenNIC users are.
>
> Also for monitoring of the OpenNIC systems, Nagios[0] might be a good 
> choice to monitor all host systems. Nagios also has great graphing 
> tools so we can put together a downtime chart, and various other 
> informative charts.
(Continue reading)

Permalink | Reply |
headers
Julian De Marchi | 24 May 2007 02:18
Picon

Re: "Roles", was PROJECT: Bug Tracking

Robin wrote:
> I've got a lot more experience with OTRS as a ticket tracking system 
> (since I set it up and use it for our ISP), but I've never seen Request 
> Tracker.
> 
> I should probably learn Nagios anyway, though, and since we don't have a 
> volunteer for auditor I suppose I can see about getting it set up on 
> zero to monitor the other servers.
> 
> I have a rough audit script that reads in the config files (from which 
> the scripts build our root zone and decide which servers to show on the 
> web page) and does SOA queries against all the servers for each OpenNIC 
> zone.  I need to clean up its output so it can give a synopsis of which 
> machines are serving what data corectly, at which point I'll set it up 
> to run on a schedule and email its output to a mailing list.
> 
> -robin

The nagios monitoring host should not be a critical system in the 
OpenNIC network. The host should be on a machine whos sole purpose is to 
monitor the state of the OpenNIC network. I have nearly finished my 
nagios setup on a host.

I am unsure who should have access to the charts and graphs and other 
information nagios contains. Who should have access?

Also the alerts nagios outputs, should go to a list like 
alerts <at> opennic.unrated.net? I have also been testing nagios to produce a 
voice alert if the internet connection of the host goes down.
(Continue reading)

Permalink | Reply |
headers
Robin | 24 May 2007 04:39

Re: "Roles", was PROJECT: Bug Tracking

I agree completely; I figured it would be useful to have zero monitoring 
things as well (and no one else had volunteered to be auditor, so I 
figured I could at least start with that).

At the very least, the admins should all have access; it'd probably be 
best to let any member access any stats or charts that wouldn't contain 
any private info on a server or a member and restrict those to the folks 
who are on any of the operational teams.

I'll add "alerts <at> " to the list of lists I need to get set up with mailman.

-robin

Julian De Marchi wrote:
> . ..
> The nagios monitoring host should not be a critical system in the 
> OpenNIC network. The host should be on a machine whos sole purpose is 
> to monitor the state of the OpenNIC network. I have nearly finished my 
> nagios setup on a host.
>
> I am unsure who should have access to the charts and graphs and other 
> information nagios contains. Who should have access?
>
> Also the alerts nagios outputs, should go to a list like 
> alerts <at> opennic.unrated.net? I have also been testing nagios to produce 
> a voice alert if the internet connection of the host goes down.
>
> Julian
...
######################################################################
(Continue reading)

Permalink | Reply |
headers
Anner van Hardenbroek | 24 May 2007 09:08
Picon
Gravatar

Re: "Roles", was PROJECT: Bug Tracking

Robin,

On 5/24/07, Robin <krystal <at> devnull.net> wrote:
I agree completely; I figured it would be useful to have zero monitoring
things as well (and no one else had volunteered to be auditor, so I
figured I could at least start with that).

I'd  volunteered ...:
On 5/24/07, Anner van Hardenbroek <dwlnetnl <at> gmail.com> wrote:
auditor
   dwlnetnl <at> gmail.com

-Anner

--
Anner van Hardenbroek,
dwlnetnl <at> gmail.com
Permalink | Reply |
headers
Julian De Marchi | 24 May 2007 04:49
Picon

Re: "Roles", was PROJECT: Bug Tracking

Robin wrote:
> I agree completely; I figured it would be useful to have zero monitoring 
> things as well (and no one else had volunteered to be auditor, so I 
> figured I could at least start with that).
> 

I shall be auditor if you wish, and run the nagios host to monitor the 
OpenNIC network.

> At the very least, the admins should all have access; it'd probably be 
> best to let any member access any stats or charts that wouldn't contain 
> any private info on a server or a member and restrict those to the folks 
> who are on any of the operational teams.
> 
> I'll add "alerts <at> " to the list of lists I need to get set up with mailman.
> 
> -robin

If a go ahead is given, nagios will be installed on a server whose 
primary role will be to monitor everything.

Julian
######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
"unsubscribe discuss" in the body of the message to
"majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
######################################################################
Permalink | Reply |
headers
avo | 23 May 2007 18:44

Re: "Roles", was PROJECT: Bug Tracking


I should also take a shot at nagios for other purposes as well, so don't 
feel obliged or alone :)

avo

######################################################################
This is the discussion list for the Open Network Information
Center.  You can unsubscribe by sending an email containing the words
"unsubscribe discuss" in the body of the message to
"majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net".
######################################################################
Permalink | Reply |
headers
Anner van Hardenbroek | 24 May 2007 00:34
Picon
Gravatar

Re: "Roles", was PROJECT: Bug Tracking

Sorry for the quite late responding. I had holiday in Spain. I'd like the idea of Robin to make different teams or persons head of something. I know about myself that I'm good making visions and idea's of architectures and so, but that I'm not really  the guy to implement them in great number. I'd like to help where I can, but I'm more at the vision site than the actual dev-site. I see myself as part of the architects, I'd like to see what the area's are that I form a good addition. I think it's the website, (little) database, propably list admin and some net admin stuff like server monitoring.

So I'd like to make an addition to the list of Robin:

admins
   krystal <at> devnull.net
    shdwdrgn <at> sourpuss.net
   julian <at> jdcomputers.com.au

architects
    krystal <at> devnull.net
   shdwdrgn <at> sourpuss.net
    thatoneguy <at> aaronjangel.us
   dwlnetnl <at> gmail.com

auditor
   dwlnetnl <at> gmail.com

bugmeister
    shdwdrgn <at> sourpuss.net

dbadmins
   thatoneguy <at> aaronjangel.us
   dwlnetnl <at> gmail.com

hostmasters
   krystal <at> devnull.net (root, opennic.glue, .null)
    dennisthetiger <at> gmail.com (root, opennic.glue, .fur)
   shdwdrgn <at> sourpuss.net (.oss)

list admins
   krystal <at> devnull.net
   dwlnetnl <at> gmail.com (stand in or so? - i don't have really an idea how much time it cost)

pr reps

webmasters
   brian <at> pongonova.net (Wiki)
    shdwdrgn <at> sourpuss.net (registration, bug tracking)
   dwlnetnl <at> gmail.com (lead?)

-Anner.

--
Anner van Hardenbroek,
dwlnetnl <at> gmail.com

Permalink | Reply |

Gmane