Distributed Account Management Middleware Glenn Bresnahan (PI), Boston University Steve Quinn (Co. PI), NCSA Aaron Fuegi, Boston University Chris Pond, NCSA Michael Shapiro, NCSA Ester Soriano, NCSA
Objective Provide mechanisms to allow for the automated management of resource allocations, resource access control, user information, user login accounts, and usage reporting in a grid environment spanning multiple administrative domains
Background l Alliance partnership (PACI) – NCSA, Boston, Kentucky, New Mexico, Wisconsin, Maui l NSF PACI Allocation Peer Review (NRAC and AAB) l Manage accounts, allocations and reporting across Alliance resources
Requirements l Compatible with current practices (e. g. PACI) l Independent of local account management system l Heterogeneous environment l Multiple administration domains l Economic model neutral
Strategy l Provide grid services to exchange and manipulate shared accounting objects – – – Resource requests Resources allocations User information Project/group information Access permissions Usage reports
AMIE Data Representation l XML schema for Accounting Objects – Machines – Users – Accounts – Allocations – Usage
AMIE Architecture l Transaction-based exchange mechanism – Transaction comprised of sequence of packets (messages) and acknowledgements l Sites send Requests and Notifications – Site A requests site B to perform an action – Site B notifies site A of actions taken • Independently or as the result of a request l Set of objects and states – Well defined state change sequences l l Robust error detection and recovery Asynchronous or real-time communication – No transport reliability assumptions l “Glue” modules to interface to site-specific accounting system
Configuration: Star
Configuration: Peer to Peer
Current Implementations Alliance Partner Sites (Version 1) l Alliance Grid Testbed (Version 1) l Teragrid (Version 2 – NMI) l NEES Grid (Version 2 – NMI) l (implementation in progress)
Transaction Example 1 Account Creation
Transaction Example 2 Modify User Information
Transaction Example 3 Usage Reporting
Transaction States Four possible states 1. On-hold - Waiting for another event. No further action should be taken until state changes. 2. In-progress – processing is underway 3. Completed – processing completed 4. Error – processing failed. More information is available via the packet state
Transaction Packet States Incoming Packets l l l l Construct – Message being assembled Received – Complete and ready to be processed Validate – Waiting for XML validation Inbox – Waiting to be put into AMIE DB Done – All processing sucessfully completed Error – Awaiting error notification to be issued Failed – Completed with failure
Transaction Packet States Outgoing Packets l l l l Construct – Message being assembled Validate – Waiting for XML validation Outbox – Waiting to be transmitted Sent – Sucessfully sent to remote site Wait – Waiting for a reply Done – All processing sucessfully completed Error – Awaiting error notification to be issued Failed – Completed with failure
AMIE Reference Implementation
Current Status Items Complete l Core AMIE system l XML Schema l XML validation l Method call interface specification l Transport/processing engine l State tracking l Error handling l Testbed Implementation
Current Status Reference Implementation l Reference implementation of AMIE method call interface l Relational "intermediate DB" schema (Oracle, Postgres, Sybase support) to interface AMIE to local AM system
Current Status In Development l Reference implementation of Account Management system – fully functional AM DB Schema – method call implementation – glue between AM system and AMIE implementation – Should be "drop in" AM system with grid capability through AMIE
Current Status Packaging l Core implementation l Reference implementation of method call interface l Reference AM implementation l Documentation
Distributed Account Management Questions?
Скачать презентацию Distributed Account Management Middleware Glenn Bresnahan PI Boston
c6bb3699946287b0ec7ded107d12f7cb.ppt