Difference between revisions of "Agenda-01-06-2012"
Jump to navigation
Jump to search
Line 29: | Line 29: | ||
# '''Accounting data is published through aggregated records''' (''Those sites are not in the list below'') | # '''Accounting data is published through aggregated records''' (''Those sites are not in the list below'') | ||
# '''APEL publisher is not properly configured''' | # '''APEL publisher is not properly configured''' | ||
#: In the APEL publisher configuration file the directive ''publishGlobalUserName'' is by default set to ''NO''. ''<JoinProcessor publishGlobalUserName="yes">'' | #: In the APEL publisher configuration file the directive ''publishGlobalUserName'' is by default set to ''NO''. It to enable userDN publication it should be: ''<JoinProcessor publishGlobalUserName="yes">'' | ||
#: The YAIM directive "''APEL_PUBLISH_USER_DN''" should be "''yes''" | #: The YAIM directive that triggers this configuration is"''APEL_PUBLISH_USER_DN''", and it should be "''yes''" | ||
#: If a site in the list below is misconfigured and wants to publish the UserDNs, the steps are: | #: If a site in the list below is misconfigured and wants to publish the UserDNs, the steps are: | ||
#* Reconfigure the APEL publisher with the correct configuration (this will enable the UserDN publication in the usage record published from now on) | #* Reconfigure the APEL publisher with the correct configuration (this will enable the UserDN publication in the usage record published from now on) |
Revision as of 10:46, 1 June 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Detailed agenda: Grid Operations Meeting 1 June 2012 14h00 Amsterdam time (Friday)
EVO direct link | Pwd: gridops |
EVO details | Indico page |
1. Middleware releases and staged rollout
1.1 EMI release status
1.2 Staged Rollout
2. Operational Issues
2.1 Sites not publishing user DN in the usage record
In the infrastructure - in May - there were more than 90 sites not publishing the UserDN. The possible reasons are:
- NGIs/Sites who do not want to publish the UserDN, for privacy reasons
- A policy decision, it is not in topic for today
- Accounting data is published through aggregated records (Those sites are not in the list below)
- APEL publisher is not properly configured
- In the APEL publisher configuration file the directive publishGlobalUserName is by default set to NO. It to enable userDN publication it should be: <JoinProcessor publishGlobalUserName="yes">
- The YAIM directive that triggers this configuration is"APEL_PUBLISH_USER_DN", and it should be "yes"
- If a site in the list below is misconfigured and wants to publish the UserDNs, the steps are:
- Reconfigure the APEL publisher with the correct configuration (this will enable the UserDN publication in the usage record published from now on)
- To re-publish the previous usage records with the UserDN, please open a GGUS ticket vs the APEL support unit. This action will require central coordination.
- DN encryption affected by a problem with a java library
- As reported in this GGUS ticket
- The problem is affecting few sites (<15) that will be contacted by the APEL staff to solve the issue
- List of sites not publishing userDN
- ACTION: on the NGIs, follow up with your sites in the list, and provide comments in the table.