Author: buildbot Date: Fri Mar 4 02:31:35 2016 New Revision: 981774 Log: Staging update by buildbot for airavata
Modified: websites/staging/airavata/trunk/content/ (props changed) websites/staging/airavata/trunk/content/about/downloads-archive.html websites/staging/airavata/trunk/content/about/license.html websites/staging/airavata/trunk/content/architecture/airavata-stakeholders.html websites/staging/airavata/trunk/content/architecture/gfac.html websites/staging/airavata/trunk/content/architecture/overview.html websites/staging/airavata/trunk/content/architecture/registry.html websites/staging/airavata/trunk/content/architecture/workflow.html websites/staging/airavata/trunk/content/architecture/ws-messenger.html websites/staging/airavata/trunk/content/community/get-involved.html websites/staging/airavata/trunk/content/community/governance/consensusBuilding.html websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html websites/staging/airavata/trunk/content/community/governance/voting.html websites/staging/airavata/trunk/content/community/how-to-commit-contributed-code.html websites/staging/airavata/trunk/content/community/how-to-contribute-code.html websites/staging/airavata/trunk/content/community/mailing-lists.html websites/staging/airavata/trunk/content/community/projects-using.html websites/staging/airavata/trunk/content/community/submit-patch.html websites/staging/airavata/trunk/content/development/build.html websites/staging/airavata/trunk/content/development/edit-cms-website.html websites/staging/airavata/trunk/content/development/release-management.html websites/staging/airavata/trunk/content/development/roadmap.html websites/staging/airavata/trunk/content/development/source.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/airavata_api.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/airavata_commons.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/airavata_errors.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/application_deployment_model.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/application_io_models.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/compute_resource_model.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/data_movement_models.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/experiment_model.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/gateway_resource_profile_model.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/index.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/messaging_events.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/process_model.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/replica_catalog_models.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/status_models.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/task_model.html websites/staging/airavata/trunk/content/documentation/api-docs/0.16/workspace_model.html websites/staging/airavata/trunk/content/documentation/gfac/gfac.html websites/staging/airavata/trunk/content/documentation/messenger/ws-messenger.html websites/staging/airavata/trunk/content/documentation/quickstart-tutorials.html websites/staging/airavata/trunk/content/documentation/registry/xregistry.html websites/staging/airavata/trunk/content/documentation/tutorials/advanced-workflow-samples.html websites/staging/airavata/trunk/content/documentation/tutorials/airavata-in-10-minutes.html websites/staging/airavata/trunk/content/documentation/tutorials/airavata-in-5-minutes.html websites/staging/airavata/trunk/content/documentation/workflow/xbaya.html websites/staging/airavata/trunk/content/documentation/xbaya/xbaya_menues.html websites/staging/airavata/trunk/content/index.html websites/staging/airavata/trunk/content/tools/devtools.html Propchange: websites/staging/airavata/trunk/content/ ------------------------------------------------------------------------------ --- cms:source-revision (original) +++ cms:source-revision Fri Mar 4 02:31:35 2016 @@ -1 +1 @@ -1728169 +1733546 Modified: websites/staging/airavata/trunk/content/about/downloads-archive.html ============================================================================== --- websites/staging/airavata/trunk/content/about/downloads-archive.html (original) +++ websites/staging/airavata/trunk/content/about/downloads-archive.html Fri Mar 4 02:31:35 2016 @@ -133,9 +133,20 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>All downloads can be verified using the Apache Airavata code signing <a href="http://archive.apache.org/dist/airavata/KEYS">KEYS</a>.</p> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>All downloads can be verified using the Apache Airavata code signing <a href="http://archive.apache.org/dist/airavata/KEYS">KEYS</a>.</p> <p>Note: These releases are for historical purposes. We strongly recommend to download the latest release avaialble from <a href="downloads.html">current release</a>.</p> -<h4 id="013">0.13</h4> +<h4 id="013">0.13<a class="headerlink" href="#013" title="Permanent link">¶</a></h4> <p>IMPORTANT NOTE: Apache Airavata 0.13 release is primarily targetted for developer community. This release is a step towards the thrift based API release. 0.13 is churning quickly and users should wait for it. The tutorial, client packages and build instructions are not fully upto-date with 0.13 release. All these will be rectified as developers move focus onto packaging during and after 0.13. </p> <ul> @@ -166,7 +177,7 @@ Apache Airavata 0.13 release is primaril </ul> </li> </ul> -<h4 id="012">0.12</h4> +<h4 id="012">0.12<a class="headerlink" href="#012" title="Permanent link">¶</a></h4> <p>IMPORTANT NOTE: Apache Airavata 0.12 release is primarily targetted for developer community. This release is a step towards the thrift based API release.</p> <ul> @@ -197,7 +208,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="011">0.11</h4> +<h4 id="011">0.11<a class="headerlink" href="#011" title="Permanent link">¶</a></h4> <ul> <li><a href="http://svn.apache.org/repos/asf/airavata/tags/airavata-0.11/RELEASE_NOTES">Release Notes</a></li> <li> @@ -248,7 +259,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="010">0.10</h4> +<h4 id="010">0.10<a class="headerlink" href="#010" title="Permanent link">¶</a></h4> <ul> <li><a href="http://svn.apache.org/repos/asf/airavata/tags/0.10/RELEASE_NOTES">Release Notes</a></li> <li> @@ -290,7 +301,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="09">0.9</h4> +<h4 id="09">0.9<a class="headerlink" href="#09" title="Permanent link">¶</a></h4> <ul> <li><a href="http://svn.apache.org/repos/asf/airavata/tags/airavata-0.9/RELEASE_NOTES">Release Notes</a></li> <li> @@ -332,7 +343,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="08">0.8</h4> +<h4 id="08">0.8<a class="headerlink" href="#08" title="Permanent link">¶</a></h4> <ul> <li><a href="http://svn.apache.org/repos/asf/airavata/tags/airavata-0.8/RELEASE_NOTES">Release Notes</a></li> <li> @@ -374,7 +385,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="07">0.7</h4> +<h4 id="07">0.7<a class="headerlink" href="#07" title="Permanent link">¶</a></h4> <ul> <li><a href="http://svn.apache.org/repos/asf/airavata/tags/airavata-0.7/RELEASE_NOTES">Release Notes</a></li> <li> @@ -425,7 +436,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="06">0.6</h4> +<h4 id="06">0.6<a class="headerlink" href="#06" title="Permanent link">¶</a></h4> <ul> <li><a href="http://svn.apache.org/repos/asf/airavata/tags/airavata-0.6/RELEASE_NOTES">Release Notes</a></li> <li> @@ -476,7 +487,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="05">0.5</h4> +<h4 id="05">0.5<a class="headerlink" href="#05" title="Permanent link">¶</a></h4> <ul> <li> <p>Source: </p> @@ -492,7 +503,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="04-incubating">0.4-incubating</h4> +<h4 id="04-incubating">0.4-incubating<a class="headerlink" href="#04-incubating" title="Permanent link">¶</a></h4> <ul> <li> <p>Source: </p> @@ -508,7 +519,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h4 id="03-incubating">0.3-incubating</h4> +<h4 id="03-incubating">0.3-incubating<a class="headerlink" href="#03-incubating" title="Permanent link">¶</a></h4> <ul> <li> <p>Source: </p> @@ -524,7 +535,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h5 id="02-incubating">0.2-incubating</h5> +<h5 id="02-incubating">0.2-incubating<a class="headerlink" href="#02-incubating" title="Permanent link">¶</a></h5> <ul> <li> <p>Source: </p> @@ -540,7 +551,7 @@ Apache Airavata 0.12 release is primaril </ul> </li> </ul> -<h5 id="01-incubating">0.1-incubating</h5> +<h5 id="01-incubating">0.1-incubating<a class="headerlink" href="#01-incubating" title="Permanent link">¶</a></h5> <p><em>The 0.1-incubating release was cancelled by the community as LICENSE & NOTICE files were worked towards complaince.</em></p> </article> </section> Modified: websites/staging/airavata/trunk/content/about/license.html ============================================================================== --- websites/staging/airavata/trunk/content/about/license.html (original) +++ websites/staging/airavata/trunk/content/about/license.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Apache License<br></br>Version 2.0, January 2004<br></br> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>Apache License<br></br>Version 2.0, January 2004<br></br> <a href="http://www.apache.org/licenses/">http://www.apache.org/licenses/</a> </p> <p>TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION</p> <p><strong><a name="definitions">1. Definitions</a></strong>.</p> @@ -287,7 +298,7 @@ harmless for any liability incurred by, Contributor by reason of your accepting any such warranty or additional liability.</p> <p>END OF TERMS AND CONDITIONS</p> -<h1 id="apply">APPENDIX: How to apply the Apache License to your work</h1> +<h1 id="apply">APPENDIX: How to apply the Apache License to your work<a class="headerlink" href="#apply" title="Permanent link">¶</a></h1> <p>To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be 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 Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Apache Airavata software framework enables building Science Gateways empowering users to register and execute applications and compose, manage, execute and + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<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> @@ -143,24 +154,24 @@ monitor distributed composite applicatio <li>Airavata Framework Developers - These group of developers understand the internals of Airavata and develop, enhance, mainatain the core software.</li> </ul> <hr /> -<h3 id="legacy-content-needs-revsisting">Legacy Content - Needs Revsisting</h3> +<h3 id="legacy-content-needs-revsisting">Legacy Content - Needs Revsisting<a class="headerlink" href="#legacy-content-needs-revsisting" title="Permanent link">¶</a></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> +<h2 id="end-users">End Users<a class="headerlink" href="#end-users" title="Permanent link">¶</a></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 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> +<h2 id="gateway-developers">Gateway Developers<a class="headerlink" href="#gateway-developers" title="Permanent link">¶</a></h2> <p><img alt="Gateway Developers" src="/architecture/user3.png" title="Gateway Developers" /></p> <p>The Research Scientist is the one who comes up with requirement of bundling scientific 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> +<h2 id="core-developers">Core Developers<a class="headerlink" href="#core-developers" title="Permanent link">¶</a></h2> <p><img alt="Core Developers" src="/architecture/user4.png" title="Core Developers" /></p> <p>Core Developer is the one who develops and contributes to Airavata framework code-base. The Gateway Developers use the software developed by the Core Developers to create science gateways.</p> Modified: websites/staging/airavata/trunk/content/architecture/gfac.html ============================================================================== --- websites/staging/airavata/trunk/content/architecture/gfac.html (original) +++ websites/staging/airavata/trunk/content/architecture/gfac.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Airavata Generic Application Service Factory (GFac) facilitates users to create Web Services wrapping commandline + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>Airavata Generic Application Service Factory (GFac) facilitates users to create Web Services wrapping commandline applications. The generated application service WSDL interface provides input and outputs of the wrapped application. GFac provides a generic framework to wrap an application as a service interface in Java. This service layers separates the invocation from the communication layer supporting multiple protocol likes SOAP, REST, Modified: websites/staging/airavata/trunk/content/architecture/overview.html ============================================================================== --- websites/staging/airavata/trunk/content/architecture/overview.html (original) +++ websites/staging/airavata/trunk/content/architecture/overview.html Fri Mar 4 02:31:35 2016 @@ -133,14 +133,25 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Apache Airavata is a software toolkit with features to compose, manage, execute, and monitor small to large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds.</p> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>Apache Airavata is a software toolkit with features to compose, manage, execute, and monitor small to large scale applications and workflows on computational resources ranging from local clusters to national grids and computing clouds.</p> <p>Airavata builds on general concepts of service oriented computing, distributed messaging, and workflow composition and orchestration. The services primarily communicate using SOAP messages. In addition to the basic Web services specifications like SOAP and WSDL, the Web services also support WS-Addressing and WS-Messaging. WS-Addressing is used to provide an asynchronous communication mechanism for the services to communicate. All the communication channels are secured using https as the transport layer.</p> <p>Airavata features Dynamic Service Binding where in a proxy service accepts an input message intended to a target application Web service instance invoked by a workflow engine. The proxy service binds an appropriate Web service instance created by the Generic Facory Service. </p> <p>Airavata's primary goal is to support long running applications and workflows on distributed computational resources. The architecture is designed to be modular, componentized software framework as illustrated in the following Figure. The goal of the Airavata framework is minimalist architectural design (i.e., a thin layer), a conceptually simple to understand architecture; and easier to install, maintain and use. Its salient feature includes using components by themselves or as an integrated solution.</p> <p><img alt="Airavata Overview" src="/architecture/airavata-overview.png" title="Airavata Overview" /></p> -<h2 id="airavata-features">Airavata Features</h2> +<h2 id="airavata-features">Airavata Features<a class="headerlink" href="#airavata-features" title="Permanent link">¶</a></h2> <ul> <li>desktop tools and browser-based web interface components for managing applications, workflows and generated data. </li> <li>sophisticated server-side tools for registering and managing scientific applications on computational resources. </li> @@ -148,7 +159,7 @@ The goal of the Airavata framework is mi <li>interfacing and interoperability with with various external (third party) data, workflow and provenance management tools.</li> </ul> -<h2 id="airavata-components">Airavata Components</h2> +<h2 id="airavata-components">Airavata Components<a class="headerlink" href="#airavata-components" title="Permanent link">¶</a></h2> <ul> <li>XBaya Workflow Suite - includes a GUI for workflow composition and monitoring. The workflows can be interpreted at each step providing dynamic interactive capabilities. The composed workflow can be exported to various workflow Modified: websites/staging/airavata/trunk/content/architecture/registry.html ============================================================================== --- websites/staging/airavata/trunk/content/architecture/registry.html (original) +++ websites/staging/airavata/trunk/content/architecture/registry.html Fri Mar 4 02:31:35 2016 @@ -133,13 +133,24 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Airavata provides capabilities for an integrated workflow and data management system. The information and data has to + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>Airavata provides capabilities for an integrated workflow and data management system. The information and data has to be persisted into a registry service. To adhere to the philosophies of Airavata for layering over existing stable third party components, Airavata usage is consolidated into a thick-client API. This API allows the pluggability of the infrastructure and avoids locks in into any specific registry architectures. This following figure summarizes the use of the registry.</p> <p><img alt="Airavata Registry Usage" src="/architecture/airavata-registry.png" title="Airavata Registry Usage" /></p> -<h2 id="jcr-specification">JCR Specification:</h2> +<h2 id="jcr-specification">JCR Specification:<a class="headerlink" href="#jcr-specification" title="Permanent link">¶</a></h2> <p>The Content Repository for Java Technology specification, developed under the Java Community Process JSR-170, aims to standardize Java API to repositories. The specification provides a unified API under the javax.jcr namespace that allows you to access any specification-compliant repository implementation in a vendor-neutral manner. A major advantage of @@ -150,7 +161,7 @@ back ends and JCR implementations. Final a wide variety of existing content repositories, while simultaneously standardizing complex functionality such as versioning, access control, and searching. There are open source implementations of JSR-170 such as Apache Jackrabbit, Alfresco and WSO2 Registry.</p> -<h2 id="airavata-registry-api">Airavata Registry API</h2> +<h2 id="airavata-registry-api">Airavata Registry API<a class="headerlink" href="#airavata-registry-api" title="Permanent link">¶</a></h2> <p>When implementing registry functionality to store data and retrieve data we did not want to have locking for any custom API's to content repository implementations. Airavata tried to integrate with existing repositories without having to re-invent the wheel. JCR-2.0 specification and the JSR-170 implementation is plugged in to Apache Airavata system. The Modified: websites/staging/airavata/trunk/content/architecture/workflow.html ============================================================================== --- websites/staging/airavata/trunk/content/architecture/workflow.html (original) +++ websites/staging/airavata/trunk/content/architecture/workflow.html Fri Mar 4 02:31:35 2016 @@ -133,20 +133,31 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Airavata XBaya workflow system provides a programming model that allows the scientist to program experiments using + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>Airavata XBaya workflow system provides a programming model that allows the scientist to program experiments using service-oriented architecture that would abstract the complexities of the underlying middleware. Airavata XBaya provides interfaces for composition, execution and monitoring of the workflows as illustrated in the following Figure. Airavata XBaya consist of convenient GUI interface for workflow composition, workflow enactment engine/interface for workflow enactment and workflow monitoring module.</p> <p><img alt="Airavata Workflow Suite" src="/architecture/workflow-suite.png" title="Airavata Workflow Suite" /></p> -<h2 id="workflow-composition">Workflow Composition</h2> +<h2 id="workflow-composition">Workflow Composition<a class="headerlink" href="#workflow-composition" title="Permanent link">¶</a></h2> <p>Airavata XBaya by design decouples composition and monitoring from the orchestration of the workflow although it does provide an embedded workflow enactment engine integrated with the workbench. As a scientific workflow suite XBaya is often expected to run long running computations thus it often delegates the workflow execution to a persistent orchestration engine and XBaya workbench can monitor the progress of the workflow asynchronously. The workbench provides a convenient drag and drop GUI for SOA based service composition along with other functionalities like service discovery, registry lookup and workflow experiment management.</p> -<h2 id="workflow-orchestration">Workflow orchestration</h2> +<h2 id="workflow-orchestration">Workflow orchestration<a class="headerlink" href="#workflow-orchestration" title="Permanent link">¶</a></h2> <p>XBaya provides a unique pluggable architecture for selecting the orchestration engine. When a user composes a workflow using XBaya workbench it builds an abstract Directed Acyclic Graph (DAG) which is independent of any workflow runtime. There are pluggable compiler modules that are capable of producing workflow execution scripts for target runtimes. The @@ -157,7 +168,7 @@ orchestration engine well suited for lon sweeps whereas XBaya Interpreter engine is strong in dynamic and user interactive workflow execution. It is also capable of generating a Jython script that can be executed in any Jython runtime independent of any of the workflow infrastructure.</p> -<h2 id="workflow-interpreter">Workflow interpreter</h2> +<h2 id="workflow-interpreter">Workflow interpreter<a class="headerlink" href="#workflow-interpreter" title="Permanent link">¶</a></h2> <p>XBaya provides a inbuilt workflow enactment engine that provides extremely dynamic and interactive workflow execution. As the name suggests the workflow interpreter provides an interpreted workflow execution framework rather than the compiled workflow execution environments. In this context the interpreted workflow means at that execution framework @@ -180,7 +191,7 @@ functionalities. <em> Reconfiguration of workflow activity </em> Dynamic addition of activities to the DAG. * Dynamic remove or replace of activity to the DAG.</p> -<h2 id="workflow-monitoring">Workflow monitoring:</h2> +<h2 id="workflow-monitoring">Workflow monitoring:<a class="headerlink" href="#workflow-monitoring" title="Permanent link">¶</a></h2> <p>XBaya workbench allows the user to monitor the progress of the workflow in real-time. Monitoring includes the services which are currently executing, those that are done. It also provides state of the job submissions to the batch job queues and status of the data transfer. Workflow monitoring in XBaya workbench work in two modes; synchronous mode and Modified: websites/staging/airavata/trunk/content/architecture/ws-messenger.html ============================================================================== --- websites/staging/airavata/trunk/content/architecture/ws-messenger.html (original) +++ websites/staging/airavata/trunk/content/architecture/ws-messenger.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Airavata WS-Messenger is a Web Services-based Messaging System for Service-Oriented Computing and is + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>Airavata WS-Messenger is a Web Services-based Messaging System for Service-Oriented Computing and is an implementation of <a href="http://www.oasis-open.org/committees/wsn/">WS-Notification</a> and <a href="http://www.w3.org/Submission/WS-Eventing/">WS-Eventing</a> specifications. The message format can be automatically converted between the two specifications. The subscription request type (Ws-Notification or WS-Eventing) for a listener determines the message format that the notification @@ -153,7 +164,7 @@ The embedded Derby database is deployed subscriptions and notifications which will tolerate failures and restarts of the application server. </p> <p>The following figure illustrates the high level overview of the WS-Messenger <img alt="WS Messenger Overview" src="/architecture/messenger-overview.png" title="WS Messenger Overview" /></p> -<h2 id="ws-messenger-modules">WS-Messenger Modules</h2> +<h2 id="ws-messenger-modules">WS-Messenger Modules<a class="headerlink" href="#ws-messenger-modules" title="Permanent link">¶</a></h2> <ol> <li>Message Broker: The broker handles filtering/delivering messages to even sinks and subscription management. WS-Messenger support filtering messages based on XPath expression and topic expression. Message broker is implemented on @@ -178,7 +189,7 @@ the subscriber can send another web serv send notifications directly to even sink running behind the firewall. This deployment is a very common firewall configuration between DMZ and green zone in an enterprise deployment.provide a web service interface for subscribers behind the firewalls.</li> </ol> -<h2 id="airavata-usage-of-the-ws-messenger">Airavata Usage of the WS-Messenger</h2> +<h2 id="airavata-usage-of-the-ws-messenger">Airavata Usage of the WS-Messenger<a class="headerlink" href="#airavata-usage-of-the-ws-messenger" title="Permanent link">¶</a></h2> <p>Within Airavata, the WS-Messenger is used for user and system communications between GFac, XBaya and Workflow Intepreter. XBaya in monitoring mode subscribes to a pre-specified topic to which Workflow Engine and GFac are publishing status notifications. XBaya is instrumented to react to the messages to illustrate workflow progress by means of color coding of tasks being executed.</p> Modified: websites/staging/airavata/trunk/content/community/get-involved.html ============================================================================== --- websites/staging/airavata/trunk/content/community/get-involved.html (original) +++ websites/staging/airavata/trunk/content/community/get-involved.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>You don't need to be a software developer to contribute to + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>You don't need to be a software developer to contribute to Apache Airavata. To be successful this project requires a huge range of different skills, levels of involvement and degrees of technical expertise. So, if you want to get involved in Apache Airavata, there @@ -156,10 +167,10 @@ is almost certainly a role for you. </p> the community. The project team and the broader community will therefore welcome and encourage participation, and attempt to make it as easy as possible for people to get involved. </p> -<h2 id="mailing-lists">Mailing lists</h2> +<h2 id="mailing-lists">Mailing lists<a class="headerlink" href="#mailing-lists" title="Permanent link">¶</a></h2> <p>Your first engagement with the project should be to subscribe to our <a href="/community/mailing-lists.html">mailing lists</a>.</p> -<h2 id="decision-making">Decision Making</h2> +<h2 id="decision-making">Decision Making<a class="headerlink" href="#decision-making" title="Permanent link">¶</a></h2> <p>The most important thing about engaging with any Apache project is that everyone is equal. All people with an opinion are entitled to express that opinion and, where appropriate, have it considered by the community.</p> @@ -169,18 +180,18 @@ set of simple processes to ensure things <p>In ASF projects we don't like to vote. We reserve that for the few things that need official approval for legal or process reasons (e.g. a release or a new committer). Most of the time we work with the consensus building techniques documented below.</p> -<h3 id="lazy-consensus">Lazy Consensus</h3> +<h3 id="lazy-consensus">Lazy Consensus<a class="headerlink" href="#lazy-consensus" title="Permanent link">¶</a></h3> <p><a href="/community/governance/lazyConsensus.html">Lazy consensus</a> is the first, and possibly the most important, consensus building tool we have. Essentially lazy consensus means that you don't need to get explicit approval to proceed, but you need to be prepared to listen if someone objects.</p> -<h3 id="consensus-building">Consensus Building</h3> +<h3 id="consensus-building">Consensus Building<a class="headerlink" href="#consensus-building" title="Permanent link">¶</a></h3> <p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to make a proposal to the mailing list and discuss options. There are mechanisms for quickly showing your support or otherwise for a proposal and <a href="/community/governance/consensusBuilding.html">building consensus</a> amongst the community.</p> <p>Once there is a consensus people can proceed with the work under the <a href="/community/governance/lazyConsensus.html">lazy consensus</a> model.</p> -<h3 id="voting">Voting</h3> +<h3 id="voting">Voting<a class="headerlink" href="#voting" title="Permanent link">¶</a></h3> <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to have a measurable consensus. For example, when <a href="/community/governance/voting.html">voting</a> in new committers or to approve a release. </p> Modified: websites/staging/airavata/trunk/content/community/governance/consensusBuilding.html ============================================================================== --- websites/staging/airavata/trunk/content/community/governance/consensusBuilding.html (original) +++ websites/staging/airavata/trunk/content/community/governance/consensusBuilding.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>In some cases there is no obvious path to take, or you might be a new community, + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>In some cases there is no obvious path to take, or you might be a new community, or a new member of an existing community. In these cases people will often need to build consensus by making proposals and eliciting responses.</p> <p>We want to avoid unnecessary discussion and the creation of significant @@ -141,7 +152,7 @@ amounts of unnecessary mail that everyon That is not to say that we want to avoid constructive discussion. This is the lifeblood of a successful project. However, many ASF projects adopt a shorthand notation for showing support, or otherwise, for a proposal.</p> -<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)</h2> +<h2 id="expressing-support-or-otherwise">Expressing support (or otherwise)<a class="headerlink" href="#expressing-support-or-otherwise" title="Permanent link">¶</a></h2> <p>The notation used is "+1", "-1" and "0". It's also common to see "+0" and "-0".</p> <p>So, what do these notations mean?</p> <ul> @@ -158,7 +169,7 @@ to help implement"</li> like "+1000".</p> <p>The important thing is that this is not an exact science. It's just a shorthand way of communicating strength of feeling.</p> -<h2 id="consensus-building-is-not-voting">Consensus Building is Not Voting</h2> +<h2 id="consensus-building-is-not-voting">Consensus Building is Not Voting<a class="headerlink" href="#consensus-building-is-not-voting" title="Permanent link">¶</a></h2> <p>The confusing thing about this notation is that it is the same notation used in a formal vote. Knowing when something is a vote and when it is a preference is important. It's easy to tell though, if the subject does not have Modified: websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html ============================================================================== --- websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html (original) +++ websites/staging/airavata/trunk/content/community/governance/lazyConsensus.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>The concept of "Lazy Consensus" is very important in any apache project. Lazy + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>The concept of "Lazy Consensus" is very important in any apache project. Lazy Consensus means that when you are convinced that you know what the community would like to see happen you can simply assume that you already have consensus and get on with the work. You don't have to insist people discuss and/or @@ -144,7 +155,7 @@ You just assume you have the community's to indicate disapproval. If you believe the community will support your action you can operate on lazy consensus as long as you are prepared to roll back any work should a valid objection is raised.</p> -<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion</h2> +<h2 id="avoiding-unnecessary-discussion">Avoiding Unnecessary Discussion<a class="headerlink" href="#avoiding-unnecessary-discussion" title="Permanent link">¶</a></h2> <p>The key thing about lazy consensus is that it's easier for people to agree, by doing nothing, than it is to object, which requires an alternative to be proposed. This has two effects, firstly people are less @@ -156,7 +167,7 @@ of the project to watch what is happenin far down the road will cause upset, but objecting (or asking for clarification of intent) early is likely to be greeted with relief that someone is watching and cares.</p> -<h2 id="stating-lazy-consensus">Stating Lazy Consensus</h2> +<h2 id="stating-lazy-consensus">Stating Lazy Consensus<a class="headerlink" href="#stating-lazy-consensus" title="Permanent link">¶</a></h2> <p>Sometimes a member of the community will believe a specific action is the correct one for the community but are not sure enough to proceed with the work under the lazy consensus model. In these circumstances they can state Lazy Consensus is in @@ -169,7 +180,7 @@ around their proposal, nor are they requ supports their actions. However, this differs from assuming lazy consensus since it allows space and time to <a href="/community/governance/consensusBuilding.html">express support or objections</a> and corrections to the proposal before work begins. </p> -<h2 id="silence-is-consent">Silence is consent</h2> +<h2 id="silence-is-consent">Silence is consent<a class="headerlink" href="#silence-is-consent" title="Permanent link">¶</a></h2> <p>People may choose to indicate their support for the actions taken with a +1 mail - quick and easy to read and reassuring for the implementer. However, remember, in a lazy consensus world silence is the equivalent to support. This Modified: websites/staging/airavata/trunk/content/community/governance/voting.html ============================================================================== --- websites/staging/airavata/trunk/content/community/governance/voting.html (original) +++ websites/staging/airavata/trunk/content/community/governance/voting.html Fri Mar 4 02:31:35 2016 @@ -133,22 +133,33 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to have a + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>Occasionally a "feel" for consensus is not enough. Sometimes we need to have a measurable consensus. For example, when voting in new committers or to approve a release. </p> -<h2 id="preparing-for-a-vote">Preparing for a Vote</h2> +<h2 id="preparing-for-a-vote">Preparing for a Vote<a class="headerlink" href="#preparing-for-a-vote" title="Permanent link">¶</a></h2> <p>Before calling a vote it is important to ensure that the community is given time to discuss the upcoming vote. This will be done by posting an email to the list indicating the intention to call a vote and the options available. By the time a vote is called there should already be <a href="/community/governance/consensusBuilding.html">consensus in the community</a>. The vote itself is, normally, a formality.</p> -<h2 id="calling-a-vote">Calling a Vote</h2> +<h2 id="calling-a-vote">Calling a Vote<a class="headerlink" href="#calling-a-vote" title="Permanent link">¶</a></h2> <p>Once it is time to call the vote a mail is posted with a subject starting with "[VOTE]". This enables the community members to ensure they do not miss an important vote thread. It also indicates that this is not consensus building but a formal vote. The initiator is responsible for the vote. That means also to count the votes and present the results. Everyone has 1 vote.</p> -<h3 id="casting-your-vote">Casting Your Vote</h3> +<h3 id="casting-your-vote">Casting Your Vote<a class="headerlink" href="#casting-your-vote" title="Permanent link">¶</a></h3> <p>The notation used in voting is:</p> <p>+1 (means I vote positive) You can say why you vote positive but it's not a must-have.</p> @@ -156,7 +167,7 @@ and present the results. Everyone has 1 <p>-1 (means I vote negative because of the following reason) Yes, you must support your objection and provide an alternative course of action that you are willing and able to implement (where appropriate).</p> -<h4 id="example-for-a-vote-mail">Example for a vote mail:</h4> +<h4 id="example-for-a-vote-mail">Example for a vote mail:<a class="headerlink" href="#example-for-a-vote-mail" title="Permanent link">¶</a></h4> <div class="codehilite"><pre><span class="n">Address</span><span class="o">:</span> <span class="kd">private</span><span class="err">@</span> <span class="n">Subject</span><span class="o">:</span> <span class="o">[</span><span class="n">VOTE</span><span class="o">]</span> <span class="n">John</span> <span class="n">Doe</span> <span class="n">should</span> <span class="n">become</span> <span class="n">a</span> <span class="n">regular</span> <span class="n">committer</span> @@ -173,7 +184,7 @@ and present the results. Everyone has 1 </pre></div> -<h4 id="example-for-a-reply-mail">Example for a reply mail:</h4> +<h4 id="example-for-a-reply-mail">Example for a reply mail:<a class="headerlink" href="#example-for-a-reply-mail" title="Permanent link">¶</a></h4> <div class="codehilite"><pre><span class="n">Text</span><span class="p">:</span> <span class="o">+</span>1 @@ -181,7 +192,7 @@ and present the results. Everyone has 1 </pre></div> -<h4 id="example-for-a-result-mail">Example for a result mail:</h4> +<h4 id="example-for-a-result-mail">Example for a result mail:<a class="headerlink" href="#example-for-a-result-mail" title="Permanent link">¶</a></h4> <div class="codehilite"><pre><span class="n">Subject</span><span class="p">:</span> <span class="p">[</span><span class="n">VOTE</span><span class="p">][</span><span class="n">RESULTS</span><span class="p">]</span> <span class="n">John</span> <span class="n">Doe</span> <span class="n">should</span> <span class="n">become</span> <span class="n">a</span> <span class="n">regular</span> <span class="n">committer</span> <span class="n">Text</span><span class="p">:</span> Modified: websites/staging/airavata/trunk/content/community/how-to-commit-contributed-code.html ============================================================================== --- websites/staging/airavata/trunk/content/community/how-to-commit-contributed-code.html (original) +++ websites/staging/airavata/trunk/content/community/how-to-commit-contributed-code.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <h3 id="accepting-contributed-code">Accepting Contributed Code</h3> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<h3 id="accepting-contributed-code">Accepting Contributed Code<a class="headerlink" href="#accepting-contributed-code" title="Permanent link">¶</a></h3> <p>Apache Airavata follows the core philosophy of the Apache Software Foundation, informally quoted as "Apache Way". To ensure the contributions have both legally complaint as well as merotically rewarded, following guidlines should be used.</p> <ul> <li>Prefered contribution is by submitting patches through Airavata JIRA. The contributors while uploading the PATCH accept the donation of the copy right to ASF. </li> @@ -142,7 +153,7 @@ <li>Its better to preverse linear commit history and avoiding merged commits. </li> </ul> <p>Note: This page describes steps for accepting previously contributed code and is relavent for Airavata committers. Contributors should refer to [Airavata Contributor Guide][airavata-contribute]</p> -<h4 id="contributed-by-a-patch-file">Contributed by a PATCH file</h4> +<h4 id="contributed-by-a-patch-file">Contributed by a PATCH file<a class="headerlink" href="#contributed-by-a-patch-file" title="Permanent link">¶</a></h4> <p>If the contributor has submitted a patch file on mailing list or JIRA (prefered), follow these steps to commit it.</p> <ol> <li>First update your local checkout with any remote changes (git pull). @@ -152,7 +163,7 @@ <li>Its a good practice to run the full build with test enabled to ensure the patch did not break the code. </li> <li>Finally push the patch to remote master/branch using git push.</li> </ol> -<h4 id="contributed-by-a-github-pull-request">Contributed by a GitHUB Pull request</h4> +<h4 id="contributed-by-a-github-pull-request">Contributed by a GitHUB Pull request<a class="headerlink" href="#contributed-by-a-github-pull-request" title="Permanent link">¶</a></h4> <p>Its preferable to clone a new copy into a temporary location (or maintain one for contributions). This ensures the contributors changes do not get tangled with your local development. The following steps list out a fresh checkout, adapt them to use your previous checkout. </p> <ol> <li>Clone the Airavata repo:<code>git clone https://git-wip-us.apache.org/repos/asf/airavata.git</code>. <code>cd airavata</code> (if the PR is for a branch, do a appropriate checkout)</li> Modified: websites/staging/airavata/trunk/content/community/how-to-contribute-code.html ============================================================================== --- websites/staging/airavata/trunk/content/community/how-to-contribute-code.html (original) +++ websites/staging/airavata/trunk/content/community/how-to-contribute-code.html Fri Mar 4 02:31:35 2016 @@ -133,13 +133,24 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <h3 id="apache-airavata-contribution-guide">Apache Airavata Contribution Guide</h3> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<h3 id="apache-airavata-contribution-guide">Apache Airavata Contribution Guide<a class="headerlink" href="#apache-airavata-contribution-guide" title="Permanent link">¶</a></h3> <p>Welcome and thank you for your interest in contributing to Apache Airavata! This guide will take you through the process of making contributions to the airavata code base.</p> -<h4 id="engage-with-the-community">Engage with the community</h4> +<h4 id="engage-with-the-community">Engage with the community<a class="headerlink" href="#engage-with-the-community" title="Permanent link">¶</a></h4> <p>Identify an issue or documentation that you want to fix or improve. Search <a href="https://issues.apache.org/jira/browse/airavata">JIRA</a> and the mailing list to see if itâs already been discussed. </p> -<h4 id="create-an-issue-in-jira">Create an issue in JIRA</h4> +<h4 id="create-an-issue-in-jira">Create an issue in JIRA<a class="headerlink" href="#create-an-issue-in-jira" title="Permanent link">¶</a></h4> <p>If itâs a bug or a feature request, open a JIRA issue. Create a sample that you can use for prototyping the feature or demonstrating the bug. If creating a sample is time consuming, write steps to reproduce the issue. Attach this sample to the JIRA issue if itâs representing a bug report. </p> -<h4 id="create-a-pull-request-in-github">Create a pull request in GitHub</h4> +<h4 id="create-a-pull-request-in-github">Create a pull request in GitHub<a class="headerlink" href="#create-a-pull-request-in-github" title="Permanent link">¶</a></h4> <p><a href="/development/source.html">Checkout</a> the source code. Create a pull request (PR) in GitHub for the change you're interested in making. The comment section of the PR must contain a link to the JIRA issue. Please also reference the issue in the commit message, and make sure it properly describes the changes that have been made and their purpose.</p> <p>Some good references for working with GitHub are below. We ask that you keep your change rebased to master as much as possible, and we will ask you to rebase again if master has moved before accepting your patch. </p> <ul> @@ -148,13 +159,13 @@ <li><a href="https://help.github.com/articles/using-pull-requests">Submitting Pull Requests</a></li> <li><a href="https://help.github.com/articles/about-git-rebase">Rebasing your Branch</a> </li> </ul> -<h4 id="comment-the-issue-in-jira">Comment the issue in JIRA</h4> +<h4 id="comment-the-issue-in-jira">Comment the issue in JIRA<a class="headerlink" href="#comment-the-issue-in-jira" title="Permanent link">¶</a></h4> <p>Finally, add a comment in the JIRA issue with a link to the pull request so we know the code is ready to be reviewed. </p> -<h4 id="the-review-process">The review process</h4> +<h4 id="the-review-process">The review process<a class="headerlink" href="#the-review-process" title="Permanent link">¶</a></h4> <p>The airavata community will need to review your pull request before it is merged. If we are slow to respond, feel free to also email the dev mailing list: d...@airavata.apache.org. </p> <p>During the review process you may be asked to make some changes to your submission. While working through feedback, it can be beneficial to create new commits so the incremental change is obvious. This can also lead to a complex set of commits, and having an atomic change per commit is preferred in the end. Use your best judgement and work with your reviewer as to when you should revise a commit or create a new one.</p> <p>A pull request is considered ready to be merged once it gets at lease one +1 from a reviewer. Once all the changes have been completed and the pull request is accepted, it must be rebased to the latest upstream version. It is also a good idea to squash all the commits into a single one, since this will allow us to generate a clean patch and merge it properly.</p> -<h4 id="accepting-contributions">Accepting Contributions</h4> +<h4 id="accepting-contributions">Accepting Contributions<a class="headerlink" href="#accepting-contributions" title="Permanent link">¶</a></h4> <p>Developers with Airavata Commit access should read <a href="how-to-commit-contributed-code.html">Accepting Contribtions</a> on steps to accept the contributed code</p> </article> </section> Modified: websites/staging/airavata/trunk/content/community/mailing-lists.html ============================================================================== --- websites/staging/airavata/trunk/content/community/mailing-lists.html (original) +++ websites/staging/airavata/trunk/content/community/mailing-lists.html Fri Mar 4 02:31:35 2016 @@ -133,8 +133,19 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache Airavata.</p> -<h3 id="user-mailing-list">User Mailing List</h3> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>We welcome you to join mailing lists and let us know about your thoughts or ideas about Apache Airavata.</p> +<h3 id="user-mailing-list">User Mailing List<a class="headerlink" href="#user-mailing-list" title="Permanent link">¶</a></h3> <p>Apache Airavata User Mailing List is where you can ask questions about Airavata. All the developers are subscribed to the list and you may ask questions on how to integrate Airavata into existing frameworks, or how to use Airavata out of the box. If you have a use case you are intending to use Airavata, please convey it to this list.</p> <ul> <li>Subscribe: <a href="mailto:users-subscr...@airavata.apache.org">users-subscr...@airavata.apache.org</a></li> @@ -146,7 +157,7 @@ </ul> </li> </ul> -<h3 id="developer-mailing-list">Developer Mailing List</h3> +<h3 id="developer-mailing-list">Developer Mailing List<a class="headerlink" href="#developer-mailing-list" title="Permanent link">¶</a></h3> <p>Apache Airavata Developer Mailing List is where the community hangs out and discussion about Airavata development happens. This list is used to coordinate activities and ensure we are all pulling in the same direction.</p> <ul> <li>Subscribe: <a href="mailto:dev-subscr...@airavata.apache.org">dev-subscr...@airavata.apache.org</a></li> @@ -159,7 +170,7 @@ </ul> </li> </ul> -<h3 id="architecture-mailing-list">Architecture Mailing List</h3> +<h3 id="architecture-mailing-list">Architecture Mailing List<a class="headerlink" href="#architecture-mailing-list" title="Permanent link">¶</a></h3> <p>Apache Airavata Architecture Mailing List is have the architecture discussion focused and managable for casual contributors, airavata conducts most of the architecture brainstorming on a architecture mailing list. This list is used to coordinate activities and ensure we are all pulling in the same direction.</p> <ul> <li>Subscribe: <a href="mailto:architecture-subscr...@airavata.apache.org">architecture-subscr...@airavata.apache.org</a></li> @@ -171,7 +182,7 @@ </ul> </li> </ul> -<h3 id="issues-mailing-list">Issues Mailing List</h3> +<h3 id="issues-mailing-list">Issues Mailing List<a class="headerlink" href="#issues-mailing-list" title="Permanent link">¶</a></h3> <p>To keep the dev list traffic down from JIRA issues, comments, GitHUB Pull Requests and comments, these are sent to the Apache Airavata Issues Mailing List. Developers are encouraged to subscribe to this list to follow all development roadmaps and code reviews. </p> <ul> <li>Subscribe: <a href="mailto:issues-subscr...@airavata.apache.org">issues-subscr...@airavata.apache.org</a></li> @@ -183,7 +194,7 @@ </li> </ul> <p>Note: This is a notification only mailing list and all queries have to directed to user/dev/architecture lists as appropriate. </p> -<h3 id="commit-mailing-list">Commit Mailing List</h3> +<h3 id="commit-mailing-list">Commit Mailing List<a class="headerlink" href="#commit-mailing-list" title="Permanent link">¶</a></h3> <p>Apache Airavata Commit Mailing List is where the community receives automated notifications of any changes to the airavata code and documentation.</p> <ul> <li>Subscribe: <a href="mailto:commits-subscr...@airavata.apache.org">commits-subscr...@airavata.apache.org</a></li> Modified: websites/staging/airavata/trunk/content/community/projects-using.html ============================================================================== --- websites/staging/airavata/trunk/content/community/projects-using.html (original) +++ websites/staging/airavata/trunk/content/community/projects-using.html Fri Mar 4 02:31:35 2016 @@ -133,9 +133,20 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>The strategy of the Airavata framework is a minimalist architectural design - a conceptually simple to understand modular, componentized software - which is easy to install, maintain and use. This service oriented architecture helps Apache Airavata to blend into diverse software systems. Early adopters of Apache Airavata includes Science Gateways which integrate applications, workflows, data collections with computational resources like Extreme Science and Engineering Discovery Environment (XSEDE), The National Energy Research Scientific Computing Center (NERSC) and Amazon Elastic Compute Cloud (EC2). </p> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>The strategy of the Airavata framework is a minimalist architectural design - a conceptually simple to understand modular, componentized software - which is easy to install, maintain and use. This service oriented architecture helps Apache Airavata to blend into diverse software systems. Early adopters of Apache Airavata includes Science Gateways which integrate applications, workflows, data collections with computational resources like Extreme Science and Engineering Discovery Environment (XSEDE), The National Energy Research Scientific Computing Center (NERSC) and Amazon Elastic Compute Cloud (EC2). </p> <p>This page provides a sample set of projects using Apache Airavata. Please note that this list if not comprehensive by any means and only to give ideas on possibile integrations. If you are aware of such projects built over Airavata, we would appreciate if you could communite the same by posting the project details to Users of Dev <a href="/community/mailing-lists.html">Mailing Lists</a>.</p> -<h2 id="biovlab">BioVLab</h2> +<h2 id="biovlab">BioVLab<a class="headerlink" href="#biovlab" title="Permanent link">¶</a></h2> <p>The Biology Virtual Collaborative Labs (BioVLAB) provides reconfigurable cloud computing workbench built using Apache Airavata tools to execute workflows on Amazon EC2 resources. The BioVlab project developed workflows include:</p> <ul> <li>Protein Sequence workflow</li> @@ -145,41 +156,41 @@ </ul> <p>Airavata helps BioVLab workbench lower the barriers of setting up and maintaining computational resources and building and configuring bioinformatics tools and databases. </p> <p>More details about the project can be found on <a href="http://biohealth.snu.ac.kr/wiki/index.php/BioVLab_:_Biology_Virtual_Collaborative_Lab">BioVLab Project Website</a>.</p> -<h2 id="computational-chemistry-grid">Computational Chemistry Grid</h2> +<h2 id="computational-chemistry-grid">Computational Chemistry Grid<a class="headerlink" href="#computational-chemistry-grid" title="Permanent link">¶</a></h2> <p>The "Computational Chemistry Grid" (CCG) is a virtual organization that provides access to high performance computing resources for computational chemistry with distributed support and services, intuitive interfaces and measurable quality of service. The CCG client, GridChem, is a Java desktop application that provides an interface to integrate the hardware, software and middleware resources necessary to solve quantum chemistry problems using grid technologies.</p> <p>CCG uses Airavata workflow capabilities to execute couple computational workflows.</p> <p>More details about the project can be found on <a href="https://www.gridchem.org/">GridChem Website</a></p> -<h2 id="des-simwg">DES-SimWG</h2> +<h2 id="des-simwg">DES-SimWG<a class="headerlink" href="#des-simwg" title="Permanent link">¶</a></h2> <p>The simulation working group for the Dark Energy Survey Dark Energy Survey is using Airavata to develop High throughput workï¬ow environment for cosmological simulations. The simulations provide support for analysis of systematics in the three methods associated with large-scale structure (LSS). The workflows devloped and executed using Airavata tools will assist the Simulation Working Group with coordinating a Blind Cosmology Challenge (BCC) process, in which a variety of sky realizations in dierent cosmologies are analyzed.</p> <p>Apache Airavata interfaces DES workflows with XSEDE resources to produce multiple syn- thetic sky surveys of galaxies and large-scale structure in support of science analysis for the Dark Energy Survey. The Airavata workflow infrastructure makes it possible to scale executions to level of fifty 1010-particle simulations.</p> <p>More details can be found of <a href="https://des.fnal.gov/">DES Website</a>.</p> -<h2 id="lcci">LCCI</h2> +<h2 id="lcci">LCCI<a class="headerlink" href="#lcci" title="Permanent link">¶</a></h2> <p>The Leadership Class Configuration Interaction (LCCI) project targets to accurately predict properties of nuclei important for astrophysical and fusion energy processes. Many of these properties are inaccessible to laboratory experiments since either the nuclei are highly unstable or the required experimental precision cannot be obtained. Using computational resources at the National Energy Research Scientific Computing Center (NERSC), the project has obtained converged ground state energies and nearly-converged excited states of several light nuclei using realistic nuclear interactions, and the results compare favorably with experiment. </p> <p>LCCI is one of the DOE SciDAC UNEDF programâs collaboration effort and focuses on Ab Initio and Configuration Interaction computation for nuclear physics theory. The project unifies, preserves and disseminates and provides a user-friendly environment to enable calculations planned for extreme-scale computers and archive the results. </p> <p>The LCCI project uses Apache Airavata to develop workflow infrastructure to democratize the access to the nuclear physics simulations executing on remote supercomputing resources. </p> <p>More details about UNEDF can be found on the <a href="http://www.unedf.org/">Website</a>.</p> -<h2 id="odi">ODI</h2> +<h2 id="odi">ODI<a class="headerlink" href="#odi" title="Permanent link">¶</a></h2> <p>The One-Degree Imager is a gigapixel mosiac camera being built by WIYN Observatory with a pixel scale of 0.1 arcseconds for the 3.5-meter telescope. The ODI camera is an array of 32+2 separate CCD controller with Orthogonal Transfer Array CCD devices to do real time image correction based on guide star video streams. From a continuous stream of guide star images, telescope guiding and atmospheric image aberration can be reduced using real time image shifting via orthogonal charge transfer on the CCD.</p> <p>Apache Airavata enables the ODI's Pipeline, Portal, and Archive (PPA) system to executes the NOAO High Performance Pipeline System (NHPPS) pipelines on XSEDE resources.</p> <p>More details about ODI can be found on the <a href="http://www.noao.edu/wiyn/ODI/">Website</a>.</p> -<h2 id="olam">OLAM</h2> +<h2 id="olam">OLAM<a class="headerlink" href="#olam" title="Permanent link">¶</a></h2> <p>The Ocean Land Atmosphere Model Science Gateway is a collaboration between a consortium of professors, research scientists and students from the University of Miamiâs Rosenstiel School of Marine and Atmospheric Science, Science Gateways Group at the Pervasive Technology Institute, Indiana University, hydrology modelers and water resource managers from the South Florida Water Management District (SFWMD), and government scientists from NOAAâs Atlantic Oceanographic and Meteorological Laboratory. </p> <p>The project is currently in development and OLAMâs unique, flexible mesh refinement capability, combined with local high-resolution land surface characteristics databases and XSEDE computing resources, will make it possible to generate unrivaled regional climate change projections that can be used to guide water management decisions in South Florida.</p> <p>More details about OLAM model can be found on <a href="http://olam-model.sourceforge.net/">Website</a>. </p> -<h2 id="orechem">OREChem</h2> +<h2 id="orechem">OREChem<a class="headerlink" href="#orechem" title="Permanent link">¶</a></h2> <p>The Object Reuse and Exchange (ORE) integrates the information from compound, journals containing the compound and also molecular properties of the compound. ORE proposed by the digital libraries community aggregate resources on the web. OREChem is a research project funded by Microsoft External Research that aims to apply and extend ORE to enable the integration of experimental, bibliographical and molecular properties data. OREChem targets crystallography as its primary application domain. This effort has focused on designing a prototypical, semantic-based eScience infrastructure for chemistry and chemical informatics.</p> <p>This project has used Airavata tools to create web services and orchestrate them as workflows integrating chemistry scholarship with web architectures, grid Computing and semantic Web. The project has published results but is not currently active.</p> <p>For more details about on the project <a href="http://research.microsoft.com/en-us/projects/orechem/">Website</a></p> -<h2 id="paramchem">ParamChem</h2> +<h2 id="paramchem">ParamChem<a class="headerlink" href="#paramchem" title="Permanent link">¶</a></h2> <p>ParamChem project is creating cyberenvironments to automate the process of parameterization for classical molecular mechanics (MM) and semi-empirical (SE) Hamiltonians and allow for wide dissemination of the developed parameters. The Project is developing an extensible cyberenvironment for the rapid and systematic parameterization of novel Hamiltonians; the systematic extension of currently available models, with the resulting parameters sets from both. </p> <p>ParamChem integrates with Apache Airavata Workflow framework to generate QM reference data, monitoring parameter optimization and analysis. The Architecture of ParamChem integration with Airavata and more details are on <a href="https://cwiki.apache.org/confluence/display/AIRAVATA/Param+Chem">Wiki</a></p> <p>Airavata is pleased to leviate ParamChem from Cyberinfrastructure details and rather focus on developing more accurate descriptions of the static and dynamic properties of a wide range of material, pharmacological and biological systems using theoretical methods by simplifying the task of parameter optimization. This will allow for the generation of high quality parameters for a wide variety of molecular systems. Improvements in the accuracy of modeling as well as the range of accessible chemical systems will benefit such fields as chemistry, nanotechnology, medicine and biology, among others. In addition, analytical models used in engineering fields such as structural mechanics and fluid dynamics will become accessible to molecular level treatments.</p> <p>For more details about the project can be found on <a href="https://www.paramchem.org/">ParamChem website</a>.</p> -<h2 id="scigap">SciGaP</h2> +<h2 id="scigap">SciGaP<a class="headerlink" href="#scigap" title="Permanent link">¶</a></h2> <p>Science Gateway Platform as a Service (SciGaP) will provide RESTful application programmer interfaces (APIs) to hosted generic infrastructure services that can be used by domain science communities to create Science Gateways. The hosted services will support access to core infrastructure services required by Science Gateways, including: user identity, accounts, authorization, and access to multiple computational resources from campus, national, and international Grid and cloud efforts. Domain Gateway developers will be able to access these services via community-created interfaces.</p> <p>The SciGaP website provides further details <a href="http://scigap.org/">SciGaP website</a>.</p> -<h2 id="ultrascan">UltraScan</h2> +<h2 id="ultrascan">UltraScan<a class="headerlink" href="#ultrascan" title="Permanent link">¶</a></h2> <p>The Ultrascan Laboratory Information Management System provides a user friendly web inter- face for evaluation of experimental analytical ultracentrifuge data using the UltraScan modeling software. </p> <p>The UltraScan Laboratory Information Management System, uses Airavata to execute analytical ultracentrifugation analysis experiments on XSEDE. These experiments provide information about biological or synthetic molecules for experimental biochemists, biophysicists, and material scientists.</p> <p>For more details about the project can be found on <a href="http://www.ultrascan.uthscsa.edu/">UltraScan Website</a></p> Modified: websites/staging/airavata/trunk/content/community/submit-patch.html ============================================================================== --- websites/staging/airavata/trunk/content/community/submit-patch.html (original) +++ websites/staging/airavata/trunk/content/community/submit-patch.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <ul> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<ul> <li>Identify an issue or documentation that you want to fix or improve</li> <li>Search <a href="https://issues.apache.org/jira/browse/airavata">JIRA</a> and the mailing list to see if itâs already been discussed</li> <li>If itâs a bug or a feature request, open a JIRA issue</li> Modified: websites/staging/airavata/trunk/content/development/build.html ============================================================================== --- websites/staging/airavata/trunk/content/development/build.html (original) +++ websites/staging/airavata/trunk/content/development/build.html Fri Mar 4 02:31:35 2016 @@ -133,7 +133,18 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <h3 id="prerequisites">Prerequisites</h3> + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<h3 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h3> <ul> <li>Sources compilation require Java SE 8 or higher.</li> <li>The project is built with Apache Maven 3+ <a href="http://maven.apache.org/download.html">Download</a> and <a href="http://maven.apache.org/download.html#Installation">install</a> (Maven 2.x build will @@ -144,8 +155,8 @@ </li> <li>Get Airavata source <a href="source.html">checked out</a> from Airavata trunk.</li> </ul> -<h2 id="command-line">Command line</h2> -<h3 id="build-the-distribution">Build the distribution</h3> +<h2 id="command-line">Command line<a class="headerlink" href="#command-line" title="Permanent link">¶</a></h2> +<h3 id="build-the-distribution">Build the distribution<a class="headerlink" href="#build-the-distribution" title="Permanent link">¶</a></h3> <ul> <li>cd airavata-trunk</li> <li>mvn clean install</li> @@ -155,10 +166,10 @@ </li> <li>The compressed binary distribution is created at <PROJECT DIR>/modules/distribution/target</li> </ul> -<h3 id="now-what">Now What?</h3> +<h3 id="now-what">Now What?<a class="headerlink" href="#now-what" title="Permanent link">¶</a></h3> <p>Once you have built the binaries the best thing to do is take a look at our <a href="/documentation/tutorials/airavata-in-5-minutes.html">Airavata in Five Minutes</a> document which will help you get up and running.</p> -<h3 id="build-profiles">Build profiles</h3> +<h3 id="build-profiles">Build profiles<a class="headerlink" href="#build-profiles" title="Permanent link">¶</a></h3> <p>One of the salient features of Airavata Airavata is ability to use modules by themselves or as an integrated solution. The following modules can be build independently.</p> <ul> @@ -183,14 +194,14 @@ integrated solution. The following modul </ul> </li> </ul> -<h2 id="eclipse-preparation">Eclipse preparation</h2> +<h2 id="eclipse-preparation">Eclipse preparation<a class="headerlink" href="#eclipse-preparation" title="Permanent link">¶</a></h2> <ul> <li>Download <a href="http://www.eclipse.org/downloads/">Eclipse IDE for Java EE Developers</a></li> <li>Follow the instructions on Eclipse <a href="http://help.eclipse.org/indigo/index.jsp?topic=/org.eclipse.platform.doc.user/tasks/tasks-127.htm">Add New Software</a> to add the following pluggins</li> <li>Add <a href="http://download.eclipse.org/technology/m2e/releases">M2Eclipse</a> pluggin.</li> <li>Add <a href="http://subclipse.tigris.org/update_1.6.x/">Subclipse</a> pluggin</li> </ul> -<h2 id="eclipse-workspace-configuration">Eclipse workspace configuration</h2> +<h2 id="eclipse-workspace-configuration">Eclipse workspace configuration<a class="headerlink" href="#eclipse-workspace-configuration" title="Permanent link">¶</a></h2> <ul> <li>Build first using command line (see above)</li> <li>Regenerate .project/.classpath files</li> Modified: websites/staging/airavata/trunk/content/development/edit-cms-website.html ============================================================================== --- websites/staging/airavata/trunk/content/development/edit-cms-website.html (original) +++ websites/staging/airavata/trunk/content/development/edit-cms-website.html Fri Mar 4 02:31:35 2016 @@ -133,10 +133,21 @@ <div class="span9"> <section id="content" class="row"> <article class="span9"> - <p>This HowTo documentation will show the needed steps to edit the Airavata + <style type="text/css"> +/* The following code is added by mdx_elementid.py + It was originally lifted from http://subversion.apache.org/style/site.css */ +/* + * Hide class="elementid-permalink", except when an enclosing heading + * has the :hover property. + */ +.headerlink, .elementid-permalink { + visibility: hidden; +} +h2:hover > .headerlink, h3:hover > .headerlink, h1:hover > .headerlink, h6:hover > .headerlink, h4:hover > .headerlink, h5:hover > .headerlink, dt:hover > .elementid-permalink { visibility: visible }</style> +<p>This HowTo documentation will show the needed steps to edit the Airavata website. This includes creation of new pages, modification, and deletion - for files and sub-directories.</p> -<h2 id="how-it-works-in-general">How it works in general</h2> +<h2 id="how-it-works-in-general">How it works in general<a class="headerlink" href="#how-it-works-in-general" title="Permanent link">¶</a></h2> <p>The website is hosted in a Content Management System (CMS). You will not edit the HTML pages directly. The actual edit is split up in 2 parts:</p> <ol> @@ -156,8 +167,8 @@ HTML pages directly. The actual edit is as log message).</p> </li> </ol> -<h2 id="what-do-you-prefer-working-via-commandline-or-in-the-browser">What do you prefer: Working via commandline or in the browser?</h2> -<h3 id="via-commandline">Via commandline</h3> +<h2 id="what-do-you-prefer-working-via-commandline-or-in-the-browser">What do you prefer: Working via commandline or in the browser?<a class="headerlink" href="#what-do-you-prefer-working-via-commandline-or-in-the-browser" title="Permanent link">¶</a></h2> +<h3 id="via-commandline">Via commandline<a class="headerlink" href="#via-commandline" title="Permanent link">¶</a></h3> <p>It is assumed that you have already checked out the code from the SVN repository <a href="https://svn.apache.org/repos/asf/airavata/site/trunk/">https://svn.apache.org/repos/asf/airavata/site/trunk/</a>.</p> <p>Edit the file via your favorite editor like vi and finally commit via SVN:</p> @@ -177,20 +188,20 @@ executing this:</p> </pre></div> -<h3 id="editing-in-the-browser">Editing in the browser</h3> -<h4 id="prerequisites">Prerequisites</h4> -<h5 id="browser-bookmark">Browser bookmark</h5> +<h3 id="editing-in-the-browser">Editing in the browser<a class="headerlink" href="#editing-in-the-browser" title="Permanent link">¶</a></h3> +<h4 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">¶</a></h4> +<h5 id="browser-bookmark">Browser bookmark<a class="headerlink" href="#browser-bookmark" title="Permanent link">¶</a></h5> <p>Normally you see the webpage in your browser. To update this page with an inline-editor and little preview you need to add a link as bookmark to your browser (more information see <a href="https://cms.apache.org/#bookmark">here</a>).</p> <p><a href="javascript:void(location.href='https://cms.apache.org/redirect?uri='+escape(location.href))">Add this link as bookmark</a></p> -<h5 id="apache-id">Apache ID</h5> +<h5 id="apache-id">Apache ID<a class="headerlink" href="#apache-id" title="Permanent link">¶</a></h5> <p>Furthermore, you need an Apache ID to authenticate to the system.</p> -<h4 id="starting">Starting</h4> +<h4 id="starting">Starting<a class="headerlink" href="#starting" title="Permanent link">¶</a></h4> <p>Browse to the respective webpage or directory you would like to edit and click on the bookmark. Now click on the [Edit this directory] link on the top. The following is displayed as content from the CMS.</p> -<h4 id="edit-an-existing-webpage">Edit an existing webpage</h4> +<h4 id="edit-an-existing-webpage">Edit an existing webpage<a class="headerlink" href="#edit-an-existing-webpage" title="Permanent link">¶</a></h4> <p>Click on the actions link [Edit] in the appropriate table cell for editing the favorite file. If the file is not in this directory but in a subdir, just click on the directory name (e.g., "docs/") to enter this directory.</p> @@ -203,21 +214,21 @@ the directory name (e.g., "docs/") to en </ol> <p>When you have finished writing your text, check the "Log message" box, enter a commit message and click on [Submit].</p> -<h4 id="create-a-new-webpage">Create a new webpage</h4> +<h4 id="create-a-new-webpage">Create a new webpage<a class="headerlink" href="#create-a-new-webpage" title="Permanent link">¶</a></h4> <p>When in the correct directory, at the top enter a name for the new text file (e.g., "my-file.mdtext"). Now you enter your text (see topic above).</p> -<h4 id="create-new-subdirectory">Create new subdirectory</h4> +<h4 id="create-new-subdirectory">Create new subdirectory<a class="headerlink" href="#create-new-subdirectory" title="Permanent link">¶</a></h4> <p>When in the correct directory, at the top enter a name for the new directory (e.g., "my-dir/"). Make sure you entered a trailing "/"!</p> -<h4 id="delete-a-webpage-or-subdirectory">Delete a webpage or subdirectory</h4> +<h4 id="delete-a-webpage-or-subdirectory">Delete a webpage or subdirectory<a class="headerlink" href="#delete-a-webpage-or-subdirectory" title="Permanent link">¶</a></h4> <p>When in the corrext directory, click on the actions link [Delete] in the appropriate table cell and enter a commit message. Finally click on [Submit].</p> -<h4 id="how-to-put-into-production">How to put into production?</h4> +<h4 id="how-to-put-into-production">How to put into production?<a class="headerlink" href="#how-to-put-into-production" title="Permanent link">¶</a></h4> <p>After you have edited your files and/or directories, you need now to pubish your modifications into production. For this please click on the link [Publish site] on the top of the webpage. Enter a commit message on click on [Submit]. Alterantively you can click on this <a href="https://cms.apache.org/airavata/publish">pubish link</a>, review the diff's and submit.</p> -<h3 id="links">Links</h3> +<h3 id="links">Links<a class="headerlink" href="#links" title="Permanent link">¶</a></h3> <p><a href="http://www.apache.org/dev/cmsref.html">CMS Documentation Reference</a></p> </article> </section>