>>Hi everybody. This is Dave Volante. Welcome to this cube conversation where we're going to go back in time a little bit and explore the early days of Kubernetes. Talk about how it formed the improbable events, perhaps that led to it. And maybe how customers are taking advantage of containers and container orchestration today, and maybe where the industry is going. Matt Provo is here. He's the founder and CEO of storm forge and Chandler Huntington hoes. Hoisington is the general manager of EKS edge and hybrid AWS guys. Thanks for coming on. Good to see you. Thanks for having me. Thanks. So, Jenny, you were the vice president of engineering at miso sphere. Is that, is that correct? >>Well, uh, vice-president engineering basis, fear and then I ran product and engineering for DTQ masons. >>Yeah. Okay. Okay. So you were there in the early days of, of container orchestration and Matt, you, you were working at a S a S a Docker swarm shop, right? Yep. Okay. So I mean, a lot of people were, you know, using your platform was pretty novel at the time. Uh, it was, it was more sophisticated than what was happening with, with Kubernetes. Take us back. What was it like then? Did you guys, I mean, everybody was coming out. I remember there was, I think there was one Docker con and everybody was coming, the Kubernetes was announced, and then you guys were there, doc Docker swarm was, was announced and there were probably three or four other startups doing kind of container orchestration. And what, what were those days like? Yeah. >>Yeah. I wasn't actually atmosphere for those days, but I know them well, I know the story as well. Um, uh, I came right as we started to pivot towards Kubernetes there, but, um, it's a really interesting story. I mean, obviously they did a documentary on it and, uh, you know, people can watch that. It's pretty good. But, um, I think that, from my perspective, it was, it was really interesting how this happened. You had basically, uh, con you had this advent of containers coming out, right? So, so there's new novel technology and Solomon, and these folks started saying, Hey, you know, wait a second, wait if I put a UX around these couple of Linux features that got launched a couple of years ago, what does that look like? Oh, this is pretty cool. Um, so you have containers starting to crop up. And at the same time you had folks like ThoughtWorks and other kind of thought leaders in the space, uh, starting to talk about microservices and saying, Hey, monoliths are bad and you should break up these monoliths into smaller pieces. >>And any Greenfield application should be broken up into individuals, scalable units that a team can can own by themselves, and they can scale independent of each other. And you can write tests against them independently of other components. And you should break up these big, big mandalas. And now we are kind of going back to model this, but that's for another day. Um, so, so you had microservices coming out and then you also had containers coming out, same time. So there was like, oh, we need to put these microservices in something perfect. We'll put them in containers. And so at that point, you don't really, before that moment, you didn't really need container orchestration. You could just run a workload in a container and be done with it, right? You didn't need, you don't need Kubernetes to run Docker. Um, but all of a sudden you had tons and tons of containers and you had to manage these in some way. >>And so that's where container orchestration came, came from. And, and Ben Heineman, the founder of Mesa was actually helping schedule spark at the time at Berkeley. Um, and that was one of the first workloads with spark for Macy's. And then his friends at Twitter said, Hey, come over, can you help us do this with containers at Twitter? He said, okay. So when it helped them do it with containers at Twitter, and that's kinda how that branch of the container wars was started. And, um, you know, it was really, really great technology and it actually is still in production in a lot of shops today. Um, uh, more and more people are moving towards Kubernetes and Mesa sphere saw that trend. And at the end of the day, Mesa sphere was less concerned about, even though they named the company Mesa sphere, they were less concerned about helping customers with Mesa specifically. They really want to help customers with these distributed problems. And so it didn't make sense to, to just do Mesa. So they would took on Kubernetes as well. And I hope >>I don't do that. I remember, uh, my, my co-founder John furrier introduced me to Jerry Chen way back when Jerry is his first, uh, uh, VC investment with Greylock was Docker. And we were talking in these very, obviously very excited about it. And, and his Chandler was just saying, it said Solomon and the team simplified, you know, containers, you know, simple and brilliant. All right. So you guys saw the opportunity where you were Docker swarm shop. Why? Because you needed, you know, more sophisticated capabilities. Yeah. But then you, you switched why the switch, what was happening? What was the mindset back then? We ran >>And into some scale challenges in kind of operationalize or, or productizing our kind of our core machine learning. And, you know, we, we, we saw kind of the, the challenges, luckily a bit ahead of our time. And, um, we happen to have someone on the team that was also kind of moonlighting, uh, as one of the, the original core contributors to Kubernetes. And so as this sort of shift was taking place, um, we, we S we saw the flexibility, uh, of what was becoming Kubernetes. Um, and, uh, I'll never forget. I left on a Friday and came back on a Monday and we had lifted and shifted, uh, to Kubernetes. Uh, the challenge was, um, you know, you, at that time, you, you didn't have what you have today through EKS. And, uh, those kinds of services were, um, just getting that first cluster up and running was, was super, super difficult, even in a small environment. >>And so I remember we, you know, we, we finally got it up and running and it was like, nobody touch it, don't do anything. Uh, but obviously that doesn't, that doesn't scale either. And so that's really, you know, being kind of a data science focused shop at storm forge from the very beginning. And that's where our core IP is. Uh, our, our team looked at that problem. And then we looked at, okay, there are a bunch of parameters and ways that I can tune this application. And, uh, why are the configurations set the way that they are? And, you know, uh, is there room to explore? And that's really where, unfortunately, >>Because Mesa said much greater enterprise capabilities as the Docker swarm, at least they were heading in that direction, but you still saw that Kubernetes was, was attractive because even though it didn't have all the security features and enterprise features, because it was just so simple. I remember Jen Goldberg who was at Google at the time saying, no, we were focused on keeping it simple and we're going from mass adoption, but does that kind of what you said? >>Yeah. And we made a bet, honestly. Uh, we saw that the, uh, you know, the growing community was really starting to, you know, we had a little bit of an inside view because we had, we had someone that was very much in the, in the original part, but you also saw the, the tool chain itself start to, uh, start to come into place right. A little bit. And it's still hardening now, but, um, yeah, we, as any, uh, as any startup does, we, we made a pivot and we made a bet and, uh, this, this one paid off >>Well, it's interesting because, you know, we said at the time, I mean, you had, obviously Amazon invented the modern cloud. You know, Microsoft has the advantage of has got this huge software stays, Hey, just now run it into the cloud. Okay, great. So they had their entry point. Google didn't have an entry point. This is kind of a hail Mary against Amazon. And, and I, I wrote a piece, you know, the improbable, Verizon, who Kubernetes to become the O S you know, the cloud, but, but I asked, did it make sense for Google to do that? And it never made any money off of it, but I would argue they, they were kind of, they'd be irrelevant if they didn't have, they hadn't done that yet, but it didn't really hurt. It certainly didn't hurt Amazon EKS. And you do containers and your customers you've embraced it. Right. I mean, I, I don't know what it was like early days. I remember I've have talked to Amazon people about this. It's like, okay, we saw it and then talk to customers, what are they doing? Right. That's kind of what the mindset is, right? Yeah. >>That's, I, I, you know, I've, I've been at Amazon a couple of years now, and you hear the stories of all we're customer obsessed. We listened to our customers like, okay, okay. We have our company values, too. You get told them. And when you're, uh, when you get first hired in the first day, and you never really think about them again, but Amazon, that really is preached every day. It really is. Um, uh, and that we really do listen to our customers. So when customers start asking for communities, we said, okay, when we built it for them. So, I mean, it's, it's really that simple. Um, and, and we also, it's not as simple as just building them a Kubernetes service. Amazon has a big commitment now to start, you know, getting involved more in the community and working with folks like storm forage and, and really listening to customers and what they want. And they want us working with folks like storm florigen and that, and that's why we're doing things like this. So, well, >>It's interesting, because of course, everybody looks at the ecosystem, says, oh, Amazon's going to kill the ecosystem. And then we saw an article the other day in, um, I think it was CRN, did an article, great job by Amazon PR, but talk about snowflake and Amazon's relationship. And I've said many times snowflake probably drives more than any other ISV out there. And so, yeah, maybe the Redshift guys might not love snowflake, but Amazon in general, you know, they're doing great three things. And I remember Andy Jassy said to me, one time, look, we love the ecosystem. We need the ecosystem. They have to innovate too. If they don't, you know, keep pace, you know, they're going to be in trouble. So that's actually a healthy kind of a dynamic, I mean, as an ecosystem partner, how do you, >>Well, I'll go back to one thing without the work that Google did to open source Kubernetes, a storm forge wouldn't exist, but without the effort that AWS and, and EKS in particular, um, provides and opens up for, for developers to, to innovate and to continue, continue kind of operationalizing the shift to Kubernetes, um, you know, we wouldn't have nearly the opportunity that we do to actually listen to them as well, listen to the users and be able to say, w w w what do you want, right. Our entire reason for existence comes from asking users, like, how painful is this process? Uh, like how much confidence do you have in the, you know, out of the box, defaults that ship with your, you know, with your database or whatever it is. And, uh, and, and how much do you love, uh, manually tuning your application? >>And, and, uh, obviously nobody's said, I love that. And so I think as that ecosystem comes together and continues expanding, um, it's just, it opens up a huge opportunity, uh, not only for existing, you know, EKS and, uh, AWS users to continue innovating, but for companies like storm forge, to be able to provide that opportunity for them as well. And, and that's pretty powerful. So I think without a lot of the moves they've made, um, you know, th the door wouldn't be nearly as open for companies like, who are, you know, growing quickly, but are smaller to be able to, you know, to exist. >>Well, and I was saying earlier that, that you've, you're in, I wrote about this, you're going to get better capabilities. You're clearly seeing that cluster management we've talked about better, better automation, security, the whole shift left movement. Um, so obviously there's a lot of momentum right now for Kubernetes. When you think about bare metal servers and storage, and then you had VM virtualization, VMware really, and then containers, and then Kubernetes as another abstraction, I would expect we're not at the end of the road here. Uh, what's next? Is there another abstraction layer that you would think is coming? Yeah, >>I mean, w for awhile, it looked like, and I remember even with our like board members and some of our investors said, well, you know, well, what about serverless? And, you know, what's the next Kubernetes and nothing, we, as much as I love Kubernetes, um, which I do, and we do, um, nothing about what we particularly do. We are purpose built for Kubernetes, but from a core kind of machine learning and problem solving standpoint, um, we could apply this elsewhere, uh, if we went that direction and so time will tell what will be next, then there will be something, uh, you know, that will end up, you know, expanding beyond Kubernetes at some point. Um, but, you know, I think, um, without knowing what that is, you know, our job is to, to, to serve our, you know, to serve our customers and serve our users in the way that they are asking for that. >>Well, serverless obviously is exploding when you look again, and we tucked the ETR survey data, when you look at, at the services within Amazon and other cloud providers, you know, the functions off, off the charts. Uh, so that's kind of an interesting and notable now, of course, you've got Chandler, you've got edge in your title. You've got hybrid in, in your title. So, you know, this notion of the cloud expanding, it's not just a set of remote services, just only in the public cloud. Now it's, it's coming to on premises. You actually got Andy, Jesse, my head space. He said, one time we just look at it. The data centers is another edge location. Right. Okay. That's a way to look at it and then you've got edge. Um, so that cloud is expanding, isn't it? The definition of cloud is, is, is evolving. >>Yeah, that's right. I mean, customers one-on-one run workloads in lots of places. Um, and that's why we have things like, you know, local zones and wavelengths and outposts and EKS anywhere, um, EKS, distro, and obviously probably lots more things to come. And there's, I always think of like, Amazon's Kubernetes strategy on a manageability scale. We're on one far end of the spectrum, you have EKS distro, which is just a collection of the core Kubernetes packages. And you could, you could take those and stand them up yourself in a broom closet, in a, in a retail shop. And then on the other far in the spectrum, you have EKS far gate where you can just give us your container and we'll handle everything for you. Um, and then we kind of tried to solve everything in between for your data center and for the cloud. And so you can, you can really ask Amazon, I want you to manage my control plane. I want you to manage this much of my worker nodes, et cetera. And oh, I actually want help on prem. And so we're just trying to listen to customers and solve their problems where they're asking us to solve them. Cut, >>Go ahead. No, I would just add that in a more vertically focused, uh, kind of orientation for us. Like we, we believe that op you know, optimization capabilities should transcend the location itself. And, and, and so whether that's part public part, private cloud, you know, that's what I love part of what I love about EKS anywhere. Uh, it, you know, you shouldn't, you should still be able to achieve optimal results that connect to your business objectives, uh, wherever those workloads, uh, are, are living >>Well, don't wince. So John and I coined this term called Supercloud and people laugh about it, but it's different. It's, it's, you know, people talk about multi-cloud, but that was just really kind of vendor diversity. Right? I got to running here, I'm running their money anywhere. Uh, but, but individually, and so Supercloud is this concept of this abstraction layer that floats wherever you are, whether it's on prem, across clouds, and you're taking advantage of those native primitives, um, and then hiding that underlying complexity. And that's what, w re-invent the ecosystem was so excited and they didn't call it super cloud. We, we, we called it that, but they're clearly thinking differently about the value that they can add on top of Goldman Sachs. Right. That to me is an example of a Supercloud they're taking their on-prem data and their, their, their software tooling connecting it to AWS. They're running it on AWS, but they're, they're abstracting that complexity. And I think you're going to see a lot, a lot more of that. >>Yeah. So Kubernetes itself, in many cases is being abstracted away. Yeah. There's a disability of a disappearing act for Kubernetes. And I don't mean that in a, you know, in an, a, from an adoption standpoint, but, uh, you know, Kubernetes itself is increasingly being abstracted away, which I think is, is actually super interesting. Yeah. >>Um, communities doesn't really do anything for a company. Like we run Kubernetes, like, how does that help your bottom line? That at the end of the day, like companies don't care that they're running Kubernetes, they're trying to solve a problem, which is the, I need to be able to deploy my applications. I need to be able to scale them easily. I need to be able to update them easily. And those are the things they're trying to solve. So if you can give them some other way to do that, I'm sure you know, that that's what they want. It's not like, uh, you know, uh, a big bank is making more money because they're running Kubernetes. That's not, that's not the current, >>It gets subsumed. It's just become invisible. Right. Exactly. You guys back to the office yet. What's, uh, what's the situation, >>You know, I, I work for my house and I, you know, we go into the office a couple of times a week, so it's, it's, uh, yeah, it's, it's, it's a crazy time. It's a crazy time to be managing and hiring. And, um, you know, it's, it's, it's, it's definitely a challenge, but there's a lot of benefits of working home. I got two young kids, so I get to see them, uh, grow up a little bit more working, working out of my house. So it's >>Nice also. >>So we're in, even as a smaller startup, we're in 26, 27 states, uh, Canada, Germany, we've got a little bit of presence in Japan, so we're very much distributed. Um, we, uh, have not gone back and I'm not sure we will >>Permanently remote potentially. >>Yeah. I mean, w we made a, uh, pretty like for us, the timing of our series B funding, which was where we started hiring a lot, uh, was just before COVID started really picking up. So we, you know, thankfully made a, a pretty good strategic decision to say, we're going to go where the talent is. And yeah, it was harder to find for sure, especially in w we're competing, it's incredibly competitive. Uh, but yeah, we've, it was a good decision for us. Um, we are very about, you know, getting the teams together in person, you know, as often as possible and in the safest way possible, obviously. Um, but you know, it's been a, it's been a pretty interesting, uh, journey for us and something that I'm, I'm not sure I would, I would change to be honest with you. Yeah. >>Well, Frank Slootman, snowflakes HQ to Montana, and then can folks like Michael Dell saying, Hey, same thing as you, wherever they want to work, bring yourself and wherever you are as cool. And do you think that the hybrid mode for your team is kind of the, the, the operating mode for the, for the foreseeable future is a couple of, >>No, I think, I think there's a lot of benefits in both working from the office. I don't think you can deny like the face-to-face interactions. It feels good just doing this interview face to face. Right. And I can see your mouth move. So it's like, there's a lot of benefits to that, um, over a chime call or a zoom call or whatever, you know, that, that also has advantages, right. I mean, you can be more focused at home. And I think some version of hybrid is probably in the industry's future. I don't know what Amazon's exact plans are. That's above my pay grade, but, um, I know that like in general, the industry is definitely moving to some kind of hybrid model. And like Matt said, getting people I'm a big fan at Mesa sphere, we ran a very diverse, like remote workforce. We had a big office in Germany, but we'd get everybody together a couple of times a year for engineering week or, or something like this. And you'd get a hundred people, you know, just dedicated to spending time together at a hotel and, you know, Vegas or Hamburg or wherever. And it's a really good time. And I think that's a good model. >>Yeah. And I think just more ETR data, the current thinking now is that, uh, the hybrid is the number one sort of model, uh, 36% that the CIO is believe 36% of the workforce are going to be hybrid permanently is kind of their, their call a couple of days in a couple of days out. Um, and the, the percentage that is remote is significantly higher. It probably, you know, high twenties, whereas historically it's probably 15%. Yeah. So permanent changes. And that, that changes the infrastructure. You need to support it, the security models and everything, you know, how you communicate. So >>When COVID, you know, really started hitting and in 2020, um, the big banks for example, had to, I mean, you would want to talk about innovation and ability to, to shift quickly. Two of the bigger banks that have in, uh, in fact, adopted Kubernetes, uh, were able to shift pretty quickly, you know, systems and things that were, you know, historically, you know, it was in the office all the time. And some of that's obviously shifted back to a certain degree, but that ability, it was pretty remarkable actually to see that, uh, take place for some of the larger banks and others that are operating in super regulated environments. I mean, we saw that in government agencies and stuff as well. >>Well, without the cloud, no, this never would've happened. Yeah. >>And I think it's funny. I remember some of the more old school manager thing people are, aren't gonna work less when they're working from home, they're gonna be distracted. I think you're seeing the opposite where people are too much, they get burned out because you're just running your computer all day. And so I think that we're learning, I think everyone, the whole industry is learning. Like, what does it mean to work from home really? And, uh, it's, it's a fascinating thing is as a case study, we're all a part of right now. >>I was talking to my wife last night about this, and she's very thoughtful. And she w when she was in the workforce, she was at a PR firm and a guy came in a guest speaker and it might even be in the CEO of the company asking, you know, what, on average, what time who stays at the office until, you know, who leaves by five o'clock, you know, a few hands up, or who stays until like eight o'clock, you know, and enhancement. And then, so he, and he asked those people, like, why, why can't you get your work done in a, in an eight hour Workday? I go home. Why don't you go in? And I sit there. Well, that's interesting, you know, cause he's always looking at me like, why can't you do, you know, get it done? And I'm saying the world has changed. Yeah. It really has where people are just on all the time. I'm not sure it's sustainable, quite frankly. I mean, I think that we have to, you know, as organizations think about, and I see companies doing it, you guys probably do as well, you know, take a four day, you know, a week weekend, um, just for your head. Um, but it's, there's no playbook. >>Yeah. Like I said, we're a part of a case study. It's also hard because people are distributed now. So you have your meetings on the east coast, you can wake up at seven four, and then you have meetings on the west coast. You stay until seven o'clock therefore, so your day just stretches out. So you've got to manage this. And I think we're, I think we'll figure it out. I mean, we're good at figuring this stuff. >>There's a rise in asynchronous communication. So with things like slack and other tools, as, as helpful as they are in many cases, it's a, it, isn't always on mentality. And like, people look for that little green dot and you know, if you're on the you're online. So my kids, uh, you know, we have a term now for me, cause my office at home is upstairs and I'll come down. And if it's, if it's during the day, they'll say, oh dad, you're going for a walk and talk, you know, which is like, it was my way of getting away from the desk, getting away from zoom. And like, you know, even in Boston, uh, you know, getting outside, trying to at least, you know, get a little exercise or walk and get, you know, get my head away from the computer screen. Um, but even then it's often like, oh, I'll get a slack notification on my phone or someone will call me even if it's not a scheduled walk and talk. Um, uh, and so it is an interesting, >>A lot of ways to get in touch or productivity is presumably going to go through the roof. But now, all right, guys, I'll let you go. Thanks so much for coming to the cube. Really appreciate it. And thank you for watching this cube conversation. This is Dave Alante and we'll see you next time.

(uplifting music) >> Hello and welcome to this Cube Conversation. I'm John Furrier, host of theCube here in Palo Alto, California. We've got two great remote guests to talk about some big news hitting with Scality and Hewlett Packard Enterprise. Jerome Lecat CEO of Scality and Chris Tinker, Distinguished Technologist from HPE, Hewlett Packard Enterprise, Jerome, Chris, great to see you both Cube alumnis from an original gangster days as we'd say back then when we started almost 11 years ago. Great to see you both. >> It's great to be back. >> Good to see you John. >> So, really compelling news around kind of this next generation storage cloud native solution. Okay, it's really kind of an impact on the next gen, I call next gen, dev ops meets application, modern application world and something we've been covering heavily. There's some big news here around Scality and HPE offering a pretty amazing product. You guys introduced essentially the next gen piece of it, Artesca, we'll get into in a second, but this is a game-changing announcement you guys announced, this is an evolution continuing I think is more of a revolution, but I think, you know storage is kind of abstractionally of evolution to this app centric world. So talk about this environment we're in and we'll get to the announcement, which is object store for modern workloads, but this whole shift is happening Jerome. This is a game changer to storage and customers are going to be deploying workloads. >> Yeah, Scality really, I mean, I personally really started working on Scality more than 10 years ago, close to 15 now. And if we think about it I mean the cloud has really revolutionized IT. And within the cloud, we really see layers and layers of technology. I mean, it all start at around 2006 with Amazon and Google and Facebook finding ways to do initially what was consumer IT at very large scale, very low credible reliability and then slowly creeped into the enterprise. And at the very beginning, I would say that everyone was kind of wizards trying things and really coupling technologies together. And to some degree we were some of the first wizard doing this, but we, we're now close to 15 years later and there's a lot of knowledge and a lot of experience, a lot of tools. And this is really a new generation. I'll call it cloud native, or you can call it next gen whatever, but there is now enough experience in the world, both at the development level and at the infrastructure level to deliver truly distributed automated systems that run on industry standard servers. Obviously good quality server deliver a better service than others, but there is now enough knowledge for this to truly go at scale. And call this cloud or call this cloud native. Really the core concept here is to deliver scalable IT at very low cost, very high level of reliability, all based on software. And we've, we've been participated in this motion, but we feel that now the breadth of what's coming is at the new level, and it was time for us to think, develop and launch a new product that's specifically adapted to that. And Chris, I will let you comment on this because the customers or some of them, you can add a customer, you do that. >> Well, you know, you're right. You know, I've been in the, I've been like you I've been in this industry for a, well, along time. Give a long, 20 to 21 years in HPE in engineering. And look at the actual landscape has changed with how we're doing scale-out software-defined storage for particular workloads. And we're a catalyst has evolved here is an analytics normally what was only done in the three letter acronyms and massively scale-out parallel namespace file systems, parallel file systems. The application space has encroached into the enterprise world where the enterprise world needed a way to actually take a look at how to, how do I simplify the operations? How do I actually be able to bring about an application that can run in the public cloud or on premise or hybrid, be able to actually look at a workload optimized step that aligns the actual cost to the actual analytics that I'm going to be doing the workload that I'm going to be doing and be able to bridge those gaps and be able to spin this up and simplify operations. And you know, and if you, if you are familiar with these parallel processes which by the way we actually have on our truck, I, I do engineer those, but they are, they are, they are they have their own unique challenges, but in the world of enterprise where customers are looking to simplify operations, then take advantage of new application, analytic workloads whether it be smart, Mesa, whatever it might be, right. I mean, if I want to spin up a Mongo DB or maybe maybe a, you know, last a search capability how do I actually take those technologies, embrace a modern scale-out storage stack that without without breaking the bank, but also provide a simple operations. And that's, that's why we look for object storage capabilities because it brings us this massive parallelization. Back to you John. >> Well before we get into the product. I want to just touch on one thing Jerome you mentioned, and Chris, you, you brought up the DevOps piece next gen, next level, whatever term you use. It is cloud native, cloud native has proven that DevOps infrastructure is code is not only legit. It's being operationalized in all enterprises and add security in there, you have DevSecOps, this is the reality and hybrid cloud in particular has been pretty much the consensus is that standard. So our defacto center whatever you want to call it, that's happening. Multicloud are on the horizon. So these new workloads are have these new architectural changes, cloud on premises and edge. This is the number one story. And the number one challenge all enterprises are now working on. How do I build the architecture for the cloud on premises and edge? This is forcing the DevOps team to flex and build new apps. Can you guys talk about that particular trend? And is it, and is that relevant here? >> Yeah, I, I now talk about really storage anywhere and cloud anywhere and and really the key concept is edge to go to cloud. I mean, we all understand now that the edge will host a lot of that time and the edge is many different things. I mean, it's obviously a smartphone, whatever that is, but it's also factories, it's also production. It's also, you know, moving moving machinery, trains, planes, satellites that that's all the edge, cars obviously. And a lot of that I will be both produced and process there, but from the edge who will want to be able to send the data for analysis, for backup, for logging to a call, and that call could be regional, maybe not, you know, one call for the whole planet, but maybe one corporate region the state in the U.S. And then from there you will also want to push some of the data to public cloud. One of the thing that we see more and more is that the D.R that has centered the disaster recovery is not another physical data center. It's actually the cloud, and that's a very efficient infrastructure very cost efficient, especially. So really it, it, it's changing the paradigm on how you think about storage because you really need to integrate these three layers in a consistent approach especially around the topic of security because you want the data to be secure all along the way. And data is not just data, its data, and who can access the data, who can modify the data what are the conditions that allow modification all automatically erasure of the data? In some cases, it's super important that the data automatically erased after 10 years and all this needs to be transported from edge to core to cloud. So that that's one of the aspects. Another aspects that resonates for me with what you said is a word you didn't say, but it's actually crucial this whole revolution. It's Kubernetes I mean, Kubernetes is in now a mature technology, and it's, it's just, you know the next level of automatized operation for distributed system, which we didn't have 5 or 10 years ago. And that is so powerful that it's going to allow application developers to develop much faster system that can be distributed again edge to go to cloud, because it's going to be an underlying technology that spans the three layers. >> Chris, your thoughts hybrid cloud. I've been, I've been having questions with the HPE folks for God years and years on hybrid clouds, now here. >> Right (chuckles) >> Well, you know, and, and it's exciting in a layout right, so you look at like a, whether it be enterprise virtualization, that is a scale-out general purpose virtualization workloads whether it be analytic workloads, whether it be no data protection is a paramount to all of this, orchestration is paramount. If you look at that DevSecOps, absolutely. I mean, securing the actual data the digital last set is, is absolutely paramount. And if you look at how we do this look at the investments we're making, we're making enough and look at the collaborative platform development which goes to our partnership with Scality. It is, we're providing them an integral aspect of everything we do, whether we're bringing in Ezmeral which is our software we use for orchestration look at the veneer of its control plane, controlling Kubernetes. Being able to actually control the active clusters and the actual backing store for all the analytics that we just talked about. Whether it be a web-scale app that is traditionally using a politics namespace and now been modernized and take advantage of newer technologies running an NBME burst buffers or a hundred gig networks with Slingshot network of 200 and 400 gigabit looking at how do we actually get the actual analytics, the workload to the CPU and have it attached to the data at risk. Where's the data, how do we land the data? How do we actually align, essentially locality, locality of the actual asset to the computer. And this is where, you know, we can look leverage whether it be a Zair or Google or name your favorite hybrid, hyperscaler, leverage those technologies leveraging the actual persistent store. And this is where Scality is, with this object store capability has it been an industry trendsetter, setting the actual landscape of how provide an object store on premise and hybrid cloud run it in a public cloud, but being able to facilitate data mobility and tie it back to, and tie it back to an application. And this is where a lot of things have changed in the world of analytics, because the applications that you, the newer technologies that are coming on the market have taken advantage of this particular protocol as threes. So they can do web scale massively parallel concurrent workloads. >> You know what let's get into the announcement. I love cool and relevant products. And I think this hits the mark. Scality you guys have Artesca, which is just announced. And I think it, you know, we obviously we reported on it. You guys have a lightweight true enterprise grade object store software for Kubernetes. This is the announcement, Jerome, tell us about it. What's the big deal? Cool and relevant, come on, this is cool. Right, tell us. >> I'm super excited. I'm not sure, if you can see it as well on the screen, but I'm super, super excited. You know, we, we introduced the ring 11 years ago and they says our biggest announcements for the past 11 years. So yes, do pay attention. And, you know, after, after looking at, at all these trends and understanding where we see the future going. We decided that it was time to embark (indistinct) So there's not one line of code that's the same as our previous generation product. They will both exist, they both have a space in the market. And Artesca was specifically designed for this cloud native era. And what we see is that people want something that's lightweight especially because it had to go to the edge. They still want the enterprise grid that Scality is known for. And it has to be modern. What we really mean by modern is, we see object storage now being the primary storage for many application more and more applications. And so we have to be able to deliver the performance, that primary storage expects. This idea of a Scality of serving primary storage is actually not completely new. When we launched Scality 10 years ago, the first application that we were supporting was consumer email for which we were, and we are still today, the primary storage. So we have, we know what it is to be the primary store. We know what's the level of reliability you need to hit. We know what, what latency means and latency is different from throughput, you really need to optimize both. And I think that still today we're the only object storage company that protects data from both replication and original encoding Because we understand that replication is faster, but the original encoding is more better, and more, of file where fast internet latency doesn't matter so much. So we we've been being all that experience, but really rethinking of product for that new generation that really is here now. And so where we're truly excited, I guess people a bit more about the product. It's a software, Scality is a software company and that's why we love to partner with HPE who's producing amazing servers, you know for the record and the history. The very first deployment of Scality in 2010 was on the HP servers. So this is a long love story here. And so to come back to our desk is lightweight in the sense that it's easy to use. We can start small, we can start from just one server or one VM I mean, you would start really small, but he can grow infinitely. The fact that we start small, we didn't, you know limit the technology because of that. So you can start from one to many and it's cloud native in the sense that it's completely Kubernetes compatible it's Kubernetes office traded. It will deploy on many Kubernetes distributions. We're talking obviously with Ezmeral we're also talking with zoo and with the other all those of communities distribution it will also be able to be run in the cloud. Now, I'm not sure that there will be many true production deployment of Artesca going the cloud, because you already have really good object storage by the cloud providers but when you are developing something and you want to test that, you know just doing it in the cloud is very practical. So you'll be able to deploy our Kubernetes cloud distribution, and it's more than object storage in the sense that it's application centric. A lot of our work is actually validating that our storage is fit for this single purpose application. And making sure that we understand the requirement of these application, that we can guide our customers on how to deploy. And it's really designed to be the primary storage for these new workloads. >> The big part of the news is your relationship with Hewlett Packard Enterprise is some exclusivity here as part of this and as you mentioned the relationship goes back many, many years. We've covered the, your relationship in the past. Chris also, you know, we cover HP like a blanket. This is big news for HPE as well. >> This is very big news. >> What is the relationship, talk about this exclusivity Could you share about the partnership and the exclusivity piece? >> Well, there's the partnership expands into the pan HPE portfolio. we look, we made a massive investment in edge IOT device. So we actually have how did we align the cost to the demand. Our customers come to us, wanting to looking at think about what we're doing with Greenlake, like in consumption based modeling. They want to be able to be able to consume the asset without having to do a capital outlay out of the gate. Number two, look at, you know how do you deploy technology, really demand. It depends on the scale, right? So in a lot of your web skill, you know, scale out technologies, it putting them on a diet is challenging. Meaning how skinny can you get it. Getting it down into the 50 terabyte range and then the complexities of those technologies at as you take a day one implementation and scale it out over you know, you know, multiple iterations over quarters, the growth becomes a challenge so working with Scality we, we believe we've actually cracked this nut. We figured out how to a number one, how to start small, but not limit a customer's ability to scale it out incrementally or grotesquely. You can eat depending on the quarters, the month, whatever whatever the workload is, how do you actually align and be able to consume it? So now whether it be on our Edgeline products our DL products go right there, now what that Jerome was talking about earlier you know, we, we, we ship a server every few seconds. That won't be a problem. But then of course, into our density optimized compute with the Apollo products. And this where our two companies have worked in an exclusivity where they scale the software bonds on the HP ecosystem. And then we can, of course provide you, our customers the ability to consume that through our GreenLake financial models or through a CapEx partners. >> Awesome, so Jerome and, and Chris, who's the customer here obviously, there's an exclusive period. Talk about the target customer and how the customers get the product and how they get the software. And how does this exclusivity with HP fit into it? >> Yeah, so there there's really a three types of customers and we've really, we've worked a lot with a company called UseDesign to optimize the user interface for each the types of customers. So we really thought about each customer role and providing with each of them the best product. So the, the first type of customer are application owners who are deploying an application that requires an object storage in the backend, you typically want a simple object store for one application, they want it to be simple and work. Honestly they want no thrill, just want an object store that works. And they want to be able to start as small as they start with their application. Often it's, you know, the first deployment maybe a small deployment, you know applications like a backup like VML, Rubrik, or analytics like (indistinct), file system that now, now available as a software, you know like CGI does a really great departmental NAS that works very well that needs an object store in the backend. Or for high performance computing a wake-up house system is an amazing file system. We will also have vertical application like road peak, for example, who provides origin and the view of the software broadcasters. So all these are application, they request an object store in the backend and you just need a simple high-performance working well object store and I'll discuss perfect for that. Now, the second type of people that we think will be interested by Artesca are essentially developer who are currently developing some capabilities or cloud native application, your next gen. And as part of their development stack, it's getting better and better when you're developing a cloud native application to really target an object storage rather than NFS, as you're persistent. It just, you know, think about generations of technologies and NFS and filesystem were great 25 years ago. I mean, it's an amazing technology. Now, when you want to develop a distributed scalable application object storage is a better fit because it's the same generation. And so same thing, I mean, you know, they're developing something they need an object store that they can develop on. So they want it very lightweight, but they also want the product that their enterprise or their customers will be able to rely on for years and years on. And this guy's really great fit to do that. The third type of customer are more architects, I would say are the architects that are designing a system where they are going to have 50 factories, a thousand planes, a million cars, they are going to have some local storage which will they want to replicate to the core and possibly also to the cloud. And as the design is really new generation workloads that are incredibly distributed but with local storage Artesca are really great for that. >> And tell about the HPE exclusive Chris. What's the, how does that fit in? Do they buy through Scality? Can they get it for the HP? Are you guys working together on how customers can procure it? >> Both ways, yeah both ways they can procure it through Scality. They can secure it through HPE and it's, it's it's the software stack running on our density optimized compute platforms which you would choose and align those and to provide an enterprise quality. Cause if it comes back to it in all of these use cases is how do we align up into a true enterprise stack, bringing about multitenancy bringing about the, the, the fact that you know, if you look at like a local coding one of the things that they're bringing to it, so that we can get down into the DL325. So with the exclusivity, you actually get choice. And that choice comes into our entire portfolio whether it be the Edgeline platform the DL325 AMD processing stack or the Intel 380, or whether it be the Apollos or like I said, there's, there's, there's so many ample choices there that facilitate this, and it's this allows us to align those two strategies. >> Awesome, and I think the Kubernetes piece is really relevant because, you know, I've been interviewing folks practitioners and Kubernetes is very much maturing fast. It's definitely the centerpiece of the cloud native both below the, the line, if you will below under the hood for the, for the infrastructure and then for apps, they want a program on top of it that's critical. I mean, Jerome, this is like, this is the future. >> Yeah, and if you don't mind like to come back to the myth on the exclusivity with HP. So we did a six month exclusive and the very reason we could do this is because HP has such breadth of server portfolio. And so we can go from, you know, really simple, very cheap you know, DL380, machine that we tell us for a few dollars. I mean, it's really like simple system, 50 terabyte. We can have the DL325 that Chris mentioned that is really a powerhouse all NVME, clash over storage is NVME, very fast processors you know, dense, large, large system, like the APOE 4,500. So it's a very large graph of portfolio. We support the whole portfolio and we work together on this. So I want to say that you know, one of the reason I want to send kudos to HP for the breadth of their server line really. As mentioned, Artesca can be ordered from either company. In hand-in-hand together, so anyway, you'll see both of us and our field working incredibly well together. >> Well, just on that point, I think just for clarification was this co-design by Scality and HPE, because Chris you mentioned, you know, the, the configuration of your systems. Can you guys, Chris quickly talk about the design. >> From, from, from the code base the software is entirely designed and developed by Scality, from testing and performance, so this really was a joint work with HP providing both a hardware and manpower so that we could accelerate the testing phase. >> You know, Chris HPE has just been doing such a great job of really focused on this. I know I've been covering it for years before it was fashionable. The idea of apps working no matter where it lives, public cloud, data center, edge. And you mentioned edge line's been around for awhile, you know, app centric, developer friendly, cloud first, has been an HPE kind of guiding first principle for many, many years. >> Well, it has. And, you know, as our CEO here intended, by 2022 everything will be able to be consumed as a service in our portfolio. And then this stack allows us the simplicity and the consumability of the technology and the granulation of it allows us to simplify the installation. Simplify the actual deployment bringing into a cloud ecosystem, but more importantly for the end customer. They simply get an enterprise quality product running on an optimized stack that they can consume through a orchestrated simplistic interface. That customers that's what they're wanting for today's but they come to me and ask, hey how do I need a, I've got this new app, new project. And, you know, it goes back to who's actually coming. It's no longer the IT people who are actually coming to us. It's the lines of business. It's that entire dimension of business owners coming to us, going this is my challenge. And how can you, HPE help us? And we rely on our breadth of technology, but also our breadth of partners to come together in our, of course Scality is hand in hand and our collaborative business unit our collaborative storage product engineering group that actually brought, brought this to market. So we're very excited about this solution. >> Chris, thanks for that input and great insight. Jerome, congratulations on a great partnership with HPE obviously great joint customer base. Congratulations on the product release here. Big moving the ball down the field, as they say. New functionality, clouds, cloud native object store. Phenomenal, so wrap, wrap, wrap up the interview. Tell us your vision for Scality and the future of storage. >> Yeah, I think I started in, Scality is going to be an amazing leader, it is already. But yeah, so, you know I have three things that I think will govern how storage is going. And obviously Marc Andreessen said it software is everywhere and software is eating the world. So definitely that's going to be true in the data center in storage in particular, but the three trends that are more specific are first of all, I think that security performance and agility is now basic expectation. It's, it's not, you know it's not like an additional feature. It's just the basic tables, security performance and our job. The second thing is, and we've talked about it during this conversation is edge to go. You need to think your platform with edge, core and cloud. You know, you, you don't want to have separate systems separate design interface point for edge and then think about the core and then think about cloud, and then think about the diverse power. All this needs to be integrated in a design. And the third thing that I see as a major trend for the next 10 years is data sovereignty. More and more, you need to think about where is the data residing? What are the legal challenges? What is the level of protection, against who are you protected? What is your independence strategy? How do you keep as a company being independent from the people you need to be in the band? And I mean, I say companies, but this is also true for public services. So these, these for me are the three big trends. And I do believe that software defined distributed architecture are necessary for these trends but you also need to think about being truly enterprise grade. and that has been one of our focus with design of Artesca. How do we combine a lightweight product with all of the security requirements and data sovereignty requirements that we expect to have in the next thing? >> That's awesome. Congratulations on the news Scality, Artesca. The big release with HPE exclusive for six months, Chris Tinker, Distinguished Engineer at HPE. Great to see you Jerome Lecat CEO of Scality, great to see you as well. Congratulations on the big news. I'm John Furrier from theCube. Thanks for watching. (uplifting music)

>>from San Francisco. It's the queue every day to thank you. Brought to you by day to like you. Hey, >>welcome back already, Jeffrey. Here with the Cube were a day to IQ's headquarters in downtown San Francisco. They used to be metal sphere, which is what you might know them as. And they've rebranded earlier this year. And they're really talking about helping Enterprises in their journey to cloud native. And we're really excited to have really one of the product guys he's been here and seeing this journey and how through with the customers and helping the company transforming his Chandler hosing tonight. He's the s VP of engineering and product. Chandler, great to see you. Thanks. So, first off, give everyone kind of a background on on the day to like you. I think a lot of people knew mesosphere. You guys around making noise? What kind of changed in the marketplace to to do a rebranding? >>Sure. Yeah, we've been obviously, Mason's here in the past and may so so I think a lot of people watching the cube knows No, no one knows about Mace ose as as we were going along our journey as a company. We noticed that a lot of people are also asking for carbonates. Eso We've actually been working with kubernetes since I don't know 16 4017 something that for a while now and as Maur Maur as communities ecosystem starting involving mature more. We also want to jump in and take advantage of that. And we started building some products that were specific to kubernetes and eso. We thought, Look, you know, it's a little bit confusing for people May, SOS and Kubernetes and at times those two technologies were seen almost as competitive, even though we didn't always see it that way. The market saw it that way, so we said, Look, this is going too confusing for customers being called Mesa Sphere. Let's let's rebrand around Maur what we really do. And we felt like what we do is not just focus around one specific technology. We felt like we helped customers with more than that more than just may so support more than just community support, Andi said. Look, let's let's get us a name that shows what we actually do for customers, and that's really helping them take their workloads and put them on on Not just, you know, um, a source platform, but actually take their workloads, bring them into production and enterprise way. That's really ready for day two. And that's that's why we called it data. >>And let's unpack the day to, cause I think some people are really familiar with the concept of day two. And for some people, they probably never heard it. But it's a pretty interesting concept, and I think it packs a lot of meaning in it. A number of letters. I think you >>can kind of just think about it if you were writing software, right? I mean, Day zero is okay. We're gonna design it. We're gonna start playing with some ideas. We're gonna pull into different technologies. We're gonna do a POC. We're gonna build our skateboards. So to say, that's kind of your day. Zero. What do we want? Okay, we're gonna build a Data Analytics pipeline. We want spark. We're going to store data. Cassandra, we're gonna use cough. Go to pass it around. We're gonna run our containers on top of communities. That's just kind of your day. Zero idea. You get it working, you slap it on a cluster. Things are good right? Day one might be okay. Let's actually do a beta put in production in some kind of way. You start getting customers using it. But now, in Day two, after all that's done, you're like, Wait a second. Things were going wrong. Where's our monitoring? We didn't set that up. Where's our logging? Oh, I don't know. Like, >>who do we >>call this? Our container Run time, we think has above. Who do we call like? Oh, I don't know What support contract that we cut, Right? So that's the things that we want to help customers with. We want to help them in the whole journey, getting to Day two. But once they're there, we want them to be ready for day two, right? And that's what we do. >>I love it because one of my favorite quotes I've used it 1000 times. I'll do 2001 right? Is that open source is free like a puppy. Exactly for you. When you leave you guys, you're not writing a check necessarily to the to the shelter, But there's a whole lot of other check. You got a right and take care of. And I think that's such a key piece. Thio Enterprise, right. They need somebody to call when that thing breaks. >>Yeah. I mean, I haven't come from enterprise company. I was actually a customer basis Fear before I joined. Yeah, that's exactly why we're customers that we wanted. Not only that, insurance policy, but someone that partner with us as we start figuring this out, you know? I mean, just picking. You know what container run time do I want to use with communities? That one decision could take months if you're not familiar with it. And you you put a couple of your best architects on it. Go research container. You go research, cryo go research doctor. Tell me what's what's the best one we should use with kubernetes. Whereas if you're going, if you have a partnership with a company like day two, you can say, Look, I trust these. You know this company, they they're they're experts of this and they see a lot of this. Let's go with their recommendation. It's >>okay. So you got you got your white board. You've got a whole bunch of open source things going on, right? And you've got a whole bunch of initiatives and the pressure's coming down from from on high to get going, you've got containers, Asian and Cloud native and hybrid Cloud all the stuff. And then you've got some port CEO on his team trying to figure it out. You guys have a whole plethora of service is around some of these products. So as you try it and then you got the journey right and you don't start from from a standing start. You gotta go. You gotta go. So how do you map out the combination of how people progress through their journey? What are the different types of systems that they want to put in place and into, prioritize and have some type of a logical successful implementation and roll out of these things from day zero day 132? No, it's >>a great question. I think that's actually how we formed our product. Strategy is we've been doing this for a while now and we've we've gone. We've gone on this journey with really big advanced customers like ride sharing companies and large telcos customers like that. We've also gone on this journey with smaller, less sophisticated customers like, you know, industrial customers from the Midwest. Right? And those are two very, very different customers. But what's similar is they're both going on the same journey we feel like, but they're just at different places. So we wanted to build products, find the customer where they're at in their journey, and the way we see it really is just at the very beginning. It's just training, right? So we have, ah, bunch of support. We're sorry. Service is around training. Help you understand? Not just kubernetes, but the whole cloud native ecosystem. So what is all this stuff? How does it work? How does it fit together? How do I just deploy simple app to right? That's the beginning of it. We also have some products in that area as well, to help people scale their training across the whole whole organization. So that's really exciting for us once once, once that customer has their training down there like Okay, look, get I need a cluster now, like I need a destroyer of sorts and criminals itself is great, but it needs a lot of pieces to actually get it ready for prime time. And that's where we build a product called Convoy Say Okay, here is your enterprise great. Ready to go kubernetes destro right out of the box. And that product is really it's what you could use to just fiddle around with communities. It's also what you put into production right on the game. That's that's been scale tested, security tests and mixed workload tested. It's everything. So that's that's kind of our communities. Destro. So you've gotten your training. You have your destro and now you're like, OK, I actually wanna want to run some applesauce. >>Let me hold there. Is it Is it open corps? Or, you know, there's a lot of conversation in the way the boys actually >>the way we built convoy. It's a great question. The way we build convoys said, Okay, we don't We want to pick the best of breed from each of these. Have you seen the cloud native ecosystem kind of like >>by charter, high charter, whatever it is, where they have all the logos and all the different spiral thing. So it's crazy. Got thousands of logos, right? And >>we said, Look, we're gonna navigate this for you. What's the best container run time to pick. And it's It's almost as if we were gonna build this for ourselves using all open source technology. So convoys completely opens. Okay, um, there's some special sauce that we put in on how to bring these things together. Install it. But all the actual components itself is open source. Okay, so that's so if you're a customer, you're like, OK, I want open source. I don't want to be tied to any specific vendor. I want to run on Lee open. So >>yeah, I was just thinking in terms of you know, how Duke is a reference right. And you had, you know, the Horton worst cloud there and map our strategies, which were radically different in the way they actually packaged told a dupe under the covers. Yeah, >>you can think of it similar. How Cloudera per ship, Possibly where they had cdh. And they brought in a lot of open source. But they also had a lot of proprietary components to see th and what we've tried to get away from it is tying someone in tow. Us. I know that sounds counterintuitive from a business perspective, but we don't want customers to feel like if I go with D to like you. I always have to go with me to like you. I have to drink the Kool Aid, and I'm never gonna be able to get off. >>Kind of not. Doesn't really go with the open source. Exactly this stuff. It's not >>right for our customers, right? A lot of our customers want that optionality, and they don't want to feel locked in. And so when we built convoy, he said, Look, you know, if we were to start our own company, not not an infrastructure coming that we are right now, but just a software company build any kind of ab How would we approach it? And that was one of the problems we saw for We don't wanna feel like we're tied into any. >>Right. Okay, so you got to get the training, you got the products. What's >>next? What's next is if you think about the journey, you're like, OK, a lot. What we've found and this may or may not be totally true is one of the first things people like to run on committees is actually they're builds. So see, I see. And we said, How can we help with this. We looked around the market and there's a lot of great see, I see products out there right now. There's get lab, which is great partner of ours. It's a great product. There's there's your older products. Like Jenkins. There's a bunch of sass products, Travis. See all these things. But what we we wanted to do if we were customers of our own products is something that was native to Kubernetes. And so we started looking at projects like tectonic and proud. Some of these projects, right? And we said, How can we do the same thing we did with convoy where we bring these projects together and make it easy for someone to adopt these kubernetes native. See, I see tools. And we did some stuff there that we think is pretty innovative as well. And that's what that's the product we call dispatch. >>Okay. What do you got? More than just products. You've got profession service. That's right. So now >>you need help setting all this up. How do you actually bring your legacy applications to this new platform? How do you get your legacy builds onto these new build systems That that's where our service is coming the plate and kind of steer you through this whole journey. Lastly, what we next in the journey, though? Those service's compliment Really? Well, with with the kind of the rest of the product suite, right? And we didn't just stop with C i c. He said, what is the next type of work that we want to run here? Okay, so there we looked at things like red hat operators. Right? And we said, Look, red hats doing really cool thing here with this operator framework, how can we simplify it? We learn we've done a lot of this before with D. C. O s, where we built what we called the DCS sdk to help people bring advanced complex workloads onto that platform. And we saw a lot of similarities with operators to our d c West sdk. We said, How can we bring some of our understanding and knowledge to that world? And we built this open source product called kudo. Okay, people are free to go check that out. And that's how we bring more advanced workload. So if you think about the journey back to the journey again, you got some training you have your have your cluster, you put your builds on it. Now you want to run some advance work logs? That's where Kudo comes. >>Okay? And then finally, at the end of the trail is 1 800 I need help. Well, almost into the trail. We're not there yet. There was one thing they're still moving with one more step right on >>the very last one. Actually, we said, Okay, what's next in this journey? And that's running multiple clusters of the same. Okay, so that's kind of the scale. That's the end of the journey from for us, for our proxy as it stands right now. And that's where you build a product called Commander. And that's really helping us launch and manage multiple >>companies clusters at the same time. >>So it's so great that you have the perspective of a customer and you bring that directly in two. You know what you want because you just have gone through this this journey. But I'm just curious, you know, if you put your old hat on, you know, kind of c i o your customer. You know, you just talked about the cake chart with Lord knows how many logos? How do you help people even just begin to think about about the choices and about the crazy rapid change in what? That I mean? Kubernetes wasn't a thing four years ago to help them stay on top of it to help them, you know, both kind of have a night to the vision, you know, make sure you're delivering today on not just get completely distracted by every bright, shiny object that happens to come along. Yeah, no, >>I think it's really challenging for the buyers. You know, I think there's a, especially as the industry continues to make sure there's a new concept that gets thrown at all times. Service Manager. You know, some new, cool way to do monitoring or logging right? And you almost feel like a dinosaur. If you're not right on top of these things to go to a conference in, are you using? You know, you know B P f. Yet what is that? You didn't feel right? Exactly. I think I think most importantly, what customers want is the ability what, the ability to move their technology and their platforms as their business has the need. If the need isn't there for the business, and the technology is running well. There shouldn't be a reason to move to a new platform. Our new set of technologies, in fact, with dese us with Mason charities. To us, we have a lot of happy customers that are gonna be moving crib. Amazing if they wanted to anytime soon. Do you see What's that? Something's that criminal is currently doesn't do. It may never do because the community is just not focused on it that DCS is solving. And those customers just want to see that will continue to support them in the journey that they're on with their their business. And I think that's what's most important is just really understanding our customer's understanding their business, understand where they wanna go. What are their goals, So to say, for their technology platforms and and making sure you were always one step ahead >>of them, that's a >>good place to be one step ahead of demand. All right, well, thanks for for taking a few minutes and sharing the story. Appreciate it. Okay. Thank you. All right. Thanks. Chandler. I'm Jeff. You're watching >>the Cube. Where? Day two. I >>Q in downtown San Francisco. Thanks for watching. We'll see you next time

>> Announcer: Live from Orlando, Florida it's theCUBE! Covering Microsoft Ignite, brought to you by Cohesity. >> Hello, and happy taco Tuesday CUBE viewers! You are watching theCUBE's live coverage of Microsoft's Ignite here in Orlando, Florida. I'm your host Rebecca Knight, along with Stu Miniman. We're joined by Scott Hanselman, he is the partner program manager at Microsoft. Thank you so much for coming on theCUBE! >> Absolutely, my pleasure! >> Rebecca: And happy taco Tuesday to you! Will code for tacos. >> Will code for tacos. >> I'm digging it, I'm digging it >> I'm a very inexpensive coder. >> So you are the partner program manager, but you're really the people's programmer at Microsoft. Satya Nadella up on the main stage yesterday, talking about programming for everyone, empowering ordinary citizen developers, and you yourself were on the main stage this morning, "App Development for All", why is this such a priority for Microsoft at this point in time? >> Well there's the priority for Microsoft, and then I'll also speak selfishly as a priority for me, because when we talk about inclusion, what does that really mean? Well it is the opposite of exclusion. So when we mean inclusion, we need to mean everyone, we need to include everyone. So what can we do to make technology, to make programming possible, to make everyone enabled, whether that be something like drag and drop, and PowerApps, and the Power platform, all the way down to doing things like we did in the keynote this morning with C# on a tiny micro-controller, and the entire spectrum in between, whether it be citizen programmers in Excel using Power BI to go and do machine learning, or the silly things that we did in the keynote with rock, paper scissors that we might be able to talk about. All of that means including everyone and if the site isn't accessible, if Visual Studio as a tool isn't accessible, if you're training your AI in a non-ethical way, you are consciously excluding people. So back to what Satya thinks is why can't everyone do this? SatyaSacha thinks is why can't everyone do this? Why are we as programmers having any gate keeping, or you know, "You can't do that you're not a programmer, "you know, I'm a programmer, you can't have that." >> So what does the future look like, >> Rebecca: So what does the future look like, if everyone knows how to do it? I mean, do some imagining, visioning right now about if everyone does know how to do this, or at least can learn the building blocks for it, what does technology look like? >> Well hopefully it will be ethical, and it'll be democratized so that everyone can do it. I think that the things that are interesting, or innovative today will become commoditized tomorrow, like, something as simple as a webcam detecting your face, and putting a square around it and then you move around, and the square, we were like, "Oh my God, that was amazing!" And now it's just a library that you can download. What is amazing and interesting today, like AR and VR, where it's like, "Oh wow, I've never seen augmented reality work like that!" My eight-year-old will be able to do it in five years, and they'll be older than eight. >> So Scott, one of the big takeaways I had from the app dev keynote that you did this morning was in the past it was trying to get everybody on the same page, let's move them to our stack, let's move them to our cloud, let's move them on this programming language, and you really talked about how the example of Chipotle is different parts of the organization will write in a different language, and there needs to be, it's almost, you know, that service bus that you have between all of these environments, because we've spent, a lot of us, I know in my career I've spent decades trying to help break down those silos, and get everybody to work together, but we're never going to have everybody doing the same jobs, so we need to meet them where they are, they need to allow them to use the tools, the languages, the platforms that they want, but they need to all be able to work together, and this is not the Microsoft that I grew up with that is now an enabler of that environment. The word we keep coming back to is trust at the keynote. I know there's some awesome, cool new stuff about .net which is a piece of it, but it's all of the things together. >> Right, you know I was teaching a class at Mesa Community College down in San Diego a couple of days ago and they were trying, they were all people who wanted jobs, just community college people, I went to community college and it's like, I just want to know how to get a job, what is the thing that I can do? What language should I learn? And that's a tough question. They wonder, do I learn Java, do I learn C#? And someone had a really funny analogy, and I'll share it with you. They said, well you know English is the language, right? Why don't the other languages just give up? They said, you know, Finland, they're not going to win, right? Their language didn't win, so they should just give up, and they should all speak English, and I said, What an awful thing! They like their language! I'm not going to go to people who do Haskell, or Rust, or Scala, or F#, and say, you should give up! You're not going to win because C won, or Java won, or C# won. So instead, why don't we focus on standards where we can inter-operate, where we can accept that the reality is a hybrid cloud things like Azure Arc that allows us to connect multiple clouds, multi-vendor clouds together. That is all encompassing the concept of inclusion, including everyone means including every language, and as many standards as you can. So it might sound a little bit like a Tower of Babel, but we do have standards and the standards are HTTP, REST, JSON, JavaScript. It may not be the web we deserve, but it's the web that we have, so we'll use those building block technologies, and then let people do their own thing. >> So speaking of the keynote this morning, one of the cool things you were doing was talking about the rock, paper, scissors game, and how it's expanding. Tell our viewers a little bit more about the new elements to rock, paper, scissors. >> So folks named Sam Kass, a gentleman named Sam Kass many, many years ago on the internet, when the internet was much simpler web pages, created a game called Rock, Paper, Scissors, Lizard, Spock, and a lot of people will know that from a popular TV show on CBS, and they'll give credit to that show, in fact it was Sam Kass and Karen Bryla who created that, and we sent them a note and said, "Hey can I write a game about this?" And we basically built a Rock, Paper, Scissors, Lizard, Spock game in the cloud containerized at scale with multiple languages, and then we also put it on a tiny device, and what's fun about the game from a complexity perspective is that rock, paper, scissors is easy. There's only three rules, right? Paper covers rock, which makes no sense, but when you have five, it's hard! Spock shoots the Rock with his phaser, and then the lizard poisons Spock, and the paper disproves, and it gets really hard and complicated, but it's also super fun and nerdy. So we went and created a containerized app where we had all different bots, we had node, Python, Java, C#, and PHP, and then you can say, I'm going to pick Spock and .net, or node and paper, and have them fight, and then we added in some AI, and some machine learning, and some custom vision such that if you sign in with Twitter in this game, it will learn your patterns, and try to defeat you using your patterns and then, clicking on your choices and fun, snd then, clicking on your choices and fun, because we all want to go, "Rock, Paper, Scissors shoot!" So we made a custom vision model that would go, and detect your hand or whatever that is saying, this is Spock and then it would select it and play the game. So it was just great fun, and it was a lot more fun than a lot of the corporate demos that you see these days. >> All right Scott, you're doing a lot of different things at the show here. We said there's just a barrage of different announcements that were made. Love if you could share some of the things that might have flown under the radar. You know, Arc, everyone's talking about, but some cool things or things that you're geeking out on that you'd want to share with others? >> Two of the things that I'm most excited, one is an announcement that's specific to Ignite, and one's a community thing, the announcement is that .net Core 3.1 is coming. .net Core 3 has been a long time coming as we have began to mature, and create a cross platform open source .net runtime, but .net Core 3.1 LTS Long Term Support means that that's a version of .net core that you can put on a system for three years and be supported. Because a lot of people are saying, "All this open source is moving so fast! "I just upgraded to this, "and I don't want to upgrade to that". LTS releases are going to happen every November in the odd numbered years. So that means 2019, 2021, 2023, there's going to be a version of .net you can count on for three years, and then if you want to follow that train, the safe train, you can do that. In the even numbered years we're going to come out with a version of .net that will push the envelope, maybe introduce a new version of C#, it'll do something interesting and new, then we tighten the screws and then the following year that becomes a long term support version of .net. >> A question for you on that. One of the challenges I hear from customers is, when you talk about hybrid cloud, they're starting to get pulled apart a little bit, because in the public cloud, if I'm running Azure, I'm always on the latest version, but in my data center, often as you said, I want longer term support, I'm not ready to be able to take that CICD push all of the time, so it feels like I live, maybe call it bimodal if you want, but I'm being pulled with the am I always on the latest, getting the latest security, and it's all tested by them? Or am I on my own there? How do you help customers with that, when Microsoft's developing things, how do you live in both of those worlds or pull them together? >> Well, we're really just working on this idea of side-by-side, whether it be different versions of Visual Studio that are side-by-side, the stable one that your company is paying for, and then the preview version that you can go have side-by-side, or whether you could have .net Core 3, 3.1, or the next version, a preview version, and a safe version side-by-side. We want to enable people to experiment without fear of us messing up their machine, which is really, really important. >> One of the other things you were talking about is a cool community announcement. Can you tell us a little bit more about that? >> So this is a really cool product from a very, very small company out of Oregon, from a company called Wilderness Labs, and Wilderness Labs makes a micro-controller, not a micro-processor, not a raspberry pie, it doesn't run Linux, what it runs is .net, so we're actually playing Rock, Paper, Scissors, Lizard, Spock on this device. We've wired it all up, this is a screen from our friends at Adafruit, and I can write .net, so somehow if someone is working at, I don't know, the IT department at Little Debbie Snack Cakes, and they're making WinForms applications, they're suddenly now an IOT developer, 'cause they can go and write C# code, and control a device like this. And when you have a micro-controller, this will run for weeks on a battery, not hours. You go and 3D print a case, make this really tiny, it could become a sensor, it could become an IOT device, or one of thousands of devices that could check crops, check humidity, moisture wetness, whatever you want, and we're going to enable all kinds of things. This is just a commodity device here, this screen, it's not special. The actual device, this is the development version, size of my finger, it could be even smaller if we wanted to make it that way, and these are our friends at Wilderness Labs. and they had a successful Kickstarter, and I just wanted to give them a shout out, and I just wanted to give them a shoutout, I don't have any relationship with them, I just think they're great. >> Very cool, very cool. So you are a busy guy, and as Stu said, you're in a lot of different things within Microsoft, and yet you still have time to teach at community college. I'm interested in your perspective of why you do that? Why do you think it's so important to democratize learning about how to do this stuff? >> I am very fortunate and I think that we people, who have achieved some amount of success in our space, need to recognize that luck played a factor in that. That privilege played a factor in that. But, why can't we be the luck for somebody else, the luck can be as simple as a warm introduction. I believe very strongly in what I call the transitive value of friendship, so if we're friends, and you're friends, then the hypotenuse can be friends as well. A warm intro, a LinkedIn, a note that like, "Hey, I met this person, you should talk to them!" Non-transactional networking is really important. So I can go to a community college, and talk to a person that maybe wanted to quit, and give a speech and give them, I don't know, a week, three months, six months, more whatever, chutzpah, moxie, something that will keep them to finish their degree and then succeed, then I'm going to put good karma out into the world. >> Paying it forward. >> Exactly. >> So Scott, you mentioned that when people ask for advice, it's not about what language they do, is to, you know, is to,q you know, we talk in general about intellectual curiosity of course is good, being part of a community is a great way to participate, and Microsoft has a phenomenal one, any other tips you'd give for our listeners out there today? >> The fundamentals will never go out of style, and rather than thinking about learning how to code, why not think about learning how to think, and learning about systems thinking. One of my friends, Kishau Rogers, talked about systems thinking, I've hade her on my podcast a number of times, and we were giving a presentation at Black Girls Code, and I was talking to a fifteen-year-old young woman, and we were giving a presentation. It was clear that her mom wanted her to be there, and she's like, "Why are we here?" And I said, "All right, let's talk about programming "everybody, we're talking about programming. "My toaster is broken and the toast is not working. "What do you think is wrong?" Big, long, awkward pause and someone says, "Well is the power on?" I was like, "Well, I plugged a light in, "and nothing came on" and they were like, "Well is the fuse blown?" and then one little girl said "Well did the neighbors have power?", And I said, "You're debugging, we are debugging right?" This is the thing, you're a systems thinker, I don't know what's going on with the computer when my dad calls, I'm just figuring it out like, "Oh, I'm so happy, you work for Microsoft, "you're able to figure it out." >> Rebecca: He has his own IT guy now in you! >> Yeah, I don't know, I unplug the router, right? But that ability to think about things in the context of a larger system. I want toast, power is out in the neighborhood, drawing that line, that makes you a programmer, the language is secondary. >> Finally, the YouTube videos. Tell our viewers a little bit about those. you can go to D-O-T.net, so dot.net, the word dot, you can go to d-o-t.net, so dot.net, the word dot, slash videos and we went, and we made a 100 YouTube videos on everything from C# 101, .net, all the way up to database access, and putting things in the cloud. A very gentle, "Mr. Rodgers' Neighborhood" on-ramp. A lot of things, if you've ever seen that cartoon that says, "Want to draw an owl? "Well draw two circles, "and then draw the rest of the fricking owl." A lot of tutorials feel like that, and we don't want to do that, you know. We've got to have an on-ramp before we get on the freeway. So we've made those at dot.net/videos. >> Excellent, well that's a great plug! Thank you so much for coming on the show, Scott. >> Absolutely my pleasure! >> I'm Rebecca Knight, for Stu Miniman., stay tuned for more of theCUBE's live coverage of Microsoft Ignite. (upbeat music)

>> SiliconANGLE Media Presents the CUBE! Covering Alibaba's Cloud annual conference. Brought to you by Intel. Now, here's John Furrier... >> Hello there, and welcome to theCUBE here on the ground in China for Intel's booth here at the Alibaba Cloud event. I'm John Furrier, the co-founder of SiliconANGLE, Wikibon, and theCUBE. We're here with John Sakamoto who is the vice president of the Programmable Solutions Group. Thanks for stopping by. >> Thank you for having me, John. >> So FPGAs, field-programmable gate arrays, kind of a geeky term, but it's really about software these days. What's new with your group? You came to the Intel through an acquisition. How's that going? >> Yeah, so far it's been great. As being part of a company with the resources like Intel and really having access to data center customers, and some of the data center technologies and frameworks that they've developed and integrating MPJs into that, it's been a great experience. >> One of the hot trends here, I just interviewed Dr. Wong, at Alibaba Cloud, the founder, and we were talking about Intel's relationship, but one of the things he mentioned was striking to me is that, they got this big city brain IOT project, and I asked him about the compute at the Edge and how data moves around, and he said "for all the Silicon at the Edge, one piece of Silicon at the Edge is going to be 10X inside the data center, inside the cloud or data center," which is fundamentally the architecture these days. So it's not just about the Edge, it's about how the combination of software and compute are moving around. >> Right. >> That means that data center is still relevant for you guys. What is the impact of FPGA in the data center? >> Well, I think FPGA is really our great play in the data center. You mentioned City Brain. City Brain is a great example where they're streaming live video into the data center for processing, and that kind of processing power to do video live really takes a lot of horsepower, and that's really where FPGAs come into play. One of the reasons that Intel acquired Altera was really to bring that acceleration into the data center, and really that is a great complement to Xeon's. >> Take a minute on FPGA. Do you have to be a hardware geek to work with FPGA? I mean, obviously, software is a big part of it. What's the difference between the hardware side and the software side on the programmability? >> Yes, that's a great question. So most people think FPGAs are hard to use, and that they were for hardware geeks. The transitional flow had been using RTL-based flows, and really what we've recognized is to get FPGA adoption very high within the data center, we have to make it easier, and we've invested quite a bit in acceleration stacked to really make it easier for FPGAs to be used within the data center. And what we've done is we've created frameworks and pre-optimized accelerators for the FPGAs to make it easy for people to access that FPGA technology. >> What's the impact of developers because you look at the Acceleration Stack that you guys announced last month? >> Yes, that's correct. >> Okay, so last month. This is going to move more into software model. So it's almost programmability as a dev-ops, kind of a software mindset. So the hardware can be programmed. >> Right. >> What's the impact of the developer make up, and how does that change the solutions? How does that impact the environment? >> So the developer make up, what we're really targeting is guys that really have traditionally developed software, and they're used to higher level frameworks, or they're used to designing INSEE. So what we're trying to do is really make those designers, those developers, really to be able to use those languages and frameworks they're used to and be able to target the FPGA. And that's what the acceleration stack's all about. And our goal is to really obfuscate that we actually have an FPGA that's that accelerator. And so we've created, kind of, standard API's to that FPGA. So they don't really have to be an FPGA expert, and we've taken things, basically standardized some things like the connection to the processor, or connections to memory, or to networking, and made that very easy for them to access. >> We see a lot of that maker culture, kind of vibe and orientation come in to this new developer market. Because when you think of a field-programmable gate array, the first thing that pops into my mind is oh my God, I got to be a computer engineering geek. Motherboards, the design, all these circuits, but it's really not that. You're talking about Acceleration-as-a-Service. >> That's right. >> This is super important, because this brings that software mindset to the marketplace for you guys. So talk about that Accelerations-as-a-Service. What is it? What does it mean? Define it and then let's talk about what it means. >> Yeah. Okay, great. So Acceleration-as-a-Service is really having pre-optimized software or applications that really are running on the FPGA. So the user that's coming in and trying to use that acceleration service, doesn't necessarily need to know there's an FPGA there. They're just calling in and wanting to access the function, and it just happens to be accelerated by the FPGA. And that's why one of the things we've been working with with Alibaba, they announce their F1 service that's based on Intel's Arria 10 FPGAs. And again we've created a partner ecosystem that have developed pre-optimized accelerators for the FPGA. So users are coming in and doing things like Genomics Sequencing or database acceleration, and they don't necessarily need to know that there's an FPGA actually doing that acceleration. >> So that's just a standard developer just doing, focusing in on an app or a use case with big data, and that can tap into the hardware. >> Absolutely, and they'll get a huge performance increase. So we have a partner in Falcon Computing, for example, that can really increase the performance of the algorithm, and really get a 3X improvement in the overall gene sequencing. And really improve the time it takes to do that. >> Yeah, I mean, Cloud and what you're doing is just changing society. Congratulations, that's awesome. Alright, I want to talk about Alibaba. What is the relationship with Intel and Alibaba? We've been trying to dig that out on this trip. For your group, obviously you mentioned City Brain. You mentioned the accelerations of service, the F1 instances. >> Right. >> What specifically is the relationship, how tight is it? What are you guys doing together? >> Well the Intel PSG group, our group, has been working very closely with Alibaba on a number of areas. So clearly the acceleration, the FPGA acceleration is one of those areas that are big, big investors. We announced the Arria 10 version today, but will continue to develop with them in the next generation Intel FPGAs, such as Stratix 10 which is based on 14 nanometer. And eventually with our Falcon Mesa product which is a 10 nanometer product. So clearly, acceleration's a focus. Building that ecosystem out with them is going to be a continued focus. We're also working with them on servers and trying to enhance the performance >> Yeah. >> of those servers. >> Yeah. >> And I can't really talk about the details of all of those things, but certainly there are certain applications that FPGAs, they're looking to accelerate the overall performance of their custom servers, and we're partnering with them on that. >> So one of the things I'm getting out of this show here, besides the conversion stuff, eCommerce, entertainment, and web services which is Alibaba's, kind of like, aperture is that it's more of a quantum mindset. And we talked about Blockchain in my last interview. You see quantum computing up on their patent board. >> Yeah. >> Some serious IT kinds of things, but from a data perspective. How does that impact your world, because you provide acceleration. >> Right. >> You got the City Brains thing which is a huge IOT and AI opportunity. >> Right. >> How does someone attack that solution with FPGAs? How do you get involved? What's your role in that whole play? >> Again, we're trying to democratize FPGAs. We're trying to make it very easy for them to access that, and really that's what working with Alibaba's about. >> Yeah. >> They are enabling FPGA access via their Cloud. Really in two aspects, one which we talked about which we have some pre-optimized accelerators that people can access. So applications that people can access that are running on FPGAs. But we're also enabling a developer environment where people can use the tradit RTL flow, or they can use an OpenCL Flow to take their code, compile it into the FPGA, and really get that acceleration that FPGAs can provide. So it's not only building, bringing that ecosystem accelerators, but also enabling developers to develop on that platform. >> You know, we do a lot of Cloud computing coverage, and a lot of people really want to know what's inside the Cloud. So, it's one big operation, so that's the way I look at it. But there's a lot going on there under the hood. What is some of the things that Alibaba's saying to you guys in terms of how the relationship's translating into value for them. You've mentioned the F1 instances, any anecdotal soundbites you can share on the feedback, and their direction? >> Yeah, so one of the things they're trying to do is lower the total TCO of the data center. And one of the things they have is when you look at the infrastructure cost, such as networking and storage, these are cycles that are running on the processor. And when there's cycles running on the processor, they monetize that with the customers. So one of the areas we're working with is how do we accelerate networking and storage functions on a FPGA, and therefore, freeing up HORVS that they can monetize with their own customers. >> Yeah. >> And really that's the way we're trying to drop the TCO down with Alibaba, but also increase the revenue opportunity they have. >> What's some updates from the field from you guys? Obviously, Acceleration's pretty hot. Everyone wants low latency. With IOT, you need to have low latency. You need compute at the edge. More application development is coming in with Vertical Specialty, if you will. City Brains is more of an IOT, but the app is traffic, right? >> Yeah. >> So that managing traffic, there's going to be a million more use cases. What are some of the things that you guys are doing with the FPGAs outside of the Alibaba thing. >> Well I think really what we're trying to do is really focus on three areas. If you look at, one is to lower the cost of infrastructure which I mentioned. Networking and storage functions that today people are using running those processes on processors, and trying to lower that and bring that into the FPGA. The second thing we're trying to do is, you look at high cycle apps such as AI Applications, and really trying to bring AI really into FPGAs, and creating frameworks and tool chains to make that easier. >> Yeah. >> And then we already talked about the application acceleration, things like database, genomics, financial, and really those applications running much quicker and more efficiently in FPGAs. >> This is the big dev-ops movement we've seen with Cloud. Infrastructure as code, it used to be called. I mean, that's the new normal now. Software guys programming infrastructure. >> Absolutely. >> Well congratulations on the great step. John Sakamoto, here inside theCUBE. Studios here at the Intel booth, we're getting all the action roving reporter. We had CUBE conversations here in China, getting all the action about Alibaba Cloud. I'm John Furrier, thanks for watching.

from Seattle Washington extracting the signal from the noise it's the cube on the ground at OpenStack days Seattle 2015 now here's your host John furrier hello and welcome to Seattle this is a special Q presentation cube on the ground OTG we call it on the ground we go out to the event and talk to all the thought leader I'm John far with the QNX arendelle with SolidFire also the famous cloudcast podcast great to see you again I know good to see John cloudcast is a hot podcast all the thought leaders are listening customers are listening guys are really the signal out there on cloud and also SolidFire growing yes all flash storage you gotta kick in some but they're always keeping tabs on you guys new approach the cloud what's going on with cloud give us the update of OpenStack what's the bottom line I mean is it failing is it winning is it growing is it stalled what do we expect to see ya know so it's at an interesting point because it absolutely is growing but it still has some operational challenges that's the number one thing we're seeing right now is actually just talking to some folks in the hall of common theme is you're still trying to figure how to upgrade it easily still figuring how to operate it easily right and the gentleman from canonical made that made the the reference you know ketchup right everyone has the in green stuff in your kitchen but no one makes their ketchup right and I thought that was fantastic because it's you know everyone's kind of looking for that easy button and it's starting to show up you know you've got you the blue box folks you've got the platform nine folks you've got some interesting startups actually coming into the OpenStack space which shows us there is some definitely some innovation and some new things going on but it's because of the challenges we faced until now the question is the ketchup good I mean is that last ingredient going to make it so that it's not too watery I mean is Cooper Nettie's is containers so truly is it good ketchup and yeah what's the next was the key ingredient well yeah and that's that's a fantastic point because we are at this inflection point where OpenStack was a necessary next that without a doubt we had to get that first step into cloud native applications had to do it but where we're going with Mesa sand cabrion at ease with mesa con going on down the street is that the true next evolution is it like the OpenStack Murano project where you're kind of getting containers built into OpenStack we'll have to wait and see because that anytime you talk to burn a DS anytime you talk Mesa that's is so cutting edge so at this point I'm still Silicon Valley home so OpenStack obviously meme of a sec being dead is kind of falls we saw some things happen last year so it opens dec sv some people aren't going to be there this year that were there last year yes either went out of business or executives have left but yet a lot of dynamics going on palma risks is stepping down as CEO of cloud pivotal cloud foundry cleans 100 million dollars in revenue leather to see those books but but the question now see amazon is doing their thing and but it's really a dynamic market right now so so it's there yes the question is who's doing what in revenue what's the numbers is it all professional surgery and cloud found your hundred million that's a huge number i just is that all professional services do they actually selling product yeah and that's a fantastic moment because the m the cloud cast we saw this consolidation coming for a long time we really started covering OpenStack about four years ago and we were just waiting for at some point you know when we first started there was 15 plus startups in the OpenStack space and there just wasn't enough customers there there wasn't enough revenue there and you just saw this natural consolidation come to a head last year and yeah some are no longer here a lot of them were sucked up into the various vendors and what you're seeing now is especially at the OpenStack summits and like these events here you have a much more mature ecosystem it's almost like the new legacy of you know all of these vendors are there they're all mature they're trying to play in this space they're trying to make money off of it and time will tell and then it's an evolution anybody brought to point you right over the easy button what is that easy button now is it just deployment in a box is it like just give me prefabricated OpenStack is it tooling is it management we're hearing a lot of different things yeah and I think time will tell but I do think the preference we're seeing in our customers is definitely moving towards that easy button as a service if you will of some of those companies where the operations have open stack because it hasn't gotten easier at the same level of the adoption people are looking to what is that next step if the operations were to get easier i don't think we'd see that market be as popular as it is right now is it is the market still in early adopter that's the thing that's on my mind has it crossed over yet I think it has I think we're at least in OpenStack context where we're beyond early adopter phase there is a lot of folks out there using it but what's interesting is is to kind of go back around to the previous question a little bit the district's taken off like I think they probably should have most of the large customers I've seen are still roll your own and it is still that staff of Engineers really keeping up and running and again because the what was the value-added the distributions we're starting to see the Red Hat distribution get a you know to that point where we're getting good adoption of that we're seeing the marantis one with all the fuel work they're doing we're getting good adoption with that so the question on adoption is it's either not Oh people aren't aware of it or the product sucks so is it mix of both is it awareness issue or is it a product issue oh that's a great question i think it's a it's a question of differentiation I don't know that it's differentiated enough at this point in time it's it's you know if you go build your own versus you farm it out if you will completely big differences right but it's almost like shades who could be fear yeah it could be a third dimension you could absolutely be fear well that's the thing you've been the issue solution of operators we hear a lot of an operator so the question is if I'm an engineering team I might want to have my tire kickers go through the motions and that's not necessary approval con so that's just core competency building so that fear could be an issue of cork opera so maybe they're aware of it maybe the products decent maybe it's just that their team's not core enough to do that yeah when it comes to the folks in house um yeah again going back to the easy button what we really need in the opposite community is that POC in a box and that's probably there today don't get me wrong but but everyone sees that POC in a box but then they're afraid of does that mean can I scale it out to 100 nodes a thousand nodes and will it be as easy and it's almost gotten a reputation now of know and and so how do we get it to grow to 100 notes thousand nodes whatever you want and do the business value out of I don't need a big staff of people and how do I get you know the underlying infrastructure to be simpler at the end of the day a little cloud cast we got going on here I mean I think in my opinion my opinion I think it's just a matter of the customers having the ability to execute and have the total cost of ownership equation nailed I think there's still this gray area of there's no straight and narrow on on the execution what's my cost i'm gonna be locked into that vendor what's going to be the lock-in oh my god yeah the shark fin the iceberg whatever metaphor you want to use yes no is that reading is their visibility on the ownership side because downstream what's the impact well it what's interesting there too is the biggest thing I'm seeing is for again from an operation standpoint how do we make this as simple as possible because what happens is you have this weird convoluted thing if you have the whole legacy apps versus cloud native apps and you take that put it aside for a second rank if we take that and put it aside well what what do they really want doesn't matter what kind of app it is well the developers want API driven infrastructure you can call it cloud but the end of the day it's it's an infrastructure that's driven by api's and then as simple as possible you know being able to really guarantee the uptime guarantee the performance and that's where OpenStack at times it gets a bad rap I don't and I'm not even necessarily agreeing with that might not even be worthy of a bad rap in that agreed absolutely because there are known customers out there that are doing it and doing it very well but again is how do you get beyond that room well Stu miniman I'm Wikibon and Brian Grace Lee and now Wikibon and and I Robin conversation about this and I think Dave vellante even chimed in and we were debating was up across the board different opinions yes what the hell is cloud native app mean you know is it is amazonas cloudy of course they're cloud Facebook a cloud native app okay but what does that mean for enterprises that mean that the app was built for just API so to me it just doesn't seen it's been a lot of there's not a lot of cloud native apps out there right now or are now what is a cloud yeah and and it's a fantastic question and my opinion have always been you know there's there was this kind of trend in the industry how do I take these legacy apps and make them cloud native well the simple answer is you don't the way I look at it is it's really more of like a star of the old build the new mentality you you want to maintain those legacy systems but the same time as those kind of age off the books if you will you're going to have to build a new infrastructure so if you're going to build new infrastructure you might as well build it the new way but that has to happen over time that is not something that happens you know most businesses out there today they don't do technology for the sake of technology there has to be a business reason and a business driver if that legacy app is still out there making them money they're going to keep using I not untrue to your point it's you cloud native is the future the soil asked of you know yeah yield some fruit on that tree if you will so that's going to take some time exactly so so you know I very much see this as a longer tail that most people would like without a doubt it is just a matter of how are we going to get their long-term and yeah there's lots of terminology and the cloud native and what does that mean big picture and architectural II that's all solved it's getting the businesses to rewrite the apps and really give them Aaron we're in Seattle right now on the ground so quickly describe to the folks out there what's the vibe here what's it like a Seattle it's been it is so it's been interesting I've been in here since tuesday now and i've done lenox con cloudstack day OpenStack day and mesa con all in the in three days now so it's what did you learn yeah it's been a world in 30-second I know yeah so it the biggest thing is there is still a lot of confusion in yes people are starting to get legacy versus cloud native but when it comes to which technologies do i use why would i use them what are the actual business drivers to actually go adopt some of these new technologies massive amounts of confusion around that and that's probably the biggest reason for you know trying to get knowledge out in the industry without a doubt okay we are OTG on the ground this is the cube in Seattle I'm John for thanks for watching and all the coverage here at OpenStack innovation day thanks for watching