airavata-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject svn commit: r823643 - in /websites/staging/airavata/trunk/content: ./ airavata/architecture/airavata-stakeholders.html
Date Thu, 28 Jun 2012 19:44:54 GMT
Author: buildbot
Date: Thu Jun 28 19:44:53 2012
New Revision: 823643

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 Thu Jun 28 19:44:53 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
Thu Jun 28 19:44:53 2012
@@ -109,13 +109,13 @@
 <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>
-<li>Research Scientists (Gateway End Users)</li>
+<li>End Users</li>
 <li>Gateway Developers</li>
 <li>Core Developers</li>
 <p>Now let's focus on each user and how they fit into Airavata's big picture.</p>
-<h2 id="gateway-end-users">Gateway End Users</h2>
-<p><img alt="Gateway End Users" src="/airavata/architecture/user2.jpg" title="Gateway
End Users" /></p>
+<h2 id="end-users">End Users</h2>
+<p><img alt="End Users" src="/airavata/architecture/user2.jpg" title="End Users"
 <p>Gateway 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>

View raw message