Difference between revisions of "Procedure Downtime Declaration"
Andrea.manzi (Talk | contribs) |
Andrea.manzi (Talk | contribs) |
||
| Line 1: | Line 1: | ||
| − | 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 | + | 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. |
[[Image:EcosystemDowntime.png|centre]] | [[Image:EcosystemDowntime.png|centre]] | ||
| − | The downtime can be caused by (1) an infrastructure/VO/VRE upgrade or (2) the unavailability of nodes (check below). In this second case, different procedures apply whether the unavailability affects gCube nodes, gLite nodes or Hadoop nodes. In any case, the [[Role Infrastructure Manager|Infrastructure Manager]], [[Role VO | + | The downtime can be caused by (1) an infrastructure/VO/VRE upgrade or (2) the unavailability of nodes (check below). In this second case, different procedures apply whether the unavailability affects gCube nodes, gLite nodes or Hadoop nodes. In any case, the [[Role Infrastructure Manager|Infrastructure Manager]], [[Role VO Admin|VO Admin]] or [[Role VRE Manager|VRE Manager]] must analyse the impact of the nodes unavailability and declare the appropriate downtime. |
Information about all declared scheduled downtimes is gathered [[Resources Downtimes|here]]. | Information about all declared scheduled downtimes is gathered [[Resources Downtimes|here]]. | ||
Revision as of 11:44, 8 December 2011
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 nodes (check below). In this second case, different procedures apply whether the unavailability affects gCube nodes, gLite nodes or Hadoop nodes. In any case, the Infrastructure Manager, VO Admin or VRE Manager must analyse the impact of the nodes unavailability and declare the appropriate downtime.
Information about all declared scheduled downtimes is gathered here.
gCube Nodes
The unavailability of gCube nodes must be declared by the Site Manager by sending an email to the WP5 mailing list. The email must contain information about the unavailability duration as well as a list of the affected nodes.
gLite Nodes
The unavailability of gLite nodes must be declared by the Site Manager following the EGI downtime procedure. Site Managers must declare the unavailability using the GOCDB website in the section related to their site.
Hadoop Nodes
The unavailability of Hadoop nodes must be declared by the Site Manager by sending an email to the WP5 mailing list. The email must contain information about the unavailability duration as well as a list of the affected nodes.
