svn commit: r909387 - in /websites/staging/stratos/trunk/content: ./ about/why-apache-stratos.html

[bu...@apache.org]

Author: buildbot
Date: Tue May 20 09:35:14 2014
New Revision: 909387

Log:
Staging update by buildbot for stratos

Modified:
    websites/staging/stratos/trunk/content/   (props changed)
    websites/staging/stratos/trunk/content/about/why-apache-stratos.html

Propchange: websites/staging/stratos/trunk/content/
------------------------------------------------------------------------------
--- cms:source-revision (original)
+++ cms:source-revision Tue May 20 09:35:14 2014
@@ -1 +1 @@
-1596162
+1596163

Modified: websites/staging/stratos/trunk/content/about/why-apache-stratos.html
==============================================================================
--- websites/staging/stratos/trunk/content/about/why-apache-stratos.html (original)
+++ websites/staging/stratos/trunk/content/about/why-apache-stratos.html Tue May 20 09:35:14 2014
@@ -156,15 +156,30 @@
 <h2>Predicting future loads</h2>
 <p>Another important capability of Apache Stratos is predicting immediate future load, based on current health statistics. All cartridges, Load balances, health monitors are publishing health status into CEP (Complex Event Processor) via real time event bus. CEP will aggregate all these events and calculate first derivative, second derivative for a given time window frame and paas resulting streams to Auto scaler via reliable message bus.</p>
 <p>Auto Scaler used motion equation to get immediate (next minute) future load.</p>
-<span>s = ut+ 1/2 at<sup>
-
-2</sup></span>
-<ul>
-<li>S = predicted load</li>
-<li>u  = first derivative (eg. first derivative of current load average)</li>
-<li>t  = time interval (eg. one minute)</li>
-<li>a  = second derivative (eg. second derivative of current load average)</li>
+<span>s = ut+ 1/2 at<sup>2</sup></span>
+<ul class="cEcation">
+<li>s = predicted load</li>
+<li>u = first derivative (eg. first derivative of current load average)</li>
+<li>t = time interval (eg. one minute)</li>
+<li>a = second derivative (eg. second derivative of current load average)</li>
 </ul>
+<P>Multi factored auto scaler leads to maximize resource utilization while benefiting easy of capacity planning. Also its capable of dynamic resource provisioning across multiple clouds. This give devOps life easy and very accurate capacity planning.</p>
+
+<h2>Multi-tenancy</h2>
+
+<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>
+
+<p>Apache Stratos has both container and in-container multi-tenancy capability provide Apache Stratos to be in uniqueness in the PaaS space. With the In-container multi-tenancy support user can have high tenance density which optimised resource utilisation by sharing resources such as CPU and memory across the tenants.</p>
+
+<h2>Scalable dynamic load balancing</h2>
+
+<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>
+
+<p>Apache Stratos capable of provision scalable load balancers for any IaaS clouds well as integrate any third party load balancers. This gives more flexibility and extendability while providing more efficient load balancing based on deployment environment.</p>
+
+<h2>Apache Stratos Load Balancing features and benefits</h2>
+
+<p>Provisioning - Load balancers can spin up dynamically. Based on load balancer as cartridges, Apache Stratos will spin up defined minimum load balancers when the first application subscription comes. Also capable of defining load balancers to spin up in every cloud, regions enabling effective multi-cloud deployment specially for geo-graphical based application deployments.</p>
         	</article>
     	</section>
   	</div>