svn commit: r909410 - in /websites/staging/stratos/trunk/content: ./ index.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 20 11:41:07 2014
New Revision: 909410

Log:
Staging update by buildbot for stratos

Modified:
    websites/staging/stratos/trunk/content/   (props changed)
    websites/staging/stratos/trunk/content/index.html

Propchange: websites/staging/stratos/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 20 11:41:07 2014
@@ -1 +1 @@
-1596204
+1596209

Modified: websites/staging/stratos/trunk/content/index.html
==============================================================================
--- websites/staging/stratos/trunk/content/index.html (original)
+++ websites/staging/stratos/trunk/content/index.html Tue May 20 11:41:07 2014
@@ -123,13 +123,13 @@
         <div class="cBox">
             <a class="cIcon tenancy" href=""></a>
             <h3>Multi-tenancy</h3>
-            <p>Stratos uses an in-container multi-tenancy (MT) model. This means, for example, within an application server MT is available for applications. In other words, a container can host multiple tenants.</p>
+            <p>Multi-tenancy has different levels of isolations. Almost all PaaS vendors only provide container multi-tenancy like virtual machine, LXC or docker etc. But this is not scalable for large deployment scenario which has hundred thousand or million of tenants. </p>
             <a href="" class="cReadmore">Read More</a>
         </div>
            <div class="cBox cBorderL">
             <a class="cIcon scale" href=""></a>
             <h3>Multi-factored auto scaling</h3>
-            <p>The auto scaling model supported by Apache Stratos (Incubating) provides better control over how the platform scales. </p>
+            <p>Majority of PaaS providers only used http traffic to auto scale or dynamic resource provisioning. It gives limitation on scaling non-http based application. But Apache Stratos auto scaler can take http traffic and non-http health data to do intelligent dynamic resource provisioning.</p>
             <a href="" class="cReadmore">Read More</a>
         </div>
         <div class="clear" style="clear:both;"></div>
@@ -142,7 +142,7 @@
            <div class="cBox">
             <a class="cIcon load" href=""></a>
             <h3>Scalable dynamic load balancing</h3>
-            <p>The platform keeps track of who does what on whose behalf, making it easy to do manage, monitor and detect all identity related aspects.</p>
+            <p>Load balancers play a major role in scaling application in the cloud. Load balancers distribute incoming traffics into several server nodes, or clusters, or other resources to maximize the throughput, minimise response time and provide mechanism scale application based on the workload.</p>
             <a href="" class="cReadmore">Read More</a>
         </div>
     </div>