Difference between revisions of "Procedure Downtime Declaration"

From D4Science Wiki
Jump to: navigation, search
 
(11 intermediate revisions by 2 users not shown)
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.
  
 
[[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 resources (check below). In this second case, different procedures apply whether the unavailability affects gCube, gLite 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 analyse the impact of the unavailability and declare the appropriate downtime.
+
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.
  
 
Information about all declared scheduled downtimes is gathered [[Resources Downtimes|here]].
 
Information about all declared scheduled downtimes is gathered [[Resources Downtimes|here]].
  
−
== gCube Resources ==
+
[[Image:gocdb.png|centre]]
−
 
+
−
The unavailability of gCube resources must be declared by the [[Role Site Manager|Site Manager]] by sending an email to the [mailto:wp5@imarine.research-infrastructures.eu WP5] mailing list. The email must contain information about the unavailability duration as well as a list of the affected resources.
+
−
 
+
−
== gLite Resources ==
+
−
 
+
−
The unavailability of gLite resources must be declared by the [[Role Site Manager|Site Manager]] following the EGI [https://wiki.egi.eu/wiki/GOCDB/Input_System_User_Documentation#Downtimes  downtime] procedure. [[Role Site Manager|Site Managers]] must declare the unavailability using the [http://goc.egi.eu/ GOCDB] website in the section related to their site.
+
−
 
+
−
== Hadoop Resources ==
+
−
 
+
−
The unavailability of Hadoop resources must be declared by the [[Role Site Manager|Site Manager]] by sending an email to the [mailto:wp5@imarine.research-infrastructures.eu WP5] mailing list. The email must contain information about the unavailability duration as well as a list of the affected resources.
+
−
 
+
−
== Runtime Resources ==
+
−
 
+
−
The unavailability of Runtime resources must be declared by the [[Role Site Manager|Site Manager]] by sending an email to the [mailto:wp5@imarine.research-infrastructures.eu WP5] mailing list. The email must contain information about the unavailability duration as well as a list of the affected resources.
+

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
Retrieved from "https://wiki.d4science.org/index.php?title=Procedure_Downtime_Declaration&oldid=21697"