Presentation Open Access

A common workflow registry of compute endpoints and applications

Katz, Daniel S; Badia, Rosa; Chard, Kyle; Ejarque, Jorge


MARC21 XML Export

<?xml version='1.0' encoding='UTF-8'?>
<record xmlns="http://www.loc.gov/MARC21/slim">
  <leader>00000nam##2200000uu#4500</leader>
  <controlfield tag="005">20200909125925.0</controlfield>
  <controlfield tag="001">4020518</controlfield>
  <datafield tag="711" ind1=" " ind2=" ">
    <subfield code="d">8-10 September 2020</subfield>
    <subfield code="a">11th Joint Laboratory for Extreme Scale Computing (JLESC) Workshop</subfield>
    <subfield code="c">virtual</subfield>
    <subfield code="n">STM3.2</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Barcelona Supercomputer Center</subfield>
    <subfield code="0">(orcid)0000-0003-2941-5499</subfield>
    <subfield code="a">Badia, Rosa</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">University of Chicago &amp; Argonne National Laboratory</subfield>
    <subfield code="0">(orcid)0000-0002-7370-4805</subfield>
    <subfield code="a">Chard, Kyle</subfield>
  </datafield>
  <datafield tag="700" ind1=" " ind2=" ">
    <subfield code="u">Barcelona Supercomputer Center</subfield>
    <subfield code="0">(orcid)0000-0003-4725-5097</subfield>
    <subfield code="a">Ejarque, Jorge</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="s">351035</subfield>
    <subfield code="z">md5:ad531317d4b8093ae27412f7025b7033</subfield>
    <subfield code="u">https://zenodo.org/record/4020518/files/JLESC11 - Common workflow registry of endpoints and applications.pdf</subfield>
  </datafield>
  <datafield tag="542" ind1=" " ind2=" ">
    <subfield code="l">open</subfield>
  </datafield>
  <datafield tag="856" ind1="4" ind2=" ">
    <subfield code="y">Conference website</subfield>
    <subfield code="u">http://icl.utk.edu/jlesc11/</subfield>
  </datafield>
  <datafield tag="260" ind1=" " ind2=" ">
    <subfield code="c">2020-09-09</subfield>
  </datafield>
  <datafield tag="909" ind1="C" ind2="O">
    <subfield code="p">openaire</subfield>
    <subfield code="o">oai:zenodo.org:4020518</subfield>
  </datafield>
  <datafield tag="100" ind1=" " ind2=" ">
    <subfield code="u">University of Illinois Urbana-Champaign</subfield>
    <subfield code="0">(orcid)0000-0001-5934-7525</subfield>
    <subfield code="a">Katz, Daniel S</subfield>
  </datafield>
  <datafield tag="245" ind1=" " ind2=" ">
    <subfield code="a">A common workflow registry of compute endpoints and applications</subfield>
  </datafield>
  <datafield tag="540" ind1=" " ind2=" ">
    <subfield code="u">https://creativecommons.org/licenses/by/4.0/legalcode</subfield>
    <subfield code="a">Creative Commons Attribution 4.0 International</subfield>
  </datafield>
  <datafield tag="650" ind1="1" ind2="7">
    <subfield code="a">cc-by</subfield>
    <subfield code="2">opendefinition.org</subfield>
  </datafield>
  <datafield tag="520" ind1=" " ind2=" ">
    <subfield code="a">&lt;p&gt;This is a presentation given at the 11th JLESC workshop (&lt;a href="https://jlesc.github.io/events/11th-jlesc-workshop/"&gt;https://jlesc.github.io/events/11th-jlesc-workshop/&lt;/a&gt;)&lt;br&gt;
&lt;br&gt;
There is now a large and ever growing number of workflow systems, and we have lost hope in encouraging users not to continue developing more. Instead, we want to focus on building shared elements that can help us with our own systems, as well as the users of those systems and the developers of applications that will increasingly be used as workflow elements in simulation, analysis, search, optimization, and parameter study research campaigns.&lt;/p&gt;

&lt;p&gt;As discussed briefly at JLESC 9 (in ST A1.1. Python-based Workflows &amp;amp; Software Sustainability), two of the common types of elements that workflow systems interact with are the end computing systems and the preexisting applications that the workflows wrap and call. Today, users of a workflow system have to find information about both the end points and the applications, they have to map that information to workflow-specific configuration formats, individually customize their workflow to use these configurations, and keep up with changes over time. Instead, we propose a registry of compute end points and applications, where an entry could be automatically brought in to a workflow system.&lt;/p&gt;</subfield>
  </datafield>
  <datafield tag="773" ind1=" " ind2=" ">
    <subfield code="n">doi</subfield>
    <subfield code="i">isVersionOf</subfield>
    <subfield code="a">10.5281/zenodo.4020517</subfield>
  </datafield>
  <datafield tag="024" ind1=" " ind2=" ">
    <subfield code="a">10.5281/zenodo.4020518</subfield>
    <subfield code="2">doi</subfield>
  </datafield>
  <datafield tag="980" ind1=" " ind2=" ">
    <subfield code="a">presentation</subfield>
  </datafield>
</record>
134
79
views
downloads
All versions This version
Views 134134
Downloads 7979
Data volume 27.7 MB27.7 MB
Unique views 121121
Unique downloads 7373

Share

Cite as