 Good morning, everybody. My name is Bill Hilf, and I'm very pleased to be here with you this morning. I have only a few slides to share with you. What I'm going to spend most of my time on is talking to one of our customers here on stage. I think the customer stories that we're hearing yesterday and today, just now, earlier from Doug are the best indicator of where Cloud Foundry, the project, and the community, and its customers are today. Better than hearing vendor blather about what we're all doing to build products around Cloud Foundry. So I've been at Hula Packard Enterprise for three years, actually three years coming up in about a week. And it's been an absolute joy to work in the Cloud Foundry community and be part of the foundation and on the board. And I'm going to talk a lot about that, the importance of that, and some of the things that happen behind the scenes to make this all go. So I thought in the morning I would start off with all the corporate marketing slides, and then take you through deep marketing slides for about 20 minutes. Is that good? Everyone good with that? Awesome. No, actually, in reality, I want to make sure you understand why HPE is in the business of Cloud Foundry, why we are building products with Cloud Foundry, and why we're doing these things. A lot of people think of HP, classically, as a printer company, PC company, server, storage company. So often I'll get the question, why are you in the developer game? Why are you working with a Paz platform, an application platform? I want to take you through that a little bit before we go too deep. We spend a lot of time with our customers. We target the large enterprise and large governments. We target all sides of businesses, but I would say our focus primarily is on the very large enterprise. And so we do get the benefit, frankly, of working with customers and understanding their requirements, but also their complexity. And I'll just sum it up. For many of you have been in the space for a long time. I've been working with enterprises my entire career. And the CIO statement that best sums it up is something I've heard in many different languages in many different ways, although I only understand one language. So I'm presuming they're all saying something important to me when they speak in different languages, including Klingon, for all my Klingon friends out there. One of the things I hear a lot is, Bill, I have one of everything. I have every database that's essentially been created. I still run Spark systems. I talked to a customer yesterday that is the number one customer for side-based databases. They have more side-based databases than any customer in the world, and they're a very large bank. We have customers that run legacy systems, vintage systems, they call them sometimes. And these systems are frequently very, very strategic and critical to the way that business runs. Sometimes we naively think, particularly here in Silicon Valley, we naively think, ah, just cut those apron strings, silly enterprise, move to the new world. See the Facebook infrastructure, be like Google. Pull your own sheet metal, lay cork down. You can do it. And the reality is, that's not what these businesses do. These large enterprises are not in large-scale-out infrastructures where they can easily just roll out a distributed operating system in a way they go. Many of them have critical systems, sometimes life-critical systems, that need to work and grow as they build to the new. And so that is the genesis or the root of what we call hybrid. And so a lot of the work that we do at HPE is helping customers go through that journey of taking their existing business systems and building the new applications and new services. And in many cases, the new organizational and operational models around that entire environment. That's what hybrid means to us. So this first area that we call transform to a hybrid infrastructure is one of our core four transformation areas. These four slices of the pie represent the HPE strategy and how we see the different challenges that customers are having as they think about moving to a hybrid, protecting more and more in their enterprise as things become digitized, really empowering from analytics up the entire business. And of course, how do they enable their employees and workforce? But from the transformation to a hybrid infrastructure, this is absolutely where Cloud Foundry and our Helion portfolio, which is the name of our portfolio products for all the cloud things that we do, really fit because these are technologies that we're building to help customers build apps, build services that allow them to move across those traditional and new environments. You notice I don't use the words public and private a lot. I'm really trying my hardest. I really am to eliminate those words in front of the word cloud computing. I'm trying really hard to make public and private go away from our vernacular. Thank you. I will pay you later, Australian man. The reason why is, I think in five years' time, maybe longer, we'll look back at those words as very simple, in many cases, wrong. Because the enterprises that I talk to, and I talk to enterprise customers literally every day, do not think in this very simple, naive construct of I have a public thing and I have a private thing. They already run extremely hybrid environments across multiple data centers, some that they own, some that they don't. They're used to co-location, they're used to hosting, they're used to building their own, they're used to renting. So that's the reality that enterprises are in. So as we look at technologies that can help those customers move forward in their strategies and their agendas, Cloud Foundry, where the core value proposition is multicloud, fits perfectly for those types of customers. That's why you're hearing these awesome stories about what I think Doug said, 30% of his environment now running on Cloud Foundry at all state. That's awesome. I mean, that is frickin' awesome. I'm a customer of all state, I think it's awesome. Not Snapchat, not a new fangled company, but all state. And that's part of the reason that I think we should all be so excited here is it's not just happening for file new types of deployments and green field deployments and developers saying I'm gonna hack something up on my own and stand up. It's happening for mission critical systems. And that's a very special time this community is in. I've been fortunate to be part of open source communities at various points of their evolution. Probably the most notable one that I'm thinking of that's went through a similar evolution was the Apache project. And a lot of the things I'm seeing with Cloud Foundry remind me of that. Where there's a point in time where it literally goes non-linear and there's a breakthrough moment where the next thing you know, Apache became a verb to web servers. And that's happening now with Cloud Foundry. So rather than have me blather about it even longer, I'm gonna invite someone up to share some of these stories and I'm gonna talk with them about the journey they've gone through. This is a customer that has been dealing with large systems and large applications for a long time. And I'm gonna invite Jason up to talk to us a little bit about their journey and spend some time with us on stage with Jason. Come on up, Jason Armstrong from Travelport. Thanks for joining us, buddy. I didn't just select the other guy who was exactly my size out of the audience. But thanks for coming out and talking to us. Any time. So Jason, tell the group here about your role, what Travelport does. Some of the things you told me about Travelport, about the business that you're in and how these folks might be using Travelport but they don't even know it. Excellent, so welcome this morning. My name is Jason Armstrong. I'm a director of enterprise services and middleware at Travelport. Probably never heard of Travelport and that's okay. I'll share a little bit about it with you. Travelport is a travel commerce platform. So what we do is we work with those travel providers that you work with and they work with us and through our systems they can book, sell, share, search for any travel option through our travel products. For example, many of you flew in or probably stayed at a hotel this week. More than likely your travel provider is worked with Travelport in order to book, sell and reserve that travel for you. And so Travelport's been around about 40 years, is that right? Yep. And so what is your role at Travelport and then maybe tell us a little bit about why you chose Cloud Foundry. So my role at Travelport is to lead a team that's implementing lots of different tiers of our cloud strategies. So I have middleware, traditional engineers. I have the operating system type of engineers. I have the senior developers in a more creative area of cutting edge service development. Awesome. And when you were looking at technologies to choose or platforms to choose, what was it about Cloud Foundry that resonated? It was the vendor lockout and the option that with Cloud Foundry, we had one consistent way to be able to push content, to scale content, to develop applications. It's actually funny, one of the beauties of Cloud Foundry was it embraced the term that a lot of people at Travelport hadn't heard of, which is 12-factor apps. So to us, it's the add-on of by going to a Cloud Foundry solution where no matter which data center you're in within our complex of environments, whether that's cloud or within our personal data centers, it's the same experience for those developers. The engineers have some work in the back end to deal with different distributions, but for the development team, which is the core where our revenue comes from, they have that. And so I got to ask Jason, did you look at other options? Did you look at other cloud technologies or other application platform options before you made that decision? Absolutely. We actually evaluated for a period of about six months all of the different options for cloud frameworks. Everything from Docker, Ansible, there's lots of vendor solutions I can name. You all probably know them very well. And we kept coming back to it each time that we looked at the different flavors. We really looked at Cloud Foundry as, wait a second, there's an open source community, it's very robust. Our goal was to create an environment where we could implement best practices in the community. All of you out here are the ones that kind of convinced us to go to Cloud Foundry because you convinced us that there are best practices that could increase our productivity. There was best practices that would enable us to deploy faster, and there was best practices for how to cut our costs by using a centralized system like Cloud Foundry. Awesome. One thing that we talked about in, I think this is maybe one of the most important aspects of the transition that we see customers go through is the technology, certain, there's tons of technologies out here. The technology is one aspect of moving to a cloud-native application platform. But something that Doug also mentioned this morning, tell me a little bit about the organization. As you moved, as you shifted left, both metaphorically and literally, as you shifted left, what happened to the org? What happened to the culture at Travelport? Or what's happening? Because I know it's in progress. Yeah, it's currently in progress. And what we're seeing so far is that by shifting left, and there's a love-hate relationship with the word DevOps, but shift left is the friendly term we use for it, which means we're pushing more responsibility to the left side of the diagram where traditionally development people are. So the development community is taking on roles such as coordinating their builds, doing their own regression testing, managing their deployments, production support. But in fairness, that leaves the right side of the diagram able to spend more time keeping the infrastructure up for those development teams. So where traditionally they were spending a lot of time in the infrastructure side, troubleshooting services and helping memory tune and other things. With Cloud Foundry, what we're seeing is a shift where those responsibilities for tuning and tweaking applications have moved to left. And the operation side is now focused on can I keep my servers up? Is my monitoring resilient? How are my customer experiences? Awesome. And for customers out there in the audience, what would you recommend? What tips would you give them as they're, because you're on the journey. As some are considering, how do we get there? Because I talked to someone last night who's literally here just taking notes and learning before they take the first step. What would you recommend to them? That's a great step. The community is excellent. Like I said, kudos out to all of you for being such a great community because you're responsive. When people post items to boards, you're very responsive. So I'd encourage them to go out to the community and find out how they're working. Go up to the meetups and things like that. The other important thing as a big enterprise, and I make no qualms about it, where a big mainframe shop that has a whole lot of open systems around it, it's hard to shift your organizations. So you really need to brace them and bring them into the process. So where we brought in our network team and said, look, look at how many firewall requests you don't have to do. Look how many load balancer requests you do not have to do anymore. You can spend more time looking at the cool new load balancer strategy versus having to worry about, oh, I have to implement 15 new load balancer requests today. So by kind of bringing them into that process, security, server engineering, all of them, they really got excited about the possibilities, how they can have more time to do the cool things. Great. And Jason, one last thing, a year from now, what does success look like? So you're in the process of this and the organization's moving there. Where do you want to be in a year? In a year, we're hoping to move many of our microservice APIs. So again, the pieces of our travel commerce platform that agencies and travel providers are hooking into to have them hosted closer to those vendors. So success is basically having Cloud Foundry instances running both in our data center and across the globe where we can actually have an experience where an Australian agency calls an Australian service which we happen to know that the data's coming from the Australian airline. Why come back all the way to the United States to our personal data center just to go back out to Australia to get that data? Again, success for us is being able to co-host that with the benefit of reducing that development time, reducing that deployment time. That's an extremely important part for us. We're a very quick moving industry in travel and if you don't keep up, you're gonna quickly get behind and those nimble deployments and processes are what we're looking for. Jason, thank you very much, man. Thank you. Appreciate it. Thank you. I think what the theme that you're also seeing from all state and travel port is, these are businesses that had to make this transition that would be out of business if they were not moving this direction and taking advantage of the things that we're seeing with Cloud Native application platforms. So it's something we were talking about backstage a little bit. It's not so much, hey, could we do something like that? Would that be interesting? It's really survivability. How do you make a get to the point where you're able to work at the speed of development and reach your customers at the speed of development because times become the critical variable in extracting and delivering value to customers. I got just a couple more things I wanna talk about. One is about this slide here and I'll tell you six, seven years ago when I first really, really started spending time with large enterprises and government agencies about cloud computing just generally, I would never have predicted this slide seven years ago. I would not have guessed that all of these types of vendors and customers would come together in some sort of community to build something related to cloud computing. And to see how far, and this isn't just a marketplace where people stuck up their logos and some NASCAR-like experience to slap something up on a slide. To get on the slide means you're putting contrivial money and time into being part of the foundation. And I mean, it's real time. Like there's real work that happens to make, for all of these members to participate. And I think this here, and if you just look at some of the brands on here, look at the six I think that were announced yesterday that came into the foundation. It's truly remarkable. And I don't think it's because we're all just happy, go lucky guys and gals that like to get together. I'd love to believe that, but I'm not as, Sam does a better job of the Zen stuff. Like I'll let Sam stay in that zone. I believe this is because the commercial market is demanding it. I believe because we're in a different phase of cloud computing, where it's becoming much more synonymous with IT. I think the word cloud is starting to mean IT in many ways. And so because of that and the large complex heterogeneous requirements that enterprises have, this the market has demanded a multi-cloud application platform. That's why this group exists and that's why it's come together. But I just wanted to say thanks to all the members who've been part of this. And I would say even a year and a half ago or so when the foundation was just being thought of, or a couple of years ago, I don't think anyone would have guessed the amount of membership and the growth of this community. It's truly remarkable. And take a moment really at why you're here to have deep and authentic conversations with people in this community because I think Cloud Foundry really is at that liminal moment of growth. That's exciting. So as part of that, one of the things that we do at HPE is we want to help continue that growth. So we're announcing today a new dojo in Seattle that is open now. And this is the one picture that we took of Seattle that didn't have rain and clouds. But it looks really nice. We call this interview weather when we're trying to hire people. But we're really excited by this. And the model of how, and many thanks to Pivotal for helping establish the model that exists for how contributions happen and how you build high quality software. And we're very happy to participate by opening a Seattle-based dojo. We're not doing this because it's just my hometown. Maybe kind of. We're actually doing this because there's a very large growing ecosystem in the Seattle and the Puget Sound area around cloud computing. There's a couple really big players in the market there in terms of Microsoft and Amazon. But that's also created a pretty significant ecosystem of other startups and a pretty big developer community. So we're very happy to be hosting that dojo in Seattle starting today. I would also add, as you think about the, one of the fun parts of coming to events like this is I ran into literally eight people, eight, who have all worked for me in different companies all out that I met in the outside of this room. And they're all at different companies now, eight different companies. And I would like to think they're all here because I'm so terribly charming and they came to see their old boss. That's not it. They've all gone off to different roles where now Cloud Foundry is seated all over in these different companies, some vendors, some customers, some people doing services business, businesses around Cloud Foundry. And that ecosystem, just think how fast this has happened in the amount of time that growth has happened. It's pretty remarkable. So with that, I'm going to close. I'm going to give you my email address and my Twitter handle. I do want to have your feedback on how things are going, not just with HPE and what we're doing. Certainly to take any feedback except about my hair and being bald. Can't tweet about that. I get really, really sensitive on that subject. That's because I'm not Australian. But I do want to hear from you how you think the Cloud Foundry project is going as well because there's a lot of still shaping and molding and growth that's happening in this project which makes it so vibrant and exciting to be part of. So feel free to shoot me email with your ideas and thoughts. With that, thank you very much. Have a great time for the rest of the event.