Difference between revisions of "Procedure Downtime Declaration"

From D4Science Wiki
Jump to: navigation, search
 
(19 intermediate revisions by 2 users not shown)
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  Manager|VO Manager]] or  [[Role VRE Manager|VRE Manager]] exploiting the facilities offered on each VO/VRE by the Resource Management portlet.
+
__TOC__
  
[[EcosystemDowntime.png|centre]]
+
== Downtime Declaration ==
  
The downtime of the infrastructure can be caused by (1) an infrastructure 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]] must analyse the impact of the nodes unavailability and declare the appropriate infrastructure downtime.
+
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.
  
Information about all declared scheduled downtimes is gathered [[SA1 Nodes Downtimes|here]].
+
[[Image:EcosystemDowntime.png|centre]]  
  
 +
The downtime can be caused by (1) an infrastructure/VO/VRE 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 [[Role Infrastructure Manager|Infrastructure Manager]], [[Role VO  Admin|VO Admin]] or  [[Role VRE Manager|VRE Manager]] must analyze the impact of the unavailability and declare the appropriate downtime.
  
== gCube Nodes ==
+
Information about all declared scheduled downtimes is gathered [[Resources Downtimes|here]].
  
The unavailability of gCube nodes must be declared by the [[Role Site Manager|Site Manager]] by sending an email to the [mailto:sa1@d4science-ii.research-infrastructures.eu SA1] mailing list. The email must contain information about the unavailability duration as well as a list of the affected nodes.
+
[[Image:gocdb.png|centre]]
 
+
 
+
== gLite Nodes ==
+
 
+
The unavailability of gLite nodes must be declared by the [[Role Site Manager|Site Manager]] following the EGI [http://cic.gridops.org/index.php?section=home&page=SDprocedure downtime] procedure. [[Role Site Manager|Site Managers]] must declare the unavailability using the [https://goc.gridops.org/ GOCDB] website in the section related to their site.
+
 
+
 
+
== Hadoop Nodes ==
+
 
+
The unavailability of Hadoop nodes must be declared by the [[Role Site Manager|Site Manager]] by sending an email to the [mailto:sa1@d4science-ii.research-infrastructures.eu SA1] mailing list. The email must contain information about the unavailability duration as well as a list of the affected nodes.
+

Latest revision as of 19:18, 27 March 2018

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.

EcosystemDowntime.png

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.

Gocdb.png