List All Pages
Responsible for the lifecycle of agents. Provides the API that agents use to communicate with the infrastructure. Defines the lifecycle and linking model for applications. Activities...
Overview The goal of the STCI project is to provide an open source, scalable, portable, and extensible run-time and communication infrastructure for the deployment of developer tools on the...
The meeting will be held in Building 221 Room A216 on Thursday and Room A261 on Friday. We'll start at 9:30am. Google map of Argonne
Title Batch Instrumentation of Running Program High Level Description: This use case covers the cases where the user has instrumented an application program by modifying the source code and...
Bootstrapping is the process of establishing the infrastructure and components necessary for a tool to operate. The infrastructure is comprised of a number of different types of agents. Agents are...
Active messages There are two types of active messages, small and large. With small messages, the message is received into a temporary buffer then the handler function is called and a pointer to...
The component manager is in charge of the discovery, the loading, the unloading of components. Characteristics: The component manager must support static and dynamic components. The component...
For more information about this site, please contact jarrah.
The controller is a meta component in which other managers are located, such as the session manager. Persistent state will be maintained by the individual managers if necessary. It is the control...
Charter This working group is tasked with creating a technical specification for the data exchange component of the infrastructure, including defining the plugin (filter)...
The routing layer is responsible for sending messages from one end point to another end point. An end point could be an agent, a junction or the frontend. Decisions about where messages go are...
Title: Data Staging High Level Description User has files accessible from the front-end and wants to distribute them to the compute nodes, either to local storage, or directly to memory. There...
Used by router to interact with hardware to send/receive data Abstract layer on the top of the network device. (This should support any optimized specific hardware operations, e.g....
This subsystem is responsible for converting data type formats for communication between different architectures. Data types may be non-contiguous.
Title Distributed Agent (DA) - In Progress High Level Description The DA is started up to perform its work. It relies on the STCI infrastructure to start it up, which is often initiated by the...
Startup/configuration Start cold (e.g. infrastructure instantiation) Attach to running session/job Process/job/session location Security...
Language Core components will be C99 Other components can be C++ Build/Configure System Makefile Autotools Testing Tools MTT (http://open-mpi.org/projects/mtt) Hosting Indiana University...
A subsystem that allows events to be published and subscribed to. Event subscribers will be notified asynchronously. Delivery of some event types is enforced. Types of events will include cleanup,...
Provides an API for managing fault policy. Fault policy can be provided on a per-stream basis. Fault types Infrastructure bootstrap faults Startup faults Link failures (temporary or...
This subsystem is responsible for transferring one or more files to or from a group of compute/infrastructure nodes. For example this would be used to transfer files such as binaries, shared...
Agent A separate process that interacts with the external environment on behalf of the infrastructure. Control Stream A stream that is set up by the infrastructure for the purpose of managing...
STCI - first meeting Attendees Greg Watson, IBM Research Dorian Arnold, U. Wisconsin (MRNet) Feiyi Wang, ORNL Tim Mattox, Indiana Univ (Open MPI) Wyatt Spear, U.Oregon (TAU) Matt Drahzal, IBM John...
If you are allowed to edit pages in this Site, simply click on edit button at the bottom of the page. This will open an editor with a toolbar pallette with options. To create a link to a new page,...
2:00PM EST, Thursday, August 30th, 2007 Meeting Agenda: Determine voting process Decide on meeting protocols, agenda, and notification Establish a work approval process Establish a quality and...
2PM EST, September 13th Preliminary Agenda Review the joint meeting with the Data Exchange WG. Verify use case coverage. Confirm use case assignments Establish time/date for next meeting. The...
Charter Develop a specification for the infrastructure lifecycle. This will include defining what the infrastructure comprises (as pertaining to the lifecycle), and how the lifecycle will be...
Title Interactive Tools High Level Description This set of use cases involve those situations in which there are interactions between client code, running on either the system front-end service...
managing stdin/stdout/stderr from agents Create a special stream to handle I/O. Stdin can be delivered to a specific agent, or multicast to some agents. Allow customizations/annotations of the...
Who can join? This site is available to developers interested in contributing to the Scalable Tools Communication Infrastructure initiative. Join! So you want to become a member of this site? Tell...
The junction manager handles the life cycle of the "filters" (i.e., creation, configuration, termination and update) and also "connects" them to the router layer and/or other junctions (pipeline of...
A description of the licensing model that will be used by STCI.
Hawthorne, August 21-22, 2007 Oak Ridge, October 22-24, 2007 Reno, November 12, 2007 Argonne January 17-18, 2008
High level components Execution contexts Communication Session control Persistence Security Execution contexts Components associated with managing execution contexts. Execution context...
Working meeting Meeting Outcomes A list of common and use case-specific requirements, including any requirements that we have missed. A list of supported environments and platforms. Maybe a list...
This page lists the high-level technical objectives that will be addressed by STCI.
Plugin description A plug-in receives messages as part of a stream processes the messages (in an application-specific way), and sends one or more new messages on the same stream. A plug-in has one...
The process manager component manages process groups defined associated with STCI sessions. It is responsible for Creating new process groups, when new sessions are started Expanding existing...
Purpose The propose of the project is to: Develop infrastructure to support the development, debugging, deployment, monitoring, and analyzing of HPC applications from the desktop to the capability...
The task of defining the organizational structure has been delegated to the project structure working group. This page is a work-in-progress. Organization Key organizational...
Charter Develop a formal structure for the project organization. Requirements to be considered include: Get all important stakeholders involved License GPL/LGPL are problematic Formally defined...
The third STCI meeting was held in conjunction with SC07 in Reno, NV on Monday November 12, from 1-5 pm, in the Tradewinds II on the convention level of the Atlantis Hotel. Attendees: Rob...
The following high-level requirements have been identified: layered architecture lowest level mechanisms high level policy tiered architecture frontend middleware agents component...
Support topologies Pass messages Interconnect and routing Forming topology From entry point through plugins to agent and back Between plugins/agents Point-to-point (e.g. entry point to...
This subsystem is responsible for implementing the security model that controls access to a distributed set of resources that may have their own security model. It provides an entry point for...
Set of agents/plugins per user session Adhere to principal of least privilege Entry point Authentication (e.g. frontend in different authentication domain) Pluggable Ssl/ssh Plugins Run with...
Attendees Rich Graham, ORNL Darius Bruntinas, ANL Greg Watson, IBM Agenda & Minutes Determine meeting voting process It was determined that any decisions would need to be ratified by the full...
Definition of “session” Persists from session initialization to session termination Contains a set of streams which operate as defined by the infrastructure and lifecycle groups Contains the...
Agenda Meeting protocols Confirm agenda Administrative considerations Define 'session' Session lifecycle Inter-Session communication Tools (agents): one per session or...
Typical Use Cases 1. Create a New Session Remotely User launches Eclipse on their workstation. Eclipse launches a resource manager proxy by establishing an ssh connection to a remote machine and...
Charter Define what is meant by a ''session''. Define what ''session management'' means. Deliverables Use cases High level description, with examples State transition or block structure...
creation Provide a single point of entry into the system. It returns a unique session identifier. destruction Given the unique session id it release all resources attached to the specified id....
At Front-End STCI_FE_init() : Rich STCI_create session() : George STCI_allocate_resources(STCI_slurm, "queue=immediate nodes=12", 5*24*60*60) : Greg STCI_create_topology() :...
Welcome page Mailing list How to edit pages? How to join this site? Site members Recent changes List all pages Page Tags Site Manager Page tags Add a new page edit this panel
Members: Moderators Admins
creation The front-end create a stream based on the HANDLES of already existing junctions and agents, plus the topology. Return a unique stream HANDLE. May also need a version that is callable by...
Handle the creation, deletion and query of the stream topology (what is where, connected with who?). It creates the mapping between the logical connectivity and the physical location of the stream...
Components of the infrastructure need resources in order to function. Resources may consist of processes (or execution contexts), communication hardware, or other shared system functionality. The...
navigation project scope project structure licensing requirements architecture use cases meetings working groups environment glossary home contact
The following are the use cases that have been identified for the STCI. There are a set of assumptions that apply to all the use cases. Interactive Tool Use Cases Batch Instrumentation of Running...
What is the STCI lifecycle? STCI Deployment Lifecycle Install (deploy) Configure (setup) Standby Enable (start) Status available resources (nodes, …) active sessions Disable (stop) Uninstall...
Title Brief and descriptive, such as "Interctive Interogation of Running Job" High Level Description Short description of the use scenario, such as "User starts up Interactive Tool, attaches to...
Purpose The purpose of the Scalable Tools Communication Infrastructure initiative is to develop a common, scalable, portable, and extensible communication infrastructure for the deployment of...
According to Wikipedia, the world largest wiki site: A Wiki ([ˈwiː.kiː] <wee-kee> or [ˈwɪ.kiː] <wick-ey>) is a type of website that allows users to add, remove, or otherwise edit...
Session Management Working Group Data Exchange Infrastructure Working Group Infrastructure Lifecycle Working Group Project Structure Working Group
Unless otherwise stated, the content of this page is licensed under Creative Commons Attribution-ShareAlike 3.0 License