>> Voice over: From around the globe, it's theCUBE with coverage of KubeCon and CloudNativeCon Europe 2020 virtual, brought to you by Red Hat, the Cloud Native Computing Foundation and Ecosystem Partners. >> Hi, I'm Stu Mittleman, and welcome back to theCUBE's Coverage of KubeCon CloudNativeCon Europe for 2020. Get to talk to the participants in this great community and ecosystem where they are around the globe. And when you think back to the early days of containers, it was, containers, they're lightweight, they're small, going to obliterate virtualization is often the headline that we had. Of course, we know everything in IT tends to be additive. And here we are in 2020 and containers and virtual machines, living side by side and often we'll see the back and forth that happens when we talk about virtualization in containers. To talk about that topic specifically, happy to welcome to the program, first time guest, Steve Gordon. He's the director of product management at Red Hat. Steve, thanks so much for joining us. >> Thanks so much Stu, it's great to be here. >> All right, as I teed up of course, virtualization was a wave that swept through the data center. It is a major piece, not only of what's in the data center, but even if you look at the public Clouds, often it was virtualization underneath there. Certain companies like Google, of course, really drove a container adoption. And often you hear when people talk about, I built something CloudNative, that underlying piece of being containerized and then using an orchestration layer like Kubernetes is what they talk about. So maybe stop for a sec, Red Hat of course, heavily involved in virtualization and containers, how you see that landscape and what's the general conversation you have with customers as to how they make the choice and how the lines blur between those worlds? >> Yeah, so at Red Hat, I think we've been working on certainly the current iteration of the next specialization with KVM for around 12 years and myself large portion of that. I think, one thing that's always been constant is while from the outside-in, specialization looks like it's been a fairly stable marketplace. It's always changing, it's always evolving. And what we're seeing right now is as people are adopting containers and even constructs built on top of containers into their workflows, there is more interest and more desire around how can I combine these things, recognizing that still an enormous percentage of my workloads are out there running in virtual machines today, but I'm building new things around them that need to be able to interact with them and springboard off of that. So I think for the last couple of years, I'm sure you yourself have seen a number of different projects pop up and the opensource community around this intersection of containers and visualization and how can these technologies compliment each other. And certainly KubeVirt is one of the projects that we've started in this space, in reaction to both that general interests, but also the real customer problems that people have, as they try and meld these two worlds. >> So Steve, at Red Hat Summit earlier this year, there was a lot of talk around container native virtualization. If you could just explain what that means, how that might be different from just virtualization in general, and we'll go from there. >> Sure, so back in, I think early 2017, late 2016, we started playing around this idea. We'd already seen the momentum around Kubernetes and the result the way we architected OpenShift, three at a time around, Kubernetes has this strength as an orchestration platform, but also a shared provider of storage, networking, et cetera, resources. And really thinking about, when we look at virtualization and containers, some of these problems are very common regardless of what footprint the workload happens to fit into. So leveraging that strength of Kubernetes as an orchestration platform, we started looking at, what would it look like to orchestrate virtual machines on that same platform right next to our application containers? And the extension of that the KubeVirt project and what has ultimately become OpenShift virtualization is based around that core idea of how can I make a traditional virtual machine to a full operating system, interact with and look exactly like a Kubernetes native construct, that I can use from the same platform? I can manage it using the same constructs, I can interact with it using the same console, all of these kinds of ideas. And then on top of that, not just bring in workloads as they lie, but enable really powerful workforce with people who are building a new application in containers that still need some backend components, say a database that's sitting in a VM, or also trying to integrate those virtual machines into new constructs, whether it's something like a pipeline or a service mesh. We're hearing a lot of questions around those things these days where people don't want to just apply those things to brand new workloads, but figure out how do they apply those constructs to the broader majority of their fleet of workflows that exist today. >> All right, so I believe back at Red Hat Summit, OpenShift virtualization was in beta. Where's the product that solution sets till today? >> Right, so at this year's KubeCon, we're happy to announce that OpenShift virtualization is moving to general availability. So it will be a fully supported part of OpenShift. And what that means is, you, as a subscriber to OpenShift, the platform, get virtualization as just an additional capability of that platform that you can enable as an operator from the operator hub, which is really a powerful thing for admins to be able to do that. But also is just really powerful in terms of the user experience. Like once that operator is enabled on your cluster, the little tab shows up, that shows that you can now go and create a virtual machine. But you also still get all of the metrics and the shared networking and so on that goes with that cluster, that underlies it all. And you can again do some really powerful things in terms of combining those constructs for both virtual machines and containers. >> When you talk about that line between virtualization and containers, a big question is, what does this mean for developers? How is it different from what they were using before? How do they engage and interact with their infrastructure today? >> Sure, so I think the way a lot of this current wave of technology got started for people was whether it was with Kubernetes or Docker before that, people would go and grab, easiest way they could grab compute for capacity was go to their virtual machine firm, whether that was their local virtualization estate at their company, or whether that was taking a credit card to public Cloud, getting a virtual machine and spinning up a container platform on top of that. What we're now seeing is, as that's transitioning into people building their workloads, almost entirely around these container constructs, in some cases when they're starting from scratch, there is more interest in, how do I leverage that platform directly? How do I, as my application group have more control over that platform? And in some cases, depending on the use case, like if they have demand for GPUs, for example, or other high-performance devices, that question of whether the virtualization layer between my physical host and my container is adding that much value? But then still wanting to bring in the traditional workloads they have as well. So I think we've seen this gradual transition where there is a growing interest in reevaluating, how do we start with container based architectures? To, okay, how has we transitioned towards more production scenarios and the growth in production scenarios? What tweaks do we make to that architecture? Does it still make sense to run all of that on top of virtual machines? Or does it make more sense to almost flip that equation as my workload mix gradually starts changing? >> Yeah, two thoughts come to mind on that. Number one is, are there specific applications out there, or I think about traditional VMs, often that Windows environments that we have there, is that some of the use case to bring them over to containers? And then also, once I've gotten it into the container environment, what are the steps to move forward? Because I have to expect that there's going to be some refactoring, some modernization to take advantage of the innovation and pace of change, not just to take it, containerize it and leave it. >> Yeah, so certainly, there is an enormous amount of potential out there in terms of Windows workloads, and people are definitely trying to work out how do they leverage those workloads in the context of OpenShift and Kubernetes based environment. And Windows containers obviously, is one way to address that. And certainly, that is very powerful in and of itself, for bringing those workloads to OpenShift and Kubernetes, but does have some constraints in terms of needing to be on a relatively recent version of Windows server and so on for those workloads to run in that construct. So where OpenShift virtualization helps with that is we can actually take an existing virtual machine workload, bring that across, even if it's say Windows server 2012, run it on top of the OpenShift virtualization platform as a VM, And then if or when you start modernizing more of that application, you can start teasing that out into actual containers. And that's actually something, it is one of our very early demos at Red Hat Summit 2018, I think was how you would go about doing that, and primarily we did that because it is a very powerful thing for customers to see how they can bring those, all the applications into this mix. And the other aspect of that I'll mention is one of our financial services customers who we've been working with, basically since that demo, they saw it from a hallway at Red Hat Summit and came and said, "Hey, we want to talk to you guys about that." One of the primary workload, is a Windows 10 style environment, that they happened to be bringing in as well. And that's more in that construct of treating OpenShift almost as a pool of compute, which you can use for many different workload types with the Windows 10 being just one aspect of that. And the other thing I'll say in terms of the second part of the question, what do I need to do in terms of refactoring? So we are very conscious of the fact that, if this is to provide value, you have to be able to bring in existing virtual machines with as minimal change as possible. So we do have a migration solution set, that we've had for a number of years, for bringing our virtual machines to Linux specialization stacks. We're expanding that to include OpenShift virtualization as a target, to help you bring in those existing virtual machine images. Where things do change a little bit is in terms of the operational approaches. Obviously, admin console now is OpenShift for those virtual machines, that does right now present a change. But we think it is a very powerful opportunity in terms of, as people get more and more production workloads into containers, for example, it's going to become a lot more appealing to have a backup solution, for example, that can cater to both the virtual machine workloads as well as any stateful container workloads you may have, which do exist in increasing numbers. >> Well, I'm glad you brought up a stateful discussion because as an industry, we've spent a long time making sure that virtual machines, have storage and have networking that is reliable in performance and the like. What should customers be thinking about and operators when they move to containers? Are there things that are different you manage bringing into, this brings them into the OpenShift management plane. So what else should I be thinking about? What do I need to do differently when I've embraced this? >> Yeah, so I think in terms of the things that virtual machine expects, the two big ones that come to mind to me are networking and storage. The compute piece is still there obviously, but I think is a little less complicated to solve just because the OpenShift and broader Kubernetes community have done such a great job of addressing that piece, and that's really what attracted us to it in the first place. But on the networking side, certainly the expectations of a traditional virtual machine are a little bit different to the networking model of Kubernetes by default. But again, we've seen a lot of growth in container based applications, particularly in the context of CloudNative network functions that have been pushing the boundaries of Kubernetes networking as well. That's resulted in projects like Motus, which allow us to give a virtual machine related to networking interface that it expects, but also give it the option of using the pod networking natively, for some of those more powerful constructs that are native to Kubernetes. So that's one of those areas where you've got a mix of options, depending on how far you want to go from a modernization perspective versus do I just want to bring this workload in and run it as it is. And my modernization is more built around it, in terms of the other container based things. Then similarly in storage, it's an area where obviously at Red Hat, we've been working close with the OpenShift container storage team, but we also work with a number of ecosystem partners on, not just how do we certify their storage plugins and make sure they work well both for containers and virtual machines, but also how do we push forward upstream efforts, around things like the container storage interface specification, to allow for these more powerful capabilities like snapshots cloning and so on which we need for virtual machines, but are also very valuable for container based workloads as well. >> Steve, you've mentioned some of the reasons why customers were moving towards this environment. Now that you're GA, what learnings did you have during beta? Are there any other customer stories you could share that you've learned along this journey? >> Yeah, so I think one of the things I'll say is that, there's no feedback like direct product in the hands of customer feedback. And it's really been interesting to see the different ways that people have applied it, not necessarily having set out to apply it, but having gotten partway through their journey and realized, hey, I need this capability. You have something that looks pretty handy and then having success with it. So in particular, in the telecommunications vertical, we've been working closely with a number of providers around the 5G rollouts and the 5G core in particular, where they've been focused on CloudNative network functions. And really what I mean by that is the wave of technology and the push they're making around 5G is to take what they started with network function virtualization a step further, and build that next generation network around CloudNative technologies, including Kubernetes and OpenShift. And as I've been doing that, I have been finding that some of the vendors are more or less prepared for that transition. And that's where, while they've been able to leverage the power of containers for those applications that are ready, they're also able to leverage OpenShift virtualization as a transitionary step, as they modernize the pieces that are taking a little bit longer. And that's where we've been able to run some applications in terms of the load balancer, in terms of a carrier grade database on top of OpenShift virtualization, which we probably wouldn't have set out to do this early in terms of our plan, but we're really able to react quickly to that customer demand and help them get that across the line. And I think that's a really powerful example where the end state may not necessarily be to run everything as a virtual machine forever, but that was still able to leverage this technology as a powerful tool in the context of our broadened up optimization effort. >> All right, well, Steve, thank you so much for giving us the updates. Congratulations on going GA for this solution. Definitely look forward to hearing more from the customers as they come. >> All right, thanks so much Stu. I appreciate it. >> All right, stay tuned for more coverage of KubeCon CloudNativeCon EU 2020, the virtual edition. I'm Stu Stu Mittleman. And thank you for watching theCUBE. (upbeat music)

from San Francisco it's the queue covering Red Hat summit 2018 brought to you by Red Hat hey welcome back everyone here live in San Francisco at Moscone West of cubes exclusive coverage of Red Hat summit 2018 I'm John four with mykos John Troy a founder of tech reckoning advisory and on community services firm our next guest is Jason O'Connell openshift platform owner of mark mcquarrie group welcome to the cubes let's get it right that's right well the retail bank of Macquarie so thank you and financial services thanks for coming on so bossy begging is pretty hot big time early adopter of all things tech yes and you doing a lot of work at kubernetes tell us about what you're doing take a minute to explain your job what your focus is some of the some of the environment DevOps things you're doing it's a basically I'm head of the container platform team at Macquarie Bank so basically my team manages open shifts on AWS we do the architecture on there but we also focus a lot on the value add on top so we don't just give our our customers for my team are the developers and the development teams we don't just give them a blank platform we do a lot of automation a lot of work on top of that basically because we want to make sure that the idea of a platform as a service is that we do as much as possible to make developers lives easy talk about the journey when did you start on this effort Asli Amazon's great cloud we use it as well other clouds are coming on you had Google and Microsoft and others but when did the open shift conversations start happening where were you what year was it how long have you been using it it's gone through some great changes I want to get your experience on that open shifter journey I mean somewhat of an early adopter I mean we started looking at this two years ago so that was openshift 3.1 a lot of the basic features weren't even there and it took us a year to both build it out as well as migrate about 40 applications to production so it was only a year ago that we've been in production so it's evolved like so rapidly during that time so 40 applications migrating right that enough in and of itself in a year is is a pretty heavy lift can you talk a little bit about are you just re platforming the applications obviously probably not rewriting at this point the open shift has been a good home for the applications that you started out with it sounds like I mean one of the reasons to choose open shift was docker and it was about that migration path I mean part of the migration was ensuring that developers could get everything running locally get these legacy systems we did a lot of micro services running locally on docker containers on their laptop then the migration was was easy from there but we deliberately didn't want to do like a lift and shift we wanted to rethink how we delivered software as part of this project okay what's the biggest challenges you had in doing this I mean as you can open ships got some great movement Houston Cooper native good bet and kubernetes is looking like a really awesome way to move workloads around and manage containers and clusters so you know what's what are some of the things we've learned what are some of the complexities that you overcame can you share a little bit about some of the specifics I think I think the newness is is probably the biggest challenge I mean going back to two years ago there was some very basic components that weren't there at the time and we knew were coming and even now there are pieces of work which we just don't tackle and we do a very quick fix because we know it's coming later I mean it's just moving and evolving so quickly you know we're waiting a lot for sto which is coming in the future so we're holding back on investing in certain areas because of that so it's always a constant challenge yeah I still looking good and the service mesh is hot as well how has OpenShift helped you but what's the list if you had to kind of boil it down what's the bin the the impact to you guys where's the where's that coming from I mean before we even selected OpenShift we had we're looking at our objectives from a business perspective not a technology perspective I'm the biggest objective we had was speed to delivery you know how could you get a business idea a product idea into production as fast as possible or even if you look at a minor fix to something something that should be easier develop it takes a data ride why does it take a month to release the production so speed of delivery was one of the key objectives and I can tell you more about how we we delivered that in detail but just going back to the objectives we also looked at developer experience you know sometimes the developers are not spending enough time coding and doing it they want they get bogged down in a lot of other pieces of work that I I'm really delivering business value yeah so again we wanted the platform to handle that for them they could focus more on their work this is the promise of DevOps and the whole idea of DevOps is to automate away the hassles and I mean my partner Dave a lot that calls a rock fetches no one likes to do all that work it's like can someone else just handle it and then when you got now automation that frees it up but this brings up the thing that I would love to get your reaction to because one things we've been covering and talking a lot about in the cube is this isn't happening around us it's not just what we're doing but this new modern way to deploy software you'll get like some of the big things that are happening in with cloud native and you mission is do is to do this awesome dynamic things on the fly that are automated away so it changes the how software is being built how are you guys embracing that what's the thought obviously you've got a team that's got the mindset of dev yeah I'll see embracing this vision and if everything else is probably substandard she'll you look at you know waterfall or any kind of non agile what is the your view of this modern era of writing code and building applications what I mean for people who don't aren't getting it how are you how do you explain it you know I think it's I mean it's an unbelievable time that we're in at the moment I mean the amount of automation that we're doing is huge and part of our openshift is that it's an automated bull platform so I've got a few junior guys in my team they're like two graduates and in turn they do a lot of the automation yeah it's that easy if you look at interestingly in like security and risk teams and governance teams where we're finding look they can improve security risk and all this by automating you know they're the one set and now we've got SEC offs movements and things like that so speed of production is is does not prohibit better security and in fact with Sec ups the amount of automation we do you got a far greater amount of security because we now know everything that's deployed we can continually scanning for vulnerabilities yeah so Jason you talked about it being new we've talked a little bit about culture how much of this has been a training exercise how much is that it's been a cultural shift within your organization as one of the leaders of it how are you approaching I mean we're lucky there within Macquarie Bank there was a large scale culture shift towards agile where the whole bank runs in that gel manner so that's helped us then fill in our technology and automation it complements that way of delivering so we've got some very unique ways where we've done automation and delivery which completely rethinks how we used to deliver before so right example yeah for instance now if you think why were people scared of delivering something into production why was a small change scary change and a big part of it is the blast radius if something went wrong you know connecting through to our API is we've got our own channels mobile apps a website you've got a lot of partners there are the companies connecting through as well and so even if you did a small change if it costs an issue everyone's affected at once so a big piece of what we did to deliver faster is allowed targeted releases you know I could target a release and a change just to you we could target it to a percentage of customers monitor rolled out quickly if there's a problem dial it up if it's looking good good target to any channel it seems like there's a business benefit to that too right that's massive here because you also can promise stability on certain channels if you want you can have faster channels that are moving quickly and in an API driven world we've got external companies connecting through to these api's you want to be able to say that we've given you a stable offering and you can upgrade when you want and then our channels we cannot move more fast so we've got a minister no-brainer I mean really the old way is completely dead because of that because I think what the blast radius you're pointing about blast radius the risk is massive so everyone's kind of on edge all these tests have to go in redundancies as if the planning is ridiculous all for the risk all that energy you're optimizing for a potential non-event or event here with micro services and you an out can go down to the granular level the granularity is really amazing so when you go forward first of all it's a recruiting opportunity to get better engineers wait this is a way we work I'm going forward I want you to comment on your opinion as an industry participant and can clarify this because a lot of people get confused here Automation they think jobs are going away administration is getting automated system admin type roles where junior people can now do more operating things but the operating roles not going away so talk about that that ops side because now the ops are more efficient the right things are audited maybe but talk about that dynamic between the right things being automated and the right things that are gonna roll to operational service messages or whatnot yeah I mean basically it's about getting people to do these higher-order functions so the people who are doing things manually and operating things manually you look at our Ops teams now morphing into like the classic SRE team you know the side reliability engineering teams where they're spending a significant amount of that time automating things you know looking at alerting and monitoring and then Auto healing I mean it's actually more work to automate everything but with a far greater amount of quality and reliability and what we get and the benefits are long it's worth it basically you do the work upfront and you reap the benefits and then variety away it's like writing rolling out software managing workloads talk about multi class here on Amazon multi cloud is a big focus to your hybrid cloud multi-cloud obviously we're seeing that trend how do you look at multi cloud as a practitioner what are some of the things that check our check boxes for you in terms of okay as we start looking to the next level there might be a multiple cloud scenario how do you think about that and how do you put that into perspective that's worth noting even two years ago and we selected openshift it was with the idea that we could go multi cloud you know that for the users for the developers they're not going to know the difference where we run it on so we're not locked into any provider final question for you if you can boil down openshift into kind of like a soundbite for you what does it mean to you guys what's been the benefit what's been it it's been that what's been the role what's the benefit of OpenShift as you pour the cloud journey you know I could say speed I could say automation I mean that's huge but but really open shift and read how to pick the winner which is docker and kubernetes and a colleague of mine is in coop con in Copenhagen last week he's constantly messaging me saying there's new tooling you guys can use this you can use that and it means that rather than us doing the work we're just getting tooling from the community so it's the de facto standards so that's that's probably the biggest benefit all the goodness is just coming right to your front door luckily and I got to do my homework every night playing around with this technology so yeah gates success story and again the great community open-source projects out there you guys can bring that in and productize it for the retail bank congratulations love open-source stories like this tier one citizen and again continues to power the world open source softens the cube do our part bring and use all the data from Red Hat summit 2018 I'm John fryer with John Tory we'll be back with more after this short break

(upbeat electronic music) >> Announcer: Live from San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hey, welcome back, everyone. This is theCUBE, we're live in San Francisco, California, here at Moscone West, Red Hat Summit 2018. I'm John Furrier, the co-host of theCUBE. We've got three great guests, exciting segment. Really looking at the future of computer programming, the youth in our generation, the young minds, and the award winners here at Red Hat Summit. Our three guests are Leigh Day, Vice Present of Marketing and Communications at Red Hat. Ellie Galloway with Jewelbots, and Sara Chipps, CTO at Jewelbots Thanks for spending the time and coming on. I really appreciate it. Love this story because I always, as a computer person, I always love getting nerdy, but now nerd is the new cool. So starting young and coding is not just for guys anymore, it's for everybody. So congratulations on your success. Take a minute to explain what's happened here, because the folks watching don't know what happened yesterday. You guys were featured at part of Open Source Stars. Leigh, talk about the story. >> So about three years ago, the Red Hat Marketing Communications Group decided that they needed a passion project, something that would make them feel more energized about coming to work and not just selling products, but telling genuine stories about people. We started our Open Source Stories films series, and that has turned into Open Source Stories Live as well. So yesterday we brought awesome stories, like Jewelbots to our stage to tell the story of children and others getting involved in coding. And Ellie and Femmie on our stage, talking about how people should code for good and we really love that message and applaud that. >> And coding is so social because it's fun. So talk about Jewelbots and what's happening here? So how did this get started? And then I'll go into some specific questions for the young future star here. (laughter) Sara, how did it all get started? >> Yeah, so Jewelbots got started out of a desire to make a product for young girls, to get them excited about coding. So we talked to about 200 girls and we asked them what was interesting to them, and over and over from them we heard that their friendships are really important to them. And so when we were talking to them about a bracelet that lights up when your friends are nearby and you can use it to send secret messages, they got really excited. And so that's what we built and we made it open source so they would code it as well. >> How did it all get started? What was the motivation, what motivated you to take on this project? >> Good question. So I've been a software developer for seventeen years, I was five years into my career before I worked with another woman and it was another five years after that, before I worked with another one. So I really, you know, I love this career and I wanted to figure out a way to get more women excited about doing it. So, talking to my male peers, I heard from them that they started about middle school age, and so I wanted to find something for girls that would also inspire them in that way. >> That's awesome, thank you so much for doing that. I love the story, it's super important. Now, how did you get involved? You just loved programming? You wake up one day and say, hey, I love programming? How did you get involved? >> Well first, me and my dad, my dad works for Microsoft, he helped me code a game in Unity and so I love coding games so much that later he showed me Minecraft min code. And so I got involved in that, by then I kind of knew how to code and everything, so I only asked my dad for help if I absolutely needed it. And then, since my dad new Sara Chipps from Microsoft, he showed me Jewelbot one day when I got home from school and I've been on my own programming since then. >> John: You having fun? >> I am. >> What's the favorite thing about coding that you like? >> I love solving problems, and so solving problems is probably my favorite part in coding. I solve a lot of problems and inventions, tiny ones and just kind of figuring things out. >> Did you get all your friends involved? Did you spread it around to your friend group? >> I am getting some friends involved. In my YouTube channel I have someone I shared Jewel a lot with and showed how to code, and yeah. And at school, at my next school, I am going to create a Jewelbots club, and I'm hoping I can get a lot of people to join. >> So is it fun, is Jewelbot fun? I mean, how does it work, how does he Jewelbot work? So I wear a bracelet and then it lights up? So how does the code work? Is it an io sensor in the front end? How does it work? >> It works by Bluetooth. Do you mean friendship coding mode, or? >> Friendship coding mode. >> Okay, friendship coding mode. Yeah, you use Bluetooth for friendship coding mode. You pair Jewelbots together and it's pretty simple. You don't need a program, you can start right away without any program and it already has a default on it, so yeah. >> Do you have an agreement with Snapchat yet? Because that would be a great geofence feature, if I had like a Jewelbot with Snapchat integration. >> You can communicate by vibrates but there's not a Snapchat picture. >> Not yet, we'll make sure that we get that back and I'll get my daughter involved to jump in. How about the community aspect? I love the story, because what it does, it makes it fun. You don't want coding to be like eating spinach or, you know, taking out the trash or sweeping, you know, the floor up, you want to make it fun. Kids want to make it fun and gaming is key. When did it start clicking with you, Sara? You know, when did it start getting momentum? >> Yeah, well I think one thing that we realized, is that coding doesn't have to be a lonely activity, it doesn't have to be just one person sitting in a basement coding, it could be really anyone, and it's such a social thing, you know? All coders are self-taught and we all learn from each other, so having the ability to have a community that you can reach out to that are excited to help you and that kind of thing was a really important part of what we were building. >> So you guys were on stage... So tell about what happened here, 'cause folks didn't get to see and they can see it online after on a replay, you guys are out on stage, did you do like a demo? Tell us what happened on stage. >> We had a whole afternoon session that was focused on showcasing collaboration, young people coding, STEM. We had a group from our co-op, alumni come to the stage and talk about their experiences with Co.Lab, programming Raspberry Pis to take pictures. These are middle school girls, we've done programs with them all over the east coast. Then we had our CMO talk about his open-source experience. We had Women Open Source Awards, and then Sara and Ellie came out and told the audience about Jewelbots and it was just an opportunity to shine a light on their awesome project and to showcase young women doing great things. And showing women that they should have the confidence to code alongside men. >> Yeah, great program, how does someone get involved? How can someone get involved with Red Hat's Open Stories and your communities with Jewelbots. What can you guys share? Is there locations or a web app? Is there something you can get involved in? How does someone get involved? >> Well, Red Hat, we have seven Open Source Stories films, that people can go online and watch. But then yet, there's 90 of them for an open-source story, OpenSourceStories@RedHat.com is a way to contribute to that. But we're always thinking about new ideas, taking contributions and love to hear about these stories. >> Sara, how do I get involved in the Jewelbots? For anyone else watching who might be inspired by this awesomeness you guys have going on here. Great practice, I love how you're doing this. How do they get involved with what you're doing? >> So, if you have young girls in your life Jewelbots.com, Amazon.com, Target.com is all where you can get Jewelbots. If you don't and you know some people that do, a lot of people have started hosting events around Jewelbots, so if people in your office might have daughters and they might be interested in something like that, that's something that we help people do, as well. >> That's great. Ellie, what's your thoughts on all this? This celebrity status you have? Your YouTube followers are going to go through the roof now. >> Yeah, since yesterday I've had over 75 new followers. >> John: Wow. >> So yeah, it's amazing. >> Can she say the name of her YouTube channel? >> Of course. >> EllieGJewelbots. >> EllieGJewelbots, we're going to promote it, make sure it's on the screen, guys, great program. I'm so excited for you, that's amazing, don't stop. It gets better, more fun every time. When you build cool stuff it's magical. And tell all your friends. Great stuff, thanks so much for doing this. Great program, thanks for coming on. >> Thanks for having us. >> Thanks for having us. It's theCUBE, live here. A really inspirational inspirational moment here, getting everyone started at the young age really kind of opens the aperture of all people, all diversity, inclusion and diversity, really critical part of the community paying it forward. Of course, theCUBE's doing our part here, be back with more live coverage after this short break. (upbeat electronic music)

live from San Francisco it's the cube covering Red Hat summit 2018 brought to you by Red Hat hey welcome back everyone we're here live in San Francisco red hat summit 2018 s cubes exclusive coverage we're out in the open in the middle of floor here as open source has always done out in the open it's the cube doing our part extracting the cylinders I'm John for the co-host of the cube with John Troy you might coast analyst this week he's the co-founder of a firm advisory firm our guest case is Paul Comey a president and products on technology of Red Hat architecting the future of red hat and products and technologies all open source great to see you again major see you so thank you coming on so great keynote today you guys have done a great job here I thought the messaging was great but the excitement was strong we just came back off of a week in Copenhagen coop con where kubernetes clearly sees the de facto standard around kubernetes the core kubernetes with a lot of room to differentiate around you got sto service meshes a lot of exciting things for application developers and then under the hood and the new life being brought into OpenStack so there's clear visibility now into what's going on swim lanes whatever we call it people kind of see it so congratulations thank you magical moment Lucky Strike all on the cards give us some color you guys been working on this for a while go back and where did it all start and when did things start clicking together for you guys well I know I sometimes sound like a broken record here but I mean the key to our success is the commercialization of Linux I mean you know Linux we started Linux as a commodity play you know it was cheaper cheaper almost as good et cetera but it became such a powerful platform all the innovation you just talked about is built around Linux it's all tied into Linux so once we lay down the Linux base and the customer and the customer data centers which is such the logical extension to go to these new technologies because it really you really need to be a Linux vendor in order to be able to do a kubernetes to release to be able to support our containers release any of these things it's all just intertwining the Linux and your model is working honestly the open source is no secret that that's open open it's over proprietary and closed but you also have a community model that's feeding into the price of technologies Jim Weider zzyx you know went into detail on hey you don't you know you have a crystal ball and technology because you're smart guys but ultimately the users in the communities give you direct feedback of what's relevant and cool at the right time this is really where kubernetes Lucky Strike for you guys was really there you saw it so the commitment you jumped in can you explain that dynamic of how the products get fed in from the communities I'll give you actually a better example of OpenShift itself so we originally started OpenShift back in 2011 and we started it as a marketing project we started it as a as a cloud-based platform to get developers out there building to our platform and a lot of our customer base saw it and came to us and said I want this as a product this is really really powerful so we made a product out of it first one kubernetes wasn't around containers weren't around we'd built it on virtual machines we had we had what we called gears to lock in and and then containers started to morph in and read by release three we transformed it to containers then we brought in kubernetes because we had worked with the Google folks earlier on that so we really listened to our customers we started at something we thought was going to be an expense and it turns out to be you know one of our hottest our hottest platform right now based on what our customers in the community told us timings everything - and the good timing is as the clouds took the scale started also becoming relevant you see Amazon success now you got as your IBM and everyone's kind of seeing that opportunity how are you guys looking at the container piece because you know we can look at the history and docker you know trying to monetize too early we've been you know we've documented that it went well in the cube many times core OS a recent acquisition big one for you guys and strategic but also a great team containers are super important talk about the role of containers specifically not so much as a business model but as a lynchpin right between how orchestration is moving and how these service messages are coming out I mean you think just real quickly what containers are first containers are just Linux carved up in a different way you still have a kernel still have user space the difference is you take just the user space you want with the application and you run it that way so all the same life cycles security issues you have to fix etc they have to do on a standard Linux have to do it in containers the first thing containers been around forever they were in units if we all if we all remember but the killer app for containers was because now when I can bring just enough two of the OS with the application I can run that to the cloud that's how we get the app out to the cloud that's how we get it onto the private cloud out to any of the public clouds how we reverse the clouds so even though they've been around for a while it's the killer app for containers so you mentioned hybrid cloud hybrid cloud multi-cloud are there are the terms it's this week we hear them a lot that been up on stage one way of putting it is is thinking about that different places of deploying but in one you are really saying that it doesn't matter where you deploy there's there's layers of an especially openshift can take you to different clouds it location doesn't matter anymore can you drill down on that a little bit absolutely I mean our our whole we took a bed I mean it sounds obvious now it always does right we took a bed on hybrid cloud I've been talking about it for six or seven years and what it means is customers are going to have applications that run on bare metal they're going to have running as virtual machines probably on VMware they're going to maybe run their private clouds maybe containers maybe across multiple clouds end of the day it's it's Linux underneath that what customers don't want is five different operating because every Linux is slightly different they don't want five different operating environments they want and want one so what we do with rel and with openshift is we give you that abstraction layer for your application to code once and you can move that app anywhere I mean the clouds the public clouds have brought a tremendous amount of innovation and I don't want to say this in a derogatory way but in some sense they're like a mainframe because they have their stack all the way up to there a flick their products are their services and so you start you start up you start up a service of server lists of lambda that's never leaving Amazon never so so it's great in many cases if that's ok for that app but there's a lot of cases you might want to run the app here one day and there the next day so you really need an abstraction layer to ensure that you have that portability and that's what shift and containers are so important right I hear things like de-facto standard and abstraction layers the bells go up opportunity because you now that's where complexity can be reduced down when you have good at rational layers but we've been interviewing folks here and the some themes have come up about the sea change that we're facing this cloud scale new Internet infrastructure going on globally and the two points are tcp/ip moment you know during that time that was networking even and that disrupted decnet today and others and then HTTP both are different HTV was all new capabilities the web disrupt the Direct Mail and other things analog leaving but he stupid created inter inter networking basis right Cisco and everything else here what containers what's interesting and I want to get your reaction to this is that with containers I don't have to kill the old to bring in the new I can do the new and then let the lifecycle of those workloads take a natural natural course this is a good thing for enterprise they don't have to rush in do a rip and replace they don't have to react attacked hire new people at massive scale talk about that dynamic is that seems to be what's happening it's exactly what's heavy you know we did a bunch of demos on stage this week I think nine of them live the coolest demo was the one where we showed we actually took a Windows virtual machine with a Windows SQL based virtual machine from VMware with tools we brought that over to a KVM environment which is it's a different format for the VM brought that to a KVM environment we then use tools to slice it up into two containers one being the app itself the other being at SQL and we deployed it out to openshift and we could eventually have deployed out to any public cloud that's significant for two reasons first of all you're now seeing kubernetes orchestrating VMs right beside containers so you can kind of see where that's going right so that's really that's interesting for the operators now because now they get they bring whittled down some of that complex it's really interest interesting for the developers because from a perspective they're going to be asked to bring these traditional virtual machines into containers in the old world they have to go to a VMware front-end to do that then they have to come over here to a route to a to a rev or rel front-end to do it now they can just bring their VM with tools over work on it split it up into containers and deploy it it's it's its efficiency adds at its best and shift without any effort without any effort really how about the impact of the customers because this is to me that the big money moment because that means an enterprise can actually progress and accelerate their digital transformation or whatever they got going on to a new architecture a new internet infrastructure we hear things like Network effect decentralized storage with with blockchain new capabilities that aren't measured by traditional older stacks that we've seen an e-commerce DNS and other things so a shifts happening the shifts have a cloud scale I say synchronous the pile are these cars with a scalable whole new way let's see what does that mean for customers what it means for customers is two things that are important the shift is happening you're getting tools and you're getting tools and platforms to make that shift more seamless and you know I'd love to say it's all red head engineers that are giving you this but the reason why it's moving so fast is because it's open so the innovation comes from anywhere it's way too big of a problem for any one customer to solve where we're just helping our customers consume it that's one thing but I think the other thing is important is that's important is not every application is going to be suited to go to a container based application so because it's all on that rel common layer our customers can still have one operating environment and have have compatibility as they do the shift but still keep their business going over here maybe forever these apps may never come off a bare-metal for example Paul I wanted to talk a little bit about Red Hat scope inside IT I love the the connection that between you know the container layer that is just Linux but and also the standards layer but you know now that we're up at threat you know with the with open shift and with multi cloud you know global huge scale operation there's a lot there's a lot more involved right cloud layout level ops is you now at Red Hat is involved with with process and and culture and you have a lot more than just you have a lot more that you're involved in helping IT with than just a Linux and some and connection to the back to the machine so can you talk a little bit about about what you're trying to do with the customer great it's a great point then when I started with a company 17 years ago we weren't talking to CIOs in fact the CIOs we were in that we were coming in the back door the operations people were bringing Linux in the back door and they the CIOs didn't even know it was run in there and but now as you said we're CIOs are trying to figure out how does public cloud fit into my IT environment how does a multiple public cloud fit in out of containers fit in what do I do with my older applications where there re architecting that's at the cio level now you know they're having to re architecture architect for the next generation computing so we've had to build services around that we have labs we have innovation labs where we bring our customers in and work with them and help them you know figure out and help them map out where they're going for the first time we actually I've had cut many customers tell me so is this is the with openshift it's the first time I've got my developers in my Ops people in the same room and we've facilitated that discussion because no one's right it's gotta be one one motion and so that's that's the interesting part for us we've really moved up the chain and our customer base because we're almost a consultative sale now to help them get to the next generation talk about the enabling aspect of this because I referenced tcp/ip and HTTP but now if you go forward and say okay we're gonna have this new environment it's not just about redheads by Linux it's about the operating system which you guys obviously offer for free and then have services around it and have stopped software how is Linux with the new capability of open shift and standards like kubernetes with containers how in your opinion is that an enabling an opportunity for ecosystem new startups and enterprises themselves because we see if this happens and continues to happen oh yeah it's going to be a new names gonna come out of the woodwork new startups gonna happen you see you see it every day I mean you wouldn't do a start-up today that wasn't software wise it wasn't based on Linux and and and that's why in all the innovation today because all the innovation today is based on Linux you know one of the things we and that we released last week a cube con is I don't know if you saw it or not we released a kubernetes SDK and it can track or OS it couldn't came with the core OS guys we put that out into the community it's really an SDK for ISVs and software but vendors to build into the api's of kubernetes in an open way so that once they get out into the commercial world they're ready that's how significant we all think that kubernetes is going to be i we think that's where the services are going to hang in the infrastructure but but having said that I think it also tells you that you know the impact that these open technologies are having on the future I wanna get into the chorus in a minute but I want to ask you about the white spaces so if someone who's that in charge of the troops inside Red Hat products and technologies where's the white space opportunities that people can dig in and and build out innovation around this major shift that you guys are on this wave where's the opportunity for the channel partners the integrators globe last night's developers anyone where's the key areas I mean with our platforms of open shift and OpenStack we have we have certified entry points via api's in storage networking management so we've got hybrid management but certainly we don't think we're gonna do everything in management by any stretch we have it we have a set of api's from management partners to plug in and by the way what I tell my my management R&D folks no hidden api same api's we use they use so so storage is another area new storage solutions networking certainly AI is one of the areas one of the things we showcased here was AI permeating through our entire product line I don't know if you saw the face recognition demo out there but it was it was pretty cool in and even if you want to consume that AI through one of the cloud providers we can pass you straight through from openshift to consume it that way as well on automation I want to get your thoughts on something we've talked a few days ago here on the cube was automation is great so let's give an example I'm automating a service you know if it's a coop with kubernetes and containers and as a memory leak right and every boots but automates I don't know so you got to have a new level of instrumentation down at the code level how do you see that playing out because now we got to be smarter about what's working and not working because I might not never know just reboots intermittently give me some mystery was a memory link could be something else but but that's so this is one of the places where using AI so we've been we've been our first stint with AI came out of our support group so we've been supporting Linux and open source for 25 years got a massive database of what failures were what the fixes were we started using AI in a support group to point our reps at a particular article based symptoms that they were hearing from our we realized we had about an 80% hit rate on you know on getting to our reps to the right to the right article so now we've built that into the products and so we use that AI like for example OpenShift IO which is at one of our developer platforms developers trying to link in a library we can tell them you know what there's a new there's a newer version of that library you know what that library has a security flaw in and at this line of code maybe you want to consider using another one but it's from our years and years of doing this that we're building that day database I mean oai is only so good as the data that you fed it and so have a certain level of granularity down to do you do it and then also ai it also is a reason why all our services are now on open shift because you're absolutely right if I've got a raw JBoss service running on raw Amazon I can't instrument that underneath because Amazon's got that layer closed if I have open shifts there and it's in the infrastructure is open shift even running in Amazon or sure anywhere we can now instrument that to look at some of the things we need to look at to recognize an event a week or or whatever Paul talk about their journey with kora West obviously we've been super excited by that we've been following Korres from the beginning great technical team pure open-source guys and in that container part of the evolution in time everyone's trying to force a business model and you're really hard to force a business model is something that too early or might not even be relevant to build the business around it might be a feature not a company kind of thing so you guys put a big price tag on them sizable chunk of cash how did it all play out you guys just like hey wow we're gonna we wait like these guys they're super technical meeting of the minds and then how that has fit in from a product and technology stand a little bit a little of all of that of course the benefit of being you know having the open source development in in your DNA as we knew them all right so we knew how good they were because they we work our guys work with them every day so that was something when they decided early on like us to go to kubernetes they became a big part of the of the community of kubernetes in our model from day one you can't be an open-source provider if you're not strong in the upstream community because how can you affect what your customers are asking you to do if you and effect upstream they were big in the upstream big and kubernetes and so at that point we that's what we just said they had done some interesting things that we hadn't got to they did a lot of the automation they were doing over-the-air updates of the container platforms a week which we hadn't got to yet they had a really good following in the community so we decided you know we paid a we paid a hefty price but at this stage of the game we really feel that we took an early bit in kubernetes we really feel that that's gonna be the future in containers if there's gonna be a place a place that you pay maybe a little more this is the place well Paul I think another example is ansible a year or two back right and that's been a remained a huge success and I can say you haven't messed it up right and it's it's it's been powerful accomplished well most acquisitions you know and in end in tears so it seems like RedHat seems to be good at this kind of an open source acquisition we we get to interview them for two years before we bring them in based on well how we work in the community but you know we're very where we're bringing in people I don't I hate to say the word M&A or acquisition I just hate that word because we're just joining forces here you know it just took a a big check to do it yeah and you guys have the business model kneel down this is good was good for court at the time for them to they didn't have to worry about having to figure out a go to market and monetize right an upstream presence which was very valuable and then trying to shoehorn a business all around it and which is difficult companies died doing it yeah I mean I can't think of many that have been that successful at it I mean it's a hard thing to do I mean look we've had a great advantage you know we've had rail in the market for 16 years and it built a base for us I'm not gonna try to I'm not gonna try to kid you on that and it's the it's the Linux base that everything's getting built around and so we just keep those those principles we've used for the last 16 years we stay true to weak true to them we could not do a proprietary piece of software now if our lives depended on it that's the DNA well how do you handle the growth you get hiring new people - that's a challenge we've been we were talking to folks about on your team and across RedHat around hiring people and and you got to maintain that eco so you have to maintain that DNA way how do you guys do that what's the is there like a special three three day you know hypnotic class a you know this is how we do it I have to tell you it's a bit easier on the engineering side because you know it's typically engineers that have been working in the community etc but you know our business unit side and other pieces where people have been coming out of big companies and they're used to a hierarchical environment we really take that into account in the interview process I'll be frank not everyone makes it through I mean RedHat is you know titles really don't matter a ringlet company yeah totally engineering as all should be by the way if biased opinion fit okay so great to have you on thanks for spending the time I know you're super busy a couple questions before we wrap up what are you most proud of as you look back now I mean someone again it's almost hindsight's 2020 looks obvious these calls but you know I interviewed Diane at OpenStack many years ago took a lot of heat for that kubernetes movement people weren't it wasn't obvious to a lot of people at that time the kubernetes bet you guys make good bets looking back what are you most proud of that's most significant or or you think people should know well those were that was a seminal moment in redhead history that decision what take us through some of the key milestones in your opinion the for the first one there's probably three or four the first one was gonna Ralph because you have to understand what we did we were in we were a completely retail when I joined the company with 50 million dollars in revenue losing two hundred and so we had a retail product we stopped it to go to route literally literally stop the product bet the company move second one was JBoss we were about 300 million in revenue we paid 425 million for JBoss now that was a big one the third one you might not recognize this one moving from Xen to KVM because Xen was going off down the the VC world trying to figure out how to monetize as a company somebody in Israel came up with a with a better model with KVM the rest of the industry was on Zen we said as a single player we're going this way that was a big bet that I don't even know we recognized the significance of at the time and in kubernetes as I said we pivoted on that in 2012 or so and I've got a lot of R&D money in that and paying on what made you go to kubernetes just curious was the has the Borg success how software is being done at Google was it the role of containers did you guys have that foresight at that time saying containers gonna have a critical role we don't want to screw that up we can bring this in we're looking at from a stack perspective or was it more of a future scenario it was a lot of it was its its heritage out of Borg and knowing the talent in Google and engineering and we talked to we had we had many many discussions we all we continually do with those guys so I think it was mostly a technical decision and what we said was at that point putting our weight behind it we just need to make the community successful so I mean we quickly figure with us in Google it was a it was a fairly good bad not as sure bet but a good bet and that's what made us go there it was really it was really a technology decision possible final question as we wrap up for the folks watching who couldn't make it here in San Francisco for Red Hat summit 2018 what's the big takeaway what's the present technology what's the North Star for you and your team and what are you guys putting as a priority what's the focus I think I think the takeaway from here is you know I think it's I think it's a pretty solid couple things are really solid it's going to be the future is going to be open source period end of story especially in the infrastructure and application development world third thing is hybrid cloud is the model it's the only practical way not every application is moving to one public cloud tomorrow and the third thing is for Red Hat that's the architecture that we build around every day we guide what are what products we build what M&A we do everything we do is around that model and open if I see a centerpiece of all the piece without all that coming thank you for coming on president of Protestant technology at Red Hat I'm John ferry with John Moyer stay with us for more live covers our third day of three days of live coverage here out in the open like open source we're doing our share bringing you the content you right back with more after this short break you

>> Announcer: Live, from San Francisco. It's the CUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Okay, welcome back everyone. This is the CUBE. We're here in San Francisco live, wrapping up our third day of coverage at Red Hat Summit 2018. I'm John Furrier. Great event and here, our special guest appearance as our closing analyst. I've been here all week with John Troyer. He had to leave early to get down to San Jose. John Troyer is the co-founder of TechReckoning, which is an advisory and community development firm and in his place we have Keith Norbie who's the Senior Manager at NetApp, doing business development, DevOps pro, former solidifier, really at the heart of the NetApp that's transforming. Here as my guest analyst, welcome, welcome to the CUBE. >> Yeah, thank you. >> Thanks for coming in and sharing your knowledge. And to wrap up the show, really a lot going on. And I know you've been super busy. You had an appreciation of that last night with NetApp. You had customers there. But I really wanted you to come on and help me wrap up the show because you're also at the kernel of DevOps, right, where DevOps and storage, we were talking last night about the role of storage, but that's just an indication of what's going on across the board of all resources. Invisible infrastructure is the new normal and that is what people want. They want it to be invisible but they want that highly performant, they want it scalable. So roles are changing, industries are changing, application development is changing. Everything is changing with cloud scale at an unprecedented level and Red Hat is at the center of it with the kernel Linux operating system. It's all about the OS. >> Yeah. >> That's my takeaway from the show. What's your takeaway, what's your analysis here of Red Hat Summit? >> Well first off, you know, 7,000 people is a heck of a lot of growth. In some of the birthplaces of VM world, we have the new birthplace of open being real, and Red Hat's been the really the true company that's taken open and done something with it. >> What's the big, most important story for you here this week? What jumps out at you that jumps off the page and says, wow, that's happening, this is real, obviously open source, going to a whole 'nother level, the cat's been out of the bag for awhile on that, but really, it's just about the exponential growth of open source, Linux Foundation's Jim Zemlin talks about this all the time, so okay, that's not to me the most important, so that's just reality. >> Yeah. >> But what jumped off the page for you here? >> I think they said it best in one of the keynotes where they went from this being a concept of cheap to a concept of being functional or capable. So it's the c-to-c transition of cheap to capable and it is about trying to unlock the capabilities of what this show delivers, not just on Red Hat's platform but across the ecosystem. And as you see that play out in any one technology sector, you know, we've been talking DevOps which I think has been a phenomenal study in and of itself saying you know, we've gone from a lot of thought leadership a lot of, if you go to DevOps Enterprise Days, they'll talk a lot about culture and operational things to now seeing a maturation in the industry to actually have, you know, some very specific capabilities and customer (mumbles) models. >> I think the thing that jumped out, for me, Keith, I want to get your reaction to it, is that DevOps ethos, which has been around for awhile, not a lot, you know, a couple years, eight years maybe, since cloud really native really kicked in. But the ethos of open source, the ethos of DevOps, infrastructure as code is not just for software development anymore because as the things that are catalyzing around digital transformation, with Kubernetes becoming a defacto standard, with the role of containers, with server-less and all this infrastructure being programmable, the application market is about to go through a massive Renaissance, and you're seeing those changes rendered in the workplace. So the DevOps and open source ethos is going everywhere. It's not just development, it's marketing, it's how people manage their businesses and work force structure. You're seeing blockchain and decentralized applications on the horizon. This new wave is not just about DevOps for infrastructure as code, it's the world as code, it's business as code, it's everything as code so if you're doing anything with a waterfall, it's probably outdated. >> Yeah, everything has its different pace and its cadence in different industries and that's the hard thing to predict for everybody. Everybody that's coming here from different walks and enterprises of life is trying to figure out how to do this. And that permeates out into, you know, vehicles and IoT edge devices, back to the core part of the data centers and the cloud and you've got to have answers for really the three parts of that equation in different modes and ultimately equal a business equation, a business transformation. >> What did you learn here? I'll just tell you my learning, something that wasn't obvious that I learned that's validated in my mind and they didn't talk about it much on stage in Red Hat. Maybe they do off the record, maybe it's confidential information, maybe it's not. But my observation is that the Red Hat opportunity is really global. And the global growth of Red Hat, outside the United States and Europe is really where the action is. You look at Asia and third-world countries with mobile penetration. The global growth for Red Hat and Linux is astronomical. To me, that clearly came through, when I squint through the puzzle pieces and say, okay, where's the growth coming from? Certainly containers, Linux containers is going to be bigger than Rel, so that's going to be a check on the financial results. That's good growth. But it's really outside the United States. I'm like, wow, this is really not just a North America phenomenon. >> Yeah, and really, demand is demand. And at NetApp we see this in APAC almost more so than a lot of the other parts of the world. The pace of innovation and the demand for innovation you know, just kind of finds its way naturally into this market. You know, this whole community and open source approach you know, sort of incubates a lot more innovation and then the pace of the innovation, in my opinion, just by natural fellowship of these people. And the companies trying to innovate in the segment with these things. >> So what did you learn this week? What was something that you learned this week that you didn't know before or you had a hunch or you validated it here? What is something that's unique that you could share that you've learned or validated or have an epiphany? Share some color commentary on the show. >> Yeah, I think there's a little bit of industry maturation, where this technology isn't just like a Linux thing and a thing for infrastructure people trying to do, you know, paths or container automation or something technical. But it's equating out to industry solutions like NFE and Telco is a great example, you know, where all of us want to get to a 5G phone, and the problem is, is that they've got to build a completely reprogrammable, almost completed automated edge cloud type of network. And you can't do that with appliances, so they have to completely reprogram and build a new global scale of autonomy on a platform and it's awesome how like complex and how much technology is there and what it really comes down to is us having a faster phone. (laughter) It's amazing how you have all that, and it equals something so simple that my 14-year old daughter, you know, can have a new obsession with how fast the new phone is. >> I mean, (mumbles) digital transformation in all aspects, IoT edge, you mentioned that, good stuff. I got to ask you, while you're here, about NetApp, obviously, SolidFire, a great acquisition from NetApp, some transformation going on within NetApp. What's going on there? You guys got a good vibe going on right now, some good team recruiting. You guys recruit some great people, as well as the SolidFire folks. What's going on in NetApp? >> Well, yeah, I was part of the SolidFire team and that was a great group of people to really see the birth of the next generation data center through that lens of the SolidFire team. As we've come to NetApp now, we've really seen that be able to be incubated into the family of NetApp, really into three core missions, you know, modernizing data centers, you know, with an all flash approach to the ONTAP and FAS solutions, taking the SolidFire assets and really transforming that to the next level in the form of an HCI solution, you know, which is really to deliver simplicity for various consumption of economics and agility of operations within an organization. And then, you know, having that technology also show up in the marketplace at Amazon and Azure. And this week we announced Google. So it's been fun to see, not just the SolidFire thing come to life in its own mission, but how that starts to federate in this data fabric, you know, across three different missions. And then when it really gets exciting, to me, is how it applies into things that help people transform their business, like we talked DevOps and unlocking that and some of the config automation with Ansible, unlocking it some of the things with open shift that we're doing with Trident in the container automation across three of our platforms. And then seeing how this also comes to life with other factors with code and RD factory management or CIC piplup Jenkins. It's about tying this entire floor together in ways that makes it easy for people to mature and just get more agile. >> And it's a new growth for the ecosystem. We're seeing, you know, some companies that try to get big venture-backed financing, trying to monetize something that's hard to do if you're not Linux. I mean, Linux's a free product. It's all about Linux and the operating system. So, Linux is the enabler. >> Absolutely. >> To all of this and whoever can configure it in a way that's horizontally scalable, asynchronous and with microservices architecture wins the cloud game, 'cause the cloud game is just now creating clear visibility. The role that open source plays, being open I mean, look at the role that Hypervisor closed and proprietary, harder to innovate in a silo. If you're open, innovation's collective, collective intelligence. >> And I thought that one of the keynote demos, on Day One, Tuesday morning, to me, was one of the more powerful ones, where they showed a VM environment being transformed into container automation. Like literally a SQL environment being on into a container-based environment from previously being in a VM environment. And traditional IT doesn't have to do a whole lot of heavy lifting there. You know, people want that ability, kind of inch into it and then transform at their own time scale. >> Yeah, I think the big takeaway from me here in the show to kind of wrap things up is Red Hat has an opportunity to leapfrog the competition in way that's not a lone wolf kind of approach. It's like they're doing it with a collective of the whole. The second thing that jumps out at me, I think this is really game-changing for the business side of it is that because they're open with Linux and the way the ecosystem's evolving around cloud, the business issues that enterprises face, in my opinion, is really about, how do I bring in the new capability, okay of cloud, cloud scale and all asynchronous new infrastructure and applications without killing the old? And containers and Kubernetes and Openshift allow companies to slow roll the lifecycle or let workloads either live and just hang around or kind of move out on their own timetable, so you get the benefits of lift and shift with containers without killing the existing old ways while bringing in new innovation. This, to me, is an absolute game changer. I think it's going to accelerate the adoption to cloud. And it's a win-win. >> Absolutely. Transform agility. >> Cool, well Keith, thanks for coming on. Any final thoughts from yourself here on the show observations, anecdotes, stories? >> You know, sometimes less is more and this show has, you know, in a lot of ways both gotten more complex, but I would argue also much more simple and clear about directional paths that organizations can take. And that is working backwards from cloud what cloud is teaching the rest of us is that both, you know, functions more so than technology, and agility in terms of the ability to consume at the pace of the business. Those two things are the ways to take all this complexity and simplify it down into a couple of core statements. >> Someone asked me last night, what I thought about the current situation in the industry and I want to get your response to this, and get your reaction. I said, if a company is not making tweaks to their business, they're probably not positioned for success, meaning, with all the new things that have developed just in the past 12 to 18 months, if they're not tweaking something in some material, meaningful way, not like, not completely replatformizing or changing a business model. A tweak, whether it's to their marketing, or their tech or whatever, then they're probably stuck. And what I mean by that is that new things have happened in the past 18 months that are moving the needle on what the future holds. And to me, that's a tell sign when someone says is someone doing well? I just look at 'em. Well, they were kind of just doing the same thing they did 18 months ago. They really, they're talking a game, but they're not changing anything. So if they're not changing anything, it's probably broken. Your thoughts? >> Yeah, it was best said in terms if you look at the the Fortune 100 right now and contrast that with, you know, 10 or 15 years ago and it's a different landscape. And projecting that out another even five years, the rate of acceleration on this is a brutal scale. And so any company that's not thinking through transformation, you know. My kids are the future consumers. You know, they grew up as digital natives. You know, we're all migrants and they just automatically assume all these things are going to be there for them in their rhetoric, in their rationale. And the current companies of today have got to figure that out, you know, and if they don't start now, you know, they might be out of business in five years. >> If you're standing still, you get rolled over. That's my opinion. CUBE coverage here, of course, wrapping up our show here at Red Hat Summit 2018. We've been in the open all week here in the middle of the floor at Moscone West in San Francisco, live for the past three days. All the footage on Silicon Angle.com as to articles from our reporting, the CUBE.net is where all the videos will live and check out wikibon.com for all the research. Keith, thanks for being our guest analyst in the wrap up, 'ppreciate it and congratulations on all your success at as Business Development Exec at NetApp and the SolidFire stuff. Great you coming on. DevOps culture going mainstream. Software's powering the world. This is the programmable world we live in powered by Linux. Of course, the CUBE's there, covering it. Thanks for watching. Red Hat 2018, we'll see you next show.

(upbeat electronic music) >> Narrator: Live from San Francisco, it's The Cube, covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hey, welcome back, everyone. We are here live, The Cube in San Francisco, Moscone West for the Red Hat Summit 2018 exclusive coverage. I'm John Furrier, the cohost of The Cube. I'm here with my cohost, John Troyer, who is the co-founder of Tech Reckoning, an advisory and community development firm. Our next guest is Jonathan Donaldson, Technical Director, Office of the CTO, Google Cloud. Former Cube Alumni. Formerly was Intel, been on before, now at Google Cloud for almost two years. Welcome back, good to see you. >> Good to see you too, it's great to be back. >> So, had a great time last week with the Google Cloud folks at KubeCon in Denmark. Kubernetes, rocking the world. Really, when I hear the word de facto standard and abstraction layers, I start to get, my bells go off, let me look at that. Some interesting stuff. You guys have been part of that from the beginning, with the CNCF, Google, Intel, among others. Really created a movement, congratulations. >> Yeah, thank you. It really comes down to the fact that we've been running containers for almost a dozen years. Four billion a week, we launch and collapse. And we know that at some point, as Docker and containers really started to take over the new way of developing things, that everyone is going to run into that scalability wall that we had run into years and years and years ago. And so Craig and the team at Google, again, I wasn't at Google at this time, but they had a really, let's take what we know from internally here and let's take those patterns and let's put them out there for the world to use, and that became Kubernetes. And so I think that's really the massive growth there, is that people are like, "Wow, you've solved a problem, "but not from a science project. "It's actually from something "that's been running for a decade." >> Internally, that's called bore. That's tools that Google used, that their SRE cyber lab engineers used to massively provision manage. And they're all software engineers, so it's not like they're operators. They're all Google engineers. But I want to take a minute, if you can, to explain. 'Cause you're new to Google Cloud. You're in the industry, you've been around, you helped form the CNCF, which is the Cloud Native Foundation. You know cloud, you know tech. Google's changed a lot, and Google Cloud specifically has a narrative of, they're one big cloud and they have an application called Google stuff and enterprises are different. You've been there now for almost a year or more. >> Jonathan: Little over a year, yeah. >> What's Google Cloud like right now? Break the myths down around Google Cloud. What's the current status? I know personally, a lot of cloud DNA is coming in from the industry. They've been hiring, making some great progress. Take a minute to explain the Google Cloud. >> Yeah, so it's really interesting. So again, it comes back from where you started from. So Google itself started from a scale consumer SAS type of business. And so that, they understood really well. And we still understand, obviously, uptime and scalability really, really well. And I would say if you backtrack several years ago, as the enterprise really started to look at public clouds and Google Cloud itself started to spin up, that was probably not, they probably didn't understand exactly all of the things that an enterprise would need. Really, at that point in time, no one cloud understood any of the enterprise specifically. And so what they did is they started hiring in people like myself and others that are in the group that I'm in. They're former CIOs of large enterprise companies or former VPs of engineering, and really our job in the Office of the CTO for Google Cloud is to help with the product teams, to help them build the products that enterprises need to be able to use the public cloud. And then also work with some of those top enterprise customers to help them adopt those technologies. And so I think now that if you look at Google Cloud, they understand enterprise really, really well, certainly from the product and the technology perspective. And I think it's just going to get better. >> I interviewed Jennifer Lynn, I had a one-on-one with her. I didn't publish it, it was more of a briefing. She runs Product Management, all on security side. >> Jonathan: Yeah, she's fantastic. >> So she's checking the boxes. So the table stakes are set for Google. I know you got to do some basic things to catch up to get in the cloud. But also you have partnerships. Google Next is coming up, The Cube will be there. Red Hat's a partner. Talk about that relationship with Red Hat and partners. So you're very partner-centric with Google Cloud. >> Jonathan: We are. >> And that's important in the enterprise, but so what-- >> Well, there tends to be two main ares that we focus on, from what we consider the right way to do cloud. One of them is open source. So having, which again, aligns perfectly with Red Hat, is putting the technologies that we want customers to use and that we think customers should use in open source. Kubernetes is an example, there's Istio and others that we've put out that are examples of those. A lot of the open source projects that we all take for granted today were started from white papers that we had put out at one point in time, explaining how we did those things. Red Hat, from a partner perspective, I think that that follows along. We think that the way that customers are going to consume these technologies, certainly enterprise customers are, through those partners that they know and trust. And so having a good, flourishing ecosystem of partners that surround Google Cloud is absolutely key to what we do. >> And they love multicloud too. >> They love multicloud. >> Can't go wrong with it. >> And we do too. The idea is that we want customers to come to Google Cloud and stay there because they want to stay there, because they like us for who we are and for what we offer them, not because they're locked into a specific service or technology. And things like Kubernetes, things like containers, being open sourced allows them to take their tool chains all the way from their laptop to their own cloud inside their own data center to any cloud provider they want. And we think hopefully they'll naturally gravitate towards us over time. >> One of the things I like about the cloud is that there's a flywheel, if you will, of expertise. Like I look at Amazon, for instance. They're getting a lot of metadata of the kinds of workloads that are on their cloud, so they can learn from that and turn that into an advantage for them, or not, or for their customers, and how they could do that. That's their business decision. Google has a lot of flywheel action going on. A lot of Android devices connected in the Google system. You have a lot of services that you can bring to bear in the cloud. How are you guys looking at, say, from a security standpoint alone, that would be a very valuable service to have. I can tap into all the security goodness of Google around what spear phishing is out there, things of that nature. So are you guys thinking like that, in terms of services for customers? How does that play out? >> So where we, we're very consistent on what we consider is, privacy is number one for our customers, whether they're consumer customers or whether they're enterprise customers. Where we would use data, you had mentioned a lot of things, but where we would use some data across customer bases are typically for security things, so where we would see some sort of security impact or an attack or something like that that started to impact many customers. And we would then aggregate that information. It's not really customer information. It's just like you said, metadata, themes, or trends. >> John Furrier: You're not monetizing it. >> Yeah, we're not monetizing it, but we're actually using it to protect customers. But when a customer actually uses Google Cloud, that instance is their hermetically sealed environment. In fact, I think we just came out recently with even the transparency aspects of it, where it's almost like the two key type of access, for if our engineers have to help the customer with a troubleshooting ticket, that ticket actually has to be opened. That kind of unlocks one door. The customer has to say, "Yes," that unlocks the other door. And then they can go in there and help the customer do things to solve whatever the problem is. And each one of those is transparently and permanently logged. And then the customer can, at any point in time, go in and see those things. So we are taking customer privacy from an enterprise perspective-- >> And you guys are also a whole building from Google proper, like it's a completely different campus. So that's important to note. >> It is. And a lot of it just chains on from Google proper itself. If you understood just how crazy and fanatical they are about keeping things inside and secret and proprietary. Not proprietary, but not allowing that customer data out, even on the consumer side, it would give a whole-- >> Well, you got to amplify that, I understand. But what I also see, a good side of that, which is there's a lot of resources you're bringing to bear or learnings. >> Yeah, absolutely. >> The SRE concept, for instance, is to me, really powerful, because Google had to build that out themselves. This is now a paradigm, we're seeing a cloud scale here, with the Cloud Native market bringing in all-new capabilities at scale. Horizontally scalable, fully synchronous, microservices architecture. This future is a complete game-changer on functionality at the different scale points. So there's no longer the operator's room, provisioning storage here. >> And this is what we've been doing for years and years and years. That's how all of Google itself, that's how search and ads and Gmail and everything runs, in containers all orchestrated by Borg, which is our version of Kubernetes. And so we're really just bringing those leanings into the Google Cloud, or learnings into Google Cloud and to our customers. >> Jonathan, machine learning and AI have been the big topic this week on OpenShift. Obviously that's a big strength of Google Cloud as well. Can you drill down on that story, and talk about what Google Cloud is bringing on, and machine learning on OpenShift in general? Give us a little picture of what's running. >> Yeah, so I think they showed some of the service broker stuff. And I think, did they show some of the Kubeflow stuff, which is taking some machine learning and Kubernetes underneath OpenShift. I think those are very, very interesting for people that want to start getting into using AutoML, which is kind of roll-your-own machine learning, or even the voice or vision APIs to enhance their products. And I think that those are going to be keys. Easing the adoption of those, making them really, really easy to consume, is what's going to drive the significant ramp on using those types of technologies. >> One of the key touchpoints here has been the fact that this stuff is real-world and production-ready. The fact that the enterprise architecture now rolling out apps within days or weeks. One of those things that's now real is ML. And even in the opening keynote, they talked about using a little bit of it to optimize the scheduling and what sessions were in which rooms. As you talk to enterprises, it does seem like this stuff is being baked into real enterprise apps today. Can you talk a little bit about that? >> Sure, so I certainly can't give any specific examples, because what I think what you're saying is that a lot of enterprises or a lot of companies are looking at that like, "Oh, this is our new secret sauce." It always used to be like they had some interesting feature before, that a competitor would have to keep up with or catch up with. But I think they're looking at machine learning as a way to enhance that customer experience, so that it's a much more intimate experience. It feels much more tailored to whomever is using their product. And I think that you're seeing a lot of those types of things that people are starting to bake into their products. We've, again, this is one of these things where we've been using machine learning for almost 10 years inside Google. Things like for Gmail, even in the early days, like spam filtering, something just mundane like that. Or we even used it, turned it on in our data centers, 'cause it does a really good job of lowering the PUE, which is the power efficiency in data centers. And those are very mundane things. But we have a lot of experience with that. And we're exposing that through these products. And we're starting to see people, customers gravitate to grab onto those. Instead of having to hard code something that is a one to many kind of thing, I may get it right or I may have to tweak it over time, but I'm still kind of generalizing what the use cases are that my customers want to see, once they turn on machine learning inside their applications, it feels much more tailored to the customer's use cases. >> Machine learning as a service seems to be a big hot button that's coming out. How are you guys looking at the technical direction from the cloud within the enterprise? 'Cause you have three classes of enterprise. You have the early adopters, the power, front, cutting-edge. Then you have the fast followers, then you have everybody else. The everybody else and fast followers, they know about Kubernetes, some might not even, "What is Kubernetes?" So you have kind of-- >> Jonathan: "What containers?" >> A level of progress where people are. How are you guys looking at addressing those three areas, because you could blow them away with TensorFlow as a service. "Whoa, wowee, I'm just trying to get my storage LUNs "moving to a cloud operation system." There's different parts of this journey. Is there a technical direction that addresses these? What are you guys doing? >> So typically we'll work with those customers to help them chart the path through all those things, and making it easy for them to use and consume. Machine learning is still, unless you are a stats major or you're a math major, a lot of the algorithms and understanding linear algebra and things like that are still very complex topics. But then again, so is networking and BGP and things like OSPF back a few years ago. So technology always evolves, and the thing that you can do is you can just help pull people along the continuum there, by making it easy for them to use and to provide a lot of education. And so we work with customers on all ends of the spectrum. Even if it's just like, "How do I modernize my applications, "or how do I even just put them into the cloud?" We have teams that can help do that or can educate on that. If there are customers that are like, "I really want to go do something special "with maybe refactoring my applications. "I really want to get the Cloud Native experience." We help with that. And those customers that say, "I really want to find out this machine learning thing. "How can I actually make that an impactful portion of my company's portfolio?" We can certainly help with that. And there's no one, and typically you'll find in any large enterprise, because there'll be some people on each one of those camps. >> Yeah, and they'll also want to put their toe in the water here and there. The question I have for you guys is you got a lot of goodness going on. You're not trying to match Amazon speed for speed, feature for feature, you guys are picking your shots. That is core to Google, that's clear. Is there a use case or a set of building blocks that are highly adopted with you guys now, in that as Google gets out there and gets some penetration in the enterprise, what's the use, what are the key things you see with successes for you guys, out of the gate? Is there a basic building? Amazon's got EC2 and S3. What are you guys seeing as the core building blocks of Google Cloud, from a product standpoint, that's getting the most traction today? >> So I think we're seeing the same types of building blocks that the other cloud providers are, I think. Some of the differences is we look at security differently, because of, again, where we grew up. We do things like live migration of virtual machines, if you're using virtual machines, because we've had to do that internally. So I think there are some differences on just even some of the basic block and tackling type of things. But I do think that if you look at just moving to the cloud, in and of itself is not enough. That's a stepping stone. We truly believe that artificial intelligence and machine learning, Cloud Native style of applications, containers, things like service meshes, those things that reduce the operational burdens and improve the rate of new feature introduction, as well as the machine learning things, I think that that's what people tend to come to Google for. And we think that that's a lot of what people are going to stay with us for. >> I overheard a quote I want to get your reaction to. I wrote it down, it says, "I need to get away from VPNs and firewalls. "I need user and application layer security "with un-phishable access, otherwise I'm never safe." So this is kind of a user perspective or customer perspective. Also with cloud there's no perimeters, so you got phishing problems. Spear phishing's one big problem. Security, you mentioned that. And then another quote I had was, "Kubernetes is about running frameworks, "and it's about changing the way "applications are going to be built over time." That's where, I think, SRE and Istio is very interesting, and Kubeflow. This is a modern architecture for-- >> There's even KubeVirt out there, where you can run a VM inside a container, which is actually what we do internally too. So there's a lot of different ways to slice and dice. >> Yeah, how relevant is that, those concepts? Because are you hearing that as well on the customers? 'Cause that's pain point, but also the new modern software development's future way to do things. So there's pain point, I need some aspirin for that. And then I need some growth with the new applications being built and hiring talent. Is that consistent with how you guys see it? >> So which one should I tackle? So you're talking about. >> John Furrier: VPN, do the VPNs first. >> The VPNs first, okay. >> John Furrier: That's my favorite one. >> So one of the most, kind of to give you the backstory, so one of the most interesting things when I came to Google, having come from other large enterprise vendors before this, was there's no VPNs. We don't even have it on our laptop. They have this thing called BeyondCorp, which is essentially now productized as the Identity-Aware Proxy. Which is, it actually takes, we trust no one or nothing with anything. It's not the walled garden style of approach of firewall-type VPN security. What we do is, based upon the resource you're going to request access for, and are you on a trusted machine? So on one that corporate has given you? And do you have two-factor authentication that corporate, not only your, so what you have and what you know. And so they take all of those things into awareness. Is this the laptop that's registered to you? Do you have your two-factor authentication? Have you authenticated to it and it's a trusted platform? Boom, then I can gain access to the resources. But they will also look for things like if all of a sudden you were sitting here and I'm in San Francisco, but something from some country in Asia pops up with my credentials on it, they're going to slam the door shut, going, "There's no way that you can be in two places at one time." And so that's what the Identity-Aware Proxy or BeyondCorp does, kind of in a nutshell. And so we use that everywhere, internally, externally. And so that's one of the ways that we do security differently is without VPNs. And that's actually in front of a lot of the GCP technologies today, that you can actually leverage that. So I would say we take-- >> Just rethinking security. >> It's rethinking security, again, based upon a long history. And not only that, but what we use internally, from our corporate perspective. And now to get to the second question, yeah. >> Istio, Kubeflow, is more of the way software gets run. One quote from one of the ex-Googlers who left Google then went out to another company, she goes, she was blown away, "This is the way you people ship software?" Like she was a fish out of water. She was like, "Oh my god, where's Borg?" "We do Waterfall." So there's a new approach that opens doors between these, and people expect. That's this notion of Kubeflow and orchestration. So that's kind of a modern, it requires training and commitment. That's the upside. Fix the aspirin, so Identity Proxy, cool. Future of software development architecture. >> I think one of the strong things that you're going to see in software development is I think the days of people running it differently in development, and then sandbox and testing, QA, and then in prod, are over. They want to basically have that same experience, no matter where they are. They want to not have to do the crossing your fingers if it, remember, now it gets reddited or you got slash-dotted way back in the past and things would collapse. Those days of people being able to put up with those types of issues are over. And so I think that you're going to continue to see the development and the style of microservices, containers, orchestrated by something that can do auto scaling and healing, like Kubernetes. You're going to see them then start to use that base layer to add new capabilities on top, which is where we see Kubeflow, which is like, hey, how can I go put scalable machine learning on top of containers and on top of Kubernetes? And you even see, like I said, you see people saying, "Well, I don't really want to run "two different data planes and do the inception model. "If I can lay down a base layer "of Kubernetes and containers, then I can run "bare metal workloads against the bare metal. "If I need to launch a virtual machine, "I'll just launch that inside the container." And that's what KubeVirt's doing. So we're seeing a lot of this very interesting stuff pop. >> John Furrier: Yeah, creativity. >> Creativity. >> Great, talk about your role in the Office of the CTO. I know we got a couple of minutes left. I want to get out there, what is the role of the CTO? Bryan Stevens, formerly a Red Hat executive. >> Yeah, Bryan's our CTO. He used to run a big chunk of the engineering for Google Cloud, absolutely. >> And so what is the office's charter? You mentioned some CIOs, former CIOs are in there. Is it the think tank? Is it the command and control ivory tower? What's the role of the office? >> So I think a couple of years ago, Diane Greene and Bryan Stevens and other executives decided if we want to really understand what the enterprise needs from us, from a cloud perspective, we really need to have some people that have walked in those shoes, and they can't just be Diane or can't just be Bryan, who also had a big breadth of experience there. But two people can't do that for every customer for every product. And so they instituted the Office of the CTO. They tapped Will Grannis, again, had been in Boeing before, been in the military, and so tapped him to build this thing. And they went and they looked for people that had experience. Former VPs of Engineering, former CIOs. We have people from GE Oil and Gas, we have people from Boeing, we have people from Pixar. You name it, across each of the different verticals. Healthcare, we have those in the Office of the CTO. And about, probably, I think 25 to 30 of us now. I can't remember the exact numbers. And really, what our day to day life is like is working significantly with the product managers and the engineering teams to help facilitate more and more enterprise-focused engineering into the products. And then working with enterprise customers, kind of the big enterprise customers that we want to see successful, and helping drive their success as they consume Google Cloud. So being the conduit, directly into engineering. >> So in market with customers, big, known customers, getting requirements, helping facilitate product management function as well. >> Yeah, and from an engineering perspective. So we actually sit in the engineering organization. >> John Furrier: Making sure you're making the good bets. >> Jonathan: Yes, exactly. >> Great, well thanks for coming on The Cube. Thanks for sharing the insight. >> Jonathan: Thanks for having me again. >> Great to have you on, great insight, again. Google, always great technology, great enterprise mojo going on right now. Of course, The Cube will be at Google Next this July, so we'll be having live coverage from Google Next here in San Francisco at that time. Thanks for coming on, Jonathan. Really appreciate it, looking forward to more coverage. Stay with us for more of day three, as we start to wrap up our live coverage of Red Hat Summit 2018. We'll be back after this short break. (upbeat electronic music)

>> Narrator: Live from San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> And welcome back once again to theCUBE. We're here live and open in this open-source conference, Red Hat Summit 2018 here in Moscone Center in San Francisco. My name's John Troyer. We are coming close to the end of the day three of Red Hat Summit. Been here, catching all the live coverage on theCUBE.net. Great to have with us: our two guests here from UPS, Innovation Award winners here at the show, gentlemen, welcome. >> Thank you. >> Thank you. >> Mark Falto and Dan Savarese. So, welcome folks. So, we're going to talk about your journey to using OpenShift, how you guys picked it, what you guys stood up, and as we were just kind of, I saw the on-stage story, and as I was just talking to you now before we went live, I'm just so impressed by the time to market, time to value, that you guys were able to achieve. You and your teams. Which, if you think about it is really, the fact that this is a real story, and it's not just a marketing example is really great. We're living, and sometimes I wake up and I say we're living in wonderful times in 2018. So, Dan, kind of set the stage for us. You are a principal infrastructure architect, you're one of the folks that helped bring the system in, you were already Red Hat Linux ... >> Yes we were. >> ... users, but what were you looking at as you were trying to make this decision, and what were some of the drivers to bring OpenShift in-house? >> Well, we knew we wanted to go cloud, but we weren't sure whether it was public or private, so we felt that in order to start the transformation to cloud we should really focus on private. These boundaries to get that up and running, and a way to modernize our applications to be cloud ready. So that was the goal when we set this up. We had a very tight timeline, we had applications that wanted to go cloud, so we made the decision... >> Mark Falto: (mumbles) was knocking at the door. >> Everybody was knocking at the door. Right, so it was a matter of just what did we want to do? Like anything, we viewed a number of different private cloud solutions, and we really liked OpenShift because of it's flexibility, it's open-source capabilities, and the fact that it was... docket containers, which was our container strategy going forward, which we wanted to use. >> Was this the beginning of your container strategy? Had you been using them before? >> No, we hadn't been using them before. We just made the decision, prior to making the cloud decision, that we wanted to go containers and docket with the containers that we wanted to use. >> So, you some sort of evaluation, you say you know, this seems like something worth happening. In the olden days, we'd go off and you'd do some sort of POC, and you'd spend a couple months doing that, and then you'd look at it, and what are the toy projects? >> Dan Savarese: Right, yeah. >> You guys wanted to actions, so can you talk a little bit about that and the timeline there? >> Right, so we made the decision in late fall 2016 to do this. My team runs all the infrastructure, architecture, so we work with the applications to design new architectures for them, and basically we started working with Red Hat on success criteria that we established for the product, and then once we got through that we started having sessions with Red Hat and using collaborative dev ops approach with everybody in your organization who'd be affected by this private cloud we're putting in. So Mark, our info sec folks, our networking folks. We were on a very tight timeline, we had an application wanting to go quickly as possible, and they wanted to be up and running in like the late spring, early summer timeframe, so they didn't give us much time. So, a lot of work and effort into figuring out how we wanted our architects OpenShift for, not only to be operationally successful for us, but from an application perspective. So, it was important we do this in a collaborative manner, and get everybody's input in doing that. >> Yeah, that's something that's going to be interesting to dip into, right, because you can't just turn on speed like that. As I've been kind of jokingly referring to, right, you have to turn into kind of a dev ops in an agile organization. Even at the infrastructure layer. >> [Dan Savarese} Yep. >> So, Mark, within a few months you've got OpenShift up and running. Now you've got to put some apps on it. These are not new apps. You have all your existing portfolios still having to run, but so, yeah, what were you looking at putting up there, and how did you approach that in terms of native practice. >> Our strategy was to take new applications. We're trying to find app teams that we thought had at least a sophisticated enough process that they could take on the automation that we really wanted to drive with the platform as well, right? It was not just containerization, but the transformation in dev process that came with that. So it's get a pipeline in place. Understand how to use Jenkins, how to use the plugins that are necessary to make that happen. You need the right app teams that are ready to take that on. We had an example application as part of our edge initiative called Sipe, which that team we thought was ready to take this on, it was the only way we were really going to meet their timelines, too. So we worked with them for a number of weeks, and not just us, but we also had Red Hat partners helping us too, to freely build out the automation for the pipelines, get an example running for their complete automated pipeline. >> Right, so can you describe a little bit what it does? It's a business line app to help managers do some decision making and planning. >> Yeah, it's a decision assistance application for supervisors at hub facilities where, you know, where you move packages. >> Okay, so real business impact. Before, they had, I don't know what they were... Either papers, or... >> Most of it was manual processes, and it wasn't like the speed to market. The information wasn't real-time, so Sipe was all about driving real-time decisions in the field. >> Right, right, so it must have had an immediate impact, then. So, it sounds like you were up, and then also within a few months of it. >> Yes. Yeah, yeah. I mean, we're able to get at least a pipeline going within weeks for them, and that demonstrates the capacity to get yourself to production, right? And then, they're in production within a number of months after that. A couple of months after that. >> Yeah, that's great, and I'm assuming you'd then be able to revise it and kind of improve the functionality since. That and some other apps. >> Mark Falto: Yep, yep, yeah. >> Was that a big shift for you and your developers, to kind of get to this stance, of frequent releases and a pipeline? >> Yeah, it's a huge process shift, it's a cultural shift for app teams, they have more capability from the infrastructure than they have ever had before. So, they now have tools to deliver much faster than they're used to, so they change their team structures to help us facilitate that. They bring in Red Hat or other consultants to help them backfill their skillsets, so it's big transformation, yeah. >> Nice, nice. Now, I wanted to explore a little bit. One word you hear a lot here: hybrid cloud, multi cloud, we've been hearing that a lot this week. This particular app runs on Prem, right? >> Dan Savarese: Runs on Prem, yes. >> Let's make sure we it right, on PremiSys. >> Dan Savarese: On PremiSys, right. It runs actually, between today at the centers. >> Yeah, I'll get extra bonus points for that. But, as a portfolio that you have to manage, your IT department and infrastructure, UPS does take advantage of different clouds and different code running and different places, as well as sas and everything else, I'm sure. Can you talk a little bit about to portfolio? >> Sure, so we have a wide variety, as companies as large as UPS, you can imagine we have a lot of IT solutions. We leverage all of them to our benefits, so we have past solutions in the cloud, a lot of analytic stuff that we'll do out there, and we also have a lot of sas solutions that we use to do different various works across our organization. So, we are using cloud in multiple ways. Out next journey is hybrid cloud. How do we take OpenShift now, 'cause what we have is a situation where we need a lot of processing power for what we call out peak season, Christmas of course, right, but when we size today on OnPrem we size for that peak season. So, the challenge is for us now is how can we use OnPrem for, say, nine months out of the year, then expand into the cloud for peak season, reduce cost, and then drop that down after we're done with peak season? To really drive us really efficiently from across the spectrum. >> Right, right, right, and obviously OpenShift is going to be a probably key element to that. >> Dan Savarese: It is a key element. It is a key element. >> Yeah. You know, this only took a, this journey was, if you just look at the timeline we just talked about, really only a few months, and it seems like this was kind of a corner-turn for your engineering organization. I mean, is that inaccurate? >> I would say so, both from an infrastructure perspective, the biggest thing when you run a common environment, which we do in OpenShift, in other common environments you have no control over how the applications affect one another. For us, what we like about OpenShift, it gives us that capability, so application 'A' doesn't step on application 'B'. And, I think, for us, it just made our lives a lot easier from an operational perspective for that reason. >> Right, it wasn't about the tool, but the tool helped enable the processes, and then that yielded the time to market and time to value. >> Yeah, and from an app side, building these new architectures really requires containerization. It requires the automations, so we can't attack the proper microservice patterns and practices really without OpenShift as a platform underneath it. It's foundational. >> And I'd like to stress the fact that it really was all of us knew we had to get something done. We all came together. There was no... The silos were merely broken down. We knew we had a mission to get through, we knew had something to get done in a short period of time, and we just came together in such a strong, collaborative way of driving the solution. >> Wow, that's great, and congratulations. Innovation Award here at the show, it's been a great week here at Red Hat Summit. So, Mark Falto, Dan Savarese from UPS. Congrats, and thanks for being here on theCube. >> Well, thank you John. >> All right. Well we are here live in San Francisco. We are finishing up day three. We'll be back after a short break, and all of our live coverage of Red Hat Summit on theCube. (light percussive music)

>> Narrator: Live from San Francisco, it's theCUBE! Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hello and welcome back to theCUBE's exclusive coverage here in live in San Francisco, California, for Red Hat Summit 2018. I'm John Furrier, with John Troyer my co-host analyst this week he's the co-founder of TechReckoning Avisory Community Development Firm, of course I'm the co-host of theCUBE, and this is Harry Mower, Senior Director of Red Hat Developer Group within Red Hat. He handles all the outward community work, also making sure everyone's up to speed, educated, has all the tools. Of course, thanks for coming and joining on theCUBE today. Appreciate you coming on. >> Thanks for having me again. >> Obviously developer community is your customers. They're your users, Open Source is winning. Everything's done out in the open. That's your job, is to bring, funnel things and goods to the community. >> Harry: Yes. >> Take a minute to explain, what you do and what's going on with your role in the community for the Red Hat customers. >> Sure, so my group really handles three things. It's developer tools, our developer program, and the evangelism work that we do. So if I kind of start from the evangelism work, we've got a great group of evangelists who go out, around the world, kind of spreading the Gospel of Red Hat, so to speak, and they talk a lot about the things that are about to come in the portfolio, specific to developer platforms and tools. Then we try to get them into the program, which gives the developers access to the products that we have today, and information that they need to be successful with them. So it's very much about enterprise developers getting easy access to download and install, and get to Hello World as fast as possible, right? And then we also build tools that are tailored to our platform, so that developers can be successful writing the code once they download-- >> John F: And the goal is ultimately, get more people coding, with Linux, with Red Hat, with Open Source. >> Harry: Yep, it's driving more of, I mean from inwardly facing it's driving more adoption of our products but you know, outward, as the developer being our customer, it's really to make them successful and when I took over this role it was one of the things we needed to do was really focus on who the developer was, you know, there's a lot of different types of developers, and we really do focus on the nine to five developer that works within all of our customers' organizations, right? And predominately those that are doing enterprise jobs are for the most part, but we're starting to branch out with that, but it's really those nine to five developers that we're targeting. >> Got to be exciting for you now because we were just in Copenhagen last week for CubeCon with Kubernetes, you know, front and center, we're super excited about that's defacto formation around Kubernetes, the role of containers that's going on there, really kind of give kind of a fresh view, and a clear view, for the developer, your customer, where things are sitting. So how do you guys take that momentum and drive that home, because that's getting a lot of people excited, and also clarifying kind of what's going on. If you're under the hood, you got some Open Stack, if you're a developer, app develop you've got this, and then you've got orchestration here and you got containers. Kind of the perfect storm, for you guys. >> Harry: Yeah and what we've been trying to distribute in the container space, so one of the things we do we have these kind of 10 big bets that we put on a wall that really drive our product decisions, right? And one of the first, maybe the second one we put on the wall was, everything will be in containers, right? And so we knew that it was important for developers to be able to use containers really easily, but we also knew that it's an implementation detail for them. It's not something that they really need to learn a lot about, but they need to be able to use, so we made an acquisition last year, Code Envy was the company, driving force behind Eclipse J, one of the great features of Eclipse J, a lot of people see it as a web based IDE, but it's also a workspace management system, that allows developers' development environments to be automatically containerized, hosted and run on Open Shift at scale, right? And when we show the demo it's really interesting because people see us coding in a browser and "Oh that's pretty neat", and then at the end of it everyone starts to ask questions about the browser part, and I say, "Yeah, but did you notice we never typed a docker command, never had to learn about a Kubernetes file, it was always containerized right from the very beginning, and now your developers are in that world without having to really learn it". And so that's really a big big thing that we're trying to do with our tools, as we move from classic Eclipse on the desktop to these new web based. >> So simplifying but also reducing things that they normally had to do before. >> Yeah. >> Using steps to kind of. >> Yeah, we want to, people don't like when I say it, I don't want to try make them disappear into the background but what I mean is it's simple and easy to use. We take care of the creative room. >> Now is that, that's OpenShift.io? Is that where people get started with that? >> Actually Eclipse J. >> Okay, Eclipse J, okay. >> So it starts in Eclipse J, and then we take that technology and bring it into io as well. >> Gotcha gotcha, can you take a little bit about io then? You know, the experience there, and what people are doing. >> Sure, yeah so io is a concept product that we released last, well we announced last year at Summit. It's really our vision of what an end to end cloud tooling platform is going to look like. Our bet is that, many of our customers today take a lot of time to customize their integrated tool chains, because of necessity, because someone doesn't offer the fully integrated seamless one today. Many of our customers like their little snowflakes that they built, but I believe over time, that the cost of maintaining that will become something that they're not going to like, and that's one of the reasons why we built something like io. It's hosted managed by us, and integrated. >> And what are people using it for? Is this for prototyping, is this, what are people doing on the system? >> Today it's mostly for prototyping, one of the things we did here at this week's Summit is we announced kind of a general availability for Java developer using public repose. Up until this point it's always kind of been experimental. You weren't sure if your data was going to be gone if it was up or down, there's much more stability and kind of a more reliable SLA right now for those types of projects. >> John T: Gotcha, gotcha. Well, I mean, pivoting maybe to the overall developer program, so developers.redhat.com, big announcement yesterday, you reached a million members, congratulations. >> Harry: Thank you very, yeah, thanks a million is what I put in my tweet. It's been a really great journey, I started it three years ago, we consolidated a number of the smaller programs together, so we had a base of about two, 300 ish developers, and we've accelerated that adoption, now we're over a million and growing fast, so it's great. >> What's the priorities as you go on? I mean all of these new tools out there and I was just talking with someone, one of your partners here, we were out at a beer thing last night, got talking and like waterfall's dying in software development but Open Source ethos is going into other areas. Marketing, and so the DevOps concepts are actually being applied to other things. So how are you taking that outreach to the community, so as you take the new Gospel, what techniques do you use? I mean, you're tweeting away, you going in with blogging, content marketing, how are you engaging the content, how are you getting it out in digital? >> Our key thing is the demo, right? So you saw a lot of great demos on stage this week, Burr Sutter on our team did a phenomenal job every day with a set of demos, and we take those demos, those are part of the things we bring to all the other conferences as well, they become the center stage for that, because it's kind of the proof of concept, right? It's the proof of what can be possible, and then we start to build around that. And it helps us show it's possible, it actually helps get our product teams coelest around our idea, they start to build better products, we bring that to customers, and then customer engagement starts early, but that's the key of it. >> I mean demos the ultimate content piece, right? >> It forces everybody to, on the scene-- >> Real demo, not a fake demo. >> And those were all real, that's the thing the demos are so good I think some of them people thought they were fake. I'm like Burr you didn't do a good enough job of like pulling the plug faster, and showing it was real, right? But they're, yes, they're absolutely real demos, real technology working, and that creates a lot of momentum around. >> You guys see any demographics shifts in the developers, obviously there's a new wave of developers coming in, younger certainly, right? You get the older developers that know systems, so you're seeing coexistence of different demographics. Old and young, kind of playing together. >> Yeah, so there's a full spectrum of ages, a full spectrum of diversity, and geography, I mean, it's obvious to everybody that our growing markets are Asia, it's India and China right now. You'll see, you know, Chinese New Year we see a dip in usage in our tools, you know, it's very much, that's where the growth is. Our base right now is still predominately North America and EMIA, but all the growth is obviously Asian and-- >> John T: (mumbles). Harry I wanted to talk about the role of the developer advocate a little bit. It's a relatively new role in the ecosystem, not everybody understands it, I think some companies use a title like that in very different ways, can you talk, it's so important, this peer to peer learning, you know, putting a human face on the company, especially for a company like Red Hat, right? Built from Open Source communities from the ground up. Can you talk a little bit about what is a developer advocate, and am I even getting the title right? But what do they do here at Red Hat? >> Yeah so it's funny, so an evangelist is an advocate, and how do you distinguish the difference? So I spend a lot of time at Microsoft, you know, I think they pioneered a lot of that a long time ago, 10 or 12 years ago, really started doing that, and those ideas have matured, many different philosophies of how you do it. I bring a philosophy here and at work and with Burr, that, you know, it's one thing to preach the Gospel, but the end goal is to get them into Church, right? And eventually get them to, you know, donate, right? So, our evangelists are really out there to convince and you know, get them to adopt. Other models where you're an advocate, it's about funneling, it's almost like a marketing, inbound marketing kind of role, where you're taking feedback from the developers and helping to reshape the product. We do a little bit of that, but it's mostly about understanding what Red Hat has, 'cause when people look at Red Hat they think that's the Linux I used to use, I started in college, right? And for us we're trying to transform that view. >> John F: Huge scope now. >> And that's why we're more of an evangelistic organization. >> I mean Linux falls in the background I mean with cloud. Linux, isn't that what the old people used to like install? Like, it's native now. So again, new opportunities. And Open Shift is a big part of that. >> Yeah and we work hand in hand, there's actually an Open Shift evangelism team that we work hand in hand with, and their job is really more of a workshop style engagement, and get the excitement, bring them to that, and then do the engagements and bring it in. >> John F: What's the bumper sticker to developers? I mean obviously developer's mind sheer is critical. So they got to see the pitch of Linux helps a lot, it's all about the OS, what's the main value proposition to the developers that you guys are trying to have front and center the whole time? >> Harry: For Red Hat specific? >> Yeah yeah. >> It's funny, we just redid all of our marketing about the program, and specifically it's build here, go anywhere. And for two levels, right? With using Red Hat technologies, being part of the Open Source community, you can take those skills and knowledge and go anywhere in your career, right? But also with our technology, you can take that, and you can run it anywhere as well. You can take that technology and run it roll on prem, run it on someone else's cloud, and it really is just, we, you know, we really give the developers a lot of options and possibilities, and when you learn our products and use our products, you can really go anywhere. >> So Harry there's a, I loved how you distinguished at the very beginning of the conversation who the program is for, and that particular role, right? I sit down and I code enterprise products and glue stuff together and build new things, bring new functionality to the market, shit, excuse me, this week has been all about speed to market, right? And that's the developers out there, right? See I get so excited about it. >> That's okay, you can swear. >> (mumbles) >> But you know, there's a lot of shifting roles in IT, and the tech industry, over the last, say, decade or so, you know, do we spec the people who we used to call system mins, do they have to become developers? Open Source contributors also are developers. But it sounds like maybe the roles are clarifying a little bit, other than, you know, an Open Shift operator, you know, doesn't have to be a developer, but does have to be, know about APIs and things, how are you looking at it? >> I don't have too strong an opinion on this, but when I talk to other people and we kind of talk about it, you know the role of the, so we made operations easy enough that developers can do a lot of it, but they can't do all of it, right? And there's still a need for operations people out there, and those roles are a lot around being almost automation developers. Things that you do like an (mumbles) playbook or, you know, what other technology might use, so there is an element of operations people having to start to learn how to do some sort of coding, but it's not the same type of that a normal developer will do. So somehow we're meeting in the middle a little bit. But, I'm so focused on the developer part that I really don't have too strong an opinion. >> Well let us know how we can help, we love your mission, theCUBE is an open community brand, we love to get any kind of content, let us know when your big events are, I certainly want to promote it sir. Open Source is one, it's winning, it's changing and you're starting to see commercialization happen in a nice way, where projects are preserved upstream, people are making great products out of it, so a great opportunity for careers. And building great stuff, I mean new application start-ups, it's all over the place so it's great stuff, so congratulations and thanks for coming on theCUBE. It's theCUBE, out in the open here in the middle of the floor at Moscone West, bringing all the covers from Red Hat Summit 2018. We'll be right back with more after this short break, I'm John Furrier, with John Troyer, we'll be right back. (electronic music)

>> Announcer: Live from San Francisco, it's theCUBE, covering Red Hat SUMMIT 2018, brought to you by Red Hat. >> Okay welcome back everyone. We are here live in San Francisco at Moscone West. This is theCube's exclusive coverage of Red Hat SUMMIT 2018. I'm John Furrier, co-host of theCube. This week John Troyer, guest analyst, he's the co-founder of TechReckoning, an advisory and consulting firm around community. Our next guest Matt Hicks, Senior Vice President of Engineering at Red Hat. He's going to give us all the features, and specs of the road map, and all the priorities. Thanks for coming on. >> Hey, thanks guys. >> John: He's like, "I'm not." >> So thanks for comin' on, obviously a successful show for you guys, congratulations. >> Matt: Thank you Paul Cormier was on earlier talking about some of the bets you guys made and it's all open source, so those bets are all part of the community, with the community. But certainly there's a big shift happening, we're seeing it now with containers, and Kubernetes really showing the way, giving customers clear line of sight of where things are startin' to fall in the stack. Obviously you got infrastructure and application development all under a DevOps kind of concept, so congratulations. >> Thank you, thank you, it's been fun, it's been, I think Paul shared this a couple weeks, we started OpenShift in 2011, so it's pretty cool to be here now, 2018, and just see how far that's come in terms of how many customers using it, how successful they've been with it. So that's, it's been great. >> Yeah we always like to talk on theCube, we love talkin' to product people and engineers because we always say the cloud is like an operating system. It's just all over the place, decentralized network, distributing computing, these are concepts that have been around. A lot of the Red Hat DNA comes from systems, you have SELinux operating system, that you offer for free but also have services around it. It's a systems problem as we look at the cloud, cloud economics. So when you go look at some of the product and engineering priorities, how do you guys keep that goin'? What are some of the guiding principles that you guys have with your team? Obviously open-source, being in up-stream projects, but as you guys have to build this out in realtime, what are some of the principles that you guys have? >> That's a great, that's a great question. I'll try to cover it on two areas. I think the first for us is workload compatibility, where you get down into the, building that new apps is great, it's fun, a lot of people can do it, and that's an exciting area. The customers also, they have to deal with apps they built over 10 plus years, and so in everything we design, we try to make sure we can address both of those use cases. I think that's one of the reasons, yeah we talk about OpenShift and how coupled it is to RHEL and Linux. It's for that you can take anything that runs on RHEL, run it in a container on OpenShift, stateful, not stateful. That's one really key design principle. The other one, and this we've actually experienced ourselves, of the roles and responsibilities separation. We run an OpenShift host environment publicly, I joke, like anyone that gives me an email address, I'll run their code and my operations team doesn't have to know what's inside of the containers. They have a really clear boundary which is make the infrastructure infinitely available for them, and know that you can run anything on that environment. So that separation, you know when customers talk about DevOps, and getting to agile, I think that's almost as critical as the technology itself, is letting them be able to do that. >> Yeah, that's been a real theme here at the show, I've certainly noticed. Sure there were technology demos up on stage, but also a lot of talk about culture, about process or anti-planning maybe, or you know helping people. The role of Red Hat with OpenShift and the full stack all the way down is bigger now than it was, just when it was just Linux. So I mean, is it you and your team, I mean your in engineering as you work with the open source communities, surely it seems like you're having to deal with a much broader scope of responsibilities. >> Yeah, that's true. I started in Red Hat when it was just Linux and part of it is, you know Linux is big, and it's complex, and that in and of itself is a pretty broad community. But these days it is, we get to work with customers that are transforming their business and that touches everything from how they're organizationally structured, how we make teams work together, how I make the developers happy with their rate of innovation and the security team still comfortable with what they're changing. I love it, like it is, you know and we open source at our core, so I fell like, I'm an open source guy. I always have been. You're seeing open source drive a much wider scope of change then I ever have before. >> Let's talk about functionality product-wise, 'cause again we interviewed Jim Whitehurst yesterday and we had Denise Dumas on as well, on the RHEL side, and we talked about security. These things going on, and with OpenShift, and with Kubernetes, and containers, it makes your job harder. You got to do more right? So talk about what does that mean for you guys and how does that translate to the customer impact because it's more complicated. There's abstraction layers that are abstracting away the complexity. The complexity is not going away, it's just being abstracted away. This is harder on engineering. How are you handling that and what's your approach? >> So I've looked at it as a great opportunity for us. I've been working with Linux for a long time and I was a big fan when we introduced SELinux, and for a long time moving from traditional Linux hosting to operations teams wanting to turn on SELinux, it's been a really tough climb. It's, it'll break things, and they're not comfortable with it. They know they need that layer of security, but turning it on has been a challenge. Then go to cgroups, or different namespaces, and they're not going to get there. With OpenShift, the vast majority of OpenShift deployments, under the covers we run with SELinux on by default, customize policies, everything's in control groups, containers uses Linux namespaces. So you get a level of workload isolation that it was unimaginable you know five, 10 years ago, and I love that aspect, 'cause you start with one aspect of security, you get much, much stronger. So it's our ability to, you know we know all the levers and knobs in Linux itself, and we get to turn 'em all and pull 'em all so, >> I want to put you on the spot, I want to, and it's not an insult to you guys at all. But we've heard some hallway conversations. You know just in a joking way 'cause everyone loves Linux, open source, we all love that. But they say, nothings perfect either. No software actually runs all the time great. So one customer said, I won't say the name, "When OpenShift fails, it fails big." Meaning there's, it's very reliable but it's taking on a lot of heaving lifting. There's a lot of things going on in there, 'cause that's, 'cause it's Linux, when it breaks, it breaks a lot, and I know you're tryin' to avoid that. But my point is, is that just as these are important components. How do you make that completely bullet proof? How do you guys stay on top of it so that thinks don't break? I'm not saying they do all the time. I'm just saying it's common. It was more an order of magnitude kind of thing. >> Yeah, yeah, no, well I think it's a coupla things. So we invested in OpenShift Online and OpenShift Dedicated and those were new for Red Hat, and for running hosting environments, so we could learn a lot of the nuances of how do you, OpenShift Online is roughly a single environment, how do we make that never break as a whole. A user might do something in their app and make their app break. How do we not make the whole break? The second challenge I think we've hit is just skills in the market of it's not necessarily an easy system there are lots of moving pieces there. The deal with Azure and the partnership there, having managed service offerings I think is really going to help users get into, I have a highly available environment, I don't have to worry about SED replication or those components but I can still get the benefits. And then I think over time as people learn the technology, they know how to utilize it well, we'll see, we'll see less and less of the it catastrophically failed because I didn't know that I could make it highly available. Those are always painful to me, where it's you know, >> John: That's education. >> Yeah >> So Matt, there's a clear conversation here. Very clarity of roles and responsibilities even in the stack. I think even as recently as a year or two ago, people were having conversations about the role of OpenStack, versus Kubernetes, and you were getting kind of weird, like what's on top of what? And even in terms of, you know other parts of the stack, I mean here it's clear, very clear, you know OpenStack is about infrastructure, OpenShift you know on top of it, and even in terms of virtualization, containers versus VMs. The conversation this year seems more clear. As an engineer, you know and an engineering leader, were the, did the engineering teams rolling their eyes going well we knew how this was going to work out all along, or did you all also kind of come along on that journey the last couple years? >> I think seeing the customer use cases refined a little bit while education builds those has been great. We always, like we're engineers, we like clear separation and what each products good at, so for us it's fantastic. You know OpenStack is great at managing metal. One of my favorite demonstrations was using OpenStack Director to on a, you know boot machines, put OSs on 'em, and leave OpenShift running, and be able to share network and storage clients with OpenStack. Those things are, you know they're great for me as an engineering lead because we're doing that once as well as we can, but it's nice in engineering if you get to optimize each side of the stack. So I think I have seen the customers understanding, as they've done more with OpenStack, and they've done more with OpenShift, they know which product they want to use, what for. That has helped us accelerate the engineering work towards it. >> You mention skills, skills gaps, and skills in general. How is the hiring going? Is there a new kind of DevOps rockstar out there? Is there a new kind of profile? Is there pieces of the stack that you want certain skills for? Is there generalism? Are the roles in engineering changing? If you could just add some color to that conversation around, you know cause we're talkin' about engineering now. It used to be called software engineering when I graduated, and then you became a developer. I don't know which ones better, but you know to me this is real engineering going on, which is using software development techniques. So what's the skills situation? >> For us I think, it is nice that you're seeing a lot of gravitation to Linux at the host level, and Kubernetes has helped, just at the distributed system level, so obviously skills there play pretty well in general. I would say what we have seen is there has been a stronger increase in having operational skills as well as development skills, and it's a spectrum. You're still going to have operational experts and algorithmic experts, but the blended role where you do know what it takes to run an application in production to some extent, or you do know something about infrastructure and development. I certainly look for that on our teams because that's, where customers I've seen struggle for years and years is in the handoff in the shift between, everyone can write functional apps, they usually struggle getting them into production. And it's really neither teams fault, it's in that translation and these platforms help bridge that. People that have some skills on either side have become incredibly valuable in that. >> John: So that's were the DevOps action is right, the overlay. >> It really is yeah. >> So thinking about network as the networking growth with DevOps. DevOps has always been infrastructure as code. And it all comes to, there's to many, many, I don't want to talk about it. It's always the network that gets beat on the most, I need better latency. And so networking software to find networking is not a new concept, self-defined data centers are out there. What's new in networking that you could point to that's part of this new wave? >> Two geeky things that might not have been noticed. One is the work we've done on Ansible networking has been stunningly popular to me, and that was just this simplicity of Ansible just needs us to sage in a minimal set of dependencies. Most switches out there can actually, they have SSH running, and having automation of switches in the actual gear itself was surprisingly not unified. And Ansible was able to fit that niche where you could remotely configure switches and that has grown and exploded. Because if you think of the, I'm going to do a DevOps workflow but now I need to actually change routing or bleed something, you're often talking to switches, and being able to couple that in has been, it has been fun to watch, so I've loved that aspect. The other portion when we combine OpenShift on OpenStack the courier work which we've talked about some, is, you know OpenShift often described as it consumes infrastructure that OpenStack provides, and the one exception was usually the networking tier. It was like we have to run an overlay network on it. When we run OpenShift on OpenStack it can actually utilize OpenStack's networking to be able to try that instead of doing it's own overlay. That is critical at the larger scale. >> John: So the policy comes in handy there is that, or configurations, where's the benefit? >> Both on network topology, which do you have two teams that are building different structures that may collide in the night. So it gets it from two teams down to one, and then the second is just the knock controls in isolation, it's done once. It's been nice for me on the engineering side where we'd put a ton of effort in the OpenStack community, we put a ton of effort in Kubernetes and the OpenShift communities, and we're able to pretty nicely combine those. We know 'em both really well. >> So take us through some inside baseball at Red Hat. What's going on internally within' your group. I want to probe on developer and software engineers productivity. If the quote DevOps works, the test is the freeing up their time from doing mundane tasks, and you got cool things like you said about the network things, pretty positive. This is going to free up some intellectual capital from engineering. So okay if that's true, I'm assuming it's true, if it's not then say it's not true, but it sounds like it's probably going to be true for you. What are your guys working on, what's next? So can you share some of what, 'cause you guys are doing your own thing, you're using your own software. Is that intellectual capital being freed up on the developers side? Are they doing some more programming? Are you seeing some more creativity? What are they doing with that free time, free time, extra intellectual cycles? >> All our excesses, I'll tell Paul that. He was up before me. Like, Ops team barely has to work anymore. >> There in there clipping coupons at the beach you know. It's all running, we're busy. >> So a good creative example, and this was I think the second demo we showed. Red Hat Insights has been in the market for a while and that was our, can we glean enough information from systems to get ahead of a support issue, and this year we showed the, it's not just known fixes, you know we match it to a knowledgebase article. But can we interpret fixes from peer analysis and you know machine learning type techniques? That's a classic example where we use the creativity and free time, and say you know what that stack internally runs on OpenShift, running on OpenStack, using Red Hat storage, and we're applying some of, you know TensorFlow and other capabilities to do that. That was probably my favorite example at SUMMIT where if we weren't getting more efficient at what we worked on, we wouldn't of been able to stand up that stack ourselves, much less execute to it, and show it live in SUMMIT, doing the analysis across a hybrid cloud. >> But this is the whole point of DevOps. This the whole purpose, being highly productive, to use those intellectual cycle times to build stuff, solve problems. >> Yeah absolutely. >> Not provision servers or networks. Awesome, well thanks for coming on theCUBE, really appreciate it. >> Matt: Thank you guys. >> What's the priorities for you guys this year? What's the focus? Share your plans for the year. >> You know I think it's similar to the last thing we showed today. We really want to make customers feel like they can deploy hybrid cloud. Whether it's compute, applications, they have the services they need, down to storage, it works. They're on premise. They know we're going to have the best combination we can. This year is a stay ahead of people on that path, make sure their successful with it. >> We'll see you guys at OpenStack SUMMIT, Vancouver. Thanks for comin' on, Matt Hicks, Senior Vice-President of Engineering at Red Hat. I'm John Furrier, John Troyer, Stay with us, we're day three of three days of live coverage here in San Francisco, Red Hat SUMMIT 2018. Stay with us, we'll be right back after this short break. (digital music)

>> Announcer: Live from San Francisco, it's theCUBE, covering Red Had SUMMIT 2018, brought to you by Red Hat. >> Hello everyone, welcome back. This is theCUBE's exclusive live coverage here in San Francisco at Red Hat SUMMIT 2018. I'm John Furrier with my co-host John Troyer. Our next guest is Arkady Kanevsky, Ph.D, Director Software Development at Dell EMC, Service Provider Business Unit. Thanks for joining us, thanks for coming on. >> Thank you for having me here. >> So we were just talking before we came on, obviously great, we're in the middle of the open here in the hall, in Moscone West. But you guys have a definition of service providers. It's very broad. It's obviously Dell EMC, you guys, Dell's tons of equipment that they sell, providing a lot of the equipment What does that, just take a quick second to describe who you guys are targeting, and your role here at Red Hat SUMMIT? >> Sure so we are a small portion within the Dell EMC portfolio and the organization I am in specifically creating a target and a solution for service providers. The service provider, you know the probably best known service providers are telecommunication service providers, AT&T, Verizon, Telestrom, you know all over the world. Very highly regulated areas, and have been around forever, and they are going through the major transformation right now from the 4G to 5G, network age, and so on. But we are also covering the much larger set of the providers. If you can think of the hosted service provider, managed service providers, those are the people who either have as a core of their business, providing the services for their customers. If you can think of the eBay, or Amazon, or Google, they have the services which are, they're running public cloud or not a public cloud for general sense, but for specific purpose which they're delivering, SalesForce, >> Yeah everyone's a service provider. If they're using cloud, they're some sort of service provider right? >> If they're delivering they're volume through the service, then they are the service providers. If you are, you know you have the businesses which are still doing the business the way they were doing before. Banks are not really service providers. They are not them, and yes they communicate with their customers through the portals, but that's not the purpose of their business. >> It's great now in 2018, we are gettin' some clarity on cloud right. We thought maybe it was all into public, now we see that actually there's a lot of use cases for smaller public clouds, hybrid clouds, private clouds depending on peoples needs. I'm curious how the service provider world, specifically like the MSBs, and the telcos of the world, are looking at how, what kinds of clouds they're going to provide, and maybe also how they partner with the bigger clouds. >> So there is a different angle there. So people, a lot of the work being done in a public cloud, initially when they try to do the development of their new application because it's the easiest way for them to do it, but once you hit the next level and you need to deliver it as a service in a special and more regulated environment, where we have certain strict security requirement. You want to protect access to the data. A lot of the time they kind of do the hybrid, go on the hybrid model because it's much more, they have better control of what they're doing. I mean some of the announcement and some of the demos, we showed that today in the keynote today and two days ago, we're clearly demonstrating this kind of approach. So we are partnering with Red Hat over developing the optimized platforms for the development and operation of those applications. All the way from RHEL Linux layer all the way up to OpenShift and beyond? >> All the way, we announced on Monday that we have our seventh joint version of Red Hat OpenStack already bundled. This is the first one where we start providing the workload optimized host, such that customer can choose to optimize from the hardware, to the operating system, to the OpenStack for their specific workload. We have a profile, pre-defined profile for NFE and we have a pre-defined profile for web based application, and of course it's open sourced, and extendible, flexible, and provide what customer expecting for their own use cases. >> How 'about the relationship between Dell, now Dell EMC, now Dell Technologies, and a variety of other things, the relationship with Red Hat. How long, how many years, how deep? How would you describe the relationship time-wise, and just duration, and depth? >> Very happy to, so we start our relationship 18 years ago, in 2001 was the first release of the laptops and the servers with a pre-installed program that on the factory, and Dell, at that time Dell was OEMing that solution for the customers. Over the years since that we started developing more and more solutions for different customer domain. We have HPC based solution, again URL based. We have SAP, we have Oracle, and variety of different Hadoop Open, Hadoop variation of the Hadoop, again on the base RHEL platforms. And most recently the OpenStack over the last five years. At the Dell Technology World last week, we announced all of the OpenShift on bare metal as a joint solution between the two companies. We have the OpenShift on OpenStack which we announced two years ago, still supportable and delivered to our customers. So the goal for us is to provide the flexibility and choices for the customers. >> What's the unique value for customers that you guys bring to the table? What's the unique value with the Red Hat relationship that's the most important? >> So the most important is the robustness of the integrated solutions, and the two companies together standing behind them. So they can go either to Red Hat or to Dell EMC and we together delivering of the solution. It is robust, it is still open and flexible, but it is also optimized all the way from hardware to the top layer of the software for their use cases. >> So customers are concerned, obviously we saw Spectre bug, and all this stuff going on with security. Red Hat customers, they're not micro-coders, I mean they have to upgrade. You guys have to take that responsibility at the hardware level, and some great certification, we know that. Going forward as the stacks become robust from, you know down to the chip level, up through applications, well you've got DevOps, you've got all these cool things happening. How are you guys keeping up with the pace to mitigate security risks and continuing the partnership? What's the story of the customer? What should they know about that particular piece? >> So obviously we are taking care of security on multiple layers from the micro-code, as you pointed out, in the solution partnering not only with Red Hat but with Intel and the hardware vendors to ensure that all of the mitigated, mitigation factors are put into place for security. But most importantly we are providing the tooling to make the benching and fixes in automated way without any disruption to the workloads which customer are running. Or minimizing the disruption for the workload so you can do all of your securities updates and for that matter, upgrades of the solution in such a way that you're minimizing the disruption for your customers. >> Okay so security, obviously hugely important. One of the themes of this event has been talking to the IT audience about kind of up-leveling digital, but you can call it digital transformation, but actually bringing more business value, and that's been really well received here as you realize all the demos, faster time to market, more business value, faster time to value. So as you talk with the customers here, and service providers. What are they asking you as a director of the software stack that has to, that you could look at as just the bottom of the stack, but in fact is hugely important to what they're doing. So what are you having to provide from the Dell side to help that acceleration? >> So the most important thing that our customer looking for is partnership. They're looking for us working with Intel, with Red Hat, and with partners specific to their area, to do together integration, and so we can provide the support and lifecyle of the solutions. >> John T: You're part of the rubber hits the road. They buy the unit, and the system, and the software from you. It better be all integrated and work. >> Correct, so again they go on this Oz with Red Hat because they want to have a flexibility so they can add more things, but what they're looking for, especially teleco providers, they would like Oz to partner all the way down to the next level-up with NFE lenders. The people who are providing them virtualized functions, so they can bring that to the solution and have level of confidence and you know peace of mind, that all of those pieces have been integrated together, validated together, and we have a continuous program where we take care of them of the full upgrade and lifecyle of not individual pieces, but the whole thing. >> Once your customers know about your relationship with Red Hat, want to get to the end of the statement, which is really even important. 'Cause I think this is important. We're seeing more and more security go from chip, to the OS, to the application layer. There's going to be more and more of that, and you got to evolve your relationship and technology. >> Yes. >> What should they know about Dell, Dell Technologies, Dell EMC, Dell proper and that's most important for them to understand, what you guys do for customers. >> So one of the most important things to understand, now we are Dell Technology. We have been Dell Technology for about a year and a lot of the integration pieces start being mature and now we can have a joint integrate solution. One of the big piece of the Dell Technology portfolio is RSA. They're probably the oldest and the most established security company in the world. And we are getting more and more integration of their tool sets into various solutions across the board. And that probably is the unique value which we as a Dell Technology can provide because we have individual pieces which are leaders in their specific field and we can put all of those pieces together to have the value to the customers through one place. >> That's exciting, well thanks for coming on and sharing the insight. We love Michael Dell, been a big fan, and Michael's been on theCUBE many times. He listens, he's probably watching right now. Hey Michael, how are you? Sorry I missed Dell EMC World, or Dell World, but John was there with Stu. Great to have you on. We've seen continuous success and a lot of skeptics on that merger, or the mergers, or the whole thing, and Pivotal just went public. Things are happening. >> Definitely, exciting time to live in. >> Yeah, thanks for coming on. More live coverage here in San Francisco at Red Hat SUMMIT 2018. I'm John Furrier, John Troyer, stay with us for more coverage after this short break. (digital music)

>> (dramatic orchestral music) >> Announcer: Live from San Francisco. It's the Cube. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hello welcome back everyone. Day three of wall-to-wall coverage here at Red Hat Summit 2018 live in San Francisco, California, here at Moscone West. I'm John Furrier, your co-host of The Cube with John Troyer, analyst, co-host this week. He's the co-founder of TechReckoning, and advisory and community development firm. Our next guest is our (mumble) of the senior Vice President General Manager of Hewlett Packard Enterprises Pointnext HPE. Great to see you. >> Great to see you as well. Thank you. >> So there's not secret HPE been partnering with companies for many generations. And Red Hat is one of the big strategic partners. Lot of services opportunity, a lot of transformation happening, and the biggest thing is that true Private Cloud and Hybrid Cloud, and Public Clouds all happening an IOT Edge is kind of seeing pretty clearly what's happening. On-Premise isn't going away. >> No! >> It'll look like Cloud is going to run like a Cloud. >> Yeah. >> Has to work with the Cloud or Clouds plural, and then you got the IOT Edge out there-- >> That's right. >> All kind of coming together with software Kubernetes containers all kind of being glue layers in here. So, you know, must be good for you guys okay, customers can now see what you guys have been promoting. So what is HP doing with their ad? How's that tie into that-- >> Sure, sure >> You know, transformation with the cloud? >> You said it very well John. In fact when we talked to our customers weather they realized it or not, it's the Hybrid world, and the environments are hybrid, and like you said, probably private (mumble) are not going anywhere. In fact we did the CTPF acquisition, Red Pexia acquisition, and this is really all to help clients on the Cloud journey. Doesn't really matter to us whether the workload ends up in AWS, Google, Azure, on Prime or dedicated infrastructure. So, that's actually been a huge plus for us to really have a seat at the table, to have a discussion on the customers workload strategy. Now a partner like Red Hat, who have been together working together for probably 18 years now, and it's been a long steady partnership. Who they're number one OAM partner but also the point you made I think from a services standpoint that's just a huge opportunity you know, customers tell us anyone can do infrastructure service or they're looking for platforming service. So in jointly with our consumption capabilities, and Red Hat Open Shift. Now who giving them true Container Product Service. >> Containerization, how we were talking yesterday in our wrap-up. You can bring in the new without killing the old and but it's really fundamental because people want Cloud scale, they want the horizontal scalable application, devops and programing infrastructures code. But they can't just throw out their legacy stuff. Containers which allows them to nurture those applications and workload, and let it take it's natural course. This is actually good for services cause you can take-- there's a solution there. >> That's right! There's absolutely. In fact customers tell us when they looking for the platform, it's not just to help them on their new build. They're looking for help also to run the existing environment and most of the times it's not practical to re-factor, re-architect every single of the Legacy applications, and cause some of them applications, as you know, they were done to leverage the performance optimization on the underlying infrastructure piece of it, and so one of the things we're doing join to the Red Hat is leverage Containerization to provide the portability for the applications. To move between the different environments and whether it's Private Cloud, Public Cloud, but the key thing is portability, and mobility and that's sweet spot for containerization. >> Give some use cases of customers. Take us through a day-in-the-life of maybe a couple different examples where you guys are engaging with Red Hat where you coming in the customer is like, "Okay, here's my situation". What are some of the trends and patterns that you see with customers? What specifically are you, is it workload, moving it to the mobile clouds? Is it more re-platforming On-Premise. >> Yeah! >> What are some of the things that you guys are doing? >> I would say that the bulk of our engagement, and that's one thing that we feel really good about joining Red Hat. We have really shifted our engagement model to be much more outcome driven. So the discussions with the client is always start off with like a workshop, and within that workshop we're actually understanding where the customer is really trying to go, what business outcomes they're trying to achieve? Before we start we going to push a specific technology or stack with specific solution set, and by having that alignment, in in fact, we talk about that IT means to be embedded with the business. Not alignment, embedded with the business, and because the role of IT has changed. So when we talk about workload, right, it's about no longer, and I talked about this earlier today, you no longer running workload just within the Forward Data Center, and the traditional view of that IT owns and operates the Forward Data Center, that's just dead. So, it's really more about managing the supply chain. We talk about the overall workload strategy. Which workloads make the most sense to go on Public Cloud, Private Cloud, and then the discussion also centers around their application portfolio and really understanding which applications truly need to be Cloud Native. Which ones really need to be left in shift, and this whole portability concept comes into play and that's one thing joining with Red Hat because Red Hat is really good joining with us on driving this kind of innovation workshops. Then you heard this earlier today as well, and that's just the fun of if. When no longer you talking about PowerPoint presentation, this and that. It's getting in a room, getting on a White Board and talking about what kind of journey really make sense for that party-- >> That's been really notable here, this week at this conference, right. There a lot of tech, a lot of software talked about, but also on the keynote a lot of people talking about culture, transformation, getting beyond your process, and the places you get stuck as IT professionals. So that's a great way to approach it. Right, nobody starts with a list of skews-- >> No! And absolutely, the other point is that one of the things that always gets missed is the focus on the management of change, and that's one of the key pieces we emphasize that not just the business process, but the culture, the people. How you going to bring them along the change journey. So, we actually put lot of emphasis on the whole area around management of change. We actually have a practice that this is one of the keys areas they focus on. So, you're absolutely right. Key focus area. >> I did want to flip to the products for a second. There was an announcement here now and talk a little bit about HP Synergy, Composable Infrastructure, with Open Shift. Maybe if you have a headline on exactly how you guys describe Synergy and then maybe how we working with Open Shift. >> So the HP Synergy the best way I can describe it is it is truly industry first composable infrastructure, and it gives you the ability to pull fluid resources and with software intelligence built in, and Unified API. It really gives you the ability to pull the resource that you need for specific applications. In fact, I use the analogy, it's kind of like building Legos and you can pull together based on what you going to do at a given moment, and then you decompose it and build something new. So it's all done via a software and truly gives you that flexibility that customers have been seeking. So it's just to me its got a great market traction across the globe and we'll just see continued momentum when joining with the Red Hat. What we've done is now with the announcing new solutions like the one you referenced to, to support ansible automation of the Red Hat Open Shift on the Synergy platform from the three part and the Nimble product lines and it just helps scale the Open Shift and while making container operation simple, scalable and more importantly repeatable. >> I want to make sure that I get this out there, because you guys were early with composable. Dave Valata and I had a debate on this at one of your HP Discovers where, I was really lov'n the composable message. Although it was kind of for a different massage but at that time Devos was really picking up steam. But, it's actually happening now three years later the level of granularity to services level as microservices as it comes the architecture of the future. The services model is literally, "What do you want?" it's not, "Here's the solution", it's like< "What do you need?" so, you're buying off the menu, if you will, so that changes the game. So congratulations on having that composable method first. I got to ask you, the impact to the engagements. So you now have menu of services. Does that change how you guys go to market? You mention that you do kick of meeting, you do the needs assessment, so I get that. Check! good approach. But the customers now, they just want to make sure that it's custom for them. How does that change your engagement? >> At the CXO level, the discussion, no mater which way you start the discussion it tends to kind of follow into a few buckets. Rather it's about generating additional revenue, going to market quicker, or it's about safe to invest, reducing their operating expenses, or it's about securing their information network. One of the thing we find is especially if you take a look at even the containers, applications deploying it. It's one thing to deploy in the corporate environment but if you're trying to scale that with an enterprise. If the enterprises look for added features for their security, whether it's persistent storage and again the focus always turns into what can you do to help drive the total cost of ownership down. I think with Red Hat this is one thing that works great with Open standards. The focus is really much more around not just the simplicity, reducing costs, it's also about improving performance. Rather it's the physical virtual environment. So, you're right, the menu of services. Whether it's you talking about IOT Use Scape and I think you going to see more and more of that with the user experience, the focus that we talked about. Context of our apps. I use the example of going to the airport, getting into whatever transportation you using these days, but the point from point A to point B, you're no longer fumbling through cash or credit cards. It's a very easy experience, much more personalized much more usable and a lot of what some of the hospitality franchises are doing, whether you look at Starwood Properties, Marriott. Now you use a mobile device to access your room, and as soon as you get into some of the hotel property, as soon as you access their Wifi coverage all of a sudden you can actually, the hotel property picks you up. They can provide you with the navigation, how to get to your room and depending on your profile, and whether you opted in or opted out, they will push and their partners will push some specific services to you. So, how you are able to create that kind of experience and drive additional revenue and all that is possible to the point he just make, it's truly a flourishing eco-system of micro services and apps driven by the-- >> I think that business now seeing that which is great about that having a clear line of site that these new apps and new experiences is going to drive top line revenue for your customers. I got to ask you about the services now. With more services comes more delivery, right? So, options, ecosystems, you guys have a pretty big ecosystem right as a lot of other providers. You guys always worked will with multiple companies. How are you guys engaging with Pointnext with now new sets of service providers and your network. You got Cloud Service and you have someone actually maybe could be an intergrater, could be a software developer. How do you deal with this new stake holder in your equation? >> After all the spin mergers have been completed now and I think after DXC1 it really open up the door to get a lot of the system (mumble) back on the table because they don't really view us as competitor anymore. Because we no longer have a large the EDS acquisition that we had now the DXE. So whether you look at Accenture or whether you look at Deloitte and the other (mumble) we're actually partnering with them very well both in joint submission creation but also when we talk about true additions transformation for our client a lot of expertise they bring to us is very complimentary to what we have. So one of the thing we do very well is really around the technology advisor services. (mumble) bring more of the business advisory services as well as the specific vertical depth around the specific vertical whether it's emphasized retail. So when somebody talking about retail of the future or something like that. You marry the two together and you have a strong value proposition. I think the area that we have to put a lot more emphasis upon is more around program management, and because now you actually are trying to show that one outcome for the client, so it's very important whether you working with the ISB or whet ever you working with DSI or whether you working with the other intergraters, and your own resources how you going to bring that pool together around specific tracks and deliver a one common objective for the clients? The Program Manager plays a huge role in this process. >> For the folks watching. What should they know about HP Pointnext that they many or may not know about or should know about that that highlights what you guys are doing. Can you simplify, what is the value proposition that Pointnext is bring to customers? >> As the brand itself states, the Pointnext, it's really about working with the clients finding what's next in their journey. One of the thing I would say and a lot of people get surprised by this, even with after all the spin merge. We are twenty-five thousand people plus strong and we have a lot of great and deep appreciation when it comes to some of these solution and one thing we do very well is partner. Whether it's Red Hat and other SI and bring some unique innovative solution to the market and one of the thing Jim talked about here is all about accelerating user driven innovation, and when you take a look at some of the use cases we're rolling out and I talked about the analytics and the one AI project and how we're helping manufacturing clients or other use cases to truly analyze patterns and predict failures and increase productivity. These discussions customers truly trust us. With the (mumble) and CTP acquisitions we no longer just having On-Premise discussions. We have a strong public hard knowledge. It doesn't matter whether you cloud journey involves AWS, Google, Azure and what not. We are able to actually provide a very objective road map for the workload strategy and the transmission journey. >> The users in the communities as Jim pointed out in the meeting yesterday. The communities in Open Source are now also your customers. >> Right. >> So your customers are also participating in these projects upstream. Are you guys doing an Open Source work? What Pointnext doing? Are you guys relying on that community? Is there a crossover between your customers and those users in the Open Source community? >> Yeah, we always had a very strong (mumble) with the Open Source community. We contributed a lot to the Open Source communities and if you take a look at now as we working with the number of this next generation of partners, whether it's darker, scale it and Red Hat and others it's truly opened up the boundaries as to what can we push to drive new kind of solution there. I love what some of the speakers said yesterday. You remember the example from the Boston Children's Hospital where they talked about they didn't want to deal with the complexity, they'd rather focus on what they do best and so one of the thing we're focused on in the Open Source Continuity is the driving more standardization and automation. So you can run applications as scale. You can run analytics as scale. I think those are somethings we can bring to the table. >> Great! You know the thing about what's going on now with these abstraction layers is an opportunity to create new services and accelerate the services, and congratulations. Great to have you on the program. Thanks for sharing the update. >> Absolutely! >> Congratulation on your deep partnership with Red Hat. Go to see HP Pointnext doing well. Thanks for coming on. >> Thank you so much. >> Live coverage here in San Francisco California. Red Hat Summit 2018 will continue. I'm John Furrier John Troyer. Stay with us more coverage after this short break. >> (electronic music) >> Often times a communities all ready know about facilities that are problematic, because they smell it, they see it but

>> Announcer: Live, from San Francisco, it's theCUBE. Covering Red Hat Summit 2018. Brought to you by Red Hat. >> Hello everyone, welcome back, this is day three of theCUBE's exclusive coverage of Red Hat Summit 2018, live in San Francisco, California, at Moscone West. We're out in the open, in the middle of the floor here, I'm John Furrier, your co-host, with my co-host to speak, John Troyer, co-founder of TechReckoning, advisory and community development firm, our next guest is CUBE alumni Kim Stevenson, Senior Vice President, General Manager of the Data Center Group Solution segment at Lenovo, great to see you. >> Hey, how are you? >> Thanks for coming on, so Red Hat Summit, Lenovo, okay, how does that fit together for you guys, Data Center obviously is cloud now, and you got on-premise-- >> We're both in Raleigh (Kim laughs) >> You moved to Raleigh, news, what's the update? Where's that connection with an hybrid cloud is taking this world by storm? >> Yeah, so, we're a great partner with Red Hat, and we're very focused on enabling that hybrid enterprise through hybrid cloud. So one of the things that we've done, we do a lot of co-development, but one of the things is we've taken our systems management software, which is Xclarity, and we're the first to embed that into cloud forms, so that we can move assets, public assets to private assets, and vice versa, and that wouldn't be possible without working really closely with Red Hat, so-- >> Well Red Hat's been very strong at support, and you go to the RHL side, on the operating system side, very reliable, it's got years and years of experience, but it's always been kind of let's certify the hardware, and now that you have a hardware at the baseline moving up the stack, you have OpenShift, getting huge success, Kubernetes, now you've got multiple clouds, which has other hardware, security becomes a concern, we hear that, okay, security being on top of that's a really big deal. How does that change the game for you guys, how are you guys adjusting to that, because it requires everyone to do more work, but now you got automation playing a role, take us through that relationship between from the hardware all the way up to the stack. >> Yeah, and it is the weakest link issue, right, that every piece of the solution has to be secure in and its own right, and the solution has to be secure, right? So, we do a lot in the hardware environment through our supply chain, we have efficacy of every part and component that goes in, every piece of software loaded through manufacturing, one of the benefits of having your own manufacturing organization, so we know what give is a secure platform when there is ready to go. But then as you start to add the software, this is where things like containers become really important, and the ability to do monitoring of the environment, without having to stop the environment. And, so, we have a lot of investment going in OpenShift, and we've launched recently a DevOps practice, based on OpenShift, to actually accelerate the deployment of more and more containers, to again, figure out the security by design versus security after the fact. The problem with monitoring is it's after the fact. You want to design in, and you need to rethink the application structure in order to be able to do that. >> Talk about Lenovo's strategy and innovation around enterprise and emerging tech, because, consumerization of IT has been topic, we talk about going way back, many, many years, but actually, the role of consumer hardware products is becoming more and more enterprise, as IoT for instance, becomes a critical piece of the network, whether it's new wearables for humans, or a security camera on a network, the edge of the network is now the IoT device, but also the data center can be considered an edge, a big edge, right? So, you have now devices everywhere, that's not so much consumer-ish, it really has to be enterprise, and cloud enabled. What are you guys doing in the innovation area there? What are some of the things that Lenovo's doing to move the needle on really making a seamless IoT edge, secure, and functional? >> Yeah, so, one of the things, if you look back at the last ten years of IT, right, we've spent a lot of time as IT organizations consolidating data centers, and then, basically, getting rid of people in IT, right? The simplicity of an AWS, and Azure Stack, has actually driven down the number of operational people in IT. And now you're hitting this wave where, on-prem private clouds, are becoming more and more important. It could be the analytic workloads, it could be your blockchain workloads, but the workloads that you want to keep on-prem, and you're going, "Holy crap, I need a robust "operational organization to actually "make this come to life." So that was one of my predictions for this year, was operational simplicity rises in importance, and our response to that from a Lenovo solution is to build fully-integrated appliances. So we have fully-integrated private cloud appliances based on Azure Stack, based on Nutanix, based on VMware's vSAN, ready nodes, so that you pick either at the software layer only, or you can pick a fully-integrated appliance where it's integrated in the factory, that's what I call rack-and-roll, comes with white glove support, and you need far less operational people. And if you want to know, I mean, it's mimicking that simplicity that AWS offers, right? So it's really an application team that now can manage this entire operational environment. >> So is that targeted towards folks who are transitioning to cloud operations? One of the things about true private cloud is, they're essentially rebooting their organizations to be cloud operations, essentially. >> That's right, yeah. >> And so they want that plug-and-play, if you will, I use that old term, but, just out of the box, and then it becomes a resource on the network, is that what you-- >> Yeah, well everybody says, they say the hardware doesn't matter, well it matters (laughs), you know, because it what makes everything run. But what they mean by that is they don't want to mess with it, it needs to be a no-fuss, no-muss, it needs to be there like a utility, but not have to have the resource dedication that used to exist, where I needed storage admins, and database admins, and server admins. That level of monitoring and management has to be abstracted to the software layer, and you have to then be able to integrate your resource components to be able to do that, and look at it as a system, not as a component. And that's where we're headed with our strategy. >> Yeah, Kim, that's a great consumption model, right? An increasing part of the market, converged infrastructure, hybrid conversion infrastructure, like you say rack and, what'd you use? >> Rack-and-roll. >> Rack-and-roll, I like that. But the hardware does matter, right? A few years ago, if you'd listen to some people, we were going to be inside public clouds with some sort of undifferentiated pools of x86 servers out there, but it turns out the actual hardware, and the integration pieces, do matter. John mentioned IoT, AI, we've seen some examples of it here at the show, real world examples, and then for that, hardware really starts to matter. Can you talk a little bit about how Lenovo's looking to some of these emerging tech? >> At the beginning of the year, we formed an IoT division specifically to focus on IoT, and it really is bringing the edge to life, that's the mission of that particular organization. And so, we see sort of the remote office, branch office concept that has long since, I mean, it goes back to AS/400 days, right? You had branch office computing. But, reinventing itself in a modern way into these edge servers that can be rugged-ized, for, you know, we have edge servers in windmills, as an example, to manage and monitor a windmill farm, right? To optimize generation with wind shifts, those kinds of things, but it could be a closet, right, and it could-- >> It's not a data center. >> It's not a data center, is in a physical construct of a data center, is in the functionality provided, it is a data center, and so, we have from our PC group one of the things I'm pretty interested about is we have these things called stackables, so they're about five by eight inches of a PC, and then you can magnetically connect a battery to a magnetically projector to it through magnets, and you can get basically a stack of computing power. So, we've looked at that from our PC colleagues, and said, "Huh, that's the future of the edge, "but it needs to be ZEON class, "it needs to be enterprised as manageability,", and so it won't be five inches by eight inches when we're done, but, it will use some of that IP in the stackable nature, that will allow you, then I can put that stackable unit on the back of a television monitor for a smart display, I could put it back on a kiosk, or a vending machine, or, and all of the sudden, now I can get really different customer experience at the edge, and then I can parse data, maybe I don't need that data, to go back to the cloud, maybe I do need some of that, for, you know, machine-learning capabilities, I want to create big data sets back in the cloud, you can create that level of intelligence at the edge, and parse the data, to where you think the appropriate destination for that data is. >> How important is the IoT edge for you guys, and what should customers who are trying to merge cultures of OT, Operational Technology, with IT? 'Cause now you have IP devices. Which, it creates a security potential, but, there's now policy involved, you got to write software apps for it, you got unique use cases, talk about the importance of the IoT edge, for Lenovo, and what customers should be thinking about when they architect. >> So, my starting point is every piece of equipment becomes an IP-enabled device that will generate and collect data, you're going to have to figure out how to use that data, right? I said to our facilities leader, not too long ago, I said, I pointed at the table, at the conference table we were at, "What do you think this is?" And he's like, "Uh, it's table," and I'm like, "Hmm, no, to me, this is a smart table. "It could be IP-connected, and we could figure out, "is it the right value for this particular room," and you could just get into these crazy things, some will make sense, some won't make sense, but basically, I think every company is looking at how do they make their products and services smart by wrapping them with IT-enabled services. So that creates a new edge. We used to think of endpoints as PCs and phones, now there are cars, and you know, any form of transportation vehicle, they're windmills, they're semi-conductor equipment, you name it. And, that is sort of the new, that's where we are trying to attack, from the IoT perspective, what we're trying to help customers understand is, it's that data collection use case analysis that will enable them. One of my favorite examples is Ford has a prototype product, it's not a car, it's a baby crib. Now, why, right? So, through autonomous driving, they collect a bunch of data, everybody knows that when new parents have a cranky baby in the middle of the night, what do you do, you put 'em in the car, you take 'em for a ride, right? So this baby crib mimics the motion of a car, mimics the sound of an engine, and mimics the streetlights. There's no more taking your baby for a ride in the middle of the night, you put 'em in the bed, yeah, we've all done it! And this is why these endpoint devices collecting data to figure out these new products and services, and I just think, whether they ever bring that to market or not is not the point-- >> It's new experiences. >> It's a brilliant idea, and gives you a really good illustration of how creating these smart-enabled endpoints will allow you to generate new business opportunities. >> That's been a real theme here at the show, getting beyond the technology, right? Transformation is kind of a buzz word, but, I loved that they didn't put a huge amount of tech on stage, they really did talk to the people here, attendees, about, "Look, you've got to step up, "you've got to have new ideas, "you've got to affect the business." How are you, as you talk with both of your customers and inside Lenovo, addressing those kind of transformation and business ad sorts of deals? >> Yeah, look, I said today, and I really believe this, there's a new mandate for IT. The table stakes of keeping the business running, of course we have to keep the business running and running well, right? But really, every IT leader should be thinking about how do they redefine the customer experience for their organization, how they drive extreme productivity, through AI and blockchain and stuff, companies today are extraordinarily inefficient. We all live in a company, and we can tell you it's inefficient, right? But, you now have the ability to affordably drive out that inefficiency through this level of extreme productivity, and then everybody needs to be thinking about the future of the company, what are you in the business of, and how do you wrap those with new products and services, whether it's adjacent markets that you're going to create, or it's enhancements of your existing product, so you can reach new customers, new markets, and that's a far more interesting role for IT, but you can't give up the ship either, right? You cannot let operational performance decline while you're operating on the new mandate, which is why new operating models for IT, and the hyper-converged infrastructures, and in-- >> Containers have been a great help there too-- >> Containers, right, we just have to fundamentally re-architect, so that it's easy to actually drive change, flawless change, into the enterprise, and, the volume of change for our future is twice as great as what we've experienced in the past, and if you accept that as a premise, you'll rethink how you've done your architecture, and how you promote code into production, and how you manage that code going forward. >> We always love having you on theCUBE, 'cause you always do predictions, so I want to go back and get some predictions from you. What's your predictions next year, what do you see happening, you know, by the way, you have been right in a lot of your predictions, so, we have the tapes, we can go back and look at the videos. (laughs) Ah, I guess you were right on that one! What's your predictions this year, I mean obviously you've seen a lot going on, we are talking about, here on theCUBE, seeing what's going on with Kubernetes, change to OpenShift, that a new internet infrastructure's being recast, with compatibility modes, with containers, and Kubernetes for orchestration, cloud scale, you can come up with IoTs, a new infrastructure, and upgrade, is coming. So there's a lot of things happening. So what's your prediction, what's going to happen over the next year? >> Yeah, so I actually believe this is the first year that we have human capacity in IT organizations to reinvent the enterprise structure, which comes led with an enterprise architecture discussion. We've been moving more cloud to the cloud SaaS applications, you know, infrastructure as a service, and that is now absorbed enough into that you can stand back and look at it, so I do believe that, I call it data centers go micro, that the era of data center consolidation is over, that we will be more data centers, they just will be micro-data centers, because they will reflect the edge of every company, and those endpoint aggregation that you need to do to figure out what your data analysis is going to be. I also think that the operational simplicity that operating models are going to be redefined, as more and more private clouds get deployed, the structure of an IT organization has typically looked like this, you have four basic functions, you have IT engineering, IT operations, application development, and applications maintenance. That's typically the structure. I think you're going to see a collapsing of that. There actually is no reason for four independent functions, you need to organize by line of business, and the business outcome you're trying to drive, and, workers are going to need to be more versatile, in terms of being able to span, you're going to abstract a lot from the infrastructure, right, so you need to be able to manage at a higher level, therefore you can't organize in that discreet manner, and I think you'll start to see that come life-- >> John: Like horizontally scalable people. >> Sounds like horizontally scalable people, yeah. >> You've been a CIO at Intel, you have a lot of varieties of roles sittin' on some boards, you're now in an executive role at Lenovo, you're managing products, your responsibilities are building, shipping and business performance as well. How has your role changed? You've been there for about what, a year and a 1/2 or so? >> Yep, just about a year. >> Just about a year, what's the energy like, what are you bringing to the teams, what's your vision, what's your to do list within Lenovo to take it to the next level? >> Yeah, so when I started with Lenovo because I considered Lenovo the underdog, in the data center industry, which was going through phenomenal change, right? And so, the underdog has the best opportunity to capture hearts and minds and share when the industry's going through change, and so that's what attracted me. And it's been true. We organized, about this time last year, by customer segment, to serve the unique needs of our customers in terms of hyper-scaling customers, high performance compute and enterprise, both at the software-defined and traditional layer. And, in that one year, we've won six out of the ten top hyper-scalers in the world, from zero to six in a year, we consider that to be great, and we learn so much from their, they're doing a lot of customization, and they're two, three, four years ahead of what the general enterprise will consume, and so we're able to take that then and pull it back into our private cloud deployment strategy, into our enterprise management, software management, and strategy, because we see what they're doing, and use that as a virtual cycle of life, and we've got a lot of momentum in that area. And our employees are just excited about how much progress we've made in a year. And I would say if you pulled ten of 'em, nine out of ten would've said they wouldn't have believed we could make so much progress in one year. And that's a good feeling to have. Now, there's more work to do (laughs). >> Yeah, you have product leadership, you've got some great products, it's now just focus and getting on the right wave, right? I mean, 'cause the industry is changing! >> Kim: The industry is changing-- >> So you can move the needle big time. >> Yeah, and we've chosen from a software perspective, we've chosen a deep partnership model, with Red Hat as one of the partners, and so, if I look forward, and I would say, "Look, "we're going to have to go deeper and partner more broadly "across the ISV sphere to continue to bring "these tightly integrated appliances "in simple cloud deployment models to the market," and that's what you'll see us do next. >> Well it's exciting for you, and congratulation on that, and they're lucky to have you, and we know from when you were at Intel, you've seen the playbook, you know? (laughs) A lot of change going on, so great to see you, congratulations, we sure did love covering Lenovo, a lot of great action, thanks for your support, and thanks for coming on, sharing your insights here on theCUBE again, appreciate it. >> Thanks for having me. >> Kim Stevenson here outside theCUBE for Red Hat Summit 2018, live in San Francisco, I'm John Furrier with John Troyer, we'll be back with more, after this short break. (bright electronic music) (soothing music) >> Oftentimes the communities already know about a facility that's a problematic because, they smell it, they see it, but, again, they don't have the evidence to basically prove that whatever's happening with their health is related to that facility. (bright music) If you have a low-cost instrument that's easy to use, then all of the sudden, science becomes something that everyday people can do. (bright music) (somber electronic music) >> Hi I'm John Furrier, the co-founder of SiliconANGLE Media, and co-host of theCUBE. I've been in the tech business since I was 19, first programming on minicomputers in a large enterprise, and then worked at IBM and Hewlett Packard, a total of nine years in the enterprise, various jobs from programming, training, consulting, and ultimately, as an executive salesperson, and then started my first company in 1997. And moved to Silicon Valley in 1999, I've been here ever since. I've always loved technology, and I loved covering, you know, emerging technology. I was trained as a software developer, and loved business. And I loved the impact of software, and technology, to business. To me, creating technology that starts a company and creates value and jobs is probably one of the most rewarding things I've every been involved in. And, I bring that energy to theCUBE, because theCUBE is where all the ideas are, and where the experts are, where the people are, and I think what's most exciting about theCUBE is that we get to talk to people who are making things happen. Entrepreneurs, CEO of companies, venture capitalists, people who are really on a day-in and day-out basis, building great companies. And the technology business has just not a lot of real time, live TV coverage, and theCUBE is a nonlinear TV operation, we do everything that the TV guys on cable don't do. We do longer interviews, we ask tougher questions, we ask sometimes some light questions, we talk about the person, and what they feel about. It's not prompted, and scripted, it's a conversation, it's authentic. And for shows that have theCUBE coverage, it makes the show buzz, it creates excitement, and more importantly, it creates great content, and great digital assets, that can be shared instantaneously through the world. Over 31 million people have viewed theCUBE, and that is the result of great content, great conversations, and I'm so proud to be part of theCUBE, we're a great team. Hi, I'm John Furrier, thanks for watching theCUBE. (soothing music) >> Man: One of the community's goals.

[Music] and y'all know that these [Music] ladies and gentlemen please take your seats and silence your cellphone's our program will begin shortly ladies and gentlemen please welcome Red Hat executive vice president and chief people officer dallisa Alexander an executive vice president and chief marketing officer Tim Layton [Music] hi everyone we're so excited to kick off this afternoon day 2 at the Red Hat summit we've got a stage full of stories about people making amazing contributions with open source well you know dallisa you and I both been coming to this event for a long long time so what keeps you coming back well you know the summit started as a tech conference an amazing tech conference but now it's expanded to be so much more this year I'm really thrilled that we're able to showcase the power of open source going way beyond the data center and beyond the cloud and I'm here also on a secret mission oh yes I'm here to make sure you don't make too many bad dad jokes so there's no such thing as a bad dad they're just dad jokes are supposed to be bad but I promise to keep it to my limit but I do have one okay I may appeal to the geeks in the audience okay so what do you call a serving tray full of empty beer cans yeah we container platform well that is your one just the one that's what I only got a budget of one all right well you know I have to say though in all seriousness I'm with you yeah I've been coming to the summit since its first one and I always love to hear what new directions people are scoring what ideas they're pursuing and the perspectives they bring and this afternoon for example you're gonna hear a host of different perspectives from a lot of voices you wouldn't often see on a technology mainstage in our industry and it's all part of our open source series live and I have to say there's been a lot of good buzz about this session all week and I'm truly honored and inspired to be able to introduce them all later this afternoon I can tell you over the course the last few weeks I've spent time with all of them and every single one of them is brilliant they're an innovator they're fearless and they will restore your faith in the next generation you know I can't wait to see all these stories all of that and we've got some special guests that are surprised in store for us you know one of the things that I love about the people that are coming on the stage today with us is that so many of them teach others how to code and they're also bringing more people that are very different in to our open-source communities helping our community is more innovative and impactful and speaking of innovative and impactful that's the purpose of our open brand project right that's right we're actually in the process of exploring a refresh of our mark and we'd really like your help as well because we're doing this all in the open we've we've been doing it already in the open and so please join us in our feedback zone booth at the summit to tell us what you think now it's probably obvious but I'm big into Red Hat swag I've got the shirt I've got my pen I've got the socks so this is really important to me personally especially that when my 15 year old daughter sees me in my full regalia she calls me adorable okay that joke was fed horrible as you're done it wasn't it wasn't like I got way more well Tim thanks for helping us at this stage for today it's time to get started with our first guest all right I'll be back soon thank you the people I'm about to bring on the stage are making outstanding contributions to open source in new and brave ways they are the winners of the 2018 women and open source Awards the women in open source awards was created to highlight the contributions that women are making to open source and to inspire new generations to join the movement our judges narrowed down the panel a very long list just ten finalists and then the community selected our two winners that were honoring today let's learn a little bit more about them [Music] a lot of people assume because of my work that I must be a programmer engineer when in fact I specifically chose and communications paths for my career but what's fascinating to me is I was able to combine my love of Communications and helping people with technology and interesting ways I'm able to not be bound by the assumptions that everybody has about what the technology can and should be doing and can really ask the question of what if it could be different I always knew I wanted to be in healthcare just because I feel like has the most impact in helping people a lot of what I've been working on is geared towards developing technology and the health space towards developing world one of the coolest things about open-source is bringing people together working with other people to accomplish amazing things there's so many different projects that you could get involved in you don't even have to be the smartest person to be able to make impact when you're actually developing for someone I think it's really important to understand the need when you're pushing innovation forward sometimes the cooler thing is not [Music] for both of us to have kind of a health care focus I think it's cool because so many people don't think about health care as being something that open-source can contribute to it took a while for it to even get to the stage where it is now where people can open-source develop on concepts and health and it's an untapped potential to moving the world for this award is really about highlighting the work of dozens of women and men in this open source community that have made this project possible so I'm excited for more people to kind of turn their open-source interest in healthcare exciting here is just so much [Music] I am so honored to be able to welcome to the stage some brilliant women and opensource first one of our esteemed judges Denise Dumas VP of software engineering at Red Hat she's going to come up and share her insights on the judging process Denise so you've been judging since the very beginning 2015 what does this judge this being a judge represents you what does the award mean to you you know every year it becomes more and more challenging to select the women an opensource winner because every year we get more nominees and the quality of the submissions well there are women involved in so many fabulous projects so the things that I look for are the things that I value an open source initiative using technology to solve real world problems a work ethic that includes sin patches and altruism and I think that you'll see that this year's nominees this year's winners really epitomize those qualities totally agree shall we bring them on let's bring them on let's welcome to the stage Zoe de gay and Dana Lewis [Music] [Applause] [Applause] [Music] alright let's take a seat [Applause] well you both have had an interesting path to open-source zuy you're a biomedical engineering student any of it you have a degree in public relations tell us what led to your involvement and open source yeah so coming to college I was new I was interested in science but I didn't want to be a medical doctor and I didn't want to get involved in wet lab research so through classes I was taking oh that's why I did biomedical engineering and through classes I was taking I found the classroom to be very dry and I didn't know how how can I apply what I'm learning and so I got involved in a lot of entrepreneurship on campus and through one of the projects I was asked to build a front end and I had no idea how to go about doing that and I had some basic rudimentary coding knowledge and what happened was I got and was digging deep and then found an open source library that was basically building a similar thing that I needed and that was where I learned about open source and I went from there now I'm really excited to be able to contribute to many communities and work on a variety of projects amazing contributions Dana tell us about your journey well I come from a non-traditional background but I was diagnosed with type 1 diabetes at the age of 14 and over the next couple years got really frustrated with the limitations of my own diabetes devices but felt like I couldn't change them because that wasn't my job as a patient but it was actually through social media I discovered someone who had solved one of the problems that I had been found having which was getting date off my diabetes device and that's how I learned about open source was when he was willing to share his code with me so when we turned around and made this hybrid closed-loop artificial pancreas system it was a no brainer to make our work open source as well that's right absolutely and we see using the hash tag we are not waiting can you tell us about that yeah so this hash tag was created actually before I even discovered the open source diabetes world but I loved it because it really illustrates exactly the fact that we have this amazing technology in our hands in our pockets and we can solve some of our most common problems so yes you could wait but waiting is now a choice with open source we have the ability to solve some of our hardest problems even problems dealing with life and death that's great so zuy with the vaccine carrier system that you helped to build how were you able to identify the need and where did you build it yes so I think before you even build anything first need to understand what is the problem that you're trying to solve and that really was the case when starting this project I got to collaborate with engineers in Kampala Uganda and travel there and actually interview stakeholders in the medical field medical doctors as well as pharmaceutical companies and from there I really got to understand the health system there as well as what is how do vaccines enter the country and how can we solve this problem and that's how we came up with the solution for an IOT based vaccine carrier tracking system I think it's really important especially today when products might be flashy to also understand what is the need behind it and how do we solve problems with these products yeah yeah it's so interesting how both of you have this interest in health care Dana how do you see open-source playing a role in healthcare but first before you answer that tell us about your shirt so this shirt has the code of my artificial pancreas on it and I love it as an illustration of no thank you I love it as an illustration of how open-source is more than we think it is I've just been blown away by the contributions of people in my open-source communities and I think that that is what we should apply to all of healthcare there's a lot of tools and technologies that are solving real world problems and I think if we take what we know in technology and apply it to healthcare we'll solve a lot of problems more quickly but it really needs to be recognizing everything an open source it's the documentation it's the collaboration it's the problem-solving it's working together to take technologies that we didn't previously think we're applicable and finding new ways to apply it it's a great answer Sooey yeah I think especially where healthcare is related to people and open-source is the right way to collaborate with people all over the world especially in the project I've been working on we're looking at vaccines in Uganda but the same system can be applied in any other country and then you can look at cross countries health systems there and from there it becomes bigger and bigger and I think it's really important for people who have an idea and want to take it further to know that open-source is a way that you could actually take your idea further whether you have a technical background or not so yeah stories are amazing you're just an inspiration for everyone in open-source I want to thank you so much for joining us here today let's give another round of applause to our winners [Applause] [Music] you know the tagline for the award is honor celebrate inspire and I feel like we've been doing that today very very well and I know that so many people have been inspired today especially the next generation who go on to do things we can't even dream of yet [Music] I think collabs important because we need to make sure we get younger children interested in technology so that they understand the value of it but also that there are a lot of powerful women in technology and they can be one of them I hope after this experience maybe we'll get some engineers and some girls working our hot so cool right well we have some special guests convite for the club stage now I'd like to invite Tim back and also introduce Red Hat's own Jamie Chappell along with our collab students please welcome Gabby tenzen Sofia lyric Camila and a Volyn [Applause] you've been waiting for this moment for a while we're so excited hear all about your experiences but Jamie first tell us about collab sure so collab is red hats way of teaching students about the power of open source and collaboration we kicked off a little over a year ago in Boston and that was so successful that we decided to embark on an East Coast tour so in October we made stops at middle schools in New York DC and Raleigh and these amazing people over here are from that tour and this week they have gone from student to teacher so they've hosted two workshops where they have taught Red Hat summit attendees how to turn raspberry pies into digital cameras they assigned a poem song of the open road by Walt Whitman and they've been working at the open source stories booth helping to curate photos for an installation we're excited to finish up tomorrow so amazing and welcome future women in open source we want to know all about your experiences getting involved can you tell us tenzen tell us about something you've learned so during my experience with collab I learned many things but though however the ones that I valued the most were open source and women empowerment I just I was just so fascinated about how woman were creating and inventing things for the development of Technology which was really cool and I also learned about how open source OH was free and how anyone could access it and so I also learned that many people could you know add information to it so that other people could you learn from it and use it as well and during Monday's dinner I got this card saying that the world needed more people like you and I realized through my experience with collab that the world does not only need people like me but also everyone else to create great technology so ladies you know as you were working on your cameras and the coding was there a moment in time that you had an AHA experience and I'm really getting this and I can do this yes there was an aha moment because midway through I kind of figured out well this piece of the camera went this way and this piece of the camera did it go that way and I also figured out different features that were on the camera during the camera build I had to aha moments while I was making my camera the first one was during the process of making my camera where I realized I was doing something wrong and I had to collaborate with my peers in order to troubleshoot and we realize I was doing something wrong multiple times and I had to redo it and redo it but finally I felt accomplished because I finished something I worked hard on and my second aha moment was after I finished building my camera I just stared at it and I was in shock because I built something great and it was so such a nice feeling so we talked a lot about collaboration when we were at the lab tell us about how learning about collaboration in the lab is different than in school so in school collaboration is usually few and far between so when we went to collab it allowed us to develop new skills of creativity and joining our ideas with others to make something bigger and better and also allowed us to practice lots of cooperation an example of this is in my group everybody had a different problem with their pie camera and we had to use our different strengths to like help each other out and everybody ended up assembling and working PI camera great great awesome collaboration in collab and the school is very different because in collab we were more interactive more hands-on and we had to work closer together to achieve our own goals and collaboration isn't just about working together but also combining different ideas from different people to get a product that is so much better than some of its parts so girls one other interesting observation this actually may be for the benefit of the folks in our audience but out here we have represented literally hundreds and hundreds of companies all of whom are going to be actually looking for you to come to work for them after today we get first dibs that's right but um you know if you were to have a chance to speak to these companies and say what is it that they could do to help inspire you know your your friends and peers and get them excited about open source what would you say to them well I'm pretty sure we all have app store and I'm pretty sure we've all downloaded an app on that App Store well instead of us downloading app State well the computer companies or the phone companies they could give us the opportunity to program our own app and we could put it on the App Store great idea absolutely I've got to tell you I have a 15 year old daughter and I think you're all going to be an inspiration to her for the same absolutely so much so I see you brought some cameras why don't we go down and take a picture let's do it [Applause] all right I will play my very proud collab moderator role all right so one two three collab okay one two three [Applause] yeah so we're gonna let leave you and let you tell us more open source stories all right well thank you great job thank you all and enjoy the rest of your time at Summit so appreciate it thanks thank you everyone pretty awesome pretty awesome and I would just like to say they truly are fedorable that's just um so if you would like to learn more as you heard the girls say they're actually Manning our open-source stories booth at the summit you know please come down and say hello the stories you've seen thus far from our women and open-source winners as well as our co-op students are really bringing to life the theme of this year's summit the theme of ideas worth exploring and in that spirit what we'd like to do is explore another one today and that is how open-source concepts thrive and expand in the neverending organic way that they do much like the universe metaphor that you see us using here it's expanding in new perspectives and new ideas with voices beyond their traditional all starting to make open-source much bigger than what it was originally started as fact open-source goes back a long way long before actually the term existed in those early days you know in the early 80s and the like most open-source projects were sort of loosely organized collections of self-interested developers who are really trying to build low-cost more accessible replicas of commercial software yet here we are 2018 the world is completely different the open-source collaborative development model is the font of almost all original new innovation in software and they're driven from communities communities of innovation RedHat of course has been very fortunate to have been able to build an extraordinary company you know whose development model is harnessing these open-source innovations and in turning them into technologies consumable by companies even for their most mission-critical applications the theme for today though is we see open-source this open source style collaboration and innovation moving beyond just software this collaborative community innovation is starting to impact many facets of society and you're starting to see that even with the talks we've had already too and this explosion of community driven innovation you know is again akin to this universe metaphor it expands in all directions in a very organic way so for red hat you know being both beneficiaries of this approach and stewards of the open collaboration model we see it important for us to give voice to this broader view of open source stories now when we say open source in this context of course will meaning much more than just technology it's the style of collaboration the style of interaction it's the application of open source style methods to the innovation process it's all about accelerating innovation and expanding knowledge and this can be applied to a whole range of human endeavors of course in education as we just saw today on stage in agriculture in AI as the open source stories we shared at last year's summit in emerging industries like healthcare as we just saw in manufacturing even the arts all these are areas that are now starting to benefit from collaboration in driving innovation but do we see this potentially applying to almost any area of human endeavor and it expands again organically expanding existing communities with the addition of new voices and new participants catalyzing new communities and new innovations in new areas as we were talking about and even being applied inside organizations so that individual companies and teams can get the same collaborative innovation effects and most profound certainly in my perspective is so the limitless bounds that exist for how this open collaboration can start to impact some of humankind's most fundamental challenges we saw a couple of examples in fact with our women and open-source winners you know that's amazing but it also potentially is just the tip of the iceberg so we think it's important that these ideas you know as they continue to expand our best told through storytelling because it's a way that you can embrace them and find your own inspirations and that's fundamentally the vision behind our open-source stories and it's all about you know building on what's come before you know the term we use often is stay the shoulders are giants for a lot of the young people that you've seen on this stage and you're about to see on this stage you all are those giants you're the reason and an hour appears around the world are the reasons that open-source continues to expand for them you are those giants the other thing is we all particularly in this room those of us have been around open-source we have an open-source story of our own you know how were you introduced the power of open-source how did you engage a community who inspired you to participate those are all interesting elements of our personal open-source stories and in most cases each of them are punctuated by you here my question to the girls on stage an aha moment or aha moments you know that that moment of realization that enlightens you and causes you to think differently and to illustrate I'm going to spend just a few minutes sharing my open-source story for for one fundamental reason I've been in this industry for 38 years I am a living witness to the entire life of open-source going back to the early 80s I've been doing this in the open-source corner of the industry since the beginning if you've listened to Sirhan's command-line heroes podcasts my personal open story will actually be quite familiar with you because my arc is the same as the first several podcast as she talked about I'm sort of a walking history lesson in fact of open source I wound up at most of the defining moments that should have changed how we did this not that I was particularly part of the catalyst I was just there you know sort of like the Forrest Gump of open-source I was at all these historical things but I was never really sure how it went up there but it sure was interesting so with that as a little bit of context I'm just gonna share my aha moment how did I come to be you know a 59 year old in this industry for 38 years totally passionate about not just open source driving software innovation but what open source collaboration can do for Humanity so in my experience I had three aha moments I just like to share with you the first was in the early 80s and it was when I was introduced to the UNIX operating system and by the way if you have a ha moment in the 80s this is what it looks like so 1982 mustache 19 where were you 2018 beard that took a long time to do all right so as I said my first aha moment was about the technology itself in those early days of the 80s I became a product manager and what at the time was digital equipment corporation's workstation group and I was immediately drawn to UNIX I mean certainly these this is the early UNIX workstation so the user interface was cool but what I really loved was the ability to do interactive programming via the shell but by a--basically the command line and because it was my day job to help figure out where we took these technologies I was able to both work and learn and play all from the same platform so that alone was was really cool it was a very accessible platform the other thing that was interesting about UNIX is it was built with networking and and engagement in mind had its own networking stack built in tcp/ip of course and actually built in a set of services for those who've been around for a while think back to things like news groups and email lists those were the first enablers for cross internet collaboration and that was really the the elements that really spoke to me he said AHA to me that you know this technology is accessible and it lets people engage so that was my first aha moment my second aha moment came a little bit later at this point I was an executive actually running Digital Equipment Corporation UNIX systems division and it was at a time where the UNIX wars were raging right all these companies we all compartmentalized Trump those of the community and in the end it became an existential threat to the platform itself and we came to the point where we realized we needed to actually do something we needed to get ahead of this or UNIX would be doomed the particular way we came together was something called cozy but most importantly the the technique we learned was right under our noses and it was in the area of distributed computing distributed client-server computing inherently heterogenous and all these same companies that were fierce competitors at the operating system level were collaborating incredibly well around defining the generation of client-server and distributed computing technologies and it was all being done in open source under actually a BSD license initially and Microsoft was a participant Microsoft joined the open group which was the converged standards body that was driving this and they participated to ensure there was interoperability with Windows and and.net at the time now it's no spoiler alert that UNIX lost right we did but two really important things came out of that that sort of formed the basis of my second aha moment the first is as an industry we were learning how to collaborate right we were leveraging open source licenses we realized that you know these complex technologies are best done together and that was a huge epiphany for the industry at that time and the second of course is that event is what opened the door for Linux to actually solve that problem so my second aha was all about the open collaboration model works now at this point to be perfectly candidates late 1998 well we've been acquired by compacts when I'm doing the basically same role at Compaq and I really had embraced what the potential impact of this was going to be to the industry Linux was gaining traction there were a lot of open source projects emerging in distributed computing in other areas so it was pretty clear to me that the in business impact was going to be significant and and that register for me but there was seem to be a lot more to it that I hadn't really dropped yet and that's when I had my third aha moment and that was about the passion of open-source advocates the people so you know at this time I'm running a big UNIX group but we had a lot of those employees who were incredibly passionate about about Linux and open source they're actively participating so outside of working a lot of things and they were lobbying more and more for the leadership to embrace open source more directly and I have to say their passion was contagious and it eventually spread to me you know they were they were the catalyst for my personal passion and it also led me to rethink what it is we needed to go do and that's a passion that I carry forward to this day the one driven by the people and I'll tell you some interesting things many of those folks that were with us at Compaq at the time have gone on to be icons and leaders in open-source today and many of them actually are involved with with Red Hat so I'll give you a couple of names that some of whom you will know so John and Mad Dog Hall work for me at the time he was the person who wrote the first edition of Linux for dummies he did that on his own time when he was working for us he he coined he was part of the small team that coined the term open source' some other on that team that inspired me Brian Stevens and Tim Burke who wrote the first version to rent out Enterprise Linux actually they did that in Tim Burke's garage and cost Tim's still with Red Hat today two other people you've already seen him on stage today Denise Dumas and Marko bill Peter so it was those people that I was fortunate enough to work with early on who had passion for open-source and much like me they carry it forward to this day so the punchline there is they ultimately convinced us to you know embrace open-source aggressively in our strategy and one of the interesting things that we did as a company we made an equity investment in Red Hat pre-ipo and a little funny sidebar here I had to present this proposal to the compact board on investing in Red Hat which was at that time losing money hand over fist and they said well Tim how you think they're gonna make money selling free software and I said well you know I don't really know but their customers seem to love them and we need to do this and they approve the investment on the spot so you know how high do your faith and now here we are at a three billion dollar run rate of this company pretty extraordinary so from me the third and final ha was the passion of the people in the way it was contagious so so my journey my curiosity led me first to open source and then to Red Hat and it's been you know the devotion of my career for over the last thirty years and you know I think of myself as pretty literate when it comes to open source and software but I'd be the first one to admit I would have never envisioned the extent to which open source style collaboration is now being brought to bear on some of the most interesting challenges in society so the broader realization is that open source and open can really unlock the world's potential when applied in the collaborative innovative way so what about you you know you many of you particular those have been around for a while you probably have an open source story of your own for those that maybe don't or they're new to open source are new to Red Hat your open source story may be a single inspiration away it may happen here at the summit we certainly hope so it's how we build the summit to engage you you may actually find it on this stage when I bring up some of the people who are about to follow me but this is why we tell open-source stories and open source stories live so each of you hopefully has a chance to think about you know your story and how it relates over source so please take advantage of all the things that are here at the summit and and find your inspiration if you if you haven't already so next thing is you know in a spirit of our telling open source stories today we're introducing our new documentary film the science of collective discovery it's really about citizen scientists using open systems to do serious science in their backyards and environmental areas and the like we're going to preview that I'm gonna prove it preview it today and then please come see it tonight later on when we preview the whole video so let's take a look I may not have a technical scientific background but I have one thing that the scientists don't have which is I know my backyard so conventional science happens outside of public view so it's kind of in this black box so most are up in the ivory tower and what's exciting about citizen science is that it brings it out into the open we as an environmental community are engaging with the physical world every day and you need tools to do that we needed to democratize that technology we need to make it lightweight we need to make it low-cost we needed to make it open source so that we could put that technology in the hands of everyday people so they go out and make those measurements where they live and where they breathe when you first hear about an environmental organization you mostly hear about planting trees gardens things like that you don't really think about things that are really going to affect you hey we're the air be more they'd hold it in their hand making sure not to cover the intake or the exhaust I just stand here we look at the world with forensic eyes and then we build what you can't see so the approach that we're really centered on puts humans and real issues at the center of the work and I think that's the really at the core of what open source is social value that underlies all of it it really refers to sort of the rights and responsibilities that anyone on the planet has to participate in making new discoveries so really awesome and a great story and you know please come enjoy the full video so now let's get on with our open stories live speakers you're going to really love the rest of the afternoon we have three keynotes and a demo built in and I can tell you without exaggeration that when you see and hear from the young people we're about to bring forward you know it's truly inspirational and it's gonna restore totally your enthusiasm for the future because you're gonna see some of the future leaders so please enjoy our open source stories live presentation is coming and I'll be back to join you in a little bit thanks very much please welcome code newbie founder Saran yep Eric good afternoon how y'all doing today oh that was pretty weak I think you could do better than that how y'all doing today wonderful much better I'm Saran I am the founder of code newbie we have the most supportive community of programmers and people learning to code this is my very first Red Hat summits I'm super pumped super excited to be here today I'm gonna give you a talk and I'm going to share with you the key to coding progress yes and in order to do that I'm gonna have to tell you a story so two years ago I was sitting in my hotel room and I was preparing for a big talk the next morning and usually the night before I give a big talk I'm super nervous I'm anxious I'm nauseous I'm wondering why I keep doing this to myself all the speakers backstage know exactly what I'm what I'm talking about and the night before my mom knows this so she almost always calls just to check in to see how I'm doing to see how I'm feeling and she called about midnight the night before and she said how are you how are you doing are you ready and I said you know what this time I feel really good I feel confident I think I'm gonna do a great job and the reason was because two months ago I'd already given that talk in fact just a few days prior they had published the video of that talk on YouTube and I got some really really good positive feedback I got feedback from emails and DMS and Twitter and I said man I know people really like this it's gonna be great in fact that video was the most viewed video of that conference and I said to my office said you know what let's see how many people loved my talk and still the good news is that 14 people liked it and a lot more people didn't and I saw this 8 hours before I'm supposed to give that exact same talk and I said mom I gotta call you back do you like how I did that to hang up the phone as if that's how cellphones work yeah and so I looked at this and I said oh my goodness clearly there's a huge disconnect I thought they were really liked they were I thought they were into it and this showed me that something was wrong what do you do what do you do when you're about to give that same talk in 8 hours how do you begin finding out what the problem is so you can fix it I have an idea let's read the comments you got to believe you gotta have some optimism come on I said let's read the comments because I'm sure we'll find some helpful feedback some constructive criticism some insights to help me figure out how to make this talk great so that didn't happen but I did find some really colorful language and some very creative ideas of what I could do with myself now there are some kids in the audience so I will not grace you with these comments but there was this one comment that did a really great job of capturing the sentiment of what everyone else was saying I can only show you the first part because the rest is not very family-friendly but it reads like this how do you talk about coding and not fake societal issues see the thing about that talk is it wasn't just a code talk it was a code and talk is about code and something else that talked touched on code and social justice I talked a lot about how the things that we build the way we build them affect real people and their problems and their struggles and that was absolutely not okay not okay we talk about code and code only not the social justice stuff it also talked about code and diversity yeah I think we all know the diversity is really about lowering the bar it forces us to talk about people and their issues and their problems in their history and we just don't do that okay absolutely inappropriate when it comes to a Tech Talk That Talk touched on code and feelings and feelings are squishy they're messy they're icky and a lot of us feel uncomfortable with feelings feelings have no place in technology no place in code we want to talk about code and code I want you to show me that API and when you show me that new framework that new tool that's gonna solve my problems that's all I care about I want to talk about code and give me some more code with it now I host a podcast called command line heroes it's an original podcast from Red Hat super excited about it if you haven't checked it out and totally should and what I love about this show as we talk about these really important moments and open swords these inflection points moments where we see progress we move forward and what I realized looking back at those episodes is all of those episodes have a code and something let's look at a few of those the first two episodes focused on the history of operating systems as a two-part episode part 1 and part 2 and there's lots of different ways we can talk about operating systems for these two episodes we started by talking about Windows and Mac OS and how these were two very powerful very popular operating systems but a lot of a lot of developers were frustrated with them they were closed you couldn't see inside you can see what it was doing and I the developer want to know what it's doing on my machine so we kind of had a little bit of a war one such developer who was very frustrated said I'm gonna go off and do my own thing my name is Linus this thing is Linux and I'm gonna rally all these other developers all these other people from all over the old to come together and build this new thing with me that is a code and moment in that case it was code and frustration it was a team of developers a world of developers literally old world of developers who said I'm frustrated I'm fed up I want something different and I'm gonna do something about it and what's really beautiful about frustration is it the sign of passion we're frustrated because we care because we care so much we love so deeply then we want to do something better next episode is the agile revolution this one was episode three now the agile revolution is a very very important moment in open-source and technology in general and this was in response to the way that we used to create products we used to give this huge stack of specs all these docs from the higher-ups and we'd take it and we go to our little corner and we lightly code and build and then a year with Pastor here's a pass a few years have passed and we'd finally burst forth with this new product and hope that users liked it and loved it and used it and I know something else will do that today it's okay no judgment now sometimes that worked and a lot of times it didn't but whether or not it actually worked it hurt it was painful these developers not enjoy this process so what happened a dozen developers got together and literally went off into their own and created something called the agile manifesto now this was another code and moment here it's code and anger these developers were so angry that they literally left civilization went off into a mountain to write the agile manifesto and what I love about this example is these developers did not work at the same company we're not on the same team they knew each other from different conferences and such but they really came from different survive and they agreed that they were so angry they were going to literally rewrite the way we created products next as an example DevOps tear down the wall this one is Episode four now this is a bit different because we're not talking about a piece of technology or even the way we code here we're talking about the way we work together the way that we collaborate and here we have our operations folks and our developers and we've created this new kind of weird place thing called DevOps and DevOps is interesting because we've gotten to a point where we have new tools new toys so that our developers can do a lot of the stuff that only the operations folks used to be able to do that thing that took days weeks months to set up I can do it with a slider it's kind of scary I can do it with a few buttons and here we have another code and moment and here that blink is fear for two reasons the operations focus is looking over the developer folks and thinking that was my job I used to be able to do that am I still valuable do I have a place in this future do I need to retrain there's also another fear which is those developers know what they're doing do they understand the security implications they appreciate how hard it is or something to scale and how to do that properly and I'm really interested in excited to see where we go with that where we take that emotion if we look at all of season one of the podcast we see that there's always a code and whether it's a code and frustration a code and anger or a code and fear it always boils down to code and feelings feelings are powerful in almost every single episode we see that that movement forward that progress is tied back to some type of Oshin and for a lot of us this is uncomfortable feelings make us feel weird and a lot of those YouTube commenters definitely do not like this whole feeling stuff don't be like those YouTube commenters there's one thing you take away from this whole talk let it be that don't be like these YouTube commenters feelings are incredibly powerful so the next time that you're working on a project you're having a conversation about a piece of software or a new piece of technology and you start to get it worked up you get angry you get frustrated maybe you get worried you get anxious you get scared I hope you recognize that feeling as a source of energy I hope you take that energy and you help us move forward I would take that to create the next inflection point that next step in the right direction feelings are your superpowers and I hope you use your powers for good thank you so much [Applause] please welcome jewel-box chief technology officer Sara Chipps [Music] Wow there's a lot of you out here how's it going I know there's a lot of you East Coasters here as well and I'm still catching up on that sleep so I hope you guys are having a great experience also my name is Sarah I'm here from New York I have been a software developer for 17 years it's longer than some of the people on stage today I've been alive big thanks to the folks at Red Hat for letting us come and tell you a little bit about jewel box so without further ado I'm gonna do exactly that okay so today we're gonna do a few things first I'm gonna tell you why we built jewel BOTS and why we think it's a really important technology I'm gonna show you some amazing magic and then we're gonna have one of the jewel bus experts come as a special guest and talk to you more about the deep technology behind what we're building so show hands in the audience who here was under 18 years old when they started coding it's hard for me to see you guys yep look around I'd have to say at least 50% of you have your hands up all right keep your hand up if you were under 15 when you started coding I think more hands up just what is it I don't know how that mouth works but awesome okay great yeah a little of I think about half of you half of you have your hands up that's really neat I've done a bunch of informal polls on the internet about this I found that probably about two-thirds of professional coders were under 18 when they started coding I myself was 11 I was a homeschooled kid so a little weird I'm part of the generation and some of you maybe as well is the reason we became coders is because we were lonely not because we made a lot of money so I was 11 this is before the internet was a thing and we had these things called BBS's and you would call up someone else's computer in your town and you would hang out with people and chat with them and play role-playing games with them it didn't have to be your town but if it wasn't your mom would yell at you for a long distance fees and I got really excited about computers and coding because of the community that I found online okay so this is sometimes the most controversial part of this presentation I promised you that they dominate our lives in many ways even if you don't even if you don't even know a 9 to 14 year old girl even if you just see them on the street sometimes they are deciding what you and I do on a regular basis hear me out for a second here so who here knows who this guy is okay you don't have to raise your hands but I think most people know who this guy is right so this guy used to be this guy and then teenage girls were like I think this guy has some talent to him I think that he's got a future and now he's a huge celebrity today what about this guy just got his first Oscar you know just kind of starting out well this guy used to be this guy and I'm proud to tell you that I am one of the many girls that discovered him and decided this guy has a future all right raise your hand if you listen to Taylor Swift just kidding I won't make you do it but awesome that's great so Taylor Swift we listen to Taylor Swift because these girls discovered Taylor Swift it wasn't a 35 year old that was like this Taylor Swift is pretty neat no one cares what we think but even bigger than that these huge unicorns that all of us some of us work for some of us wish we invented these were discovered by young teenage girls no one is checking to see what apps were using they're finding new communities in these thin in these platforms and saying this is how I want to commune with my friends things like Instagram snapchat and musically all start with this demographic and then we get our cues from them if you don't know what musically is I promise you ask your nearest 9 to 14 year old friend if you don't do that you'll hear about it in a few years but this demographic their futures are all at risk everyone here knows how much the field of software development is growing and how important technical literacy is to the future of our youth however just 18% of computer science graduates are girls just 19% of AP computer science test takers and just 15% of Google's tech force identify as female so we decided to do something about that we were inspired by platforms like MySpace and Geocities things like Neopets and minecraft all places where kids find something they love and they're like okay to make this better all I have to do is learn how to code I can totally do that and so we wanted to do that so we talked to 200 girls we went to schools we sat down with them and we were like what makes you tick what are you excited about and what we heard from them over and over again is their friends their friends and their community are pivotal to them and this time in their lives so when we started talking to them about a smart friendship bracelet that's when they started really freaking out so we built Jewel BOTS and Jewel BOTS has an active online community where girls can work together share code that they've built and learn from each other help each other troubleshoot sometimes the way they work is when you are near your friends your bracelets light up the same color and you can use them to send secret messages to each other and you can also code them so you can say things like when all my swimming friends are together in the same room all of our bracelets should go rainbow colors which is really fun you can even build games jewel BOTS started shipping about a year and a half ago about after a lot of work and we are about to ship our 12,000 jewel bot we're in 38 city sorry 38 countries and we're just getting started okay so now it's time for the magic and I have an important question does anyone here want to be my friend pick me all right someone today Gary oh I don't have many friends that's awesome I'm so glad that we'll be friends okay it's awesome so we just need to pair our jewel BA okay okay and in order to do that we're gonna hold the magic button in the middle down for two seconds so one locomotive two locomotive great and then we got a white flashing I'm gonna do yours again I did it wrong locomotive two locomotive it's we're adults we can't do it okay it's a good that are smart alright so now we get to pick our friendship color I'm gonna pick red hat red does that work for you sure okay great so now I just picked a red hat red and my jewel bot is saying alright Tim's jewel bot do you want to be my friend and imageable about it's like I'm thinking about it I think so okay now we're ready okay great so now we're red friends when we're together our bracelets are going to be red and I will send you a secret message when it's time for you to come out and trip and introduce the next guest awesome well thank you so much thank you tailor gun so glad we could be friends and if only people would start following me on Twitter it'd be a great day awesome alright so now you can see the not so technical part of jewel box they use bluetooth to sense when your friends are nearby so they would work in about a 30 meter hundred foot range but to tell you about the actual technology part I'm going to introduce is someone much more qualified than I am so Ellie is one of our jewel box ambassadors she's an amazing YouTube channel that I would please ask you to check out and subscribe she's le G Joel BOTS on YouTube she's an amazing coder and I'm really excited to introduce you today to Ellie Galloway come on out Ellie [Applause] hello my name is le gallais I'm gonna show you how I got coding and then show you some coding in action I first started coding at a6 when my dad helped me code a game soon after I program form a code for Minecraft then my dad had shown me jo bot I keep coding because it helps people for instance for instance you could code auto crack to make it a lot smarter so it can help make people stay run faster but what about something more serious what if you could help answer 911 calls and give alerts before we start I have three main steps to share with you I often use these steps to encoding my jaw bot and continue to use some of these now step one read the instructions and in other words this means for Jabba to memorize the colors and positions a way to memorize these because it's tricky is to remember all the colors and positions you O type will be capital and remember that the positions are either short for north west south west north east and south east step to learn the basic codes when it comes to coding you need to work your way up step 3 discover feel free to discover once you mastered everything now let's get to coding let's use or let's first use combining lights so under void loop I'm going to put LED turn on single s/w and blue and before we make sure that this works we got to put LED LED okay now let's type this again LED dot turn on single now let's do SW green now we have our first sketch so let's explain what this means led LED is a function that to control the LED lights LED turn on single SW blue tells that SW light to turn blue and green flashes so quickly with the blue it creates aqua now let's do another code lets you i'm going to use a more advanced command to make a custom color using RGB let's use a soft pink using 255 105 and 180 now let's type this in the button press function so let's do LED led LED dot set light and now we can do let's do position 3 255 105 and 180 now let's explain what this means the first one stands for the position the three others stand for red green and blue our GPS can only go up to 255 but there are 256 levels but if you count the first one as zero then get 255 so let's first before we move on let's show how this works so this is it before and now let's turn it on to see how our aqua turned out now let's see how our RGB light turned out so we are looking for a soft pink so let's see how it looks think about how much the code you write can help people all around the world these are ideas are just the beginning of opening a new world in technology a fresh start is right around the corner I hope this helped you learn a little bit about coding and even made you want to try it out for yourself thank you [Applause] alright alright alright I need your help for a second guys alright one second really really fascinating we're short on time today is Ellie's 11th birthday and I think we should give her the biggest present that she's gonna get today and it's something none of us have experienced and that is thousands of people saying happy birthday Elliott wants so when I say three can I get a happy birthday Elly one two three happy birthday Elly great job that's the best part of my job okay so those are that's two of us we're just getting started this numbers out Dana would almost shipped 12,000 jewel BOTS and what I'm really excited to tell you about is that 44% of our users don't just play with their jewel bots they code them and they're coding C do you even code C I don't know that you do but we have 8 to 14 year olds coding C for their jewel box we also have hundreds of events where kids come and they learn how to code for the first time here's how you can help we're open source so check out our github get involved our communities online you can see the different features that people's are asking for we're also doing events all over the world a lot of people are hosting them at their companies if you're interested in doing so reach out to us thank you so much for coming and learning about jewel box today enjoy the rest of your summit [Music] ladies and gentlemen please welcome hacker femme au founder Femi who Bois de Kunz [Music] good afternoon red hat summit 2018 i'm femi holiday combs founder of hacker femme Oh I started coding when I was 8 when I was 9 I set up South London raspberry jam through crowdfunding to share my passion for coding with other young people who might not otherwise be exposed to tech since then I've run hundreds of coding and robot workshops across the UK and globally in 2017 I was awarded an inaugural legacy Diana award by their Royal Highnesses Prince William and Prince Harry my service and community we welcome young people who have autism or like me tract syndrome because coding linked me up to a wider community of like-minded people and I'm trying to do the same for those who might also benefit from this I also deliver workshops to corporate companies and public organizations whilst feeding back ideas and resources into my community work we like to cascade our knowledge and experience to other young coders so that they can benefit too we're learning new tech every day we're starting to use github to document and manage our coding projects we've no dread we're using the terminal and beginning to really appreciate Linux as we explore cybersecurity and blockchain it's been quite a journey from South London to the world-famous Tate Modern museum to Bangladesh to this my first trip to the States and soon to China where I hope to translate my microwave workshops into Mandarin on this journey I'm noticed it is increasingly important for young coders to have collaborative and community led initiatives and enterprise and career ready skills so my vision now is to run monthly meetups and in collaboration with business partners help a hundred young disadvantaged people to get jobs in the digital services in fact out of all the lessons I've learned from teaching young coders they all have one thing in common the power of open source and the importance of developing community and today I want to talk about three of those lessons the value of reaching out and collaborating the importance of partnering event price and the ability to self organize and persist which translated into English means having a can-do attitude getting stuff done when you reach out when you show curiosity you realize you're not alone in this diverse community no matter who you are and where you're from from coding with minecraft to meeting other young people with jams I found there are people like me doing things I like doing I get to connect with them that's where open-source comes to the fourth second the open source community is so vast then it crosses continents it's so immersed perspectives that it can take you to amazing places out of space even that's my code running on the International Space Station's Columbus module let's take a lesson and playing was an audio representation for the frequencies recorded in space my team developed Python code to measure and store frequency readings from the space station and that was down linked back to earth to my email box Thomas who's 10 developed an audio file using audacity and importing it back into Python how cool is that Trulli collaboration can take you places you never thought possible because that's how the community works when you throw a dilemma a problem a tip the open source community comes back with answers when you give the community gives back tenfold that's how open source expands but in that vast starscape how do you know what to focus on there are so many problems to solve where do I start your world enterprice enterprise software is very good at solving problems what's the big problem how about helping the next generation be ready for the future I want to do more for the young coding community so I'm developing entrepreneurial business links to get that done this is a way to promote pathways to deal with future business problems whether in FinTech healthcare or supply chains a meeting the skill shortage it is a case for emerging in it's a case for investing in emerging communities and young change enablers throwing a wider net equates to being fully inclusive with a good representation of diversity you know under the shadow of the iconic show back in London there are pockets of deprivation where young people can't even get a job in a supermarket many of them are interested in tech in some way so my goal for the next three years is to encourage young people to become an active part of the coding community with open source we have the keys to unlock the potential for future innovation and technological development with young coders we have the people who have to face these problems working on them now troubleshooting being creative connecting with each other finding a community discovering their strengths along the way for me after running workshops in the community for a number of years when I returned from introducing coding to young street kids in Bangladesh I realized I had skills and experience so I set up my business hacker Famicom my first monetized fehmi's coding boot camp at Rice London Barclays Bank it was a sellout and a few weeks later shows my second I haven't looked back since but it works the opposite way - all the money raised enable me to buy robots for my community events and I was able to cascade my end price knowledge across to other young coders - when you focus on business problems you get active enthusiastic support from enterprise and then you can take on anything the support is great and we have tons of ideas but what does it really take to execute on those ideas to get things done can-do attitudes what open source needs you've seen it all this week we're all explorers ideator z' thinkers and doers open source needs people who can make the ideas happen get out there and see them through like I did setting up Safford and raspberry jam as an inclusive space to collaborate and learn together and that that led to organizing the young coders conference this was about organizing our own two-day event for our partners in industry to show they value young people and wanted to invest in our growth it doesn't stop there oh nice now I'm setting up monthly coding meetups and looking at ways to help other young people to access job opportunities in end price and digital services the underlying ethos remains the same in all I do promoting young people with the desire to explore collaborative problem-solving when coding digital making and building enterprise you fled having the confidence to define our journey and pathways always being inclusive always encouraging innovation and creativity being doers does more than get projects done makes us a pioneering force in the community dreaming and doing is how we will make exponential leaps my generation is standing on the shoulders of giants you the open-source pioneers and the technology you will built so I'd love to hear about your experiences who brought you into the open-source community who taught you as we go to upscale our efforts we encounter difficulties have you and how did you overcome them please do come to talk to me I'll be in the open-source stories booth both today and tomorrow giving workshops or visit the Red Hat page of my website hack Famicom I really value your insights in conclusion I'd like I'd like to ask you to challenge yourself you can do this by supporting young coders find the crowdfunding campaign kick-start their ideas into reality I'm proof that it works it's so awesome to be an active part of the next exponential leap together thank you [Applause] so unbelievable huh you know he reminds me of be at that age not even close and I can tell you I've spent a lot of time with Femi and his mom grace I mean what you see is what you get I mean he's incredibly passionate committed and all that stuff he's doing that long list of things he's doing he's going to do so hopefully today you get a sense of what's coming in the next generation the amazing things that people are doing with collaboration I'd also like to thank in addition to femi I'd like to thank Sauron Sarah and Ellie for equally compelling talks around the open source stories and again as I mentioned before any one of you can have an open source story that can be up here inspiring others and that's really our goal in telling these stories and giving voice to the things that you've seen today absolutely extraordinary things are happening out there and I encourage you to take every advantage you can hear this week and as is our theme for the summit please keep exploring thank you very much [Applause] [Music]

[Music] [Music] [Music] [Music] [Music] [Music] that will be successful in the 21st century [Music] being open is really important because it comes with a lot of trust the open-source community now has matured so much and that contribution from the community is really driving innovation [Music] but what's really exciting is the change that we've seen in our teams not only the way they collaborate but the way they operate in the way they work [Music] I think idea is everything ideas can change the way you see things open-source is more than a license it's actually a way of operating [Music] ladies and gentlemen please welcome Red Hat president and chief executive officer Jim Whitehurst [Music] all right well welcome to day two at the Red Hat summit I'm amazed to see this many people here at 8:30 in the morning given the number of people I saw pretty late last night out and about so thank you for being here and have to give a shout out speaking of power participation that DJ is was Mike Walker who is our global director of open innovation labs so really enjoyed that this morning was great to have him doing that so hey so day one yesterday we had some phenomenal announcements both around Red Hat products and things that we're doing as well as some great partner announcements which we found exciting I hope they were interesting to you and I hope you had a chance to learn a little more about that and enjoy the breakout sessions that we had yesterday so yesterday was a lot about the what with these announcements and partnerships today I wanted to spin this morning talking a little bit more about the how right how do we actually survive and thrive in this digitally transformed world and to some extent the easy parts identifying the problem we all know that we have to be able to move more quickly we all know that we have to be able to react to change faster and we all know that we need to innovate more effectively all right so the problem is easy but how do you actually go about solving that right the problem is that's not a product that you can buy off the shelf right it is a capability that you have to build and certainly it's technology enabled but it's also depends on process culture a whole bunch of things to figure out how we actually do that and the answer is likely to be different in different organizations with different objective functions and different starting points right so this is a challenge that we all need to feel our way to an answer on and so I want to spend some time today talking about what we've seen in the market and how people are working to address that and it's one of the reasons that the summit this year the theme is ideas worth it lorring to take us back on a little history lesson so two years ago here at Moscone the theme of the summit was the power of participation and then I talked a lot about the power of groups of people working together and participating are able to solve problems much more quickly and much more effectively than individuals or even individual organizations working by themselves and some of the largest problems that we face in technology but more broadly in the world will ultimately only be solved if we effectively participate and work together then last year the theme of the summit was the impact of the individual and we took this concept of participation a bit further and we talked about how participation has to be active right it's a this isn't something where you can be passive that you can sit back you have to be involved because the problem in a more participative type community is that there is no road map right you can't sit back and wait for an edict on high or some central planning or some central authority to tell you what to do you have to take initiative you have to get involved right this is a active participation sport now one of the things that I talked about as part of that was that planning was dead and it was kind of a key my I think my keynote was actually titled planning is dead and the concept was that in a world that's less knowable when we're solving problems in a more organic bottom-up way our ability to effectively plan into the future it's much less than it was in the past and this idea that you're gonna be able to plan for success and then build to it it really is being replaced by a more bottom-up participative approach now aside from my whole strategic planning team kind of being up in arms saying what are you saying planning is dead I have multiple times had people say to me well I get that point but I still need to prepare for the future how do I prepare my organization for the future isn't that planning and so I wanted to spend a couple minutes talk a little more detail about what I meant by that but importantly taking our own advice we spent a lot of time this past year looking around at what our customers are doing because what a better place to learn then from large companies and small companies around the world information technology organizations having to work to solve these problems for their organizations and so our ability to learn from each other take the power of participation an individual initiative that people and organizations have taken there are just so many great learnings this year that I want to get a chance to share I also thought rather than listening to me do that that we could actually highlight some of the people who are doing this and so I do want to spend about five minutes kind of contextualizing what we're going to go through over the next hour or so and some of the lessons learned but then we want to share some real-world stories of how organizations are attacking some of these problems under this how do we be successful in a world of constant change in uncertainty so just going back a little bit more to last year talking about planning was dead when I said planning it's kind of a planning writ large and so that's if you think about the way traditional organizations work to solve problems and ultimately execute you start off planning so what's a position you want to get to in X years and whether that's a competitive strategy in a position of competitive advantage or a certain position you want an organizational function to reach you kind of lay out a plan to get there you then typically a senior leaders or a planning team prescribes the sets of activities and the organization structure and the other components required to get there and then ultimately execution is about driving compliance against that plan and you look at you say well that's all logical right we plan for something we then figure out how we're gonna get there we go execute to get there and you know in a traditional world that was easy and still some of this makes sense I don't say throw out all of this but you have to recognize in a more uncertain volatile world where you can be blindsided by orthogonal competitors coming in and you the term uber eyes you have to recognize that you can't always plan or know what the future is and so if you don't well then what replaces the traditional model or certainly how do you augment the traditional model to be successful in a world that you knows ambiguous well what we've heard from customers and what you'll see examples of this through the course of this morning planning is can be replaced by configuring so you can configure for a constant rate of change without necessarily having to know what that change is this idea of prescription of here's the activities people need to perform and let's lay these out very very crisply job descriptions what organizations are going to do can be replaced by a greater degree of enablement right so this idea of how do you enable people with the knowledge and things that they need to be able to make the right decisions and then ultimately this idea of execution as compliance can be replaced by a greater level of engagement of people across the organization to ultimately be able to react at a faster speed to the changes that happen so just double clicking in each of those for a couple minutes so what I mean by configure for constant change so again we don't know exactly what the change is going to be but we know it's going to happen and last year I talked a little bit about a process solution to that problem I called it that you have to try learn modify and what that model try learn modify was for anybody in the app dev space it was basically taking the principles of agile and DevOps and applying those more broadly to business processes in technology organizations and ultimately organizations broadly this idea of you don't have to know what your ultimate destination is but you can try and experiment you can learn from those things and you can move forward and so that I do think in technology organizations we've seen tremendous progress even over the last year as organizations are adopting agile endeavor and so that still continues to be I think a great way for people to to configure their processes for change but this year we've seen some great examples of organizations taking a different tack to that problem and that's literally building modularity into their structures themselves right actually building the idea that change is going to happen into how you're laying out your technology architectures right we've all seen the reverse of that when you build these optimized systems for you know kind of one environment you kind of flip over two years later what was the optimized system it's now called a legacy system that needs to be migrated that's an optimized system that now has to be moved to a new environment because the world has changed so again you'll see a great example of that in a few minutes here on stage next this concept of enabled double-clicking on that a little bit so much of what we've done in technology over the past few years has been around automation how do we actually replace things that people were doing with technology or augmenting what people are doing with technology and that's incredibly important and that's work that can continue to go forward it needs to happen it's not really what I'm talking about here though enablement in this case it's much more around how do you make sure individuals are getting the context they need how are you making sure that they're getting the information they need how are you making sure they're getting the tools they need to make decisions on the spot so it's less about automating what people are doing and more about how can you better enable people with tools and technology now from a leadership perspective that's around making sure people understand the strategy of the company the context in which they're working in making sure you've set the appropriate values etc etc from a technology perspective that's ensuring that you're building the right systems that allow the right information the right tools at the right time to the right people now to some extent even that might not be hard but when the world is constantly changing that gets to be even harder and I think that's one of the reasons we see a lot of traction and open source to solve these problems to use flexible systems to help enterprises be able to enable their people not just in it today but to be flexible going forward and again we'll see some great examples of that and finally engagement so again if execution can't be around driving compliance to a plan because you no longer have this kind of Cris plan well what do leaders do how do organizations operate and so you know I'll broadly use the term engagement several of our customers have used this term and this is really saying well how do you engage your people in real-time to make the right decisions how do you accelerate a pace of cadence how do you operate at a different speed so you can react to change and take advantage of opportunities as they arise and everywhere we look IT is a key enabler of this right in the past IT was often seen as an inhibitor to this because the IT systems move slower than the business might want to move but we are seeing with some of these new technologies that literally IT is becoming the enabler and driving the pace of change back on to the business and you'll again see some great examples of that as well so again rather than listen to me sit here and theoretically talk about these things or refer to what we've seen others doing I thought it'd be much more interesting to bring some of our partners and our customers up here to specifically talk about what they're doing so I'm really excited to have a great group of customers who have agreed to stand in front of 7,500 people or however many here this morning and talk a little bit more about what they're doing so really excited to have them here and really appreciate all them agreeing to be a part of this and so to start I want to start with tee systems we have the CEO of tee systems here and I think this is a great story because they're really two parts to it right because he has two perspectives one is as the CEO of a global company itself having to navigate its way through digital disruption and as a global cloud service provider obviously helping its customers through this same type of change so I'm really thrilled to have a del hasta li join me on stage to talk a little bit about T systems and what they're doing and what we're doing jointly together so Adelle [Music] Jim took to see you Adele thank you for being here you for having me please join me I love to DJ when that fantastic we may have to hire him no more events for events where's well employed he's well employed though here that team do not give him mics activation it's great to have you here really do appreciate it well you're the CEO of a large organization that's going through this disruption in the same way we are I'd love to hear a little bit how for your company you're thinking about you know navigating this change that we're going through great well you know key systems as an ICT service provider we've been around for decades I'm not different to many of our clients we had to change the whole disruption of the cloud and digitization and new skills and new capability and agility it's something we had to face as well so over the last five years and especially in the last three years we invested heavily invested over a billion euros in building new capabilities building new offerings new infrastructures to support our clients so to be very disruptive for us as well and so and then with your customers themselves they're going through this set of change and you're working to help them how are you working to help enable your your customers as they're going through this change well you know all of them you know in this journey of changing the way they run their business leveraging IT much more to drive business results digitization and they're all looking for new skills new ideas they're looking for platforms that take them away from traditional waterfall development that takes a year or a year and a half before they see any results to processes and ways of bringing applications in a week in a month etcetera so it's it's we are part of that journey with them helping them for that and speaking of that I know we're working together and to help our joint customers with that can you talk a little bit more about what we're doing together sure well you know our relationship goes back years and years with with the Enterprise Linux but over the last few years we've invested heavily in OpenShift and OpenStack to build peope as layers to build you know flexible infrastructure for our clients and we've been working with you we tested many different technology in the marketplace and been more successful with Red Hat and the stack there and I'll give you an applique an example several large European car manufacturers who have connected cars now as a given have been accelerating the applications that needed to be in the car and in the past it took them years if not you know scores to get an application into the car and today we're using open shift as the past layer to develop to enable these DevOps for these companies and they bring applications in less than a month and it's a huge change in the dynamics of the competitiveness in the marketplace and we rely on your team and in helping us drive that capability to our clients yeah do you find it fascinating so many of the stories that you hear and that we've talked about with with our customers is this need for speed and this ability to accelerate and enable a greater degree of innovation by simply accelerating what what we're seeing with our customers absolutely with that plus you know the speed is important agility is really critical but doing it securely doing it doing it in a way that is not gonna destabilize the you know the broader ecosystem is really critical and things like GDP are which is a new security standard in Europe is something that a lot of our customers worry about they need help with and we're one of the partners that know what that really is all about and how to navigate within that and use not prevent them from using the new technologies yeah I will say it isn't just the speed of the external but the security and the regulation especially GDR we have spent an hour on that with our board this week there you go he said well thank you so much for being here really to appreciate the work that we're doing together and look forward to continued same here thank you thank you [Applause] we've had a great partnership with tea systems over the years and we've really taken it to the next level and what's really exciting about that is you know we've moved beyond just helping kind of host systems for our customers we really are jointly enabling their success and it's really exciting and we're really excited about what we're able to to jointly accomplish so next i'm really excited that we have our innovation award winners here and we'll have on stage with us our innovation award winners this year our BBVA dnm IAG lasat Lufthansa Technik and UPS and yet they're all working in one for specific technology initiatives that they're doing that really really stand out and are really really exciting you'll have a chance to learn a lot more about those through the course of the event over the next couple of days but in this context what I found fascinating is they were each addressing a different point of this configure enable engage and I thought it would be really great for you all to hear about how they're experimenting and working to solve these problems you know real-time large organizations you know happening now let's start with the video to see what they think about when they think about innovation I define innovation is something that's changing the model changing the way of thinking not just a step change improvement not just making something better but actually taking a look at what already exists and then putting them together in new and exciting lives innovation is about to build something nobody has done before historically we had a statement that business drives technology we flip that equation around an IT is now demonstrating to the business at power of technology innovation desde el punto de vista de la tecnología supone salir de plataform as proprietary as ADA Madero cloud basado an open source it's a possibility the open source que no parameter no sir Kamala and I think way that for me open-source stands for flexibility speed security the community and that contribution from the community is really driving innovation innovation at a pace that I don't think our one individual organization could actually do ourselves right so first I'd like to talk with BBVA I love this story because as you know Financial Services is going through a massive set of transformations and BBVA really is at the leading edge of thinking about how to deploy a hybrid cloud strategy and kind of modular layered architecture to be successful regardless of what happens in the future so with that I'd like to welcome on stage Jose Maria Rosetta from BBVA [Music] thank you for being here and congratulations on your innovation award it's been a pleasure to be here with you it's great to have you hi everybody so Josemaria for those who might not be familiar with BBVA can you give us a little bit of background on your company yeah a brief description BBVA is is a bank as a financial institution with diversified business model and that provides well financial services to more than 73 million of customers in more than 20 countries great and I know we've worked with you for a long time so we appreciate that the partnership with you so I thought I'd start with a really easy question for you how will blockchain you know impact financial services in the next five years I've gotten no idea but if someone knows the answer I've got a job for him for him up a pretty good job indeed you know oh all right well let me go a little easier then so how will the global payments industry change in the next you know four or five years five years well I think you need a a Weezer well I tried to make my best prediction means that in five years just probably will be five years older good answer I like that I always abstract up I hope so I hope so yah-yah-yah hope so good point so you know immediately that's the obvious question you have a massive technology infrastructure is a global bank how do you prepare yourself to enable the organization to be successful when you really don't know what the future is gonna be well global banks and wealth BBBS a global gam Bank a certain component foundations you know today I would like to talk about risk and efficiency so World Bank's deal with risk with the market great the operational reputational risk and so on so risk control is part of all or DNA you know and when you've got millions of customers you know efficiency efficiency is a must so I think there's no problem with all these foundations they problem the problem analyze the problems appears when when banks translate these foundations is valued into technology so risk control or risk management avoid risk usually means by the most expensive proprietary technology in the market you know from one of the biggest software companies in the world you know so probably all of you there are so those people in the room were glad to hear you say that yeah probably my guess the name of those companies around San Francisco most of them and efficiency usually means a savory business unit as every department or country has his own specific needs by a specific solution for them so imagine yourself working in a data center full of silos with many different Hardware operating systems different languages and complex interfaces to communicate among them you know not always documented what really never documented so your life your life in is not easy you know in this scenario are well there's no room for innovation so what's been or or strategy be BES ready to move forward in this new digital world well we've chosen a different approach which is quite simple is to replace all local proprietary system by a global platform based on on open source with three main goals you know the first one is reduce the average transaction cost to one-third the second one is increase or developers productivity five times you know and the third is enable or delete the business be able to deliver solutions of three times faster so you're not quite easy Wow and everything with the same reliability as on security standards as we've got today Wow that is an extraordinary set of objectives and I will say their world on the path of making that successful which is just amazing yeah okay this is a long journey sometimes a tough journey you know to be honest so we decided to partnership with the with the best companies in there in the world and world record we think rate cut is one of these companies so we think or your values and your knowledge is critical for BBVA and well as I mentioned before our collaboration started some time ago you know and just an example in today in BBVA a Spain being one of the biggest banks in in the country you know and using red hat technology of course our firm and fronting architecture you know for mobile and internet channels runs the ninety five percent of our customers request this is approximately 3,000 requests per second and our back in architecture execute 70 millions of business transactions a day this is almost a 50% of total online transactions executed in the country so it's all running yes running I hope so you check for you came on stage it's I'll be flying you know okay good there's no wood up here to knock on it's been a really great partnership it's been a pleasure yeah thank you so much for being here thank you thank you [Applause] I do love that story because again so much of what we talk about when we when we talk about preparing for digital is a processed solution and again things like agile and DevOps and modular izing components of work but this idea of thinking about platforms broadly and how they can run anywhere and actually delivering it delivering at a scale it's just a phenomenal project and experience and in the progress they've made it's a great team so next up we have two organizations that have done an exceptional job of enabling their people with the right information and the tools they need to be successful you know in both of these cases these are organizations who are under constant change and so leveraging the power of open-source to help them build these tools to enable and you'll see it the size and the scale of these in two very very different contexts it's great to see and so I'd like to welcome on stage Oh smart alza' with dnm and David Abraham's with IAG [Music] Oh smart welcome thank you so much for being here Dave great to see you thank you appreciate you being here and congratulations to you both on winning the Innovation Awards thank you so Omar I really found your story fascinating and how you're able to enable your people with data which is just significantly accelerated the pace with which they can make decisions and accelerate your ability to to act could you tell us a little more about the project and then what you're doing Jim and Tina when the muchisimas gracias por ever say interesado pono true projecto [Music] encargado registry controller las entradas a leda's persona por la Frontera argentina yo sé de dos siento treinta siete puestos de contrôle tienen lo largo de la Frontera tanto area the restreamer it EEMA e if looool in dilute ammonia shame or cinta me Jonas the tránsito sacra he trod on in another Fronteras dingus idea idea de la Magneto la cual estamos hablando la Frontera cantina tienen extension the kin same in kilo metros esto es el gada mint a maje or allege Estancia kaeun a poor carretera a la co de mexico con el akka a direction emulation s tambien o torgul premios de de residencia control a la permanencia de los rancheros en argentina pero básicamente nuestra área es prevenir que persona que estén in curie end o en delito transnational tipo pero remo trata de personas tráfico de armas sunday muy gravis SI yo que nosotros a Samos es para venir aquí es uno para que nadie meso and he saw some vetoes pueden entrada al Argentine establecer see not replaceable Terry Antone see koalas jenner are Yap liquor make animo para que - no Korra NL Angelo Millie see sighs a partir de la o doc mil DC says turmoil affirm a decision de cambiar de un sistema reactive Oh foreign c'est un sistema predict TiVo say Previn TiVo yes I don't empezamos s target area con el con las Judah in appreciable de la gente del canto la tarea el desafío era integra todo es desconocido vasa de datos propias estructura Radha's no instruct Radha's propias del organ is mo y de otros Organa Mo's del estado y tambien integral akan el mundo si si si como cinta yo el lo controls the Interpol o empezamos @n información anticipable pasajeros a travell CT ma p tambien intent ahmo's controller latrans Sybilla de en los happiness a través de en er de todo esto fue possible otra vez de la generation dune irreparable econo penchev y la virtualization de datos si esto fue fundamental por que entra moseyin una schema se en un modelo de intelligent a artificial eden machine learning KD o por resultado jimmy esto que todas esas de datos integral as tanto Nacional como Internacional A's le provision a nuestros nuestras an Aleta que antes del don't build Isis ice tenían que buscar say información integral Adel diferentes sistema z-- c yatin de Chivo manuals tarde Ando auras odious en algunos casos a tener toda la información consolidate a integra dope or poor pasajero en tiempo real esto que hizo mejor Oh el tiempo y la calidad de la toma de decisiones de nuestros durante la gente / dueño and affinity regime de lo que se trata esto es simplemente mejor our la calidad de vida de atras de mettre personas SI y meet our que el delito perform a trois Natura from Dana's Argentine sigue siendo en favor de esto SI temes uno de los países mess Alberto's Allah immigration en Latin America yah hora con una plataforma mas segunda first of all I want to thank you for the interest is played for our project the National migration administration or diem records the entry and exit of people on the Argentine territory it grants residents permits to foreigners who wish to live in our country through 237 entry points land air border sea and river ways Jim dnm registered over 80 million transits throughout last year Argentine borders cover about 15,000 kilometers just our just to give you an idea of the magnitude of our borders this is greater than the distance on a highway between Mexico City and Alaska our department applies the mechanisms that prevent the entry and residents of people involved in crimes like terrorism trafficking of persons weapons drugs and others in 2016 we shifted to a more preventive and predictive paradigm that is how Sam's the system for migration analysis was created with red hats great assistance and support this allowed us to tackle the challenge of integrating multiple and varied issues legal issues police databases national and international security organizations like Interpol API advanced passenger information and PNR passenger name record this involved starting private cloud with OpenShift Rev data virtualization cloud forms and fuse that were the basis to develop Sam and implementing machine learning models and artificial intelligence our analysts consulted a number of systems and other manual files before 2016 4 days for each person entering or leaving the country so this has allowed us to optimize our decisions making them in real time each time Sam is consulted it processes patterns of over two billion data entries Sam's aim is to improve the quality of life of our citizens and visitors making sure that crime doesn't pierce our borders in an environment of analytic evolution and constant improvement in essence Sam contributes toward Argentina being one of the leaders in Latin America in terms of immigration with our new system great thank you and and so Dave tell us a little more about the insurance industry and the challenges in the EU face yeah sure so you know in the insurance industry it's a it's been a bit sort of insulated from a lot of major change in disruption just purely from the fact that it's highly regulated and the cost of so that the barrier to entry is quite high in fact if you think about insurance you know you have to have capital reserves to protect against those major events like floods bush fires and so on but the whole thing is a lot of change there's come in a really rapid pace I'm also in the areas of customer expectations you know customers and now looking and expecting for the same levels of flexibility and convenience that they would experience with more modern and new startups they're expecting out of the older institutions like banks and insurance companies like us so definitely expecting the industry to to be a lot more adaptable and to better meet their needs I think the other aspect of it really is in the data the data area where I think that the donor is now creating a much more significant connection between organizations in a car summers especially when you think about the level of devices that are now enabled and the sheer growth of data that's that that's growing at exponential rates so so that the impact then is that the systems that we used to rely on are the technology we used to rely on to be able to handle that kind of growth no longer keeps up and is able to to you know build for the future so we need to sort of change that so what I G's really doing is transform transforming the organization to become a lot more efficient focus more on customers and and really set ourselves up to be agile and adaptive and so ya know as part of your Innovation Award that the specific set of projects you tied a huge amount of different disparate systems together and with M&A and other you have a lot to do there to you tell us a little more about kind of how you're able to better respond to customer needs by being able to do that yeah no you're right so we've we've we're nearly a hundred year old company that's grown from lots of merger and acquisition and just as a result of that that means that data's been sort of spread out and fragmented across multiple brands and multiple products and so the number one sort of issue and problem that we were hearing was that it was too hard to get access to data and it's highly complicated which is not great from a company from our perspective really because because we are a data company right that's what we do we we collect data about people what they what's important to them what they value and the environment in which they live so that we can understand that risk and better manage and protect those people so what we're doing is we're trying to make and what we have been doing is making data more open and accessible and and by that I mean making data more of easily available for people to use it to make decisions in their day-to-day activity and to do that what we've done is built a single data platform across the group that unifies the data into a single source of truth that we can then build on top of that single views of customers for example that puts the right information into the into the hands of the people that need it the most and so now why does open source play such a big part in doing that I know there are a lot of different solutions that could get you there sure well firstly I think I've been sauce has been k2 these and really it's been key because we've basically started started from scratch to build this this new next-generation data platform based on entirely open-source you know using great components like Kafka and Postgres and airflow and and and and and then fundamentally building on top of red Red Hat OpenStack right to power all that and they give us the flexibility that we need to be able to make things happen much faster for example we were just talking to the pivotal guys earlier this week here and some of the stuff that we're doing they're they're things quite interesting innovative writes even sort of maybe first in the world where we've taken the older sort of appliance and dedicated sort of massive parallel processing unit and ported that over onto red Red Hat OpenStack right which is now giving us a lot more flexibility for scale in a much more efficient way but you're right though that we've come from in the past a more traditional approach to to using vendor based technology right which was good back then when you know technology solutions could last for around 10 years or so on and and that was fine but now that we need to move much faster we've had to rethink that and and so our focus has been on using you know more commoditized open source technology built by communities to give us that adaptability and sort of remove the locking in there any entrenchment of technology so that's really helped us but but I think that the last point that's been really critical to us is is answering that that concern and question about ongoing support and maintenance right so you know in a regular environment the regulator is really concerned about anything that could fundamentally impact business operation and and so the question is always about what happens when something goes wrong who's going to be there to support you which is where the value of the the partnership we have with Red Hat has really come into its own right and what what it's done is is it's actually giving us the best of both worlds a means that we can we can leverage and use and and and you know take some of the technology that's being developed by great communities in the open source way but also partner with a trusted partner in red had to say you know they're going to stand behind that community and provide that support when we needed the most so that's been the kind of the real value out of that partnership okay well I appreciate I love the story it's how do you move quickly leverage the power community but do it in a safe secure way and I love the idea of your literally empowering people with machine learning and AI at the moment when they need it it's just an incredible story so thank you so much for being here appreciate it thank you [Applause] you know again you see in these the the importance of enabling people with data and in an old-world was so much data was created with a system in mind versus data is a separate asset that needs to be available real time to anyone is a theme we hear over and over and over again and so you know really looking at open source solutions that allow that flexibility and keep data from getting locked into proprietary silos you know is a theme that we've I've heard over and over over the past year with many of our customers so I love logistics I'm a geek that way I come from that background in the past and I know that running large complex operations requires flawless execution and that requires great data and we have two great examples today around how to engage own organizations in new and more effective ways in the case of lufthansa technik literally IT became the business so it wasn't enabling the business it became the business offering and importantly went from idea to delivery to customers in a hundred days and so this theme of speed and the importance of speed it's a it's a great story you'll hear more about and then also at UPS UPS again I talked a little earlier about IT used to be kind of the long pole in the tent the thing that was slow moving because of the technology but UPS is showing that IT can actually drive the business and the cadence of business even faster by demonstrating the power and potential of technology to engage in this case hundreds of thousands of people to make decisions real-time in the face of obviously constant change around weather mechanicals and all the different things that can happen in a large logistics operation like that so I'd like to welcome on stage to be us more from Lufthansa Technik and Nick Castillo from ups to be us welcome thank you for being here Nick thank you thank you Jim and congratulations on your Innovation Awards oh thank you it's a great honor so to be us let's start with you can you tell us a little bit more about what a viet are is yeah avatars are a digital platform offering features like aircraft condition analytics reliability management and predictive maintenance and it helps airlines worldwide to digitize and improve their operations so all of the features work and can be used separately or generate even more where you burn combined and finally we decided to set up a viet as an open platform that means that we avoid the whole aviation industry to join the community and develop ideas on our platform and to be as one of things i found really fascinating about this is that you had a mandate to do this at a hundred days and you ultimately delivered on it you tell us a little bit about that i mean nothing in aviation moves that fast yeah that's been a big challenge so in the beginning of our story the Lufthansa bot asked us to develop somehow digital to win of an aircraft within just hundred days and to deliver something of value within 100 days means you cannot spend much time and producing specifications in terms of paper etc so for us it was pretty clear that we should go for an angel approach and immediately start and developing ideas so we put the best experts we know just in one room and let them start to work and on day 2 I think we already had the first scribbles for the UI on day 5 we wrote the first lines of code and we were able to do that because it has been a major advantage for us to already have four technologies taken place it's based on open source and especially rated solutions because we did not have to waste any time setting up the infrastructure and since we wanted to get feedback very fast we were certainly visited an airline from the Lufthansa group already on day 30 and showed them the first results and got a lot of feedback and because from the very beginning customer centricity has been an important aspect for us and changing the direction based on customer feedback has become quite normal for us over time yeah it's an interesting story not only engaging the people internally but be able to engage with a with that with a launch customer like that and get feedback along the way as it's great thing how is it going overall since launch yeah since the launch last year in April we generated much interest in the industry as well from Airlines as from competitors and in the following month we focused on a few Airlines which had been open minded and already advanced in digital activities and we've got a lot of feedback by working with them and we're able to improve our products by developing new features for example we learned that data integration can become quite complex in the industry and therefore we developed a new feature called quick boarding allowing Airlines to integrate into the via table platform within one day using a self-service so and currently we're heading for the next steps beyond predictive maintenance working on process automation and prescriptive prescriptive maintenance because we believe prediction without fulfillment still isn't enough it really is a great example of even once you're out there quickly continuing to innovate change react it's great to see so Nick I mean we all know ups I'm still always blown away by the size and scale of the company and the logistics operations that you run you tell us a little more about the project and what we're doing together yeah sure Jim and you know first of all I think I didn't get the sportcoat memo I think I'm the first one up here today with a sport coat but you know first on you know on behalf of the 430,000 ups was around the world and our just world-class talented team of 5,000 IT professionals I have to tell you we're humbled to be one of this year's red hat Innovation Award recipients so we really appreciate that you know as a global logistics provider we deliver about 20 million packages each day and we've got a portfolio of technologies both operational and customer tech and another customer facing side the power what we call the UPS smart logistics network and I gotta tell you innovations in our DNA technology is at the core of everything we do you know from the ever familiar first and industry mobile platform that a lot of you see when you get delivered a package which we call the diad which believe it or not we delivered in 1992 my choice a data-driven solution that drives over 40 million of our my choice customers I'm whatever you know what this is great he loves logistics he's a my choice customer you could be one too by the way there's a free app in the App Store but it provides unmatched visibility and really controls that last mile delivery experience so now today we're gonna talk about the solution that we're recognized for which is called site which is part of a much greater platform that we call edge which is transforming how our package delivery teams operate providing them real-time insights into our operations you know this allows them to make decisions based on data from 32 disparate data sources and these insights help us to optimize our operations but more importantly they help us improve the delivery experience for our customers just like you Jim you know on the on the back end is Big Data and it's on a large scale our systems are crunching billions of events to render those insights on an easy-to-use mobile platform in real time I got to tell you placing that information in our operators hands makes ups agile and being agile being able to react to changing conditions as you know is the name of the game in logistics now we built edge in our private cloud where Red Hat technologies play a very important role as part of our overage overarching cloud strategy and our migration to agile and DevOps so it's it's amazing it's amazing the size and scale so so you have this technology vision around engaging people in a more effect way those are my word not yours but but I'd be at that's how it certainly feels and so tell us a little more about how that enables the hundreds of thousands people to make better decisions every day yep so you know we're a people company and the edge platform is really the latest in a series of solutions to really empower our people and really power that smart logistics network you know we've been deploying technology believe it or not since we founded the company in 1907 we'll be a hundred and eleven years old this August it's just a phenomenal story now prior to edge and specifically the syphon ishutin firm ation from a number of disparate systems and reports they then need to manually look across these various data sources and and frankly it was inefficient and prone to inaccuracy and it wasn't really real-time at all now edge consumes data as I mentioned earlier from 32 disparate systems it allows our operators to make decisions on staffing equipment the flow of packages through the buildings in real time the ability to give our people on the ground the most up-to-date data allows them to make informed decisions now that's incredibly empowering because not only are they influencing their local operations but frankly they're influencing the entire global network it's truly extraordinary and so why open source and open shift in particular as part of that solution yeah you know so as I mentioned Red Hat and Red Hat technology you know specifically open shift there's really core to our cloud strategy and to our DevOps strategy the tools and environments that we've partnered with Red Hat to put in place truly are foundational and they've fundamentally changed the way we develop and deploy our systems you know I heard Jose talk earlier you know we had complex solutions that used to take 12 to 18 months to develop and deliver to market today we deliver those same solutions same level of complexity in months and even weeks now openshift enables us to container raise our workloads that run in our private cloud during normal operating periods but as we scale our business during our holiday peak season which is a very sure window about five weeks during the year last year as a matter of fact we delivered seven hundred and sixty-two million packages in that small window and our transactions our systems they just spiked dramatically during that period we think that having open shift will allow us in those peak periods to seamlessly move workloads to the public cloud so we can take advantage of burst capacity economically when needed and I have to tell you having this flexibility I think is key because you know ultimately it's going to allow us to react quickly to customer demands when needed dial back capacity when we don't need that capacity and I have to say it's a really great story of UPS and red hat working you together it really is a great story is just amazing again the size and scope but both stories here a lot speed speed speed getting to market quickly being able to try things it's great lessons learned for all of us the importance of being able to operate at a fundamentally different clock speed so thank you all for being here very much appreciated congratulate thank you [Applause] [Music] alright so while it's great to hear from our Innovation Award winners and it should be no surprise that they're leading and experimenting in some really interesting areas its scale so I hope that you got a chance to learn something from these interviews you'll have an opportunity to learn more about them you'll also have an opportunity to vote on the innovator of the year you can do that on the Red Hat summit mobile app or on the Red Hat Innovation Awards homepage you can learn even more about their stories and you'll have a chance to vote and I'll be back tomorrow to announce the the summit winner so next I like to spend a few minutes on talking about how Red Hat is working to catalyze our customers efforts Marko bill Peter our senior vice president of customer experience and engagement and John Alessio our vice president of global services will both describe areas in how we are working to configure our own organization to effectively engage with our customers to use open source to help drive their success so with that I'd like to welcome marquel on stage [Music] good morning good morning thank you Jim so I want to spend a few minutes to talk about how we are configured how we are configured towards your success how we enable internally as well to work towards your success and actually engage as well you know Paul yesterday talked about the open source culture and our open source development net model you know there's a lot of attributes that we have like transparency meritocracy collaboration those are the key of our culture they made RedHat what it is today and what it will be in the future but we also added our passion for customer success to that let me tell you this is kind of the configuration from a cultural perspective let me tell you a little bit on what that means so if you heard the name my organization is customer experience and engagement right in the past we talked a lot about support it's an important part of the Red Hat right and how we are configured we are configured probably very uniquely in the industry we put support together we have product security in there we add a documentation we add a quality engineering into an organization you think there's like wow why are they doing it we're also running actually the IT team for actually the product teams why are we doing that now you can imagine right we want to go through what you see as well right and I'll give you a few examples on how what's coming out of this configuration we invest more and more in testing integration and use cases which you are applying so you can see it between the support team experiencing a lot what you do and actually changing our test structure that makes a lot of sense we are investing more and more testing outside the boundaries so not exactly how things must fall by product management or engineering but also how does it really run in an environment that you operate we run complex setups internally right taking openshift putting in OpenStack using software-defined storage underneath managing it with cloud forms managing it if inside we do that we want to see how that works right we are reshaping documentation console to kind of help you better instead of just documenting features and knobs as in how can how do you want to achieve things now part of this is the configuration that are the big part of the configuration is the voice of the customer to listen to what you say I've been here at Red Hat a few years and one of my passion has always been really hearing from customers how they do it I travel constantly in the world and meet with customers because I want to know what is really going on we use channels like support we use channels like getting from salespeople the interaction from customers we do surveys we do you know we interact with our people to really hear what you do what we also do what maybe not many know and it's also very unique in the industry we have a webpage called you asked reacted we show very transparently you told us this is an area for improvement and it's not just in support it's across the company right build us a better web store build us this we're very transparent about Hades improvements we want to do with you now if you want to be part of the process today go to the feedback zone on the next floor down and talk to my team I might be there as well hit me up we want to hear the feedback this is how we talk about configuration of the organization how we are configured let me go to let me go to another part which is innovation innovation every day and that in my opinion the enable section right we gotta constantly innovate ourselves how do we work with you how do we actually provide better value how do we provide faster responses in support this is what we would I say is is our you know commitment to innovation which is the enabling that Jim talked about and I give you a few examples which I'm really happy and it kind of shows the open source culture at Red Hat our commitment is for innovation I'll give you good example right if you have a few thousand engineers and you empower them you kind of set the business framework as hey this is an area we got to do something you get a lot of good IDs you get a lot of IDs and you got a shape an inter an area that hey this is really something that brings now a few years ago we kind of said or I say is like based on a lot of feedback is we got to get more and more proactive if you customers and so I shaped my team and and I shaped it around how can we be more proactive it started very simple as in like from kbase articles or knowledgebase articles in getting started guys then we started a a tool that we put out called labs you've probably seen them if you're on the technical side really taking small applications out for you to kind of validate is this configured correctly stat configure there was the start then out of that the ideas came and they took different turns and one of the turns that we came out was right at insights that we launched a few years ago and did you see the demo yesterday that in Paul's keynote that they showed how something was broken with one the data centers how it was applied to fix and how has changed this is how innovation really came from the ground up from the support side and turned into something really a being a cornerstone of our strategy and we're keeping it married from the day to day work right you don't want to separate this you want to actually keep that the data that's coming from the support goes in that because that's the power that we saw yesterday in the demo now innovation doesn't stop when you set the challenge so we did the labs we did the insights we just launched a solution engine called solution engine another thing that came out of that challenge is in how do we break complex issues down that it's easier for you to find a solution quicker it's one example but we're also experimenting with AI so insights uses AI as you probably heard yesterday we also use it internally to actually drive faster resolution we did in one case with a a our I bought basically that we get to 25% faster resolution on challenges that you have the beauty for you obviously it's well this is much faster 10% of all our support cases today are supported and assisted by an AI now I'll give you another example of just trying to tell you the innovation that comes out if you configure and enable the team correctly kbase articles are knowledgebase articles we q8 thousands and thousands every year and then I get feedback as and while they're good but they're in English as you can tell my English is perfect so it's not no issue for that but for many of you is maybe like even here even I read it in Japanese so we actually did machine translation because it's too many that we can do manually the using machine translation I can tell it's a funny example two weeks ago I tried it I tried something from English to German I looked at it the German looked really bad I went back but the English was bad so it really translates one to one actually what it does but it's really cool this is innovation that you can apply and the team actually worked on this and really proud on that now the real innovation there is not these tools the real innovation is that you can actually shape it in a way that the innovation comes that you empower the people that's the configure and enable and what I think is all it's important this don't reinvent the plumbing don't start from scratch use systems like containers on open shift to actually build the innovation in a smaller way without reinventing the plumbing you save a lot of issues on security a lot of issues on reinventing the wheel focus on that that's what we do as well if you want to hear more details again go in the second floor now let's talk about the engage that Jim mentioned before what I translate that engage is actually engaging you as a customer towards your success now what does commitment to success really mean and I want to reflect on that on a traditional IT company shows up with you talk the salesperson solution architect works with you consulting implements solution it comes over to support and trust me in a very traditional way the support guy has no clue what actually was sold early on it's what happens right and this is actually I think that red had better that we're not so silent we don't show our internal silos or internal organization that much today we engage in a way it doesn't matter from which team it comes we have a better flow than that you deserve how the sausage is made but we can never forget what was your business objective early on now how is Red Hat different in this and we are very strong in my opinion you might disagree but we are very strong in a virtual accounting right really putting you in the middle and actually having a solution architect work directly with support or consulting involved and driving that together you can also help us in actually really embracing that model if that's also other partners or system integrators integrate put yourself in the middle be around that's how we want to make sure that we don't lose sight of the original business problem trust me reducing the hierarchy or getting rid of hierarchy and bureaucracy goes a long way now this is how we configured this is how we engage and this is how we are committed to your success with that I'm going to introduce you to John Alessio that talks more about some of the innovation done with customers thank you [Music] good morning I'm John Alessio I'm the vice president of Global Services and I'm delighted to be with you here today I'd like to talk to you about a couple of things as it relates to what we've been doing since the last summit in the services organization at the core of everything we did it's very similar to what Marco talked to you about our number one priority is driving our customer success with red hat technology and as you see here on the screen we have a number of different offerings and capabilities all the way from training certification open innovation labs consulting really pairing those capabilities together with what you just heard from Marco in the support or cee organization really that's the journey you all go through from the beginning of discovering what your business challenge is all the way through designing those solutions and deploying them with red hat now the highlight like to highlight a few things of what we've been up to over the last year so if I start with the training and certification team they've been very busy over the last year really updating enhancing our curriculum if you haven't stopped by the booth there's a preview for new capability around our learning community which is a new way of learning and really driving that enable meant in the community because 70% of what you need to know you learned from your peers and so it's a very key part of our learning strategy and in fact we take customer satisfaction with our training and certification business very seriously we survey all of our students coming out of training 93% of our students tell us they're better prepared because of red hat training and certification after Weeds they've completed the course we've updated the courses and we've trained well over a hundred and fifty thousand people over the last two years so it's a very very key part of our strategy and that combined with innovation labs and the consulting operation really drive that overall journey now we've been equally busy in enhancing the system of enablement and support for our business partners another very very key initiative is building out the ecosystem we've enhanced our open platform which is online partner enablement network we've added new capability and in fact much of the training and enablement that we do for our internal consultants our deal is delivered through the open platform now what I'm really impressed with and thankful for our partners is how they are consuming and leveraging this material we train and enable for sales for pre-sales and for delivery and we're up over 70% year in year in our partners that are enabled on RedHat technology let's give our business partners a round of applause now one of our offerings Red Hat open innovation labs I'd like to talk a bit more about and take you through a case study open innovation labs was created two years ago it's really there to help you on your journey in adopting open source technology it's an immersive experience where your team will work side-by-side with Red Hatters to really propel your journey forward in adopting open source technology and in fact we've been very busy since the summit in Boston as you'll see coming up on the screen we've completed dozens of engagements leveraging our methods tools and processes for open innovation labs as you can see we've worked with large and small accounts in fact if you remember summit last year we had a European customer easier AG on stage which was a startup and we worked with them at the very beginning of their business to create capabilities in a very short four-week engagement but over the last year we've also worked with very large customers such as Optim and Delta Airlines here in North America as well as Motability operations in the European arena one of the accounts I want to spend a little bit more time on is Heritage Bank heritage Bank is a community owned bank in Toowoomba Australia their challenge was not just on creating new innovative technology but their challenge was also around cultural transformation how to get people to work together across the silos within their organization we worked with them at all levels of the organization to create a new capability the first engagement went so well that they asked us to come in into a second engagement so I'd like to do now is run a video with Peter lock the chief executive officer of Heritage Bank so he can take you through their experience Heritage Bank is one of the country's oldest financial institutions we have to be smarter we have to be more innovative we have to be more agile we had to change we had to find people to help us make that change the Red Hat lab is the only one that truly helps drive that change with a business problem the change within the team is very visible from the start to now we've gone from being separated to very single goal minded seeing people that I only ever seen before in their cubicles in the room made me smile programmers in their thinking I'm now understanding how the whole process fits together the productivity of IT will change and that is good for our business that's really the value that were looking for the Red Hat innovation labs for us were a really great experience I'm not interested in running an organization I'm interested in making a great organization to say I was pleasantly surprised by it is an understatement I was delighted I love the quote I was delighted makes my heart warm every time I see that video you know since we were at summit for those of you who are with us in Boston some of you went on our hardhat tours we've opened three physical facilities here at Red Hat where we can conduct red head open Innovation Lab engagements Singapore London and Boston were all opened within the last physical year and in fact our site in Boston is paired with our world-class executive briefing center as well so if you haven't been there please do check it out I'd like to now talk to you a bit about a very special engagement that we just recently completed we just recently completed an engagement with UNICEF the United Nations Children's Fund and the the purpose behind this engagement was really to help UNICEF create an open-source platform that marries big data with social good the idea is UNICEF needs to be better prepared to respond to emergency situations and as you can imagine emergency situations are by nature unpredictable you can't really plan for them they can happen anytime anywhere and so we worked with them on a project that we called school mapping and the idea was to provide more insights so that when emergency situations arise UNICEF could do a much better job in helping the children in the region and so we leveraged our Red Hat open innovation lab methods tools processes that you've heard about just like we did at Heritage Bank and the other accounts I mentioned but then we also leveraged Red Hat software technologies so we leveraged OpenShift container platform we leveraged ansible automation we helped the client with a more agile development approach so they could have releases much more frequently and continue to update this over time we created a continuous integration continuous deployment pipeline we worked on containers and container in the application etc with that we've been able to provide a platform that is going to allow for their growth to better respond to these emergency situations let's watch a short video on UNICEF mission of UNICEF innovation is to apply technology to the world's most pressing problems facing children data is changing the landscape of what we do at UNICEF this means that we can figure out what's happening now on the ground who it's happening to and actually respond to it in much more of a real-time manner than we used to be able to do we love working with open source communities because of their commitment that we should be doing good for the world we're actually with red hat building a sandbox where universities or other researchers or data scientists can connect and help us with our work if you want to use data for social good there's so many groups out there that really need your help and there's so many ways to get involved [Music] so let's give a very very warm red hat summit welcome to Erica kochi co-founder of unicef innovation well Erica first of all welcome to Red Hat summit thanks for having me here it's our pleasure and thank you for joining us so Erica I've just talked a bit about kind of what we've been up to and Red Hat services over the last year we talked a bit about our open innovation labs and we did this project the school mapping project together our two teams and I thought the audience might find it interesting from your point of view on why the approach we use in innovation labs was such a good fit for the school mapping project yeah it was a great fit for for two reasons the first is values everything that we do at UNICEF innovation we use open source technology and that's for a couple of reasons because we can take it from one place and very easily move it to other countries around the world we work in 190 countries so that's really important for us not to be able to scale things also because it makes sense we can get we can get more communities involved in this and look not just try to do everything by ourselves but look much open much more openly towards the open source communities out there to help us with our work we can't do it alone yeah and then the second thing is methodology you know the labs are really looking at taking this agile approach to prototyping things trying things failing trying again and that's really necessary when you're developing something new and trying to do something new like mapping every school in the world yeah very challenging work think about it 190 countries Wow and so the open source platform really works well and then the the rapid prototyping was really a good fit so I think the audience might find it interesting on how this application and this platform will help children in Latin America so in a lot of countries in Latin America and many countries throughout the world that UNICEF works in are coming out of either decades of conflict or are are subject to natural disasters and not great infrastructure so it's really important to a for us to know where schools are where communities are well where help is needed what's connected what's not and using a overlay of various sources of data from poverty mapping to satellite imagery to other sources we can really figure out what's happening where resources are where they aren't and so we can plan better to respond to emergencies and to and to really invest in areas that are needed that need that investment excellent excellent it's quite powerful what we were able to do in a relatively short eight or nine week engagement that our two teams did together now many of your colleagues in the audience are using open source today looking to expand their use of open source and I thought you might have some recommendations for them on how they kind of go through that journey and expanding their use of open source since your experience at that yeah for us it was it was very much based on what's this gonna cost we have limited resources and what's how is this gonna spread as quickly as possible mm-hmm and so we really asked ourselves those two questions you know about 10 years ago and what we realized is if we are going to be recommending technologies that governments are going to be using it really needs to be open source they need to have control over it yeah and they need to be working with communities not developing it themselves yeah excellent excellent so I got really inspired with what we were doing here in this project it's one of those you know every customer project is really interesting to me this one kind of pulls a little bit at your heartstrings on what the real impact could be here and so I know some of our colleagues here in the audience may want to get involved how can they get involved well there's many ways to get involved with the other UNICEF or other groups out there you can search for our work on github and there are tasks that you can do right now if and if you're looking for to do she's got work for you and if you want sort of a more a longer engagement or a bigger engagement you can check out our website UNICEF stories org and you can look at the areas you might be interested in and contact us we're always open to collaboration excellent well Erica thank you for being with us here today thank you for the great project we worked on together and have a great summer thank you for being give her a round of applause all right well I hope that's been helpful to you to give you a bit of an update on what we've been focused on in global services the message I'll leave with you is our top priority is customer success as you heard through the story from UNICEF from Heritage Bank and others we can help you innovate where you are today I hope you have a great summit and I'll call out Jim Whitehurst thank you John and thank you Erica that's really an inspiring story we have so many great examples of how individuals and organizations are stepping up to transform in the face of digital disruption I'd like to spend my last few minutes with one real-world example that brings a lot of this together and truly with life-saving impact how many times do you think you can solve a problem which is going to allow a clinician to now save the life I think the challenge all of his physicians are dealing with is data overload I probably look at over 100,000 images in a day and that's just gonna get worse what if it was possible for some computer program to look at these images with them and automatically flag images that might deserve better attention Chris on the surface seems pretty simple but underneath Chris has a lot going on in the past year I've seen Chris Foreman community and a space usually dominated by proprietary software I think Chris can change medicine as we know it today [Music] all right with that I'd like to invite on stage dr. Ellen grant from Boston Children's Hospital dr. grant welcome thank you for being here so dr. grant tell me who is Chris Chris does a lot of work for us and I think Chris is making me or has definitely the potential to make me a better doctor Chris helps us take data from our archives in the hospital and port it to wrap the fastback ends like the mass up and cloud to do rapid data processing and provide it back to me in any format on a desktop an iPad or an iPhone so it it basically brings high-end data analysis right to me at the bedside and that's been a barrier that I struggled with years ago to try to break down so that's where we started with Chris is to to break that barrier between research that occurred on a timeline of days to weeks to months to clinical practice which occurs in the timeline of seconds to minutes well one of things I found really fascinating about this story RedHat in case you can't tell we're really passionate about user driven innovation is this is an example of user driven innovation not directly at a technology company but in medicine excuse me can you tell us just a little bit about the genesis of Chris and how I got started yeah Chris got started when I was running a clinical division and I was very frustrated with not having the latest image analysis tools at my fingertips while I was on clinical practice and I would have to on the research so I could go over and you know do line code and do the data analysis but if I'm always over in clinical I kept forgetting how to do those things and I wanted to have all those innovations that my fingertips and not have to remember all the computer science because I'm a physician not like a better scientist so I wanted to build a platform that gave me easy access to that back-end without having to remember all the details and so that's what Chris does for us is brings allowed me to go into the PAC's grab a dataset send it to a computer and back in to do the analysis and bring it back to me without having to worry about where it was or how it got there that's all involved in the in the platform Chris and why not just go to a vendor and ask them to write a piece of software for you to do that yeah we thought about that and we do a lot of technical innovations and we always work with the experts so we wanted to work with if I'm going to be able to say an optical device I'm going to work with the optical engineers or an EM our system I'm going to work with em our engineers so we wanted to work with people who really knew or the plumbers so to speak of the software in industry so we ended up working with the massive point cloud for the platform and the distributed systems in Red Hat as the infrastructure that's starting to support Chris and that's been actually a really incredible journey for us because medical ready medical softwares not typically been a community process and that's something that working with dan from Red Hat we learned a lot about how to participate in an open community and I think our team has grown a lot as a result of that collaboration and I know you we've talked about in the past that getting this data locked into a proprietary system you may not be able to get out there's a real issue can you talk about the importance of open and how that's worked in the process yeah and I think for the medical community and I find this resonates with other physicians as well too is that it's medical data we want to continue to own and we feel very awkward about giving it to industry so we would rather have our data sitting in an open cloud like the mass open cloud where we can have a data consortium that oversees the data governance so that we're not giving our data way to somebody else but have a platform that we can still keep a control of our own data and I think it's going to be the future because we're running of a space in the hospital we generate so much data and it's just going to get worse as I was mentioning and all the systems run faster we get new devices so the amount of data that we have to filter through is just astronomically increasing so we need to have resources to store and compute on such large databases and so thinking about where this could go I mean this is a classic feels like an open-source project it started really really small with a originally modest set of goals and it's just kind of continue to grow and grow and grow it's a lot like if yes leanest torval Linux would be in 1995 you probably wouldn't think it would be where it is now so if you dream with me a little bit where do you think this could possibly go in the next five years ten years what I hope it'll do is allow us to break down the silos within the hospital because to do the best job at what we physicians do not only do we have to talk and collaborate together as individuals we have to take the data each each community develops and be able to bring it together so in other words I need to be able to bring in information from vital monitors from mr scans from optical devices from genetic tests electronic health record and be able to analyze on all that data combined so ideally this would be a platform that breaks down those information barriers in a hospital and also allows us to collaborate across multiple institutions because many disorders you only see a few in each hospital so we really have to work as teams in the medical community to combine our data together and also I'm hoping that and we even have discussions with people in the developing world because they have systems to generate or to got to create data or say for example an M R system they can't create data but they don't have the resources to analyze on it so this would be a portable for them to participate in this growing data analysis world without having to have the infrastructure there and be a portal into our back-end and we could provide the infrastructure to do the data analysis it really is truly amazing to see how it's just continued to grow and grow and expand it really is it's a phenomenal story thank you so much for being here appreciate it thank you [Applause] I really do love that story it's a great example of user driven innovation you know in a different industry than in technology and you know recognizing that a clinicians need for real-time information is very different than a researchers need you know in projects that can last weeks and months and so rather than trying to get an industry to pivot and change it's a great opportunity to use a user driven approach to directly meet those needs so we still have a long way to go we have two more days of the summit and as I said yesterday you know we're not here to give you all the answers we're here to convene the conversation so I hope you will have an opportunity today and tomorrow to meet some new people to share some ideas we're really really excited about what we can all do when we work together so I hope you found today valuable we still have a lot more happening on the main stage as well this afternoon please join us back for the general session it's a really amazing lineup you'll hear from the women and opensource Award winners you'll also hear more about our collab program which is really cool it's getting middle school girls interested in open sourcing coding and so you'll have an opportunity to see some people involved in that you'll also hear from the open source Story speakers and you'll including in that you will see a demo done by a technologist who happens to be 11 years old so really cool you don't want to miss that so I look forward to seeing you then this afternoon thank you [Applause]

I won't mind that either live from San Francisco it's the queue covering Red Hat summit 2018 brought to you by Red Hat and welcome back to the cube we're here live in San Francisco on day two of our coverage of red hat summit 2018 I'm John Troyer I'm here with Larry soccer Larry is the hi Larry weõll area the global lead for infrastructure growth and strategy at Accenture that's great though and welcome as a first timer to the cube you remember the Cuban member the cube alums Ozzy awesome so one of the themes here that we've noticed here on day two of the conference is the reality of hybrid cloud multi-cloud the demos up on stage have been real production workloads from real companies at a global scale and the the theme it's been a lot about open shift open and an open ship and that as a bridge for the right with the rest of Red Hat's stack so Accenture and global si you know work with very big companies very complicated problems and enabling them hybrid cloud is that important for you and your customers absolutely Accenture actually got out very aggressively about four or five years of work go with our cloud first strategy and it was very public centric you know how do we you know how do you start to take advantage of the innovation of the hyper scalers the AWS as the answer is to really start to innovate drive drive agile application development and get out there very quickly however if you take a look at our clients you know they're typically large complex global 2000 companies and for variety of reasons whether it's regulatory reasons gxb compliance if you go to the pharmaceutical industry HIPAA for health care you know PCI they they've really you know they continue to invest in their data centers I mean other reasons toko clouds an interesting one it's a proximity thing it's the thing that actually connects the the public providers and and if he's getting built on that performance you know if you know I start to look with sa P driving a terabyte Hana you know where do you start to deploy that so you know and then even investment say a lot of our clients have significant investments in their data centers and infrastructure so what we've been doing over the last probably six to eight months is really taking a look at a lot of the innovation that we saw from those hyper scalars and bringing it to the to the data center and really trying to create industrialized private clouds with the same kind of standardization that you haven't you know in the world of Amazon and as you're in a you know same automation the cloud operating model and really start to do that not just in the datacenter a private cloud but also the rest of infrastructure and ultimately our clients are going to end up with with hybrid environment so we're you know we've been using our extension cloud platform to integrate you know the public providers now in the person and the private side you know with open shifts the you know the VMware's of the world and even back into the legacy infrastructure well that's that's fascinating and also I think really grounded in reality I mean that the tech industry there's you know we all there's all these pendulums and hype cycles and a few years ago it's right right we we were talking a lot about public there was a lot of innovation and it and maybe it's taken a few years for the private stack and the hybrid stack to catch up to give you that advantage in terms of agility and in terms of speed to market speed to production can you talk a little bit about maybe what that relationship with with openshift you say you you're seeing we saw a like I said we've seen a lot of open ship in production are you saying that as well yeah yeah we did we definitely are I mean you know we have a lot of our clients who they're looking ok hey I this look I want to start getting to more service architectures I want to start adopting the new technologies agile development you know start to really embrace DevOps at the same time it's you know either for data gravity or for compliance reasons there's certain applications they just can't move into the public environments ASAP say you know has been challenging to do it particularly as we start to get HANA so you know they've been starting to look and say ok well open ship becomes a very attractive alternative to start developing applications that I can then you know right in a private environment as well as bring up into Amazon and as yours so a few years ago for better or worse one of the terms people were using was lift and shift right and people were taking their you know or legacy that there's a lot of years of battle-tested infrastructure and do you just hoist it into the cloud do I have to rewrite it can i containerize it I mean what are people doing and how are you going back to the scale of our clients you know a lot our plants will have anywhere from two thousand to over twenty thousand workloads and applications so the the notion of lift and shift or or modernization it's not a binary problem so what we actually did was we took our app modernization practice which is part about technology business we coupled it with our infrastructure migration teams as a part of our Accenture Operations Group and we created an integrated cloud factory and then we actually took we had two different two sets of tools we combined them into one accelerate toolkit and and what that does is it allows us to do the upfront application portfolio assessment we figure out the dispositions of the applications you know what what needs to stay together you know we determine which ones need to be refactored or remediated or modernized and that's our technology organization and then for those that we need to just migrate or so you know a few minor changes we then had you know do all the planning the migrations of that and we're able to do this at you know at scale with the factory leveraging a combination of onshore and offshore and these tools to do all the automation and do the you know the wave planning keeping dependencies and moving data around and and we're able to do you know anywhere at one climb we doing over 1200 workloads a month that's amazing I mean that the scale and the speed that time-to-market even in the demos here on stage has been actually pretty pretty surprising to me because it means that it's real as our people shift as people are shifting their portfolios into a hybrid stance some workloads here some workloads in a multi cloud can you talk a little bit about how you're approaching multi cloud and now you're approaching maybe the multi cloud over time well you know I mean we made a big bet on our Accenture cloud platform so which which is really a cmp started very public focused you know how do I provision and manage optimize my workloads across the public providers we've now started to integrate in the private side much more aggressively we're always doing it at our clients but it was a very custom one-off as we start to industrialize and standardize on the private side it now gives a seamless hybrid cloud management we're actually extending that to go to legacy we've still got a number of clients like insurance companies where they've got significant business logic trapped in their mainframes and our app modernization guys are starting to wrap those with micro services starting to do front-end development in OpenShift it's example and get closer to the users for you know for better customer experience much more agile delivery while still maintaining that frame and and what we find is as you've got these distributed applications based on micro services you now need to manage across that hybrid environment and it's it's public it's private but it's also legacy infrastructure yeah and that's got to be complicated one of the other themes of this show probably coming out of Red Hat's own culture of openness and a we had a great I love the the keynote this morning talking about well you know planning is great but you know eventually the plan is going to hit the battlefield and you've got to be adaptive and you've got to be agile so when you are talking with the CIO and when you're talking with these leads of business and their IT leads you know what are some of the things that you're preparing them with and what are maybe some of the signals that they're up there ready to do this versus maybe not ready to do this yeah you know very good question what's interesting is when I talk to most of our of the CIOs I think they've got a pretty good handle on the technologies I mean it's and not to trivialize it's not simple technology but I think most have focused a lot of their energy on that I think their biggest challenges are the culture and and the operating model so you know if you look thinking well how the hyper scalars do it I mean firstly standardize which I think that's you know these CIOs are typically do want you know they they're not driving standard t-shirt sizes they don't have that discipline to have a standardized service catalog what you need to audit traditionally the enterprise everything most custom everything was bespoke exactly so it's not in their DNA to go to that Christian you know standardization and I mean think about the hyper scalars I mean a well Amazon innovates an incredible pace they still have a discrete set of services and if you can automate and do real cloud operating model you really need to have that level of standardization the whole operate the business and operational transformation is very difficult you know it's interesting now the apps guys have typically done a reasonably good job I mean getting out there and using agile development you know they're embedded in the be used doing their sprints etcetera still some work to be done for the infrastructure guys you know if you if you start to take a look at it you could have an app team doing - you know two-week sprints they're ready to drop code all of a sudden have to wait 12 weeks for the infrastructure to catch up so we've been spending a lot of time looking at how do we enable software to find infrastructure how do we start to even do you know infrastructure is code with similar Sprint's and embedded into the be used groans etc talyn's a huge issue I mean they are all struggling it's very hard to get people with native cloud skills you know it sorts them in the market so most of our clients are really struggling I mean it's good for us as an integrator and bring me how to bring those skills but but they too need to develop those skills as well and that all in some way solves over itself over time as standardization happens right yeah as kubernetes becomes more ubiquitous you will have more people trained up in kubernetes same thing with some of the infrastructure layer maybe can you drill down maybe a little bit more into the infrastructure and how are you helping so do you say the infrastructure folks become more agile you know at some point you've got mainframes they're not moving so you kind of have to wall them off with some agile layers we'd be big proponents of software-defined infrastructure or I think VMware has actually done a pretty good job getting the market up to speed on software-defined data centers so how do you how do you first use virtualization techniques like you know if you think about VMware is NSX or Cisco's ACI part how do you deploy those two to provide the vehicle to do the automation and then grit you know severe you know just very intense automation now if I have to standardize first but then I start to automate so whether it's V you know VMware would be realize it's you know ansible so I mean we've seen red have to do some great work around ansible and doing that automation we use chef in our in our central cloud platform but but it but really starting to drive that similar type standardization and automation but but you have to chain change how you operate to do that and I think that's where a lot of people struggle so they you know they may have automation projects acceptor but they they haven't really fundamentally shifted how they do it so at one of our clients a life sciences client we actually were doing we were implemented a software-defined datacenter we had service now as as the the front end portal you know V realized automation integrated with a GXP compliance system and we just kept iterating through in two-week Sprint's we would incremental II deliver a you know first minimal Viable Product and compute and storage then up to t-shirts we got into you know more database-as-a-service eventually even as being able to spend up s a PE basis instances and we were able to leverage a lot of the automation including the network which is oftentimes a long pole in order to accomplish that right alright so starting with bite-sized pieces and exactly incrementally improvement and that's the great thing about agile right I mean it and to put the problems and the apps guys have known it for a while as infrastructure guys with a little new so we've actually taken out Accenture DevOps platform and we've created an infrastructure exclude plugin you know that uses github and jerry' to now deliver drop releases of infrastructure as good well that's great I mean you mentioned a lot of different tools and platforms here a lot of them open source right we're here at Red Hat summit I think one of the again one of the signals of this week they were you know announcement with Microsoft announcement with IBM you know very serious and you all have been working with them very serious enterprise ready ecosystem here do you get any pushback about the open source nature of some of these things you know less and less and a number of years ago there was clearly you know because of particularly licensing an tabria Enterprise great applications I think that you know I think people become much more comfortable with open source I mean what when it one thing I often look at is Kafka and you looking at me I see so much Kafka getting deployed right now it's you know open source model it's you know I'm seeing it used in so many different uses you know you pet use cases and development and so I think I think a lot of and thanks to Red Hat I you know give them credit for bringing open source to mainstream and to the enterprise market I'm putting you know licensing around it so I think no I don't see the same kind of pushback anymore and I think the walls changed it's kind of the bearable right it's either both at the cloud layer and then at the infrastructure layer in the automation everything like that you know maybe talk a little bit more about some of a Accenture what I would I would have been gathering here right there's a bunch of open source tools you're using but you have your own tool sets too right and and and the eccentric cloud can you talk a little bit so the extension cloud platform is I mean we do use a lot of third-party technologies we're not gonna go reinvent the wheel we're gonna pull in the best of products that we can me and it says and we started off I mean it's been out there for about five years you know to be you know we have an orchestration platform that's built into it we do use a lot of shaft to do you know the provisioning of the environments have a but you know and we keep evolving it we've changed out building optimization engines and now are very focused on how do we push it into the private world so that brings in new tools and capabilities to do that automation so so as we continue to push that the the next big step that we're focused on is the application and infrastructure management so one of the emerging problems is we start to see micro services get adopted and you're gonna get applications that might have a front-end running service and Amazon you know with lambda you know distributed private cloud with a CouchDB you know data right yeah and then a mainframe reservation system so this is one of our you know one of our clients has that environment how do you manage and troubleshoot across that environment so the ability to first look at what I'll call the application or service topology you know up in the tools like I just saw dynaTrace presentation app DS of the world but then go you know the east-west apology then mapping north south into virtualized and physical infrastructure and this to me is gonna be one of our you know more difficult challenges because that at the you know at the same time you've got that complexity it's getting more complicated you know I think containers become much more dynamic you software-defined networking it becomes a lot harder to sexualize and troubleshoot that so we starting to look at the assurance or service management side and really start to innovate you know more there yeah that's that's amazing and I think that's going to become more and more necessary right we you know with big companies global you know distributed all over the world distributed on multiple platforms with private with private components all these services mixed together with a service bus you know you know when that blows up it's gonna blow up spectacular exactly and we've all been on those calls with 50 people that we can't afford to do you know and it's everybody I'm a network guy everyone points at us I really do want the tooling and instrumentation I mean the other big change that's interesting is the operator is gonna change I mean I think there's two major elements to that it's obviously you know DevOps you know development and operations getting cut you know much tighter together asre is a great example that and I think we you know if I look at DevOps right now I feel it's still very dev centric I mean we've grade on CI CD pipelines not quite as good on the op side I think we've got some room to to change there oh there's a lot of there's a lot of growth and journey and I love that the community like we can all learn together and I think open source and all these pieces are a big piece of it but I look at on the infrastructure side in the infrastructure operation side one things we're looking at now is how do we transform both our clients operators and our own operators when we do the outsourcing so how do we take them from what was traditionally eyes on glass looking at consoles and now write the next you know data ingestion scripts the the analytic algorithms of visualizations you know write the next automations to streamline something and over time tune the AI engines as we start to adopt AI to particularly around performance optimization you know how do we start to incorporate that absolutely I think yeah we're all facing that I mean it sounds like I really enjoyed learning about how all everything that Accenture is bringing to the table on this enterprise journey to the cloud Larry thanks for joining us Larry said Larry soccer Global lead for infrastructure growth and strategy at Accenture thanks for being on the deck enjoy it I think we are here we're just wrapping up here we are live here for two days at Red Hat summit in San Francisco we're closing up our second day we'll be joining you in the morning tomorrow as we finish off the conference that's all what you can always count here live on the cube