Difference between revisions of "Agenda-12-03-2012"
Jump to navigation
Jump to search
Line 27: | Line 27: | ||
== 2. Operational Issues == | == 2. Operational Issues == | ||
=== 2.1 OPS VO Membership === | === 2.1 OPS VO Membership === | ||
Recently there were few requests to replace some '''ops''' VO members because they were no more part of the NGIs' staff. I would encourage NGIs to replace their ops members as soon as they are not working on this task anymore, if possible: | Recently there were few requests (triggered by the glexec monitoring [https://ggus.eu/ws/ticket_info.php?ticket=79558 tickets])to replace some '''ops''' VO members because they were no more part of the NGIs' staff. I would encourage NGIs to replace their ops members as soon as they are not working on this task anymore, if possible: | ||
# Currently only 2 members per NGI are allowed in ops, it would be important to have both of them active members of the NGI's staff. If the main SAM admin is unavailable(e.g. he needs to wait few days for a new certificate), there is the need for an immediate backup. | # Currently only 2 members per NGI are allowed in ops, it would be important to have both of them active members of the NGI's staff. If the main SAM admin is unavailable(e.g. he needs to wait few days for a new certificate), there is the need for an immediate backup. | ||
# It is also important to have in ops only who strictly needs the membership. | # It is also important to have in ops only who strictly needs the membership. |
Revision as of 18:06, 8 March 2012
Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Detailed agenda: Grid Operations Meeting 27 February 2012 14h00 Amsterdam time
EVO direct link | Pwd: gridops |
EVO details | Indico page |
1. Middleware releases and staged rollout
1.1 EMI-1 release status
1.2 Staged Rollout
UMD-1
2. Operational Issues
2.1 OPS VO Membership
Recently there were few requests (triggered by the glexec monitoring tickets)to replace some ops VO members because they were no more part of the NGIs' staff. I would encourage NGIs to replace their ops members as soon as they are not working on this task anymore, if possible:
- Currently only 2 members per NGI are allowed in ops, it would be important to have both of them active members of the NGI's staff. If the main SAM admin is unavailable(e.g. he needs to wait few days for a new certificate), there is the need for an immediate backup.
- It is also important to have in ops only who strictly needs the membership.