1 / 17

Update on Version Control Services at CERN

Update on Version Control Services at CERN. Giacomo Tenaglia , Hugo Jonatan Hugosson , Artur Wiecek , Alvaro Gonzalez Alvarez, Manuel Guijarro HEPiX Fall ’09 Meeting, LBNL. Agenda. Overview of VCS at CERN Subversion hosting VCS Roadmap Conclusions. VCS at CERN. CVS Started on 2000

jacie
Download Presentation

Update on Version Control Services at CERN

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. Update onVersion Control Servicesat CERN GiacomoTenaglia, Hugo JonatanHugosson, ArturWiecek, Alvaro Gonzalez Alvarez, Manuel Guijarro HEPiX Fall ’09 Meeting, LBNL

  2. Agenda • Overview of VCS at CERN • Subversion hosting • VCS Roadmap • Conclusions Update on VCS at CERN - 2

  3. VCS at CERN • CVS • Started on 2000 • >60 Active Projects, >23K commits/month • AFS-centric • LCGCVS • Started on 2002 • ~20 Active Projects, >22K commits/month • FS-based (faster access) • Subversion • Pilot: June 2008, Production: January 2009 • >110 Active Projects, >33K commits/month Update on VCS at CERN - 3

  4. VCS at CERN (2) • CVS to Subversion Migration • Campaign started on January 2009 • 34 CVS projects have migrated(*) so far, including: • ATLAS (Offline, Groups and Documents) • CMS Online and DAQ • CASTOR • 0 LCGCVS projects have migrated(*) so far • Tentative CVS shutdown (write access): • End 2009 • End 2010 • Beginning 2011 (*) based on spontaneous declarations by librarians Update on VCS at CERN - 4

  5. Usage Statistics Update on VCS at CERN - 5

  6. Support Requests Update on VCS at CERN - 6

  7. Subversion Hosting Golden Rule: “Thou Shalt Not Provide Personalizations” Update on VCS at CERN - 7

  8. SVN Service Design Update on VCS at CERN - 8

  9. SVN Service Design (2) • Repository access • “Core business” • Restricted shell (SVN+SSH) • Minimal Webserverconfig (HTTPS) • Hooks chrooted • Web interface(s) • WebSVN • Trac (yes, it’s also a ticketing system) • Standard CERN SSO authenticated access Update on VCS at CERN - 9

  10. SVN Service Design (3) • Administration delegated to librarians: • AuthZ management • Versioning of config files • Hooks personalization • Trac administrator privileges • Usage statistics • Personal repositories • Lifetime = account lifetime • Limited quota Update on VCS at CERN - 10

  11. SVN Service Design (4) • Librarians and Users have influence on: • Architecture and Standards (eg: NFS for Trac) • Functional Requirements (eg: HTTPS Access) • Usability Requirements (eg: Migration Recipes) • KPI (eg: Single repository availability) • SVN Forum twice a year: • Meet users in non-stressful situations • Review of major changes and incidents • Presentation of current development efforts • Proposals for future changes and discussion Update on VCS at CERN - 11

  12. SVN Service Operation • Built on top of standard CERN IT tools: • HelpDesk • Change Management (TBD) • Incident Management (Remedy) • Access Management (E-Groups, CERN SSO) • Monitoring and Control (LEMON, SLS) • IT Operations (SLC, Quattor, TSM, AFS) • Complemented by standard DES tools: • Functional Monitoring (Oracle EM) • Extended IT Operations (OffSite Backup) • NAS-based storage (NFS) Update on VCS at CERN - 12

  13. SVN: Open Issues • CVS Migration • “Tags Blues” • Big success stories help.. sometimes • 100% User-driven • Not your “standard” FLOSS-based service • AFS limitation on max files per dir: upgrade to SVN 1.5 Server-side • “Endless checkout” problem for statistics generation: change tool Update on VCS at CERN - 13

  14. SVN: More Open Issues • Clients madness • “1.5 is strongly recommended for branching/merging” (SVN Book) • SL5 has only 1.4 • Server is 1.5 (“version envy”) • Security is a trade-off • Less flexibility • Slower request fulfillment • Full-blown test environment/sandbox • Lack of it Update on VCS at CERN - 14

  15. VCS Roadmap • LCGCVS: Migration to “standard” CVS • Measure performance • CVS: Guess what ? • We rely on librarians will.. • SVN: Usability and Maintainability • User-centricness (docs, “My projects” page) • Fully move to NFS Storage Update on VCS at CERN - 15

  16. Conclusions • VCS hosting is not trivial: • Users know clearly what they want (eg: Trac popularity) • Being up to date is essential • Communication with Users is useful: • Are we correctly measuring our Service ? • Are we implementing the right standards ? • Which percentage of the functionalities are actually used ? • ITIL (in our case) works! Update on VCS at CERN - 16

  17. Questions(maybe also Answers) ? Thanks for listening! http://cern.ch/((lcg)?cvs|svn) Update on VCS at CERN - 17

More Related