 Welcome, thanks for joining the session. I'm Arnie Arnold. I'm at Red Hat in the RELBU, the Product Manager for our Mission Critical Workload. So that includes SAP, a few or more, which we actually care about and has pointed as a strategic workload. And so today's session will be about S4 HANA migrations. And so I mean, it's the topic in the space of SAP. And so maybe to just act, to just check the audience a little bit, who of you is actually running SAP? Wonderful. How much of you are in the migration to S4 HANA? OK. Anyone already completed with migration? Wonderful. Great mix. So I probably don't have to go into too much detail, actually, what it is involved. I also assume that you know about who SAP actually is. I'll catch to a new fact sheet. So it's actually quite impressive also in terms of numbers, total revenue just in 2021, even bumped up further to almost $28 billion of, I think it's years of revenue more than 100,000 employees. So definitely a big leader in the business of enterprise application and a partner of Red Hat since more than 20 years, 23, I think it's now, 24. It was 1999 when SAP was bringing R3 to Linux and since then the partnership between Red Hat and SAP exists as it was back then, also porting to Red Hat Linux. So I mean, over time, SAP Fervor evolved into the company which is now with an entire suite of products which they offer. Also Red Hat has Fervor evolved into leader in open source technology, not just the operating system, but also our technologies, hypervisor, automation, integration all the way now to containers with OpenShift and that is also visible in that timeline where actually the topics between the two companies had been further evolved by constantly working together making sure that products are certified on the corresponding platforms and also the collaboration in the engineering's happening. For example, working with SAP Data Hub or SAP Data Intelligence team to actually bring that on top of OpenShift. So it's just a little bit of a history between the two companies and why we have also SAP here at the event. You may have seen the booth. You may have actually stopped by, had a few conversations. And what I would actually like to talk now a little bit more is actually how we actually can help in the migration to S4HANA. And so I mean, anyone can modernize SAP, but in the end, we talk about mission critical. So it is about our scalability, about speed, but also about doing it right. And so it is about best practices. And I mean, Red Hat is a leader in open source technologies and infrastructure, but we may not necessarily have the answers to all those questions. So if you are on a project to migrate to S4HANA and you ask yourself, OK, do I actually keep the data into the new system? Or should I actually clean the data before? Should I do it in a hybrid world, in an on-prem world? Should I do it in the cloud? Should I use SAP Rise? So there are many questions which you need to get an answer to. And so while I personally have an SAP background and had worked 10 years there, it's still tough for me to get the answers everywhere. So what do we do at Red Hat? We are built around the idea of open source, open source communities. So we actually work together with partners. And so we do also in the SAP space. So we actually have built up a bigger network of partners who actually have the expertise in the corresponding steps of S4HANA migration and work together with them and you to actually bring you through that journey. And so this is just an illustration of the different phases which you may have gone through, those who already finished S4HANA migration, or at least still are looking into if it's still in front of us. And so everything starts with analysis. I just mentioned a few aspects. If you are now on the existing system and you want to move to S4HANA, it's not just an upgrade which you apply to the system. But actually you will need to understand how customized is your system today, whatever things which are in the target S4 stack which actually map to that of what quality is my data, or what data do I need to archive, what data do I need to transform. So a lot of things will actually happen here. And both will be the input to the next step, which is then the actually integration and pre-project. We then have to map out how the new system landscape looks like and how you actually want to build that up. We had a few words earlier, Brownfield, Queenfield, which goes into there. And then ultimately you want to go into the execution, actually a role of that system, which you may still do on-prem or which you may want to do in the cloud. You may leverage SAS offerings as S4HANA public cloud by SAP, combined with existing assets of systems which you don't migrate at the same step, all the way into the innovation pillar where you then want to rebuild the end-to-end business process by enhancing the stack, the custom code, the third-party applications. So that does not necessarily mean that it looks like how your old system had been, as I said earlier. There may be things which are now in the standard. There may be other things which are no longer in the standard. So those are things which you want to go through. And as I said, for all those pillars, there are experts which work with SAP closely to actually provide the corresponding tools and best practices. So in the analyst phase, we are having some partners like Bestrex where we also had some customer stories public on reddit.com who help in the analysis. We have the interpretation and the execution step where we work with partners like Devo Team together who help us to actually automate that part of the chain and the configuration and the systems all the way into the innovation space where we again work together with partners who can help to then build those container-based extensions to actually enhance the business functionality of what SAP has. That said, it should already make clear that it's actually not just about Reddit Enterprise-Dinox as a basis of your S-400 system. But actually, when you go through an S-400 migration, you touch all those different technologies. You have to think about where does my HANA database run on? Yes, but it needs to be a Linux operating system. And so that brings many customers from different platforms first time to Reddit Enterprise-Dinox. But it also means that you have to think about where does my application development happen? Is that on the SAP Business Technology Platform? Is that somewhere outside of it? Is it a combination of it all the way to how does my deployment look like? I already said you may consume certain parts from SAP software as a service, but you may still run other parts of your SAP applications a little bit longer because you will not shift overnight if you have a more complex environment. Or you may also depend on third-party application or legacy application which actually generates the data which SAP is operating on. I will touch on that in one of the customer scenarios later on. And so it's a combination of all those different technologies which we on the Reddit side have in the portfolio to support you on the S-400 migration. What I wanted to do for a talk today because I mean we are here at the Reddit event, which is that we somehow need to bridge a little bit the both faults we have on one side, we have SAP experts on the other side, we have a technology expert on the Reddit side. So let's start a little bit with the use cases. And then we can dive in a little bit into the technologies which we use. And if there are questions left and we can have those at the end of the session or you can stop me after the session to actually get further answers to that. So picking three examples. One is WWSAT which is more closer to the first aspect which I showed, the Enterprise Linux under the S4 stack than expanding into another customer which we also saw this morning in the keynote which is Spanish customer at Sepsar. And then rounding out with Tokyo Electron which shows a little bit how you can use technologies like integration and OpenShift to actually enhance your SAP environment on the way to S4HANA. Good. What was the challenge which WWSAT had? Or maybe starting with who WWSAT is, it's a customer in Europe more precise in Switzerland. They are providing energy or internet water services to other residents in the Canton Souk. And they had been challenged by their competition to actually improve the speed and the quality of their services which they provide to their customers. So we all know that from our private lives that we are now used to have those mobile apps to see our consumption on energy and all that stuff. So that is where we're looking into to actually get the necessary performance by migrating to the S4HANA environment as a basis for their end user services. But their challenge had been that their former SAP system was not based on Linux but that they actually run that on a different operating system. And so they had been part of that group who actually first time needed to get the HANA system to Linux. And they have looked into the options that they have and decided to pick Reddit Enterprise Linux because it had the necessary best practices and tailoring for the SAP workload built in. So Reddit Enterprise Linux, I guess, is known in that audience. It has Enterprise in its name. So it's coming with a lot of tooling and certification to meet the needs of an enterprise workload at scale. But yet, if we talk about business critical workloads like an SAP, again, then you have additional requirements that you raise to that system which usually are around, OK, I further want to reduce risk by really having a stable and trusted environment across my landscape. I also want to ensure that I have extensibility in that system because if I build up an SAP system at the last form, maybe a decade, you also need to have the supportability throughout the stack. And that means that you are not just looking for the next six months which we have in the C-stream, but that you really want to ensure that once you have built up a system and certified it end to end, that you can maintain that version of the stack a little bit longer. And ultimately, if we talk about it in-memory database like HANA, then, of course, also performance is a bigger topic. So those are more or less the additional asks which we had been receiving from customers running SAP on top of Reddit Enterprise Linux, which we then built the corresponding SAP offering around providing exactly those capabilities like high-vibrility, live kernel patching, the extended support, and now also added insights. And so this was the convincing part for WWSET to actually say, OK, yes, we want to go to S-400 with Reddit Enterprise Linux as a basis. And so they did that migration. And actually, they gained out of it this improved efficiency because they leveraged the automation capabilities which we have in the product with the rail system roles, easily being able to roll out the operating system and also the SAP components. They also valued a lot the reduced risk from a security aspect, building on top of the certifications and public validations we have and the tooling insights role. And last but not least, also by leveraging automation, they also reduced the human error in the process which we had not before. And so overall, the customer was actually able to migrate to S-400 successful with the Reddit Enterprise for SAP solutions. The other example which I picked is Cepcer, which is an oil and gas company in Spain. They have been a Reddit customer before they migrated to S-400, leveraging Ansible a lot to automate their processes. Actually, not necessarily the Reddit Ansible, but also using the open-source AWX version. And so they already had built that habit of doing things in an automated way. But at the moment, we're actually way looked into the migration to S-400. They realized that this is actually a bigger project. They wanted to do it automated, but they didn't felt comfortable in actually doing that alone. So they reached back to us and to our professional service organization to actually help them on implementing Ansible as part of their S-400 migration. And so the key value which they actually get out of that was the Ansible platform subscription and the Reddit automation hub, because that provided them with a platform where they can build the corresponding artifacts for that S-4 migration. So I don't know as to how far Ansible, the Reddit automation hub, the Ansible platform subscription is known here. But basically, it provides you with a single entry point where you can build on existing Reddit certified content. So you can go into a Google-like search. You can look up for existing building blocks which are part of your stack. So if you want to run SAP on an Azure hypervisor with some third-party fireballing tooling, you can just look for the corresponding vendors. You will get all those certified content packages and you can then build on top so that you can focus on the orchestration workflow instead of rebuilding all those lower-level tooling. The next thing which was very important for that customer is that it comes to this entire workbench of managing development at scale. So I can actually have a team which is using the Reddit automation hub to create content, to check in the content, to do the lifecycle management of the content. And so while actually working in a distributed fashion, the team was able to actually leverage the content which was generated by different teams through the platform. And ultimately, of course, also the topic of trust played a role here because at the moment where you base your automation on Reddit certified content, you have all the benefits in which you are also gaining by other product subscription, meaning that you can actually get back to Reddit open case if you need an extension or if something does not work, but you also rely on the testing which is happening in the QA procedures. So if I actually translate that to what we do in the SAP space, we are, for example, testing our real system roles for SAP in a nightly fashion against SAP workloads. So whenever something changes either on our site or SAP site, we will find that in most testing quite well. And so leveraging Ansible Automation Platform as part of their S4 migration project actually helped them quite a bit. So the result was an increased productivity, but it was also a safe of more than 6,000 man hours in that automation approach which actually resulted in more than 400 IT operations being automated. And so all in all, they were able to actually do their S4 migration with the support of Ansible within a couple of months. And even beyond that, they are now still heavily using their Reddit Automation Hub to automate all their day two operations around the S4 system. So whenever there is a new task coming, they write both corresponding playbooks so that the next time a similar request comes in, we can do that by a click or for button, ideally. Last example which I wanted to highlight here is the example of Tokyo Electron. Tokyo Electron is a company which produces the manufacturing equipment for the semiconductor business. And they had the challenge that they had been historically growing. They had been quite distributed. They had almost different factories with their own systems. And by new financial laws, they actually had to rebuild that landscape and actually integrate all into one system where they also picked SAP and SAP S400 as the system to actually go to. But the challenge here was that on one side we had a quite rigid deadline because this needed to be fulfilled by end of the year. But on the other side, they had a lot of legacy applications in their manufacturing sites which actually produced the data. And so coming back to that slide, which I had at the very beginning, the question for them was really how do I get from the existing ECC system to S4? I think they had roughly about 45% of custom code in their system. And so how much of that code can be just taken over to save some time? How much can be actually done in a more future ready fashion, meaning that you really invest the time on data cleansing and analysis because you know that this system will stay for a longer time? How do I actually manage the dependencies between the S4 system, which will be run in a cloud environment, and the stuff which actually remains on-prem? So that had been all those questions where the customer struggled a lot to actually find the right balance in terms of how much actually take from the existing stack into the new S4 HANA system versus really starting Greenfield and implementing it fresh. And so the technologies which helped the customers here had been a combination out of integration and relative open shift. And it was a kind of two-step approach. So the first step was really to connect the S4 HANA system, which had been built up in the cloud, to all those source systems in the factories and in the satellite offices. And the challenge here had been quite technical nature. I mean, the S4 HANA system is not necessarily supporting all the same APIs as the old systems had. So you had to ensure that we had some protocol transformations happening between both systems. You also needed to ensure that there is an end to end via secure connection. As I said, it's actually a hybrid setup where you have things running on-prem and things running in the cloud. You had to ensure that you do some data cleansing in between. And so the fact that there is actually the SAP Open API Hub, which on the Reddit side, we have certified integration with our Reddit integration solution, helped the customer a lot to spin up that connectivity quite fast and ensure that the customer was able to focus on bringing up the S4 HANA system while not touching those smaller legacy systems in their factories. In the next step, they then looked into what can be actually done to better scale. Because I mean, if you now have a S4 HANA system, which is quite powerful from a technology also scalable in the cloud, you're still depending on those systems which I just mentioned. And so the customers then started in the next step to actually containerize those applications and breaking up this former monolithic environment into smaller containerized applications, which then allowed the customer step by step to actually change their implementations of our source systems, bring it to a level where it was able to scalable by the number of containers, and also being able to actually move them a little bit easier around, so move a few of them also into the cloud, which then is also cost saving in terms of data, which goes between the systems. And it also helped the customer to reach a higher availability of the overall stack. And so if we skip to the next slide, according to the customer, he actually reached 100% system availability in that time frame. They also saw improved developer productivity with the containerized environment, and they simplified their integration of newer applications through the use of Reddit integration, ultimately helping the customer to achieve the project goal, which was a goal life before the end of the year of the S4 HANA system, and hence, serving the need of a business to be on the new financial reporting for the starting fiscal year. There's one more example, which I add here, which is our recent press announcement, which we did together with SAP, so also SAP themselves is meanwhile using more Reddit Enterprise Linux to support their SAP Rise business. So if you are running SAP, then you know that you have options to actually either deploy S4 HANA in your own data center, or to use that, or to consume that as a software, as a service offering. And so if you do that, if you're looking to the cloud edition of S4 HANA, then you will be able to also leverage that in the knowledge that this is now also using more and more of a Reddit technology. And while we are talking here and still have two and a half hours more until the actual evening pub crawl starts, our colleagues in EMEAR who are attending the SAP EMEAR sapphire are already past the point. And unfortunately, the picture is not coming up. That's sad. We wanted to share the LinkedIn post of a colleague, which I just shared, who actually met Christian Klein at the event, talking a little bit about what we can do to further level up that partnership between SAP and Red Hat in context of SAP Rise. So great having SAP here on the event in Boston. And same wise, we are also at the event in EMEAR and here making sure that we can continue that collaboration between the two companies. If you want to read more about those case studies, then you can actually follow the link which is here on the slide. So we had been working over the last months with a lot of our partners who actually have also both joined customer stories. So the partners which I mentioned earlier, Mastrex, Devoteam, the cloud provider. So if you are actually looking into a specific combination of running SAP on a specific hyperscaler with a specific partner, that's the place to go to actually see on the success stories to give you a little bit more glimpse on actually what had been done already. And with that, I would just like to shift a little bit over into a more technology focused part offer session, talking a little bit about what are the things which we actually do in our products to tailor the offerings which we have for the needs of SAP applications. And one aspect here, and I mentioned it earlier in the example of WWSAT, is the work which we do in the area of security, which had been an increased focus. I mean, a couple years back, it may have been OK to actually wait for the next maintenance window to patch the system. This is no longer acceptable in nowadays. So security is a very visible topic. And so that goes through the stack on the SAP application level all the way down into the infrastructure. And so we have a team of red headers working on site at the SAP headquarters to actually make sure that we gain the necessary best practices. How the technologies which we ship in Reddit Enterprise Linux can be used for SAP, so that maybe some documentation how to enable the SAP Linux with SAP HANA database, that maybe how you can use network bound disk encryption to protect your SAP system from physical security threats, that may be the use of the FA policy demon to ensure that certain processes are not being able to execute it on an SAP environment, all the way to the more general things which you do in rel, the FIPS compliance with working as part of the open source security foundation on a secure supply chain, or also the including of the open SCAP tooling, which is a security scanner that you get with a rel subscription to ensure that your system actually is on a level of patches and versions which does not oppose you to a higher security threat. And so you will be able to download both slides. You will be able to read a little bit more of a text. Sorry for that, but it does not come through. That is probably a session on its own. That's why I just wanted to go a little bit into a highlight but not into the level of detail. But as I said, if you have specific questions, we can do that later on as well. One topic which I also want to highlight, which I think was also visible throughout one or other session here at the event, is the topic of Red Hat Insights. Red Hat Insights is a proactive analytic monitoring and management tool which we have for our offerings. And so I usually compare it in that kind of audience with what SAP is doing with early watch. So if you are using early watch, then you receive a similar service for your application level where you get information about the health of your system so that you don't wait until there is actually an issue that you see upfront that there is a need to act. Red Hat Insights provides a similar kind of service for the infrastructure level where you actually will get warnings and advisories if performance stability or the availability of a system is at risk. You will be also able to do a drift analysis between a baseline and an actual system which you are monitoring. You can also use Insights to actually create an image which is more fitted to the needs of your workloads. So all that helps in the operation of your system. If you switch over to security, then Insights provides you with a flagging of CVEs which your system may be exposed to. Meanwhile, we also enhance that to have a malware detection in Insights. You can do a compliance check referencing back to the OpenSCAP tool which I mentioned earlier, which is part of that check. And you can also check against policies which either are coming from Red Hat or which you can build yourself if the system is actually complying to that policy, all the way to when also supporting and repatching. And more on the business side of things, you can use Insights to actually overlook your deployments to be in a good shape from a subscription point of view as well as from a resource consumption point of view. So that's roughly the overview of things that you can do with Insights. As I said, it's continuously being enhanced nowadays. More and more also the platform will go to not just get more information and analytics, but also to actually trigger actions through the whole lifecycle. What is the interesting aspect here is that we have enhanced that with the corresponding SAP application knowledge. So Insights is capable to identify that the system is running an SAP application. And at the moment where it detects what it is used in the SAP context, it's also gathering additional information like the SAP system ID or like the instance number. And so all the things which you see here now are suddenly getting further enhanced in terms of value because you're no longer applying that on the flat list of 1,000 hosts, but you're now applying that in context of the SAP application. Meaning I can now actually do a drift analysis in a cluster, in a scale out cluster, and get information that I actually have an SAP system spending five nodes. One node is somehow configured differently. And so I see that quite easily, and I know, okay, I have to act now on that host so that all the systems aren't synced again. I also get advisories, not just for the operating system, but I also get now advisories for the SAP workloads. So if there is any recommendation for kernel settings for tuning parameters for file system permissions which are derived from the SAP, you will get rows in insights for the SAP systems. You can also come up with policies which may differ between a production system and a test-dev system because you now have a system ID of a system and you can actually say that certain policies should be only applied to my production system. And of course also in terms of risk, and yeah, it is important to know, okay, is this CVE vulnerability now affecting my production system or is it a test-dev system? So having that information right in that place suddenly helps a lot to actually use those tools that you have in insights in context of SAP workloads. And yeah, if I haven't mentioned or if you haven't heard it from other presentations where it's insights is part of a subscription. So it's not something which you need to buy separately. You just need to connect the system, you need to activate it and it's ready to use. It had been part of REL for Subsolutions for a while. Meanwhile, it is also available as part of the general Reddit Enterprise Linux subscription. Another pillar where we work closely with SAP and also continue to expand the collaboration is in the area of high availability. So here we have SAP certified solutions on top of REL-HA add-on. And I want to emphasize it's really not just what we say, okay, you can use REL and versus the REL-HA add-on, which more or less is pacemaker and scripts and all that stuff, but we really do development on top of it by providing you with the corresponding resource agents and scripts to have turnkey-ready solutions to make those SAP applications high available and provide the corresponding documentation. And as I said, also do the certification with SAP but also from an SAP point of view, this is actually fulfilling all the requirements which SAP has to a cluster manager. So it started historically independent where had been the application server, HA scenarios and then added the HANA HA scenarios. Meanwhile, with S4 HANA, both worlds come together so this is more and more combined now. And you see that there is almost kind of different deployments that you may have. You have a two-node cluster, you have a multi-node cluster in terms of a database. You may want to have all the replication in a sequence or you may want to use a multi-target where you kind of have multiple targets in a start-upology. You may want to deploy that in the cloud where you actually have overlapping systems to save costs and not have individual instances for each and every test-dev system to actually share that between the systems. And we are also further expanding that now in our work with SAP to enrich the offering to additional scenarios like the HANA index server crash restart which we had been seeing a lot of interest on the customer side to actually see that also handled by the cluster instead of inside the HANA database itself. Another area that we work closely with SAP is the area of automation. And so I talked a little bit about automation as part of a SEPSAR example that wars however more in the area of Ansible platform subscription. We do also have automation as part of the operating system. So that is what we do with the rail system roles. Rail system roles in general should help you to set up the operating system also outside of the SAP context so in that example I actually highlighted a little bit what you can do in the area of security so a lot of things which I mentioned earlier to be in focus also for SAP applications and where we have corresponding best practices like SELinux or NBDE or Crypto Policies and SSH we provide automated setup offers offers tooling inside the operating system and the interesting aspect is that rail system roles actually try to provide an abstraction which you can use to then build an orchestration on top of it so you can use rail system roles on the command line, you can call them through Satellite or you can come up with an Ansible Playbook which is calling them and the API actually is stable across the major releases. So if we actually have a system role for the configuration of NBDE and you write a script on top of it and you change from rail A to rail nine this should actually be stable and allow you to just continue to use your orchestration workflow while the underlying version is changing. In that concept we also have expanded to SAP where we have corresponding rail system roles for SAP applications to prepare the operating system in regards of best practices, kernel settings, files everything which is needed to actually start the installation and also have a basic integration in terms of HANA installation, S4 installation can also use rail system roles to spin up those systems within a few hours instead of doing manual installation with the corresponding tools. So talking about automation I think we all know that day one installation is fine but usually it happens once in the lifetime of the system what really gets interesting is in the operation and so that is also something that we have been working with SAP and with the broader community to look into what can we do to provide automation also for the day two tasks and so here we have started to expand the installation to give a more general topics like an upgrade of an SAP kernel an upgrade of the SAP HANA system changing of the parameter configuration the services, adding users so the things which are in the life of an SAP basis admin and we provide those as Red Hat certified collections as part of the Ansible platform subscription so in the moment where you actually want to use Ansible not just for setting up the system that is where you should actually look into the Ansible Ansible platform subscription to get access to the certified collections and use them as a basis for your end orchestration and this is actually something which we do not alone but again we want to do that together with partners and so we reach back to SAP and a few other founding members to create an upstream community which is now led out of the SAP Linux lab but where we have our partners like Azure or SVA joining to actually use that community approach to further develop the list of models and roles and collections which are usable for SAP Day 2 content and then depending on the needs of our customers and partners and the quality of what is happening in the upstream community we will then pull that further down into the Red Hat subscription so pretty much the same what we do also for our technologies in Red Hat where we want to innovate in the upstream open source community and then provide value in the subscription by pulling that through a QA and through a documentation process and ensuring that we have that secure supply chain also for that content which we can provide through the corresponding subscription. And with that, I just picked a few examples and probably could go on to talk a little bit more but I think what should be very visible that actually what SAP in Red Hat is doing and is demanding as part of SAP rising as for transformation is pretty much aligned also with what we have as a strategic pillars in our Red Hat portfolio so it's supporting you with a hybrid cloud infrastructure which is scalable, which is secure which helps you to manage so that is based or this is linking to examples which I had been given around the operating system around REL about working with our cloud providers and our partner ecosystem. It's helping you to extend SAP into the cloud by giving you a platform where you can build applications which connect or enhance the SAP environment all the way into the simplification of SAP where we tightly integrate with the idea of proactive analytics and monitoring and management from an infrastructure point of view and provide the corresponding tools and best practices how you actually can run and manage those SAP systems. And just to add a few numbers here what this means so there's a research done by IDC by applying all those technologies with integration automation in the context of an enterprise workload you can actually get quite some benefits all the way from IT operation and IT effectiveness through the agility of your development teams if it goes into the extensibility and of course also on the business side by applying automation integration will also help you to actually save costs and reach higher productivity. The fact I just wanted to leave you with a little bit more talk if you want to listen in so where are all those partners which we had been working with we also recorded several online sessions which you can just tap into on YouTube how this looks on Azure or how this actually works with some other for cloud providers or if you do it on-prem how you can use Ansible to run it out in your own data center and would now open it up for any kind of questions which you may have we still have 50 minutes to round out the session. Thanks. Questions? Yes? You are in the H&M for SAP? It is... Yes, so we have an operating system we have a REL-HA add-on which is a pacemaker cluster we have our HA solutions for SAP which is when the resource agents to connect to SAP and to monitor and then you also need to take an action you need to fence the system and you need to actually switch over that requires an integration with the corresponding underlying infrastructure and so we do have that for the bare metal we do that for our partners like VMware we also work with our cloud providers so if you run SAP on Azure or AWS on our IBM cloud that is the work which our team is doing to ensure that the HA solutions with the corresponding resource agents are capable to actually run and fence on those environments so the short answer is yes with the little asterisks I mean there are dozens of cloud providers there are also different hyperwisels and different technologies so you should look into the nodes which actually state which are the partners which had been enabled VMware yes, bare metal yes the major hyperscaler yes but there may be some smaller providers where this is not the case so that's when you should go back onto the corresponding pages and look up for what are the technologies which are supported anything else? Yes Do you have experiments to do the R test? We do yes so if we go to the customer customer case studies links which I have there are two or three case studies which actually are about customers migrating from our operating systems to REL including also SLAS and I mean it's basically if it comes to the SAP application SAP has a multi vendor strategy where you support several operating systems so that's why from an application point of view it is ensured that there is a way to go from one to the other and from a tooling point of view we also have the tools and best practices available actually where it's even a white paper which is specific to that example which you can look into how you would migrate to a REL operating system for you as for environment anything else? Otherwise, thank you for being here and if you want to hear more we have one session starting in 10 minutes which talks a little bit broader about workloads so this one was now about SAP and we will have another one which then also includes MS SQL into the picture and the work which we do with some other workloads which more or less picks up on the same idea what we do with performance tuning and automation to support those kind of workloads and otherwise I wish you a great rest of the event.