You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stratos.apache.org by la...@apache.org on 2015/05/20 05:31:35 UTC
[2/2] stratos git commit: Adding linebreak for the feature headings
Adding linebreak for the feature headings
Project: http://git-wip-us.apache.org/repos/asf/stratos/repo
Commit: http://git-wip-us.apache.org/repos/asf/stratos/commit/bfdc2e82
Tree: http://git-wip-us.apache.org/repos/asf/stratos/tree/bfdc2e82
Diff: http://git-wip-us.apache.org/repos/asf/stratos/diff/bfdc2e82
Branch: refs/heads/master
Commit: bfdc2e823bd2964c6c10c26e0bf080792b580fcf
Parents: a7411ed
Author: Vishanth <vi...@gmail.com>
Authored: Tue May 19 22:51:49 2015 +0530
Committer: Lahiru Sandaruwan <la...@apache.org>
Committed: Wed May 20 09:01:29 2015 +0530
----------------------------------------------------------------------
README.md | 49 +++++++++++++++++++++++++------------------------
1 file changed, 25 insertions(+), 24 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/stratos/blob/bfdc2e82/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 54abf80..f8b3580 100644
--- a/README.md
+++ b/README.md
@@ -6,17 +6,18 @@ The following are the key features available in Apache Stratos 4.1.0:
Features
--------
-* Composite Application support
+* Composite Application support <br />
This allows applications, which requires different service runtimes with their relationship and dependencies,
to be deployed. Furthermore, each of the service runtimes in the application can scale independently or jointly with
the dependent services. The following operations are supported in composite application support:
* Starting up instances using the StartupOrder, which is defined in the cartridge group definition.
- * Starting up instances using the StartupOrder, which is defined in the application definition. After the relevant clusters and groups get activated according to the startup order, the application itself gets activated.
+ * Starting up instances using the StartupOrder, which is defined in the application definition.
+ After the relevant clusters and groups get activated according to the startup order, the application itself gets activated.
* Termination based on the TerminationBehaviour, which is defined in the cartridge group definition.
* Termination based on the TerminationBehaviour, which is defined in the application definition.
* Sharing information between instances when one instance is dependent on another.
-* Docker Support
+* Docker Support <br />
Docker support using Google Kubernetes and CoreOS. Thereby, Stratos can also leverage the use of Docker in a PaaS.
The following aspects are supported for Docker:
* Auto-scaling Docker Containers.
@@ -26,19 +27,19 @@ The following aspects are supported for Docker:
* VM LB support for dockers
* Private Docker registry
-* Cartridge Agent
+* Cartridge Agent <br />
A Python based and Java based cartridge agent is available in Stratos.
-* Update artifacts at run-time
+* Update artifacts at run-time <br />
After an application is deployed, Stratos allows users to update the following artifacts, which directly effects the runtime.
* Auto-scaling policy definition
* Deployment policy definition
* Application definition
-* Cloud Controller
+* Cloud Controller <br />
Cloud Controller (CC) leverages Apache jclouds' APIs and provides a generic interface to communicate with different IaaSes.
-* Multi-factored auto-scaling
+* Multi-factored auto-scaling <br />
The Auto-scaler uses a Complex Event Processor (CEP) for real-time decision making, and it integrates both real-time
and rule-base decision making to provide better control over scaling of platforms. Stratos allows users to define
auto-scaling policies with multiple factors,i.e., requests in flight, memory consumption and load average, which are
@@ -47,55 +48,55 @@ considered when scaling up or down. The Auto-scaler also supports scaling for no
For detailed information on how multi-factored auto-scaling takes place in Stratos,
see [Autoscaler](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Autoscaler).
-* Smart policies
+* Smart policies <br />
The Auto-scaler in Stratos uses two smart policies when making auto-scaling decisions: auto-scaling policy and deployment policy.
The instances will be automatically spawned based on the smart policies that are applied to the application.
<br />
For more information on auto-scaling and deployment policy scaling policies, see [Smart Policies](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Smart+Policies).
-* Multiple IaaS support
+* Multiple IaaS support <br />
Apache Stratos is tested on the following IaaS providers: AWS EC2 and OpenStack. However, it is very easy to extend
Apache Stratos to support any IaaS that is supported by [Apache jclouds](https://jclouds.apache.org) i.e., Google cloud, CloudStack etc.
-* Multi-cloud bursting
+* Multi-cloud bursting <br />
Apache Stratos supports multiple IaaSs. When the maximum limit of instances have been reached in an IaaS, instances
are spawned on another IaaS, which is in another network partition. Thereby, this will enable resource peak times to
be off-loaded to another cloud.
-* Controlling IaaS resources
+* Controlling IaaS resources <br />
It is possible for DevOps to define partitions in a network partition, to control IaaS resources. Thereby,
Apache Stratos can control resources per cloud, region, and zone. Controlling of IaaS resources provide a high
availability and solves disaster recovery concerns. For more information, see [Cloud Partitioning](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Cloud+Partitioning).
-* Loosely coupled communication
+* Loosely coupled communication <br />
Stratos uses the Advanced Message Queuing Protocol (AMQP) messaging technology for communication among all its components.
Apache Stratos uses an AMQP Message Broker (MB), namely ActiveMQ, to communicate in a loosely coupled fashion.
However, it is possible to use any MB, which supports AMQP, with Stratos.
-* Multi-tenancy
+* Multi-tenancy <br />
Stratos supports in-container multi-tenancy. Thereby, this helps to optimize the resource utilization.
-* Cartridges
+* Cartridges <br />
Support for PHP, MySQL, Tomcat, Windows based (.NET) cartridges. The following is the list of tested cartridges:
PHP, MySQL, Ruby, Node.js, Wordpress, Drupal, Tomcat, HAProxy and NGINX.
-* Pluggable architecture support for cartridges
+* Pluggable architecture support for cartridges <br />
A cartridge is a package of code that includes a Virtual Machine (VM) image plus additional configuration, which can
be plugged into Stratos to offer a new PaaS service. Stratos supports single tenant and multi-tenant cartridges.
If needed, tenants can easily add their own cartridges to Stratos.
<br />
For more information on how Stratos uses cartridges, see [Cartridge](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Cartridge).
-* Cartridge automation using Puppet
+* Cartridge automation using Puppet <br />
Cartridges can be easily configured with the use of an orchestration layer such as Puppet.
-* Support for third party load balancers
+* Support for third party load balancers <br />
Stratos supports third-party load balancers (LBs), i.e, HAProxy, NGINX. Thereby, if required, users can use their own
LB with Stratos.
<br />
For more information, see [Load Balancers](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Load+Balancers).
-* Artifact distribution coordination
+* Artifact distribution coordination <br />
The Artifact Distribution Coordinator is responsible for the distribution of artifacts. Artifacts can be uploaded
using git push. When a trigger event happens the ADC will find the correct matching cluster for that event from the
topology and send notifications to appropriate Cartridge instances. ADC supports external Git repositories and GitHub
@@ -104,33 +105,33 @@ a service instance.
<br />
For more information, see [Artifact Distribution Coordinator](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Artifact+Distribution+Coordinator).
-* Stratos Manager Console
+* Stratos Manager Console <br />
Administrators and tenants can use the Stratos Manager console, which is a web-based UI management console in Stratos,
to interact with Stratos.
<br />
For more information, see [Stratos Manager](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Stratos+Manager).
-* Stratos REST API
+* Stratos REST API <br />
DevOps can use REST APIs to carry out various administering functions (e.g., adding a tenant, adding a cartridge, etc.).
<br />
For more information, see the [Stratos API Reference Guide](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Stratos+API+Reference).
-* Interactive CLI Tool
+* Interactive CLI Tool <br />
Command Line Interface (CLI) tool provides users an interface to interact with Stratos and manage your applications.
<br />
For more information, see the [CLI Tool](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+CLI+Tool) and the
[CLI Guide](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+CLI+Guide).
-* Monitoring and metering
+* Monitoring and metering <br />
Apache Stratos provides centralized monitoring and metering. The level of resource utilization in Stratos is measured using metering.
-* Persistent volume support for cartridges
+* Persistent volume support for cartridges <br />
If required, the DevOps can enable a persistent volume for cartridges. If persistent volume is enabled, Apache Stratos
automatically attaches a volume when a new cartridge instance is created.
<br />
For more information, see [Persistence Volume Mapping](https://cwiki.apache.org/confluence/display/STRATOS/4.1.0+Persistence+Volume+Mapping).
-* Gracefully shutdown instances
+* Gracefully shutdown instances <br />
Before terminating an instance, when scaling down, the Auto-scaler will allow all the existing requests to the instance
to gracefully shutdown, and not accepting any new requests for that instance.