DICE Reorganisation: Meeting 2002-11-28

.........................

doc

.........................

JCMB, 11am-12.30pm

Minutes: Jeremy

Jeremy is still collating time spent on fire-related activities. All CO/CSOs should keep a record and submit figures regularly
cremated SB hosts need to be removed from the profile server. These should not be removed via rfe. Instead:
1. login to the lcfg server, tomato
2. find and rm the relevant file
3. rebuild the profiles, checking that it went correctly
it is still the policy that we are not re-using host names from legacy domains (anc, cogsci, dai, dcs, aiai) under DICE. This also include cstr as their machines will be served from inf.
the filehandle problem seen on topper is not a bug but a function of loading. To see whether it can be fixed the setting for filehandles should be increased significantly
there is uncertainty for users over the level of backup they can expect due to different policies at each site. A public statement is needed.
[ACTION: Jeremy]
the current list of all named teams and their leaders will be circulated
[ACTION: Jeremy]

RT has undergone some revisions. We now need some decisions on how it is to be used by all COs, rather than just CSOs.

ticket escalation/nagging will be implemented.
- a reminder will be sent for any an unanswered ticket after half a day, to the Ticket Allocating Supremo.
- for each queue or individiual, the status of all tickets will be summarised and sent by email once a week.
- first-pass ticket allocation (by CSOs) should be done to a team or group rather an individual.
there is an existing problem where tickets contain more than one problem. Typically a CSO retains the ticket and attempts to get answers to all aspects.
RT can have multiple queues. It is also possible to allocate tickets to groups. Which approach is most suitable for support issues needs to be investigated.
[ACTION: John/Chris/Jeremy]

Views were sought on how group meetings should operate. There are a number of basic requirements:

meetings are open to all CO/CSOs
they will be minuted and minutes publicised on the web
each group's meetings should be scheduled on a regular and not conflicting with other groups to allow CO/CSOs to attend whichever ones they need.

: Deploy : Meetings

Please contact us with any comments or corrections.
Unless explicitly stated otherwise, all material is copyright The University of Edinburgh