Insert Custom Session QR if Desired.

z/OS Cloud Services Overview Frank J. De Gilio – Chief Cloud guy Hilon Potter – The Silver Lining August 2014

2

Platform as a Service 41% CAGR1 through 2016 $4.8 Billion 24% of Cloud Revenue

Software as a Service

29% CAGR1 through 2016 $5 Billion 25% of Cloud Revenue

1Compound Annual Growth Rate

Perspective

3

per·spec·tive pəәrˈspektiv Noun 1. a particular attitude toward or way of regarding something; a point of view. "most guidebook history is written from the editor's perspective" synonyms: outlook, view, viewpoint, point of view, POV, standpoint, position, stand, stance, angle, slant, attitude, frame of mind, frame of reference, approach, way of looking, interpretation "his perspective on things had changed"

PaaS – Platform as a Service SaaS – Software as a Service

The Requirements

4

True Multi-Tennant Environment

Granular Usage Monitoring

Differentiated User Experience

Few Admins Large Community

This is easy, lots of virtual servers in a cloud environment,

with automation

The Solution?

The Requirements

5

True Multi-Tennant Environment

Granular Usage Monitoring

Differentiated User Experience

Few Admins Large Community

This is easy, it’s MVS, multiple workloads securely separated,

with a single OS Stack to manage

The Solution!

z/OS Providing Higher Level Cloud Services

6

z/OS

Service!

Service!

Service!

Service!

Service!

Service!

Linux on z Server Server Server Server

Infrastructure as a Service

Platform as a Service

Software as a Service

The Model

7

z/OS Service

Service

Service

Service

Service

Service

Linux on z

Server Server Server Server

Linux on x86

Server Server Server

Power AIX & Linux Server Server Server

REST

What if?

8

z/OS

z/OS

z/OS

CF

Nodes in a

Cloud REST

JSON

We Leverage z/OS capability as a Higher Level Cloud Service Provider? •  Software as a Service becomes a multiplatform solution •  Virtual Appliance Container

Sys

plex

Dis

tribu

tor

•  Elastic Scalability –  Create more servers with complete stacks | –  Create a new service instance with a single stack

•  Usage Monitoring – Monitor usage by gather information from multiple hypervisors | – Monitor usage on a single Plex

•  Provisioning – Provision a full stack (OS, Middleware, Application) | – Provision a new instance of a service on an existing stack

A Cloud Service? How do I cover?

9

Use Case: Caching – An example

10

Requirements: •  Provide a remote, sharable, secure, cache for data to be accessed by 1-n services running in the network

•  Meet performance requirements at as low a cost as possible

z/OS

1. Cache service is requested by an application (a)

2. Application (a) uses the cache to store transient data

3. Application (a’) accesses transient data

4. Application (b) accesses transient data created by Application (a)

5. Application (a’’) accesses transient data

6. Application (b’) accesses transient data data created by Application (a)

zCache – Active/Single

LPAR Region

Shared Port

Region

Region Region

LPAR Region

Shared Port

Region

Region Region

LPAR Region

Shared Port

Region

Region Region

Data Store

CF

End Point URL WLM Managed Sysplex Distribution

Site 1

Performance – Sustained 1,000 TPS with 1ms reads and 4ms writes Failover – Depending on the hosting environment, a backup site may be available for the environment to be restarted in after a disaster, typically with a 4-hour RTO Load balancing – Performed via Workload Manager and Sysplex Distributor across the sysplex

(Host)/resources/datacaches/BU_SBU/AppName/key

11

zCache – Active/Active

LPAR Region

Shared Port

Region

Region Region

LPAR Region

Shared Port

Region

Region Region

LPAR Region

Shared Port

Region

Region Region

LPAR Region

Shared Port

Region

Region Region

LPAR Region

Shared Port

Region

Region Region

LPAR Region

Shared Port

Region

Region Region

Data Store

CF

Data Store

CF

End Point URL End Point URL WLM Managed Sysplex Distribution WLM Managed Sysplex Distribution

Site 1 Site 2

Synch Replication

Performance – Sustained 1,000 TPS with 1ms reads and 4ms writes Failover – Each site provides 2 client ports (SSL, non-SSL). If a site becomes unavailable (ports close), all work is serviced from the alternate site. When the site becomes available again, the data from the active site is resynched to the previously down site, then the ports are reopened and distribution of work resumes Load balancing – Performed across sites in a round-robin fashion by NLB, and within a site via Workload Manager and Sysplex Distributor across the sysplex

(Host)/resources/datacaches/BU_SBU/AppName/key

Active Active

12

An interesting thing happened on the way to the market!

13

• The Cache offering was created and made available by a large retailer

• Marketed and pushed to a single developer • Resource utilization after a month went way beyond what was

projected • Why? Was there a problem? Was it working?

New problem, How do you identify different users?

/Division/Org/Department/Application/Instance/Cache

An interesting thing happened on the way to the market!

14

SMF Manager

–Easy Fix -The URI Matters!

• The Cache offering was created and made available by a large retailer

• Marketed and pushed to a single developer • Resource utilization after a month went way beyond what was

projected • Why? Was there a problem? Was it working?

• “Multiple” developers, learned by word of mouth and, were using it

It was a success and the word spread thru

the underground

Is it worth it?

15

zCache performance on WMD3 (z196): 31MAY2013 22:02:18 ------ MAINVIEW WINDOW INTERFACE (V6.0.00) ---------------- COMMAND ===> SCROLL ===> CSR CURR WIN ===> 1 ALT WIN ===> >W1 =CHIST============(ALL======TESWCAA=)31MAY2013==22:02:03====MVCICS===D==128 Task CICS Lcl Task Lcl Task Tran Response CPU Storage I/O Term Num System End Date End Time ID Time Time HWM Calls ID 66790 TESWCAA 31MAY2013 21:59:41 ZC00 0.00099 0.00070 112032 2 66792 TESWCAA 31MAY2013 21:59:41 ZC00 0.00066 0.00052 112032 2 66794 TESWCAA 31MAY2013 21:59:41 ZC00 0.00097 0.00071 112032 2 66796 TESWCAA 31MAY2013 21:59:41 ZC00 0.00082 0.00063 112032 2 66798 TESWCAA 31MAY2013 21:59:41 ZC00 0.00081 0.00059 112032 2

zCache performance on WMD3 (zEC12): 04JUN2013 13:06:32 ------ MAINVIEW WINDOW INTERFACE (V6.0.00) ---------------- COMMAND ===> SCROLL ===> CSR CURR WIN ===> 1 ALT WIN ===> >W1 =CHIST============(ALL======TESWMAC=)04JUN2013==13:06:21====MVCICS===D===96 Task CICS Lcl Task Lcl Task Tran Response CPU Storage I/O Term Num System End Date End Time ID Time Time HWM Calls ID 82132 TESWMAC 04JUN2013 13:05:34 ZC00 0.00048 0.00032 114448 2 82134 TESWMAC 04JUN2013 13:05:34 ZC00 0.00073 0.00035 114448 2 82136 TESWMAC 04JUN2013 13:05:34 ZC00 0.00042 0.00030 114448 2 82138 TESWMAC 04JUN2013 13:05:34 ZC00 0.00057 0.00034 114448 2

Average Response time (196): 8.5 MS Average CPU time (196): 6.34 MS

Average Response time (EC12): 5.28 MS Average CPU time (EC12): 3.24 MS

Potential Use Case: Serialized Incremented Integers

16

1

2

3“CS R1,R2,D1” vs. lots of code and multiple servers

•  The IBM Advanced Crypto Service Provider REST API is a cryptography service available for on- and off-platform use for z/OS Cloud Services (zCS). It provides access to z/OS cryptographic function using an HTTP Web service. This exposes ACSP services for use to distributed clients.

•  This service centralizes the definition, use, and maintenance of cryptographic keys, simplifying key management. It allows the use of secure and protected keys to avoid the exposure of sensitive key information outside of the trusted, hardened and tamper evident cryptographic co-processor. ACSP-REST also permits access control and logging on key service usage in addition to service charge-back to applications based on actual usage.

•  Any authorized RESTful application with the appropriate credentials may utilize the service. Such an application would send a HTTP request over SSL/TLS to the URL of an ACSP-REST service along with a JSON (or XML) payload formatted to match the provided schema. The client application would receive a JSON (or XML) payload containing the encrypted text as the response.

USE Case: Crypto -IBM Advanced Crypto Service Provider REST API1

17

1Lab Services Offering

The Infrastructure for ACSP (from one perspective)

18

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF

RA

CF

Liberty U

RI

Application

Catalog

“cloud” UI

A z/OS system with z/OSMF, RACF, a cloud infrastructure that uses a catalog based process i.e. Smartcloud Control Desk

System z “cloud”

Infrastructure

CR

YP

TO

Provisioned Guest

Step 1: Publish Service to Jazz SM Server

19

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF

Publish service to Jazz SM • Describe service • Define location • Define URI used to call the service Service and Workflow

is setup in z/OSMF

RA

CF

CR

YP

TO

Step 2: Build Catalog from Repository

20

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF Service and Workflow is setup in z/OSMF

Catalog

“cloud” UI

RA

CF The Provider repository on

the JazzSM can be read by any OSLC compliant product to build a catalog entry.

CR

YP

TO

Step 3: Application Programmer Asks the Factory for an Instance

21

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF Service and Workflow is setup in z/OSMF

“cloud” UI

RA

CF

Liberty

UR

I

CR

YP

TO

Step 4: z/OSMF Provisions the Service

22

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF

Service and Workflow is setup in z/OSMF

“cloud” UI

RA

CF

Liberty U

RI

Application

Provision the Service -Execute the Workflow to create an instance of the service • Connect to RACF and create the id credentials • Setup the service in either an existing Liberty server or create a new instance of a Liberty

server • Pass back the URI for the service and the credential to the application programmer

CR

YP

TO

Provisioned Guest

Step 5: The Application uses the Service

23

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF

RA

CF

Liberty U

RI

Application

• The application programmer writes code that calls the provisioned service via the URI.

•  It will use RACF to associate an identity with the service call. • This identity will be tied to usage information and possibly performance.

CR

YP

TO

Provisioned Guest

Step 6: Gather Information on the Service

24

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF

RA

CF

Liberty U

RI

Application

Catalog

“cloud” UI

OSLC Compliant tooling will use the provider information in JazzSM to gather information about the Factory and the instances created by the factory. It will do this with the help of z/OSMF and other z/OS subsystem capabilities.

CR

YP

TO

Provisioned Guest

The Infrastructure for ACSP (from the right perspective)

25

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF

RA

CF

Liberty U

RI

Application

Catalog

“cloud” UI

The infrastructure is actually multiple systems working together to provide the business services required, managed

as a cloud.

System z

“cloud” Infrastructure

CR

YP

TO

Provisioned Guest

Provisioned Service

Consuming z/OS Cloud Service with BlueMix -Demo

26

SoftLayer

BlueMix

Cloud Foundry

PaaS

BlueMix •  RESTful services allow distributed programmers to use z/OS capability without

understanding implementation details •  BlueMix streamlines the use of RESTful Services •  The vision is to give CIOs control over services that Lines of Business will use

z/OS

Linux on z Jazz SM

Liberty

UR

I

z/OSMF

RA

CF

Liberty

UR

I

CR

YP

TO

Infrastructure Services •  Certificate Management •  Cloud wide Lock •  MQ as a Service

Business Services •  Credit Card Processing •  Inventory Control •  Account Management

Other ideas?

27

28

For additional details or questions please contact degilio@us.ibm.com