1 / 9

Enterprise iRODS

Enterprise iRODS. Leesa Brieger Terrell Russell. Enterprise iRODS: E-iRODS. RENCI’s and UNC’s long-term support for iRODS Target new funding models for sustainability – move beyond traditional public research funds Beta 2 release based on iRODS 3.0 out in June 2012 at e-irods.org

cosima
Download Presentation

Enterprise iRODS

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. Enterprise iRODS Leesa Brieger Terrell Russell

  2. Enterprise iRODS: E-iRODS • RENCI’s and UNC’s long-term support for iRODS • Target new funding models for sustainability – move beyond traditional public research funds • Beta 2 release based on iRODS 3.0 out in June 2012 at e-irods.org • Organization: • Research code (DICE) released about every 4 months • Enterprise code (RENCI) released about every 18 months • Service agreements and consulting negotiable • E-iRODS Consortium to fund Enterprise support infrastructure PRACE iRODS Workshop, Sept 2012

  3. E-iRODS Goals/Process • Refactorization • Object-oriented • Dependency inversion • Simple modular architecture • Issue Tracking • Prioritized • Issue ownership • Every commit is tagged • Documentation • Doxygen • Administration manual(s) • Compiled from source as well • Automate Everything • Continuous Integration • Code coverage • Static analysis • Testing • unit • functional • Regression • topology • federation • Packaging • EPM generates RPM, DEB, DMG across multiple versions of Operating Systems • Dependency Management PRACE iRODS Workshop, Sept 2012

  4. Testing • 100% test coverage of server-side APIs across selected platforms and topologies: n-way testing across all combinations • Packages released as of June 2012 • DEB (Debian, Ubuntu) • DMG (MacOSX) – Unix client (icommands) • RPM (RHEL, CentOS, Fedora, SUSE) • Planned: • Solaris • Windows (MSI) • MacOSX (servers) • Topologies • Single zone: iCAT server + 2 non-iCAT servers • Federation: two single zones PRACE iRODS Workshop, Sept 2012

  5. RENCI Collaborative Development and Test Environment Git – distributed revision control system GForge – project management system • hosting & version control • bug-tracking • messaging Hudson/Jenkins – Continuous Integration environment: incremental quality control Nexus – Maven repository that tracks dependencies and bundles for check-out (Java) PRACE iRODS Workshop, Sept 2012

  6. Continuous Integration Automated via Hudson (moving to Jenkins) A risk reduction technique Push code frequently to the repository Build & test for each new commit in order to catch defects as early as possible Automated CI removes a level of burden from developers and provides constant insight to the state of the project PRACE iRODS Workshop, Sept 2012

  7. E-iRODS View PRACE iRODS Workshop, Sept 2012

  8. E-iRODS ConsortiumSummary • Membership dues will fund basic E-iRODS development; research funding will keep iRODS development going • E-iRODS remains completely open source (binary and source code) • The Consortium will gather together organizations who depend on the longevity of the iRODS technology, allowing them input and coordination on the roadmap • Membership levels • Affiliate • Access to release roadmap • Privileged access to (paid) consulting and technical support • Professional • Voting rights to release roadmap • Non-voting seat on governing board • Sustaining • Voting seat on governing board PRACE iRODS Workshop, Sept 2012

  9. E-iRODS Consortium • Contacts: Charles Schmitt (cschmitt@renci.org) and Leesa Brieger (leesa@renci.org) • Draft charter document available on request • We are looking for discussions with potential partners • Suggestions and ideas welcome • To reach consensus before formal establishment of the consortium PRACE iRODS Workshop, Sept 2012

More Related