Charts, recording and Q&A will be posted here. 
As part of Cloud Pak Week, we will have deep dives on specific Cloud Paks and this session 
is to cover the strategic overview of Cloud Paks. 

Q&As: 

Question: The Kubernetes distribution on Cloud Paks - Is it completely managed service offering by IBM ? Will IBM take care of patches, packs etc - I know IKS - IBM does complete managed services, however for Cloud Paks ?

Answer: IBM manages the OpenShift layer, including patches, upgrades etc. The Cloud Paks are deployed and managed by the customer, so in that respect, this is not a managed Cloud Pak offering.

Question: OpenShift comes up with its own Middleware stack (Fuse, 3Scale, Jboss), what is our strategy to propose Cloud Pak over already available Openshift stack out of the box?

Answer: IBM Cloud has the Red Hat OpenShift Kubernetes Service, which is a full OpenShift managed service. You can run Cloud Paks on that. Other cloud vendors have similar OpenShift managed services. Or you can run OpenShift on your own, it doesn't have to be a managed service.

Question: We are running CPS, does it run on s Multirack environment? And with a Multicloud environment profile?

Answer:  <Working on a final answer>

Question: What of the 6 are available on LoZ?

Answer:  At this point, only CP4Apps is available on z. Other Cloud Paks are expected to follow over the course of this year, concrete dates differ per Pak and have not yet been publicly announced.

Question: One of the benefits of Cloud Paks over Containers alone is License Metering integration, can you elaborate on that metering mechanism a bit?  Does it replace ILMT, is it automated in the platform, does it report back to IBM deirectly or does the customer still have to supply reports, etc.?

Answer: The Licensing Service comes as part of the Common Services with every Cloud Pak. It integrates with an associated Metering service in support of measuring the usage of Cloud Paks and producing related reports. In this respect, this service can be seen as an evolution of ILMT, with the added ability of handling container-based workloads (which ILMT cannot). The related reports are not uploaded to IBM.

Question: Cloud Pak story has to be told end to end - starting from App to Integration to Data to Automation etc. Now I can’t tell this story end to end because the license model (VPC) is purely for individual Cloud Paks . If I buy 200 VPC of Cloud Paks for Data, I can buy only Cloud Pak for Data components and not any other Cloud Pak components. This licensing model has to change. This licensing model has to change - This is purely my opinion. Customer should be able to choose whatever he wants from any of the 6 Cloud Paks as bottom line architecture is the same.

Answer: Technically, customers can choose from capabilities across Cloud Paks and mix and match as they see fit. They only pay for the capacity that they want to utilize. At this time, I am not aware of a plan to have a single license across all Cloud Paks.

Question: Is there a difference in the code base between the Cloud Pak licenses vs the traditional licenses? Assuming a customer already has OpenShift - what would be the motivation to acquire a Cloud Pak vs the traditional buy (which is typically far less costly)?

Answer: The OpenShift license included is in support of the software within the Cloud Pak. It is not meant as an alternative way of acquiring OpenShift.