Author: buildbot
Date: Thu May 22 12:35:35 2014
New Revision: 909597
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 Thu May 22 12:35:35 2014
@@ -1 +1 @@
-1596842
+1596843
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 Thu
May 22 12:35:35 2014
@@ -148,7 +148,7 @@
<p>Another important extendability of Apache Stratos is that ability to plugin
any IaaS due to the use of apache jclouds API. Which give more freedom to
choose your own IaaS vendor, and it also enable to extend multiple IaaS
integration, which is important in features like cloud bursting etc.
<h2>True flexibility for custom services</h2>
<p>If you look at current PaaS offering, you can't get true flexibility for
your own custom service. Many cases, you have to bare with what they are
offering and make your solution around it. With the Apache Stratos cartridge
model, you can create custom service, without any limited boundaries. Your
cartridge can be fully configured (installed all software, configuration ..etc)
or zero configured (let cartridge user to install and config what they want) or
in-between. This will allow you to customise your PaaS to suite in your
current business workflows.</p>
-<a name="multi-factored-auto-scaling"/></a>
+<a class="cBookmark" name="multi-factored-auto-scaling"/></a>
<h2>Multi-factored auto scaling</h2>
<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. Also its capable
of dealing with these multiple factors run through scaling algorithm
simultaneously. Inflight request count on Load Balancers, Load average, Memory
consumption are some of factors and its easy to extend (benefit from clean
unified communication) to any factors need to take care of the auto scaling.</p>
<img src="/images/v3/digram3.jpg"/>
@@ -163,7 +163,7 @@
<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>
-<a name="multi-tenancy"/></a>
+<a class="cBookmark" name="multi-tenancy"/></a>
<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>
@@ -186,7 +186,7 @@
<p>With the partitions and Network partitions, devOps can defined smart
policies namely auto scaling and deployment policies, which can be used in
cartridge subscriptions. Smart policies will provide cloud SLAs which
absolutely mandatory when you consider cloud solutions.</p>
<h2>Logging, metering and monitoring</h2>
<p>Logging, metering and monitoring are primary but important features you
should not neglect. Apache Stratos capable of capturing all health statistics,
application logs well as usage and aggregate them into centralized location. it
provide devOps life easy otherwise it is impossible task to login and monitor
each and every instances in a large scale deployment which has hundreds of
instances.</p>
-<a name="cloud-bursting"/></a><h2>Cloud bursting</h2>
+<a class="cBookmark" name="cloud-bursting"/></a><h2>Cloud bursting</h2>
<p>Cloud bursting is now widely discuss since it reduces TCO (Total Cost of
Ownership) while provisioning application into another cloud to handle peak
load. Like all other aspect, Apache Stratos cloud bursting also carefully
design to work with private, public and hybrid cloud with effective
provisioning load balancers per bursting cloud.</p></p>
</article>
</section>
