Build Platform as a Service (PaaS) with SUSE Studio, WSO2 Middleware, and EC2 Chris Haddad

Transcription

1 Build Platform as a Service (PaaS) with SUSE Studio, WSO2 Middleware, and EC2 Chris Haddad VP, Platform Evangelism WSO2 [email protected]

2 Section Break Text Here (32pt)

3 Cloudy Goals Improve efficiency and productivity Lower capex Improve utilization Build New Style systems Gain Cloud-native advantage Create Cloud-aware applications 3

4 4 Cloud-Native Platform Characteristics

5 Why do you Cloud? Obtain the right tool bits Access a pre-built platform Rely on embedded compliance, governance, and security policies Creative experimentation Spin up and down on demand Lower startup cost Meet business demand Fulfill dynamic and spiky usage requirements Optimize spend 5

6 Why do you PaaS? Ready to DevOps Hug a virtual server (or container) Configure a run-time environment Provision software development lifecycle repos and tools Build better software and accelerate software delivery Offer a pre-built platform to development teams No QoS worries 6

7 Section Break Text Here (32pt)

8 Technical Objectives Improve efficiency and productivity Use Amazon EC2 or private Cloud Create small, scale-out containers Adopt DevOps practices Build New Style Systems Tap into shared middleware services Incorporate anti-fragile, circuit breaker design patterns Realize multi-tenancy and service-oriented solution design 8

9 Architecture SUSE Studio WSO2 Application Server Asset Repository User Store Amazon EC2 9

10 DevOps Steps Build container image with platform services Deploy the image into the Cloud Configure user store, security, and asset delivery Provision applications, services, and APIs Monitor and manage runtime environment 10

11 Step 1a: Choose Container Services * 11

12 Step 1b: Build the AMI Build the Image with SUSE Studio Start Software Configuration Files Build 12

13 Step 2: Deploy the Image into the Cloud Deploy Image on EC2 Choose AMI size Ports Security key pairs Considerations Clustering System Dependencies 13

14 Build and Deploy Best Practices Automate build Pull resources from online repositories Define configuration as parameters Dynamically connect (and re-connect) Decouple location Inject circuit breakers 14

15 Step 3a: Configure User Store and Security Where is the user store? Internal user store External user store Access control Role Permissions 15

16 Step 3b: Configure Asset Delivery Deployment Synchronization Automatic hot-update to cluster Reconcile with version control Link to continuous delivery processes 16

17 Step 4a: Migrate Applications WSO2 Application Server Web Profile Support 17

18 18 Step 4b: Migrate Everything

19 Step 5: Monitor and Manage Run-time Environment Monitor Log file collection Run-time usage and performance statistics Manage Cloud node restart Resiliency 19

20 Bonus Step: Create a SaaS Application Multi-tenancy Considerations Tenant density model User Store Roles and Permissions Session cache Queues 20

21 21 Bonus Step: Implement a Full PaaS

22 22 DevOps PaaS: AppFactory

23 WSO2 Advantage API-Centric, Cloud-Native, DevOps Friendly, Enterprise-Ready Open Source 23

24 Build Cloud-native solutions with SUSE and Cloud-aware applications with WSO2 wso2.com Cloud Thank you. 24

25 Corporate Headquarters Maxfeldstrasse Nuremberg Germany (Worldwide) Join us on: 25

26 Unpublished Work of SUSE. All Rights Reserved. This work is an unpublished work and contains confidential, proprietary, and trade secret information of SUSE. Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated, abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE. Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability. General Disclaimer This document is not to be construed as a promise by any participating company to develop, deliver, or market a product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The development, release, and timing of features or functionality described for SUSE products remains at the sole discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All third-party trademarks are the property of their respective owners.