 Live from Vancouver, Canada, it's theCUBE at OpenStack Summit Vancouver 2015. Brought to you by headline sponsors EMC and Joypling by Red Hat and Cisco with additional sponsorship by Brocade and HP. And now your host, John Furrier. Okay, welcome back everyone. We are live here in Vancouver, British Columbia for the OpenStack Summit. This is theCUBE. This is SiliconANGLE's flagship program. We go out to the events and extract the signal from the noise. I'm John Furrier, the founder of SiliconANGLE. I'm joined with CUBE alumni and previous guest, Monty Taylor, distinguished technologist of HP Cloud Group. Welcome back. You got to be a distinguished technologist. I mean, you don't want to be non-distinguished, right? Yeah, I mean, you're definitely distinguished. Obviously you've been involved. You've been on theCUBE many times. Thanks for coming and spending your lunch hour. My pleasure. I know you're super busy. Appreciate it. We're trying to get the data, share that out to the audience out there. We're on the ground. We're seeing everything. We're seeing, you know, Randy Bias talking to Lee Tucker, huddling over there doing a deal. It's a lot of super-duper action going on. Biz dev, every session, people are literally on the floor. Oh yeah. So it's got that vibe of like... It's absolutely insane. There's so many people running around doing so many things. And I don't know if this is coming across to you as well, but it's so exciting to me how many more of the people who are doing things are the users and the deployers actually doing this. It's not a whole bunch of developers just talking about, you know, what features we're going to write. There's actually, and we got PayPal running all their stuff on top of OpenSec. That's real stuff. It's really happening. And everybody here is talking with each other. They're talking about their actual businesses. Yeah, and we were, you know, Mark Collier wrote a tweet. Oh, Opus Tech Community is mature. I'm like, what? Stu and I were like, roll our eyes. Come on, it's not mature. I ain't ever going to be mature. I'm not mature. I'm 49 years old. I'm still 18, but my wife would say, you know, another kid in the house. But no, but this is evolution, right? So it's maturing. So Stu and I had a long commentary on Mark's comments saying it's complete BS. It's not mature. Long ways to maturity. However, it's maturing. You're seeing demos on stage that are live, more use cases for diverse use cases, more production, not just POCs. No, it's in production. It's a building mode. It's playing the folks out there. Where are we? Because this is an important distinction when you see an event, like I mean, certainly a great venue in Vancouver. But when you have people in session, sitting on the floor, you have real production. It's in full build out mode. And explain that dynamic. No, it's huge. I mean, we've got, I mean, the explosion of people doing it for real. I think I've got eight or 10 different public cloud accounts from providers across the world. So like I just added an account on for my stuff with the United Stack from China. Got the OVH guys are rolling out a thing in Europe. Like it's, that's blowing out. So what you wind up having here is you have, you know, you have Martin McLean's 101 on Neutron talk where he's just going through basic things. And it's literally spelling out the door because the big guys are getting their stuff up and running. Now everybody says, okay, it's worthwhile for me to dive in and figure out how to do. And they want to know, they want to know what it means. They want to know what the stuff is. We get people in here. This is their first summit. This is their first exposure to how all this works. And they can't get enough. They can't get enough information, right? There's so much to get. They're so motivated. They're so hungry for learning things. And it's really exciting to get that vibe. And this crosses over the POC kind of will open stack scale because now it's scaling, if you will. You start to see things like certification. That's a proof positive that there's demand to start vetting out and putting some, you know, certification. Exactly. So people update their LinkedIn profile, open stack certify. I mean, but that's a market. It's certifiable. I don't know. Certifiable. It really is. And the other thing too, as we're seeing lots of different people, it was one thing when it was just HP and Rackspace doing this, right? But now that we've got, you know, eight, 10, 12, 20 clouds, the patterns start to emerge. Okay, what is it? What does the people really are doing? Because we can sit around talking at a bar about what it should be. But now we're actually seeing what it is. You know, what are the patterns that are emerging? And that's sort of helping the deaf core folks to really be able to drive that definition of, okay, here's what you can expect. If you're building your business on top of this, you're building your app on top of this, you can expect these things. We're seeing them actually emerge in the market and emerge in the ecosystem. One thing I'd like you to comment on, Martha, you've been involved in the growth and the momentum involved in the technical committee and all the board stuff and Eileen as well. You guys have been great, great, great supporters. HP, huge contingent contributing in boatload of code. So, you know, golf clap for that. But I want you to talk about the dynamic between this community. There's still the founding core DNA of people who are involved in OpenStack, who shepherded it to that early adopter mode now across the chasm. And then also now the new dynamic, HP being there from the beginning, but still a big company. HP, you got IBM, you have Red Hat, Cisco, Intel's making some security announcements this morning. You got Oracle. So, I mean, you have big whales coming in and the tide is lifting all the boats. So, talk about that dynamic. And compare and contrast that founding DNA yourself and others that are still here. The founders are still around. You have new blood. What does that do to the community? I think it's actually, it's really important. It's a really good question. I think one of the things that we focused on from the very beginning, in addition to building great software, which obviously we want to do, was to build that community and to make a place where IBM and HP and Cisco can all come together and work on this thing collaboratively. So, that's actually been one of the goals, you know, since day one. And I think we did a really good job of nailing that. So, you get to the point where we've got, you know, we've got Fish at Oracle now, right? Like, he's been there. He was in the original ANSO Labs startup that, you know, that did work for NASA. You know, I'm at HP. We've got, you know, we've got all of us, because we created that ability for collaboration, we're not having to get rid of the sort of initial startup folks to be able to ride the wave of success that we've got with the big company. And at the same time, it doesn't mean that it's just the initial, it's not that important to things that I'm here personally. I've done my stuff and I can still be involved, but the community also can bring in new blood and all of these companies, especially all these companies that are multinational, that are worldwide, that's a whole different viewpoint on what you might want to do and what might be important to you. You got all these big clouds spinning up in China and India. They've got a different worldview than I do. And that's, and if we can bring them in and their energy and excitement as well. And also the balance of power too, when you have that passion of the early founders, if you will, like say founders, but the early community guys, it's a balance of power because now if the big boys come in, big boys come in and they start throwing their weight around, the community has this nice balance to it because there's rules of engagement if you will, right? They really are. There's some of us like, you know, like Vish and Jay and I that can sit here and be like, yeah, that's maybe not okay, but day in and day out, it's, you know, we've done a great job of making a place where these people can collaborate and they know how to. Like we've actually set out the rules. So we actually, most of the time, don't need to call anybody to task because it's really clear the benefits and value to them from coming in and actually participating. Talk about some of the changes that have happened. Obviously it's big tent, the main tent, what they call it. And you had kind of the loose integrated approach which is kind of like, took on its own life of its own, but really was kind of a de facto way to do updates. And the power that the big guys now bring as well because also they're contributing HP, for example, you guys get props, I don't think you get enough props, but you guys donate a boatload of code. So this notion of voting with your code or contributing with code has value, but also you have now real niche and or scoped performance. Cisco brings X to the table, Brocade brings something to the table, HP brings something to the table, and IBM brings something to the table, Oracle brings something. Now each with their own agenda, how do they differentiate? How does OpenStack enable this new model with the big tent, the main tent, whatever it's called for folks to cooperate and compete at the same time, AKA, co-opetition? Yeah, so that's an excellent question. One of the things that we, I think that we accomplished with the big tent or that we set out to accomplish with that is to separate the question of who is OpenStack? Who are the people doing this? Who are we from the idea of the code itself? Because people come in with a great idea and they say, hey, I'm IBM, I want to do this thing or I'm HP, I want to do this thing over here. And we were having to bless that idea just to bring them into the party, right? And that's, we don't want to be in the business of a blessing. We want to let the, we sort of want to let the market sort that out. Like that's really important for that competition to be able to take place in the outlining areas, even where on some things like Nova, not really particularly interested in lots of new competing projects to do the same thing as Nova because that's really important to our users. We need both of those things. We need a vibrant competition because that's how you get better products. But ultimately once our users start depending on something like Nova, then we need to make sure that that's going to be solid and a thing that our users can count on. So I think a lot of this is about focusing on our end users and focusing on people doing applications on top of it and making sure we're serving them. Yeah, and that's also the focus of getting quality releases out of OpenStack. That's exactly right. So you get the quality going. So I got to ask you, what's the quality aside? You get some nice machinery. You get the certifications. Some say we were a little bit late to the game, but Jonathan was even admitting that, hey, we should have done that earlier, but it's moving fast now, great. Now let's talk about the marketplace, right? Technology's shifting. You have the three layers, infrastructure as a service, platform as a service and software as a service. I mean, people always use that as a way to kind of put people in boxes. Oh yeah, that's a pass. That's Cloud Foundry. That's all blurring. When you have a service oriented architecture like the cloud, you have a service architecture. Can you comment on what your views are on the service oriented approach? Because if you look at it as a service architecture, then you don't really care about layers. Or do you? You want resources. No, you don't care about layers. It's really great for people writing blog posts. It's really great for people making taxonomies and selling consulting services, I think. They like to use acronyms and point at that. Ultimately people getting stuff done, they're wanting to get resources. A person wants a place to run their workload. If you're doing image transcoding for a big media pipeline like the digital film tree folks were showing us yesterday, you're not thinking about is this a pass or is this an IaaS? You don't care. You want to transcode your images. I couldn't be more thrilled with looking at the demo they showed earlier today of Magnum running on top of Ironic. So bare metal and containers. Everybody's like clouds about VMs. We just added both bare metal and containers and here the two of them are playing directly with each other because it's a way for you to get your job done. They're all elements. But they really are. This is how customers are talking. I mean this is the language of the builder, right? So let's take that to another level. Explain to the folks out there that they're trying to grok the whole cloud thing around those three layers and how does that translate? What is a service architecture? As someone who's a builder, it's just a toolbox. What is it? How do you describe that? It's tools behind APIs. So much of it is about the self-service aspect. The traditional IT, you call somebody on the phone. You say, hey, I think I want some computers and they go, okay, well I'll take it for you and two weeks later you do it. So you just had a huge investment in time and resources to try something. In this case, you put these tools in the hands of the makers and inside of the companies whether they're sysadmins, whether they're developers. I think we use the word developer a lot. But actually cloud is just as much of a tool for an ops sysadmin person as it is for developers. It's engineering, right? I mean you call whoever. That's exactly right. You're software engineer, you're ops engineer, I mean you're engineering the solution. And you enable the engineers to do things without much red tape. That allows them to have a new idea and execute on it. And then as you see that come to fruition, they say, oh, this is a really great idea. This has driven our business to a wonderful place. Then you've got the tools to even scale those things out in a supported way in production without having to completely re-engineer everything after the fact. So it really allows for agility and speed of reaction. Let's talk about some of the conversations in the quote, engineer, or developer. Software and community, where software is driving everything. We're showing it at our crowd pages, AngularJS component. We have a node front end with CrowdChat and got Java on the back end. Let's talk about code bases. Java's got a good function for heavy lifting stuff, Angular with real time, and then node for IO. So I got to ask you, in this API based economy, what is some of the tooling, what are some of the things that are going on at the front end to make the cloud really render well in terms of whether it's visualization or whether it's using services. What's the tooling of choice? I mean obviously Angular just throw that in there because we just showed you the demo. We've got the right after, right after the lunch break here, there's a guy, in fact I was talking about yesterday, Michael Kroetschek's leading and design summit session on what our AngularJS story is inside of OpenStack. OpenStack's UI, Project Horizon, has been incorporating more and more of it, but they've been incorporating it in the context of the Python based web framework they've been using. And so now the question is okay, how about we look at what the real story for this wants to be, right? And how do we engage with that? You look at other things that other ways people are interfacing with things. Google has the go language also showing up here. Mozilla just released Rust as a 1.0. So the world of that is moving just at a breakneck pace, but the key about all of these new things is they all have built in understanding of REST APIs. Like you go to go, you write a thing, it knows how to interact with the REST API. You look at AngularJS, it knows it's not just you can do anything because it's a programming language, it has primitive built in to be able to do that, which positions things like OpenStack really well because the trading currency inside of OpenStack is REST APIs. So you can make, you can do that from JavaScript, you can do that from anything you want to. And that's enabled, built in native into the platform. That's exactly right. So this is the modern tooling, basically. This is the modern tooling. This is the way it all works. And with that as a commonality, everything can talk to these APIs. And we don't have to get into this language lock-in war. If your business wants to be Java-based, if your business wants to be .NET-based, doesn't matter. You can use these APIs and you know how to do it. And that's the beautiful thing. I mean, we were just talking about Azure potentially coming in and putting something on OpenStack. So OpenStack is really out there now where you can bring anything in. You can run a .NET with components. This is the service architecture. That's exactly right. And we want to be that place that allows you to have a sort of common interface for getting all those things done so that you can worry about your applications. You can worry about your business. You can worry about the thing that you're doing rather than spending all of your time worrying about different, you know, what's the language on the back end and how is that going to affect my ecosystem? Well, people are going to be bolting in a lot of different things whether it's third party kind of tooling and you got analytics in real time and you go to self-driving cars. Things are going not from near real time, but real time. All kinds of analytics solutions are all going to be done at wire speed or whatever you want to call it. So real time is huge. Yeah, you look again at the digital film tree demo from yesterday and the transformation that was making into that media pipeline. They're filming in real time, sending dailies into the cloud, processing them in another city and sending them back to be included in afternoon. That's just the mind shift that is for all of them and what that allows them to do. And that's sort of an obvious one because they used to courier around tapes. But, you know, the same thing is true in all of the rest, you know, banking and retail. So I got to ask you, I mean, this is the build out dream right now. It's a nirvana for builders and engineers right now. That's why the sessions are packed. Reminds me again, the old, early VMware days. I've seen the Microsoft community in the 90s was the same way. Really rabid and the eyes are popping out of their head. They've seen a lot of creative opportunities and also hardcore build outs for, you know, a lot of the transformation people are talking about. So I got to ask you, you know, you're in the industry as an individual, also you work for HP. What are the conversations that you guys are having at HP? And you guys are doing a lot of work on OpenStack, contributing a lot of code. What are some of the conversations you're having with customers? Where is the utopia of building out right now? It's like, it's a maker fair, if you will, of cloud, whatever you want to call it. And just goofing on maker fair was just this past weekend. I mean, it's an engineering dream. A lot of stuff's happening. What's going on? What's your take on this? And what conversations can you share that kind of highlight this revolution of building out? So in general, when I go sit with customers and I interact with them, the themes that come out of that, I have a lot to do with that. The thing we mentioned earlier, that sort of self-sufficiently, they all know that the world of business, the world of commerce these days is moving at a breakneck pace and they've got to keep up with it. And the slower their systems are to be able to react to their developers and their developers putting out new applications is they're dead in the market if they do that. And they all know that. And so they want to get onto the cloud bandwagon as quickly as possible, but that doesn't mean that they initially know what that means for their business. So not only is it, to your point, sort of a maker fair for the engineers, but this is actually a business transformation moment. This is people looking at what does it mean to move faster? How do we think about that? Think about funding cycles. Think about how that works in finance and how you think about strategic planning when you can turn around something in a week rather than six months. That's a whole different business mindset. And so in as much as we've got the engineers going in and building out these clouds, at the same time we're talking to the business side of the coin about how they need to start thinking about their businesses differently and how they can take advantage of. Because ultimately if they just install a cloud and don't think about it in business terms, they've given their engineers a great fun playground, but what's the point? So I got to ask you also, as you know theCUBE we're really big on women in tech. We've been covering a lot of it for years before. It's fashionable now, I guess fashionable. People use it as more of a political thing, but it's a lot of great women in tech. And now with the scope and diversity of the solution and use cases, it's just not IT guys building stuff. It's really not. You have women who are coding up to analysts with big data kind of converging together. So there's a huge squath of opportunity for women in tech. What are you guys doing there, HP? What's some of the things that OpenStack that you see happening that are compelling that you can share? So we've actually been making a really big push on this in OpenStack. We're big supporters of the OPW program, which used to be called something else and I can't remember what it is because it's just OPW to me. But so we've got OPW interns because part of the solution is getting a good pipeline in. We're also doing a lot of work on things like codes of conduct and things of that nature to make sure that we're creating a collegial environment and not one that feels adversarial. We don't want the excellent women engineers to come in and feel like they're just in an old boys' club where everybody's in a locker room or something like that. And that's a thing that the community has to come together and understand and value. And I've been really excited to see this. There was a women in OpenStack. There's been several women in OpenStack events this week already. We do them, it's not just here at the summit. It's not just sort of a, you know, we get together a party. There was a great session this morning, in fact, where everybody broke off into things to see about how can we do that and there's some really concrete suggestions on how we can structure the community. HP are also in my team and the other teams around where we're focused on making sure that we're providing opportunities at all levels. You guys are doing some scholarship stuff, right? Yeah, we've got scholarship programs for that. How does that work? There's only so many things at HP that I honestly have no idea. But you're giving out cash or code? We're giving out, we're funding people to work on things and also trying to have that provide then a pipeline into hiring opportunities. Because honestly, you do like just a short term thing and then there's no follow up. That's not particularly. All right, so the final question I got to ask you, share with the folks the things they should know about HP Cloud that they may not know about. I mean, besides the fact that you guys are probably one of the biggest contributors to OpenStack, what are the things that you guys doing that people may or may not know about that you'd like to share? We're doing just about everything. We've got the public cloud, which is going strong. You know, I'm a huge user of that. We've got managed private things that we're doing for people, bunch of private cloud deployments. A large reason that I mentioned all three of those is that ultimately each of our customers and especially the sizes, as you might imagine HP's customers are, they're a single solution for a problem that doesn't work for any of those customers. You need a little bit of everything. I mean, the digital film tree, I'm just, they were so awesome, but I point at them, but they're a really good example of that. They've got a private cloud, they're doing bursting to public, and that's a really great example for what a lot of the enterprise customers really need. They've got different workloads. So we're focusing a lot on making sure that we're solving each of those things. There's a resource tool. There's a resource tool. They want resources and they want to get to them by API. Services and resources that are programmable. That's exactly right. And that's in having the tooling on the front end. It's all kind of coming together. So we're doing all of those things and we're out there, you know, out there kicking it every day. All right, so I got to ask a personal question. What are you most excited about right now in the industry right now? What gets you excited? You're a distinguished technologist. So as a distinguished technologist, I love the joke on the title. I know you're goofing on yourself on that, but no, seriously, you've been in a trend, you're involved in a lot of stuff. What's getting you pumped up about? I mean, there's the obvious things. I mean, obviously I'm excited about Open Sack, but that probably goes without saying, is that particularly interesting thing to come out of my mouth. I do think a lot of the stuff that's going on in the container space is especially exciting. I think that the combination of those things. So I think that the landscape of containers and VMs and bare metal and having all of those available across an infrastructure, I think that's really great. I think a lot of people want us to make that into a bloodbath, but I think that actually watching the people work on projects to stitch those together, that's actually entertaining. Is Docker going to take over the world? No, Docker's not going to take over the world. It doesn't work for everybody's workload, but is Docker really... It's enabling a lot of standardization. It's enabling a lot of standardization in a lot of places. So you integrate that. But it's not the end of the game. I mean, I talked to Ben Gallup, he's like, we are far from over. No, there's no end of the game. He's still working hard. The fact that the game keeps expanding every single day, and the fact that we're seeing innovation in places that I'm pretty sure we weren't expecting to see innovation, I mentioned Rust from Mozilla earlier. I'm a huge fan of that. It's a statically compiled language for doing things very similar to C. Who thought we'd be seeing innovation in that space? Yeah, I mean, it's this code for everything, but it's fantastic. You brought a bloodbath and this is interesting. I comment on this all the time on theCUBE with Dave Vellante, like the press loves, oh, bloodbath, something is dead, something's dying. It's like if it bleeds, it leads unless they say in the media business, but there's really not a bloodbath mentality in this market because there's so much growth. Bloodbaths happen when there's constricting markets. That's exactly right. So what's happening here is there's so much fruit on the tree, there's so much beach head. That's the container argument. That's the container argument, and there's people who want to say, oh, are containers killing VMs? No, containers aren't killing VMs. That's ridiculous. They do different things. What's exciting is that we're actually, the containers have now reached the maturity point where people are starting to make those sort of erroneous kinds of thoughts. Now we've actually got choices for the consumers, and they can do all sorts of exciting things, and that's how much that's changing every day is. So growth is there, there's large future growth coming, so it's evolving and then maturing. Definitely crossed over. Monty, thanks for coming on. I appreciate it. My pleasure, anytime. Monty Taylor, the Distinguished Engineer at HP Cloud. Great person to always have on theCUBE. He's been involved in the Foundation, Board, Technical Committee, again, grassroots in the core, kernel in the community is growing, growing, adding new blood. Thanks for joining on theCUBE. We'll be right back after this short break.