 Let's get started. Hi again. Thank you for coming here today. I realize we are between you and you're on the lunch, so we will try to get you all out by 12.30. So today, we are going to talk about Beyond Bosch and CPI. So what that means is basically a journey for the last one year. So in May 2015, last year, a little over a year. And I remember the day because last year, the summit was right after Mother's Day weekend, so I traveled the day. So last year, it was just Ning and me at the conference. Our CPI was an early preview, and we demoed it. And we're really glad to be back again here this year and share our incredible journey the last one year, releasing the services, running customers in production, and building a Microsoft Cloud Foundry community within Microsoft. So our goal today is to share our experience and our journey. Ning, if you don't mind, hit the slide next, please. About us, who are we? As I mentioned, we have a small Cloud Foundry community within Microsoft. There are a few folks here in the room as well, in addition to us. I'm a program manager primarily working on Azure first-party pass services and open-source pass service integration as well. And with me is Gil. Gil is a partner architect who primarily focuses on ISV onboarding. And we have Ning, who heads the team, who's a program manager for Cloud Foundry project, and she works in the open-source team. So this is just a small team. The rest of us are, you can find us in the booth. So today in the 30 minutes, we want to walk away with these three takeaways, Cloud Foundry plus Azure. So we'll spend a few minutes talking about the why and the how. Then we want to show you how you can easily get started with the click of a button, Deploy Cloud Foundry on Azure. And finally, we just announced the Azure service brokers. These are service brokers for Azure first-party services. And Ning will do a demo of that. Thanks, Ning. So before we get started, let's look at what is supported today. Cloud Foundry on Azure, where are we? What's supported? So number one is the open-source Cloud Foundry is generally available today. In addition, Pivotal Cloud Foundry is fully supported. We also have a single click template in our marketplace that allows you to deploy PC of an Azure with the click of a button. And just announced, hard thing is service brokers. So these are the things that are today supported in Azure. And if you go to the next slide, and one more. Thank you. So just to quickly give some highlights of Cloud Foundry on Azure in terms of what's supported. So a lot of customers, a lot of folks ask us why do we support Cloud Foundry in Azure? What's a primary driver? The number one reason for us to work on Cloud Foundry is many of our customers have asked this. So it's frequently asked by our customers. It's a great option for running Java workloads on Azure. In addition, it's fully owned and supported by Microsoft. And it's backed by our executive. So it's a full executive commitment. In addition, we have a great joint engineering model with Pivotal. And now, from recent news, you might have seen Microsoft. It's also invested in Pivotal Success. So a lot of, again, in just one year, this project picked up a lot of momentum and a lot of cool highlights to share. So a lot of, in the next couple of three, four slides, I want to give an overview of some of the most commonly asked questions and try to summarize where we are. So the first question is, where does Cloud Foundry fit in Azure ecosystem? So Azure has a lot of past services. So our customers ask us, where does it fit in the ecosystem? When do you use what? So this diagram is what we call a past continuum. This describes all of the past services in Azure, starting from the IaaS side to the past side and in between. And I'm not planning to cover any of these in detail except Cloud Foundry. But if you look at Cloud Foundry, Cloud Foundry sits at the same level as other first party services. It's built on the same infrastructure like the rest of the services. And at the end of the day, we leave it to the customers to choose the platform that's right for their applications. All right, so this is about where it fits. The second next question that gets asked often is, in what regions can you deploy Cloud Foundry in Azure today? So if you go to the next slide, so if you've seen Azure regions, so Azure today has been announced in 32 regions. So this is more than any other Cloud combined. And out of these 24 are operational. So this is a huge, huge investment. This is serious stuff, right? So we are making a big bet on this, growing our infrastructure. The goal for Azure is to be in all major regions and where Azure cannot be, Azure Stack will be there. So I just wanted to actually take a quick pause and ask a question that I wanted to ask in the beginning, but I forgot, is how many folks in the room use Azure? Thank you. This store doesn't call, it's all Microsoft phones. Okay, a few of you. So for those of you who are not familiar, right? So this is one of the strategic investments where Azure is growing all these Azure regions. And so out of these regions, some of these are sovereign Clouds. For example, Azure China is an example, which is sovereign Cloud. Germany, which was announced, is also a sovereign Cloud. So these are all the regions. There's another government Cloud as well. So these are all the public Cloud and sovereign Clouds where you could run Cloud Foundry. All right, next one. A little bit about the Bosch project. So Bosch CPI, as everybody in the room knows what CPI is, so I will not talk about it. Just like any other CPI for any Cloud, Azure's version is also fully open sourced. We have a dedicated engineering team that started small and it's growing. It's aligned with the community engineering practices. We work very closely with the community. So if anybody in the room has worked with us on this project, many thanks to you. And the most important thing for us is the whole CPI, and the whole Azure, it's designed to work both in Azure public Cloud or the Azure Stack, which is an on-prem data center. So when Cloud Foundry, when it becomes available, our goal is to make it easy to deploy Cloud Foundry in Azure Stack. So yeah, and we have a committed roadmap. Some of it we'll share today. If you want what's coming in the pipeline, please feel free to stop by our booth. Next slide. Yeah, so the last, so another question that we get often is, this is a new service gone in production, just like any other services, how ready is it for enterprise workloads? So today with Cloud Foundry in the last one year, by working with customers, we have actually exercised many enterprise scenarios, and these are some of the examples. So you can take Cloud Foundry and do an active-active configuration or a multi-region deployment. This is just a topology I put there. Things like securing your deployments, isolating them. So most of the enterprise scenarios are supported today, and many of them are in the roadmap. All right, so with that high-level overview, I'm going to give it to Gil to talk about pivotal Cloud Foundry. All right, well that was solid. I'm gonna pay attention to where the boundaries on the stage are. Yeah, I'll try not to fall as well. Okay, thanks, Kundana, and as Kundana mentioned, I'm an Azure architect. I work exclusively with ISV partners who are onboarding onto Azure and enabling their solutions on Azure. Over the past six, eight months, my life has become almost exclusively Cloud Foundry and Pivotal Cloud Foundry, and we're working very closely, and this is just some examples of the work that we have done over the past few months. This is a picture of a hack fest we had where we brought together a group of people who were just getting started within Microsoft on various projects around Cloud Foundry. We brought them out into Redmond. We had some Pivotal folks who were doing some training with us, and then we did some of our own projects, and out of this, we have a growing community. We have, I think our, we have, if anybody uses Yammer, we have our internal Yammer group. It's got almost 100 folks on it, and we're actively working together and supporting each other. You may have seen the Ford project announcement, so a lot of us worked on that, either in one way or another, and behind the scenes helping each other. And in addition, you may have seen around the time of the Ford announcement that we brought to market a marketplace offer, which I'm gonna talk about in a second, which allows you to single click out of the marketplace and deploy a test environment in Azure. We're also working side by side with Pivotal engineers. We have Azure engineers who are gonna be spending time with Pivotal directly, and we're also advising on architecture with our customer advisory team. And again, starting with Kandana and Ning's work, which we're all very lucky that they started, we're fully supported on Azure. So how can you deploy Cloud Foundry with one click? I like to think of this part of our presentation as easy ways for you to get started, even if you, I saw, we had, I'm gonna just call it 20% in the audience who have played around with Azure. These couple slides, I threw some links in here, and this content will be available to everybody after the summit, but it's super easy to get started with Azure, and it's super easy to single click and get started with Cloud Foundry on Azure. So a fundamental basic foundation of this is the Azure Resource Manager, and that is essentially the API for everything that happens within Azure, and it not only is the API, but it includes a really easy template-driven way to create things in Azure. So you can build a JSON template, you send it to the Azure Resource Manager, and you get stuff. It's all related, it's all pre-configured. We actually have an extensive library, and I'm gonna show these in just a second, but we have an extensive library of pre-built templates to construct a lot of common use cases within Azure, and the open-source Cloud Foundry, the first release that came out last year, the Bosch components and the initial networking is all based on a pre-configured Azure template, which you can go to and you can look at that. So again, Resource Manager is foundational to this. From there, you use ARM, and then we have now built a marketplace, so a lot of popular software solutions that you may be familiar with and may be used to using in the Cloud are available in the marketplace from a single click, and based on that, we built the PCF on Azure offering, and additionally, if you get into trouble, we've done a really nice job in partnership with Pivotal writing a deployment guide, so let's take a quick look at these. Where is the browser? Okay, so, first starters. Oh, it's on the, needs to be moved over to here, right? Okay, now I can't see the screen. Can we make it a single screen? All right, I'll just improvise. So you don't usually hear people talking about documentation as being very exciting, but if you haven't looked at any of the Microsoft sites lately, we've put a tremendous amount of investment into the documentation. There's a lot of great examples as tutorials, there's getting started guides, and there's really tremendous detail about how to do things. This is just the example of the Resource Manager documentation landing page, and it's really quite extensive. So based on this, where is the mouse? Okay, we over, since Resource Manager has come out, and this is something that Microsoft is really doing a heck of a lot of work on internally and with the community, is we built this library, and it's, you can see it's on GitHub, anybody can look at this, anybody can contribute, participate of quite a lot of common use cases of preconfigured solutions that you can deploy right onto Azure. And again, you may have seen this at some of the previous presentations, but this is our GA guidance for Bosch and Cloud Foundry on Azure. So again, you'll see there's a resource template in here, and then from the resource template, and your jumpbox is created, and then you can go right in and launch deployment scripts just like you would on any Cloud Foundry. And this is the marketplace, so let's see what's that number there, it's now 3700 and growing, and a lot of my colleagues are actively working with names you would all recognize. In fact, actually I think this was yesterday, we just made a really nice announcement with Jenkins, so there's Jenkins integration, so we're working really closely with them. So just to give you an example, if you looked for any of your favorite solutions in here, you're likely to find them by going here and search for Pivotal. Hopefully I typed it correctly, all right? And there is the offer, so if I select that, how are we doing on time? Okay, good. I can single click right into here and it's gonna launch, so let's just take a quick look at what that does for us. So that deploy button, and actually if you look at the quick start library that I showed in GitHub, every single one of those templates also has a deploy button, what the deploy button does is it just takes a template, starts the Azure portal, and takes you right to a launch page with the template. Now when you do a marketplace offering, the quick launch goes to the partners launch page and you can see there's extensive description and it's really pretty much what was on the marketplace landing page also is in here, and I'll show this at the end, but this is the only way to the bottom. The deployment guide is here as well. So if we, which I didn't mean to click on, that's the deployment guide. Okay, but if I click on create, all right, we had, we were using several people's laptops so we have different logins, so what you would see if I had the correct login here is there's an entry screen, there's a few fields that you need to enter so that Bosch has the right credentials in order to create things in Azure and then also this is a commercial offering so you do need a PIVnet token but it is a 90 day free trial. And then that would start to launch the entire Cloud Foundry. Now this is a preset size that's meant for POCs and testing but it's again, you enter your secure credentials, hit click and you're off to the races. And so again, if you're doing that, this is, okay. This guide will help you all, if you hit something that's an issue, this guide is probably in here. Okay, we've done a pretty, a lot of people have battle tested this to make sure we have all the appropriate guidance in here. So let's go back to PowerPoint. So give that template, deploy some more 50 VMs, right? Yeah, it expands to somewhere like 50, I think the actual number is in the deployment guide, Kudana, but it's something like 50, 60 VMs as it, you know, Cloud Foundry has a lot of worker roles and then it settles down to like 30, 35 VMs. Yeah, and that's all automated. It's just, you know, runs. And so if you have entered all of your, we'll get back to here, we're wrong way. You will see all of your VMs running once you've launched. So this is just a screenshot of a running Cloud Foundry that has several VMs. So with that, over to Ning. We're kind of optimizing it all the time. The last thing I've seen was somewhere in the hour or so timeframe. Of course, you know, any Cloud Foundry that you would launch, that is gonna depend on how many, you know, how big you make it, right? This is, like we said, about 30 to 50 VMs. Okay? So on to service brokers. Okay, thank you Gil and Kudana. So we are the engineer team for Azure Open Source and in the past two years, our major focus is Cloud Foundry and enable Cloud Foundry on Azure and we work closely with the community and with our customers and has been an incredible journey. Here you can, just as Kudana mentioned, CPI is the first project we work on. With that, that is the first interface we have between Cloud Foundry and Azure. And we have a preview last year about the same time for the summit and the end of last year we finally announced the GA. And CPI is just the first step. Beyond that, actually, there are a lot of more components in Azure that can contribute to the ecosystem of Cloud Foundry. And from this graph, you can see for the infrastructure of Cloud Foundry and at different level, we have component in Azure that our customer is interested in asking us to integrate and contribute to Cloud Foundry component. For example, the application gateway for routing and load balancing, for Azure Active Directory for authentication, block storage and service brokers, and then our Microsoft operation manager suite for monitoring and logging. So today, I'm going to focus on service brokers because as Gil and Kudana just mentioned, we just released a public preview of our first batch of service brokers last week. Okay, quick look here. Here are the five service brokers, the Azure Blob Storage, Event Hub, Service Bus, Radius and DocumentDB. These are the top, on the top list customer is asking. And you can also see later I'll show the UI. We have a simple and consistent interface. So whatever you are comfortable today to develop for service brokers on your existing platform, it's consistent. You can use the same way to configure it and to use it. We call it meta-service broker. What this does is we have one single service broker interface. You only need to install and configure one service broker. And after that, all the services, the five services is included in this package. We just need to enable it. And this is totally open source. So it's open to community to contribute and adding feedbacks. For different roles for Cloud Foundry, for service broker, we have different guidance. For admins, we have guidance on guide you through the process of creating service, finding services. And for developers, we just need to, all you need to do is to utilize the environment variables to access the service incidences. And then for contributors, and we have guidance on how you can write your own service brokers to, if you like any Azure services, you can use the same way to add to our package. So next, I'm going to take a look. So this is where our service broker in GitHub. And we have the, this is the meta-service broker. Here's the overview and the guidance for admin and the guidance for each individual services. The service bus and the event hub are in same service. And then the contributors guidance. Okay, so the next I'm going to walk through the step how an admin can deploy and utilize a service broker. Here I already have a Cloud Foundry deployment. And with that, I just install our meta-service broker as an application to this Cloud Foundry deployment. And right now, since this is a PCF deployment, you can see if I check the marketplace, these are the default service brokers that is installed that does not have any Azure services yet. So what I'm going to do is I'm going to first create a service. Okay, so seem to me the service broker is currently created. This is the meta-service broker I just mentioned, which is it appears to be a single service broker, but it contains all the services. In order for you to access all the services, you need to enable them. So let me enable the service broker. Let me just a little bit better typing. Okay, so we enable the first service broker, which is the block storage. Let's enable the next one, which is Azure service bus. Okay, and let's enable. Remember, Azure service bus have both service bus and event log. Now we enable the document DB and finally the latest service, Azure service. Okay, so all the five services is now enabled. What we can do is we can do a marketplace. So from here, if you look at the marketplace, you can see the Azure service brokers are already here and they're available for the developer to use. Next, the admin wanted to make a service instance. So the developer can take advantage of it. So he first need to create a service. I'll specify the plan. My spelling is really bad. Okay, so it's already created, same to me. So in order to, so the service is created in order for the application to use it, you need to actually, you actually need to look at your applications. So let's go to our application and here. So if you look at your application, you will find, so all you need to do with your application is you can take advantage of the service, the environment variables we just created for you. So here you can see that's the Azure block service and then if you have the service enabled and then you can access the environment variable. So here, what? That's looking at the slide. So finally, let's take a quick look at this. So this is the PCI app manager with the Cloud Foundry deployment and you can see with the marketplace, all the Azure service broker is now enabled and you just need to run your application to bind it later. Okay, yeah, switch this slide. Thank you. So we have a couple of other sessions. If you want to learn more about Azure, we have a session on .NET and then we have also tomorrow a panel where you can come and ask some tough questions. No. No, because these guys are taking some, signing them up for tough questions. But hope to see you around in the booth if not there. Thank you.