[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-258563-105":53,"doc-detail-258563-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","a-model-of-pilot-abstractions-pilot-api","A Model of Pilot-Abstractions - Pilot-API","","Pilot-Jobs support effective distributed resource utilization and are widely adopted across distributed computing applications and production cyberinfrastructures. Despite this adoption, no single, well-defined conceptual model exists to unify and compare different Pilot-Job implementations. The paper introduces a minimal complete P* model, maps major frameworks (e.g., Condor, DIANE) to P*, and derives an interoperable, extensible Pilot-API. It validates the API via concurrent use of multiple frameworks on distinct infrastructures and extends the model to Pilot-Data.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":51,"@type":70,"position":76},"https://docshare.wps.com/template/general/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/a-model-of-pilot-abstractions-pilot-api/258563/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/a-model-of-pilot-abstractions-pilot-api/258563.png","ImageObject",442,249,{"name":88,"@type":89},"Đào","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-09-21","2026-09-13",true,{"@type":98,"interactionType":99,"userInteractionCount":73},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"What problem does the paper address about Pilot-Jobs?","Question",{"text":108,"@type":109},"It addresses the lack of a well-defined, unifying conceptual model for Pilot-Jobs, which makes different implementations hard to define, compare, and contrast.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"What is the purpose of the P* Model (P-star)?",{"text":113,"@type":109},"The P* Model provides a minimal but complete conceptual basis to compare and contrast different Pilot-Job frameworks.",{"name":115,"@type":106,"acceptedAnswer":116},"How is interoperability achieved and validated?",{"text":117,"@type":109},"The paper derives the Pilot-API from the P* Model and validates it by concurrently using multiple distinct Pilot-Job frameworks on different production distributed cyberinfrastructures.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},258563,1789991286,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":50,"category_name":51,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":73,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":137,"faqs":138,"seo_title":139,"seo_description":61,"update_tm":140,"read_time":79},1374402968488,"https://ap-avatar.wpscdn.com/davatar_29158cc5080c5b710cf443261637dec0","P*: A Model of Pilot-Abstractions  \nAndre Luckow 1 , Mark Santcroos2 ; 1 , Ole Weidner1 , Andre Merzky 1 , Pradeep Mantha 1 , Shantenu Jha3 ; 1􀀃  \n1 Center for Computation & Technology, Louisiana State University, USA  \n2 Bioinformatics Laboratory, Academic Medical Center, University of Amsterdam, The Netherlands  \n3 Rutgers University, Piscataway, NJ 08854, USA  \n􀀃 Contact Author: shantenu . jha@rutgers .edu  \narXiv : 1207 .6644v1 [ cs .DC] 27 Jul 2012  \nAbstract—Pilot-Jobs support effective distributed resource utilization, and are arguably one of the most widely-used distributed computing abstractions – as measured by the number and types of applications that use them, as well as the number of production distributed cyberinfrastructures that support them. In spite of broad uptake, there does not exist a well-defined, unifying conceptual model of Pilot-Jobs which can be used to define, compare and contrast different implementations. Often Pilot-Job implementations are strongly coupled to the distributed cyberinfrastructure they were originally designed for. These factors present a barrier to extensibility and interoperability. This paper is an attempt to (i) provide a minimal but complete model (P*) of Pilot-Jobs,(ii) establish the generality of the P* Model by mapping various existing and well known Pilot-Job frameworks such as Condor and DIANE to P*, (iii) derive an interoperable and extensible API for the P* Model (Pilot-API),(iv) validate the implementation of the Pilot-API by concurrently using multiple distinct Pilot-Job frameworks on distinct production distributed cyberinfrastructures, and (v) apply the P* Model to Pilot-Data.  \nI. INTRODUCTION AND OVERVIEW  \nThe seamless uptake of distributed infrastructures by scientific applications has been limited by the lack of pervasive and simple-to-use abstractions at multiple levels – at the development, deployment and execution stages [1] . Even where meaningful abstractions exist, the challenges of implementing them in an extensible, reliable and scalable manner, so as to support multiple applications are formidable. The lack of appropriate implementations has in fact resulted in “one-off” solutions that address challenges in a highly customized manner. Tools and implementations are often highly dependent on and tuned to a specific execution environment, further impacting portability, reusability and extensibility. Semantic and interface incompatibility are certainly barriers, but so is the lack of a common architecture and conceptual framework upon which to develop similar tools a barrier. This general state of affairs also captures the specific state of the abstractions provided by Pilot-Jobs (PJ) . There are a plethora of working definitions and roles for Pilot-Jobs; from our perspective, a Pilot-Job provides the ability to utilize a placeholder job as a container fora dynamically determined set of compute tasks.  \nDistributed cyber/e-infrastructure is by definition comprised of a set of resources that is fluctuating – growing, shrinking, changing in load and capability (in contrast to a static resource utilization model of traditional parallel and cluster computing systems) . The ability to utilize a dynamic resource pool is thus an important attribute of any application that needs to utilize distributed cyberinfrastructure (DCI) efficiently. Asa consequence of providing a simple approach for decoupling  \nworkload management and resource assignment/scheduling, PJ provide an effective abstraction for dynamic execution and resource utilization in a distributed context. Not surprisingly, Pilot-Jobs have been one of the most successful abstractions in distributed computing. The fundamental reason for the success of the Pilot-Job abstraction is that Pilot-Jobs liberate applications/users from the challenging requirement of mapping specific tasks onto explicit heterogeneous and dynamic resource pools. Pilot-Jobs thus shield applications from having to loadbalance tasks across such re","cbCaioQn5VmiBpxv","https://ap.wps.com/l/cbCaioQn5VmiBpxv","pdf",526603,10,"English","# Introduction and Overview\n## Motivation for a unified Pilot-Abstractions model\n## Pilot-Job abstraction and distributed dynamic resources\n# Pilot-Jobs frameworks and interoperability\n## Existing PJ frameworks overview\n## Mapping frameworks to the P* Model\n# Pilot-API and validation approach\n## Deriving an interoperable extensible API\n## Experiments and performance measurements\n# Extending to Pilot-Data\n## Generalization from compute to data","[{\"question\":\"What problem does the paper address about Pilot-Jobs?\",\"answer\":\"It addresses the lack of a well-defined, unifying conceptual model for Pilot-Jobs, which makes different implementations hard to define, compare, and contrast.\"},{\"question\":\"What is the purpose of the P* Model (P-star)?\",\"answer\":\"The P* Model provides a minimal but complete conceptual basis to compare and contrast different Pilot-Job frameworks.\"},{\"question\":\"How is interoperability achieved and validated?\",\"answer\":\"The paper derives the Pilot-API from the P* Model and validates it by concurrently using multiple distinct Pilot-Job frameworks on different production distributed cyberinfrastructures.\"}]","A Model of Pilot-Abstractions - Pilot-API | PDF",1789323350]