WLCG-OSG-EGEE Ops' Minutes Mon 27 Apr 2009

Summary

Sites in the UK and in SouthEast Europe highlighted the fact that they will rely on strictly 32 bit hardware for some time. As such the final demise of gLite 3.1 as being the last 32 bit release is very significant to them.

Attendance

EGEE

  • Asia Pacific ROC: Jason
  • Central Europe ROC: Malgorzata Krakowian
  • OCC / CERN ROC: John Shade, Antonio Retico, Nick Thackray, Steve Traylen, Dianna
  • French ROC: Pierre Girard, Osman Aidel, Rolf
  • German/Swiss ROC: Sven, Angela
  • Italian ROC: Alessandro Cavalli
  • Northern Europe ROC: Ron Trompert
  • Russian ROC: Lev Shamardin
  • South East Europe ROC: Marios Chatziangelou.
  • South West Europe ROC: Kai Neuffer,Christian Neissner
  • UK/Ireland ROC: Jeremy Coles, Doug McNab, Derek,
  • GGUS: Torsten Antoni
  • GOCDB: Gilles Mathieu

Feedback on Last Week's Minutes

None was given.

EGEE Items

Grid Operator Hand Over on Duty

Quiet Week. No Serious Alarms. Outstanding issues are three tickets at 3rd mail to site admin level. No response received from grid site: MPI-K from the ROC_DECH It looks like the entire site is failing and should probably be put into downtime.

Report from cCOD (SouthWest Europe): Problems with ROC CERN. We don't know if they haven't received mails or notifications, as they haven't reacted to our notifications, they have a lot of "OK" time out and alarms without tickets. Alas, this site just start on C-COD and may be adapting still.

NorthenEruope has GGUS:10045 time out since 10-04-2009

Sites Considered For Suspension

PPS Reports and Issues

gLite Release News

EGEE Items From ROC Reports

  • Central Europe: In CE ROC we have some sites with 32bit machines so we are interested in plans when 32bit glite 3.1 is planed to be discontinued. We need that to check if those sites are able to upgrade till that time.
    • No plans at the moment for when this might happen. Sites should expect some warning.
  • UK/I: SAM results in the ROC report this week are missing? Response from SAM team The query had a problem, a trouble ticket opened with CERN DB. Helen will also follow up if this can be detected and flagged CIC portal side.
  • UK/I: Last August there was a security incident and a UKI site was involved. As a precaution a UKI user was banned at sites pending investigation. No connection with or compromise of this user s account was found. The user still finds that they are banned at some sites - their grid certificate was reissued. What is the procedure here - should the user send GGUS tickets to all sites. Is this a ROC responsibility? Response from EGEE Security Officer: The VO is the entity who can suspend a user. Of course some sites may manually ban the user (and sometimes they are asked to), but usually the problem is solved after the affected site sends its security incident resolution report. However, ultimately, any site can decide to never re-enable the affected user again. In this case the user should contact his VO, who should talk to the sites. When this happens, usually users open a GGUS ticket. To answer specifically to your question, the agreement is between the sites and the VOs (hence the VO should be contacting the site(s), but whenever appropriate (eg: when there is clearly no security risk anymore) the ROC could help and simply recommend to all its sites to un-ban the user. Usually this poses no problem.

REMINDER: Retirement of gLite 3.0
As previously announced, it is planned that all remaining gLite 3.0 services will be retired by the end of April. At this point, all support for these services will cease. All sites should ensure that they are running up-to-date versions of their services. If any site sees a need to keep a gLite 3.0 service in the middleware stack, please submit a GGUS ticket as soon as possible.

List of sites still publishing gLite 3.0 : https://twiki.cern.ch/twiki/bin/view/EGEE/SitesPublishinggLite30

OSG Items

Discussion of open tickets for OSG OSG Information on GOCdb-to-OIM migration for USA wLCG T1 sites

  • GGUS:44104. This ticket is waiting on the OSG GOC to roll out changes to their production BDII that will publish entries by their OSG resource group, not the OSG resource name. This will remove this issue before it gets to the BDII. Next action deadline in OIM is in Feb 2010. Should we close as unsolved to free the escalation reports?
  • GGUS:46988. Nothing happened since my comment of 2009-03-30.
  • GGUS:47716. Misrouted ticket. In status 'Closed' in OIM. Why not in GGUS? Rob/Guenter, please comment in the ticket.
  • GGUS:47786. Urgent. Submitted 2009-04-08!

Newly Created Action Items

Assigned to Due date Description State Closed Notify  
Main.OCC 2007-03-05 Example Action Item 2007-03-06 SteveTraylen   edit

Review of Open Action Items

  • GOCDB extension item. There is a reply. Action will be updated.
  • OSCT Rota. The rota will be supplied.

Open Action Items

IdSubmitterDescriptionCreationDueAssigned To 

Actions Closed in Last 20 Days

IdSubmitterDescriptionCreationDueAssigned ToClosed 

AOB

Next Meeting

The next meeting will be Monday, 4 May 2009 15:00 UTC (16:00 Swiss local time).

  • Attendees can join from 14:45 UTC (15:45 Swiss local time) onwards.
  • The meeting will start promptly at 13:00 UTC (16:00 Swiss local time).
  • To dial in to the conference:
    • Dial +41227676000
    • Enter access code 0148141


These minutes can only be changed by members of:

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2009-04-28 - SteveTraylen
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    EGEE All webs login

This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback