<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Cloud Transition: Integrating Cloud Calls into Workflow Petri Nets</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Sofiane Bendoukha</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Thomas Wagner</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Extended Abstract</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>University of Hamburg, Department of Informatics</institution>
        </aff>
      </contrib-group>
      <kwd-group>
        <kwd>Cloud computing</kwd>
        <kwd>Workflow Management Systems</kwd>
        <kwd>Workflow Petri Nets</kwd>
        <kwd>Reference Nets</kwd>
        <kwd>Cloud Workflow Transition</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>-</title>
      <p>In this paper, we present the Cloud Workflow Transition. An extension of Petri
nets formalisms to adopt Cloud interactions. This allows workflows to request
compute or storage services from the cloud. Such refinements permit to codify
operational procedures into Petri net models and reduce user implication during
the specification of their workflows. The main purpose behind our proposed
refinements is to allow users to automatically execute workflows on distributed
infrastructures (Cloud, SOA, grid, cluster).</p>
      <p>Through the Cloud transition users can specify their requests formulated as
tasks and parameters (see Figure 1). These requests will be treated in a
transparent way i.e. that technical information is hidden from the user. The WFMS will
then either accept the request and make the connection to the specified Cloud
services according to user inputs or will reject it. The input places of the Cloud
transition model the pre-conditions of an event, the input data for the
computational task. The output places of the transition model the post-conditions
associated with an event, the results of the computational task.</p>
      <p>
        Our approach uses workflow Petri nets [
        <xref ref-type="bibr" rid="ref1">1</xref>
        ]. More specifically we use the
reference net formalism [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] extended with a specialized workflow task transition
[
        <xref ref-type="bibr" rid="ref3">3</xref>
        ]. Renew, the Reference Net Workshop, is our chosen tool for modeling with
reference nets. A very interesting and useful property of reference nets in Renew
is their use of the so-called shadow layer. It hides the technical details from the
user, who can concentrate on simply the nets.
      </p>
      <p>
        The technical integration of the Cloud transition into our workflow nets and
workflow managment system is carried out in three main steps: The integration
into the existing workflow net formalism for Renew [
        <xref ref-type="bibr" rid="ref3">3</xref>
        ], the integration into the
current WFMS in Renew [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ] and finally the integration into the user interface.
Due to the dynamic aspect of the cloud computing, further integration issues are
investigated such as including Quality-of-Service (QoS) requirements (time and
expenditure limit). The WFMS should be able to identify and handle failures
and support reliable execution in the presence of concurrency to guarantee a
high level of performance and availability of services.
      </p>
      <p>PNSE’12 – Petri Nets and Software Engineering</p>
      <p>We plan to define the oprational semantics of the Cloud transition using
Renew as well as a working use case. As an example, we intend to include the
Cloud transition to model and enact a storage workflow using existing Cloud
storage services within a Petri net-based multi-agent system.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Aalst</surname>
          </string-name>
          , W.:
          <article-title>Verification of workflow nets</article-title>
          . In Azéma, P.,
          <string-name>
            <surname>Balbo</surname>
          </string-name>
          , G., eds.
          <source>: Application and Theory of Petri Nets</source>
          <year>1997</year>
          . Volume
          <volume>1248</volume>
          of Lecture Notes in Computer Science., Springer-Verlag, Berlin (
          <year>1997</year>
          )
          <fpage>407</fpage>
          -
          <lpage>426</lpage>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Kummer</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          :
          <string-name>
            <surname>Referenznetze</surname>
          </string-name>
          . Logos Verlag, Berlin (
          <year>2002</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Jacob</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kummer</surname>
            ,
            <given-names>O.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Moldt</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ultes-Nitsche</surname>
            ,
            <given-names>U.</given-names>
          </string-name>
          :
          <article-title>Implementation of workflow systems using reference nets - security and operability aspects</article-title>
          . In Jensen, K., ed.
          <source>: Fourth Workshop and Tutorial on Practical Use of Coloured Petri Nets and the CPN Tools</source>
          , Ny Munkegade, Bldg. 540, DK-8000
          <string-name>
            <surname>Aarhus</surname>
            <given-names>C</given-names>
          </string-name>
          , Denmark, University of Aarhus, Department of Computer Science (
          <year>August 2002</year>
          )
          <article-title>DAIMI PB: Aarhus</article-title>
          , Denmark,
          <source>August</source>
          <volume>28</volume>
          -30, number 560.
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Wagner</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>A centralized Petri net- and agent-based workflow management system</article-title>
          . In Duvigneau,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Moldt</surname>
          </string-name>
          , D., eds.
          <source>: Proceedings of the Fifth International Workshop on Modeling of Objects, Components and Agents, MOCA'09</source>
          ,
          <string-name>
            <surname>Hamburg</surname>
          </string-name>
          .
          <source>Number FBI-HH-B-290/09 in Report of the Department of Informatics, Vogt-Kölln Str. 30</source>
          ,
          <string-name>
            <given-names>D</given-names>
            <surname>-</surname>
          </string-name>
          22527 Hamburg, University of Hamburg, Department of Informatics (
          <year>September 2009</year>
          )
          <fpage>29</fpage>
          -
          <lpage>44</lpage>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>