Nrb Mainframe Day - Ibm z A Key Player In The Hybrid Cloud Journey - Bob Catteew

Editor's Notes

• #4: Over the past decade, cloud has become integral to nearly every digital, and business transformation strategy, allowing enterprises access the latest technologies like IoT, high performance computing, and blockchain from virtually any vendor to reimagine business processes and ecosystems. Its allowed enterprises to tap into more sources of data, both their own as well as partner, social, weather, and other data sources, plus new ways to analyze it. New algorithms, machine learning and AI are driving new insights that enable more engaging, personalized client experiences, all while extending the value of existing investments. Yet even with this ability to source more innovation and data from more from more places, only 20% of enterprise workloads have moved to date. The question is why? -------- Source: McKinsey: https://www.mckinsey.com/industries/high-tech/our-insights/it-as-a-service-from-build-to-consume
• #5: Today we are in a transition to a new chapter for the IT industry. I'll refer to as Chapter 2 Chapter 1 was consumer led, driven by end used apps of smartphones and tablets Chapter 2 is about enterprises innovating, for example not just Fintechs but large incumbents Second change is AI and digital, businesses are now building AI into their business workflow Third change is cloud. Chapter 1 was about user apps, 20% of all workloads, Chapter 2 is mission critical, the tough 80% Chapter 1 was focused on public cloud, chapter 2 is more holistic, bringing mission critical apps into the realm of cloud what is going to really matter is the ability to INTEGRATE both the TRADITIONAL systems with the NEW systems Today we are in a transition to a new chapter for the IT industry. I'll refer to as Chapter 2. So what are these differences?  Chapter 1: much of the innovation in IT has been driven by consumer technology - by things that you interact with on your smartphone and with a lot of applications that are end user oriented.  in Chapter 2 we’re now seeing enterprises actually innovating - the big enterprises. For example – in Financial Services – it is not just the Fintechs that are innovating – the large incumbents have come back. So from consumer driven to enterprise driven is one big shift.  The second change is around AI and digital. In Chapter 1 there has been a lot of experimentation and proof of concepts that clients have been going through.  In Chapter 2 - we're moving into a stage where businesses are moving from EXPERIMENTING to actually building AI into their business workflow. The third change is around Cloud – in Chapter 1 the focus of cloud has been around what I would call user applications - things that you can use your smartphone for – e.g. checking your bank balance on your bank account and things like that. But these workloads make up at most only 20% of all workloads … the easy part… 80% of the workload movement is ahead .. the hard part – i.e. the mission critical workloads that clients run their businesses on. These are very data-rich … enterprise data … transaction processing workloads that now will either be moved to the cloud or need to connect to the cloud. And that's where the action in Chapter 2 is going to be.   Related to that - Chapter 1 has been a lot about PUBLIC cloud. Chapter 2 is more holistic – it is about pulling together the mission critical/core enterprise apps and bringing them into the realm of cloud – either moving to private or public cloud … or at interoperating with cloud. That's what HYBRID cloud is about.  And that's what the Red Hat acquisition is about. Finally – in chapter 2 what is going to really matter is the ability to INTEGRATE both the TRADITIONAL systems with the NEW systems. The player that has the ability to bring together an end to end integrated value proposition will win in Chapter 2. We are unique AT that … chapter 2 plays to our strengths.  That is our heritage – one that we will build on in our future.
• #6: Many clients just beginning to evolve and transform their workloads. They are still heavily invested in traditional on-premises IT while starting to explore growing or shifting workloads to the public and private cloud. Over time, there will be a significant growth of workload on the public cloud while traditional on-prem workloads will decrease as companies look to cloud solutions to provide agility and new value to their businesses. However, The on-prem data center is not going away. There will at the same time be an increasing and growing workload on-prem for enterprise clients in the form of the Private cloud. Regulations, compliance, security, sensitive data, and core workloads are not going away, but they will need to evolve to ensure that the same levels of agility can be achieved while protecting the core of the business. Private cloud is the path to this secure and trusted modernization strategy. This evolving hybrid ecosystem which provides every business the choice on how and where they leverage IT will drive new levels of innovation and value across all corners of the market.
• #7: Five key principles define IBM’s approach and separate it from other vendor approaches. Hybrid - enable enterprises across Public, Private, and traditional environments Multicloud - Manage other vendors’ Clouds, acknowledging the reality that client environments are heterogeneous Open - Build capabilities that are open by design, enabling client flexibility and reducing vendor “lock in” Secure - Provide reliability and continuous security for the client’s environment
• #8: In many peoples minds IBM Z and Cloud don’t go together.
• #9: IBM Z strengths: Availability Control Privacy & security Reliability Cloud strengths: agility accessibility scalability pay structure & costs collaboration
• #10: You can “combine” the best of both worlds with IBM Z
• #11: - And we are seeing this shift playing out with our clients - One of the major analyst firms surveyed NA mainframe clients and 82% of them stated they will either hold or grow their usage of IBM Z. - Option 1: keep the status quo, meaning: Keep the mainframe separate, using old tools and old ways of working. Don’t rock the boat...“if it ain't broke don't fix it” - Option 2: rewrite all your applications using modern technologies on distributed systems. This is a very expensive option, and very RISKY for your mission critical applications. By the time you are done rewriting your applications, you would already be behind your competition in the digital marketplace. This will result in lost marketshare and lost revenue. Another major analyst firm did a nice job recently laying out a set of recommendations to follow before you embark on this...things like remove emotion, document real gaps in technology (versus perceived ones), and real total cost analysis. - Option 3: leverage your mainframe assets to accelerate your digital transformation. It is critical to open the enterprise assets in IBM Z to be connected to the modern applications. Have clients already reaping value from Option 3. - Easy to fund … - Break even in 10 months - Return 3x savings to the business - Positive impacts on top line growth 47 % Platform continues to shine once solutions are deployed with the about half the costs of operations when compared to distributed with developers showing productivity improvements of 15%
• #12: How does IBM Z make true hybrid Cloud Integration integration a reality for clients? True integration happens with focus, innovation, and trust. These four areas describe where the platform is driving solutions and alignment, and all of them are built on the laurels and solid foundation of IBM Z. Modernization for Cloud is about transformation, reimagining, and modernization of the infrastructure, applications, and data. This may take the form of APIs built from trusted and proven core applications, it is also could take the form of automation and intelligence for operations. The next focus area is all about delivering a cloud native experience across the HW and SW stack. This means providing access and use of IBM Z by developers, administrators and architects with no special skills required. No specials skills means the tooling, languages, and standards expected and widely used in the distributed world are the same for IBM Z. We will focus more on private cloud today as we dive into how clients can tie z/OS into their cloud ecosystem all managed from behind the firewall for optimal security and trust. And the final focus area is public cloud. Here we already provide services in the IBM Cloud today that are running on IBM Z in the form of our HyperProtect services. No matter where our clients are, where they are going, or how they want to operate… IBM Z is integrated with and strengthening their Cloud foundation for mission critical workloads
• #13: Cloud is the linchpin of our clients' digital transformation, it is the default choice for new workload  According to IDC, by 2022, the acceleration of legacy app modernization and net-new development will lead to 35% of production apps being cloud native - utilizing microservices, containers and dynamic orchestration. So how do we get there?    By continuing to deliver capabilities on IBM Z across these four dimensions. Modernization for Cloud- this is all about how you plug the platform into the broader enterprise architecture in a standard way.  We can do this today w/ APIs for apps and data with z/OS Connect, we can do this today for application performance management w/ Z APM Connect, and we can do this today for operations analytics with Z Service Automation Suite. Cloud native experience - this is about opening IBM Z for access and use by new developers without requiring specialized skills.  We are changing the experience of working w/ the platform w/ Zowe, we've enabled our clients to use the same devops toolchain w/ IBM Z Open Development, and we will enable the deployment of Linux on Z docker images on z/OS, inheriting the management, security and resiliency strengths of z/OS.  Private cloud - this is where we help our clients deliver the value of cloud...speed and agility...with IBM Z.   We support IBM Cloud Private on Linux on Z and LinuxONE, which provides the platform for modernizing, developing and managing on-premises, containerized applications.  We've extended this capability to support non-containerized z/OS workloads, with the z/OS Cloud Broker, and we've made available Blockchain for ICP and Hyper Protect virtual servers, for private cloud. Public Cloud - and we continue to strengthen IBM Cloud offerings w/ IBM Z differentiation in the area of security.  Blockchain was first...and now we have the Hyper Protect family, which are a new set of highly secure cloud native services to help developers create new, born on the cloud applications of the highest security. This is how we are enabling our clients journey to cloud and this is where we continue to invest to meet our clients evolving needs, building on the strength and differentiation of the platform...which Tarun will talk more about.
• #14: In the hybrid cloud world, applications tend to be containerized in order to deliver flexibility and choice of deployment independent of underlying platform Besides the application code , the container has also all the necessary functions and features to run in any environment. To simplify , IBM has provide a suite of containerized software solutions called cloud paks. They provide an easier, faster and more secure way to move applications to any cloud including on-prem Private cloud. They are based on a container platform layer that is Kubernetes-based and portable. Kubernetes is the management environment for the containers. Cloud Paks are coming on Red Hat openshift as the platform As you can see there are 5 cloud paks currently available: Applications, Data, Integration, Automation and multicloud management. As of Q1 2020, RH Openshift is equally available and supported on z Linux and therefore also the cloud paks. This delivers high value in using the z platform in the hybrid cloud environment.
• #15: Now how do enterprises select which workload will be running in which environment. This exercise is key in order to plan for the digital transformation. You will see that some applications better reside on prem for a nr of reasons you can see here. On Private the most obvious selection application with the need of flexibility but clearly a higher level of security needed. Also regulation can be a driver to select private cloud. Finally the less critical applications and front-end services might be better placed in the Public cloud environment.
• #16: IBM makes it easier to move more to the cloud today, without compromising visibility or control. We have a proven approach built on deep industry, security and cloud expertise and we apply it to your unique business. In fact, we’ve helped thousands of clients realize a faster, more secure, and cost effective journey to cloud. This approach is enriched by unique technology, expertise, and tools across the cloud advisory, migration, build, and management phases with tools and support such as: Multivendor, multicloud architectures Automated tools that can assess your existing applications and workloads and determine what to migrate, modernize, and where to best run it Methods to transform skills, culture, and processes Service management and brokerage to procure and manage multivendor environments End-to-end governance, security, compliance expertise to reduce unnecessary risks All of this is delivered through IBM Garage Method, an end-to-end services methodology that defines a reliable, repeatable, secure path for our clients to embark and succeed on their cloud journeys. Based on comprehensive capabilities including analytics and cognitive market leadership, this methodology allows clients to perform structured assessments and cloud affinity analyses. This better enables businesses to migrate, modernize, and build applications for the optimal destination cloud—public, private, and hybrid—and then to manage them efficiently. Source: IBM Global Business Services
• #17: Thank you all for taking the time to be with us today We hope you enjoy the rest of the conference