Publication Notices

Notifications of New Publications Released by ERDC

Contact Us






ERDC Library Catalog

Not finding what you are looking for? Search the ERDC Library Catalog

Tag: iRODS (Computer system)
  • Integrated Rule-Oriented Data System (iRODS) and High Performance Computing (HPC) Architecture Design

    Abstract: The Integrated Rule-Oriented Data System (iRODS) proof-of-concept will be deployed within the existing U.S. Army Engineer Research and Development Center (ERDC) Department of Defense Supercomputing Resource Center (DSRC) to test additional capabilities and features for high performance computing (HPC) users. iRODS is a data-grid middleware that virtualizes access to data, regardless of which physical storage device the data resides within. Users, and HPC jobs on behalf of users, can leverage the various application programming interfaces (APIs) within iRODS to search and retrieve data using metadata and a unified data namespace. In addition to facilitating data discovery and retrieval, iRODS has a robust security system to implement fine-grained access control and auditing rules.
  • Integrated Rule-Oriented Data System (iRODS) and High Performance Computing (HPC) Project Management Plan

    Abstract: This project management plan (PMP) is established to provide guidance on the management of the Integrated Rule-Oriented Data System (iRODS) Project. The PMP and its associated plans are the primary source of information for how the project will be planned, executed, monitored, controlled, and closed. The intended audience of the plan is all project stakeholders including the project manager (PM), Engineered Resilient Systems (ERS), High-Performance Computing (HPC), and the Geocent project team members.
  • Integrated Rule-Oriented Data System (iRODS) and High Performance Computing (HPC) Requirements Document

    Abstract: The purpose of this report is to capture all relevant use cases, functional requirements, and technical requirements of the Integrated Rule-Oriented Data System (iRODS) prototype. The use cases (UCs) define the system interactions an iRODS user, iRODS administrator, and an auditor would expect within the system. The functional requirements define the expected behavior of the system to support the individual use cases; functional requirements are grouped in reference to the use cases supported by the set of functional requirements. The technical requirements are defined last and include references to specific functional requirements and use cases supported by the requirement.
  • Web-Enabled Interface for iRODS: Comparing Hydroshare and Metalnx

    Abstract: The Integrated Rule-Oriented Data System (iRODS) software provides ample resources for managing data and collections thereof, but there are occasions where utilizing its command line interface (CLI) is impractical or not desirable. One such example is when it is required that the user authenticate using a common access card (CAC), which is more easily accomplished through a graphical user interface (GUI) than through a CLI. Furthermore, restricting the system to only offering a CLI can alienate users who would normally be averse to using a system in such a way, and there are users who are not averse to utilizing a CLI, but who would still benefit from a GUI until they are able to familiarize themselves with the iCommands provided by iRODS. Thus, it becomes imperative to either implement or utilize an existing GUI for the system.
  • Analysis of ERS use cases for iRODs

    Abstract: The purpose of this paper is to discuss the challenges inherent with High Performance Computing (HPC) data storage access and management, the capabilities of iRODS, and the analysis of several Engineered Resilient Systems (ERS) use cases relating iRODS capabilities to the teams’ stated needs. Specifically, these teams are the ERS Data Analytics group (specifically their research on rotorcraft maintenance in conjunction with the U. S. Army Aviation and Missile Research Development and Engineering Center [AMRDEC]), the ERS Environmental Simulation research team, the ERS Sensor Systems research team, and the HPC/Scientific computing group representing the “General HPC User.”