WSO2 Stratos 2010 September Workshop

  • 1,893 views
Uploaded on

 

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,893
On Slideshare
0
From Embeds
0
Number of Embeds
2

Actions

Shares
Downloads
65
Comments
0
Likes
1

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Introduction to WSO2 Cloud Platform Presenter Afkham Azeez Senior Software Architect & Senior Manager WSO2 Inc.
  • 2. About Me ● Architected the WSO2 Carbon & WSO2 Stratos platforms ● Member, Apache Software Foundation ● Committer & PMC member on a number of Apache projects ● Senior Manager, WSO2 PaaS – Manage the Stratos team which spans across all product groups ● LinkedIn http://lk.linkedin.com/in/afkhamazeez
  • 3. Cloud Computing ● Ability to buy computations power, storage or services on demand ● Service Delivery Model – What is given “as a Service” – “as a Service” ● Pay per use ● Self service provisioning ● Virtually unlimited resources ● Resource sharing ● Cloud Deployment Model – Where is the cloud deployed
  • 4. Cloud Computing – Service Delivery Model For end-users For developers, integrators, architects For infrastructure specialists
  • 5. Cloud Computing – Deployment Model ● In public – IaaS, PaaS, SaaS available on the Internet – Use one of the cloud service providers – Information is stored and managed by provider under SLA ● In Private – Have a cloud, in-house – IaaS provides by hardware on your data centers – PaaS running on your IaaS – SaaS executing on your PaaS ● Or use both – Hybrid Cloud
  • 6. Enterprise IT in 2010 © WSO2 2010 6
  • 7. Enterprise IT in 2015+ © WSO2 2010 7
  • 8. Some aims of ours with Stratos ● Configure an Identity Server in the Cloud – Either bootstrap with users or connect to existing AD/LDAP – Use with Google Apps, Salesforce.com as well as other Stratos services ● Go online and deploy a WAR file ● Seamless access control for Tomcat webapps – Including OpenID/OAuth support ● Seamless access control for your Governance Registry – Yes, you get a Governance Registry out-of-the-box ● Every service you deploy is automatically governed, monitored and metered And a lot more too…
  • 9. web.xml <login-config> <auth-method>BASIC</auth-method> <realm-name>Basic Auth</realm-name> </login-config> Automatically ties into Stratos Identity
  • 10. WSO2 Platform as a Service ● Available as a public cloud – https://cloud.wso2.com – Hosted with Amazon EC2 ● Or in the private cloud – In house deployment of pass – Available based on a variety of IaaS (UEC, etc.) ● Or both – Hybrid solution architecture
  • 11. Why Public Cloud? ● No need to buy machines ● No need to setup ● No need to spend anything, if we are not using ● No need to wait, if you need more computing power ● It is just out there, ready to be used
  • 12. Why not Public Cloud ● Because it is out there :) – Data is wealth, often key to competitive advantage ● Not supposed to move it out-premisses – Due to some security reasons ● Take no chance on sensitive elements in IT – You cannot move your mainframe to your cloud ● Legacy apps are better off the way they are – Quality of service ● Availability, SLA – Regulations ● Government and industry regulations – Like all banks should have the data center within the country ● Greater total cost over time
  • 13. Private Cloud to the Rescue ● Cloud in-house ● All cloud platform advantages intact ● Stratos can be deployed onto a private cloud setup – Leverage “cloud native” aspects
  • 14. Pre-Requisites for a Private Cloud ● IaaS – Hardware ● Computers (CPU/Memory/virtualization) ● Large storage ● High speed network connectivity – Cloud ready OS ● e.g. Ubuntu Server – Cloud Infrastructure ● e.g. Eucalyptus
  • 15. User Experience of Stratos
  • 16. Why “Cloud Native” on Private Cloud? ● Distributed / Dynamically Wired (works properly in the cloud) – Finds services across applications – Reuse services from other departments e.g. People information required by all of Finance, Engineering and Sales ● Elastic (uses the cloud efficiently) – Scales up and down as needed – Some departments might want varying resources with varying bandwidth with varying priority ● Multi-tenant (only costs when you use it) – Virtual isolated instances to facilitate isolation between departments etc. – e.g. Sales vs Finance tenants. Finance want complete isolation for some sensitive services ● Self-service (in the hands of users) – De-centralized creation and management of tenants – No need to come to IT department to gain access – served via portal – no need to be on the queue or waiting list ● Granularly Billed and Metered (pay for just what you use) – Allocate costs to exactly who uses them – Bill and cost various departments per use – Get rid of the situations where unused computing assets lying in one department while the other departments are starving for the same ● Incrementally Deployed and Tested (supports seamless live upgrade) – Not disrupt other operations © WSO2 2010
  • 17. Autoscaling ● The Solution – Traditional solution ● Buying safety-net capacity – Better solution ● Scale-up the system when the load increases ● Scale-down the system when the load decreases ● Should not have idling nodes ● Pay only for the actual computing power & bandwidth utilized ● Cloud independent autoscaling
  • 18. Deploying a Service on the Cloud AMI Instances 19
  • 19. Deploying a Service on the Cloud 20
  • 20. Deploying a Service on the Cloud 21
  • 21. Deploying a Service on the Cloud Service is available now 22
  • 22. Autoscaling – Steady load 23
  • 23. Autoscaling – Load increasing Load Increases 24
  • 24. Autoscaling – Load increasing Startup new instances 25
  • 25. Autoscaling – Steady load New instances join group 26
  • 26. Autoscaling – Load decreasing Load Decreases 27
  • 27. Autoscaling – Load decreasing Terminate instances 28
  • 28. Autoscaling – Steady load 29
  • 29. Analysis & Results 30
  • 30. Analysis & Results 31
  • 31. “Multi-tenancy” within organizations ● Can be used to give departments their own PaaS world to operate in ● Yet all share same hardware resources – Not all departments need resources at the same time – Really pay per use – Opportunity to unify departmental level small server pools ● Drastically reduce admin/management costs – One software installation to maintain ● Use differentiated QoS
  • 32. Achieving Tenant Isolation ● Each tenant is given a Security Domain ● Each domain is isolated and do not have access to other domains – Data isolation – Logic Isolation
  • 33. Example: Multitenant Artifact Deployment & Dispatching
  • 34. Public / Private Cloud Bridging - CSG
  • 35. Public / Private Cloud Bridging - VPC http://aws.amazon.com/vpc/
  • 36. Why use a PaaS in a… ● Public Cloud – Fast time to market – Makes it easier to write scalable code ● Private Cloud – Give each team their own instant infrastructure – Govern centrally but code and deploy by team – Automated governance, registry, identity – Instant BAM ● SaaS market – Build multi-tenant apps faster
  • 37. Summary ● WSO2 private cloud solution gives you: – An enterprise grade PaaS ● On Amazon or in your Datacenter – Deploy existing webapps, create new composite apps ● Use what you need – Completely multi-tenanted and elastically scaling ● Cloud Native – Tooling for development & management ● Highly effective and productive ● Built on battle-hardened, proven middleware – In production at eBay, Deutsche Bank, Prudential, Kaiser Permanente and others ● Only vendor with a comprehensive PaaS offering with zero lock-in