You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stratos.apache.org by bu...@apache.org on 2014/05/22 14:24:12 UTC
svn commit: r909594 - in /websites/staging/stratos/trunk/content: ./
index.html
Author: buildbot
Date: Thu May 22 12:24:12 2014
New Revision: 909594
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 Thu May 22 12:24:12 2014
@@ -1 +1 @@
-1596834
+1596836
Modified: websites/staging/stratos/trunk/content/index.html
==============================================================================
--- websites/staging/stratos/trunk/content/index.html (original)
+++ websites/staging/stratos/trunk/content/index.html Thu May 22 12:24:12 2014
@@ -124,13 +124,13 @@
<a class="cIcon tenancy" href=""></a>
<h3>Multi-tenancy</h3>
<p>Multi-tenancy has different levels of isolations. Almost all PaaS vendors only provide container multi-tenancy like virtual machine, LXC or docker etc.</p>
- <a href="about/why-apache-stratos.html#multi-tenancy" class="cReadmore">Read More</a>
+ <a href="/about/why-apache-stratos.html#multi-tenancy" class="cReadmore">Read More</a>
</div>
<div class="cBox cBorderL">
<a class="cIcon scale" href=""></a>
<h3>Multi-factored auto scaling</h3>
<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.</p>
- <a href="" class="cReadmore">Read More</a>
+ <a href="/about/why-apache-stratos.html#multi-factored-auto-scaling" class="cReadmore">Read More</a>
</div>
<div class="clear" style="clear:both;"></div>
<div class="cBox cBorderR cBorderL">