Difference between revisions of "Ticket generator Top-BDII"
Jump to navigation
Jump to search
Line 2: | Line 2: | ||
{{Template:GO menubar}} {{TOC_right}} | {{Template:GO menubar}} {{TOC_right}} | ||
[[Category: | [[Category:Infrastructure_Oversight]] | ||
= How to use ticket generator for WI04 (core services followup) = | = How to use ticket generator for WI04 (core services followup) = |
Latest revision as of 14:48, 23 October 2014
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
EGI Infrastructure Operations Oversight menu: | Home • | EGI.eu Operations Team • | Regional Operators (ROD) |
How to use ticket generator for WI04 (core services followup)
Configure the script.
In start-bdii.pl file at the beginning of the script you have to fill in following variable:
# PRODUCTION my $endpoint = "https://prod-ars.ggus.eu/arsys/services/ARService?server=prod-ars&webService=Grid_HelpDesk"; my $user = ""; # login to GGUS web-services my $pass = ""; # password to GGUS web-services # Submitter data, Those data will be used as submitter's data to create tickets my $Mail = ""; # your email address my $DN = ""; # your DN my $Name = ""; # Name and Surname
- Prepare input file.
The input plain file format for the scripts is as follow:
ROC/NGI support unit in GGUS; Availability; Reliability;
Remember that in each line should be one site and the number of semicolons should be always 3.
example:
NGI_PL; 50%; 10%; NGI_NL; 15%; 3%;
- Execute the tool
Login to machine with perl installed and execute the script as follow:
perl start-bdii.pl PARENT_TICKET_ID "DATE" FILE_NAME
PARENT_TICKET_ID - number of the ticket created by COO to handle the report
DATE - date of the report. Format: "month year"
FILE_NAME - file with input data
example:
perl start-bdii.pl 4121 "May 2010" dane.txt