ROC Start-up Template

Note this block will only appear when viewing the template and not when generating a page from it.

This is the template for the new ROC project page. Editing this template will cause all future minutes pages created on CERNROCIncubator to use the new modified template. Existing pages will not be altered.

Actual template starts after this line.

---

LCG Grid Deployment - CERN ROC - ROC Incubator

Plan and milestones for the creation of the new ROC Full ROC Name (to be defined)

---

• ROCName: ROC Name (to be defined)
  
• StartDate: NA
  
• DueDate: NA
  
• Status: To Start
  

---

This page is used to define requisites, plans and milestones in the set-up of the new ROC ROC Name (to be defined) and bring it up to operations.
This main actors of this process are the ROC ROC Name (to be defined) (candidate) and the ROC (incubator).
In all of the following, we will assume that both parties have read the Definition of a ROC and associated functions

References will be used also for the socument describing the step-by-step creation of a new ROC.

Requisites for the new ROC personnel.

The following is the minimal set of pre-requisites that need to be fulfilled start before the new ROC is set into operations.

• Training-on-the-job (minimum 1-month for the future technical manager(s)
  • The training is completed by participating to the ROC CERN ROD activities in order to get familiarity with the infrastructure and procedures. For a maximum efficiency it's highly recommended to arrange a stage at CERN at this purpose.
  • I can be done in parallel the technical task for the creation and go along throughout the whole execution of the project. It's advised however to start it as soon as possible in order to profit of the experience during the design of the regional infrastructure.
  • Equivalent recent experience can be accepted if certified by another ROC.
• A record of 4 attendances to the weekly OPS meeting

These pre-requisites are posed in the interest of the sites to be operated in the scope of the future ROC
In addition it would be good if the following started at the same time:

• Operating Nagios at regional level
• Operating the top level BDII

Design of the Infrastructure

The infrastructure would need to be defined well in advance, at least one month/3 weeks prior to the starting of the operations. A typical infrastructure may require:

• If relevant, the registration of a new DNS domain name
• The name of the new ROC, the ROC manager, the ROC manager's deputies, the ROC security contact.
• mailing list to contact the ROC, for ROC management purposes
• mailing list to contact the ROC for security purposes
• mailing list to contact the ROC for user support purposes
• Web site for the new ROC as a reference point for the public and maybe the administrators of the sites belonging to the ROC
• Internal twiki or other collaboration tool targeted at the members of the ROC team
• A regional top-level BDII (accessing all the sites in the EGEE infrastructure)
• Certification infrastructure
  • A certification bdii, containing the entries that are available in production, plus the services run at the site(s) to be certified
  • A WMS able to submit to the CE(s) belonging to the sites to be certified
  • A ROC Nagios

Tasks for ROC CERN (before kick-off meeting)

• Produce ROC start-up project wiki (this page) : done
• Send information documentation: not started
• Request contacts and draft infrastructure plan: not started
• Call kick-off meeting: not started
• Provide draft start-up plan: not started

Tasks for ROC ROC Name (to be defined)

• Provide contacts: not started
  • Mailing list : n.a.
  • Responsible people: n.a.
• Definition of service infrastructure: not started
  • management : n.a.
  • systems layout : n.a.
  • User support (GGUS/not GGUS) : n.a.
  • Sites: n.a.

Joint tasks (meeting)

• Review and Approve execution plan

Input documents (before kick-off meeting)

General Documentation (by ROC CERN )

• Definition of a ROC and associated functions (mandatory)
• CERNNewROCROC Name (to be defined)#Tasks_for_ROC_ROC Name (to be defined)[Initial checklists for the new ROC] (mandatory)
• EGEE Operational documentation(optional at this stage but highly recommended)

Draft Execution Plan ( by ROC CERN )

Proposal for Infrastructure (by ROC ROC Name (to be defined) )

Output Documents (after kick-off meeting)

Minutes of kick-off meeting

Implementation

Tasks for ROC ROC Name (to be defined) (after kick-off meeting)

Task	Start Date	Due Date	Status
Complete the check-list to join as the CERN ROD rota	dd-Mon-YY	dd-Mon-YY	not started
CERN ROD Rota	dd-Mon-YY	dd-Mon-YY	not started
Installation of the ROC Nagios	dd-Mon-YY	dd-Mon-YY	not started
Installation of the ROC bdii	dd-Mon-YY	dd-Mon-YY	not started
Set-up of the user support infrastructure (GGUS or not GGUS)	dd-Mon-YY	dd-Mon-YY	not started
Installation of the certification infrastructure	dd-Mon-YY	dd-Mon-YY	not started
Communication of the ROC security contact and mailing list to OSCT	dd-Mon-YY	dd-Mon-YY	not started
Setting up of the VOMS dteam infrastructure	dd-Mon-YY	dd-Mon-YY	not started
[[https://twiki.cern.ch/twiki/bin/view/LCG/ProceduresForCandidateROCs][Sign SLA with sites] ]	dd-Mon-YY	dd-Mon-YY	not started

Tasks for ROC CERN (after kick-off meeting)

Task	Start Date	Due Date	Status
assisting in the installation of the ROC infrastructure	dd-Mon-YY	dd-Mon-YY	not started
Supervision of the ROD shifts	dd-Mon-YY	dd-Mon-YY	not started
Enable the ROC ROC Name (to be defined)over various operational tools	dd-Mon-YY	dd-Mon-YY	not started
Communicate to dteam the creation of the new ROC	dd-Mon-YY	dd-Mon-YY	not started
Notify SA1 management to include the new ROC representatives in the ROC managers mailing list	dd-Mon-YY	dd-Mon-YY	not started
E-mailing the ROC CERN sites of the change of ROC	dd-Mon-YY	dd-Mon-YY	not started
Run check and tests against the new ROC infrastructure	dd-Mon-YY	dd-Mon-YY	not started
Notify the production service of the new ROC ROC Name (to be defined) in operations	dd-Mon-YY	dd-Mon-YY	not started

Input documentation (for implementation phase)

Output documentation (completed after implementation)

Description of the infrastructure

Final assessment

Milestones

• Start Date:
• Start/finish participation in the ROC CERN ROD activities:
• Start Participation to the OPS meeting
• Finish Design Phase:
• Relevant GGUS releases:
• Checkpoint to see that the ROC infrastructure is completely defined:
• Start of Operations:

After the creation of the ROC (tasks for ROC CERN )

• Check regular participation to the OPS meeting
• Monitoring of the new ROC ROD activities, assist wherever possible
• Check status of new ROC web site/twiki, assist wherever possible
• check at the end of the first and second month after the ROC is set up that they are correctly publishing
  • accounting
  • site availability/reliability
• Follow closely and assist in the certification of the first new site in the new ROC