Author: buildbot
Date: Fri Jan 31 13:52:53 2014
New Revision: 895943
Log:
Staging update by buildbot for airavata
Added:
websites/staging/airavata/trunk/content/images/airavata-stakeholders.png
(with props)
Modified:
websites/staging/airavata/trunk/content/ (props changed)
websites/staging/airavata/trunk/content/architecture/airavata-stakeholders.html
Propchange: websites/staging/airavata/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Fri Jan 31 13:52:53 2014
@@ -1 +1 @@
-1562093
+1563133
Modified:
websites/staging/airavata/trunk/content/architecture/airavata-stakeholders.html
==============================================================================
---
websites/staging/airavata/trunk/content/architecture/airavata-stakeholders.html
(original)
+++
websites/staging/airavata/trunk/content/architecture/airavata-stakeholders.html
Fri Jan 31 13:52:53 2014
@@ -133,17 +133,19 @@
<div class="span9">
<section id="content" class="row">
<article class="span9">
- <p><img alt="Airavata Stakeholders"
src="/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>
+ <p>Apache Airavata software framework enables building Science
Gateways empowering users to register and execute applications and compose,
manage, execute and
+monitor distributed composite applications and workflows on computational
resources. Airavata abstracts computational resources ranging from local
resources to computational grids and clouds. The following figure illustrate
these interactions and highlights different user roles.</p>
+<p><img alt="Airavata Stakeholders" src="/images/airavata-stakeholders.png"
title="Airavata Stakeholders" /></p>
<ul>
-<li>End Users</li>
-<li>Gateway Developers</li>
-<li>Core Developers</li>
+<li>Gateay End Users - These users interacts with the portal and desktop user
interfaces and are agnostic to the existance of Airavata.</li>
+<li>Gateway Developers - The primary target for Airavata Client SDK's is
gateway developers. They program against Airavata API (eased through client
sdk's in Java, or PHP or C++ or JS) and build science centric gateway
interfaces.</li>
+<li>Gateway Adminstrators - These users are responsible for operating a
developed gateway and are primary target for Airavata Adminstrative Tools which
faciliate system level monitoring, security and user management and so
forth.</li>
+<li>Airavata Framework Developers - These group of developers understand the
internals of Airavata and develop, enhance, mainatain the core software.</li>
</ul>
-<p>Now let's focus on each user and how they fit into Airavata's big
picture.</p>
+<hr />
+<h3 id="legacy-content-needs-revsisting">Legacy Content - Needs Revsisting</h3>
+<p><img alt="Airavata Stakeholders" src="/architecture/user1.png"
title="Airavata Stakeholders" /></p>
+<p>Below we describe each of these user roles in detail and how they fit into
Airavata's big picture.</p>
<h2 id="end-users">End Users</h2>
<p><img alt="End Users" src="/architecture/user2.png" title="End Users" /></p>
<p>End User is the one who will have a model code to do some scientific
application. Sometimes this End User can be a
Added: websites/staging/airavata/trunk/content/images/airavata-stakeholders.png
==============================================================================
Binary file - no diff available.
Propchange:
websites/staging/airavata/trunk/content/images/airavata-stakeholders.png
------------------------------------------------------------------------------
svn:mime-type = image/png
