Notes from Pole 2, 3rd TC

Participants: Georgatos Fotis. Vera, Malgorzata Helene Diana Ioannis

Agenda, notes, APs:

1. Handling of security incidents in the OPS Manuals.

We need to include in the OPS manual information about security procedures. We will put Romains text replacing section 9 of the manual. Still though the role of OSCT-DC is not clear. More discussion with Romain should be done on the issues. We have also to follow up the creation of middleware vulnerability and CA update procedure into the OPS manual.

AP: Include Romains text in the new version of the OPS manual. (Ioannis) AP: Collect all security related issues in Helsinki so that a meeting with Romain is organized. (Helene) AP: Send mail to Romain explaining the situation and asking him about the middleware vulnerability and CA update procedure text to be inclided in the OPS manual.

2. Upgrade of the manuals based on the comments received in the SA1 coordination meeting. Separation of procedures from tools and their description.

This requires quite a lot of work and will have to be done after Helsinki. We have to ask developers to document their tools so that there is no need to maintain all this information on the OPS manual.

Actions for the future: create separate C-COD manual and ROD/1st line support.

AP: Request from Maite to discuss with the OAT the possibility for this documentatin to be provided. (Ioannis)

3. Best Practices Manual.

It was noted that there is various types of documentation regarding the COD work around that is not trivial to find out where it is. It was proposed that we collect all this documentation and put it clearly in the CIC portal / ROC section.

The documentation is:

a. OPS Manual

b. Best Practices Guide (to be created)

c. Training material for CIC portal

d. ….?

The best practices manual should contain instructions from the experience of ROD and 1st line support and C-COD work that are not clearly instructions and cannot be put in the OPS manual. It could be a wiki. Fotis to maintain the wiki.

AP: create the wiki page and send mail to fotis to start polulating it (Ioannis)

AP: Fotis to be responsible for the best practices wiki and propose a structure for it. (Fotis)

4. Training material.

Training material is to be distributed before the meeting.

Trainers have to be indentified before the meeting in Helsinki.

Malgorzata, Daniel, Michalea to provide some training sessions in Helsinki

AP: Distribute training material before training in Helsinki (Helene?)

AP: Who is maintaining the training material? To be decided.

5. COD work organization

Discussed the future of the different pole inside the COD work organization.

Pole1 and Pole2 have finished their major work which was: for pole1 to organize the regional model and for pole2 to do the OPS manual restructuring and produce the regional OPS manual. The remaining work for pole1 is to monitor the process of the regional monitoring trying to see how it evolves over time. It was decided that pole1 and pole2 should merge.

Pole 3 is about the tools and can continue its work as it is now.

For the merge of pole1 and pole2 we need to provide a new mandate and indentify the people that lead it and people that work in the various working groups within pole2.

AP: To write the pole1,2 mandate.

AP: To identify the leaders and stuff the working groups.

6. how to set-up the feedback from RODs of all countries and make the community worthwhile for bottom-up needs and experience gathering and top-down know-how and info diffusion

Communication and feedback loops between 1st line suppoeters, ROD and C-COD is not very well established.

Different use cases for such communication where identified:

a. identify solutions that ROD cannot solve by themselves

b. announce current issues with the infrastructure so that all 1st line supporters and RODs/C-COD know.

c. Extract usefull long term information from the above exchange of knowledge.

Proposed solutions where the creation of chat rooms, mailing lists, forum. It was discussed that the main problem is not the technical implementation but the stuffing of such communication channels.

Maybe a good solution for a start is the use of existing mailing list. C-COD people should be responsible for extract useful information from such communication in the mailing lists and all RODs should have somebody to monitor the lists and provide feedback. It is advised to re-use existing mailing lists if possible and not create yet another mailing list.

AP: Produce a draft proposal for setting up those communication channels and discuss it in Helsinki. This has to be communicated inside Pole2 first.

7. AOB.

When is the next release of the OPS Manual and what it contains?

The next release should be soon after Helsinki.

The changes to be included are:

a. List of references to the whole documentation related to the work of 1st line support/ROD/C-COD.

b. Changes on OSCT-DC section. Replace section 9 with Romains text. See if it is going to be in common section or in different sections.

c. New proposal for escalation. Minor change.

-- IoannisLiabotis - 12 Jun 2009

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2009-06-12 - IoannisLiabotis
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback