Procedure Downtime Declaration

From D4Science Wiki
Revision as of 13:12, 8 December 2011 by Andrea.manzi (Talk | contribs)

Jump to: navigation, search

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 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 Resources

The unavailability of gCube resources 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 resources.


gLite Resources

The unavailability of gLite resources 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 Resources

The unavailability of Hadoop resources 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 resources.

Runtime Resources

The unavailability of Runtime resources 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 resources.