Difference between revisions of "EGI-InSPIRE:Ibergrid-QR4"
Jump to navigation
Jump to search
Line 78: | Line 78: | ||
<!-- Provide your test below --> | <!-- Provide your test below --> | ||
# The IBERGRID r-Nagios service has been configured to use Ibergrid core services in a failover. The only service for which there is not a failover mechanism is for MyProxy service. | # The IBERGRID r-Nagios service has been configured to use Ibergrid core services in a failover. The only service for which there is not a failover mechanism is for MyProxy service. | ||
# Start enforcing the support on regional macro VOs. The policy is that sites in the region should provide at least the 20% of their resources to the regional macro VOs indicated as a payment of the international services provided by the NGI. If it is not possible (if the local infrastructure is owned by dedicated projects) sites should select at least one of these macro VOs and provide opportunistic access. Simultaneously the decomission of old regional VOs started. | # Start enforcing the support on regional macro VOs. The policy is that sites in the region should provide at least the 20% of their resources to the regional macro VOs indicated as a payment of the international services provided by the NGI. If it is not possible (if the local infrastructure is owned by dedicated projects) sites should select at least one of these macro VOs and provide opportunistic access. Simultaneously the decomission of old regional VOs started. | ||
# | # Regional VOMS replication scheme implementation in progress. The aim is to keeping DB copies of a main host (MASTER) in a secondary host (SLAVE). By architecture, the slave host will only have read access to the Database entries. | ||
# | # Enforcement of the phase out of EGEE name in the information system. | ||
# Internal discussion of the Resource Centre OLA (ongoing). | # Internal discussion of the Resource Centre OLA (ongoing). | ||
# Produce internal documentation on accounting, benchmarking and on gLite-Cluster node. | # Produce internal documentation on accounting, benchmarking and on gLite-Cluster node. | ||
# | # Following a request from WLCG, we have developed a schema to support TopBDIIs in high availability mode. | ||
# | # Contribution on a best effort basis to the Certification Manual documentation. | ||
# Several IBERGRID sites contributed to the Stage Rollout process. | |||
# Completion of the Survey for supported OS platforms, LB, service management and monitoring (for EMI components). | |||
# Provide input to the list of components from EMI 1.0 that should be integrated in UMD with high priority. | |||
# Both Portugal and Spain have provided self-assessment input of NGI international tasks for MS109. | |||
# Provide feedback to deliverable D4.2 - Annual Report on the EGI Production Infrastructure | |||
# Review of the deliverables D5.2 - Annual Report on the status of the software provisioning activity and the work of DMSU; and D6.3 - Annual Report on the Tools and Services of the Heavy User Communities | |||
# Ibergrid ROD team was invited to share their support model and experience with regional tools during the ROD session in EGI User Forum (https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=210&confId=207) | |||
===2.2. Main Achievements=== | ===2.2. Main Achievements=== |
Revision as of 18:14, 28 April 2011
Quarterly Report Number | NGI Name | Partner Name | Author |
---|---|---|---|
QR4 | Ibergrid | LIP & CSIC | G. Borges (LIP) |
1. MEETINGS AND DISSEMINATION
1.1. CONFERENCES/WORKSHOPS ORGANISED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|
1.2. OTHER CONFERENCES/WORKSHOPS ATTENDED
Date | Location | Title | Participants | Outcome (Short report & Indico URL) |
---|
1.3. PUBLICATIONS
Publication title | Journal / Proceedings title | Journal references Volume number Issue Pages from - to |
Authors 1. 2. 3. Et al? |
---|
2. ACTIVITY REPORT
2.1. Progress Summary
- The IBERGRID r-Nagios service has been configured to use Ibergrid core services in a failover. The only service for which there is not a failover mechanism is for MyProxy service.
- Start enforcing the support on regional macro VOs. The policy is that sites in the region should provide at least the 20% of their resources to the regional macro VOs indicated as a payment of the international services provided by the NGI. If it is not possible (if the local infrastructure is owned by dedicated projects) sites should select at least one of these macro VOs and provide opportunistic access. Simultaneously the decomission of old regional VOs started.
- Regional VOMS replication scheme implementation in progress. The aim is to keeping DB copies of a main host (MASTER) in a secondary host (SLAVE). By architecture, the slave host will only have read access to the Database entries.
- Enforcement of the phase out of EGEE name in the information system.
- Internal discussion of the Resource Centre OLA (ongoing).
- Produce internal documentation on accounting, benchmarking and on gLite-Cluster node.
- Following a request from WLCG, we have developed a schema to support TopBDIIs in high availability mode.
- Contribution on a best effort basis to the Certification Manual documentation.
- Several IBERGRID sites contributed to the Stage Rollout process.
- Completion of the Survey for supported OS platforms, LB, service management and monitoring (for EMI components).
- Provide input to the list of components from EMI 1.0 that should be integrated in UMD with high priority.
- Both Portugal and Spain have provided self-assessment input of NGI international tasks for MS109.
- Provide feedback to deliverable D4.2 - Annual Report on the EGI Production Infrastructure
- Review of the deliverables D5.2 - Annual Report on the status of the software provisioning activity and the work of DMSU; and D6.3 - Annual Report on the Tools and Services of the Heavy User Communities
- Ibergrid ROD team was invited to share their support model and experience with regional tools during the ROD session in EGI User Forum (https://www.egi.eu/indico/contributionDisplay.py?sessionId=9&contribId=210&confId=207)
2.2. Main Achievements
2.3. Issues and mitigation
- We were investigating the possibility of using Robot certificates for the IBERGRID r-Nagios to mitigate the fact that MyProxy represents a single point of failure for the regional moniroting service.
Issue Description | Mitigation Description |
---|