1 / 8

February GDB

February GDB. Jeremy ’ s summary notes. Introduction. Introduction: April meeting cancelled. March in KIT. Future support of EGI services Strategy – rely on EC projects and community funding. EGI workshop (Jan) to confirm priorities Emerging support services for federated cloud

dillon-arnold
Download Presentation

February GDB

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. February GDB Jeremy’s summary notes

  2. Introduction • Introduction: April meeting cancelled. March in KIT. Future support of EGI services • Strategy – rely on EC projects and community funding. • EGI workshop (Jan) to confirm priorities • Emerging support services for federated cloud • Proactive maintenance for ops tools • UMD updates -> quarterly • UMD structure – Core products : Contributing products : Community products • (New) UMD release team to collect plans, track urgent bugs and support integration • WLCG coordination meeting could collect/input WLCG requrements. Concern about funding model.

  3. IPv6 • IPv4 address exhaustion. • Dual stack approach. Users should not notice IPv4 vs IPv6. But VMs mean IPv6 only or private IPv4 used. • OpenAFS – no IPv6 support. • Need to confirm GridPP contribution (Glasgow DPM end-point). IPv6 at RAL. • Short term work on SL5. US-LHCnet SL6 GridFTP. Batch system support? • Testing in 3 phases. Test dual stack; IPV6 only WNs (CERN); full test • • HEPiX IPv6 wiki • https://w3.hepix.org/ipv6-bis/ • • Working group meetings • http://indico.cern.ch/categoryDisplay.py?categId=3538

  4. Status of upgrade • VOMS waiting for EMI-3 in some cases • EMI-1 end of security support: April 30. Alarms from 1st March. • Putting tarball in CVMFS discussed.

  5. WLCG ops • Squid monitoring – register servers in GOCDB/OIM • gLEXec – milestone in two weeks • SHA-2 new CA CERN available soon • FTS3 – new features (mySQL, monitoring…) demonstrated, stress testing now. • Tracking tools: vetting based on IDPs • perfSONAR: Needs to be treated as production service. Needs SAM tests for NGI, GGUS tickets, proactive. MDM vs PS. How to use. • SL6. Green light but no push

  6. Authentication and Authorization • Read access to data: no data world-readable. Local clients can have lower authorization overhead for better performance. • Data ownership issues: perhaps use VOMS groups. Owned by VO…robot certificate. Kerberos access local issue. • Clouds: too early to look at non-trivial features.

  7. Clouds • eGroup. • Topics: image contextualization; VM instantiation and scheduling; VM duration (discussion on move to wall-clock time) • Interfaces not important. Fairshare grid concept – want better than static partition. • Graceful end of VM use?

  8. WG on Storage Federations • Mainly technical aspects • Info at https://twiki.cern.ch/twiki/bin/view/LCG/WLCGStorageFederationsWG. • Glue tools: examples DBs, cronjobs, scripts. Links things not natively designed to work together. • Goals: relax data locality requirement. Make life easier for users. • Interoperability - xrootd • Federation = Worldwide storage cluster • Self-healing • Site analysis cache • Security • Name translations and catalogues • Xrootd good for retries, waiting…. • Why http? Partly community wider than HEP. Rucio. SEless sites.

More Related