EGI-InSPIRE:Greece-QR13

From EGIWiki
(Redirected from OMB:Greece-QR13)
Jump to: navigation, search
EGI Inspire Main page


Inspire reports menu: Home SA1 weekly Reports SA1 Task QR Reports NGI QR Reports NGI QR User support Reports


Contents


Quarterly Report Number NGI Name Partner Name Author
<Number of Quarterly report> <NGI Name> <NGI Country> <Name of person submitting the QR>


1. MEETINGS AND DISSEMINATION

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

1.1. CONFERENCES/WORKSHOPS ORGANISED

Date Location Title Participants Outcome (Short report & Indico URL)
<Date> <Location> <Title> <Participants> <Outcome>
<Date> <Location> <Title> <Participants> <Outcome>
<Date> <Location> <Title> <Participants> Test

1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED

Date Location Title Participants Outcome (Short report & Indico URL)
<Date> <Location> Title Participants Outcome
<Date> <Location> Title Participants Outcome
<Date> <Location> Title Participants Outcome Test


1.3. PUBLICATIONS

Publication title Journal / Proceedings title Journal references
Volume number
Issue

Pages from - to
Authors
1.
2.
3.
Et al?
<Publication title> <Journal/Proceedings> Vol:<volume number>
Issue:<Issue>
Pg: <from> - <to>
1.<Author 1>
2.<Author2>
3. <Author3>
<Publication title> <Journal/Proceedings> Vol:<volume number>
Issue:<Issue>
Pg: <from> - <to>
1.<Author 1>
2.<Author2>
3. <Author3>
<Publication title> <Journal/Proceedings> Vol:<volume number>
Issue:<Issue>
Pg: <from> - <to>
1.<Author 1>
2.<Author2>
3. <Author3>

2. ACTIVITY REPORT

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

2.3. Issues and mitigation

Issue Description 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.

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Print/export