iRODS 4.1 - Build and Test
2015 iRODS User Meeting, Jun 10-11 -- Renaissance Computing Institute (RENCI), Chapel Hill, NC
Terrell Russell, Ph.D.
Renaissance Computing Institute (RENCI)
University of North Carolina at Chapel Hill
Ben Keller
Renaissance Computing Institute (RENCI)
University of North Carolina at Chapel Hill
Motivation and Goals
Build and Test serves multiple purposes. The target audiences include core developers, external developers, users, users’ managers, and grid administrators.
Transparency (in both process and product)
Use of existing industry best practices
Coverage → Confidence in Refactoring
Packaging → Ease of installation and upgrade
Test framework idempotency
Test independence
Topology awareness
Automation, Automation, Automation
The zone_bundle.json schema
Configuration Management
The izonereport iCommand produces a zone_bundle about the entire local Zone. This representation serves two primary, complementary use cases:
Combining these two use cases provides a very powerful effect.
iRODS Build and Test - Yesterday
July 2011
October 2012
January 2013
October 2013
iRODS Build and Test - Today
Spring 2015
This version stands out for two reasons:
iRODS Build and Test - Today
Coverage
Topology Tests
Additional | Cumulative | ||
Standalone single server | 59.2% | 59.2% | observed |
Topology | 2.3% | 61.5% | observed |
Error Checking | ~14% | 75% | estimated |
Untested features | ~25% | 100% | estimated |
iRODS Build and Test - Tomorrow
Fall 2015 (expected)
Features
Thank you
Questions?
Demo!
Terrell Russell, Ph.D
RENCI
Ben Keller
RENCI
Links