 My name is Dan Crook. I am an enterprise architect within Intel IT. So I'm not here to talk about chips or SSD drives that Intel produces. Those are all awesome. I'm in IT. And we have a program at Intel called IT at Intel where we go and we talk about our experiences in whatever it might be. In this case, it's our experiences with cloud and cloud foundry, but there's also other topics. If you're interested in learning more about Intel IT, there's a link at the end of the presentation that is available on the website for the session. So you can find out more information. Intel IT is pretty typical for a large enterprise, a multinational corporation. We have roughly 6,000 IT employees, which if you think about, wow, that's a lot of IT people in the department, but we also have 106,000 Intel employees. So it's a lot of customers to provide service for. Our percentage of revenue spending on IT is decreasing, and that's good from a CEO perspective. Hey, we're decreasing the costs, which is good, but it's also from an IT service provider perspective. It's a little scary. So now we're getting our budgets cut and cut, and now it's like, okay, how are we going to make this all work and still provide the service at a high level for our customers? We have roughly 220,000 devices that we manage between laptops, desktops, workstations, and small four-factor devices. So there's a lot of devices to manage. We have 163 petabytes of storage that we maintain within Intel IT. So it's pretty standard for a large corporation, but it is a pretty complex environment. So this next slide, which you can't see, is just a lot of the things that I think we're all, if you're an IT or in Silicon Valley, you're experiencing these types of things. So things like the cloud is real and disruptive, and it is. The cybersecurity threats, DevOps, open standards, multiple platform applications. User experience. All this stuff is influencing not only the vendors, but also IT departments. So the one I'm going to focus on is the cloud. So let me just talk about an experience in my IT career when I wish I would have had something like a cloud to run. So about 17 years ago, I worked for a company that was providing a front-end for a ticketing for a Major League Baseball team. So this was the Giants. And we had created this website. We thought it was great. We got a heavy-duty back-end system. We're going to be able to handle all the volume. Don't worry. We're going to be fine. And so we put out a release. Hey, at this date and time, you're going to be able to order your tickets for the season or whatever you want. And so, you know, we're all ready. That point in time came, and all of a sudden, we were flooded with requests, HTTP requests, you know, login requests. And this system that we thought was so heavy and strong just went to its knees and it crashed. And we said, okay, well, let's bring it back up. And we brought it back up, and it just crashed again because of the volume. And it's at that time when it would have been fantastic to have a hybrid cloud or some kind of cloud workload distribution mechanism. So I said, look, you know, in this point in time, I'm going to have, you know, a million requests for login. It would be great to be able to distribute that burst out into the public cloud or a private cloud. But as it was, we didn't have that option. So we did the old-fashioned way. We gave them a date. We said, you can buy your tickets on Friday. We didn't give them a time. And so that way, things would happen more in a, if you're familiar with statistics, in a Poisson arrival where things kind of happen in a natural way. And that's how we got around it is, you know, we didn't give it a point in time because if we did, it would happen again. So the power of cloud is that you can start distributing your workloads. You can think about your IT workloads in a modular way in a way that in the past wasn't really possible. Oh, is it working? Yeah, yeah, go ahead. I'll keep going. So what is hybrid cloud? So hybrid cloud is the ability to, if you have something like a burst of traffic or a workload to be able to spin that out into a public cloud, for example, where, you know, for the short period of time, you know, if you're a major e-tailer, you know, if it's the, you know, Black Friday or whatever it is, you want to burst your workload for this particular point in time, you could do that in a hybrid cloud scenario. So Intel firmly believes that hybrid cloud is the future. Oh, cool. So there we go for you. So it's like four to reverse and that's a laser pointer right there. We got the Wizard of Oz back there behind the curtain. Okay. Got all kinds of issues here. Do I have to get closer? Hang on. That might help. Okay. Okay, thank you. Thank you. Yeah, no problem. Okay. So hybrid cloud. So the research tells us that roughly 60% of IT decision makers are looking at some point to move to the hybrid cloud, which is kind of the end all be all, as we see it, of the cloud strategy. And that 70% of U.S. organizations are considering it in the next 24 months, which is pretty soon. Where are we at right now, generally speaking, from an industry perspective? 82% of organizations have a multi-cloud strategy. So multi-cloud is where you might have a private cloud, maybe running on cloud foundry. You might have infrastructure as a service, but you also might have SaaS cloud vendors that you're using. And so most people, and this is where Intel is today, is really in kind of this multi-cloud area where we're leveraging the cloud in SaaS. We have a private cloud, a successful private cloud based on cloud foundry, but we're not at the hybrid cloud yet, but hopefully we'll get there. The hybrid architecture, as seen here, is all of the vectors are going in the right direction, lower cost, higher developer satisfaction, improved scalability and resiliency. All that stuff is heading in the right direction. So what Intel was faced with was, Intel's been around for a number of years, and we've built up a huge capability of software and applications and capabilities in our data center. So the question that we had to ask ourselves was, okay, we have all this stuff running internally. What of any of this stuff is going to make sense to put into a cloud offering, whether it be private or whether it be a SaaS vendor or a public cloud? And so what we did is we did an analysis. So we did an analysis. We looked at it from several different perspectives, and we looked at it from business considerations, agility time to market to TCO. There's also technical considerations of the workload you're talking about, performance integration and data size. And there's also ecosystem considerations, security of the SaaS offerings, how stable they are, how mature they are, how well funded they are, et cetera. So these are the kind of categories that we started this analysis with. And we specifically went, and I'll talk through a little bit about the technical considerations. So in the technical considerations space, in the performance vector, public cloud, if you have unpredictable workloads, public cloud is a great place to go. In the security, if you don't have a lot of security expertise in-house, public cloud is a good way to go. If you don't have a lot of dependencies on your back-end systems, then public cloud is a way to go to save costs. And if you don't have a ton of data volumes, well, it might be a large dataset, but you don't access that often, like backup recovery, things like that. That would make sense in the public cloud. In the private cloud, and this is where Cloud Foundry at Intel plays, if you have applications that are late and sensitive, you need responses back from your applications and subseconds. You need to control the access to the data, maybe it's very sensitive data, financial data, things like that. You definitely want to consider a private cloud. If you have high-risk data, if this data got into the public hands or into the wrong hands, maybe it's a circuit design that is proprietary, that's highly valuable, a patent, or something like that. Stuff like that, we think you probably want to keep it in-house, in a private cloud scenario. In the integration space, if you have dependent systems that don't have open APIs or that you have a lot of APIs that you have to call into internal systems, you're probably going to want to do that in the private cloud, and then if you have significant data volumes, financial, industrial, and others, that would point to the private cloud as well. What we did is we took all of the different applications and workloads at Intel, and we analyzed them and rated them in these different areas. This is what you see from an affinity of workload placement. Starting over here, things where you, a generic web server, CRM, email web search, this stuff on this end of the spectrum made sense for us to look at moving off-premise into a SaaS cloud offering. On the far right-hand corner, you have financial data, you have R&D, you have national or industrial security. This kind of stuff is stuff that you would, or what we said, this is the stuff we want to keep close to our vest, and we want to either on-prem on servers or in an internal cloud. And the stuff in the middle is the stuff that we needed to look at individually. It's not an easy answer. I think the far left and the far right here are the easy answers, and in the middle is you have to really look at what are these applications doing, what are these capabilities doing in the ERP space. Maybe you don't move your entire ERP into the cloud, but maybe you move pieces. And so this is what our findings were, so I'm sharing that here. So I'm going to give a couple of use cases, and I'm going to focus on the items that, or the use cases that Cloud Foundry is based, that the use cases that use Cloud Foundry, because this is the Cloud Foundry conference, we have a lot of other use cases for Cloud, but wanted to focus on just the ones for Cloud Foundry. So before I get to that, one of the key things, and I think I've heard it multiple times at this conference itself, service is the key. I'm from the developer world, and sometimes developers and systems engineers may not always see eye to eye on things. It reminds me of the Seinfeld soup guy where you go to him and say, can I please have a server? It says no server for you. That's the way it kind of fails to develop. You're like, hey, I just want to do my job. I want to develop this capability. And the systems engineers are always grumpy and they don't want to talk to you. So self-service is a key to enabling this whole experience with the internal Cloud. So we have an internal Cloud app platform. So this is based on Cloud Foundry. We have a database as a service offering, and then we have an infrastructure as a service offering, where if you actually need a VM with a lot more control, then we have that offering. When we analyzed the private versus public Cloud, I don't know where that's doing that, what you see here is you're moving to the Cloud. Moving to the Cloud, you're going to see your cost decrease, which is awesome. But what we actually saw is that the cost decrease was even more with the private Cloud, which was a little surprising because you would think, hey, in public Cloud, you would see more cost savings, but we actually saw more cost savings in the private Cloud, which is a little bit surprising. This scenario is a project that I actually worked on very closely. And I gave an entire session earlier today on this capability, just the short synopsis. About three years ago, we actually had two enterprise mobile platforms, and they were very complex and costly, and we decided to EOL both of them and actually move to a Cloud Foundry runtime for things like your mobile browser and for push notifications. And it was, in my mind, it was a leap of faith because I was very used to coming from an enterprise IT, software background, the vendor. It's a very nice thing to be able to call the vendor and complain to them, where now you're kind of the software vendor and they're going to get the complaints and you have no one to talk to because now it's your software. So it was a little bit scary, to be honest, but we went ahead with it, and it has been a great success, in my opinion. We've been in production for three years. We've seen a 50% reduction in our environment complexity. So we went down from two systems to one. We've reduced our hardware footprint by 90%. And it used to take 20 weeks to develop a mobile application on these other platforms, and the way we've moved to open source and Cloud Foundry, we can now do that in about three weeks and even shorter if it's extremely important. So huge win in the mobile space for Intel IT. And this next one is with open source. One thing that we are very aware of is, with open source, when you say open source, it's a huge category of software. There's anything from a little JavaScript library that's 10 lines long to millions of lines of code, is all open source. And so you have to be cognizant and mindful when you look at adopting open source and ensure that it's legal for you to use at your company, that it is secure. And so what we did is we actually created a catalog on top of Cloud Foundry where we list all of the approved libraries, open source libraries components that have been pre-approved for use from a legal perspective, pre-approved for use from a security perspective. And there's documentation on how it's actually to be used within Intel. So we stood up this open source catalog. We have several hundred users dispersed across the globe. It enables Intel to be secure and legally compliant because the last thing you want to do is get into legal troubles with software licensing. So the takeaway that I would hope that you would have from this is Cloud technologies, whatever they might be, accelerate your business. Focus on both the infrastructure and application transformation. Look at your workloads and analyze them and see what's best for your company. Look at them in the vectors that we had or make up your own vectors. But do a mindful approach to determining what you want to keep in-house and what you want to put on your private cloud in-house and what you want to put out into the public cloud and what you want to use SaaS vendors for. My recommendation would be to do a mindful approach and I think that's the main takeaway there. We believe the future is the hybrid cloud. We've been using Cloud Foundry now since 2014 and we've seen a great adoption and we're actually a part of the Cloud Foundry Foundation. We're a contributing member and if you have any questions about Intel at IT, you can click that link on the presentation and also some more information about the cloud at Intel. So I think that is it. So that is the presentation. I apologize for the delay that we had some technical difficulties but thanks for sticking with me to the very end of the conference. If you have any questions, feel free to come up to me afterwards. I'll be around for a few minutes. But thank you for coming.