>> Computer Museum, in the heart of Silicon Valley, extracting the signal from the noise. It's theCUBE. Covering OpenStack Silicon Valley 2015. Brought to you by Mirantis. Now, your hosts John Furrier and Jeff Frick. (upbeat music) >> Okay welcome back everyone. We are here live, broadcasting. This is SiliconANGLE Media, theCUBE, our flagship program. We go out to the events and extract the signal from the noise. I'm John Furrier, my co-host Jeff Frick this week. Two days of wall-to-wall coverage live in Silicon Valley for OpenStack Silicon Valley or #OpenStackSV or the hashtag for this event today, #OSSV15. Join the conversation. Join our crowd chat, crowdchat.net/OSSV15. Our next guest is Craig McLuckie, who's with Google. He's on the Google Cloud team, CUBE Alum. Welcome back to theCUBE. Got a keynote there, welcome back. >> Thank you so much, great to be with you again. >> So Silicon Valley house leads center of the innovation engine house a lot of investment capital here, a lot of big players, you guys, Facebook, VMware, Intel, you name it. It's the giants of the technology industry. And the bubble conversation's happening. China's going down in terms of economics, and seeing the stock market crash there. But yet, underlying infrastructure change is happening. Cloud certainly is floating, that wealth-creation engine, you guy are a big part of it here in Silicon Valley. Just talk about the state of the Cloud. OpenStack has momentum, you have some stability in the core compute side with OpenStack, virtualization is not going away. New things like Kubernetes, Containers, fast on the scene, rising very fast. What's your take on this innovation engine in the Cloud? >> So I think there's a couple of things that are really exciting and interesting that are happening right now, as we speak. The first is a transition to open. It's a way of rethinking about how you evaluate, acquire, and integrate your software. And I think that OpenStack has established a legitimacy as a technology that's really bringing the value proposition of traditional infrastructure service to everyone everywhere. And we're really starting to see a convergence to that community, a set of technologies that are consistent, of high simatic consistency, is really becoming a thing, which is phenomenal. At the same time we're also seeing another disruption happening. And it was really a disruption that was triggered by the emergence of Docker as a technology to support a new way of thinking about packaging and deployment. And it's really part of a bigger story around a move towards Cloud -Ntive computing. This is a computing set of patterns that was really inspired by the internet giants by the Google's, the Facebook's, the Twitter's. But it's really been cracked open and been accessible by folks like Docker who have opened up those container technologies and now we're seeing a lot of the players start to really focus on this and look at bringing the value proposition of that new style of computing to enterprises everywhere. >> You know you start to see maturity in a market specially when platforms are involved, platform wars, whatever the bloggers want to put the headline out there, when you see abstraction layers develop. And one of the things that you talked about in your keynote I'd like you can elaborate on is ending the distinction between what's under the hood. Containers you mentioned bring out this notion that, "I'm a developer I want interoperability." >> Right. >> "I want cross platform API's." This is the economy so I want you to explain that. What is this disruption with containers and Kubernetes? Do, for this abstraction, do we care about the features any more? And that's one of the signals of maturity. Is that you're not talking speeds and feeds and infrastructure to service, platform as a service. When those conversations go away you know things are moving. >> Right. >> Or is that true, what's your take on all that? >> I think that's a very good observation. I think that one of the things we as a community have looked for for a while is a separation between the world of tools and infrastructure that people interact with on a day to day basis to build applications and in the systems that actually take those built applications and run them for you. And a big part of our focus has been to make the set of subsystems that are actually responsible for the operations of applications, transparent to the end developer. And we're looking to formalize that interface that exists between how you create an application, how you package up it's dependencies and how you offer up the infrastructure and then how you run it. One of the most exciting and energizing things for me is to see the emergence of a standard set of abstraction that interface between these two worlds so it creates massive opportunities for innovation. By standardizing that interface you have incredible innovation in the tooling area with technologies like Docker or continuous integration of delivery frame works. You know new development environments that are producing an artifact that can be universally consumed everywhere else. And then on the infrastructure side you have a lot of innovation around running that artifact for the developer, the end enterprise efficiently and intelligently whether it's being deployed into a virtual machine on OpenStack with being deployed into a main-source cluster running on the metal or whether it's been deployed into a next generation Kubernetes cluster running in one of those environments or somewhere else. We're looking to create this common abstraction and it's going to drive a lot of innovation at every level of the stack. >> You know at Wikibon research one of the things that they're putting out, some cutting edge research around the innovation around some of the technologies under the hood. Conversion infrastructure, cloud technologies, flash, storage, software defined networking all that stuff under the hood is evolving as fast as well. So you have underlying core technology and tooling exploding. >> Right. >> So some really good stuff coming out Wikibon.com. And with that and your comment I want to ask, kind of a pointed question which is: Does hybrid cloud really exist? Is it a concept or is it a category? Do people buy hybrid-cloud? Do they buy into it? It seems to be that's the conversation people are talking about now. But I just don't see hybrid-cloud existing other than being part of private and public. >> Right. >> And talk about that. >> It's a great question. I love that question. It exists but not the way that people think of it existing. Right so you can think about it this way when you are building an application on your laptop and deploying it into a cloud it's kind of hybrid-cloud right? But it's not the way that people think about hybrid-cloud. When you want to run a continuous integration server for your company and have it hosted in the cloud and have it create artifacts that are deployed into you on-prem production clusters. That's hybrid-cloud but it's not the way people have come to think about it. And so what I think about it is really about the ecosystem. About establishing a common set of tools and capabilities so that first and foremost people can choose the destination for an application based solely on the technical merits of the infrastructure that they're ruing on. Google offers some very high quality, robust, fast, affordable cloud infrastructure. But we recognize and embrace the fact that for some customers you have very legitimate regional requirements. For some of the applications you might really want to run them on premises. And so the first step toward achieving legitimacy for hybrid-cloud is establishing a common set of patterns and tools and capabilities that exist in both places. The next step is going to be around creating a common services abstraction that let's you start to access things from other environments. And then over time you might actually see people deploy these sort of cloud bursting scenarios et cetera. But the path to get there is really through infrastructure. You know like a common set of abstractions, a common set of tools, a common set of pattern, and making those available to people everywhere. And then over time we will start building these fused together, legitimately hybrid solutions. >> So hybrid-cloud then is a paradigm, it's a concept that highlights the common tooling interoperability so developers can actually work in these environments without having to do anything. That's where Docker comes in, that's where Kubernetes come in? >> Exactly. And it's really, hybrid needs to be first and foremost about being able to use a common set of technologies to build an application for A or B. >> So let's take it forward. So let's put the brainstorming hat on. Let's talk about the future and let's kind of play with some scenario's. Internet of things opens up a huge can of worms and challenges, engineering challenges around: How do I manage the data? How do I drive workloads to these devices? Whether their wearables or cars or stacks or devices? Anything that's on the edge of the network is now considered a device. PC, mobile, internet of things. So for a developer to work in that kind of environment they need these toolings. Is that how you see it? >> Absolutely, I think that's a great way to think about it. You know it's an interesting thing you raise. Because if you think about it Cloud-Native has really been the domain of internet companies, right? It's really been something that Google's done because it's the only way to practically achieve a certain level of scale. We've seen co-evolution of this, of these patterns inside Twitter, eBay, Facebook, Netflix. Everyone's been doing it on their own terms. Now the reality is when IoT happens every enterprise has to kind of become a internet company right? And what we've seen consistently across, you know all of the internet companies that exist today is there's one pattern that really works well to actually deploy computational infrastructure, at scale efficiently. And that's this pattern around container package, dynamically schedule, microservices oriented computing. And so our mission is really to bring these technologies in a democratized way to enterprises so that they can actually tackle problems that were previously only really solved by the internet giants. Without having to make Google level investments or Facebook level investments in technology. >> Yeah. When we hear that Internet companies, just clarify like a hyperscaler like with Yahoo and Google did. Building large scale systems in a seamless way that's kind of abstract to the user. >> Right. >> Just pure performance all, everything is running and it's kind of a brilliant concept. That brings up the point of Google envy. I mean you hear this all the time in the enterprise. "I want to be more like Google." "I want to be more like Facebook." And what they really are saying is: "I want to have Ops." Right so. >> Right. >> DevOps, Cloud-Native do you hear hat often? And when you hear that: "I want to be more like Google." What does that really mean from your stand point? How do you guys internalize that? >> Right. >> How do you talk back to customers? >> So I think you know when I say I want to be more like Google I think there's a lot of different sort of angles that you might have there. I've heard people coin this phrase GIFEE to describe what we're trying to do: Google Infrastructure for Everyone else. But I think the heart of it is really this: If you're a Google engineer, it's like you have a superpower, right. You have access to this amazing almost unlimited mass of infrastructure that's just at your disposal immediately. At very little cost or overhead. And you don't have to worry about the mechanics of actually where the thing I built is run, right. Operations is just a function of the platform. The developer gets to focus on their application and their application operations and what they get for free is this cluster environment where cluster operations is handled for you. The process of actually mapping an atom of code into a distributors systems environment. The ability to use some very powerful services that make it trivial to build distributable systems. The fact that I'm not paged all the time because what I deploy is understandable by some very smart subsystems, they can watch it, they know what it's supposed to be doing. They can tell when it's not doing that and they know how to fix it, right. And so traditionally when you go out of operating parameters in a traditional system you get paged. And for me a lot of what this operate like Google really means is one is I want to be able to Access Compute at an unprecedented level easily and two is I don't want to get paged by my applications that are doing that. >> Yes so let's bring that up, the API economy. Let's bring this to the next level. Today applications are either Legacy or their Cloud-Native so and I ask everyone the question, even on our own Wikibon team we have a debate. And I ask Dave Alante: "Dave name the Cloud-Native Apps that are out there?" I don't think there are any Cloud-Native apps out there. I mean who has a Cloud-Native App? Now that's a trick question because he goes: "Amazons an App, Google has Cloud-Native." Well they're already hyperscaled. >> Right. >> So the question is what, where are the Cloud-Native apps? Where are the examples? Now Facebook's a Cloud-Native App because they built it from the ground up to be Cloud-Native. >> Sure. >> Google same way. So as an enterprise, what is the Cloud-Native App to the enterprise and how do they get there? And what Legacy do they have to throw away because its synchronous and API interactions is fundamental. >> Right. >> How do you ease that out? >> This is actually a fascinating topic and I think one of the most dangerous things people assume is that to accomplish Cloud-Native you have to go fully along the API-Fication path, right. Now the reality is that of you look at they way that people access data today the fast majority of business data's stored in relational database's. People have great tools to access data in relational databases. They want to be able to move that forward. And to me if you force API-Fication, if you force a protocol specific approach to actual integration, if you force people to use a specific authentication scheme you're going to alienate a very broad array of your customers and you're going to create this cognitive hurdle that's very hard for people to get over. So when I think about Cloud-Native, I think about it as providing a different paradigm for deployment management, activation et cetera. But it has to make allowances for integration with your existing systems. And so I think at the forefront of this is the notion of a service or a microservice. And a microservice has to be a minimal atom of software consumption, the easiest way to find and consume something and you can't force an opinion around how people project that, right. So if you build something that runs in a cluster you should be able to access an Oracle database as if it were a microservice running inside your cluster. You should be able to access a sales force SAS endpoint as if it were a microservice running inside your cluster. And so as I think about my mission and Google's mission around the move towards Cloud-Native computing, you can't create this experiential cliffs, you can't create these artificial boundaries to your system. You have to make natural allowances where, look there's some stuff that just works better in a vertically scalable VM. If you want to run a big database with a Dune Kernel and a few other things, by all means put it in a VM. And we are absolutely committed to the idea of creating a natural set of experiences when you want to go from that to some portion of the application that's doing stateless, front and serving. Or a portion of the application that's running in a cloud-friendly, distributed scaled out database. You shouldn't have to take the pull and be stuck in this world. You should be able to mix these. >> So you're saying it's dangerous to force API-Fication, if that's a term I can't even spell it, It's too may I's at the end there, I like that hyphen in there. But if you force API-Fication or movement, you can foreclose future performance and functionality by alienating existing apps. >> By alienating the existing system. It is a very dangerous, there's a lot of. It's very attractive to drive API-Fication but it has to be, you have to create this pressure grading that attracts people up it by adding value at every stage of the game. And you can't build your management systems around a predicated, sort of, opinionated API framework. We saw this with, in the world of SOA, I mean I don't know if you remember the SOAP and SOA stuff. >> Yeah, yeah. >> You know way back when. >> That was just another way of describing API-Fication and we've saw where it went. The problem was that. >> It wasn't ready, the market wasn't ready for web services at that time. >> And it was, but it was beyond that, it was like, no one's willing to make a massive infrastructure investment to get you to ground zero, where you can actually start building. >> So let's look at that web services back in 2000, 2001 when you saw SOAP, XML, SAM all those things emerging. At that time who did take advantage of that? It was the hyperscalers. It was internet companies cause they needed it, right. So the mainstream market now is adopting that kind of concept around microservices. Explain that. >> But it wasn't, the interesting thing is when you look at what the adoption was around microservices, it wasn't around interoperable SOAP, it was around discrete, highly optimized RPC protocols. It was around relatively closed systems at that time. And it worked well, right? The challenge. >> It was controlled. >> It was controlled and it worked well inside a closed ecosystem. Now what, the thing that really held people back is that to get there you had to do a big ESP deployment. You had to then go and SOA-fy a bunch of your components and it required a huge investment in terms of sort of infrastructure and capabilities to get, before you started realizing value. And it was inaccessible to most people and it alienated technologies that didn't fit well into that model. Right like how do you take your database and put it into that model? It was purely optimized around a certain portion of it. And so now we're in a world where we make it available to everyone. We reduce barriers to entry and you get immediate value without having to make huge investments. So let's take microservices and let's unpack that for the audience out there. You're seeing DockerCon, ContainerCon, KubeCon, MasosCon. All these conferences are around developers. And this is all about scale right? >> Right. >> Operating a scale, abstraction layers. I think it's, we need to be careful not to pigeonhole this as about operating at scale. It is the only practical way to operate at internet scale but the value proposition is just as applicable if you're running something in five virtual machines, at a more humble scale. >> So let's talk about development versus operation team. >> Right. >> Where does the Kubernetes, where does the microservices model fit in? And how do companies avoid the trap of alienating existing apps? How do they get the system up and running? What is the roadmap? And differentiate from a Dev standpoint and an Ops standpoint. >> I think one of the most important things you're going to start seeing is a specialization of the operations function. Today it's all kind of glum together and if you ask a developer to actually run an application they have to be cognizant of which virtual machine it's in. You force them into the ugly world of infrastructure Ops. And sort of common services Ops. And what we're going to start seeing, and what I hope to help companies achieve, is a specialization of the operations function. So Infrastructure Ops should be relegated to a set of people that actually understand the physical infrastructure. They will create an optimal physical environment surround your application. There'll be a small number of specialized people that know how to do that and they will rack and stack and wire and configure and do what ever needs to be done to tune the infrastructure. Above that you're going to see this Cluster Operations. So a common Services Operation team that provide a basic operational platform and common services to everyone. So these are a highly specialized set of people that provide you the tools you need to be able to autonomously run a distribute system. They are unlikely to be involved in the day to day operations because most of these systems will be autonomous but they're there to answer the call if something happens in, in that system. So it becomes a very specialized function. And Google does this with our SRE folks that actually manage our, like the Boar clusters that run all our infrastructure. Small number of highly specialized people providing a very valuable service to a lot of folks. And then at the top level you're going to have Application Operations. And that really just becomes the developers function. And it should really be about understanding and managing your code and you should never have to think about: Where it's running? How it's running? You never, should never have to SSH into an instance to try and debug it. All that should be presented to you through your tools. So the developer's experience becomes one of of using logical infrastructure. And so I think what we're going to start seeing is companies making investments in these clustering technologies. Offering up these simple, clustered service environments for their departments. And then having portfolio's of container package applications that can be easily taken, adjusted and run in these environments. And we'll naturally see the specialization of operations emerge. >> So we're running out of time. Jeff didn't get one question in but maybe next time. >> He has a role in that. >> Brendan Burns, Brendan Burns I think on your team. >> Yeah. >> Brendan, so he brought up something. He brought up the hybrid-cloud is kind of the way, meaning the way you described it, not as a category. But he also brought up the different aspects of Google Cloud in our last crowd chat last month. How do customers mix and mach with the cloud? I mean you guys offer Linux, you guys offer Windows. I mean if I want to work with Google Cloud what are the touch points? How do people ingratiate in? How do they engage with Google? What are some of the use cases? Can you share just put the plug in for Google Cloud what you guys have up and running that's mature, stable, >> Right >> Shipping. And how do customers get into the Google Cloud? >> So we've really seen Google Cloud, it needs to be in all of the above sort of capabilities. The operating characteristics. The thing that make Google Cloud unique is the quality of the basic infrastructure. We offer by far the most price performing basic infrastructure out there. It's an innovative clouds, you know it's driving and active in a lot of the sort of disruptions we're seeing around the container space. It's an open cloud. It's a cloud that's invested in making sure that we engage and connect with the OpenSource community. So if you want to work with Google Cloud there's a lot of different ways to do it. One is you can go and just buy beautiful, clean, pristine, powerful, affordable infrastructure in large chucks through Google compute engine. And we're seeing a tremendous amount of adoption. You don't have to make massive capex down payments to get our best price. We really focus on doing that. You can also come in if you just want to write a bit of code, have it run, we have a wonderful Pass product called Google App engine that's becoming very naturally integrated into the container ecosystem and is a natural sort of path. It's a great entry point for people that just want to operate on a higher level and want to take some code and then have it easily deployed and run on your behalf. And then we're also, another entry pointy that isn't obvious to people is, you can help us build the Google Cloud. What we're building with our next generation set of offerings with technologies like Google Container Engine, is an opensource cloud. It's been built in public. Come join our community, work with us. Try it out. Give us feedback and be part of actually building the next generation of clouds. >> Okay so the question I have for you is, let's just say I'm an Amazon customer and I want to go to Google Cloud, do you have like an elastic Beanstalk application containers an App Engine, how do I get I there? I mean there are some things that Amazon has you might have some things. How do you talk to that, Beanstalk particulars. >> That's a great question. So Beanstalk you know provides the ability to you know deploy and run applications. The closest analogy is App Engine. So Beanstalk traditionally was a Java base platform that you could provide your Java code and it would run it for you. App Engine gives you that equivalent capability. And with the new generation of App Engine we actually provide the ability to deploy into directly into VM. So that it feels a lot, it feels a lot like the Beanstalk experience. But it comes with a lot of other high value services. And so that's a natural starting point. And App Engine it self is being rebased on a lot of the Kubernetes concepts. So that you have this immediate, easy, accessible experience for code but when you reach an edge and you want to actually integrate it naturally with a vertically scaled database that runs in a VM, we have compute engine waiting for you and all very natural, it will feel natural to actually just integrate those two things together and snap together these more holistic solutions. >> You guys have a, final question. I now you guys have a lot of track record with developers certainly Google's history and OpenSource, everything is great. But other competitors, more commercial IBM and Amazon, they're providing marketplaces for distribution, where people can make some cash and some cabbage. >> Right. >> What's the plans Google? Is there anything there? How do I make money if I'm a developer with Google? Or is there plans there, what's the state of that? >> It's a great question and obviously we have aspirations in that space. I can't go into all the details right now. But you know the we are obviously investing in that area. And one of the things that we're really like though is looking at containers as a standard distribution framework, let's you plug into everyone's market places. So one of the things that I see around marketplaces historically is that they offer immediate value in connecting a producer and consumer of software but they're not offering steady state value. So once those two have been connected the marketplace isn't adding significant ongoing value. So when you think about what we want to do, we want to make sure that one is, we become a market maker, we let lost of different market places emerge and that we support those. But then in our own efforts we actually add legitimate value to both the producer and the consumer of the software. And the we're not just taking a cut off the top. So but that's, it will become much more clearer in the face of time. >> Craig, thanks for spending some time and congrats on a great keynote. Good to see you again. Thanks for jumping in and sharing the data here on theCUBE, really appreciate it. We are live here in Silicon Valley. It's theCUBE at OpenStackSV, join the conversation #OSSV15. We'll be right back after this short break. (upbeat music)

from the computer museum in the heart of Silicon Valley extracting the signal from the noise it's the cube cover you openstack Silicon Valley 2015 brought to you by marantis now your host Jeff prick hey welcome back everybody I'm Jeff Rick you're watching the cube we are live at OpenStack Silicon Valley 2015 at the computer history museum in Mountain View California really excited to be out here the second year the event second year the cubes been here we go in two days wall-to-wall coverage is a lot of vibe around OpenStack a lot of vibe around cloud right now we have vmworld happening next week we were to OpenStack Seattle in Linux closed last week so it's all about cloud right now so we're really excited for our next guest kind of a relatively new startup Madeira miskovsky from platform 9 vp of product and co-founder so welcome thanks so for the people that aren't familiar with platform 9 wanna get kind of an overview of what you guys are up to absolutely so fat online is a startup that came out of VMware so we're part of the V mafia that's happening in the cell quality mafia there's quite a few of them and they're very helpful as well so it's a it's a good community good but so what platform i does is we are in a nutshell our mission is to make private clouds at any scale for organizations of any size extremely out of the box and intuitive and simple right in in order to do that we have a very unique approach or model that on OpenStack so we package OpenStack and deliver it as a web service so that's that's in somebody or platform mind us so you're delivering OpenStack as a web service that's interesting a lot of the early OpenStack players we've been talking over the over the day you know have been acquired by emc and HP and an IBM etc so now there's kind of this next-gen of startups really approaching OpenStack in a new way not necessarily kind of the fundamental poor at the bottom but new deployment methodologies new ways to consume it so that's a pretty interesting innovation and how are you finding the market uptake for that you know it's um it's fantastic to be in the space at this time we think the timing is perfect um because if you look at the OpenStack mind shell in the small to medium to large enterprises it's kind of reached at a point now where our buyers right RIT and applies directors or administrators or end users understand the value proposition that OpenStack provides so it's no longer a question about what is OpenStack and why should I care they've gone way past that right more about okay I understand the value proposition and I know open sources the future OpenStack is going to be powering clouds from now onwards and how do i align myself with it what is my OpenStack strategy and that's really where we come into picture and we can highlight what some of our unique differentiators in value adds on right and just coming from VMware just having built vCloud director and having work with enterprise customers um that gives us I think a little bit of an edge because we understand very well what some of the pain points of enterprise customers are in terms of building a private cloud and running it right right and how different is it working with an open source technology at the core and open source framework at the core yeah rather than building something on you know something that was designed inspected built in-house yeah it's a it's a very interesting experience having come from a company that builds proprietary software but one that has been just phenomenally popular it has powered private clouds of the entire world for for almost a decade I'm coming from that wall to the open source world is definitely a shift um there's a shift not only in terms of how the you know how you look at the technology um there is also shift in terms of how as a company you want to market and present yourself it's really all about community right open source is all about community OpenStack is about that so it's about openness and that's a really important part of our culture as well so you see that not only in the product we build but in terms of the blog posts we're I the support articles that we ride and the culture we have within our team as well right and then clearly you know vmware's got a huge engaged community to will be at vmworld next year I don't even know how many tens of thousands of people will be there but it's slightly different really it's kind of an ecosystem built around it versus everybody really contributing to the core and and then like you say so how do you manage being really active in open-source first building the stuff that that makes platform 9 platform 9 I always find that it's kind of an interesting management challenge for somebody managing engineering managing resources well how do you decide what that next unit of work needs to be for that engineer because clearly there's a lot of benefits to contributing back to the open source people get a lot of personal kind of pride and recognition within the community which is very important in open source so how do you kind of balance you know working for OpenStack versus working for platform 9 yeah no that's the way a good question and I think that's that's the key part of what a product person needs to play in terms of the role right because you have to not lose track not lose sight of the fact that you are part of this open-source community right OpenStack is part of our bread and butter right now so an OpenStack is all about openness right so so what's important to us is not necessarily that we create a proprietary modified version of OpenStack right that we offer to our customers we're not in business to do that we're here to make all the goodness of OpenStack in its entirety and purity so we're here to make the coil open-source OpenStack available to enterprises in a production-ready way right so our focus is really on simplified consumption of OpenStack that's been one of the biggest pain points right OpenStack right which is this is this wonderful powerful software which has so many knobs and you know different different options that you can tweak to make it work for your your environment but you really need to know how to do it and many times that manual is missing right which tends to be the challenge right so we're here to provide those really simplified recipes to our end users and in kind of hand hold them and say think of us as an extension of your ops team so let us do the hard work of getting your openstack cloud getting it up and running and then managing it on an ongoing basis or you focus on just consuming it and that's really the balance that we draw a bit and at the same time kind of going back to your point we are we're really passionate about making OpenStack better right improving it and so that community aspect is part of our team we're part of OpenStack OpenStack summits that the Vancouver one the one in Japan we're also taking initiatives and contributing back to the community on the vmware driver forint on the dr front that subclass so lots of that is also happening simultaneously yeah that's it's great so let's shift gears a little bit back to the company so um you've raised some money so you just raised around so congratulations thank you can you tell us who who's leading that round yeah your bench partners definitely so we taste our cities around with point munchers they've just been fantastic mentors and partners to have and to work with they were the previous funders of cloud stock as well um and then use your partner at the satish dharmarajan Scott rainy a great point and they've just both been a fantastic baby think of them as part of our team so good we love them and then four cities B which we just recently made that announcement and we were fortunate to have menlo ventures backing us funding us mark segal is a partner there um who's part of our board now and again that you know they are there also from a little with the V mafia you know we have our friends from put Nick's data and other companies right you know they're backing some of the same people right so really really excited about the new new team it is exciting like I said I think I view from here you know sitting is kind of this next wave of startups that are kind of attacking the next wave of problems um with the OpenStack deployment and you know you mentioned that often the manual is missing also the people are often missing here I think every single person here at the end of their keynote gave a little plug come work for us even though that's the AT&T DirecTV guys so so what's kind of your next challenge what can we look forward to from platform 9 next week at vm at the vmworld and and over the next six months yeah so you know what why we announced our funding we also made announcement that we are officially in GA with our vmware vsphere support and that was really a key announcement for us right we think it's a key enabler I'm not only from the perspective that if you think of the virtualization market in total and the percentage that's that's covered by VMware customers customers were on virtualization using VMware software it's humongous right silver it really gives us the opportunity to tap into that market and we don't really see OpenStack as an either/or when it comes to VMware many times it's presented that way but we don't see that at all partly also because we come from VMware right so we understand the power of that platform in what we believe strongly is that OpenStack only makes that platform a lot more easier to consume and automate right in a more next-generation cloud centric way so that's really what we are here to enable all right so next week you'll see us talking a lot more about how do we natively integrate with VMware and really make that stack you know consumable as an openstack cloud so from a vm with end users perspective he doesn't have to change a thing and that's a huge value proposition that we are making which is take what you have today including the workloads that you have and kind of magically transform them into an openstack cloud so in that instance is so customers already running vmware right they want to deploy OpenStack for a different application set for a particular reason is that kind of the use case that's got that's right and then different use cases also come into picture right cuz it's not really rip and replace I mean if you got a bunch of VMware infrastructure and things are running you know you don't necessarily look in the rip and replace it only not it yeah and that start of you doesn't work well either right right i am getting from vm would use to say beyond words technologies the most disruptive non-disruptive technology stopped in what it does but non-disruptive and how the things customer gets use it and we have the exact same philosophy right but it's but to your point there's different workloads that the penny it's really where it still goes back to this workload specific kind of driver based on the workload what's the application what are they trying to do you know then that should really drive the deployment but from that that's really from an Operations perspective from the from the actual app development perspective I don't really care and don't necessarily want to care right it should just work that's right that's exactly right it's the use cases that really are the most important question right that the end-users ask as well right which is we have this vSphere infrastructure which we really don't want to get get rid of at the same time we as an IT team are tired of having to constantly respond to our developers needs we are tickets and you know the usual delays in classes so we really want something about more agile and that's really what OpenStack enables right through OpenStack heat orchestration through just the simple self service access that's what we are here to enable awesome open door thanks for stopping by the cube I wish you the best and probably see you next week thank you ms county center alright thanks for stopping by i'm jeff Rick you're watching the cube we are live at OpenStack Simon Silicon Valley 2015 will be back with our next segment after this short break you