You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airavata.apache.org by sm...@apache.org on 2012/10/23 04:54:38 UTC
svn commit: r1401146 - in /airavata/site/trunk/content:
architecture/overview.mdtext development/release-management.mdtext
Author: smarru
Date: Tue Oct 23 02:54:37 2012
New Revision: 1401146
URL: http://svn.apache.org/viewvc?rev=1401146&view=rev
Log:
forcing a build to test if cms svsnpub is working back
Modified:
airavata/site/trunk/content/architecture/overview.mdtext
airavata/site/trunk/content/development/release-management.mdtext
Modified: airavata/site/trunk/content/architecture/overview.mdtext
URL: http://svn.apache.org/viewvc/airavata/site/trunk/content/architecture/overview.mdtext?rev=1401146&r1=1401145&r2=1401146&view=diff
==============================================================================
--- airavata/site/trunk/content/architecture/overview.mdtext (original)
+++ airavata/site/trunk/content/architecture/overview.mdtext Tue Oct 23 02:54:37 2012
@@ -16,26 +16,15 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-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.
-
-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.
-
-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 running
-Web service instance by looking up in XRegistry. When no Web service instances are available, a new instance of the
-GFac service is created.
+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.
+
+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.
+
+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.
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.
+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.
Modified: airavata/site/trunk/content/development/release-management.mdtext
URL: http://svn.apache.org/viewvc/airavata/site/trunk/content/development/release-management.mdtext?rev=1401146&r1=1401145&r2=1401146&view=diff
==============================================================================
--- airavata/site/trunk/content/development/release-management.mdtext (original)
+++ airavata/site/trunk/content/development/release-management.mdtext Tue Oct 23 02:54:37 2012
@@ -16,26 +16,18 @@ Notice: Licensed to the Apache Softwa
specific language governing permissions and limitations
under the License.
-Releases are crucial aspects for an apache project and following the guidelines is very important.
-The [Release FAQ][release-faq] describes the foundation wide policies. The [Incubator Release Management][inc-release-mgmt]
-describes incubator project specific release process. The following instructions walkthrough Airavata specific release steps.
+Releases are crucial aspects for an apache project and following the guidelines is very important. The [Release FAQ][release-faq] describes the foundation wide policies. The following instructions walkthrough Airavata specific release steps.
<a name="release-setup"></a>
###One time release management setup
-This section describes release management configuration steps, if you have previously configured these steps,
-jump directly to [Release Process](#release-process).
+This section describes release management configuration steps, if you have previously configured these steps, jump directly to [Release Process](#release-process).
Performing a release will require:
-* Access to people.apache.org to stage builds, verify access by following these [instructions](#access-people).
* Generate, sign and upload gpg key, you can follow these [gpg instructions](#gpg-key).
* Configure Maven and get access to Nexus Repo, more [maven & nexus instructions](#maven-nexus-setup).
-<a name="access-people"></a>
-####Access to people.apache.org
-Ensure you can access the apache gateway server by `ssh <asfid>@people.apache.org`. If you have any trouble with your ASF LDAP, you can change or reset your password at [Apache Account Utility Page][asf-profile].
-
<a name="gpg-key"></a>
#### Generate GPG key
The releases have to be signed by public key cryptography signatures. Detailed instructions on why releases have to be signed are provided on [Release Signing][release-signing] page.
@@ -234,7 +226,6 @@ gpg: Good signature from ...
gpg: Signature made ...
[release-faq]: http://www.apache.org/dev/release.html
-[inc-release-mgmt]: http://incubator.apache.org/guides/releasemanagement.html
[asf-profile]: https://id.apache.org/
[gpg-keys]: http://www.apache.org/dev/openpgp.html
[release-signing]: http://www.apache.org/dev/release-signing.html
@@ -243,4 +234,4 @@ gpg: Signature made ...
[key-sign]: http://www.apache.org/dev/release-signing.html#key-signing-party
[henk-trust]: http://people.apache.org/~henkp/trust/
[maven-artificats]: http://www.apache.org/dev/publishing-maven-artifacts.html#dev-env
-[airavata-dist-svn]: https://dist.apache.org/repos/dist/release/incubator/airavata/
\ No newline at end of file
+[airavata-dist-svn]: https://dist.apache.org/repos/dist/release/airavata/
\ No newline at end of file