incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "StratosProposal" by AfkhamAzeez
Date Thu, 30 May 2013 14:24:16 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "StratosProposal" page has been changed by AfkhamAzeez:
https://wiki.apache.org/incubator/StratosProposal?action=diff&rev1=2&rev2=3

  
  == Proposal ==
  The Stratos PaaS framework will encompass four layers:
- 1) An IaaS-agnostic layer that can interface with a wide variety of IaaS systems to provide
elastic resources, and for multiple IaaS infrastructures to be automated at one time (hybrid
clouds.)
+  1. An IaaS-agnostic layer that can interface with a wide variety of IaaS systems to provide
elastic resources, and for multiple IaaS infrastructures to be automated at one time (hybrid
clouds.)
- 2) A PaaS Controller that with a cloud controller that automates and monitors IaaS runtime
interactions, distributes artifacts to the underlying runtimes, deploys workloads, directs
runtime traffic to the right runtimes using a tenant-aware elastic load balancer, and provides
a portal for monitoring and provisioning of tenants on the system.
+  2. A PaaS Controller that with a cloud controller that automates and monitors IaaS runtime
interactions, distributes artifacts to the underlying runtimes, deploys workloads, directs
runtime traffic to the right runtimes using a tenant-aware elastic load balancer, and provides
a portal for monitoring and provisioning of tenants on the system.
- 3) Foundational Services including security, logging, messaging, registry, storage (relational,
file, and noSQL), task management, and billing.  Foundational services will be loosely-coupled
to allow swapping in alternate foundational services. 
+  3. Foundational Services including security, logging, messaging, registry, storage (relational,
file, and noSQL), task management, and billing.  Foundational services will be loosely-coupled
to allow swapping in alternate foundational services. 
- 4) A Cartridge Architecture allowing frameworks, servers, and other runtimes to participate
in the advantages of the system.  The Cartridge Architecture must support multi-tenant workloads,
and provide for various levels of tenant isolation and policy-based control over provisioning.
+  4. A Cartridge Architecture allowing frameworks, servers, and other runtimes to participate
in the advantages of the system.  The Cartridge Architecture must support multi-tenant workloads,
and provide for various levels of tenant isolation and policy-based control over provisioning.
  
  
  Together these layers offer a foundational layer upon which applications and middleware
frameworks can be deployed to speed time-to-market and simplify the development of scalable
applications, as well as provide a high level of resource sharing and centralized management
that can deliver lowest resource, infrastructure, and management costs.
@@ -35, +35 @@

  
  
  Stratos has appeal, and should attract community members, from among a number of constituencies:
- - Private PaaS deployment within an enterprise to benefit enterprise application deployment.
+  * Private PaaS deployment within an enterprise to benefit enterprise application deployment.
- - PaaS providers wishing to leverage a PaaS toolkit to build a PaaS customized to their
particular vertical industry, ecosystem, or internal development processes.
+  * PaaS providers wishing to leverage a PaaS toolkit to build a PaaS customized to their
particular vertical industry, ecosystem, or internal development processes.
- - SaaS providers wishing to build upon a widely-deployed and supported elastic, multi-tenant
platform.
+  * SaaS providers wishing to build upon a widely-deployed and supported elastic, multi-tenant
platform.
- - ISPs wishing to offer hosted application services with higher resource utilization capabilities
than provided by IaaS layers.
+  * ISPs wishing to offer hosted application services with higher resource utilization capabilities
than provided by IaaS layers.
- - IaaS vendors wishing to provide higher-level PaaS services to customers.
+  * IaaS vendors wishing to provide higher-level PaaS services to customers.
- - Vendors wishing to support Stratos on or under their projects and products.  Vendors of
higher level runtimes will contribute Cartridges enabling those runtimes to participate in
the Stratos-sphere.  Vendors of underlying IaaS infrastructure will contribute adapters to
ensure their IaaS is fully operational for Stratos.
+  * Vendors wishing to support Stratos on or under their projects and products.  Vendors
of higher level runtimes will contribute Cartridges enabling those runtimes to participate
in the Stratos-sphere.  Vendors of underlying IaaS infrastructure will contribute adapters
to ensure their IaaS is fully operational for Stratos.
  
  == Core Developers ==
  All core developers are currently employed by WSO2. This is a very important project for
our company and is a core part of our business. Whilst we have sought to engage a broader
community through the meritocratic model this has, until now, manifested itself through our
teams contributions to other projects used within Stratos, including
@@ -68, +68 @@

  stratos-dev@incubator.apache.org - for developer/user discussions,  JIRA change notifications
& continuous build/test notifications
  
  === Other Resources ===
- 1. A Git repository
+  1. A Git repository
- 2. A JIRA issue tracker: short code "Stratos"
+  2. A JIRA issue tracker: short code "Stratos"
  
  
  == Initial Committers ==

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message