Difference between revisions of "SL5 retirement"
Jump to navigation
Jump to search
(Created page with "The role of this page is tracking the progressive decommissioning of SL5 from sites. Each NGI can update the status here in order to have the picture on the status of the SL5 dep...") |
|||
Line 1: | Line 1: | ||
The role of this page is tracking the progressive decommissioning of SL5 from sites. Each NGI can update the status here in order to have the picture on the status of the SL5 deployment. | The role of this page is tracking the progressive decommissioning of SL5 from sites. Each NGI can update the status here in order to have the picture on the status of the SL5 deployment. | ||
= Table = | |||
For NGIs/ROCs: please update the status in the table below. | |||
= Comments = | |||
*SAM-nagios is still SL5, no SL6 available. If ARGO gets fully centralized, there is no need to use SAM-nagios anymore; otherwise, we need a schedule for porting SAM-nagios on SL6 | |||
** action on Vincenzo to understand the status of ARGO scalability tests |
Revision as of 17:58, 15 June 2015
The role of this page is tracking the progressive decommissioning of SL5 from sites. Each NGI can update the status here in order to have the picture on the status of the SL5 deployment.
Table
For NGIs/ROCs: please update the status in the table below.
Comments
- SAM-nagios is still SL5, no SL6 available. If ARGO gets fully centralized, there is no need to use SAM-nagios anymore; otherwise, we need a schedule for porting SAM-nagios on SL6
- action on Vincenzo to understand the status of ARGO scalability tests