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

[bu...@apache.org]

Author: buildbot
Date: Fri May 30 08:47:37 2014
New Revision: 910506

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 Fri May 30 08:47:37 2014
@@ -1 +1 @@
-1598491
+1598498

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 Fri May 30 08:47:37 2014
@@ -177,7 +177,19 @@
 <p><strong>Flexibility</strong> - Can define service-level dedicated load balancing. Easy to define service-level load balancers via REST API while capable of carrying out load balancing in multiple services with a single load balancer.</p>
 <p><strong>Expandability</strong> - Capability of integrating with any third-party load balancers. With the message broker and topology-based model, it's easy to integrate load balancers like HAProxy, nginx, AWS ELB, etc. It provides optimized load balancing based on the deployment (e.g. uses AWS ELB on EC2 deployment).</p>
 <img src="/images/v3/digram4.jpg"/>
-<p>Figure 4</p> </p>
+<p>Figure 4</p>
+<h2>Capability of controlling IaaS resources</h2>
+<p>Different IaaS vendors provide different resource pooling, like regions, availability zones, hosts, subnets, etc. If we could not control these resources and utilize it in the PaaS layer it would result in waste of many resources. Controlling these is also key to carry out high available kinds of deployments.</p>
+<p>Apache Stratos has been carefully designed to address the problem discussed above. It has introduced partitions and network partitions to group IaaS resources to deploy cartridges in a very controlled manner.</p>
+<h3>Partitions</h3>
+<p>Partitions are logical groups that can be defined by devOps based on available IaaS resource pooling like regions, availability zones, etc. With this definition, Apache Stratos is capable of selecting where to spawn Cartridge instances and select the resource pool, which is very useful in deployments like high available or disaster recovery.</p>
+<h3>Network partitions</h3>
+<p>With this concept, Apache Stratos can logically group one or more partitions that reside in the same network. With this network partition concept, Apache Stratos Auto Scaler can have the intelligence of monitoring and predicting load of particular network bound regions and take necessary auto scaling decisions very easily. This is also a very unique and important feature that Apache Stratos brings into the PaaS space.</p>
+<h2>Logging, metering, and monitoring</h2>
+<p>Logging, metering, and monitoring are primary, but important features that should not be ignored. Apache Stratos is capable of capturing all health statistics, application logs, and usage, and aggregating them into a centralized location. It makes devOps life easy, otherwise it is an impossible task to login and monitor each and every instance in a large-scale deployment that has hundreds of instances.</p>
+<a class="cBookmark" name="cloud-bursting"/></a>
+<h2>Cloud bursting</h2>
+<p>Cloud bursting is now widely discussed as it reduces TCO (total cost of ownership) while provisioning application into another cloud to handle peak load. Like all other aspects, Apache Stratos cloud bursting is also carefully designed to work with private, public, and hybrid cloud with effective provisioning load balancers per bursting cloud.</p></p>
         	</article>
     	</section>
   	</div>