1. Main Sphinx Design Concepts There are two primary design components which comprise Sphinx The Database Warehouse The Control Process The Database Warehouse is the information depot for all of Sphinx All information is stored/retrieved via the database (or possibly multiple databases) There is no direct communication between different internal Sphinx modules The API for all internal modules is SQL along (with the database schema) The Control Process is the main point of activity It is a loop which calls different Sphinx modules All modules in the control process operate on stateful entities in the database, changing the state of an entity from one to another state Sphinx operates as a Finite State Machine! Uses data mining principles in the design: The API for all modules is SQL along the database schema Modules mine the database for information and then take some action.

2. Version 1: Sphinx Server/Client Sphinx Server VDT Client VDT Server Site Monitoring Service Resource Condor-G/DAGMan Single-threaded Control Process Job Execution Planner DAG Reducer Prediction Engine Message Interface Job Table DAG Table Data Warehouse Information Gatherer Sphinx Client Message Interface Job Submitter Job Tracker Message Tbl. Site Tables Replica Table

3. More Details The next slides show the message passing between different Sphinx components The components are split (packaged) in the following way: Sphinx Client Incomming Messages Outgoing Messages Sphinx Server Incomming Messages Control Process Outgoing Messages See http://ufgrid.phys.ufl.edu:8080 for documentationhttp://ufgrid.phys.ufl.edu:8080 The next version of Sphinx (currently in progress) will split/package the components into a more logically distinct, modular scheme (yet to be decided)

4. Version 1: Sphinx Client (outgoing message) Message Type Path to file(DAX) Path to User ID file Clinet ClinetOutModule XMLDocUtils Files Msg strings Sender Info Message ID Msg Type Msg Sender Message ACK MsgID Msg Type Msg Sender Message XML message MsgHandlerDOMparser MsgID Msg Type Msg Sender Message XML message SendRequest XML message Destination URL XML RPC ACK

5. Version 1: Sphinx Client (incoming message) XML message ClientIncModule MsgHandler XML message Msg type Message string DOMparser XML message Msg ID Msg Type Msg Sender Message JobWrapper Message stringjob ID dag ID Msg string Work Dir SubmissionGenerator condor_submit_dag ACK createSubmissionexecute Super dag file

6. Version 1: Sphinx Server (incoming message) IncModule DOMparser XML message ACK (Msg ID) XML message Msg Id Msg Type Msg Sender Info Message InMessageWrapper DB Connector Msg Type Msg Sender Info Message MsgHandler XML message Msg Id Msg Type Msg Sender Info Message MessageWrapper message checkIn AbstractDagParser checkOutremove(msg) DagwrapperJobwrapper checkIn Dag Job checkIn Dag InfoJob Info Dag Obj Job Obj

7. Version 1: Control Process Dag Table Job Table DagReducer UNPREDICTED UNREDUCED PredictionEngine UNPREDICTED UNFINISHED UNPREDICTED UNPLANNED execute UNPLANNED SchedulingModule Job, Strategy Sites Info JobWrapper UNSENT Exec. site info Input file info Output file info Site Tables Physical site info Replica Table Physical file info OutMessageWrapper Planner Message Table Client ID Msg tpye Job info string Check In / SUB_REQ MessageWrapper Control Process

8. Version 1: Sphinx Server (outgoing message) OutgoingInterface Message MessageWrapper Next msg ID Check Out message Msg ID Client Info Msg type message ACK OutModule MsgHandlerDOMparser MsgID Msg Type Client Info Message XML message MsgID Msg Type Client Info Message XML message SendRequest XML message Destination URL SOAP RPC ACK

9. Version 2 of Sphinx (current) The current development cycle is represented in the next three slides Essentially: More planning tables have been added to the database warehouse More planning modules have been added to the control process A Data Management Component is being added to the Sphinx Server Replica Management (via RLS and GridFTP) The Monitoring Interface was upgraded to use MonALISA We also want to investigate the possibility of making a “Clarens service” out of any arbitrary planning module in the control process The Job Submitter, Job Tracking, and Condor-G/DAGMan (which currently form the Sphinx Client) is an example.

10. Version 2: Sphinx Server with Sphinx Submission Client Sphinx Server VDT Client VDT Server Site Monitoring Service Resource Repl. Loc. Serv. Condor-G/DAGMan Multi-threaded Control Process Job Execution Planner DAG Reducer DAG Tracker Job Predictor DAG Data Repl. Planner Job Admission Control Message Interface DAG Predictor DAG Admission Control Policies Accounting Resource Prop. Resource Hier. Resource Dist. Distance Entity-Name Entity Hier. Job-Entity Prop. Job DAG Rel. Data Rel. Appl. Job Tracking Grid Weather Data Warehouse Schedule Prediction Data Management Information Gatherer Sphinx Client Message Interface Job Submitter Job Tracker Message

11. Sphinx Server/VDT Client Version 2: Sphinx Server with Sphinx UI Client UI Machine VDT Server Site Monitoring Service Resource Multi-threaded Control Process Job Execution Planner DAG Reducer DAG Tracker Job Predictor DAG Data Repl. Planner Job Admission Control Job Submitter Message Interface DAG Predictor DAG Admission Control Job Tracker Data Management Information Gatherer Repl. Loc. Serv. Condor-G/DAGMan Policies Accounting Resource Prop. Resource Hier. Resource Dist. Distance Entity-Name Entity Hier. Job-Entity Prop. Job DAG Rel. Data Rel. Appl. Job Tracking Grid Weather Data Warehouse Schedule Prediction Sphinx Client Message Interface Message

12. Version 2: Finite State Machine Control Process DAG: unreduced JOB: unpredicted DAG: unpredicted JOB: unpredicted DAG: unaccepted JOB: unaccepted DAG: unpredicted JOB: unaccepted DAG: unaccepted JOB: unplanned DAG: unplanned JOB: unplanned yes no Await Mesg. Reduce DAG Predict Job no yes no Predict DAG Admit Job Admit DAG no yes DAG: unfinished JOB: unplanned DAG: unfinished JOB: unsent DAG: remove JOB: remove DAG: unfinished JOB: remove yes no Plan Dag Plan Job Submit Job no yes no Remove Job Remove DAG