3. Placing
PaaS
in
a
Connected
Business
Context
Reduces
interac)on
fric)on
and
cost
Accelerates
interac)ons
inside
and
outside
the
organiza)on
Increases
engagement
and
enhances
produc)vity
Senses
business
ac)vity
and
automa)cally
adapts
http://wso2.com/landing/enabling-the-connected-business
4. Mapping
The
PaaS
Promise
On-‐demand
Internet
Accessible
Self
Service
Cloud
Services
Resource
Pooling
Measured
service
Measured
Service
DevOps
Elas)c
Scalability
5. PaaS Blockers
• Only
suitable for web applications
• Fuzzy
cost model benefits
• Dynamic
environment introduces
management complexity
• High
learning curve to adopt new practices
• Gaining
Development and Operations Buy-in
6. Technology Trends Shaping PaaS
• Rise
in cloud based DevOps and ALM adaptation
• Rise in demand for hybrid cloud configurations
• Big data analysis and complex event processing
in the cloud
• Greater emphasis on required change
management and cost benefits when enterprise
organizations select aPaaS instead of CEAP
19. Understanding the Stratos Controller
The Stratos Controller is a set of components that deploy, scale, monitor,
and manage an elastic middleware Cloud.
•
Cloud Controller: using jclouds creates/removes VM or LXC instances, based on
input from -
•
Load Monitor: acquires load information from multiple sources
•
Elastic Load Balancer: distributes requests to the correct instances, based on
tenant and load balance, including rewriting URLs
•
Artifact Distribution Server: takes complete applications and breaks into perinstance components, which are then loaded into instances by
•
Deployment Synchronizer: checks out the right code for an instance
•
Management Console: allows control of all this by either Web UI or commandline tooling
20. Stratos Core Services
• The
Stratos Core Services provide essential
capabilities to Cartridges and applications running
in Stratos (all available “as-a-Service”)
Logging (Log4J, Syslog)
• Data (MySQL and Cassandra)
• Identity (SAML2, OAuth, OpenID, XACML)
• Registry/Repository (for metadata and config)
• Billing and Metering
• Monitoring (BAM)
• File System (HDFS)
•
22. Understanding Cartridges
• A
cartridge is a package of code/
configuration that plugs into Stratos to
offer a new PaaS Service
• e.g.
Carbon ESB cartridge plugs in to provide a
Stratos ESB-as-a-Service
• PHP Cartridge plugs in to provide PHP-as-aService
• A
cartridge is a VM image plus config
• In
•
Stratos 2.0 you need a VM per IaaS
e.g. need to create both EC2 and LXC image to use
on both IaaS
23. Cartridge Tenancy
• A
•
cartridge can operate in two modes:
Single tenant
•
•
•
Stratos will run and manage a separate instance for each tenant
The PHP Cartridge runs this way
Multi-tenant
•
•
•
Stratos will run multiple instances partitioned so that sets of
tenants run on sets of instances
Each instance of a Cartridge may run more than one tenant
Carbon Cartridges run this way
25. DevOps PaaS Differentiation
• Self
service project and policy configuration
• Via
project configuration portals
• Security, service levels, frameworks, usage, topology
• Automated
platform provisioning
• Via
service tier templates
• Framework and policy enforcement points (PEPs)
• Process
automation
• Continuous
build, test, and deployment
• Code promotion and synchronization across
environments and servers
• Dependency
analysis and impact analysis