>> Announcer: From around the globe, it's theCUBE with digital coverage of AWS Public Sector Partner Awards Brought to you by Amazon Web Services. >> All right, welcome back to "the Cube's" coverage here from Palo Alto, California in our studio with remote interviews during this time of COVID-19 with our quarantine crew. I'm John Furrier, your host of "the Cube" and we have here the award winners for the best EDU solution from NorthBay Solutions, Jim Keller, the president and from Harvard Business Publishing and the University of Pittsburgh, Chad Burton, PhD and Data Privacy Officer of University of Pittsburgh IT. Thanks for coming on gentlemen, appreciate it. >> Thank you. >> So, Jim, we'll start with you. What is the solution that you guys had got the award for? And talk about how it all came about. >> Yeah, thank you for asking and it's been a pleasure working with Chad and the entire UPitt team. So as we entered this whole COVID situation, our team really got together and started to think about how we could help AWS customers continue their journey with AWS, but also appreciate the fact that everyone was virtual, that budgets were very tight, but nonetheless, the priorities remained the same. So we devised a solution which we called jam sessions, AWS jam sessions, and the whole principle behind the notion is that many customers go through AWS training and AWS has a number of other offerings, immersion days and boot camps and other things, but we felt it was really important that we brought forth a solution that enables customers to focus on a use case, but do it rapidly in a very concentrated way with our expert team. So we formulated what we call jam sessions, which are essentially very focused two week engagements, rapid prototyping engagements. So in the context of Chad and UPitt team, it was around a data lake and they had been, and Chad will certainly speak to this in much more detail, but the whole notion here was how does a customer get started? How does, a customer prove the efficacy of AWS, prove that they can get data out of their on premises systems, get it into AWS, make it accessible in the form, in this case, a data lake solution and have the data be consumable. So we have an entire construct that we use which includes structured education, virtual simultaneous rooms where development occurs with our joint rep prototyping teams. We come back again and do learnings, and we do all of this in the construct of the agile framework, and ideally by the time we're done with the two weeks, the customer achieves some success around achieving the goal of the jam session. But more importantly, their team members have learned a lot about AWS with hands on work, real work, learn by doing, if you will, and really marry those two concepts of education and doing, and come out of that with an opportunity then to think about the next step in that journey, which in this case would be the implementation of a data lake in a full scale project kind of initiative. >> Chad, talk about the relationship with NorthBay Solutions. Obviously you're a customer, you guys are partnering on this, so it's kind of you're partnering, but also they're helping you. Talk about the relationship and how the interactions went. >> Yeah, so I would say the challenge that I think a lot of people in my role are faced with where the demand for data is increasing and demand for more variety of data. And I'm faced with a lot of aging on premise hardware that I really don't want to invest any further in. So I know the cloud's in the future, but we are so new with the cloud that we don't even know what we don't know. So we had zeroed in on AWS and I was talking with them and I made it very clear. I said "Because of our inexperience, we have talented data engineers, but they don't have this type of experience, but I'm confident they can learn." So what I'm looking for is a partner who can help us not only prove this out that it can work, which I had high confidence that it could, but help us identify where we need to be putting our skilling up. You know, what gaps do we have? And AWS has just so many different components that we also needed help just zeroing in on for our need, what are the pieces we should really be paying attention to and developing those skills. So we got introduced to NorthBay and they introduced us to the idea of the jam session, which was perfect. It was really exactly what I was looking for. We made it very clear in the early conversations that this would be side by side development, that my priority was of course, to meet our deliverables, but also for my team to learn how to use some of this and learn what they need to dive deeper in at the end of the engagement. I think that's how it got started and then I think it was very successful engagement after that. >> Talk about the jam sessions, because I love this. First of all, this is in line with what we're seeing in the marketplace with rapid innovation, now more than ever with virtual workforces at home, given the situation. You know, rapid agile, rapid innovation, rapid development is a key kind of thing. What is a jam session? What was the approach? Jim you laid a little bit about it out, but Chad, what's your take on the jam sessions? How does it all work? >> I mean, it was great, because of large teams that NorthBay brought and the variety of skills they brought, and then they just had a playbook that worked. They broke us up into different groups, from the people who'd be making the data pipeline, to the people who then would be consuming it to develop analytics projects. So that part worked really well, and yes, this rapid iterative development. Like right now with our current kind of process and our current tool, I have a hard time telling anybody how long it will take to get that new data source online and available to our data analysts, to our data scientists, because it takes months sometimes and nobody wants that answer and I don't want to be giving that answer, so what we're really focused on is how do we tighten up our process? How do we select the right tools so that we can say, "We'll be two weeks from start to finish" and you'll be able to make those data available. So the engagement with NorthBay, the jam session scheduled like that really helped us prove that once you have the skills and you have the right people, you can do this rapid development and bring more value to our business more quickly, which is really what it's all about for us. >> Jim, I'll get your thoughts because, you know, we see time and time again with the use cases with the cloud, when you got smart people, certainly people who play with data and work with data, They're pretty savvy, right? They know limitations, but when you get the cloud, it's like if a car versus a horse, right? Got to go from point A to point B, but again, the faster is the key. How did you put this all together and what were the key learnings? >> Yeah, so John, a couple of things that are really important. One is, as Chad mentioned, really smart people on the U-PIT side that wanted to really learn and had a thirst for learning. And then couple that with the thing that they're trying to learn in an actual use case that we're trying to jointly implement. A couple of things that we've learned that are really important. One is although we have structure and we have a syllabi and we have sort of a pattern of execution, we can never lose sight of the fact that every customer is different. Every team member is different. And in fact, Chad, in this case had team members, some had more skills on AWS than others. So we had to be sensitive to that. So what we did was we sort of used our general formula for the two weeks. Week one is very structured, focused on getting folks up to speed and normalize in terms of where they are in their education of AWS, the solution we're building and then week two is really meant to sort of mold the clay together and really take this solution that we're trying to execute around and tailor it to the customer so that we're addressing the specific needs, both from their team member perspective and the institution's perspective in total. We've learned that starting the day together and ending the day with a recap of that day is really important in terms of ensuring that everyone's on the same page, that they have commonality of knowledge and then when we're addressing any concerns. You know, this stuff we move fast, right? Two weeks is not a long time to get a lot of rapid prototyping done, so if there is anxiety, or folks feel like they're falling behind, we want to make sure we knew that, we wanted to address that quickly, either that evening, or the next morning, recalibrate and then continue. The other thing that we've learned is that, and Chad and entire U-Pit team did a phenomenal job with this, was really preparation. So we have a set of preliminary set of activities that we work with our customers to sort of lay the foundation for, so that on day one of the jam session, we're ready to go. And since we're doing this virtually, we don't have the luxury of being in a physical room and having time to sort of get acclimated to the physical construct of organizing rooms and chairs and tables and all that. We're doing all that virtually. So Chad and the team were tremendous in getting all the preparatory work done Thinking about what's involved in a data lake, it's the data and security and access and things our team needed to work with their team and the prescription and the formula that we use is really three critical things. One is our team members have to be adept at educating on a virtual whiteboard, in this case. Secondly, we want to do side by side development. That's the whole goal and we want team members to build trust and relationships side by side. And then thirdly, and importantly, we want to be able to do over the shoulder mentoring, so that as Chad's team members were executing, we could guide them as we go. And really those three ingredients were really key. >> Chad, talk about the data lake and the outcome as you guys went through this. What was the results of the data Lake? How did it all turn out? >> Yeah, the result was great. It was exactly what we were looking for. The way I had structured the engagement and working with Jim to do this is I wanted to accomplish two things. I wanted to one, prove that we can do what we do today with a star schema mart model that creates a lot of reports that are important to the business, but doesn't really help us grow in our use of data. So there was a second component of it that I said, I want to show how we do something new and different that we can't do with our existing tools, so that I can go back to our executive leadership and say "Hey, by investing in this, here's all the possibilities we can do and we've got proof that we can do it." So some natural language processing was one of those and leveraging AWS comprehend was key. And the idea here was there are, unfortunately, it's not as relevant today with COVID, but there are events happening all around campus and how do students find the right events for them? You know, they're all in the calendar. Well, with a price of natural language processing using AWS comprehend and link them to a student's major, so that we can then bubble these up to a student "Hey, do you know of all these thousands of events here are the 10 you might be most interested in." We can't do that right now, but using these tools, using the skills that that NorthBay helped us develop by working side by side will help us get there. >> A beautiful thing is with these jam sessions, once you get some success, you go for the next one. This sounds like another jam session opportunity to go in there and do the virtual version. As the fall comes up, you have the new reality. And this is really kind of what I like about the story is you guys did the jam session, first of all, great project, but right in the middle of this new shift of virtual, so it's very interesting. So I want to get your thoughts, Chad, as you guys looked at this, I mean on any given Sunday, this is a great project, right? You can get people together, you go to the cloud, get more agile, get the proof points, show it, double down on it, playbook, check. But now you've got the virtual workforce. How did that all play out? Anything surprise you? Any expectations that were met, or things that were new that came out of this? 'Cause this is something that is everyone is going through right now. How do I come out of this, or deal with current COVID as it evolves? And then when I come out of it, I want to have a growth strategy, I want to have a team that's deploying and building. What's your take on that? >> Yeah, it's a good question and I was a little concerned about it at first, because when we had first begun conversations with NorthBay, we were planning on a little bit on site and a little bit virtual. Then of course COVID happened. Our campus is closed, nobody's permitted to be there and so we had to just pivot to a hundred percent virtual. I have to say, I didn't notice any problems with it. It didn't impede our progress. It didn't impede our communication. I think the playbook that NorthBay had really just worked for that. Now they may have had to adjust it and Jim can certainly talk to that, But those morning stand-ups for each group that's working, the end of day report outs, right? Those were the things I was joining in on I wasn't involved in it throughout the day, but I wanted to check in at the end of the day to make sure things are kind of moving along and the communication, the transparency that was provided was key, and because of that transparency and that kind of schedule they already had set up at North Bay, We didn't have any problems having it a fully virtual engagement. In fact, I would probably prefer to do virtual engagements moving forward because we can cut down on travel costs for everybody. >> You know, Jim, I want to get your thoughts on this, 'cause I think this is a huge point that's not just represented here and illustrated with the example of the success of the EDU solution you guys got the award for, but in a way COVID exposes all the people that have been relying on waterfall based processes. You've got to be in a room and argue things out, or have meetings set up. It takes a lot of time and when you have a virtual space and an agile process, yeah you make some adjustments, but if you're already agile, it doesn't really impact too much. Can you share your thoughts because you deployed this very successfully virtually. >> Yeah, it's certainly, you know, the key is always preparation and our team did a phenomenal job at making sure that we could deliver equal to, or better than, virtual experience than we could an on-site experience, but John you're absolutely right. What it forces you to really do is think about all the things that come natural when you're in a physical room together, but you can't take for granted virtually. Even interpersonal relationships and how those are built and the trust that's built. As much as this is a technical solution and as much as the teams did really phenomenal AWS work, foundationally it all comes down to trust and as Chad said, transparency. And it's often hard to build that into a virtual experience. So part of that preparatory work that I mentioned, we actually spend time doing that and we spent time with Chad and other team members, understanding each of their team members and understanding their strengths, understanding where they were in the education journey and the experiential journey, a little bit about them personally. So I think the reality in the in the short and near term is that everything's going to be virtual. NorthBay delivers much of their large scale projects virtually now. We have a whole methodology around that and it's proven actually it's made us better at what we do quite frankly. >> Yeah it definitely puts the pressure on getting the job done and focusing on the creativity in the building out. I want to ask you guys both the same question on this next round, because I think it's super important as people see the reality of cloud and this certainly has been around, the benefits of there, but still you have the mentality of "we have to do it ourselves", "not invented here", "It's a managed service", "It's security". There's plenty of objections. If you really want to avoid cloud, you can come up with something if you really looked for it. But the reality is is that there are benefits. For the folks out there that are now being accelerated into the cloud for the reasons with COVID and other reasons, What's your advice to them? Why cloud? What's the bet? What comes out of making a good choice with the cloud? Chad, as people sitting there going "okay, I got to get my cloud mojo going" What's your advice to those folks sitting out there watching this? >> So I would say, and Jim knows this, we at Pitt have a big vision for data, a whole universe of data where just everything is made available and I can't estimate the demand for all of that yet, right? That's going to evolve over time, so if I'm trying to scale some physical hardware solution, I'm either going to under scale it and not be able to deliver, or I'm going to invest too much money for the value I'm getting. By moving to the cloud, what that enables me to do is just grow organically and make sure that our spend and the value we're getting from the use are always aligned. And then, of course, all the questions about, scalability and extensibility, right? We can just keep growing and if we're not seeing value in one area, we can just stop and we're no longer spending on that particular area and we can direct that money to a different component of the cloud. So just not being locked in to a huge expensive product is really key, I think. >> Jim, your thoughts on why cloud and why now? Obviously it's pretty obvious reasons, but benefits for the naysayer sitting on the fence? >> Yeah, it's a really important question, John and I think Chad had a lot of important points. I think there's two others that become important. One is agility. Whether that's agility with respect to if you're in a competitive market place, Agility in terms of just retaining team members and staff in a highly competitive environment we all know we're in, particularly in the IT world. Agility from a cost perspective. So agility is a theme that comes through and through over and over and over again, and as Chad rightfully said, most companies and most organizations they don't know the entirety of what it is they're facing, or what the demands are going to be on their services, so agility is really, is really key. And the second one is, the notion has often been that you have to have it all figured out before you can start and really our mantra in the jam session was sort of born this way. It's really start by doing. Pick a use case, pick a pain point, pick an area of frustration, whatever it might be and just start the process. You'll learn as you go and not everything is the right fit for cloud. There were some things for the right reasons where alternatives might be be appropriate, but by and large, if you start by doing and in fact, through jam session, learn by doing, you'll start to better understand, enterprise will start to better understand what's most applicable to them, where they can leverage the best bang for the buck, if you will. And ultimately deliver on the value that IT is meant to deliver to the line of business, whatever that might be. And those two themes come through and through. And thirdly, I'll just add speed now. Speed of transformation, speed of cost reduction, speed of future rollout. You know, Chad has users begging for information and access to data, right? He and the team are sitting there trying to figure how to give it to them quickly. So speed of execution with quality is really paramount as well these days. >> Yeah and Chad also mentioned scale too, cause he's trying to scale up as key and again, getting the cloud muscles going for the teams and culture is critical because matching that incentives, I think the alignment is critical point. So congratulations gentlemen on a great award, best EDU solution. Chad, while I have you here, I want to just get your personal thoughts, but your industry expert PhD hat on, because one of the things we've been reporting on is in the EDU space, higher ed and other areas, with people having different education policies, the new reality is with virtualized students and faculty, alumni and community, the expectations and the data flows are different, right? So you had stuff that people used, systems, legacy systems, kind of as a good opportunity to look at cloud to build a new abstraction layer and again, create that alignment of what can we do development wise, because I'm sure you're seeing new data flows coming in. I'm sure this kind of thinking going on around "Okay, as we go forward, how do we find out what classes to attend if they're not onsite?" This is another jam session. So I see more and more things happening, pretty innovative in your world. What's your take on all this? >> My take, so when we did the pivot, we did a pivot right after spring break to be virtual for our students, like a lot of universities did. And you learn a lot when you go through a crisis kind of like that and you find all the weaknesses. And we had finished the engagement, I think, with NorthBay by that point, or were in it and seeing how if we were at our future state, you know, might end up the way I envisioned the future state, I can now point to these specific things and give specific examples about how we would have been able to more effectively respond when these new demands on data came up, when new data flows were being created very quickly and able to point out to the weaknesses of our current ecosystem and how that would be better. So that was really key and this whole thing is an opportunity. It's really accelerated a lot of things that were kind of already in the works and that's why it's exciting. It's obviously very challenging and at Pitt we're really right now trying to focus on how do we have a safe campus environment and going with a maximum flexibility and all the technology that's involved in that. And, you know, I've already got, I've had more unique data requests come to my desk since COVID than in the previous five years, you know? >> New patterns, new opportunities to write software and it's great to see you guys focused on that hierarchy of needs. I really appreciate it. I want to just share with you a funny story, not funny, but interesting story, because this highlights the creativity that's coming. I was riffing on Zoom with someone in a higher ed university out here in California and it wasn't official business, was just more riffing on the future and I said "Hey, wouldn't it be cool if you had like an abstraction layer that had leveraged Canvas, Zoom and Discord?" All the kids are on Discord if they're gamers. So you go "Okay, why discord? It's a hang space." People, it's connective tissue. "Well, how do you build notifications through the different silos?" You know, Canvas doesn't support certain things and Canvas is the software that most universities use, but that's a use case that we were just riffing on, but that's the kind of ideation that's going to come out of these kinds of jam sessions. Are you guys having that kind of feeling too? I mean, how do you see this new ideation, rapid prototype? I only think it's going to get faster and accelerated. >> As Chad said, his requests are we're multiplying, I'm sure and people aren't, you know, folks are not willing to wait. We're in a hurry up, 'hurry up, I want it now' mentality these days with both college attendees as well as those of us who are trying to deliver on that promise. And I think John, I think you're absolutely right and I think that whether it be the fail fast mantra, or whether it be can we make even make this work, right? Does it have legs? Is it is even viable? And is it even cost-effective? I can tell you that we do a lot of work in Ed tech, we do a lot of work in other industries as well And what the the courseware delivery companies and the infrastructure companies are all trying to deal with as a result of COVID, is they've all had to try to innovate. So we're being asked to challenge ourselves in ways we never been asked to challenge ourselves in terms of speed of execution, speed of deployment, because these folks need answers, you know, tomorrow, today, yesterday, not six months from now. So I'll use the word legacy way of thinking is really not one that can be sustained, or tolerated any longer and I want Chad and others to be able to call us and say, "Hey, we need help. We need help quickly. How can we go work together side by side and go prove something. It may not be the most elegant, it may not be the most robust, but we need it tomorrow." And that's really the spirit of the whole notion of jam session. >> And new expectations means new solutions. Chad, we'll give you the final word. Going forward, you're on this wave right now, you got new things coming at you you're getting that foundation set. What's your mindset as you ride this wave? >> I'm optimistic. It really is, it's an exciting time to be in this role, the progress we've made in the calendar year 2020, despite the challenges we've been faced with, with COVID and budget issues, I'm optimistic. I love what I saw in the jam session. It just kind of confirmed my belief that this is really the future for the University of Pittsburgh in order to fully realize our vision of maximizing the value of data. >> Awesome! Best EDU solution award for AWS public sector. Congratulations to NorthBay Solutions. Jim Keller, president, and University of Pittsburgh, Chad Burton. Thank you for coming on and sharing your story. Great insights and again, the wave is here, new expectations, new solutions, clouds there, and you guys got a good approach. Congratulations on the jam session, thanks. >> Thank you, John. Chad, pleasure, thank you. >> Thank you. >> See you soon. >> This is "the Cube" coverage of AWS public sector partner awards. I'm John Furrier, host of "the Cube". Thanks for watching. (bright music)

>>from the Cube Studios in Palo Alto and Boston connecting with thought leaders all around the world. This is a cube conversation. >>Welcome back to the Cube's coverage here from Palo Alto, California in our studio with remote interviews during this time of covert 19 with our quarantine crew. I'm John Furrier, your host of the Cube, and we have here the award winners for the best CDU solution from North based loses. Jim Keller, the president and from Harvard Business Publishing and University of Pittsburgh, Chad Burden PhD in data privacy officer of University of Pittsburgh. Thanks for coming on, gentlemen. Appreciate it. >>Thank you. >>So, Jim, we'll start with you. What is the solution that you guys have got the award for and talk about how it all came about? >>Yeah. Thank you for asking. And, uh, it's been a pleasure Worldwide chat and the entire you pitch team. So? So as we as we enter this this this whole covitz situation, our team really got together and started to think about how we could help AWS customers continue their journey with AWS, but also appreciate the fact that everyone was virtual. The budgets were very tight, but Nonetheless, the priorities remained the same. Um, So So we devised a solution which which we call jam sessions, AWS jam sessions and the whole principle behind the notion is that many customers go through AWS training and AWS has a number of other offerings, immersion days and boot camps and other things. But we felt it was really important that we brought forth a solution that enables customers to focus on a use case but do it rapidly in a very concentrated way with our expert team. So we formulated what we call jam sessions, which are essentially very focused, too. Weak engagements, rapid prototyping engagements. So in the context of Chad on the pitch team, it was around a data lake and they had been channels certainly speak to this in much more detail. But the whole notion here was how do you How does the customer get started out? Is how does a customer prove the efficacy of AWS proved that they can get data out of their on premises systems, get it into AWS, make it accessible in the form in this case, a data lake solution, and have the data be consumable. So we have an entire construct that we use, which includes structured education, virtual simultaneous rooms where development occurs with our joint sap prototyping teams. We come back again and do learnings, and we do all of this in the construct of the agile framework. And ideally, by the time we're done with the two weeks, um, the customer achieves some success around achieving the goal of the jam session. But more importantly, their team members have learned a lot about AWS with hands on work, real work. Learn by doing if you will, um, and really marry those two concepts of education and doing and come out of that with an opportunity then to think about the next step in that journey, which in this case be Thea implementation of a data lake in a full scale project kind of initiative. >>Talk about the relationship with the North based solutions. So your customer, you guys were partnering on this, so it's kind of your partnering, but also your they're helping you talk about the relationship and how the interactions went. >>Yeah, so I was faced with a challenge that I think a lot of people in my role is faced with where the demand for data is increasing and demand for more variety of data. And I'm faced with a lot of aging on premise hardware that, um I really don't want to invest any further. And so I know the clouds in the future, but we are so new with the cloud that we don't even know what we don't know. So it has zeroed in on AWS and I was talking with them and I made it very clear. I said, you know, because of our inexperience, you know, we have talented data engineers, but they don't have this type of experience, but I'm confident they can learn. What I'm looking for is a partner who can help us not only prove this out, that it can work, which I had high confidence that it could, but help us identify where we need to be putting our still skilling up. You know what gaps do we have? And you know, aws has so many different components. But we also needed help zeroing in on or our need. You know, what are the pieces we should really be paying attention to and developing those skills. So we got introduced to North Bay and they introduced us to the idea of the jam session, which was perfect. It was really exactly what I was looking for. Um, you know, we made it very clear in the early conversations that this would be side by side development, that my priority was, of course, to meet our deliverables. But it also for my team to learn how to use some of this and learn what they need to dive deeper in at the end of the engagement. I think that's how we got started on then. It was very successful engagement after that >>talk about the jam sessions because I love this. First of all, this is in line with what we're seeing in the marketplace, with rapid innovation now more than ever, with virtual workforces at home given situation, rapid, agile, rapid innovation, rapid development is a key kind of thing. What is a jam session was the approach. Give me a little bit about of it out, but what's your take on the jam sessions? Had it all has it all work? >>It was great because of the large team that north a broad and the variety of skills they brought and then they just had a playbook that worked, right? They broke us up into different groups from the people who be making the data pipeline to the people who then would be consuming it to develop analytics projects. Um, so that part works really well. And, yes, this rapid iterative development, You know, right now, with our current kind of process in our current tools, I have a hard time telling anybody how long it will take to get that new data source online and available to our data analysts who are data scientists because it takes months sometimes and nobody wants that answer. And I don't want to be giving that answer. So what we're really focused on is how do we tighten up our process? How do we still like the right tools so that we can pay, you know, will be two weeks from start to finish and you know you'll be able to make the data available. So the engagement with North of the jam session scheduled like that really helped us prove that. You know, once you have the skills and have the right people, you can do this rapid development and bring more value to our business more quickly, which is really what it's all about. We're out, >>Jim. I want get your thoughts because, you know, we see time and time again with the use cases with the cloud When you got smart people, certainly people who play with data and work with data, they're not. They're pretty savvy. They know the limitations. But when you get the cloud, it's like a car versus a horse or, you know, get a go from point A to point B. But again, the faster is the key. How did you put this all together And what were the key learnings? >>Yeah. So, uh, John, you know, a couple of things that are really important. One is, as Chad mentioned, really smart people, um, on the it side that wanted to wanted to really learn and had had a thirst for learning. Um, and then couple that with the thing that they're trying to learn in the actual use case that we're trying to jointly jointly implement a couple of things that we've learned that they're they're really important. One is, although we have structure, we have a Silla by and we have sort of a pattern of execution. We never lose sight of the fact that every customer's different. Every team members different and in fact chat in this case that team members some had more skills on AWS than others, so we had to be sensitive to that. So what we did was we sort of use our general formula for for the two weeks one week one is very structured, focused on getting folks up to speed and normalize in terms of where they are in their education of aws solution we're building, um, and then we two is really meant to sort of multiple together and really take this the solution that we're trying to execute around, um, and tailor it to the customer. So they were addressing the specific needs both from their team member of perspective and, uh, and the institutions perspective, Um, in total. We've learned that starting the day together and ending today with the recap of that day is really important in terms of ensuring that everyone's on the same page, that they have commonality of knowledge. And then we were addressing any concerns. You know, this stuff we move fast, right? Two weeks is is not a long time to get a lot of rapid prototyping done. So if there is anxiety or folks feel like they're falling behind, you want to make sure we knew that we want to address that quickly that evening or the next morning, recalibrate and and then continue. The other thing that we've learned is that and Chad, the entire Cube team did a phenomenal job of this was really preparation. So we want to We we We have a set of preliminary set of activities that we that we work with our customers sort of lay the foundation for, so that on day one of the jam session, we're ready to go. And with this we're doing this virtually. We don't have the luxury of being in a physical room and having time to sort of get acclimated to the physical constructive of organizing rooms and shares and tables. All of that, we're doing all that virtually so. Joe and the team were tremendous and getting all the preparatory work done. The thing about was involved in a data lake. It's the data and security and access of things Our team needed to work with their team and the prescription that in the formula that we use is really 33 critical things. One is our team members have to be adept that educating on a white board in this case. Secondly, we want to do side by side element. That's that's the whole goal. And then we want team members to to build trust and relationship side by side and then, thirdly and importantly, we want to be able to do over the shoulder mentoring. So as Chad's team members were executing, UI could guide them as we go. And those really those three ingredients really >>talk about the Data Lake on the outcome. As you guys went through this, what was the results of the Data Lake? How did it all? How'd it all turn out? >>Yeah, the result was great. It was exactly what we're looking for. The way I had structured the engagement and working with Jim to do this is I wanted to accomplish two things. I wanted to one prove that we can do what we do today with a star schema Martin model that creates a lot of reports that are important to the business but doesn't really help us grow in our use of data. There was a second component of it that I said, I want I want to show how we do something new and different that we can't do with our existing tools so that I can go back to our executive leadership and say, Hey, you know, by investing in this year's all the possibilities we can do and we've got proof that we can do it. So some natural language processing was one of those and leveraging aws comprehend with key and And the idea here was there are unfortunately relevant today with Cove it. But there are events happening all around campus. And how do students find the right events for them? You know, they're all in the calendar will live pricing national language processing using AWS comprehend and link them to a student's major so that we can then bubble these up to a student. Hey, you know of all these thousands of events here and you might be most interested in you can't do that right now, but using these tools using the skills that north they helped us develop working side by side will help us get there, >>you know, beautiful thing is with these jam sessions. You want to get some success, You go for the next one. You get this Sounds like another jam session opportunity to go in there and do the virtual version as well. As the fall comes up, you have the new reality. And this >>is >>really kind of What I like about this story is you guys did the jam session. First of all, great project, but right in the middle of this new shift of virtual, so it's very interesting. So I want to get your thoughts, Chad, You know, as you guys look at this, I mean on any given Sunday, this is a great project. You get people together, you have the cloud get more agile, get the proof points, show it double down on it. Playbook check. But now you've got the virtual workforce. How did that all play out? Anything surprise you any expectations that were met or things that were new that came out of this? Because this is something that everyone is going through right now. How do I come out of this or deal with current Cove it as it evolves and when I come out of it. I don't have a growth strategy in a team that's deploying and building. What's your take on? >>Yeah, so, yeah, you know, it's a good question. And I was a little concerned about it at first, cause when we had first begun conversations with North Bay, we were planning on a little bit on site and a little bit virtual. And of course, Cove. It happened. Our campuses closed. Nobody's permitted to be there. And so we had to just pivot to 100% virtual. I have to say I didn't notice any problems with it. It didn't impede our progress that didn't impede our communication. I think the playbook that North they had really just worked for that. Now they may have had to adjust it, and Jim can certainly part of that. But you know those morning stand ups for each group that's working the end of day worn out right? That's what those were the things I was joining in on, you know, it wasn't involved in it throughout the day, but I wanted to check in at the end of the day to make sure things are kind of moving along and the communication the transparency that was provided with key, and because of that transparency and that kind of schedule, they already have set up North Bay. We didn't see we didn't have any problems having a fully virtual engagement. In fact, I would probably prefer to do for two engagements moving forward because we can cut down on travel costs for everybody. >>You know, Jim O. Negative thoughts that I think is a huge point that's not just representing with here and illustrate with the example of the success of the EU solution. You guys got the award for, but in a way, covert exposes all the people that are been relying on waterfall based processes. You got to be in a room and argue things out. Our have meetings set up. It takes a lot of time when you when you have a virtual space and an agile process, you make some adjustments. But if you're already agile, it doesn't really impact too much. Can you share your thoughts because you deployed this very successfully? Virtually. >>Yeah, I know it is. Certainly, um, the key is always preparation and on our team did a phenomenal job of making sure that we could deliver equal to or better than virtual experience than we could on site and on site experience. But, John, you're right. You're absolutely right. But it forces you to really do is think about all the things that come natural when you're when you're in a physical room together, you can't take for granted virtually, um, even even interpersonal relationships and how those were built and the trust that's built in. And this whole, as much as this is a technical solution and as much as the teams did you really phenomenal aws work, foundational Lee. It all comes down to trust it, as Chad said, transparency, and it's hard, often hard to to build that into a virtual experience. So part of that preparatory work that I mentioned, we actually spend time doing that. And we spent time with Chad and other team members understanding each of their team members and understanding their strengths, understanding where they were in the education journey and experiential journey a little bit about them personally, right? So so I think. Look, I think the reality in the short and near term is that everything is gonna be virtual North Bay delivers much of their large scale projects. Virtually now, we have a whole methodology around that, and, um, and it's proven. Actually, it's made us better at what we do. >>Yeah, definitely puts the pressure on getting the job done and focusing on the creativity the building out. I want to ask you guys both the same question on this next round, because I think it's super important as people see the reality of cloud and there certainly has been around the benefits of there. But still you have, you know, mentality of, you know, we have to do it ourselves, not invented here. It's a managed services security. You know, there's plenty of objections. If you really want to avoid cloud, you can come up with something if you really look for it. Um, but the reality is, is that there are benefits for the folks out there that are now being accelerated into the cloud for the reasons we cove it and other reasons. What's your advice to them? Why cloud, what's the what's the bet? What comes? What comes out of making a good choice with the cloud? Chad? Is people sitting there going? Okay, I got to get my cloud mojo going What's your What's your What's your advice to those folks sitting out there watching this? >>Yeah, so I would say it. And Jim does this, you know, we have a big vision for data, you know, the whole universe of data. Where does everything is made available? And, um, I can't estimate the demand for all of that yet, right, That's going to evolve over time. So if I'm trying to scale some physical hardware solution, I'm either going to under scale it and not be able to deliver. Or I'm gonna invest too much money for the value in getting what? By moving to the cloud. What that enables me to do is just grow organically and make sure that our spend and the value we're getting from the use are always aligned. Um And then, of course, all the questions that you have availability and acceptability, right? We can just keep growing. And if we're not seeing value in one area, we can just we're no longer spending on that particular area, and we contract that money to a different components of the cloud, so just not being locked into a huge expense up front is really key, I think, >>Jim, your thoughts on Why Cloud? Why now? It's pretty obvious reasons, but benefits for the naysayers sitting on the fence who are? >>Yeah, it's It's a really important question, John and I think that had a lot of important points. I think there's two others that become important. One is, um, agility. Whether that's agility with respect to your in a competitive marketplace, place agility in terms of just retaining team members and staff in a highly competitive environment will go nowhere in particularly in the I t world, um, agility from a cost perspective. So So agility is a theme that comes through and through, over and over and over again in this change, right? So, he said, most companies and most organizations don't they don't know the entirety of what it is they're facing or what the demands are gonna be on their services. The agility is really is really key, and the 2nd 1 is, you know, the notion has often been that you have to have it all figured out. You could start and really our mantra and the jam session was sort of born this way. It's really start by doing, um, pick a use case, Pick a pain point, pick an area of frustration, whatever it might be. And just start the process you learn as you go. Um, and you know, not everything is the right fit for cloud. There are some things for the right reasons where alternatives might be might be appropriate. But by and large, if you if you start by doing And in fact, you know the jam session, learn by doing, and you start to better understand, enterprise will start to better understand what's most applicable to that where they can leverage the best of this bang for the buck if you will, um, and ultimately deliver on the value that that I t is is meant to deliver to the line of business, whatever that whatever that might be. And those two themes come through and through. And thirdly, I'll just add speed now. Speed of transformation, Speed of cost reduction, speed of feature rollout. Um, you know, Chad has users begging for information and access to data. Right? And the team we're sitting there trying to figure how to give it to him quickly. Um, so speed of execution with quality is really paramount as well these days >>and channels. You mentioned scale too, because he's trying to scale up as key and again getting the cloud muscles going for the teams. And culture is critical because, you know, matching that incentives. I think the alignment is critical. Point point. So congratulations, gentlemen. On great award best edu solution, Chad, While I have you here, I want to just get your personal thoughts. Put your industry expert PhD hat on because, you know, one of the things we've been reporting on is a lot of in the edu space higher ed in other areas with people having different education policies. The new reality is with virtual virtualized students and faculty alumni nine in community, the expectations and the data flows are different. Right? So you you had stuff that people use systems, legacy systems, >>kind of. >>It's a good opportunity to look at cloud to build a new abstraction layer and again create that alignment of what can we do? Development wise? I'm sure you're seeing new data flows coming in. I'm sure there's kind of thinking going on around. Okay. As we go forward, how >>do >>we find out who's what. Classes to attend if they're not on site this another jam session. So I see more, more things happening pretty innovative in your world. What's your take on all this? >>Um, I take, you know, So when we did the pivot, we did a pivot right after spring. Great toe. Be virtual for our students, Like a lot of universities dead. And, um, you learn a lot when you go through a crisis kind of like that. And you find all the weaknesses And we had finished the engagement. I think north by that point, or it were in it. And, um, seeing how if we were at our future state, you know, the way I envision the future state, I can now point to the specific things and get specific examples of how we would have been able to more effectively on when these new demands on data came up when new data flows were being created very quickly and, you know, able to point out to the weaknesses of our current ecosystem and how that would be better. Um, so that was really key. And then, you know, it's a This whole thing is an opportunity. It's really accelerated a lot of things that were kind of already in the works, and that's why it's exciting. It's obviously very challenging, you know, and that if it were really right now trying to focus on how do we have a safe campus environment and going with a maximum flexibility and older technology that's involved in that? And, you know, I've already got you know, I've had more unique data requests. >>My desk >>is coded and in the previous five years, you know, >>new patterns, new opportunities to write software. And it's great to see you guys focused on the hierarchy of needs. Really appreciate. I want to just share a funny story. Not funny, but interesting story, because this highlights the creativity that's coming. I was riffing on Zoom with someone in Higher Ed University out here in California, and it was wasn't official. Business was just more riffing on the future, and I said, Hey, wouldn't it be cool if you have, like an abstraction layer that had leverage, canvas, zoom and discord and all the kids are on discourse, their game received. Okay, why discord? It's the hang space people are his connective tissue Well, how do you build notifications through the different silos? So canvas doesn't support certain things? And campuses? The software. Most companies never say years, but that's a use case that we were just riffing on. But that's the kind of ideation that's going to come out of these kinds of jam sessions. You guys having that kind of feeling to? How do you see this new ideation? Rapid prototyping. I only think it's gonna get faster. Accelerated >>It was. Chad said, you know, his requests are multiplying. I'm sure on people are you know, folks are not willing to wait, you know, we're in a hurry up. Hurry up. I wanted now mentality these days with with both, um college attendees as well as those of us. We're trying to deliver on that promise. And I think, John, I think you're absolutely right. And I think that, um, whether it be the fail fast mantra or whether it be can we may even make this work right? Doesn't have lakes, is it is even viable. Um, and is it even cost effective? I can tell you that the we do a lot of work in tech. We do a lot of work in other industries as well. And what what the courseware delivery companies and the infrastructure companies are all trying to deal with and as a result of coaches, they've all had to try to innovate. Um, so we're being asked to challenge ourselves in ways we never been asked to challenge ourselves in terms of speed, of execution, speed of deployment, because these folks need answers, you know, tomorrow, Today, yesterday, not not six months from now. So the the I'll use the word legacy way of thinking is really not one that could be sustained or tolerated any longer. And and I want Chad and others to be able to call us and say, Hey, we need help. We need help quickly. How we go work together, side by side and go prove something. It may not be the most elegant. It may not be the most robust, but we need. We need it kind of tomorrow, and that's really the spirit of the whole. The whole notion of transition >>and new expectations means new solutions that will give you the final word going forward. You're on this wave right now. You got new things coming at you. You get in that foundation set. What's your mindset as you ride this wave? >>I'm optimistic it really It's an exciting time to be in this role. The progress we've made in the county or 2020 despite the challenges we've been faced with with, um cove it and budget issues. Um, I'm optimistic. I love what I saw in the in the jam session. It just kind of confirmed my I believe that this is really the future for the University of Pittsburgh in order to fully realize our vision of maximizing the value of data. >>Awesome. Best Edu solution award for AWS Public sector Congratulations and North based solutions. Jim Keller, President and University of Pittsburgh Chadbourne. Thank you for coming on and sharing your story. Great insights. And again, the wave is here. New expectation, new solutions. Clouds There. You guys got a good approach. Congratulations on the jam session. Thanks. >>Thank you, John. Pleasure. Thank you. Through >>the cube coverage of AWS Public Sector Partner Awards. I'm John Furrow, your host of the Cube. Thanks for watching. Yeah, yeah, yeah, yeah

>> From Las Vegas, it's theCUBE covering Open Systems. The future is crystal clear with security and SD-Wan. Brought to you by Open Systems. >> Hello everyone, I'm John Furrier here in Las Vegas for special CUBE presentation. We're at the Chandelier Bar at the Cosmopolitan Hotel, the Cosmo, on the Las Vegas strip. Part of a series of a lot of events going on. Gartner's got two events happening, But we're here as part of Open Systems. You got exclusive get-together of influencers, customers, all talking about the impact the Cloud, Secure, SD-Wan, a variety of other things. Open Systems, a very successful, Switzerland-based company expanding rapidly in the United States, a global platform and we're here with the CTO, Stefan Keller, thanks for joining me. >> Thank you for having me. >> You guys have been very successful in this, I will say, changing SD-Wan, a completely new re-imagined SD-Wan market because with the internet and Cloud, people don't want to connect to the internet anymore, they want either direct connection, they want high-secure, wide-area network connections. They want secure connections. More important than ever when you have Internet of Things, a lot of surface area, nevermind multiple headquarters or branch offices, so SD-Wan has gone from a connection, connectivity, move packets from A to B, to a fully-integrated, secure architecture that's easy to use, that can deal with mobile embedded. You guys have been successful, with almost no marketing, all word of mouth, successful product, tell us, Stefan, as the CTO, what is the most compelling thing about the technology that's been resonating with customers? >> Well, as I said, the last couple of years there was a lot of change, technology change. The requirements of our customers changed as well. With Cloud, you'll all of a sudden have traffic pattern that you didn't have before. Before, everything was static. You had just your band connectivity to the data center and there is left, towards the internet. But with SD-Wan, you now have the capability to have very complex traffic flow at the branch office, itself. So, you have a lot of logic that you put to the branch office and the challenge is now, how can you actually control all that traffic flow in a central way? Because in the end, all our customers or companies, what they want, they want to have the flexibility to use all those new technologies, be it Cloud, be it IOT, whatever. But still have the security in mind in the sense, they want to be protected, they want to be protected. You now have the branch office with a lot of new traffic patterns. How do you control that? And that's where our integrated approach of SD-Wan and security is the perfect fit. So you really have a global policy that you assign locally. >> One of the big trends that's happening now obviously, is the Cloud has grown so big and popular that the economics, you cannot ignore the economics and the value in the cloud for what you're paying. Agility, etc., we've heard that. However, validated even more than ever is on-premises. People are going to have an on-premises and Cloud or Hybrid Cloud solution. Now, IT departments and these people managing CSOS, managing all these people have to deal with the distributed, in some cases decentralized operations. The problem is there's so many vendors. They don't have the expertise so they need things as a managed service, sometimes they want to maybe choose something on premise that's deployed. So you need a diversity of choices without compromising ease of use. So the question for you is: How do you guys make that happen because this is something that you've heard people like about your product, complex, I hate the word single-pane of glass but that's been an IT term, that's essentially dashboard, central teams can use telemetry... and data but get the benefits of.. variety of environments. Why is it so successful, what is the choices for customer? Is it managed service, is that the direction? Or and odd PRAM, what's your thoughts? >> Yeah, that's a good point. In the end it's a combination because we are a managed service because, as you said, things get more complex and the talent market is challenging so it's difficult to find the right talents that can manage it. So that's where we come in as a strategic partner. We are not only in the SD-Wan market, we are also in the security market as well. So we combine security and the SD-Wan. That's what you see with all the SD-Wan vendors out there and they're very strong with SD-Wan capabilities but in order to provide security functionality they start to partner, be it with a firewall vendor, with a proxy vendor what so on. So, in the end, you as a customer, you don't deal just with one partner, all of a sudden you have four, five, or even six such partners you have to deal with. And if a managed service provider can provide a holistic approach of security and SD-Wan you have one partner you can deal with so it makes, for you, very easy. >> So a lot of peoples have say, "oh" they've been trying security, a variety, "we've seen every scheme in the book." And the easiest one was, oh, network traffic. Pack an inspection, kind of not very good. But you want to watch the bad guys move. When things are moving around, that's when you get the pattern recognition. Is there software that you guys write? How do you get that security edge? Is it watching the movement patterns, not just the packets but who has what systems, is it a variety of things? What's the underlying secret sauce for Open Systems? >> The secret sauce, well let's say, is that we are flexible to take out whatever is state of the art and put it together to a managed service in a standardized way for our customers If you look as today's companies they want to do it on their own. They may have to deal with 30, 40 different kind of vendors and components and put it together. We do that for our customers. We take state of the art technology, put it together, and make all the service of it. And the advantage is, because we have that high level of integration, we can all of a sudden, use one component for different kind of services we provide. That's the difference when you have an ecosystem like SD-Wan where you have three, four components, they don't really talk with each other, they do not have a common language. We bring that common language so that the consistent view and the consistent logic over the entire band of our customers. >> So you're the glue layer. Between all the different components. >> Right. >> Okay, so I got to ask you a question. If someone says to you "hey Stefan, this other vendor promised me all this stuff over here, some other person. I got to get current on SD-Wan." What do you think people don't know about SD, whether they should know, that might be a surprise or things that you've observed with your successful customer deployments that's a lot harder than it looks. Cause a lot of people say "oh we got that!" And it doesn't really work very well. Or is a blind spot for the CSOS team, security team, around capabilities. So you can be aspirational but you got to have the capability what are some areas that you've seen that are important for buyers to consider when architecting and then deploying and executing an SD-Wan strategy? >> I mean, When you see all those SD-Wan vendors what they say, "hey it's easy to deploy, it's zero-touch deployment." Can't be true but in the end, you have a global network you want to deploy a global policy and somehow, you have to manage that. And this is something that most of them just underestimate. You only need, really, a strategic partner who knows how to deal with it, who has the capabilities, the experience, and the know-how to deploy it easily and manage it for you So then you don't have the pain. >> Give me an example of a customer, you don't have to say their name, where the old way they did something and then the Open Systems side of it, they did it your way and watch changed, what was the impact? Did they have more efficiency with the people? Did they save time, what was some of the consequences of doing the old way versus the new way? >> The old way also then involved some kind of an MPLS network, or course, if we go with the SD-Wan approach, the really good ones convince a customer, "hey, you don't need MPLS for the application you need." For the SLA you want to have. Internet connectivity if fine and just have two or three such internet connection per location. So in the end, it was cost-saving, it was a full put agreement. Performance all of a sudden was very great and in the end they liked us because of our operational efficiency so our operations model is very efficient and helps our customers so that they can focus on their core business. >> So the applications get smarter, and then you actually saved money because, remember, it still costs a lot of money to send traffic over the network, in some cases. Okay, final question. There's a big trend towards direct connections, where do you see that going, how does that impact SD-Wan? >> I would say that's again on the security side because with SD-Wan, you have a lot of flexibility we just didn't have in the past. This means you have traffic flow all of a sudden which is not expected by many people. If you go to a single branch office, a small one, all of a sudden they have local exits, they do internet surfing, youtube video-ing, they have connections to their private data center, to their public Cloud environment, everything. So different kind of traffic pattern. And here we have just the single way, a unique approach, about a global Zone-Based Firewall. So this makes your traffic pattern all of a sudden very transparent and simple again, this helps you to control the traffic flow and to avoid any kind of leak. >> As we always say, don't send those cat videos. It still costs money to share the cat videos around. Super Content is a big part of this too, you've got all kinds of new SAS applications, talking to each other, this is another layer of abstraction that needs to be managed. That's an area you guys do? API's and applications? >> We're going in that direction, I would say we're not that far yet. We can do much more but this is the direction we have to go to. >> Final question: you come to the U.S. A lot of people are learning about you guys, If we're at a cocktail party, which we are at now, and I say "hey Stefan, bottom line me, what's the one thing about Open Systems that makes you guys great?" >> Then I'll still go back to our operational excellence. We really have a way to operate thousands of devices in a way that is so efficient and scaled very well for a huge customer base. >> Alright Stefan, thanks for coming on. Stefan Keller, CTO of Open Systems, hot start-up out of Zurich, Switzerland. A very successful company, really now exploding in the United States, expanding to Silicon Valley. We are here in Las Vegas, theCUBE coverage. Bringing all the action down here at the Open Systems influencer, expert cocktail party, here at the Chandelier Bar at the Cosmo hotel. Part of a lot of events around Gartner's events are here. Covering it all, stay with us for more after this short break. (chill electronic beats)

[Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] [Music] hello and welcome to the Palo Alto students leaky bomb John free we're here for a special cube conversation and special report big news from VMware to discuss the launch of the availability of vSphere seven I'm here with Chris Prasad SVP and general manager of the vSphere business and cloud platform business unit and Paul Turner VP a VP of Product Management guys thanks for coming in and talking about the big news thank you for having us you guys announced some interesting things back in march around containers kubernetes and the vSphere there's just about the hard news what's being announced today we are announcing the general availability of vSphere 7 John it's by far the biggest release that we have done in the last 10 years we previewed it this project Pacific a few months ago with this release we are putting kubernetes native support into the vSphere platform what that allows us to do is give customers the ability to run both modern applications based on kubernetes and containers as well as traditional VM based applications on the same platform and it also allows the IT departments to provide their developers cloud operating model using the VMware cloud foundation that is powered by this release this is a key part of our tansu portfolio of solutions and products that we announced this year and it is targeted fully at the developers of modern applications and the specific news is vSphere 7 is general available you know really vSphere 7 yes ok that so let's on the trend line here the relevance is what what's the big trend line that this is riding obviously we saw the announcements at VMworld last year and throughout the year there's a lot of buzz Pat Keller says there's a big wave here with kubernetes what does this announcement mean for you guys with the marketplace trend yeah so what kubernetes is really about is people trying to have an agile operation they're trying to modernize their IT applications and they the best way to do that is build off your current platform expanded and and make it a an innovative a agile platform for you to run kubernetes applications and VM applications together I'm not just that customers are also looking at being able to manage a hybrid cloud environment both on Prem and public cloud together so they want to be able to evolve and modernize their application stack but modernize their infrastructure stack which means hybrid cloud operations with innovative applications kubernetes or container based applications and VMs what's excited about this trend Chris we were talking with us at VMworld last year and we've had many conversations around cloud native but you're seeing cloud native becoming the operating model for modern business I mean this is really the move to the cloud if you look at the successful enterprises even the suppliers the on-premises piece if not move to the cloud native marketplace technologies the on premise isn't effective so it's not so much on premises going away we know it's not but it's turning into cloud native this is the move to the cloud generally this is a big wave yeah absolutely I mean if Jon if you think about it on-premise we have significant market share by far the leader in the market and so what we are trying to do with this is to allow customers to use the current platform they are using but bring their application modern application development on top of the same platform today customers tend to set up stacks which are different right so you have a kubernetes stack you have a stack for the traditional applications you have operators and administrators who are specialized in kubernetes on one side and you have the traditional VM operators on the other side with this move what we are saying is that you can be on the same common platform you can have the same administrators who are used to administering the environment that you already had and at the same time offer the developers what they like which is kubernetes dial-tone that they can come and deploy their applications on the same platform that you use for traditional applications yep all Pat said Cuba is gonna be the dial tone on the internet most Millennials might even know what dial tone is but a buddy mince is is that's the key fabric there's gonna work a straight and you know we've heard over the years skill gap skill gap not a lot of skills out there but when you look at the reality of skills gap it's really about skills gaps and shortages not enough people most CIOs and chief and major security are so that we talk to you say I don't want to fork my development teams I don't want to have three separate teams so I don't have to I want to have automation I want an operating model that's not gonna be fragmented this kind of speaks to this whole idea of you know interoperability and multi-cloud this seems to be the next big way behind ibrid I think it I think it is the next big wake the the thing that customers are looking for is a cloud operating model they like the ability for developers to be able to invoke new services on demand in a very agile way and we want to bring that cloud operating model to on-prem to Google cloud to Amazon Cloud to Microsoft cloud to any of our VC peepee partners you get the same cloud operating experience and it's all driven by a kubernetes based dial-tone it's effective and available within this platform so by bringing a single infrastructure platform that can one run in this hybrid manner and give you the cloud operating agility that developers are looking for that's what's key in version seven says Pat Kelsey near me when he says dial tone of the internet kubernetes does he mean always on or what does he mean specifically just that it's always available what's what says what's the meaning behind that that phrase the the first thing he means is that developers can come to the infrastructure which is the VMware cloud foundation and be able to work with a set of api's that are kubernetes api s-- so developers understand that they're looking for that they understand that dial tone right and you come to our VMware cloud foundation that runs across all these clouds you get the same API said that you can use to deploy their application okay so let's get into the value here of vSphere seven how does VMware vSphere 7 specifically help customers isn't just bolting on kubernetes to vSphere some will say is it that's simple or are you running product management no it's not that easy it's yeah some people say hey just Bolton kubernetes on vSphere it's it's not that easy so so one of the things if if anybody's actually tried deploying kubernetes first it's it's highly complicated um so so definitely one of the things that we're bringing is you call it a bolt on but it's certainly not like that we are making it incredibly simple you talked about IT operational shortages customers want to be able to deploy kubernetes environments in a very simple way the easiest way that we can you can do that is take your existing environment that are out ninety percent of IT and just turn on turn on the kubernetes dial tone and it is as simple as that now it's much more than that in version 7 as well we're bringing in a couple things that are very important you also have to be able to manage at scale just like you would in the cloud you want to be able to have infrastructure almost self-managed and upgrade and lifecycle manage itself and so we're bringing in a new way of managing infrastructure so that you can manage just large scale environments both on-premise and public cloud environments and scale and then associated with that as well is you must make it secure so there's a lot of enhancements we're building into the platform around what we call intrinsic security which is how can we actually build in truly a trusted platform for your developers and IIT yeah I mean I I was just going to touch on your point about the shortage of IT staff and how we are addressing that here the the way we are addressing that is that the IT administrators that are used to administering vSphere can continue to administer this enhanced platform with kubernetes the same way administered the older laces so they don't have to learn anything new they're just working the same way we are not changing any tools process technologies so same as it was before same as it was before more capable dealer and developers can come in and they see new capabilities around kubernetes so it's best of both worlds and what was the pain point that you guys are so obviously the ease-of-use is critical Asti operationally I get that as you look at the cloud native developer Saiga's infrastructure as code means as app developers on the other side taking advantage of it what's the real pain point that you guys are solving with vSphere 7 so I think it's it's it's multiple factors so so first is we've we've talked about agility a few times right there is DevOps as a real trend inside an IT organizations they need to be able to build and deliver applications much quicker they need to be able to respond to the business and to do that what they are doing is is they need infrastructure that is on demand so what what we're really doing in the core kubernetes kind of enablement is allowing that on-demand fulfillment of infrastructure so you get that agility that you need but it's it's not just tied to modern applications it's also your all of your existing business applications and your monitoring applications on one platform which means that you know you've got a very simple and and low-cost way of managing large-scale IT infrastructure so that's a that's a huge piece as well and and then I I do want to emphasize a couple of other things it's we're also bringing in new capabilities for AI and m/l applications for sa P Hana databases where we can actually scale to some of the largest business applications out there and you have all of the capabilities like like the GPU awareness and FPGA were FPGA awareness that we built into the platform so that you can truly run this as the fastest accelerated platform for your most extreme applications so you've got the ability to run those applications as well as your kubernetes and container based applications that's the accelerated application innovation piece of the announcement right that's right yeah it's it's it's quite powerful that we've actually brought in you know basically new hardware awareness into the product and expose that to your developers whether that's through containers or through VMs Chris I want to get your thoughts on the ecosystem and then the community but I want to just dig into one feature you mentioned I get the lifestyle improvement a life cycle improvement I get the application acceleration innovation but the intrinsic security is interesting could you take a minute explain what that is yeah so there's there's a few different aspects one is looking at how can we actually provide a trusted environment and that means that you need to have a way that the the key management that even your administrator is not able to get keys to the kingdom as we would call it you you want to have a controlled environment that you know some of the worst security challenges inside and some of the companies has been your Intel or internal IT staff so you've got to have a way that you can run a trusted environment in independent we've got these fair trust Authority that we released in version 7 that actually gives you a a secure environment for actually managing your keys to the kingdom effectively your certificates so you've got this you know continuous runtime now not only that we've actually gone and taken our carbon black features and we're actually building in full support for carbon black into the platform so that you've got negative security of even your application ecosystem yeah that's been coming up a lot conversations the carbon black in the security piece Chris obviously have vsphere everywhere having that operating model makes a lot of sense but you have a lot of touch points you got cloud hyper scale is got the edge you got partners so the other dominant market share and private cloud we are on Amazon as you well know as your Google IBM cloud Oracle cloud so all the major clouds there is a vSphere stack running so it allows customers if you think about it right it allows customers to have the same operating model irrespective where their workload is residing they can set policies compliance security they said it once it applies to all their environments across this hybrid cloud and it's all for a supported by our VMware cloud foundation which is powered by vSphere 7 yeah I think having that the cloud is API based having connection points and having that reliable easy to use is critical operating model all right guys so let's summarize the announcement what do you guys take Derek take away from this vSphere 7 what is the bottom line what's what's it really mean I think what we're if we look at it for developers we are democratizing kubernetes we already are in 90% of IT environments out there are running vSphere we are bringing to every one of those be sphere environments and all of the virtual infrastructure administrators they can now manage kubernetes environments you can you can manage it by simply upgrading your environment that's a really nice position rather than having independent kind of environments you need to manage so so I think that's that is one of the key things that's in here the other thing though is there is I don't think any other platform out there that other than vSphere that can run in your data center in Google's in Amazon's in Microsoft's in you know thousands of VC PP partners you have one hybrid platform that you can run with and that's got operational benefits that's got efficiency benefits that's got agility benefits yeah I just add to that and say that look we want to meet customers where they are in their journey and we want to enable them to make business decisions without technology getting in the way and I think the announcement that we made today with vSphere 7 is going to help them accelerate their digital transformation journey without making trade-offs on people process and technology and there's more to come that we're laser focused on making our platform the best in the industry for running all kinds of applications and the best platform for a hybrid and multi cloud and so you'll see more capabilities coming in the future stay tuned oh one final question on this news announcement which is this awesome vSphere core product for you guys if I'm the customer tell me why it's gonna be important five years from now because of what I just said it is the only platform that is going to be running across all the public clouds right which will allow you to have an operational model that is consistent across the clouds so think about it if you go to Amazon native and then you have orc Lord and as your you're going to have different tools different processes different people trained to work with those clouds but when you come to VMware and you use our cloud foundation you have one operating model across all these environments and that's going to be game-changing great stuff great stuff thanks for unpacking that for us graduates on the insulin Thank You Vera bees fear 7 News special report here inside the cube conversation I'm John Farrar your thanks for watch [Music] and welcome back everybody Jeff Rick here with the cube we are having a very special Q conversation and kind of the the ongoing unveil if you will of the new VMware vSphere 7 dot gonna get a little bit more of a technical deep dive here today we're excited to have a longtime cube alumni kit Kolbert here is the vp and CTO cloud platform at being work it great to see you yeah and and new to the cube jared rose off he's a senior director of product management at VMware and I'm guessin had a whole lot to do with this build so Jared first off congratulations for birthing this new release and great to have you on board alright so let's just jump into it from kind of a technical aspect what is so different about vSphere seven yeah great so vSphere seven baek's kubernetes right into the virtualization platform and so this means that as a developer I can now use kubernetes to actually provision and control workloads inside of my vSphere environment and it means as an IT admin I'm actually able to deliver kubernetes and containers to my developers really easily right on top of the platform I already run so I think we had kind of a sneaking suspicion that that might be coming when the with the acquisition of the hefty Oh team so really exciting news and I think it you tease it out quite a bit at VMware last year about really enabling customers to deploy workloads across environments regardless of whether that's on Prem public cloud this public cloud that public cloud so this really is the the realization of that vision yes yeah so we talked at VMworld about project Pacific right this technology preview and as Jared mentioned of what that was was how do we take kubernetes and really build it into vSphere as you know we had a hybrid cloud vision for quite a while now how do we proliferate vSphere to as many different locations as possible now part of the broader VMware cloud foundation portfolio and you know as we've gotten more and more of these instances in the cloud on-premises at the edge with service providers there's a secondary question how do we actually evolve that platform so it can support not just the existing workloads but also modern work clothes as well right all right so I think you brought some pictures for us a little demo so why don't ya well into there and let's see what it looks like you guys can cube the demo yes we're gonna start off looking at a developer actually working with the new VMware cloud foundation for an vSphere 7 so what you're seeing here is the developers actually using kubernetes to deploy kubernetes the self eating watermelon right so the developer uses this kubernetes declarative syntax where they can describe a whole kubernetes cluster and the whole developer experience now is driven by kubernetes they can use the coop control tool and all of the ecosystem of kubernetes api is and tool chains to provision workloads right into vSphere and so you know that's not just provisioning workloads though this is also key to the developer being able to explore the things they've already deployed so go look at hey what's the IP address that got allocated to that or what's the CPU load on this you know workload I just deployed on top of kubernetes we've integrated a container registry into vSphere so here we see a developer pushing and pulling container images and you know one of the amazing things about this is from an infrastructure as code standpoint now the developers infrastructure as well as their software is all unified in source control I can check in not just my code but also the description of the kubernetes environment and storage and networking and all the things that are required to run that app so now we're looking at a sort of a side-by-side view where on the right hand side is the developer continuing to deploy some pieces of their application and on the left-hand side we see V Center and what's key here is that as the developer deploys new things through kubernetes those are showing up right inside of the V center console and so the developer and IT are seeing exactly the same things with the same names and so this means what a developer calls their IT department says hey I got a problem with my database we don't spend the next hour trying to figure out which VM they're talking about they got the same name they say they see the same information so what we're gonna do is that you know we're gonna push the the developer screen aside and start digging into the vSphere experience and you know what you'll see here is that V Center is the V Center you've already known and loved but what's different is that now it's much more application focused so here we see a new screen inside of V Center vSphere namespaces and so these vSphere namespaces represent whole logical applications like a whole distributed system now as a single object inside a V Center and when I click into one of these apps this is a managed object inside of e spear I can click on permissions and I can decide which developers have the permission to deploy or read the configuration of one of these namespaces I can hook this into my Active Directory infrastructure so I can use the same you know corporate credentials to access the system I tap into all my existing storage so you know this platform works with all of the existing vSphere storage providers can use storage policy based management to provide storage for kubernetes and it's hooked in with things like DRS right so I can define quotas and limits for CPU and memory and all that's going to be enforced by Drs inside the cluster and again as an as an admin I'm just using vSphere but to the developer they're getting a whole kubernetes experience out of this platform now vSphere also now sucks in all this information from the kubernetes environment so besides you know seeing the VMS and and things that developers have deployed I can see all of the desired state specifications all the different kubernetes objects that the developers have created the compute network and storage objects they're all integrated right inside the the vCenter console and so once again from a diagnostics and troubleshooting perspective this data is invaluable it often saves hours just in trying to figure out what what we're even talking about when we're trying to resolve an issue so the you know as you can see this is all baked right into V Center the V Center experience isn't transformed a lot we get a lot of VI admins who look at this and say where's the kubernetes and they're surprised that like they've been managing kubernetes all this time it just looks it looks like the vSphere experience they've already got but all those kubernetes objects the pods and containers kubernetes clusters load balancer stores they're all represented right there natively in the V Center UI and so we're able to take all of that and make it work for your existing VI admins well that's a it's pretty it's pretty wild you know it really builds off the vision that again I think you kind of outlined kid teased out it at VMworld which was you know the IT still sees vSphere which is what they want to see when they're used to seeing but devs siku Nettie's and really bringing those together in a unified environment so that depending on what your job is and what you're working on that's what you're gonna see in this kind of unified environment yeah yeah as the demo showed it is still vSphere at the center but now there's two different experiences that you can have interacting with vSphere the kubernetes base one which is of course great for developers and DevOps type folks as well as the traditional vSphere interface API is which is great for VI admins and IT operations right and then and really it was interesting to you tease that a lot that was a good little preview of people knew they're watching but you talked about really cloud journey and and kind of this bifurcation of kind of classical school apps that are that are running in their classic memes and then kind of the modern you know county cloud native applications built on kubernetes and youyou outlined a really interesting thing that people often talk about the two ends of the spectrum and getting from one to the other but not really about kind of the messy middle if you will and this is really enabling people to pick where along that spectrum they can move their workloads or move their apps ya know I think we think a lot about it like that that we look at we talk to customers and all of them have very clear visions on where they want to go their future state architecture and that involves embracing cloud it involves modernizing applications and you know as you mentioned that it's it's challenging for them because I think what a lot of customers see is this kind of these two extremes either you're here where you are kind of the old current world and you got the bright Nirvana future on the far end there and they believe it's the only way to get there is to kind of make a leap from one side to the other that you have to kind of change everything out from underneath you and that's obviously very expensive very time-consuming and very error-prone as well there's a lot of things that can go wrong there and so I think what we're doing differently at VMware is really to your point as you call it the the messy middle I would say it's more like how do we offer stepping stones along that journey rather than making this one giant leap we had to invest all this time and resources how come you able people to make smaller incremental steps each of which have a lot of business value but don't have a huge amount of cost right and its really enabling kind of this next gen application where there's a lot of things that are different about about one of the fundamental things is we're now the application defines a reach sources that it needs to operate versus the resources defining kind of the capabilities of what the what the application can't do and that's where everybody is moving as quickly as as makes sense you said not all applications need to make that move but most of them should and most of them are and most of them are at least making that journey you see that yeah definitely I mean I think that you know certainly this is one of the big evolutions we're making in vSphere from you know looking historically at how we managed infrastructure one of things we enable in VCR 7 is how we manage applications right so a lot of the things you would do in infrastructure management of setting up security rules or encryption settings or you know your your resource allocation you would do this in terms of your physical and virtual infrastructure you talk about it in terms of this VM is going to be encrypted or this VM is gonna have this firewall rule and what we do in vSphere 7 is elevate all of that to application centric management so you actually look at an application and say I want this application to be constrained to this much CPU or I want this application to be have these security rules on it and so that shifts the focus of management really up to the application level right yeah and like I kind of even zoom back a little bit there and say you know if you look back one thing we did was something like V San before that people had to put policies on a LUN you know an actual storage LUN and a storage array and then by virtue of a workload being placed on that array it inherited certain policies right and so these have turned that around allows you to put the policy on the VM but what jerez talking about now is that for a modern workload a modern were close not a single VM it's it's a collection of different things you've got some containers in there some VMs probably distributed maybe even some on-prem some in the cloud and so how do you start managing that more holistically and this notion of really having an application as a first-class entity that you can now manage inside of vSphere it's really powerful and very simplifying one right and why this is important is because it's this application centric point of view which enables the digital transformation that people are talking about all the time that's it's a nice big word but the rubber hits the road is how do you execute and deliver applications and more importantly how do you continue to evolve them and change them you know based on either customer demands or competitive demands or just changes in the marketplace yeah well you look at something like a modern app that maybe has a hundred VMs that are part of it and you take something like compliance right so today if I want to check of this app is compliant I got to go look at every individual VM and make sure it's locked down and hardened and secured the right way but now instead what I can do is I can just look at that one application object inside of each Center set the right security settings on that and I can be assured that all the different objects inside of it are gonna inherit that stuff so it really simplifies that it also makes it so that that admin can handle much larger applications you know if you think about vCenter today you might log in and see a thousand VMs in your inventory when you log in with vSphere seven what you see is a few dozen applications so a single admin can manage a much larger pool of infrastructure many more applications and they could before because we automate so much of that operation and it's not just the scale part which is obviously really important but it's also the rate of change and this notion of how do we enable developers to get what they want to get done done ie building applications well at the same time enabling the IT operations teams to put the right sort of guardrails in place around compliance and security performance concerns these sorts of elements and so being by being able to have the IT operations team really manage that logical application at that more abstract level and then have the developer be able to push in new containers or new VMs or whatever they need inside of that abstraction it actually allows those two teams to work actually together and work together better they're not stepping over each other but in fact now they can both get what they need to get done done and do so as quickly as possible but while also being safe and in compliance is ready fourth so there's a lot more to this is a very significant release right again a lot of foreshadowing if you go out and read the tea leaves that's a pretty significant you know kind of RER context or many many parts of ease of beer so beyond the kubernetes you know kind of what are some of the other things that are coming out and there's a very significant release yeah it's a great question because we tend to talk a lot about kubernetes what was project Pacific but is now just part of vSphere and certainly that is a very large aspect of it but to your point you know vSphere 7 is a massive release with all sorts of other features and so instead of a demo here let's pull up with some slides right look at what's there so outside of kubernetes there's kind of three main categories that we think about when we look at vSphere seven so the first first one is simplified lifecycle management and then really focus on security it's a second one and then applications as well out both including you know the cloud native apps that don't fit in the kubernetes bucket as well as others and so we go on the first one the first column there there's a ton of stuff that we're doing around simplifying life cycle so let's go to the next slide here where we can dive in a little bit more to the specifics so we have this new technology vSphere lifecycle management VL cm and the idea here is how do we dramatically simplify upgrades lifecycle management of the ESX clusters and ESX hosts how do we make them more declarative with a single image you can now specify for an entire cluster we find that a lot of our vSphere admins especially at larger scales have a really tough time doing this there's a lot of in and out today it's somewhat tricky to do and so we want to make it really really simple and really easy to automate as well so if you're doing kubernetes on kubernetes I suppose you're gonna have automation on automation right because they're upgrading to the sevens is probably not any consequent inconsequential tasks mm-hm and yeah and going forward and allowing you know as we start moving to deliver a lot of this great VCR functionality at a more rapid clip how do we enable our customers to take advantage of all those great things we're putting out there as well right next big thing you talk about is security yep we just got back from RSA thank goodness we got that that show in before all the badness started yeah but everyone always talked about security's got to be baked in from the bottom to the top yeah talk about kind of the the changes in the security so done a lot of things around security things around identity Federation things around simplifying certificate management you know dramatic simplifications there across the board one I want to focus on here on the next slide is actually what we call vSphere trust Authority and so with that one what we're looking at here is how do we reduce the potential attack surfaces and really ensure there's a trusted computing base when we talk to customers what we find is that they're nervous about a lot of different threats including even internal ones right how do they know all the folks that work for them can be fully trusted and obviously if you're hiring someone you somewhat trust them but you know what what's how do you implement that the concept of least privilege right or zero trust right yeah topic exactly so the idea with trust authorities that we can specify a small number of physical ESX hosts that you can really lock down and sure fully secure those can be managed by a special vCenter server which is in turn very lockdown only a few people have access to it and then those hosts and that vCenter can then manage other hosts that are untrusted and can use attestation to actually prove that okay these untrusted hosts haven't been modified we know they're okay so they're okay to actually run workloads on they're okay to put data on and that sort of thing so is this kind of like building block approach to ensure that businesses can have a very small trust base off of which they can build to include their entire vSphere environment right and then the third kind of leg of the stool is you know just better leveraging you know kind of a more complex asset ecosystem if you know what things like FPGAs and GPUs and you know kind of all of the various components that power these different applications which now the application could draw the appropriate resources as needed so you've done a lot of work here as well yeah there's a ton of innovation happening in the hardware space as you mentioned all sort of accelerators coming out we all know about GPUs and obviously what they can do for machine learning and AI type use cases not to mention 3d rendering but you know FPGAs and all sorts of other things coming down the pike as well there and so what we found is that as customers try to roll these out they have a lot of the same problems that we saw in the very early days of virtualization ie silos of specialized hardware that different teams were using and you know what you find is all things we found before you found we find very low utilization rates inability to automate that inability to manage that well putting security and compliance and so forth and so this is really the reality that we see at most customers and it's funny because and some ones you think well well shouldn't we be past this as an industry shouldn't we have solved this already you know we did this with virtualization but as it turns out the virtualization we did was for compute and then storage and network but now we really needed to virtualize all these accelerators and so that's where this bit fusion technology that we're including now with vSphere it really comes to the forefront so if you see in the current slide we're showing here the challenge is that just these separate pools of infrastructure how do you manage all that and so if you go to the we go to the next slide what we see is that with bit fusion you can do the same thing that we saw with compute virtualization you can now pool all these different silos infrastructure together so they become one big pool of GPUs of infrastructure that anyone in an organization can use we can you know have multiple people sharing a GPU we can do it very dynamically and the great part of it is is that it's really easy for these folks to use they don't even need to think about it in fact integrates seamlessly with their existing workflows so it's pretty it's pretty trick is because the classifications of the assets now are much much larger much varied and much more workload specific right that's really the opportunities flash they are they're good guys are diverse yeah and so like you know a couple other things just I don't have a slide on it but just things we're doing to our base capabilities things around DRS and vmotion really massive evolutions there as well to support a lot of these bigger workloads right so you look at some of the massive sa P Hana or Oracle databases and how do we ensure that the emotion can scale to handle those without impacting their performance or anything else they're making DRS smarter about how it does load balancing and so forth right now a lot of this stuff not just kind of brand new cool new accelerator stuff but it's also how do we ensure the core ass people have already been running for many years we continue to keep up with the innovation and scale there as well right all right so do I give you the last word you've been working on this for a while there's a whole bunch of admins that have to sit and punch keys what do you what do you tell them what should they be excited about what are you excited for them in this new release I think what I'm excited about is how you know IT can really be an enabler of the transformation of modern apps right I think today you look at a lot of these organizations and what ends up happening is the app team ends up sort of building their own infrastructure on top of IT infrastructure right and so now I think we can shift that story around I think that there's you know there's an interesting conversation that a lot of IT departments and appdev teams are gonna be having over the next couple years about how do we really offload some of these infrastructure tasks from the dev team make you more productive give you better performance availability disaster recovery and these kinds of capabilities awesome well Jared congratulations that get both of you for forgetting to release out I'm sure it was a heavy lift and it's always good to get it out in the world and let people play with it and thanks for for sharing a little bit more of a technical deep dive I'm sure there's ton more resources from people I even want to go down into the weeds so thanks for stopping by thank you thank you all right ease Jared he's kid I'm Jeff you're watching the cube we're in the Palo Alto studios thanks for watching we'll see you next time [Music] hi and welcome to a special cube conversation I'm Stu min a minute and we're digging into VMware vSphere seven announcement we've had conversations with some of the executives some of the technical people but we know that there's no better way to really understand a technology than to talk to some of the practitioners that are using it so really happy to have joined me for the program I have Bill Buckley Miller who is in infrastructure designer with British Telecom joining me digitally from across the pond bill thanks so much for joining us nice - all right so Phil let's start of course British Telecom I think most people know you know what BT is and it's a you know a really sprawling company tell us a little bit about you know your group your role and what's your mandate okay so my group it's called service platforms it's the bit of BT that services all of our multi millions of our customers so they we have broadband we have TV we have mobile we have DNS and email systems and one and it's all about our customers it's not a B to be part of BT you with me we we specifically focus on those kind of multi million customers that we've got in those various services I'm in particular my group is for we do infrastructure so we really do from data center all the way up to really about boot time or so we'll just past boot time and the application developers look after that stage and above okay great we definitely gonna want to dig in and talk about that that boundary between the infrastructure teams and the application teams but let's talk a little bit first you know we're talking about VMware so you know how long's your organization been doing VMware and tell us you know what you see with the announcement that VMware's making work BC or seven sure well I mean we've had a really great relationship with VMware for about twelve thirteen years something like that and it's a absolutely key part of our of our infrastructure it's written throughout BT really in every part of our operations design development and the whole ethos of the company is based around a lot of VMware products and so one of the challenges that we've got right now is application architectures are changing quite significantly at the moment and as you know in particular with serving us and with containers and a whole bunch of other things like that we're very comfortable with our ability to manage VMs and have been for a while we currently use extensively we use vSphere NSX t.v raps log insight network insight and a whole bunch of other VMware constellation applications and our operations teams know how to use that they know how to optimize they know how to capacity plan and troubleshoot so that's that's great and that's been like that for a half a decade at least we've been really really confident with our ability to still with Yemen where environments and Along Came containers and like I say multi cloud as well and what we were struggling with was the inability to have a cell pane a glass really on all of that and to use the same people and the same same processes to manage a different kind of technology so we we'd be working pretty closely with VMware on a number of different containerization products for several years now I would really closely with the b-string integrated containers guys in particular and now with the Pacific guys with really the idea that when we we bring in version 7 and the containerization aspects of version 7 we'll be in a position to have that single pane of glass to allow our operations team to really barely differentiate between what's a VM and what's a container that's really the holy grail right so we'll be able to allow our developers to develop our operations team to deploy and to operate and our designers to see the same infrastructure whether that's on premises cloud or off premises and be able to manage the whole piece in that was bad ok so Phil really interesting things you walked through here you've been using containers in a virtualized environment for a number of years want to understand in the organizational piece just a little bit because it sounds I manage all the environment but you know containers are a little bit different than VMs you know if I think back you know from an application standpoint it was you know let's stick it in a vm I don't need to change it and once I spin up a VM often that's gonna sit there for you know months if not years as opposed to you know I think about a containerization environment it's you know I really want a pool of resources I'm gonna create and destroy things all the time so you know bring us inside that organizational piece you know how much will there need to be interaction and more interaction or change in policies between your infrastructure team and your app dev team well yes making absolutely right that's the nature and that the time scales that were talking about between VMs and containers oh he's wildly different as you say we we probably oughta certainly have VMs in place now that were in place in 2000 and 2018 certainly but I imagine I haven't haven't really been touched whereas as you say VMs and a lot of people talk about spinning them all up all the time there are parts of our architecture that require that in particular the very client facing bursty stuff it you know does require spinning up spinning down pretty quickly but some of our smaller the containers do sit around for weeks if not if not months I really just depend on the development cycle aspects of that but the heartbeat that we've we've really had was just the visualizing it and there are a number different products out there that allow you to see the behavior of your containers and understand the resource requirements that they are having at any given moment allows troubleshoot and so on but they are not they need their new products their new things that we we would have to get used to and also it seems that there's an awful lot of competing products quite a Venn diagram if in terms of functionality and user abilities to do that so through again again coming back to being able to manage through vSphere to be able to have a list of VMs and alongside it is a list of containers and to be able to use policies to define how the behave in terms of their networking to be able to essentially put our deployments on Rails by using in particular tag based policies means that we can take the onus of security we can take the onus of performance management and capacity management away from the developers you don't really care about a lot of time and they can just get on with their job which is to develop new functionality and help our customers so that then means that then we have to be really responsible about defining those policies and making sure that they're adhered to but again we know how to do that with VMs new visa so the fact that we can actually apply that straightaway just to add slightly different completely unit which is really what we're talking about here is ideal and then to be able to extend that into multiple clouds as well because we do use multiple cards where AWS and as your customers and were between them is an opportunity that we can't do anything of them be you know excited about take oh yeah still I really like how you described it really the changing roles that are happening there in your organization need to understand right there's things that developers care about you know they want to move fast they want to be able to build new things and there's things that they shouldn't have to worry about and you know we talked about some of the new world and it's like oh can the platform underneath this take care of it well there there's some things platforms take care of there's some things that the software or you know your theme is going to need to understand so maybe if you could dig in a little bit some of those what are the drivers from your application portfolio what is the business asking of your organization that that's driving this change and you know being one of those you know tailwind pushing you towards you know kubernetes and the the vSphere 7 technologies well it all comes down with the customers right our customers want new functionality they want new integrations they want new content and they want better stability and better performance and our ability to extend or contracting capacity as needed as well so they're the real ultimate we want to give our customers the best possible experience of our products and services so we have to address that really from a development perspective it's our developers that have the responsibility to design them to deploy those so we have to in infrastructure we have to act as a firm foundation really underneath all of that that allows them to know that what they spend their time and develop and want to push out to our customers is something that can be trusted as performant we understand where their capacity requirements are coming from in in the short term and in the long term for that and it's secure as well obviously is a big aspect to it so really we're just providing our developers with the best possible chance of giving our customers what will hopefully make them delighted great Phil you've mentioned a couple of times that you're using public clouds as well as you know your your your your VMware farm one of make sure I if you can explain a little bit a couple of things number one is when it comes to your team especially your infrastructure team how much are they involved with setting up some of the the basic pieces or managing things like performance in the public cloud and secondly when you look at your applications are some of your clouds some of your applications hybrid going between the data center and the public cloud and I haven't talked to too many customers that are doing applications that just live in any cloud and move things around but you know maybe if you could clarify those pieces as to you know what cloud really means to your organization and your applications sure well I mean to us climate allows us to accelerate development she's nice because it means we don't have to do on-premises capacity lifts for new pieces of functionality or so we can initially build in the cloud and test in the cloud but very often applications really make better sense especially in the TV environment where people watch TV all the time I mean yes there are peak hours and lighter hours of TV watching same goes for broadband really but we generally we're well more than an eight-hour application profile so what that allows us to do then is to have well it makes sense we run them inside our organization where we have to run them in our organization for you know data protection reasons or whatever then we can do that as well but where we say for instance we have a boxing match on and we're going to be seen enormous spike in the amount of customers that want to sign up into our order journey for to allow them to view that and to gain access to that well why would you spend a lot of money on servers just for that level of additional capacity so we do absolutely have hybrid applications not sorry hybrid blocks we have blocks of suburb locations you know dozens of them really to support oil platform and what you would see is that if you were to look at our full application structure for one of the platform as I mentioned that some of the smoothers application blocks I have to run inside some can run outside and what we want to be able to do is to allow our operations team to define that again by policy as to where they run and to you know have a system that allows us to transparently see where they're running how they're running and the implications of those decisions so that we can tune those maybe in the future as well and that way we best serve our customers we you know we get to get our customers yeah what they need all right great Phil final question I have for you you've been through a few iterations of looking at VMS containers public cloud what what advice would you give your peers with the announcement of vSphere 7 and how they can look at things today in 2020 versus what they might have looked at say a year or two ago well I'll be honest I was a little bit surprised by vSphere so we knew that VMware we're working on trying to make containers on the same level both from a management deployment perspective as we MS I mean they're called VMware after all we knew that they were looking it's no surprise by just quite how quickly they've managed to almost completely reinvent their application really it's you know if you look at the whole tansy stuff from the Mission Control stuff I think a lot of people were blown away by just quite how happy VMware were to reinvent themselves and from an application perspective you know and to really leap forward and this is the very between version six and seven I've been following these since version three at least and it's an absolutely revolutionary change in terms of the overall architecture the aims to - what they want to achieve with the application and you know luckily the nice thing is is that if you're used to version six is not that big a deal it's really not that big a deal to move forward at all it's not such a big change to process and training and things like that but my word there's no awful lot of work underneath that underneath the covers and I'm really excited and I think other people in my position should really just take it as an opportunity to really revisit what they can achieve with them in particular with vSphere and with in combination with and SXT it's it's but you know it's quite hard to put into place unless you've seen the slide or slides about it and useless you've seen the products just how revolutionary the the version 7 is compared to previous revisions which have kind of evolved for a couple of years so yeah I think I'm really excited to run it and know a lot of my peers other companies that I speak with quite often are very excited about seven as well so yeah I'm really excited about the whole ball base well Phil thank you so much absolutely no doubt this is a huge move for VMware the entire company and their ecosystem rallying around helped move to the next phase of where application developers and infrastructure need to go Phil Buckley joining us from British Telecom I'm Stu minimun thank you so much for watching the queue

>>Live from Copenhagen, Denmark. It's the Q covering Nutanix dot. Next 2019 brought to you by Nutanix. >>Welcome back everyone to the cubes live coverage of dot. Next here in Copenhagen. I'm your host, Rebecca Knight along with my cohost Stu Miniman. We are joined by Sammy Zog LaMi. He is the SVP sales Europe, Nutanix and Sylvan CU. He is the senior director systems engineer for EMEA at Newtanics. Thank you so much for coming on the cube for you for returning. And this is your first time. >>First time. Absolutely. >>Well I want to, I want to start with you. You were on the main stage this morning and you were describing being one of the first few employees in France, working out of hotel lobbies, keeping all the promotional materials in your house and people not even knowing how to pronounce Nutanix. Now here you are for you six years later. Describe, describe a little bit what it, what, what this journey has been like for you. Being at Nutanix >>for this journey. Um, you know, is a, is a successful journey obviously, uh, where we started from scratch in Eva, uh, where we built a lot of relationship with the channel. We started to have our first stories with customers and, uh, you know, the only thing we could not, uh, you know, focus was the speed of growth. And I, if you told me six years ago that we would be four and a half thousand, you know, in this conference, I wouldn't have believed it. And I think the, you know, overall journey is a, you know, an accelerated journey of development and that we have, >>yeah, Sam, Sammy, prednisone side, a little bit about, uh, you know, we sometimes call it nation building, but, uh, you know, the channel of course, a very important, uh, you know, talked about some of the, kind of, the challenges in, uh, some of the successes as to what, what has made Nutanix so successful, uh, in, in your time. Yeah. I think, uh, >>you know, the technology is for sure a big element in this that is solving business problems. But when you think about it, there's many stories of great technologies that didn't make it or didn't make it big. So I think the openness of this company from day one, uh, to work with partners to work with an ecosystem of Alliance partners. Uh, we were also very open to share how the Nutanix technology is built and is working. So there's a lot of openness around your Hasise works. It's not a black box. Uh, and we integrate with the ecosystem. So for our positioning, which is mainly initially the data center, the large environments we have to integrate into customer environment, we have to integrate with existing technologies and uh, the fact that we are open from day one and we keep that line is helping a lot in the traction. >>I want to get into that strategy in a little bit, but I want to bring you into this conversation to Sylvan and, and just to have you talk a little bit about what you're seeing in the competitive landscaping, what, what are some of the things that Nutanix needs to focus on? Because the competitors are a really edging in. We are focused to deliver >>our vision and continue to build the pieces that are still under construction there right now. And to be back on the question about the partners, the adoption also come first from the partners before their customers. And really working with them on engaging with them was the result of the success was not just signing contract enabled them, but really engaging with them at customer sites. And as soon as they see the reaction of the customer, they can be believe in it. And we scaled very fast because of them. I'm wondering, get both of your comments. Talk about the, uh, the competition for talent. Also, when you talk about Nutanix over 5,000, the channel is very strong. It makes it a little bit tougher, uh, to kind of pull those pieces in. If you're Silicon Valley, Oh, there's this startup, I want to join, things like that, but have to imagine things are a little bit different. And I'm in Mia, >>I would say. Well, competition for talent is definitely here in Emir, especially on the topics that we are tackling in the cloud, the DevOps, big data, et cetera. Um, now, you know, we are not attractive brand, uh, you know, there's a demonstrated pass of development for our employees. So I think on top of being a successful company, we have a lot of proof points of building careers. So people want to join for the fun for the success. We are also to be able to fast career. That's helps now saying that it's still not an easy task. You know, there's a, especially the volume of recruitment we are doing, uh, so we have organized ourselves very well, uh, to onboard people, enable people and maybe be in a position to hire people that don't have all the skills but have the right DNA and then we can, you know, always teach the skills. That's the way we are. >>and on a technical side, uh, all the user's previous it vendor let's say, was looking for specialists of complexity. You know, what is the behind the scene and we are in different situation, meaning that we can start small first and we talk about the project of the customer. And until this project works, we cannot move forward. We cannot obsessive. So our situation is more consultative and being a trusted advisor of what they tried to achieve and not anymore on what we tried to build our own our side. >>That's a very important point. The mindset of successful employees are the ones that are focused on the outcomes. You know, they're not here to sell a product, they focus on project and the outcome of customers. >>So how do you find that person when you are, when you're interviewing your pool of applicants? I mean that, that is, that is such an important part of the culture here, this people first attitude and really being all hands on deck if a customer has an issue. So how do you, how do you know when you're interviewing someone that, that, that they have got their, the right DNA to be here? >>Well, first we knew before they, during the interview, because we are well connected on the market and we have sources of information about how they operate on day to day. Now, of course, of hiring so many people over the years helps. And there's a lot of small details that, you know, we can notice, uh, in, uh, in our recruitment process. I think we've gotten very professional in the way we recruit. We still have a lot of refills as well from employees, which helps in terms of, uh, you know, making sure we hiring the right DNA, but we want to diversify. We don't want people coming from the same background. We're doing a pretty good job on diversity, on every topic, you know, gender, ethnicity, background, uh, this is a, you know, pretty good success. Alright, so >>semi you, you've got a new role. So it gives us a little bit of insight as to your vision. What should we should expect to see as a strategy for Nutanix and EMEA? >>I would say first, uh, you know, three months on the job and I have no intent to break anything that works. Uh, I think there's a successful recipe in anemia, which is a legacy of Chris Keller Ross. Uh, lots of good methodologies, verse of good principles of working, no intention to change that and maybe the phase after that for MEA, but for the whole company is to focus on Australia. And we see that, you know, our technology is well suited for mission critical environment is well suited for strategic projects for customers. And maybe we should become the default, uh, you know, uh, vendor that you think about when you go for mission critical projects and you know, trust formation. Uh, I think today we do a very broad set of projects with customers. Um, tomorrow I would like customers to think first about Nutanix when they think about something that is critical to their business. >>And in the same way for partners, uh, if we can move from being a vendor with high grows, great margin to a vendor that is helping them transform, you know, their business model or the way they attack different segments, you know, then we will have achieved a good phase two. What do you see as the biggest challenges facing you right now? Well, the biggest challenge is inside clearly is growth. We see that in every area, every time we grow fast, then suddenly you need to change organization processes, your principle of working and you, you need to reassess yourself and your way of doing things. Even at pesonal level. Uh, that's the biggest challenge. I think we, if we are not constantly paranoid about re re assessing that uh, growth can break a lot of quality, uh, in the relationship we have with customers but also in our velocity. >>Oh, I wonder if you could bring us inside the customers a little bit. What are some of the key roles that you find in, you know, where does Nutanix has the best engagement with and you know, strategically where would Nutanix may be a change over time as to where they're, where they're engaging with a customer. >>So now there is no more question about the fact that part of the, it will be in the cloud part will be internally, some people will go more one side or the other side because Nutanix both technology >>on both sides, we can take care of old school application and be sure that can still run in the cloud. And on this society, if you develop an application totally distributed and so on, meaning a cloud native, we can run it on a Nutanix and all the platform looks like the pubic cloud for this application. So we are the unique situation where we can, we don't need to be in the cloud or outside of the cloud, meaning that we can give a strategy with the customers or what it can do. What is the good point, what is the most difficult to achieve on both sides. And also we provide a way to package application to deploy everywhere. We have all these governance tools on top of it because we know the new way of consuming the cloud is more open bar, which you need some way of controlling the situation and we are really trusted advisor on their strategy to define what will be their it in two, three or four years. >>Okay. So sounds like not just the infrastructure owner but talking to the application owner or some of the C suite that might make some of those broader strategic decisions. >>Yeah. Yeah, exactly. Uh, the platform works, meaning that there is no more cushion on that at scale. You get all the benefits that you can see on the, on the public cloud. Now it's more the way you consume it, you organize the consumption and also you've have those, the same of urine Mount whatever is the application, uh, to, to find the, to have the best place for this application. >>What would you say your, your, your here as you said, uh, at in Copenhagen, thousands of European customers all here under one roof. What are you getting out of this? What kind of conversations are you hearing? What's most surprising to you? Just to, I mean we're, I know we're only in the beginning of day one, but what, what do you, what are you hearing right now? >>Well, we talked to a few customers already and what's a very common pattern? Most of the customers I took so far, they really accelerating on becoming a service organization. So enterprise companies, they really want to organize themselves to be cloud ops. And even though we were talking about automation before, now they really are doing it and they are actually focusing on changing the skills of their teams, their organizations and of course the technology afterwards. >>Yeah. Uh, any, any particular is on automation. Cause I think back, we've been talking about automation my entire career. I agree with you today. It is a, you know, more substantial conversation on automation. Are there any particular as either in Newtanics portfolio where some of the kind of partner tooling out there that are kicking things along? >>So, uh, we talk about automation since a long time, but most of the time that was, you have an orchestrator, it's like a Swiss knife and you can orchestrate what you want, but at the end of the day, nothing was done. We believe that the platform must be automated by design, right? And everything need to be by design. So it's a, it's the difference between the, between the previous way of thinking, automation and now where the platform is totally it. >>I believe Leber GF said autonomous is what >>we were looking for. Yes. You got to the point. If it's not autonomous, why? Why bother? Yeah. Or we had examples of customers who launched private cloud projects and they had like 8,000 Mondays to build the orchestration of the private cloud. And honestly, if you don't have a a hundred thousand VMs to run, it makes no sense. So the fact that no, it's built in and it's not a project to have automation, you know, that makes sense economically as well. Great. Well semi and see you. Thank you so much for coming on the cube. It's a pleasure having you later, Rebecca. Thanks a lot. Thank you. I'm Rebecca Knight for Stu Mittleman. Stay tuned for more of the cubes live coverage of.next.

>> from San Matteo. It's the Cube covering scaler Innovation Day Brought to you by scaler. >> I'm John for the Cube. We are here in San Mateo, California, for special Innovation Day with scaler at their headquarters. Their new headquarters here. I'm here. She here. Lou, Who's Xia Liu? Who's the software engineering team? Good to see you. Thanks for joining. >> Thank you. >> So tell us, what do you do here? What kind of programming? What kind of engineering? >> Sure. Eso i'ma back and suffer engineer at scaler. What I work on from the day to day basis is building our highly scaleable distributed systems and serving our customers fast queries. >> What's the future that you're building? >> Yeah. So one of the project that I'm working on right now is it will help our infrastructure to move towards a more stateless infrastructure s o. The project itself is a meta data storage component and a series of AP ice that Comptel are back and servers where to find a lock file. That might sound really simple, but at the massive scale of ours, it is actually a significant challenge to do it fast and reliably. >> And you're getting date is a big challenge or run knows that data is the new oil date is the goal. Whatever the people saying, the states is super important. You guys have a unique architecture around data ingest What's so unique about it? You mind sharing? >> Of course, s O. We have a lot of things that we do or don't do. Uniquely. I would like to start with the ingestion front of things and what we don't do on that front. So we don't do keywords indexing which most other extinct existing solutions, too. By not doing that, not keeping the index files up to date with every single log message that's incoming. We saved a lot of time and resource, actually, from the moment that our customers applications generate a logline Teo that logline becoming available to for search in scaler. You y that takes just a couple of seconds on DH on other existing solutions. That can take hours. >> So that's the ingests I What about the query side? Because you got in just now. Query. What's that all about? >> Yeah, of course. Actually. Do you mind if we go to black board a little bit? >> Take a look. >> Okay. Grab a chart real quick. Um, so we have a lot of servers around here. We have, uh, Q >> servers. Let's see. >> These are accused servers and, um, a lot of back and servers, Um, just to reiterate on the interest inside a little bit. When locks come in, they will hit one of these Q servers, and you want them Any one of them. And the Q server will kind of batch the log messages together and then pick one of the bag and servers at random and send the batch of locks. Do them any Q can reach any back in servers. And that's how we kind of were able to handle gigs of laughs. How much ever log that you give us way in jazz? Dozens of terabytes of data on a daily basis. Um, and then it is this same farm of back and servers. That's kind of helping us on the query funds crave front. Um, our goal is when a query comes in, we summon all of these back and servers at once. We get all of their computation powers, all of their CPU cores, to serve this one queer Ari, And that is just a massively scalable multi tenant model and in my mind is really economies of scale at its best. >> So scales huge here. So they got the decoupled back in and accused Q system. But yet they're talking to each other. So what's the impact of the customer? What some of the order of magnitude scale we're talking about here? >> Absolutely. So for on the loch side, we talked about seconds response time from logs being generated, too. They see the lock show up and on the query side, um, the median response time of our queries is under 100 milli second. And we defined that response time from the moment the customer hit in the return button on their laptop to they see results show up and more than 90% of our queries return results in under one second. >> So what's the deployment model for the customers? So I'm a customer. Oh, that sounds great. Leighton sees a huge issue one of low late and seek. His legacy is really the lag issue for data. Do I buy it as a service on my deploying boxes? What does this look like here? >> Nope. Absolutely. Adult were 100 plan cloud native. All of this is actually in our cloud infrastructure and us a customer. You just start using us as a sulfur is a service, and when you submit a query, all of our back and servers are at your service. And what's best about this model is that asks Keller's business girls. We will add more back and servers at more computation power and you as a customer's still get all of that, and you don't need to pay us any extra for the increased queries. >> What's the customer news case for this given you, given example of who would benefit from this? >> Absolutely. So imagine your e commerce platform and you're having this huge black Friday sales. Seconds of time might mean millions of revenues to you, And you don't wantto waste any time on the logging front to debug into your system to look at your monitoring and see where the problem is. If you ever have a problem, so we give you a query response time on the magnitude of seconds versus other is existing solutions. Maybe you need to wait for minutes anxiously in front of your computer. >> She What's the unique thing here? This looks like a really good actor, decoupling things that might make sense. But what's the What's the secret sauce? You? What's the big magic here? >> Yeah, absolutely. So anyone can kind of do a huge server farm Route Fours query approach. But the 1st 80% of a brute force algorithm is easy. It's really the last 20%. That's kind of more difficult, challenging and really differentiate. That's from the rest of others. Solutions. So to start with, we make every effort we can teo identify and skip the work that we don't have to do. S O. Maybe we can come back to your seats. >> Cut. >> Okay, so it's so it's exciting. >> Yeah. So we there are a couple things we do here to skip the work that we don't have to do. As we always say, the fastest queries are those we don't even have to run, which is very true. We have this Colin, our database that wee boat in house highly performance for our use case that can lead us only scan the columns that the customer cares about and skipped all the rest. And we also build a data structure called bloom Filters And if a query term does not occur in those boom filters, we can just skip the whole data set that represents >> so that speed helps on the speed performance. >> Absolutely. Absolutely. If we don't even have to look at that data set, >> You know, I love talking to suffer engineers, people on the cutting edge because, you know, you guys were startup. Attracting talent is a big thing, and people love to work on hard problems. What's the hard problem that you guys are solving here? >> Yeah, absolutely. S o we we have this huge server farm at at our disposal. It's, however, as we always say, the key to brute force algorithms is really to recruit as much force as possible as fast as we can. If you have hundreds thousands, of course lying around. But you don't have an effective way to some of them around when you need them. Then there's no help having them around 11 of the most interesting things that my team does is we developed this customised scatter gather algorithm in order to assign the work in a way that faster back and servers will dynamically compensate for slower servers without any prior knowledge. And I just love that >> how fast is going to get? >> Well, I have no doubt that will one day reach light speed. >> Specialist. Physics is a good thing, but it's also a bottleneck. Just what? Your story. How did you get into this? >> Yeah, s o. I joined Scaler about eight months ago as an ap s server, Actually. Sorry. As an FBI engineer, actually eso during my FBI days. I use scaler, the product very heavily. And it just became increasingly fascinated about the speed at which our queria runs. And I was like, I really want to get behind the scene and see what's going on in the back end. That gives us such fast query. So here I am. Two months ago, I switched the back and team. >> Well, congratulations. And thanks for sharing that insight. >> Thank you, John. Thank >> jumper here with Cuban Sites Day and Innovation Day here in San Mateo. Thanks for watching

(upbeat music) >> From our studios in the heart of Silicon Valley, Palo Alto, California, this is a CUBEConversation. >> Hi everyone, welcome to the special CUBEConversation. We're in Palo Alto, California, at theCUBE studio. I'm John Furrier, co-host of the CUBE. We're here with Chris Yeh. He's the co-founder and general partner of Blitzscaling Ventures, author of the book Blitzscaling with Reid Hoffman, founder of LinkedIn and a variety of other ventures, also a partner at Greylock Partners. Chris, great to see you. I've known you for years. Love the book, love Reid. You guys did a great job. So congratulations. But the big news is you're now a TV star as one of the original inaugural contestants on the Mental Samurai, just premiered on Fox, was it >> On Fox. >> On Fox, nine o'clock, on which days? >> So Mental Samurai is on Fox, Tuesdays at 9 p.m. right after Master Chef Junior. >> Alright. So big thing. So successful shows. Take us through the journey. >> Yeah. >> It's a new show, so it's got this kind of like Jeopardy vibe where they got to answer tough questions in what looks like a roller coaster kind of arm that moves you around from station to station, kind of jar you up. But it's a lot of pressure, time clock and hard questions. Tell us about the format. How you got that. Gives all the story. >> So the story behind Mental Samurai is it's from the producers of American Ninja Warrior, if you've ever seen that show. So American Ninja Warrior is a physical obstacle course and these incredible athletes go through and the key is to get through the obstacle course. If you miss any of the obstacles, you're out. So they took that and they translated it to the mental world and they said, okay, we're going to have a mental obstacle course where you going to have different kinds of questions. So they have memory questions, sequence questions, knowledge questions, all these things that are tapping different elements of intelligence. And in order to win at the game, you have to get 12 questions right in five minutes or less. And you can't get a single question wrong. You have to be perfect. >> And they do try to jar you up, to kind of scrabble your brain with those devices, it makes it suspenseful. In watching last night at your watch party in Palo Alto, it's fun to watch because yeah, I'm like, okay, it's going to be cool. I'll support Chris. I'll go there, be great and on TV, and oh my, that's pretty interesting. It was actually riveting. Intense. >> Yeah. You have that element of moving around from station to station and it's dramatic. It's kind of a theater presence. But what's it like in there? Give us some insight. You're coming on in April 30th so you're yet to come on. >> Yes. >> But the early contestants, none of them made it to the 100,000. Only one person passed the first threshold. >> Right >> Take us through the format. How many thresholds are there? What's the format? >> Perfect, so basically when a competitor gets strapped into the chair, they call it Ava, it's like a robot, and basically they got it from some company in Germany and it has the ability to move 360 degrees. It's like an industrial robot or something. It makes you feel like you're an astronaut or in one those centrifugal force things. And the idea is they're adding to the pressure. They're making it more of a challenge. Instead of just Jeopardy where you're sitting there, and answering questions and bantering with Alex Trebek, you're working against the clock and you're being thrown around by this robot. So what happens is first you try to answer 12 questions correctly in less than five minutes. If you do that, then you make it through to the next round, what they call the circle of samurai and you win $10,000. The circle of samurai, what happens is there are four questions and you get 90 seconds plus whatever you have left over from your first run, to answer those four questions. Answer all four questions correctly, you win $100,000 and the official title of Mental Samurai. >> So there's only two levels, circle of samurai but it gets harder. Now also I noticed that it's, their questions have certain puzzles and there's certain kinds of questions. What's the categories, if you will, what's the categories they offer? >> Yes, so the different categories are knowledge, which is just classic trivia, it's a kind of Jeopardy stuff. There's memory, where they have something on screen that you have to memorize, or maybe they play an audio track that you have to remember what happened. And then there's also sequence where you have to put things in order. So all these different things are represented by these different towers which are these gigantic television screens where they present the questions. And the idea is in order to be truly intelligent, you have to be able to handle all of these different things. You can't just have knowledge. You can't just have pop culture. You got to have everything. >> So on the candidates I saw some from Stanford. >> Yeah. >> I saw an athlete. It's a lot of diversity in candidates. How do they pick the candidates? How did you get involved? Did your phone ring up one day? Were you identified, they've read your blog. Obviously they've, you're smart. I've read your stuff on Facebook. How did you get in there? (laughs) >> Excellent question. So the whole process, there's a giant casting department that does all these things. And there's people who just cast people for game shows. And what happened with me is many years ago back in 2014, my sister worked in Hollywood when I was growing up. She worked for ER and Baywatch and other companies and she still keeps track of the entertainment industry. And she sent me an email saying, hey, here's a casting call for a new show for smart people and you should sign up. And so I replied to the email and said hey I'm Chris Yeh. I'm this author. I graduate from Stanford when I was 19, blah blah blah blah. I should be on your show. And they did a bunch of auditions with me over the phone. And they said we love you, the network loves you. We'll get in touch and then I never heard. Turns out that show never got the green light. And they never even shot that show. But that put me on a list with these various casting directors. And for this show it turns out that there was an executive producer of the show, the creator of the show, his niece was the casting director who interviewed me back in 2014. And she told her uncle, hey, there's this guy, Chris Yeh, in Palo Alto. I think would be great for this new show you're doing. Why don't you reach out to him. So they reached out to me. I did a bunch of Skype auditions. And eventually while I was on my book tour for Blitzscaling, I got the email saying, congratulations, you're part of the season one cast. >> And on the Skype interviews, was it they grilling you with questions, or was it doing a mock dry run? What was some of interview vetting questions? >> So they start off by just asking you about yourself and having you talk about who you are because the secret to these shows is none of the competitors are famous in advance, or at least very few of them are. There was a guy who was a major league baseball pitcher, there's a guy who's an astronaut, I mean, those guys are kind of famous already, but the whole point is, they want to build a story around the person like they do with the Olympics so that people care whether they succeed or not. And so they start off with biographical questions and then they proceed to basically use flash cards to simulate the game and see how well you do. >> Got it, so they want to basically get the whole story arc 'cause Chris, obviously Chris is smart, he passed the test. Graduate when he's 19. Okay, you're book smart. Can you handle the pressure? If you do get it, there's your story line. So they kind of look from the classic, kind of marketing segmentation, demographics is your storylines. What are some of the things that they said to you on the feedback? Was there any feedback, like you're perfect, we like this about you. Or is it more just cut and dry. >> Well I think they said, we love your energy. It's coming through very strongly to the screen. That's fantastic. We like your story. Probably the part I struggle the most with, was they said hey, you know, talk to us about adversity. Talk to us about the challenges that you've overcome. And I tell people, listen, I'm a very lucky guy. A lot of great things have happened to me in life. I don't know if there's that much adversity that I can really complain about. Other people who deal with these life threatening illnesses and all this stuff, I don't have that. And so that was probably the part I struggled the most with. >> Well you're certainly impressive. I've known you for years. You're a great investor, a great person. And a great part of Silicon Valley. So congratulations, good luck on the show. So it's Tuesdays. >> 9 p.m. >> 9 p.m. >> On fox. >> On Fox. Mental Samurai. Congratulations, great. Great to be at the launch party last night. The watch party, there'll be another one. Now your episode comes out on April 30th. >> Yes. So on April 30th we will have a big Bay area-wide watch party. I'm assuming that admission will be free, assuming I find the right sponsors. And so I'll come back to you. I'll let you know where it's going to be. Maybe we should even film the party. >> That's, well, I got one more question on the show. >> Yeah. >> You have not been yet on air so but you know the result. What was it like sitting in the chair, I mean, what was it personally like for you? I mean you've taken tests, you've been involved with the situation. You've made some investments. There's probably been some tough term sheets here and there, board meetings. And all that experience in your life, what was it compared to, what was it like? >> Well, it's a really huge adrenaline rush because if you think about there's so many different elements that already make it an adrenaline rush and they all combine together. First of all, you're in this giant studio which looks like something out of a space-age set with this giant robotic arm. There's hundreds of people around cheering. Then you're strapped into a robotic arm which basically makes you feel like an astronaut, like every run starts with you facing straight up, right? Lying back as if you're about to be launched on a rocket. And then you're answering these difficult questions with time pressure and then there's Rob Lowe there as well that you're having a conversation with. So all these things together, and your heart, at least for me, my heart was pounding. I was like trying very hard to stay calm because I knew it was important to stay clam, to be able to get through it. >> Get that recall, alright. Chris, great stuff. Okay, Blitzscaling. Blitzscaling Ventures. Very successful concept. I remember when you guys first started doing this at Stanford, you and Reid, were doing the lectures at Stanford Business School. And I'm like, I love this. It's on YouTube, kind of an open project initially, wasn't really, wasn't really meant to be a book. It was more of gift, paying it forward. Now it's a book. A lot of great praise. Some criticism from some folks but in general it's about scaling ventures, kind of the Silicon Valley way which is the rocket ship I call. The rocket ship ventures. There's still the other venture capitals. But great book. Feedback from the book and the original days at Stanford. Talk about the Blitzscaling journey. >> And one of the things that happened when we did the class at Stanford is we had all these amazing guests come in and speak. So people like Eric Schmidt. People like Diane Greene. People like Brian Chesky, who talked about their experiences. And all of those conversations really formed a key part of the raw material that went into the book. We began to see patterns emerge. Some pretty fascinating patterns. Things like, for example, a lot of companies, the ones that'd done the best job of maintaining their culture, have their founders involved in hiring for the first 500 employees. That was like a magic number that came up over and over again in the interviews. So all this content basically came forward and we said, okay, well how do we now take this and put it into a systematic framework. So the idea of the book was to compress down 40 hours of video content, incredible conversations, and put it in a framework that somebody could read in a couple of hours. >> It is also one of those things where you get lightning in a ball, the classic and so then I'd say go big or go home. But Blitzscaling is all about something new and something different. And I'm reading a book right now called Loonshots, which is a goof on moonshots. It's about the loonies who start the real companies and a lot of companies that are successful like Airbnb was passed over on and they call those loonies. Those aren't moonshots. Moonshots are well known, build-outs. This is where the blitzscaling kind of magic happens. Can you just share your thoughts on that because that's something that's not always talked about in the mainstream press, is that a lot of there blitzscaling companies, are the ones that don't look good on paper initially. >> Yes. >> Or ones that no one's talking about is not in a category or herd mentality of investors. It's really that outlier. >> Yes. >> Talk about that dynamic. >> Yeah, and one of the things that Reid likes to say is that the best possible companies usually sound like they're dumb ideas. And in fact the best investment he's been a part of as a venture capitalist, those are the ones where there's the greatest controversy around the table. It's not the companies that come in and everyone's like this is a no-brainer, let's do it. It's the companies where there's a big fight. Should we do this, should we not? And we think the reason is this. Blitzscaling is all about being able to be the first to scale and the winner take most or the winner take all market. Now if you're in a market where everyone's like, this is a great market, this is a great idea. You're going to have huge competition. You're going to have a lot of people going after it. It's very difficult to be the first to scale. If you are contrarian and right you believe something that other people don't believe, you have the space to build that early lead, that you can then use to leverage yourself into that enduring market leadership. >> And one of the things that I observed from the videos as well is that the other fact that kind of plays into, I want to get your reaction, this is that there has to be a market shift that goes on too because you have to have a tailwind or a wave to ride because if you can be contrarian if there's no wave, >> Right. >> right? so a lot of these companies that you guys highlight, have the wave behind them. It was mobile computing, SaaSification, cloud computing, all kind of coming together. Talk about that dynamic and your reaction 'cause that's something where people can get confused on blitzscaling. They read the book. Oh I'm going to disrupt the dry cleaning business. Well I mean, not really. I mean, unless there's something different >> Exactly. >> in market conditions. Talk about that. >> Yeah, so with blitzscaling you're really talking about a new market or a market that's transforming. So what is it that causes these things to transform? Almost always it's some new form of technological innovation, or perhaps a packaging of different technological innovations. Take mobile computing for example. Many of the components have been around for a while. But it took off when Apple was able to combine together capacitative touchscreens and the form factor and the processor strength being high enough finally. And all these things together created the technological innovation. The technological innovation then enables the business model innovation of building an app store and creating a whole new way of thinking about handheld computing. And then based on that business model innovation, you have the strategy innovation of blitzscaling to allow you to grow rapidly and keep from blowing up when you grow. >> And the spirit of kind of having, kind of a clean entrepreneurial segmentation here. Blitzscaling isn't for everybody. And I want you to talk about that because obviously the book's popular when this controversy, there's some controversy around the fact that you just can't apply blitzscaling to everything. We just talk about some of those factors. There are other entrepreneurialship models that makes sense but that might not be a fit for blitzscaling. Can you just unpack that and just explain, a minute to explain the difference between a company that's good for blitzscaling and one that isn't. >> Well, a key thing that you need for blitzscaling is one of these winner take most or winner take all markets that's just enormous and hugely valuable, alright? The whole thing about blitzscaling is it's very risky. It takes a lot of effort. It's very uncomfortable. So it's only worth doing when you have those market dynamics and when that market is really large. And so in the book we talk about there being many businesses that this doesn't apply to. And we use the example of two companies that were started at the same time. One company is Amazon, which is obviously a blitzscaling company and a dominant player and a great, great company. And the other is the French Laundry. In fact, Jeff Bezos started Amazon the same year that Thomas Keller started the French Laundry. And the French Laundry still serves just 60 people a day. But it's a great business. It's just a very different kind of business. >> It's a lifestyle or cash flow business and people call it a lifestyle business but mainly it's a cash flow or not a huge growing market. >> Yeah. >> Satisfies that need. What's the big learnings that you learned that was something different that you didn't know coming out of blitzscaling experience? Something that surprised you, something that might have shocked you, something that might have moved you. I mean you're well-read. You're smart. What was some learnings that you learned from the journey? >> Well, one of the things that was really interesting to me and I didn't really think about it. Reid and I come from the startup world, not the big company world. One of the things that surprised me is the receptivity of big companies to these ideas. And they explained it to me and they said, listen, you got to understand with a big company, you think it's just a big company growing at 10, 15% a year. But actually there's units that are growing at 100% a year. There's units that are declining at 50% a year. And figuring out how you can actually continue to grow new businesses quicker than your old businesses die is a huge thing for the big, established companies. So that was one of the things that really surprised me but I'm grateful that it appears that it's applicable. >> It's interesting. I had a lot of conversations with Michael Dell before, and before they went private and after they went private. He essentially was blitzscaling. >> Yeah. >> He said, I'm going to winner take most in the mature, somewhat declining massive IT enterprise spend against the HPs of the world, and he's doing it and VMware stock went to an all time high. So big companies can blitz scale. That's the learning. >> Exactly. And the key thing to remember there is one of the reasons why somebody like Michael Dell went private to do this is that blitzscaling is all about prioritizing speed over efficiency. Guess who doesn't like that? Wall street doesn't like because you're taking a hit to earnings as you invest in a new business. GM for example is investing heavily in autonomous vehicles and that investment is not yet delivering cash but it's something that's going to create a huge value for General Motors. And so it's really tough to do blitzscaling as a publicly traded company though there are examples. >> I know your partner in the book, Reid Hoffman as well as in the blitzscaling at Stanford was as visible in both LinkedIn and as the venture capitalist of Greylock. But also he was involved with some failed startups on the front end of LinkedIn. >> Yeah. >> So he had some scar tissue on social networking before it became big, I'll say on the knowledge graph that he's building, he built at LinkedIn. I'm sure he had some blitzscaling lessons. What did he bring to the table? Did he share anything in the classes or privately with you that you can share that might be helpful for people to know? >> Well, there's a huge number of lessons. Obviously we drew heavily on Reid's life for the book. But I think you touched on something that a lot of people don't know, which is that LinkedIn is not the first social network that Reid created. Actually during the dot-com boom Reid created a company called SocialNet that was one of the world's first social networks. And I actually was one of the few people in the world who signed up and was a member of SocialNet. I think I had the handle, net revolutionary on that if you can believe that. And one of the things that Reid learned from his SocialNet experience turned into one of his famous sayings, which is, if you're not embarrassed by your first product launch, you've launched too late. With SocialNet they spent so much time refining the product and trying to get it perfectly right. And then when they launched it, they discovered what everyone always discovers when they launch, which is the market wants something totally different. We had no idea what people really wanted. And they'd wasted all this time trying to perfect something that they've theoretically thought was what the market wanted but wasn't actually what the market wanted. >> This is what I love about Silicon Valley. You have these kind of stories 'cause that's essentially agile before agile came out. They're kind of rearranging the deck chairs trying to get the perfect crafted product in a world that was moving to more agility, less craftsmanship and although now it's coming back. Also I talked to Paul Martino, been on theCUBE before. He's a tribe with Pincus. And it's been those founding fathers around these industries. It's interesting how these waves, they start off, they don't get off the ground, but that doesn't mean the category's dead. It's just a timing issue. That's important in a lot of ventures, the timing piece. Talk about that dynamic. >> Absolutely. When it comes to timing, you think about blitzscaling. If you start blitzscaling, you prioritize speed over efficiency. The main question is, is it the right time. So Webvan could be taken as an example of blitzscaling. They were spending money wildly inefficiently to build up grocery delivery. Guess what? 2000 was not the right time for it. Now we come around, we see Instacart succeeding. We see other delivery services delivering some value. It just turns out that you have to get the timing right. >> And market conditions are critical and that's why blitzscaling can work when the conditions are right. Our days back in the podcast, it was, we were right but timing was off. And this brings up the question of the team. >> Yeah. >> You got to have the right team that can handle the blitzscaling culture. And you need the right investors. You've been on both sides of the table. Talk about that dynamic because I think this is probably one of the most important features because saying you going to do blitzscaling and then getting buy off but not true commitment from the investors because the whole idea is to plow money into the system. You mentioned Amazon, one of Jeff Bezos' tricks was, he always poured money back into his business. So this is a capital strategy, as well financial strategy capital-wise as well as a business trait. Talk about the importance of having that stomach and the culture of blitzscaling. >> Absolutely. And I think you hit on something very important when you sort of talk about the importance of the investors. So Reid likes to refer to investors as financing partners. Or financing co-founders, because really they're coming on with you and committing to the same journey that you're going on. And one of the things I often tell entrepreneurs is you really have to dig deep and make sure you do more due diligence on your investors than you would on your employees. Because if you think about it, if you hire an employee, you can actually fire them. If you take money from an investor, there's no way you can ever get rid of them. So my advice to entrepreneurs is always, well, figure out if they're going to be a good partner for you. And the best way to do that is to go find some of the entrepreneurs they backed who failed and talked to those people. >> 'Cause that's where the truth will come out. >> Well, that's right. >> We stood by them in tough times. >> Exactly. >> I think that's classic, that's perfect but this notion of having the strategies of the elements of the business model in concert, the financial strategy, the capital strategy with the business strategy and the people strategy, all got to be pumping that can't be really any conflict on that. That's the key point. >> That's right, there has to be alignment because again, you're trying to go as quickly as possible and if you're running a race car and you have things that are loose and rattling around, you're not going to make it across the finish line. >> You're pulling for a pit stop and the guys aren't ready to change the tires, (snapping fingers) you know you're out of sync. >> Bingo. >> Chris, great stuff. Blitzscaling is a great book. Check it out. I recommend it, remember blitz scale is not for anyone, it's for the game changers. And again, picking your investors is critical on this. So if you picked the wrong investors, blitzscaling will blow up in a bad way. So don't, don't, pick properly on the visa and pick your team. Chris, so let's talk about you real quick to end the segment and the last talk track. Talk about your background 'cause I think you have a fascinating background. I didn't know that you graduated when you're 19, from Stanford was it? >> Yes. >> Stanford at 19, that's a great accomplishment. You've been an entrepreneur. Take us through your journey. Give us a quick highlight of your career. >> So the quick highlight is I grew up in Southern California and Santa Monica where I graduated from Santa Monica High School along with other luminaries such as Rob Lowe, Robert Downey, Jr., and Sean Penn. I didn't go at the same time that they did. >> They didn't graduate when they were 17. >> They did not, (John laughing) and Charlie Sheen also attended Santa Monica High School but dropped out or was expelled. (laughing) Go figured. >> Okay. >> I came up to Stanford and I actually studied creative writing and product design. So I was really hitting both sides of the brain. You could see that really coming through in the rest of my career. And then at the time I graduated which was the mid-1990s that was when the internet was first opening up. I was convinced the internet was going to be huge and so I just went straight into the internet in 1995. And have been in the startup world ever since. >> Must love that show, Halt and Catch Fire a series which I love reminiscing. >> AMC great show. >> Just watching that my life right before my eyes. Us old folks. Talk about your investment. You are at Wasabi Ventures now. Blitzscaling Ventures. You guys looks like you're going to do a little combination bring capital around blitzscaling, advising. What's Blitzscaling Ventures? Give a quick commercial. >> So the best way to think about it is for the entrepreneurs who are actually are blitzscaling, the question is how are you going to get the help you need to figure out how to steer around the corners to avoid the pitfalls that can occur as you're growing rapidly. And Blitzscaling Ventures is all about that. So obviously I bring a wealth of experience, both my own experience as well as everything I learned from putting this book together. And the whole goal of Blitzscaling Ventures is to find those entrepreneurs who have those blitzscalable opportunities and help them navigate through the process. >> And of course being a Mental Samurai that you are, the clock is really important on blitzscaling. >> There are actually are a lot of similarities between the startup world and Mental Samurai. Being able to perform under pressure, being able to move as quickly as possible yet still be accurate. The one difference of course is in our startup world you often do make mistakes. And you have a chance to recover from them. But in Mental Samurai you have to be perfect. >> Speed, alignment, resource management, capital deployment, management team, investors, all critical factors in blitzscaling. Kind of like entrepreneurial going to next level. A whole nother lesson, whole nother battlefields. Really the capital markets are flush with cash. Post round B so if you can certainly get altitude there's a ton of capital. >> Yeah. And the key is that capital is necessary for blitzscaling but it's not sufficient. You have to take that financial capital and you have to figure out how to combine it with the human capital to actually transform the business in the industry. >> Of course I know you've got to catch a plane. Thanks for coming by in the studio. Congratulations on the Mental Samurai. Great show. I'm looking forward to April 30th. Tuesdays at 9 o'clock, the Mental Samurai. Chris will be an inaugural contestant. We'll see how he does. He's tight-lipped, he's not breaking his disclosure. >> I've got legal requirements. I can't say anything. >> Just say he's sticking to his words. He's a man of his words. Chris, great to see you. Venture capitalist, entrepreneur, kind of venture you want to talk to Chris Yeh, co-founder, general partner of blitzscaling. I'm John Furrier for theCUBE. Thanks for watching. (upbeat music)