You are here

Perimeter Filter Reporting

Project ID: 
32
Current stage: 
Manager: 
Unit: 
What: 

Description:

At present our perimeter filter holes are reported on by a mixture of
context diffs and nightly automatic mail summaries. This was fine when
we only had a few holes open, but things have grown so much that it's all
now rather undigestible. The aim of this project is to revamp the
reporting mechanisms substantially, probably to include more targetted
automatic mail and some generated web information and status pages.

Associated with this are the regular scans which IS make of (some of)
our self-managed wires. We should really do something more useful with the
results!

Deliverables: Generated web pages and much better automatic mail warnings.

Why: 

Customer: Anyone with an interest in our perimeter filters (i.e. at least all COs!).

Case statement: While the mechanisms we have in place for reporting on perimeter filter
holes (automatic mail, mostly) work just about well enough, it's obvious
that the information isn't presented in a particularly clear fashion or
perhaps to the right people. Generated web pages and more targetted mail
would make it much easier to keep on top of what's open (and what's not!),
and would allow Unit Leaders to keep the holes opened for "their" machines
under much closer review.

When: 

Status: Stalled, pending allocation of person-power.

This project came about as a result of a meeting between Tim and George
to discuss perimeter filter holes, how they're set up, and how they're
reported back to COs and machine managers.

Timescales: No fixed timescale. What we have works just about well enough to be
going on with.

Priority:

Time:

How: 

Proposal:

Resources: 2-3 weeks of someone's time

Plan:

Other: 

Dependencies: None

Risks:

URL: http://www.dice.inf.ed.ac.uk/units/infrastructure/Projects/06-ipfilter.html

Milestones

Proposed date Achieved date Name Description