From TeraGrid Wiki
Requirement Analysis Teams (RATs)
What is a RAT?
RATs are not persistent bodies and are typically small teams that do not have representatives from all RPs. A RAT is defined by a charter with a clearly defined statement of the issues to be addressed, a set of outcomes, and a schedule of milestones to be accomplished in a period of 6-8weeks. Generally a RAT will create a recommendation or set of recommendations.
Status: In proposal stage
Report Due Date: TBD
This RAT will recommend appropriate infrastructure and processes for empowering people to readily and easily share, search, and access information. The RAT will recommend appropriate synchronous and asynchronous tools for virtual meetings, on-line discussion forums, exchange of information, where to post multi-media files, and a process for indexing and searching for the files.
AD: Scott Lathrop
Status: No action to date.
Recommended Action: Re-consider charter goals and membership
Report Due Date: 02-01-07
Lead: Patricia Kovatch, Warren Smith
This Requirements Analysis Team (RAT) builds on the work from the previous Scheduling RAT by refining TeraGrid metascheduling requirements, documenting deployed Resource Provider (RP) technologies and policies, and investigating metascheduling technologies. It concludes by recommending the path that TeraGrid should take in the area of metascheduling including capabilities to deploy and technologies that might be used to provide these capabilities.
- RAT Charter
- Preliminary Report
- Final Report
- For the survey data, please contact Warren Smith or Patricia Kovatch
TeraGrid Campus Partnership
Report Due Date: 11-30-06
Lead: Gary Bertoline and Scott Lathrop
This RAT, is in response to a number of campuses in the US that have approached the leadership of TeraGrid expressing an interest in becoming affiliated with TeraGrid, will investigate and recommend the policy, technical, and support issues that must be addressed if TG is opened to other campuses outside of the GIG and RP sites.
AD: Scott Lathrop
Status: 5 sub-groups actively working on recommendations; one sub-group recently started, others are at various stages; sub-group reports are posted on wiki; overall RAT should be able to produce recommendations by January
Recommended Action: Extend timeline to complete until end of January
Instrumentation and Metrics RAT
Lead: Tony Rimovsky, Matt Heinzel
AD: Tony Rimovsky
Objective: The purpose of this rat is to describe the metrics and instrumentation necessary for the GIG to facilitate the operation of TeraGrid and to develop a set of functional requirements to guide the development of tools for collecting, and reporting on those metrics. The plans and following implementations are intended to augment and improve the operational monitoring and instrumentation and not replace similar activities that take place at individual RPs.
Status: The group has discussed several use cases and has developed requirements and milestones for Data Movement and Grids. We are in the process of developing those into functional plans. Discussions have started with respect to Gateway requirements. Remaining topic areas are: Usage Reporting, Networking, Real Time Monitoring, Listener, and Annual Report.
Lead: Gary Bertoline
Objective: The purpose of this RAT is to write a Governance Model that will be used as a guide in the management of TeraGrid.
Status: RAT committee has been formed with the first meeting on Wednesday, June 7, 2007 at the TeraGrid '07 Conference in Madison, WI. The RAT has set a goal to have the draft Governance Model completed by September 1, 2007.
Report Due Date: 9/20/2007
Leaders: Jay Boisseau and Sergiu Sanielevici
With the first Track 2 system, Ranger at TACC, about to be deployed in production and the second Track 2 system about to be awarded, TG must now organize itself to meet the challenges and opportunities of intergrating them into the TG such that the productivity of our users is maximized.
To initiate this process, a staff workshop on extreme scalability was held at TG’07 in Madison, WI, on June 7, 2007. The participants considered the challenges and possible solutions and concluded that addressing them will require the formation of a new TG Working Group. They suggested that this RAT be chartered to define the scope and optimal staffing and functioning of this Working Group and its role within the evolving TG organization.
July 9 Minutes
> 1. Introduction of participants (All)
Present: Kelly, Nick, Ray, John, Jay A, Vickie, Amit, Shawn, Sergiu.
> 2. RAT objectives and timeline (Sergiu)
. Whitepaper: Challenges of Maximizing Science Productivity with the TeraGrid Track 2 Systems. . Charter of the TeraGrid Extreme Scalability Working Group (Draft)
7/16/07 Internal organization and work assignments in place 8/17/07 First drafts of Whitepaper and WG Charter 9/6/07 Final drafts of Whitepaper and WG Charter presented at the ARCH 9/14/07 RAT work completed
> 3. Internal organization and work assignments (Discussion)
We decided to hold weekly meetings Mondays at 1 pm Central.
We decided to form teams to focus on the Challenges and how the new WG should go about addressing them on behalf of the TG. We will start from the Challenges suggested in Tables 1 and 2 of the Charter. Each RAT member should send email back to this list by Friday 7/13, specifying:
- which Challenge(s) (s)he wishes to work on; - suggested new Challenges that are not spelled out in Table 1 and 2, or that (in the member's opinion) would be better addressed if broken out explicitly (rather than included in the suggested Challenges). It will be assumed that a Member suggesting a new Challenge is thereby volunteering to work on fleshing it out for the Whitepaper.
> 4. Draft Agenda for 7/16 meeting (Discussion)
The final set of Chhallenges and the teams working on each will be reviewed, discussed and approved.
We will discuss how and when each Challenge team should report back to the plenary.
Challenge Team Work Areas
- 1 Improve Scal., Num. Stability & Robustness
- 2 Multi-core Performance
- 3 Architecture Performance
- 4 Deploy Scalable Debugger
- 5 Tools for Performance Optimization
- 6 Workflow: Data Transport, Analysis, Vis. & Storage
Report Preparation Zone
--- End of Active RATS section ---
Status: Completed 9/2010
Lead: Mike Northrop
Information and deliverables at Roaming Requirements.
Charter: The idea of roaming is quite simple – users get a TeraGrid roaming allocation and can use it to run on any system. There are a number of issues with this idea that have resulted in restricting the use of roaming within the TG. The TG currently uses the term roaming in a manner that appears to be confusing to users. We want to understand what users want to do, and what RPs are able to support, and then to merge these user and RP requirements into a new recommended policy that supports both users and RPs as much as possible. This new policy, if approved, would need to be clearly reflected in TG documentation.
Status: Completed 6/2009
Lead: Mike Northrop
Information and deliverables at TeraGrid User Portal Third Party Hosting RAT.
Charter: The TeraGrid is migrating the TeraGrid User Portal (TGUP) from a RP site to a commercial third-party provider. The goal of this RAT is to identify issues with the move of the TGUP, as a critical piece of TeraGrid Infrastructure with a role in the TeraGrid single sign-on architecture, from a RP to the third party and make suggestions on how those issues should be addressed.
Information and deliverables at Allocations RAT 2008.
UPDATE (12/26/07): The RAT report is complete and posted below. RPs can use this report a the basis for any Statements of Work they would like to submit for planning purposes to address the findings of the HPC University RAT/
- RAT Report - Final
- SC07 HPC University BoF Powerpoint Slides.
Report Due Date: 30-November 2007
Leads: Laura McGinnis (lfm at psc dot edu) and Brad Armosky (barmosky at tacc dot utexas dot edu)
The HPC Training RAT will identify successful paths to creating qualified, effective HPC professionals, capable of exploiting current super-terascale and upcoming petascale technologies for the advancement of scientific research. Gaps in training materials and delivery methods will be identified, and recommendations for filling these gaps will be presented.
Report: None. NCAR integration plan in progress through normal channels at this point
Lead: Tony Rimovsky, Wendy Huntoon
This RAT will initially focus on integrating NCAR into the Teragrid Network and then establishing NCAR as one of the Teragrid's Science Gateways.
Science Impact and Metrics
Lead: Mark Sheddon and Ann Zimmerman.
This RAT will investigate and recommend measures to assess the short- , mid-, and long-term effects of the TeraGrid's capabilities and resources on the outcomes of the work conducted by the scientific users of the TeraGrid.
Web Site Redesign
Lead: Diana Diehl and Steve Dunlop
This RAT will reassess the audiences, the functionality, and the overall design of the TeraGrid website. We also need to build into the site a method for gathering better quantitative and qualitative measurement of site utilization.
AD: Scott Lathrop
Status: RAT has completed. Have moved to implementation phase.
Recommended Action: Close the RAT
AURA - Accounting/Allocations
Report Due Date: 11-30-06 (need to update this with final report)
This RAT did a thorough analysis of the current allocation system, usage patterns, ideas for increasing usage on less scarce resources (freeing the scarce ones up), leveraging roaming capabilities and providing potential "discounts" to entice users to try out systems. This RAT also looked at non-compute resources beginning with data, visualization services, instruments, and consulting support.
Status: Complete (April 2005)
Lead: Laura McGinnis
The purpose of the TG Accounting RAT formalized a number open issues remaining in completing the accounting, allocations, and usage tracking functionality for the Teragrid circa early 2005. The RAT also began to define future accounting needs for accounting support throughout the life of the TeraGrid.
Status: Complete (April 2005)
Lead: Edward Walker
This RAT conducted a survey amongst fifteen large application groups: nine were considered traditional HPC users with large allocations on the TeraGrid, and six were non-traditional potentially large users of the TeraGrid. The survey highlights some important requirements pertaining to job scheduling across sites on TeraGrid resources.
Lead: Sergiu Sanielevici.
In May 2005, this RAT recommended a process by which advanced application support will be provided to TeraGrid users.
This RAT was in response to a survey of TG Science Partners that the two most pressing TeraGrid concerns cited by our TeraGrid Science Partners are the need for high performance file transfers, and the need to perform remote file read/write.
Lead: Linda Winkler
This RAT's purpose was to investigate and recommend a network configuration in advance of the expiration of the original networking contract.
Lead: Stuart Martin
This RAT investigated bridging the Open Science Grid and TeraGrid to interoperate as a seamless single grid for user applications.
This RAT's purpose was to gather and synthesize requirements for Science Gateways.
Lead: Michael Levine
This RAT investigated stronger authentication and more precise authorization schemes to reduce exposure to increased threats. Second, we are moving toward a more diverse set of access modes with new science gateway projects, and must develop authorization models that allow for these new access modes as well as examine certificate policies that are more scalable than the current bilateral agreement schemes. One new access mode involves the general user portal, where it is our intent to offer users a single point of entry for management of all TeraGrid logins and credentials.
Lead: JP Navarro
This RAT provided a set of requirements and recommendations to significantly improve key aspects of software evolution. First we discuss the overall software change management process with particular emphasis on improving the requirements gathering process, evaluating those requirements and creating a plan for the timely delivery of software changes, and the process for tracking and communicate what software and services are available on the TeraGrid. Next we present improvements in the Validation and Verification system (Inca) used to systematically measure the status of TeraGrid software and services. Finally we present recommendations designed to simplify the mechanisms of building, packaging, installing and maintaining TeraGrid software in order to ease the administrative load and lower the bar for deploying the TeraGrid software stack on new resources.
Lead: Eric Roberts
This RAT investigated the requirements for adding grid account management functionality to the TeraGrid User Portal as well as recommended solutions for addressing these requirements.
Lead: Ivan Judson
This RAT did a survey of gateways to determine requirements for web services.
Status: Completed 12-01-06
Lead: Natasha Balac.
This RAT will address a wide range of topics dealing with data collections on the TG, and will provide recommendations on how to address the topics. Issues specifically addressed include: what is a designated TG collection, location, allocations, service levels, tools supporting collections, clean up existing TG Collections table/web site, and suggestions for new potential providers and users of the TG collections.