>>live from Atlanta, Georgia. It's the Q covering answerable best 2019. Brought to you by Red hat. >>Welcome back, everyone to the Cube. Live coverage in Atlanta, Georgia for answerable fest. This is Red Hats Event where all the practices come together. The community to talk about automation anywhere. John Kerry with my coast to Minutemen, our next two guests arrive. And Bergeron, principal community architect for answerable now Red Hat and Greg Dankers Berg, senior director, Community Ansel's. Well, thanks for coming on. Appreciate it. >>Thank you. >>Okay, So we were talking before camera that you guys had. This is a two day event. We're covering the Cube. You guys have an awful fast, but you got your community day yesterday. The day before the people came in early. The core community heard great things about it. Love to get an update. Could you share just what happened yesterday? And then we'll get in some of the community. Sure. >>We s o uh, for all of our answer professed for a while now we've started them with ah, community contributor conference. And the goal of that conference is to get together. Ah, lot of the people we work with online right people we see is IRC nicks or get hub handles rights to get them together in the same room. Ah, have them interact with, uh, with core members of our team. Uh, and that's where we really do, uh, make a lot of decisions about how we're gonna be going forward, get really direct feedback from some of our key contributors about the decisions were making The things were thinking about, uh, with the goal of, you know, involving our community deeply in a lot of decisions we make, that's >>a working session, meets social, get together. That's >>right, Several working sessions and then, you know, drinks afterward for those who want the drinks and just hang out time that >>way. Drinks and their last night was really good. I got the end of it. I missed the session, but >>they have the peaches, peaches, it on the >>table. That was good. But this is the dynamic community. This is one things we notice here. Not a seat open in the house on the keynote Skinny Ramon Lee, active participant base from this organic as well Be now going mainstream. How >>you >>guys handling it, how you guys ride in this way? Because certainly you certainly do. The communities which is great for feedback get from the community. But as you have the commercial eyes open sores and answerable, it's a tough task. >>Well, I'd like to think part of it is, I guess maybe it's not our first rodeo. Is that what we'd say? I mean, yeah, uh, for Ansel. I worked at ELASTICSEARCH, uh, doing community stuff. Before that, I worked at Red Hat. It was a fedora. Project leader, number five. And you were Fedora project Leader. What number was that? Number one depends >>on how you count, but >>you're the You're the one that got us to be able to call it having a federal project leader. So I sort of was number one. So we've been dealing with this stuff for a really long time. It's different in Anselm that, you know, unlike a lot of, you know, holds old school things like fedora. You know, a lot of this stuff is newer and part of the reason it's really important for us to get You know, some of these folks here to talk to us in person is that you know especially. And you saw my keynote this morning where they talked about we talked about modularity. Lot of these folks are really just focused on. They're one little bit and they don't always have is much time. People are working in lots of open source projects now, right, and it's hard to pay deep attention to every single little thing all the time. So this gives them a day of in case you missed it. Here's the deep, dark dive into everything that you know we're planning or thinking about, and they really are. You know, people who are managing those smaller parts all around answerable, really are some of our best feedback loops, right? Because they're people who probably wrote that model because they're using it every single day and their hard core Ansel users. But they also understand how to participate in community so we can get those people actually talking with the rest of us who a lot of us used to be so sad. Men's. I used to be a sis admin, lots of us. You know. A lot of our employees actually just got into wanting to work on Ansel because they loved using it so much of their jobs. And when you're not, actually, since admitting every day, you you lose a little bit of >>the front lines with the truth of what's around. Truth is right there >>and putting all these people together in room make sure that they all also, you know, when you have to look at someone in the eye and tell them news that they might not like you have a different level of empathy and you approach it a little bit differently than you may on the Internet. So, >>Robin So I lived in your keynote this morning. You talked about answerable. First commit was only back in 2012. So that simplicity of that modularity and the learnings from where open source had been in the past Yes, they're a little bit, you know, what could answerable do, being a relatively young project that it might not have been able to dio if it had a couple of decades of history? >>Maybe Greg should tell the story about the funk project >>way. There was a There was a project, a tread hat that we started in 2007 in a coffee shop in Chapel Hill, North Carolina is Ah, myself and Michael the Han and Seth the doll on entry likens Who still works with this with us? A danceable Ah, and we we put together Ah, an idea with all the same underpinnings, right? Ah, highly modular automation tool We debated at the time whether it should be based on SSL or SS H for funk. We chose SSL Ah, and you know, after watching that grow to a certain point and then stagnates and it being inside of red Hat where, you know, there were a lot of other business pressures, things like that. We learned a lot from that experience and we were able to take that experience. And then in 2012 there there's the open source community was a little different. Open source was more acceptable. Get Hubbell was becoming a common plat platform for open source project hosting. And so a lot of things came together in a short pier Time All that experience, although, >>and also market conditions, agenda market conditions in 2007 Cloud was sort of a weird thing that not really everyone was doing 2012 rolls around. Everyone has these cloud images and they need to figure out how to get something in it. Um, and it turns out that Hansel's a really great way to actually do that. And, you know, even if we had picked SS H back in the beginning, I don't know, you know, not have had time projects grow to a certain point. And I could point a lots of projects that were just It's a shame they were so ahead of their time. And because of that, you know, >>timing is everything with the key. I think now what I've always admired about the simplicity is automation requires that the abstract, the way, the complexities and so I think you bring a cloud that brings up more complexity, more use cases for some of the underlying paintings of the plumbing. And this is always gonna This is a moving train that's never going to stop. What was the feedback from the community this year around? As you guys get into some of these analytical capabilities, so the new features have a platform flair to it. It's a platform you guys announced answerable automation platform that implies that enables some value. >>You know, I >>think in >>a way. We've always been a platform, right, because platform is a set of small rules and then modules that attached to it. It's about how that grows, right? And, uh, traditionally, we've had a batteries included model where every module and plug in was built to go into answerable Boy, that got really big bright and >>we like to hear it. I don't even know how many I keep say, I'll >>say 2000. Then it'll be 3000 say 3000 >>something else, a lot of content. And it's, you know, in the beginning, it was I can't imagine this ever being more than 202 150 batteries included, and at some point, you know, it's like, Whoa, yeah, taking care of this and making sure it all works together all the time gets >>You guys have done a great You guys have done a great job with community, and one of the things that you met with Cloud is as more use cases come, scale becomes a big question, and there's real business benefits now, so open source has become part of the business. People talk about business, models will open source. You guys know that you've been part of that 28 years of history with Lennox. But now you're seeing Dev Ops, which is you'll go back to 78 2009 10 time frame The only the purest we're talking Dev ops. At that time, Infrastructures Co was being kicked around. We certainly been covering the cubes is 2010 on that? But now, in mainstream enterprise, it seems like the commercialization and operational izing of Dev ops is here. You guys have a proof point in your own community. People talk about culture, about relationships. We have one guest on time, but they're now friends with the other guy group dowels. So you stay. The collaboration is now becoming a big part of it because of the playbook because of the of these these instances. So talk about that dynamic of operational izing the Dev Ops movement for Enterprise. >>All right, so I remember Ah, an example at one of the first answer professed I ever went thio There were there were a few before I came on board. Ah, but it was I >>think it was >>the 1st 1 I came to when I was about to make the jump from my previous company, and I was just There is a visitor and a friend of the team, and there was an adman who talked to me and said, For the first time, I have this thing, this playbook, that I can write and that I can hand to my manager and say this is what we're going to D'oh! Right? And so there was this artifact that allowed for a bridging between different parts of the organization. That was the simplicity of that playbook that was human readable, that he could show to his boss or to someone else in the organ that they could agree on. And suddenly there was this sort of a document that was a mechanism for collaboration that everyone could understand buy into that hadn't really existed before. Answerable existed after me. That was one of the many, you know, flip of the light moments where I was like, Oh, wow, maybe we have something >>really big. There were plenty of other infrastructures, code things that you could hand to someone. But, you know, for a lot of people, it's like I don't speak that language right? That's why we like to say like Ansel sort of this universal automation language, right? Like everybody can read it. You don't have to be a rocket scientist. Uh, it's, you know, great for your exact example, right? I'm showing this to my manager and saying This is the order of operations and you don't have to be a genius to read it because it's really, really readable >>connecting system which connects people >>right. It's fascinating to May is there was this whole wave of enterprise collaboration tools that the enterprise would try to push down and force people to collaborate. But here is a technology tool that from the ground up, is getting people to do that collaboration. And they want to do it. And it's helping bury some >>of those walls. And it's interesting you mention that I'm sure that something like slack is a thing that falls into that category. And they've built around making sure that the 20 billion people inside a company all sign up until somebody in the I T departments like, What do you mean? These random people are just everyone's using it. No one saving it isn't secure, and they all freak out, and, um, well, I mean, this is sort of, you know, everybody tells her friend about Ansel and they go, Oh, right, Tool. That's gonna save the world Number 22 0 wait, actually, yeah. No, this is This actually is pretty cool. Yeah, yeah, yeah, I get started. >>Well, you know, sometimes the better mouse trap will always drive people to that solution. You guys have proven that organic. What's interesting to me is not only does it keep win on capabilities, it actually grew organically. And this connective tissue between different groups, >>right? Got it >>breaks down that hole silo mentality. And that's really where I tease been stuck? Yes. And as software becomes more prominent and data becomes more prominent, it's gonna just shift more power in the hands of developer and to the, uh, just add mons who are now being redeployed into being systems, architects or whatever they are. This transitional human rolls with automation, >>transformation architect >>Oh my God, that's a real title. I don't >>have it, but >>double my pay. I'll take it. >>So collections is one of the key things talked about when we talk about the Antelope Automation platform. Been hearing a lot discussion about how the partner ecosystems really stepping up even more than before. You know, 4600 plus contributors out there in community, But the partners stepping up Where do you see this going? Where? Well, collections really catalyze the next growth for your >>It's got to be the future for us that, you know, there there were a >>few >>key problems that we recognize that the collections was ultimately the the dissolution that we chose. Uh, you know, one key problem is that with the batteries included model that put a lot of pressure on vendors to conform to whatever our processes were, they had to get their batteries in tow. Are thing to be a part of the ecosystem. And there was a huge demand to be a part of our ecosystem. The partners would just sort of, you know, swallow hard and do what they needed to d'oh. But it really wasn't optimized Tol partners, right? So they might have different development processes. They might have different release cycles. They might have different testing on the back end. That would be, you know, more difficult to hook together collections, breaks a lot of that out and gives our partners a lot of freedom to innovate in their own time. Uh, >>release on their own cycle, the down cycle. We just released our new version of software, but you can't actually get the new Ansel modules that are updated for it until answerable releases is not always the thing that you know makes their product immediately useful. You know, you're a vendor, you really something new. You want people to start using it right away, not wait until, you know answerable comes around so >>and that new artifact also creates more network effects with the, you know, galaxy and automation hub. And you know, the new deployment options that we're gonna have available for that stuff. So it's, I think it's just leveling up, right? It's taking the same approach that's gotten us this foreign, just taking out to, uh, to another level. >>I certainly wouldn't consider it to be like that. Partners air separate part of our They're still definitely part of the community. It's just they have slightly different problems. And, you know, there were folks from all sorts of different companies who are partners in the contributor summit. Yesterday >>there were >>actually, you know, participating and you know, folks swapping stories and listening to each other and again being part of that feedback. >>Maybe just a little bit broader. You know, the other communities out there, I think of the Cloud Native Computing Foundation, the Open Infrastructure Foundation. You're wearing your soul pin. I talk a little bit of our handsome How rentable plays across these other communities, which are, you know, very much mixture of the vendors and the end users. >>Well, I mean and will certainly had Sorry. Are you asking about how Ansel is relating to those other communities? Okay, Yeah, because I'm all about that. I mean, we certainly had a long standing sort of, ah fan base over in the open stacks slash open infrastructure foundation land. Most of the deployment tools for all of you know, all the different ways. So many ways to deploy open stack. A lot of them wound up settling on Ansel towards the end of time. You know, that community sort of matured, and, you know, there's a lot of periods of experimentation and, you know, that's one of the things is something's live. Something's didn't but the core parts of what you actually need to make a cloud or, you know, basically still there. Um And then we also have a ton of modules, actually unanswerable, that, you know, help people to operationalize all their open stack cloud stuff. Just like we have modules for AWS and Google Cloud and Azure and whoever else I'm leaving out this week as far as the C N. C f stuff goes, I mean again, we've seen a lot of you know how to get this thing up and running. Turns out Cooper Daddy's is not particularly easy to get up and running. It's even more complicated than a cloud sometimes, because it also assumes you've got a cloud of some sort already. And I like working on our thing. It's I can actually use it. It's pretty cool. Um, cube spray on. Then A lot of the other projects also have, you know, things that are related to Ansel. Now there's the answer. Will operator stuff? I don't know if you want to touch on that, but >>yeah, uh, we're working on. We know one of the big questions is ah, how do answerable, uh, and open shift slash kubernetes work together frequently and in sort of kubernetes land Open shift land. You want to keep his much as you can on the cluster. Lots of operations on the cluster. >>Sometimes you got >>to talk to things outside of the cluster, right? You got to set up some networking stuff, or you gotta go talk to an S three bucket. There's always something some storage thing. As much as you try to get things in a container land, there's all there's always legacy stuff. There's always new stuff, maybe edge stuff that might not all be part of your cluster. And so one of the things we're working on is making it easier to use answerable as part of your operator structure, to go and manage some of those things, using the operator framework that's already built into kubernetes and >>again, more complexity out there. >>Well, and and the thing is, we're great glue. Answerable is such great glue, and it's accessible to so many people and as the moon. As we move away from monolithic code bases to micro service's and vastly spread out code basis, it's not like the complexity goes away. The complexity simply moves to the relationship between the components and answerable. It's excellent glue for helping to manage those relationships between. >>Who doesn't like a glue layer >>everyone, if it's good and easy to understand, even better, >>the glue layers key guys, Thanks for coming on. Sharing your insights. Thank you so much for a quick minute to give a quick plug for the community. What's up? Stats updates. Quick projects Give a quick plug for what's going on the community real quick. >>You go first. >>We're big. We're 67 >>snow. It was number six. Number seven was kubernetes >>right. Number six out of 96 million projects on Get Hub. So lots of contributors. Lots of energy. >>Anytime. I tried to cite a stat, I find that I have to actually go and look it up. And I was about to sight again. >>So active, high, high numbers of people activity. What's that mean? You're running the plumbing, so obviously it's it's cloud on premise. Other updates. Projects of the contributor day. What's next, what's on the schedule. >>We're looking to put together our next contributor summit. We're hoping in Europe sometime in the spring, so we've got to get that on the plate. I don't know if we've announced the next answer will fast yet >>I know that happens tomorrow. So don't Don't really don't >>ruin that for everybody. >>Gradual ages on the great community. You guys done great. Work out in the open sores opened business. Open everything these days. Can't bet against open. >>But again, >>I wouldn't bet against open. >>We're here. Cube were open. Was sharing all the data here in Atlanta with the interviews. I'm John for his stupid men. Stayed with us for more after this short break.

>> Announcer: Live from Vancouver, Canada. It's theCUBE covering OpenStack Summit North America 2018, brought to you by Red Hat, the OpenStack Foundation and its ecosystem partners. >> Welcome back, I'm Stu Miniman and my cohost John Troyer and you're watching theCUBE, the worldwide leader in tech coverage and this is exclusive coverage from OpenStack Summit 2018 in Vancouver. Usually this time of year it is a little bit overcast, but for the second time the OpenStack Summit has been here, the sun is shining. It has been gorgeous weather but we are in here really digging in and understanding it One of the people I have gotten to know through this community especially, is our wrap up guest today, Sean Michael Kerner, who is a senior editor with eWeek, amongst other bi-lines that you have. Pleasure to see you. >> Great, good seeing you too Stu. >> Alright, so we let you keep on the Toronto Bluejays hat >> Thank you, there we go. >> We have had quite a few Canadians on our program here. >> Well, seeing as how you're here in Canada, it's not all that surprising. >> It's lovely. They have you working on Victoria Day. >> Yeah, that's unfortunate but I will take Memorial Day off in a week, so it works out. >> Excellent. So Sean, for our audience that might not know you, give us a little bit about your background. You've been to umpteen of these shows. >> Sure. I have been with the same publication roughly, I guess 15-16 years at this point. I've been writing before there was cloud, core living and Opensource stuff, networking. And then through the magic of technology, I shifted a little bit to security, which is a core focus for me. I have been to every OpenStack Summit since the San Diego Summit, I guess, 2011. Somebody can correct me afterwards. I did miss the Sydney Summit for various reasons, but yeah, I've been to a bunch of these things, so interesting to see how things have shifted over the years from nothing to certain heights to where we are now. >> Alright, so bring us up to that, as to where we are now. Attendance is down a little bit. They haven't been talking a lot about it but quality I guess is here. Sessions, they've broadened down a bit of the scope. We have been digging into it, but want to get your take so far. >> Yeah, well it's like anything else, there are standard hype cycles, as it were and there's a trough of disillusionment. I wouldn't call this a trough of disillusionment, but when you get to a certain plateau, people just, there'sn't as much interest. In the early days, I remember the San Diego Summit I went to. They didn't schedule it properly. They didn't know how many people they were going to have, and they had to line up around the corner and stuff. That was six years ago, but that is when OpenStack was new. There was no such thing as the Foundation, and everyone was trying to figure out what was what. And, there was no clue at this point. Cloud is a well understood thing. There are competitive efforts or complimentary efforts, as the Foundation would probably like to put it; whether it's CNCF, there's the public cloud and it's different. There is, with all respect to the OpenStack Foundation and its member projects, there's not as much excitement. This in now a stable, mature ecosystem and because of that, I don't think there's as much of a draw. When something is brand new and shiny, you get more of a draw. If they would have put the name Blockchain somewhere, maybe, maybe they would have had a few more. They put Kubernetes in there, which is fine, but no machine learning or artificial intelligence quite yet, though that's a topic somewhere in there too. >> Yeah, John, you've been making a lot of comments this week talking about we've matured and the lower layer pieces just work a bit more. Give us your take about that. >> Sure. That's the way it seems. There wasn't a whole lot of talk about the release, news release, and all the different components, even the keynotes. But, the people we have talked to, both on the vendor and the customer side, they have working production OpenStack environments. They're very large. They require very few admins. They work. They're embedded in telecom and banking, et cetera. It's here and it's working. >> Yeah, that's so something that happened, maybe three cycles ago at this point, because they used to have the release the same time as the Summit and the Design Summit. It was together, so, there was essentially a celebration of the release. People would talk about the release and then they desegrigated that. I think that took a lot of steam out of the reason why you got developers to attend. So, when you don't have the Design Summit, there's this separate open endeavor, there's the forum, I don't quite understand how that works here now. There isn't as much momentum. Yeah, I agree with you. There has been very little talk about Queens. In each of the project update sessions I have been to, and I have been to a couple, there has always been a slight on Rocky, what's coming. I think we are on the second milestone of Rocky, at this point, so there's some development, but at this point it is incremental featurettes. There is no whiz bang. OK, we're going to have flying cars, you know send a Tesla to outer space kind of Earth shattering kind of news, literally, because that's not where it's at. It's just incremental tuck in features in stability and that kind of thing. >> Alright, you talk space and thinks like that and it brings to mind a certain attendee of the program that has actually been to outer space and maybe one of the more notable moments of the show so far. Give us your take on Mr. Shuttleworth. >> Well, I'm a big fan of Mr. Shuttleworth, top to bottom. Hey Mark. Big fan, always have been. He has his own opinion on things of course. Usually in a keynote you don't tend to take direct aim at competitors and he chose to do that. It made some people a little uncomfortable. I happened to be sitting in the front row, where I like to sit, and there was some Red Hat people, and there were some frantic emails going back and forth. And people were trying to see what was going on et cetera. I think, for me, a little bit of drama is okay. You guys go to more shows than I do, and sometimes you get these kind of sales kind of things. But in an open community, there's almost an unwritten rule, which perhaps will be written after this conference, that whether or not everybody is a business competitor or not, is that this is neutral territory as it were and everybody is kind of friendly. In the exhibit hall, you can say this and that, we are better, whatever, but on the stage you don't necessarily do that, so there was some drama there. Some of my peers wrote about that and I will be writing about it as well. It's a, I prefer to write about technology and not necessarily drama. Whether somebody is faster, better, stronger than others, you let the number prove them out. When we talk about Opensource, Opensource Innovation without Canonical, there probably wouldn't have been an OpenStack. All the initial OpenStack reference and limitations are on Canonical. They got a number of large public clouds, as does Red Hat. I think they both have their tactical merits and I'm sure on some respects Red Hat's better and on some respects Canonical is better, but him standing up there and beating on the competition was something that across the 13 summits I have been I have never seen before. One guy I talked to my first OpenStack Summit was in San Diego and the CTO of VMware at the time came up to, VMware was not an OpenStack contributor at the time, they were thinking about it, and he was fielding questions about how it was competitive or not and he was still complimentary. So there has always been that kind of thing. So, a little bit of an interesting shift, a little bit of drama, and gives this show something memorable, because you and I and others will be able to talk about this five years from now, et cetera. >> You talked about something you would write up. I mean part of your job is to take things back to the readers at eWeek. >> Yeah. >> What are the things, highlights you're going to be covering? >> The highlights for me, Stu and I talked about this at one point off the camera, this is not an OpenStack Summit necessarily, they're calling it Open Infrastructure. I almost thought that they would change, we almost thought that they would change the name of the entire organization to the Open Infrastructure Foundation. That whole shift, and I know the foundation has been talking about that since Sydney last year, that they're going to shift to that, but, that's the take away. The platform itself is not the only thing. Enabling the open infrastructure is nice. They're going to try and play well and where it fits within the whole stack. That gets very confusing because talking about collaboration is all fine and nice, but that is not necessarily news. That is how the hot dog is made and that's nice. But, people want to know what's in that dog and how it is going to work. I think it's a tougher show for me to cover than it has been in past years, because there has been less news. There's no new release. There was Kata 1.0 release and there was the Zuul project coming out on its own. Zuul project, they said it was 3.0, it was actually March was Zuul 3.03. Kata Container project, okay, interesting, we'll see how it goes. But a tougher project, tougher event for me to cover for that reason. Collaboration is all fine and nice. But, the CNCF CloudNativeCon KubeCon event two weeks ago, or three weeks ago, had a little bit more news and a lot it's same kind of issues come up here. So, long winded answer, tough to come up with lessons learned out of this, other than everyone wants to be friends, well some people want to be. And, collaboration is the way forward. But that is not necessarily a new message. >> When I think about Kubernetes, we are talking about the multi cloud world and that's still, the last few years, where it's been. Where does OpenStack really fit in that multi cloud world? One of the things I have been a little disappointed actually, is most of the time, when I'm having a conversation, it's almost the, yeah, there's public cloud, but we are going to claw things back and I need it for governments, and I need all of these other things. When I talk to customers, it is I'm going to choose what I put in my data center. I'm going to choose how I use probably multiple public cloud finders. It is not an anti-public cloud message, and it feels a little bit on the anti-public cloud mass. I want to work with what you're hearing when you >> talk to users? >> When I talk to users, vast majority of people, unless it's something, where there's regulatory issues or certain legacy issues or private cloud, public cloud period. The private cloud idea is gone or mostly gone. When I think about private clouds, it's really VmWare. We have virtualized instances that sitting there. >> What's OpenStack? >> OpenStack is fine, but how many are running OpenStack as a private cloud premise? >> Yeah, so what's OpenStack then? >> When I think of OpenStack, Oracles public cloud. Oracle is not here surprisingly. Oracle's public cloud, Larry Ellison, who I know you guys have spoken to more than once on theCUBE at various points on Oracle World and other things. Oracle's public cloud, they want to compete against AWS. That's all. OpenStack IBM cloud, all OpenStack. The various big providers out of China are OpenStack based. OEH is here. So that's where it fits in is that underlying infrastructure layer. Walmart uses it. Bestbuy, all these other places, Comcast, et cetera; ATT. But individual enterprises, not so much. I have a hard time finding individual enterprises that will tell me we are running our own private cloud as OpenStack. They will tell me they're running VmWare, they will tell me they're running REV or even some flavor of Citrix end server, but not a private cloud. They may have some kind of instances and they will burst out, but it's not, I don't think private cloud for mid tier enterprises ever took off the way some people thought five years ago. >> That's interesting. Let's go meta for a second. You talked about things you do and don't write about, you don't necessarily write the VC's are not here necessarily, but you don't write about necessarily financial stuff. >> Sometimes. There was actually at the Portland summit, I did a panel with press and analysts at the time and afterwards there might have been four different VC's that came up to me and asked me what I thought about different companies. They were looking at different things where they would invest. And I remember, we looked at the board and one VC who shall remain nameless, and I said you know what, we'll look at this board with all these companies and five years from now, three quarters of them will not be here. I think I was probably wrong because it is more than that. There are so many. I wrote a story, I don't remember the exact name of it, but I wrote a story not that long ago about OpenStack deadpool. There are so, multiple companies that raised funding that disappeared. In the networking space, there were things like Plumgrid, they mminorly acquired for assets by Vmware, if I'm not mistaken. There was Pivotal, Joshua McKenzie, one of the co-founders of OpenStack itself, got acquired by Cisco. But they would have collapsed perhaps otherwise. Nebula Computing is perhaps, it still shocks me. They raised whatever it was 50 odd million, someone will correct me afterward. Chris Kemp, CTO of NASA who helped start it. Gone. So, there has been tremendous consolidation. I think when VC's lose money, they lose interest really fast. The other thing you have to think about, from the VC side, they don't write too much on the financial. My good friend Fredrick, who didn't make it, Where are you, Fredrick, where are you? Does more on that funding side. But has there been a big exit for an OpenStack company? Not really, not really. And without that kind of thing, without that precedence it's a tough thing, especially for a market that is now eight years old, give or take. >> Even the exits that had a decent exit, you know that got bought into the say IBM's, Cisco's of the world, and when you look a couple of years later, there's not much left of those organizations. >> Yeah. It's also really hard. People really don't want to compete against, well, some people want to compete against AWS. But, if you're going to try to go toe to toe with them, it's a challenge. >> Okay, so what brings you back here every year? You're speaking at the show. You're talking to people. >> What brings me back here is regardless of the fact that momentum has probably shifted, it's not in that really hype stage, OpenStack's core infrastructure, literally, core infrastructure that runs important assets. Internet assets, whether it certain public cloud vendors, large Fortune 500 companies, or otherwise. So it's an important piece of the stack, whether it's in the hype cycle or not, so that brings me back, because it's important. It brings me back because I have a vested interest. I have written so much about it so I'm curious to see how it continues to evolve. Specifically, I'm speaking here on Thursday doing a panel on defending Cloud Counsel Security as a core competence, a core interest for me. With all these OpenStack assets out there, how they're defended or not is a critical interest. In the modern world, cyber attacks are a given. Everybody should assume they're always under a constant state of attack and how that security works is a core area of interest and why I will keep coming back. I will also keep coming back because I expect there to be another shift. I don't think we have heard the end of the OpenStack story yet. I think the shift towards open infrastructure will evolve a little bit and will come to an interesting conclusion. >> Alright, last thing is what's your favorite question you're asking at this show. Any final things you want to ask us as we wrap? >> Yeah, my favorite, well, I want to ask you guys, what the most interesting answer you got from all the great people you interviewed because I'm sure some of it was negative and you got mostly positive as well. >> Well, we aren't used to answering the questions Stu. >> I'm used to being on the other side here, right. >> Well, I do say we got a lot of stuff about some interesting and juicy cases, like I say, the practitioners I talked to were real. I was always impressed by how few administrators it takes to run a huge OpenStack based cloud once it's set up. I think that's something interesting to me. You asked some folks about a public cloud a lot. >> Yeah, so it has been interesting. For me, it's, we've reached that certain maturity level. I was looking at technology. What's kind of the watermark that this is going to come to? We had said years ago, I don't think you're going to have somebody selling a billion dollars worth of distribution on OpenStack. So, that story with how Kubernetes and Containers and everything fits in, OpenStack is part of the picture, and it might not be the most exciting thing, but then again, if you watch Linux as long as most of us have, Red Hat took a really long time to get a billion dollars and it was much more than just Linux that got them there. This still has the opportunity to be tooling inside the environment. We have talked to a number of users that use it. It's in there. It's not that the flagpole, we're an OpenStack company anymore because there really aren't many companies saying that that is the core of their mission, but that is still an important piece of the overall fabric of what we are covering. >> Exactly right. >> Alright, we on that note, Sean Michael Kerner, we really appreciate you joining us. Please support good technology journalism because it is people like him that help us understand the technology. I read his stuff all the time and always love chatting with him off the record and dragged him on here and Fredrick from Techron Show we are disappointed you could not join us, but we'll get you next time. For Jon Troyer, I'm Stu Miniman, be sure to join us for the third day tomorrow of three days of wall to wall live coverage here from OpenStack Summit 2018 in Vancouver. And once again, thank you for watching theCUBE. (upbeat music)