View source for EGI-InSPIRE:Greece-QR13

{{Template:EGI-Inspire menubar}}

{{Template:Inspire_reports_menubar}}
{{TOC_right}}

{| class="wikitable"
|-
! scope="col" | Quarterly Report Number 
! scope="col" | NGI Name 
! scope="col" | Partner Name 
! scope="col" | Author
|-
| &lt;Number of Quarterly report&gt; 
| &lt;NGI Name&gt; 
| &lt;NGI Country&gt; 
| &lt;Name of person submitting the QR&gt;
|}

<!-- 
Fill the second line of the table replacing the <...> stuff with your data.
--> 

== 1. MEETINGS AND DISSEMINATION  ==

Note: Complete the tables below by adding as many rows as needed. 

=== 1.1. CONFERENCES/WORKSHOPS ORGANISED  ===

{| class="wikitable"
|-
! scope="col" | Date 
! Location 
! Title 
! Participants 
! Outcome (Short report &amp; Indico URL)
|-
| &lt;Date&gt; 
| &lt;Location&gt; 
| &lt;Title&gt; 
| &lt;Participants&gt; 
| &lt;Outcome&gt;
|-
| &lt;Date&gt; 
| &lt;Location&gt; 
| &lt;Title&gt; 
| &lt;Participants&gt; 
| &lt;Outcome&gt;
|-
| &lt;Date&gt; 
| &lt;Location&gt; 
| &lt;Title&gt; 
| &lt;Participants&gt; 
| Test <!-- formatting_test -->
|}

=== 1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED  ===

{| class="wikitable"
|-
! scope="col" | Date 
! Location 
! Title 
! Participants 
! Outcome (Short report &amp; Indico URL)
|-
| &lt;Date&gt; 
| &lt;Location&gt; 
| Title 
| Participants 
| Outcome
|-
| &lt;Date&gt; 
| &lt;Location&gt; 
| Title 
| Participants 
| Outcome
|-
| &lt;Date&gt; 
| &lt;Location&gt; 
| Title 
| Participants 
| Outcome Test <!-- formatting text -->
|}

<!--
 Please, fill the fields replacing <...> sections with your data. You can add a line copyng the two lines:
|<Date>||<Location>||Title||Participants||Outcome 
|-
--> 

===1.3. PUBLICATIONS=== <!--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.--> 

{| class="wikitable"
|-
! 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?''
|-
| &lt;Publication title&gt; 
| &lt;Journal/Proceedings&gt; 
| Vol:&lt;volume number&gt;<br>Issue:&lt;Issue&gt;<br>Pg: &lt;from&gt; - &lt;to&gt; 
| 1.&lt;Author 1&gt;<br>2.&lt;Author2&gt;<br>3. &lt;Author3&gt;<br>
|-
| &lt;Publication title&gt; 
| &lt;Journal/Proceedings&gt; 
| Vol:&lt;volume number&gt;<br>Issue:&lt;Issue&gt;<br>Pg: &lt;from&gt; - &lt;to&gt; 
| 1.&lt;Author 1&gt;<br>2.&lt;Author2&gt;<br>3. &lt;Author3&gt;<br>
|-
| &lt;Publication title&gt; 
| &lt;Journal/Proceedings&gt; 
| Vol:&lt;volume number&gt;<br>Issue:&lt;Issue&gt;<br>Pg: &lt;from&gt; - &lt;to&gt; 
| 1.&lt;Author 1&gt;<br>2.&lt;Author2&gt;<br>3. &lt;Author3&gt;<br>
|}

== 2. ACTIVITY REPORT == <!--''Note: just report activities relevant to this Quarter.''--> 

===2.1. Progress Summary=== 


Early Adopters:

The services tested for the reporting period are:

Ige-gw-metascheduler-5.14.0
Emi-3.0.1-UI-SL6
Emi-3-dpm-1.8.6-3
Emi-3-bdii-core-1.5.1
Emi-3-cream-1.15.1

All the services were accepted. The only problems found were in Cream:

Problem with id 156 occured. The workaround was applied:

In /opt/glite/yaim/examples/edgusers.conf 156 was changed to 256.


Also the following GGUS ticket was opened:
https://ggus.eu/ws/ticket_info.php?ticket=94518
for waiting jobs 444444.
Lastly, the update from APEL UMD-2 to UMD-3 was done but not in the Stage Rollout process.
The following ticket was opened:
https://ggus.eu/ws/ticket_info.php?ticket=94509

===2.2. Main Achievements=== <!--
Provide your text below
-->
* expanded HG-08-Okeanos to have 48 WNs and upgraded them to UMD-3
* All services with the exception of VOMs (see issue bellow) and one wms are SHA-2 ready
* Preparation of the HellasGRID CA and Seegrid CA (catch all) for SHA-2 support  according to eugridpma road map.
* Deployed CVMFS over NFS on most sites
* Planning to deploy CVMFS stratum 0 service
* Volunteered to be early adopters for VOMS and Dcache on top of cream and wms.

=== 2.3. Issues and mitigation  ===

{| class="wikitable"
|-
! scope="col" | Issue Description 
! scope="col" | Mitigation Description
|-
| Issue description 
| Issue mitigation
|}

The issues that are standing between the full migration of dteam VO from VOMRS to VOMS are not relevant to the migration itself (we have seen that this has worked without major issues) but with the way users and their registration is handled in VOMS. 

Up until the latest version of VOMS we have tested the only group of persons that are allowed to handle a VO registration request (regardless of the sub-group for which the user requests registration) are the people that have been assigned the VO-Admin role on a top level hierarchy. 

Given that the dteam VO is a highly distributed VO and that decisions on who becomes a member should be handled by NGI representatives per NGI (and not directly by a VO-Admin group as is frequently the case in VOMS) such advanced features should be satisfied. 

Currently we have deployed a testing VOMS instance with VOMS Admin version 3.2.0 and we are running some checks to see if these features are after all included in the latest release of the software.
<!--
 Please, fill the table below. You can add a line copyng the two lines
|-
| Issue Description || Issue mitigation
-->