--------------------------------
--------------------------------
Parallel session Wrap-up
COD and CE 1st line Support 
--------------------------------
--------------------------------


attendance:
-----------
Emir Imamagic
Jan Astalos
Gilles Mathieu

References/background:
----------------------
http://goc.grid.sinica.edu.tw/gocwiki/TIC_1st_line_support_integration
http://indico.cern.ch/materialDisplay.py?contribId=319&sessionId=5&materialId=slides&confId=18714


Discussion and agreements:
--------------------------

- A specific dashboard for CE 1st Line Support (CE 1LS) will be added to the ROC section of the
  CIC portal

- Write access to this dashboard will be based on GOC-DB "CIC-for-CE" role

- This Dashboard will contain:
	- alarms raised for CE nodes younger than 24h
	- assigned alarms/tickets

- possible actions on alarms:
	- switch off
	- release alarms, so that COD can see them
	- annotate (if not technically possible, start with site annotation)

- which alarms for CE nodes will be invisible on COD dashboard ?
	- alarms raised for CE nodes younger than 24h

- which alarms for CE nodes will still appear on COD dashboard ?
	- alarms raised for CE nodes older than 24h
	- alarms for central services (weight > 30000)

- CE 1LS won't open GGUS tickets

- How to react in case of urgent problem, or problem on "Central services" ?
	- COD will open tickets on a normal way for CE central services
	- CE 1LS will act transparently in parallel (not modifying nor closing anything)
	- if a problem at site level appears to be urgent, CE 1LS can choose to propagate to COD


Technical ideas:
----------------

- to choose if an alarm should appear or not on the COD dashboard, we can add a flag to he SAM alarm
- This needs:
	- precise definition of the rules to set this flag
	- technical investigation with SAM team

- Other technical issues are only related to display
- couple these changes with a global improvement of the dashboard