>> Announcer: From San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hey, welcome back everyone. This is theCUBE live here in San Francisco at Moscone West Fourth, Red Hat Summit 2018. I'm John Furrier, the co-host of theCUBE with John Troyer, the co-founder of TechReckoning, an advisory firm in the area of open source communities and technology. Our next guest is Cube alumni Dietmar Fauser, head of core platforms and middleware at Amadeus, experienced Red Hatter, event go-er, and practitioner. Great to have you back, great to see you. >> Thank you, good to be here. >> So why are you here, what's going on? Tell us the latest and greatest. What's going on in your world? Obviously, you've been on theCUBE. You go on YouTube, there's a lot of videos on there, you go into great detail on. You been on the Docker journey. You got Red Hat, you got some Oracle. You got a complex environment. You're managing cloud native-like services. Tell us about it. >> We do so, yes, so this time I am here mostly to feed back some experience of concrete implementation out there in the Cloud and on premise so. Paul told me that the theme was mostly hybrid cloud deployments so we have chosen two of our really big applications to explain how concretely this works out with you and when you deploy on the Cloud. >> So you were up on stage this morning in the keynote. I think the scale of your operation maybe raised some eyebrows as well. You're talking about over a trillion transactions. Can you talk a little bit about, talk about your multi-cloud stance and what you showed this morning. >> Okay, so first to frame a bit of the trillion transactions. It's not traditional data based transactions. It's individual data access and highly in-memory cached environment. So I'd say that's a very large number and it's a significant challenge to produce this system. So we're talking about like more than 100,000 core deployments of this applications so. Response time matters extremely in this game because at the end what we are talking here about is the back end that powers large P2C sites, like Kayak, some major search engines, online travel agencies. So it just has to respond in a very fast way. Which pushed us to deploy the solutions very close to where the transactions are really originating to avoid our historical data centers in Germany. We just want to take out the back and forth travel under the Atlantic basically to create a better end user experience at the end. >> Furrier: So you had to drive performance big time? >> We, very much. It's either performance or higher availability or both actually. >> This is a true hybrid cloud, right? You're on prem, you're in AWS, and you're in Google Cloud. So could you talk a little bit about that? All powered by OpenShift. >> OpenShift is the common denominator of the solutions. Some of our core design goals is to build the applications in a platform agnostic way. So an application should not know what's its deployment topology, what's the underlying infrastructure. Which is why I believe that platforms like OpenShift and Kubernetes underneath are so important, because they take over the role of a traditional operating system, but at a larger scale. Either in big Cloud deployments or on premise, but the span of operations that you get with these environments is just like an OS but on a bigger scale. It's not a surprise that people talked about this like a data center operating system for a while. We use it this way so OpenShift is clearly the masterpiece, I would say of the deployment. >> That's the key though, I think, thinking about it as an operating system or an operating environment is the kind of the architectural mindset that you have to be in. Because you've got to look at these resources and connections, link them together. You've got all these team systems constant. So you've got to be a systems person kind of design. How does someone get there that may or may not have traditional systems experience? Like us surly generation systems folks have gone through. Because you have devops automating away things. You have more of an SRE model that Google's talking about. Talking about large scale, it's not a data center anymore, it's an operating environment. How do people get there? What's your recommendation, how do I learn more. What do I do to deploy architecturally? >> That's a key question I think. I think there were two sections to your question, how to get there, so. I think at Amadeus we are pretty good at catching early big trends in the industry. We are very close to large engineering houses like Google and Facebook and others like Red Hat of course and so, it was pretty quickly clear to us, at least to a small amount of these decision-makers that the combination of Red Hat and Google was kind of, a game-changing event, which is why we went there, so. It's, I mean. >> Furrier: The containers have been important for you guys. >> Containers were coming along, so, when this happened Docker became big, our development teams, they wanted to do containers. It was not something that the management has had to push for, it was grassroots type of adoption here. So different pieces fed together that gave us some form of certainty, or a belief that these platforms would be around for a decade to come. >> Developers love Kubernetes, and I mean that, containers, it's like a fish to water, it's just natural. Now talk about Kubernetes now, OpenShift made a bet with Kubernetes, obviously, a few years ago. People were like, what is that about? Now it's obvious why. How are you looking at the Kubernetes trade, obviously it creates a de facto capability, you can wrap services around it, there's a notion of service meshes coming, Istio is the hottest product in the Linux Foundation, CNCF, KubeFlow is right behind it, I mean these are kind of thinking about service and micro-services and workload management. How do you view that, what's your opinion on that direction? >> I'm afraid there is no simple answer to this, because if you start new solutions from scratch, going directly to Kubernetes, OpenShift is the natural way. Now the big thing in large corporations is we all have legacy applications, whatever we call legacy applications, in our case these are pretty large C++ environments that are relatively modern but they are not strictly micro-service based and they are a bit fatter, they have an enterprise service bus on top of this, and so it's not, and we have very awkward, old network protocols, so going straight to the mesh for these applications and micro-services is not a possibility because there is significant re-engineering needed in our own applications before we believe it makes sense to throw them onto a container platform. We could stick all of this in a container but you have to wonder whether you get the benefit you really want to. >> Furrier: Time ROI, return on investment, on the engineering, retrofitting it for service mesh. >> Yes, I mean, the interesting thing is Kubernetes or not, we would have touched these applications anyway to cut them into more manageable pieces. We call this compartmentalization. Other people may call this micro-service-ification, or however we want to call this. So that's, to me this is work that is independent from the cloud strategy in itself. Some of our applications, to move faster, we have decided to put them more or less as they are onto OpenShift, others we take some more time to say, okay let's do the engineering homework first so that we reap the full benefits of this platform, and the benefit really is, what is fundamental for developers, efficiency and agility is that you have relatively small, independent load sets, so that you can quickly load small pieces, you can roll them in. >> Time to production, time from developer to production. >> But also quality, the less isolated, the more you isolate the changes, the less you run the risk that a change is cross-impacting things that are in the same delivery basically. It's a lot about, smaller chunks of software that are managed and for this obviously a micro-service platform is absolutely ideal. So it helps us to push the spirit of the company in this direction, no more monolithical applications, fast daily loads. >> Morale's higher, people happy. >> Well, it's a long journey, so some are happy, some are impatient like me to move faster. Some are still a bit reluctant, it's normal in larger organizations. >> Talk about the scale, I'm really interested in your reaction and experience, let's talk about the scale. I think that's a big story. As cloud enables more horizontally scalable applications, the operating aperture is bigger. It's not like managing systems here, it's a little bit bigger picture. How are you guys looking at the operational framework of that, because now you're essentially a site reliable engineering role, that's what Google talks, in SRE, but now you're operating but you're still developing code, and you're writing applications. So, talk about that dynamic and how you see that playing out going forward. >> So, what we try to do is to separate the platform aspects from the application aspects, so I'm leading the platform engineering unit, including platform operations, so this means that we have the platform SRE role, if you want, so we oversee frontline operations 24 by seven stability of the global system. To me, the game is really about trying to separate and isolate as much as we can from the applications to put it on the platform because we have, like, close to 100 applications running on the platform and if we can fix stuff on the platform for all the applications without being involved in the individual load cycles and waiting for them to integrate some features, we just move much faster. >> You can decouple the application from some core platform features, make them highly cohesive, sounds like an operating system to me. >> It is, and I'll come to the second thought of the SRE a bit later, but currently the big bulk of the work we are doing with OpenShift is now to bring our classical platform stuff under OpenShift. And by classical application, I mean our internal components like security, business rule engines, communication systems, but also the data management side of the house. And I think this is what we're going to witness over the next two or three years, is how can we manage, like, in our case CouchBase, Kafka, all of those things, we want them to be managed as applications under OpenShift with descriptive blueprints, descriptive configurations which means you define the to-be state of a system and you leave OpenShift to ensure that if the to-be state is like, I need 1000 ports for a given application, is violated OpenShift will repair automatically the system. >> That's interesting, you bring up a dynamic that's a trend we're seeing, I want to get your thoughts on this. And it hasn't really been kind of crystallized and yet I haven't heard a good explanation but, the trend seems to be to have many databases. In other words, we're living in a world where there's a database for everything, but not one database. So, like, if I got an application at the edge of the network, it can have its own database, so we shouldn't have to design around a database concept, it should be, concept should still be databases everything, living and growing and managing it. How are, first of all do you believe that, and if so, how do you architect the platform to manage potentially ubiquitous amount of different kinds of databases where the apps are kind of driving their own database role, and working with the core platform. Seems to be an area people are really talking about, because this is where AI shines if you get that right. >> So I agree with you that there are a lot of solutions out there. Sometimes a bit confusing choice, which type of solutions to choose. In our case we have quite a mature, what we call a technical policy, a catalog of technologies that application designers can choose from, so there are several data management stores in there. Traditionally speaking we use Oracle, so Oracle is there and is a good solution for many use cases. We were very early in the Nosql space so we have introduced Couchbase for highly scalable environments, Mongo for more sophisticated objects or operations. We try to educate, or to talk with our application people not to go outside of this. We also use Redis for our platform internal things, so we try to narrow their choices down. >> Stack the databases, what about the glue layer? Any kind of glue layer standards, gluing things together? >> In general we always put an API layer on top of the solutions, so we use our own infrastructure independence layer when we talk to the databases, so we try not to have those native bindings in the application, it's always about disentangling platform aspects from the application. >> So Dietmar, you did talk about this architectural concept, right, of these layers, and you're protecting the application from the platform, what about underneath, right? You're running on multiple clouds. What have been the challenges of, in theory, you know, there's a separation layer there and OpenShift is underneath everything, you've got OpenStack, you've got the public clouds, have there been some challenges operationally in making sure everything runs the same? >> There are multiple challenges, so to start with, the different infrastructures do not behave exactly the same, so just taking something from Google to Amazon, it works in theory but practically speaking the APIs are not exactly the same, so you need to remap the APIs. The underlying behavior is not exactly the same. In general from an application design point of view, and we are pretty used to this anyway because we are distributed systems specialists, but the learning curve comes from the fact that you go to an infrastructure that is, in itself, much less reliable if you look to individual pieces of it. It works fine if you use well the availabilities on concepts and you start with the mindset that you can lose availabilities or even complete regions and take this as a granted, natural event that will happen. If you are in this mindset there aren't so many surprises, OpenShift operates very well with the unreliability of virtual machines. We even contract, in the case of Google, what is called preemptive VM so they get restarted anyway very frequently because they have a different value proposition so if you can run with less reliable stuff you pay less, basically. So if you can take advantage of this, you have another advantage using those. >> Dietmar, it's great to hear your stories, congratulations on your success and all the work you're doing, it's sounds like really cutting-edge and great work. You've been to many Red Hats. What's the revelation this year? What's the big thing that people should know about that's happening in 2018? Is it Kubernetes? What should people pay attention to from your opinion? >> I think we can take Kubernetes now as granted. That's very good news for me and for Amadeus, it was quite a bet at the beginning but we see this now as the de facto standard, and so I think people can now relax and say, okay this is one of the pieces that will be predominant for the decade to come. Usually I'm referring to IT decades, only three years long, not 10 years. >> Okay, and as moving to an operating system environment, I love that analogy. I think it's totally right from the data that we see. We're living in a cloud native world, hybrid cloud on-premise, still true private cloud as Wikibon calls it and really it's an operating system concept architecturally, and IoT is coming fast. It's just going to create more and more data. >> So, what I believe, and what we believe in general at Amadeus is that the next evolution of systems, the big architectural design approach will be to create applications that are much more streaming oriented because it allows to decouple the different computing steps much more. So rather than waiting for a transaction, you subscribe to an event, and any number of processes can subscribe to an event, the producer doesn't have to know who is consuming what, so we go streaming data-centric and massively asynchronous. Which, which, which yields smoother throughput, less hiccups because in transactional systems you always have something that slows down temporarily a little bit, it's very difficult to architect systems with absolute separation of concerns in mind, so sometimes a slowdown of a disk might trigger impacts to other systems. With a streaming and asynchronous approach the systems tend to be much more stable with higher throughput. >> And a lot more scalable. There's the horizontally scalable nature of the cloud, you've got to have the streaming and this architecture in place. This is a fundamental mistake we see with people out there, they don't think like this but then when they hit scale points, it breaks. >> Absolutely, and so, I mean we are a highly transactional shop but many of our use cases already are asynchronous so we go a deep step further on this and we currently work on bringing Kafka massively under OpenShift because we're going to use Kafka to connect data center footprints for all types of data that we have to stream to the application that are out in the public cloud, or on premise basically. >> We should call you professor because this was such a great segment, thanks for sharing an awesome amount of insight on theCube. Thanks for coming on, good to see you again. Dietmar Fauser, head of core platforms and middleware at Amadeus. You know, down and dirty, getting under the hood really at the architecture of scale, high availability, high performance of the systems to be scalable with cloud, obviously open source is powering it, OpenShift and Red Hat. It's theCube bringing you all the power here in San Francisco for Red Hat Summit 2018. I'm John Furrier and John Troyer, we'll be back with more after this short break. (electronic music)

(upbeat electronic music) >> Announcer: Live from Santa Clara, California, it's theCUBE covering Open Networking Summit 2017. Brought to you by The Linux Foundation. >> Hey, welcome back, everybody, Jeff Frick here with theCUBE. We are in Santa Clara, California at the Open Networking Summit 2017. Really happy to be joined by my co-host for the next couple of days, Scott Raynovich. And we've been talking to a lot of providers and technical people, but now we want to talk to customers. We love talking to customers, and we're really excited to have Rashesh Jethi. He's the SVP, Head of R&D for the Americas for Amadeus, which is a big travel company. Welcome. >> Thank you so much, Jeff. Thank you, Scott. >> So like I said, we'd love to talk to a practitioner. So you're out on the frontlines, you're seeing all this talk of software-defined and software-defined networking. From your point of view, how real is it, where are we on this journey? What do you see from your point of view? >> Super real. Have you searched for a flight lately? >> I have searched for a flight. >> Excellent. I'm proud to tell you that your flight search very likely was powered by Amadeus, and it's running on a software-defined data center completely. So this stuff is real. We are, I believe, one of the first companies who have actually taken this from what was a very strong academic kind of research project onto this start-up ecosystem, but we're actually out there deploying it, running real world business, using a very purposeful and deliberate software-defined strategy. >> And it's interesting because you said before we got on camera that you guys are actually very active participants in the open source movement and development of this stuff. You're not just kind of a participant waiting in the wings for this stuff to get developed. >> I mean absolutely, and to me, that's one of the reasons which if you're serious about open source, you have to use it. You can't just talk about it. You can't just say it looks like a nice idea. You have to get out there and get your hands dirty and do it. But the other thing also is you have to contribute back. I think that's a big tenet of the open source community. And we all and certainly the company, we grew up and we've seen tech evolve through the ages. And a big part, especially in the last 10 years or so, has been the open source movement, and it's contributing back. It's one of the reasons I'm here. It's one of the reasons the conference organizers invited me, is to actually talk about how we use open source and software-defined strategy for our technology. >> That's cool. So where do you run this software? You run it in private cloud, public cloud? Do you guys build your own data centers? How do you run it? >> Quick history lesson and our quick history-- >> Let's back up. First off, where is Amadeus today for people that aren't familiar with the company? >> We are actually a 30-year-old company. We are celebrating our 30th birthday this year. The company was started in the late '80s as a consortium between four leading European airlines, Lufthansa, Air France, Iberia, and Scandinavian. So we started off, which was very typical at that time, as a mainframe shop, and that's where a lot of our core systems were built. We're a big provider of technology in general to the travel industry even though we were founded by airlines. So to put it in perspective, we carry about 95% of the world's scheduled commercial seats, airline seats, on our platform. >> 95%. >> 95%, so we work with the world's-- >> Are available to purchase. Obviously, 95% of the purchases don't go through your system. >> Right. They are available. They are used by over 90,000 travel agents, retail travel agents, corporate travel, online travel. And we work with over, like I said, 700 airlines, work for their inventory. So chances are if you travel on an airplane, very good chances that our software was used to make the reservation. We also have airline ID systems and hotel ID systems, and we work with the airports. And this is where we do departure control, flight management, baggage reconciliation, a lot of the back end processes. And we started the company, essentially runs as we write our own software. We are offered as a service from day one, so we are one of the oldest software service providers in the industry. And obviously, when we got started to do that, you had to own your own infrastructure. So we are pretty good at it. We have very strong kind of technical chops. We have a large data center outside Munich Airport and a bunch of smaller data centers all over the world. And what we're doing now is really very deliberately making the journey towards a cloud, both our private cloud, so taking our own infrastructure, virtualizing it, and making it available as a service for our own applications, and then where it makes sense, to leverage public cloud infrastructures where they are available. >> So different apps in different clouds, is that-- >> Different apps in different clouds based on customer preferences. The core reservation booking engines, they are in our own private cloud because we do have a lot of regulatory security, privacy considerations. So that stuff, we keep kind of close where we can keep a very watchful eye on it, but there are a lot of transactions we are also talking about. The volume of searches has grown up, right? Obviously, Google has seen a lot of search volume. If you look at our business, it used to be when you wanted to book a flight, you'd go to a travel agent and be able to look at a bunch of flight options and you'd pick one. About 20 years ago, you call it the look to book ratios. You'd look at 10 to 20 options and you'd book one. You want to guess what it is today? >> The look to book ratio was 20 to one. That's got to be way higher. That's got to be 80 to one. >> It's more like 1,000 to one. >> 1,000 to one. >> 1,000 to one. It's partly people like you and I who have a spare moment and have a vacation in mind, and we are looking at options. But keep in mind, anything that you search, it has to come into our systems. We have to configure the journey. We have to price it. We have to make sure it's available before we offer it up to you, right? So it's very transaction and computing intensive even before it touches any of the back ends where we do core kind of booking and passenger processing. And so to handle that scale, those are the kind of very logical applications that make sense for the public cloud. And those are the ones that we've looked to move. Certainly, for customers, we are a global company. We have customers all over the world. Some customers want to have some of these systems closer to their geographic location. So we look at all use cases kind of. >> That's amazing to think of. These things have so changed behavior and the way that we interact. I assume that 20 to one was a function because you would sit down. Now you sit down at your desk, time to book that flight, and maybe you don't get it done that day. You come back two or three times. But as you said, now it's grabbing little bits of time throughout the day whenever we can. But do you get paid on a regular subscription, or do you get paid on the transaction? Has that just increased your overhead, whatever the ratio 20 to 1,000 is? >> Absolutely, no, our business model has been very consistent from day one. We get paid on the number of bookings we make and the number of people that board aircraft, I mean roughly speaking. There are smaller lines of businesses, but those are our two main revenue drivers. So we see a lot of transaction volume upfront, but it doesn't translate to a booking which logically, it won't. Yes, that's noise or revenue for us, but we still have to service that volume because that's eventually, the funnels just gotten wider. And so it makes sense to do that in the most cost efficient manner but without compromising quality, without compromising speed. I mean if you're like me, if you have to wait for more than two or three seconds, you're like, "Ah, I'm moving on." >> Oh, two seconds. It's milliseconds, isn't it? >> Absolutely. >> And by the way, I still don't always find the flight I want. So where are those extra flights? Can you provide those for your service? >> Jeff: That extra 5% those are under. >> That's very different. It's got nothing to do with open source and kind of what we're talking about here, but a lot of what you're doing in there from an engineering perspective is just looking at, for example, machine learning algorithms. And what you said is actually a very common complaint, is how do I find kind of the right sort of flights. And more importantly, if you have certain preferences with airports or airlines or loyalty programs or time of day, how do I provide you context-sensitive results? We are doing a lot of kind of core R&D work for that, but our customers are doing amazing work as well. KAYAK is one of our customers, very close to our offices in the Boston area, and they do pretty amazing work in terms of getting their context right and then applying machine learning technologies and artificial intelligence. It's very, very early days but very exciting, very promising. >> One of the cool features I like are these fare alerts. I don't know if you use them. It tells you, it predicts this is going to go up. You better book now, wait. Do you guys do that sort of thing too? >> Our customers do that. We have a very simple model. Our customers are travel agencies, online, American Express, Expedia, metasearches like KAYAK, Skyscanner, et cetera, the airlines themselves whose products we host in our system and we sell. So a lot of our engineering work is learning to offering kind of core innovation so that they can offer products for people like you and me, their customers, the best products out there. So we focus on enabling them. And then at an operational level, we try to do it in the most efficient manner and the most future proof that we can think of. >> What about security? I mean it sounds like a lot of sensitive data changing hands here, right, where are people going to sit on an airplane, where are they going. You must have incredible security demands on your data now. >> Yes. (Jeff and Scott laugh) I mean you understand, obviously, it's paramount to us. And the good news is, look, we've been in this business for 30 years. We have really deep domain expertise in that. And also, you'll understand why I wouldn't want to talk too much about what we do and how we do it, but absolutely, that's one of the-- >> Scott: You just lock it down. >> Prime drivers of everything we think all the way from application design to things like the infrastructure planning and design to the physical level. I mean everything you can think of and probably a couple of things you may not think of. >> Hopefully a few things we didn't think of. So where do you go next? It sounds like you're enabling a lot of the innovation on your partner's side. You just mentioned KAYAK and people writing some of the machine learning and AI algorithms to help the end traveler find what they're looking for. Where are you guys concentrating? You said you've been at it for 30 years. What are some of the next big hurdles that you're looking to take down? >> It's wonderful, I think, being close to our customers. And one of the reasons I'm in Boston, we are a European company. We are actually headquartered in Madrid. Our core engineering team, our central engineering team is in France. The reason I'm in Boston and my team is in Boston is we've started doing a lot of business here in North America, and we try to stay very close to our customers. And when you listen carefully, and that's why we have two ears and one mouth is to hopefully try to listen a lot, you do see their pain points, you do see where they are going with kind of their business. And it gives us a chance to have a front row seat in designing new products that they can use. So to me, it's kind of two pronged. One is we want to offer the best technology we can to our customers at the best price point we can. And obviously, by now, you've figured out it's mission critical stuff has to always be on. Keeping those kind of boundary conditions in mind, you want to be the best technology provider, and then we want to innovate. So one of the things I'm seeing at this conference, there's a lot of friends from the service providers who are talking about 5G technology. And so with connected cars, with virtual reality, I mean these are all trends that are going to impact us as travelers in a positive way. And so we have a dedicated innovation team across all our business lines. We do a lot of work with academic institutions, with ETH in Zurich, with MIT here, close to my office in Boston. And there's just a chockfull of possibilities in terms of what can be done. >> All right, I'll give you the last word, impressions on the show. What do you get out of a show like this? Why is it important for you to come? >> It's amazing. I mean this morning, Martin Casado was there. He's called kind of the grand daddy of software-defined networking (mumbles). >> He's not that old yet, but he's going to like seeing that clip. (laughs) >> It's true. I read that at The Guardian. It was on one of the newspapers. But the fact is we used NSX for virtualization in our entire data center, and we have close to 20,000 infrastructure devices. All our computers are virtualized, 100% of it, and it's all using NSX from VMware, right? Now this was a sort of brilliant idea by an extremely intelligent and persuasive graduate student at Stanford 15 years ago that is, as he announced this morning, is a billion-dollar business today, right? And we are actually using the technology, and it's very real, to process all of this. So it's great to be able to see what people like him, I mean from Google, he's a great partner of ours. We use Kubernetes for kind of the container deployment strategy for our cloud network. We hear him speak about what they're thinking about in terms of investments and how the network is going to essentially drive the movement of data analytics. It's just phenomenal to get the top leadership. I'm obviously very honored and privileged to be presenting to this audience and to share our thoughts and what we're doing and just to see a lot of the buzz around here and what wonderful ideas are happening in the Valley. There's so much action, as always, going on. >> Great, great, great summary. Well, glad you could take a few minutes to stop by theCUBE. >> Completely my pleasure. Thank you very much. Great meeting you, and have a great rest of the show. >> All right. He's Rashesh, he's Scott, I'm Jeff. You're watching theCUBE from Open Networking Summit 2017 in Santa Clara. We'll be back after this short break. Thanks for watching. (upbeat electronic music) >> Announcer: Robert Herjavec. >> People obviously know you from Shark Tank, but The Herjavec Group has been really laser focused on cybersecurity. >> I actually helped to bring upon Checkpoint to (mumbles) firewalls, URL filtering, that kind of stuff. >> But you're also...

>>Oh, welcome back to the Cube here at aws Reinvent 22. As we continue our coverage here, the AWS Global Showcase, the Startup Showcase, John Wall is here hosting for the Cube as we've been here all week. Hope you're enjoying our coverage here. This is day three, by the way. We're wrapping it up shortly with us to talk about what's going on in the, kind of the hotel world in it and what's going on in the cloud, especially at I hg is Eric Norman, head of infrastructure, architecture, and innovation at I H G Hotels and Resorts. Eric, good to see you, >>Sir. Oh, thank you. And thank you for inviting me. Yeah, >>You bet. Glad to have you board here on the queue. First time, I think too, by the way, right? >>It is. And can I just tell you who IHG is >>Real quick? Yeah, wait a second. First I want another rest. I got Introduc to Rod Stuller, who is the Vice president and of Solutions marketing at Aviatrix and Rod. Good to see you, sir. Thanks a lot. Now let's talk about I ih. >>Great. Well, IHGs a a hospitality company, it's been around for 200 years, that has 17 brands globally in over a hundred countries. We sleek, you know, up could up to 888,000 people a night. So it's a pretty large company that we compete with, you know, all the hotel companies globally. >>So let's talk about your, your footprint right now in, in terms of what your needs are, because you've mentioned obviously a lot of, you have a lot of customers needs, you have a lot of internal stakeholder needs. Yeah. So just from that perspective, how are you balancing out, you know, the products you wanna launch as opposed to the, on the development side and the maintenance side? >>Yeah, I mean we, we have focused our, our attention to our, our guests and our hotels globally and, and taking technology and from a foundation, getting it at, at the edge so that way the consumer and the hotel owner can deliver a quality product to a guest experience. You know, we've have moved larger, a large deployment of our mission critical applications over the last five years really, of moving into more SaaS and infrastructure like AWS and GCP and, and leveraging their global scale to be able to deliver at the edge or get closer to the edge. And so we've, you know, I'm pretty sure you've seen, you know, kind of people building, you know, mission critical apps. You know, probably in the last three years it's probably escalating and more of like a hockey stick of moving stuff. I'd love to hear what AVIA is seeing. Oh >>Yeah. Now we're, we're seeing that quite a bit, right? As people move into the cloud, it's now business critical applications that are going there. So good enough isn't good enough anymore, right? It has to be, you know, a powerful capability that's business critical, can support that, give people the ability to troubleshoot it when something goes wrong. And then multi-cloud, you mentioned a couple different cloud companies, a lot of enterprises are moving to multiple clouds and you don't want to have to do it differently in every cloud. You want a infrastructure management layer that allows you to do that across >>Clouds. So how do you go about that, you know, deciding what goes where. I mean, it sounds like a simple question, but, but if you are dealing in a lot of different kinds of environments, different needs and different requirements, whatever, you know, how are you sorting out, delegating, you know, you know, you're, you're you're gonna be working here, you're gonna be >>Working there. Yeah. So we built some standards base that says, you know, certain types of apps, you know, transactional base, you know, go to this cloud provider and data analytics that's gonna go to another, another cloud provider based on our decision of key capability, native capability, and, and also coverage. You know, cuz we are in China, right? You know, you know, I, I've gotta be able to get into China and, and build not only a network that can support that, but also business apps locally to meet, compete with compliance, regulatory type activities. I mean, even in, in the US market, I got, you know, California privacy laws, you know, you have globally, you've gotta deal with getting data applications into compliance for those globally, right? >>Yeah. So, so you got that compliance slash governance Yeah. Issue. Huge issue. Yeah. I would think for you, you gotta decide who's gonna get to what when, and also we have to meet certain regulatory standards as you pointed out. And not just there, but you got European footprint, right? I mean, you're global. Yeah. So, so you know, handling that kind of scope or scale, what kind of nightmares or challenges does that provide you and how's Aviatrix helping you solve >>That? Yeah, in the early days, you know, we were using cloud native, you know, constructs for networking and a little bit of a security type angle to it. What we found was, you know, you can't get the automation you need. You can't get the, the scalability, you know, cuz we're, we're trying to shift left our, you know, our DevOps and our ability to deploy infrastructure. Aviatrix had come in and, and provided a, a solution that gets us there quicker than anybody else. It's allow us to, you know, build a mesh network across all our regions globally. I'm able to deploy, you know, new landing zones or, you know, public cloud fairly quickly with my, you know, networking construct. We also, we found that because we are a multi hybrid cloud, we, we introduced on the edge a a new network. We had to introduce a performance hub architecture that's using Equinix that sits in every region in every public cloud and partner. Cuz all our partners, you know, we, we've moved a lot of stuff to sas. You know, Amadeus is our centralized reservation system. That's our key, you know? Sure. You know, reservation tool, it's so sourced out. I need to bring them in and I need to get data that's closer to where, in a region to where it needs the land so I can process it. Right. >>And it's a big world out there too. I mean, you're, you're not in your head Rod. So talk about if you would share some of the, the aviatrix experience in that regard. When you have a client like this that has these, you know, multinational locations and, and yet you're looking for some consistency and some uniformity. You don't, you know, you can't be reinventing the wheel every time something pops up, right? >>Right. No. And then, and it's about agility and speed and, you know, being able to do it with less people than you used to have to do things, right? You, you want to be able to give the developers what they need when they need it. There was a time when people were going around it, swiping their credit card and, and saying, it doesn't give me what I need. And so cloud is supposed to change that. So we're trying to deliver the ability to do that for the developers a lot faster than had been done in the past. But at the same time, giving the enterprise the controls, the security, the compliance that they need. And sometimes those things got in the way, but now we're building systems that allow that to happen at, at the piece that developers needed to happen. >>But what Rod said about, you know, one of the big things you sparked my thinking is it also, you know, building a overlay of the cloud native construct allows for visibility that, you know, you didn't have, you know, from a developer or even a operations day two operations, now you get that visibility into the network space and controls and management of that space a lot easier now, you know? >>Yeah. I mean, business critical applications, right? People, the people, the business does not care about networking, right? They see it as electricity and if it's down somebody else's problem to fix it. But the people who do need to keep it up, they need the telemetry. They need the ability to understand, are we trending in the wrong direction? Should we be doing something so that we don't get to the point where it goes down? And that's the kind of information that we're providing in this multi-cloud environment. You mentioned Equinix, we, we just have a partnership with Equinix where we're extending the cloud operational model that Aviatrix delivers all the way out to Equinix and that global fabric that you're talking about. So this is allowing the, the comp companies to have that visibility, that operational ability all the way globally. >>Yeah. Because you know, when you start building all these clouds now and multi regions, multiple AZs or different cloud providers or SaaS providers, you're moving data all over the place. And if you, if you don't have a single pane of glass to see that entire network and be able to route stuff accordingly, it's gonna be a zoo. It's not gonna >>Work. We were, I was talking earlier with, with another guest and we were just talking about companies in your case, I, I IHG kind of knowing what you have and it's not like such a basic thing he said, but yeah, you'd be surprised how many people don't know what they have. Oh, yeah. And so they're trying to provide that visibility and, and, and awareness. So, so I'm kind of curious because you were just the next interview up, so sorry Ken, but, but do you know what you have, I mean, are you learning what you have or is how do you identify, prioritize? How valuable is this asset as opposed to this can wait? I mean, is that still an ongoing process for >>You? It, it's definitely an ongoing process. I mean, we've done over the last three years of constantly assessing all our inventory of what we have, making sure we have the right mo roadmaps for each of the apps and products that we have. Cause we've turned to more of a product driven organization and a DevOps and we're, we're moving more and more product teams onto that DevOps process. Yep. So we can shift left a lot of the activities that developer in the past had to go over a fence to ask for help and, and, you know, kind of the automation of the network and the security built in allows us to be able to shift that left. >>Did that, I, you were saying too three years, right? You've been on, on this path Yep. Going back then to 2019 right. Pandemic hits, right. The world changes. How has that affected this three year period for you? And where are you in terms of where you expected to be and, and Yep. And then what's your, what are your headlights seeing down the road as to what your, your eventual journey, how you want that to end? >>I probably, the biggest story that we have a success story is when the pandemic did happen, you know, all our call centers, all agents had to go home. We were able within 30 days be able to bring up remote desktops, you know, workspaces an a uws and give access to globally in China and in Singapore and in the Americas. There's >>No small task there, >>That's for sure. So we built a desktop, certified it, and, and agents were able to answer calls for guests, you know, you know, so it was a huge success to us. Sure. It did slow down. I mean, during the pandemic it did slow us down from what gets migrated. You know, our focus is, you know, again, back to what I was saying earlier is around our guests and our loyalty and, you know, how do we give value back to our hotel owners and our guests? >>And how do you measure that? I mean, how do you know that what you're doing is working with, with that key audience? >>We'd measured by, you know, one occupa >>There so many, how many people do we have in the rooms? Right? But in terms of the interface, in terms of the effectiveness, the applications, in terms of what you're offering. Yeah. >>It gets back to uptime of our systems and you know, being able to deploy an application in multiple regions elevates the availability of the product to our guest. You know, the longer I'm up, the more revenue I can produce. Right. So, you know, so we, we try to, you know, we measure also guest satisfaction at the properties, you know, them using our tech and that kind of stuff to >>Be so you surveying just to find out what, how they feel about, so some, >>Cause we have a lot of tech inside of our hotels that allow for, we have ISG connect, which allows for people to go from one hotel another and not ask for passwords and, you know, that kind of stuff. >>That would not be made by the way. I'd be begging for help. Let's talk about skills, because I hear that a lot. Talk a lot about that this week. Hearing that, that, you know, the advancement of knowledge is obviously a very powerful thing, but it's also a bit of a shortcoming right now in terms of, of having a need for skills and not having that kind of firepower horsepower on your bench. What, what do you see in that regard? And, and first off, what did you see about it? And then I'll follow >>Up with Yeah, I mean, over our journey, it started off where you didn't have the skills, you know, you didn't have the skill from an operations engineering architecture. So we went on a, you know, you know, how do we build training programs? How do we get, you know, tools to, to either virtual training, bringing teachers, we built, you know, daily, our weekly calls where we bring our experts from our vendors in there to be able to ask questions to help engineering people or architecture people or operations to ask questions and get answers. You know, we, we've been on a role of, you know, upscaling over the last three years and we continue to drive that, you know, we have lunch and learns that we bring people to. Yep. You know, and, and we, and we, we ta tailor the, the content for that training based on what we are consuming and what we're using as opposed to just a, you know, a broad stroke of, of public cloud or, it's >>Almost like you don't have to be holistic about it. You just need to, what do you need to know to >>Make >>Them successful, to be better at what you're doing here? Right. Sure. >>And that's been huge. And, >>And yeah, we, and we have a program called ace, which is AVIATRIX certified engineer. And there's a bunch of different types of classes. So if you're a networking person in the past it's like A C C I E, but we have about 18,000 people over the last three years who have gone through that training. One of them. One of them, right? Is that right? Yeah. Yeah. And, and this is not necessarily about aviatrix. What we're doing is trying to give multi-cloud, you know, networking expertise because a lot of the people that we're talking about are coming from the data center world. And networking is so different in the cloud. We're helping them understand it's not as scary as they might think. Right. If your whole career has been networking in the data center and all of a sudden there's this cloud thing that you don't really understand, you need somebody to help you sort of get there. And we're doing that in a multi-cloud way. And we have all kinds of different levels to teach people how to do, do infrastructure as code. That's another thing, you know, data center guys, they never did infrastructure as code. It was, you had to bolt it in and plug stuff in. Right. But now things are being done much faster with infrastructure as code. And we're teaching people how >>To do that. Yeah. I mean, yesterday, one of the keynotes is about the partner in the, the marketplace. And they use the image imagery of, of marathon runner, you know, a marathon runner. Yeah. You could do a marathon by yourself, but if you want to improve and become a, a great marathon runner, you need a coach, you need nutritionist, you need people running with you to, to make that engine go faster a little bit. Yeah, exactly. And you know, having a partner like Aviatrix helps you know the team to be successful. >>Well, it is, it is a marathon, not a sprint. That's for sure. And you've been on this kind of three year jog. You might feel like you've been running a marathon a little bit, but it sounds like you're really off to a great start and, and have a pretty good partnership here. So thank you. Congratulations on that, Eric. Thank you for being with us. And Rod, same to you. Thank you. Appreciate the time here on the AWS Global Showcase. I'm John Wal, you're watching The Cube. We're out in Las Vegas and of course the cube, as you well know, is the leader in high tech coverage.

>>Mhm >>Welcome to this preview of couch based connect online 2021. My name is Dave Volonte with the cube and we're here with couch based ceo matt cain matt. Good to see you again. Welcome >>Thanks Dave. Great to be here. >>We are super excited at the Cube to partner with Couch Base this year to share the news, the analysis from connect online 21. What can attendees expect from the event this year? What's the theme? What can people really take away? >>They were fired up, you know, there is no different. Our theme this year is modernized now and it's something that we're hearing from our customers across the world is they think about leveraging technology to get closer to their customers and at the top of every one of their strategic agendas is figuring out how to build the best applications to service our needs as our personal lives and in our business lives and we're really focused on talking about the technology that we uniquely architected to enable this that stands aspects of relational database technology and new capabilities, leveraging those people technology, putting that into an integrated platform and really supporting customers. And we love talking about what we built Dave but we love even more when our customers share what they've been doing with our platform, customers like Pepsi and Amadeus and American greetings, you're going to hear them and their development meant teams talk about how they have leverage couch base to solve some of the most fundamental application challenges and how that's really opening up new businesses for them in their end markets. >>Let's talk a little bit more mad about that, the modernized now. I mean the trends that we're seeing in in the market place, they were in motion before the pandemic. But digital digitization and modernization has really become a high priority. Talk about why in your view now is the time to modernize and what's the mandate for enterprises? >>Well look, I think digital transformation has been a focus point for some time and I think that's going to continue as we go forward. But I think as enterprise think about the challenges they have in front of them to successfully transform digitally, they may be thinking about the problem a little bit differently in light of current circumstances. Uh and what we're seeing is enterprises have the desire to innovate, but they may not always have the resources or the capabilities to do it at the place they want to. And so how do they approach this challenge first and foremost, they need a platform that can help bridge the legacy world and the new one that they can safely evolve applications and modernize, you know, workloads that were dependent on relational databases while putting them into new platforms. At the same time, they need people to do this work. So if I'm an democrats, almost an insatiable demand to build new applications, but I don't necessarily have all the people and teams and capability and skill sets needed to support that. So as a technology company, we've got to think through how do we help provide the tools that will open up more people's ability to contribute to that digital transformation leveraging things like sequel is the fact of language in the database technology allowing enterprises to repurpose workforces free up investment dollars, free up people to really focus on the next generation of properties that are going to change their businesses. And so I think the current economic conditions haven't changed the fact that digital transformation is the top of the priority list. If anything, that reinforced the urge with which enterprises need to go after this, but also the way that they need to do it. But I can't just continue to throw niche technologies of problems. I've really got to think about what kind of platforms tonight and then in the future and a couch base as the modern database for enterprise applications. This is what we're going to spend time talking about and helping customers understand the value that we can unlock for them as they invest in the couch based platform. >>Super relevant now since we last talked matt, he made some big moves, not the least of which is you're now a public company. We've been following that. But what's changed what's new product wise and maybe one of the fundamentals of the market that that your your customers and your culture or driving. >>Yeah, well let's talk about first, what's not changed? We continue to be long term oriented couch basically believe we're in truly what we call a generational market transition and the challenges in front of enterprises unparalleled. So too are the opportunities for enterprises that get this right? They will innovate and thriving in their respective markets. And so as a company, we pride ourselves in being maniacally focused at solving unmet, underserved needs in the world of databases. And really thinking through what technological challenges do we need to innovate on store, customers can take that technology and successful. That's not, that hasn't changed that, that won't change. We continue to be insanely customer focused and really studying those problems and making sure that we're adding value in everything we do from a product perspective services, how we show up to help our customers and that's really important. Um certainly as you said, it's a big milestone for the company step in the public market. We're very proud of what we've accomplished over our first decade or so of existence. But we truly believe that we've been built for this moment and that market transition that ever have referred to um that that movement into the public markets allows us to talk more broadly about all that we've built and how customers are taking advantage of our technology case in point is probably the biggest release in company history couch based server seven oh, so while we were busy taking a step into the public market, we also continue to innovate as I said and are very pleased to be a market with couch base 70 which fundamentally bridges for enterprise customers to move from relational to modern databases and do that in a single integrated platform. And we're going to talk about that connect in more detail and how application developers can re platform applications in a much more seamless way and then start to innovate in a way, you know, that they never have. So a ton of work underway. We've got some really exciting announcements which I think we'll talk about here in the second at least plant the seeds on those. But we're going to be really focused on the innovation that we've delivered up to this point because it's so fundamentally valuable to the enterprise customers we serve and couldn't be more excited to share the benefits of that. That's actually what we're going to help customers do as we go forward. >>Well, we see a lot of companies and as as we evaluated, you've hit critical mass in terms of how we think about it successful I. P. O. Your surpassed $100 million in revenue 500 plus customers talk about the opportunity for couch based to continue to grow. What's in store. What's the focus? >>Well, as I mentioned, we're going to we're going to continue to innovate and so you know, ahead of the conference. We're going to talk about some really important upcoming innovations and I'm not gonna steal too much of the thunder from the show, people are really pumped and putting that material together? We we focus a lot on ensuring that we have the best database in the market, particularly for enterprise applications. Uh and really thinking through the architecture that will support applications today and going forward and we've been really successful with that date. As you mentioned, we have not only a lot of enterprise customers and we're really proud of those customers would support what were even more proud of though. Dave is the mission critical nature the enterprise nature of those applications. These companies are truly running their businesses on applications powered by pouches as we go forward. We have almost unlimited potential for new opportunity in acquiring new customers. Um and we're really focused on that and evangelizing what we've done successfully with our existing base to new customers and their respective markets and we continue to acquire those and you know will successfully expand because of the power of our platform. We've done a lot to invest in our partner ecosystem. So you know we have many I. S. V. S. That are taking our solutions to market. We have G. S. I. S. That are building practices around couch base because our database provides capabilities that others don't and they can run their businesses and help their end customers transform with the power of couch face. But Dave what we like to talk about a couch bases, we have opportunities to really help customers once we get in. We think about many factors of growth. So when we support a customer with an application, what often happens is that application growth because the enterprises successful and they put more users in or they deployed a new new geography at the same time, they realize, wow, if I can support highly interactive, highly scalable distributed applications in this particular area, I have hundreds, if not thousands of those in my enterprise, so I can use the platform for that. Then one of the things that we focus on is giving more and more capabilities to developers to enhance the performance and the personalization of their applications I mentioned, we support the sequel query language, we've got operational analytics, we've embedded full text search, we have things like eventing all of these are elegantly architected features that allow developers to build great applications and the more that were successful in helping developers do that, you know, the more, the more the company is going to grow. Um and then on top of all that we couldn't be more excited about about cloud and couch based cloud from the very outset has been a cloud, native platform, are enterprises are running this and multi and hybrid cloud deployments, but what we really have an opportunity to do is help them and run more of the service of, of that cloud solution and we're gonna be talking a lot more uh you know, come come the show about some specifics around that offering and could be more excited about augmenting or portfolio with some new capabilities there >>lot to learn at this event. Tons of meat on the bone. Okay. Matt, we're gonna leave it right there. Couch based, connect online. It's a two day event, october 20th to the 21st. More than 80 sessions geared for architects, developers, business users, open source advocates. Now the easiest way to register, all you gotta do is go to couch base dot com. You'll see the link there. There's a hackathon with prizes. So start developing and win. And while you're there, check out the free downloads with a number of different deployment options. Couch based, connect 2021 modernized. Now we'll see you there. >>Mhm mm.

>>From London, England. It's the cube covering Koopa inspire 19 brought to you by Cooper. >>Hey, welcome to the cube. At least the Martin on the ground in London, a Coupa inspire 19 and I'm really excited to be joined by my last guest of the day. Save the best for last. We have Roger Hamoud, the EVP of products from Kupo Russia. Welcome back to the program. Thank you for having me. Thanks for coming here. Of course, it's been great. We've had a, we've had a great day. Lots of buzz and excitement in the expo hall. The lights are jammed. It's happy hours. Happy hour for time for the Q during happy hour. So I know your keynote is tomorrow, so we'll get to that since we won't cover that. But talk to me about some of the new product innovations that Cuba announced today. The last time we spoke at inspire Las Vegas was only a few months ago. So what's new? Wow. A lot is new. It's, it's hard to believe. >>It's only been three months since then. It's been so close. Um, we very much continue our, um, focus on our community. Powered, uh, capabilities. Uh, this has been an incredible focus for us. Uh, so most recently we've added to all of the announcements we talked about at, uh, Vegas, uh, the, um, next waves of source together the opportunity to bring our community to come and source, uh, using their collective spent power and lots of new enhancements in that area. And also we're taking our supplier insights to the next level. One of the exciting capabilities our customers loved is that being part of a community member, I can come in and I can look at insights across all of my suppliers, uh, from the entire community. What we have, we've been working with them on is constantly adding more and more information to that. So now we have diversity data. >>So you can come in and you can search for suppliers that meet your women. Exactly. Exactly. Those are increasingly becoming more and more important. And then we can help companies source with the right suppliers much more easily right off the bat. Um, other areas that we've announced today was a coupon pay for expenses in early access program. Uh, we also announced invoice thing. Um, going on GA, when we talked in Vegas, it was still in the early access program, uh, capabilities and opening up our platform, Coupa as a platform. >> Uh, tell me about that, cause I wasn't quite clear when Rob was talking about it this morning. I thought I wanna dig in that with you. Kupa as a platform. What is that? What does it look like? So what's exciting about this is, so from our inception as a company, we were always had this old in Cooper about being open as an ally for the entire ecosystem that our customers might have. >>Our vision has always been, we want to be the, ultimately the business screen for everything business spend management related for our customers. So over years we kept taking the level of openness with our partners through different, um, different levels. If you say, if you will, for example, we started with just integrations in the beginning and we certify these integrations with coupon link. Um, we've taken it most recently where we allow partners to embed their mini apps within Cooper. So, for example, um, you can see in one of our partners EcoVadis now they have the capability to embed their supplier diversity data sustainability data right on the supplier record. Okay. And what's beautiful about this is that our customers, when they look at it, it looks a one beautiful unified experience and bringing all the data in context for what they want. Um, today, this morning, uh, Rob shared one example from Amadeus for, uh, trip integrations. >>So right on the homepage, I can see right within Cooper, I can see all their bookings that I've done with the travel provider, Mike pre-approvals, expense reports, all within one unified experience. But ultimately where we want to take coop as a platform is to become this app directory that, uh, third party partners and platform developers start building applications to extend Copa to bring more choice and value to our customers. Okay. Wow. Is that one of the things I saw Rob shared this morning was integration with Slack. Yes. So business folks can review, approve, or reject, like expenses for example, right from within Slack without even having to go into the platform. Yes, yes. That you hit on a very important concept, which we call the best UI is no UI in many ways. And the idea there is um, we always put ourselves in the user's shoes and ask ourselves how do we get them what they need with the least friction? >>In some cases that might involve a user experience because you need to ask them questions and make cases. We can automate the whole thing. So we just do it. And in many cases it means we go to them to where they are such as in Slack, I'm going to ask you to leave Slack, go somewhere else right then and there you should be able to approve or reject why you have to go anywhere else. Is that what, what Cuba means by no UI is the best UI, correct. Best UI is no UI. So ultimately wherever there is effort, we, we want to involve people only when they need to add value. That's it. And as much as we're able to automate, that's great. So we take that off of their table and we also adjust to the type of experience they need. Sometimes just a text message is enough sometimes to bring the data to me into a collaboration applications that I want. >>Um, sometimes we, we help them approve right from, um, a button. You don't even go into Kupa in order to do that. So always thinking of how we drive adoption, drive adoption. And it's an important concept, not just on the employee side of companies, it's even more so on the supplier side as well. Now when you think of any or like large organizations, they have tens of thousands of thousands of suppliers, many have hundreds of thousand suppliers. And the supplier ecosystem is everything from very small contractor, mom and pop shop, maybe two people or even one person all the way to very, very large companies. Okay. So as you look at that whole spectrum, you have to really think what does every audience need? And so in many cases, these people, um, they may need to do everything very quickly straight from an email without having to remember a user ID and a password to log into something. >>So eliminates friction at every step of the process for them. Wow. So let's talk about that Vic community insights. As we look at some of the, uh, the data that KUKA has gotten from finance leaders of the UK, that was like a survey that you guys, yes, I did recently have 253 decision makers and finance and some of the numbers were glaring. Like, wow, 96% of these decision makers said we don't have complete visibility correct. Of all of our spent. And then I was talking to a customer today who said, we've got now gotten 95% of all of our business men going through Coupa and that was within less than a year. Yes. So the opportunity there to deliver that visibility and those insights back to the community is, is pumped, is incredibly exciting. It's incredibly exciting. We're starting to see more and more the sentiment that's in key, loud and clear and um, by working constantly on the AE, the accelerated and coupon, we work on getting more and more of the spend for each and every customer under management. >>Um, we, when we start to projects for customers right off the bat, uh, we use our AI classification tools before they even start with Copa, where we start helping them get visibility onto all of their existing spent so that as they start into their Coupa journey, they are always looking at it holistically. Okay. So we know them, realize all of that data and provide them insights and reports right off the bat as well. Tell me about the customer interactions that you have as the EVP of product, lot of customers on the platform, a lot of data there. How are customers influential? Yes, yes. The direction. Like for example, you know, obviously I won't give a secret sauce, but for Cooper inspire 20, 20, what are some of the things that we might see customers influencing in terms of your roadmap that direction? Partnerships? Yes. Yes. >>Um, in general, the way, um, we've always worked, uh, at Coupa with our customers and we call them like our community members really is an inc very incredibly tight partnership. Um, we have three releases a year, January, may and September. Each of them packed with roughly about anywhere 72, 19 new features and capabilities. And all of these capabilities are touched either conceived by customers, with customers or touched by customers in the form of working with them on early access validation and all of that. And for me, one of my most favorite things I get to enjoy about working in SAS and, and uh, being at Cooper is that as soon as you are rolling out these capabilities and turning them on in the cloud, customers are using them. So even though like for example right now my entire team has just finished the walkthroughs of all our may release for inspire. >>And when we come back from this trip, uh, we will start the, you know, the, these, the design and, and um, definition. Um, often we might hear of new requirements that might come up and because we are InsightSquared able to, um, here at just what it makes sense and actually be incredibly responsive to what we see. >> How do you do that? How do you look through all the different responses and correlate that data and determine what makes sense to stack? Rank in terms of priorities for new features and new capabilities. So it's definitely an art and a science for sure. Um, but there's a framework that, uh, we follow, uh, since the beginning and we continue to follow and continues to serve us really well. Uh, which is always balancing between three drivers of customers, market and innovation. So the customer one is the obvious one of course, where and many events like this and one on ones and online community. >>We're talking to customers and they're specifically coming and asking for help in areas. Now, we may not build the feature exactly as they asked, but we listened to the pain beneath it and late using the latest technologies, we think of what is the best approach to solve the real pain that they have. So that's one part of the planning for every release cycle. The other is overall market. So for example, as we grow into more regions, uh, newer areas, new spend categories, um, new adjacent powered applications that our customers are needing, um, we started expanding in that area as well. Um, for example, we, right now in London, um, a lot of, uh, when I joined Cooper back in 2012, uh, we were just starting the, uh, entry into the, uh, Mel market and a lot of the product capabilities were market driven in the sense that we were spending a lot of time on compliance and different regulations and all of that. >>And the third is innovation. And what is always one of the things as we bring people on board at Cooper and talk about the framework, um, innovation for us is what we call pragmatic innovation. And it's comes from deep understanding what are the customer problems, what are the market problems? And then we ask ourselves using everything, the latest technologies, what is the best way? So you'll never hear us talk about AI for AI sake and blockchain and all of that would always talking about do we deeply understand the problem and what is the most appropriate? Um, so we call them CMI customer innovation. Uh, within my products organization, every product managers usually has a vision for their product and they have a full release roadmap. And in each full release roadmap, they are listing things as C M I in many cases the same capability is C and M and I, so it becomes an art and a science of balancing those types of things. >>But ultimately when we look at our collective release of CMI, we're asking ourselves, how much does this release accelerate the success goals of our customers? Right. And generally that's the framework that we use. Yeah, that's fantastic. Thank you for explaining that. In terms of acceleration, some of the numbers that Rob shared this morning, we're, I think your customers are collectively approving invoices 30% faster than last year. I said medium, mid size market, customers are getting lot going live on Kupa in about four months. Correct. And mid large enterprises and about eight months. So. Right. And I've talked to a number of customers today about the speed of which they're able to get onto the platform and actually start seeing business value. So that's a free coupon for acceleration was well dissected today. Yes. Yes. It's definitely, yeah. Um, these are the vision areas that Rob talked about today. >>And in each of these vision areas, we're always asking ourselves, how do we continue to accelerate? So that's actually how one of the ideas was born around the turtle is I'm the hair, which is we want to accelerate cycle times, cycle times, and what are the different ways we can do this? What can we borrow from um, the, uh, our consumer lives to do this? And that's where the game unification came. Yes. And sure enough, it was one of those things that got people super excited and, and they're putting more attention into it. Well, the consumer side of our lives is we're so demanding because we can get anything that we want. We can buy products and services, we can pay bills with a clicker swipe. And so the B to C side from a payments perspective has innovated far more rapidly than the B2B side has. >>Correct. A lot more challenged there on the B2B side. But as consumers, we want a simple experience. One of the customers I spoke to who said when he was looking for technology, he's on what something that looks like Amazon marketplace. Yeah. Because from an adoption perspective, my teams will understand it. You so that the consumerization always interests me because we are those pretty much, you know, 12 plus hours a day and to see how software companies like KUKA are taking and meeting the needs of those customers, obviously it's not an overnight process. It gets people excited. It gets its absolutely is you right. That always fascinated me also how I've seen so many companies, um, like people almost have two personalities. Like they go into their personal life, they have a personality, they go into their professional lives and like, Oh, it's okay. It's like a backend system. >>This and this and this. Um, but increasingly the new generation is no longer tolerating and the drive is starting to just go find those shifts that happen changing, right? Yes, yes. But I can't, if I can have this in my personal life, then I need to be able to transact. Exactly. Exactly. Why does it take 45 days? Exactly. Exactly. Five days. Um, so last question for you. Since your keynote is tomorrow. Yes. What are some of the strategic visionary elements that you're going to leave the audience with? So I'm going to leave the audience with the key pillars of our strategy. Um, latest innovations we've done towards them and where we are taking them in the years ahead. One of the things I've always done over the years at inspire is we always share at preview of what, um, the community has been talking to us about and we're working with. >>And usually at the end of it, a lot of new community members might come in and ask to participate in some of the development because it means a lot to them for their own business. And then usually by the following inspire, we start showing these things actually live and, and, um, executed on. So the, um, the three strategic pillars I'll be sharing and talking about are all around the pipe that Trump talked about. Yep. How do I capture more and more spend under management? So we'll be talking about the consumerizing experiences voice using voice use Copa using facial recognition in Cooper. Uh, we'll be talking about new concepts around travel, around the group card school, applying all of it around the theme, focused on the um, end users and delight them, blow them away with consumer experiences. And then now that we do all of that, we can jump into the power users because we are increasing that spend under management. >>The theme by far is all around suite synergy suite synergy. So we seriously, this doesn't exist in the market. The market overall was all siloed applications. We're creating a new category and we've created these beautiful, elegant flows for our customers today. But there's also a wonderful long journey ahead in what we are taking up. Well maybe we'll get to talk about synergy at inspire 20 slowly. I will, we would love to have you again. Excellent. We're going to in Vegas for the afternoon. Best of luck in your keynote tomorrow and we'll see you the next inspire. Thank you. My pleasure. Thanks for Raja Hamoud. I, I'm Lisa Martin. You're watching the cube from Coupa inspire 19 from London. Bye for now.

>> Live from Las Vegas it's theCUBE covering Adobe Summit 2019. Brought to you by Accenture Interactive. >> Welcome back everybody, Jeff Frick here with theCUBE. We're in Vegas at the Adobe Summit 2019. I think there's about 17,000 people. The first time we've been here but we've been excited to be here. There's a crazy good buzz and energy and actually a ton of CUBE alumni here at Adobe. We're greeting old friends but it's always great to meet new friends. And coming off of great mention in the keynote this morning we're excited to have Santiago Aldana. He is the CDO and CTO of Avianca. Welcome. >> Thank you, John. >> So I was surprised this morning, we were watching the keynote and there's Satya Nadella and he has a shout-out for you guys. >> It was quite a surprise. It was very engaging and I'm happy to hear that. >> Yeah, congratulations. >> Thank you. >> And a little fact, you guys are the second oldest commercial airline, he said. I had no idea. >> That's right, we've been flying for almost 100 years. It's our 100th anniversary this year. >> Awesome. >> So great, great. >> Well, congratulations. >> Thank you. >> So air travel's a really interesting industry because it's growing like crazy in terms of the total number of passenger miles, right? More people are flying all the time. But it's got to be super competitive. You got to worry about fuel costs. A seat mile is a seat mile. So there's all kinds of interesting ways to compete. You guys are really into it, you've been successful for 100 years, so how do you differentiate what you guys are doing and continue to evolve and be successful? >> So there's several things. If you look 10 years back we used to be a domestic airline. We used to have around 30 planes, now we're around 170 planes. We're the second largest airline in Latin America. That has been a huge growth. >> Wait, how long did you do that? >> That's for the last 10 years. >> 10 years you went from 30 planes to 170. >> To 170, 180. >> And domestic to international. >> To a Latin American airline. >> That's a big move. >> That's a big move but we're shifting our emphasis, going more, rather than growth, going to profitability. And to make that profitability we have to make the strong transformation to make that happen. >> So for profitability there's all kinds of things that go in there, there's higher utilization, there's hopefully everybody buys Teslas so the gas doesn't cost as much for the airplanes. How are you focusing on profitability? 'Cause here we're at Adobe, all the talk's about experience, experience, experience. If I'm flying on your plane, I want to get a good deal and keep everything good but I'm not necessarily that worried about your profitability. >> So let me tell you a little bit about that. If you think about an airline we're just the distance between our customers and their dreams. We're just the distance. So the customer doesn't want to go to security. The customer doesn't want to go to the whole hassle of planning the trip. Our purpose is reducing that distance, reducing that effort, and when we reduce that effort we're going to self-service, we're going to personalize, to make life easier for our customers. That's the basic challenge. And that has to do with three main areas. One, knowing our customer. The other one is, making sure that the value proposal for that customer journey is proper. So that's operational work. And the other one is providing our employees with enough information to make that happen. All of those are working along data, and data to be able to provide a real value proposal to making that happen. The customer has to be in the center of our strategy and that's where we have to be working all the time. And when you do this, it's not about technology, it's about the customer. And being that, about the customer, the strongest challenge is not technology but people, making people change so we that can provide the value proposals to our customers. >> So what are some of the things that you did to enable the experience of my engagement, whether it's electronic or whether it's when I'm talking to that person at the counter, checking in or getting on my flight, how have you helped them provide me a better experience? >> You talk as if it was part of the past. To be honest, it's a journey, we're still working on that. There are several things that we did last year, a whole bunch of things. We changed our app, we changed our website, we changed our interaction with our customers with data. And regarding Adobe, we're here at Adobe, we implemented a whole set of tools. So AEM, the website is a new thing. Regarding Microsoft we implemented a CRM to know about our customers. We changed our app, and the app is like a platform with which we're transforming the customer journey. What we have to do at the end of the game is changing those touch points so that those require less effort from our customer, they're more seamless and we are able to personalize and know in advance what the customer is looking for to provide alternatives. And that makes it more seamless. So we're in that process of doing data-centered decision making to reduce that effort from our customers and make things happen. >> So as you've gone through this journey to date what are some of the surprising things that came up that you just didn't expect at all, on a positive side? And then what were some of the negative things that you didn't know, that were so negative that now you've kind of removed? >> Okay, so I've been here in this business and Avianca just for the last two years, so if you talk about surprises this is my first time in airlines. I wasn't expecting this to be so challenging. >> Well, it's good to come at it from a fresh point of view, absolutely. >> I've been in banking, I've been in telcos. Believe me, there's a huge technical depth, there's a lot of complexity, and bringing this customer information up to the table, it's been challenging. Lots of things going together. Surprises, yeah, we have to work with our employees. We have to transform that culture. We have to move towards a more testing ... Having experiments iterating and learning from that process. And that takes time and that requires a lot change of culture. The other one is being more agile and that's more easily said than done. So making the teams be more collaborative. And working with partners. We decided to choose a handful of partners to make this transformation work. And those partners, that's not one thing that you just plug and play, you have to make it work and that requires a lot of effort. Even if it's big, strong, world-wide, world-level sponsors and partners, it requires engaging and making them work together. At the end it's about people in every part. And making people work together, that's a challenge. That's a challenge. >> You've got the whole gamut too, 'cause you've got the front line people that are directly engaged with the client, whether again it be at the gate agent or on the telephone or processing those things all the way back to the senior management and the operations which I'm sure are not only regulated and very very finely detailed for safety and everything else. So that's got to be hard to try to drive transformation in what was probably a pretty rigid situation. >> It is, that's why you have to choose what to do. And probably you don't know how to do it at the beginning but you know what you want to achieve. And that requires a more iteration way of learning, experimenting and finding a way. That's regarding agility. And that's where you work with partners to also leapfrog and move faster forward unto this. That's where we choose partners as Accenture, Adobe, Microsoft, SAP, and Amadeus. And they're moving us forward unto that. >> So what are some of the ways that you're trying to measure success? What are some of the things you're tracking as you go through this transformation? >> Well, several of them. Let me talk just about a couple of them. One of the things that we have to do is make the buying process easier. We're starting way behind, strong technical depth, and we have to decouple our systems to make those steps that our customer has to do, make them fewer, easier, and changing the whole booking flow. But to do that, we don't have the answer. First we have to decouple the system, the legacy systems, and then we have to learn from our customers. We have to do a lot of A/B testing to see what works better. Test and see if the process is better accepted by our customers, learn from that, probably fail, do it again, iterate it and do it again. And that process we have to engage unto that. The other one is ... So that's one of the areas. But the other one is, how can we make sure that the operational value proposal takes place? Since we have been growing for the last 10 years so much, we started from a local airline to the second biggest airline in Latin America, but that growth is a little bit disorganized and we have to set things up to make it happen. We have to provide a lot more data and connectivity to all our employees at the airports, at the counters, at the call center, and providing them with more customer information to make it happen. >> Right, so you're on that process, so you're starting to deliver new data to the gate agents and the people on the front line? >> Sure. >> So how are they reacting to that? Do they like to be empowered, are they afraid of being empowered, are they saying, "Ah, finally I have the information "in front of me that I can take care of this traveler?" >> So there's not one answer for that. In some cases we empower them and they enjoy a lot and they say, "Hey, finally we got this." For example, we are giving our ... This is a recent project that we launched at the airport. We're providing them data through mobility, making the turnaround of our planes faster, and we're giving them much more data. Before then, they had to call everywhere to find what was happening. Now they have it at their hands, and that's different. So that changes the whole thing and they look forward to that. At other times, we sometimes do mistakes also. We provided more information through the apps to our pilots. They were finding that awesome. But then some of the information that they used to have, we didn't get it. So we have to iterate it and give it and then they start loving it. Regarding our customers, which is the other side, it's not internal employees, we do some things in which we test and sometimes they say, "Oh, that was not what we were expecting." So we have to learn from that. I mean, it's not about making a huge waterfall project. It's about learning in the process, failing, and iterating and making it happen again and again. It's a whole journey. >> We just had our last guest, he talked about trying to move this stuff to the cloud. It's like, first time didn't work, second time didn't work, third time, hey, now it's working. So you don't know until you know, right? And what we hear over and over is as you start this top-level transformation project you uncover a bunch of stuff under the covers that has to be reworked to support what you're trying to do on the front end. >> That's right. >> I assume it's a lot of the same thing that you found? >> You're exactly right, there's a lot of things in that way. On all three areas. Customer, on customer we didn't have customer information, we didn't even have a CRM. So we implemented our CRM at a huge fast pace that we did it, in a year we already had it. The app and the website, we have to totally remake it, and getting more information from that and getting personalized information regarding that. That's technical depth, I was not expecting that to be there. >> So I'm just curious, what was the catalyst of this transformation and this growth? Were you trying to put in systems to support the growth that you did from going from a relatively small domestic airline to an international, or are you trying to set the table for continued growth, to continue on that growth path? That's a pretty aggressive growth path. >> It's a little bit more simple than that and I'm going to be blunt here. Three years ago the board at Avianca was doing a search for a new CEO. That's my boss right now. He came over three years ago. He used to be the president for Microsoft in Latin America. In the interviews they told him a lot of things. And after he was questioned and doing the interview, he said, "Okay, let me say this now. "Are you asking me to make Avianca "a digital company flying airplanes?" And they said, "Yeah, that's exactly right. "That's what we want." So that was the initial pace. That was three years ago. I joined the team two years ago. There was already a vision, and that vision is making things easier and effortless for the customer. That's part of what we're trying to build. And that is before, during, and after the trip. If we are able to do that we're reducing costs, we're making it simpler. The whole process is about being simpler, taking away complexity, making sure that our operations are better, and that's taking away complexity. You can do that through technology also. But again, the biggest challenge is probably not technology. It's a cultural change and it's the leadership required to move on and make our employees, our customers, take advantage of it. >> Bold move by the board and a bold move by the CEO but we hear it all the time. Everybody's a digital company now, it's just what product or service do you happen to wrap it around? So what a great story. >> Thank you. And yeah, again, we got to go more data-centered, we have to know our customer better. If we want to do something personalized the only way is through the data. We have to know in advance what our customers are requesting and trying to make it easier for all of them, and that's the data. >> Well Santiago, thanks for sharing your story. And again congratulations on the keynote shout-out. >> Thank you, thanks a lot. >> All right. He's Santiago, I'm Jeff, you're watching theCUBE. We're at Adobe Summit 2019 in Las Vegas. Thanks for watching, we'll see you next time. (lively electronic music)

>> Live from Washington DC. It's theCUBE, covering Inforum DC2018, brought to you by Infor. >> Well good afternoon and welcome back to Inform18, we are live in Washington DC, the nation's capital for this year's show. Joining Dave Vellante and me is Corey Tollefson, who is the Senior Vice President and General Manager for retail at Infor. Corey good to see you today sir. >> Good to see you, good to be seen. >> Yeah, right (laughs) it is, under any circumstance right. >> Absolutely. >> So retail, you talk about a world that's kind of upside down now. The brick and mortar guys are, they aren't brick and mortar anymore. So talk about the state of the industry if you would a little bit since it's moved to the digital platform and how that's changing your work with it. >> It certainly was simple 20 years ago. Manufacturers manufactured things, wholesale distributors distributed things, and then retailers sold things. Right, and so the whole business model has been disrupted. Mainly because of the advent of the mobile phone, a mobile device. I said it last year it feels like everyday you wake up and it's very chaotic and there is a lot of disorder. And I think it's an amazing opportunity for retailers to reinvent themselves into a modern 21st century retailer. Everyday is a challenge but we're working on it. >> So what's it like, I mean, every retailer I talk to has this sort of Amazon war room. They're trying to use their physical presence to drive online. They're really getting creative. Amazon continues to do super well. There are those who are predicting the end of of retail stores because of AI etcetera. What's your take? You're knee deep in this business. >> Well I feel, I mean Amazon certainly is bringing a lot of downward pressure. It's the first digital, retail is the first industry to be digitally disrupted. It is happening in healthcare, its happening in manufacturing, but retail brought on the initial wave so to speak. And what I'm seeing is a lot of the middle of the road retailers that don't have too much of an online presence, their legacy brands that maybe had their following 20 years ago. They're going to get squeezed out because the middle in this group is going to get squeezed out. The high end brands that control their own brand image, they brand manufacture their own products, they also have their own retail stores. Those are the companies that are uniquely qualified to compete and thrive against Amazon because the last I looked having stores and having an outlet for immediate gratification of getting products and services is a good thing. The retailers that we are working with are combating that against pure plays like Amazon. >> But there's some consumer friction there right, and it's generational, so how we shop is different then how our kids shop. They look at retail in a very different, through a very different prism then we do. So how do you address that in terms of, how do you help your clients address that through different segmentation of their audiences and addressing those unique problems? >> Well even as a kid I remember that the retail shopping was a destination shopping experience, so we'd load up the family truck, and we'd go to a mall, and spend the whole day. There would be entertainment there, there would be restaurants to eat at. We'd shop and then we'd come home, it was a destination. Try doing that when it is 24 hours, seven days a week, 365 days a year on your phone, suddenly the social engagement, with social media, and Snapchat, and Twitter, and Facebook. Facebook is a little old for a lot of the younglings now, but the moral of the story is social media takes on everything and that's where the influence is. And that whole shopping experience it used to be, well I'm just going to get some product information and then I'm going to go into the store. That's been completely disrupted as well. One other aspect of this is the whole concept of consumerism is disrupted. There is a lot of, you know you look at a lot of the cool brands that are in other adjacent industries whether its Uber or Airbnb, they don't own any of their assets. Same thing is happening in retail, a lot of the new emerging brands are going to have disruptive business models. Like you go into a store and they don't even have any inventory. It's all made to order right. So there's a lot of disruption that's happening and we're working with a lot of brands to help. >> So talk about the next big thing NBT, next big thing in retail is that one of them? I go into a store and say that's what I want send it to my house, what else? >> Well I think one of the next big things that we're working on is the whole concept of machine learning. I think you guys have heard about this before, but the whole technology singularity where its the point in which there is no differentiation between engaging with a customer. Oh sorry engaging with a human versus engaging with a computer. We're not that far away and its a little bit scary. I think we talked about it a couple years ago but the whole concept is why do I need to interact with a human being for my shopping experience? I can just interact with a chat bot, for example. As long as I the customer gets the information I need to make an informed decision, I don't really feel weird talking to a computer anymore. >> Yeah so that's the idea of systems of agency, right, where the machine is taking action on behalf of the brand, and the consumer either doesn't know or doesn't care. >> Right that's right. >> So do you have customers that are on the precipice of doing that? >> Yeah we do. In one of the areas I have talked about this before, machine learning-based demand forecasting. So getting better at forecasting the right product, the right skew on a store-by-location basis. And what we do is we leverage a lot of the inherent capabilities of the internet. A lot of companies talk about cloud as simply a cost reduction. We view cloud as taking advantage of the world's greatest super computer which is the internet. And so, that's one of the areas in which we've been using machine learning. >> So what's the, you say the company, that mid-lane, or middle range, what are they to do now? Because they are kind of stuck, they have their challenges, they have this legacy approach that they are kind of in a tough spot. >> The die has been cast, if I was in their shoes, a lot of these middle of the road retailers. I would look at finding ways to optimize what I have. So whether that's optimizing your inventory, optimizing your labor. That's another thing we talked about, Charles this morning mentioned the whole concept of unleashing maximizing human behavior and unleashing human capital. For years we've been on shows like this talking about products, instead it's about engaging your customer. Everybody's a customer, if you're in healthcare you're a customer. In manufacturing distribution, you have customers. To look at it more from a human element around store associates, I think there's are a lot of middle of the road retailers that have an old iconic brand that could reinvent themselves with time and enough patience. >> How do you deal with the inevitable, well first of all how do your customers deploy your software? It's in the cloud. >> Yeah. >> It's in the Amazon cloud right? >> Well three years ago we made a fundamental decision that we were not going to be an on premise company. So we are a cloud-only applications provider. The second decision point we made was, do we want to be suite or best-to-breed. And when we say suite that was our decision. The third point was, how do you want it to be able to be deployed? So when I started off in this industry which felt like yesterday. I feel like I'm super old now, I started off as a software developer for a company called Retech out of Minneapolis. You know I was doing batch forms, and Oracle PL/SQL and everything was tied to the database, and the user experience was basically a graphical depiction of a database. (Dave laughs) But back in those days-- >> And it still is in a lot of apps. >> Yeah. In those days it was pretty much all about developing that individual code. I kind of lost my train of thought on that. The way you can deploy our assets is on an individualized basis. You can deploy our demand forecasting engine for example. You can deploy our allocation and replenishment engine. And when you tie it all together, you can have a suite that doesn't need to be deployed like it used to be in the old days is where I was going. Which is you have to deploy the whole data model to get all the information that you're looking for. >> Okay so in retail you've got the inevitable, oh well, I'm going to run this in Amazon, they're my big competitor, they're disrupting me. What's the conversation like with customers? How do you guarantee we're protecting their data, you point to Netflix and say hey it's working for them? What do you say? >> Well I think, I mean we're Infor, we're a big company. It's on a case-by-case basis. Yes we have a relationship with AWS and yes they are a strategic partner for us. That doesn't preclude the fact that we work with Google we work with Azure. We are cloud agnostic in retail so, it hasn't been as big of an issue as a lot of industry critics and analysts have made it out to be. >> So if there were an issue, you'd could run it anywhere you want. >> Yeah you just swap it out yeah. >> Alright I want to change gears here. Announcement on the stage today, keynote Van Jones from CNN was talking about #YesWeCode, an organization he has an affiliation with. You've created this, well launched an initiative NextGen. First off explain what that is but fill us back up to the genesis of that because as we found out just a few moments before it's a pretty interesting journey. >> Yeah. >> That you personally were involved in. >> Yeah, I know I am sure a lot of friends and family that know me well are going to be tired of hearing this story. I will give you the condensed version, which is-- >> Take your time. >> Growing up in Minneapolis, I was a huge Prince fan like most Minneapolis people are. And through serendipity I met Prince's brother, and Prince's brother pre-social, pre-internet, pre-mobile, put me on Prince's private guest list for parties at Paisley Park. And so here I am I had a loving family, and I can't believe my mom and dad would let me do this, but I am 16, 17 years old going to parties with Prince. And when I say parties I mean these were intimate parties, maybe the most was 50 people in his house. Sometimes there's like five of us, and what happened at these parties were he would play new music. If we danced and got up there and jammed with him, then he'd put it on an album. If it wasn't very good, or he felt like there wasn't a good strong reaction he put it in his vault. So we were a test case, a Petri dish so to speak, for his music. And I got to build a relationship with him as much as anyone that could. He was a very stand-offish person, but a brilliant artist, and a brilliant human being for that matter. I got to build that relationship and through that relationship I met Van Jones. We hooked up again at one of Prince's memorials a couple of years ago after his death, and we looked at each other and we connected and I said I'm in the technology industry. And he goes we got to talk because there's some things related to Prince's legacy we should really talk about. Which ties us back to #YesWeCode and the announcement we made today about GenOne. >> For GenOne excuse me I said NextGen. >> Yeah GenOne. >> My fault. >> Yeah no, no worries. And the genesis of this was Prince, Rogers Nelson, and Van Jones had a conversation right after Trayvon Martin was shot and killed. And a lot of people suspect the main reason was he looked suspect because he had a hoodie on. And here is an African American kid wearing a hoodie, they follow him and bad things happen right. Van Jones asked Prince directly he goes, you know clearly that guy was racist. And Prince said, think again, maybe if that was a white kid in Silicon Valley wearing a hoodie he'd be a dot.com billionaire, but because we haven't produced enough people of color in CEO level positions in our tech industry, that's on us. Meaning we need to develop more of our own. And so this project means a lot to us, because of the fact that we don't think diversity is just a check box that you have on your corporate mission statement. We think diversity can change the DNA of your company and it can influence better products, solutions, and services to our customers. So it's really important for us and this is just the first step of a multi-echelon, multi-year, multi-faceted program. That we want to take this and roll it out to the entire industry. I'd love for Salesforce and Oracle and SAP and Workday. I'd love for all of them to adapt a program similar to this. This isn't pride of ownership, it's the right thing to do and putting brilliant kids and brilliant minds that maybe came from a bad circumstance, they all deserve a chance too. And it only makes all of us better, and I feel like a lot of great things have happened to me in my career and I feel like I have to give back. And if I can be a small part of this with Van, so be it. >> So that's a very thoughtful response by Prince, and you were saying earlier Corey it was sort of hard to get to know him. Was that typical of Prince, was he sort of introspective and maybe pensive and prescient in that way? >> Well the piece the people that don't understand about Prince is that the whole story of his life is written in his music. And he's released over two thousand songs, you know I'm sure the family and the estate might see this but I've heard another couple thousand songs that have been unreleased and it's beautiful brilliant music and his whole life story is there. You just need to listen to the lyrics, or read the lyrics and listen to the music. >> So was... You mentioned this story, and I just thought 17-year-old kid, I mean with all do respect you don't look like one of Prince's friends right. You're a Minnesota guy, he was too, but just different and I think, did you ever just think that what in the world am I doing here? >> I had that moment, I will never forget that one moment. So it was probably the summer of 1995, Prince was standing five feet from me. He had his right hand strumming his electric guitar, his left hand was playing lead keyboard lines on the keyboard, his right foot was controlling the pitch of the guitar, the left foot was controlling the pitch on the keys, and he was singing vocals and dancing. And I said to myself, I pinched myself, and I said this moment in time, if Amadeus Mozart was standing here he would be blown away. Because there is nobody in the history of music that can write, produce all this great music, but also maintain that look, that image. And then the musicianship, he's a musician's musician. You know we talk about Lenny Kravitz, I ran into Lenny Kravitz about 20 years ago sitting on Prince's couch. He probably doesn't remember me, I am pretty sure he doesn't. >> We'll find out tomorrow night. >> We'll find out tomorrow, but I mean the moral of the story is he was a musician's musician. I'll never forget sitting on the couch and this really soft spoken gal said to me she was really nervous to perform tonight. And I am like don't worry you go this, and it was an 18 year old Alicia Keys. And Prince behind the scenes had been cultivating and developing talent whether its Beyonce, Alicia Keys, Nora Jones, you know. These people he helped develop behind the scenes, and no one really knew it. >> Well his band members were always incredibly talented. I don't know if you ever saw Prince live. >> Nope, did not. >> You've saw him many times. Man as he would say, that band was tight. (laughing) >> That's right. >> Well the program's a great legacy. >> It is. >> And one that is certainly not apparent, but it is great to know that back story to know the generation of that. What got going and certainly I think there's a lot seems like of emotional equity that you and the company have invested, to make sure it's successful as well. >> We think that it was Prince's legacy, but we feel like he has passed the torch between Van, myself and Charles. This really means a lot to us. So we want to take it to the next level so, we are pretty excited. >> Fantastic. >> Congratulations. >> Thanks for having me here. >> Thanks for sharing the story too. I'm glad and it's just wonderful and look forward to talking to Charles about it, when we have him on tomorrow. Alright back with more we are live here, theCUBE is covering Inforum18 in Washington D.C. (upbeat music)

>> Live from San Francisco, it's theCUBE, covering DockerCon 18. Brought to you by Docker and its ecosystem partners. >> Welcome back to theCUBE's continuing coverage of DockerCon 2018. I'm Lisa Martin with John Troyer. We are in San Francisco on a spectacularly sunny day. We're excited to welcome to theCUBE some guys from Red Hat. We've got Ben Breard, Senior Technical Products Manager, and Reza Shafii, VP of Platform Services. Guys, thanks so much for stopping by. >> Thanks for having us. >> Thank you. >> It's great. >> So, Reza, you come from the CoreOS acquisition, you've been with Red Hat for about five months, Ben, you've been there about eight years, but I did see online that it's Red Hat's 25th anniversary. You guys have been doing something right for 25 years. >> Open source, that's what we do. (laughs) >> Open source. So talk to us, what's going on at Red Hat, what's new, what's exciting? >> I mean, OpenShift is, I mean, that's the big thing, right? I mean, so, just, this is a humbling time to be in the industry, like with this container wave and to see the industry adoption that we've had with OpenShift and, like, how all the technology in Red Hat's portfolio is just pushing and driving that along, it's, I don't know. It's exciting to me. >> No, it's very exciting. For us I think that cultural compatibility between CoreOS and Red Hat has been just fabulous to see. And then seeing how Red Hat provides a platform to really extend that and enhance that is just great, yeah. >> Culture is key. We talk about culture a lot when, at every event we talk about digital transformation, right? And culture is key to that, so maybe, Reza, give us a little bit of perspective, it's been five months now. How has CoreOS been embraced by the Red Hat guys and how are you now living in harmony? >> Right, well, first of all, CoreOS had, we always believed in open source. We were behind many open source projects in the containerized infrastructure space. And in that space, especially there on Kubernetes, we worked very closely with Red Hat. So, we knew each other really well. So as the teams got together, it was very easy for us to really get together and brainstorm towards what are the possibilities. And that's what we've been working on and, you know, the shovel has been hitting the ground for a while now and we're working on a conversion platform that brings Tectonic's technology to OpenShift. That's been very exciting as well as bringing the container Linux technology together with Red Hat, so. >> Some of those announcements happened at Red Hat summit a few weeks back or a month or so back. Can you talk about have there been any other updates? And also like, okay, maybe go one level deeper, so Tectonic was CoreOS', Kubernetes', I don't know, I don't wanna call it, would you call it a distribution? But a lot of autonomic and automation technologies for the operator built into Tectonic which was part of CoreOS' core DNA, now being brought into, kind of, the Red Hat platforms. So maybe you can talk a little bit about some of the stats, some of the recent developments. >> Yeah, so where we're at, it's kind of a phased implementation of bringing those technologies in, right? And so our next quarterly release, right, is gonna start, that's where, you know, we start bringing in some of the components, right? And then the one after that, you know, it's more on the operator side and then, you know, end of the year is when it's fully converged and so that's the path we're on, yeah. >> In terms of Kubernetes in general, Red Hat made a really early bet on Kubernetes and a big shift, a big pivot for its OpenShift platform. Kind of really embracing, throwing out a lot of the internals and embracing Kubernetes. Here at DockerCon, Kubernetes was a big topic, Docker's doing a lot of integration with Kubernetes, I kind of think that maybe that is, one size doesn't fit all but certainly Kubernetes is becoming accepted a lot more places. Can you talk a little bit about, you know, the implications of that, this phenomenon? >> Yeah. >> Yeah, well I think it's, there's a recognition that Kubernetes is now the defacto standard for orchestration, right? I think even if you go back a year ago, that was probably not quite there but now I think that that sense is there, and I think you're right, like, Red Hat embraced that three or four years ago and so did CoreOS and we both had to do a big shift, right? CoreOs was using fleets before that and we made a shift to Kubernetes. That has paid dividends, I think, because now we're really focusing on many of the concerns above and beyond just operating Kubernetes itself. It's what do you do above the stack and how do you operate everything above the stack, and that's where all the operator framework and everything we've been working on comes in. >> Yeah, I mean, it's basically how you get value in a more applied technology and a more application centered way. And so it's just been great to see the whole industry really rally around those standards and API's and everything and, you know, all the cloud platforms, everything, and so it's, you know, it's where the ecosystem is. >> Let's talk about collaboration. When you're talking with customers, you know, we've talked a lot today and at other events too, our enterprises are spending a lot of money, a lot of their IT budgets, on just keeping the lights on on mission-critical applications that they have to have but there's very little budget for innovation. Which is key to an organization being competitive, being relevant and being a leader. What are some of the customer conversations that you guys are having and what are some of the common barriers to container adoption that you're helping, with open to public customers, to eliminate? >> Yeah. >> I can take a shot at it. So, essentially, now on Kubernetes running stateless work goal at Kubernetes, is something that most people can do, right? Once you get to stateful work mode, that starts getting tricky and what we're seeing is that people who have now adopted Kubernetes for a year plus, they're starting to think, how do I run my stateful work on the databases, backend storage, in a, you know, scalable fashion on top of Kubernetes. And that's where we're coming in ans trying to help people, help the community, deliver that, really. Through creation of operators, through creation of reusable business logic that can do that across any Kubernetes department. >> Yip, I was just gonna add on to that, it's, like, as far just keeping the lights on and freeing up resources, right? When you look at all of the path and the deployment models on the net and new stuff, right, we're able to take away a serious amount of, like, operational overhead and just everything to where people can scale and just move way faster, right, and so there's a certain amount of that value that carries over to the traditional stuff, right, and so, you know, I think the biggest thing on the customer side is just, like, a mindset and culture change and getting, getting people to, like, change the way they look at the problem, right? And so, you know, those things and just understanding security, those are the big topics. >> Nice. I was at some Red Hat summit and one of the things that really impressed me there was this promise that, you know, we've all been trying to promise the end customer a time to value that you can actually do things faster, that you actually can innovate, was actually starting to be real in the sense that all of the customer examples were in terms of weeks or months and not years. And the Apple's app and the Apple's multi-cloud and all those other, and, so, can you talk a little about maybe some customers that are doing that or some examples of that, of both time to value and then the fact that a very few number of people were controlling very large infrastructures and I think you were just touching on that in terms of the operators and just all the automation, the day two sort of things. It seems like, I kind of think we've turned a corner in terms of productivity and time to value and real-life, real production workloads. >> Yeah, absolutely, and when you look at, like, where we see adoption, be it the financial sector, or, I mean, it's all over the place, it's really encouraging. And so at summit we had, I don't know, I think, like, 300, or 200 customer talks, it was insane. Going through the use cases and everything. Some of the big ones we're seeing from Amadeus, Optum and it was great. >> I saw an IDC report, I think on the Red Hat website, that showed that customers that adopt OpenShift can see a massive ROI, I wanna say it was, like, over 500% ROI within a 5 year period. >> Well, I think, part of, there's multiple factors to that, right? Part of it comes out of, just the sheer power of containerized infrastructure. Instead of deploying applications on a per compute basis and having to map them to single compute nose, you have the orchestrator that plays that perfect Tetris game with all of your applications. The other part comes a bit out of simplified operations, right? And that's where I think we're just at the beginning of the road. There is plenty more work to do on simplifying operations of Kubernetes and that's what I'm most excited about on this. >> Nice. Let's talk about the future. We are, I don't know, at an inflection point of this container technology, it's becoming more mature, people are in production, multi-cloud is certainly an aspect of what's going on, but I'd love for you to kind of explore a little bit more about some of the tooling. Like, I don't know if you need to get down into the OCI and the runtime level but, you know, what do we see the tooling doing? So, Kubernetes is there, you know, that level is there, but, like, what about, you know, builder and other things like that, like, what other pieces of tooling and automation are being developed to help, again, help developer productivity? >> Yeah, that's a good one, so I'll take a shot. So, it's a couple of things, so Kubernetes itself is plugable on, like, every tier, right, so it's finding that balance of seeing defaults and guidance of what works but then being flexible to work in customer environments so we can lock into, whether we're in, kind of, build strategy pipelines and, you know, whatever works for the customer and their, frankly, different teams, right? Because they all have different levels of maturity and stuff, so that's one thing, is just providing that level of flexibility. And the other thing is, you know, you said multi-cloud, just the way OpenShift provides that, like, common platform across anything, right, it just abstracts away any of the, you know, differences and whatever. >> Yeah, and we're seeing multi-cloud more and more with our customer base. And having a consistent model to deal with every one of them, including your non-prep environment, is becoming a bigger deal. >> In terms of, so on prep, maybe, actually I think it'd be useful. We've been talking about Kubernetes and OpenShift a lot but maybe let's step up a level and say, okay, OpenShift, how do you decide, so OpenShift has Kubernetes in it, but it's much more, it's a services platform built up off of, you know, rail on the bottom all the way up to, kind of, operators now. Can you talk a little bit about what else, what is some of the special sauce of OpenShift? >> Yeah, so, kind of what I was saying earlier about just, like, kind of every layer. So, we start, you know, like you said, rail, right, so the supported bulletproof kernel right up to the runtime, to the, literally the enterprise cube distribution is OpenShift. And then what we bring to it is this, like, amazing developer experience, right? And, like, the secret sauce of where it's going is all of the beauty from the CoreOS side on top of that. So, we've had the developer story, right, so, really, prescriptive onboarding of applications is the power because an empty cluster is useless, right, so you've gotta have that easy path to onboard. And then when we marry that with the day two stuff and all of the, you know, the deployment, and say, operators, everything, I mean, that's the, those pieces coming together is what differentiates it. >> From just up in the air of, kind of, Kubernetes. >> Right. >> Gets you part of the way but there's certainly a lot more. >> Yeah, it doesn't have any of the developer experience, the web console, the admin console, none of that stuff exists, right? >> The way I look at it is that the value add comes from two perspectives, right? One is from the system administrators and the infrastructural owners. That certainly comes to day two operations and how much to simplify that. How do you get a consistent interface across different environments? And how do you do things like accountability? Converging everything on to the same cluster, which is really what Kubernetes does, also changes the focus from a cost perspective, for example. From different application owners to a single owner. How do you make sure that, like, that owner is able to say, well, these are the people that are using it. We have services on top of Kubernetes, in OpenShift, that provide you that capability, for example. Through metering and charge back. Sometimes people call it metering and shame back. (laughing) And then from the point of view of developers, you know, there is multiple opinionated ways of simplifying developers life, right? And any given large enterprise has many, many ways of doing that and we wanna just be ready to address all of them and by the way, we have our own opinions and we have built that on top of OpenShift as well. >> So, you guys work a lot with developers. We have about five or six thousand people that are here at this event. I'm curious, when you go to open source events, including your own, are you finding that same mix of developers, IT professionals, enterprise architects and execs? And if so, what is that conversation like at that higher level where there might be, you know, checkbooks and keys to the kingdom and a business saying, hey, we have to iterate quickly. What is, kind of, the mix of conversations that you guys find in these communities? >> Yeah, it's the difference between the strategy, right, versus, like, bits, right? So, the admin, developer, we wanna focus, we wanna get in the weeds, right, and then the higher levels it's all about strategy, direction and enablement and those types of, you know, higher level concepts, right? So, I mean, that's, I don't know, my perspective. >> Are you learning that your conversations and maybe education of developers helps them then go up the chain within their organizations to explain, this is why we need to do this? >> I think there's some of that, right? The other thing I left off the lift though, is the cultural piece, because traditional enterprises, there's something here that they want to glean and take home in the culture space, right? And so that's a, you know, that's the other big one. >> I find that the conversation varies widely, right? So, when you talk to the infrastructure administrators and developers, you gotta be able to talk very technical and explain to them exactly how all this is working. And they're interested in the feature and technology. But when you talk to the CIO's out there, and the CTO's out there, really they're in interested in the outcome. And when you talk about the outcome it's easy just to show just what everybody wants to get to a pure DevOps model, everybody wants to get to a microservices model. This is kind of like going to the gym and seeing the of really fit people and then saying, well, yeah, but how do I get there, right? And this is where I think a company like Red Hat can come in and say, well, we'll work with you to get you there, right? So that's, that's important. >> Well the other one is just the value of being there and talking to your peers in the industry too, right? I mean, yeah, it's us, we're facilitating, but it's peers too, right? >> But you're right, culture, we talked about that, John, a number of times today, how critical culture is to being able to move past inertia. You know, we mentioned when I kicked off the segment that Red Hat is just celebrating its 25th birthday, so I imagine, I know you've been there, Ben, for 8 years, that there's been a lot of change there and a lot of cultural, kind of, mindset shift. Obviously, Reza, coming on in the last 5 months. Give us a little bit of an insight into the Red Hat culture that's helping to drive the agility that you need to also give your customers. >> Yeah, this is something our CEO talks about all the time, right? He wrote a book on it, The Open Organization, and, you know, just, like, lays out clear values of transparency, doing things very visually. We go through these exercises all the time just for changing our slogans and brands and these types of things, and the way where everybody participates and everybody takes ownership in it, right, and is part of it. And so that's one thing, I mean, we've been going through crazy growth. When I joined it was 3,000 people, now it's, like, 12,000 or so. I don't know the exact number but, and so how we scale that culture has been, it's been interesting, but it's been really successful. I mean, it's a big part of it. Open was a really clear message from summit, you know, basically in the cloud, open has won, right? Open innovation, open source, open culture. That's what's driving all the things we see now, I'd say. >> Yes. >> Well guys, thanks so much, Ben and Reza for stopping by theCUBE and sharing with us what's new at Red Hat and what excites you guys and we look forward to having you back on. >> Thanks so much for having us. >> Thank you. >> We wanna thank you guys for watching theCUBE. Lisa Martin with John Troyer, from DockerCon 2018. Stick around, we'll be right back with our next guest. (upbeat music)

(upbeat music) >> Narrator: Live from Vancouver, Canada, It's theCUBE. Covering OpenStack Summit, North America, 2018. Brought to you by Red Hat, the OpenStack Foundation, and its ecosystem partners. >> Welcome back to theCUBE's coverage of OpenStack Summit 2018, here in Vancouver. Three days wall-to-wall coverage. I'm Stu Miniman with my cohost, John Troyer. Happy to welcome back to the program, Radhesh Balakrishnan, who is the general manager of OpenStack with Red Hat. Radhesh, great to see you. It's been a week since John talked to you, and always good to have you on at the show. >> Great to be on. Good to be here talking about OpenStack at OpenStack Summit. >> Yeah so, look, OpenStack is in the title of your job. I believe, did we have a birthday cake and a party celebrating a certain milestone? >> That is indeed true; so it's the fifth anniversary of that fact that we've had a product, Red Hat OpenStack Platform, on the market. And so, we've been doing a little bit of a look back at how far we have come in the last five years as well as looking ahead at, you know, how does the next three to five years shape as well. >> Yeah, Radhesh, I'm going to date myself and when I think back to, gosh it was 18 years ago, I was working with Linux, and there were kernels all over the place and things like that. And then, I worked for an enterprise storage company and was like, ugh, like keeping up with Chrome.org was a pain in the neck. There came out this thing called Red Hat Advanced Server that was like, oh wait, we can glom onto this, we can support this with our customers, and that eventually turned into RHEL, which, of course, kind of becomes the main standard for how to do Linux. I feel like we have a lot of similarities. >> Radhesh: Absolutely, absolutely. >> In how we did. RHOSP, I believe, is the acronym, so. >> That's exactly right, and we like to have long names. >> Which are very descriptive, but Red Hat OpenStack Platform, fundamentally, to your point brings the same valid proposition that RHEL brought to Linux, to OpenStack, with the twist that, it's not just curated OpenStack, but it's a co-engineered solution of Linux and Cavium and OpenStack. And along the way we learned that, look, it's not just OpenStack and the infrastructure solution. It's done in conjunction with the software-defined storage solution or it's done in conjunction with software-defined networking. Or, fast-forward all the way now, it's being done in conjunction with cloud-native applications running on top of it, right? But regardless, in five years we've been able to grow to address these different demands being placed at infrastructure level, and at the same time evolved to address new-use cases as well; Telco is an example of that. >> Radhesh, let's spend a couple of minutes, though, on the OpenStack Platform itself from Red Hat. Some of the things, guys, that you were bringing to market, I know we talked about, here at the show, fast-forward upgrades, for instance were, they were just introducing, and maybe some other things in the Queens release that you all are bringing forward and have engineered. >> Yeah, thanks for that question, very topical, in the sense that yesterday we launched OSP 13, which is the latest and greatest version based on Queens release. If you look at the innovation packed in that it fundamentally falls in three buckets. One is the bread part that you talked about, whereby, anybody who is standing on OSP 10, which was the prior, long-release lifecycle product, over to 13, how do you kind of get over there in a graceful manner is the first area that we have addressed. The second area is around security, because how do you make sure that OpenStack-based clouds are secure by default, from the day you roll out all the way to until you retire it, right? I don't know if there's going to be a retirement, but that's the intent of all the security enablements that we have in the product as well. And the third one, how do we make sure that containers in OpenStack can come together in a nice manner. >> Yeah, the container piece is something else that, so a lot of effort, here at the show. They announced Kata containers, which, trying to give the security of a VM, lightweight VM. How does Red Hat look at Kata containers? I know Red Hat, you know Linux's containers, you know, very strong position, fill us in on that. >> Yeah, to maybe pull back a little bit and then look at the larger picture of there is the notion of infrastructure or the open infrastructure that you need and OpenStack is a good starting point for that. And then, you overlay on top of that an application deployment management configuration, lifecycle management solution that's the container platform called OpenShift, right. These are the two centers of gravity for the stack. Now, aspects such as Kata containers or Hubbard, which is for again, similar concept of addressing how do you use virtualization in addition to containers to bring some of the value around security et cetera, right? So we are continuing to engage in all these upstream projects, but we'll be careful and methodical in bringing those technologies into our products as we go along. >> Okay, how about Edge is the other kind of major topic that we're having here, I know I've interviewed some Red Hat customers looking at NFV solutions, so some of the big telcos you know specifically that use various pieces. What do you hear from your customers and help us kind of draw that line between the NFV to the Edge. Yeah, so Edge has become the center is kind of the new joke in the sense that, from an NFV perspective, customers have already effectively addressed the CORD errors and the challenges, now it's about how do you scale that and deploy that on a massive scale, right? That's a good problem to have. Now the goodness of virtualization can be brought all the way down to the radio Edge so that a programmable network becomes the reality that a telco or a carrier can get into. So in that context, Edge becomes a series of use cases. You know, it's not just one destination. Another way to say it is there is Edge an objective and there is Edge as a noun. Edge as the objective is a set of technologies that are enabling Edge, Edge networking, right. Edge management, for example, and then Edge as a destination where you have a series of Edge locations starting from CORD error center going all the way to radio. Now, the technology answers for all these are just being figured out right now. So you can say, you know, put crudely, KBM, OpenStack, containers, and Ansible will be all good elements that will come into the picture when it comes to a solution for all these footprints. >> Nice. Radhesh, maybe let's switch over to talk about the summit here, and the people here, filled with people being productive with OpenStack, right? Either looking at it, upgrading it, inheriting it. We talked to people in a bunch of different scenarios Red Hat, huge installed base, and you are good at helping and supporting, and uplifting, and upskilling a set of operators who started with Linux and now have to be responsible for an entire cloud infrastructure. Plus, now, at this conference, we've been talking about containers, we've been talking about open dev, right. That's again broadening the scope of what an operator might have to deal with. How does Red Hat look at that? How are you and your team helping upskill and enhance the role of the operator? >> Yeah, so I think it comes down to, how do we make sure that we are understanding the journey that the operator himself or herself is taking from a career perspective, right, the skill set of evolving from Linux and core automation-related skills to going to being able to understand what does it mean to live with cloud implementation on a day-to-day basis. What does it mean to live with network function virtualization as the way in which new services are going to be deployed. So, our course curriculum has evolved to be able to address all these needs today. That's one dimension, the other dimension is how do we make sure that the product itself is so easy that the journey is getting to a point where the infrastructure is invisible, and the focus is on the application platform on top. So I think we have multiple areas of focus to get to the point where it's so relevant that it's invisible, if that paradox makes sense. That's what we're trying to make happen with OpenStack. >> Radhesh, Red Hat has a very large presence at the show here; we were noting in the keynote the underlying infrastructure didn't get a lot of discussion because it is more mature, and therefore, we can talk about everything like VGPUs and containers, and everything like that. But Red Hat has a lot in the portfolio that helps in some of those underlying pieces. So maybe you can give us some of the highlights there. >> Absolutely, so we aren't looking at OpenStack as the be-all end-all destination for customers, but rather an essential ingredient in the journey to a hybrid cloud. So when you have that lens it becomes natural to you that a portfolio of our offerings, which are either first-party or in conjunction with our partners --we have over 400 partners with whom we have joint solutions as well -- so you naturally take a holistic view and then say, "How do you optimize the experience of ceph plus OpenStack for example." So we were talking about Edge recently, right, in the context of Edge we realize that there is a particular use-case for hyperconverged infrastructure whereby you need to collocate, compute, and store it in a way that the footprint is so small and easy to manage plus you want to have one life-cycle both for OpenStack and ceph right, so to address that we announced, right at hypercloud infrastructure for cloud, as an offering that is co-engineered between ceph team, or our storage team, and the OpenStack team. Right, that's just an example of how, by bringing the rest of the portfolio, we're able to address needs being expressed by our customers today. Or you look forward in terms of use-case, one thing that we are hearing from all our large customers, such as the Amadeus's of the world is, make the experience of OpenShift on OpenStack, easy to deploy and manage, as well as reduce the penalty of running containers on VMs. Because we understand the benefits of security and all of that, but we want to be able to get that without having any penalty of using a virtual infrastructure so that's why we're heavily focused on OpenShift, on OpenStack, as the form-factor for delivering that while continuing to work on things such as Kata containers as well as, you know, Kuryrs, as technology is evolving to make communities much richer as well as the infrastructure management at OpenStack level richer. >> You brought up an interesting point, we spoke a little bit yesterday with John Allessio and Margaret Dawson, about really that kind of multi-cloud world out there, because pieces like Kubernetes and Ansible, aren't just in the data center with this one stack, it's spanning across multiple environments and when we talk to customers, they do cloud, and cloud is multiple things in multiple places and changing all the time. So I'd love to get your viewpoint on what you hear from customers, how Red Hat's helping them across all those environments. >> Absolutely, so the key differentiation we see in being able to provide to our customers is that unlike some of the other providers out there, they're where they are stitching you with a particular private cloud, with the particular public cloud, and then saying, "Hey, this is sort of the equivalent of the AOL walled gardens, if you will, right, that's being created for a particular private and public cloud. What we're saying is fundamentally three things. First is, the foundation of Linux skills from RHEL that you have is going to be what you can build on to innovate for today and tomorrow, that's number one. Secondly, you can invest in infrastructure that is 100% open using OpenStack so that you can use commodity hardware, bring in multiple use-cases which are bleeding it, such as data lags, big data, Apache Spark, or going all the way to cloud-native application, development on top of OpenStack. And then last but not least, when you are embarking on a multi-cloud journey it is important that you're not tied to innovation speed of one particular public cloud provider, or even a private cloud provider, for that matter, so being able to get to a container platform, which is OpenShift, that can run pretty much everywhere, either on PREM or on a public cloud, and give you that single pane of consistency for your application, which is where business and IT alignment is the focus right now, then I think you've got the best of all the worlds. You know, freedom from vendor-lock in, and a future-proof infrastructure and application platform that can take you to where you need to go, right. So pretty excited to be able to deliver on that consistently as of today, as well as in the coming years. >> All right, we just want to give you the final word, for people out there that ... you know, often they get their opinion based on when they first heard of something. OpenStack's been around for a number of years, five years now, with your platform. Give us the takeaway for 2018 here from OpenStack Summit as to how they should be thinking about OpenStack, in that larger picture. >> The key takeaway is that OpenStack is rock-solid, that you can bring into your environment, not just to power your virtual machine infrastructure, but also baremetal infrastructure on which you can bring in containers as well. So if you're thinking about an infrastructure fabric, either to power your telco network or to power your private cloud in its entirety OpenStack is the only place that you need to be looking at and our OpenStack platform from end to end delivers that value proposition. Now the second aspect to think about is, OpenStack is a step in the journey of a hybrid future destination that you can get to. Red Hat not only has the set of surround products and technologies to round-up the solution, but also have the largest partner ecosystem to offer you choice. So what's your excuse from getting to a hybrid cloud today if not tomorrow? >> Well, Radhesh Balakrishnan, thank you for all the updates appreciate catching up with you once again. For John Troyer, I'm Stu Minimam, getting near the end of three days wall-to-wall coverage here in Vancouver, thank you so much for watching theCUBE. (upbeat music)

(upbeat music) >> Announcer: Live from San Francisco, It's the Cube. Covering Red Hat Summit 2018. Brought to you buy, Red Hat. >> Okay, welcome back everyone. We're live here in the Cube in San Francisco, California, Monscone West, Cube's exclusive coverage of Red Hat Summit 2018. I'm John Furrier, co-host. With John Troyer, he's my analyst co- host, he's the co -founder of Tech Reckoning Advisory and Community Development Firm. My next guest is Marco Bill-Peter, Senior vice-president of Customer Experience and Engagement at Red Hat. Welcome back to the Cube. Good to see you. So, you guys have a great track record with customer support. You guys use gold standard in open source, you've done it well, very reliable. It's a changing world. You know, Open Shift now, certainly the center piece, west, new acquisition. A lot of things happening with in the portfolio. Cloud native new capabilities are on the horizon. So, you've got to figure it out. So, what's the support strategy? What do you guys do? How are you looking? I'm sure it's challenging but never too much of a challenge for you guys. You're smart, what's the support strategy? >> I think the recipe it is really like not getting stuck in a wave, right? And be open to, you know I think Jim Whitehurst and his keynote talk quite a bit about, you used to do all plan, describe and execute. That thing just doesn't work, right? Because supporting customers on Linux, supporting them when they move to Open Shift or even application, is a whole different piece. So, as a leader you got to be flexible as in okay, here we do it this way, let's put more money in this. Let's say Open Shift support, Open Shift kind of, what's the customer experience there, right? Kind of figure out how it works. There's a lot of things that scare me in the daily business as in like okay, we can't do that. But I think Red Hat is really good in reconfiguring, Jim talked about that in a keynote as well, reconfiguring the organization. And so, we move for example, quality assurance into my organization and combining that with support. All of them give some more opportunities realizing, oh this product maybe not ready yet for the market, right? We can not support that. Or, you augmented with, I wouldn't call it AI capabilities, but more like those capabilities. All of the sudden stuff gets done automatically. >> And multi cloud is again, just like multi vendor environment, but it's a little bit different obviously. But multiple clouds you have different architectures. You guys do some progressive things. What's new, architecturally within the support group? Because you have deals announced here with IBM and Microsoft, one of them is a joint, I think integrated program where guys are teaming up. >> Microsoft is interesting. >> We've teamed last three, four years, right? With he first deal and gone further. You're like funny, right? I've been at Red Hat so long and you put people on premise. It's kind of funny. But it's good, right? And that's where you got to glue together. Sometimes it's people. Sometimes it's also more having the data, right? I mean if you go multi cloud. Difference between multi vendor, multi cloud. Multi vendor, you just call the vendor and tell them hey you handle it. Here, I'll put data, you handle it. Or maybe you do it a bit better. But, multi cloud is, well it's running there, how do you get access to that? Then the whole privacy laws comes in. So you got to be more instrumentation, you know, telemetry-- >> You're using tech to help you guys out. That's what you're referring by AI. >> I actually think that the next ten years you will see support changing quite a bit. >> John: In what way? >> But also you have to staff this up, right? You need to upscale your folks as well as technology. >> That doesn't go away. But I think you've got to go more that you really need deep skills. If you want to support Open Shift you've got to, either you understand it from the middle side, from the application side or from the bottom from the infrastructure. You need both skill sets. So you need really highly skilled people. But one the other hand if it's really like real time and people don't have patience to wait two weeks, especially if you're in the cloud. More and more tooling. I see the vision as in it would be less and less based on the scale but I think it's less people involved more and more automation, tooling. >> You kind of see it now with boss, kind of just tip of the iceberg. But you've got automation built into the culture of Red Hat. You've put coral west. They want to automate everything. >> You see Insights, right? We launched Insights three years ago out of support. They take support data, find out what's really happening, create rules that if you match it the customer systems say you have this and this issue. And now it's in the incentive stage of the strategy as in we can automate it, but you can automate it. you have a problem, you want to have it solved. >> You're presenting a support service. >> Exactly, and eventually, we'll not even tell you, in maybe hindsight we'll tell you, hey, you had this network issue or configured the wrong way, we fixed it have a good day. >> Well it came up in Cooper Netty's conversation we had last week in Copenhagen, we were in Denmark for CubeCon around things Cooper Netty's defacto standing, so great stuff, that's certainly great. Istio service mesh is atopic that's highly discussed. And one of the thing that comes up is the automation the down side is potentially it fixes things. So, you could have a memory leak for instance, that you never know gets fixed. But it just crashes every day and reboots itself. So, the new kinds of instrumentation that's emerging. So this is really the though job. >> Yeah. Yeah. >> How do you get in there-- >> Also have automation-- >> And you as the central provider, right, are pulling in data from across the world and across the customer base. So how do you take that, sift it to be more proactive about decision making and support. >> So we capture all this support data. And you know it's fascinating, we have some AI capabilities, some machine learning capabilities go through there. But it's fascinating, sometimes we see new issues coming up. What we do is then, we go well let's look who is exposed to that, just to get a footprint. And then you actually inform customers, hey, you had this and this issue or you have this. It's really a different, I want to get more proactive or I want to get more automated. With the automation I just want to be, right, so we installed, over the last, I would say 18 months, like a bot, simple bot basically, his name is Edmond. And he works on support cases. And we started slow, very slow. We didn't let it go as in total machine or anything. But now, I gave some stats earlier today. In one used case it's 25 percent faster solving a customer issue using Edmond. And he participates in 11 percent of all support cases. >> Wow. >> Edmond is a busy guy. >> And the game is changing too. I mean in the old days, first lines support, second lines support, offline support, then escalation. These things are older IT mechanisms. With this you're talking about completely doing away with, in essence first line support. But also first line support might come in, from say a Microsoft or an IBM. You've got to be ready for anything. >> Actually I think it's not just first line support. And it's not replacing them. It's helping them. It's really making them faster, right? I think the frustration piece is, like, customer opens his support case, some data is missing, right? So, you have a que it gets to that. Engineering looks and oh, there's data missing. Edmond sees that and says hey, I need this data. Based on all the support cases we fixed similar issues, this is the data we need. So Edmond gets the data ready, engineer looks and in some cases Edmond actually closes it out. >> Closes it out. >> Tells the customer here there's a better solution, do it this way. >> Yeah, that's fascinating. >> I'd love to pull the camera back a little bit, right? You are not the SVP of support. You're the SVP of customer experience and engagement, right? That's an entirely different role in some ways, in that you're responsible for customer success at some level. >> That is correct, yeah. >> Talk a little bit about reconfiguring organization to be that-- >> So I think maybe dive in a little bit on the customer success. So we have a organization, they call technical account. It's part of the customer success organization. That's a human business but it's fascinating, right. We put these claims on clients and have them work together. They understand the business. It's an old business but trust me, having still a human in there understanding, okay this is customer x, y, z. That's the business objective, I talked about this today as well, not to forget, hey this customer actually wants to do whatever, whatever on the like an SIP to actually take that further to actually support case and doing that the team helps quite a bit. And then also the commitment, right? We don't want just to do support cases and then that's why you renew with Red Head, we want to make sure you actually get value out of it and that's why you want to renew. So that's why we configured different. It's bigger, right? It's bigger as in really making sure the product is correct. So that's why quality assurance is in my team, this support. That's why I run internal IT for the engineering team. We run the stuff that we sell actually earlier. And some of my team is like, Marco why do we have to do that? Because we learn and I much rather have you feel the pain than the customer feel the pain. That's why we configure different than, I've been 12 a half years right on this and it's still exciting that we are still able to change around-- >> I think the quality assurance piece is still big too cause you're in there as well. Looking at the QA. >> Yeah. >> Making sure that's good too. You're testing out the products and doing QA all within the mindset of customer experience. >> Exactly, and you've got to move that being agile, is more you see developers actually submitting test cases. Tests, so that's the component testing and the basic tests. What we got to do more, is what you mentioned, if somebody does less with Open Shift to contain all that, that thing together, if some service software defines storage, that thing together to bring together that's the hard drive. So I want to move more and more. That we take used spaces from customers, we'll close it. This is how we do it. X, y, z, customer and apply that. >> At the end of the day it's the same game different playing field. The customer wants choice, best possible solution experience, for them. You guys got to enable that, and then support it, make it happen. >> Yeah. >> And with cloud. >> And you see how, I don't know if you saw the demo yesterday when they show basically I think or Amazon was slower and every traffic that routed. This is reality as well, right? I mean if you look at one press release we did yesterday, I just find it a fascinating story. They're kitchen appliances. I don't know if you saw that. But they have over a million kitchen appliances or cooking appliances connected to the internet. It's a German, Swiss company when they got to upgrade the system so they get recipes done, they actually spin up instances in Alibaba in Asia and I think in Amazon in the U.S. They spin it up, they scale out all the appliances connect then they shrink it together. How do you support these customers a whole different case. >> That's great for the customer. >> Yeah. >> But more of a challenge for you guys. >> Then again with preparation of the right integration testing before, with the right set up that we know this is what the customer is doing this weekend. Amadeus as well, talked at the keynote, we worked long time with Amadeus. >> You're a smart team. >> As part of your customer role, you were involved with the Innovation awards. They were up on stage this morning. What struck me was they were both about time to value. And speed of deployment as well as scale. Often these were global companies, we had Amadeus on yesterday, spanning the globe. Huge number of transactions. Anything stand out to you in those Innovation Awards this year? Perhaps, that's been different in previous years? I think that the scale is actually interesting that you say. I think we have much quicker now. I think that's awesome, technology matures. I think we used to have more smaller work projects in getting to a certain scale. But I just goes faster. I think the controlled piece is probably a bit more accepted. This whole containerization is not magic anymore. I think a lot is being moved, is coming from the development side but also from the Linux side. So I think there's a less struggle of that. But I do still see some cultural struggles. You talk to customers, maybe not the Innovation Award winners. but even them they say, hey it took us a long time to convince internal structures, how we change things around. >> Talk about the open source role because you mentioned, before we came on how you guys are all in the open, an open source. Is there like a project that you're part of that supports centric? Is there certain things you're picking out over the source? As you guys do the QA and build you own stuff. >> Yeah we do a lot. We submit a lot to open. There's very few. We don't share data. We can't share customer data for obvious reasons. But tooling, most of the tooling we share if it's data collectors. We re an open source road. There' not much that we don't, there's nothing proprietary. Engineers, that's why they're coming to write. That's the configuration. They want to see, hey how does this stuff get applied. They own the packages, then some stuff is shared. If it's tied to the customer portal, the AI pieces maybe the open source parts of it but-- >> What's it like this year, for the folks who are watching who couldn't make it? What's the vibe here at Red Hat Summit 2018? What's the hallway conversations like? What's some of the dinners? What are you talking about? What's the chatter? >> I think the big chatter for me is kind of like this Open Shift, containers, agile development. You know the agile development comes back and back and really like how do we do this right? And tech connects obviously, how do you take application develop them or how do you take applications put them in a container. And then you see these demos. With multi cloud. >> New applications is not stand alone Linux anymore. >> Yeah. We have containers and tend to be able to run public cloud or multi cloud on premise. The options are endless. And I think that's the strengths from Red Hat. We prove that with Linux we can have a solid API. We don't screw up the applications. And if we can guarantee that across the four footprints, that's Paul's vision five, six years ago. I think we are there. >> You talked about a bit of cultural shift. How can Red Hat help it's customers come up to speed? That's a little bit...but be more agile. >> It's a good example. I think we do a lot of these sessions. I actually think that our sales motion, they are pretty aware with open sources, what the culture is. They do a lot of these sessions with customers. Jim Whitehurst is actually awesome. When he comes to clients. We did a C level event at a bank, based in Zurich and it was in a Swiss bank. And I think that they got like 140 C level, CIO groups. And Jim did a talk about the open organization about breaking down the barriers. I think that's a role that we play. Well some is Red Hat's role, but we go to do that stuff. Because we can share part of it in how we are configured, how we are different. >> I think that kind of thing is high on every CIO's list of agendas. >> And everything in the open is proving that open is winning. Open beats closed pretty much every time and is now pretty standard operating wise we're starting to see but operational wise, not just for software development. >> I actually think that from practice and how to run the company. Some stuff is transparency, right? If you work in a company that you're not transparent with your associates, can you really do this in 2018? >> No. >> And so I think those are elements that I think we do well to have had. And we got to keep internal as well, reminding ourselves, these core principles from open source are really important. >> Hiring, so you're bringing new Red Hatters in? >> At the rate we are hiring it's actually big concerns. How do we maintain this culture, right. This talk is not always polite but it's the way we function. >> You guys are humble. You're playing the long game, I love that about you. So congratulations Marco. Thanks for coming on the Cube show. >> Thanks very much. >> Thanks. >> It's the Cube Live here in San Francisco for Red Hat Summit 2018 here in Moscone West. I'm John Furrier and John Troyer. Stay with us for more live coverage after this short break. (upbeat music)

San Francisco it's the Red Hat summit 2018 brought to you by Red Hat okay welcome back everyone this is the cube live in San Francisco for Red Hat summit 2018 I'm John for the co-host of the cube and this week for three days of wall-to-wall coverage my co-host analyst is John Tory the co-founder of check reckoning and advisory and community development services firm industry legend formerly VMware's Bentley he was at the Q in 2010 our first ever cube nine years ago John Day one wrap up let's analyze what we heard and dissect and and put Red Hat into day one in the books but you know clearly it's a red-letter day for red hat so to speak your thoughts big day for open shift I think and hybrid cloud right we just saw a lot of signs here that we'll talk about that it's real there's real enterprises here real deployments in the cloud multi-cloud on-site hybrid cloud and i think there's really no doubt about that they really brought a brought the team out and you know red hat's become a bellwether relative to the tech industry because if you look at what they do there's so many irons on the fires but more the most important is that they have huge customer base in the enterprise which they've earned over a decades of work being the open source renegade to the open source darling and Tier one citizen they got a huge install basin they got to manage this so they can't just throw you know spaghetti at the wall they gotta have big solutions they're very technical company very humble but they do make some good tech bets absolutely we'll be talking with the folks from core OS tomorrow they have a couple of other action you know things we'll be talking about a lot of interesting partnerships the the most you know the thing here Linux is real and it's is the 20-year growth and that it's real in the enterprise and I mean the top line think the top line slowed and John is is is kubernetes than the gnu/linux for the cloud and I got to say there's some reality there yeah it's there's no doubt about it I mean then I've got my notes here just my summary for the day is on that point the new wave is here okay the glue layer that kubernetes and containers provide on top of say Linux in this case OpenShift a you know alternative past layer just a few years ago becomes the centerpiece of red hats you know architecture really providing some amazing benefits so I think what's clear is that this new shift this new wave is massive and we've heard on the cube multiple references to tcp/ip HTTP these are seminal moments where there's a massive inflection point where the games just radically changes for the better wealth creation happens startups boom new brands emerged that we've never heard of that just come out of the woodwork entrepreneurial activity hits an all-time high and they all these things are coming yeah I said John I was really impressed if we talk to a number of folks who are involved with technologies that some people might call legacy right we the Java programmers the IBM WebSphere folks they've been you you look at these technologies solid proven tested but yet still over here and adapted for today right and they talked about how they're fitting into openshift how they're fitting into modern application development and you're not leaving those people behind they're really here and you know the old joke going back to say Microsoft when Steve Ballmer was the CEO hell will freeze over when Linux isn't in in Microsoft ecosystem look today no further than what's going on in their developer Commerce called Microsoft build where Linux is the centerpiece of their open-source strategy and Microsoft has transformed themselves into a total open-source world so you know now you got Oracle with giving up Java II calling a Jakarta essentially bringing Java into an the Eclipse community huge move it's a kind of a nuance point but that's another signal of the shifts going on out in the open where communities aren't just yesterday's open source model a new generation of open source actors are coming in a new model I think the CNC F is showing it the Linux Foundation proves that you can have commercialization downstream with open source projects as that catalyst point as a big deal and I think that is happening at a new new level and it's super exciting to see yeah I mean open source is the new normal sure that that works it's in the enterprise but that doesn't mean that open source disappears it actually means that open source and communities and companies coming together to drive innovation actually gets more and more important I kind of thought well you know it's open source well everybody does open source but actually the the dynamics we're seeing of these both large companies partnering with small companies foundations like you talked about the Linux cutlasses various parts the Linux Foundation cloud boundary foundation etc right are really making a big impact well we had earlier on assistant general counsel David Levine and bringing about open source I think one key thing that's notable is this next generation of open source wave comes is the business model of open source and operationalizing it in not just server development lifecycle but in the business operation so for example spending resources on managing proprietary products with that have open source components separate from the community is a resource that you don't have to spend anymore if you just contribute everything to open source that energy can go away so I think open source projects and the product monetization component not new concepts is now highlighted as a bonafide competitive advantage across the company not just proven but like operationally sound legally verified certified and I think also you have to look at the distribution of open source versus the operation and management of open source we see a lot of management managed kubernetes coming out and in fact we didn't talk about today Microsoft big announcement here at the show Microsoft is on Azure is running a managed open ship not not kubernetes they already have kubernetes they're running a managed open ship another way of adding value to an open open source platforms to date directly to the IT operator honestly do you think these kind of deals would happen if you go back four years three years ago oh no way as you're running an open shift absolutely I mean were you crazy the you know the kingdom is turned upside down absolutely this is a notable point I want to get your reaction is because I see this absolutely as validation to the new wave being here with kubernetes containers as a de facto rallying point an inflection point big deals are happening IBM and Red Hat big deal we just talked about them with the players here two bellwether saying we're getting behind containers and two bays in a big way from that relationship essentially it changes the game literally overnight for IBM changes the game for Red Hat I think a little bit more for IBM than Red Hat already gets a ton of benefit but IBM instantly gets a cloud strategy that has a real scalable product market to it Arvind the the head of research laid that out and IBM now can go and compete with major players on deals with the private cloud more deals are coming absolutely this is the beginning now that everyone snapped into place is saying okay kubernetes and containers we now understand this the rallying cry a de facto standard I think a formation is going to happen in the next six to 12 months of major major major players now I mean we are in a not one size does not fit all world John so I mean we will continue to see healthy ecosystems I mean mesosphere and DT cos is still out there Dockers still out there right you will see very functional communities and and functioning application platforms and cloud platforms but you got to say the momentum is here I mean look at amine docker mace those fears look at when things like this happened this is my opinion so I'm just gonna say it out there when you have de facto standards that happen like this it's an opportunity to differentiate so I think what's gonna happen is docker meso sphere and others including the legacy guys like IBM and in others they have to differentiate their products they have to compete software companies so I think docker I think is come tonight at docker con but my opinion looking at from the outside is I think Dockers realized looking we can't make money from containers kubernetes is happening we're a great standard in that let's be a software company let's differentiate around kubernetes so this is just more pressure or more call-to-action to deliver good software hey it's never been of somebody said it's never been a better time to be an IT and IT infrastructure right this is a you think that the tools we have available to us super-powerful another key point I want to get your reaction on with kubernetes and containers this kind of de facto standardization is breathing new life into good initiatives and legacy projects so you think about OpenStack okay OpenStack gets a nice segmented approach is now clear with a where the swim lanes are you're an app developer you go over here and if you are a network and infrastructure guy you're going here but middleware a from talk to the Red Hat guys here we talk to IBM those legacy and apps can put a container around it and don't have to be thrown away and take their natural course now I think it's gonna be a three line through this holy a second life is for legacy and stuff and then to cloud is and it's in second inning because now you have the enablement for cloud your reaction the enablement of cloud Ibn iBM has cloud and then the market shares of nm who you believe they're not in that they're in the top three but they're not double digits according to synergy research and he bought us a little bit higher but still if you compare public cloud they're small they look at IBM's and tire and small base and saying if they have a specialty cloud that can be assembled quit Nellie yeah and scaled and maybe instantly successfully overnight yeah I think a few years ago you know there was a lot different always a few years back it always looks confusing right a few years back we were still arguing public cloud private cloud as private cloud ed is what is a true private cloud is that even valuable I still see people on Twitter making fun of everything anybody who's not 100% into the full public cloud which means they must not have talked to you know a lot of IT folks who have to business to run today so I think you're saying it's a it's a it's a multivalent world multi-cloud there's going to be differentiated clouds there's going to be operational clouds there's gonna be financial clouds and just it's it seems clear that you know from the perspective of right now here in San Francisco and 2018 that that you know the purpose of public-private hybrid seems pretty clear just like the purpose of like I said we're gonna in two weeks we'll be an openstack summit I mean the purpose of that seems pretty clear it's it's funny it's like I had this argument and each Assateague he thinks everything should go the public cloud goes eaten has one of the public clouds but he's kind of right and I and I and we talked about this way I with him I said if everything is running cloud operation we're talking about cloud ops we're talking about how its managed how its deployed code bases across the board if everything is clarified from an OP raishin standpoint the Dearing on Prem and cloud and IOT edge is there's no difference stuffs moving around so you almost treats a data center as an edge network so now it's sexually all cloud in my mind so then and also you do have to keep in mind time time horizons right anybody who has to do work the today this quarter right has to keep in mind what's what what portfolio of business deeds and tools do I have right now versus what it's gonna look like in a few years all right so I want to get your thoughts on your walk away from today I'll start my walk away from day one was talking some of the practitioners Macquarie Bank and Amadeus to me they're a tell signed the canary in the coalmine what's happening horizontally scalable synchronous infrastructure the new model is here now we're seeing them saying things like it's a streaming world not just Kafka for streaming data streaming services levels of granularity that at workers traded with containers and kubernetes up and down the stack to me architects who think that way will have a preferred advantage over everybody else that to me was like okay we're seeing it play out I guess I totally agree right the future isn't evenly distributed my takeaway though is there's certainly a future here and the people we talked to today are doing real-world enterprise scale multi-cloud micro services and modern architectures incorporating their legacy applications and components and that and they're just doing it and they're not even breaking a sweat so I think IT has really changed ok day one coverage continues day two tomorrow we have three days of wall-to-wall coverage day two and then finally day three Thursday here in San Francisco this is the cubes live coverage go to the cube dotnet to check out all the videos they're gonna be going up as soon as they are done live here and check out all the cube alumni and check out Silicon angle comm for all news coverage then of course you got tech reckoning Jon's company's the co-founder of for John Fourier and John Shroyer that's day one in the books thanks for watching see you tomorrow

[Music] from San Francisco it's the covering Red Hat summit 2018 brought to you by Red Hat everyone welcome back is the cubes live coverage here in San Francisco Red Hat summit 2018 I'm Sean furry co-host of the cube with my coasts analyst this week John Troyer who's the co-founder of tech reckoning advisory and Community Development firm our next guess is red hash Balakrishnan is the general manager of OpenStack for Red Hat welcome to the cube good to see you ready to be here so OpenStack is very hot obviously with the with the with the trends we've been covering from day one been phenomenal to watch that grow and change but with kubernetes you seeing cloud native to robust communities you got application developers and you got under the hood infrastructure so congratulations and you know what's what's the impact of that what is how is OpenStack impacted by the cloud native trend and what is Red Hat doing they're the best epidermis ation of that is openshift on OpenStack if you had caught the keynotes earlier today there was a demo that we did whereby they were spawning open shifts on bare metal using OpenStack and then you run open shift on power that's what we kind of see as the normed implementation for customers looking to get - I want an open infrastructure on Prem which is OpenStack and then eventually want to get to a multi cloud application platform on top of it that makes up the hybrid cloud right so it's a essential ingredient to the hybrid cloud that customers that are trying to get to and open shifts role in this is what I'm assuming we are asked about openshift ownerships will be multi cloud from a application platform perspective right so OpenStack is all about the infrastructure so as long as you're worrying about info or deployment management lifecycle that's going to be openstax remet once you're thinking about applications themselves the packaging of it the delivery of it and the lifecycle of it then you're in openshift land so how do you bring both these things together in a way that is easier simpler and long-standing is the opportunity and the challenge in front of us so the good news is customers are already taking us there and there's a lot of production workflow is happening on OpenStack but I got to ask the question that someone might ask who hasn't been paying attention in a year or so it was thick hey OpenStack good remember that was what's new with OpenStack what would you say that person if they asked you that question about what's new with OpenStack the answer would be something along the lines of boring is the new normal right we have taken the excitement out of OpenStack you know the conversations are on containers so OpenStack has now become the open infrastructure that customers can bring in with confidence right so that's kind of the boring Linux story but you know what that's what we thrive on right our job as reddit is to make sure that we take away the complexities involved in open source innovation and make it easy for production deployment right so that's what we're doing with OpenStack too and I'm glad that in five years we've been able to get here I definitely I think along with boring gos clarity right last year the cube was that OpenStack summit will be there again in two weeks so with you and I enjoy seeing you again for it the last year there was a lot of you know containers versus there was some confusion like where people got sorted out in their head oh this is the infrastructure layer and then this is the a play I think now people have gotten it sorted out in their head open open shipped on OpenStack very clear message so a meaning of the community in two weeks in any comments on the growth of the open OpenStack community the end users that are there the the depth of experience it seemed like last year was great everywhere for OpenStack on the edge it ended you know set top devices and pull top devices all the way to OpenStack in in private data centers and and for various security or logistical reasons where is OpenStack today yeah I think that he phrased would be workload optimization so OpenStack has now evolved to become optimized for various workloads so NFV was a workload that people were talking about now people are in when customers are in production across the globe you know beat Verizon or the some of the largest telcos that we have in any and a pack as well the fact that you can actually transform the network using OpenStack has become real today now the conversation is going from core of the data center to the edge which is radio networks so the fact that you can have a unified fabric which can transcend from data center all the way to a radio and that can be OpenStack is a you know great testament to the fact that a community has rallied around OpenStack and you know delivering on features that customers are demanding pouring is the new normal of that is boring implies reliable no-drama clean you know working if you had to kind of put a priority in a list of the top things just that it are still being worked on I see the job is never done with infrastructure always evolving about DevOps certainly shows that with programmability what are the key areas still on the table for OpenStack that are that are key discussion points where there's still innovation to be done and built upon I think the first one is it's like going from a car to a self-driving car how can we get that infrastructure to autonomously manage itself we were talking about network earlier even in that context how do you get to a implementation of OpenStack that can self manage itself so there's a huge opportunity to make sure that the tooling gets richer to be able to not just deploy manage but fine-tune the infrastructure itself as we go along so clearly you know you can call it AI machine learning implementation you on OpenStack to make sure that the benefit is occurring to the administrator that's an opportunity area the second thing is the containers and OpenStack that we taught touched upon earlier OpenShift on OpenStack in many ways is going to be the cookie cutter that we're gonna see everywhere there's going to be private cloud if you've got a private cloud it's gotta be an open shift or on OpenStack and if it's not I would like to know why right it's a it becomes a de-facto standard you start to have and they enablement skills training for a few folks as you talk to the IT consumer right the the IT admins out there you know what's the message in terms of upskilling and managing say an OpenStack installation and and what does Red Hat doing to help them come along yeah so those who are comfortable with Braille Linux skills are able to graduate easily over to OpenStack as well so we've been nationally focused on making sure that we are training the loyal Linux installed based customers and with the addition of the fact that now the learnings offerings that we have are not product specific but more at the level of the individual can get a subscription for all the products that reddit has you could get learning access to learning so that does help make sure that people are able to graduate or evolve from being able to manage Linux to manage a cloud and the and face the brave new world of hybrid cloud that's happening in front of our eyes but let's talk about the customer conversations you're having as the general manager of the stack red hat what what are the what's the nature of the conversations are they talking about high availability performance or is it more under the hood about open shift and containers or they range across the board depending upon the use cases whose they do range but the higher or the bit is that applications is where the focuses well closes where the focus is so the infrastructure in many ways needs to get out of the way to make sure that the applications can be moving from the speed of thought to execution right so that's where the customer conversations are going so which is kind of ties back to the boring is the new normal as well so if we can make sure that OpenStack is boring enough that all the energy is focused on developing applications that are needed for the enterprise then I think the job is done self-driving OpenStack it means when applications are just running and that self-healing concepts you were talking about automation is happening exactly that's the opportunity in front of us so you know it's by N's code by code we will get there I think I love the demo this morning which showed that off right bare metal stacks sitting there on stage from different vendors right actually you're the you know OpenStack is the infrastructure layer so it's it's out there with servers from Dell and HP II and others right and then booting up and then the demo with the with Amadeus showing you know OpenStack and public clouds with openshift all on top also showed how it fit into this whole multi cloud stack is it is it challenging to to be the layer with with the hardware hardware heterogeneous enough at this point that OpenStack can handle it are there any issues they're working with different OEMs and if you look at the history of red add that's what we've done right so the rel became rel because of the fact that we were able to abstract multi various innovation that was happening at the so being able to bring that for OpenStack is like we've got you know that's the right to swipe the you know employee card if you will right so I think the game is going back to what you were only talking about the game is evolving to now that you have the infrastructure which abstracts the compute storage networking etc how do you make sure that the capacity that you've created it's applied to where the need is most right for example if you're a telco and if you're enabling Phi G IOT you want to make sure that the capacity is closest to where the customer fool is right so being able to react to customer needs or you know the customers customers needs around where the capacity has to be for infrastructure is the programmability part that we've you know we can enable right so that's a fascinating place to get into I know you are technology users yourself right so clearly you can relate to the fact that if you can make available just enough technology for the right use case then I think we have a winner at hand yeah and taking as you said taking the complexity out of it also means automating away some of those administrative roles and moving to the operational piece of it which developers want to just run their code on it kind of makes things go a little faster and and so ok so I get that and I but I got to ask the question that's more Redhead specific that you could weigh in on this because this is a real legacy question around red hats business model you guys have been very strong with rel the the the record speaks for itself in terms of warranty and and serviceability you guys give like I mean how many years is it now like a zillion years that support for rel OpenStack is boring is Red Hat bringing that level of support now how many years because if I use it I'm gonna need to have support what's the Red Hat current model on support in terms of versioning xand the things that you guys do with customers thank you for bringing that up what have you been consciously doing is to make sure that we have lifecycle that is meeting two different customers segments that we are talking about one is customers who want to be with the latest and the greatest closer to the trunk so every six months there is an openstack released they want to be close enough they want to be consuming it but it's gotta be production ready in their environment the second set of customers are the ones who are saying hey look the infrastructure part needs to stay there cemented well and then every maybe a couple of years I'll take a real look at you know bringing in the new code to light up additional functionality or on storage or network etc so when you look at both the camps then the need is to have a dual life cycle so what we have done is with OpenStack platform 10 which is two years ago we have a up to five year lifecycle release so obvious that platform 10 was extensible up to five years and then every two releases from there 11 and 12 are for just one year alone and then we come back to again a major release which is OSP 13 which will be another five years I know it can be and they get the full Red Hat support that they're used to that's right so there are years that you're able to either stay at 10 or you could be the one who's going from 10 to 11 to 12 to 13 there are some customers were saying staying at 10 and then I won't go over to 13 and how do you do that we'll be a industry first and that's what we have been addressing from an engineering perspective is differentiated - I think that's a good selling point guy that's always a great thing about Red Hat you guys have good support give the customers confidence or not you guys aren't new to the enterprise and these kinds of customers so right - what are you doing here at the show red hat summit 2018 what's on your agenda what some of the hallway conversations you're hearing customer briefings obviously some of the keynote highlights were pretty impressive what going on for you it's a Volvo OpenShift on OpenStack that's where the current and the future is and it's not something that you have to wait for the reality is that when you're thinking about containers you might be starting very small but the reality is that you're going to have a reasonably sized farm that needs to power all the innovation that's going to happen in your organization so given that you need to have an infrastructure management solution thought through and implemented on day one itself so that's what OpenStack does so when you can roll out OpenStack and then on top of it bring in openshift then you not only have to you're not only taking care of today's needs but also as you scale and back to the point we were talking about moving the capacity where is needed you have a elastic infrastructure that can go where the workload is demanding the most attention so here's another question that might come up from when I asked you and you probably got this but I'll just bring it up anyway I'm a customer of OpenStack or someone kicking the tires learning about deploying up a stack I say ritesh what is all this cloud native stuff I see kubernetes out there what does that mean for me visa V OpenStack and all the efforts going on around kubernetes and above and the application pieces of the stack right let's say if you looked at the rear view mirror five years ago when we looked at cloud native as a contract the tendency was that hey look I need to be developing net new applications that's the only scenario where cloud native would be thought thought off now fast forward five years now what has happened is that cloud native and DevOps culture has become the default if you are a developer if you're not sort of in that ploughed native and DevOps then you are working on yesterday's problem in many ways so if digital transformation is urging organizations to drive - as cloud native applications then cloud native applications require an infrastructure that's fungible inelastic and that's how openshift on OpenStack again coming back to the point of that's the future that customers can build on today and moving forward so summarize I would say what I heard you saying periphery if I'm wrong open ship is a nice bridge layer or an up bridge layer but a connection point if you bet on open ship you're gonna have best of both worlds that that's a good summary and you gotta be you know betting on open first of all is the first order a bet that you should be making once you've bet on open then the question is you gotta bet on an infrastructure choice that's OpenStack and you gotta bet on an application platform choice that's open shift once you've got both of these I think then the question is what are you going to do with your spare time okay count all the cash you're making from all the savings but also choice is key you get all this choice and flexibility is a big upside I would imagine British thanks for coming on sharing your insight on the queue appreciate it thanks for letting us know what's going on and best of luck see you in Vancouver thank you for having okay so the cube live coverage here in San Francisco for Red Hat summit 2018 John four with John Troy you're more coverage after this short break

[Music] [Music] [Music] [Laughter] [Laughter] [Laughter] [Laughter] [Music] [Music] [Music] [Music] you you [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Applause] [Music] wake up feeling blessed peace you warned that Russia ain't afraid to show it I'll expose it if I dressed up riding in that Chester roasted nigga catch you slippin on myself rocks on I messed up like yes sir [Music] [Music] [Music] [Music] our program [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] you are not welcome to Red Hat summit 2018 2018 [Music] [Music] [Music] [Laughter] [Music] Wow that is truly the coolest introduction I've ever had thank you Wow I don't think I feel cool enough to follow an interaction like that Wow well welcome to the Red Hat summit this is our 14th annual event and I have to say looking out over this audience Wow it's great to see so many people here joining us this is by far our largest summit to date not only did we blow through the numbers we've had in the past we blew through our own expectations this year so I know we have a pretty packed house and I know people are still coming in so it's great to see so many people here it's great to see so many familiar faces when I had a chance to walk around earlier it's great to see so many new people here joining us for the first time I think the record attendance is an indication that more and more enterprises around the world are seeing the power of open source to help them with their challenges that they're facing due to the digital transformation that all of enterprises around the world are going through the theme for the summit this year is ideas worth exploring and we intentionally chose that because as much as we are all going through this digital disruption and the challenges associated with it one thing I think is becoming clear no one person and certainly no one company has the answers to these challenges right this isn't a problem where you can go buy a solution this is a set of capabilities that we all need to build it's a set of cultural changes that we all need to go through and that's going to require the best ideas coming from so many different places so we're not here saying we have the answers we're trying to convene the conversation right we want to serve as a catalyst bringing great minds together to share ideas so we all walk out of here at the end of the week a little wiser than when we first came here we do have an amazing agenda for you we have over 7,000 attendees we may be pushing 8,000 by the time we got through this morning we have 36 keynote speakers and we have a hundred and twenty-five breakout sessions and have to throw in one plug scheduling 325 breakout sessions is actually pretty difficult and so we used the Red Hat business optimizer which is an AI constraint solver that's new in the Red Hat decision manager to help us plan the summit because we have individuals who have a clustered set of interests and we want to make sure that when we schedule two breakout sessions we do it in a way that we don't have overlapping sessions that are really important to the same individual so we tried to use this tool and what we understand about people's interest in history of what they wanted to do to try to make sure that we spaced out different times for things of similar interests for similar people as well as for people who stood in the back of breakouts before and I know I've done that too we've also used it to try to optimize room size so hopefully we will do our best to make sure that we've appropriately sized the spaces for those as well so it's really a phenomenal tool and I know it's helped us a lot this year in addition to the 325 breakouts we have a lot of our customers on stage during the main sessions and so you'll see demos you'll hear from partners you'll hear stories from so many of our customers not on our point of view of how to use these technologies but their point of views of how they actually are using these technologies to solve their problems and you'll hear over and over again from those keynotes that it's not just about the technology it's about how people are changing how people are working to innovate to solve those problems and while we're on the subject of people I'd like to take a moment to recognize the Red Hat certified professional of the year this is known award we do every year I love this award because it truly recognizes an individual for outstanding innovation for outstanding ideas for truly standing out in how they're able to help their organization with Red Hat technologies Red Hat certifications help system administrators application developers IT architects to further their careers and help their organizations by being able to advance their skills and knowledge of Red Hat products and this year's winner really truly is a great example about how their curiosity is helped push the limits of what's possible with technology let's hear a little more about this year's winner when I was studying at the University I had computer science as one of my subjects and that's what created the passion from the very beginning they were quite a few institutions around my University who were offering Red Hat Enterprise Linux as a course and a certification paths through to become an administrator Red Hat Learning subscription has offered me a lot more than any other trainings that have done so far that gave me exposure to so many products under red hair technologies that I wasn't even aware of I started to think about the better ways of how these learnings can be put into the real life use cases and we started off with a discussion with my manager saying I have to try this product and I really want to see how it really fits in our environment and that product was Red Hat virtualization we went from deploying rave and then OpenStack and then the open shift environment we wanted to overcome some of the things that we saw as challenges to the speed and rapidity of release and code etc so it made perfect sense and we were able to do it in a really short space of time so you know we truly did use it as an Innovation Lab I think idea is everything ideas can change the way you see things an Innovation Lab was such an idea that popped into my mind one fine day and it has transformed the way we think as a team and it's given that playpen to pretty much everyone to go and test their things investigate evaluate do whatever they like in a non-critical non production environment I recruited Neha almost 10 years ago now I could see there was a spark a potential with it and you know she had a real Drive a real passion and you know here we are nearly ten years later I'm Neha Sandow I am a Red Hat certified engineer all right well everyone please walk into the states to the stage Neha [Music] [Applause] congratulations thank you [Applause] I think that - well welcome to the red has some of this is your first summit yes it is thanks so much well fantastic sure well it's great to have you here I hope you have a chance to engage and share some of your ideas and enjoy the week thank you thank you congratulations [Applause] neha mentioned that she first got interest in open source at university and it made me think red hats recently started our Red Hat Academy program that looks to programmatically infuse Red Hat technologies in universities around the world it's exploded in a way we had no idea it's grown just incredibly rapidly which i think shows the interest that there really is an open source and working in an open way at university so it's really a phenomenal program I'm also excited to announce that we're launching our newest open source story this year at Summit it's called the science of collective discovery and it looks at what happens when communities use open hardware to monitor the environment around them and really how they can make impactful change based on that technologies the rural premier that will be at 5:15 on Wednesday at McMaster Oni West and so please join us for a drink and we'll also have a number of the experts featured in that and you can have a conversation with them as well so with that let's officially start the show please welcome red hat president of products and technology Paul Cormier [Music] Wow morning you know I say it every year I'm gonna say it again I know I repeat myself it's just amazing we are so proud here to be here today too while you all week on how far we've come with opens with open source and with the products that we that we provide at Red Hat so so welcome and I hope the pride shows through so you know I told you Seven Summits ago on this stage that the future would be open and here we are just seven years later this is the 14th summit but just seven years later after that and much has happened and I think you'll see today and this week that that prediction that the world would be open was a pretty safe predict prediction but I want to take you just back a little bit to see how we started here and it's not just how Red Hat started here this is an open source in Linux based computing is now in an industry norm and I think that's what you'll you'll see in here this week you know we talked back then seven years ago when we put on our prediction about the UNIX error and how Hardware innovation with x86 was it was really the first step in a new era of open innovation you know companies like Sun Deck IBM and HP they really changed the world the computing industry with their UNIX models it was that was really the rise of computing but I think what we we really saw then was that single company innovation could only scale so far could really get so far with that these companies were very very innovative but they coupled hardware innovation with software innovation and as one company they could only solve so many problems and even which comp which even complicated things more they could only hire so many people in each of their companies Intel came on the scene back then as the new independent hardware player and you know that was really the beginning of the drive for horizontal computing power and computing this opened up a brand new vehicle for hardware innovation a new hardware ecosystem was built around this around this common hardware base shortly after that Stallman and leanness they had a vision of his of an open model that was created and they created Linux but it was built around Intel this was really the beginning of having a software based platform that could also drive innovation this kind of was the beginning of the changing of the world here that system-level innovation now having a hardware platform that was ubiquitous and a software platform that was open and ubiquitous it really changed this system level innovation and that continues to thrive today it was only possible because it was open this could not have happened in a closed environment it allowed the best ideas from anywhere from all over to come in in win only because it was the best idea that's what drove the rate of innovation at the pace you're seeing today and it which has never been seen before we at Red Hat we saw the need to bring this innovation to solve real-world problems in the enterprise and I think that's going to be the theme of the show today you're going to see us with our customers and partners talking about and showing you some of those real-world problems that we are sought solving with this open innovation we created rel back then for this for the enterprise it started it's it it wasn't successful because it's scaled it was secure and it was enterprise ready it once again changed the industry but this time through open innovation this gave the hardware ecosystem a software platform this open software platform gave the hardware ecosystem a software platform to build around it Unleashed them the hardware side to compete and thrive it enabled innovation from the OEMs new players building cheaper faster servers even new architectures from armed to power sprung up with this change we have seen an incredible amount of hardware innovation over the last 15 years that same innovation happened on the software side we saw powerful implementations of bare metal Linux distributions out in the market in fact at one point there were 300 there are over 300 distributions out in the market on the foundation of Linux powerful open-source equivalents were even developed in every area of Technology databases middleware messaging containers anything you could imagine innovation just exploded around the Linux platform in innovation it's at the core also drove virtualization both Linux and virtualization led to another area of innovation which you're hearing a lot about now public cloud innovation this innovation started to proceed at a rate that we had never seen before we had never experienced this in the past in this unprecedented speed of innovation and software was now possible because you didn't need a chip foundry in order to innovate you just needed great ideas in the open platform that was out there customers seeing this innovation in the public cloud sparked it sparked their desire to build their own linux based cloud platforms and customers are now are now bringing that cloud efficiency on-premise in their own data centers public clouds demonstrated so much efficiency the data centers and architects wanted to take advantage of it off premise on premise I'm sorry within their own we don't within their own controlled environments this really allowed companies to make the most of existing investments from data centers to hardware they also gained many new advantages from data sovereignty to new flexible agile approaches I want to bring Burr and his team up here to take a look at what building out an on-premise cloud can look like today Bure take it away I am super excited to be with all of you here at Red Hat summit I know we have some amazing things to show you throughout the week but before we dive into this demonstration I want you to take just a few seconds just a quick moment to think about that really important event your life that moment you turned on your first computer maybe it was a trs-80 listen Claire and Atari I even had an 83 b2 at one point but in my specific case I was sitting in a classroom in Hawaii and I could see all the way from Diamond Head to Pearl Harbor so just keep that in mind and I turn on an IBM PC with dual floppies I don't remember issuing my first commands writing my first level of code and I was totally hooked it was like a magical moment and I've been hooked on computers for the last 30 years so I want you to hold that image in your mind for just a moment just a second while we show you the computers we have here on stage let me turn this over to Jay fair and Dini here's our worldwide DevOps manager and he was going to show us his hardware what do you got Jay thank you BER good morning everyone and welcome to Red Hat summit we have so many cool things to show you this week I am so happy to be here and you know my favorite thing about red hat summit is our allowed to kind of share all of our stories much like bird just did we also love to you know talk about the hardware and the technology that we brought with us in fact it's become a bit of a competition so this year we said you know let's win this thing and we actually I think we might have won we brought a cloud with us so right now this is a private cloud for throughout the course of the week we're going to turn this into a very very interesting open hybrid cloud right before your eyes so everything you see here will be real and happening right on this thing right behind me here so thanks for our four incredible partners IBM Dell HP and super micro we've built a very vendor heterogeneous cloud here extra special thanks to IBM because they loaned us a power nine machine so now we actually have multiple architectures in this cloud so as you know one of the greatest benefits to running Red Hat technology is that we run on just about everything and you know I can't stress enough how powerful that is how cost-effective that is and it just makes my life easier to be honest so if you're interested the people that built this actual rack right here gonna be hanging out in the customer success zone this whole week it's on the second floor the lobby there and they'd be glad to show you exactly how they built this thing so let me show you what we actually have in this rack so contained in this rack we have 1056 physical chorus right here we have five and a half terabytes of RAM and just in case we threw 50 terabytes of storage in this thing so burr that's about two million times more powerful than that first machine you boot it up thanks to a PC we're actually capable of putting all the power needs and cooling right in this rack so there's your data center right there you know it occurred to me last night that I can actually pull the power cord on this thing and kick it up a notch we could have the world's first mobile portable hybrid cloud so I'm gonna go ahead and unplug no no no no no seriously it's not unplug the thing we got it working now well Berg gets a little nervous but next year we're rolling this thing around okay okay so to recap multiple vendors check multiple architectures check multiple public clouds plug right into this thing check and everything everywhere is running the same software from Red Hat so that is a giant check so burn Angus why don't we get the demos rolling awesome so we have totally we have some amazing hardware amazing computers on this stage but now we need to light it up and we have Angus Thomas who represents our OpenStack engineering team and he's going to show us what we can do with this awesome hardware Angus thank you Beth so this was an impressive rack of hardware to Joe has bought a pocket stage what I want to talk about today is putting it to work with OpenStack platform director we're going to turn it from a lot of potential into a flexible scalable private cloud we've been using director for a while now to take care of managing hardware and orchestrating the deployment of OpenStack what's new is that we're bringing the same capabilities for on-premise manager the deployment of OpenShift director deploying OpenShift in this way is the best of both worlds it's bare-metal performance but with an underlying infrastructure as a service that can take care of deploying in new instances and scaling out and a lot of the things that we expect from a cloud provider director is running on a virtual machine on Red Hat virtualization at the top of the rack and it's going to bring everything else under control what you can see on the screen right now is the director UI and as you see some of the hardware in the rack is already being managed at the top level we have information about the number of cores in the amount of RAM and the disks that each machine have if we dig in a bit there's information about MAC addresses and IPs and the management interface the BIOS kernel version dig a little deeper and there is information about the hard disks all of this is important because we want to be able to make sure that we put in workloads exactly where we want them Jay could you please power on the two new machines at the top of the rack sure all right thank you so when those two machines come up on the network director is going to see them see that they're new and not already under management and is it immediately going to go into the hardware inspection that populates this database and gets them ready for use so we also have profiles as you can see here profiles are the way that we match the hardware in a machine to the kind of workload that it's suited to this is how we make sure that machines that have all the discs run Seth and machines that have all the RAM when our application workouts for example there's two ways these can be set when you're dealing with a rack like this you could go in an individually tag each machine but director scales up to data centers so we have a rules matching engine which will automatically take the hardware profile of a new machine and make sure it gets tagged in exactly the right way so we can automatically discover new machines on the network and we can automatically match them to a profile that's how we streamline and scale up operations now I want to talk about deploying the software we have a set of validations we've learned over time about the Miss configurations in the underlying infrastructure which can cause the deployment of a multi node distributed application like OpenStack or OpenShift to fail if you have the wrong VLAN tags on a switch port or DHCP isn't running where it should be for example you can get into a situation which is really hard to debug a lot of our validations actually run before the deployment they look at what you're intending to deploy and they check in the environment is the way that it should be and they'll preempts problems and obviously preemption is a lot better than debugging something new that you probably have not seen before is director managing multiple deployments of different things side by side before we came out on stage we also deployed OpenStack on this rack just to keep me honest let me jump over to OpenStack very quickly a lot of our opens that customers will be familiar with this UI and the bare metal deployment of OpenStack on our rack is actually running a set of virtual machines which is running Gluster you're going to see that put to work later on during the summit Jay's gone to an awful lot effort to get this Hardware up on the stage so we're going to use it as many different ways as we can okay let's deploy OpenShift if I switch over to the deployed a deployment plan view there's a few steps first thing you need to do is make sure we have the hardware I already talked about how director manages hardware it's smart enough to make sure that it's not going to attempt to deploy into machines they're already in use it's only going to deploy on machines that have the right profile but I think with the rack that we have here we've got enough next thing is the deployment configuration this is where you get to customize exactly what's going to be deployed to make sure that it really matches your environment if they're external IPs for additional services you can set them here whatever it takes to make sure that the deployment is going to work for you as you can see on the screen we have a set of options around enable TLS for encryption network traffic if I dig a little deeper there are options around enabling ipv6 and network isolation so that different classes of traffic there are over different physical NICs okay then then we have roles now roles this is essentially about the software that's going to be put on each machine director comes with a set of roles for a lot of the software that RedHat supports and you can just use those or you can modify them a little bit if you need to add a monitoring agent or whatever it might be or you can create your own custom roles director has quite a rich syntax for custom role definition and custom Network topologies whatever it is you need in order to make it work in your environment so the rawls that we have right now are going to give us a working instance of openshift if I go ahead and click through the validations are all looking green so right now I can click the button start to the deploy and you will see things lighting up on the rack directors going to use IPMI to reboot the machines provisioned and with a trail image was the containers on them and start up the application stack okay so one last thing once the deployment is done you're going to want to keep director around director has a lot of capabilities around what we call de to operational management bringing in new Hardware scaling out deployments dealing with updates and critically doing upgrades as well so having said all of that it is time for me to switch over to an instance of openshift deployed by a director running on bare metal on our rack and I need to hand this over to our developer team so they can show what they can do it thank you that is so awesome Angus so what you've seen now is going from bare metal to the ultimate private cloud with OpenStack director make an open shift ready for our developers to build their next generation applications thank you so much guys that was totally awesome I love what you guys showed there now I have the honor now I have the honor of introducing a very special guest one of our earliest OpenShift customers who understands the necessity of the private cloud inside their organization and more importantly they're fundamentally redefining their industry please extend a warm welcome to deep mar Foster from Amadeus well good morning everyone a big thank you for having armadillos here and myself so as it was just set I'm at Mario's well first of all we are a large IT provider in the travel industry so serving essentially Airlines hotel chains this distributors like Expedia and others we indeed we started very early what was OpenShift like a bit more than three years ago and we jumped on it when when Retta teamed with Google to bring in kubernetes into this so let me quickly share a few figures about our Mario's to give you like a sense of what we are doing and the scale of our operations so some of our key KPIs one of our key metrics is what what we call passenger borders so that's the number of customers that physically board a plane over the year so through our systems it's roughly 1.6 billion people checking in taking the aircrafts on under the Amarillo systems close to 600 million travel agency bookings virtually all airlines are on the system and one figure I want to stress out a little bit is this one trillion availability requests per day that's when I read this figure my mind boggles a little bit so this means in continuous throughput more than 10 million hits per second so of course these are not traditional database transactions it's it's it's highly cached in memory and these applications are running over like more than 100,000 course so it's it's it's really big stuff so today I want to give some concrete feedback what we are doing so I have chosen two applications products of our Mario's that are currently running on production in different in different hosting environments as the theme here is of this talk hybrid cloud and so I want to give some some concrete feedback of how we architect the applications and of course it stays relatively high level so here I have taken one of our applications that is used in the hospitality environment so it's we have built this for a very large US hotel chain and it's currently in in full swing brought into production so like 30 percent of the globe or 5,000 plus hotels are on this platform not so here you can see that we use as the path of course on openshift on that's that's the most central piece of our hybrid cloud strategy on the database side we use Oracle and Couchbase Couchbase is used for the heavy duty fast access more key value store but also to replicate data across two data centers in this case it's running over to US based data centers east and west coast topology that are fit so run by Mario's that are fit with VMware on for the virtualization OpenStack on top of it and then open shift to host and welcome the applications on the right hand side you you see the kind of tools if you want to call them tools that we use these are the principal ones of course the real picture is much more complex but in essence we use terraform to map to the api's of the underlying infrastructure so they are obviously there are differences when you run on OpenStack or the Google compute engine or AWS Azure so some some tweaking is needed we use right at ansible a lot we also use puppet so you can see these are really the big the big pieces of of this sense installation and if we look to the to the topology again very high high level so these two locations basically map the data centers of our customers so they are in close proximity because the response time and the SLA is of this application is are very tight so that's an example of an application that is architectures mostly was high ability and high availability in minds not necessarily full global worldwide scaling but of course it could be scaled but here the idea is that we can swing from one data center to the unit to the other in matters of of minutes both take traffic data is fully synchronized across those data centers and while the switch back and forth is very fast the second example I have taken is what we call the shopping box this is when people go to kayak or Expedia and they're getting inspired where they want to travel to this is really the piece that shoots most of transit of the transactions into our Mario's so we architect here more for high scalability of course availability is also a key but here scaling and geographical spread is very important so in short it runs partially on-premise in our Amarillo Stata Center again on OpenStack and we we deploy it mostly in the first step on the Google compute engine and currently as we speak on Amazon on AWS and we work also together with Retta to qualify the whole show on Microsoft Azure here in this application it's it's the same building blocks there is a large swimming aspect to it so we bring Kafka into this working with records and another partner to bring Kafka on their open shift because at the end we want to use open shift to administrate the whole show so over time also databases and the topology here when you look to the physical deployment topology while it's very classical we use the the regions and the availability zone concept so this application is spread over three principal continental regions and so it's again it's a high-level view with different availability zones and in each of those availability zones we take a hit of several 10,000 transactions so that was it really in very short just to give you a glimpse on how we implement hybrid clouds I think that's the way forward it gives us a lot of freedom and it allows us to to discuss in a much more educated way with our customers that sometimes have already deals in place with one cloud provider or another so for us it's a lot of value to set two to leave them the choice basically what up that was a very quick overview of what we are doing we were together with records are based on open shift essentially here and more and more OpenStack coming into the picture hope you found this interesting thanks a lot and have a nice summer [Applause] thank you so much deeper great great solution we've worked with deep Marv and his team for a long for a long time great solution so I want to take us back a little bit I want to circle back I sort of ended talking a little bit about the public cloud so let's circle back there you know even so even though some applications need to run in various footprints on premise there's still great gains to be had that for running certain applications in the public cloud a public cloud will be as impactful to to the industry as as UNIX era was of computing was but by itself it'll have some of the same limitations and challenges that that model had today there's tremendous cloud innovation happening in the public cloud it's being driven by a handful of massive companies and much like the innovation that sundeck HP and others drove in a you in the UNIX era of community of computing many customers want to take advantage of the best innovation no matter where it comes from buddy but as they even eventually saw in the UNIX era they can't afford the best innovation at the cost of a siloed operating environment with the open community we are building a hybrid application platform that can give you access to the best innovation no matter which vendor or which cloud that it comes from letting public cloud providers innovate and services beyond what customers or anyone can one provider can do on their own such as large scale learning machine learning or artificial intelligence built on the data that's unique probably to that to that one cloud but consumed in a common way for the end customer across all applications in any environment on any footprint in in their overall IT infrastructure this is exactly what rel brought brought to our customers in the UNIX era of computing that consistency across any of those footprints obviously enterprises will have applications for all different uses some will live on premise some in the cloud hybrid cloud is the only practical way forward I think you've been hearing that from us for a long time it is the only practical way forward and it'll be as impactful as anything we've ever seen before I want to bring Byrne his team back to see a hybrid cloud deployment in action burr [Music] all right earlier you saw what we did with taking bare metal and lighting it up with OpenStack director and making it openshift ready for developers to build their next generation applications now we want to show you when those next turn and generation applications and what we've done is we take an open shift and spread it out and installed it across Asia and Amazon a true hybrid cloud so with me on stage today as Ted who's gonna walk us through an application and Brent Midwood who's our DevOps engineer who's gonna be making sure he's monitoring on the backside that we do make sure we do a good job so at this point Ted what have you got for us Thank You BER and good morning everybody this morning we are running on the stage in our private cloud an application that's providing its providing fraud detection detect serves for financial transactions and our customer base is rather large and we occasionally take extended bursts of traffic of heavy traffic load so in order to keep our latency down and keep our customers happy we've deployed extra service capacity in the public cloud so we have capacity with Microsoft Azure in Texas and with Amazon Web Services in Ohio so we use open chip container platform on all three locations because openshift makes it easy for us to deploy our containerized services wherever we want to put them but the question still remains how do we establish seamless communication across our entire enterprise and more importantly how do we balance the workload across these three locations in such a way that we efficiently use our resources and that we give our customers the best possible experience so this is where Red Hat amq interconnect comes in as you can see we've deployed a MQ interconnect alongside our fraud detection applications in all three locations and if I switch to the MQ console we'll see the topology of the app of the network that we've created here so the router inside the on stage here has made connections outbound to the public routers and AWS and Azure these connections are secured using mutual TLS authentication and encrypt and once these connections are established amq figures out the best way auda matically to route traffic to where it needs to get to so what we have right now is a distributed reliable broker list message bus that expands our entire enterprise now if you want to learn more about this make sure that you catch the a MQ breakout tomorrow at 11:45 with Jack Britton and David Ingham let's have a look at the message flow and we'll dive in and isolate the fraud detection API that we're interested in and what we see is that all the traffic is being handled in the private cloud that's what we expect because our latencies are low and they're acceptable but now if we take a little bit of a burst of increased traffic we're gonna see that an EQ is going to push a little a bi traffic out onto the out to the public cloud so as you're picking up some of the load now to keep the Layton sees down now when that subsides as your finishes up what it's doing and goes back offline now if we take a much bigger load increase you'll see two things first of all asher is going to take a bigger proportion than it did before and Amazon Web Services is going to get thrown into the fray as well now AWS is actually doing less work than I expected it to do I expected a little bit of bigger a slice there but this is a interesting illustration of what's going on for load balancing mq load balancing is sending requests to the services that have the lowest backlog and in order to keep the Layton sees as steady as possible so AWS is probably running slowly for some reason and that's causing a and Q to push less traffic its way now the other thing you're going to notice if you look carefully this graph fluctuate slightly and those fluctuations are caused by all the variances in the network we have the cloud on stage and we have clouds in in the various places across the country there's a lot of equipment locked layers of virtualization and networking in between and we're reacting in real-time to the reality on the digital street so BER what's the story with a to be less I noticed there's a problem right here right now we seem to have a little bit performance issue so guys I noticed that as well and a little bit ago I actually got an alert from red ahead of insights letting us know that there might be some potential optimizations we could make to our environment so let's take a look at insights so here's the Red Hat insights interface you can see our three OpenShift deployments so we have the set up here on stage in San Francisco we have our Azure deployment in Texas and we also have our AWS deployment in Ohio and insights is highlighting that that deployment in Ohio may have some issues that need some attention so Red Hat insights collects anonymized data from manage systems across our customer environment and that gives us visibility into things like vulnerabilities compliance configuration assessment and of course Red Hat subscription consumption all of this is presented in a SAS offering so it's really really easy to use it requires minimal infrastructure upfront and it provides an immediate return on investment what insights is showing us here is that we have some potential issues on the configuration side that may need some attention from this view I actually get a look at all the systems in our inventory including instances and containers and you can see here on the left that insights is highlighting one of those instances as needing some potential attention it might be a candidate for optimization this might be related to the issues that you were seeing just a minute ago insights uses machine learning and AI techniques to analyze all collected data so we combine collected data from not only the system's configuration but also with other systems from across the Red Hat customer base this allows us to compare ourselves to how we're doing across the entire set of industries including our own vertical in this case the financial services industry and we can compare ourselves to other customers we also get access to tailored recommendations that let us know what we can do to optimize our systems so in this particular case we're actually detecting an issue here where we are an outlier so our configuration has been compared to other configurations across the customer base and in this particular instance in this security group were misconfigured and so insights actually gives us the steps that we need to use to remediate the situation and the really neat thing here is that we actually get access to a custom ansible playbook so if we want to automate that type of a remediation we can use this inside of Red Hat ansible tower Red Hat satellite Red Hat cloud forms it's really really powerful the other thing here is that we can actually apply these recommendations right from within the Red Hat insights interface so with just a few clicks I can select all the recommendations that insights is making and using that built-in ansible automation I can apply those recommendations really really quickly across a variety of systems this type of intelligent automation is really cool it's really fast and powerful so really quickly here we're going to see the impact of those changes and so we can tell that we're doing a little better than we were a few minutes ago when compared across the customer base as well as within the financial industry and if we go back and look at the map we should see that our AWS employment in Ohio is in a much better state than it was just a few minutes ago so I'm wondering Ted if this had any effect and might be helping with some of the issues that you were seeing let's take a look looks like went green now let's see what it looks like over here yeah doesn't look like the configuration is taking effect quite yet maybe there's some delay awesome fantastic the man yeah so now we're load balancing across the three clouds very much fantastic well I have two minute Ted I truly love how we can route requests and dynamically load transactions across these three clouds a truly hybrid cloud native application you guys saw here on on stage for the first time and it's a fully portable application if you build your applications with openshift you can mover from cloud to cloud to cloud on stage private all the way out to the public said it's totally awesome we also have the application being fully managed by Red Hat insights I love having that intelligence watching over us and ensuring that we're doing everything correctly that is fundamentally awesome thank you so much for that well we actually have more to show you but you're going to wait a few minutes longer right now we'd like to welcome Paul back to the stage and we have a very special early Red Hat customer an Innovation Award winner from 2010 who's been going boldly forward with their open hybrid cloud strategy please give a warm welcome to Monty Finkelstein from Citigroup [Music] [Music] hi Marty hey Paul nice to see you thank you very much for coming so thank you for having me Oh our pleasure if you if you wanted to we sort of wanted to pick your brain a little bit about your experiences and sort of leading leading the charge in computing here so we're all talking about hybrid cloud how has the hybrid cloud strategy influenced where you are today in your computing environment so you know when we see the variable the various types of workload that we had an hour on from cloud we see the peaks we see the valleys we see the demand on the environment that we have we really determined that we have to have a much more elastic more scalable capability so we can burst and stretch our environments to multiple cloud providers these capabilities have now been proven at City and of course we consider what the data risk is as well as any regulatory requirement so how do you how do you tackle the complexity of multiple cloud environments so every cloud provider has its own unique set of capabilities they have they're own api's distributions value-added services we wanted to make sure that we could arbitrate between the different cloud providers maintain all source code and orchestration capabilities on Prem to drive those capabilities from within our platforms this requires controlling the entitlements in a cohesive fashion across our on Prem and Wolfram both for security services automation telemetry as one seamless unit can you talk a bit about how you decide when you to use your own on-premise infrastructure versus cloud resources sure so there are multiple dimensions that we take into account right so the first dimension we talk about the risk so low risk - high risk and and really that's about the data classification of the environment we're talking about so whether it's public or internal which would be considered low - ooh confidential PII restricted sensitive and so on and above which is really what would be considered a high-risk the second dimension would be would focus on demand volatility and responsiveness sensitivity so this would range from low response sensitivity and low variability of the type of workload that we have to the high response sensitivity and high variability of the workload the first combination that we focused on is the low risk and high variability and high sensitivity for response type workload of course any of the workloads we ensure that we're regulatory compliant as well as we achieve customer benefits with within this environment so how can we give developers greater control of their their infrastructure environments and still help operations maintain that consistency in compliance so the main driver is really to use the public cloud is scale speed and increased developer efficiencies as well as reducing cost as well as risk this would mean providing develop workspaces and multiple environments for our developers to quickly create products for our customers all this is done of course in a DevOps model while maintaining the source and artifacts registry on-prem this would allow our developers to test and select various middleware products another product but also ensure all the compliance activities in a centrally controlled repository so we really really appreciate you coming by and sharing that with us today Monte thank you so much for coming to the red echo thanks a lot thanks again tamati I mean you know there's these real world insight into how our products and technologies are really running the businesses today that's that's just the most exciting part so thank thanks thanks again mati no even it with as much progress as you've seen demonstrated here and you're going to continue to see all week long we're far from done so I want to just take us a little bit into the path forward and where we we go today we've talked about this a lot innovation today is driven by open source development I don't think there's any question about that certainly not in this room and even across the industry as a whole that's a long way that we've come from when we started our first summit 14 years ago with over a million open source projects out there this unit this innovation aggregates into various community platforms and it finally culminates in commercial open source based open source developed products these products run many of the mission-critical applications in business today you've heard just a couple of those today here on stage but it's everywhere it's running the world today but to make customers successful with that interact innovation to run their real-world business applications these open source products have to be able to leverage increase increasingly complex infrastructure footprints we must also ensure a common base for the developer and ultimately the application no matter which footprint they choose as you heard mati say the developers want choice here no matter which no matter which footprint they are ultimately going to run their those applications on they want that flexibility from the data center to possibly any public cloud out there in regardless of whether that application was built yesterday or has been running the business for the last 10 years and was built on 10-year old technology this is the flexibility that developers require today but what does different infrastructure we may require different pieces of the technical stack in that deployment one example of this that Effects of many things as KVM which provides the foundation for many of those use cases that require virtualization KVM offers a level of consistency from a technical perspective but rel extends that consistency to add a level of commercial and ecosystem consistency for the application across all those footprints this is very important in the enterprise but while rel and KVM formed the foundation other technologies are needed to really satisfy the functions on these different footprints traditional virtualization has requirements that are satisfied by projects like overt and products like Rev traditional traditional private cloud implementations has requirements that are satisfied on projects like OpenStack and products like Red Hat OpenStack platform and as applications begin to become more container based we are seeing many requirements driven driven natively into containers the same Linux in different forms provides this common base across these four footprints this level of compatible compatibility is critical to operators who must best utilize the infinite must better utilize secure and deploy the infrastructure that they have and they're responsible for developers on the other hand they care most about having a platform that can creates that consistency for their applications they care about their services and the services that they need to consume within those applications and they don't want limitations on where they run they want service but they want it anywhere not necessarily just from Amazon they want integration between applications no matter where they run they still want to run their Java EE now named Jakarta EE apps and bring those applications forward into containers and micro services they need able to orchestrate these frameworks and many more across all these different footprints in a consistent secure fashion this creates natural tension between development and operations frankly customers amplify this tension with organizational boundaries that are holdover from the UNIX era of computing it's really the job of our platforms to seamlessly remove these boundaries and it's the it's the goal of RedHat to seamlessly get you from the old world to the new world we're gonna show you a really cool demo demonstration now we're gonna show you how you can automate this transition first we're gonna take a Windows virtual machine from a traditional VMware deployment we're gonna convert it into a KVM based virtual machine running in a container all under the kubernetes umbrella this makes virtual machines more access more accessible to the developer this will accelerate the transformation of those virtual machines into cloud native container based form well we will work this prot we will worked as capability over the product line in the coming releases so we can strike the balance of enabling our developers to move in this direction we want to be able to do this while enabling mission-critical operations to still do their job so let's bring Byrne his team back up to show you this in action for one more thanks all right what Red Hat we recognized that large organizations large enterprises have a substantial investment and legacy virtualization technology and this is holding you back you have thousands of virtual machines that need to be modernized so what you're about to see next okay it's something very special with me here on stage we have James Lebowski he's gonna be walking us through he's represents our operations folks and he's gonna be walking us through a mass migration but also is Itamar Hine who's our lead developer of a very special application and he's gonna be modernizing container izing and optimizing our application all right so let's get started James thanks burr yeah so as you can see I have a typical VMware environment here I'm in the vSphere client I've got a number of virtual machines a handful of them that make up my one of my applications for my development environment in this case and what I want to do is migrate those over to a KVM based right at virtualization environment so what I'm gonna do is I'm gonna go to cloud forms our cloud management platform that's our first step and you know cloud forms actually already has discovered both my rev environment and my vSphere environment and understands the compute network and storage there so you'll notice one of the capabilities we built is this new capability called migrations and underneath here I could begin to there's two steps and the first thing I need to do is start to create my infrastructure mappings what this will allow me to do is map my compute networking storage between vSphere and Rev so cloud forms understands how those relate let's go ahead and create an infrastructure mapping I'll call that summit infrastructure mapping and then I'm gonna begin to map my two environments first the compute so the clusters here next the data stores so those virtual machines happen to live on datastore - in vSphere and I'll target them a datastore data to inside of my revenue Arman and finally my networks those live on network 100 so I'll map those from vSphere to rover so once my infrastructure is map the next step I need to do is actually begin to create a plan to migrate those virtual machines so I'll continue to the plan wizard here I'll select the infrastructure mapping I just created and I'll select migrate my development environment from those virtual machines to Rev and then I need to import a CSV file the CSV file is going to contain a list of all the virtual machines that I want to migrate that were there and that's it once I hit create what's going to happen cloud forms is going to begin in an automated fashion shutting down those virtual machines begin converting them taking care of all the minutia that you'd have to do manually it's gonna do that all automatically for me so I don't have to worry about all those manual interactions and no longer do I have to go manually shut them down but it's going to take care of that all for me you can see the migrations kicked off here this is the I've got the my VMs are migrating here and if I go back to the screen here you can see that we're gonna start seeing those shutdown okay awesome but as people want to know more information about this how would they dive deeper into this technology later this week yeah it's a great question so we have a workload portability session in the hybrid cloud on Wednesday if you want to see a presentation that deep dives into this topic and how some of the methodologies to migrate and then on Thursday we actually have a hands-on lab it's the IT optimization VM migration lab that you can check out and as you can see those are shutting down here yeah we see a powering off right now that's fantastic absolutely so if I go back now that's gonna take a while you got to convert all the disks and move them over but we'll notice is previously I had already run one migration of a single application that was a Windows virtual machine running and if I browse over to Red Hat virtualization I can see on the dashboard here I could browse to virtual machines I have migrated that Windows virtual machine and if I open up a tab I can now browse to my Windows virtual machine which is running our wingtip toy store application our sample application here and now my VM has been moved over from Rev to Vita from VMware to Rev and is available for Itamar all right great available to our developers all right Itamar what are you gonna do for us here well James it's great that you can save cost by moving from VMware to reddit virtualization but I want to containerize our application and with container native virtualization I can run my virtual machine on OpenShift like any other container using Huebert a kubernetes operator to run and manage virtual machines let's look at the open ship service catalog you can see we have a new virtualization section here we can import KVM or VMware virtual machines or if there are already loaded we can create new instances of them for the developer to work with just need to give named CPU memory we can do other virtualization parameters and create our virtual machines now let's see how this looks like in the openshift console the cool thing about KVM is virtual machines are just Linux processes so they can act and behave like other open shipped applications we build in more than a decade of virtualization experience with KVM reddit virtualization and OpenStack and can now benefit from kubernetes and open shift to manage and orchestrate our virtual machines since we know this virtual machine this container is actually a virtual machine we can do virtual machine stuff with it like shutdown reboot or open a remote desktop session to it but we can also see this is just a container like any other container in openshift and even though the web application is running inside a Windows virtual machine the developer can still use open shift mechanisms like services and routes let's browse our web application using the OpenShift service it's the same wingtip toys application but this time the virtual machine is running on open shift but we're not done we want to containerize our application since it's a Windows virtual machine we can open a remote desktop session to it we see we have here Visual Studio and an asp.net application let's start container izing by moving the Microsoft sequel server database from running inside the Windows virtual machine to running on Red Hat Enterprise Linux as an open shipped container we'll go back to the open shipped Service Catalog this time we'll go to the database section and just as easily we'll create a sequel server container just need to accept the EULA provide password and choose the Edition we want and create a database and again we can see the sequel server is just another container running on OpenShift now let's take let's find the connection details for our database to keep this simple we'll take the IP address of our database service go back to the web application to visual studio update the IP address in the connection string publish our application and go back to browse it through OpenShift fortunately for us the user experience team heard we're modernizing our application so they pitched in and pushed new icons to use with our containerized database to also modernize the look and feel it's still the same wingtip toys application it's running in a virtual machine on openshift but it's now using a containerized database to recap we saw that we can run virtual machines natively on openshift like any other container based application modernize and mesh them together we containerize the database but we can use the same approach to containerize any part of our application so some items here to deserve repeating one thing you saw is Red Hat Enterprise Linux burning sequel server in a container on open shift and you also saw Windows VM where the dotnet native application also running inside of open ships so tell us what's special about that that seems pretty crazy what you did there exactly burr if we take a look under the hood we can use the kubernetes commands to see the list of our containers in this case the sequel server and the virtual machine containers but since Q Bert is a kubernetes operator we can actually use kubernetes commands like cube Cpl to list our virtual machines and manage our virtual machines like any other entity in kubernetes I love that so there's your crew meta gem oh we can see the kind says virtual machine that is totally awesome now people here are gonna be very excited about what they just saw we're gonna get more information and when will this be coming well you know what can they do to dive in this will be available as part of reddit Cloud suite in tech preview later this year but we are looking for early adopters now so give us a call also come check our deep dive session introducing container native virtualization Thursday 2:00 p.m. awesome that is so incredible so we went from the old to the new from the close to the open the Red Hat way you're gonna be seeing more from our demonstration team that's coming Thursday at 8 a.m. do not be late if you like what you saw this today you're gonna see a lot more of that going forward so we got some really special things in store for you so at this point thank you so much in tomorrow thank you so much you guys are awesome yeah now we have one more special guest a very early adopter of Red Hat Enterprise Linux we've had over a 12-year partnership and relationship with this organization they've been a steadfast Linux and middleware customer for many many years now please extend a warm welcome to Raj China from the Royal Bank of Canada thank you thank you it's great to be here RBC is a large global full-service is back we have the largest bank in Canada top 10 global operate in 30 countries and run five key business segments personal commercial banking investor in Treasury services capital markets wealth management and insurance but honestly unless you're in the banking segment those five business segments that I just mentioned may not mean a lot to you but what you might appreciate is the fact that we've been around in business for over 150 years we started our digital transformation journey about four years ago and we are focused on new and innovative technologies that will help deliver the capabilities and lifestyle our clients are looking for we have a very simple vision and we often refer to it as the digitally enabled bank of the future but as you can appreciate transforming a hundred fifty year old Bank is not easy it certainly does not happen overnight to that end we had a clear unwavering vision a very strong innovation agenda and most importantly a focus towards a flawless execution today in banking business strategy and IT strategy are one in the same they are not two separate things we believe that in order to be the number one bank we have to have the number one tactic there is no question that most of today's innovations happens in the open source community RBC relies on RedHat as a key partner to help us consume these open source innovations in a manner that it meets our enterprise needs RBC was an early adopter of Linux we operate one of the largest footprints of rel in Canada same with tables we had tremendous success in driving cost out of infrastructure by partnering with rahat while at the same time delivering a world-class hosting service to your business over our 12 year partnership Red Hat has proven that they have mastered the art of working closely with the upstream open source community understanding the needs of an enterprise like us in delivering these open source innovations in a manner that we can consume and build upon we are working with red hat to help increase our agility and better leverage public and private cloud offerings we adopted virtualization ansible and containers and are excited about continuing our partnership with Red Hat in this journey throughout this journey we simply cannot replace everything we've had from the past we have to bring forward these investments of the past and improve upon them with new and emerging technologies it is about utilizing emerging technologies but at the same time focusing on the business outcome the business outcome for us is serving our clients and delivering the information that they are looking for whenever they need it and in whatever form factor they're looking for but technology improvements alone are simply not sufficient to do a digital transformation creating the right culture of change and adopting new methodologies is key we introduced agile and DevOps which has boosted the number of adult projects at RBC and increase the frequency at which we do new releases to our mobile app as a matter of fact these methodologies have enabled us to deliver apps over 20x faster than before the other point about around culture that I wanted to mention was we wanted to build an engineering culture an engineering culture is one which rewards curiosity trying new things investing in new technologies and being a leader not necessarily a follower Red Hat has been a critical partner in our journey to date as we adopt elements of open source culture in engineering culture what you seen today about red hearts focus on new technology innovations while never losing sight of helping you bring forward the investments you've already made in the past is something that makes Red Hat unique we are excited to see red arts investment in leadership in open source technologies to help bring the potential of these amazing things together thank you that's great the thing you know seeing going from the old world to the new with automation so you know the things you've seen demonstrated today they're they're they're more sophisticated than any one company could ever have done on their own certainly not by using a proprietary development model because of this it's really easy to see why open source has become the center of gravity for enterprise computing today with all the progress open-source has made we're constantly looking for new ways of accelerating that into our products so we can take that into the enterprise with customers like these that you've met what you've met today now we recently made in addition to the Red Hat family we brought in core OS to the Red Hat family and you know adding core OS has really been our latest move to accelerate that innovation into our products this will help the adoption of open shift container platform even deeper into the enterprise and as we did with the Linux core platform in 2002 this is just exactly what we did with with Linux back then today we're announcing some exciting new technology directions first we'll integrate the benefits of automated operations so for example you'll see dramatic improvements in the automated intelligence about the state of your clusters in OpenShift with the core OS additions also as part of open shift will include a new variant of rel called Red Hat core OS maintaining the consistency of rel farhat for the operation side of the house while allowing for a consumption of over-the-air updates from the kernel to kubernetes later today you'll hear how we are extending automated operations beyond customers and even out to partners all of this starting with the next release of open shift in July now all of this of course will continue in an upstream open source innovation model that includes continuing container linux for the community users today while also evolving the commercial products to bring that innovation out to the enterprise this this combination is really defining the platform of the future everything we've done for the last 16 years since we first brought rel to the commercial market because get has been to get us just to this point hybrid cloud computing is now being deployed multiple times in enterprises every single day all powered by the open source model and powered by the open source model we will continue to redefine the software industry forever no in 2002 with all of you we made Linux the choice for enterprise computing this changed the innovation model forever and I started the session today talking about our prediction of seven years ago on the future being open we've all seen so much happen in those in those seven years we at Red Hat have celebrated our 25th anniversary including 16 years of rel and the enterprise it's now 2018 open hybrid cloud is not only a reality but it is the driving model in enterprise computing today and this hybrid cloud world would not even be possible without Linux as a platform in the open source development model a build around it and while we have think we may have accomplished a lot in that time and we may think we have changed the world a lot we have but I'm telling you the best is yet to come now that Linux and open source software is firmly driving that innovation in the enterprise what we've accomplished today and up till now has just set the stage for us together to change the world once again and just as we did with rel more than 15 years ago with our partners we will make hybrid cloud the default in the enterprise and I will take that bet every single day have a great show and have fun watching the future of computing unfold right in front of your eyes see you later [Applause] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] anytime [Music]

>> Narrator: Live from San Francisco. It's theCUBE! Covering RedHat Summit 2018. Brought to you by Red Hat. >> Alright welcome back, this is theCUBE's exclusive coverage of Red Hat 2018. I'm John Furrier, the co host of theCUBE with John Troyer, co-founder of TechReckoning Advisory Firm. Next guest is Chris Wright, Vice President and CTO Chief of Technology of his Red Hat. Great to see you again, thanks for joining us today. >> Yeah, great to be here. >> Day one of three days of CUBE coverage, you got, yesterday had sessions over there in Moscone South, yet in classic Red Hat fashion, good vibes, things are rocking. Red Hat's got a spring to their step, making some good calls technically. >> Chris: That's right. >> Kubernetes' one notable, Core OS Acquisition, really interesting range, this gives, I mean I think people are now connecting the dots from the tech side, but also now on the business side, saying "Okay we can see now some, a wider market opportunity for Red Hat". Not just doing it's business with Linux, software, you're talking about a changing modern software architecture, for application developers. I mean, this is a beautiful thing, I mean. >> Chris: It's not just apps but it's the operator, you know, operation side as well, so we've been at it for a long time. We've been doing something that's really similar for quite some time, which is building a platform for applications, independent from the underlying infrastructure, in the Linux days I was X86 hardware, you know, you get this HeteroGenius hardware underneath, and you get a consistent standardized application run time environment on top of Linux. Kubernetes is helping us do that at a distributive level. And it's taken some time for the industry to kind of understand what's going on, and we've been talking about hybrid cloud for years and, you really see it real and happening and it's in action and for us that distributed layer round Kubernetes which just lights up how do you manage distributed applications across complex infrastructure, makes it really real. >> Yeah it's also timing's everything too right? I mean, good timing, that helps, the evolution of the business, you always have these moments and these big waves where you can kind of see clunking going on, people banging against each other and you know, the glue layers developing, and then all of a sudden snaps into place, and then it just scales, right? So you're starting to see that, we've seen this in other ways, TCPIP, Linux itself, and you guys are certainly making that comparison, being Red Hat, but what happens next is usually an amazing growth phase. Again, small little, and move the ball down the field, and then boom, it opens up. As a CTO, you have to look at that 20 mile stair now, what's next? What's that wave coming that you're looking at in the team that you have on Red Hat's side and across your partners? What's the wave next? >> Well there's a lot of activity going on that's beyond what we're building today. And so much of it, first of all, is happening in Open Source. So that itself is awesome. Like we're totally tuned into these environments, it's core to who we are, it's our DNA to be involved in these Open Source communities, and you look across all of the different projects and things like machine learning and blockchain, which are really kind of native Open Source developments, become really relevant in ways that we can change how we build functionality and build business, and build business value in the future. So, those are the things that we look at, what's emerging out of the Open Source communities, what's going to help continue to accelerate developers' ability to quickly build applications? Operations team's ability to really give that broad scale, policy level view of what's going on inside your infrastructure to support those applications, and all the data that we're gathering and needing to sift through and build value from inside the applications, that's very much where we're going. >> Well I think we had a really good example of machine learning used in an everyday enterprise application this morning, they kicked off the keynote, talking about optimizing the schedule and what sessions were in what rooms, you know, using an AI tool right? >> Chris: That's right. >> And so, that's reality as you look at, is that going to be the new reality as you're looking into the future of building in these kind of machine learning opportunities into everyday business applications that, you know, in the yesteryear would've been just some, I don't know, visual basic, or whatever, depending on how far back you look, right? You know, is that really going to be a reality in the enterprise? It seems so. >> It is, absolutely. And so what we're trying to do is build the right platforms, and build the right tools, and then interfaces to those platforms and tools to make it easier and easier for developers to build, you know, what we've been calling "Intelligent Apps", or applications that take advantage of the data, and the insights associated with that data, right in the application. So, the scheduling optimization that you saw this morning in the keynote is a great example of that. Starting with basic rules engine, and augmenting that with machine learning intelligence is one example, and we'll see more and more of that as the sophisticated tools that are coming out of Open Source communities building machine learning platforms, start to specialize and make it easier and easier to do specific machine learning tasks within an application. So you don't have to be a data scientist and an app developer all in one, you know, that's, there's different roles and different responsibilities, and how do we build, develop, life cycle managed models is one question, and how do we take advantage of those models and applications is another question, and we're really looking at that from a Red Hat perspective. >> John F: And the enterprises are always challenged, they always (mumbles), Cloud Native speaks to both now, right? So you got hybrid cloud and now multi-cloud on the horizon, set perfectly up with Open Shift's kind of position in that, kind of the linchpin, but you got, they're still two different worlds. You got the cloud-native born in the cloud, and that's pretty much a restart-up these days, and then you've got legacy apps with container, so the question is, that people are asking is, okay, I get the cloud-native, I see the benefits, I know what the investment is, let's do it upfront, benefits are horizontally scalable, asynchronous, et cetera et cetera, but I got legacy. I want to do micro-servicing, I want to do server-less, do I re-engineer that or just containers, what's the technical view and recommendation from Red Hat when you say, when the CIO says or enterprise says, "Hey I want to go cloud native for over here and new staff, but I got all this old staff, what do I do?". Do I invest more region, or just containerize it, what's the play? >> I think you got to ask kind of always why? Why you're doing something. So, we hear a lot, "Can I containerize it?", often the answer is yes. A different question might be, "What's the value?", and so, a containerized application, whether it's an older application that's stateful or whether it's a newer cloud-native application (mumbles), horizontally scalable, and all the great things, there's value potentially in just the automation around the API's that allow you to lifecycle manage the application. So if the application itself is still continuing to change, we have some great examples with some of our customers, like Keybank, doing what we call the "Fast moving monolith". So it's still a traditional application, but it's containerized and then you build a CICD model around it, and you have automation on how you deliver and deploy production. There's value there, there's also value in your existing system, and maybe building some different services around the legacy system to give you access, API access, to data in that system. So different ways to approach that problem, I don't think there's a one size fits all. >> So Chris, some of this is also a cultural and a process shift. I was impressed this morning, we've already talked with two Red Hat customers, Macquarie and Amadeus, and you know Macquarie was talking about, "Oh yeah we moved 40 applications in a year, you know, onto Open Shift", and it turns out they were already started to be containerized and dockerized and, oh yeah yeah you know, that is standard operating procedure, for that set of companies. There's a long tail of folks who are still dealing with the rest of the stuff we've had to deal, the stack we've had to deal with for years. How is Red Hat, how are you looking at this kind of cultural shift? It's nice that it's real, right? It's not like we're talking about microservices, or some sort of future, you know, Jettison sort of thing, that's going to save us all, it's here today and they're doing it. You know, how are you helping companies get there? >> So we have a practice that we put in place that we call the "Open Innovation Lab". And it's very much an immersive practice to help our customers first get experience building one of these cloud native applications. So we start with a business problem, what are you trying to solve? We take that through a workshop, which is a multi-week workshop, really to build on top of a platform like Open Shift, real code that's really useful for that business, and those engineers that go through that process can then go back to their company and be kind of the change agent for how do we build the internal cultural shift and the appreciation for Agile development methodologies across our organization, starting with some of this practical, tangible and realist. That's one great example of how we can help, and I think part of it is just helping customers understand it isn't just technology, I'm a technologist so there's part of me that feels pain to say that but the practical reality is there's whole organizational shifts, there's mindset and cultural changes that need to happen inside the organization to take advantage of the technology that we put in place to build that optimize. >> John F: And roles are changing too, I'll see the system admin kind of administrative things getting automated way through more operating role. I heard some things last week at CubeCon in Copenhagen, Denmark, and I want to share some quotes and I want to get your reaction. >> Alright. >> This is the hallway, I won't attribute the names but, these were quotes, I need, quote, "I need to get away from VP Engine firewalls. I need user and application layer security with unfishable access, otherwise I'm never safe". Second quote, "Don't confuse lift and shift with running cloud-native global platform. Lot of actors in this system already running seamlessly. Versus say a VM Ware running environment wherein V Center running in a data center is an example of a lift and shift". So the comments are one for (mumbles) cloud, you need to have some sort of security model, and then two, you know we did digital transformation before with VM's, that was a different world, but the new world's not a lift and shift, it's re-architect of a cloud-native global platform. Your reaction to those two things, and what that means to customers as they think about what they're going to look like, as they build that bridge to the future. >> Security peace is critical, so every CIO that we're talking to, it's top of mind, nobody wants to be on the front page of The Wall Street Journal for the wrong reasons. And so understanding, as you build a micro-services software architected application, the components themselves are exposed to services, those services are API's that become potentially part of the attack surface. Thinking of it in terms of VPN's and firewalls, is the kind of traditional way that we manage security at the edge. Hardened at the edge, soft in the middle isn't an acceptable way to build a security policy around applications that are internally exposing parts of their API's to other parts of the application. So, looking at it for me, application use case perspective, which portions of the application need to be able to talk to one another, and it's part of why somebody like Histio are so exciting, because it builds right in to the platform, the notion of mutual authentication between services. So that you know you're talking to a service that you're allowed to talk to. Encryption associated with that, so that you get another level of security for data and motion, and all of that is not looking at what is the VPN or what is the VLAN tag, or what is the encapsulation ID, and thinking layer two, layer three security, it's really application layer, and thinking in terms of that policy, which pieces of the application have to talk to each other, and nobody else can talk to that service unless it's, you know, understood that that's an important part for how the application works. So I think, really agree, and you could even say DevSecOps to me is something that I've come around to. Initially I thought it was a bogus term and I see the value in considering security at every step of build, test and deliver an application. Lift and shift, totally different topic. What does it mean to lift and shift? And I think there's still, some people want to say there's no value in lift and shift, and I don't fully agree, I think there's still value in moving, and modernizing the platform without changing the application, but ultimately the real value does come in re-architecting, and so there's that balance. What can you optimize by moving? And where does that free up resources to invest in that real next generation application re-architecting? >> So Chris, you've talked about machine learning, right? Huge amounts of data, you've just talked about security, we've talked about multi-cloud, to me that says we might have an issue in the future with the data layer. How are people thinking about the data layer, where it lives, on prem, in the cloud, think about GDPR compliance, you know, all that sort of good stuff. You know, how are you and Red Hat, how are you asking people to think about that? >> So, data management is a big question. We build storage tooling, we understand how to put the bytes on disc, and persist, and maintain the storage, it's a different question what are the data services, and what is the data governance, or policy around placement, and I think it's a really interesting part of the ecosystem today. We've been working with some research partners in the Massachusetts Open Cloud and Boston University on a project called "Cloud Dataverse", and it has a whole policy question around data. 'Cause there, scientists want to share data sets, but you have to control and understand who you're sharing your data sets with. So, it's definitely a space that we are interested in, understand, that there's a lot of work to be done there, and GDPR just kind of shines a light right on it and says policy and governance around where data is placed is actually fundamental and important, and I think it's an important part, because you've seen some of the data issues recently in the news, and you know, we got to get a handle on where data goes, and ultimately, I'd love to see a place where I'm in control of how my data is shared with the rest of the world. >> John F: Yeah, certainly the trend. So a final question for you, Open Source absolutely greatness going on, more and more good things are happening in projects, and bigger than ever before, I mean machine learning's a great example, seeing not just code snippets, code bases being you know, TensorFlow jumps out at me (mumbles), what are you doing here this year that's new and different from an Open Source standpoint, but also from a Red Hat standpoint that's notable that people should pay attention to? >> Well, one of the things that we're focused on is that platform layer, how do we enable a machine learning workload to run well on our platform? So it starts actually at the very bottom of the stack, hardware enablement. You got to get GPUs functional, you got to get them accessible to virtual machine based applications, and container based applications, so that's kind of table stakes. Accelerate a machine learning workload to make it usable, and valuable, to an enterprise by reducing the training and interference times for a machine learning model. Some of the next questions are how do we embed that technology in our own products? So you saw Access Insights this morning, talking about how we take machine learning, look at all of the data that we're gathering from the systems that our customers are deploying, and then derive insights from those and then feed those back to our customers so they can optimize the infrastructure that they're building and running and maintaining, and then, you know, the next step is that intelligent application. How do we get that machine learning capability into the hands of the developer, and pair the data scientist with the developers so you build these intelligent applications, taking advantage of all the data that you're gathering as an enterprise, and turning that into value as part of your application development cycle. So those are the areas that we're focused on for machine learning, and you know, some of that is partnering, you know, talking through how do we connect some of these services from Open Shift to the cloud service providers that are building some of these great machine learning tools, so. >> Any new updates on (mumbles) the success of Red Hat just in the past two years? You see the growth, that correlates, that was your (mumbles) Open Shift, and a good calls there, positioned perfectly, analysts, financial analysts are really giving you guys a lot of props on Wall Street, about the potential revenue growth opportunities on the business side, what's it like now at Red Hat? I mean, do you look back and say, "Hey, it was only like three years ago we did this", and I mean, the vibes are good, I mean share some inside commentary on what's happening inside Red Hat. >> It's really exciting. I mean, we've been working on these things for a long time. And, the simplest example I have is the combination of tools like the JBoss Middleware Suite and Linux, well they could run well together and we have a lot of customers that combine those, but when you take it to the next step, and you build containerized services and you distribute those broadly, you got a container platform, you got middleware components, you know, even providing functionality as services, you see how it all comes together and that's just so exciting internally. And at the same time we're growing. And a big part of-- >> John F: Customers are using it. >> Customers are using it, so putting things into production is critical. It's not just exciting technology but it's in production. The other piece is we're growing, and as we grow, we have to maintain the core of who we are. There's some humility that's involved, there's some really core Open Source principles that are involved, and making sure that as we continue to grow, we don't lose sight of who we are, really important thing for our internal culture, so. >> John F: Great community driven, and great job. Chris, thanks for coming on theCUBE, appreciate it. Chris Wright, CTO of Red Hat, sharing his insights here on theCUBE. Of course, bringing you all a live action as always here in San Francisco in Moscone West, for Red Hat Summit 2018, we'll be right back. (electronic music) (intense music)