airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r823732 - in /websites/staging/airavata/trunk/content: ./ airavata/architecture/airavata-stakeholders.html
Date Fri, 29 Jun 2012 13:34:56 GMT
Author: buildbot
Date: Fri Jun 29 13:34:56 2012
New Revision: 823732

Staging update by buildbot for airavata

    websites/staging/airavata/trunk/content/   (props changed)

Propchange: websites/staging/airavata/trunk/content/
--- cms:source-revision (original)
+++ cms:source-revision Fri Jun 29 13:34:56 2012
@@ -1 +1 @@

Modified: websites/staging/airavata/trunk/content/airavata/architecture/airavata-stakeholders.html
--- websites/staging/airavata/trunk/content/airavata/architecture/airavata-stakeholders.html
+++ websites/staging/airavata/trunk/content/airavata/architecture/airavata-stakeholders.html
Fri Jun 29 13:34:56 2012
@@ -105,7 +105,7 @@
   <div id="content">
     <h1 class="title">Airavata Stakeholders</h1>
-    <p><img alt="Airavata Stakeholders" src="/airavata/architecture/user1.jpg" title="Airavata
Stakeholders" /></p>
+    <p><img alt="Airavata Stakeholders" src="/airavata/architecture/user1.png" title="Airavata
Stakeholders" /></p>
 <p>Airavata is a framework which enables a user to build Science Gateways. It is used
to compose, manage, execute and monitor distributed applications and workflows on computational
resources. These computational resources can range from local resources to computational grids
and clouds. Therefore,  various users with different backgrounds either contribute or use
Airavata in their  applications. From the Airavata standpoint, three
 main users can be identified.</p>
@@ -115,15 +115,15 @@ main users can be identified.</p>
 <p>Now let's focus on each user and how they fit into Airavata's big picture.</p>
 <h2 id="end-users">End Users</h2>
-<p><img alt="End Users" src="/airavata/architecture/user2.jpg" title="End Users"
+<p><img alt="End Users" src="/airavata/architecture/user2.png" title="End Users"
 <p>End User is the one who will have a model code to do some scientific application.
Sometimes this End User can be a Research Scientist. He/She writes scripts to wrap the applications
up and by executing those scripts, they run the scientific workflows in Super Computers. This
can be called a scientific experiment. Now the Scientist might have a requirement to call
multiple of these applications together and compose a workflow. That's where the Gateway Developer
comes into the picture.</p>
 <h2 id="gateway-developers">Gateway Developers</h2>
-<p><img alt="Gateway Developers" src="/airavata/architecture/user3.jpg" title="Gateway
Developers" /></p>
+<p><img alt="Gateway Developers" src="/airavata/architecture/user3.png" title="Gateway
Developers" /></p>
 <p>The Research Scientist is the one who comes up with requirement of bundling scienitific
applications together and composing as a workflow.</p>
 <p>The job of the Gateway Developer is to use Airavata and wrap the above mentioned
model code and scripts together. Then, scientific workflows are created out these.</p>
 <p>Above diagram depicts how Gateway Developer fits into the picture.</p>
 <h2 id="core-developers">Core Developers</h2>
-<p><img alt="Core Developers" src="/airavata/architecture/user4.jpg" title="Core
Developers" /></p>
+<p><img alt="Core Developers" src="/airavata/architecture/user4.png" title="Core
Developers" /></p>
 <p>Core Deveoper is the one who develops and contributes to Airavata framework codebase.
The Gateway Developers use the software developed by the Core Developers to create science

View raw message