https://wiki.egi.eu/w/api.php?action=feedcontributions&user=Vgkamas&feedformat=atomEGIWiki - User contributions [en]2024-03-29T11:41:42ZUser contributionsMediaWiki 1.37.1https://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR16&diff=66852EGI-InSPIRE:Greece-US-QR162014-04-23T13:59:49Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|QR16<br />
|NGI_GRNET<br />
|GRNET<br />
|Gkamas Vasileios<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day-to-day user support.<br />
* Solving problems at the SOAP interface used for the communication between HellasGrid RT and GGUS.<br />
* Support of Shibboleth authentication at the HellasGrid WS-PGRADE portal using the AAI infrastructure of GRNET.<br />
<br />
===2.2. Plans===<br />
<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR15&diff=63658EGI-InSPIRE:Greece-US-QR152014-01-20T09:02:53Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|QR15<br />
|NGI_GRNET<br />
|GRNET<br />
|Gkamas Vasileios<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day-to-day user support.<br />
* Solving problems at the SOAP interface used for the communication between HellasGrid RT and GGUS.<br />
<br />
===2.2. Plans===<br />
* Support of Shibboleth authentication at the HellasGrid WS-PGRADE portal using the AAI infrastructure of GRNET.<br />
* Installation of the Dirac service for HellasGrid users.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR14&diff=61040EGI-InSPIRE:Greece-US-QR142013-10-23T11:06:42Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|QR14<br />
|NGI_GRNET<br />
|GRNET<br />
|Gkamas Vasileios<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day-to-day user support.<br />
* Update the HellasGrid WS-PGRADE portal to its latest version.<br />
<br />
===2.2. Plans===<br />
* Installation of WRF for Scientific Gateway (WRF4SG) as extension of WS-PGRADE portal.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR14&diff=61035EGI-InSPIRE:Greece-US-QR142013-10-23T11:03:19Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day-to-day user support.<br />
* Update the HellasGrid WS-PGRADE portal to its latest version.<br />
<br />
===2.2. Plans===<br />
* Installation of WRF for Scientific Gateway (WRF4SG) as extension of WS-PGRADE portal.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR14&diff=61034EGI-InSPIRE:Greece-US-QR142013-10-23T11:01:47Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day-to-day user support.<br />
* Solving problems dealing with the functionality of WS-PGRADE portal.<br />
* Restore the broken interface between GGUS and HellasGrid RT<br />
<br />
===2.2. Plans===<br />
* Update the HellasGrid WS-PGRADE portal to its latest version.<br />
* Installation of WRF for Scientific Gateway (WRF4SG) as extension of WS-PGRADE portal.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR13&diff=58341EGI-InSPIRE:Greece-US-QR132013-07-25T08:41:20Z<p>Vgkamas: /* 2.1. User Support achievements */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|QR13<br />
|NGI_GRNET<br />
|GRNET<br />
|Gkamas Vasileios, Giannakopoulou Kalliopi<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day-to-day user support.<br />
* Solving problems dealing with the functionality of WS-PGRADE portal.<br />
* Restore the broken interface between GGUS and HellasGrid RT<br />
<br />
===2.2. Plans===<br />
* Update the HellasGrid WS-PGRADE portal to its latest version.<br />
* Installation of WRF for Scientific Gateway (WRF4SG) as extension of WS-PGRADE portal.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR13&diff=58339EGI-InSPIRE:Greece-US-QR132013-07-25T08:38:54Z<p>Vgkamas: /* 2.2. Plans */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|QR13<br />
|NGI_GRNET<br />
|GRNET<br />
|Gkamas Vasileios, Giannakopoulou Kalliopi<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day to day user support.<br />
* Solving problems dealing with the functionality of WS-PGRADE portal.<br />
* Restore the broken interface between GGUS and HellasGrid RT<br />
<br />
===2.2. Plans===<br />
* Update the HellasGrid WS-PGRADE portal to its latest version.<br />
* Installation of WRF for Scientific Gateway (WRF4SG) as extension of WS-PGRADE portal.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR13&diff=58338EGI-InSPIRE:Greece-US-QR132013-07-25T08:35:28Z<p>Vgkamas: /* 2.1. User Support achievements */</p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|QR13<br />
|NGI_GRNET<br />
|GRNET<br />
|Gkamas Vasileios, Giannakopoulou Kalliopi<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
* Day to day user support.<br />
* Solving problems dealing with the functionality of WS-PGRADE portal.<br />
* Restore the broken interface between GGUS and HellasGrid RT<br />
<br />
===2.2. Plans===<br />
* Update of the HellasGrid WS-PGRADE portal to its latest version.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR12&diff=54320EGI-InSPIRE:Greece-US-QR122013-04-25T07:32:12Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
* Official announcement of the HellasGrid WS-PGRADE portal to the HellasGrid users.<br />
<br />
* Update of the HellasGrid site.<br />
<br />
* Day to day user support.<br />
<br />
===2.2. Plans===<br />
<br />
* Update of the HellasGrid WS-PGRADE portal to its latest version.<br />
<br />
* Implementation of Shibboleth authentication at HellasGrid WS-PGRADE portal using the AAI infrastructure of GRNET.<br />
<br />
* Publication of HellasGrid newsletter at tri-monthly basis.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR12&diff=54319EGI-InSPIRE:Greece-US-QR122013-04-25T07:30:43Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
* Official announcement of the HellasGrid WS-PGRADE portal to the HellasGrid users.<br />
<br />
* Update of the HellasGrid site.<br />
<br />
* Day to day user support.<br />
<br />
===2.2. Plans===<br />
<br />
* Update of the HellasGrid WS-PGRADE portal to its latest version.<br />
<br />
* Implementation of Shibboleth authentication at HellasGrid WS-PGRADE portal using the AAI infrastructure of GRNET.<br />
<br />
* HellasGrid newsletter publication at tri-monthly basis.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR11&diff=49783EGI-InSPIRE:Greece-US-QR112013-01-21T09:56:17Z<p>Vgkamas: </p>
<hr />
<div>{{Template:Op menubar}}<br />
{{Template:Inspire_reports_menubar}}<br />
{{TOC_right}}<br />
[[Category:NGI US QR Reports]]<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author<br />
|-<br />
| QR11<br />
| NGI_GRNET<br />
| GRNET<br />
| Gkamas Vasileios, Giannakopoulou Kalliopi<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| class="wikitable"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
* Problems dealing with the functionality of WS-PGRADE have been solved.<br />
<br />
* Update of the HellasGrid site with the software packages installed at the various HellasGrid clusters.<br />
<br />
* Day to day user support.<br />
<br />
===2.2. Plans===<br />
<br />
* Official announcement of the HellasGrid WS-PGRADE portal to the HellasGrid users.<br />
<br />
* Provision of credentials for accessing the HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). <br />
These credentials will be also used for accessing the HellasGrid User Interfaces.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| class="wikitable"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44481EGI-InSPIRE:Greece-US-QR102012-11-02T13:48:11Z<p>Vgkamas: /* 2.1. User Support achievements */</p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number <br />
!scope="col"| NGI Name <br />
!scope="col"| Partner Name <br />
!scope="col"| Author <br />
|-<br />
| QR10<br />
| NGI_GRNET<br />
| GRNET<br />
| Gkamas Vasileios<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
1. Installation of software packages OPEMFOAM (http://www.openfoam.com/), ROOT (http://root.cern.ch/drupal/), GEANT4 (http://geant4.cern.ch/) and RegCM (http://gforge.ictp.it/gf/project/regcm/) at the HellasGrid sites.<br />
<br />
2. Solving of various problems concerning the WS-PGΡADE portal.<br />
<br />
3. Update of the SOAP interface between the GGUS and HellasGrid Request Tracker.<br />
<br />
===2.2. Plans===<br />
<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44480EGI-InSPIRE:Greece-US-QR102012-11-02T13:40:47Z<p>Vgkamas: </p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number <br />
!scope="col"| NGI Name <br />
!scope="col"| Partner Name <br />
!scope="col"| Author <br />
|-<br />
| QR10<br />
| NGI_GRNET<br />
| GRNET<br />
| Gkamas Vasileios<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
1. Participation of the HellasGrid User Support Team, at the Virtual Team "Science Gateway Primer" as NGI_GRNET representative.<br />
<br />
2. Solving of various problems concerning the WS-PGΡADE portal.<br />
<br />
3. Update of the SOAP interface between the GGUS and HellasGrid Request Tracker.<br />
<br />
===2.2. Plans===<br />
<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44479EGI-InSPIRE:Greece-US-QR102012-11-02T13:38:37Z<p>Vgkamas: </p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number <br />
!scope="col"| NGI Name <br />
!scope="col"| Partner Name <br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
1. Participation of the HellasGrid User Support Team, at the Virtual Team "Science Gateway Primer" as NGI_GRNET representative.<br />
<br />
2. Solving of various problems concerning the WS-PGΡADE portal.<br />
<br />
3. Update of the SOAP interface between the GGUS and HellasGrid Request Tracker.<br />
<br />
===2.2. Plans===<br />
<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44478EGI-InSPIRE:Greece-US-QR102012-11-02T13:36:43Z<p>Vgkamas: /* 2.2. Plans */</p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
1. Participation of the HellasGrid User Support Team, at the Virtual Team "Science Gateway Primer" as NGI_GRNET representative.<br />
<br />
2. Solving of various problems concerning the WS-PGΡADE portal.<br />
<br />
3. Update of the SOAP interface between the GGUS and HellasGrid Request Tracker.<br />
<br />
===2.2. Plans===<br />
<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44476EGI-InSPIRE:Greece-US-QR102012-11-02T13:34:43Z<p>Vgkamas: /* 2.1. User Support achievements */</p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
1. Participation of the HellasGrid User Support Team, at the Virtual Team "Science Gateway Primer" as NGI_GRNET representative.<br />
<br />
2. Solving of various problems concerning the WS-PGΡADE portal.<br />
<br />
3. Update of the SOAP interface between the GGUS and HellasGrid Request Tracker.<br />
<br />
===2.2. Plans===<br />
Our plans include:<br />
<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44475EGI-InSPIRE:Greece-US-QR102012-11-02T13:28:47Z<p>Vgkamas: /* 2.1. User Support achievements */</p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
<br />
1. Participation of the HellasGrid User Support Team, at the Virtual Team "Science Gateway Primer" as NGI_GRNET representative.<br />
2. Solving of various problems concerning the WS-PGΡADE portal.<br />
3. Update of the SOAP interface between the GGUS and HellasGrid Request Tracker.<br />
<br />
===2.2. Plans===<br />
Our plans include:<br />
<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44473EGI-InSPIRE:Greece-US-QR102012-11-02T13:27:54Z<p>Vgkamas: /* 2.2. Plans */</p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
===2.2. Plans===<br />
Our plans include:<br />
<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Greece-US-QR10&diff=44472EGI-InSPIRE:Greece-US-QR102012-11-02T13:26:49Z<p>Vgkamas: /* 2.2. Plans */</p>
<hr />
<div>[[Category:NGI QR Reports]]<br />
<br />
<!-- VERY IMPORTANT<br />
This report covers support activities to existing user communities, and belongs to EGI-InSPIRE SA1 (Task SA1.7 - Support Teams). The outreach to new communities activities that NGIs perform under NA2 are gathered through the Virtual Teams. However, there may be outreach activities that do outside of VTs. You can report about these in your 2.2.3 paragraph as well.<br />
Please check the previous quarterly report to see the type of input I expect: https://documents.egi.eu/document/999. <br />
--><br />
<br />
__NOTOC__<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Quarterly Report Number<br />
!scope="col"| NGI Name<br />
!scope="col"| Partner Name<br />
!scope="col"| Author <br />
|-<br />
|<br />
|<br />
|<br />
|<br />
|-<br />
|}<br />
<br />
<!-- <br />
Fill the second line of the table replacing the <...> stuff with your data.<br />
--><br />
<br />
==1. MEETINGS AND DISSEMINATION ==<br />
<!--=====GENERAL GUIDELINES FOR ALL EVENTS REPORTED IN THE FOLLOWING SECTIONS:=====<br />
*please do not provide a list of participants, only give the number of people that attended<br />
*for outcome, please list tangible agreements, decisions instead of listing program points or presentations you made. (Do not write just that "X gave a presentation about Y" <br />
*include your local events only if there was any EGI-related topic on the agenda<br />
*provide an indico URL to your presentation (if available) or to the event itself.<br />
**If your presentation is not available online, please send the slides to erika.swiderski@egi.eu. <br />
Note1: Complete the tables below by adding as many rows as needed. <br />
Note2: Complete the tables below by adding as many rows as needed. <br />
--><br />
<br />
===1.1. CONFERENCES/WORKSHOPS ORGANISED===<br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
<!-- |+Provided by each SA1 partner. Just report events relevant to SA1 activities.--><br />
|-<br />
!scope="col"|Date||Location||Title||Participants||Outcome (Short report & Indico URL) <br />
|-<br />
|<br />
|<br />
|<br />
| <br />
|<br />
|-<br />
|}<br />
<br />
<br />
===1.3. PUBLICATIONS===<br />
<!--List all publications as bullet points, detailing: Publication title, author(s), journal title, number/issue, date. Also mention any articles published further to interviews given by members of your activity.--><br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"|Publication title||Journal / Proceedings title||align="left" |Journal references<br> ''Volume number<br> Issue<br><br>Pages from - to''||align="left" |Authors ''<br>1.<br>2.<br>3.<br>Et al?''<br />
|-<br />
|}<br />
<br />
== 2. ACTIVITY REPORT ==<br />
<!--''Note: just report activities relevant to this Quarter.''--><br />
<br />
===2.1. User Support achievements===<br />
===2.2. Plans===<br />
Our plans include:<br />
1. The provision of credentials for access to HellasGrid WS-PGRADE portal through the HellasGrid access site (https://access.hellasgrid.gr). These credentials will be also used for access to the HellasGrid User Interfaces.<br />
2. The update of the HellasGrid site with the software packages installed at the various HellasGrid sites.<br />
<br />
===2.3. Issues and mitigation===<br />
<!-- Describe any issue here that you were unable to resolve with the processes and mechanisms that exist within the project. Describe issues that can delay or can have other types of negative effect on the delivery of User Support activities. --><br />
<br />
<br />
{| border="1" cellspacing="0" cellpadding="2"<br />
|-<br />
!scope="col"| Issue Description<br />
!scope="col"| Mitigation Description<br />
|-<br />
|}<br />
<br />
<!--<br />
Please, fill the table below. You can add a line copyng the two lines<br />
|-<br />
| Issue Description || Issue mitigation<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=VT_Science_Gateway_Primer&diff=37580VT Science Gateway Primer2012-06-13T14:06:57Z<p>Vgkamas: </p>
<hr />
<div><!--<br />
{{Template:EGICompendium_menubar}} {{TOC_right}} <br />
<br />
<br />
{{Finished VirtualTeamProject | <br />
--><br />
{{VirtualTeamProject | <br />
VTP_Leader = open call |<br />
VTP_ML = vt-science-gateway-primer@mailman.egi.eu |<br />
VTP_Status = Running |<br />
VTP_StartDate = 16/05/2012 |<br />
VTP_EndDate = not decided yet (max 6 months) | <br />
VTP_Meetings = [http://wiki.egi.eu/wiki/VT_Science_Gateway_Primer/meetings see dedicated page]<br />
<!--<br />
[[VT_EGI_Compendium_Meetings| see dedicated page]]<br />
--><br />
|<br />
VTP_Motivation = An EGI science gateway is a community-specific set of tools, applications, and data collections that are integrated together via a web portal or a desktop application, providing access to resources and services from the European Grid Infrastructure. These gateways can support a variety of community-specific capabilities including workflows, virtualisation of software and hardware, visualization, resource discovery, job execution, access to data collections, repositories, applications and tools. A science gateway enables community members to define and perform custom research scenarios. Science gateways can hide the complexities of distributed infrastructures from researchers, therefore several communities build or would like to build science gateways for their members. <br />
<br />
The EGI.eu User Community Support Team together with its partners from the NGIs and VRCs has already setup dedicated webpages to present basic information about [http://www.egi.eu/services/support/science-gateways/science_gateways_for_users.html ready to use science gateways] and about [http://www.egi.eu/services/support/science-gateways/science_gateways_for_developers.html science gateway enabling technologies] for gateway developers. However, identifying the right set of technologies from this set, collecting and applying best practices and solutions to have a science domain specific gateway can be still a difficult task for some. This VT aims to help gateway developers and provide an 'EGI gateway primer', a manual that collects useful and up to date information from the EGI community about science gateway development. <br />
|<br />
VTP_Output = <br />
The expected outputs of the project are:<br />
# Up to date and complete information in the EGI Application Database about EGI science gateways and science gateway enabling technologies<br />
# Recommendations on how to improve the data structure of the EGI Application Database and the EGI website to better support science gateway developers<br />
# A comprehensive document, an 'EGI gateway primer', that collects information about technologies, policies, solutions that exist from the EGI community for gateway developers.<br />
<br />
| <br />
VTP_Tasks = <br />
# Check, and if needed sanitise the information that is presented about science gateways and science gateway enabling technologies on the EGI website from the EGI Applications Database<br />
# Make recommendations for data structure updates in the EGI Applications Database in order to better support science gateway users and developers<br />
# Define the structure (Table of content) of the EGI gateway primer<br />
# Collect and integrate contributions in the EGI gateway primer<br />
# Promote the EGI gateway primer to existing and to new EGI communities<br />
<br />
<!--<br />
([[VT_EGI_Compendium_Tasks|see dedicated page]])<br />
--><br />
|<br />
VTP_Team =<br />
Email nuno.ferreira@egi.eu if you wish to join. <br />
<br />
Leader: <br />
* To be decided (open call)<br />
EGI.eu support:<br />
* Nuno Ferreira, [http://www.egi.eu EGI.eu] (EGI.eu)<br />
<br />
Members:<br />
* Armenia<br />
**Hrachya Astsatryan (NGI_AM)<br />
<br />
* France:<br />
** Tristan Glatard, LSGC VRC<br />
<br />
*Greece<br />
**Giannakopoulou Kalliopi (NGI_GRNET/CTI)<br />
**Gkamas Vasilis (NGI_GRNET/CTI)<br />
<br />
* Hungary:<br />
** Peter Kacsuk, [http://www.lpds.sztaki.hu MTA SZTAKI] ([http://www.sci-bus.eu/ SCI-BUS] project coordinator)<br />
** Agnes Szeberenyi, (NGI Hungary, MTA SZTAKI)<br />
<br />
*Ireland:<br />
**David O'Callaghan (NGI_IE NIL)<br />
<br />
* Italy:<br />
** Roberto Barbera, (University of Catania and INFN)<br />
** Riccardo Bruno, (Consorzio COMETA)<br />
** Riccardo Rotondo, (University of Catania and INFN)<br />
** Giuseppe La Rocca (INFN)<br />
** Diego Scardaci (INFN)<br />
** Valeria Ardizzone (INFN)<br />
<br />
*Netherlands:<br />
** Shayan Shahand, [http://www.amc.nl Academisch Medisch Centrum]<br />
** Gergely Sipos, [http://www.egi.eu EGI.eu] (EGI.eu)<br />
** Karolis Eigelis, [http://www.egi.eu EGI.eu] (EGI.eu)<br />
<br />
*Poland<br />
**Mariusz Sterzel, (NGI_PL, ACC Cyfronet)<br />
<br />
*Singapore<br />
** Muhammad Farhan Sjaugi (SCI-BUS subcontractor)<br />
<br />
*Spain:<br />
** Rubén Vallés Pérez, University of Zaragoza - [http://bifi.es/en/ BIFI] (SCI-BUS dissemination WP leader)<br />
** Elisa Cauhé Martín, University of Zaragoza - [http://bifi.es/en/ BIFI] <br />
** Ricardo Graciani, University of Barcelona (DIRAC project co-Coordinator, developer, deployment, User and Community support)<br />
<br />
* Switzerland:<br />
** Sergio Maffioletti, (UZH)<br />
<br />
* Taiwan<br />
** Hsin-Yen Chen (ASGC)<br />
** Eric Yen (ASGC)<br />
** Vicky Huang (ASGC)<br />
<br />
* UK:<br />
** Tamas Kiss, [http://www.westminster.ac.uk/home University of Westminster] (SCI-BUS User Support WP leader)<br />
<br />
* Ukraine <br />
**Yuri Gordienko (SCI-BUS subcontractor)<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
|<br />
VTP_Resources = <br />
* Proposed Table of content of the EGI gateway primer: [[EGI gateway primer ToC]]<br />
* EGI portal-community email list: <portal-community@mailman.egi.eu>, https://www.egi.eu/sso/groupView/portal-community<br />
* Information about science gateways on the EGI website: http://www.egi.eu/services/support/science-gateways/index.html<br />
|<br />
VTP_Progress = <br />
}} <br />
<br />
<!--<br />
[[Category:EGI_Compendium]]<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:TNA3.3_NGI_User_Support_Teams&diff=18608EGI-InSPIRE:TNA3.3 NGI User Support Teams2011-06-02T15:20:20Z<p>Vgkamas: /* User Support contacts in the NGIs */</p>
<hr />
<div>==Role of NGI User Support Teams in TNA3.3 ==<br />
The main actors of EGI are the National Grid Initiatives (NGIs) whose work is coordinated by the EGI.eu organisation. NGIs ensure the operation of the grid infrastructures and support services in each country as well as a transparent representation of the requirements of all their scientific communities. The primary responsibility of the User Support Teams (USTs) of the NGIs is to provide services for users that help these users integrate/establish self-sustainable EGI user communities. These services provided by NGI USTs belong to TNA3.3. The services include (but are not restricted to):<br />
* '''Identifying new users and new user communities'''<br />
* '''Consultancy:''' NGI USTs provide technical advice on the infrastructure and support services available to users and on the various DCI technologies that EGI could provide access to in order to support their research activities. NGIs are expected to engage with national scientific communities and catalyze grid uptake within the country. After the first contact is made with a new community, consultancy is typically the next service required. <br />
* '''Training''': Many NGIs provide their own training team and facilities for users. These NGI teams provide courses at various levels and with different scope. While short events only give a brief introduction for new users, longer courses include hands-on sessions and provide attendees with a deep knowledge on specific services and tools.<br />
* '''Porting scientific applications to the infrastructure''': Experts within the NGIs are available to support users in the integration of new applications into the production infrastructure. This activity involves an analysis of the existing software, an analysis of the users’ expectations and needs, defining porting scenarios, then coding, testing and finally documenting the application. For the sake of other users NGI teams also assist with sharing the grid-enabled applications with the EGI community through the application database.<br />
* '''Arranging access for users to EGI applications''': The fastest and easiest way to use the grid is to access the already grid-enabled applications. NGIs can help users access and use applications from other communities, applications that are available in the EGI application database. <br />
* '''Supporting new VOs''': Virtual Organisations represent the collaboration of people and computers on the grid. VOs can be setup for the purpose of a single grid application, to support scientists from the same field or for researchers who work in the same geographic region. NGIs can provide users with information about existing VOs, about the processes of joining VOs, or setting up a new VO if the scope of existing VOs is not in line with the users’ scientific goals. NGIs can also assist in the allocation of computing, storage and other types of resources into VOs.<br />
* '''Developing new software services (portals, toolkits, middleware extensions, etc.)''': Most scientific collaborations and VOs require additional elements in the infrastructure to fully exploit the capabilities of their scientific applications. The integration of new infrastructure services, new portal interfaces, new programming frameworks or toolkits require deep knowledge of the existing architecture. NGIs can help users during this process, by allocating experts who can assist these users during the development, testing and integration of the components.<br />
* '''Collecting feedback''' (which is then evaluated and prioritised by TNA3.2): NGI USTs engage with user communities within their countries, monitor their development and collect feedback from them on the services and features of EGI. This feedback is collected and prioritised by EGI.eu than forwarded to the middleware developer and infrastructure operator teams, who incorporate the requested changes into the EGI roadmap. <br />
* '''Improving documentation''': Documentations on the infrastructure, its components and services are available for users at various levels. Experts in the NGI help users find appropriate documentation and contribute to new documentation as new technologies and procedures become available, or gaps in current documentation is found.<br />
* '''Providing helpdesk''': NGIs provide support personnel who can answer and deal with day-to-day issues that users find and experience during using the infrastructure. This helpdesk is available for users through a central Web portal where requests and answers can be accessed. <br />
* '''Fostering the integration of communities''' (identified by TNA3.2): The integration of scientific communities is carried out by establishing Virtual Research Communities (VRCs). VRCs represent sustainable, key customers for EGI. The VRC accreditation process is managed by EGI.eu UCST.<br />
<br />
<br />
<br />
=== What is expected from NGI User Support Teams? ===<br />
There are a number of formal and informal documents that members of NGI User Support Teams need to read in order to gain a thorough understanding of the user support activities of EGI. Many of these are reports that are produced as part of the official activities dictated by the Description of Work (DoW) for EGI-InSPIRE. The DoW defines many of our activities for the four years of the InSPIRE project.<br />
<br />
NGI User Support Teams, primarily the [https://wiki.egi.eu/wiki/TNA3.3_NGI_User_Support_Teams#User_Support_contacts_in_the_NGIs main contacts] are expected to be familiar with these resources:<br />
<br />
* EGI Web site - http://www.egi.eu/<br />
* the User support section of the website: http://egi.eu/user-support/<br />
* (NA3 section of) EGI-InSPIRE Description of Work<br />
* D3.1 document - User Community Support Process – a detailed overview: https://documents.egi.eu/document/106<br />
* MS305 - User Feedback and Recommendations – an excellent overview of the requirements gathering process and summary of the requirements captured at this point in the project: https://documents.egi.eu/document/211<br />
* NA3 Wiki: https://wiki.egi.eu/wiki/WP3:_User_Community_Coordination<br />
<br />
Optional readings:<br />
* Minutes of UCB (User Community Board) https://documents.egi.eu/document/211: https://www.egi.eu/indico/categoryDisplay.py?categId=21<br />
* Minutes of USAG (User Services Advisory Group) meetings: https://www.egi.eu/indico/categoryDisplay.py?categId=38<br />
<br />
'''As a bare minimum''' it is expected that NGI User Support Teams are proactive in informing the rest of the community about new solutions, experiences and developments. There are number of ways to do so (see D3.1 document for details):<br />
* Register forthcoming training events into the [http://www.egi.eu/user-support/technical_services/ training calendar]<br />
* [https://documents.egi.eu/document/280 Report back] to EGI.eu about training events held<br />
* Register ported applications into the [http://www.egi.eu/user-support/technical_services/ EGI Application Database]<br />
* Post on the na3 email list: inspire-na3@mailman.egi.eu<br />
* Provide information about the user support services of [https://wiki.egi.eu/wiki/TNA3.3_NGI_User_Support_Teams#User-related_development_projects_inside_the_NGIs your NGI in the NA3 Wiki]<br />
* Communicate requirements, recommendations and needs to EGI through any of the [https://wiki.egi.eu/wiki/Requirements_gathering_details feedback channels]<br />
<br />
==Role of EGI.eu in TNA3.3==<br />
NGIs are heterogeneous in terms of the size and composition of their user communities, the size and expertise of their USTs. Consequently, NGIs are not equally active and strong in all the above listed user support fields. E.g. while an NGI UST can be very experienced with application porting, it may have less interest and knowledge on the development of grid portals for end users. On top of that the primary goal of EGI is to attract and serve multi-national, large user communities. To meet these demands the User Community Support Team (UCST) of EGI.eu monitors the status of NGI USTs and help NGIs <br />
* serve local users whose requirements exceed the expertise and capacity which is available locally; <br />
* serve international user communities by integrating the user support services and expertise of multiple NGI USTs;<br />
* identify and recommend best practices and tools for NGI USTs.<br />
<br />
The monitoring of NGIs is currently done through face to face and telephone interviews, online and email questionnaires. EGI.eu UCST aims to put a more efficient mechanism in place to simplify the monitoring process and to allow NGIs to "broadcast" relevant information about their user support status and services in an intelligent way to EGI.eu and other NGIs.<br />
<br />
== User Support contacts in the NGIs ==<br />
<br />
* EGI.eu maintains a list of NGI user support contacts. Please get in contact with your NGI's support contact in training, consultancy and other types of support. <br />
* If you cannot find your country in the list, or would like to add/correct your countries representative then please contact the User Community Support Team of EGI: '''ucst@egi.eu'''. <br />
* These persons are also subscribed to the email list '''ngi-ust-managers@mailman.egi.eu'''. List archive: https://mailman.egi.eu/mailman/private/ngi-ust-managers/ (available for list members only)<br />
<br />
<br />
{| style="border-spacing:0;"<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''Country'''<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''Name of main User''' <br />
'''Support Contact in the NGI'''<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''NGI user support contact (YES) <br>or<br> NGI technical contact (NO)'''<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Albania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Neki Frasheri<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Armenia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hrachya Astsatryan<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Belarus<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Oleg Tchij <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Belgium<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Rosette Vandenbrouck<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Bulgaria<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Aneta Karaivanova <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Cyprus<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Andoena Balla<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Croatia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ivan Maric (through email list)<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Czech Republic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ivana Krenkova<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Denmark<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Michael Gronager<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also for the whole Nordic region)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Finland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Pekka Lehtovuori<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| France<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Helene Cordier, Geneviève Romier <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Georgia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nugzar Gamtsemlidze, Ramaz Kvatadze<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Germany<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Sabine Reißer<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Greece<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vasileios Gkamas, Kostas Koumantaros<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hungary<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Imre Szeberenyi<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ireland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| David O'Callaghan, Stuart Kenny, John Walsh<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Israel<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nadav Grossaug, Arad Alper<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Italy<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Claudio Vuerli, Antonio Lagana, Luciano Milanesi, Laura Perini<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Latvia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Edgars Znots<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Lithuania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Rolandas Naujikas<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Former Yugoslav Republic of Macedonia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Anastas Misev<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Republic of Moldova<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nikolai P. Iliuha, Alexandr Golubev<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Montenegro<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Lidija Milosavljevic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Netherlands<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Machiel Jansen, Tom Visser<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Norway<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Jacko Koster<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Poland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Mariusz Sterzel, Maciej Filocha<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Portugal<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Gonçalo Borges<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Romania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Alexandru Stanciu<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Russian Federation<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Valeriy Kirichenko<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Serbia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vladimir Slavnic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Slovakia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ladislav Hluchy<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Slovenia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Barbara Krasovec<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Spain<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vicente Hernández<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Sweden<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Mats Nylén<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| No<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Switzerland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Andres Aeschlimann<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Turkey<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Emrah AKKOYUN<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| United Kingdom<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| John Kewley<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| '''Outside of Europe'''<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Brazil, Chile, Colombia, Mexico<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Renato Santana, Luciano Diaz, Andres Holguin<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Taiwan<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hsin-Yen Chen, Stella Shen, Vicky Huang<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Philippines<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ms. Nena Carina Española<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Indonesia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Basuki Suhardiman, Pelita Fajarhati<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Republic of Korea<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Soonwook Hwang<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<!--<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Singapore<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Malaysia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Thailand<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
--><br />
<br />
|}<br />
<br />
<br />
* Related milestone document: [https://documents.egi.eu/secure/ShowDocument?docid=60 MS301-User Support Contacts]<br />
* NGI User Support Teams session of EGI Technical Forum 2010: [https://www.egi.eu/indico/sessionDisplay.py?sessionId=78&slotId=0&confId=48#2010-09-17 session]<br />
* Overview presentation of "NGI based User Support in EGI" by Gergely Sipos at EGI Technical Forum 2010: [https://www.egi.eu/indico/contributionDisplay.py?contribId=277&sessionId=78&confId=48 presentation]<br />
<br />
== User-related development projects inside the NGIs ==<br />
<br />
'''Greece:'''<br />
* repository.egi.eu: respotory for EGI middleware components <br />
* appdb.egi.eu: EGI Application database <br />
* Enabling the Environment Modules package (http://modules.sourceforge.net/) on UIs and WNs to make users capable of modifying the environment their applications run in.<br />
* HellasGrid Wiki (http://wiki.hellasgrid.gr): Contains documentation and guides (in text and multimedia format) for both grid users and administrators <br />
* Training portal (http://www.egee-see.org/training/): An information portal for the various trainings performed in Greece. The portal is in Greek, training materials are available in English. <br />
* Software Discovery Engine (http://sde.hellasgrid.gr/): A service to discover grid sites where particular software is installed, and to find instructions on how to use the installed software. <br />
<br />
'''Italy:''' <br />
* In view of SC10’s live demos:<br />
** enhanced the status of the VisualGrid application with the support to the stereoscopy. Created two different use cases for VisualGrid: 3D rendering using Blender and VISIVO.<br />
** Updated the infrastructure for the ASTRA demo.<br />
* Developed of Java APIs for supporting a new grid authentication process with smart card.<br />
* Started to update the IGI Application Database.<br />
* Applications porting and support to the user for no HEP disciplines like Climatology, Biology and Geology<br />
* Test of the installation and configuration of a dedicated Nagios server for VOs<br />
<br />
'''Ireland:'''<br />
* Grid-Ireland eLearning facility: http://www.grid.ie/elgrid/ <br />
* A framework to facilitate simple parameter sweep type applications is in development – it is currently being used in a Computational Mathematics application, but will be reused by our other user communities. <br />
* MPI support will be provided under EGI-INSPIRE TSA 3.2.5. <br />
<br />
'''Serbia:'''<br />
* SCL repository service (http://rpm.scl.rs) powered by DWARF (https://dwarf.scl.rs/) that contains self produced RPMS (produced by Scientific Laboratory) and mirror repositories of different version of Linux (Scientific Linux, Ubuntu), gLite software and some frequently used community repositories (e.g. dag). <br />
* WatG Browser (What is at the Grid Browser) (http://watgbrowser.scl.rs:8080/), a web-based Grid Information System (GIS) visualization application providing detailed overview of the status and availability of various Grid resources in a given gLite-based e-Infrastructure (description at https://http.ipb.ac.rs/tools/watg_browser/). <br />
* gFinger (https://http.ipb.ac.rs/tools/gfinger/), a command-line tool provides information on local VOMS mapping of users authenticated by digital certificates on various Grid services, such as Computing Element (CE), Workload Management System (WMS), Storage Element (SE), etc.<br />
<br />
'''Switzerland:'''<br />
* List of applications ported to Swiss Multi-Science Computing Grid: www.smscg.ch<br />
<br />
'''UK:'''<br />
* NGS Roadshows, Innovation Forums: http://www.ngs.ac.uk/events<br />
* The NGS have produced many pieces of middleware, for example: MEG, Cert Wizard, and the NGS Portal. See User Tools on the NGS website for more information: http://www.ngs.ac.uk/tools/overview<br />
<br />
==NGI User Support Teams - Knowledge base==<br />
<br />
The purpose of this knowledge base is to collect those services, tools and solutions that NGI USTs can offer for other NGIs and for the EGI collaboration to serve international user communities. The knowledge base also collects requirements from the NGI USTs that EGI must meet in order to facilitate the user support activity within these NGIs. Initial content for the table has been collected in a [[Requirements_gathering_details#Surveys_for_user_communities]] by EGI.eu.<br />
<br />
Knowledge base: [https://www.humyo.com/FRnSjhN/04-Project%20Activity/WP3/NGI%20User%20Support%20Teams/NGI%20User%20Support%20Questionnaire%202010%20october/processed%20questionnaires/?a=D9c1UAPLS5o Excel file in EGI Humyo]<br />
<br />
<font color=red>'''The knowledge base can be updated by NGIs by sending a new version of it to ucst AT egi DOT eu.'''</font><br />
<br />
<br />
<!--<br />
{| border="1" cellspacing="0" cellpadding="5" width="100%"<br />
!Name of the NGI<br />
!Services, resources and tools offered by the User Support Team of the NGI ''for international user communities and for other NGIs''<br />
!Services, resources and tools requested by the User Support Team of the NGI to better serve local users<br />
!''Ongoing developments'' of user support services and tools that could be interesting ''for other NGIs or for user communities''<br />
|-<br />
!Czech Republic<br />
!* Interfacing local user support systems with GGUS <br>* VOCE catch-all VO and support for training and application prototyping <br />
!-<br />
!-<br />
|-<br />
!Georgia<br />
!-<br />
!-<br />
!-<br />
|-<br />
!Greece<br />
! * HellasGrid Wiki (https://wiki.hellasgrid.gr): Contains documentation and guides (in text and multimedia format) for both grid users and administrators <br> * Training portal (http://www.egee-see.org/training/): An information portal for the various trainings performed in Greece. The portal is in Greek, training materials are available in English. <br> * Software Discovery Engine (http://sde.hellasgrid.gr/): A service to discover grid sites where particular software is installed, and to find instructions on how to use the installed software. <br> * Knowledge transfer to other NGIs on running user support processes and projects <br />
! Feels lack of funding as the major limitation to expand user support activities. <br />
! * repository.egi.eu: respotory for EGI middleware components; <br>* appdb.egi.eu: EGI Application database <br>* Enabling the Environment Modules package (http://modules.sourceforge.net/) on UIs and WNs to make users capable of modifying the environment their applications run in. <br />
|-<br />
!Turkey<br />
!-<br />
!-<br />
!-<br />
|-<br />
<br />
|}<br />
--><br />
<br />
<br />
<!--<br />
<br />
!Albania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Armenia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Austria<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Belarus<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Belgium<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Bosnia Herzegovina<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Bulgaria<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Croatia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Cyprus<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Denmark<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Finland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!France<br />
!to be defined<br />
!to be defined<br />
|-<br />
<br />
|-<br />
!Germany<br />
!to be defined<br />
!to be defined<br />
<br />
!Hungary<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Ireland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Israel<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Italy<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Latvia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Lithuania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!FYR Macedonia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Moldova<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Montenegro<br />
!to be defined<br />
!to be defined<br />
|-<br />
!The Netherlands<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Norway<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Poland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Portugal<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Romania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Russian Federation<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Serbia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Slovakia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Slovenia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Spain<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Sweden<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Switzerland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Turkey<br />
!to be defined<br />
!to be defined<br />
|-<br />
!United Kingdom<br />
!to be defined<br />
!to be defined<br />
|-<br />
!...<br />
!...<br />
!...<br />
<br />
<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:TNA3.3_NGI_User_Support_Teams&diff=18607EGI-InSPIRE:TNA3.3 NGI User Support Teams2011-06-02T15:19:55Z<p>Vgkamas: /* User-related development projects inside the NGIs */</p>
<hr />
<div>==Role of NGI User Support Teams in TNA3.3 ==<br />
The main actors of EGI are the National Grid Initiatives (NGIs) whose work is coordinated by the EGI.eu organisation. NGIs ensure the operation of the grid infrastructures and support services in each country as well as a transparent representation of the requirements of all their scientific communities. The primary responsibility of the User Support Teams (USTs) of the NGIs is to provide services for users that help these users integrate/establish self-sustainable EGI user communities. These services provided by NGI USTs belong to TNA3.3. The services include (but are not restricted to):<br />
* '''Identifying new users and new user communities'''<br />
* '''Consultancy:''' NGI USTs provide technical advice on the infrastructure and support services available to users and on the various DCI technologies that EGI could provide access to in order to support their research activities. NGIs are expected to engage with national scientific communities and catalyze grid uptake within the country. After the first contact is made with a new community, consultancy is typically the next service required. <br />
* '''Training''': Many NGIs provide their own training team and facilities for users. These NGI teams provide courses at various levels and with different scope. While short events only give a brief introduction for new users, longer courses include hands-on sessions and provide attendees with a deep knowledge on specific services and tools.<br />
* '''Porting scientific applications to the infrastructure''': Experts within the NGIs are available to support users in the integration of new applications into the production infrastructure. This activity involves an analysis of the existing software, an analysis of the users’ expectations and needs, defining porting scenarios, then coding, testing and finally documenting the application. For the sake of other users NGI teams also assist with sharing the grid-enabled applications with the EGI community through the application database.<br />
* '''Arranging access for users to EGI applications''': The fastest and easiest way to use the grid is to access the already grid-enabled applications. NGIs can help users access and use applications from other communities, applications that are available in the EGI application database. <br />
* '''Supporting new VOs''': Virtual Organisations represent the collaboration of people and computers on the grid. VOs can be setup for the purpose of a single grid application, to support scientists from the same field or for researchers who work in the same geographic region. NGIs can provide users with information about existing VOs, about the processes of joining VOs, or setting up a new VO if the scope of existing VOs is not in line with the users’ scientific goals. NGIs can also assist in the allocation of computing, storage and other types of resources into VOs.<br />
* '''Developing new software services (portals, toolkits, middleware extensions, etc.)''': Most scientific collaborations and VOs require additional elements in the infrastructure to fully exploit the capabilities of their scientific applications. The integration of new infrastructure services, new portal interfaces, new programming frameworks or toolkits require deep knowledge of the existing architecture. NGIs can help users during this process, by allocating experts who can assist these users during the development, testing and integration of the components.<br />
* '''Collecting feedback''' (which is then evaluated and prioritised by TNA3.2): NGI USTs engage with user communities within their countries, monitor their development and collect feedback from them on the services and features of EGI. This feedback is collected and prioritised by EGI.eu than forwarded to the middleware developer and infrastructure operator teams, who incorporate the requested changes into the EGI roadmap. <br />
* '''Improving documentation''': Documentations on the infrastructure, its components and services are available for users at various levels. Experts in the NGI help users find appropriate documentation and contribute to new documentation as new technologies and procedures become available, or gaps in current documentation is found.<br />
* '''Providing helpdesk''': NGIs provide support personnel who can answer and deal with day-to-day issues that users find and experience during using the infrastructure. This helpdesk is available for users through a central Web portal where requests and answers can be accessed. <br />
* '''Fostering the integration of communities''' (identified by TNA3.2): The integration of scientific communities is carried out by establishing Virtual Research Communities (VRCs). VRCs represent sustainable, key customers for EGI. The VRC accreditation process is managed by EGI.eu UCST.<br />
<br />
<br />
<br />
=== What is expected from NGI User Support Teams? ===<br />
There are a number of formal and informal documents that members of NGI User Support Teams need to read in order to gain a thorough understanding of the user support activities of EGI. Many of these are reports that are produced as part of the official activities dictated by the Description of Work (DoW) for EGI-InSPIRE. The DoW defines many of our activities for the four years of the InSPIRE project.<br />
<br />
NGI User Support Teams, primarily the [https://wiki.egi.eu/wiki/TNA3.3_NGI_User_Support_Teams#User_Support_contacts_in_the_NGIs main contacts] are expected to be familiar with these resources:<br />
<br />
* EGI Web site - http://www.egi.eu/<br />
* the User support section of the website: http://egi.eu/user-support/<br />
* (NA3 section of) EGI-InSPIRE Description of Work<br />
* D3.1 document - User Community Support Process – a detailed overview: https://documents.egi.eu/document/106<br />
* MS305 - User Feedback and Recommendations – an excellent overview of the requirements gathering process and summary of the requirements captured at this point in the project: https://documents.egi.eu/document/211<br />
* NA3 Wiki: https://wiki.egi.eu/wiki/WP3:_User_Community_Coordination<br />
<br />
Optional readings:<br />
* Minutes of UCB (User Community Board) https://documents.egi.eu/document/211: https://www.egi.eu/indico/categoryDisplay.py?categId=21<br />
* Minutes of USAG (User Services Advisory Group) meetings: https://www.egi.eu/indico/categoryDisplay.py?categId=38<br />
<br />
'''As a bare minimum''' it is expected that NGI User Support Teams are proactive in informing the rest of the community about new solutions, experiences and developments. There are number of ways to do so (see D3.1 document for details):<br />
* Register forthcoming training events into the [http://www.egi.eu/user-support/technical_services/ training calendar]<br />
* [https://documents.egi.eu/document/280 Report back] to EGI.eu about training events held<br />
* Register ported applications into the [http://www.egi.eu/user-support/technical_services/ EGI Application Database]<br />
* Post on the na3 email list: inspire-na3@mailman.egi.eu<br />
* Provide information about the user support services of [https://wiki.egi.eu/wiki/TNA3.3_NGI_User_Support_Teams#User-related_development_projects_inside_the_NGIs your NGI in the NA3 Wiki]<br />
* Communicate requirements, recommendations and needs to EGI through any of the [https://wiki.egi.eu/wiki/Requirements_gathering_details feedback channels]<br />
<br />
==Role of EGI.eu in TNA3.3==<br />
NGIs are heterogeneous in terms of the size and composition of their user communities, the size and expertise of their USTs. Consequently, NGIs are not equally active and strong in all the above listed user support fields. E.g. while an NGI UST can be very experienced with application porting, it may have less interest and knowledge on the development of grid portals for end users. On top of that the primary goal of EGI is to attract and serve multi-national, large user communities. To meet these demands the User Community Support Team (UCST) of EGI.eu monitors the status of NGI USTs and help NGIs <br />
* serve local users whose requirements exceed the expertise and capacity which is available locally; <br />
* serve international user communities by integrating the user support services and expertise of multiple NGI USTs;<br />
* identify and recommend best practices and tools for NGI USTs.<br />
<br />
The monitoring of NGIs is currently done through face to face and telephone interviews, online and email questionnaires. EGI.eu UCST aims to put a more efficient mechanism in place to simplify the monitoring process and to allow NGIs to "broadcast" relevant information about their user support status and services in an intelligent way to EGI.eu and other NGIs.<br />
<br />
== User Support contacts in the NGIs ==<br />
<br />
* EGI.eu maintains a list of NGI user support contacts. Please get in contact with your NGI's support contact in training, consultancy and other types of support. <br />
* If you cannot find your country in the list, or would like to add/correct your countries representative then please contact the User Community Support Team of EGI: '''ucst@egi.eu'''. <br />
* These persons are also subscribed to the email list '''ngi-ust-managers@mailman.egi.eu'''. List archive: https://mailman.egi.eu/mailman/private/ngi-ust-managers/ (available for list members only)<br />
<br />
<br />
{| style="border-spacing:0;"<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''Country'''<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''Name of main User''' <br />
'''Support Contact in the NGI'''<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''NGI user support contact (YES) <br>or<br> NGI technical contact (NO)'''<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Albania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Neki Frasheri<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Armenia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hrachya Astsatryan<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Belarus<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Oleg Tchij <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Belgium<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Rosette Vandenbrouck<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Bulgaria<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Aneta Karaivanova <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Cyprus<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Andoena Balla<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Croatia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ivan Maric (through email list)<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Czech Republic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ivana Krenkova<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Denmark<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Michael Gronager<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also for the whole Nordic region)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Finland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Pekka Lehtovuori<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| France<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Helene Cordier, Geneviève Romier <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Georgia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nugzar Gamtsemlidze, Ramaz Kvatadze<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Germany<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Sabine Reißer<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Greece<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vasilis Gkamas, Kostas Koumantaros<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hungary<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Imre Szeberenyi<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ireland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| David O'Callaghan, Stuart Kenny, John Walsh<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Israel<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nadav Grossaug, Arad Alper<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Italy<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Claudio Vuerli, Antonio Lagana, Luciano Milanesi, Laura Perini<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Latvia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Edgars Znots<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Lithuania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Rolandas Naujikas<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Former Yugoslav Republic of Macedonia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Anastas Misev<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Republic of Moldova<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nikolai P. Iliuha, Alexandr Golubev<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Montenegro<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Lidija Milosavljevic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Netherlands<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Machiel Jansen, Tom Visser<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Norway<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Jacko Koster<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Poland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Mariusz Sterzel, Maciej Filocha<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Portugal<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Gonçalo Borges<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Romania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Alexandru Stanciu<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Russian Federation<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Valeriy Kirichenko<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Serbia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vladimir Slavnic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Slovakia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ladislav Hluchy<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Slovenia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Barbara Krasovec<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Spain<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vicente Hernández<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Sweden<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Mats Nylén<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| No<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Switzerland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Andres Aeschlimann<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Turkey<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Emrah AKKOYUN<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| United Kingdom<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| John Kewley<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| '''Outside of Europe'''<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Brazil, Chile, Colombia, Mexico<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Renato Santana, Luciano Diaz, Andres Holguin<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Taiwan<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hsin-Yen Chen, Stella Shen, Vicky Huang<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Philippines<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ms. Nena Carina Española<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Indonesia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Basuki Suhardiman, Pelita Fajarhati<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Republic of Korea<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Soonwook Hwang<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<!--<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Singapore<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Malaysia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Thailand<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
--><br />
<br />
|}<br />
<br />
<br />
* Related milestone document: [https://documents.egi.eu/secure/ShowDocument?docid=60 MS301-User Support Contacts]<br />
* NGI User Support Teams session of EGI Technical Forum 2010: [https://www.egi.eu/indico/sessionDisplay.py?sessionId=78&slotId=0&confId=48#2010-09-17 session]<br />
* Overview presentation of "NGI based User Support in EGI" by Gergely Sipos at EGI Technical Forum 2010: [https://www.egi.eu/indico/contributionDisplay.py?contribId=277&sessionId=78&confId=48 presentation]<br />
<br />
== User-related development projects inside the NGIs ==<br />
<br />
'''Greece:'''<br />
* repository.egi.eu: respotory for EGI middleware components <br />
* appdb.egi.eu: EGI Application database <br />
* Enabling the Environment Modules package (http://modules.sourceforge.net/) on UIs and WNs to make users capable of modifying the environment their applications run in.<br />
* HellasGrid Wiki (http://wiki.hellasgrid.gr): Contains documentation and guides (in text and multimedia format) for both grid users and administrators <br />
* Training portal (http://www.egee-see.org/training/): An information portal for the various trainings performed in Greece. The portal is in Greek, training materials are available in English. <br />
* Software Discovery Engine (http://sde.hellasgrid.gr/): A service to discover grid sites where particular software is installed, and to find instructions on how to use the installed software. <br />
<br />
'''Italy:''' <br />
* In view of SC10’s live demos:<br />
** enhanced the status of the VisualGrid application with the support to the stereoscopy. Created two different use cases for VisualGrid: 3D rendering using Blender and VISIVO.<br />
** Updated the infrastructure for the ASTRA demo.<br />
* Developed of Java APIs for supporting a new grid authentication process with smart card.<br />
* Started to update the IGI Application Database.<br />
* Applications porting and support to the user for no HEP disciplines like Climatology, Biology and Geology<br />
* Test of the installation and configuration of a dedicated Nagios server for VOs<br />
<br />
'''Ireland:'''<br />
* Grid-Ireland eLearning facility: http://www.grid.ie/elgrid/ <br />
* A framework to facilitate simple parameter sweep type applications is in development – it is currently being used in a Computational Mathematics application, but will be reused by our other user communities. <br />
* MPI support will be provided under EGI-INSPIRE TSA 3.2.5. <br />
<br />
'''Serbia:'''<br />
* SCL repository service (http://rpm.scl.rs) powered by DWARF (https://dwarf.scl.rs/) that contains self produced RPMS (produced by Scientific Laboratory) and mirror repositories of different version of Linux (Scientific Linux, Ubuntu), gLite software and some frequently used community repositories (e.g. dag). <br />
* WatG Browser (What is at the Grid Browser) (http://watgbrowser.scl.rs:8080/), a web-based Grid Information System (GIS) visualization application providing detailed overview of the status and availability of various Grid resources in a given gLite-based e-Infrastructure (description at https://http.ipb.ac.rs/tools/watg_browser/). <br />
* gFinger (https://http.ipb.ac.rs/tools/gfinger/), a command-line tool provides information on local VOMS mapping of users authenticated by digital certificates on various Grid services, such as Computing Element (CE), Workload Management System (WMS), Storage Element (SE), etc.<br />
<br />
'''Switzerland:'''<br />
* List of applications ported to Swiss Multi-Science Computing Grid: www.smscg.ch<br />
<br />
'''UK:'''<br />
* NGS Roadshows, Innovation Forums: http://www.ngs.ac.uk/events<br />
* The NGS have produced many pieces of middleware, for example: MEG, Cert Wizard, and the NGS Portal. See User Tools on the NGS website for more information: http://www.ngs.ac.uk/tools/overview<br />
<br />
==NGI User Support Teams - Knowledge base==<br />
<br />
The purpose of this knowledge base is to collect those services, tools and solutions that NGI USTs can offer for other NGIs and for the EGI collaboration to serve international user communities. The knowledge base also collects requirements from the NGI USTs that EGI must meet in order to facilitate the user support activity within these NGIs. Initial content for the table has been collected in a [[Requirements_gathering_details#Surveys_for_user_communities]] by EGI.eu.<br />
<br />
Knowledge base: [https://www.humyo.com/FRnSjhN/04-Project%20Activity/WP3/NGI%20User%20Support%20Teams/NGI%20User%20Support%20Questionnaire%202010%20october/processed%20questionnaires/?a=D9c1UAPLS5o Excel file in EGI Humyo]<br />
<br />
<font color=red>'''The knowledge base can be updated by NGIs by sending a new version of it to ucst AT egi DOT eu.'''</font><br />
<br />
<br />
<!--<br />
{| border="1" cellspacing="0" cellpadding="5" width="100%"<br />
!Name of the NGI<br />
!Services, resources and tools offered by the User Support Team of the NGI ''for international user communities and for other NGIs''<br />
!Services, resources and tools requested by the User Support Team of the NGI to better serve local users<br />
!''Ongoing developments'' of user support services and tools that could be interesting ''for other NGIs or for user communities''<br />
|-<br />
!Czech Republic<br />
!* Interfacing local user support systems with GGUS <br>* VOCE catch-all VO and support for training and application prototyping <br />
!-<br />
!-<br />
|-<br />
!Georgia<br />
!-<br />
!-<br />
!-<br />
|-<br />
!Greece<br />
! * HellasGrid Wiki (https://wiki.hellasgrid.gr): Contains documentation and guides (in text and multimedia format) for both grid users and administrators <br> * Training portal (http://www.egee-see.org/training/): An information portal for the various trainings performed in Greece. The portal is in Greek, training materials are available in English. <br> * Software Discovery Engine (http://sde.hellasgrid.gr/): A service to discover grid sites where particular software is installed, and to find instructions on how to use the installed software. <br> * Knowledge transfer to other NGIs on running user support processes and projects <br />
! Feels lack of funding as the major limitation to expand user support activities. <br />
! * repository.egi.eu: respotory for EGI middleware components; <br>* appdb.egi.eu: EGI Application database <br>* Enabling the Environment Modules package (http://modules.sourceforge.net/) on UIs and WNs to make users capable of modifying the environment their applications run in. <br />
|-<br />
!Turkey<br />
!-<br />
!-<br />
!-<br />
|-<br />
<br />
|}<br />
--><br />
<br />
<br />
<!--<br />
<br />
!Albania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Armenia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Austria<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Belarus<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Belgium<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Bosnia Herzegovina<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Bulgaria<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Croatia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Cyprus<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Denmark<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Finland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!France<br />
!to be defined<br />
!to be defined<br />
|-<br />
<br />
|-<br />
!Germany<br />
!to be defined<br />
!to be defined<br />
<br />
!Hungary<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Ireland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Israel<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Italy<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Latvia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Lithuania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!FYR Macedonia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Moldova<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Montenegro<br />
!to be defined<br />
!to be defined<br />
|-<br />
!The Netherlands<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Norway<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Poland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Portugal<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Romania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Russian Federation<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Serbia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Slovakia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Slovenia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Spain<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Sweden<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Switzerland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Turkey<br />
!to be defined<br />
!to be defined<br />
|-<br />
!United Kingdom<br />
!to be defined<br />
!to be defined<br />
|-<br />
!...<br />
!...<br />
!...<br />
<br />
<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:TNA3.3_NGI_User_Support_Teams&diff=17160EGI-InSPIRE:TNA3.3 NGI User Support Teams2011-05-10T11:52:02Z<p>Vgkamas: </p>
<hr />
<div>==Role of NGI User Support Teams in TNA3.3 ==<br />
The main actors of EGI are the National Grid Initiatives (NGIs) whose work is coordinated by the EGI.eu organisation. NGIs ensure the operation of the grid infrastructures and support services in each country as well as a transparent representation of the requirements of all their scientific communities. The primary responsibility of the User Support Teams (USTs) of the NGIs is to provide services for users that help these users integrate/establish self-sustainable EGI user communities. These services provided by NGI USTs belong to TNA3.3. The services include (but are not restricted to):<br />
* '''Identifying new users and new user communities'''<br />
* '''Consultancy:''' NGI USTs provide technical advice on the infrastructure and support services available to users and on the various DCI technologies that EGI could provide access to in order to support their research activities. NGIs are expected to engage with national scientific communities and catalyze grid uptake within the country. After the first contact is made with a new community, consultancy is typically the next service required. <br />
* '''Training''': Many NGIs provide their own training team and facilities for users. These NGI teams provide courses at various levels and with different scope. While short events only give a brief introduction for new users, longer courses include hands-on sessions and provide attendees with a deep knowledge on specific services and tools.<br />
* '''Porting scientific applications to the infrastructure''': Experts within the NGIs are available to support users in the integration of new applications into the production infrastructure. This activity involves an analysis of the existing software, an analysis of the users’ expectations and needs, defining porting scenarios, then coding, testing and finally documenting the application. For the sake of other users NGI teams also assist with sharing the grid-enabled applications with the EGI community through the application database.<br />
* '''Arranging access for users to EGI applications''': The fastest and easiest way to use the grid is to access the already grid-enabled applications. NGIs can help users access and use applications from other communities, applications that are available in the EGI application database. <br />
* '''Supporting new VOs''': Virtual Organisations represent the collaboration of people and computers on the grid. VOs can be setup for the purpose of a single grid application, to support scientists from the same field or for researchers who work in the same geographic region. NGIs can provide users with information about existing VOs, about the processes of joining VOs, or setting up a new VO if the scope of existing VOs is not in line with the users’ scientific goals. NGIs can also assist in the allocation of computing, storage and other types of resources into VOs.<br />
* '''Developing new software services (portals, toolkits, middleware extensions, etc.)''': Most scientific collaborations and VOs require additional elements in the infrastructure to fully exploit the capabilities of their scientific applications. The integration of new infrastructure services, new portal interfaces, new programming frameworks or toolkits require deep knowledge of the existing architecture. NGIs can help users during this process, by allocating experts who can assist these users during the development, testing and integration of the components.<br />
* '''Collecting feedback''' (which is then evaluated and prioritised by TNA3.2): NGI USTs engage with user communities within their countries, monitor their development and collect feedback from them on the services and features of EGI. This feedback is collected and prioritised by EGI.eu than forwarded to the middleware developer and infrastructure operator teams, who incorporate the requested changes into the EGI roadmap. <br />
* '''Improving documentation''': Documentations on the infrastructure, its components and services are available for users at various levels. Experts in the NGI help users find appropriate documentation and contribute to new documentation as new technologies and procedures become available, or gaps in current documentation is found.<br />
* '''Providing helpdesk''': NGIs provide support personnel who can answer and deal with day-to-day issues that users find and experience during using the infrastructure. This helpdesk is available for users through a central Web portal where requests and answers can be accessed. <br />
* '''Fostering the integration of communities''' (identified by TNA3.2): The integration of scientific communities is carried out by establishing Virtual Research Communities (VRCs). VRCs represent sustainable, key customers for EGI. The VRC accreditation process is managed by EGI.eu UCST.<br />
<br />
<br />
<br />
=== What is expected from NGI User Support Teams? ===<br />
There are a number of formal and informal documents that members of NGI User Support Teams need to read in order to gain a thorough understanding of the user support activities of EGI. Many of these are reports that are produced as part of the official activities dictated by the Description of Work (DoW) for EGI-InSPIRE. The DoW defines many of our activities for the four years of the InSPIRE project.<br />
<br />
NGI User Support Teams, primarily the [https://wiki.egi.eu/wiki/TNA3.3_NGI_User_Support_Teams#User_Support_contacts_in_the_NGIs main contacts] are expected to be familiar with these resources:<br />
<br />
* EGI Web site - http://www.egi.eu/<br />
* the User support section of the website: http://egi.eu/user-support/<br />
* (NA3 section of) EGI-InSPIRE Description of Work<br />
* D3.1 document - User Community Support Process – a detailed overview: https://documents.egi.eu/document/106<br />
* MS305 - User Feedback and Recommendations – an excellent overview of the requirements gathering process and summary of the requirements captured at this point in the project: https://documents.egi.eu/document/211<br />
* NA3 Wiki: https://wiki.egi.eu/wiki/WP3:_User_Community_Coordination<br />
<br />
Optional readings:<br />
* Minutes of UCB (User Community Board) https://documents.egi.eu/document/211: https://www.egi.eu/indico/categoryDisplay.py?categId=21<br />
* Minutes of USAG (User Services Advisory Group) meetings: https://www.egi.eu/indico/categoryDisplay.py?categId=38<br />
<br />
'''As a bare minimum''' it is expected that NGI User Support Teams are proactive in informing the rest of the community about new solutions, experiences and developments. There are number of ways to do so (see D3.1 document for details):<br />
* Register forthcoming training events into the [http://www.egi.eu/user-support/technical_services/ training calendar]<br />
* [https://documents.egi.eu/document/280 Report back] to EGI.eu about training events held<br />
* Register ported applications into the [http://www.egi.eu/user-support/technical_services/ EGI Application Database]<br />
* Post on the na3 email list: inspire-na3@mailman.egi.eu<br />
* Provide information about the user support services of [https://wiki.egi.eu/wiki/TNA3.3_NGI_User_Support_Teams#User-related_development_projects_inside_the_NGIs your NGI in the NA3 Wiki]<br />
* Communicate requirements, recommendations and needs to EGI through any of the [https://wiki.egi.eu/wiki/Requirements_gathering_details feedback channels]<br />
<br />
==Role of EGI.eu in TNA3.3==<br />
NGIs are heterogeneous in terms of the size and composition of their user communities, the size and expertise of their USTs. Consequently, NGIs are not equally active and strong in all the above listed user support fields. E.g. while an NGI UST can be very experienced with application porting, it may have less interest and knowledge on the development of grid portals for end users. On top of that the primary goal of EGI is to attract and serve multi-national, large user communities. To meet these demands the User Community Support Team (UCST) of EGI.eu monitors the status of NGI USTs and help NGIs <br />
* serve local users whose requirements exceed the expertise and capacity which is available locally; <br />
* serve international user communities by integrating the user support services and expertise of multiple NGI USTs;<br />
* identify and recommend best practices and tools for NGI USTs.<br />
<br />
The monitoring of NGIs is currently done through face to face and telephone interviews, online and email questionnaires. EGI.eu UCST aims to put a more efficient mechanism in place to simplify the monitoring process and to allow NGIs to "broadcast" relevant information about their user support status and services in an intelligent way to EGI.eu and other NGIs.<br />
<br />
== User Support contacts in the NGIs ==<br />
<br />
* EGI.eu maintains a list of NGI user support contacts. Please get in contact with your NGI's support contact in training, consultancy and other types of support. <br />
* If you cannot find your country in the list, or would like to add/correct your countries representative then please contact the User Community Support Team of EGI: '''ucst@egi.eu'''. <br />
* These persons are also subscribed to the email list '''ngi-ust-managers@mailman.egi.eu'''. List archive: https://mailman.egi.eu/mailman/private/ngi-ust-managers/ (available for list members only)<br />
<br />
<br />
{| style="border-spacing:0;"<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''Country'''<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''Name of main User''' <br />
'''Support Contact in the NGI'''<br />
| style="background-color:#ffffff;border-top:0.0069in solid #000000;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:none;padding-top:0in;padding-bottom:0in;padding-left:0.0201in;padding-right:0.0201in;"| '''NGI user support contact (YES) <br>or<br> NGI technical contact (NO)'''<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Albania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Neki Frasheri<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Armenia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hrachya Astsatryan<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Belarus<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Oleg Tchij <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Belgium<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Rosette Vandenbrouck<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Bulgaria<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Aneta Karaivanova <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Cyprus<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Andoena Balla<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Croatia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ivan Maric (through email list)<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Czech Republic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ivana Krenkova<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Denmark<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Michael Gronager<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also for the whole Nordic region)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Finland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Pekka Lehtovuori<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| France<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Helene Cordier, Geneviève Romier <br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Georgia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nugzar Gamtsemlidze, Ramaz Kvatadze<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Germany<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Sabine Reißer<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Greece<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vasilis Gkamas, Kostas Koumantaros<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hungary<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Imre Szeberenyi<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ireland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| David O'Callaghan, Stuart Kenny, John Walsh<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Israel<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nadav Grossaug, Arad Alper<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Italy<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Claudio Vuerli<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Latvia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Edgars Znots<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Lithuania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Rolandas Naujikas<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Former Yugoslav Republic of Macedonia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Anastas Misev<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Republic of Moldova<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Nikolai P. Iliuha, Alexandr Golubev<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Montenegro<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Lidija Milosavljevic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Netherlands<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Machiel Jansen, Tom Visser<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Norway<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Jacko Koster<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| NO<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Poland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Mariusz Sterzel, Maciej Filocha<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Portugal<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Gonçalo Borges<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Romania<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Alexandru Stanciu<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Russian Federation<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Valeriy Kirichenko<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Serbia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vladimir Slavnic<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (also through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Slovakia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ladislav Hluchy<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Slovenia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Barbara Krasovec<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Spain<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Vicente Hernández<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Sweden<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Mats Nylén<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| No<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Switzerland<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Andres Aeschlimann<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Turkey<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Emrah AKKOYUN<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| United Kingdom<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| John Kewley<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| '''Outside of Europe'''<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0069in solid #000000;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding:0.0382in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
| style="background-color:#ffffff;border-top:none;border-bottom:0.0007in solid #ffffff;border-left:0.0007in solid #ffffff;border-right:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| <br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Brazil, Chile, Colombia, Mexico<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Renato Santana, Luciano Diaz, Andres Holguin<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| YES<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Taiwan<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Hsin-Yen Chen, Stella Shen, Vicky Huang<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes (through email list)<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Philippines<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Ms. Nena Carina Española<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Indonesia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Basuki Suhardiman, Pelita Fajarhati<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Republic of Korea<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Soonwook Hwang<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Yes<br />
<!--<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Singapore<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Malaysia<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
<br />
|-<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| Thailand<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
| style="background-color:#ffffff;border:0.0007in solid #ffffff;padding-top:0in;padding-bottom:0in;padding-left:0.0208in;padding-right:0.0208in;"| -<br />
--><br />
<br />
|}<br />
<br />
<br />
* Related milestone document: [https://documents.egi.eu/secure/ShowDocument?docid=60 MS301-User Support Contacts]<br />
* NGI User Support Teams session of EGI Technical Forum 2010: [https://www.egi.eu/indico/sessionDisplay.py?sessionId=78&slotId=0&confId=48#2010-09-17 session]<br />
* Overview presentation of "NGI based User Support in EGI" by Gergely Sipos at EGI Technical Forum 2010: [https://www.egi.eu/indico/contributionDisplay.py?contribId=277&sessionId=78&confId=48 presentation]<br />
<br />
== User-related development projects inside the NGIs ==<br />
<br />
'''Greece:'''<br />
* repository.egi.eu: respotory for EGI middleware components <br />
* appdb.egi.eu: EGI Application database <br />
* Enabling the Environment Modules package (http://modules.sourceforge.net/) on UIs and WNs to make users capable of modifying the environment their applications run in.<br />
* HellasGrid Wiki (https://wiki.hellasgrid.gr): Contains documentation and guides (in text and multimedia format) for both grid users and administrators <br />
* Training portal (http://www.egee-see.org/training/): An information portal for the various trainings performed in Greece. The portal is in Greek, training materials are available in English. <br />
* Software Discovery Engine (http://sde.hellasgrid.gr/): A service to discover grid sites where particular software is installed, and to find instructions on how to use the installed software. <br />
<br />
'''Italy:''' <br />
* In view of SC10’s live demos:<br />
** enhanced the status of the VisualGrid application with the support to the stereoscopy. Created two different use cases for VisualGrid: 3D rendering using Blender and VISIVO.<br />
** Updated the infrastructure for the ASTRA demo.<br />
* Developed of Java APIs for supporting a new grid authentication process with smart card.<br />
* Started to update the IGI Application Database.<br />
* Applications porting and support to the user for no HEP disciplines like Climatology, Biology and Geology<br />
* Test of the installation and configuration of a dedicated Nagios server for VOs<br />
<br />
'''Ireland:'''<br />
* Grid-Ireland eLearning facility: http://www.grid.ie/elgrid/ <br />
* A framework to facilitate simple parameter sweep type applications is in development – it is currently being used in a Computational Mathematics application, but will be reused by our other user communities. <br />
* MPI support will be provided under EGI-INSPIRE TSA 3.2.5. <br />
<br />
'''Serbia:'''<br />
* SCL repository service (http://rpm.scl.rs) powered by DWARF (https://dwarf.scl.rs/) that contains self produced RPMS (produced by Scientific Laboratory) and mirror repositories of different version of Linux (Scientific Linux, Ubuntu), gLite software and some frequently used community repositories (e.g. dag). <br />
* WatG Browser (What is at the Grid Browser) (http://watgbrowser.scl.rs:8080/), a web-based Grid Information System (GIS) visualization application providing detailed overview of the status and availability of various Grid resources in a given gLite-based e-Infrastructure (description at https://http.ipb.ac.rs/tools/watg_browser/). <br />
* gFinger (https://http.ipb.ac.rs/tools/gfinger/), a command-line tool provides information on local VOMS mapping of users authenticated by digital certificates on various Grid services, such as Computing Element (CE), Workload Management System (WMS), Storage Element (SE), etc.<br />
<br />
'''Switzerland:'''<br />
* List of applications ported to Swiss Multi-Science Computing Grid: www.smscg.ch<br />
<br />
'''UK:'''<br />
* NGS Roadshows, Innovation Forums: http://www.ngs.ac.uk/events<br />
* The NGS have produced many pieces of middleware, for example: MEG, Cert Wizard, and the NGS Portal. See User Tools on the NGS website for more information: http://www.ngs.ac.uk/tools/overview<br />
<br />
==NGI User Support Teams - Knowledge base==<br />
<br />
The purpose of this knowledge base is to collect those services, tools and solutions that NGI USTs can offer for other NGIs and for the EGI collaboration to serve international user communities. The knowledge base also collects requirements from the NGI USTs that EGI must meet in order to facilitate the user support activity within these NGIs. Initial content for the table has been collected in a [[Requirements_gathering_details#Surveys_for_user_communities]] by EGI.eu.<br />
<br />
Knowledge base: [https://www.humyo.com/FRnSjhN/04-Project%20Activity/WP3/NGI%20User%20Support%20Teams/NGI%20User%20Support%20Questionnaire%202010%20october/processed%20questionnaires/?a=D9c1UAPLS5o Excel file in EGI Humyo]<br />
<br />
<font color=red>'''The knowledge base can be updated by NGIs by sending a new version of it to ucst AT egi DOT eu.'''</font><br />
<br />
<br />
<!--<br />
{| border="1" cellspacing="0" cellpadding="5" width="100%"<br />
!Name of the NGI<br />
!Services, resources and tools offered by the User Support Team of the NGI ''for international user communities and for other NGIs''<br />
!Services, resources and tools requested by the User Support Team of the NGI to better serve local users<br />
!''Ongoing developments'' of user support services and tools that could be interesting ''for other NGIs or for user communities''<br />
|-<br />
!Czech Republic<br />
!* Interfacing local user support systems with GGUS <br>* VOCE catch-all VO and support for training and application prototyping <br />
!-<br />
!-<br />
|-<br />
!Georgia<br />
!-<br />
!-<br />
!-<br />
|-<br />
!Greece<br />
! * HellasGrid Wiki (https://wiki.hellasgrid.gr): Contains documentation and guides (in text and multimedia format) for both grid users and administrators <br> * Training portal (http://www.egee-see.org/training/): An information portal for the various trainings performed in Greece. The portal is in Greek, training materials are available in English. <br> * Software Discovery Engine (http://sde.hellasgrid.gr/): A service to discover grid sites where particular software is installed, and to find instructions on how to use the installed software. <br> * Knowledge transfer to other NGIs on running user support processes and projects <br />
! Feels lack of funding as the major limitation to expand user support activities. <br />
! * repository.egi.eu: respotory for EGI middleware components; <br>* appdb.egi.eu: EGI Application database <br>* Enabling the Environment Modules package (http://modules.sourceforge.net/) on UIs and WNs to make users capable of modifying the environment their applications run in. <br />
|-<br />
!Turkey<br />
!-<br />
!-<br />
!-<br />
|-<br />
<br />
|}<br />
--><br />
<br />
<br />
<!--<br />
<br />
!Albania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Armenia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Austria<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Belarus<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Belgium<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Bosnia Herzegovina<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Bulgaria<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Croatia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Cyprus<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Denmark<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Finland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!France<br />
!to be defined<br />
!to be defined<br />
|-<br />
<br />
|-<br />
!Germany<br />
!to be defined<br />
!to be defined<br />
<br />
!Hungary<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Ireland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Israel<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Italy<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Latvia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Lithuania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!FYR Macedonia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Moldova<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Montenegro<br />
!to be defined<br />
!to be defined<br />
|-<br />
!The Netherlands<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Norway<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Poland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Portugal<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Romania<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Russian Federation<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Serbia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Slovakia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Slovenia<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Spain<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Sweden<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Switzerland<br />
!to be defined<br />
!to be defined<br />
|-<br />
!Turkey<br />
!to be defined<br />
!to be defined<br />
|-<br />
!United Kingdom<br />
!to be defined<br />
!to be defined<br />
|-<br />
!...<br />
!...<br />
!...<br />
<br />
<br />
--></div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12797NGI International Task Review MS109 Greece2011-03-09T20:46:18Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general.<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you need any more the LCG-CE service?)<br />
<br />
| US_HS_Application_Database_Assessment = Till now 9 applications from HellasGrid has been registered to EGI AppDB. <br />
| US_HS_Application_Database_Score = 4<br />
| US_HS_Application_Database_HowToImprove = Better dissemination of the AppDB to users.<br />
<br />
| US_HS_Training_Assessment = NGI GRNET does not offer training services in the context of EGI-InSPIRE project<br />
| US_HS_Training_Score = N/A<br />
| US_HS_Training_HowToImprove = N/A<br />
<br />
| US_HS_Consultancy_Assessment = Consultancy is provided via helpdesk where two mailing lists (user-support and application-support) are used for direct communication of the users with the two main user support teams of HellasGrid. A request tracking system is also used for the better tracking of all users-related issues arised. <br />
| US_HS_Consultancy_Score = 4<br />
| US_HS_Consultancy_HowToImprove = By constructing updated user-oriented material (cookbooks, user guides, screencasts, etc) concerning mainly issues introduced by decomission of old services and gradual transition to new ones (for example transition from LCG-CE to Cream CE).<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12796NGI International Task Review MS109 Greece2011-03-09T20:44:45Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general.<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you need any more the LCG-CE service?)<br />
<br />
| US_HS_Application_Database_Assessment = Till now 9 applications from HellasGrid has been registered to EGI AppDB. <br />
| US_HS_Application_Database_Score = 4<br />
| US_HS_Application_Database_HowToImprove = Better dissemination of the AppDB to users.<br />
<br />
| US_HS_Training_Assessment = NGI GRNET does not offer training services in the context of EGI-InSPIRE project<br />
| US_HS_Training_Score = N/A<br />
| US_HS_Training_HowToImprove = N/A<br />
<br />
| US_HS_Consultancy_Assessment = Consultancy is provided via helpdesk where two mailing lists (user-support and application-support) are used for direct communication of the users with the two main user support teams at HellasGrid. A request tracking system is used for the better tracking of all users-related issues arised. <br />
| US_HS_Consultancy_Score = 4<br />
| US_HS_Consultancy_HowToImprove = By constructing updated user-oriented material (cookbooks, user guides, screencasts, etc) concerning mainly issues introduced by decomission of old services and gradual transition to new ones (for example transition from LCG-CE to Cream CE).<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12795NGI International Task Review MS109 Greece2011-03-09T20:43:56Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general.<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you need any more the LCG-CE service?)<br />
<br />
| US_HS_Application_Database_Assessment = Till now 9 applications from HellasGrid has been registered to EGI AppDB. <br />
| US_HS_Application_Database_Score = 4<br />
| US_HS_Application_Database_HowToImprove = Better dissemination of the AppDB to users.<br />
<br />
| US_HS_Training_Assessment = NGI GRNET does not offer training services in the context of EGI-InSPIRE project<br />
| US_HS_Training_Score = N/A<br />
| US_HS_Training_HowToImprove = N/A<br />
<br />
| US_HS_Consultancy_Assessment = Consultancy is provided via helpdesk where two mailing lists (user-support and application-support) are used for direct communication of the users with the two main user support teams at HellasGrid. A request tracking system is used for the better tracking of all users-related issues arised. <br />
| US_HS_Consultancy_Score = 4<br />
| US_HS_Consultancy_HowToImprove = By constructing updated user-oriented material (cookbooks, user guides, screencasts, etc) concerning mainly issues introduced by decomission of old services and gradual transition to new ones(for example transition from LCG-CE to Cream CE).<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12794NGI International Task Review MS109 Greece2011-03-09T20:42:36Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general. be<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you prefer LCG-CE or CreamCE?)<br />
<br />
| US_HS_Application_Database_Assessment = Till now 9 applications from HellasGrid has been registered to EGI AppDB. <br />
| US_HS_Application_Database_Score = 4<br />
| US_HS_Application_Database_HowToImprove = Better dissemination of the AppDB to users.<br />
<br />
| US_HS_Training_Assessment = NGI GRNET does not offer training services in the context of EGI-InSPIRE project<br />
| US_HS_Training_Score = N/A<br />
| US_HS_Training_HowToImprove = N/A<br />
<br />
| US_HS_Consultancy_Assessment = Consultancy is provided via helpdesk where two mailing lists (user-support and application-support) are used for direct communication of the users with the two main user support teams at HellasGrid. A request tracking system is used for the better tracking of all users-related issues arised. <br />
| US_HS_Consultancy_Score = 4<br />
| US_HS_Consultancy_HowToImprove = By constructing updated user-oriented material (cookbooks, user guides, screencasts, etc) concerning mainly issues introduced by decomission of old services and gradual transition to new ones(for example transition from LCG-CE to Cream CE).<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12793NGI International Task Review MS109 Greece2011-03-09T20:40:39Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general. be<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you prefer LCG-CE or CreamCE?)<br />
<br />
| US_HS_Application_Database_Assessment = Till now 9 applications from HellasGrid has been registered to EGI appdb. <br />
| US_HS_Application_Database_Score = 4<br />
| US_HS_Application_Database_HowToImprove = write here<br />
<br />
| US_HS_Training_Assessment = NGI GRNET does not offer training services in the context of EGI-InSPIRE project<br />
| US_HS_Training_Score = N/A<br />
| US_HS_Training_HowToImprove = N/A<br />
<br />
| US_HS_Consultancy_Assessment = Consultancy is provided via helpdesk where two mailing lists (user-support and application-support) are used for direct communication of the users with the two main user support teams at HellasGrid. A request tracking system is used for the better tracking of all users-related issues arised. <br />
| US_HS_Consultancy_Score = 4<br />
| US_HS_Consultancy_HowToImprove = By constructing updated user-oriented material (cookbooks, user guides, screencasts, etc) concerning mainly issues introduced by decomission of old services and gradual transition to new ones(for example transition from LCG-CE to Cream CE).<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12792NGI International Task Review MS109 Greece2011-03-09T20:38:00Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general. be<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you prefer LCG-CE or CreamCE?)<br />
<br />
| US_HS_Application_Database_Assessment = write here<br />
| US_HS_Application_Database_Score = 0-5<br />
| US_HS_Application_Database_HowToImprove = write here<br />
<br />
| US_HS_Training_Assessment = NGI GRNET does not offer training services in the context of EGI-InSPIRE project<br />
| US_HS_Training_Score = N/A<br />
| US_HS_Training_HowToImprove = N/A<br />
<br />
| US_HS_Consultancy_Assessment = Consultancy is provided via helpdesk where two mailing lists (user-support and application-support) are used for direct communication of the users with the two main user support teams at HellasGrid. A request tracking system is used for the better tracking of all users-related issues arised. <br />
| US_HS_Consultancy_Score = 4<br />
| US_HS_Consultancy_HowToImprove = By constructing updated user-oriented material (cookbooks, user guides, screencasts, etc) concerning mainly issues introduced by decomission of old services and gradual transition to new services (for example transition from LCG-CE to Cream CE).<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12791NGI International Task Review MS109 Greece2011-03-09T20:32:35Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general. be<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you prefer LCG-CE or CreamCE?)<br />
<br />
| US_HS_Application_Database_Assessment = write here<br />
| US_HS_Application_Database_Score = 0-5<br />
| US_HS_Application_Database_HowToImprove = write here<br />
<br />
| US_HS_Training_Assessment = NGI GRNET does not offer training services in the context of EGI-InSPIRE project<br />
| US_HS_Training_Score = N/A<br />
| US_HS_Training_HowToImprove = N/A<br />
<br />
| US_HS_Consultancy_Assessment = write here<br />
| US_HS_Consultancy_Score = 0-5<br />
| US_HS_Consultancy_HowToImprove = write here<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12790NGI International Task Review MS109 Greece2011-03-09T20:31:50Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general. be<br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line survey). Also the questions of the surveys must be as simple as possible, without make the user to be confused with a lot of technical terminology (for example do you prefer LCG-CE or CreamCE?)<br />
<br />
| US_HS_Application_Database_Assessment = write here<br />
| US_HS_Application_Database_Score = 0-5<br />
| US_HS_Application_Database_HowToImprove = write here<br />
<br />
| US_HS_Training_Assessment = write here<br />
| US_HS_Training_Score = 0-5<br />
| US_HS_Training_HowToImprove = write here<br />
<br />
| US_HS_Consultancy_Assessment = write here<br />
| US_HS_Consultancy_Score = 0-5<br />
| US_HS_Consultancy_HowToImprove = write here<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_International_Task_Review_MS109_Greece&diff=12789NGI International Task Review MS109 Greece2011-03-09T20:29:47Z<p>Vgkamas: </p>
<hr />
<div>{{NGI_InternationalTask_Review<br />
<br />
<!-- User Services - Human Services --><br />
<br />
| US_HS_RequirementsGathering_Assessment = In order to gather users' requirements a mailing list with all the registered to HellasGrid users is used. Also there is a plan to make a survey using on-line questionnaire in order to gather users' requirements and their assessment regarding the use of HellasGrid and EGI infrastructure in general . Finnaly <br />
| US_HS_RequirementsGathering_Score = 3<br />
| US_HS_RequirementsGathering_HowToImprove = In order to gather the real requirements of the users' more formal means of communication are preferable (for example an on-line questionnaire). Also the questions done must is as simple as possible, without the user get in trouble of what a question means (for example do you prefer LCG-CE or Cream CE?)<br />
<br />
| US_HS_Application_Database_Assessment = write here<br />
| US_HS_Application_Database_Score = 0-5<br />
| US_HS_Application_Database_HowToImprove = write here<br />
<br />
| US_HS_Training_Assessment = write here<br />
| US_HS_Training_Score = 0-5<br />
| US_HS_Training_HowToImprove = write here<br />
<br />
| US_HS_Consultancy_Assessment = write here<br />
| US_HS_Consultancy_Score = 0-5<br />
| US_HS_Consultancy_HowToImprove = write here<br />
<br />
<!-- Operations Services - Human Services --><br />
<br />
| OS_HS_RequirementsGathering_Assessment | your assessment here<br />
| OS_HS_RequirementsGathering_Score = 0-5<br />
| OS_HS_RequirementsGathering_HowToImprove | how to improve <br />
<br />
| OS_HS_Coordination_Assessment = write here<br />
| OS_HS_Coordination_Score = 0-5<br />
| OS_HS_Coordination_HowToImprove = write here<br />
<br />
| OS_HS_Security_Assessment = write here<br />
| OS_HS_Security_Score = 0-5<br />
| OS_HS_Security_HowToImprove = write here<br />
<br />
<!-- Operations Services - Infrastructure Services --><br />
<br />
| OS_IS_SoftwareRollout_Assessment = write here<br />
| OS_IS_SoftwareRollout_Score = 0-5<br />
| OS_IS_SoftwareRollout_HowToImprove = write here<br />
<br />
| OS_IS_Monitoring_Assessment = write here<br />
| OS_IS_Monitoring_Score = 0-5<br />
| OS_IS_Monitoring_HowToImprove = write here<br />
<br />
| OS_IS_Accounting_Assessment = write here<br />
| OS_IS_Accounting_Score = 0-5<br />
| OS_IS_Accounting_HowToImprove = write here<br />
<br />
| OS_IS_Configuration_OpPortal_Assessment = write here<br />
| OS_IS_Configuration_OpPortal_Score = 0-5<br />
| OS_IS_Configuration_OpPortal_HowToImprove = write here<br />
<br />
| OS_IS_Helpdesk_Assessment = write here<br />
| OS_IS_Helpdesk_Score = 0-5<br />
| OS_IS_Helpdesk_HowToImprove = write here<br />
<br />
| OS_IS_CoreServices_Assessment = write here<br />
| OS_IS_CoreServices_Score = 0-5<br />
| OS_IS_CoreServices_HowToImprove = write here<br />
<br />
<!-- Others - Policy --><br />
<br />
| O_Policy_Assessment = write here<br />
| O_Policy_Score = 0-5<br />
| O_Policy_HowToImprove = write here<br />
<br />
<!-- Others - Dissemination --><br />
<br />
| O_Dissemination_Assessment = write here<br />
| O_Dissemination_Score = 0-5<br />
| O_Dissemination_HowToImprove = write here<br />
<br />
}}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=EGI-InSPIRE:Training_Working_Group&diff=6754EGI-InSPIRE:Training Working Group2010-12-13T13:41:47Z<p>Vgkamas: </p>
<hr />
<div>= Introduction =<br />
The purpose of the EGI Training Working Group is to develop and monitor a training coordination strategy for the EGI community. By EGI community we mean the community of actual and potential users of Distributed Computing Infrastructure (DCI) across Europe. Research communities in Europe frequently collaborate with communities outside of Europe so there will also be a need for training that relates to systems outside of Europe. Equally, there will be a similar demand for European training from communities outside of Europe to support such collaboration.<br />
<br />
EGI already has a [http://www.egi.eu/user-support/technical_services/ training events calendar and a training materials database] where information can be deposited and found. However, the plan is to extend this functionality with a broader support structure whereby users can submit suggestions and requests for training and others can offer topics around which training could be developed or events could be planned. Such functionality would enable people planning events and those developing training material to have advanced knowledge of requirements and opportunities. The end result will be a more productive training landscape that is better aligned to the needs of the communities.<br />
<br />
= Goals, members =<br />
The role of the Training Working Group is to establish an interactive market place as efficiently as possible and then to monitor the training services provided for the EGI community and to ensure that they serve the needs of the whole community but with the focus on end-users. In other words, the actual matchmaking of need and provision would take place through the online application or portal not within the working group. Therefore, it is not a necessity for every project and NGI to have a representative on the Working Group only those with a specific interest in the wider strategic issues relating to training. Through email lists and mechanisms - for example through this Wiki page - the group keeps the whole training community informed of the actual training resources. The group reports to the [http://www.egi.eu/policy/groups/User_Community_Board_UCB.html EGI User Community Board].<br />
<br />
'''Members:'''<br />
{| border="1" cellspacing="0" cellpadding="5"<br />
! Name<br />
! Institute<br />
! Representative of<br />
|-<br />
| Steve Brewer (chair)<br />
| EGI.eu<br />
| EGI-InSPIRE, User Community Support Team<br />
|-<br />
| Gergely Sipos, Nuno Ferreira, Karolis Eigelis<br />
| EGI.eu<br />
| EGI-InSPIRE, User Community Support Team<br />
|-<br />
| Emrah Akkoyun <br />
| ULAKBIM<br />
| NGI of Turkey<br />
|-<br />
| Kathryn Cassidy<br />
| TCD<br />
| EMI project<br />
|-<br />
| Gkamas Vasileios<br />
| CTI/GRNET<br />
| NGI of Greece<br />
|-<br />
| Peter Stefan <br />
| NIIF<br />
| NGI of Hungary<br />
|}<br />
<br />
= How to participate = <br />
The Training Working Group has been established by the EGI User Community Support Team (UCST). Any NGI and DCI project is invited to put forward potential members. Please get in touch with the UCST if you are interested in participating: ucst@egi.eu<br />
<br />
= Meetings = <br />
It is envisaged that the Working Group will hold telephone conferences once a month with the potential to hold a face to face meeting during the EGI User and Technical Forums.<br />
<br />
Doodle poll about the date and time of first teleconference: http://doodle.com/z7rqv73tc5y2ymsr<br />
<br />
= Tasks =<br />
The first major goal for the Working Group is to support the Programme Committee for the EGI User Forum in Vilnius, Lithuania April 2011 in driving forward the organisation of training events as a result of the emerging strategy.</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_GRNET:RT_GGUS_Integration&diff=2448NGI GRNET:RT GGUS Integration2010-08-25T11:46:10Z<p>Vgkamas: </p>
<hr />
<div>=== Scope === <br />
<br />
The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of SOAP messages. GGUS has already implemented some web services, (used for example for the integration with the SEE Helpdesk), so the necessary web services must have been implemented at the HellasGrid RT.<br />
<br />
There are three possible scenarios implemented:<br />
<br />
* '''Scenario 1''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 2''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 3''': A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. <br />
<br />
At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system.<br />
<br />
=== Implementation === <br />
<br />
For the needs of the implementation the following queues was implemented at the HellasGrid RT:<br />
<br />
* A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.<br />
* A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.<br />
* A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned. <br />
<br />
The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file ticket.cgi located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.<br />
<br />
''' Ticket creation at GGUS ''' <br />
<br />
The HellasGrid RT web services are called by the file ggus_client.pl located at the path /root/ws which is automatically executed every 5 minutes. This service checks if a transaction has occurred from the last time it was called, and in a case of a transaction the appropriate ticket at the GGUS is updated.<br />
<br />
The information regarding the correspondence of the two systems is kept at the rtdb database and more specific at the ggus_rt and ggus_transactions tables (which were created). At the table ggus_rt is stored the correspondence between the ID of a ticket at the GGUS and the ID of a ticket at the HellasGrid RT. This is done every time that a ticket at the GGUS is assigned at the NGI_GRNET support unit or at a site under the scope of the NGI_GRNET. At the table ggus_transactions are stored the IDs of the transactions which concern the corresponding tickets at the ggus_rt. This is done via the use of scrips, that is Perl hooks which can be defined at the RT and can be executed at different time instances.<br />
<br />
So, the database has the role of a message queuing system. Due to the low creation rate of tickets at the HellasGrid RT, was not used a specialized queuing system. Also another reason for using this solution instead the direct sending of the updates at the GGUS during the processing of a ticket (inside the scrip) is that this implementation results in functionality’s separation, so the call of the GGUS web services is not involved with the processing of the ticket. Also, the delay at the RT due to HTTP web services call is low.<br />
<br />
''' Ticket creation at HellasGrid RT ''' <br />
<br />
For the scenario of a ticket creation at the GGUS queue of the HellasGrid RT, two Perl script are used, the ggus_create.pl and the ggus_client.pl scripts. The first Perl script is used for the creation of a ticket at the GGUS system. Every time that a ticket is created at the GGUS queue of the HellasGrid RT, a scrip is called which stores the ID of the new ticket at a table named ggus_queue. This ID is used by the ggus_create.pl script in order to create the ticket at the GGUS system. The ggus_create.pl script is called with a cron job every 5 minutes, scans the ggus_queue table and if a new ticket exists, then a ticket is created at the GGUS system, by calling the appropriate web service. Also, a new entry is created at the ggus_rt table which stores the correspondence between the tickets created at the two systems.<br />
<br />
=== Web Services === <br />
<br />
The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system.</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=Ticket.cgi&diff=2447Ticket.cgi2010-08-25T11:45:21Z<p>Vgkamas: Created page with '#!/usr/bin/perl -w use strict; use lib '/usr/share/request-tracker3.6/lib'; use lib '/root/ws/'; use SOAP::Transport::HTTP; use MIME::Entity; use MIME::Base64; use IO::Scalar; …'</p>
<hr />
<div>#!/usr/bin/perl -w<br />
<br />
use strict;<br />
use lib '/usr/share/request-tracker3.6/lib';<br />
use lib '/root/ws/';<br />
<br />
use SOAP::Transport::HTTP;<br />
use MIME::Entity;<br />
use MIME::Base64;<br />
use IO::Scalar;<br />
use File::MimeInfo::Magic;<br />
use RT;<br />
use RT::User;<br />
use RT::CurrentUser;<br />
use RT::Ticket;<br />
use GGUS::Transaction;<br />
use GGUS::Transactions;<br />
<br />
SOAP::Transport::HTTP::CGI<br />
-> dispatch_to('TicketWS')<br />
-> handle;<br />
<br />
package TicketWS;<br />
<br />
# Create a new ticket<br />
# Parameters:<br />
# Necessary:<br />
# ggus_id: int, id in ggus database<br />
# requestor: string, email address of requestor<br />
# subject: string<br />
# content: string<br />
# priority: string, as defined in ggus wsdl<br />
# affected_site: string, site that affects the ticket<br />
sub create_ticket {<br />
my $self = shift;<br />
<br />
RT::LoadConfig();<br />
RT::Init();<br />
<br />
my $num_args = 6;<br />
unless (@_ == $num_args) {<br />
$RT::Logger->log(<br />
level => 'err',<br />
message => "Not enough arguments."<br />
);<br />
return (0, "ngigrnet");<br />
}<br />
<br />
my $ggus_id = shift;<br />
my $requestor = shift;<br />
$requestor =~ s/ //g;<br />
my $subject = shift;<br />
my $content = shift;<br />
my $priority = shift;<br />
$priority = convert_priority($priority);<br />
my $affected_site = shift;<br />
<br />
# queue name<br />
my $queue = get_queue($affected_site);<br />
<br />
unless (is_int($ggus_id)) {<br />
$RT::Logger->log(level=>'alert', message => "Requested ticket from ggus $ggus_id");<br />
return (0, "ngigrnet");<br />
}<br />
<br />
$RT::Logger->log(level => 'info', message => "ggus $ggus_id added by $requestor.");<br />
$RT::Logger->log(level => 'crit', message => "affected site: $affected_site");<br />
<br />
# build MIME encoded content<br />
my $MIMEContent = MIME::Entity->build(<br />
Data => [ $content ]<br />
);<br />
my $ticket = new RT::Ticket($RT::SystemUser);<br />
my %ticket_args = (<br />
"Queue" => $queue,<br />
"Requestor" => [$requestor,],<br />
"Subject" => $subject,<br />
"Priority" => $priority,<br />
"MIMEObj" => $MIMEContent,<br />
);<br />
my @res = $ticket->Create(%ticket_args);<br />
if ($res[0] == 0) {<br />
# error creating ticket<br />
$RT::Logger->log(level => 'err', message => $res[2]);<br />
return (0, "ngigrnet");<br />
}<br />
$RT::Logger->log(level => 'debug', message => $res[2]);<br />
# Add ggus id to ggus_rt table<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
$rt_handle->BeginTransaction;<br />
$rt_handle->Insert('ggus_rt', ('ggus_id', $ggus_id, 'rt_id', $res[0]));<br />
$rt_handle->Commit;<br />
<br />
# get user from requestor's address<br />
my $user = RT::User->new($RT::SystemUser);<br />
$RT::Logger->log(<br />
level => 'info',<br />
message => "user: $requestor",<br />
);<br />
$user->LoadOrCreateByEmail($requestor);<br />
# set Creator and Created fields<br />
ticket_set_creat($res[0], $user->id);<br />
# set corresponding transaction's creater and created<br />
my $trans_id = $res[1];<br />
trans_set_creat($trans_id, $user->id);<br />
<br />
return ($res[0], "ngigrnet");<br />
}<br />
<br />
# Edit an existing ticket.<br />
# Parameters:<br />
# Necessary:<br />
# ggus_id: int, from ggus<br />
# requestor: email address<br />
# content: string<br />
# status: string<br />
# priority: string<br />
sub edit_ticket {<br />
my $self = shift;<br />
<br />
RT::LoadConfig();<br />
RT::Init();<br />
<br />
my $num_args = 5;<br />
unless (@_ == $num_args) {<br />
$RT::Logger->log(<br />
level => 'err',<br />
message => 'Not enough arguments.'<br />
);<br />
return (0, "ngigrnet");<br />
}<br />
<br />
<br />
my $ggus_id = shift;<br />
my $requestor = shift;<br />
$requestor =~ s/ //g;<br />
my $content = shift;<br />
my $status = shift;<br />
my $priority = shift;<br />
<br />
unless (is_int($ggus_id)) {<br />
$RT::Logger->log(level=>'alert', message => "Requested ticket from ggus $ggus_id");<br />
return (0, "ngigrnet");<br />
}<br />
<br />
# get user from requestor's address<br />
my $user = RT::User->new($RT::SystemUser);<br />
$RT::Logger->log(<br />
level => 'crit',<br />
message => "user: $requestor",<br />
);<br />
$user->LoadOrCreateByEmail($requestor);<br />
<br />
# get rt_id for this ggus_id<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
my $query = 'SELECT rt_id FROM ggus_rt WHERE ggus_id=?';<br />
my @res = $rt_handle->FetchResult($query, ($ggus_id, ));<br />
unless (@res) {<br />
$RT::Logger->log(<br />
level => 'err', <br />
message => "No rt ticket for ggus $ggus_id"<br />
);<br />
return (0, "ngigrnet");<br />
}<br />
my $ticket_id = $res[0];<br />
$RT::Logger->log(<br />
level => 'crit', <br />
message => "ggus: $ticket_id for ggus $ggus_id edited."<br />
);<br />
<br />
unless ($content eq '') {<br />
my %args = (<br />
'Content' => $content,<br />
);<br />
<br />
my $ticket = new RT::Ticket($RT::SystemUser);<br />
$ticket->Load($ticket_id);<br />
@res = $ticket->Comment(%args);<br />
if ($res[0] == 0) {<br />
$RT::Logger->log(level => 'crit', message => $res[1]);<br />
return (0, "ngigrnet");<br />
}<br />
$RT::Logger->log(level => 'crit', message => $res[1]);<br />
<br />
# set creator of transaction<br />
trans_set_creat($res[0], $user->id);<br />
}<br />
<br />
# set status<br />
set_status($ggus_id, $status);<br />
# set priority<br />
set_priority($ggus_id, $status);<br />
<br />
# scrips have been run<br />
# mark transaction done<br />
mark_transaction_done($res[0]);<br />
<br />
return ($ticket_id, "ngigrnet");<br />
}<br />
<br />
<br />
# Add an attachemnt<br />
# params:<br />
# ggus_id: int from ggus<br />
# atch_data: base64string the data of the attachment<br />
# atch_name: string the name of the attachment<br />
sub add_attachment {<br />
my $self = shift;<br />
<br />
RT::LoadConfig();<br />
RT::Init();<br />
<br />
my $num_args = 3;<br />
unless (@_ == $num_args) {<br />
$RT::Logger->log(<br />
level => 'err',<br />
message => 'Not enough arguments.'<br />
);<br />
return (0, "ngigrnet");<br />
}<br />
<br />
my $ggus_id = shift;<br />
my $atch_data = shift;<br />
my $atch_name = shift;<br />
<br />
unless (is_int($ggus_id)) {<br />
$RT::Logger->log(level=>'alert', message => "Requested ticket from ggus $ggus_id");<br />
return (0, "ngigrnet");<br />
}<br />
<br />
# get rt_id for this ggus_id<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
my $query = 'SELECT rt_id FROM ggus_rt WHERE ggus_id=?';<br />
my @res = $rt_handle->FetchResult($query, ($ggus_id, ));<br />
unless (@res) {<br />
$RT::Logger->log(<br />
level => 'err', <br />
message => "No rt ticket for ggus $ggus_id"<br />
);<br />
return (0, "ngigrnet");<br />
}<br />
my $ticket_id = $res[0];<br />
$RT::Logger->log(<br />
level => 'info', <br />
message => "ggus: $ticket_id for ggus $ggus_id attachment added."<br />
);<br />
my $data = MIME::Base64::decode_base64($atch_data);<br />
$RT::Logger->log(<br />
level => 'crit', <br />
message => "ggus: attachment $data"<br />
);<br />
<br />
<br />
my $content = '';<br />
<br />
# build MIME encoded content<br />
my $MIMEContent = MIME::Entity->build(<br />
Data => [ $content ]<br />
);<br />
my $atch_type = get_mime_type($atch_data);<br />
add_attachment_to_mimeobj(\$MIMEContent, $atch_data, $atch_type, $atch_name);<br />
<br />
my %args = (<br />
'MIMEObj' => $MIMEContent,<br />
);<br />
<br />
# make transaction<br />
my $ticket = new RT::Ticket($RT::SystemUser);<br />
$ticket->Load($ticket_id);<br />
@res = $ticket->Comment(%args);<br />
if ($res[0] == 0) {<br />
$RT::Logger->log(level => 'err', message => $res[1]);<br />
return (0, "ngigrnet");<br />
}<br />
$RT::Logger->log(level => 'info', message => $res[1]);<br />
<br />
# scrips have been run<br />
# mark transaction done<br />
mark_transaction_done($res[0]);<br />
<br />
return ($ticket_id, "ngigrnet");<br />
}<br />
<br />
# Change priority<br />
<br />
# params:<br />
# id: int, from ggus<br />
# priority: string<br />
sub set_priority {<br />
RT::LoadConfig();<br />
RT::Init();<br />
<br />
my $num_args = 2;<br />
unless (@_ >= $num_args) {<br />
$RT::Logger->log(<br />
level => 'err',<br />
message => 'Not enough arguments.'<br />
);<br />
return (0, "ngigrnet");<br />
}<br />
<br />
my $ggus_id = shift;<br />
unless (is_int($ggus_id)) {<br />
$RT::Logger->log(level=>'alert', message => "Requested ticket from ggus $ggus_id");<br />
return (0, "ngigrnet");<br />
}<br />
<br />
my $ticket_id = ggus_to_rt($ggus_id);<br />
my $priority = shift;<br />
$priority = convert_priority($priority);<br />
my $ticket = new RT::Ticket($RT::SystemUser);<br />
$ticket->Load($ticket_id);<br />
$ticket->SetPriority($priority);<br />
<br />
return ($ticket_id, "ngigrnet");<br />
}<br />
<br />
# Change status<br />
# params:<br />
# id: int, from ggus<br />
# status: string<br />
sub set_status {<br />
RT::LoadConfig();<br />
RT::Init();<br />
<br />
my $num_args = 2;<br />
unless (@_ >= $num_args) {<br />
$RT::Logger->log(<br />
level => 'err',<br />
message => 'Not enough arguments.'<br />
);<br />
return (0, "ngigrnet");<br />
}<br />
<br />
my $ggus_id = shift;<br />
unless (is_int($ggus_id)) {<br />
$RT::Logger->log(level=>'alert', message => "Requested ticket from ggus $ggus_id");<br />
return (0, "ngigrnet");<br />
}<br />
<br />
my $ticket_id = ggus_to_rt($ggus_id);<br />
my $status = shift;<br />
$status = convert_status($status);<br />
my $ticket = new RT::Ticket($RT::SystemUser);<br />
$ticket->Load($ticket_id);<br />
$ticket->SetStatus($status);<br />
<br />
return ($ticket_id, "ngigrnet");<br />
}<br />
<br />
# Handle attachments.<br />
# Add them as part of a MIMEEntity. parameteres are passwd as references.<br />
# MIMEContent: MIMEEntity, where to add the attachment<br />
# atch_data: base64string, the data of the attachment<br />
# atch_type: string, the MIME type of the attachment<br />
# atch_filename: string, the filename of the attachment<br />
sub add_attachment_to_mimeobj {<br />
unless (@_ == 4) {<br />
die 'Incorrect number of arguments.';<br />
}<br />
my $MIMEContent = shift;<br />
my $atch_data = shift;<br />
my $atch_type = shift;<br />
my $atch_filename = shift;<br />
<br />
$atch_data = MIME::Base64::decode_base64($atch_data);<br />
<br />
<br />
$$MIMEContent->make_multipart;<br />
$$MIMEContent->attach(<br />
Data => [ $atch_data ],<br />
Type => $atch_type,<br />
Filename => $atch_filename,<br />
);<br />
}<br />
<br />
# Check if argument(s) is(are) integers.<br />
sub is_int {<br />
for (@_) {<br />
return 0 if (/\D/);<br />
}<br />
return 1;<br />
}<br />
<br />
# Mark transaction as done<br />
sub mark_transaction_done {<br />
my $id = shift;<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
my $t = GGUS::Transaction->new( $rt_handle);<br />
$t->LoadByCol('transaction_id', $id);<br />
$t->Setdone(1);<br />
<br />
return 0;<br />
}<br />
<br />
# Convert priority from ggus to rt<br />
sub convert_priority {<br />
my $priority = shift;<br />
$RT::Logger->log(level=>'crit', message => "Requested ticket with priority $priority");<br />
my %priorities = (<br />
'less urgent' => 0,<br />
'urgent' => 50,<br />
'very urgent' => 75,<br />
'top priority' => 99,<br />
);<br />
return $priorities{$priority};<br />
}<br />
<br />
# Convert status from ggus to rt<br />
sub convert_status {<br />
my $status = shift;<br />
return "resolved" if ($status eq "solved");<br />
return "open";<br />
}<br />
<br />
# Set the creator and created to transaction<br />
sub trans_set_creat {<br />
my $transaction = shift;<br />
my $user = shift;<br />
my $query_t = "UPDATE Transactions SET Creator=? WHERE id=?";<br />
my $query_a = "UPDATE Attachments SET Creator=? WHERE TransactionId=?";<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
$rt_handle->BeginTransaction;<br />
$rt_handle->SimpleQuery($query_t, $user, $transaction);<br />
$rt_handle->SimpleQuery($query_a, $user, $transaction);<br />
$rt_handle->Commit;<br />
}<br />
<br />
# Set the creator to transaction<br />
sub trans_set_creator {<br />
my $transaction = shift;<br />
my $user = shift;<br />
my $query = "UPDATE Transactions SET Creator=? WHERE id=?";<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
$rt_handle->BeginTransaction;<br />
$rt_handle->SimpleQuery($query, $user, $transaction);<br />
$rt_handle->Commit;<br />
}<br />
# Set create fields for new tickets<br />
# params:<br />
# ticket: id<br />
# user: id<br />
sub ticket_set_creat {<br />
my $ticket = shift;<br />
my $user = shift;<br />
my $query = "UPDATE Tickets SET Creator=? WHERE id=?";<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
$rt_handle->BeginTransaction;<br />
$rt_handle->SimpleQuery($query, $user, $ticket);<br />
$rt_handle->Commit;<br />
}<br />
<br />
# Get rt id from ggus id<br />
# params:<br />
# ggus_id<br />
# returns:<br />
# ticket_id<br />
sub ggus_to_rt {<br />
my $ggus_id = shift;<br />
<br />
my $rt_handle = $RT::Handle->new($RT::SystemUser);<br />
my $query = 'SELECT rt_id FROM ggus_rt WHERE ggus_id=?';<br />
my @res = $rt_handle->FetchResult($query, ($ggus_id, ));<br />
unless (@res) {<br />
$RT::Logger->log(<br />
level => 'err', <br />
message => "No rt ticket for ggus $ggus_id"<br />
);<br />
exit(0);<br />
}<br />
my $ticket_id = $res[0];<br />
return $ticket_id;<br />
}<br />
<br />
# Get the MIME type of base64 encoded data<br />
# params:<br />
# $data base64 encoded data<br />
sub get_mime_type {<br />
my $data = shift;<br />
my $raw_data = MIME::Base64::decode($data);<br />
my $sh = new IO::Scalar \$raw_data;<br />
return File::MimeInfo::Magic::mimetype($sh);<br />
}<br />
<br />
sub get_queue {<br />
my $site = shift;<br />
return "GR-01-AUTH" if ($site eq "GR-01-AUTH");<br />
return "GR-02-UoM" if ($site eq "GR-02-UoM");<br />
return "GR-03-HEPNTUA" if ($site eq "GR-03-HEPNTUA");<br />
return "GR-04-FORTH-ICS" if ($site eq "GR-04-FORTH-ICS");<br />
return "GR-05-DEMOKRITOS" if ($site eq "GR-05-DEMOKRITOS");<br />
return "GR-06-IASA" if ($site eq "GR-06-IASA");<br />
return "GR-07-UOI-HEPLAB" if ($site eq "GR-07-UOI-HEPLAB");<br />
return "GR-08-CEID" if ($site eq "GR-08-CEID");<br />
return "GR-09-UoA" if ($site eq "GR-09-UoA");<br />
return "GR-10-UOI" if ($site eq "GR-10-UOI");<br />
return "HG-01-GRNET" if ($site eq "HG-01-GRNET");<br />
return "HG-02-IASA" if ($site eq "HG-02-IASA");<br />
return "HG-03-AUTH" if ($site eq "HG-03-AUTH");<br />
return "HG-04-CTI-CEID" if ($site eq "HG-04-CTI-CEID");<br />
return "HG-05-FORTH" if ($site eq "HG-05-FORTH");<br />
return "HG-06-EKT" if ($site eq "HG-06-EKT");<br />
return "NGI_GRNET";<br />
}</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_GRNET:RT_GGUS_Integration&diff=2446NGI GRNET:RT GGUS Integration2010-08-25T11:44:57Z<p>Vgkamas: </p>
<hr />
<div>=== Scope === <br />
<br />
The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of SOAP messages. GGUS has already implemented some web services, (used for example for the integration with the SEE Helpdesk), so the necessary web services must have been implemented at the HellasGrid RT.<br />
<br />
There are three possible scenarios implemented:<br />
<br />
* '''Scenario 1''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 2''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 3''': A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. <br />
<br />
At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system.<br />
<br />
=== Implementation === <br />
<br />
For the needs of the implementation the following queues was implemented at the HellasGrid RT:<br />
<br />
* A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.<br />
* A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.<br />
* A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned. <br />
<br />
The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file [[ticket.cgi]] located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.<br />
<br />
''' Ticket creation at GGUS ''' <br />
<br />
The HellasGrid RT web services are called by the file ggus_client.pl located at the path /root/ws which is automatically executed every 5 minutes. This service checks if a transaction has occurred from the last time it was called, and in a case of a transaction the appropriate ticket at the GGUS is updated.<br />
<br />
The information regarding the correspondence of the two systems is kept at the rtdb database and more specific at the ggus_rt and ggus_transactions tables (which were created). At the table ggus_rt is stored the correspondence between the ID of a ticket at the GGUS and the ID of a ticket at the HellasGrid RT. This is done every time that a ticket at the GGUS is assigned at the NGI_GRNET support unit or at a site under the scope of the NGI_GRNET. At the table ggus_transactions are stored the IDs of the transactions which concern the corresponding tickets at the ggus_rt. This is done via the use of scrips, that is Perl hooks which can be defined at the RT and can be executed at different time instances.<br />
<br />
So, the database has the role of a message queuing system. Due to the low creation rate of tickets at the HellasGrid RT, was not used a specialized queuing system. Also another reason for using this solution instead the direct sending of the updates at the GGUS during the processing of a ticket (inside the scrip) is that this implementation results in functionality’s separation, so the call of the GGUS web services is not involved with the processing of the ticket. Also, the delay at the RT due to HTTP web services call is low.<br />
<br />
''' Ticket creation at HellasGrid RT ''' <br />
<br />
For the scenario of a ticket creation at the GGUS queue of the HellasGrid RT, two Perl script are used, the ggus_create.pl and the ggus_client.pl scripts. The first Perl script is used for the creation of a ticket at the GGUS system. Every time that a ticket is created at the GGUS queue of the HellasGrid RT, a scrip is called which stores the ID of the new ticket at a table named ggus_queue. This ID is used by the ggus_create.pl script in order to create the ticket at the GGUS system. The ggus_create.pl script is called with a cron job every 5 minutes, scans the ggus_queue table and if a new ticket exists, then a ticket is created at the GGUS system, by calling the appropriate web service. Also, a new entry is created at the ggus_rt table which stores the correspondence between the tickets created at the two systems.<br />
<br />
=== Web Services === <br />
<br />
The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system.</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_GRNET:RT_GGUS_Integration&diff=2445NGI GRNET:RT GGUS Integration2010-08-25T11:43:43Z<p>Vgkamas: </p>
<hr />
<div>=== Scope === <br />
<br />
The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of SOAP messages. GGUS has already implemented some web services, (used for example for the integration with the SEE Helpdesk), so the necessary web services must have been implemented at the HellasGrid RT.<br />
<br />
There are three possible scenarios implemented:<br />
<br />
* '''Scenario 1''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 2''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 3''': A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. <br />
<br />
At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system.<br />
<br />
=== Implementation === <br />
<br />
For the needs of the implementation the following queues was implemented at the HellasGrid RT:<br />
<br />
* A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.<br />
* A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.<br />
* A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned. <br />
<br />
The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file [ticket.cgi] located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.<br />
<br />
''' Ticket creation at GGUS ''' <br />
<br />
The HellasGrid RT web services are called by the file ggus_client.pl located at the path /root/ws which is automatically executed every 5 minutes. This service checks if a transaction has occurred from the last time it was called, and in a case of a transaction the appropriate ticket at the GGUS is updated.<br />
<br />
The information regarding the correspondence of the two systems is kept at the rtdb database and more specific at the ggus_rt and ggus_transactions tables (which were created). At the table ggus_rt is stored the correspondence between the ID of a ticket at the GGUS and the ID of a ticket at the HellasGrid RT. This is done every time that a ticket at the GGUS is assigned at the NGI_GRNET support unit or at a site under the scope of the NGI_GRNET. At the table ggus_transactions are stored the IDs of the transactions which concern the corresponding tickets at the ggus_rt. This is done via the use of scrips, that is Perl hooks which can be defined at the RT and can be executed at different time instances.<br />
<br />
So, the database has the role of a message queuing system. Due to the low creation rate of tickets at the HellasGrid RT, was not used a specialized queuing system. Also another reason for using this solution instead the direct sending of the updates at the GGUS during the processing of a ticket (inside the scrip) is that this implementation results in functionality’s separation, so the call of the GGUS web services is not involved with the processing of the ticket. Also, the delay at the RT due to HTTP web services call is low.<br />
<br />
''' Ticket creation at HellasGrid RT ''' <br />
<br />
For the scenario of a ticket creation at the GGUS queue of the HellasGrid RT, two Perl script are used, the ggus_create.pl and the ggus_client.pl scripts. The first Perl script is used for the creation of a ticket at the GGUS system. Every time that a ticket is created at the GGUS queue of the HellasGrid RT, a scrip is called which stores the ID of the new ticket at a table named ggus_queue. This ID is used by the ggus_create.pl script in order to create the ticket at the GGUS system. The ggus_create.pl script is called with a cron job every 5 minutes, scans the ggus_queue table and if a new ticket exists, then a ticket is created at the GGUS system, by calling the appropriate web service. Also, a new entry is created at the ggus_rt table which stores the correspondence between the tickets created at the two systems.<br />
<br />
=== Web Services === <br />
<br />
The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system.</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_GRNET:RT_GGUS_Integration&diff=2444NGI GRNET:RT GGUS Integration2010-08-25T11:40:00Z<p>Vgkamas: </p>
<hr />
<div>=== Scope === <br />
<br />
The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of SOAP messages. GGUS has already implemented some web services, (used for example for the integration with the SEE Helpdesk), so the necessary web services must have been implemented at the HellasGrid RT.<br />
<br />
There are three possible scenarios implemented:<br />
<br />
* '''Scenario 1''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 2''': A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* '''Scenario 3''': A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. <br />
<br />
At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system.<br />
<br />
=== Implementation === <br />
<br />
For the needs of the implementation the following queues was implemented at the HellasGrid RT:<br />
<br />
* A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.<br />
* A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.<br />
* A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned. <br />
<br />
The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file ticket.cgi located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.<br />
<br />
''' Ticket creation at GGUS ''' <br />
<br />
The HellasGrid RT web services are called by the file ggus_client.pl located at the path /root/ws which is automatically executed every 5 minutes. This service checks if a transaction has occurred from the last time it was called, and in a case of a transaction the appropriate ticket at the GGUS is updated.<br />
<br />
The information regarding the correspondence of the two systems is kept at the rtdb database and more specific at the ggus_rt and ggus_transactions tables (which were created). At the table ggus_rt is stored the correspondence between the ID of a ticket at the GGUS and the ID of a ticket at the HellasGrid RT. This is done every time that a ticket at the GGUS is assigned at the NGI_GRNET support unit or at a site under the scope of the NGI_GRNET. At the table ggus_transactions are stored the IDs of the transactions which concern the corresponding tickets at the ggus_rt. This is done via the use of scrips, that is Perl hooks which can be defined at the RT and can be executed at different time instances.<br />
<br />
So, the database has the role of a message queuing system. Due to the low creation rate of tickets at the HellasGrid RT, was not used a specialized queuing system. Also another reason for using this solution instead the direct sending of the updates at the GGUS during the processing of a ticket (inside the scrip) is that this implementation results in functionality’s separation, so the call of the GGUS web services is not involved with the processing of the ticket. Also, the delay at the RT due to HTTP web services call is low.<br />
<br />
''' Ticket creation at HellasGrid RT ''' <br />
<br />
For the scenario of a ticket creation at the GGUS queue of the HellasGrid RT, two Perl script are used, the ggus_create.pl and the ggus_client.pl scripts. The first Perl script is used for the creation of a ticket at the GGUS system. Every time that a ticket is created at the GGUS queue of the HellasGrid RT, a scrip is called which stores the ID of the new ticket at a table named ggus_queue. This ID is used by the ggus_create.pl script in order to create the ticket at the GGUS system. The ggus_create.pl script is called with a cron job every 5 minutes, scans the ggus_queue table and if a new ticket exists, then a ticket is created at the GGUS system, by calling the appropriate web service. Also, a new entry is created at the ggus_rt table which stores the correspondence between the tickets created at the two systems.<br />
<br />
=== Web Services === <br />
<br />
The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system.</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_GRNET:RT_GGUS_Integration&diff=2443NGI GRNET:RT GGUS Integration2010-08-25T11:39:27Z<p>Vgkamas: </p>
<hr />
<div>=== Scope === <br />
<br />
The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of SOAP messages. GGUS has already implemented some web services, (used for example for the integration with the SEE Helpdesk), so the necessary web services must have been implemented at the HellasGrid RT.<br />
<br />
There are three possible scenarios implemented:<br />
<br />
* Scenario 1: A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* Scenario 2: A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* Scenario 3: A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. <br />
<br />
At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system.<br />
<br />
=== Implementation === <br />
<br />
For the needs of the implementation the following queues was implemented at the HellasGrid RT:<br />
<br />
* A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.<br />
* A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.<br />
* A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned. <br />
<br />
The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file ticket.cgi located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.<br />
<br />
''' Ticket creation at GGUS ''' <br />
<br />
The HellasGrid RT web services are called by the file ggus_client.pl located at the path /root/ws which is automatically executed every 5 minutes. This service checks if a transaction has occurred from the last time it was called, and in a case of a transaction the appropriate ticket at the GGUS is updated.<br />
<br />
The information regarding the correspondence of the two systems is kept at the rtdb database and more specific at the ggus_rt and ggus_transactions tables (which were created). At the table ggus_rt is stored the correspondence between the ID of a ticket at the GGUS and the ID of a ticket at the HellasGrid RT. This is done every time that a ticket at the GGUS is assigned at the NGI_GRNET support unit or at a site under the scope of the NGI_GRNET. At the table ggus_transactions are stored the IDs of the transactions which concern the corresponding tickets at the ggus_rt. This is done via the use of scrips, that is Perl hooks which can be defined at the RT and can be executed at different time instances.<br />
<br />
So, the database has the role of a message queuing system. Due to the low creation rate of tickets at the HellasGrid RT, was not used a specialized queuing system. Also another reason for using this solution instead the direct sending of the updates at the GGUS during the processing of a ticket (inside the scrip) is that this implementation results in functionality’s separation, so the call of the GGUS web services is not involved with the processing of the ticket. Also, the delay at the RT due to HTTP web services call is low.<br />
<br />
''' Ticket creation at HellasGrid RT ''' <br />
<br />
For the scenario of a ticket creation at the GGUS queue of the HellasGrid RT, two Perl script are used, the ggus_create.pl and the ggus_client.pl scripts. The first Perl script is used for the creation of a ticket at the GGUS system. Every time that a ticket is created at the GGUS queue of the HellasGrid RT, a scrip is called which stores the ID of the new ticket at a table named ggus_queue. This ID is used by the ggus_create.pl script in order to create the ticket at the GGUS system. The ggus_create.pl script is called with a cron job every 5 minutes, scans the ggus_queue table and if a new ticket exists, then a ticket is created at the GGUS system, by calling the appropriate web service. Also, a new entry is created at the ggus_rt table which stores the correspondence between the tickets created at the two systems.<br />
<br />
=== Web Services === <br />
<br />
The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system.</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=NGI_GRNET:RT_GGUS_Integration&diff=2442NGI GRNET:RT GGUS Integration2010-08-25T11:38:45Z<p>Vgkamas: Created page with '=== Scope === The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of …'</p>
<hr />
<div>=== Scope === <br />
<br />
The main scope of this task is the implementation of the automatic communication between the GGUS and HellasGrid Request Tracker (RT) systems via the exchange of SOAP messages. GGUS has already implemented some web services, (used for example for the integration with the SEE Helpdesk), so the necessary web services must have been implemented at the HellasGrid RT.<br />
<br />
There are three possible scenarios implemented:<br />
<br />
* Scenario 1: A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at the NGI_GRNET support unit, using the “Assign to ROC/NGI” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* Scenario 2: A ticket is created at the GGUS, where the ticket submitter or the TPM on duty team assigns the ticket at a site in the scope of the NGI_GRNET, using the “Notify SITE” field of the “Submit ticket” form of the GGUS. In this scenario, a corresponding ticket must be created at the appropriate queue of the HellasGrid RT.<br />
* Scenario 3: A ticket is created at the HellasGrid RT, where the ticket submitter assigns the ticket at the GGUS support unit. In this scenario, a corresponding ticket must be created at the GGUS. <br />
<br />
At all the scenarios, when a ticket is resolved/re-opened at the HellasGrid RT (GGUS) then the corresponding ticket must been by resolved/re-opened at the GGUS (HellasGrid RT) system.<br />
<br />
=== Implementation === <br />
<br />
For the needs of the implementation the following queues was implemented at the HellasGrid RT:<br />
<br />
* A queue with name NGI_GRNET. For every ticket assigned to the NGI_GRNET support unit at the GGUS, a new ticket is created at the NGI_GRNET queue.<br />
* A queue for every site under the scope of the NGI_GRNET. For every ticket assigned to a site in the scope of NGI_GRNET support unit at the GGUS, a new ticket is created at the corresponding site’s queue at the HellasGrid RT.<br />
* A queue with name GGUS. For every ticket assigned to the GGUS queue at the HelalsGrid RT, a new ticket is created at the GGUS which is initially un-assigned. <br />
<br />
The implementation was done with the use of the Perl programming language, in order to reuse the HellasGrid RT code for the access and the administration of the tickets stored at the HellasGrid RT database. For the web services implementation, the Perl module SOAP::Lite (http://www.soaplite.com/) was used. The code of the web service implemented is in the file ticket.cgi located at the path /usr/lib/cgi. It is a cgi script which provides 3 call functions for a ticket creation, a ticket update, and for sending an attachment within a ticket.<br />
<br />
''' Ticket creation at GGUS ''' <br />
<br />
The HellasGrid RT web services are called by the file ggus_client.pl located at the path /root/ws which is automatically executed every 5 minutes. This service checks if a transaction has occurred from the last time it was called, and in a case of a transaction the appropriate ticket at the GGUS is updated.<br />
<br />
The information regarding the correspondence of the two systems is kept at the rtdb database and more specific at the ggus_rt and ggus_transactions tables (which were created). At the table ggus_rt is stored the correspondence between the ID of a ticket at the GGUS and the ID of a ticket at the HellasGrid RT. This is done every time that a ticket at the GGUS is assigned at the NGI_GRNET support unit or at a site under the scope of the NGI_GRNET. At the table ggus_transactions are stored the IDs of the transactions which concern the corresponding tickets at the ggus_rt. This is done via the use of scrips, that is Perl hooks which can be defined at the RT and can be executed at different time instances.<br />
<br />
So, the database has the role of a message queuing system. Due to the low creation rate of tickets at the HellasGrid RT, was not used a specialized queuing system. Also another reason for using this solution instead the direct sending of the updates at the GGUS during the processing of a ticket (inside the scrip) is that this implementation results in functionality’s separation, so the call of the GGUS web services is not involved with the processing of the ticket. Also, the delay at the RT due to HTTP web services call is low.<br />
<br />
''' Ticket creation at HellasGrid RT ''' <br />
<br />
For the scenario of a ticket creation at the GGUS queue of the HellasGrid RT, two Perl script are used, the ggus_create.pl and the ggus_client.pl scripts. The first Perl script is used for the creation of a ticket at the GGUS system. Every time that a ticket is created at the GGUS queue of the HellasGrid RT, a scrip is called which stores the ID of the new ticket at a table named ggus_queue. This ID is used by the ggus_create.pl script in order to create the ticket at the GGUS system. The ggus_create.pl script is called with a cron job every 5 minutes, scans the ggus_queue table and if a new ticket exists, then a ticket is created at the GGUS system, by calling the appropriate web service. Also, a new entry is created at the ggus_rt table which stores the correspondence between the tickets created at the two systems.<br />
<br />
=== Web Services === <br />
<br />
The wsdl file which completely describes the provisioned web services is located at the url http://rt-ws.hellasgrid.gr/rt.wsdl. The web services are also listen to this hostname. Also, the rt-ws.hellasgrid.gr is alias to rt.hellasgrid.gr. It was chosen a different hostname, in order to restrict the web services to be called only by the IP address of the GGUS system.</div>Vgkamashttps://wiki.egi.eu/w/index.php?title=GGUS-RT_Interface_Task_Force&diff=2440GGUS-RT Interface Task Force2010-08-25T10:07:16Z<p>Vgkamas: </p>
<hr />
<div>=== GGUS-RT Interface Task Force ===<br />
<br />
* [[NGI_CZ:RT_GGUS_Integration|Description of current NGI_CZ RT - GGUS interface]]<br />
* [[NGI_GRNET:RT_GGUS_Integration|Description of current NGI_GRNET RT - GGUS interface]]</div>Vgkamas