 Okay, I Guess audio-wise we are fine, right? So I guess we should get started welcome To this talk about go big or go home SAP's journey to offering a public platform as a service built with cloud foundry Who am I to actually talk about that topic? So that's me. My name is band Kranich I'm the technical lead for taking cloud foundry from the open source and making that part of SAP cloud platform. So SAP's platform as a service offering So we're really indeed building an own SAP based cloud foundry Delivery and putting that out to the market. So we recently jade with that technology About my history with SAP. I guess some would call me an SAP veteran on 19 years with the company meanwhile I actually started in more the kind of mode one world if you will basically with the stuff that made SAP big so Classical on-premise businesses stuff that is actually running the core of many enterprises Today, so I started in the business information warehouse. So SAP's data warehouse solution there in the front-end piece As I said classical on-premise basically then moved over to The business objects division of SAP when SAP acquired business objects So I was with with that team for for quite some time then I guess moved one Layer down the stack actually to be with the ABAP application server teams So basically ABAP is SAP's own programming language and development environment And this is what is really powering Many of SAP's core business systems So I guess from that perspective. I kind of know the mode one world quite a bit and then Some some years ago. I actually moved over to more the mode two world With moving over to what was called SAP HANA cloud platform back then and is now called SAP cloud platform Okay, so what do I want to talk about? I want to talk about SAP and SAP cloud platform How does SAP actually come from being that mode one? company powering many Enterprises and businesses across the world to being a cloud company. How does that work? I also want to talk about specifically cloud foundry and what it actually took for us to take cloud foundry and Make that part of SAP cloud platform and what we learned along that way and and that is I guess both interesting for people who are thinking about taking cloud foundry running that themselves or our Fellow competition to basically see and find like did SAP face similar challenges or different challenges or even people that are trying to Use cloud foundry and then see what does it actually take to run the system underneath and really run that at production scale And then last but not least I want to close off with saying what is actually next for SAP cloud platform With a focus on cloud foundry So that is kind of the standard starting slide I try to make it not that boring. I guess it's sufficient to say that we're Driving many of the big enterprises of the world so 76% of SAP of the world's transactional revenue touches an SAP system. There's Millions of people that are actually Using our cloud solution many of the Forbes 2000 companies are SAP customers and this is I guess one of the fun facts 79% of the world's chocolate production is Produced by SAP customers using one of the SAP systems and you can run similar Analogies with beer and cars and like many traditional goods that everybody is familiar with So that's like on that part of the figure side. Let's look a little bit into the company And also into our customer base So 350,000 plus customers in 180 plus countries I guess that's quite quite a number More than 80,000 employees across 130 Countries, so I guess we are following our customers in many of the countries that that they are actually in About a third fourth of the employee base being in research and development 23,000 plus Then also quite a big partner ecosystem So there is like many SAP partners more than 15,000 Across the world that are helping our customers to put SAP solution into production doing consulting etc etc and Also quite an impressive figure 125 million subscribers for our cloud-based solutions, which is like Kind of development that was actually fostered by another thing which is Showing you a little bit of history of how we actually came to SAP cloud platform and how SAP evolved from this Traditional R3 type of company to being a cloud company as well so you can see on that chart that things actually started with a mix of Technology and solution innovations as well as acquisitions. So the first one was around acquiring side base So database and mobile company basically back in 2010 And then there was a I would say quick succession of on the one-hand side Technology and solution launches as well as additional acquisitions. So I guess many people in this room are familiar with Solutions like SAP success factors or even conquer to book your travel to here and do the Expenses via that as well as SAP own built products like SAP HANA SAP's in-memory database solution as well as the SAP HANA enterprise cloud as I said as it was called previously. So SAP's platform as a service offering as well as then building on top of SAP in brackets HANA enterprise cloud additional solutions that have been launched for example in 2015 2016 and then also 2017 So what does that all have to do actually with with cloud foundry? so basically What we can say about SAP cloud platform today and the chart that I just showed was was basically Kind of built on an own platform as a service offering coming to more than 7,000 SAP cloud platform customers Building quite a few applications on top of that platform. So as I said Partners are important for SAP and the SAP ecosystem. So it's important to have partners that are actually using the platform So we have partners they're building quite a few applications Then also enterprise applications that are delivered running on SAP cloud platform As well as an app center that is a marketplace kind of an app store type of thing Where customers can buy additional solutions? As I said, what does that all have to do with with cloud foundry actually? So cloud foundry and you might have seen the keynote of our CTO Bjorn Gurke on day one We have a bit on an on and off relationship with with cloud foundry at SAP So we started looking into cloud foundry pretty early on when it was announced by the M-Bear back then in 2011 People on the engineering side looked into the cloud foundry offering found it pretty interesting from a technical perspective But then we actually figured out that like the licensing scheme and the way it was handling open source And IP was actually not fitting to to our business needs and business model So back in 2011 we basically had a no-go decision to not go with cloud foundry But instead build an own platform as as a service technology Things started to change then in 2013 when actually IBM Teamed up with cloud foundry overall and even SAP did first open source Contributions to cloud foundry with a service broker that was built to actually provision Instances for our SAP HANA and memory database Shortly after beginning of 2014 SAP was actually joining the cloud foundry foundation and then Having a keynote at the cloud foundry summit at this year So this is kind of I would say more more of the formal stuff But then also back then the actual work was beginning to look into cloud foundry from from a technical perspective I guess it was pretty much three years ago May 2014 when we first started to Take the version of cloud foundry back then and try to bring it up on Amazon web services And then shortly after we also figured out that it's not sufficient to just like use whatever is in the open source But we also need to Contribute to the open source and know more about the open source in detail So we sent first SAP employees to a cloud foundry dojo here in San Francisco 2015 then marked the start of our collaboration with a big customer Siemens Siemens is running their mind sphere platform So their IOT platform With the help of SAP's cloud foundry offering So the basis for Siemens mind sphere is actually SAP cloud platform and then shortly after end of 2015 We were also Achieving the certification to be a cloud foundry certified platform Which was also a major step and we indeed renewed that certification in 2017 so then 2016 Siemens went live with their mind sphere platform But not only that but also we as SAP cloud platform had a first beta version of a Cloud foundry powered system that people could actually have a look at we launched it at our big SAP fair called sapphire in May 2016 and we've seen quite some some adoption ever since and also Used that to gain further experience scaling up cloud foundry obviously So then later on I said we were already sending people to the cloud foundry dojo in 2015 or even 2014 2016 we actually opened our own dojo So we said we also need to actively influence certain parts of cloud foundry and one of the early areas was to say We want to contribute to making sure that cloud foundry runs very nicely on top of open stack as an infrastructure as a service So we took over the project leadership of that part the Bosch open stack CPI and also opened a dojo That was then also joined by colleagues from SUSE So SAP and SUSE are currently driving the open stack CPI efforts and there's plans to even Extend the the ownership in in the Bosch space even further and I'm going to talk about that a bit later then last but not least end of 2016 On top of looking into open stack and Amazon web services We started a collaboration with Microsoft Azure and also Google cloud and that then in 2017 also brought some Fruitful results in the end so 2017 as I said we renewed our certification. We had first SAP solutions that are actually built on SAP cloud platform cloud foundry That are we're being announced and are now going out to the market and then finally in May this year So round about a month ago. We announced a general available SAP cloud platform cloud foundry offering to people So that is by and large a little bit more detailed look at the adoption timeline So let's look at what it means to actually deploy SAP cloud platform So this is kind of the tentative data center build out plan so you basically see that SAP cloud platform is Either today or in the very near future Running on all the major infrastructure as a service providers. That means Amazon web services We have a beta on Microsoft Azure and we plan to Release on Google cloud platform soon. I would say on top of that We are also running SAP cloud platform in SAP status centers And that is a mix of the existing SAP cloud platform technology as well as cloud foundry based on open stack And there's quite an ambitious plan to extend that coverage of data centers even further And you can see that here. So why are we actually doing that? Like why are we not focusing on one of those deployment methods but are running a true multi-cloud strategy and are with that multi-cloud strategy at least to my knowledge one of The very few vendors that are actually offering a public platform as a service offering on Amazon web services Microsoft Azure and soon Google cloud platform So essentially one reason is to say that specific customers have specific needs some customers say I'm in competition with Amazon as a retailer. So you won't see my data going to AWS Or other customers are saying I already have a large enterprise contract with Microsoft Azure So I want to see SAP cloud platform running on that infrastructure as well. So and then also there is obviously data protection and certain legal requirements to basically be in certain geographies when it comes to Deploying enterprise critically later. So that is one of the reasons why we are running that to multi-cloud strategy Okay, so only some some very few impressions on how that actually looks like from from a customer perspective This is our cockpit entry page where you see the various data centers that people can can select from Just a brief browse through then parts of the service catalog where you can see The services that we are actually offering from big data services to Like traditional open-source databases like MongoDB or Postgres Things like Redis and Rabbit MQ But then also SAP services like the SAP HANA in-memory database or SAP ASE as an additional database offering and then last but not least integrating that into Basically the way how Cloud Foundry is displaying things and ability to start stop applications scale them up even via the UI Not only the command line, etc Okay, so that's the high-level overview with kind of quote-unquote architectural boxes on SAP Cloud Platform Cloud Foundry so you can see as I mentioned earlier the support for various infrastructure providers You can see a layering of services for data and storage certain platform services And then programming models and DevOps tools So usually at that point in time I get the question of like how do you guys differentiate from other Cloud Foundry based offerings? And my kind of standard answer is up until that point We don't even want to differentiate and I'm going to spend a couple of words on on why that is In a couple of minutes where we see ourselves actually differentiating is what made SAP strong So SAP being a 45 year old company kind of for the entire lifetime focusing on Providing business driven services and applications and this is where we think as SAP we can actually differentiate by enabling both SAP internal groups to build business services and business applications on top of our platform as well as enabling our partner and Customer ecosystem to do the same and then by that enriching the platform by more and more business services and APIs So that's one important differentiator the other important differentiator is shown here on the left and on the right Which is our existing on-premise and software as a service offerings So obviously we as SAP have an interest to make sure that you can nicely integrate with other SAP offerings and As many SAP customers are looking for a way to enhance their mode one business So for example an SAP S4 HANA or an SAP business suite with more agile ways in the kind of mode to fashion SAP cloud platform is the ideal way to actually build those types of application and service Iterate rapidly on on those and basically make them available to a broad range of customers Be it via mobile devices be it by hooking in IOT devices, etc, etc So that's the high-level overview and but then I also wanted to get back to the slide that Björn Gorka showed on day one around the detailed Components, I also don't want to bore you with let's say explaining all the boxes, but what I can say is actually People that want to go with running cloud foundry itself It's not only running cloud foundry itself There's a whole lot of other things that you actually need to consider So if you look at that slide a bit more closely you will actually find that the cloud foundry box is maybe One-third of the overall architecture only and this is because cloud foundry is is a great environment for 12-factor Applications and has great abstractions, but then cloud foundry itself doesn't solve problems around How do you actually monitor that whole thing? How do you actually? Receive the locks and collect the locks and analyze the locks of the applications that are running on top of it How do you monitor those applications? What do you do about continuous integration and most importantly? What do you do with backing services like taking cloud foundry from the open source is nice and fine, but Riding a 12-factor application without any backing service will probably not provide any any good value So you need to have a good set of backing services available and cloud foundry itself Doesn't provide an answer to how do you actually manage operate? Back up etc. etc all those backing services So if you're looking into spinning up your own cloud foundry environment The stuff that I just mentioned is important additional considerations along that journey Plus then obviously the fact that like you have different IAS layers underneath so that opens a whole lot of Additional questions at least if you are not Able or willing to focus on just one infrastructure as a service So what did we learn along the way? We learned quite a lot. I have to say and in the last three years and I have categorized that in in five categories knowledge open source operations Security and certifications, and I want to spend a bit of time on on each of those So what did we learn in the area of knowledge? So first of all, it's important to train the people that are Building and operating cloud foundry and for us actually it started with like even the hiring process When by chance many people came across our job postings and then had suddenly the feedback of We didn't even know that SAP is doing that cool stuff, right? so we SAP traditionally known as Kind of the very boring mode one kind of thing and then usually also our job postings Starting with explaining what SAP does but that does not necessarily reach the people that you need to reach To actually run something like cloud foundry So you want to have the people that are kind of either fresh from university are keen to learn or have a background in things like Networking and operations, etc. Etc. So we had to look into changing our hiring process there then once you've hired people the next question is how you do you train them because Usually you do not get the people that already know it all which is fine because like that stuff can be learned But how do you learn that? And there we figured out that actually dojo is a nice way to to train people and get people up to speed But then also taking the methodologies inside the dojo and applying that to our own development is another key factor So things like pair programming if you have the right people that are open to that is an excellent way to actually share the knowledge inside the organization Also, many people inside SAP are more coming from a traditional environment with a single language Maybe Alva maybe Java we've moved that completely by kind of having All of our people actually being now polyglot things like Ruby go bash scripts. Don't scare them anymore So expect a steep learning curve for for those people So multi-cloud as I said another challenge infrastructures are similar, but then have subtle differences People need to dig through that themselves. There's no like this is the difference between AWS and Azure course People need to learn that in more detail and in order to be able to learn that they need to know the good old basics So stuff like what is a distributed systems? What is actually networking? What does that Linux thing do? Why do I need to actually work on the shell and not have a GUI or an IDE to work with that stuff? And then last but not least also a topic for SAP The environment that you are doing or that you are running cloud foundry in needs to support it And if it doesn't support it out of the box, it actually needs to be changed to support it So so things like corporate proxies that like enterprise IT applications or departments usually put in place are definitely preventing Adoption of cloud-based software things like everybody gets a windows laptop when they're on board is preventing development in in a cloud-based environment. So it's those Seemingly relatively simple things, but then it takes quite a bit to actually change that Training people using cloud foundry is also important. So I've talked about what does it take to run cloud foundry now? What does it take to actually? Ride an application on top of cloud foundry. So we Traditionally again have many people coming more from the on-premise world and taking or doing that mindset change Takes quite some time, but then also some effort. So here's a couple of figures of Our people from what is called the cloud curriculum. So a specific department inside SAP that are running training courses in order to make sure that the people that are Onboarding towards a cloud journey have the right mindset that starts from like very basic trainings Like what is the difference between on-prem and and cloud just from from a principles perspective over to training them on Microservices continuous delivery, etc. etc. So if you are onboarding on on a cloud foundry journey make sure that You have appropriate training for the people in place And then also those trainings provide a nice stress test for the cloud foundry instance that you're actually spinning up Because like mostly those trainings are around you deploy an application you create a backing service You bind that backing service, etc, etc And it's not single users that are doing that but it's maybe 50 or 100 that are doing that in parallel So we actually learn quite a bit from from that And especially on what is called our canary system So that is our internal development system that most people Inside SAP are actually using and that has seen in peak times as many as 4,000 Active developers meaning developers that have locked in in a time span of two weeks and that are working with that system So like judging from the number of people in R&D at SAP 23,000 roughly 4,000 of them using that cloud foundry instance You can see kind of the order of magnitude inside SAP that cloud foundry has has meanwhile reached So what did we learn on on the open source side of the house open source has definitely won the enterprise period There's no other way of like any single company doing all the stuff themselves and then like still being successful Openness meanwhile is also an important selling aspect towards our customers And then it's also an important discussion with with our partners So if you're not open you're oftentimes out of any business discussion But then open source consumption itself is not enough So open source consumption is like the first step if you are serious about open source You need to go into contribution which then leads you into actually actively influencing the community Which is what SAP is is doing for for cloud foundry Open source initially saves some time because you don't have to write all that code yourself. That is clear But don't be mistaken. You still need to know that code. So even if you haven't written it yourself You need to be able to read it to understand it to debug it to operate it. So that is important skillset to actually build up Also another advice from from our experience use the open source as it was actually intended to be used Don't try to invent like interesting ways of saying hey This open source has this great feature and I can combine it nicely and kind of turn it into something That was maybe not originally intended to be that way But I use it that way simply because the open source underneath you could just change and then like your nice ideas might just turn Into something that was a temporary thing Forking means death. Don't fork open source and then like be brave and say I can continue to maintain that stuff Which is also critical when when it comes to to the security aspect Processes make sure that your internal processes are set up. I've talked about that already What I can also say as a result of open source usage in cloud foundry at SAP is that SAP cloud platform cloud foundry meanwhile represents the biggest usage of open source Inside SAP by far I would say So what is our credo for open source? SAP's goal is to actually commoditize the platform as a service layer So with the lowest possible effort, we want to take whatever comes from cloud foundry in the open source and bring that into production We want to use as much open source as possible Where we find that there's areas inside the open source that are not sufficient for our needs We instead of keeping things proprietary want to contribute to the open source because again, we have Realized and come to know that doing things alone is actually much slower and much harder than doing it in the community in that sense we are more kind of a distributor of of Platform as a service with cloud foundry and then last but not least on on the influencing part It's definitely an important aspect for SAP to make sure that cloud foundry Stays the ecosystem of choice for the industry in in the years to come So we feel topics like for example containerization Especially Kubernetes and its relation to cloud foundry is an important topic Topics around security and compliance is another important topic So we want to make sure that cloud foundry stays on top of those developments our commitment to cloud foundry Björn Gerker in his keynote has shown that quite a bit So we have instantiated and actively managing quite a few open source projects Be it on the open stack side be it on the side of managing services service fabric is one of The open sourcing that we did there to manage enterprise ready services Topics around security like for example IP sec or in order to securely communicate Between VMs inside a Bosch deployment Abacus as a way to meter your cloud foundry environment a Kubernetes CPI as one Initial experiment to actually look into into the direction of what does it the intersection between cloud foundry and Kubernetes actually do? Java memory assistant, etc, etc We have major contributions in many of the core areas of cloud foundry But also in many of the extension areas of cloud foundry and obviously more committers in in much more areas Just a quick peek on on that one This is actually showing in orange the number of pull requests with SAP involvement That means either pull requests that have been created by SAP starting from 2014 until May 2017 over time or the pull requests that were actually pulled in by SAP Full-time committers to certain projects and that is indeed growing nicely Similar things can be said about the total contributors per month that are actually contributing as well as distinct contributors per month So what did we learn on the operations front Bosch is definitely a great tool which is powering our cloud foundry landscapes It's a standard. We like it. We have survived many critical situations by by the help of Bosch And it also enables our multi-cloud strategy So we wouldn't be able to ship on for infrastructure layer as a service If we wouldn't have Bosch underneath that is actually driving all of that Observing stuff in production is always The better case instead of sitting back and thinking about theoretical problems that you want to solve Learn from what you have put in production adapt your strategy based on that and then iterate quickly on on that and Deployments can grow really huge which is why we are glad that we have Bosch to manage all of those deployments and Surprisingly enough even if you think there's many big cloud foundry deployments out there We're still hitting certain limits that other people didn't hit and we are every now and then asking ourselves Why did other people not hit those limits like initially when go router came out? We hit performance limits where we thought okay, like go router is kind of completely rewritten in go and should actually scale Very nicely initial performance measurements showed that this was not the case Unfortunately, we were able to provide that feedback to Shannon Kohn and the go router team They adapted based on that feedback and now I think the go router scaling is actually where we need it Similar things can be said about memory calculation in the Java build pack and also metrics Real quick a sneak peek and you don't need new glasses. I've blurred that image a little bit on Conquerors so everybody is using conquerors I guess we use it for both deployment as well as monitoring of our systems But why I actually brought in that picture is to show you what we do with conquerors So we have development systems not only one but many of them where the actual functionality of SAP cloud platform is developed We need to have it on the four infrastructure layers That development is then consolidated into staging systems again on all the four infrastructures That is brought into our internal cannery landscape. So the testing landscape that I talked about earlier From there it goes into what is called a hotfix system because in order to do a fix in the live system You need to have a system that actually reflects the life status and where you can test your your patch basically That again has to be on all four infrastructure layers to cater for The differences between them and then last but not least that floats into our life systems So by just counting the number of boxes and conquerors pipelines You can maybe get a glimpse of the order of magnitude that we are running cloud foundry on So then our second to last security open source security I guess the basic statement is that we can say if you want to sleep well at night Don't use open source because if you use open source your vulnerabilities will be pretty visible to you and they will be published out to The world basically and everybody seeing those vulnerabilities has a chance to attack your system So you better know what you're actually shipping with your deployment and it's not only cloud foundry But also all the other stuff and the stuff that you package into applications You need to have an agile security response process because Once those vulnerabilities are published you basically Need to be able to react quickly to patch quickly to bring in changes and to make your systems against secure and Oftentimes fall forward is the best strategy to do that So be able to adopt the latest releases of cloud foundry in essentially no time roll that out to production This is a safe way to to keep your system secure Cloud security also has changed. It's different from on-premise security This like you build a big castle wall and then like everybody Basically runs through that or against that wall and can't get in this is that this is on-premise worlds You need to have security in depth where you have various barriers of security in place You need to take care about authentication authorization and encryption of everything that goes in and out the system But also inside the system and usually penetration testing. So external people trying to hack you But are then also paid by you is a good way to actually learn the things that you did not figure out yourself and Last but not least multi cloud forces you to generalize certain concepts like if you want to run on multiple infrastructure layers Then you need to generalize certain concepts in security as well So last thing Certifications or we have an ISO 27001 certification for some of our environments. We are cloud foundry certified Topics that are still remaining and that is related to cloud foundry itself is topics around Separation of duties. So if you are a cloud foundry administrator, you're essentially ruling the entire system You can see all the things that your users can see This is a concern for us and this is some area that actually we see some demand to change things And credentials rotation is another one that actually comes from certification So be able to change your credentials rapidly where we think credit up is a great project that will push cloud foundry in the exactly right direction There's a lot of work hidden in Certifications and you can solve many topics with either technology or process if you solve them with process only solutions meaning You have responsibilities and like this person needs to do that that might bite you later on Okay with that last but not least what's next for SAP cloud platform expanding our multi cloud strategy more data centers infrastructures, etc, etc More SAP applications and services also partners and customers obviously and contributing more to cloud foundry and Then last but not least cloud foundry itself stays dynamic. So we want to make sure that the cloud foundry ecosystem Keeps up with the changes in the container world, especially on on kubernetes And us answering the question of like does it is it really required to co innovate? Or to not co innovate in a world between kubernetes and cloud foundry is one of our major questions as well as is API management because in a microservices world APIs are paramount and cloud foundry could need a little bit more support for for those types of scenarios With that one last thing Oh, there's a trial out that everybody can subscribe to and try out what we have built up That is one URL and QR code to to actually look at and then last but not least we are hiring so if you want to join our efforts if you're Courageous enough to jump on what you have just seen There's open postings out there and with that running a little bit over time. Thank you very much Open for questions afterwards. Thank you