Procedure Downtime Declaration
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, gLite Hadoop or Runtime resources. In any case, the Infrastructure Manager, VO Admin or VRE Manager must analyse the impact of the unavailability and declare the appropriate downtime.
Information about all declared scheduled downtimes is gathered here.
During the iMarine project the Downtime procedure will be enhanced with a new tool which will be made available to Site Managers. The GOCDB tool has been adopted and enhanced in order to meet the requirements of EGEE first and EGI project then, and it's a quite useful tool to store the infrastructure topology and manage the related downtimes. It's the tool already used in iMarine to report gLite Resources downtime, and it will be extended as well to gCube, Hadoop and Runtime Resources.
The tools will be installed in the context of iMarine and the procedure for Downtime reporting will be updated accordingly. With the installation of the service also a new interface reporting the past, ongoing and future downtimes will be available, therefore the wiki page for Resource Downtimes will become obsolete. The following is an example of the visualization interface offered by the service.
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.
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.
