[Music] [Music] [Music] [Music] ladies and gentlemen please welcome Red Hat senior vice president of engineering Matt Hicks [Music] welcome back I hope you're enjoying your first day of summit you know for us it is a lot of work throughout the year to get ready to get here but I love the energy walking into someone on that first opening day now this morning we kick off with Paul's keynote and you saw this morning just how evolved every aspect of open hybrid cloud has become based on an open source innovation model that opens source the power and potential of open source so we really brought me to Red Hat but at the end of the day the real value comes when were able to make customers like yourself successful with open source and as much passion and pride as we put into the open source community that requires more than just Red Hat given the complexity of your various businesses the solution set you're building that requires an entire technology ecosystem from system integrators that can provide the skills your domain expertise to software vendors that are going to provide the capabilities for your solutions even to the public cloud providers whether it's on the hosting side or consuming their services you need an entire technological ecosystem to be able to support you and your goals and that is exactly what we are gonna talk about this afternoon the technology ecosystem we work with that's ready to help you on your journey now you know this year's summit we talked about earlier it is about ideas worth exploring and we want to make sure you have all of the expertise you need to make those ideas a reality so with that let's talk about our first partner we have him today and that first partner is IBM when I talk about IBM I have a little bit of a nostalgia and that's because 16 years ago I was at IBM it was during my tenure at IBM where I deployed my first copy of Red Hat Enterprise Linux for a customer it's actually where I did my first professional Linux development as well you and that work on Linux it really was the spark that I had that showed me the potential that open source could have for enterprise customers now iBM has always been a steadfast supporter of Linux and a great Red Hat partner in fact this year we are celebrating 20 years of partnership with IBM but even after 20 years two decades I think we're working on some of the most innovative work that we ever have before so please give a warm welcome to Arvind Krishna from IBM to talk with us about what we are working on Arvind [Applause] hey my pleasure to be here thank you so two decades huh that's uh you know I think anything in this industry to going for two decades is special what would you say that that link is made right Hatton IBM so successful look I got to begin by first seeing something that I've been waiting to say for years it's a long strange trip it's been and for the San Francisco folks they'll get they'll get the connection you know what I was just thinking you said 16 it is strange because I probably met RedHat 20 years ago and so that's a little bit longer than you but that was out in Raleigh it was a much smaller company and when I think about the connection I think look IBM's had a long long investment and a long being a long fan of open source and when I think of Linux Linux really lights up our hardware and I think of the power box that you were showing this morning as well as the mainframe as well as all other hardware Linux really brings that to life and I think that's been at the root of our relationship yeah absolutely now I alluded to a little bit earlier we're working on some new stuff and this time it's a little bit higher in the software stack and we have before so what do you what would you say spearheaded that right so we think of software many people know about some people don't realize a lot of the words are called critical systems you know like reservation systems ATM systems retail banking a lot of the systems run on IBM software and when I say IBM software names such as WebSphere and MQ and db2 all sort of come to mind as being some of that software stack and really when I combine that with some of what you were talking about this morning along hybrid and I think this thing called containers you guys know a little about combining the two we think is going to make magic yeah and I certainly know containers and I think for myself seeing the rise of containers from just the introduction of the technology to customers consuming at mission-critical capacities it's been probably one of the fastest technology cycles I've ever seen before look we completely agree with that when you think back to what Paul talks about this morning on hybrid and we think about it we are made of firm commitment to containers all of our software will run on containers and all of our software runs Rell and you put those two together and this belief on hybrid and containers giving you their hybrid motion so that you can pick where you want to run all the software is really I think what has brought us together now even more than before yeah and the best part I think I've liked we haven't just done the product in downstream alignment we've been so tied in our technology approach we've been aligned all the way to the upstream communities absolutely look participating upstream participating in these projects really bringing all the innovation to bear you know when I hear all of you talk about you can't just be in a single company you got to tap into the world of innovation and everybody should contribute we firmly believe that instead of helping to do that is kind of why we're here yeah absolutely now the best part we're not just going to tell you about what we're doing together we're actually going to show you so how every once you tell the audience a little bit more about what we're doing I will go get the demo team ready in the back so you good okay so look we're doing a lot here together we're taking our software and we are begging to put it on top of Red Hat and openshift and really that's what I'm here to talk about for a few minutes and then we go to show it to you live and the demo guard should be with us so it'll hopefully go go well so when we look at extending our partnership it's really based on three fundamental principles and those principles are the following one it's a hybrid world every enterprise wants the ability to span across public private and their own premise world and we got to go there number two containers are strategic to both of us enterprise needs the agility you need a way to easily port things from place to place to place and containers is more than just wrapping something up containers give you all of the security the automation the deploy ability and we really firmly believe that and innovation is the path forward I mean you got to bring all the innovation to bear whether it's around security whether it's around all of the things we heard this morning around going across multiple infrastructures right the public or private and those are three firm beliefs that both of us have together so then explicitly what I'll be doing here number one all the IBM middleware is going to be certified on top of openshift and rel and through cloud private from IBM so that's number one all the middleware is going to run in rental containers on OpenShift on rail with all the cloud private automation and deployability in there number two we are going to make it so that this is the complete stack when you think about from hardware to hypervisor to os/2 the container platform to all of the middleware it's going to be certified up and down all the way so that you can get comfort that this is certified against all the cyber security attacks that come your way three because we do the certification that means a complete stack can be deployed wherever OpenShift runs so that way you give the complete flexibility and you no longer have to worry about that the development lifecycle is extended all the way from inception to production and the management plane then gives you all of the delivery and operation support needed to lower that cost and lastly professional services through the IBM garages as well as the Red Hat innovation labs and I think that this combination is really speaks to the power of both companies coming together and both of us working together to give all of you that flexibility and deployment capabilities across one can't can't help it one architecture chart and that's the only architecture chart I promise you so if you look at it right from the bottom this speaks to what I'm talking about you begin at the bottom and you have a choice of infrastructure the IBM cloud as well as other infrastructure as a service virtual machines as well as IBM power and IBM mainframe as is the infrastructure choices underneath so you choose what what is best suited for the workload well with the container service with the open shift platform managing all of that environment as well as giving the orchestration that kubernetes gives you up to the platform services from IBM cloud private so it contains the catalog of all middle we're both IBM's as well as open-source it contains all the deployment capability to go deploy that and it contains all the operational management so things like come back up if things go down worry about auto scaling all those features that you want come to you from there and that is why that combination is so so powerful but rather than just hear me talk about it I'm also going to now bring up a couple of people to talk about it and what all are they going to show you they're going to show you how you can deploy an application on this environment so you can think of that as either a cloud native application but you can also think about it as how do you modernize an application using micro services but you don't want to just keep your application always within its walls you also many times want to access different cloud services from this and how do you do that and I'm not going to tell you which ones they're going to come and tell you and how do you tackle the complexity of both hybrid data data that crosses both from the private world to the public world and as well as target the extra workloads that you want so that's kind of the sense of what you're going to see through through the demonstrations but with that I'm going to invite Chris and Michael to come up I'm not going to tell you which one's from IBM which runs from Red Hat hopefully you'll be able to make the right guess so with that Chris and Michael [Music] so so thank you Arvind hopefully people can guess which ones from Red Hat based on the shoes I you know it's some really exciting stuff that we just heard there what I believe that I'm I'm most excited about when I look out upon the audience and the opportunity for customers is with this announcement there are quite literally millions of applications now that can be modernized and made available on any cloud anywhere with the combination of IBM cloud private and OpenShift and I'm most thrilled to have mr. Michael elder a distinguished engineer from IBM here with us today and you know Michael would you maybe describe for the folks what we're actually going to go over today absolutely so when you think about how do I carry forward existing applications how do I build new applications as well you're creating micro services that always need a mixture of data and messaging and caching so this example application shows java-based micro services running on WebSphere Liberty each of which are then leveraging things like IBM MQ for messaging IBM db2 for data operational decision manager all of which is fully containerized and running on top of the Red Hat open chip container platform and in fact we're even gonna enhance stock trader to help it understand how you feel but okay hang on so I'm a little slow to the draw sometimes you said we're gonna have an application tell me how I feel exactly exactly you think about your enterprise apps you want to improve customer service understanding how your clients feel can't help you do that okay well this I'd like to see that in action all right let's do it okay so the first thing we'll do is we'll actually take a look at the catalog and here in the IBM cloud private catalog this is all of the content that's available to deploy now into this hybrid solution so we see workloads for IBM will see workloads for other open source packages etc each of these are packaged up as helm charts that are deploying a set of images that will be certified for Red Hat Linux and in this case we're going to go through and start with a simple example with a node out well click a few actions here we'll give it a name now do you have your console up over there I certainly do all right perfect so we'll deploy this into the new old namespace and will deploy notate okay alright anything happening of course it's come right up and so you know what what I really like about this is regardless of if I'm used to using IBM clout private or if I'm used to working with open shift yeah the experience is well with the tool of whatever I'm you know used to dealing with on a daily basis but I mean you know I got to tell you we we deployed node ourselves all the time what about and what about when was the last time you deployed MQ on open shift you never I maybe never all right let's fix that so MQ obviously is a critical component for messaging for lots of highly transactional systems here we'll deploy this as a container on the platform now I'm going to deploy this one again into new worlds I'm gonna disable persistence and for my application I'm going to need a queue manager so I'm going to have it automatically setup my queue manager as well now this will deploy a couple of things what do you see I see IBM in cube all right so there's your stateful set running MQ and of course there's a couple of other components that get stood up as needed here including things like credentials and secrets and the service etc but all of this is they're out of the box ok so impressive right but that's the what I think you know what I'm really looking at is maybe how a well is this running you know what else does this partnership bring when I look at IBM cloud private windows inches well so that's a key reason about why it's not just about IBM middleware running on open shift but also IBM cloud private because ultimately you need that common management plane when you deploy a container the next thing you have to worry about is how do I get its logs how do I manage its help how do I manage license consumption how do I have a common security plan right so cloud private is that enveloping wrapper around IBM middleware to provide those capabilities in a common way and so here we'll switch over to our dashboard this is our Griffin and Prometheus stack that's deployed also now on cloud private running on OpenShift and we're looking at a different namespace we're looking at the stock trader namespace we'll go back to this app here momentarily and we can see all the different pieces what if you switch over to the stock trader workspace on open shipped yeah I think we might be able to do that here hey there it is alright and so what you're gonna see here all the different pieces of this op right there's d b2 over here I see the portfolio Java microservice running on Webster Liberty I see my Redis cash I see MQ all of these are the components we saw in the architecture picture a minute ago ya know so this is really great I mean so maybe let's take a look at the actual application I see we have a fine stock trader app here now we mentioned understanding how I feel exactly you know well I feel good that this is you know a brand new stock trader app versus the one from ten years ago that don't feel like we used forever so the key thing is this app is actually all of those micro services in addition to things like business rules etc to help understand the loyalty program so one of the things we could do here is actually enhance it with a a AI service from Watson this is tone analyzer it helps me understand how that user actually feels and will be able to go through and submit some feedback to understand that user ok well let's see if we can take a look at that so I tried to click on youth clearly you're not very happy right now here I'll do one quick thing over here go for it we'll clear a cache for our sample lab so look you guys don't actually know as Michael and I just wrote this no js' front end backstage while Arvin was actually talking with Matt and we deployed it real-time using continuous integration and continuous delivery that we have available with openshift well the great thing is it's a live demo right so we're gonna do it all live all the time all right so you mentioned it'll tell me how I'm feeling right so if we look at so right there it looks like they're pretty angry probably because our cache hadn't been cleared before we started the demo maybe well that would make me angry but I should be happy because I mean I have a lot of money well it's it's more than I get today for sure so but you know again I don't want to remain angry so does Watson actually understand southern I know it speaks like eighty different languages but well you know I'm from South Carolina to understand South Carolina southern but I don't know about your North Carolina southern alright well let's give it a go here y'all done a real real know no profanity now this is live I've done a real real nice job on this here fancy demo all right hey all right likes me now all right cool and the key thing is just a quick note right it's showing you've got a free trade so we can integrate those business rules and then decide to I do put one trade if you're angry give me more it's all bringing it together into one platform all running on open show yeah and I can see the possibilities right of we've not only deployed services but getting that feedback from our customers to understand well how well the services are being used and are people really happy with what they have hey listen Michael this was amazing I read you joining us today I hope you guys enjoyed this demo as well so all of you know who this next company is as I look out through the crowd based on what I can actually see with the sun shining down on me right now I can see their influence everywhere you know Sports is in our everyday lives and these guys are equally innovative in that space as they are with hybrid cloud computing and they use that to help maintain and spread their message throughout the world of course I'm talking about Nike I think you'll enjoy this next video about Nike and their brand and then we're going to hear directly from my twitting about what they're doing with Red Hat technology new developments in the top story of the day the world has stopped turning on its axis top scientists are currently racing to come up with a solution everybody going this way [Music] the wrong way [Music] please welcome Nike vice president of infrastructure engineering Mike witig [Music] hi everybody over the last five years at Nike we have transformed our technology landscape to allow us to connect more directly to our consumers through our retail stores through Nike comm and our mobile apps the first step in doing that was redesigning our global network to allow us to have direct connectivity into both Asia and AWS in Europe in Asia and in the Americas having that proximity to those cloud providers allows us to make decisions about application workload placement based on our strategy instead of having design around latency concerns now some of those workloads are very elastic things like our sneakers app for example that needs to burst out during certain hours of the week there's certain moments of the year when we have our high heat product launches and for those type of workloads we write that code ourselves and we use native cloud services but being hybrid has allowed us to not have to write everything that would go into that app but rather just the parts that are in that application consumer facing experience and there are other back-end systems certain core functionalities like order management warehouse management finance ERP and those are workloads that are third-party applications that we host on relevent over the last 18 months we have started to deploy certain elements of those core applications into both Azure and AWS hosted on rel and at first we were pretty cautious that we started with development environments and what we realized after those first successful deployments is that are the impact of those cloud migrations on our operating model was very small and that's because the tools that we use for monitoring for security for performance tuning didn't change even though we moved those core applications into Azure in AWS because of rel under the covers and getting to the point where we have that flexibility is a real enabler as an infrastructure team that allows us to just be in the yes business and really doesn't matter where we want to deploy different workload if either cloud provider or on-prem anywhere on the planet it allows us to move much more quickly and stay much more directed to our consumers and so having rel at the core of our strategy is a huge enabler for that flexibility and allowing us to operate in this hybrid model thanks very much [Applause] what a great example it's really nice to hear an IQ story of using sort of relish that foundation to enable their hybrid clout enable their infrastructure and there's a lot that's the story we spent over ten years making that possible for rel to be that foundation and we've learned a lot in that but let's circle back for a minute to the software vendors and what kicked off the day today with IBM IBM s one of the largest software portfolios on the planet but we learned through our journey on rel that you need thousands of vendors to be able to sport you across all of your different industries solve any challenge that you might have and you need those vendors aligned with your technology direction this is doubly important when the technology direction is changing like with containers we saw that two years ago bread had introduced our container certification program now this program was focused on allowing you to identify vendors that had those shared technology goals but identification by itself wasn't enough in this fast-paced world so last year we introduced trusted content we introduced our container health index publicly grading red hats images that form the foundation for those vendor images and that was great because those of you that are familiar with containers know that you're taking software from vendors you're combining that with software from companies like Red Hat and you are putting those into a single container and for you to run those in a mission-critical capacity you have to know that we can both stand by and support those deployments but even trusted content wasn't enough so this year I'm excited that we are extending once again to introduce trusted operations now last week we announced that cube con kubernetes conference the kubernetes operator SDK the goal of the kubernetes operators is to allow any software provider on kubernetes to encode how that software should run this is a critical part of a container ecosystem not just being able to find the vendors that you want to work with not just knowing that you can trust what's inside the container but knowing that you can efficiently run that software now the exciting part is because this is so closely aligned with the upstream technology that today we already have four partners that have functioning operators specifically Couchbase dynaTrace crunchy and black dot so right out of the gate you have security monitoring data store options available to you these partners are really leading the charge in terms of what it means to run their software on OpenShift but behind these four we have many more in fact this morning we announced over 60 partners that are committed to building operators they're taking their domain expertise and the software that they wrote that they know and extending that into how you are going to run that on containers in environments like OpenShift this really brings the power of being able to find the vendors being able to trust what's inside and know that you can run their software as efficiently as anyone else on the planet but instead of just telling you about this we actually want to show you this in action so why don't we bring back up the demo team to give you a little tour of what's possible with it guys thanks Matt so Matt talked about the concept of operators and when when I think about operators and what they do it's taking OpenShift based services and making them even smarter giving you insight into how they do things for example have we had an operator for the nodejs service that I was running earlier it would have detected the problem and fixed itself but when we look at it what really operators do when I look at it from an ecosystem perspective is for ISVs it's going to be a catalyst that's going to allow them to make their services as manageable and it's flexible and as you know maintainable as any public cloud service no matter where OpenShift is running and to help demonstrate this I've got my buddy Rob here Rob are we ready on the demo front we're ready awesome now I notice this screen looks really familiar to me but you know I think we want to give folks here a dev preview of a couple of things well we want to show you is the first substantial integration of the core OS tectonic technology with OpenShift and then the other thing is we are going to dive in a little bit more into operators and their usefulness so Rob yeah so what we're looking at here is the service catalog that you know and love and openshift and we've got a few new things in here we've actually integrated operators into the Service Catalog and I'm going to take this filter and give you a look at some of them that we have today so you can see we've got a list of operators exposed and this is the same way that your developers are already used to integrating with products they're right in your catalog and so now these are actually smarter services but how can we maybe look at that I mentioned that there's maybe a new view I'm used to seeing this as a developer but I hear we've got some really cool stuff if I'm the administrator of the console yeah so we've got a whole new side of the console for cluster administrators to get a look at under the infrastructure versus this dev focused view that we're looking at today today so let's go take a look at it so the first thing you see here is we've got a really rich set of monitoring and health status so we can see that we've got some alerts firing our control plane is up and we can even do capacity planning anything that you need to do to maintenance your cluster okay so it's it's not only for the the services in the cluster and doing things that you know I may be normally as a human operator would have to do but this this console view also gives me insight into the infrastructure itself right like maybe the nodes and maybe handling the security context is that true yes so these are new capabilities that we're bringing to open shift is the ability to do node management things like drain and unscheduled nodes to do day-to-day maintenance and then as well as having security constraints and things like role bindings for example and the exciting thing about this is this is a view that you've never been able to see before it's cross-cutting across namespaces so here we've got a number of admin bindings and we can see that they're connected to a number of namespaces and these would represent our engineering teams all the groups that are using the cluster and we've never had this view before this is a perfect way to audit your security you know it actually is is pretty exciting I mean I've been fortunate enough to be on the up and shift team since day one and I know that operations view is is something that we've you know strived for and so it's really exciting to see that we can offer that now but you know really this was a we want to get into what operators do and what they can do for us and so maybe you show us what the operator console looks like yeah so let's jump on over and see all the operators that we have installed on the cluster you can see that these mirror what we saw on the Service Catalog earlier now what we care about though is this Couchbase operator and we're gonna jump into the demo namespace as I said you can share a number of different teams on a cluster so it's gonna jump into this namespace okay cool so now what we want to show you guys when we think about operators you know we're gonna have a scenario here where there's going to be multiple replicas of a Couchbase service running in the cluster and then we're going to have a stateful set and what's interesting is those two things are not enough if I'm really trying to run this as a true service where it's highly available in persistent there's things that you know as a DBA that I'm normally going to have to do if there's some sort of node failure and so what we want to demonstrate to you is where operators combined with the power that was already within OpenShift are now coming together to keep this you know particular database service highly available and something that we can continue using so Rob what have you got there yeah so as you can see we've got our couch based demo cluster running here and we can see that it's up and running we've got three members we've got an off secret this is what's controlling access to a UI that we're gonna look at in a second but what really shows the power of the operator is looking at this view of the resources that it's managing you can see that we've got a service that's doing load balancing into the cluster and then like you said we've got our pods that are actually running the software itself okay so that's cool so maybe for everyone's benefit so we can show that this is happening live could we bring up the the Couchbase console please and keep up the openshift console both sides so what we see there we go so what we see on the on the right hand side is obviously the same console Rob was working in on the left-hand side as you can see by the the actual names of the pods that are there the the couch based services that are available and so Rob maybe um let's let's kill something that's always fun to do on stage yeah this is the power of the operator it's going to recover it so let's browse on over here and kill node number two so we're gonna forcefully kill this and kick off the recovery and I see right away that because of the integration that we have with operators the Couchbase console immediately picked up that something has changed in the environment now why is that important normally a human being would have to get that alert right and so with operators now we've taken that capability and we've realized that there has been a new event within the environment this is not something that you know kubernetes or open shipped by itself would be able to understand now I'm presuming we're gonna end up doing something else it's not just seeing that it failed and sure enough there we go remember when you have a stateful application rebalancing that data and making it available is just as important as ensuring that the disk is attached so I mean Rob thank you so much for you know driving this for us today and being here I mean you know not only Couchbase but as was mentioned by matt we also have you know crunchy dynaTrace and black duck I would encourage you all to go visit their booths out on the floor today and understand what they have available which are all you know here with a dev preview and then talk to the many other partners that we have that are also looking at operators so again rub thank you for joining us today Matt come on out okay this is gonna make for an exciting year of just what it means to consume container base content I think containers change how customers can get that I believe operators are gonna change how much they can trust running that content let's circle back to one more partner this next partner we have has changed the landscape of computing specifically with their work on hardware design work on core Linux itself you know in fact I think they've become so ubiquitous with computing that we often overlook the technological marvels that they've been able to overcome now for myself I studied computer engineering so in the late 90s I had the chance to study processor design I actually got to build one of my own processors now in my case it was the most trivial processor that you could imagine it was an 8-bit subtractor which means it can subtract two numbers 256 or smaller but in that process I learned the sheer complexity that goes into processor design things like wire placements that are so close that electrons can cut through the insulation in short and then doing those wire placements across three dimensions to multiple layers jamming in as many logic components as you possibly can and again in my case this was to make a processor that could subtract two numbers but once I was done with this the second part of the course was studying the Pentium processor now remember that moment forever because looking at what the Pentium processor was able to accomplish it was like looking at alien technology and the incredible thing is that Intel our next partner has been able to keep up that alien like pace of innovation twenty years later so we're excited have Doug Fisher here let's hear a little bit more from Intel for business wide open skies an open mind no matter the context the idea of being open almost only suggests the potential of infinite possibilities and that's exactly the power of open source whether it's expanding what's possible in business the science and technology or for the greater good which is why-- open source requires the involvement of a truly diverse community of contributors to scale and succeed creating infinite possibilities for technology and more importantly what we do with it [Music] you know what Intel one of our core values is risk-taking and I'm gonna go just a bit off script for a second and say I was just backstage and I saw a gentleman that looked a lot like Scott Guthrie who runs all of Microsoft's cloud enterprise efforts wearing a red shirt talking to Cormier I'm just saying I don't know maybe I need some more sleep but that's what I saw as we approach Intel's 50th anniversary these words spoken by our co-founder Robert Noyce are as relevant today as they were decades ago don't be encumbered by history this is about breaking boundaries in technology and then go off and do something wonderful is about innovation and driving innovation in our industry and Intel we're constantly looking to break boundaries to advance our technology in the cloud in enterprise space that is no different so I'm going to talk a bit about some of the boundaries we've been breaking and innovations we've been driving at Intel starting with our Intel Xeon platform Orion Xeon scalable platform we launched several months ago which was the biggest and mark the most advanced movement in this technology in over a decade we were able to drive critical performance capabilities unmatched agility and added necessary and sufficient security to that platform I couldn't be happier with the work we do with Red Hat and ensuring that those hero features that we drive into our platform they fully expose to all of you to drive that innovation to go off and do something wonderful well there's taking advantage of the performance features or agility features like our advanced vector extensions or avx-512 or Intel quick exist those technologies are fully embraced by Red Hat Enterprise Linux or whether it's security technologies like txt or trusted execution technology are fully incorporated and we look forward to working with Red Hat on their next release to ensure that our advancements continue to be exposed and their platform and all these workloads that are driving the need for us to break boundaries and our technology are driving more and more need for flexibility and computing and that's why we're excited about Intel's family of FPGAs to help deliver that additional flexibility for you to build those capabilities in your environment we have a broad set of FPGA capabilities from our power fish at Mac's product line all the way to our performance product line on the 6/10 strat exten we have a broad set of bets FPGAs what i've been talking to customers what's really exciting is to see the combination of using our Intel Xeon scalable platform in combination with FPGAs in addition to the acceleration development capabilities we've given to software developers combining all that together to deliver better and better solutions whether it's helping to accelerate data compression well there's pattern recognition or data encryption and decryption one of the things I saw in a data center recently was taking our Intel Xeon scalable platform utilizing the capabilities of FPGA to do data encryption between servers behind the firewall all the while using the FPGA to do that they preserve those precious CPU cycles to ensure they delivered the SLA to the customer yet provided more security for their data in the data center one of the edges in cyber security is innovation and route of trust starts at the hardware we recently renewed our commitment to security with our security first pledge has really three elements to our security first pledge first is customer first urgency we have now completed the release of the micro code updates for protection on our Intel platforms nine plus years since launch to protect against things like the side channel exploits transparent and timely communication we are going to communicate timely and openly on our Intel comm website whether it's about our patches performance or other relevant information and then ongoing security assurance we drive security into every one of our products we redesigned a portion of our processor to add these partition capability which is adding additional walls between applications and user level privileges to further secure that environment from bad actors I want to pause for a second and think everyone in this room involved in helping us work through our security first pledge this isn't something we do on our own it takes everyone in this room to help us do that the partnership and collaboration was next to none it's the most amazing thing I've seen since I've been in this industry so thank you we don't stop there we continue to advance our security capabilities cross-platform solutions we recently had a conference discussion at RSA where we talked about Intel Security Essentials where we deliver a framework of capabilities and the end that are in our silicon available for those to innovate our customers and the security ecosystem to innovate on a platform in a consistent way delivering that assurance that those capabilities will be on that platform we also talked about things like our security threat technology threat detection technology is something that we believe in and we launched that at RSA incorporates several elements one is ability to utilize our internal graphics to accelerate some of the memory scanning capabilities we call this an accelerated memory scanning it allows you to use the integrated graphics to scan memory again preserving those precious cycles on the core processor Microsoft adopted this and are now incorporated into their defender product and are shipping it today we also launched our threat SDK which allows partners like Cisco to utilize telemetry information to further secure their environments for cloud workloads so we'll continue to drive differential experiences into our platform for our ecosystem to innovate and deliver more and more capabilities one of the key aspects you have to protect is data by 2020 the projection is 44 zettabytes of data will be available 44 zettabytes of data by 2025 they project that will grow to a hundred and eighty s data bytes of data massive amount of data and what all you want to do is you want to drive value from that data drive and value from that data is absolutely critical and to do that you need to have that data closer and closer to your computation this is why we've been working Intel to break the boundaries in memory technology with our investment in 3d NAND we're reducing costs and driving up density in that form factor to ensure we get warm data closer to the computing we're also innovating on form factors we have here what we call our ruler form factor this ruler form factor is designed to drive as much dense as you can in a 1u rack we're going to continue to advance the capabilities to drive one petabyte of data at low power consumption into this ruler form factor SSD form factor so our innovation continues the biggest breakthrough and memory technology in the last 25 years in memory media technology was done by Intel we call this our 3d crosspoint technology and our 3d crosspoint technology is now going to be driven into SSDs as well as in a persistent memory form factor to be on the memory bus giving you the speed of memory characteristics of memory as well as the characteristics of storage given a new tier of memory for developers to take full advantage of and as you can see Red Hat is fully committed to integrating this capability into their platform to take full advantage of that new capability so I want to thank Paul and team for engaging with us to make sure that that's available for all of you to innovate on and so we're breaking boundaries and technology across a broad set of elements that we deliver that's what we're about we're going to continue to do that not be encumbered by the past your role is to go off and doing something wonderful with that technology all ecosystems are embracing this and driving it including open source technology open source is a hub of innovation it's been that way for many many years that innovation that's being driven an open source is starting to transform many many businesses it's driving business transformation we're seeing this coming to light in the transformation of 5g driving 5g into the networked environment is a transformational moment an open source is playing a pivotal role in that with OpenStack own out and opie NFV and other open source projects were contributing to and participating in are helping drive that transformation in 5g as you do software-defined networks on our barrier breaking technology we're also seeing this transformation rapidly occurring in the cloud enterprise cloud enterprise are growing rapidly and innovation continues our work with virtualization and KVM continues to be aggressive to adopt technologies to advance and deliver more capabilities in virtualization as we look at this with Red Hat we're now working on Cube vert to help move virtualized workloads onto these platforms so that we can now have them managed at an open platform environment and Cube vert provides that so between Intel and Red Hat and the community we're investing resources to make certain that comes to product as containers a critical feature in Linux becomes more and more prevalent across the industry the growth of container elements continues at a rapid rapid pace one of the things that we wanted to bring to that is the ability to provide isolation without impairing the flexibility the speed and the footprint of a container with our clear container efforts along with hyper run v we were able to combine that and create we call cotta containers we launched this at the end of last year cotta containers is designed to have that container element available and adding elements like isolation both of these events need to have an orchestration and management capability Red Hat's OpenShift provides that capability for these workloads whether containerized or cube vert capabilities with virtual environments Red Hat openshift is designed to take that commercial capability to market and we've been working with Red Hat for several years now to develop what we call our Intel select solution Intel select solutions our Intel technology optimized for downstream workloads as we see a growth in a workload will work with a partner to optimize a solution on Intel technology to deliver the best solution that could be deployed quickly our effort here is to accelerate the adoption of these type of workloads in the market working with Red Hat's so now we're going to be deploying an Intel select solution design and optimized around Red Hat OpenShift we expect the industry's start deploying this capability very rapidly I'm excited to announce today that Lenovo is committed to be the first platform company to deliver this solution to market the Intel select solution to market will be delivered by Lenovo now I talked about what we're doing in industry and how we're transforming businesses our technology is also utilized for greater good there's no better example of this than the worked by dr. Stephen Hawking it was a sad day on March 14th of this year when dr. Stephen Hawking passed away but not before Intel had a 20-year relationship with dr. Hawking driving breakthrough capabilities innovating with him driving those robust capabilities to the rest of the world one of our Intel engineers an Intel fellow which is the highest technical achievement you can reach at Intel got to spend 10 years with dr. Hawking looking at innovative things they could do together with our technology and his breakthrough innovative thinking so I thought it'd be great to bring up our Intel fellow Lema notch Minh to talk about her work with dr. Hawking and what she learned in that experience come on up Elina [Music] great to see you Thanks something going on about the breakthrough breaking boundaries and Intel technology talk about how you use that in your work with dr. Hawking absolutely so the most important part was to really make that technology contextually aware because for people with disability every single interaction takes a long time so whether it was adapting for example the language model of his work predictor to understand whether he's gonna talk to people or whether he's writing a book on black holes or to even understand what specific application he might be using and then making sure that we're surfacing only enough actions that were relevant to reduce that amount of interaction so the tricky part is really to make all of that contextual awareness happen without totally confusing the user because it's constantly changing underneath it so how is that your work involving any open source so you know the problem with assistive technology in general is that it needs to be tailored to the specific disability which really makes it very hard and very expensive because it can't utilize the economies of scale so basically with the system that we built what we wanted to do is really enable unleashing innovation in the world right so you could take that framework you could tailor to a specific sensor for example a brain computer interface or something like that where you could actually then support a different set of users so that makes open-source a perfect fit because you could actually build and tailor and we you spoke with dr. Hawking what was this view of open source is it relevant to him so yeah so Stephen was adamant from the beginning that he wanted a system to benefit the world and not just himself so he spent a lot of time with us to actually build this system and he was adamant from day one that he would only engage with us if we were commit to actually open sourcing the technology that's fantastic and you had the privilege of working with them in 10 years I know you have some amazing stories to share so thank you so much for being here thank you so much in order for us to scale and that's what we're about at Intel is really scaling our capabilities it takes this community it takes this community of diverse capabilities it takes two births thought diverse thought of dr. Hawking couldn't be more relevant but we also are proud at Intel about leading efforts of diverse thought like women and Linux women in big data other areas like that where Intel feels that that diversity of thinking and engagement is critical for our success so as we look at Intel not to be encumbered by the past but break boundaries to deliver the technology that you all will go off and do something wonderful with we're going to remain committed to that and I look forward to continue working with you thank you and have a great conference [Applause] thank God now we have one more customer story for you today when you think about customers challenges in the technology landscape it is hard to ignore the public cloud these days public cloud is introducing capabilities that are driving the fastest rate of innovation that we've ever seen in our industry and our next customer they actually had that same challenge they wanted to tap into that innovation but they were also making bets for the long term they wanted flexibility and providers and they had to integrate to the systems that they already have and they have done a phenomenal job in executing to this so please give a warm welcome to Kerry Pierce from Cathay Pacific Kerry come on thanks very much Matt hi everyone thank you for giving me the opportunity to share a little bit about our our cloud journey let me start by telling you a little bit about Cathay Pacific we're an international airline based in Hong Kong and we serve a passenger and a cargo network to over 200 destinations in 52 countries and territories in the last seventy years and years seventy years we've made substantial investments to develop Hong Kong as one of the world's leading transportation hubs we invest in what matters most to our customers to you focusing on our exemplary service and our great product and it's both on the ground and in the air we're also investing and expanding our network beyond our multiple frequencies to the financial districts such as Tokyo New York and London and we're connecting Asia and Hong Kong with key tech hubs like San Francisco where we have multiple flights daily we're also connecting Asia in Hong Kong to places like Tel Aviv and our upcoming destination of Dublin in fact 2018 is actually going to be one of our biggest years in terms of network expansion and capacity growth and we will be launching in September our longest flight from Hong Kong direct to Washington DC and that'll be using a state-of-the-art Airbus a350 1000 aircraft so that's a little bit about Cathay Pacific let me tell you about our journey through the cloud I'm not going to go into technical details there's far smarter people out in the audience who will be able to do that for you just focus a little bit about what we were trying to achieve and the people side of it that helped us get there we had a couple of years ago no doubt the same issues that many of you do I don't think we're unique we had a traditional on-premise non-standardized fragile infrastructure it didn't meet our infrastructure needs and it didn't meet our development needs it was costly to maintain it was costly to grow and it really inhibited innovation most importantly it slowed the delivery of value to our customers at the same time you had the hype of cloud over the last few years cloud this cloud that clouds going to fix the world we were really keen on making sure we didn't get wound up and that so we focused on what we needed we started bottom up with a strategy we knew we wanted to be clouded Gnostic we wanted to have active active on-premise data centers with a single network and fabric and we wanted public clouds that were trusted and acted as an extension of that environment not independently we wanted to avoid single points of failure and we wanted to reduce inter dependencies by having loosely coupled designs and finally we wanted to be scalable we wanted to be able to cater for sudden surges of demand in a nutshell we kind of just wanted to make everything easier and a management level we wanted to be a broker of services so not one size fits all because that doesn't work but also not one of everything we want to standardize but a pragmatic range of services that met our development and support needs and worked in harmony with our public cloud not against it so we started on a journey with red hat we implemented Red Hat cloud forms and ansible to manage our hybrid cloud we also met implemented Red Hat satellite to maintain a manager environment we built a Red Hat OpenStack on crimson vironment to give us an alternative and at the same time we migrated a number of customer applications to a production public cloud open shift environment but it wasn't all Red Hat you love heard today that the Red Hat fits within an overall ecosystem we looked at a number of third-party tools and services and looked at developing those into our core solution I think at last count we had tried and tested somewhere past eight different tools and at the moment we still have around 62 in our environment that help us through that journey but let me put the technical solution aside a little bit because it doesn't matter how good your technical solution is if you don't have the culture and the people to get it right as a group we needed to be aligned for delivery and we focused on three core behaviors we focused on accountability agility and collaboration now I was really lucky we've got a pretty fantastic team for whom that was actually pretty easy but but again don't underestimate the importance of getting the culture and the people right because all the technology in the world doesn't matter if you don't have that right I asked the team what did we do differently because in our situation we didn't go out and hire a bunch of new people we didn't go out and hire a bunch of consultants we had the staff that had been with us for 10 20 and in some cases 30 years so what did we do differently it was really simple we just empowered and supported our staff we knew they were the smart ones they were the ones that were dealing with a legacy environment and they had the passion to make the change so as a team we encouraged suggestions and contributions from our overall IT community from the bottom up we started small we proved the case we told the story and then we got by him and only did did we implement wider the benefits the benefit through our staff were a huge increase in staff satisfaction reduction and application and platform outage support incidents risk free and failsafe application releases work-life balance no more midnight deployments and our application and infrastructure people could really focus on delivering customer value not on firefighting and for our end customers the people that travel with us it was really really simple we could provide a stable service that allowed for faster releases which meant we could deliver value faster in terms of stats we migrated 16 production b2c applications to a public cloud OpenShift environment in 12 months we decreased provisioning time from weeks or occasionally months we were waiting for hardware two minutes and we had a hundred percent availability of our key customer facing systems but most importantly it was about people we'd built a culture a culture of innovation that was built on a foundation of collaboration agility and accountability and that permeated throughout the IT organization not those just those people that were involved in the project everyone with an IT could see what good looked like and to see what it worked what it looked like in terms of working together and that was a key foundation for us the future for us you will have heard today everything's changing so we're going to continue to develop our open hybrid cloud onboard more public cloud service providers continue to build more modern applications and leverage the emerging technology integrate and automate everything we possibly can and leverage more open source products with the great support from the open source community so there you have it that's our journey I think we succeeded by not being over awed and by starting with the basics the technology was key obviously it's a cool component but most importantly it was a way we approached our transition we had a clear strategy that was actually developed bottom-up by the people that were involved day to day and we empowered those people to deliver and that provided benefits to both our staff and to our customers so thank you for giving the opportunity to share and I hope you enjoy the rest of the summer [Applause] I got one thanks what a great story would a great customer story to close on and we have one more partner to come up and this is a partner that all of you know that's Microsoft Microsoft has gone through an amazing transformation they've we've built an incredibly meaningful partnership with them all the way from our open source collaboration to what we do in the business side we started with support for Red Hat Enterprise Linux on hyper-v and that was truly just the beginning today we're announcing one of the most exciting joint product offerings on the market today let's please give a warm welcome to Paul correr and Scott Scott Guthrie to tell us about it guys come on out you know Scot welcome welcome to the Red Hat summer thanks for coming really appreciate it great to be here you know many surprises a lot of people when we you know published a list of speakers and then you rock you were on it and you and I are on stage here it's really really important and exciting to us exciting new partnership we've worked together a long time from the hypervisor up to common support and now around hybrid hybrid cloud maybe from your perspective a little bit of of what led us here well you know I think the thing that's really led us here is customers and you know Microsoft we've been on kind of a transformation journey the last several years where you know we really try to put customers at the center of everything that we do and you know as part of that you quickly learned from customers in terms of I'm including everyone here just you know you've got a hybrid of state you know both in terms of what you run on premises where it has a lot of Red Hat software a lot of Microsoft software and then really is they take the journey to the cloud looking at a hybrid of state in terms of how do you run that now between on-premises and a public cloud provider and so I think the thing that both of us are recognized and certainly you know our focus here at Microsoft has been you know how do we really meet customers with where they're at and where they want to go and make them successful in that journey and you know it's been fantastic working with Paul and the Red Hat team over the last two years in particular we spend a lot of time together and you know really excited about the journey ahead so um maybe you can share a bit more about the announcement where we're about to make today yeah so it's it's it's a really exciting announcement it's and really kind of I think first of its kind in that we're delivering a Red Hat openshift on Azure service that we're jointly developing and jointly managing together so this is different than sort of traditional offering where it's just running inside VMs and it's sort of two vendors working this is really a jointly managed service that we're providing with full enterprise support with a full SLA where the you know single throat to choke if you will although it's collectively both are choke the throats in terms of making sure that it works well and it's really uniquely designed around this hybrid world and in that it supports will support both Windows and Linux containers and it role you know it's the same open ship that runs both in the public cloud on Azure and on-premises and you know it's something that we hear a lot from customers I know there's a lot of people here that have asked both of us for this and super excited to be able to talk about it today and we're gonna show off the first demo of it just a bit okay well I'm gonna ask you to elaborate a bit more about this how this fits into the bigger Microsoft picture and I'll get out of your way and so thanks again thank you for coming here we go thanks Paul so I thought I'd spend just a few minutes talking about wouldn't you know that some of the work that we're doing with Microsoft Asher and the overall Microsoft cloud I didn't go deeper in terms of the new offering that we're announcing today together with red hat and show demo of it actually in action in a few minutes you know the high level in terms of you know some of the work that we've been doing at Microsoft the last couple years you know it's really been around this this journey to the cloud that we see every organization going on today and specifically the Microsoft Azure we've been providing really a cloud platform that delivers the infrastructure the application and kind of the core computing needs that organizations have as they want to be able to take advantage of what the cloud has to offer and in terms of our focus with Azure you know we've really focused we deliver lots and lots of different services and features but we focused really in particular on kind of four key themes and we see these four key themes aligning very well with the journey Red Hat it's been on and it's partly why you know we think the partnership between the two companies makes so much sense and you know for us the thing that we've been really focused on has been with a or in terms of how do we deliver a really productive cloud meaning how do we enable you to take advantage of cutting-edge technology and how do we kind of accelerate the successful adoption of it whether it's around the integration of managed services that we provide both in terms of the application space in the data space the analytic and AI space but also in terms of just the end-to-end management and development tools and how all those services work together so that teams can basically adopt them and be super successful yeah we deeply believe in hybrid and believe that the world is going to be a multi cloud and a multi distributed world and how do we enable organizations to be able to take the existing investments that they already have and be able to easily integrate them in a public cloud and with a public cloud environment and get immediate ROI on day one without how to rip and replace tons of solutions you know we're moving very aggressively in the AI space and are looking to provide a rich set of AI services both finished AI models things like speech detection vision detection object motion etc that any developer even at non data scientists can integrate to make application smarter and then we provide a rich set of AI tooling that enables organizations to build custom models and be able to integrate them also as part of their applications and with their data and then we invest very very heavily on trust Trust is sort of at the core of a sure and we now have more compliant certifications than any other cloud provider we run in more countries than any other cloud provider and we really focus around unique promises around data residency data sovereignty and privacy that are really differentiated across the industry and terms of where Iser runs today we're in 50 regions around the world so our region for us is typically a cluster of multiple data centers that are grouped together and you can see we're pretty much on every continent with the exception of Antarctica today and the beauty is you're going to be able to take the Red Hat open shift service and run it on ashore in each of these different locations and really have a truly global footprint as you look to build and deploy solutions and you know we've seen kind of this focus on productivity hybrid intelligence and Trust really resonate in the market and about 90 percent of Fortune 500 companies today are deployed on Azure and you heard Nike talked a little bit earlier this afternoon about some of their journeys as they've moved to a dot public cloud this is a small logo of just a couple of the companies that are on ashore today and what I do is actually even before we dive into the open ship demo is actually just show a quick video you know one of the companies thing there are actually several people from that organization here today Deutsche Bank who have been working with both Microsoft and Red Hat for many years Microsoft on the other side Red Hat both on the rel side and then on the OpenShift side and it's just one of these customers that have helped bring the two companies together to deliver this managed openshift service on Azure and so I'm just going to play a quick video of some of the folks that Deutsche Bank talking about their experiences and what they're trying to get out of it so we could roll the video that'd be great technology is at the absolute heart of Deutsche Bank we've recognized that the cost of running our infrastructure was particularly high there was a enormous amount of under utilization we needed a platform which was open to polyglot architecture supporting any kind of application workload across the various business lines of the third we analyzed over 60 different vendor products and we ended up with Red Hat openshift I'm super excited Microsoft or supporting Linux so strongly to adopting a hybrid approach we chose as here because Microsoft was the ideal partner to work with on constructs around security compliance business continuity as you as in all the places geographically that we need to be we have applications now able to go from a proof of concept to production in three weeks that is already breaking records openshift gives us given entities and containers allows us to apply the same sets of processes automation across a wide range of our application landscape on any given day we run between seven and twelve thousand containers across three regions we start see huge levels of cost reduction because of the level of multi-tenancy that we can achieve through containers open ship gives us an abstraction layer which is allows us to move our applications between providers without having to reconfigure or recode those applications what's really exciting for me about this journey is the way they're both Red Hat and Microsoft have embraced not just what we're doing but what each other are doing and have worked together to build open shift as a first-class citizen with Microsoft [Applause] in terms of what we're announcing today is a new fully managed OpenShift service on Azure and it's really the first fully managed service provided end-to-end across any of the cloud providers and it's jointly engineer operated and supported by both Microsoft and Red Hat and that means again sort of one service one SLA and both companies standing for a link firmly behind it really again focusing around how do we make customers successful and as part of that really providing the enterprise-grade not just isolates but also support and integration testing so you can also take advantage of all your rel and linux-based containers and all of your Windows server based containers and how can you run them in a joint way with a common management stack taking the advantage of one service and get maximum density get maximum code reuse and be able to take advantage of a containerized world in a better way than ever before and make this customer focus is very much at the center of what both companies are really centered around and so what if I do be fun is rather than just talk about openshift as actually kind of show off a little bit of a journey in terms of what this move to take advantage of it looks like and so I'd like to invite Brendan and Chris onstage who are actually going to show off a live demo of openshift on Azure in action and really walk through how to provision the service and basically how to start taking advantage of it using the full open ship ecosystem so please welcome Brendan and Chris we're going to join us on stage for a demo thanks God thanks man it's been a good afternoon so you know what we want to get into right now first I'd like to think Brandon burns for joining us from Microsoft build it's a busy week for you I'm sure your own stage there a few times as well you know what I like most about what we just announced is not only the business and technical aspects but it's that operational aspect the uniqueness the expertise that RedHat has for running OpenShift combined with the expertise that Microsoft has within Azure and customers are going to get this joint offering if you will with you know Red Hat OpenShift on Microsoft Azure and so you know kind of with that again Brendan I really appreciate you being here maybe talk to the folks about what we're going to show yeah so we're going to take a look at what it looks like to deploy OpenShift on to Azure via the new OpenShift service and the real selling point the really great part of this is the the deep integration with a cloud native app API so the same tooling that you would use to create virtual machines to create disks trade databases is now the tooling that you're going to use to create an open chip cluster so to show you this first we're going to create a resource group here so we're going to create that resource group in East us using the AZ tool that's the the azure command-line tooling a resource group is sort of a folder on Azure that holds all of your stuff so that's gonna come back into the second I've created my resource group in East us and now we're gonna use that exact same tool calling into into Azure api's to provision an open shift cluster so here we go we have AZ open shift that's our new command line tool putting it into that resource group I'm gonna get into East us alright so it's gonna take a little bit of time to deploy that open shift cluster it's doing a bunch of work behind the scenes provisioning all kinds of resources as well as credentials to access a bunch of different as your API so are we actually able to see this to you yeah so we can cut over to in just a second we can cut over to that resource group in a reload so Brendan while relating the beauty of what you know the teams have been doing together already is the fact that now open shift is a first-class citizen as it were yeah absolutely within the agent so I presume not only can I do a deployment but I can do things like scale and check my credentials and pretty much everything that I could do with any other service with that that's exactly right so we can anything that you you were used to doing via the my computer has locked up there we go the demo gods are totally with me oh there we go oh no I hit reload yeah that was that was just evil timing on the house this is another use for operators as we talked about earlier today that's right my dashboard should be coming up do I do I dare click on something that's awesome that was totally it was there there we go good job so what's really interesting about this I've also heard that it deploys you know in as little as five to six minutes which is really good for customers they want to get up and running with it but all right there we go there it is who managed to make it see that shows that it's real right you see the sweat coming off of me there but there you can see the I feel it you can see the various resources that are being created in order to create this openshift cluster virtual machines disks all of the pieces provision for you automatically via that one single command line call now of course it takes a few minutes to to create the cluster so in order to show the other side of that integration the integration between openshift and Azure I'm going to cut over to an open shipped cluster that I already have created alright so here you can see my open shift cluster that's running on Microsoft Azure I'm gonna actually log in over here and the first sign you're gonna see of the integration is it's actually using my credentials my login and going through Active Directory and any corporate policies that I may have around smart cards two-factor off anything like that authenticate myself to that open chef cluster so I'll accept that it can access my and now we're gonna load up the OpenShift web console so now this looks familiar to me oh yeah so if anybody's used OpenShift out there this is the exact same console and what we're going to show though is how this console via the open service broker and the open service broker implementation for Azure integrates natively with OpenShift all right so we can go down here and we can actually see I want to deploy a database I'm gonna deploy Mongo as my key value store that I'm going to use but you know like as we talk about management and having a OpenShift cluster that's managed for you I don't really want to have to manage my database either so I'm actually going to use cosmos DB it's a native Azure service it's a multilingual database that offers me the ability to access my data in a variety of different formats including MongoDB fully managed replicated around the world a pretty incredible service so I'm going to go ahead and create that so now Brendan what's interesting I think to me is you know we talked about the operational aspects and clearly it's not you and I running the clusters but you do need that way to interface with it and so when customers are able to deploy this all of this is out of the box there's no additional contemporary like this is what you get when you create when you use that tool to create that open chef cluster this is what you get with all of that integration ok great step through here and go ahead don't have any IP ranges there we go all right and we create that binding all right and so now behind the scenes openshift is integrated with the azure api's with all of my credentials to go ahead and create that distributed database once it's done provisioning actually all of the credentials necessary to access the database are going to be automatically populated into kubernetes available for me inside of OpenShift via service discovery to access from my application without any further work so I think that really shows not only the power of integrating openshift with an azure based API but actually the power of integrating a Druze API is inside of OpenShift to make a truly seamless experience for managing and deploying your containers across a variety of different platforms yeah hey you know Brendan this is great I know you've got a flight to catch because I think you're back onstage in a few hours but you know really appreciate you joining us today absolutely I look forward to seeing what else we do yeah absolutely thank you so much thanks guys Matt you want to come back on up thanks a lot guys if you have never had the opportunity to do a live demo in front of 8,000 people it'll give you a new appreciation for standing up there and doing it and that was really good you know every time I get the chance just to take a step back and think about the technology that we have at our command today I'm in awe just the progress over the last 10 or 20 years is incredible on to think about what might come in the next 10 or 20 years really is unthinkable you even forget 10 years what might come in the next five years even the next two years but this can create a lot of uncertainty in the environment of what's going to be to come but I believe I am certain about one thing and that is if ever there was a time when any idea is achievable it is now just think about what you've seen today every aspect of open hybrid cloud you have the world's infrastructure at your fingertips and it's not stopping you've heard about this the innovation of open source how fast that's evolving and improving this capability you've heard this afternoon from an entire technology ecosystem that's ready to help you on this journey and you've heard from customer after customer that's already started their journey in the successes that they've had you're one of the neat parts about this afternoon you will aren't later this week you will actually get to put your hands on all of this technology together in our live audience demo you know this is what some it's all about for us it's a chance to bring together the technology experts that you can work with to help formulate how to pull off those ideas we have the chance to bring together technology experts our customers and our partners and really create an environment where everyone can experience the power of open source that same spark that I talked about when I was at IBM where I understood the but intial that open-source had for enterprise customers we want to create the environment where you can have your own spark you can have that same inspiration let's make this you know in tomorrow's keynote actually you will hear a story about how open-source is changing medicine as we know it and literally saving lives it is a great example of expanding the ideas it might be possible that we came into this event with so let's make this the best summit ever thank you very much for being here let's kick things off right head down to the Welcome Reception in the expo hall and please enjoy the summit thank you all so much [Music] [Music]

>> Announcer: From San Francisco, it's theCUBE. Covering Red Hat Summit 2018 brought to you by Red Hat. >> Hello everyone and welcome back to see CUBE's exclusive coverage of Red Hat Summit 2018 live in San Francisco, California at Moscone West. I'm John Furrier, your cohost of theCUBE with John Troyer co-founder of Tech Reckoning advisory and community development firm. Our next two guests Mike Piech Vice President and General Manager of middleware at Red Hat and Mark Little, Vice President of Software Engineering for middleware at Red Hat. This is the stack wars right here. Guys thanks for coming back, good to see you guys again. >> Great to see you too. >> So we love Middleware because Dave Vellante and I and Stu always talk about like the real value is going to be created in abstraction layers. You're seeing examples of that all over the place but Kubernetes containers, multi-cloud conversations. Workload management and all these things are happening at these really cool abstraction layers. That's obviously you say global I say middleware but you know it's where the action is. So I got to ask you, super cool that you guys have been leading in there but the new stuff's happening. So let's just go review last year or was it this year? What's different this year, new things happening within the company? We see core OS' in there, you guys got OpenShift is humming along beautifully. What's new in the middleware group? >> There's a few things. I'll take one and then maybe Mike can think of another while I'm speaking but when we were here this time last year we were talking about functions as a service or server-less and we had a project of our own called Funktion with a K, between then and now the developer affinity around functions as a service has just grown. Lots of people are now using it and starting to use it in production. We did a review of what we were doing back then and looked around at other efforts that were in the market space and we decided actually we wanted to get involved with a large community of developers and try and move that in a direction that was pretty beneficial for everybody but clearly for ourselves. And we've decided, and we announced this publicly last year but we're now involved with a project called Apache OpenWhisk instead of Funktion. And OpenWhisk is a project that IBM originally kicked off. We got involved, it was tied very closely to cloud foundering so one of the first things that we've been doing is making it more Kubernetes native and allowing it to run on OpenShift. In fact we're making some announcements this week around our functions are service based on Apache OpenWhisk. But that's probably one of the bigger things that's changed in the last 12 months. >> I would just add to that that across the rest of the middleware portfolio which is as you know, a wide range of different technologies, different products, in our integration area we continue to push ahead with containerizing, putting the integration technologies in the containers, making it easier to basically connect the different components of applications and different applications to each other together through different integration paradigms whether it's messaging or more of a bus style. So with our Jboss Fuse and our AMQ we've made great progress in continuing to refine how those are invoked and consumed in the Openshift environment. Forthcoming very shortly, literally in the next week or two is our integration platform as a service based on the Fuse and AMQ technologies. In addition we've continued to charge ahead with our API management solution based on the technology we acquired from Threescale a couple of years ago. So that is coming along nicely, being very well adopted by our customers. Then further up the stack on the process automation front, so some of the business process management types of technologies we've continued to push ahead with containerizing and that was being higher up the stack and a little bit bigger a scale of technology was a little bit more complex in really setting it up for the containerized world but we've got our Process Automation 7.0 release coming out in the next few weeks. That includes some exciting new technology around case management, so really bringing all of those traditional middleware capabilities forward into the Cloud Native, containerized environment has been I would say the most significant focus of our efforts over the last year. >> Go ahead. >> Can you contextualize some of that a little bit for us? The OpenShift obviously a big topic of conversation here. You know the new thing that everyone's looking at and Kubernetes, but these service layers, these layers it takes to build an app still necessary, Jboss a piece of this stack is 17, 18 years old, right? So can you contextualize it a little bit for people thinking about okay we've got OpenStack on the bottom, we've got OpenShift, where does the middleware and the business process, how has that had to be modernized? And how are people, the Java developers, still fitting into the equation? >> Mark: So a lot of that contextualization can actually, if we go back about four or five years, we announced an initiative called Xpass which was to essentially take the rich middleware suite of products and capabilities we had, and decompose them into independently consumable services kind of like what you see when you look at AWS. They've got the simple queuing service, simple messaging service. We have those capabilities but in the past they were bundled together in an app server, so we worked to pull them apart and allow people to use them independently so if you wanted transactions, or you wanted security, you didn't have to consume the whole app server you actually had these as independent services, so that was Xpass. We've continued on that road for the past few years and a lot of those services are now available as part and parcel of OpenShift. To get to the developer side of things, then we put language veneers on top of those because we're a Java company, well at least middleware is, but there's a lot more than Java out there. There's a lot of people who like to use Pearl or PHP or JavaScript or Go, so we can provide language specific clients for them to interact. At the end of the day, your JavaScript developer who's using bulletproof, high performing messaging doesn't need to know that most of it is implemented in Java. It's just a complete opaque box to them in a way. >> John F: So this is a trend of microservices, this granularity concept of this decomposition, things that you guys are doing is to line up with what people want, work with services directly. >> Absolutely right, to give developers the entire spectrum of granularity. So they can basically architect at a granularity that's appropriate for the given part of their job they're working on it's not a one size fits all proposition. It's not like throw all the monoliths out and decompose every last workload into it's finest grain possible pieces. There's a time and a place for ultra-fine granularity and there's also a time and a place to group things together and with the way that we're providing our runtimes and the reference architectures and the general design paradigm that we're sort of curating and recommending for our customers, it really is all about, not just the right tool for the job but the right granularity for the job. >> It's really choice too, I mean people can choose and then based on their architecture they can manage it the way they want from a design standpoint. Alright I got to get your guys' opinion on something. Certainly we had a great week in Copenhagen last week, in Denmark, around CUBECon, Kubernetes conference, Cloud NativeCon, whatever it's called, they're called two things. There was a rallying cry around Kubernetes and really the community felt like that Linix moment or that TCPIP moment where people talk about standards but like when will we just do something? We got to get behind it and then differentiate and provide all kinds of coolness around it. Core defacto stand with Kubernetes is opening up all kinds of new creative license for developers, it's also bringing up an accelerated growth. Istio's right around the corner, Cubeflow have the cool stuff on how software's being built. >> Right. >> So very cool rallying cry. What is the rallying cry in middleware, in your world? Is there a similar impact going on and what is that? >> Yeah >> Because you guys are certainly affected by this, this is how software will be built. It's going to be orchestrated, composed, granularity options, all kinds of microservices, what's the rallying cry in the middleware? >> So I think the rallying cry, two years ago, at Summit we announced something called MicroProfile with IBM, with Tomitribe, another apps vendor, Piara and a few quite large Java user groups to try and do something innovative and microservices specific with Enterprise Java. It was incredibly successful but the big elephant in the room who wasn't involved in that was Oracle, who at the time was still controlling Java E and a lot of what we do is dependent on Java E, a lot of what other vendors who don't necessarily talk about it do is also dependent on Java E to one degree or another. Even Pivotal with Springboot requires a lot of core services like messaging and transactions that are defined in Java E. So two years further forward where we are today, we've been working with IBM and Oracle and others and we've actually moved, or in process of moving all of Java E away from the old process, away from a single vendor's control into the Eclipse Foundation and although that's going to take us a little while longer to do we've been on that path for about four or five months. The amount of buzz and interest in the community and from companies big and small who would never have got involved in Java E in the past is immense. We're seeing new people get involved with Eclipse Foundation, and new companies get involved with Eclipse Foundation on a daily basis so that they can get in there and start to innovate in Enterprise Java in a much more agile and interesting way than they could have done in the past. I think that's kind of our rallying call because like I said we're getting lots of vendors, Pivotal's involved, Fujitsu. >> John F: And the impact of this is going to be what? >> A lot more innovation, a lot quicker innovation and it's not going to be at the slow speed of standards it's going to be at the fast, upstream, open source innovative speed that we see in likes of Kubernetes. >> And Eclipse has got a good reputation as well. >> Yeah, the other significant thing here, in addition to the faster innovation is it's a way forward for all of that existing Java expertise, it's a way for some of the patterns and some of the knowledge that they have already to be applied in this new world of Cloud Native. So you're not throwing out all that and having to essentially retrain double digit millions of developers around the world. >> John F: It's instant developer actually and plus Java's a great language, it's the bulldozer of languages, it can move a lot, it does a lot of heavy lifting >> Yep. >> And there's a lot of developers out there. Okay, final question I know you guys got to go, thanks for spending the time on theCUBE, really appreciate certainly very relevant, middleware is key to the all the action. Lot of glue going on in that layers. What's going on at the show here for you guys? What's hot, what should people pay attention to? What should they look for? >> Mark: I'll give my take, what's hot is any talk to do with middleware >> (laughs) Biased. >> But kind of seriously we do have a lot of good stuff going on with messaging and Kafka. Kafka's really hot at the moment. We've just released our own project which is eventually going to become a product called Strimsy, integrated with OpenShift so it's coognative from the get-go, it's available now. We're integrating that with OpenWhisk, which we talked about earlier, and also with our own reactive async platform called Vertex, so there's a number of sessions on that and if I get a chance I'm hoping to say into one >> John F: So real quick though I mean streaming is important because you talk about granularity, people are going to start streaming services with service measures right around the corner, the notion of streaming asynchronously is going to be a huge deal >> Absolutely, absolutely. >> Mark: And tapping into that stream at any point in time and then pulling the plug and then doing the work based on that. >> Also real quick, Kubernetes, obviously the momentum is phenomenal in Cloud Native but becoming a first class citizen in the enterprise, still some work to do. Thoughts on that real quick? Would you say Kubernetes's Native, is it coming faster? Will it ever be, certainly I think it will be but. >> I think this is the year of Kubernetes and of enterprise Kubernetes. >> Mike: I mean you just look at the phenomenal growth of OpenShift and that in a way speaks directly to this point >> Mike, what's hot, what's hot? What are you doing at the show, what should we look at? I'd add to, I certainly would echo the points Mark made and in addition to that I would take a look at any session here on API management. Again within middleware the three-scale technology we acquired is still going gangbusters, the customers are loving that, finding it extremely helpful as they start to navigate the complexity of doing essentially distributive computing using containers and microservices, getting more disciplined about API management is of huge relevance in that world, so that would be the next thing I'd add. >> Congratulations guys, finally the operating system called the Cloud is taking over the world. It's basically distributed computer all connected together, it sounds like >> All that stuff we learned in the eighties right (laughs) >> It's a systems world, the middleware is changing the game, modern software construction of Apple cases all being done in a new way, looking at orchestration, server lists, service meshes all happening in real time, guys congratulations on the all the work and Red Hats. Be keeping it in the open, Java E coming around the corner as well, it's theCUBE bringing it out in the open here in San Francisco, I'm John Furrier with John Troyer we'll be back with more live coverage after this short break

>> Narrator: Live from Austin, Texas, It's theCUBE, covering KubeCon and CloudNativeCon 2017. Brought to you by Red Hat, the Linux Foundation, and theCUBE's ecosystem partners. >> Welcome back and we're live here in Austin, Texas. theCUBE's exclusive coverage of CloudNativeCon and KubeCon, which stands for Kubernetes Conference, the not Cube, C-U-B-E, that's us. I'm John Furrier here with Matt Broberg, co-host in here for Stu Miniman, podcaster himself And we also have a special podcaster here on theCUBE, Edaena Salinas, who's the host of The Women in Tech Show @techwomenshow on Twitter, also a software engineer at Microsoft. Welcome to theCUBE, thanks for joining us. >> Thank you for having me. >> This is kind of like a podcast, we're like live though, we're streaming. >> Oh, okay. >> Love your sweater, that's a binary tree holiday tree. >> Binary Christmas tree. >> Binary Christmas tree. >> So perfect. >> I'm going to do a quick sort quickly, no I'm only kidding. So question for you, you've got a great program, you've got a desk over there, you're doing some interviews here, great to see you here doing The Women in Tech. We've done a lot of women in tech interviews on theCUBE, love to showcase women programming, women developers, women in stem, great that you do it so congratulations. So tell us what's the vibe like, are you people excited to do podcasting, is it all women, do you interview men, so tell us a little bit about the show. >> That's a good question. The motivation of the show is to have technical women talk about what they're working on, the products they're building or business strategy, instead of what does it feel like to be a woman in tech, or the only woman in the meeting room. Those conversations are valid, but I think we've heard a lot of those, and the community can benefit if they're just listening to what they're working on. >> It's great to get the education out there. So I have a question for you, I'd love to ask this. But I never really had a, talk about software engineering on theCUBE, what's the style difference in coding, do that's talked about, are women, do they code differently? Is it, probably neater, cleaner, is there biases in coding in that come into, because. >> I'm not aware of (laughs) difference like that, but, you could find that out if you run a script on the GitHub projects but, I don't think it affects. >> People don't, they don't talk about that, do they? >> They don't talk about that, and I certainly haven't experienced anything like that, and I learn from my coworkers and they learn from me. >> Now what are you working on at Microsoft? >> I am at Microsoft Research earlier this year, so what I work on is adding AI features to our existing products, like Outlook and Dynamics, so yeah. >> And I want to switch gears and talk about the podcast a little bit. So, I'm curious what was your inspiration to start it, and had you done podcasts before or did it just feel right, like this is the time to do something? >> I hadn't done a podcast before, but I had listened to a lot of shows. And the initial motivation of this is, at Microsoft where I work, they have this Meet Our Leader series, where they bring men and women in a leadership position. The audience is mostly women, and I was tuning in there by Skype, and there's 200 people listening to them plus people in the room, and they're asking questions about what's our business strategy or technical questions, so I'm like, women want to know about these things, and then in addition to that I noticed some women, technical women, they list on their website, I love giving talks, just not the diversity talk or the lady panel, I've given it several times, I just want to talk about cloud computing or the things that I work on. And then I looked if someone was doing this already, a show like this. I didn't find it, so I started it, and it helped that I listened to other shows. >> I mean I find when I talk to a lot of my women friends that are technical, sometimes CTOs and higher, and even down in programming, they don't want to, they just want to talk about what they're working on. They don't want to be the, that woman in tech on the panel, I've had a friend said to me privately over the weekend at a party, I don't, am sick and tired of being called and them saying, I need a woman on a panel. >> Yeah. >> I mean, it's kind of like a backlash, but they also feel obligated to do it. >> Yeah. There's kind of a new culture developing. Talk about that, and what that kind of conversation's like in your world. >> Well what I've heard, for example Sheryl Sandberg I think has said, there, we will reach a point someday where we won't be called a female CEO or a woman engineer, it would just be engineer. So, that's our goal, to just lose that label at someday, right now, the show has the label because I'm raising awareness of having them talk about technical topics. As more people hear about them, it's just going to be natural and normal like, sure I learned from Nicole about Kubernetes, and then men are also listening to the show, which I think benefits a lot the community. >> I have two daughters, one's in high school, one's in college, one's at Cal, and they're techies, they're science, they like science, not coding yet. Their mom doesn't want them to be like me and code, but, so they're, but they're-- >> Just give them the choice >> I said hey, do you do Cube interviews, it's also an option. But in their culture, when I ask them about this, they're like, we don't think about it. So there's a, at their level, they're all in school together and it's interesting, I think a time is coming now where the awareness is putting the old guard pressures away, there's still some bad behavior, no doubt about it, I see it everyday and it's being called out, thank god, but now it's just like, you're a person in tech. >> Exactly. >> So I think respect is the number one, respect for the individual is something that we always preach, independent of who the person is, male, female, whatever. >> Yeah, exactly, and we will reach that point soon, I hope so, where we lose the label. >> So you're 77 episodes in, I'm also a listener, I learned a ton from it, you have brilliant people on every week. I really admire you for that because I know how hard it is to produce a podcast. What are some of the things you didn't know before starting a podcast that like, oh wow, that takes more energy than it looked like at the time. >> That's a good point, yes. The very first few interviews that I did, I didn't take into account how the guest would respond. So I prepared the questions in advance, and then I would think, this is going to be a two-minute answer, but the person just ended up saying yes, no, or sure, that's a big problem, and I was counting on it to be more, so I needed to prepare in that aspect and what helps is just, if they've already given talks, just look them up on YouTube or find all their interviews they've done, just to get a sense of how they talk. There's also people that tend to give super long answers, and you need to prepare for that, how you're going to handle it. >> I noticed you had someone from Bitnami came by recently, was that Erica? >> Erica Brescia came on the show a few months ago, the COO of Bitnami, and in that episode we focused a lot on entrepreneurship, she came out of YC, so sort of building Bitnami to where it is, and today I interviewed the engineering manager of Bitnami, and she talked about Kube apps and all this security aspects. >> What are some of the innovations you're seeing in your interviews? Can you highlight some examples recently that jump out at you, that are, lot of innovation coming from these ladies, what are some of things that they've done? Shine the light on some of the awesome highlights from your guests. >> One of my favorite ones is Rachel Thomas, she works at Fast.ai, what she works on is bias in machine learning. Machine learning is about learning from your data, but I've heard, this woman at a conference bring it up, like, if I'm a minority, I'm a minority in the data. So you need to take that into account. So there's a lot of people working in the space. That was a really cool project I think. >> Data driven analysis. >> Yeah, but sort of, considering that bias that can be in that data, and make sure your data is better. So for example, it's a known fact that there's a lot of men in the technology field, so if you're going to get job recommendations, if a person like me, Mexican, I studied computer science but if I'm a minority in the dataset, maybe I'm not going to get the recommendation. I'm not saying that how it works, but that could potentially be an issue. >> It's a statistical fact. >> Yeah, but if you don't take that into account in your system, maybe women are not getting job recommendations, of openings. >> That's a good point. >> So, it brings up-- >> That's a really powerful observation, right, and I was curious, as a software engineer, software engineering is your craft and podcasting is your hobby, how has podcasting influenced your software engineering skills? Because ultimately that's the path you're going down career-wise. >> Well a big part of software engineering is about talking to your team and going to meetings, talking about solutions. Podcasting has help me a lot, improve my soft skills. For a period of time I was editing my own shows. One thing that I noticed is when I was talking to my guests, I'm listening to my recording, when I would say an idea, I would tend to lower my voice. So I noticed that, and then I said to myself, I'm probably doing this in the meetings at work, and then, I work-- >> What an amazing insight, right, like now you're seeing how you're presenting yourself in front of other people in technical ways and then you get to bring that into your work. >> Yeah, whenever I would say an idea I would just be like, what happens if we do this instead? That was like I have to-- >> That's a great example of self-awareness, right, I mean, everyone should do that, listen to their, look at their actions. >> Yes, so it helps with the soft skills. And it also helps if you're working in a certain area of software engineering, and you want to find out more about it, you can decide to do more shows on that and just share that with the community that women are working on this. >> It's great to see you have some Cube alumni like Erica on, we interviewed her on theCUBE at Google Next a few years ago. Share some coordinates, when does the show go out, when do you record it, does it ship on a regular cadence, share a little information. >> The show is released weekly. I publish Monday evenings, but I share it on social media on Tuesday mornings, so if you're subscribed, you would get it Monday evenings. >> Good for the week, running, on the bike, in the car. >> It's 30 minutes. >> Any video podcasting coming? >> I don't have any video, no. >> Lot more editing required, trust me on that one. Cool. What's the most exciting thing that you're working on right now? You have the podcast, which is a super cool hobby, great to get those voices out there, so congratulations. But at work, what are you working on? >> Yes, well like I mentioned earlier, I work on a team it's a team under Microsoft Research, a lot of it, we don't know what people working on there, but, my team works closely with product teams. So we're adding AI features to Outlook and Dynamics CRM. Just to increase the productivity aspect, in this sense. >> So you're bringing applied R and D to the product groups, mostly AI? >> Yes, yeah. >> What's the coolest thing in AI that you like? >> Oh wow, well I really like recommendation systems and things like that. >> All right, well thanks for coming on theCUBE, really appreciate it, The Tech Women podcast here, they got a booth over there. Doing great interviews, here's at theCUBE we're doing our share. Two days, the second day of live wall to wall coverage. Be right back with more live coverage, in Austin Texas. You here the music, this is the big D, Texas here in Austin Texas. More live coverage, that's Dallas, we're in Austin. Be right back with more live coverage after this short break. (futuristic music)

>> Announcer: Live from Austin, Texas, it's theCUBE. Covering KubeCon and CloudNativeCon 2017. Brought to you by: Red Hat, the Linux Foundation, and theCUBE's ecosystem partners. >> Hey, welcome back everyone. And we're live here in Austin, Texas. This is theCUBE's exclusive coverage of the Cloud Native conference and KubeCon for Kubernetes Conference. This is for the Linux Foundation. This is theCUBE. I'm John Furrier, the co-founder of Silicon ANGLE Media. My co, Stu Miniman. Our next guest is Dustin Kirkland Vice-President of product. The Ubuntu, Canonical, welcome to theCUBE. >> Thank you, John. >> So you're the product guy. You get the keys to the kingdom, as they would say in the product circles. Man, what a best time to be-- >> Dustin: They always say that. I don't think I've heard that one. >> Well, the product guys are, well all the action's happening on the product side. >> Dustin: We're right in the middle of it. >> Cause you got to have a road map. You got to have a 20 mile steer on the next horizon while you go up into the pasture and deliver value, but you always got to be watching for it always making decision on what to do, when to ship product, not you got the Cloud things are happening at a very accelerated rate. And then you got to bring it out to the customers. >> That's right. >> You're livin' on both sides of the world You got to look inside, you got to look outside. >> All three. There's the marketing angle too. which is what we're doing here right now. So there's engineering sales and this is the marketing. >> Alright so where are we with this? Because now you guys have always been on the front lines of open source. Great track record. Everyone knows the history there. What are the new things? What's the big aha moment that this event, largest they've had ever. They're not even three years old. Why is this happening? >> I love seeing these events in my hometown Austin, Texas. So I hope we keep coming back. The aha moment is how application development is fundamentally changing. Cloud Native is the title of the Cloud Native Computing Foundation and CloudNativeConference here. What does Cloud Native mean? It's a different form of writing applications. Just before we were talking about systems programing right? That's not exactly Cloud Native. Cloud Native programming is writing to API's that are Cloud exposed API's, integrating with software as a service. Creating applications that have no intelligence, whatsoever, about what's underneath them, Right? But taking advantage of that and all the ways that you would want and expect in a modern application. Fault tolerance, automatic updates, hyper security. Just security, security, security. That is the aha moment. The way applications are being developed is fundamentally changing. >> Interesting perspective we had on earlier. Lew Tucker from Cisco, (mumbles) in the (mumbles) History Museum, CTO at Cisco, and we have Kelsey Hightower co-chair for this conference and also very active in the community. Yet, in the perspective, and I'll over simplify and generalize it, but basically was: Hey, that's been going on for 30 years, it's just different now. Tell us the old way and new way. Because the old way, you kind of describing it you're going to build your own stuff, full stack, building all parts of the stack and do a lot of stuff that you didn't want to do. And now you have more, especially time on your hands if DevOps and infrastructure as code starts to happen. But doesn't mean that networking goes away, doesn't mean storage goes away, that some new lines are forming. Describe that dynamic of what's new and the new way what changes from the old way? >> Virtualization has brought about a different way of thinking about resources. Be those compute resources, chopping CPU's up into virtual CPU's, that's KVM ware. You mentioned network and storage. Now we virtualized both of those into software defined storage and software defined networking, right? We have things like OpenStack that brings that all together from an infrastructure perspective. and we now have Kubernetes that brings that to fare from an application perspective. Kubernetes helps you think about applications in a different way. I said that paradigm has changed. It's Kubernetes that helps implement that paradigm. So that developers can write an application to a container orchestrator like Kubernetes and take advantage of many of the advances we've made below that layer in the operating system and in the Cloud itself. So from that perspective the game has changed and the way you write your application is not the same as a the monolithic app we might have written on an IBM or a traditional system. >> Dustin, you say monolithic app versus oh my gosh the multi layered cake that we have today. We were talking about the keynote this morning where CNCF went from four projects to 14 projects, you got Kubernetes, You got things like DSDU on top. Help up tease that a little bit. What are the ones that, where's canonical engaged? What are you hearing from customers? What are they excited about? What are they still looking for? >> In a somewhat self-serving way, I'll use this opportunity to explain exactly what we do in helping build that layered cake. It starts with the OS. We provide a great operating system, Ubuntu that every developer would certainly know and understand and appreciate. That's the kernel, that's the systemd, that's the hyperviser, that's all the storage and drivers that makes an operating system work well on hardware. Lot's of hardware, IBM, Dell HP, Intel, all the rest. As well as in virtual machines, the public Clouds, Microsoft, Amazon, Google, VM ware and others. So, we take care of that operating system perspective. Within the CNCF and within in the Kubernetes ecosystem, It really starts with the Kubernetes distribution. So we provide a Kubernetes distribution, we call it Canonicals Distribution of Kubernetes, CDK. Which is open source Kubernetes with security patches applied. That's it. No special sauce, no extra proprietary extensions. It is open source Kubernetes. The reference platform for open source Kubernetes 100% conformed. Now, once you have Kubernetes as you say, "What are you hearing from customers?" We hear a lot of customers who want a Kubernetes. Once they have a Kubernetes, the next question is: "Now what do I do with it?" If they have applications that their developers have been writing to Google's Kubernetes Engine GKE, or Amazon's Kubernetes Engine, the new one announced last week at re:Invent, AKS. Or Microsoft's Kubernetes Engine, Microsoft-- >> Microsoft's AKS, Amazons EKS. A lot of TLA's out there, always. >> Thank you for the TLA dissection. If you've written the applications already having your own Kubernetes is great, because then your applications simply port and run on that. And we help customers get there. However, if you haven't written your first application, that's where actually, most of the industry is today. They want a Kubernetes, but they're not sure why. So, to that end, we're helping bring some of the interesting workloads that exists, open source workloads and putting those on top of Canonical Kubernetes. Yesterday, we press released a new product from Canonical, launched in conjunction with our partners at Rancher Labs, Which is the Cloud Native platform. The Cloud Native platform is Ubuntu plus Kubernetes plus Rancher. That combination, we've heard from customers and from users of Ubuntu inside and out. Everyone's interested in a developer work flow that includes open-source Ubuntu, open-source Kubernetes and open-source Rancher, Which really accelerates the velocity of development. And that end solution provides exactly that and it helps populate, that Kubernetes with really interesting workloads. >> Dustin, so we know Sheng, Shannon and the team, they know a thing or two about building stacks with open source. We've talked with you many times, OpenStack. Give us a little bit of compare and contrast, what we've been doing with OpenStack with Canonical, very heavily involved, doing great there versus the Cloud Native stacking. >> If you know Shannon and Sheng, I think you can understand and appreciate why Mark, myself and the rest of the Canonical team are really excited about this partnership. We really see eye-to-eye on open source principles First. Deliver great open source experiences first. And then taking that to market with a product that revolves around support. Ultimately, developer option up front is what's important, and some of those developer applications will make its way into production in a mission critical sense. Which open up support opportunities for both of us. And we certainly see eye-to-eye from that perspective. What we bring to bare is Ubuntu ecosystem of developers. The Ubuntu OpenStack infrastructure is a service where we've seen many of the world's largest organizations deploying their OpenStacks. Doing so on Ubuntu and with Ubuntu OpenStacks. With the launch of Kubernetes and Canonical Kubernetes, many of those same organizations are running their own Kubernetes along side OpenStack. Or, in some cases, on top of OpenStack. In a very few cases, instead of Openstack, in very special cases, often at the Edge or in certain tiny Cloud or micro Cloud scenarios. In all of these we see Rancher as a really, really good partner in helping to accelerate that developer work flow. Enabling developers to write code, commit code to GitHub repository, with full GitHub integration. Authenticate against an active directory with full RBAC controls. Everything that you would need in an enterprise to bring that application to bare from concept, to development, to test into production, and then the life cycle, once it gains its own life in production. >> What about the impact of customers? So, I'm an IT guy or I'm an architect and man, all this new stuff's comin' at me. I love my open source, I'm happy with space. I don't want to touch it, don't want to break it, but I want to innovate. This whole world can be a little bit noisy and new to them. How do you have that conversation with that potential customer or customer where you say, Look, we can get there. Use your app team here's what you want to shape up to be, here's service meshes and plugable, Whoa plugable (mumbles)! So, again, how do you simplify that when you have conversations? What's the narrative? What's the conversation like? >> Usually our introduction into the organization of a Fortune 500 company is by the developers inside of that company who already know Ubuntu. Who already have some experience with Kubernetes or have some experience with Rancher or any of those other-- >> So it's a bottoms up? >> Yeah, it's bottoms up. Absolutely, absolutely. The developer network around Ubuntu is far bigger than the organization that is Canonical. So that helps us with the intro. Once we're in there, and the developers write those first few apps, we do get the introductions to their IT director who then wants that comfy blanket. Customer support, maybe 24 by seven-- >> What's the experience like? Is it like going to the airport, go through TSA, and you got to take your shoes off, take your belt off. What kind of inspection, what is kind of is the culture because they want to move fast, but they got to be sure. There's always been the challenge when you have the internal advocate saying, "Look, if we want to go this way "this is going to be more the reality for companies." Developers are now major influencers. Not just some, here's the product we made a decision and they ship it to 'em, it's shifted. >> If there's one thing that I've learned in this sort of product management assignment, I'm a engineer by trade, but as a product manager now for almost five years, is that you really have to look at the different verticals and some verticals move at vastly different paces than other verticals. When we are in the tele close phase, We're in RFI's, requests for a quote or a request for information that may last months, nine months. And then go through entering into a procurement process that may last another nine months. And we're talking about 18 months in an industry here that is spinning up, we're talking about how fast this goes, which is vastly different than the work we do in Silicon Valley, right? With some of the largest dot-coms in the world that are built on Ubuntu, maybe an AWS or else where. Their adoption curve is significantly different and the procurement angle is really different. What they're looking to buy often on the US West Coast is not so much support, but they're looking to guide your roadmap. We offer for customers of that size and scale a different set of products something we call feature sponsorships, where those customers are less interested in 24 by seven telephone support and far more interested in sponsoring certain features into Ubuntu itself and helping drive the Ubuntu roadmap. We offer both of those a products and different verticals buy in different ways. We talked to media and entertainment, and the conversation's completely different. Oil and gas, conversation's completely different. >> So what are you doing here? What's the big effort at CloudNativeCon? >> So we've got a great booth and we're talking about Ubuntu as a pretty universal platform for almost anything you're doing in the Cloud. Whether that's on frame infrastructure as a service, OpenStack. People can coo coo OpenStack and point OpenStack versus Kubernetes against one another. We cannot see it more differently-- >> Well no I think it's more that it's got clarity on where the community's lines are because apps guys are moving off OpenStack that's natural. It's really found the home, OpenStack very relevant huge production flow, I talk to Johnathon Bryce about this all the time. There's no co cooing OpenStack. It's not like it's hurting. Just to clarify OpenStack is not going anywhere its just that there's been some comments about OpenStack refugees going to (mumbles), but they're going there anyway! Do you agree? >> Yeah I agree, and that choice is there on Ubuntu. So infrastructure is a service, OpenStack's a fantastic platform, platforms as a service or Cloud Native through Cloud Native development Kubernetes is an excellent platform. We see those running side by side. Two racks a systems or a single rack. Half of those machines are OpenStack, Half of those are Kubernetes and the same IT department manages both. We see IT departments that are all in OpenStack. Their entire data center is OpenStack. And we see Kubernetes as one workload inside of that Openstack. >> How do you see Kubernetes impact on containers? A lot of people are coo cooing containers. But they're not going anywhere either. >> It's fundamental. >> The ecosystem's changing, certainly the roles of each part (mumbles) is exploding. How do you talk about that? What's your opinion on how containers are evolving? >> Containers are evolving, but they've been around for a very long time as well. Kubernetes has helped make containers consumable. And doctored to an extent, before that the work we've done around Linux containers LXE LEXT as well. All of those technologies are fundamental to it and it take tight integration with the OS. >> Dustin, so I'm curious. One of the big challenges I have the U face is the proliferation of deployments for customers. It's not just data center or even Cloud. Edge is now a very big piece of it. How do you think that containers helps enable the little bit of that Cloud Native goes there, but what kind of stresses does that put on your product organization? >> Containers are adding fuel to the fire on both the Edge and the back end Cloud. What's exciting to me about the Edge is that every Edge device, every connected device is connected to something. What's it connected to, a Cloud somewhere. And that can be an OpenStack Cloud or a Kubernetes Cloud, that can be a public Cloud, that could be a private implementation of that Cloud. But every connected device, whether its a car or a plane or a train or a printer or a drone it's connected to something, it's connected to a bunch of services. We see containers being deployed on Ubuntu on those Edge devices, as the packaging format, as the application format, as the multi-tendency layer that keeps one application from DOSing or attacking or being protected from another application on that Edge device. We also see containers running the micro services in the Cloud on Ubuntu there as well. The Edge to me, is extremely interesting in how it ties back to the Cloud and to be transparent here, Canonical strategy and Canonical's play is actually quiet strong here with Ubuntu providing quite a bit of consistency across those two layers. So developers working on those applications on those devices, are often sitting right next to the developers working on those applications in the Cloud and both of them are seeing Ubuntu helping them go faster. >> Bottom line, where do you see the industry going and how do you guys fit into the next three years, what's your prediction? >> I'm going to go right back to what I was saying right there. That the connection between the Edge and the Cloud is our angle right there, and there is nothing that's stopping that right now. >> We were just talking with Joe Beda and our view is if it's a shoot and computing world, everything's an Edge. >> Yeah, that's right. That's exactly right. >> (mumbles) is an Edge. A light in a house is an Edge with a processor in it. >> So I think the data centers are getting smarter. You wanted a prediction for next year: The data center is getting smarter. We're seeing autonomous data centers. We see data centers using metals as a service mask to automatically provision those systems and manage those systems in a way that hardware look like a Cloud. >> AI and IOT, certainly two topics that are really hot trends that are very relevant as changing storage and networking those industries have to transform. Amazon's tele (mumbles), everything like LAN and serverless, you're starting to see the infrastructure as code take shape. >> And that's what sits on top of Kubernetes. That's what's driving Kubernetes adoption are those AI machine learning artificial intelligence workloads. A lot of media and transcoding workloads are taking advantage of Kubernetes everyday. >> Bottom line, that's software. Good software, smart software. Dustin, Thanks so much for coming theCube. We really appreciate it. Congratulations. Continued developer success. Good to have a great ecosystem. You guys have been successful for a very long time. As the world continues to be democratized with software as it gets smarter more pervasive and Cloud computing, grid computing, Unigrid. Whatever it's called it is all done by software and the Cloud. Thanks for coming on. It's theCube live coverage from Austin, Texas, here at KubeCon and CloudNativeCon 2017. I'm John Furrier, Stu Miniman, We'll be back with more after this short break. (lively music)

>> Narrator: Live from Austin Texas. It's theCUBE, covering KubeKon and CloudNativeCon 2017. Brought to you by Red Hat, the Linux Foundation, and theCUBE's ecosystem partners. >> Welcome back everyone, live here in Austin Texas, theCUBE's exclusive coverage of CloudNativeConference and KubeKon, for Kubernetes' Conference. I'm John Furrier, co-founder of SiliconANGLE and my co-host Stu Miniman, our analyst. And next is Matt Klein, a software engineer at Lyft, ride-hailing service, car sharing, social network, great company, everyone knows that everyone loves Lyft. Thanks for coming on. >> Thanks very much for having me. >> All right so you're a customer of all this technology. You guys built, and I think this is like the shiny use cases of our generation, entrepreneurs and techies build their own stuff because they can't get product from the general market. You guys had a large-scale demand for the service, you had to go out and build your own with open source and all those tools, you had a problem you had to solve, you build it, used some open source and then give it back to open source and be part of the community, and everybody wins, you donated it back. This is, this is the future, this is what it's going to be like, great community work. What problem were you solving? Obviously Lyft, everyone knows it's hard, they see their car, lot of real time going on, lot of stuff happening >> Matt: Yeah, sure. >> magic's happening behind the scenes, you had to build that. Talk about the problem you solved. >> Well, I think, you know, when people look at Lyft, like you were saying, they look at the app and the car, and I think many people think that it's a relative simple thing. Like how hard could it be to bring up your app and say, I want a ride, and you know, get that car from here to there, but it turns out that it's really complicated. There's a lot of real-time systems involved in actually finding what are all the cars that are near you, and what's the fastest route, all of that stuff. So, I think what people don't realize is that Lyft is a very large, real-time system that, at current scale, operates at millions of requests per second, and has a lot of different use cases around databases, and caching, you know, all those technologies. So, Lyft was built on open source, as you say, and, you know Lyft grew from what I think most companies do, which is a very simple, monolithic stack, you know, it starts with a PHP application, we're a big user of MongoDB, and some load balancer, and then, you know-- >> John: That breaks (laughs) >> Well, well no but but people do that because that's what's very quick to do. And I think what happened, like most companies, is, or that most companies that become very successful, is Lyft grew a lot, and like the few companies that can become very successful, they start to outgrow some of that basic software, or the basic pieces that they're actually using. So, as Lyft started to grow a lot, things just didn't actually start working, so then we had to start fixing and building different things. >> Yeah, Matt, scale is one of those things that gets talked about a lot. But, I mean Lyft, you know, really does operate at a significant scale. >> Matt: Yeah, sure. >> Maybe you can talk a little bit about, you know, what kind of things were breaking, >> Matt: Absolutely, yeah, and then what led to Envoy and why that happened. >> Yeah, sure. I mean, I think there's two different types of scale, and I think this is something that people don't talk about enough. There's scale in terms of things that people talk about, in terms of data throughput or requests per second, or stuff like that. But there's also people scale, right. So, as organizations grow, we go from 10 developers to 50 developers to 100, where Lyft is now many hundreds of developers and we're continuing to grow, and what I think people don't talk about enough is the human scale, so you know, so we have a lot of people that are trying to edit code, and at a certain size, that number of people, you can't all be editing on that same code base. So that's I think the biggest move where people start moving towards this microservice or service-oriented architecture, so you start splitting that apart to get people-scale. People-scale probably usually comes with requests per second scale and data scale and that kind of stuff. But these problems come hand in hand, where as you grow the number of people, you start going into microservices, and then suddenly you have actual scale problems. The database is not working, or the network is not actually reliable. So from Envoy perspective, so Envoy is an open source proxy we built at Lyft, it's now part of CNCF, it's having tremendous uptake across the industry, which is fantastic, and the reason that we built Envoy is what we're seeing now in the industry is people are moving towards polyglot architectures, so they're moving towards architectures with many different applications, or many different languages. And it used to be that you could use Java and you could have one particular library that would do all of your networking and service discovery and load balancing, and now you might have six different languages. So how as an organization do you actually deal with that? And what we decided to do was build an out-of-process proxy, which allows people to build a lot of functionality into one place, around load balancing, and service discovery, and rate limiting, and buffering, and all those kinds of things, and also most importantly, observability. So things like tracing and stats and logging. And that allowed us to actually understand what was going on in the network, so that when problems were happening, we could actually debug what was going on. And what we saw at Lyft, about three years ago, is we had started our microservices journey, but it was actually almost, it was almost stopped, because what people found is they had started to build services because supposedly it was faster than the monolith, but then we would start having problems with tail latency and other things, and they didn't know hot to debug it. So they didn't trust those services, and then at that point they say, not surprisingly, we're just going to go back and we're going to build it back into the monolith. So, we're almost in that situation where things are kind of in that split. >> So Matt I have to think that's the natural, where you led to service mesh, and Istio specifically and Lyft, Google, IBM all working on that. Talk a little bit about, more about what Istio, it was really the buzz coming in with service mesh, there's also there's some competing offerings out there, Conduit, new one announced this week, maybe give us the landscape, kind of where we are, and what you're seeing. >> So I think service mesh is, it's incredible to look around this conference, I think there's 15 or more talks on service mesh between all of the Buoyant talks on Linker D and Conduit and Istio and Envoy, it's super fantastic. I think the reason that service mesh is so compelling to people is that we have these problems where people want to build in five or six languages, they have some common problems around load balancing and other types of things, and this is a great solution for offloading some of those problems into a common place. So, the confusion that I see right now around the industry is service mesh is really split into two pieces. It's split into the data plane, so the proxy, and the control plane. So the proxy's the thing that actually moves the bytes, moves the requests, and the control plane is the thing that actually tells all the proxies what to do, tells it the topology, tells it all the configurations, all the settings. So the landscape right now is essentially that Envoy is a proxy, it's a data plane. Envoy has been built into a bunch of control planes, so Istio is a control plane, it's reference proxy is Envoy, though other companies have shown that they can integrate with Istio. Linker D has shown that, NGINX has shown that. Buoyant just came out with a new combined control plane data plane service mesh called Conduit, that was brand new a couple days ago, and I think we're going to see other companies get in there, because this is a very popular paradigm, so having the competition is good. I think it's going to push everyone to be better. >> How do companies make sense of this, I mean, if I'm just a boring enterprise with complexity, legacy, you know I have a lot of stuff, maybe not the kind of scale in terms of transactions per second, because they're not Lyft, but they still have a lot of stuff. They got servers, they got data center, they got stuff in the cloud, they're trying to put this cloud native package in because the developer movement is clearly pushing the legacy guy, old guard, into cloud. So how does your stuff translate into the mainstream, how would you categorize it? >> Well, what I counsel people is, and I think that's actually a problem that we have within the industry, is that I think sometimes we push people towards complexity that they don't necessarily need yet. And I'm not saying that all of these cloud native technologies aren't great, right, I mean people here are doing fantastic things. >> You know how to drive a car, so to speak, you don't know how to use the tech. >> Right, and I advise companies and organizations to use the technology and the complexity that they need. So I think that service mesh and microservices and tracing and a lot of the stuff that's being talked about at this conference are very important if you have the scale to have a service-oriented microservice architecture. And, you know, some enterprises they're segmented enough where they may not actually need a full microservice real-time architecture. So I think that the thing to actually decide is, number one, do you need a microservice architecture, and it's okay if you don't, that's just fine, take the complexity that you need. If you do need a microservice architecture, then I think you're going to have a set of common problems around things like networking, and databases, and those types of things, and then yes, you are probably going to need to build in more complicated technologies to actually deal with that. But the key takeaway is that as you bring on, as you bring on more complexity, the complexity is a snowballing effect. More complexity yields more complexity. >> So Matt, might be a little bit out of bounds for what we're talking about, but when I think about autonomous vehicles, that's just going to put even more strain on the kind of the distributed natured systems, you know, things that have to have the edge, you know. Are we laying the groundwork at a conference like this? How's Lyft looking at this? >> For sure, and I mean, we're obviously starting to look into autonomous a lot, obviously Uber's doing that a fair amount, and if you actually start looking at the sheer amount of data that is generated by these cars when they're actually moving around, it's terabytes and terabytes of data, you start thinking through the complexity of ingesting that data from the cars into a cloud and actually analyzing it and doing things with it either offline or in real-time, it's pretty incredible. So, yes, I think that these are just more massive scale real-time systems that require more data, more hard drives, more networks, and as you manage more things with more people, it becomes more complicated for sure. >> What are you doing inside Lyft, your job. I mean obviously, you're involved in open source. Like, what are you coding specifically these days, what's the current assignment? >> Yeah, so I'm a software engineer at Lyft, I lead our networking team. Our networking team owns obviously all the stuff that we do with Envoy, we own our edge system, so basically how internet traffic comes into Lyft, all of our service discovery systems, rate limiting, auth between services. We're increasingly owning our GRPC communications, so how people define their APIs, moving from a more polling-based API to a more push-based API. So our team essentially owns the end-to-end pipe from all of our back-end services to the client, so that's APIs, analytics, stats, logging, >> So to the app >> Yeah, right, right, to the app, so, on the phone. So that's my job. I also help a lot with general kind of infrastructure architecture, so we're increasingly moving towards Kubernetes, so that's a big thing that we're doing at Lyft. Like many companies of Lyft's kind of age range, we started on VMs and AWS and we used SaltStack and you know, it's the standard story from companies that were probably six or eight years old. >> Classic dev ops. >> Right, and >> Gen One devops. >> And now we're trying to move into the, as you say, Gen Two world, which is pretty fantastic. So this is becoming, probably, the most applicable conference for us, because we're obviously doing a lot with service mesh, and we're leading the way with Envoy. But as we integrate with technologies like Istio and increasingly use Kubernetes, and all of the different related technologies, we are trying to kind of get rid of all of our bespoke stuff that many companies like Lyft had, and we're trying to get on that general train. >> I mean you guys, I mean this is going to be written in the history books, you look at this time in a generation, I mean this is going to define open source for a long, long time, because, I say Gen one kind of sounds pejorative but it's not. It's really, you need to build your own, you couldn't just buy Oracle database, because, you probably have some maybe Oracle in there, but like, you build your own. Facebook did it, you guys are doing it. Why, because you're badass, you had to. Otherwise you don't build customers. >> Right and I absolutely agree about that. I think we are in a very unique time right now, and I actually think that if you look out 10 years, and you look at some of the services that are coming online, and like Amazon just did Fargate, that whole container scheduling system, and Azure has one, and I think Google has one, but the idea there is that in 10 years' time, people are really going to be writing business logic, they're going to insert that business logic >> They may do a powerpoint slides. >> That would be nice. >> I mean it's easy to me, like powerpoint, it's so easy, that's, I'm not going to say that's coding, but that's the way it should be. >> I absolutely agree, and we'll keep moving towards that, but the way that's going to happen is, more and more plumbing if you will, will get built into these clouds, so that people don't have to worry about all this stuff. But we're in this intermediate time, where people are building these massive scale systems, and the pieces that they need is not necessarily there. >> I've been saying in theCUBE now for multiple events, all through this last year, kind of crystallized and we were talking about with Kelsey about this, Hightower, yesterday, craft is coming back to programming. So you've got software engineering, and you've got craftsmanship. And so, there's real software engineering being done, it's engineering. Application development is going to go back to the old school of real craft. I mean, Agile, all it did was create a treadmill of de-risking rapid build scale, by listening to data and constantly iterating, but it kind of took the craft out of it. >> I agree. >> But that turned into engineering. Now you have developers working on say business logic or just solving, building a healthcare app. That's just awesome software. Do you agree with this craft? >> I absolutely agree, and actually what we say about Envoy, so kind of the catchword buzz phrase of Envoy is to make the network transparent to applications. And I think most of what's happening in infrastructure right now is to get back to a time where application developers can focus on business logic, and not have to worry about how some of this plumbing actually works. And what you see around the industry right now, is it is just too painful for people to operate some of these large systems. And I think we're heading in the right direction, all of the trends are there, but it's going to take a lot more time to actually make that happen. >> I remember when I was graduating college in the 80s, sound old but, not to date myself, but the jobs were for software engineering. I mean that is what they called it, and now we're back to this devops brought it, cloud, the systems kind of engineering, really at a large scale, because you got to think about these things. >> Yeah, and I think what's also kind of interesting is that companies have moved toward this devops culture, or expecting developers to operate their systems, to be on call for them and I think that's fantastic, but what we're not doing as an industry is we're not actually teaching and helping people how to do this. So like we have this expectation that people know how to be on-call and know how to make dashboards, and know how to do all this work, but they don't learn it in school, and actually we come into organizations where we may not help them learn these skills. >> Every company has different cultures, that complicates things. >> So I think we're also, as an industry, we are figuring out how to train people and how to help them actually do this in a way that makes sense. >> Well, fascinating conversation Matt. Congratulations on all your success. Obviously a big fan of Lyft, one of the board members gave a keynote, she's from Palo Alto, from Floodgate. Great investors, great fans of the company. Congratulations, great success story, and again open source, this is the new playbook, community scale contribution, innovation. TheCUBE's doing it's share here live in Austin, Texas, for KubeKon, for Kubernetes conference and CloudNativeCon. I'm John Furrrier, for Stu Miniman, we'll be back with more after this short break. (futuristic music)

>> Narrator: Live from Austin, Texas, it's The Cube covering KubeCon and CloudNativeCon 2017. Brought to you by Red Hat, the Linux Foundation, and The Cube's ecosystem partners. >> Welcome back, everyone. Live here, The Cube's exclusive coverage in Austin, Texas. This is CloudNativeCon and KubeCon for Kubernetes Conference. I'm John Furrier, Stu Miniman. My next two guests from Red Hat, Joe Brockmeier, senior evangelist, Linux Containers, Red Hat and Kimberly Craven, Director of Portfolio Marketing at Red Hat. Welcome to The Cube, good to see you guys. >> Thank you, good to see you, too. So I was saying at re:Invent last week that Red Hat's stamp of approval has always been in the enterprise. You guys are, you know, winning the enterprise, been there for years. But now, at Cloud Native, kind of things are coming together. You've got a lot of customers that have been, I won't say quietly going with Red Hat with OpenShift, and now with Kubernetes. Huge bet a few years ago. >> Mmhmm. >> Yep. >> Only two years ago. Kind of changed the game. >> Yeah, fortunately we made a strategic decision to replatform our own platform on Kubernetes and it was the right decision to make. So we've been lucky in that we've been able to, I'd say we've been able to invest in the right open source projects. So Joe, would you agree that over the years, I mean, starting with Linux. >> Yep. >> But in other technologies as well? >> Yeah, historically, I think we, not every, not 100% of the time, but a large enough percentage of the time, picked the right horse community wise. Open Stack, now Kubernetes, Linux-Colonel, obviously. I used to work for a company called LinuxMall and we sponsored these Linux pavilions. And I remember NetBSD guys telling me how Linux was doomed because it wasn't as elegant. >> Doomed, it sure didn't turn out that way. But certainly, the community model has changed. You're starting to see, you know, Dan Cohen, in his opening slide, actually kind of laid out the circle of innovation, project, products and profit. >> Joe: Yeah. >> And so now, it's okay to have profitability objectives as an outcome of great products. And so still bringing in the culture of innovation because the business market for this is pretty large. I see the number of people coming on board. The demand is pretty strong. >> Not just innovation, but I think, one of the important things about Kubernetes is that is has been a community project where it's a community of equals contributing to the project. And it's about each company bringing the right thing for the project, not the right thing necessarily just for that company, but the right thing for the overall project, which is really important. >> Timing's everything, right? I mean, as they say in life, but remember, all that FUD about past layers and infrastructures as a service, and again, the DevOps community was still growing. No one really talks about that anymore because people just want working software. >> Joe: Right. >> Right? So it's fun not to have those kind of conversations. Instead, the conversation's about how to orchestrate great workloads, how to onboard and accelerate more application developers. This is the narrative that we wanted a couple years ago. Now it's here. What are you guys doing at Red Hat to take that to the next level? >> Kimberly: So I'm going to defer to Joe for that one. >> Joe: Okay. To take that to the next level. First, before people can get to the next level, one thing I want to point out is that while everybody here is hip deep in Kubernetes and they're ready, there are a lot of companies out there that are still digesting virtualization and still digesting cloud. >> Kimberly: Right. >> Private or public, and so one of our key roles is actually to help them consume open-source software and get from Point A to Point B. So the role that we're really playing right now is about taking customers with their workloads today that are running on bare metal, that are running on virtualization, that are pet workloads, right? And getting those into the cloud and getting in those into Kubernetes and that sort of thing. So the next level for a lot of folks is actually getting up to speed to the things that were announced today. >> Right. >> Well the question I want to ask, that I want to get this on the record, 'cause it's important to get the definition, what does Kubernetes mean to the enterprise? For us in Cloud Native, we understand what it is, we get it, but to the enterprise customer, what does Kubernetes mean to them? So I would say, based on the customer conversations that we've had, it's all about getting your workloads to the cloud and being more cloud native much more quickly. So that's the end goal for adopting containers and adopting Kubernetes. It's all about getting to be in a position where you can migrate your workloads to the cloud but also develop new on the cloud much more quickly than you could before. So it's about automating, it's about all of the processes behind that, if you will. >> Joe, comment? >> I agree with everything Kimberly said. I would also just add I think it's really about kind of an almost an end-stage of software packaging, which is something that Red Hat has been doing for 20+ years, is figuring out how do we take goodness of software, open-source software, and get it into a consumable format? First it was RPM, then it was YUM, now it's containers, now it's orchestrated containers that are, you know, able to be worked on with service mesh and all these other wonderful things, cloud native storage. It's basically about taking that software and making it scale. >> Yeah, I mean, yours is a service mesh. So let's take it to the next level of customer conversation. I love this stuff, I'm going to the cloud as soon as possible. I got some stuff in the public stuff now, I got a lot of on-premise stuff activity, I love hybrid cloud. So I got a lot of different use cases. I got some bare metal, I got some hybrid cloud and I got some public cloud. Is this where the OpenShift fits in? I mean, in that environment of a customer conversation, what's the current state of the art for Red Hat to engage that customer? >> So organizations, they're taking inventory of everything that they have today. So they're looking at what do they have on bare metal today, what do they have in virtualization, what different workloads do they have and where does it make sense to deploy them both financially and from an advancement perspective? Because some workloads don't have to be, they don't have to be advanced as quickly. You don't have to make additional updates. But there are other workloads that are moving much more quickly. And one of the things that Red Hat does and where we help our customers, especially with OpenShift, is we allow them to deploy those workloads across, whether they're going to on-premises with a bare metal if you say, or as well as virtualization, private cloud, potentially a mixture of multicloud environment where they have some workloads going to Google, some workloads going to AWS, and some going to Azure. It's being able to do that consistently, that OpenShift for guidance. >> Is that a common use case right now? Is that the number one use case, this hybrid? >> So when you say that, the hybrid cloud, it's not, it's a combination of multiple use cases. People aren't necessarily looking just yet to take the same workload and move it such that it's spanning multiple clouds, but they want to have that flexibility so that if they choose to go to a certain public cloud, and it becomes it's not cost-effective for them to do so anymore, they want to be able to take that workload and move it. And that's what we're working towards. >> Joe, I got to ask about OpenShift because, you know, we've been following you guys since the Open Stack days and now with the formation of this, seeing nice lines of sight of value proposition. What's going on with OpenShift? We're hearing a lot of good customer wins, a lot of people are using it. I heard a comment in the hallway saying that OpenShift has more customers than most of these vendors here combined. I'm not sure I believe that, that might have been just kind of chatter, but is that true or can you share the success? Because it's been on a tear. What are some of the OpenShift success points? >> Kimberly: Well-- >> So is it true there are more customers than all everyone else combined? >> I'd like to say so, I mean-- >> John: Pretty close or-- >> You were at Red Hat Summit this past year back in the May timeframe and we had many OpenShift customers that were on stage. I mean, it was-- >> John: You got lots. >> Yeah, we had to turn sessions away from customers because we didn't have enough room for them. >> So one of the things we actually haven't gotten to highlight yet at this event, Red Hat does, at a lot of these shows, ahead of the show, it's called OpenShift Commons, maybe you can give our audience a little bit of what goes into that. 'Cause all the container shows, the Cloud Native shows, you know, OpenShift has been there. >> Yeah, with OpenShift Commons, it's a great way for the community to collaborate around OpenShift specifically. It's, whether it be with our ISVs, working with our ISVs on different plugins to extend OpenShift as well as our customers to be able to provide us with feedback in terms of what they're looking for. And then we take that to the community. For example, Clayton was a top contributor. That was announced yesterday. >> Yes, Clayton got an award offered for that on stage, yeah. >> Yeah, and in essence, our customers are providing feedback to us directly in OpenShift Commons and in other forums. And that allows us to steer the community more effectively to meet their needs. >> I just want to add it's not a two-way conversation with Commons. It's also, you know, I was also there on Tuesday when we did Commons and we had Tellus, for example, telling their story to the other customers in the room. And so they're not just telling us, like, hey, this works for us, this doesn't work. They're telling each other and they're sharing successes, which is part of the wonder of open sourcing community. It's not just about, you know, you can have, I don't want to use an example, you can have a two-way conversation with any vendor that's taking your money. How many vendors are bringing you together to talk to your other customers? You have to have a lot of confidence, I think, in people being happy with your solution to build something out like that. >> Yeah, and experience, too. You guys had the experience. >> Yeah, you mentioned, we were right about that time, we'd been there a number of years. I feel the open source community is a little bit better at allowing those customers to kind of come forward. Because not only are they using it, they're usually contributing to some of these technologies. Some traditional shows, you know, getting a customer to get up on stage is pretty challenging. Any comments on that? >> Well it's funny because I think it's getting much easier, moving forward, for customers to participate in the communities, as you'll see with Netflix, for example. They were up on stage earlier and talking about the contributions that they're also making to the community. I think that it's much easier than it was even, I'd say, 5-10 years ago. With that said, there are a lot of customers that want help in terms of creating additional functionality in the community where they might have something that's, perhaps, not quite ready, not quite good enough, that we help to shepherd. >> Is there a profile of customer that's adopting Kubernetes? I mean, I've seen a lot of media coverage, obviously Netflix is on AWS. ACHB on stage today. Is it coincidental that there'd be two large big media online kind of companies, or-- >> Well, it's funny you should ask that because we're conducting a research project and we recently got some data back where we, in essence, sent out a survey to customers and non-customers to see where their adoption was. What we're finding is financial services, the media, communications organization, government, and even healthcare, to some extent, are taking a look at and adopting. I'd say that, based on the adoption curve, what's funny to note is, with government, government started looking, on average, at containers three years ago, whereas with financial services, they started to get more heavily invested, now this is in general, if you're looking at the median, two years ago. With that said, I think that financial services is actually adopting containers more quickly than government is. >> I'd love to see the data on that survey because we're always doing kind of probing, anecdotal kind of stirrup holes, friends and guests of The Cube. And it's the trend, from our standpoint, is that it seems that anywhere that there's been this transformation opportunity. >> Kimberly: Mmhmm. >> I mean, look at government. Who would've though public sector could be so fast and change? So public sector, media and entertainment, people with their modernizing seems to be where the action is. But financial services is always going to be on the IT dollar spend. But like, I mean, I'm really surprised at how fast public sector is evolving. >> And what's interesting about it, too, is also the industries that are predominantly concerned with security. Security and performance are very important to financial services and to government and to communications. And it's interesting how quickly this technology is being adopted with those considerations. >> Joe, one of the things coming into the show, I listened to some previews and they're saying, you know, we're not even going to talk about containers of the show. Of course, there's containers kind of underneath. Maybe speak a little bit about that dynamic. Red Hat, you know, so heavily involved. You know, of course Linux containers, you know, underneath there. Compare and contrast to kind of what we're kind of doing here in the Kubernetes and Cloud Native space. >> Yeah, so it really isn't about the individual container anymore than five years ago it was about the individual RPM. The container runtime and the ability to spin up a container is table stakes. And so that is no longer really where the value is. Same as like, hypervisors in cloud. Like, the real value is not in the hypervisor. It's around that, it's the ecosystem around it and the ability to do it. So yeah, I mean, we're still talking about, it's funny, when I have conversations, not here, but in other places, the parlance is still to say containers when they really mean, you know, like Kubernetes and orchestration, the whole schmear. But yeah, it's not where the value and the action is these days. >> Where's the Red Hat situation with the people now? Because we've seen, we've noticed, that you guys have really kind of continued to evolve as a company. Obviously, I mean, or in the early days of Red Hat, open source wasn't tier one. You guys made it tier one as a culture, that's well-documented. But then there's a whole new Red Hat mojo going on now. OpenShift, seeing you bringing that same principles. Talk about what's going on in the company now. We've seen a lot of smart people continuing to do the Red Hat thing. What is Red Hat now in the marketplace? The same old Red Hat? What's different, what's the same? 'Cause you guys are doing really well. >> Kimberly: Mmhmm. >> What's it like there? >> I think, I've been at Red Hat for about six years and I would say that the culture has continued to evolve since I joined. One of the things that first attracted me about it was that there are a lot of smart people that work at Red Hat and it's a very collaborative culture. It's a culture that's based on meritocracy and the best ideas truly win. So very similar to the way that OpenSource projects are run or should be run, for the good OpenSource projects, it's very much about getting people together, hearing what everyone has to say, and making sure that the right ideas are the ones that move forward. >> John: Surely they attract great people, too. >> Yeah. >> To build on that, in this industry there's so much kind of hype, boom and bust. On the outside, you look at it, I mean, from a financial standpoint, Red Hat's one of the most consistent performers out there. You know, quarter after quarter, Kim talks about the growth. So you know, I'm not asking you to talk about the financials but, you know, worth a show. Nobody here can keep up with all the changes. So you know, just, when you talk about all these projects and everything, Red Hat, can you keep up with the changes? Or is it just that you've got so many people and contribute so many places? >> We're working on it and I think, I mean, the nice thing about it is that everybody's very passionate about all of those changes that are happening. And we like change, oddly enough, we embrace it. It's interesting, but that's one of the parts of being at Red Hat. And I'd say, I mean, I would think that that's something that's inherent to us. >> Well, I mean, our corporate mission, part of our corporate mission is to be the catalyst for change and communities. And we, you know, I've worked at a couple of larger companies and this is the only one where I feel like if I don't agree with something I can send an email directly to Jim and say, "I don't agree with this and I think we should do something different." >> And he'll respond within four hours. >> And Jim will respond unless he's on a plane. >> Yeah, he'll respond and you know, even if they don't agree, which is impossible, everybody always agrees with me. (group laughs) But even if they don't agree, you know, they engage honestly and respectfully, and that's super important in this kind of industry. If you can't do that, you can't run with open source. >> Joe, Kimberly, thanks for coming on The Cube, and continued success and thanks for all the Red Hat contribution. You guys are doing a great job in the community. Continue to appreciate it. >> Thank you. >> Red Hat, here on The Cube, continuing to do the Red Hat thing. Red Hat, stamp of approval from the enterprise. Certainly well-respected and the leader inside The Cube here at the CloudNativeCon and KubeCon for KubernetesCon, not Cube. I'm John Furrier, Stu Miniman. We'll be back with more after this short break. (upbeat music)

>> Narrator: Live from Austin, Texas. It's theCUBE, covering KubeCon and CloudNativeCon 2017. Brought to you by Red Hat, the Linux Foundation, and theCUBE's ecosystem partners. >> Hey, welcome back everyone, we're here live at theCUBE in Austin, Texas for KubeCon 2017, 2nd annual conference of the Kubernetes Conference, I'm John Furrier, here with my co-host, Stu Miniman, Ben Sigelman, who's the CEO of LightStep, welcome to theCUBE. >> Thank you so much. >> So you're also involved in open tracer, all this stuff with service mesh, really instrumental tech work going on right now. >> Mmhmm, yep. >> With this KubernetesCon, I mean Kubernetes has been successful. People are now learning for, the first time in mainstream, but it's really galvanized the community. At many levels, and I haven't seen this much action and so fast, up and down the stack. You know, you got the infrastructure plumbing guys, and you got the app plumbing guys all building really, really fast. What's the state of the union? Give us a peak of what's happening, what's solid, what's foundational? What are the building blocks that are being built on and what's the current task of jobs being worked on projects and what not? >> Yeah, and that's a great question. I was, emerged my hotel room yesterday just to get on the elevator and Kelsey Hightower emerged from his hotel room, turns out two doors down from me, and we're walking to the elevator together, I'm like, "Hey! You know, so, what's your big announcement?" He's so good on stage, he's a brilliant communicator, and he's like, you know, honestly, the big news right now, is that actually there's not that much news from a release standpoint about Kubernetes, which is actually a really big deal. It's gotten to the point where it's feature set is actually appropriate and somewhat stable. And now we finally are at the point where it's, I think, it has a really natural architecture for plugins and extensions and now we can build this entire ecosystem around it, instead of building around something that's a bit of a moving target. I think it's incredible how, it is truly incredible, to see this conference over the last couple of years. >> So Pete's foundational elements are in place. >> Yeah. >> That's his, kind of his... >> Yeah, exactly. And it's incredible to see how much of, not just a commercial ecosystem, but a technology ecosystem, that's built around those primitives, and so I think those really are the right primitives, to democratize the pieces that should be democratized, and to centralize the pieces that should be centralized. So to me, this year is really about going a level up in the stack, and delivering value that's beyond, you know, the container, Kubernetes level, and that's what a lot of the projects that I'm excited about are doing. >> Yeah, so Ben, and that leads right into one of the things that we've been talking about all week here, service meshes. >> Ben: Yeah. >> So, you gave a keynote yesterday, maybe give our audience a little bit about service meshes, servibility, and there's something about a pigeon? >> (laughs) Yeah that was very funny. Just the reference about the pigeon, the first slide in my talk was a picture of a murmuration of starlings, this beautiful cloud of birds moving in harmony, and while I was waxing on about how this represented microservices, an actual bird flew above me on stage. There was a pigeon trapped in this room `(laughter) and so everyone started laughing, I didn't know what was so funny, I'm like... >> Jeez. What a great demo. >> ...like what did I do wrong? Do I have a note on my back or something? And then the hilarious thing is the second slide was actually the operational experience of deploying this sort of microservice technology is actually very difficult, and so it was this slide from Alfred Hitchcock's "The Birds," with these birds attacking this poor child. And so, and the bird is still circling around above me. It was perfect stagecraft, I wish I had tried to do it, it would have been amazing to take credit for arranging an actual live animal as part of my presentation. But in terms of the actual material in the presentation, which may be less entertaining than the bird flying around my head, but the material of the presentation is something I feel very strongly about, and I alluded to this a moment ago, I think that containers are incredibly important, I think Kubernetes is incredibly important, and I am extraordinarily confident that in ten years, they're going to be everywhere. That said, they're not something an application developer really should care that deeply about as part of their job of writing business logic for the service that they are maintaining and developing. That shouldn't be a layer that they care about. And there are a lot of really, really important problems that crop up at the application layer. At Google, the way we addressed this, was by having not a monolithic architecture, but a monolithic software repository where everyone developed the same code base, but one of the things that I thought was interesting was being at Google, if you wanted to deploy an application, even something that just printed out 'Hello, world' or something, it was like a 150 megabyte binary, because there's so much stuff that was crammed in to level 7, user level stuff, and that was right for Google, it's not really the best architecture for a lot of enterprises out there and I think what's so cool about service mesh, is that it's taken a bunch of really, genuinely hard computer science problems, like service discovery, connection, and load balancing, and reconnection, health checks, security and authentication, observability and tracing, these are really hard things to do well, and it's factored them off into a side car that you can run alongside ordinary applications that were not even developed with that in mind and take advantage of these application level, level 7 primitives. We've had people who are trying to build solutions for any number of managerial and monitoring tasks at the container level, where often that stuff is completely obscured. Like by the time you're at the kernel that you can't see any of this stuff. If you're up at level 7 in the service mesh, you have easy access to application level data, which makes everything a lot more elegant and straightforward for developers, so it's like, to me, it's this single point of integration that removes a bunch of hard computer science problems from ordinary application development. >> And so people were stuffing containers basically and trying to overdrive that. Makes total sense architecturally and I want you to take a step back and kind of unpack that a little bit. We didn't get here by accident. We got here through real hard work, I mean people were out there building from open-source large-scale systems. >> Yeah. >> Uber, Lyft, there's a handful of other examples. What was the driver around this, because you're talking about a really elegant architecture that allows for solving a problem for the guys that solve their own problems. Thousands, hundreds of thousands of transactions, services, millions of transactions per second. >> Yup. >> So this was not like "Hey, let's just design a new system!" It was some scar tissue. >> Yeah. >> How does that connect to like, reality now for, whether it's a start-up saying "Hey, you know, we're a couple of years old, we're on AWS, and we're growing, and I want to add more value, but I don't want to relearn machine learning, I want to build on all this stuff and create business value from my enterprise, growing an enterprise. Or, big enterprises, trying to be cloud enabled. So that's, how should someone think about that? And what specifically was the problem that was solved? >> Yes. Well, I'm an obsessive person, I'll admit that. And I'm personally obsessed with performance, and so when I think about this, I actually think about profiling the engineers who are building this stuff. You have developers, let's profile them, like what are they spending their time on? 'Cause that's really a precious resource right now, right? It's like, it's hard to even hire people fast enough, right? So if you think about profiling people, you have folks that are spending a lot of time trying to get their services communicated properly, to authenticate, to observe these systems, in a way that's sane. And so it's only natural you try to factor that out and make that factored out. You try to amortize the cost of solving that problem across your entire organization. And I think that you've seen people who've been at other companies, and want to recreate something like what they had at Google or Facebook or Twitter or what have you, but they want to do it in a way that meshes with their existing systems. I'm actually not surprised that super, super young companies that are starting with the true green field code base, move in this direction. What has been interesting to me, and although I shouldn't say surprising, this is actually very rational, but you also have companies that are much larger, and we, LightStep has, we have customers that are running a mainframe, alongside legacy Java VMs, alongside microservices, and they're all working in concert to the service application requests from end users. And these things need to talk to each other, and I think what's actually really fun for me, Google gets a lot of credit for building things the right way, I don't know if that's accurate for not, but it's really funny 'cause the problem is actually a lot more interesting outside of Google, because you have to integrate with a much larger surface area and the thing that's so exciting to me about a lot of the technologies that are really taking off here, is that they're designed for that kind of heterogeneity, certainly I've talked about service mesh a million times already here, open tracing also exists specifically because of heterogeneity, we didn't need open tracing at Google because everything was perfectly factored, so it was unnecessary. Outside of Google, it's necessary to have a common API to describe transactions as they propagate, because otherwise, you can't make sense of anything that's happening in your application. This sort of heterogeneity has encouraged projects that standardize at the right layer, and I think those are the ones that are proliferating. >> What is service mesh about now? I mean, how would you describe it, I mean, how would you define, in the world of Kubernetes, in the world we're talking about, for someone just getting, tech person, just getting started. What's the hubbub about with service mesh? What is it? >> Well, I mean, I think at the most basic level, it's something that sits in between any two processes that are communicating in your system, and it sits in between them at a layer where you can observe the application itself. Like, you're able to access application levels, security information application level, primitives like, you know, the particular path you're hitting for any HTP requests, something like that. It's something that sits in between at that layer. Because microservices, you know, I've seen Lyft up close 'cause they're also a customer for LightStep, and to see Envoy deployed at their company is really instructive. It's amazing, I mean it's really amazing. They went from having no integration with our product to having 100% integration with our product by flipping a configuration bit to on, you know. Actually it wasn't even on, they could do it by percentage, I mean, they can roll these things out with perfect, perfect precision. And, I mean, it's an incredibly powerful thing to be able to have that kind of leverage over an entire architecture and that didn't require all their developers to redeploy. This system required the service mesh to redeploy, so you make these sorts of changes without touching application CSCD stuff, you can do all these infrastructural level changes independently from application pushes-- >> All right, >> And that's very powerful. >> So, so hold on, I know Stu wants to get a question in, but let's stop there for a second. Compare and contrast what the old way would have been. >> Stu: Yeah. What would it have taken to do this similar concept that full team had met, assuming they had another architecture. >> I've seen, I mean, you know- >> John: Months, weeks, redeploys... >> So, you know, the model that I've seen at Google where would we make changes to software that was linked into every application would go out with the next release, we would make that change in some central place, I'd say 50% of the services would be deployed within a week, 90% within two weeks, but to get to 99% would take over a year, and so the issue is if you need a change that's going to cut across your entire system, it is not feasible to wait for people to redeploy because there are going to be services that are not being maintained by human beings anymore, and no one's about to volunteer for that chore- >> John: It's a nightmare basically. >> Of reintegrating, taking in months of code changes, making sure it still works and deploys. >> Yeah, they're going to quit right there. I mean, no one wants that. >> It's infeasible. >> Yeah, it's not feasible. >> Ben, I wanted you to be able to share a little bit about founding LightStep, you know what's kind of the need in the market, and what you're seeing from your early customers. >> Sure, LightStep is, it has a pretty simple mission. We aim to deliver insights about very complex production software, which is commonplace at this point. Anyone who's building a meaningful business is building meaningful production software, and that means it's complicated. So that's what we want to do. The way that we're doing that with our first product, LightStep XPM, is by delivering root cause analysis for the symptoms that are of most interest to these businesses, regardless of their application or architecture, as I said earlier, we have customers that run mainframes as well as microservices at the same time, multi-cloud, it doesn't matter. We follow transactions across these distributed services and use those to explain behaviors that they're puzzling over and help them with performance analysis and root cause analysis. >> And what's the relationship between the open source projects and... >> That's a great question. It's not a normal open core model. Open tracing is really an API project that's designed to ease integration with any number of vendors, and open tracing is supported by LightStep of course, but also by Jaeger, and CNCF, it's compatible with Zipkin, it's supported by New Relic and Datadog, I'll give a shoutout to some competitors. We're all in this together in the sense that I think we see that we all have a much bigger market as things like open tracing proliferate, and make it easier to actually observe your own system. I would love to compete in the playing field of solutions and not worry so much about integration, so open tracing is an integration project, it's not our core technology. Our core IP is something that's very powerful, that's designed to absorb a lot of information about these distributed systems and deliver value about that. >> And when I look at your website, and see kind of some of your early customers, I mean, jump out, you know, Lyft, Twilio, Digital Ocean, I mean, these are not kind of your typical companies, is it, you know, fully kind of cloud-native, you know, horn of the web, type companies? >> I'm really glad you asked that. No. >> Stu: Yeah. >> I mean, most of our customers at this point are, have actually never seen a full microservice deployment, certainly not at one of customers. It's always a combination of a monolith in the middle and microservices on the outside, but a lot of our customers are more traditional enterprises that we haven't put on our website for logo rights reasons, but they get a lot value out of the solution, I would say even more value in some cases because they're dealing with a greater diversity of technology generations they need to cut across. >> Yeah, I want to go back. You mentioned the time for people these days and you talk about developers and people building, the fight for talent is huge out there. What are you seeing in your customers? Is that something that you help? How's kind of that interaction? >> Yeah absolutely, I mean, I think, Digital Ocean says they're saving, I think 1000 engineer hours a month or something like that on LightStep. It's a huge timesaver for people who are trying to get to the bottom of issues. So it's a labor issue, but also root cause analysis, I mean, every second counts. Seconds cost hundreds of thousands of dollars for some of our customers for any big outage, and so we help people get those, Twilio's addressing the instance 92% faster after using LightStep, so it's a big change to their root cause analysis. >> Yeah, there was a great quote I saw that said, "When something goes wrong, it used to be you knew, now it turned into a murder mystery." >> Yeah. (laughter) >> Tell the story of why did you start the company. Was there an itch you were scratching? You saying, "Hey, you know, I've seen this movie before, I want to get out there, help customers, I mean, I heard, your mission is really straightforward, clean, good positioning. Why start the company? What was the rationale? What was the motivation? >> That's a very easy one for me. I mean, the reason I left Google was not necessarily to start a company per se, it was that I wanted to have as much of an impact on the industry as I could, I wanted to see things, not just make money and siphon cash away from companies, but actually to change the way that software is built. And the first act for us, this product, is a way for us to kind of get into the tendril, get our system deep into the fabric of an application, and from that point, I'd like to see LightStep really change the way people build software. I think people right now, it's almost like everyone's programming an assembly. Like we're all trying to operate this level that's totally inappropriate, and I'd love to see LightStep be a part of this story for making the industry move up the value chain and really focus on building applications, and that's what I want to see us do. >> You know, we've been saying, first, we have a similar mission along our media business, but one of the things we're seeing, we go to all the shows, sometimes it's like, why is theCUBE covering, you know, Node.js, or why are you covering Hadoop in 2010, why are you, because we see it early, we get in early, as I said, we can see the innovation, we like it, but I got to tell you, we've been seeing recently, I've been seeing it specifically, we see a huge renaissance in software development companies. >> Yeah, for sure. >> And my piece is, I want to test this with you because I think this is going to change the culture, certainly in Silicon Valley and around the world. Certainly with open source is exponentially growing, you know, Zemlin puts that stat up pretty clear. All software development models was crafty and built a product you QA and you'd ship it, it either worked or it didn't work, put some art to it, around ownership, and then AdJail derisked that risk, but you can get it to the market quicker, and you listen to the data, you learn from the data, but it kind of took the craft out of it. You know what I'm saying, almost we're coding and we're iterating, we're on a treadmill, which is good. But now, with what we're seeing here, is that you're getting back to extracting away, to your point, all these services you don't need to worry about anymore. I could actually focus all of my attention on the artisan aspect of the solution. Not UX, love UX design, not that kind of art, but something about software art. What's your reaction to that? Do you see that coming? Because if this continues, we're going to have a whole class of software developers just essentially painting software art, if you will. >> Yeah. >> I mean, that potentially is a scenario. Your thoughts. >> Yes, I agree with that scenario being feasible. I think it's probably more than a couple of weeks away, but I'm really excited about it. I think you're right on the money, I think a lot of the changes that we're seeing allow people to operate more independently and that's what motivates the transitions to microservice in the first place, it wasn't just to rewrite everyone's software for fun, it was because we want everyone to be able to be independent of each other and operate in that mode. The thing that I think is exciting about that vision which I would echo is a lot of the primitives that we see in the marketplace right now allow developers to focus on the semantics of application and the requirements of application which is where all of the interesting stuff is, and what we all get excited about. And I think we do see a lot of the, this number of people here right now, that investment as a community in allowing developers to focus on the logic and nothing more is really tremendous and exciting to me. >> How has community changed? I know you believe in community. Community's more important than ever now, in this new model, 'cause there's so much leverage going on with the software. How important is community and how is it changing and how should it evolve to handle all this awesome growth? >> Yeah I do have some thoughts about that. It's definitely important, I mean no one's going to deny that. I think one of the biggest challenges that I think about anyway in this sphere, has to do with, I referred to this earlier, it's important to figure out what problem you're solving with the community aspect of things, like with open tracing we thought really hard about this, like are we going to focus on, like, the bits and bytes and the wire protocols, or on the part that really needs to be standardized. I think community makes sense when standards are appropriate and standard interfaces are appropriate. I'm actually a little bit skeptical of community driven solutions where it's, you're delivering the entire package as a community because it ends up intersecting in ways that are complex I think with business motivations. I think the most successful projects are areas where the community really must collaborate, which usually has something to do with standardization. Those are the areas where I'm most excited. And then you actually literally, I was talking with Ken Goldberg yesterday, and they intentionally carved out areas for vendors to play, because they don't want to kind of meddle in that are. It's actually better not to meddle in that area. It's actually better- >> It's like microservices, you put the vendors over there and you put core commuters over there. Ben Sigelman, thanks for coming on theCUBE, I appreciate it. Congratulations on LightStep and the success and your talks here. Early community exploding, cloud native is not only a movement, it's clear to everyone, cloud and data and software and open source is making it happen, easier, accelerating velocity. It's theCUBE, doing our part, bringing you the data, here in Texas, I'm John Furrier, with Stu Miniman. We're back with more live coverage after this short break. >> Thank you. (techno music)

(upbeat music) >> Announcer: Live from Austin, Texas, it's the Cube, covering Kubecon and CloudNativeCon 2017. Brought to you by Red Hat, the Linux Foundation, and the Cube's Ecosystem partners. >> Hello and welcome back to the Cube's exclusive coverage live in Austin, Texas here for the three day CloudNative and now two days of KubeCon, Kubernetes conference. We had the second annual conference celebrating the evolution and growth of Kubernetes. I'm John Furrier, my cohost Stu Miniman and next guest Steve Watt, Chief Architect of Emerging Technologies at Red Hat, welcome back to the Cube. Good to see you. >> Thanks for having me, always a pleasure. >> So Red Hat making some good bets, some Kubernetes, not a bad call. >> No, Kubernetes has done wonders for our openship business, absolutely. (laughter) >> So how is this all playing out? We were just talking before we came on camera here about the just the pace of change. You been at Red Hat five years. We interviewed you when you were at HB during the big day to days, boy the world has certainly grown and changed. What has changed in your mind the most the people need to understand? >> I think Kubernetes has been a single biggest driving force to shift all enterprising architecture from scale up to scale out and I think that has just created a whole number of ripple effects across how applications are designed within the enterprise. >> I think that's the big one. >> Yeah. >> So Steve, that whole shift from scale up to scale out has affected lots of parts of the stack, but storage is something you've been working on, something we've been keeping a close eye on and was one of the top items we wanted to kind of dig into this week. Maybe, bring us inside a little bit, what's happening, what's Red Hat's role? >> Sure. >> Help explain. >> Absolutely, one of my favorite topics. It's kind of counterintuitive. I work in a CT office, I run the emerging technologies team, which is sort of the team that does the experiments that help shape and inform our long term strategy. And so you might think, well storage is kind of old news, how does that fit into this CloudNative world? Why does Red Hat care about it so much for their platform? And I think if you look at the CloudNative stack today, you have GKE, the new Amazon Kubernetes service, Azure, et cetera, these are all places where you can run your Kubernetes app, but just in that one place. Red Hat's platform perspective's a little different. We want you to be able to run your platform in an open hybrid cloud, whether that's in Google, in Azure or on premise, on OpenStack or on Bare Metal So you want to be able to run everywhere, but what's the biggest problem to achieving that application portability? It's data locking, so storage becomes cool again. (laughter) We got to solve this problem. >> Because you got to store the data somewhere. >> Steve: Right. >> And that's in the storage devices. >> Right, exactly. >> In the new way, the architecture. >> The new architecture, right? So the problem is, you've got to be very careful that if you want to move, ever you should think upfront about your persistence platform, so that it gives you the freedom to be able to move around. So Red Hat is investing heavily in trying to solve this problem. We've got a few exploratory prototypes that we're actually showing at this conference. And we work in both Kubernetes, building out the storage sub-system there, but also sort of in our products for like container native storage. >> Steve walk us through a little bit because we've been talking about this in the Docker Ecosystem for a bunch of years, where are we, what's being worked on? What still needs to be kind of sorted out? >> So, yeah that's interesting, I think we're finally over the hump where everybody's asking, Who's solving the persistence problem for containers? It used to drive me crazy, that went on for about three years. I think people finally realize, there are solutions. Kubernetes has always had them actually. And so, we've got past sort of the day one, like being able to, dynamically provision. Kind of like you'd see with Cinder in OpenStack. We've got a great storage. we've got a vibrant huge storage ecosystem and at our Kubernetes face to face meetings we have 50 people, they're like a mini conference. So we've got broad engagement from the entire storage ecosystem and that's doing everything that you need sort of on the file level, but there is recent (mumbles) work that we've done in Kubernetes for Service Broker is now the pattern to sort of provision object storage if you need it and most importantly, we've just enabled lock storage in Kubernetes in the 1.9 release that ships this week. And that is really interesting because it opens up the potential to run virtualization with loads on Kubernetes. >> Where's the action for the projects with storage? I heard some hallway rumbles just when I was, the Rook project. >> Steve: Yeah. >> Is that something, what projects, if I'm interested in storage, where do I dive in? Where's the most action for moving the needle for tuning the innovation around storage. >> I think it's if you're a storage vendor it's different if you're a storage consumer so Rook is a project that's focused on providing a sort of an abstraction for software defined storage platforms to run inside Kubernetes. Cluster doesn't take that approach, we've used sort of more of the pure Kubernetes approach. Sort of get to the same place. But Rook is definitely an interesting project in that, it's sort of an inception level project phase. Then for people that are wanting to consume storage, I think Kubernetes is the king of the pack. I obviously have a strong opinion on it, amongst the other container orchestrators, but the amount of investment in allowing people to do more continually more sophisticated features, you know snapshot's in, you know cloning, things like that. And obviously, I'm sure you've heard a little bit about container storage interface. >> Yes. >> CSI, and that makes it a lot easier for storage vendors to build one adapter that works across, Decos, Cloud foundry, Kubernetes, et cetera. >> What's the biggest surprise here for you, because we've been looking trying to read the tea leaves. Obviously Kubernetes, clear the runway, good standardization seeing some commoditization, great adoption, although people can tailor it. A lot of different versions, still early. >> Steve: Yeah. >> We're only two years old conference. >> I know. >> Three years it's been around. What's surprising you right now? What's jumping out at you? >> I think Amazon's announcement yesterday was very interesting. I think the fact that it's heartening to see that there's pure Kubernetes as a service being offered in Azure, Google and Amazon. And I think that quite interesting for affordability standpoint, right. And so I think to me that was a big surprise. Amazon doesn't usually go the pure vanilla open source approach and also the statements they're going to contribute back to Kubernetes, I think is quite interesting as well. So to me that's the one thing that stood out. >> What's going on for the future too? You mentioned you've got to set the roadmap. You guys have an agenda there obviously of installed base. >> Steve: Yeah. >> Now you've got OpenShift doing really well. What are you guys looking at? What's on your radar, how do you see this thing unfolding? What's in your mind? >> Yeah, I think there's a couple of really interesting things. Container orchestration is a legitimate disruption to virtualization. And that it solves the same problem opportunity space but in a fundamentally different manner that reshapes the market. I think the Kubert project is something that we're working on at Red Hat. It's another one of our sort of emerging technology focus areas. And when we enable block storage and it enables virtualization, what it gives us the opportunity to do in Kubernetes is have a single deployed platform that can serve both later adopters and early adopters. So the early adopters with pure container orchestration, but if you're wanting to have the same platform and do virtualization too on it, you can have sort of one investment, one shared experience to be able to do all of those. I think that's pretty cool. (laughter) >> Steve, talk about the customers that are watching or will be hearing over the next few months and a year around how to architectually package this and think about it in their mind. Whether it's a mental model or specifics. 'Cause there's always going to be that time tested trade off between performance, security and so you have, obviously people have VM's, not going away, but containerization where Google say, hey, we don't really care about VM's, we're a container company. There's always still going to be trade offs. >> Steve: Yeah. >> Speed, security. >> Steve: Security. >> So security factors in there. How should a practitioner think about getting their arms around this? >> I think this is the tact that OpenShift takes which is that Kubernetes is a decent project. Despite the huge amount of interest and contributions that we have and its maturity curve as far as, there are different things at attention, like enterprise use cases, versus public cloud use cases. And so we're very focused on our enterprise use cases and sort of enabling that inside OpenShift and bringing OpenShift up as a platform back to sort of enterprise level that our customers would expect. Virtualization platforms are much further down the maturity curve, and so I think that's sort of our approach is that, where that tries to meet our customers where they are. Some organizations have teams that are more advanced. Some that are less advanced. And so we try to offer, you know if you want to go virtualization we've got OpenStack, we've got Rev. If you want you could use this new school Kubernetes based container orchestration and you got teams understand it. (laughter) And you corrupt microservices then we've got a solution for that. >> Well you know that whole theme here is infrastructures is boring storage. It used to be called snorage back in the day. >> Steve: Yeah. >> It's pretty boring but relevant. Most people look at like Lambda from Amazon and some other serverless trends and certainly see them here with ServiceMesh and what not, the abstraction way of infrastructure, it's almost eliminating storage in the mind of the developer, yet it's changing, how are you guys specifically riding that wave? Because one, it's good for developers. >> Steve: Right. >> The velocity of developers increases, but the role of storage is changing. You mention block, people are like, oh block-- >> Yeah. >> It's dead. I mean storage has been dead for like 20 years now? >> Steve: Yeah. >> It keeps growing and growing, but now the role changes to the developer, abstracted away and also more important for automation and some of the dev ops things. What specifically are you guys doing? >> So, I think you said the word role. That's really important right? Like to an application developer what you said is absolutely true, they want to use persistence platforms for storing their data in a cloud native way, okay. However, the maturity code is also important. Not every application developer team is fully microservice based and understands all these architectural patterns. It's a journey, right? So we want to basically give them multiple options along their journey. So that's the one around the application persistence. So if they used to like file storage or object storage, et cetera, like we have our container native storage platform provides that for them from the application persistence level, but from an OpenShift standpoint, an OpenShift is our new platform. It's based on real but it's our new platform, our new service area to build applications and most notably, infrastructure services on. So just like with (mumbles) where we have, we created the opportunity to have a fertile ecosystem around it, we're doing the same with OpenShift, which means that we've got to enable the companies that are providing those persistence platforms. Those message cues, those NoSQL databases, to run on OpenShift. You want to run Cassandra on OpenShift on premise? What do you need underneath the Cassandra? Block storage, direct attached block storage, which we're building in Kubernetes 1.10. >> Steve, any patterns you're seeing between the customers that are being able to embrace really the kind of this new cloud data world versus those that are having challenges? Any advice you can give based on customer interactions and what you're seeing. >> That's a good question. I think, I just have to fall back on the fact that culture is a hard thing to change. It takes a long time. Institutions are persistent and so I think that for what we sort of say to our customers, our guidance on these topics is that, what we try and give you is choice. Depending on where you are on the journey, slowly move our customers through that journey and try to give them a variety of different choices on that. I think personally like with any new disruption, it usually has like 10 x value. Like the one benefit of containers over to machines is you don't have to bring the operating system along every time you create a new container, right? You can much more densely pack a server with containers with virtual machines. Get more resource utilization, but it takes a long time for an application development team to like fully get there. And so, that's the thing I think, is you just got to be judicious about like the right tool at the right time. >> Yeah, the other thing related to that is the pace of change. >> Steve: Yeah. >> I've talked to some of the people that created Kubernetes, the people who are running all this and they're like, I can't keep up with all these projects. What are you finding internally in Red Hat, as well as from your customers? >> Yeah, I think that it's absolutely true. I was just remarking on that a minute ago it's, you know I'm walking around. I hear this great quote, like why do you come to conferences? Do you come to conferences to learn or do you come to conferences to learn about what you need to learn? (laughter) >> Yeah. >> And it's the latter for me, right. And the ecosystem, the CloudNative ecosystem is exploding. And so I think what we try to do at Red Hat is, especially our team. Our goal in Emerging Technologies is to look 18 months down the road and pick the winners. Like community vitality standpoint, but also like the right technology. And there's this plethora of choices that we need to wave through and what we tend to do is distill that down into our platform that's something our customers can rely on. And that's reliable and we've picked the right project, but it's a big challenge. Like there's so much happening and even in storage it's becoming challenging. >> Steve Watt the Chief Architect of Emerging Engineering at Red Hat thanks for coming on the Cube, appreciate your perspective. It's an architectural game right now. A lot of people putting these new architectures together. It's cultural change. Congratulations on your success with OpenShift and everything else. >> Steve: Yeah, thank you very much. >> Alright, and more coverage here on the Cube after this short break. >> Steve: Thanks. (upbeat music)