>>From around the globe. It's the cube with digital coverage of AWS reinvent 2020 sponsored by Intel and AWS. >>Welcome back to the cubes coverage of AWS reinvent 2020 live I'm Lisa Martin. Really exciting topic coming up for you next, please. Welcome Blake shoulda, founder and CEO of boom supersonic Blake. It's great to have you on the program. Thank you for having me, Lisa, and your background gives me all the way with what we're going to talk about in the next few minutes or so, but supersonic flight has existed for quite a long time, like 50 or so years. I think those of us in certain generations remember the Concorde for example, but the technology to make it efficient and mainstream is only recently been approved by or accepted by regulators. Tell us a little bit about boom, your mission to make the world more accessible with supersonic commercial flight. Well, a supersonic flight has >> actually been around since 1949 when Chuck Yeager broke the speed barrier or sorry, the sound barrier. >>And as, as many of you know, he actually passed yesterday, uh, 97. So very, very sad to see one of the supersonic pioneers behind us. Uh, but, uh, but as I say goodbye to Jaeger, a new era of supersonic flight is here. And if you look at the history of progress and transportation, since the Dawn of the industrial revolution, uh, we used to make regular progress and speed. As we went from, uh, the horse to the iron horse, to the, the boats, to the, the early propeller airplanes that have the jet age. And what happened was every time we made transportation faster, instead of spending less time traveling, we actually spent more time traveling because there were more places to go, more people to meet. Uh, we haven't had a world war since the Dawn of the jet age. Uh, places like Hawaii have become, uh, a major tourist destination. >>Uh, but today, uh, today it's been 60 years since we've had a mainstream re uh, step forward and speed. So what we're doing here at boom is picking up where Concord left off building an aircraft that flies faster by factor to the, anything you can get a ticket on today. And yet is 75% more affordable than Concorde was. So we want to make Australia as accessible as a why yesterday. We want to enable you to cross the Atlantic, do business, be home in time, detect your kids into bed, or take a three-day business trip to Asia and let you do it in just 24 >> hours. I like the sound of all of that. Even getting on a plane right now in general. I think we all do so, so interesting that you, you want to make this more accessible. And I did see the news about Chuck Yeager last night. >>Um, designing though the first supersonic airliner overture, it's called in decades, as you said, this dates back 60 years, rolling it out goal is to roll it out in 2025 and flying more than 500 trans oceanic routes. Talk to me about how you're leveraging technology and AWS to help facilitate that. Right. Well, so one of the really fascinating things is the new generation of airplanes, uh, are getting born in the cloud and then they're going to go fly through actual clouds. And so there are, there are a bunch of revolutions in technology that have happened since Concord's time that are enabling what we're doing now, their breakthroughs and materials. We've gone from aluminum to carbon fiber they're breakthroughs and engines. We've gone from after burning turbo jets that are loud and inefficient to quiet, clean, efficient turbo fans. But one of the most interesting breakthroughs has been in a available to do design digitally and iteration digitally versus, uh, versus physically. >>So when conquer was designed as an example, they were only able to do about a dozen wind tunnel tests because they were so expensive. And so time consuming and on, uh, on our XP one aircraft, which is our prototype that rolled out in October. Um, uh, we did hundreds of iterations of the design in virtual wind tunnels, where we could spin up a, uh, a simulation and HPC cluster in AWS, often more than 500 cores. And then we'd have our airplanes flying through virtual wind tunnels, thousands of flights scenarios you can figure out which were the losers, which were the winners keep iterating on the winners. And you arrive at an aerodynamic design that is more efficient at high speed. We're going very safely, very quickly in a straight line, but also a very smooth controllable for safe takeoff and landing. And the part of the artist supersonic airplane design is to accomplish both of those things. One, one airplane, and, uh, being able to design in the cloud, the cloud allows us to start up to do what previously only governments and militaries could do. I mentioned we rolled out our XP one prototype in October. That's the first time anyone has rolled out a supersonic civil aircraft since the Soviet union did it in 1968. And we're able to do as a startup because of computing. >>That's incredible born in the cloud to fly in the cloud. So talk to me about a lot of, of opportunity that technology has really accelerated. And we've seen a lot of acceleration this year in particular digital transformation businesses that if they haven't pivoted are probably in some challenging waters. So talk to us about how you're going all in with AWS to facilitate all these things that you just mentioned, which has dramatic change over 12, uh, when tone test for the Concord and how many times did it, >>Uh, I mean for 27 years, but not that many flights, never, it never changed the way mainstream, uh, never, never district some of you and I fly. Right. Um, so, so how, how are we going all in? So we've, you know, we've been using AWS for, uh, you know, basically since the founding of the company. Uh, but what we, what we're doing now is taking things that we were doing outside of the cloud and cloud. Uh, as an example, uh, we have 525 terabytes of XP one design and test data that what used to be backed up offsite. Um, and, and what we're doing is migrating into the cloud. And then your data is next. Your compute, you can start to do these really interesting things as an example, uh, you can run machine learning models to calibrate your simulations to your wind tunnel results, which accelerates convergence allows you to run more iterations even faster, and ultimately come up with a more efficient airplane, which means it's going to be more affordable for all of us to go to go break the sound barrier. >>And that sounds like kind of one of the biggest differences that you just said is that it wasn't built for mainstream before. Now, it's going to be accessibility affordability as well. So how are you going to be leveraging the cloud, you know, design manufacturing, but also other areas like the beyond onboard experience, which I'm already really excited to be participating in in the next few years. >>Yeah. So there's so many, so many examples. We've talked about design a little bit already. Uh, it's going to manifest in the manufacturing process, uh, where the, the, the, the, the supply chain, uh, will be totally digital. The factory operations will be run out of the cloud. You know, so what that means concretely is, uh, you know, literally there'll be like a million parts of this airplane. And for any given unit goes through their production line, you'll instantly know where they all are. Um, you'll know which serial numbers went on, which airplanes, uh, you'll understand, uh, if there was a problem with one of it, how you fixed it. And as you continue to iterate and refine the airplane, this, this is one of things that's actually a big deal, uh, with, with digital in the cloud is, you know, exactly what design iteration went into, exactly which airplane and, uh, and that allows you to actually iterate faster and any given airline with any given airplane will actually know exactly what, what airplane they have, but the next one that rolls off the line might be even a little bit better. >>And so it allows you to keep track of all of that. It allows you to iterate faster, uh, it allows you to spot bottlenecks in your supply chain before they impact production. Um, and then it allows you to, uh, to do preventive maintenance later. So there's to be digital interpretation all over the airplane, it's going to update the cloud on, you know, uh, are the engines running expected temperature. So I'm gonna run a little bit hot, is something vibrating more than it should vibrate. And so you catch these things way before there's any kind of real maintenance issue. You flag it in the cloud. The next time the airplane lands, there's a tech waiting for the airplane with whatever the part is and able to install it. And you don't have any downtime, and you're never anywhere close to a safety issue. You're able to do a lot more preventively versus what you can do today. >>Wow. So you have to say that you're going to be able to, to have a hundred percent visibility into manufacturing design, everything is kind of an understatement, but you launched XQ on your prototype in October. So during the pandemic, as I mentioned, we've been talking for months now on the virtual cube about the acceleration of digital transformation. Andy, Jassy talked about it in his keynote at AWS reinventing, reinventing this year, virtual, what were some of the, the, the advantages that you got, being able to stay on track and imagine if you were on track to launch in October during a time that has been so chaotic, uh, everywhere else, including air travel. >>Well, some of it's very analog, uh, and some of it's very digital. So to start with the analog, uh, we took COVID really seriously at Bo. Uh, we went into that, the pandemic first hit, we shut the company down for a couple of weeks, so we'd kind of get our feet underneath of us. And then we sort of testing, uh, everyone who had to work on the airplane every 14 days, we were religious about wearing masks. And as a result, we haven't had anyone catch COVID within the office. Um, and I'm super proud that we're able to stay productive and stay safe during the pandemic. Um, and you do that, but kind of taking it seriously, doing common sense things. And then there's the digital effort. And, uh, and so, you know, part of the company runs digitally. What we're able to do is when there's kind of a higher alert level, we go a little bit more digital when there's a lower alert level. >>Uh, we have more people in the office cause we, we still really do value that in-person collaboration and which brings it back through to a bigger point. It's been predicted for a long time, that the advent of digital communication is going to cause us not to need to travel. And, uh, what we've seen, you know, since the Dawn of the telephone is that it's actually been the opposite. The more you can know, somebody even a little bit, uh, at distance, the hungry you are to go see them in person, whether it's a business contact or someone you're in love with, um, no matter what it is, there's still that appetite to be there in person. And so I think what we're seeing with the digitization of communication is ultimately going to be very, um, uh, it's very complimentary with supersonic because you can get to know somebody a little bit over a long distance. You can have some kinds of exchanges and then you're, and then the friction for be able to see them in person is going to drop. And that is, uh, that's a wonderful combination. >>I think everybody on the planet welcomes that for sure, given what we've all experienced in the last year, you can have a lot of conversations by zoom. Obviously this was one of them, but there is to your point, something about that in-person collaboration that really takes things can anyway, to the next level. I am curious. So you launched XB one in October, as I mentioned a minute ago, and I think I read from one of your press releases planning to launch in 2025, the overture with over 500 trans oceanic routes. What can we expect from boom and the next year or two, are you on track for that 2025? >>Yeah. Things are going, things are going great. Uh, so to give a sense of what the next few years hold. So we rolled out the assembled XB one aircraft this year, uh, next year that's going to fly. And so that will be the first civil supersonic, uh, flying aircraft ever built by an independent company. Uh, and along the way, we are building the foundation of overture. So that design efforts happening now as XB one is breaking the sound barrier. We'll be finalizing the overture design in 22, we'll break ground in the factory in 23, we'll start building the first airplane and 25, we'll roll it out. And 26 we'll start flight tests. And, uh, and then we'll go through the flight test methodically, uh, systematically as carefully as we can, uh, and then be ready to carry passengers as soon as we are convinced that safe, which will be right around the end of the decade, most likely. >>Okay. Exciting. And so it sounds like you talked about the safety protocols that you guys put in place in the office, which is great. It's great to hear that, but also that this, this time hasn't derailed because you have the massive capabilities of, to be able to do all of the work that's necessary, way more than was done with before with the Concorde. And that you can do that remotely with cloud is a big facilitator of that communication. >>Yeah. You're able to do the cloud enables a lot of computational efficiencies. And I think about the, um, many times projects are not measured in how many months or years exactly does it take you to get done, but it's actually much easier to think about in terms of number of iterations. And so every time we do an airplane iteration, we look at the aerodynamics high speed. We look at the low speed. We look at the engine, uh, we look at the, the weights. Uh, we look at stability and control. We look at pilots, light aside, et cetera, et cetera. And every time you do an iteration, you're kind of looking around all of those and saying, what can I make better? But each one of those, uh, lines up a little bit differently with the rest now, for example, uh, uh, to get the best airplane aerodynamically, doesn't have a good view for the pilot. >>And that's why Concord had that droop nose famously get the nose out of the way so we can see the runway. And so we're able to do digital systems for virtual vision to let the pilot kind of look through the nose of the runway. But even then they're, trade-offs like, how, how good of an actual window do you need? And so your ability to make progress in all of this is proportional to how quickly you can make it around that, that iteration loop, that design cycle loop. And that's, that's part of where the cloud helps us. And we've, we've got some, uh, uh, some stuff we've built in house that runs on the cloud that lets you basically press a button with a whole set of airplane parameters. And bam, it gives you a, it gives you an instant report. I'm like, Oh, was it that this is a good change or bad change, uh, based on running some pretty high fidelity simulations with a very high degree of automation. And you can actually do many of those in parallel. And so it's about, you know, at this stage of the program, it's about accelerating, accelerating your design iterations, uh, giving everyone of the team visibility into those. And then, uh, I think you get together in person as it makes sense to now we're actually hitting a major design milestone with over-treat this week and we're, COVID testing everybody and get them all in the same room. Cause sometimes that in-person collaboration, uh, is really significant, even though you can still do so much digitally. >>I totally agree. There's there's certain things that you just can't replicate. Last question since my brother is a pilot for Southwest and retired Lieutenant Colonel from the air force, any special training that pilots will have to have, or are there certain pilots that are going to be maybe lower hanging fruit, if they have military experience versus commercial flight? Just curious. >>Yeah. So our XB one aircraft is being flown by test pilots. There's one ex Navy one ex air force on our crew, but, uh, overture, uh, will be accessible to any commercial pilot. So, uh, think about it as if you're, if you're used to flying Boeing, it'd be like switching to Airbus, uh, or vice versa. So the, uh, Concord is a complicated aircraft to fly because they didn't have computers. And all the complexity, the soup of supersonic flight was right there and the pilots and an overture, all that gets extracted by software. And, uh, you know, the, the, the ways the flight controls change over speed regimes. You don't have to worry about it, but the airplane is handled beautifully, no matter what you're doing. And so, uh, and so there are many, many places to innovate, but actually pilot experience, not one of them, >>Because the more conventional you can make it for people like your brother, the easier it's going to be for them to learn the aircraft. And therefore the safer it's going to be to fly. I'll let them know, like this has been fantastic, really exciting to see what boom supersonic is doing and the opportunities to make supersonic travel accessible. And I think at a time when everybody wants the world to open up, so by 20, 26, I'm going to be looking for my ticket. Awesome. Can't wait to have you on board. Likewise for Blake shul, I'm Lisa Martin. You're watching the QS live coverage of AWS reinvent 2020.

>> Narrator: From around the globe it's theCUBE with digital coverage of AWS reinvent 2020. Sponsored by Intel, AWS and our community partners. >> All right, you're continuing coverage of AWS reinvent 2020 virtual event. We get the pleasure of covering this show like no other AWS reinvent. We are pulling in from the other side of the world Tomer Levy, CEO of Logz.io. First time Cuber so we're going to ease them into it but it's going to be a great conversation. I'm Keith Townsend at CTO advisor. Tomer, welcome to the show. >> Keith, thank you for having me. I'm super excited to be here. >> You know what? We love having founders here on theCUBE. We have a long history of having deep conversations with builders and we're probably the show for builders. AWS reinvent is virtual. However, I think the spirit of re-invent is highlighted in companies like this. We've seen a lot of observability companies sprout up around the industry. AWS is a big, big magnet for these types of solutions. What's the assets Logz.io and how are you guys differentiating yourselves in this crowded space? >> Yeah, absolutely Keith you see observability is so fundamental to building applications on AWS that as companies develop more applications, they have to have solid observability. And we have a mission and our mission is to enable develop engineers and any engineer out there to use open source to run their observability. So when we were developers we wanted to use open source but we had to compromise on a proprietary solution. We decided to build the company so engineers can use the observability tools they're already using for logging, for metrics, for tracing, Whatever they're already using we want to enable them to use that at scale on AWS. So it's easy to use, it's super smart and the data is coordinated. And I think fundamentally it's what we're doing very differently in the market. There is no other company in the market today that takes the best open sources and bring them together as one super strong platform and we're proud to be that company. >> Well, when you say there's no other company doing open source the way that you guys are doing it, that really intrigues me especially as we look at this from the angle of Cooper Netties, the CEO of the leading virtualization company called Kubernetes, the doubts home of the internet. How do you see the intersection of opensource observability in kubernetes especially in the public cloud? >> Yeah, for sure. People say that kubernetes is almost the operating system of the future and why do people use kubernetes? They use it to make sure they can run multiple microservices. They can take their application which used to be a monolith and put it in a distributed way. So it becomes so much harder to monitor or to troubleshoot even to secure applications. So the way we built Logz.io was really designed for companies that are moving into the cloud, companies moving into kubernetes, into microservices and by having logs and metrics and traces all work together through the best open sources. I think we can help customers really get the visibility and just accelerate the software delivery. Just provide better service to their customers. >> So Levy, walk me through that journey. What is it like for a developer to come from their traditional open source roots and enter the cloud where they're melding public cloud services in AWS alongside their tools that they're using in observability. How do you help ease that transition? >> Yeah, absolutely Keith because one of the main drivers for companies adopting tools like Logz.io is actually the migration to AWS. So imagine now migration to a new ground, what do you have to think about first? Do I have the glasses? Can I see what's going on? Like when I see what's going on, I feel more confident. So if I'm now using, let's call it elk or using the open-source Grafana or using tools like Jaeger, which are all open sources too that we offer as part of our platform. So when I use these tools I'm using them to get visibility into my own application, my own infrastructure. So Logz.io faster transition to Logz.io is super easy. This is the whole notion of having an open source compatible platform. So I want to move to Loz.io, everything that worked with my open source currently still works with Logz.io but now when you move to the cloud Logz.io on AWS, we have a very strong relationship so all the services are automatically monitored. You have pre-configured dashboard, everything is interconnected so just when I jump into the AWS platform I immediately get visibility of my existing apps and of the AWS infrastructure. And that eventually helped me become confident, grow and deliver faster on AWS. >> So again this is a conference full of builders but you used the term devOps. We're starting to see a bleeding of DevOps and builders or operations and builders come together. One of the big trans and DevOps and observability is AI and machine learning. What are some of the features of AI and Machine Learning you guys are bringing to bear to this market? >> Yeah, listen I'm a big believer in AI. You know, the amount of data that companies like Logz.io have to ingest and our customers have to process. It's just something a human being cannot possibly understand. It's like billions and millions of lines of data. So this is where we bring machines to help humans. I'll give you one example, right? If you're a DevOps engineer and you see an issue in your logs, what do you do? You usually copy that and putting it into Google and you'll end up on stack overflow, maybe on GitHub, maybe on another website. What we have done is we've scraped the web and we have learned from any user on our platform. So we actually know which log line is important and which one is not. So when companies send a log line, our AI automatically scans it and says, "Hey, here are the billion log lines. No one cares about but here is one that you should really look at right now because either you know half a million people that were searching for it. There are 7,000 alerts on this and it just happened to you. Keith look, maybe you should jump in and look at that". This is where AI makes us just better operate or better DevOp people and not kind of try to replace us. >> So I'm a technical founder, you're a technical founder, theCUBE loves supporting founders. One of the advantages of being the CEO of your company is that you get to decide the culture and the mission of your company. Talk to me about the people side of your organization and how you're making a change for the better. >> Yeah, absolutely. You know, it is a privilege and to the privilege to start and come with a mission that you want to change something in the world and we were just two developers, a staff, my co-founder and myself having to use a product we didn't want to use and you know still really wanted to use an open source product. So we said let's build the company around that and this is kind of set the mission for the company as the company evolved, so is our mission. It evolves from logging to monitoring, to tracing and we also added a cloud SIEM solution all based on open source. So we're going to DevOps engineers and any engineers and we tag any engineer we tell them, "Hey, you can use the best open source tools in the cloud is one platform without compromising". And that's something that really is very differentiated today and I'm very humbled and excited to be part of this journey and I think the team at Logz.io is as well. >> You know I'm always intrigued about this journey to the cloud. Security is one of these things that intrigues me especially as we look at something as mature in the way open source. We often associate open source with public cloud, cloud native but open source is as old as technology itself. So there is a lot of practices that we bring from legacy, traditional infrastructures into the public cloud. So talk to me about that transition of security and security models? How does observability help to either take our existing tools and migrate them to the public cloud or adopt all new cloud native tools in the public cloud? >> Yeah, for sure. I think security is probably together with observability. One of the top priority that when you think about CTOs and VP of Engineering and CSOs, they're concerned about. So we've taken the observability path and bringing better glasses to our users and then on the security side there's a whole market called the SIEM market where companies look at detecting threats, investigating them and most of these tools were that companies use our legacy, incumbents and for design on their own premises world. And are not really a fit for the dynamic world of kubernetes and the cloud. And this is when we decided a couple of years ago to launch a product in that space and today this product is extremely successful. We have customers protecting their AWS environments across the board. So basically with one product for observability, you can with a single checkbox enable security and then you can detect threats. You can look at kind of the common pitfalls of AWS environment and how you can avoid them. And eventually when you see a threat, you can use our tool to investigate and find the root cause in a tool which was designed on AWS for AWS. And it's really designed for the kind of the native cloud environment rather than the on-premise as well. >> Now, is there an integration between the AI ML law of management and the threat management solutions from our observability perspective? >> Yeah, for sure. This is the beauty, it's all one data platform. So customers ship their data, loads, metrics and traces into one place and then we start to look at how can we provide more value on the data, right? How can we look at the logs from an operational perspective and tell you, "Hey, your production might be going down because of a production risks or maybe we can provide you threat intelligence". We can enrich the data and tell you, "Hey, we think you're undergoing an attack right now". So this is all done by users and it is all enraged by AI that provides more visibility, more enrichment of the data and just advice on where to look. >> So Tomer levy, CEO, founder of Logz.io. You're now a few belong. Thank you for joining the show. I hope you have a very successful AWS reinvent. Speaking of AWS reinvent, theCUBE's nonstop coverage of AWS reinvent continues. Watch some of the world's greatest builders, innovators get challenged on their vision and for us to understand and appreciate the work that's been done in this dynamic community. Continue to watch this coverage and more. Talk to you next interview on the CUBE's coverage, of AWS reinvent 2020. (soft music)

>> From around the globe, it's theCUBE, with coverage of KubeCon and CloudNativeCon Europe 2020 virtual. Brought to you by Red Hat, the Cloud Native Computing Foundation and ecosystem partners. >> Welcome back I'm Stu Miniman. And this is theCUBE coverage of KubeCon CloudNativeCon 2020, the Europe virtual edition. Happy to welcome back to the program, fresh off the keynote stage, Priyanka Sharma. She's the general manager of the CNCF. Priyanka, thanks so much for joining us. Great to see you. And we all get to be together even while we're apart. >> That's absolutely right. Thank you so much for having me Stu and great energy in the interwebs today with my keynote and everybody engaging and attending KubeCon. So, very happy to be here. >> All right, so I want to dig into your keynote a little bit. I had a bunch of key themes, a lot of pieces, and of course, community at the heart of it. When I spoke with you when you first took the job, of course, you've got strong background, you know this community really well. We've loved covering it for the last five years, but you talked about the foundation of doers and how that's powering the end user driven open tour. So talk to us a little bit about that, how is this community different from everything else. You know, open source always is community, but this feels a little bit special. >> Well, I'm glad to hear you say that, it is special. Yes, so when you think about the Cloud Native Ecosystem, right? There's so many people who've come together to create this amazing field that we all get to create. The awesome technology that people use to be part of this whole technology creation and deployment process. Those people are the end users first and foremost, they utilize the technology every day. And as time has grown, as time has gone by, they have played a bigger and bigger role. Over time they've become very sophisticated, they're contributing their own projects such as you know, I mean, you all know Envoy and a Jaeger came from Lyft and Uber respectively, but there's many more like Spotify and Wayfair, the furniture company. They have all submitted projects for the sandbox. So there was a lot of momentum, but not only are they creating their own technologies very needed and donating them. They're becoming the guider. They're becoming the guidance for the project that exists. They're giving feedback, they're sharing requirements. It's a very collaborative process and that's what is end-user-driven open source. Now this end user-driven-open source cannot happen by one contributor alone by one maintainer or alone by one company. No, it takes a lot of people. I mean, CNCF, as you know, has invested in its global community since day one. That's why we have the KubeCon EU, we have China events, we have North America. And just the other day I was speaking on a virtual Brazil event. There's just the geographic diversity is amazing. And by being able to reach out to a very large ecosystem and by especially having a formal role for end users, by having an end user member program with their own special interest groups and working groups, we've created a safe space where there is a neutral IP zone, open governance, and also a clear directive and shared partnership with the end users. So that ends up being a large group of people who are all doers, everybody's collaboration matters, and together they create end user-driven-open source. >> Well, Priyanka, I'm not sure that that most people understand really the full charter of what the CNCF does. So maybe you could talk a little bit about, obviously there's all the projects involved. You just brought up some of the end users and how you get engaged. There's also help along career development, when you talk to the individual developers and participants. So help us understand beyond the big events that we gather people at any given time with the smaller events, just, you know, what the CNCF its charter as these days. >> Absolutely, so as some of you know, the CNCF stands for Cloud Native Computing Foundation. And our objective is to host and proliferate technologies that support development, infrastructure development that is cloud native. Now what does cloud native mean, cloud native is when you develop, when you utilize cloud computing, which is the big clouds you must have heard of such as, Alibaba cloud, AWS, Google cloud platform, Azure, IBM, all these hyperscalers. They provide these offerings by which you don't need to have your own server farm, and you can buy compute from them and run your applications on that. When you do that, the way you develop software changes, it should change in order to maximize the value you get. So you started developing with micro services, containerization happens once that happens you need to orchestrate the containers, which is where Kubernetes our founding project comes in. And then you go from there because you have different complexities and observability, you have different complexities and storage and all the cloud native tech comes together to support you in that journey. So from a technology perspective that's what we do. As we have been so fortunate to develop this large ecosystem that so many people joining in of all kinds, we believe it is part of our responsibility to support this community in skill development and always like knowledge sharing. So knowledge sharing community empowers education. And that's how we talked about the events, right? Like KubeCon et cetera. But also these days, we are focusing a lot on our programs with the certifications we offer such as a CKA, which stands for a Certified Kubernetes Admin and CKAD, which stands for Certified Kubernetes Application Developer. To date, 15,000 plus people have taken these certifications successfully. So we have more and more people joining in these ranks. And we are here to support people as they build their careers, as they get more knowledgeable on cloud native, from in formal ways, such as training edX and in informal ways, such as KubeCon and the Meetups and the Webinars, you name it, and we're here for you. >> Well, you used a word that I want to touch on, responsibility, obviously in 2020, there's a lot going on Priyanka. So first of all, you talk about the global pandemic. Some of my favorite interviews I've done for this shows and others talking about how open source and communities are contributing to it. One of the interviews I have coming up for the KubeCon show is out of the Pronto area with how's my flattening, which uses data and visualization, really phenomenal to see how, you know, Kubernetes and collaboration allowed people to rally fast and share data and get information from the right people. The other piece is social justice. You announced a new working group for racial terminology, talk about, how's the CNCF dealing with, all the changes and all the things that are happening in 2020. And how are you helping the community get engaged and participate? >> Absolutely. 2020s is a very unique year. It's had very unique challenges. We've all been through it out together as a global community. So in that way, it has brought us all together, but the fissures and cracks that maybe were overlooked before have gotten deeper this year. And we are committed to bringing the open source cloud native way to help support this full global push to overcome 2020 as a year. (laughs) So part of that as you said, we have a working group to eradicate racially charged tech, sorry, I am really not speaking well to that. So part of our initiatives is a working group to eradicate racially charged terminology from code we're working on it, not just on the CNCF level, but on the entire Linux foundation level, by bringing together various folks, such as companies projects, regardless of where they stand, they don't need to be an LF project or a CNCF project, but we're sharing best practices on What should be the terminology we agree upon? What is the change management look like? And soon we want to really encourage the people who are making these positive steps with and enablement and incentive programs, such as prizes, et cetera. So I'm very committed to this. I think anyone and everyone has a home in open source. This cannot be, you know, the take ground of one type of person or one type of community. And we're going to do our very best to welcome each and every one. This world of technology has been built by the blood, sweat, and tears off many people, and we honor them all. And we also open our arms to more and more of you, no matter how few of people from your ecosystem or community you see in open source, join in, we welcome you.. we are here for you and this working group and this initiative hopes to voice exactly just that. >> Well, yeah, the KubeCons absolutely. I can speak from the event I've gone to, you know, strong diversity. We've really appreciated being able to hear those voices. When you talk about the collaboration, the community activity, we'd love when we can help support those from our team's standpoint, when we can, we want to be able to help those nonprofits, help those communities get their messages and do their call to actions. All right, Priyanka so much to cover. This week when I look at all the breakouts, when I look at the interviews and the technologies, there's a lot of emerging themes also in edge computing has been something we've been talking about for the last year or two, of course, IOT, DevSecOps, what are some of the hot technologies that you're seeing and making sure that the show covers. >> Well, you send them all. (laughs) No, but these are the key themes. Yes, absolutely. As you know, devices are proliferating across the globe. So many people have cell phones, with the coming of 5G things will be even more rocket ship. And these folks need to go cloud native to support development as this change happens, and Kubernetes and CNCF is here to support. We have projects such as KubeEdge. We have k3s from Rancher and the sandbox, all these are meant for edge deployment. So there's that focus that we have. There's always going to be DevSecOps. The minute there is this complexity, the minute there's this growth, new security vulnerabilities, pop up, new interfaces become exposed. And so we have to be on a constant watch. So DevSecOps is a theme that we are going to see a lot of innovation and development in. For anyone who may not be familiar with DevSecOps, DevSecOps does for security, what DevOps did for operations, which is shifted left into the application developers workflow, so that things have got faster so that there is a better collaboration between security teams and application development team. So these are absolutely trans, I think a trend we briefly touched upon is, end-user-driven open source. I think the voice of end users is going to grow bigger and more louder and just that much more critical. The ship has left the dock. And now it's just going to gain steam and gain steam. I think we're going to see more technology contributions from them. We're going to see much more utilization of cloud native from them. And we also will get lots of feedback and advice from them. And there'll be interwoven into the fabric of cloud native in a way like never before. >> Yeah, Priyanka, you've known this community, but now you're very steeped into it. You had to work with a lot of people. I'm curious, does anything, especially from those end users, you know, a big focus of what you've been talking about. Absolutely, it's so important that they not just use the technology, but are participate in it. It's been one of those big waves we've been watching in the open source community for a number of years. So any insight you can give us as to why it is so important to those end users, what is encouraging them, not just to, use these projects, but, you know, assigned people and sponsor events and have much deeper integration with this community. >> They don't integrate with this community. They are part of this community. That's one key thing to remember. I would say, when we all, like, I mean, CNCF is relatively young, it started end of 2015. I started working on a project in it in 2016. And back then we were talking about things like, what are microservices? How to do a lift and shift to the cloud, or what are containers, things like that, right? And there was maybe a bit of a gap in the knowledge that people had to acquire to get good at deploying containers, that's using microservices, et cetera, et cetera. Now, in the last four years, huge leaps have been made by an users just because they were in the trenches, they were doing the work, right? So now their knowledge level has gone really up. And they've also started like knowing where the gaps are, what they need, because they're doing the building, they're the doers here. And so in that environment, it is a natural thing that they will have the best sense of where things should go next. They will have the best sense of what their own requirements are. And so it's an evolution of the end user community. It's an evolution of the doers. And I think that's why this trend is going to continue. And I would like to take like, not a credit, but I would say a tiny shoutout to the CNCF ecosystem program, which is run by Cheryl on my team. She's done a phenomenal job having been a developer herself to bring people and create safe spaces where the enhancers or the vendors are not like necessarily breathing down their neck and they can discuss amongst each other, the topics that matter. And I think that's gone a really long way. >> Yeah. There's, Cheryl's been doing some great work. I know I'm having a conversation with Liz Rice to talk about some of the new pooling, helping customers understand. It's such a broad ecosystem out there that, you know, we didn't even touch on. We're going to talk in many of the other interviews I have Priyanka. There's so many projects, new ways for sandbox and incubation and everything like that. It is definitely a challenge for everybody to look at this space. Want to give you the final word though. What do you want people to have as their takeaway from the event this time? >> Absolutely. Hi everybody. I am so happy. You all took the time and engaged with the community you joined in and attended KubeCon EU virtual, stay with us, partnering with us, come to our events, give us feedback, share ideas. We're all a foundation of doers. We're all team cloud native, and we're in this together. We will go through 2020, we'll come out strong. And this is just the beginning. >> Well, Priyanka, thank you so much. We love the partnership with the CNCF and definitely happy to be able to participate in the event again this year. >> Absolutely. Thank you so much Stu. >> All right, and stay tuned. Lots of coverage here from KubeCon, CloudNativeCon 2020 Europe the virtual edition. I'm Stu Minimam. And thank you as always for watching theCUBE. (upbeat music)

>> From theCUBE Studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE Conversation. >> Hi, I'm Stu Miniman, and welcome to this CUBE Conversation. I'm coming to you from our Boston area studio. I'm happy to welcome to the program someone we've known for many years, but a first time on the program. Priyanka Sharma, thank you so much for joining us. >> Hi, Stu. Thank you so much for having me. >> All right, and Priyanka, let's not bury the lead or anything. The reason we're talking to you is the news. You've got a new job, but in an area that you know really well. So we've known you through the cloud native communities for a number of years. We see you at the shows. We see you online. So happy to share with our community you are now the general manager of the CNCF, so congratulations so much on the job. >> Thank you so much. I am so honored to have this opportunity, and I can't wait to work even more closely with the cloud native community than I have already. I mean, as you said, I've been involved for a long time. I actually just saw on my LinkedIn today that 2016 was when my conversation within the CNCF started. I was then working on the OpenTracing Project, which was the third project to join the foundation, and CNCF had started in 2015, so it was all very new. We were in conversations, and it was just such an exciting time, and that just kept getting bigger and bigger, and then with GitLab I served, I actually still serve, until the 31st, on the board. And now this, so I'm very, very excited. >> Yeah, well right. So you're a board member of the CNCF, but Priyanka, if you go back even further, we look at how did CNCF start. It was all around Kubernetes. Where did Kubernetes come from? It came from Google, and when I dug back far enough into your CV I found Google on there, too. So maybe just give us a little bit of your career arc, and what you're involved with for people that don't know you from all these communities and events. >> Sure, absolutely. So my career started at Google in Mountain View, and I was on the business side of things. I worked with AdSense products, and around that same time I had a bit of the entrepreneurial bite, so the bug bit me, and I first joined a startup that was acquired by GoDaddy later on, and then I went off on my own. That was a very interesting time for me, because that was when I truly learned about the power of opensource. One of the products that me and my co-founder were building was an opensource time tracker, and I just saw the momentum on these communities, and that's when the dev tools love started. And then I got involved with Heavybit Industries, which is an accelerator for dev tools. There I met so many companies that were either in the cloud space, or just general other kinds of dev tools, advised a few, ended up joining LightStep, where the founders, them and a few community members were the creators of the OpenTracing standard. Got heavily, heavily involved in that project, jumped into cloud native with that, was a project contributor, organizer, educator, documentarian, all kinds of things, right, for two-plus years, and then GitLab with the board membership, and that's how I saw, actually, the governance side. Until then it had all been the community, the education, that aspect, and then I understood how Chris and Dan had built this amazing foundation that's done so much from the governance perspective. So it's been a long journey and it all feels that it's been coming towards in this awesome new direction. >> Well, yeah. Congratulations to you, and right, CNCF, in their press release I see Dan talked about you've been a speaker, you've been a governing board member, you participate in this, and you're going to help with that next phase, and you teased out a little bit, there's a lot of constituencies in the CNCF. There's a large user participation. We always love talking at KubeCon about the people not only just using the technology, but contributing back, the role of opensource, the large vendor ecosystem, a lot there. So give us your thought as to kind of where the CNCF is today, and where it needs to continue and go in the future. >> Absolutely. So in my opinion the CNCF is a breakout organization. I mean, we're approaching 600 members, of which 142 are end users. So with that number the CNCF is actually the largest, has the largest end user community of all opensource foundations. So tremendous progress has been made, especially from those days back in 2016 when we were the third project being considered. So leaps and bounds, so impressive. And I think... If you think about what's the end user storyline right now, so the CNCF did a survey last year, and so 84% of the people surveyed were using containers in production, and 78% were using Kubernetes in production. Amazing numbers, especially since both are up by about 15, 20% year over year. So this move towards devops, towards cloud native, towards Kubernetes is happening and happening really strong. The project has truly established itself. Kubernetes has won, in my opinion, and that's really good. I think now when it comes to the second wave, it is my perspective that the end user communities and the... Just the momentum that we have right now, we need to build and grow it. We need deeper developer engagement, because if you think about it, there's not just one graduated project in CNCF. There are 10. So Kubernetes being one of them, but there's Prometheus, there's Envoy, Jaeger, et cetera, et cetera. So we have amazing technologies that are all gaining adoption. Being graduated means that they have fast security audits, they have diverse contributors, they have safe, good governance, so as an end user you can feel very secure adopting them, and so we have so much to do to expand on the knowledge of those projects. We have so much to make software just better every day, so that's my one vector in my opinion. The second vector, I would say it has been more opportunistic. As you know, we are all living in a very unprecedented time with a global pandemic. Many of us are sheltering in place. Many are... Generally, life is changed. You are in media. You know this much better than me, I'm sure, that the number of, the amount of digital consumption has just skyrocketed. People are reading that many more articles. I'm watching that many more memes and jokes online, right? And what that means is that more and more companies are reaching that crazy web scale that started this whole cloud native and devops space in the first time, first place with Google and Netflix being D-to-C companies just building out what eventually became cloud native, SRE, that kind of stuff. So in general, online consumption's higher, so more and more companies need to be cloud native to support that kind of traffic. Secondly, even for folks that are not creating content, just a lot of the workflows have to move online. More people will do online banking. More people will do ecommerce. It's just the shift is happening, and for that we, as the foundation, need to be ready to support the end users with education, enablement, certifications, training programs, just to get them across that chasm into a new, even more online-focused reality. >> Yeah, and I say, Priyanka, that tees up one of the ways that most people are familiar with the CNCF is through the event. So KubeCon and CloudNativeCon, really the signature event. Tremendous growth over the last few years. You actually had involvement in a virtual event, the Cloud Native Summit recently. For KubeCon-- >> Yes. >> The European show is announced virtual. We know that there's still some uncertainty when it comes to the North America show. Supposed to be in my backyard here in Boston, so we'd love for it to happen. If it happens-- >> Of course. >> If not, we'll be there virtually or not. Give us a little bit your experience with the Cloud Native Summit, and what's your thinking today? We understand, as you said, a lot of uncertainty as to what goes on. Absolutely, even when physical events come back in the future, we expect this hybrid model to be with us for a long time. >> I definitely hear that. Completely agree that everything is uncertain and things have changed very rapidly for our world, particularly when it comes to events. We're lucky at the CNCF to be working with the LF Events team, which is just best in class, and we are working very hard every day, them, doing a lot of the lion's share of the work of building the best experience we can for KubeCon, CloudNativeCon EU, which, as you said, went virtual. I'm really looking forward to it because what I learned from the Cloud Native Summit Online, which was the event you mentioned that I had hosted in April, is that people are hungry to just engage, to see each other, to communicate however they can in this current time. Today I don't think the technology's at a point where physical events can be overshadowed by virtual, so there's still something very special about seeing someone face-to-face, having a coffee, and having that banter, conversations. But at the same time there are some benefits to online. So as an example, with the Cloud Native Summit, really, it was just me and a few community folks who were sad we didn't get to go to Amsterdam, so we're like, "Let's just get together in a group, "have some fun, talk to some maintainers," that kind of thing. I expected a few hundred, max. Thousands of people showed up, and that was just mind blowing because I was like, "Wait, what?" (chuckling) But it was so awesome because not only were there a lot of people, there were people from just about every part of the globe. So normally you have US, Europe, that kind of focus, and there's the Asia-PAC events that cater to that, but here in that one event where, by the way, we were talking to each other in realtime, there were folks from Asia-PAC, there were folks from Americas, EU, also the African continent, so geo meant nothing anymore. And that was very awesome. People from these different parts of the world were talking, engaging, learning, all at the same time, and I think with over 20,000 people expected at KubeCon EU, with it being virtual, we'll see something similar, and I think that's a big opportunity for us going forward. >> Yeah, no, absolutely. There are some new opportunities, some new challenges. I think back to way back in January I got to attend the GitLab event, and you look at GitLab, a fully remote company, but talking about the benefits of still getting together and doing things online. You think of the developer communities, they're used to working remote and working across different timezones, but there is that need to be able to get together and collaborate, and so we've got some opportunities, we've got some challenges when remote, so I guess, yeah, Priyanka. Give me the final word, things you want to look forward to, things we should be expecting from you and the CNCF team going forward. I guess I'll mention for our audience, I guess, Dan Kohn staying part of Linux Foundation, doing some healthcare things, will still stay a little involved, and Chris Aniszczyk, who's the CTO, still the CTO. I just saw him. Did a great panel for DockerCon with Kelsey Hightower, Michelle Noorali, and Sean Connelly, and all people we know that-- >> Right. >> Often are speaking at KubeCon, too. So many of the faces staying the same. I'm not expecting a big change, but what should we expect going forward? >> That's absolutely correct, Stu. No big changes. My first big priority as I join is, I mean, as you know, coming with the community background, with all this work that we've put into education and learning from each other, my number one goal is going to be to listen and learn in a very diverse set of personas that are part of this whole community. I mean, there's the board, there is the technical oversight committee, there is the project maintainers, there's the contributors, there are the end users, potential developers who could be contributors. There's just so many different types of people all united in our interest and desire to learn more about cloud native. So my number one priority is going to listen and learn, and as I get more and more up to speed I'm very lucky that Chris Aniszczyk, who has built this with Dan, is staying on and is going to be advising me, guiding me, and working with me. Dan as well is actually going to be around to help advise me and also work on some key initiatives, in addition to his big, new thing with public health and the Linux Foundation. You never expect anything average with Dan, so it's going to be amazing. He's done so much for this foundation and brought it to this point, which in my mind, I mean, it's stupendous the amount of work that's happened. It's so cool. So I'm really looking forward to building on this amazing foundation created by Dan and Chris under Jim. I think that what they have done by not only providing a neutral IP zone where people can contribute and use projects safely, they've also created an ecosystem where there is events, there is educational activity, projects can get documentation support, VR support. It's a very holistic view, and that's something, in my opinion, new, at least in the way it's done. So I just want to build upon that, and I think the end user communities will keep growing, will keep educating, will keep working together, and this is a team effort that we are all in together. >> Well, Priyanka, congratulations again. We know your community background and strong community at the CNCF. Looking forward to seeing that both in the virtual events in the near term and back when we have physical events again in the future, so thanks so much for joining us. >> Thank you for having me. >> All right. Be sure to check out thecube.net. You'll see all the previous events we've done with the CNCF, as well as, as mentioned, we will be helping keep cloud native connected at KubeCon, CloudNativeCon Europe, the virtual event in August, as well as the North American event later in the year. I'm Stu Miniman, and thank you for watching theCUBE. (smooth music)

>>Live from San Diego, California. It's the cube covering to clock in cloud native con brought to you by red hat, the cloud native computing foundation and its ecosystem. >>Welcome back to the queue bumps to men. And my cohost is John Troyer and you're watching the cube here at CubeCon, cloud-native con 2019 in beautiful and sunny San Diego today. Happy to welcome to the program a first time guest, Tom Willkie, who's vice president of product ECRO funnel labs. Thank you. Thank you so much for joining us. All right, so it's on your tee shirt. We've been hearing, uh, customers talking about it and the like, but, uh, why don't you introduce the company to our audience in a, where you fit in this broad landscape, uh, here at the CNCF show. Thank you. Yes. So Grafana is probably the most popular open source project for dashboarding and visualization. Um, started off focused on time series data on metrics, um, but really recently has branched out into log analysis and tracing and, and all, all of the kinds of aspects of your observability stack. >>Alright, so really big, uh, you know, broad topic there. Uh, we know many of the companies in that space. Uh, there's been many acquisitions, uh, you know, uh, recently in this, um, where, where do you fit in your system? I saw like databases, like a big focus, uh, when, when I, when I look at the company website, uh, bring us inside a little bit. Yeah. As a product to the offering. The customers most, um, >> most, most vendors in this space will sell you a monitoring product that includes the time series database normally includes visualization and some agent as well where pharma Lampson Griffon open source projects, very focused on the visualization aspects. So we are data source agnostic and we have back ends for more than 60 different data sources. So if you want to bring together data from let's say Datadog and combine it with some open source monitoring from, you can do that with. >>Uh, you can, you can have the dashboards and the individual panels in that dashboard combined data from multiple different data sources and we're pretty much the only game in town for that. You can, you can think of it like Tableau allows you to plug into a whole bunch of different databases for your BI with that. But for monitoring and for metrics. Well, so Tom, maybe let's, before we get into the exit products and more of the service and the, and the conference here, let's talk a little well on the front page of your website, you use the Oh 11, why word? So we've said where it's like monitoring here we use words like management, we use words like ops. Observability is a hot topic in the space and for people in a space that has some nuances. And so can you just maybe let the viewers and us know a little bit about what, how the space is looking at this and how you all feel about observability and what everybody here who's running some cloud native apps needs to actually function in production. >>Yeah. So I think, um, you can't talk about observability without either being pro or, or for, um, uh, the three pillars, right? So people talk about metrics, logs and traces. Um, I think what people miss here is that it's more about the experience for the developer, you know, Gruffalo and what we're trying to achieve is all about giving engineers and developers the tools they need to understand what their applications and their infrastructure doing, right? So we're not actually particularly picky about which pillars you use and which products you use to implement those pillars. But what we want to do is provide you with an experience that allows you to bring it all into a single, a single user interface and allows you to seamlessly move between the different sources of data and, and hopefully, uh, combine them in your analysis and in your root cause of any particular incident. >>And that for me is what observability means. It's about helping you understand the behavior of your application in particular. I mean, I'm, I'm a, I'm a software engineer by trade. I'm still on call. I still get paged at 3:00 AM occasionally. And, and having the right tools at 3:00 AM to allow me to as quickly as possible, figure out what happened and then dive into a fix. That's what we're about over funnel labs. All right. So Tom, one of the things we always need to understand and show here. There's the project and there's the company. Yep. Help us just kind of understand, you know, definitely a difference. The products, the, the, the mission of the company and how that fits with the project. So the Gruffalo project predates the company and it was started by taco. Um, he, you know, he saw a spot for like needing a much better kind of graphical editing of dashboards and making, making the kind of metrics way more accessible to your average human. >>Um, the final lab started really to focus on the it and, uh, monitoring observability use cases of profanity and, but the project itself is much broader than that. We see a lot of use cases in industrial, in IOT, even in BI as well. But Grafana labs is a company we're focused on the monitoring side of things. We're focused on the observability. So we also offer, we mean, like most companies, we have an enterprise version of. It has a few data sources for commercial vendors. So if you want to, you want to get your data dog or your Splunk into Grafana, then there's a commercial auction for that. But we also offer a hosted observability platform called Grafana clown. And this is where we take the best open source projects, the best tools that we think you need as an engineer to understand your applications and we host them for you and we operate them for you. >>We scale them, we upgrade them, we fix bugs, we sacrifice the clouds predominantly are hosted from atheists, our hosted graphite and our hosted Loki, our log aggregation system, um, all combined and brought together with uh, with the Gruffalo frontend. So yeah, like two products, a bunch of open source projects for final labs, employees, four of the promethium maintainers. And I'm one of the promethium maintainers. Um, we am employee graphite maintainers. Obviously a lot of Gryffindor maintainers, but also Loki. Um, I'm trying to think, like there's just so many open source projects. We, uh, we get involved with that. Really it's about synthesizing, uh, an observability platform out of those. And that's what we offer as a product. So you recently had an announcement that Loki is now GA. can you talk just a little bit about Loki and aggregation and logs and what Loki does? >>Yeah, I'd love to. Yeah. Um, a year ago in Seattle actually we announced the Loki project. Um, it was super early. I mean I just basically been finishing the code on the plane over and we announced it and no one I think could have predicted the response we had. Um, everyone was so keen and so hungry for alternative to traditional log aggregation systems. Um, so it's been a year and we've learned a hell of a lot. We've had so much feedback from the community. We've built a whole team internally around, around Loki. We now offer a hosted version of it and we've been running it in production now for over a year, um, doing some really great scale on it and we think it's ready for other people to do the same. One of the things we hear, especially at shows like this is I really, I really, you know, developers and the grassroots adopters come to us, say, we really love Loki. >>We really love what you're doing with it. Um, but my boss won't let me use it until it goes to be one. And so really yesterday we announced it's Don V. one, we think it's stable. We're not going to change any of the APS on you. We, uh, we would love you to use it and uh, and put it into production. All right. Uh, we'd like to hear a little bit more about the business side of things. So, um, I believe there was some news around funding, uh, uh, you know, how many people you have, how many, you know, can you parse for us, you know, how many customers have the projects versus how many customers have, uh, you know, the company's products. Well, we don't, we don't call them customers of the projects that users, yes, yes, we, uh, but I'm from a company where we have hundreds of customers. >>Um, I don't believe we make our revenue figures public and, uh, so I'm probably not going to dive into them, but I know, I know the CEO stands up at our, our yearly conference and, and discloses, you know, what our revenue the last year was. So I'll refer you to that. Um, the funding announcement, that was about a month ago. We, uh, we raised a great round from Lightspeed, um, 24 million I believe. Um, and we're gonna use that to really invest in the community, really invest in our projects and, and build a bit more of a commercial function. Um, the company is now about 110 people. I think, um, it's growing so quickly. I joined 18 months ago and we were 30 people and so we've almost quadrupled in size in, in the last year and a half. Um, so keeping up is quite a challenge. Uh, the two projects, uh, products I've already touched on a few hundred customers and I think we're, you know, we're really happy with the growth. >>We've been, uh, we've never had any institutional funding before this. The company is about five years old. So we've been growing based on organic revenue and, and, and, and, you know, barely profitable, uh, but reinvesting that into the company and, and it's, yeah, it's going really well. We're also one of the, I mean it's not that unique I guess, but we're remote first. We have a more than 50% of our employees work from home. I work from my basement in London. We have a few tiny like offices, one in Stockholm and one in New York, but, but we're really keen to hire the best people wherever they are. Um, and we invest a lot in travel. Uh, we invest a lot in, um, the, the right tools and getting the whole company together to really make that work. Actually a really fun place to work. What time? >>We're S we're still in the business here and I don't know how much time you've spent at the booth this year, but I don't, can you compare, I mean, we've been talking about the growth of this community and the growth of this conference. Can you compare say this year to last year, the, the people coming up, their maturity, the maturity of their production, et cetera. Are they, are they ready to buy? Are they still kicking? Are they still wondering what this Cooper Cooper need easy things is, you know, where, where is everybody this year and how does that, how has it changed? Yeah, and that's a good question where we're definitely seeing people with a lot more sophisticated questions. The, the, the conversations we're having at the booth are a lot longer than they've been in previous years. The um, you know, in particular people now know what key is. We only announced it a year ago and gonna have a lot of people asking us very detailed questions about what scale they can run it at. >>Um, otherwise, yeah, I think there is starting to be a bit more commercial intent at the conference, some few more buying decisions being made here. It's still predominantly a community oriented conference and I think the, the, I don't want that to go away. Like, that's one of the things that makes it attractive to me. And, and I bring my whole team here and that's one of the things that makes it attractive to them. But there is a little bit more, I'm a little more sales activity going on for sure. Any updates to the, to the tracing and monitoring observability stories of the projects here at CNCF this year since you as you're part of the promethium project? >> Yes. So we actually, we had the promethium conference in Munich two weeks ago and after each committee conference, the maintainers like to get together and kind of plan out the next six months of the project. >>So we started to talk about um, adding support for things like exemplars into Prometheus's. This is where each histogram bucket, you can associate an example trace that goes, that contributed towards that, that history and that latency. And then you can build nice user interfaces around that. So you can very quickly move from a latency graph to example traces that caused that. Um, so that's one of the things we're looking to do in Prometheus. And of course Jaeger graduated just a week ago. I think. Um, we're big users of Jaeger internally at for final amps. And actually on our booth right now, uh, we're showing a demo of how we're integrating, um, visualization of distributed tracing, integral foreigner. So you can, you know, using the same approach we do with metrics where we support multiple backends, we're going to support Yeager, we're going to support Zipkin, we're going to support as many open source tracing projects as we can with the Grafana UI experience and being able to seamlessly kind of switch between different data sources, metrics all the way to logs all the way to traces within one UI. >>And without ever having to copy and paste your query and make mistakes and kind of translate it in your head. Right. >> Tom, give us a little bit, look forward. Uh, you know, a lot of activities as the thing's going to, you know, graduating and pulling things together. So what should your users be looking for kind of over the next six to 12 months? >> That's a great question. Yeah, I think we do a yearly release cycle for foreigners. So the next one we're, we're aiming towards is for seven, like for me to find a seven's going to be all about tracing. So I really want to see the demo we're doing. I want to see that turned into like production ready code support for multiple different data sources, support for things like exemplars, which we're not showing yet. Um, I want to see all of that done in Grafana in the next year and we've also massively been flushing out the logging story. >>I'm with Loki, we've been adding support for uh, extracting metrics from the logs and I really think that's kind of where we're going to drive Loki forward in the future. And that really helps with systems that aren't really exposing metrics like legacy systems where the only kind of output you get from them is the logs. Um, beyond that. Yeah, I mean the welds are kind of oyster. I think I'm really keen to see the development of open telemetry and um, we've just starting to get involved to that project ourselves. Um, I'm really interested to kind of talk to people about what they need out of a tracing system. We, we see people asking for a hosted tracing systems. Um, but, but IMO is very much like pick the best open source ones. I don't think that's, that's emerged yet. I don't think people know which is the best one yet. >>So we're going to get involved in all of them. See which one's a C, which one's a community kind of coalesces around and maybe start offering a hosted version of that. >> You know, our final thing is, uh, you know, what advice do you have for users? Obviously, you know, you like the open source thing, but you know, they're hearing about observability everywhere there are, you know, the, the whole APM market is moving this direction. There's acquisitions as we talked about earlier. Um, there's so many moving pieces and a lot of different viewpoints out there. So just, you know, from a user, how do you know, how will things ma, what makes their lives easier and what advice would you give them? Yeah, no, definitely. I think a lot of vendors will tell you like to pick a, pick a vendor who's going to help you with this journey. >>Like I would say like, pick a vendor you trust who can help you make those decisions. Like find someone impartial who's gonna not make, not try and persuade you to buy their product. So we would, uh, you know, I would encourage you to try things out to dog food and to really like invest in experimentation. There's a lot going on in, uh, in, in the observability world and in the cloud native world. And you've got to, you've got to try it and see what fits. Like we embrace this, uh, composability of the, uh, of the observatory of, of the observability ecosystem. So like, try and find which, which choices work best for you. Like I, uh, whenever, whenever I talk to him, you still have to lick all the cupcakes in 2019. I think. I mean, I would, it depends on your level of kind of maturity, right? >>And sophistication. Like, I think if, uh, if, if this is really important to you, you should go down that approach. You should try them all. If this is not one of your core competencies that may be going with a vendor that helps you is a better approach. But, but I'm, I come from the open source world and, uh, you know, I like to see the, um, the whole ecosystem and all the different players and all the different, new and exciting ways to solve these problems. Um, so I'm, I'm always going to encourage people to have a play and try things out. All right, Tom, final word, Loki. Explain to us, uh, you know, when you're coming up with it, how you ended, uh, are you the God of mischief? Well, so the official line is the Loki is the, um, is the North mythology equivalent of Prometheus's, uh, in Greek mythology and, and lochia logging project is, is, is Prometheus's inspired logging. So we've tried to take the operational model from, from atheists, the query language from, from atheists and, and the kind of a cost efficiency from, from atheists and apply it to logs. Um, but I will admit to being a big fan of the Marvel movies. All right, Tom Willkie. Thank you so much for sharing the updates on, on the labs. Uh, we definitely look forward to hearing updates from you and thank you. All right, for, for John Troyer, I'm Stu Madmen back with more coverage here from San Diego. Thank you for watching. Thank you for watching the cube.

>> Live from Barcelona, Spain it's theCUBE, covering KubeCon, CloudNativeCon, Europe 2019. Brought to you by Red Hat, the Cloud Native Computing Foundation and Ecosystem Partners. >> Welcome back. This is theCUBE's coverage of KubeCon, CloudNativeCon 2019. I'm Stu Miniman, my co-host for two days wall-to-wall coverage is Corey Quinn. Happy to welcome back to the program first Ben Sigelman, who is the co-founder and CEO of LightStep. And welcome to the program a first time Morgan McLean, who's a product manager at Google Cloud Platform. Gentlemen, thanks so much for joining us. >> Thanks for having us. >> Yeah. >> All right so, this was a last minute ad for us because you guys had some interesting news in the keynote. I think the feedback everybody's heard is there's too many projects and everything's overlapping, and how do I make a decision, but interesting piece is OpenCensus, which Morgan was doing, and OpenTracing, which Ben and LightStep were doing are now moving together for OpenTelemetry if I got it right. >> Yup. >> So, is it just everybody's holding hands and singing Kumbaya around the Kubernetes campfire, or is there something more to this? >> Well I mean, it started when the CNCF locked us in a room and told us there were too many projects. (Stu and Ben laughing) Really wouldn't let us leave. No, to be fair they did actually take us to a room and really start the ball rolling, but conversations have picked up for the last few months and personally I'm just really excited that it's gone so well. Initially if you told me six or nine months ago that this would happen, I would've been, given just the way the projects were going, both were growing very quickly, I would've been a little skeptical. But seriously, this merger's gone beyond my wildest dreams. It's awesome, both to unite the communities, it's awesome to unite the projects together. >> What has the response been from the communities on this merger? >> Very positive. >> Yeah. >> Very positive. I mean OpenTracing and OpenCensus are both projects with healthy user bases that are growing quickly and all that, but the reason people adopt them is to future-proof their own software. Because they want to adopt something that's going to be here to stay. And by having these two things out in the world that are both successful, and were overlapping in terms of their goals, I think the presence of two projects was actually really problematic for people. So, the fact that they're merging is net positive, absolutely for the end user community, also for the vendor community, it's a similar, it's almost exactly the same parallel thought process. When we met, the CNCF did broker an in-person meeting where they gave us some space and we all got together and, I don't know how many people were there, like 20 or 30 people in that room. >> They did let us leave the room though, yesterday, yeah that was nice. >> They did let us leave the room, that's true. We were not locked in there, (Morgan laughing) but they asked us in the beginning, essentially they asked everyone to state what their goals were. And almost all of us really had the same goal, which is just to try and make it easy for end users to adopt a telemetry project that they can stick with for the long haul. And so when you think of it in that respect, the merger seems completely obvious. It is true that it doesn't happen very often, and we could speculate about why that is. But I think in this case it was enabled by the fact that we had pretty good social relationships with OpenCensus people. I think Twitter tends to amplify negativity in the world in general, as I'm sure people, not a controversial statement. >> News alert, wait, absolutely the negatives are, it's something in the algorithm I think. >> Yeah, yeah. >> Maybe they should fix that. >> Yeah, yeah (laughs) exactly. And it was funny, there was a lot of perceived animosity between OpenTracing and OpenCensus a year ago, nine months ago, but when you actually talk to the principals in the projects and even just the general purpose developers who are doing a huge amount of work for both projects, that wasn't a sentiment that was widely held or widely felt I think. So, it has been a very kind of happy, it's a huge relief frankly, this whole thing has been a huge relief for all of us I think. >> Yeah it feels like the general ask has always been that, for tracing that doesn't suck. And that tends to be a bit of a tall order. The way that they have seemed to have responded to it is a credit to the maturity of the community. And I think it also speaks to a growing realization that no one wants to have a monoculture of just one option, any color you want so long as it's black. (Ben laughing) Versus there's 500 different things you can pick that all stand in that same spot, and at that point analysis paralysis kicks in. So this feels like it's a net positive for, absolutely everyone involved. >> Definitely. Yeah, one of the anecdotes that Ben and I have shared throughout a lot of these interviews is there were a lot of projects that wanted to include distributed tracing in them. So various web frameworks, I think, was it Hadoop or HBase was-- >> HBase and HDFS were jointly deciding what to do about instrumentation. >> Yeah, and so they would publish an issue on GitHub and someone from OpenTracing would respond saying hey, OpenTracing does this. And they'd be like oh, that's interesting, we can go build an implementation file and issue, someone from OpenCensus would respond and say, no wait, you should use OpenCensus. And with these being very similar yet incompatible APIs, these groups like HBase would sit it and be like, this isn't mature enough, I don't want to deal with this, I've got more important things to focus on right now. And rather than even picking one and ignoring the other, they just ignored tracing, right? With things moving to microservices with Kubernetes being so popular, I mean just look at this conference. Distributed tracing is no longer this kind of nice to have when you're a big company, you need it to understand how your app works and understand the cause of an outage, the cause of a problem. And when you had organizations like this that were looking at tracing instrumentation saying this is a bit of joke with two competing projects, no one was being served well. >> All right, so you talked about there were incompatible APIs, so how do we get from where we were to where we're going? >> So I can talk about that a little bit. The APIs are conceptually incredibly similar. And the part of the criteria for any new language, for OpenTelemetry, are that we are able to build a software bridge to both OpenTracing and OpenCensus that will translate existing instrumentation alongside OpenTelemetry instrumentation, and omit the correct data at the end. And we've built that out in Java already and then starting working a few other languages. It's not a tremendously difficult thing to do if that's your goal. I've worked on this stuff, I started working on Dapper in 2004, so it's been 15 years that I've been working in this space, and I have a lot of regrets about what we did to OpenTracing. And I had this unbelievably tempting thing to start Greenfield like, let's do it right this time, and I'm suppressing every last impulse to do that. And the only goal for this project technically is backwards compatibility. >> Yeah. >> 100% backwards compatibility. There's the famous XKCD comic where you have 14 standards and someone says, we need to create a new standard that will unify across all 14 standards, and now you have 15 standards. So, we don't want to follow that pattern. And by having the leadership from OpenTracing and OpenCensus involved wholesale in this new effort, as well as having these compatibility bridges, we can avoid the fate of IPv6, of Python 3 and things like that. Where the new thing is very appealing but it's so far from the old thing that you literally can't get there incrementally. So that's, our entire design constraint is make sure that backwards compatibility works, get to one project and then we can think about the grand unifying theory of a provability-- >> Ben you are ruining the best thing about standards is that there is so many of them to choose from. (everyone laughing) >> There's still plenty more growing in other areas (laughs) just in this particular space it's smaller. >> One could argue that your approach is nonstandard in its own right. (Ben laughing) And in my own experiments with distributed tracing it seems like step one is, first you have to go back and instrument everything you've built. And step two, hey come back here, because that's a lot of work. The idea of an organization going back and reinstrumenting everything they've already instrumented the first time. >> It's unlikely. >> Unless they build things very modularly and very portably to do exactly that, it's a bit of a heavy lift. >> I agree, yeah, yeah. >> So going forward, are people who have deployed one or the other of your projects going to have to go back and do a reinstrumentation, or will they unify and continue to work as they are? >> So, I would pause at the, I don't know, I would be making up the statistic, so I shouldn't. But let's say a vast majority, I'm thinking like 95, 98% of instrumentation is actually embedded in frameworks and libraries that people depend on. So you need to get Dropwizard, and Spring, and Django, and Flask, and Kafka, things like that need to be instrumented. The application code, the instrumentation, that burden is a bit lower. We announced something called SpecialAgent at LightStep last week, separate to all of this. It's kind of a funny combination, a typical APM agent will interpose on individual function calls, which is a very complicated and heavyweight thing. This doesn't do any of that, but it takes, it basically surveys what you have in your process, it looks for OpenTracing, and in the future OpenTelemetry instrumentation that matches that, and then installs it for you. So you don't have to do any manual work, just basically gluing tab A into slot B or whatever, you don't have to do any of that stuff which is what most OpenTracing instrumentation actually looks like these days. And you can get off the ground without doing any code modifications. So, I think that direction, which is totally portable and vendor neutral as well, as a layer on top of telemetry makes a ton of sense. There are also data translation efforts that are part of OpenCensus that are being ported in to OpenTelemetry that also serve to repurpose existing sources of correlated data. So, all these things are ways to take existing software and get it into the new world without requiring any code changes or redeploys. >> The long-term goal of this has always been that because web framework and client library providers will go and build the instrumentation into those, that when you're writing your own service that you're deploying in Kubernetes or somewhere else, that by linking one of the OpenTelemetry implementations that you get all of that tracing and context propagation, everything out of the box. You as a sort of individual developer are only using the APIs to define custom metrics, custom spans, things that are specific to your business. >> So Ben, you didn't name LightStep the same as your project. But that being said, a major piece of your business is going through a change here, what does this mean for LightStep? >> That's actually not the way I see it for what it's worth. LightStep as a product, since you're giving me an opportunity to talk about it, (laughs) foolish move on your part. No, I'm just kidding. But LightStep as a product is totally omnivorous, we don't really care where the data comes from. And translating any source of data that has a correlation ID and a timestamp is a pretty trivial exercise for us. So we do support OpenTracing, we also support OpenCensus for what it's worth. We'll support OpenTelemetry, we support a bunch of weird in-house things people have already built. We don't care about that at all. The reason that we're pursuing OpenTelemetry is two-fold, one is that we do want to see high quality data coming out of projects. We said at the keynote this morning, but observability literally cannot be better than your telemetry. If your telemetry sucks, your observability will also suck. It's just definitionally true, if you go back to the definition of observability from the '60s. And so we want high quality telemetry so our product can be awesome. Also, just as an individual, I'm a nerd about this stuff and I just like it. I mean a lot of my motivation for working on this is that I personally find it gratifying. It's not really a commercial thing, I just like it. >> Do you find that, as you start talking about this more and more with companies that are becoming cloud-native rapidly, either through digital transformation or from springing fully formed from the forehead of some God, however these born in the cloud companies tend to be, that they intuitively are starting to grasp the value of tracing? Or does this wind up being a much heavier lift as you start, showing them the golden path as it were? >> It's definitely grown like I-- >> Well I think the value of tracing, you see that after you see the negative value of a really catastrophic outage. >> Yes. >> I mean I was just talking to a bank, I won't name the bank but a bank at this conference, and they were talking about their own adoption of tracing, which was pretty slow, until they had a really bad outage where they couldn't transact for an hour and they didn't know which of the 200 services was responsible for the issue. And that really put some muscle behind their tracing initiative. So, typically it's inspired by an incident like that, and then, it's a bit reactive. Sometimes it's not but either way you end up in that place eventually. >> I'm a strong proponent of distributed tracing and I feel very seen by your last answer. (Ben laughing) >> But it's definitely made a big impact. If you came to conferences like this two years ago you'd have Adrian, or Yuri or someone doing a talk on distributed tracing. And they would always start by asking the 100 to 200 person audience, who here knows what distributed tracing is? And like five people would raise their hand and everyone else would be like no, that's why I'm here at the talk, I want to find out about it. And you go to ones now, or even last year, and now they have 400 people at the talk and you ask, who knows what distributed tracing is? And last year over half the people would raise their hand, now it's going to be even higher. And I think just beyond even anecdotes, clearly businesses are finding the value because they're implementing it. And you can see that through the number of companies that have an interest in OpenTracing, OpenTelemetry, OpenCensus. You can see that in the growth of startups in this space, LightStep and others. >> The other thing I like about OpenTelemetry as a name, it's a bit of a mouthful but that's, it's important for people to understand the distinction between telemetry and tracing data and actual solutions. I mean OpenTelemetry stops when the correct data is being omitted. And then what you do with that data is your own business. And I also think that people are realizing that tracing is more than just visualizing a single distributed trace. >> Yeah. >> The traces have an enormous amount of information in there about resource usage, security patterns, access patterns, large-scale performance patterns that are embedded in thousands of traces, that sort of data is making its way into products as well. And I really like that OpenTelemetry has clearly delineated that it stops with the telemetry. OpenTracing was confusing for people, where they'd want tracing and they'd adopt OpenTracing, and then be like, where's my UI? And it's like well no, it's not that kind of project. With OpenTelemetry I think we've been very clear, this is about getting >> The name is more clear yeah. >> very high quality data in a portable way with minimal effort. And then you can use that in any number of ways, and I like that distinction, I think it's important. >> Okay so, how do we make sure that the combination of these two doesn't just get watered-down to the least common denominator, or that Ben just doesn't get upset and say, forget it, I'm going to start from scratch and do it right this time? (Ben laughing) >> I'm not sure I see either of those two happening. To your comment about the least common denominator, we're starting from what I was just commenting about like two years ago, from very little prior art. Like yeah, you had projects like Zipkin, and Zipkin had its own instrumentation, but it was just for tracing, it was just for Zipkin. And you had Jaeger with its own. And so, I think we're so far away, in a few years the least common denominator will be dramatically better than what we have today. (laughs) And so at this stage, I'm not even remotely worried about that. And secondly to some vendor, I know, because Ben had just exampled this, >> Some vendor, some vendor. >> that's probably not, probably not the best one. But for vendor interference in this projects, I really don't see it. Both because of what we talked about earlier where the vendors right now want more telemetry. I meet with them, Ben meets with 'em, we all meet with 'em all the time, we work with them. And the biggest challenge we have is just the data we get is bad, right? Either we don't support certain platforms, we'll get traces that dead end at certain places, we don't get metrics with the same name for certain types of telemetry. And so this project is going to fix that and it's going to solve this problem for a lot of vendors who have this, frankly, a really strong economic incentive to play ball, and to contribute to it. >> Do you see that this, I guess merging of the two projects, is offering an opportunity to either of you to fix some, or revisit if not fix, some of the mistakes, as they were, of the past? I know every time I build something I look back and it was frankly terrible because that's the kind of developer I am. But are you seeing this, as someone who's probably, presumably much better at developing than I've ever been, as the opportunity to unwind some of the decisions you made earlier on, out of either ignorance or it didn't work out as well as you hoped? >> There are a couple of things about each project that we see an opportunity to correct here without doing any damage to the compatibility story. For OpenTracing it was just a bit too narrow. I mean I would talk a lot about how we want to describe the software, not the tracing system. But we kind of made a mistake in that we called it OpenTracing. Really people want, if a request comes in, they want to describe that request and then have it go to their tracing system, but also to their metric system, and to their logging stack, and to anywhere else, their security system. You should only have to instrument that once. So, OpenTracing was a bit too narrow. OpenCensus, we've talked about this a lot, built a really high quality reference implementation into the product, if OpenCensus, the product I mean. And that coupling created problems for vendors to adopt and it was a bit thick for some end users as well. So we are still keeping the reference implementation, but it's now cleanly decoupled. >> Yeah. >> So we have loose coupling, a la OpenTracing, but wider scope a la OpenCensus. And in that aspect, I think philosophically, this OpenTelemetry effort has taken the best of both worlds from these two projects that it started with. >> All right well, Ben and Morgan thank you so much for sharing. Best of luck and let us know if CNCF needs to pull you guys in a room a little bit more to help work through any of the issues. (Ben laughing) But thanks again for joining us. >> Thank you so much. >> Thanks for having us, it's been a pleasure. >> Yeah. >> All right for Corey Quinn, I'm Stu Miniman we'll be back to wrap up our day one of two days live coverage here from KubeCon, CloudNativeCon 2019, Barcelona, Spain. Thanks for watching theCUBE. (soft instrumental music)

>> Live from Seattle, Washington, it's theCUBE, covering KubeCon, and CloudNativeCon North America 2018. Brought to you by Red Hat, the CloudNative Computing Foundation, and the Antigo System Partners. >> Hey, welcome back everyone live here in Seattle for the theCUBE's coverage of KubeCon and CloundNativeCon 2018. I'm John Furrier, theCUBE with Stu Miniman, breaking down all the action. Three days of coverage, we're in day two. A lot of action at Open-source. 8,000 attendees, up from 4,000 North America, they were in China, they were all over Europe. The community's growing in a massive way. We had two great guests from Red Hat, all making it happen, part of the community. We've got Diane Mueller, whose theCUBE alumni director of community development, many times on theCUBE, good to see you, and Rob Szumski, principal product manager, both at Red Hat. Guys, thanks for coming on. Great to see you again. >> Yeah, glad to be here. - Great to be here. >> So the world's changing a lot, and there was some news recently around Red Hat. I can't remember what it was. Recently, something big news, but you guys have been big players in Open-source for years. We always cover it, we always wax on about the origination of it and how the evolution, but the CloudNative piece has gotten so real, and your role in it particularly, we've had many conversations, going maybe back to the OpenStack days of how OpenShift was developing, then the bet on Kubernetes that you made, Core OS acquisition, those two things I think, to me, at least from my perspective, really catalyzed a lot of things at the right time, right? So, from there, just a lot of things has just been happening really in a good way. Big tail wind for you guys, CloudNative app developers are using Open-source, CI/CD pipeline, and then also policy based up under the hood, completely big shift in moving the game down the field. So big congratulations first of all. But what's new? What's the update? >> The update is Operators. I think the next big thing that we are really focusing on, and that's a game changer for all the second day operations type things, and we'll make Rob talk about it in detail, is the rise of Kubernetes' Operators. It's not a scary thing, it's not like terminator day, or anything like that, but it is really the thing that helps us make the service catalogs, the Kubernetes marketplaces really accessible to all of the data bases as a service, and all of the other things, and takes out some of the complexity of delivering applications and database  as a Service to anybody running Kubernetes anywhere. >> Take a minute to explain Operator, real quick, and then we can jump into it, because I think this is a fundamental trend, that we're seeing. Developer trend is pretty obvious, it's been that word for awhile, CloudScale, ML, machine learning, and all the goodness around application development, but the Operator side of it has been an IT thing. But now you guys have a different, a new approach that's winning. What is it? What is Operator? >> Well, it's Kubernetes that has the approach, and I'll let you-- >> Yeah, so it's basically like the rise of containers was great, because you could take a single container and package an application and give to somebody, and know that they can run it successfully. And Operator does that for a distributed system in the exact same way. So you're using all the Kubernetes primitives, so you're not reinventing service discovery, and seeker management, and all that. And you can give somebody an entire Kafka stack, or a machine learning stack, or whatever it is, these very complex distributed systems, and have them run it without having to be an expert. They need to know Kafka at a high level, but not exactly all the underpinnings of it, because that's all baked in the software. >> And the benefit and the impact of the organization is what? >> And just to clarify, so this was added in, I believe Kubernetes is like 1.7, it's something that's in there, it's not something Red Hat specific- >> Yeah, it's like-- >> So you're extending Kubernetes so that you have a custom resource definition, which is an extensible mechanism for saying, hey, I've got a deployment or a staple set, but what if I want to have a new object called a MongoDB? That knows how to deploy, and manage, and upgrade MongoDB. So that's the extension mechanism that we're using. >> Yeah, so you got to think, there's certain applications that this is going to make, just a lot easier how I manage them, deploy them, things like that. Any specific examples you want to share as to-- >> All the clustered data bases. >> There's a lot of the application side in this model have been very excited about this. >> So its all the vendors and partners that want a hybrid Cloud story, just targeting Kubernetes, and we're using Kubernetes under the hood, and then everybody wants to run like a staple data base tier, whether that's Mongo and Couchbase, and Cassandra, whatever. And these are all distributed systems. >> Alright, so I want you to just perch, you said a hybrid Cloud. Explain that model, because there's just something in general discussion that is hybrid or multi means I'm running multiple places, I'm not necessarily stretching an application, but I have instances there, just want to make sure we're on the same page. >> So this would be more the compatibility that you're programming against when you're building an operator, is Kubernetes. It's not a Cloud offering, it's not OpenShift, so you're just targeting Kubernetes, and so you can run MongoDB on prem, in the Cloud, and have it function the exact same, by standing up one of these Operators. And then if that Operator has higher level constructs for how to do multi-cluster aware data rebalancing, you can take advantage of that too. >> And the Open-source status of this product is what? >> It's all Open-source, it's all in the github repos, there's a Google group for Operator framework, that anyone can come and participate in. We hold SIG meetings on the third Friday of every month, 9 a.m. Pacific Time, and it's a completely Open-source project. There's a whole framework around it, so there's the Operator SDK, the Operator Lifecycle Management, and Operator metering, all the tooling there to help people build and manage these Operators, and it's all being built out there in the open with the community's support and feedback loops. >> What's the feedback? What's the top feedback you guys are getting right now? Seeing right now? >> I have to say, this is really, like I've been hanging out with you guys like for the past three, four months on this topic, trying to get my head around it and everything, and we came here and we had two sessions, an intro session and a deep dive session, intro yesterday, deep dive today. Today's deep dive, the room was about 250 people, and they're were people outside of it-- >> Security guards blocking people from coming in. >> Nobody could come in and it's like, it's insane. It's like, everybody needs these things, and everybody wants to figure out that, and when you ask people in the room whose building one, half the room raises their hands. It's just crazy. This thing crept up on us really, maybe not on Core OS, okay, it crept up on me very quickly, and it's very rapid adoption. We have a Kubernetes Operators workshop on Friday, so not only do we have pre-conference days of like OpenShift Cons that are huge now, but now we're starting to book end, CNCF events and put on other things, just because, and that, we had 100 seats that we were hoping we would fill, and it sold out in like minutes once it got in there, and there's a waiting list of like 300 people. It is like one of, aside from Knative, and all the other wonderful hot things too, it is one of the most interesting developments I think right now. >> Thirst for the content. Would it impact? >> Yeah, and you can get all of the documentation is out there now, and people are already building them. We have a list of 50 community Operators. It's just, it's phenomenal how quickly it's growing. >> You know, Diane and Rob, it's funny because you know, we do so many of these theCUBE interviews, and this is our 10th year doing theCUBE coming up, and I remember the conversations going back in the OpenStack days, we would ask questions like, if you had a magic wand, what would you like, hope to have happened, right? And you know, those are parts of the evolution, where it's like, it's aspirational, things are being built. It seems now with Kubernetes, it's almost like, wait a minute, it's actually, this is like the goodness is so compelling, above and below Kubernetes that it's almost like uncomprehendible. You think about, oh this is actually happening. Finally the kinds of steady state kind of operational things that have been a pain in the butt for years-- >> Yeah, the toil, it's gone, for the most part. >> Yeah. >> So Rob, I've been having a lot of just thinking back to, you're employee number two at Core OS, when I first talked to Core OS, it was, we're going to build all of these individual tools, and we're going to Open-source them, and it's going to be good. We watched this just rising ecosystem and the CNCF, and it feels like what's nice and what's different that I see, compared to some previous things, is it's not one product or even a small group of companies. It's, I have this tool kit, and some of them work together, but many of them are independently used. We've talked to your peers earlier about it, etCD. etCD is totally stand alone, doesn't need to be Kubernetes. What have you seen, if you go back to that original vision, would Core OS just been, part of this whole ecosystem, and done it, if this was available, and has this delivering on a promise that your team had hoped to work on? >> Yeah, so we've always filled in where we see gaps, and so something like etCD, the concept is not new, and it comes from Google, and they have a system internally, and as Brandon got up on stage and said, we needed that coordinate, reboot, to grow out, to cluster of machines. It didn't exist so we had to build it. Same thing with how we wanted to manage Linux. There was no distro that even resembled what we were doing. Wanted to do automatic upgrades, people thought that was crazy, so we had to go build it. And so, but we always adopted the best of breed technology, when it existed. In our early bet Kubernetes, we just saw, this is the thing, and went for it. I don't even remember what version, but it was months and months before it was zero point oh, or one point oh, so it was, we've been doing it forever. And you just see the right thing, and it's the little nugget that you need, and if you don't see it, then you build it. >> What are you surprised about Rob, in terms of the ecosystem now, you mentioned some goodness is happening, still a lot more to do, visibility around value creation, you're starting to see spots where value can be created in the ecosystem, which is great. Still more work areas, but what's surprising you? What do you see as opportunities, challenges? Your thoughts, because this vision of ease of use and programmability, is happening, right? So there's still more work to do. What's your vision there? What's your thoughts? >> I mean, I think self service is key, so this is like the rise of the Cloud comes from self service for developers, and Kubernetes gives you the right abstraction, where self service for VM's, like OpenStack, which is not quite at the level of what you want. You don't want a VM, you actually wanted a place to deploy an application, you wanted load balancing, you wanted service discovery, you didn't want like a bare Ubuntu VM, and so Kubernetes raises you up to where you're productive, and then it's about building stuff on top. But what's interesting, in the space is, we're still kind of competing on Kubernetes installers, and stuff like that, so we're not even really into like the phase where people are being super productive on the platform, other than these leading companies. So I think we'll democratize that, and we'll have a whole new landscape. >> And so 2019 you see as what being a key theme for Kubernetes? >> I think it'll be Core stuff built on top, like all the serverless frameworks, a bunch of container natives storage solutions, solving some of these problems that folks are reaching out to external machine learning, but bringing that onto the cluster, GPU support, that type of stuff. It's all about the workloads. >> And tradition end users, you have a huge install base, with Red Hat, well documented, as the end users start coming in and looking at CloudNative, and doing a reimagine of their environment, whether it's IT span, IT investments, to have a run their coding and the deployments. It's going to change. 2019's going to have an impact on what I call mainstream enterprise, for lack of a better description. What's the impact of those guys, 'cause now, they now have head room, they can do more, what's the main stream enterprise look like right now with the impact of Kubernetes? >> I think they're going to start deploying applications and get like lower the time to business value, much, much lower. And I was just talking to a customer, and they ordered bare metal machines like a year ago, and they're still not racked and in the data center. And so people are still getting over that type of stuff, but once you have like a shared Kubernetes layer, you can onboard teams like crazy. I mean, name spaces are free, quote, unquote, and you can get 35 engineering teams on a Kubernetes cluster super easy. >> So they can ramp up in development teams basically, as they bring value in-house, versus outsourcing everything. They start getting development teams, this is where the action is. >> I think you're also going to see the rise of those end users contributing back things, to the Kubernetes community and as Lyft, and Uber, and everybody are great examples of that. Uber with Jaeger, and Lyft is, we were just in the Operators thing, and they raised their hand that they are about to Open-source it, a few Operators that they're building and stuff, and you're just going to see people that you didn't normally see. Often these large foundation driven things are vendor driven, but I think what you see here, is the end user community is now embracing the Open-source, is getting the legal teams there, allowing them to share their things, because one, they get more people to maintain them, and more people working on them, but it's really I think the rise of the end user we'll see, as they start participating more and more in here. And that's the promise of Open-source. >> And that's where CNCF really made it's bones. It wasn't really vendor led per se, it was really end users, the guys building out their stuff for the first time. You see Lyft for instance, great example, you guys did a Core OS, this is like the new generational model. Final question before we break. I want to get this out there. Get a plug in for Red Hat. What are you guys, what's the focus for the show? What's the news? What's the big story for Red Hat here at KubeCon this year? >> I think it's Operators, that's what we're here talking about. It's a really big push to once again get smarter workloads onto the cluster. We've got a really great hybrid story, we've got a really great over the air upgrade story that we're bringing from some of the Core OS technology, and then the next thing is, once it's easy to run 35 clusters, we need a bunch of workloads to put on there. And so we want to save folks from the toil of running all those workloads as well, just like we did at the cluster level. >> Awesome. >> Well put. I couldn't add more. One of the things that Core OS did, you hit the nail on the head earlier, is when there was something missing, they helped us build it, and with the Operator SDK, and the Lifecycle Management, and the metering, and whatever else the tooling is, they have really been inspirational inside of Red Hat. And so they filled a number of gaps, and it's just been all Operators all the time right now. >> It's great when a plan comes together. You guys got a great tail wind. Congratulations on all the success, and it's just the beginning of the wave. It's theCUBE, covering the wave of innovation here at KubeCon CloudNativeCon 2018, we'll be back with more live coverage. Day two of Three days of Kube Coverage. We'll be right back. (upbeat music)

>> Narrator: Live from Austin, Texas, it's theCUBE, covering KubeCon and CloudNativeCon 2017, brought to you by Red Hat, the Linux Foundation, and theCUBE's ecosystem partners. >> Okay, welcome back, everyone. This is theCUBE's exclusive coverage live here in Austin, Texas for the CNCF's two conferences, CloudNativeCon, which was yesterday, and two days, today and tomorrow, KubeCon for Kubernetes' conference. This is theCUBE, of course, from SiliconANGLE Media. I'm John Furrier with my cohost, Stu Miniman. Our next guest, Dan Kohn, is the executive director of the CNCF, the man who put it all together. Congratulations. Welcome back to theCUBE. Good to see you. >> Oh, absolutely. Thrilled to have you guys back here again. >> So you kind of doing a victory lap here now, high fiving each other? >> Dan: Great hugs. >> John: Great event. >> Laughing: I'm glad it's a good event, and I am hearing fantastic feedback that folks are thrilled to be here. But we sort of describe this moment for the organization and the community as being the end of the beginning. >> John: Yeah. >> Where we now have all the major cloud vendors, all of the biggest enterprise software companies. We have a core group of 14 projects anchored by Kubernetes, but tons and tons of work in front of us. >> And tons of success, so I'm just going to read a couple of highlights from yesterday. There's a lot today. Baidu joins the CNCF, a lot of scaling production application examples, 31 new silver end-user members joined, Alibaba Cloud update to platinum, CoreDNS 1.0, Containerd, Fluentd, Jaeger, tons of news. Obviously, we've been pumping out the coverage. Today, again, more and more great goodness. But really interesting is that you guys have put a frame around this community to allow it to grow, to fertilize the open source vibe, which is all cloud but yet scaled. And you put up a slide I want to get your reaction to that I thought was compelling yesterday during your keynote. It was the flywheel, circle, and it said projects, products, profit. >> Dan: Right. >> And not that you're promoting profit, but you're not hiding the ball, either, saying, hey, you know what? There's a lot of commercial interest in cloud, obviously. We saw AWS' success last week. And that is if you create good products in this community framework, there's profit to be had. >> Right. So first of all, I should admit to plagiarizing that slide from Linux Foundation Executive Director Jim Zemlin. >> And similarly, I think you can look at a lot of aspects... >> It's an open source feature. >> Dan: Yes. >> Free for you to use. >> John: Right. >> Similarly, I think there's a lot of ways in which Kubernetes is trying to build on the success of Linux. And Jim even describes Kubernetes as the Linux of the cloud. >> John: Yeah. >> Stu: Yeah. >> John: That's a good point. >> Dan, one of the things we've been talking around Kubernetes is you talk about scale. >> Dan: Right. >> Talk about scale of the CNCF. You have 4 to 14 projects. People are a little worried when you get all the vendors around here and there's all these projects. It's a foundation thing, it's going to go off the rails. >> Dan: Yeah. >> Customers aren't going to have a voice. How do we make sure we kind of learn from some of the things that other projects have had challenges with in the past? >> And I think that's our advantage, which is the great thing about coming later than some of the other foundations, is we can look at where they had successes and where they had issues. And our aspiration for CNCF is to get to go make entirely new mistakes rather than replicating some of the issues that have come before. And so really from the beginning of CNCF, we had a somewhat unusual and frankly a little bit cumbersome charter where I describe it at times as a three-ring circus. We have a governing board made up of the vendors that are putting a lot of money into the community, but they don't get to run the projects and they don't even get to pick the projects. Instead, they appoint six of the nine members of an independent technical oversight committee, kind of like the Supreme Court. And then we have a third group in the end-user community that I'm thrilled to say is now up to 28 members in it. They appoint one of those folks. We finally got that working. We have Sam Lambert, the director of infrastructure at GitHub, who has just made a huge commitment to Kubernetes and is moving all their infrastructure over into it. Those seven appoint the last two. And so that body, and they just had their public meeting a couple hours ago. They feel very strongly about their independence, about their reputation, that they're trying to make very good judgments based on what they're seeing in the marketplace. >> That's interesting, the three-ring circle. I like how you put it. But let's talk about the end-user piece because I think that's critical. One of the things we were commenting earlier from the Lyft folks was you have a lot of end users who have built some large-scale systems out of their own sheer necessity. >> Dan: Definitely. >> And that is now being donated in. We saw Kubernetes come in with, you shepherded beautifully, went from Google, but you've got Lyft donating an amazing product convoy. >> This first convoy has a huge amount of excitement. And what was fun was, actually, on the same stage that they contributed back in LA in September, Uber contributed a separate project. Now, unlike Uber and Lyft, the two projects are in no way competitive- >> John: Yeah. >> Like Jaeger is really fantastic tracing one. But what they have in common is that they're companies that have had to grow from nothing to extremely high scale and then had problems that they solved. And they wanted to share that expertise with us. >> I want to get your thoughts on this. Because we've been speculating, on theCUBE, we've been kind of thinking, an editorial, but just that this is all good business. Now, that's pretty obvious, right? You're starting to see this kind of contribution, the gifts that keep on giving. These are significant code. >> Dan: Yeah. >> Not like, okay, let's start a little group and huddle and build something organically. You have real goodness coming in from Google, Uber, Lyft, and there's a million others. >> Dan: Right. >> How is that changing the game? Certainly accelerating it. That's really bringing goods to the table. >> Right. I think the whole... >> You have to manage it. >> Well, and for what it's worth, I don't actually manage the projects. And so we do provide a set of services- >> John: The community? >> -to them and we help them, we market them. But one of the unusual aspects of CNCF is that the projects do actually manage themselves. A little bit of guidance from the TOC, but we really are unusual in that sense. And that's one of the reasons the projects have been... >> And what's interesting is, to connect the dots, though, one step further, you're talking about a commercial entity donating massive intellectual property in the open for all the goodness of everyone else. But yet that flywheel is continuing. They're still using it. So it is inherently commercial dynamic. >> Right. And back to that circle, I think really the underlying concept is that companies agree that sharing key parts of their infrastructure has a huge amount of value to the whole ecosystem, to each other. And then they're absolutely eager to compete above that. And so you can look at it with the public clouds where we have now Amazon, Microsoft, Google, Alibaba, IBM, Oracle all at the table. They are absolutely fierce competitors. But they're saying that this specific software infrastructure layer isn't the area that they want to compete. They want to compete on all the value-added services, customer service, et cetera. >> Dan, I wonder if you can speak to how CNCF connects to some of the broader communities out there. Things like Kata containers got announced coming out of the OpenStack group. You've got a serverless track happening here, kind of extends some of where Kubernetes is going. How does CNCF fit into the broader... >> Sure. And it's definitely the case that all the innovation out there cannot happen in CNCF. Most obviously, everything that we do, almost everything depends on Linux. And so that's our parent organization, the Linux Foundation. But we've had a good collaboration with Jonathan Bryce from OverStack. They have two booths on the floor here at the show. And we've spoken to Clear Containers and RunV, the two predecessors in the past. But the part that I'm particularly pleased with for Kata containers is that it is an OCI-compliant runtime, that's another sister organization, and is really designed to work well for Kubernetes. And then they can pitch that and let the market go decide which container runtimes they find the most valuable. >> Obviously a lot of traction here in terms of the sentiment around service meshes and pluggable lock-in textures. That's been very cool. But security came up. So I want to get your thoughts around security, obviously storage and these older models around how to deal with storage and networking. Obviously, always in the action. >> Yeah. >> But security is top of mind for everyone. How is that being addressed? You know, talk is out there... >> Sure. I mean our philosophy on this is that moving to cloud-native and particularly the continuous integration and continuous development that goes along with that is the most important step that you can do to help secure your infrastructure. And Equifax is the example everyone always brings up. But there was a case where they were using known insecure software and they didn't have the processes up to place where instead of doing quarterly updates or monthly updates, you want to be doing dozens of updates per day. And a cloud-native infrastructure allows you to do that. >> What's next for you? Because you've got great traction with both community response, and the community has been absolutely amazing, the quality of people, level has been great, but also at the funding sponsors. You've got a lot of people that are involved. What's next? What happens next? What do you envision happening? What's the plan, and then how do you view that evolving? >> Well, I hate to fall into the buzzword implosion here, but if you go back to the crossing the chasm metaphor, I think we're still very much just in the early adopter phase. 2018 could very well be the moment that we jump over to the early majority. And I do feel like this whole community now has the velocity to do that and that we're on track for it. But as that happens, there's just far, far more people who need to be educated so they understand the projects and the options and how to work with them. And then hopefully they go from just being consumers of these technologies to contributors and that we can welcome them into our community and hopefully get the advantage of their expertise as well. >> I want to get your thoughts on a comment that Stu and I were talking about. Stu, you and I were talking about the notion of value creation above the stack, and then how Kubernetes, although some could say being commoditized, but it's also creating value because with that consistency of Kubernetes, you can now create value. So we believe, and I want to get your reaction to this, because we think a whole new ecosystem dynamic will emerge of a new kind of ecosystem. And if this new app developer combined with software engineering, which is really going on, you're talking about the cloud, the app developers will just build in value, that value creation will be rewarded. That's where monetization will be happening. >> And if I could build off that... >> John: Yeah. >> Dan, I loved one of your opening comments. You quoted, "exciting times for boring infrastructure, "maybe too exciting." So this week we've been teasing out there's a lot of work to make that infrastructure boring. You've got everybody on this floor, the CNCF board, lots of new projects making that. Where the action is and what this is going to create is that application monetization and the speed and agility of being able to create these cool new cloud-native applications out there. So it's interesting dynamic, spans broad pieces of this, layers of the stack there. >> Yeah. Well, I will point out that there was an odd level of unanimity of just a ton of different leaders in the community, in keynotes from Craig McLuckie and Chen Goldberg and others where they all agree that Kubernetes is not by any means the ultimate answer or the final answer. I think everybody now expects to see Kubernetes as a core aspect of the infrastructure for software for the next decade or more. But there's a belief that there's a whole ton of value that needs to be added above it, particularly to try and show for a regular application developer who just has a PHP app or no-GS microservices or anything else what's the easiest way to go from having a piece of software and deploying it effectively. >> Dan, so it's interesting. You watch the people on the outside. They're like, oh, look at Kubernetes. They're all holding hands and saying Kumbaya. We know there's some spirited debates that happen- >> Dan: Definitely. >> In the code, some projects that are sometimes competing up there. Why has the community come together, and where are some of the areas that we still need to work on and improve to help customers going forward? >> And again, I think they have the big advantage of having watched other communities that didn't value community and consensus and the ability to work through their issues. And so thankfully, we just have a ton of really capable engineers who also have some of those social or personal qualities that they care about working these things out. And to date, at least, I think most of those disagreements have been settled pretty amicably and in a positive direction. I think there's still huge swathes of this space that are still up in the air. Storage is an obvious one where there's a ton of work going on in a storage working group of CNCF. Serverless is another where I think everyone agrees that the application deployment model of AWS Lambda is really exciting and has things that people should replicate and should be brought over to Kubernetes. But how that should happen, what the software is, et cetera, there's still, in fact, we have our first serverless track today here at KubeCon where several different competing approaches are all talking about what they'd like to do. >> Awesome stuff. And you also announced some dates for next year, December 11 and 13 in Seattle. >> Dan: Yes. >> Okay. >> Dan: That's a year from now. >> November 14 and 15 in Shanghai. >> Now, you and I met in Hangzhou in the lobby, which was just amazing. But I certainly am hoping to convince you to go back to China with us. This will be our first event... >> I got a three-year visa. >> Good, yeah, that's the exactly right one. But this will be our first event in China, which I think is just a huge opportunity. We now have Baidu, Tencent, Huawai, ZTE, a number of startups. There's just so much excitement for this space over there that we're really excited to satisfy. >> Stu: And Copenhagen in May. >> And that's the last one. Thank you. May 2 to 4 in Copenhagen, and we're really excited for the event, to bring it to Europe and the rest of the world. >> Okay. So you've been working like a dog, you've been working hard. I've seen you in China. It's serendipitous. But it's not without being mentioned that this has been great effort by your team and the Linux Foundation and Jim and the whole team. But congratulations. Are you having a pinch me moment? I know it's too early to do a victory lap. >> But you've got to be pretty excited. >> Yeah. It really has been a great thing for the foundation that we sort of accomplished many of our 2018 and 2019 goals this year. But I'm sure we're going to find plenty of stuff to do next year. >> And your goal for the next 6 to 12 months, what's on your top three to-do's, continue the momentum? Share your API for... >> Yeah. What's great is that we really have plenty of members. We'd always like to add new ones and serve the ones we have better. But right now, the focus is really about providing better services to our projects. All of them feel overworked. They would love help on documentation, on marketing, on messaging about it, and some of them need help with testing development and other things. So that's really what we're buckling down on. >> Great community are going to test them, being here on the ground, personally present at creation. And I was standing there with J.J. and Lew Tucker, OpenStack three years ago, talking about Kubernetes. We were kind of ripping. We couldn't have imagined, then, obviously, they bolted it on last year with your event. Now second year here, huge community... >> But you have 4,100 folks here, is more than the previous four events combined. >> Yeah, awesome. >> So it really is exciting. >> TheCUBE, always on the ground. And sometimes the squirrel finds a nut. We found a cloud-native foundation, part of the Linux Foundation. CNCF, Cloud-Native Compute Foundation, really a new, growing, and relevant community for cloud and a new way to do software and reimagine the future from software engineering to full application development, a new way. This is theCUBE's coverage, and we are here live in Austin. More live coverage after this short break. We'll be right back. [Techno Music]

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

(gentle music) >> Announcer: Live, from Los Angeles, it's theCUBE, covering Open Source Summit, North America, 2017, brought to you by the Linux Foundation and Red Hat. >> Okay welcome back, and we're live here in Los Angeles, this is theCUBE's exclusive coverage of the Linux Foundation's Open Source Summit North America. I'm John Furrier, your host with my co-host Stu Miniman. Our next guest is Chris Aniszczyk, who's the COO, Chief Operating Officer of the CNCF, the Cloud Native Compute Foundation, formerly Cube-Con, Cloud Native Foundation, all rolled into the most popular Linux Foundation project right now, very fashionable, cloud native, running on native clouds, Chris welcome back to theCUBE, good to see you. >> Awesome, it's been a while, great to be back. >> So you are the Chief Operating Officer of the hottest project, to me at least, in the Foundation. Not the most important, because there's a lot of really important, everything's important, you don't pick a favorite child, but, if one's trending, the CNCF is certainly trending, it's got the most sponsors, it's got the most participants, there's so much action going on, there's so much change and opportunity, around Kubernetes, around containers, around writing cloud-native applications. You've guys have really put together a nice foundation around that, nice group, congratulations. >> Thank you. >> Take a step back and explain to us, what the hell is the CNCF? We know what it is, we were there present at creation, but it's super-important, it's growing in relevance every day. Take a minute to explain. >> So I mean, you know, CNCF is all about providing a neutral home for cloud-native technology, and it's been about almost two years since our first board meeting and the idea was, there's a certain set of technology out there that are essentially micro-service-based, that live in containers that are centrally orchestrated by some process, right, that's essentially what we mean when we say cloud-native, right, and CNCF was seeded with Kubernetes as its first project, and as we've seen over the last couple of years, Kubernetes has grown quite well, they have a large community, diverse contributor base, and have done kind of extremely well. They're one of actually the fastest, highest velocity open source projects out there, maybe only, compared to the kernel is maybe a little bit faster but it's just great to kind of see it growing. >> Why is it so hot right now? What's the catalyst? >> So I think if we kind of step back and we look at the trends in industry, right, more and more companies are becoming software companies, you know, folks like John Deere, building IoT platforms. You need some type of infrastructure to run this stuff, and especially at scale. You know, imagine sensors in every tractor, farm or in every vehicle, you're going to need serious infrastructure and cloud native really is a way to scale those type of infrastructure needs and so this is kind of I think why you're seeing a lot of interest being piqued in CNCF-related technology. >> A lot of prototypes too. >> Chris, see you know, it's interesting, I look back you know, a year or two ago, and it was like, oh, it was like the orchestration wars, it was Swarm versus Mesos, and now I look at it in the last year it's like, wait, Mesos fully embracing it, MesosCon they're going to be talking about how Mesos is the best place to you know, Kubernetes on DCOS, containerd now part of the container wars, so the container wars, we're going to talk about OCI, you know, Amazon, Microsoft, of course Google, out there at the beginning. Is there anybody that's not on board that Kubernetes... >> I mean we really have the top five cloud providers in the world, depending on what metrics you look at, part of CNCF, you know there's some others out there that still aren't fully part of the family. Hopefully if you stay tuned over the next week or so you may hear some announcements coming from CNCF of other large cloudy-type companies joining the family. >> Every week there's a new platinum sponsor (Chris laughs) and you guys are getting a check every week it seems. >> To me it's great to see companies stepping up to the play and actually sustaining open source foundations that are critical to the actual business, and I think that it's great to see this involvement. So to me I'm personally thrilled, 'cause otherwise we'd be in a situation where if the top five cloud providers in the world weren't part of CNCF, maybe they'd be trying to do their own initiative, so it's great that we have these companies at the table, and all trying to build, you know, find their own pathway to cloud-native. >> You guys are hyper-growth right now, and you're new too, you're still kind of you know, >> Chris: Less than two years old! >> I mean it's amazing. So I want to put a little Jim Zemlin test to you, (Chris laughs) which is, in his keynote today he talked about, this is the big kind of event for the whole community of open source to come together, and again, you're talking 64 million libraries out there now. He projected by 2026, 400 million, it literally is a hockey stick growth, so you got growth there, so he talked about four things, my summary. Project health, so healthiness, sustainability, secure code, training, new members. What's your strategy re those four things? Keeping the CNCF healthy, you don't eat too much and choke on all of that growth... >> Yeah, so in terms of projects, we have a very unique governance structure in place when we designed CNCF. So we kind of have this independent technical operating committee, we kind of jokingly refer to them as a technical supreme court, but they are made up of people from, kind of luminaries in the container cloud-native space, they're from competing companies too, but they try to really wear an independent hat and make sure that we're, projects that we're accepting are high quality, are a good fit for the foundation, and so it's actually fairly hard to get a project in CNCF, 'cause it really requires the blessing of this TOC. So, even though we have 10 projects now in about two years, I think that's about a project every two months, which is an okay pace. The other unique thing that we're doing is we have different levels of projects, we have inception, incubation and graduation. Right now, we have no graduated projects in CNCF, believe it or not, Kubernetes has not graduated yet because they're still finalizing their governance for the project and they're almost there. Once they do that, they'll most likely graduate. >> They'll walk cap and gown all nine yards, eh? >> Exactly, it'll be great. December we'll have the cap and gown ceremony. But the other unique thing is we're not, we do annual kind of reviews for some of our projects, certain levels will be annually reviewed, and if they're not longer healthy or a good fit, we're okay archiving them, or telling, you know, telling them you know, maybe you're not a good fit anymore for the foundation, or you know. And so I think you have to have a process in place where sometimes you do have to move things to the attic. >> Do you have a high bar on the projects >> The initial bar is extremely, extremely high, and I think over time, we may see some projects that get recycled or moved to the attic, or maybe they maybe merged together, we'll see, so we're thinking about this already, so... >> John: Okay, security? >> Security, so we, all projects in CNCF that graduate have to partake in the core infrastructures best practices badging program, so if the CII has this great effort that is basically helping to ensure projects meet a minimal level of best practices that make their projects secure. You know, it doesn't give you like full-blown guarantee, but these are good practices. >> So you were leveraging pre-existing work, classic, open-source ethos. >> Exactly, and they have like a set of domain experts completely focused on security building out these practices and you'll notice Kubernetes recently merged in the CII Best Practices badge, so if you go to the readme, you'll actually see it, and you'll click through and you'll see all the things that they've had to sign off and check on that they participate in, and so all of our projects are kind of going >> Training. >> Training, yeah, we just recently announced couple things. One is we have a >> Looking good so far, you get an A plus. >> Yeah, so as of today we've launched the Certified Kubernetes Administrator Program or CKA for short. So we have folks that are getting trained on, and are having official stamps that they are certified Kubernetes administrators, and to me that's huge, given like how hot the space is, having some stamp of approval that they are really certified in the space is huge. So we also offer free training through edX, so we launched some training courses earlier, and to be honest, if you look at our member companies, lots of great folks out there providing training material. >> So one of the keynotes that Christine Corbett Moran was talking about in her keynote was, more inclusion so there's no ruling class. Now I know you really have a ruling class going on with your high bar, I get that. How are you getting new members in, what's the strategy, who are the new members, how are you going to manage the perception possibly that a few people control the swing votes at potentially big projects? >> So here what's interesting is, people joining CNCF, like I mentioned before, we have a TOC, right? So there's kind of this separation of, I don't say church and state, but like, so the governing board, people who pay to join CNCF, they pay to sustain our open source projects, and so essentially they help with, they pay for marketing, staff, events and so on. They actually don't have technical influence over the projects. You don't have to be a member to have technical influence over our projects. People join CNCF because they want to have a say in the overall budget of how marketing, events and stuff, and just overall support the organization. But on the technical side, there's this kind of firewall, there's an independent TOC, they make the technical decisions. You can't really pay to join that at all, you have to actually be heavily participating in that community. >> John: How does someone get in that group? Is there a code? >> They have to just be like a luminary, we have a kind of election process that happens every two or three years, depending on how things are structured, and it's independently elected by the CNCF member community, essentially, is the simplest way I can explain it. >> The other announcement you talked about, kind of the individual certification, but the KCSP sort of programs >> Correct, exactly. >> Maybe you can tell us a little bit about that. >> Yes, so we had a program set up so it's Kubernetes Certified Service Provider, KCSP, that basically >> rolls right off the tongue >> I know, right, exactly. Herbal space program, whatever, I think of sometimes video games when we say it, but essentially, the program was put in place that a lot of end users out there in companies that are new to cloud native, and they're new to Kubernetes, essentially want to find a trusted set of partners that they can rely on, services and other things, so we created KCSP as a way to vet a certain set of companies that have at least a minimum of three people that have passed the Kubernetes certification exam that I talked about, and are essentially participating upstream in some way actively in the Kubernetes community. So we got a couple handfuls of companies that have launched, which is great, and so now, given that we're growing so fast, companies out there that are early end users that are exploring the space now have a trusted set of companies that go look at, and we're hoping to grow that program over time too. So this is just phase one. >> All right, so Chris, the other thing that I want to make sure we talk about, the Open Container Initiative, so I think it was originally OCP, which of course is, >> Open Container Project which when OCP was announced, it was like, okay, the cold war of Docker versus CoreOS versus everybody else, (Chris laughs) trying to figure out what that container format was, we all shook hands, I took a nice selfie with Ben who was CEO at the time, and everybody. So 1.0 is out. So, container's fully mature, ready to be rolled out right? But what does it mean? >> So I mean it's funny 'cause I basically joined the Linux Foundation, to help both start CNCF and OCI around the same time, right, and OCI was very narrowly scoped to only care about a small set of container-specific issues. One around how do you actually really run containers, start, stop, all that kind of life cycle bit, and how are containers laid out on disk, we call that the image specification. So you have the runtime spec and the image spec, and those are just very limited core pieces, like that OCI was not opinionated on networking or storage or any of, those are all left to other initiatives. And so after almost two years, we shipped 1.0, we got basically all the major container players to agree that this is 1.0 and we're going to build off from this, and so if you look at Docker with it's containerd project, or you know, fully adopting OCI, the Mesos community is, Cloud Foundry, even AWS announced their container register's supporting OCI, so we got the 1.0 out there, now we're going to see an abundance of people building tools and other things. I think you'll see more end users out there exploring containers. I've talked to a lot of companies that I can't necessarily name, but there's a lot of folks out there that may not dive into container technology until there is actually a mature standard and they feel like this technology is just not going to go away or they're going to get locked into some specific platforms. So, with 1.0 out the door, you'll see over the next six to 12 months, more tools being built. We're actually working to roll out a certification program so you get that nice little, you know, hey, this product is OCI-certified and supports the spec, so you'll see that happen over the next... >> Okay, so you've got the runtime spec and the image format spec, >> Yep, those are the two big ones. >> All 1.0, we're ready to roll, what's the roadmap >> Yeah, what's next. So there are early discussions about what other mature areas are out there kind of in container land right now. There are some discussions around distribution, so having a standard API to basically fetch and push container images out there. If you look at it, each container registry has basically a different set of APIs, and wouldn't it be nice if we could all kind of easily work together and have maybe one set, a way to kind of distribute these things. So there are some early discussions around potentially building out a distribution specification, but that's something that the technical community has to decide within OCI to do, and so over the next couple of months we're having some meetings, we're doing a bigger meeting at DockerCon Europe coming up in October to basically try to figure out what's really next. So I think after we shipped 1.0 a lot of people took a little bit of a breather, a break, and say like, congratulate themselves, take some vacation over the summer, and now we're going to get back into the full swing of things over the next couple of months. >> Say, what's the big conversation here, obviously at your event in Austin, it's got a plug for, theCUBE will be live covering it as well. >> I know, I'm excited. >> What's the uptake, what's the conversation in the hallways, any meetings, give us some >> Yeah, so we're doing >> I know there's some big announcement coming on Wednesday, there's some stuff happening >> Yeah, so, you know, first coming Wednesday, so like I mentioned, we have 10 projects right now in CNCF. We have two projects currently out for vote. So one of them is Envoy. There's a company you've probably heard of, Lyft, ride-sharing company, but Envoy essentially is their fancy service mesh that powers the Lyft platform, and many other companies out there are actually taking advantage of Envoy. Google's playing around with it, integrating into the Istio project, which is pretty powerful, but Envoy is currently, it was invited by the TOC for a formal vote, the voting period started last week, so we're collecting votes from the nine TOC members, and once that voting period is hopefully we can announce whether the project was accepted or not. The other project in the pipeline is a project called Jaeger, which is from Uber, you know, nice to have Uber >> John: Jaegermeister. >> Yeah, Jaegermeister, a bit like it. It's nice to have a product from Uber, another product from Lyft, kind of it's nice to see >> And if you have too much Jaeger, you have to take the Lyft to get home, right? >> Exactly, correct. So you know, just like Envoy, Jaeger is, you know, was formally invited by the TOC, it's out for vote, and hopefully we'll count the votes soon and figure out if it gets accepted or not. So Jaeger is focused on distributed tracing, so one problem in micro-services land is once you kind of like refactor your application to kind of be micro-services-based, actually tracing and figuring out what happens when things go wrong is hard, and you need a really good set of distributed tracing tools, 'cause otherwise it's like the worst murder mystery, you have like no idea what's happened, so having solid distributed tracing solution like Jaeger is great, 'cause in CNCF we're going to have a project called OpenTracing, but that's just kind of like the spec of how you do things, there's no full-blown client-server distributed >> For instance you usually need it for manageability >> Exactly, and that's what Jaeger provides, and I'm excited to kind of have these two projects under consideration in CNCF. >> Is manageability the hottest thing going on right now in terms of conversations? (Chris sighs) Or is it more stability and getting projects graduating? >> Yeah, so like our big focus is like, we want to see projects graduate, kind of meet the minimum bar that the TOC set up for graduated projects. In terms of other hot areas that are under discussion in CNCF are storage, so for example we have a storage working group that's been working hard to kind of bring in all the vendors and different storage folks together, and there's some early work called the container storage interface, we call it CSI for short, and so you know there's another project at CNCF called CNI, which basically tried to build a standard around how networking is done in container land. CSI is doing the same thing because, you know, it's no fun rewriting your storage drivers for all the different orchestration systems out there, and so why not get together and build out a standard that is used by Kubernetes, by Mesos, by Cloud Foundry, by Docker, and just have it so they all work across these things. So that's what's happening, and it's still early days, but there's a lot of excitement in that. >> Okay, the event in Austin, what can people expect? Cube-Con. >> You're literally going to have the biggest gathering of Kubernetes and cloud-native talent. It's actually going to be one of our biggest events probably for the Linux Foundation at all. We're probably going to get 3-4,000 people minimum out there, and I'm stoked, we're going to have some... Schedule's not fully announced yet. I do secretly know some of the keynotes potentially, but just wait for that announcement, I promise you it's going to be great. >> And one question I get, just I thought I'd bring it up since you're here in the hot seat, lot of people coming in with, supporting you guys on the governing side, not even cyclical. How are you going to service them, how are you going to scale up, do you have confidence that you have the ability to execute against those sponsorships, support the members, what's your plan, can you share some insights, clarify that? >> You know, pressure makes diamonds, right? We have a lot of people at the right table, and we are doing some hiring, so we have a couple spots open for developer advocacy, technical writing, you know additive things that help our project overall. We're also trying to hire a head of marketing. So like, we are in the process of expanding the organization. >> Do you feel comfortable... >> I feel comfortable, like things are growing, things are moving at a fast clip, but we're doing the best we can to hire and don't be surprised if you hear some announcements soon about some fun hires. >> Well it's been great for us covering, we've been present and creating, if you will, this movement, which has been kind of cool, because it kind of a confluence of a couple of things coming together. >> Chris: Yeah, absolutely. >> It's just been really fun to watch, just the momentum from the cloud really early days, 2009 timeframe to now, it's been a real nice ride and congratulations to the entire community. >> Thank you, like for me it's just exciting to have all these companies sitting together at the same table, having Amazon join, and the other top fighters, all basically committing to saying, we are in the cloud-native, we may have different ways of getting there, but we're all committed working together at some level. So I'm stoked. >> Great momentum, and you guys doing some great work, congratulations. >> Thank you very much. >> And you know it's working when I get focused, hey can you, so and so, I'm like, oh yeah, no problem, oh wow, they're big time now, you guys are big time. Congratulations. >> Thank you, it's in phase one now, like we have the right people at the table >> Don't screw it up! (John and Chris laugh) As they say. It's on yours. Chris Aniszczyk, who's the COO of the Cloud Native Compute Foundation, the hottest area of Linux Foundation right now, a lot of action on cloud, cloud-native developers where DevOps is meeting, lot of progress in application development. Still, they're really only two years old, get involved, more inclusion the better. It's theCUBE, Cube coverage of CNCF. We'll be in Austin in December. >> Chris: Yep, six to eight. >> December 6 to 8, we'll be there live. More live coverage coming back in Los Angeles here for the Open Source Summit North America after this short break.