Service Level Agreement/Description between CE ROC and Sites

Slides:



Advertisements
Similar presentations
SERVICE LEVEL AGREEMENTS The Technical Contract Within the Master Agreement.
Advertisements

Summer IAVA1 NATIONAL INFORMATION ASSURANCE TRAINING STANDARD FOR SYSTEM ADMINISTRATORS (SA) Minimum.
EGEE SA1 Operations Workshop Stockholm, 13-15/06/2007 Enabling Grids for E-sciencE Service Level Agreement Metrics SLA SA1 Working Group Łukasz Skitał.
LCG Milestones for Deployment, Fabric, & Grid Technology Ian Bird LCG Deployment Area Manager PEB 3-Dec-2002.
Operational Security Working Group Topics Incident Handling Process –OSG Document Review & Comments:
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks PoW for the second year Transition to EGI.
EGI: SA1 Operations John Gordon EGEE09 Barcelona September 2009.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
Deployment Issues David Kelsey GridPP13, Durham 5 Jul 2005
GRANT MANAGEMENT SEMINARS MEMORANDUM OF UNDERSTANDING.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Middleware Deployment and Support in EGEE.
Security Policy Update LCG GDB Prague, 4 Apr 2007 David Kelsey CCLRC/RAL
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks David Kelsey RAL/STFC,
EGEE-III INFSO-RI Enabling Grids for E-sciencE Monitoring and enforcement of Service Level Agreements John Shade EGEE-II / EGEE.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks The Bazaar Vision Ideas of RC/VO coordination,
SA1/SA2 meeting 28 November The status of EGEE project and next steps Bob Jones EGEE Technical Director EGEE is proposed as.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Multi-level monitoring - an overview James.
Mine Altunay July 30, 2007 Security and Privacy in OSG.
Grid Operations Centre LCG SLAs and Site Audits Trevor Daniels, John Gordon GDB 8 Mar 2004.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks SA1: Grid Operations Maite Barroso (CERN)
INFSO-RI Enabling Grids for E-sciencE EGEE SA1 in EGEE-II – Overview Ian Bird IT Department CERN, Switzerland EGEE.
8 th CIC on Duty meeting Krakow /2006 Enabling Grids for E-sciencE Feedback from SEE first COD shift Emanoil Atanassov Todor Gurov.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks DSA1.4 – Objectives and Status Ioannis Liabotis.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks ROC Security Contacts R. Rumler Lyon/Villeurbanne.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Resource Allocation in EGEEIII Overview &
AEGIS Academic and Educational Grid Initiative of Serbia Antun Balaz (NGI_AEGIS Technical Manager) Dusan Vudragovic (NGI_AEGIS Deputy.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Deliverable DSA1.4 Jules Wolfrat ARM-9 –
Temporary Assistance for Needy Families Part 265: Data Collection and Reporting.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Operations Automation Team Kickoff Meeting.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Ian Bird All Activity Meeting, Sofia
Operations model Maite Barroso, CERN On behalf of EGEE operations WLCG Service Workshop 11/02/2006.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Pole 2 : Restructuration of the OPS Manual.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks LHCOPN Operational model: Roles and functions.
CERN - IT Department CH-1211 Genève 23 Switzerland t IT-GD-OPS attendance to EGEE’09 IT/GD Group Meeting, 09 October 2009.
EGEE-III INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks What all NGIs need to do: Helpdesk / User.
EGEE-II INFSO-RI Enabling Grids for E-sciencE EGEE and gLite are registered trademarks Grid is a Bazaar of Resource Providers and.
EGI Process Assessment and Improvement Plan – EGI core services – Tiziana Ferrari FedSM project 1EGI Process Assessment and Improvement Plan (Core Services)
Grid Deployment Technical Working Groups: Middleware selection AAA,security Resource scheduling Operations User Support GDB Grid Deployment Resource planning,
Service Level Agreement Considerations
Registration of treaties under Article 102 of the Charter of the United Nations Keiichiro Okimoto Associate Legal Officer Treaty Section, Office of Legal.
SLAs with Software Provider. Scope “…declare the rights and responsibilities between EGI.eu and the Software Provider for a particular component.” Which.
JRA2: Quality Assurance
PLWG Review 6.9 and the Interconnection process
Operations Status Report
Support Operation Challenge – 1 SOC-1 Alistair Mills Torsten Antoni
Open Science Grid Consortium Meeting
SA1 Execution Plan Status and Issues
Content of Tender Dossier Instructions to Tenderers
EGEE-II SLA Progress Report & Initial Proposal
Ian Bird GDB Meeting CERN 9 September 2003
Sistemi di monitoraggio e allarmistica
The CREAM CE: When can the LCG-CE be replaced?
Report on SLA progress Ioannis Liabotis <ilaboti at grnet.gr>
Maite Barroso, SA1 activity leader CERN 27th January 2009
Nordic ROC Organization
Outline Introduction Objectives Motivation Expected Output
BalticGrid Operations
ITIL: Why Your IT Organization Should Care Service Support
ITIL: Why Your IT Organization Should Care Service Support
CONTRACT ADMINISTRATION
WHAT TO EXPECT: A CROWN CORPORATION’S GUIDE TO A SPECIAL EXAMINATION
Compliance of Voluntary Organisations
IEEE IMT-Advanced Review Process
ITIL: Why Your IT Organization Should Care Service Support
IEEE IMT-Advanced Review Process
QA Reviews Lecture # 6.
Kashif Mohammad Deputy Technical Co-ordinator (South Grid) Oxford
EGEE Operation Tools and Procedures
Compliance of Voluntary Organisations
Site availability Dec. 19 th 2006
Presentation transcript:

Service Level Agreement/Description between CE ROC and Sites Tomasz Szepieniec, CYFRONET CE SA1 Transition Meeting

ROC and Site Clear communication and agreed expectations make for happy relationships, which is where service level agreements come in. SLAs provide each party with a clear idea of what they are expected to do and how, clarifying any previously gray areas. Taken from: http://www.isgtw.org/?pid=1000798 Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28

Why we need to do this now? EGEEII TA: „In EGEE-III it will be important to fully develop a full set of Service Level Agreements (SLA) at several levels.” ROC-Site SLA(SLD) is planned to be first ROCs are constantly asked about progress in this Template of SLD is (almost) ready https://edms.cern.ch/file/860386/0.6/EGEE-ROC-Site-SLD-v1.5.pdf Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28

ROC Obligations provide Help Desk facilities (first-level support) register site administrators in the available Help Desk facilities; provide third-level support by helping in the resolution of advanced and specialized operational problems; propagate and follow-up problems with higher-level operational or development teams; ticket follow-up (ensure that sites work on tickets opened against them). respond to tickets from sites in a timely manner (four hours)‏ Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28

Site Obligations Site is obliged to: What if site or ROC fail SLD: adhere to the Operational Procedures described in the Operations Procedures Manual; maintain accurate information on the services they provide in GOCDB; adhere to the Grid Site Operations Policy, and other policy documents referenced therein; adhere to the requirements stated in the Security and Availability Policy document; adhere to the criteria and metrics that are defined in this Service Level Description (SLD); run supported versions of gLite (or compatible) middleware respond to GGUS tickets in a timely manner (four hours)‏ What if site or ROC fail SLD: „No penalties for missing targets will be applied, but results will be published openly (in GridView). Site are responsible to provide justification for any SLD violations. Similarly, ROC..” Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28

Metrics Minimum number of site BDIIs Minimum number of CEs or SEs Minimum number of WN CPUs/cores Minimum capacity of SE(s)‏ Minimum site availability according GridView, includes scheduled downtimes Minimum site reliability Reliability = Availability / (Availability + Unscheduled Downtime)‏ Period of availability/reliability/outage calculations (per month)‏ Minimum number of system administrators (one)‏ Maximum time to acknowledge GGUS tickets (four hours)‏ Maximum time to resolve GGUS incidents (five working days)‏ Minimum number of supported user-community VOs (one)‏ Tracking of SLD conformance (monthly)‏ Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28

Procedure (draft)‏ On sites registration primary site manager must send to ROC document: designating him/her to be responsible for a site, claiming that ROC will be informed in case of changes in this position, signed by organization/institute director or person mentioned as responsible for the project in TA (technical person); Declare who will sign SLD document should include DN (equals to one in his certificate) of Primary Site Manager. values of SLD metrics are fixed proposed by Site, approved by ROC limits for SLD boundaries of acceptance not defined (yet)‏ primary site manager and ROC manager sign SLD using his/her certificate that is approved For existing sites the procedure could be similar Procedure of signing amendment „form of a signed and dated SLD addendum” Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28

Organization Provisional timeframe Responsible person in ROC May – fix the regulations, clearify issues June – July adapt site registration procedure call for documents that support Primary Site Manager possition August – September fixing SLD metrics with sites signing documents Responsible person in ROC Tomasz Szepieniec (organization and preparation)‏ Alex Kusznir (signing SLD)‏ Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28

Issue to disscuse/changes „GridView is used to calculate a site's SLD conformance, using data from GOCDB and SAM” what about 'core service failures'? Procedures of signing who will sign it for a Site? Primary site manager or director Any changes to SLD template? What to do with sites which are no EGEE3 members? we prefer all sites in production sign SLD Tomasz Szepieniec,CE SA1 Meeting , 2008-04-28