Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

Difference between revisions of "NGI HU:Main Page"

From EGIWiki
Jump to navigation Jump to search
Line 22: Line 22:
{| border="1"
{| border="1"
|+  
|+  
!  !! Institute/Organization !! Shift starts on
! Institute/Organization !! Shift starts on
|-
|-
! SZTAKI:
! SZTAKI
|30. August -3. Septermber 2010
|30. August -3. Septermber 2010
|-
|-
Line 30: Line 30:
| 6. September - 10. Septermber 2010
| 6. September - 10. Septermber 2010
|-
|-
! NGI manager mailing list
! SZTAKI
| [[File:ngi_manager.png|180px]]||
|13. September – 17. Septermber 2010
|-
|-
! NGI security officer contact data
! NGI security officer contact data

Revision as of 20:23, 31 August 2010

The Hungarian Grid Initiative.


Organisational Structure

Member institutes:


User support shifts

Recognizing that improvements in the quality and shaping-up of the NGI_HU infrastructure is an important and ongoing effort, necessary for the successful work of application developers, as well as for the usage of our infrastructure by the existing user community, the pro-active monitoring of the NGI_HU sites is organized in rotating shifts taken by BME and SZTAKI representatives.

Basically, the idea is that each institute is on shift during one week, and opens tickets in GGUS.

Details of the organization of the shifts are given below, and will be updated according to the available information.


Institute/Organization Shift starts on
SZTAKI 30. August -3. Septermber 2010
BME 6. September - 10. Septermber 2010
SZTAKI 13. September – 17. Septermber 2010
NGI security officer contact data File:Roczei.png Gabor Roczei / NIIF
NGI security mailing list File:Ngi security.png
ROD team mailing list File:Ngi rod.png
Mailing list for GGUs tickets if using GGUS directly File:Ngi ggus.png
User support mailing list File:Ngi support.png



Hand-over report

When creating a shift ticket to initiate a hand-over at the end of the week, previous shift provider should open a new ticket and enter brief hand-over report, i.e. list of major problems that remain to be solved, observations about some hard cases, number of newly created tickets during the last week, overall number of tickets still open, number of tickets closed last week, etc. (2 paragraphs at most usually). On Monday the next shift provider should close the ticket, acknowledging the hand-over.

External Links