Difference between revisions of "Procedure Downtime Declaration"
| Line 1: | Line 1: | ||
__TOC__ | __TOC__ | ||
| + | |||
| + | == Downtime Declaration == | ||
| + | |||
Any scheduled downtime must be announced in advance to the user communities. The announcement is done by the [[Role Infrastructure Manager|Infrastructure Manager]], [[Role VO Admin|VO Admin]] or [[Role VRE Manager|VRE Manager]] exploiting the facilities offered on each VO/VRE by the Resource Management portlet. | Any scheduled downtime must be announced in advance to the user communities. The announcement is done by the [[Role Infrastructure Manager|Infrastructure Manager]], [[Role VO Admin|VO Admin]] or [[Role VRE Manager|VRE Manager]] exploiting the facilities offered on each VO/VRE by the Resource Management portlet. | ||
Latest revision as of 18:18, 27 March 2018
Contents
Downtime Declaration
Any scheduled downtime must be announced in advance to the user communities. The announcement is done by the Infrastructure Manager, VO Admin or VRE Manager exploiting the facilities offered on each VOVirtual Organization;/VREVirtual Research Environment. by the Resource Management portlet.
The downtime can be caused by (1) an infrastructure/VOVirtual Organization;/VREVirtual Research Environment. upgrade or (2) the unavailability of resources (check below). In this second case, different procedures apply whether the unavailability affects gCube, Hadoop or Runtime resources. In any case, the Infrastructure Manager, VO Admin or VRE Manager must analyze the impact of the unavailability and declare the appropriate downtime.
Information about all declared scheduled downtimes is gathered here.
