>>Hey everyone. Welcome to the AWS partner showcase season one, episode three women in tech. I'm your host. Lisa Martin. I've got two female rock stars joining me. Next Vera Reynolds is here engineering manager, telemetry at honeycomb, and one of our Cub alumni, Danielle GShock ISV PSA director at AWS joins us as well. Ladies. It's great to have you talking about a very important topic today. >>Thanks for having us. Yeah, thanks for having me. Appreciate it. >>Of course, Vera, let's go ahead and start with you. Tell me about your background and tech. You're coming up on your 10th anniversary. Happy anniversary. >>Thank you. That's right. I can't believe it's been 10 years, but yeah, I started in tech in 2012. I was an engineer for most of that time. And just recently, as of March switched to engineering management here at honeycomb and, you know, throughout my career, I was very much interested in all the things, right. And it was a big FOMO as far as trying a few different companies and products, and I've done things from web development to mobile, to platforms. It would be apt to call me a generalist. And in the more recent years, I was sort of gravitating more towards developer tool space. And for me, that came in the form of cloud Foundry circle CI, and now honeycomb. I actually had my eye on honeycomb for a while before joining, I came across a blog post by charity majors. Who's one of our founders and she was actually talking about management and how to pursue that and whether or not it's right for your career. >>And so I was like, who is this person? I really like her found the company. They were pretty small at the time. So I was sort of keeping my eye on them. And then when the time came around for me to look again, I did a little bit more digging, found a lot of talks about the product. And on the one hand, they really spoke to me as the solution. They talked about developers owning their coding in production and answering questions about what is happening, what are your users seeing? And I felt that pain, I got what they were trying to do. And also on the other hand, every talk I saw at the time was from an amazing woman, which I haven't seen before. So I came across charity majors again, Christine Young, who's our other founder. And then Liz Frank Jones, who's our, our principal developer advocate. And that really sealed the deal for me as far as wanting to work here. >>Yeah. Honeycomb is interesting. This is a female founded company. You two leaders, you mentioned that you liked the technology, but you were also attracted because you saw females and the leadership position. Talk to me a little bit about what that's like working for a female led organization at honeycomb. >>Yeah. You know, historically we have tried not to over index on that because there was this maybe fear or rareness of it taking away from our legitimacy as an engineering organization, from our success as a company. But I'm seeing that rhetoric shift recently because we believe that with great responsibility with great power comes great responsibility. And we're trying to be more intentional as far as using that attribute of our company. So I would say that for me, it was a choice between a few offers, right. And that was a selling point, for sure, because again, I've never experienced it and I've really seen how much they walk that walk. Even me being here and me moving into management, I think were both ways in which they really put a lot of trust and support in me. And so I it's been a great ride. >>Excellent. Sounds like it. Before we bring Danielle in to talk about the partnership. I do wanna have you here, talk to the audience a little bit about honeycomb, what technology it's delivering and what are its differentiators. >>Yeah, absolutely. So honeycomb is an observability tool that enables engineers to answer questions about the code that runs in production. And we work with a number of various customers. Some of them are Vanguards, slack. Hello, fresh. Just to name a couple. If you're not familiar with observability tooling, it's akin to traditional application performance monitoring, but we believe that observability is succeeding APM because APM tools were built at the time of monoliths and they just weren't designed to help us answer questions about complex distributed systems that we work with today, where things can go wrong anywhere in that chain. And you can't predict what you're gonna need to ask ahead of time. So some of the ways that we are different is our ability to store and query really rich data, which we believe is the key to understanding those complex systems. What I mean by rich data is something that has a lot of attributes. >>So for example, when an error happens, knowing who it happened to, which user ID, which I don't know region, they were in, what, what they were doing at the time and what was happening at the rest of your system. And our ingest engine is really fast. You could do it in as little as three seconds and we call data like this. I said, kind of rich data, contextual data. We refer it as having high ity and high dimensionality, which are big words. But at the end of the day, what that means is we can store and we can query this data and we can do it really fast. And to give you an example of how that looks for our customers, let's say you have a developer team who are using honeycomb to understand and observe their system. And they get a report that a user is experiencing a slowdown or something's wrong. >>They can go into honeycomb and figure out that this only happens to users who are using a particular language pack with their app. And they operated their app last week, that it only happens when they are trying to upload a file. And so it's this level of granularity and being able to zoom in and out under data that allows you to understand what's happening, especially when you have an incident going on, right. Or your really important high profile customer is telling you that something's wrong. And we can do that. Even if everything else in your other tools looks fine, right? All of your dashboards are okay. You're not actually getting paged on it, but your customers are telling you that something's wrong. And we believe that's where we shine in helping you there. >>Excellent. It sounds like that's where you really shine that realtime visibility is so critical these days. Danielle, Danielle, wanna bring you into the conversation. Talk to us a little bit about the honeycomb partnership from the AWS lens. >>Yeah. So excuse me, observability is obviously a very important segment in the cloud space, very important to AWS, because a lot of all of our customers, as they build their systems distributed, they need to be able to see where, where things are happening in the complex systems that they're building. And so honeycomb is a, is an advanced technology partner. They've been working with us for quite some time and they have a, their solution is listed on the marketplace. Definitely something that we see a lot of demand with our customers, and they have many integrations, which, you know, we've seen is key to success. Being able to work seamlessly with the rest of the services inside of the AWS platform. And I know that they've done some, some great things with people who are trying to develop games on top of AWS things in that area as well. And so very important partner in the observa observability market that we have >>You back to you, let's kind of unpack the partnership, the significance that honeycomb ha is getting from being partners with an organization as potent and pivotal as AWS. >>Yeah, absolutely. I know that this predates me to some extent, but I know for a long time, AWS and honeycomb has really pushed the envelope together. And I think it's a beneficial relationship for both ends. There is kind of two ways of looking at it. On the one side, there is our own infrastructure. So honeycomb runs on AWS and actually one of our critical workloads that supports that fast query engine that I mentioned uses Lambda. And it does so in a pretty Orthodox way. So we've had a long standing conversation with the AWS team as far as drawing outside those lines and kind of figuring out how to use the technology in a way that works for us and hopefully will work for other customers of theirs as well. That also allows us to ask for early access for certain features when they become available. >>And then that way we can be sort of the Guinea pigs and try things out in a way that migrates our system and optimizes our own performance, but also allows again, other customers of AWS to follow in that path. And then the other side of that partnership is really supporting our customers who are both honeycomb users and AWS users, because it's, as you imagine, quite a big overlap, and there are certain ways in which we can allow our customers to more easily get their data from AWS to honeycomb. So for example, last year we built a tool based on the new Lambda extension capability that allowed our users who run their applications in Lambdas to get that tele, telemetry data out of their applications and into honeycomb and it land was win-win >>Excellent. So I'm hearing a lot of synergies from a technology perspective, you're sticking with you, and then Danielle will bring you in. Let's talk about how honeycomb supports D and I across its organization. And how is that synergistic with AWS's approach? Yeah, >>Yeah, absolutely. So I, I sort of alluded to that hesitancy to over index on the women led aspect of ourselves. But again, a lot of things are shifting, we're growing a lot. And so we are recognizing that we need to be more intentional with our DEI initiatives, and we also notice that we can do better and we should do better. And to that, and we're doing a few things differently that are pretty recent initiatives. We are partnering with organizations that help us target specific communities that are underrepresented in tech. Some examples would be after tech hu Latinas in tech among a number of others. And another initiative is DEI head start. That's something that is an internal practice that we started that includes reaching out to underrepresented applicants before any new job for honeycomb becomes live. So before we posted to LinkedIn, before it's even live on our job speech, and the idea there is to kind of balance our pipeline of applicants, which the hope is we'll lead to more diverse hires in the long term. >>That's a great focus there. Danielle, I know we've talked about this before, but for the audience, in terms of the context of the honeycomb partnership, the focus at AWS for D E and I is really significant, unpack that a little bit for us. >>Well, let me just bring it back to just how we think about it with the companies that we work with, but also in, in terms of, you know, what we want to be able to do, excuse me, it's very important for us to, you know, build products that reflect the customers that we have. And I think, you know, working with a company like honeycomb that is looking to differentiate in a space by, by bringing in, you know, the experiences of many different types of people I genuinely believe. And I'm sure Vera also believes that by having those diverse perspectives, that we're able to then build better products for our customers. And, you know, it's one of, one of our leadership principles is, is rooted in this. I write a lot, it asks for us to seek out diverse perspectives and you can't really do that if everybody kind of looks the same and thinks the same and has the same background. So I think that is where our de and I, you know, I thought process is rooted and, you know, companies like honeycomb that give customers choice and differentiate and help them to do what they need to do in their unique environments is super important. So >>The, the importance of thought diversity cannot be underscored enough. It's something that is, can be pivotal to organizations. And it's very nice to hear that that's so fundamental to both companies, Barry, I wanna go back to you for a second. You, I think you mentioned this, the DEI headstart program, that's an internal program at honeycomb. Can you shed a little bit of light on that? >>Yeah, that's right. And I actually am in the process of hiring a first engineer for my team. So I'm learning a lot of these things firsthand and how it works is we try to make sure to pre-load our pipeline of applicants for any new job opening we have with diverse candidates to the best of our abilities. And that can involve partnering with the organizations that I mentioned or reaching out to our internal network and make sure that we give those applicants a head start, so to speak. >>Excellent. I like that. Danielle, before we close, I wanna get a little bit of, of your background. We've got various background in tech, she's celebrating her 10th anniversary. Give me a, a short kind of description of the journey that you've navigated through being a female in technology. >>Yeah, thanks so much. I really appreciate being able to share this. So I started as a software engineer back actually in the late nineties during the, the first.com bubble and have, have spent quite a long time actually as an individual contributor, probably working in software engineering teams up through 2014 at a minimum until I joined AWS as a customer facing solutions architect. I do think spending a lot of time, hands on, definitely helped me with some of the imposter syndrome issues that folks suffer from not to say I don't at all, but it, it certainly helped with that. And I've been leading teens at AWS since 2015. So it's really been a great ride. And like I said, I'm very happy to see all of our engineering teams change as far as their composition. And I'm, I'm grateful to be part of it. >>It's pretty great to be able to witness that composition change for the better last question for each of you. And we're almost out of time and Danielle, I'm gonna stick with you. What's your advice or your recommendations for women who either are thinking about getting into tech or those who may be in tech, maybe they're in individual contributor positions and they're not sure if they should apply for that senior leadership position. What do you advise them to do? >>I mean, definitely for the individual contributors, tech tech is a great career direction and you will always be able to find women like you, you have to maybe just work a little bit harder to join, have community in that. But then as a leader, representation is very important and we can bring more women into tech by having more leaders. So that's my, you just have to take the lead, >>Take the lead, love it there. Same question for you. What's your advice and recommendations for those maybe future female leaders in tech? >>Yeah, absolutely. Danielle mentioned imposter syndrome and I think we all struggle with it from time to time, no matter how many years it's been. And I think for me, for me, the advice would be if you're starting out, don't be afraid to ask questions and don't be afraid to kind of show a, a little bit of ignorance because we've all been there. And I think it's on all of us to remember what it's like to not know how things work. And on the flip side of that, if you are a more senior IC or in a leadership role, also being able to model just saying, I don't know how this works and going and figuring out answers together because that was a really powerful shift for me early in my career is just to feel like I can say that I don't know something. >>I totally agree. I've been in that same situation where just ask the question because you I'm guaranteed. There's a million other people in the room that probably has the, have the same question. And because of imposter syndrome, don't wanna admit, I don't understand that. Can we back up, but I agree with you. I think that is one of the best things. Raise your hand, ask a question, ladies. Thank you so much for joining me talking about honeycomb and AWS, what you're doing together from a technology perspective and the focus efforts that each company has on D and I, we appreciate your insights. >>Thank you so much for having us great talking to you. >>My pleasure, likewise for my guests, I'm Lisa Martin. You're watching the AWS partner showcase women in check.

>>Hey everyone. Welcome to the AWS partner showcase season one, episode three women in tech. I'm your host. Lisa Martin. I've got two female rock stars joining me. Next Vera Reynolds is here engineering manager, telemetry at honeycomb, and one of our Cub alumni, Danielle GShock ISV PSA director a at AWS joins us as well. Ladies. It's great to have you talking about a very important topic today. >>Thanks for having us. Yeah, thanks for having me. Appreciate it. >>Of course, Vera, let's go ahead and start with you. Tell me about your background and tech. You're coming up on your 10th anniversary. Happy anniversary. >>Thank you. That's right. I can't believe it's been 10 years, but yeah, I started in tech in 2012. I was an engineer for most of that time. And just recently, as of March switched to engineering management here at honeycomb and, you know, throughout my career, I was very much interested in all the things, right. And it was a big FOMO as far as trying a few different companies and products. And I've done things from web development to mobile, to platforms. It would be apt to call me a generalist. And in the more recent years, I was sort of gravitating more towards developer tool space. And for me, that came in the form of cloud Foundry circle CI, and now honeycomb. I actually had my eye on honeycomb for a while before joining, I came across a blog post by charity majors. Who's one of our founders and she was actually talking about management and how to pursue that and whether or not it's right for your career. >>And so I was like, who is this person? I really like her found the company. They were pretty small at the time. So I was sort of keeping my eye on them. And then when the time came around for me to look again, I did a little bit more digging, found a lot of talks about the product. And on the one hand, they really spoke to me as the solution. They talked about developers owning their coding in production and answering questions about what is happening, what are your users seeing? And I felt that pain, I got what they were trying to do. And also on the other hand, every talk I saw at the time was from an amazing woman, which I haven't seen before. So I came across charity majors again, Christine yen, who our other founder, and then Liz Frank Jones, who our principal developer advocate. And that really sealed the deal for me as far as wanting to work here. >>Yeah. Honeycomb is interesting. This is a female founded company. You're two leaders. You mentioned that you like the technology, but you were also attracted because you saw females in the leadership position. Talk to me a little bit about what that's like working for a female led organization at honeycomb. >>Yeah. You know, historically we have tried not to over index on that because there was this maybe fear or rareness of it taking away from our legitimacy as an engineering organization, from our success as a company. But I'm seeing that rhetoric shift recently because we believe that with great responsibility with great power comes great responsibility. And we're trying to be more intentional as far as using that attribute of our company. So I would say that for me, it was a choice between a few offers, right. And that was a selling point, for sure, because again, I've never experienced it and I've really seen how much they walk that walk. Even me being here and me moving into management, I think were both ways in which they really put a lot of trust and support in me. And so I it's been a great ride. >>Excellent. Sounds like it. Before we bring Danielle in to talk about the partnership. I do wanna have you here, talk to the audience a little bit about honeycomb, what technology it's delivering and what are its differentiators. >>Yeah, absolutely. So honeycomb is an observability tool that enables engineers to answer questions about the code that runs in production. And we work with a number of various customers. Some of them are Vanguard, slack. Hello, fresh. Just to name a couple. If you're not familiar with observability tooling, it's akin to traditional application performance monitoring, but we believe that observability is succeeding APM because APM tools were built at the time of monoliths and they just weren't designed to help us answer questions about complex distributed systems that we work with today, where things can go wrong anywhere in that chain. And you can't predict what you're gonna need to ask ahead of time. So some of the ways that we are different is our ability to store and query really rich data, which we believe is the key to understanding those complex systems. What I mean by rich data is something that has a lot of attributes. >>So for example, when an error happens, knowing who it happened to, which user ID, which I don't know region, they were in, what, what, what they were doing at the time and what was happening at the rest of your system. And our ingest engine is really fast. You can do it in as little as three seconds and we call data like this. I said, kind of rich data, contextual data. We refer it as having high ity and high dimensionality, which are big words. But at the end of the day, what that means is we can store and we can query this data and we can do it really fast. And to give you an example of how that looks for our customers, let's say you have a developer team who are using comb to understand and observe their system. And they get a report that a user is experiencing a slowdown or something's wrong. >>They can go into honeycomb and figure out that this only happens to users who are using a particular language pack with their app. And they operated their app last week, that it only happens when they are trying to upload a file. And so it's this level of granularity and being able to zoom in and out under data that allows you to understand what's happening, especially when you have an incident going on, right. Or your really important high profile customer is telling you that something's wrong. And we can do that. Even if everything else in your other tools looks fine, right? All of your dashboards are okay. You're not actually getting paged on it, but your customers are telling you that something's wrong. And we believe that's where we shine in helping you there. >>Excellent. It sounds like that's where you really shine that real time visibility is so critical these days. Danielle, Danielle, wanna bring you into the conversation. Talk to us a little bit about the honeycomb partnership from the AWS lens. >>Yeah. So excuse me, observability is obviously a very important segment in the cloud space, very important to AWS, because a lot of all of our customers, as they build their systems distributed, they need to be able to see where, where things are happening in the complex systems that they're building. And so honeycomb is a, is an advanced technology partner. They've been working with us for quite some time and they have a, their solution is listed on the marketplace. Definitely something that we see a lot of demand with our customers, and they have many integrations, which, you know, we've seen is key to success. Being able to work seamlessly with the rest of the services inside of the AWS platform. And I know that they've done some, some great things with people who are trying to develop games on top of AWS things in that area as well. And so very important partner in the observa observability market that we have. >>Vera a back to you, let's kind of unpack the partnership, the significance that honeycomb ha is getting from being partners with an organization as potent and pivotal as AWS. >>Yeah, absolutely. I Don know that this Predates me to some extent, but I Don know for a long time, AWS and honeycomb has really pushed the envelope together. And I think it's a beneficial relationship for both ends. There's kind of two ways of looking at it. On the one side, there is our own infrastructure. So honeycomb runs on AWS and actually one of our critical workloads that supports that fast query engine that I mentioned uses Lambda. And it does also in a pretty unorthodox way. So we've had a long standing conversation with the AWS team as far as drawing outside those lines and kind of figuring out how to use the technology in a way that works for us and hopefully will work for other customers of theirs as well. That also allows us to ask for early access for certain features when they become available. >>And then that way we can be sort of the Guinea pigs and try things out in a way that migrates our system and optimizes our own performance, but also allows again, other customers of AWS to follow in that path. And then the other side of that partnership is really supporting our customers who are both honeycomb users and AWS users, because it's, as you imagine, quite a big overlap, and there are certain ways in which we can allow our customers to more easily get their data from AWS to honeycomb. So for example, last year, we built a tool based on the new Lambda extension capability that allowed our users who run their applications in Lambdas to get that tele telemetry data out of their applications and into honeycomb and demand was win-win >>Excellent. So I'm hearing a lot of synergies from a technology perspective, you're sticking with you, and then Danielle will bring you in. Let's talk about how honeycomb supports D E and I across its organization. And how is that synergistic with AWS's approach Vera? >>Yeah, absolutely. So I sort of alluded to that hesitancy to over index on the women led aspect of ourselves. But again, a lot of things are shifting, we're growing a lot. And so we are recognizing that we need to be more intentional with our DEI initiatives, and we also notice that we can do better and we should do better. And to that end, we're doing a few things differently that are pretty recent initiatives. We are partnering with organizations that help us target specific communities that are underrepresented in tech. Some examples would be Africa, tech hu Latinas in tech among a number of others. And another initiative is DEI head start. That's something that is an internal practice that we started that includes reaching out to underrepresented applicants before any new job for honeycomb becomes live. So before we posted to LinkedIn, before it's even live on our job speech, and the idea there is to kind of balance our pipeline of applicants, which the hope is will lead to more diverse hires in the long term. >>That's a great focus there. Danielle, I know we've talked about this before, but for the audience, in terms of the context of the honeycomb partnership, the focus at AWS for D E and I is really significant, unpack that a little bit for us. >>Well, let me just bring it back to just how we think about it with the companies that we work with, but also in, in terms of, you know, what we want to be able to do, excuse me, it's very important for us to, you know, build products that reflect the customers that we have. And I think, you know, working with a company like honeycomb that is looking to differentiate in a space by, by bringing in, you know, the experiences of many different types of people I genuinely believe. And I'm sure Vera also believes that by having those diverse perspectives, that we're able to then build better products for our customers. And, you know, it's one of, one of our leadership principles is, is rooted in this. I write a lot, it asks for us to seek out diverse perspectives and you can't really do that if everybody kind of looks the same and thinks the same and has the same background. So I think that is where our de and I, you know, I thought process is rooted and, you know, companies like honeycomb that give customers choice and differentiate and help them to do what they need to do in their unique environments is super important. So >>The, the importance of thought diversity cannot be underscored enough. It's something that is, can be pivotal to organizations. And it's very nice to hear that that's so fundamental to both companies, Barry, I wanna go back to you for a second. You, I think you mentioned this, the DEI head start program, that's an internal program at honeycomb. Can you shed a little bit of light on that? >>Yeah, that's right. And I actually am in the process of hiring a first engineer for my team. So I'm learning a lot of these things firsthand and how it works is we try to make sure to pre-load our pipeline of applicants for any new job opening we have with diverse candidates to the best of our abilities. And that can involve partnering with the organizations that I mentioned or reaching out to our internal network and make sure that we give those applicants a head start, so to speak. >>Excellent. I like that. Danielle, before we close, I wanna get a little bit of, of your background. We've got various background in tech, she's celebrating her 10th anniversary. Give me a, a short kind of description of the journey that you've navigated through being a female in technology. >>Yeah, thanks so much. I really appreciate being able to share this. So I started as a software engineer back actually in the late nineties during the, the first.com bubble and have, have spent quite a long time actually as an individual contributor, probably working in software engineering teams up through 2014 at a minimum until I joined AWS as a customer facing solutions architect. I do think spending a lot of time, hands on, definitely helped me with some of the imposter syndrome issues that folks suffer from not to say I don't at all, but it, it certainly helped with that. And I've been leading teen at AWS since 2015. So it's really been a great ride. And like I said, I'm very happy to see all of our engineering teams change as far as their composition. And I'm, I'm grateful to be part of it. >>It's pretty great to be able to witness that composition change for the better last question for each of you. And we're almost out of time and Danielle, I'm gonna stick with you. What's your advice, your recommendations for women who either are thinking about getting into tech or those who may be in tech, maybe they're in individual contributor positions, and they're not sure if they should apply for that senior leadership position. What do you advise them to do? >>I mean, definitely for the individual contributors, tech tech is a great career direction and you will always be able to find women like you, you have to maybe just work a little bit harder to join, have community in that. But then as a leader, representation is very important and we can bring more women into tech by having more leaders. So that's my, you just have to take the lead, >>Take the lead. Love that various same question for you. What's your advice and recommendations for those maybe future female leaders in tech? >>Yeah, absolutely. Danielle mentioned imposter syndrome and I think we all struggle with it from time to time, no matter how many years it's been. And I think for me, for me, the advice would be if you're starting out, don't be afraid to ask questions and don't be afraid to kind of show a bit, a little bit of ignorance because we've all been there. And I think it's on all of us to remember what it's like to not know how things work. And on the flip side of that, if you are a more senior IC or in a leadership role, also being able to model just saying, I don't know how this works and going and figuring out answers together because that was a really powerful shift for me early in my career is just to feel like I can say that I don't know something. >>I totally agree. I've been in that same situation where just ask the question because you I'm guaranteed. There's a million outta people in the room that probably has the, have the same question and because an imposter syndrome don't wanna admit, I don't understand that. Can we back up, but I agree with you. I think that is one of the best things. Raise your hand and ask a question, ladies. Thank you so much for joining me talking about honeycomb and AWS, what you're doing together from a technology perspective and the focus efforts that each company has on D E and I, we appreciate your insights. >>Thank you so much for having us talking to >>My pleasure. Likewise, for my guests, I'm Lisa Martin. You're watching the AWS partner showcase women in.

>>Okay, we're back with Jen Vera, who's the Chief Human Resource Officer of Dell, and we're gonna discuss people, culture and hybrid work and leadership in the post isolation economy. Jen, the conversations that we had at Dell Tech World this past May around the new work environment were some of the most interesting and engaging that I had personally. So I'm really eager to, to get the update. It's great to see you again. Thanks for coming on the cube. >>Thanks for having me, Dave. There's been a lot of change, just a short amount of time, so I'm excited to, to share some of our learnings with >>You. I, I mean, I'll bet there has, I mean, post pandemic companies, they're trying, everybody's trying to figure out the return to work and, and what it looks like. You know, last May there was really a theme of flexibility, but depending, we talked about, well, millennial or not young old, and it's just really was mixed, but, so how have you approached the topic? What, what are your policies? What's changed since we last talked? You know, what's working, you know, what's still being worked? What would you recommend to other companies to over to you? >>Yeah. Well, you know, this isn't a topic that's necessarily new to Dell technology. So we've been doing hybrid before. Hybrid was a thing, so for over a decade we've been doing what we called connected workplace. So we have kind of a, a history and we have some great learnings from that. Although things did change for the entire world. You know, March of 2020, we went from kind of this hybrid to everybody being remote for a while. But what we wanted to do is, we're such a data driven company. There's so many headlines out there, you know, about all these things that people think could happen will happen, but there wasn't a lot of data behind it. So we took a step back and we asked our team members, How do you think we're doing? And we asked very kind of strong language, because we've been doing this for a while. >>We asked them, Do you think we're leading in the world of hybrid? And 86% of our team members said that were, which is great, but we always know there's nuance right behind that macro level. So we, we asked them a lot of different questions and we just went on this kind of myth busting journey and we decided to test some of those things. We're hearing about Culture Willow Road or new team members will have trouble being connected or millennials will be different. And we really just collected a lot of data, asked our team members what their experiences. And what we have found is really, you don't have to be together in the office all the time to have a strong culture, a sense of connection, to be productive and to have a really healthy business. >>Well, I like that you were data driven around it with the data business here. So, but, but there is a lot of debate around your culture and how it suffers in a hybrid environment and how remote workers won't get, you know, promoted. And so I'm curious, you know, and I've, and I've seen some like-minded companies like Dell say, Hey, we want you guys to work the way you wanna work. But then they've, I've seen them adjust and say, Well, yeah, but we also want you to know in the office, be so we can collaborate a little bit more. So what are you seeing at Dell and, and, and how do you maintain that cultural advantage that you're alluding to in this kind of strange, new ever changing world? >>Yeah. Well, I think, look, one approach doesn't fit all. So I don't think that the approach that works for Dell Technologies is necessarily the approach that works for every company. It works with our strategy and culture. It is really important that we listen to our team members and that we support them through this journey. You know, they tell us time and time again, one of the most special things about our culture is that we provide flexibility and choice. So we're not a mandate culture. We really want to make sure that our team members know that we want them to be their best and do their best. And not every individual role has the same requirements. Not every individual person has the same needs. And so we really wanna meet them where they are so that they can be productive. They feel connected to the team and to the company and engaged and inspired. >>So, you know, for, for us, it really does make sense to go forward with this. And so we haven't, we haven't taken a step back. We've been doing hybrid, We'll continue to do hybrid, but just like if you, you know, we talk about not being a mandate. I think the companies that say nobody will come in or you have to come in three days a week, all of that feels more limiting. And so what we really say is, work out with your team, work out with your role work, workout with your leader, what really makes the most sense to drive things forward. >>I, >>You were, were talking, that's >>What we, you were talking before about myths and you know, the, I wanna talk about team member performance cuz there's a lot of people believe that if, if you're not in the office, you have disadvantages, People in the office have the advantage cuz they get FaceTime. Is is that a myth? You know, is there some truth to that? What, what do you think about that? >>Well, for us, you know, we look, again, we just looked at the data. So we said we don't wanna create a have and have not culture that you're talking about. We really wanna have an inclusive culture. We wanna be outcome driven, we're meritocracy. But we went and we looked at the data. So pre pandemic, we looked at things like performance. We looked at rewards and recognition, we looked at attrition rates, we looked at sentiment, Do you feel like your leader is inspiring? And we found no meaningful differences in any of that or in engagement between those who worked fully remote, fully in the office or some combination between. So our data would bust that myth and say, it doesn't, you don't have to be in an office and be seen to get ahead. We have equitable opportunity. Now, having said that, you always have to be watching that data. And that's something that we'll continue to do and make sure that we are creating equal opportunity regardless of where >>You work. And it's personal too, I think, I think some people can be really productive at home. I happen to be one that I'm way more productive in the office cause the dogs aren't barking. I have less distractions. And so, yeah, I think we think, and I think the takeaway that in just in talking to, to, to you Jen and, and folks at Dell is, you know, whatever works for you, we're we're gonna, we're gonna support. So I, I wanted to switch gears a little bit and talk about leadership and, and very specifically empathic leadership has been said to be, have a big impact on attracting talent, retaining talent, but, but it's hard to have empathy sometimes. And I know I saw some stats in a recent Dell study. It was like two thirds the people felt like their organization underestimates the people requirements. And I, I ask myself, I'm like, Hmm, what am I missing? You know, with our folks. So especially as it relates to, to transformation programs. So how can human resource practitioners support business leaders generally, specifically as it relates to leading with empathy? >>I think empathy's always been important. You have to develop trust. You can have the best strategy in the world, right? But if you don't feel like your leader understands who you are, appreciates the the value that you bring to the company, then you're not gonna get very far. So I think empathetic leadership has always been part of the foundation of a trusting, strong relationship between a leader and a team member. But if I think we look back on the last two years, and I imagine it'll be even more so as we go forward, empathetic leadership will be even more important. There's so much going on in the world, politically, socially, economically, that taking that time to say you want your team members to see you as credible, that you and confident that you can take us forward, but also that, you know, and understand me as a human being. >>And that to me is really what it's about. And I think with regard to transformation that you brought up, I think one of the things we forget about as leaders, we've probably been thinking about a decision or a transformation for months or weeks and we're ready to go execute, We're ready to go operationalize that thing. And so sometimes when we get to that point, because we've been talking about it for so long, we sent out the email, we have the all hands and we just say we're ready to go. But our team members haven't always been on that journey for those months that we have. And so I think that empathetic moment to say, Okay, not everybody is on this change curve where I am. Let's take a pause, let me put myself in their shoes and really think about how we bring everybody along. Culture. >>You know, Jen, in the spirit of myth busting, I mean I'm one of those people who felt like that a business is gonna have a hard time, harder time fostering this culture of collaboration and innovation in post isolation economy as they, they could pre covid. But you know, I notice there's, there's an announcement today that came across my desk, I think it's from Newsweek. Yes. And, and it's the list of top hundred companies recognized for employee motivation satisfaction. And it was really interesting because you, you always see, oh, we're the top 10 or the top hundred, But this says as a survey of 1.4 million employees from companies ranging from 50 to 10,000 employees. And it recognizes the companies that put respect, caring, and appreciation for their employees at the center of their business model and doing so have earned the loyalty and respect of the people who work for them. >>Number one of the lists is Dell sap. So congratulations. SAP was number two. I mean, there really isn't any other tech company on there, certainly no large tech companies on there. So I always see these lists, they go, Yeah, okay, that's cool. Top a hundred, whatever. But top one in, in, in an industry where there's only two in the top is, is pretty impressive. And how does that relate to fostering my earlier skepticism of a culture of collaboration? So first of all, congratulations, you know, how'd you do it and how are you succeeding in, in this new world? >>Well thanks. It does feel great to be number one, but you know, it doesn't happen by accident. And I think while most companies have a, a culture and a spouse values, we have ours called the culture code. But it's really been very important to us that it's not just a poster on the wall or or words on paper. And so we embed our culture code into all of our HR practices, that whole ecosystem from recognition rewards to performance evaluation, to interviewee to development. We build it into everything. So it really reflects who we are and you experience it every day. And then to make sure that we're not, you know, fooling ourselves, we ask all of our employees, do you feel like the behaviors you see and the experience you have every day reflects the culture code? And 94% of our team members say that, in fact it does. So I think that that's really been kind of the secret to our success. If you, if you listen to Michael Dell, he'll always say, you know, the most special thing about Dell is our culture and our people. And that comes through being very thoughtful and deliberate to preserve and protect and continue to focus on our culture. >>Don't you think too that repetition and, well first of all, belief in that cultural philosophy is, is important and then kind of repeating, like you said, Yeah, it's not just a poster on the wall, but I remember like, you know, when we're kids, your parents tell you, okay, power a positive thinking, do want to others as others, you know, you have others do it to you. Don't make the see you're gonna do some dumb things but don't do the same dumb things twice and you sort of fluff it up. But then as you mature you say, Wow, actually those were, >>That you might have had a >>Were instilled in me and now I'm bringing them forward and you know, paying it forward. But, but so it, my, I guess my, my point is, and it's kind of a point observation, but I'll turn it into a question, is isn't isn't consistency and belief in your values really, really important? >>I couldn't agree with you more, right? I think that's one of those things that we talk about it all the time and as an HR professional, you know, it's not the HR people just talking about our culture, it's our business leaders, it's our ceo, it's our CEOs, it's our partners. We share our culture code with our partners and our vendors and our suppliers and, and everybody, this is important. We say when you interact with anybody at Dell Technologies, you should expect that this is the experience that you're gonna get. And so it is something that we talk about that we embed in, into everything that we do. And I think it's, it's really important that you don't just think it's a one and done cuz that's not how things really, really work >>Well. It's a culture of respect. You know, high performance, high expectations, accountability, having followed the company and worked with the company for many, many years, you always respect the dignity of your partners and your people. So really appreciate your time Jen. Again, congratulations on being number one. >>Thank you so much. >>You're very welcome. Okay. You've been watching a special presentation of the Cube inside Dell Technology Summit 2022. Remember, these episodes are all available on demand@thecube.net and you can check out silicon angle.com for all the news and analysis. And don't forget to check out wikibon.com each week for a new episode of breaking analysis. This is Dave Ante, thanks for watching and we'll see you next time.

>>The transformation of Dell into Dell emc. And now Dell Technologies has been one of the most remarkable stories in the history of the enterprise technology industry. The company has gone from a Wall Street darling rocket ship PC company to a Midling enterprise player, forced to go private to a debt laden powerhouse that controlled one of the most valuable assets in enterprise tech i e VMware, and now is a hundred billion dollar giant with a low margin business. A strong balance sheet in the broadest hardware portfolio in the industry and financial magic that Dell went through would make anyone's head spin. The last lever of Dell EMC of the Dell EMC deal was detailed in Michael Dell's book Play Nice But Win in a captivating chapter called Harry You and the Bolt from the Blue Michael Dell described how he and his colleagues came up with the final straw of how to finance the deal. >>If you haven't read it, you should. And of course, after years of successfully integrating EMC and becoming VMware's number one distribution channel, all of this culminated in the spin out of VMware from Dell and a massive wealth creation milestone pending, of course the Broadcom acquisition of VMware. So where's that leave Dell and what does the future look like for this technology powerhouse? Hello and welcome to the Cube's exclusive coverage of Dell Technology Summit 2022. My name is Dave Ante and I'll be hosting the program. Now today in conjunction with the Dell Tech Summit, we're gonna hear from four of Dell's senior executives, Tom Sweet, who's the CFO of Dell Technologies. He's gonna share his views on the company's position and opportunities going forward. He's gonna answer the question, why is Dell a good long-term investment? Then we'll hear from Jeff Boudreau, who's the president of Dell's ISG business. >>That unit is the largest profit driver of Dell. He's gonna talk about the product angle and specifically how Dell is thinking about solving the multi-cloud challenge. And then Sam Groot, who is the senior vice president of marketing, will come on the program and give us the update on Apex, which is Dell's as a service offering, and then the new Edge platform called Project Frontier. Now it's also cyber security Awareness month that we're gonna see if Sam has, you know, anything to say about that. Then finally, for a company that's nearly 40 years old, Dell actually has some pretty forward thinking philosophies when it comes to its culture and workforce. And we're gonna speak with Jen Vera, who's Dell's chief Human Resource Resource Officer about hybrid work and how Dell is thinking about the future of work. However, before we get into all this, I wanna share our independent perspectives on the company and some research that we'll introduce to frame the program. >>Now, as you know, we love data here at the cube and one of our partners, ETR has what we believe is the best spending intentions data for enterprise tech. So here's a graphic that shows ET R'S proprietary net score methodology in the vertical access. That's a measure of spending velocity. And on the X axis, his overlap of pervasiveness in the data sample, this is a cut for just the server, the storage, and the client sectors within the ETR taxonomy. So you can see Dell CSG products, laptops in particular are dominant on both the X and the Y dimensions. CSG is the client solutions group and accounts for nearly 60% of Dell's revenue and about half of its operating income. And then the arrow signifies that dot, that represents Dell's ISG business that we're gonna talk to Jeff Boudro about. That's the infrastructure solutions group. Now, ISG accounts for the bulk of of the remainder of Dell's business, and it is, it's, as I said, it's most profitable from a margin standpoint. >>It comprises the EMC storage business as well as the Dell server business and Dell's networking portfolio. And as a note, we didn't include networking in that cut had we done. So Cisco would've dominated the graphic. And frankly, Dell's networking business isn't industry leading in the same way that PCs, servers and storage are. And as you can see, the data confirms the leadership position Dell has in its client side, its server and its storage sectors. But the nuance is look at that red dotted line at 40% on the vertical axis that represents a highly elevated net score, and every company in the sector is below that line. Now we should mention that we also filtered the data for those companies with more than a hundred mentions in the survey, but the point remains the same. This is a mature business that generally is lower margin storage is the exception, but cloud has put pressure on margins even in that business in addition to the server space. >>The last point on this graphic is we put a box around VMware and it's prominently present on both the X and Y dimensions. VMware participates with purely software defined high margin offerings in this, in these spaces, and it gives you a sense of what might have been had Dell chosen to hold onto that asset or spin it into the company. But let's face it, the alternatives from Michael Dell were just too attractive and it's unlikely that a spin in would've unlocked the value in the way a spinout did, at least not in the near future. So let's take a look at the snapshot of Dell's financials. To give you a sense of where the company stands today, Dell is a company with over a hundred billion in revenue. Last quarter, it did more than 26 billion in revenue and grew at a quite amazing 9% rate for a company that size. >>But because it's a hardware company, primarily its margins are low with operating income, 10% of revenue, and at 21% gross margin with VMware on Dell's income statement before the spin, its gross margins. Were in the low thirties. Now, Dell only spends about 2% of revenue on r and d because because it's so big, it's still a lot of money. And you can see it is cash flow positive. Dell's free cash flow over the trailing 12 month period is 3.7 billion, but that's only 3.5% of trailing 12 month revenue. Dell's Apex, and of course it's hardware maintenance business is recurring revenue and that is only about 5 billion in revenue and it's growing at 8% annually. Now having said that, it's the equivalent of service now's total revenue. Of course, service now is 23% operating margin and 16% free cash flow margin and more than 5 billion in cash on the balance sheet and an 85 billion market cap. >>That's what software will do for you. Now Dell, like most companies, is staring at a challenging macro environment with FX headwinds, inflation, et cetera. You've heard the story and hence it's conservative and contracting revenue guidance. But the balance sheet transformation has been quite amazing. Thanks to VMware's cash flow, Michael Dell and his partners from Silver Lake at all, they put up around $4 billion of their own cash to buy EMC for 67 billion, and of course got VMware in the process. Most of that financing was debt that Dell put on its balance sheet to do the transaction to the tune of 46 billion. It added to the, to the balance sheet debt. Now Dell's debt, the core debt net of its financing operation is now down to 16 billion and it has 7 billion in cash in the balance sheet. So dramatic delta from just a few years ago. So pretty good picture. >>But Dell a hundred billion company is still only valued at 28 billion or around 26 cents on the revenue dollar H HP's revenue multiple is around 60 cents on the revenue dollar. HP Inc. Dell's, you know, laptop and PC competitor is around 45 cents. IBM's revenue multiple is almost two times. By the way, IBM has more than 50 billion in debt thanks to the Red Hat acquisition. And Cisco has a revenue multiple, it's over three x, about 3.3 x currently. So is Dell undervalued? Well, based on these comparisons with its peers, I'd say yes and no. Dell's performance relative to its peers in the market is very strong. It's winning and has an extremely adept go to market machine, but it's lack of software content and it's margin profile leads. One to believe that if it can continue to pull some valuation levers while entering new markets, it can get its valuation well above where it is today. >>So what are some of those levers and what might that look like going forward? Despite the fact that Dell doesn't have a huge software revenue component since spinning out VMware and it doesn't own a cloud, it plays in virtually every part of the hardware market and it can provide infrastructure for pr pretty much any application in any use case and pretty much any industry and pretty much any geography in the world and it can serve those customers. So its size is an advantage. However, the history for hardware heavy companies that try to get bigger has some notable failures, namely hp, which had to split into two businesses, HP Inc. And hp E and ibm, which has had in abysmal decade from a performance standpoint and has had to shrink to grow again and obviously do a massive 34 billion acquisition of Red Hat. So why will Dell do any better than these two? >>Well, it has a fantastic supply chain. It's a founder led company, which makes a cultural difference in our view, and it's actually comfortable with a low margin software, light business model. Most certainly, IBM wasn't comfortable with that and didn't have these characteristics, and HP was kind of just incomprehensible at the end. So Dell in my opinion, is a much better chance of doing well at a hundred billion or over, but we'll see how it navigates through the current headwinds as it's guiding down. Apex is essentially Dell's version of the cloud. Now remember, Dell got started late. HPE is further along from a model standpoint with GreenLake, but Dell has a larger portfolio, so they're gonna try to play on that advantage. But at the end of the day, these as a service offerings are simply ways to bring a utility model to existing customers and generate recurring revenue. >>And that's a good thing because customers will be loyal to an incumbent if it can deliver as a service and reduce risk for for customers. But the real opportunity lies ahead, specifically Dell is embracing the cloud model. It took a while, but they're on board as Matt Baker Dell's senior vice president of corporate strategy likes to say it's not a zero sum game. What it means by that is just because Dell doesn't own its own cloud, it doesn't mean Dell can't build value on top of hyperscale clouds, what we call super cloud. And that's Dell's strategy to take advantage of public cloud CapEx and connect on-prem to the cloud, create a unified experience across clouds and out to the edge that's ambitious and technically it's non-trivial. But listen to Dell's vice chairman and Coco, Jeff Clark, explain this vision, please play the clip. >>You said also technology and business models are tied together and enabler. That's if, if you believe that, then you have to believe that it's a business operating system that they want, They want to leverage whatever they can, and at the end of the day there's, they have to differentiate what they do. Well that, that's >>Exactly right. If I take that and what, what Dave was saying and and I, and I summarize it the following way, if we can take these cloud assets and capabilities, combine them in an orchestrated way to delivery a distributed platform, game over, >>Eh, pretty interesting, right? John Freer called it a business operating system. Essentially, I think of it sometimes as a cloud operating system or cloud operating environment to drive new business value on top of the hyperscale CapEx. Now, is it really game over? As Jeff Clark said, if Dell can do that, I'd say if it had that today, it might be game over for the competition, but this vision will take years to play out. And of course it's gotta be funded and now it's gonna take time. And in this industry it tends to move. Companies tend to move in lockstep. So as often as the case, it's gonna come down to execution and Dell's ability to enter new markets that are ideally, at least from my perspective, higher margin data management, extending data protection into cyber security as an adjacency and of course edge at telco slash 5G opportunities. >>All there for the taking. I mean, look, even if Dell doesn't go after more higher margin software content, it can thrive with a lower margin model just by penetrating new markets and throwing off cash from those markets. But by keeping close to customers and maybe through Tuck in acquisitions, it might be able to find the next nugget beyond today's cloud and on-prem models. And the last thing I'll call out is ecosystem. I say here ecosystem, ecosystem, ecosystem. Because a defining characteristic of a cloud player is ecosystem, and if Apex is Dell's cloud, it has the opportunity to expand that ecosystem dramatically. This is one of the company's biggest opportunities and challenges. At the same time, in my view, it's just scratching the surface on its partner ecosystem. And it's ecosystem today is is both reseller heavy and tech partner heavy. And that's not a bad thing, but in a, but it's starting to evolve more rapidly. >>The snowflake deal is an example of up to stack evolution, but I'd like to see much more out of that snowflake relationship and more relationships like that. Specifically I'd like to see more momentum with data and database. And if we live at a data heavy world, which we do, where the data and the database and data management offerings, you know, coexist and are super important to customers, like to see that inside of Apex, like to see that data play beyond storage, which is really where it is today and it's early days. The point is with Dell's go to market advantage, which which company wouldn't treat Dell like the on-prem hybrid edge super cloud player that I wanna partner with to drive more business. You'd be crazy not to, but Dell has a lot on its plate and we'd like to see some serious acceleration on the ecosystem front. In other words, Dell as both a selling partner and a business enabler with its platform, its programmable infrastructure as a service. And that is a moving target that will rapidly involve. And of course we'll be here watching and reporting. So thanks for watching this preview of Dell Technology Summit 2022. I'm Dave Vte. We hope you enjoy the rest of the program.

>>As we said in our analysis of Dell's future, the transformation of Dell into Dell emc and now Dell Technologies has been one of the most remarkable stories in the history of the technology industry. After years of successfully integrated EMC and becoming VMware's number one distribution channel, the metamorphosis of Dell com culminated in the spin out of VMware from Dell and a massive wealth creation milestone pending, of course the Broadcom acquisition of VMware. So where's that leave Dell and what does the future look like for this technology powerhouse? Hello and welcome to the Cube's exclusive coverage of Dell Technology Summit 2022. My name is Dave Ante and I'll be hosting the program today In conjunction with the Dell Tech Summit. We'll hear from four of Dell's senior executives. Tom Sweet is the CFO of Dell Technologies. He's gonna share his views of the company's position and opportunities and answer the question, why is Dell good long term investment? >>Then we'll hear from Jeff Boudreau was the president of Dell's ISG business unit. He's gonna talk about the product angle and specifically how Dell is thinking about solving the multi-cloud challenge. And then Sam Grow Cot is the senior vice president of marketing's gonna come in the program and give us the update on Apex, which is Dell's as a service offering and a new edge platform called Project Frontier. By the way, it's also Cybersecurity Awareness Month, and we're gonna see if Sam has any stories there. And finally, for a company that's nearly 40 years old, Dell has some pretty forward thinking philosophies when it comes to its culture and workforce. And we're gonna speak with Jen Savira, who's Dell's chief Human Resource officer about hybrid work and how Dell is thinking about the future of work. We're gonna geek out all day and talk multi-cloud and edge and latency, but first, let's talk wallet. Tom Sweet cfo, and one of Dell's key business architects. Welcome back to the cube, >>Dave, it's good to see you and good to be back with you. So thanks for having me, Jay. >>Yeah, you bet. Tom. It's been a pretty incredible past 18 months. Not only the pandemic and all that craziness, but the VMware spin, you had to give up your gross margin binky as kidding, and, and of course the macro environment. I'm so sick of talking about the macro, but putting that aside for a moment, what's really remarkable is that for a company at your size, you've had some success at the top line, which I think surprised a lot of people. What are your reflections on the last 18 to 24 months? >>Well, Dave, it's been an incredible, not only last 18 months, but the whole transformation journey. If you think all the way back maybe to the LBO and forward from there, but, you know, stepping into the last 18 months, it's, you know, I, I think I remember talking with you and saying, Hey, you know, this scenario planning we did at the beginning of this pandemic journey was, you know, 30 different scenarios roughly, and none of which sort of panned out the way it actually did, which was a pretty incredible growth story as we think about how we helped customers, you know, drive workforce productivity, enabled their business model during the all remote work environment. That was the pandemic created. And couple that with the, you know, the, the rise then and the infrastructure spin as we got towards the tail end of the, of the pandemic coupled with, you know, the spin out of VMware, which culminated last November, as you know, as we completed that, which unlocked a pathway back to investment grade within unlocked, quite frankly shareholder value, capital allocation frameworks. It's really been a remarkable, you know, 18, 24 months. It's, it's never dull at Dell Technologies. Lemme put it that way. >>Well, well, I was impressed with you, Tom, before the leverage buyout and then what I've seen you guys navigate through is, is, is truly amazing. Well, let's talk about the challenging macro. I mean, I've been through a lot of downturns, but I've never seen anything quite like this with fed tightening and you're combating inflation, you got this recession looming, there's a bear market you got, but you got zero unemployment, you're rising wages, strong dollar, and it's very confusing. But it spending is, you know, it's somewhat softer, but it's still not bad. How are you seeing customers behave? How is Dell responding? >>Yeah, look, if you think about the markets we play in Dave, and we should start there as a grounding, you know, the, the total market, the core market that we think about is roughly 700 and, you know, 50 billion or so. If you think about our core IT services capability, you couple that with some of the, the growth initiatives that we're driving and the adjacent markets that that, that brings in, you're roughly talking a 1.4 to $1.5 trillion market opportunity, total addressable market. And so from from that perspective, we're extraordinarily bullish on where are we in the journey as we continue to grow and expand. You know, we have, we're number one share in just about every category that we plan, but yet when you look at that, you know, number one share in some of these, you know, our highest share position may be, you know, low thirties and maybe in the high end of storage you're at the upper end of thirties or 40%. >>But the opportunity there to continue to expand the core and, and continue to take share and outperform the market is truly extraordinary. So, so you step back and think about that, then you say, okay, what have we seen over the last number of months and quarters? It's been, you know, really great performance through the pandemic as, as you highlighted, we actually had a really strong first half of the year of our fiscal year 23 with revenue up 12% operating income up 12% for the first half. You know, what we talked about as you, if you might recall in our second quarter earnings, was the fact that we were starting to see softness. We had seen it in the consumer PC space, which is not a big area of focus for us in the sense of our, our total revenue stream, but we started to see commercial PC soften and we were starting to see server demand soften a bit and storage demand was, was holding quite frankly. >>And so we gave a a framework around guidance for the rest of the year as a, of what we were seeing. You know, the macro environment as you highlight it continues to be challenging. You know, if you look at inflation rates and the efforts by central banks across the globe to with through interest rate rise to press down and, and constrain growth and push down inflation, you couple that with supply chain challenges that continue principle, particularly in the ISG space. And then you couple that with the Ukraine war and the, and the energy crisis that that's created. And particularly in Europe, it's a pretty dynamic environment. And, but I'm confident, you know, I'm confident in the long term, but I do think that there is, you know, that there's navigation that we're going to have to do over the coming number of quarters, who knows quite how long, you know, to, to make sure the business is properly positioned and, you know, we've got a great portfolio and you're gonna talk to some of the team LA later on as you think your way through some of the solution capabilities we're driving what we're seeing around technology trends. >>So the opportunities there, there's some short term navigation that we're gonna need to do just to make sure that we address some of the, you know, some of the environmental things that we're seeing right >>Now. Yeah. And as a global company, of course you're converting local currencies back to appreciated dollars. That's, that's, that's another headwind. But as you say, I mean, that's math and you're navigating it. And again, I've seen a lot of downturns, but you know, the best companies not only weather the storm, but they invest in ways they that allow them to cut out, come out the other side stronger. So I wanna talk about that longer term opportunity, the relationship between the core, the the business growth. You mentioned the tam, I mean, even as a lower margin business, if, if you can penetrate that big of a tam, you could still throw off a lot of cash and you've got other levers to turn in potentially acquisitions and software. And, but so ultimately what gives you confidence in Dell's future? How should we think about Dell's future? >>Yeah, look, I, I think it comes down to we are extraordinarily excited about the opportunity over the long term digital transformation continues. I I am on numerous customer and CIO calls every week. Customers are continuing to invest in digital transformation and infrastructure to enable their business model. Yes, maybe it's gonna slow or, or pause or maybe they're not gonna invest quite at the same rate over the next number of quarters, but over the long term the needs are there. You look at what we're doing around the, the growth opportunities that we see, not only in our core space where we continue to invest, but also in the, what we call the strategic adjacencies. Things like 5G and modern telecom infrastructure as our, the telecom providers across the globe open up their, what a cl previous been closed ecosystems, you know, to open architecture. You think about, you know, what we're doing around the edge and the distribution now that we're seeing of compute and storage back to the edge given data gravity and latency matters. >>And so we're pretty bullish on the opportunity in front of us, you know, yes, we will and we're continuing to invest and you know, Jeff Boudreau talk about that I think later on in the program. So I'm excited about the opportunities and you look at our cash flow generation capability, you know, we are in, in, in normal times a, a cash flow generation machine and we'll continue to do so, You know, we've got a negative, you know, CCC in terms of, you know, how do we think about efficiency of working capital? And we look at our, you know, our capital allocation strategy, which has now returned, you know, somewhere in near 60% of our free cash flow back to shareholders. And so, you know, there's lots to, lots of reasons to think about why this, you know, we are a great sort of, I think value creation opportunity and a over the long term that the long term trends are with us, and I expect them to continue to be so, >>Yeah, and you guys, you, you, you do what you say you're gonna do. I mean, I said in my, in my other piece that I did recently, I think you guys put 46 billion on the, on the, on the balance sheet in terms of debt. That's down to I think 16 billion in the core, which that's quite remarking and that gives you some other opportunities. Give us your, your closing thoughts. I mean, you kind of just addressed why Dell is a good long term play, but I'll give you an opportunity to bring us home. >>Hey, Dave. Yeah, look, I, I just think if you look at the good, the market opportunity, the size and scale of Dell and how we think about the competitive advantages that we have, we com you know, if you look at, say we're a hundred billion revenue company, which we were a year, you know, last year, that as we reported roughly 60, 65 billion of that in the client, in in PC space, roughly, you know, 35 to 40 billion in the ISG or infrastructure space, those markets are gonna continue the opportunity to grow, share, grow at a premium to the market, drive, cash flow, drive, share gain is clearly there. You couple that with, you know, what we think the opportunity is in these adjacent markets, whether it's telecom, the edge, what we're thinking around data services, data management, you know, we, and you cut, you put that together with the long term trends around, you know, data creation and digital transformation. We are extraordinarily well positioned. We have the largest direct selling organization in in the technology space. We have the largest supply chain, our services footprint, you know, well positioned in my mind to take advantage of the opportunities as we move forward. >>Well Tom, really appreciate you taking the time to speak with us. Good to see you again. >>Nice seeing you. Thanks Dave. >>All right. You're watching the Cubes exclusive behind the scenes coverage of Dell Technology Summit 2022. In a moment, I'll be back with Jeff Boudreau. He's the president of Dell's ISG Infrastructure Solutions Group. He's responsible for all the important enterprise business at Dell, and we're excited to get his thoughts, keep it right there. >>Welcome back to the cube's exclusive coverage of the Dell Technology Summit. I'm Dave Ante and we're going inside with Dell execs to extract the signal from the noise. And right now we're gonna dig into customer requirements in a data intensive world and how cross cloud complexities get resolved from a product development perspective and how the ecosystem fits in to that mosaic to close the gaps and accelerate innovation. And with me now as friend of the cube, Jeff Boudreau, he's the president of the Infrastructure Solutions Group, ISG at Dell Technologies. Jeff, always good to see you. Welcome. >>You too. Thank you for having me. It's great to see you and thanks for having me back on the cube. I'm thrilled to be here. >>Yeah, it's our pleasure. Okay, so let's talk about what you're observing from customers today. You know, we talk all the time about operating in a data driven multi-cloud world, blah, blah, blah, blah. But what does that all mean to you when you have to translate that noise into products that solve specific customer problems, Jeff? >>Sure. Hey, great question. And everything always starts with our customers. There are motivation, they're top of mind, everything we do, my leadership team and I spend a lot of time with our customers. We're listening, we're learning, we're really understanding their pain points, and we wanna get their feedback in regards to our solutions, both turn and future offerings, really ensure that we're aligned to meeting their business objectives. I would say from these conversations, I'd say customers are telling us several things. First, it's all about data for no surprise going back to your opening. And second, it's about the multi-cloud world. And I'd say the big thing coming from all of this is that both of those are driving a ton of complexity for our customers. And I'll unpack that just a bit, which is first the data. As we all know, data is growing at unprecedented rates with more than 90% of the world's data being produced in the last two years alone. >>And you can just think of that in it's everywhere, right? And so as it as the IT world shifts towards distributed compute to support that data growth and that data gravity to really extract more value from that data in real time environments become inherently more and more hybrid and more and more multi-cloud. Which leads me to the second key point that I've been hearing from our customers, which it's a multi-cloud world, not new news. Customers by default have multiple clouds running across multiple locations that's on-prem and off-prem, it's running at the edge and it's serving a variety of different needs. Unfortunately, for most of our CU customers, multi-cloud is actually added to their complexity. As we've discussed. It's been a lot more of multi-cloud by default versus multi-cloud by design. And if you really think about our customers, I mean, I, I, I've talking to 'EM all the time, you think about the data complexity, that's the growth and the gravity. >>You think about their infrastructure complexity shifting from central to decentralized it, you think about multi-cloud complexity. So you have these walled gardens, if you will. So you have multiple vendors and you have these multiple contracts that all creates operational complexity for their teams around their processes of their tools. And then you think about security complexity that that dries with the, just the increased tax service and the list goes on. So what are we seeing for our customers? They, what they really want from us, and what they're asking us for is simplicity, not complexity. The immediacy, not latency. They're asking for open and aligned versus I'd say siloed and closed. And they're looking for a lot more agility and not rigidity in what we do. So they really wanna simplify everything. They're looking for a simpler IT and a more agile it. And they want more control of their data, right? >>And so, and they want to extract more of the value to enrich their business or their customer engagements, which all sounds pretty obvious and we've probably all heard it a bunch, but it's really hard to achieve. And that's where I believe, and we believe as Dell that we, it creates a big opportunity for us to really help our customers as that great simplifier of it. We're already doing this today on just a couple quick examples. First is Salesforce. We've supported recently, we've supported their global expansion with a multi-cloud solution to help them drive their business growth. Our solution delivered a reliable and consistent IT experience. We go back to that complexity and it was across a very distributed environment, including more than 60 data centers, 230 countries and hundreds of thousands of customers. It really provided Salesforce with the flexibility of placing workloads and data in an environment based on the right service level. >>Objective things like cost complexity or even security compliance considerations. The second customer A is a big New England Patriot fan. And Dan, Dave, I know you are as well. Oh yeah, this one's near, near data to my heart, it's the craft group. We just created a platform to span all the businesses that create more, I'd say data driven, immersive, secure experience, which is allowing them to capture data at the edge and use it for real time insights for things like cyber resiliency, but also like safety of the facilities. And as being a PA fan like I am, did they truly are meeting us where we are in our seats on their mobile devices and also in the parking lot. So just keep that in mind next time you're there. The bottom line, everything we're doing is really to make it simpler for our customers and to help them get the most of their data. I'd say we're gonna do this, is it through a multi-cloud by design approach, which we talked a lot about with you and and others at Dell Tech world earlier this year, >>Right? And we had Salesforce on, actually at Dell Tech group. The craft group is interesting because, you know, when you get to the stadium, you know, everybody's trying to get, get, get out to the internet and, and, but then the experience is so much better if you can actually, you know, deal with that edge. So I wanna talk about complexity though. You got data, you got, you know, the, the edge, you got multiple clouds, you got a different operating model across security model, different. So a lot of times in this industry we solve complexity with more complexity and it's like a bandaid. So I wanna, I wanna talk to, to how you're innovating around simplicity in ISG to address this complexity and what this means for Dell's long term strategy. >>Sure, I'd love to. So first I, I'd like to state the obvious, which are our investments in our innovations really focused on advancing, you know, our, our our customers needs, right? So we are really, our investments are gonna be targeted. We, we believe customers can have the most value. And some of that's gonna be around how we create strategic partnerships as well connected to what we just spoke about. Much of the complexity of customers have or experiencing is in the orchestration and management of all the data in all these different places and customers, you know, they must be able to quickly deploy and operate across cloud environments. They need to increase their developer productivity, really enabling those developers that do what they do best, which is creating more value for their customers than for their businesses. Our innovation efforts are really focused on addressing this by delivering an open and modern IT architecture that allows customers to run and manage any workload in any cloud anywhere. >>Data lives we're focused on, also focused on consumption based solutions, which allow for a greater degree of simplicity and flexibility, which they're really asking for as well. The foundation for this is our software to define common storage layer, that common storage layer. You can think about this Dave, as our ias if you will. It underpins our data access in mobility across all data types and locations. So you can think private, public, telecom, colo, edge, and it's delivered in a secure, holistic, and consistent cloud experience through Apex. We are making a ton of progress to let you just to be, just to be clear, we've made headway in things like Project Alpine, which you're very well aware of. This is our storage as a service. We announce this back in in January, which brings our unique software IP from our flagship storage platform to all the major public clouds. >>Really delivering the best of both worlds, allowing our customers to take advantage of Dell's enterprise class data services and storage software, such as performance at scale, resiliency, efficiency and security. But in addition to that, we're leveraging the breadth of the public cloud services, right? They're on demand scaling capabilities and access to analytical services. So in addition, we're really, we're, we're on our way to win at the edge as well with Project Frontier, which reduces complexity at the edge by creating an open and secure software platform to help our customers simplify their edge operations, optimize their edge environments and investments, secure that edge environment as well. I believe you're gonna be discussing Project Frontier here with Sam Gro Crop, the very near future. So I won't give up too many more details there. And lastly, we're also scaling Apex, which, oh, well, shifting from our vision, really shifting from vision to reality and introducing several new Apex service offerings, which are coming to market over the next month or so. And the intent is really supporting our customers on their as a service transitions by modernize the consumption experience and providing that flexible as a service model. Ultimately, we're trying to help our customers achieve that multi-cloud by design to really simplify it and unlock the power of their data. >>So some good examples there. I I like to talk about the super Cloud as you, you know, you're building on top of the, you know, hyperscale infrastructure and you got Apex is your cloud, the common storage layer, you call it your is. And that's, that's a ingredient in what we call the super cloud out to the edge. You have to have a common platform there and one of the hallmarks of a cloud company. And as you become a cloud company, everybody's a cloud company ecosystem becomes really, really important in terms of product development and, and innovation. Matt Baker always loves to stress it's not a zero zero sum game. And, and I think Super Cloud recognizes that, that there's value to be built on top of other clouds and, and, and of course on top of your infrastructure so that your ecosystem can add value. So what role does the ecosystem play there? >>For me, it's, it's pretty clear. It's, it's, it's critical. I can't say that enough above the having an open ecosystem. Think about everything we just discussed, and I agree with your super cloud analogy. I agree with what Matt Baker had said to you, I would certain no one company can actually address all the pain points and all the issues and challenges our customers are having on their own, not one. I think customers really want and deserve an open technology ecosystem, one that works together. So not these close stacks that discourages interoperability or stifles innovation and productivity of our, of each of our teams. We del I guess have a long history of supporting open ecosystems that really put customers first. And to be clear, we're gonna be at the center of the multi-cloud ecosystem and we're working with partners today to make that a reality. >>I mean, just think of what we're doing with VMware. We continue to build on our first and best alliances with them in August at their VMware explorer, which I know you were at, we announced several joint engineering initiatives to really help customers more easily manage and gain value from their data and their infrastructure. For multi-cloud specifically, we strength our relationship with VMware and with Tansu as part of that. In addition, just a few weeks ago we announced our partnership with Red Hat to simplify our multi-cloud deployments for managing containerized workloads. I'd say, and using your analogy, I could think of that as our multicloud platform. So that's kind of our PAs layer, if you will. And as you're aware, we have a very long standing and strategic partnership with Microsoft and I'd say stay tuned. There's a lot more to come with them and also others in this multicloud space. >>Shifting a bit to some of the growth engines that my team's responsible for the edge, right? As you think about data being everywhere, we've established partnerships for the Edge as well with folks like PTC and Litmus for the manufacturing edge, but also folks like Deep North for the retail edge analytics and data management. Using your Supercloud analogy, Dave the sa, right? This is our Sasa, we've announced that we're collaborating, partnering with folks like Snowflake and, and there's other data management companies as well to really simplify data access and accelerate those data insights. And then given customers choice of where they'd like to have their IT and their infrastructure, we've we're expanding our colo partnerships as well with folks like eex and, and they're allowing us to broaden our availability of Apex, providing customers the flexibility to take advantage of those as a service offerings wherever it's delivered and where they can get the most value. So those are just some you can hear from me. I think it's critical not only for, for us, I think it's critical for our customers. I think it's been critical, critical for the entire, you know, industry as a whole to really have that open technology ecosystem as we work with our customers on our multi-cloud solutions really to meet their needs. We'll continue to collaborate with whoever customers choose and you know, and who they want us to do business with. So I'd say a lot more coming in that space. >>So it's been an interesting three years for you, just, just over three years now since you've been made the president of the IS isg. And so you had to dig in and, and it was obviously a strange time around the world, but, but you really had to look at, okay, how do we modernize the platform? How do we make it, you know, cloud first, You've mentioned the edge, we're expanding. So what are the big takeaways? What do you want customers and our audience to understand? Just some closing thoughts and if you could summarize. >>Sure. So I'd say first, you know, we discussed we're working in a very fast paced, ever-changing market with massive amounts of data that needs to be managed. It's very complex and our customers need help with that complexity. I believe that Dell Technologies is uniquely positioned to help as their multicloud champion. No one else can solve the breadth and depth of the challenges like we can. And we're gonna help our customers move forward when they basically moving from a multi-cloud by default, as we've discussed before, to multicloud by design. And I'm really excited for the opportunity to work with our customers to help them expand that ecosystem as they truly realize the future of it and, and what they're trying to accomplish. >>Jeff, thanks so much. Really appreciate your time. Always a pleasure. Go pats and we'll see you on the blog. >>Thanks Dave. >>All right, you're watching exclusive insight insights from Dell Technology Summit on the cube, your leader in enterprise and emerging tech coverage. >>Hello everyone, this is Dave Lanta and you're watching the Cubes coverage of the Dell Technology Summit 2022 with exclusive behind the scenes interviews featuring Dell executive perspectives. And right now we're gonna explore Apex, which is Dell's as a service offering Dell's multi-cloud and edge strategies and the momentum around those. And we have news around Project Frontier, which is Dell's vision for its edge platform. And there's so much happening here. And don't forget it's cyber security Awareness month. Sam Grot is here, he's the senior vice president of marketing at Dell Technologies. Sam, always great to see you. How you doing? >>Always great to be here, Dave. >>All right, let's look at cloud. Everybody's talking about cloud Apex, multi-cloud, what's the update? How's it going? Where's the innovation and focal points of the strategy? >>Yeah, yeah. Look Dave, if you think back over the course of this year, you've really heard, heard us pivot as a company and discussing more and more about how multi-cloud is becoming a reality for our customers today. And when we listen and talk with our customers, they really describe multi-cloud challenges and a few key threads. One, the complexity is growing very, very quickly. Two, they're having a harder time controlling how their users are accessing the various different clouds. And then of course, finally the cloud costs are growing unchecked as well. So we, we like to describe this phenomenon as multi-cloud by design. We're essentially, organizations are waking up and seeing cloud sprawl around their organization every day. And this is creating more and more of those challenges. So of course at Dell we've got a strong point of view that you don't need to build multicloud by by default, rather it's multicloud by design where you're very intentional in how you do multicloud. >>And how we deliver multicloud by design is through apex. Apex is our modern cloud and our modern consumption experience. So when you think about the innovation as well, Dave, like we've been on a pretty quick track record here in that, you know, the beginning of this year we introduced brand new Apex backup services that provides that SAS based backup service. We've introduced or announced project outline, which is bringing our storage software, intellectual property from on-prem and putting it and running it natively in the public cloud. We've also introduced new Apex cyber recovery services that is simplifying how customers protect against cyber attacks. They can run an Amazon Azure, aw, I'm sorry, Amazon, aws, Azure or Google. And then, you know, we are really focused on this multi-cloud ecosystem. We announce key partnerships with SaaS providers such as Snowflake, where you can now access our information or our data from on-prem through the Snow Snowflake cloud. >>Or if needed, we can actually move the data to the Snowflake cloud if required. So we're continuing to build out that ecosystem SaaS providers. And then finally I would say, you know, we made a big strategic announcement just recently with Red Hat, where we're not only delivering new Apex container services, but we announce the strategic partnership to build jointly engineered solutions to address hybrid and multi-cloud solutions going forward. You know, VMware is gonna always continue to be a key partner of ours at the la at the recent VMware explorer we announced new Tansu integration. So, So Dave, I, I think in a nutshell we've been innovating at a very, very fast pace. We think there is a better way to do multi-cloud and that's multi-cloud by design. >>Yeah, we heard that at Dell Technologies world. First time I had heard that multi-cloud by design versus sort of default, which is great Alpine, which is sort of our, what we called super cloud in the making. And then of course the ecosystem is critical for any cloud company. VMware of course, you know, top partner, but the Snowflake announcement was very interesting Red Hat. So seeing that expand, now let's go out to the edge. How's it going with the edge expansion? There's gotta be new speaking of ecosystem, the edge is like a whole different, you know, OT type, that's right, ecosystem, that's telcos what and what's this new frontier platform all about? >>Yeah, yeah. So we've talked a lot about cloud and multi clouds, we've talked about private and hybrid cloud, we've talked about public clouds, clouds and cos, telcos, et cetera. There's really been one key piece of our multi-cloud and technology strategy that we haven't spent a lot of time on. And that's the edge. And we do see that as that next frontier for our customers to really gain that competitive advantage that is created from their data and get closer to the point of creation where the data lives. And that's at the edge. We see the edge infrastructure space growing very, very quickly. We see upwards of 300% year of year growth in terms of amount of data being created at the edge. That's almost 3000 exabytes of data by 2026. So just incredible growth. And the edge is not really new for Dell. We've been at it for over 20 years of delivering edge solutions. >>81% of the Fortune 100 companies in the US use Dell solutions today at the Edge. And we are the number one OEM provider of Edge solutions with over 44,000 customers across over 40 industries and things like manufacturing, retail, edge healthcare, and more. So Dave, while we've been at it for a long time, we have such a, a deep understanding of how our customers are using Edge solutions. Say the bottom line is the game has gotta change. With that growth that we talked about, the new use cases that are emerging, we've got to un unlock this new frontier for customers to take advantage of the edge. And that's why we are announcing and revealing Project Frontier. And Project Frontier in its most simplest form, is a software platform that's gonna help customers and organizations really radically simplify their edge deployments by automating their edge operations. You know, with Project Frontier organizations are really gonna be able to manage, OP, and operate their edge infrastructure and applications securely, efficiently and at scale. >>Okay, so it is, first of all, I like the name, it is software, it's a software architecture. So presumably a lot of API capabilities. That's right. Integration's. Is there hardware involved? >>Yeah, so of course you'll run it on Dell infrastructure. We'll be able to do both infrastructure orchestration, orchestration through the platform, but as well as application orchestration. And you know, really there's, there's a handful of key drivers that have been really pushing our customers to take on and look at building a better way to do the edge with Project Frontier. And I think I would just highlight a handful of 'em, you know, freedom of choice. We definitely see this as an open ecosystem out there, even more so at the Edge than any other part of the IT stack. You know, being able to provide that freedom of choice for software applications or I O T frameworks, operational technology or OT for any of their edge use cases, that's really, really important. Another key area that we're helping to solve with Project Frontier is, you know, being able to expect zero trust security across all their edge applications from design to deployment, you know, and of course backed by an end and secure supply chain is really, really important to customers. >>And then getting that greater efficiency and reliability of operations with the centralized management through Project Frontier and Zero Touch deployments. You know, one of the biggest challenges, especially when you get out to the far, far reach of the frontier is really IT resources and being able to have the IT expertise and we built in an enormous amount of automation helps streamline the edge deployments where you might be deploying a single edge solution, which is highly unlikely or hundreds or thousands, which is becoming more and more likely. So Dave, we do think Project Frontier is the right edge platform for customers to build their edge applications on now and certain, excuse me, certainly, and into the future. >>Yeah. Sam, no truck rolls. I like it. And you, you mentioned, you mentioned Zero trust. So we have Mother's Day, we have Father's Day. The kids always ask When's kids' day? And we of course we say every day is kids' day and every day should be cybersecurity awareness day. So, but we have cybersecurity awareness month. What does it mean for Dell? What are you hearing from customers and, and how are you responding? >>Yeah, yeah. No, there isn't a more prevalent pop of mind conversation, whether it's the boardroom or the IT departments or every company is really have been forced to reckon with the cybersecurity and ransom secure issues out there. You know, every decision in IT department makes impacts your security profile. Those decisions can certainly, positively, hopefully impact it, but also can negatively impact it as well. So data security is, is really not a new area of focus for Dell. It's been an area that we've been focused on for a long time, but there are really three core elements to cyber security and data security as we go forward. The first is really setting the foundation of trust is really, really important across any IT system. And having the right supply chain and the right partner to partner with to deliver that is kind of the foundation in step one. >>Second, you need to of course go with technology that is trustworthy. It doesn't mean you are putting it together correctly. It means that you're essentially assembling the right piece parts together. That, that coexist together in the right way. You know, to truly change that landscape of the attackers out there that are gonna potentially create risk for your environment. We are definitely pushing and helping to embrace the zero trust principles and architectures that are out there. So finally, while when you think about security, it certainly is not absolute all correct. Security architectures assume that, you know, there are going to be challenges, there are going to be pain points, but you've gotta be able to plan for recovery. And I think that's the holistic approach that we're taking with Dell. >>Well, and I think too, it's obviously security is a complicated situation now with cloud you've got, you know, shared responsibility models, you've got that a multi-cloud, you've got that across clouds, you're asking developers to do more. So I think the, the key takeaway is as a security pro, I'm looking for my technology partner through their r and d and their, you mentioned supply chain processes to take that off my plate so I can go plug holes elsewhere. Okay, Sam, put a bow on Dell Technology Summit for us and give us your closing thoughts. >>Yeah, look, I I think we're at a transformative point in it. You know, customers are moving more and more quickly to multi-cloud environments. They're looking to consume it in different ways, such as as a service, a lot of customers edge is new and an untapped opportunity for them to get closer to their customers and to their data. And of course there's more and more cyber threats out there every day. You know, our customers when we talk with them, they really want simple, consistent infrastructure options that are built on an open ecosystem that allows them to accomplish their goals quickly and successfully. And look, I think at Dell we've got the right strategy, we've got the right portfolio, we are the trusted partner of choice, help them lead, lead their, their future transformations into the future. So Dave, look, I think it's, it's absolutely one of the most exciting times in it and I can't wait to see where it goes from here. >>Sam, always fun catching up with you. Appreciate your time. >>Thanks Dave. >>All right. A Dell tech world in Vegas this past year, one of the most interesting conversations I personally had was around hybrid work and the future of work and the protocols associated with that and the mindset of, you know, the younger generation. And that conversation was with Jen Savira and we're gonna speak to Jen about this and other people and culture topics. Keep it right there. You're watching the cube's exclusive coverage of Dell Technology Summit 2022. Okay, we're back with Jen Vera, who's the chief human resource officer of Dell, and we're gonna discuss people, culture and hybrid work and leadership in the post isolation economy. Jen, the conversations that we had at Dell Tech World this past May around the new work environment were some of the most interesting and engaging that I had personally. So I'm really eager to, to get the update. It's great to see you again. Thanks for coming on the cube. >>Thanks for having me Dave. There's been a lot of change in just a short amount of time, so I'm excited to, to share some of our learnings >>With you. I, I mean, I bet there has, I mean, post pandemic companies, they're trying, everybody's trying to figure out the return to work and, and what it looks like. You know, last May there was really a theme of flexibility, but depending, we talked about, well, millennial or not young old, and it's just really was mixed, but, so how have you approached the topic? What, what are your policies? What's changed since we last talked? You know, what's working, you know, what's still being worked? What would you recommend to other companies to over to you? >>Yeah, well, you know, this isn't a topic that's necessarily new to Dell technology. So we've been doing hybrid before. Hybrid was a thing. So for over a decade we've been doing what we called connected workplace. So we have kind of a, a history and we have some great learnings from that. Although things did change for the entire world. You know, March of 2020, we went from kind of this hybrid to everybody being remote for a while. But what we wanted to do is, we're such a data driven company, there's so many headlines out there, you know, about all these things that people think could happen will happen, but there wasn't a lot of data behind it. So we took a step back and we asked our team members, How do you think we're doing? And we asked very kind of strong language because we've been doing this for a while. >>We asked them, Do you think we're leading in the world of hybrid in 86% of our team members said that we were, which is great, but we always know there's nuance right behind that macro level. So we, we asked 'em a lot of different questions and we just went on this kind of myth busting journey and we decided to test some of those things. We're hearing about Culture Willow Road or new team members will have trouble being connected or millennials will be different. And we really just collected a lot of data, asked our team members what their experience is. And what we have found is really, you don't have to be together in the office all the time to have a strong culture, a sense of connection, to be productive and to have it really healthy business. >>Well, I like that you were data driven around it in the data business here. So, but, but there is a lot of debate around your culture and how it suffers in a hybrid environment, how remote workers won't get, you know, promoted. And so I'm curious, you know, and I've, and I've seen some like-minded companies like Dell say, Hey, we, we want you guys to work the way you wanna work. But then they've, I've seen them adjust and say, Well yeah, but we also want you to know in the office be so we can collaborate a little bit more. So what are you seeing at Dell and, and, and how do you maintain that cultural advantage that you're alluding to in this kind of strange, new ever changing world? >>Yeah, well I think, look, one approach doesn't fit all. So I don't think that the approach that works for Dell Technologies isn't necessarily the approach that works for every company. It works with our strategy and culture. It is really important that we listen to our team members and that we support them through this journey. You know, they tell us time and time again, one of the most special things about our culture is that we provide flexibility and choice. So we're not a mandate culture. We really want to make sure that our team members know that we want them to be their best and do their best. And not every individual role has the same requirements. Not every individual person has the same needs. And so we really wanna meet them where they are so that they can be productive. They feel connected to the team and to the company and engaged and inspired. >>So, you know, for, for us, it really does make sense to go forward with this. And so we haven't, we haven't taken a step back. We've been doing hybrid, we'll continue to do hybrid, but just like if you, you know, we talk about not being a mandate. I think the companies that say nobody will come in or you have to come in three days a week, all of that feels more limiting. And so what we really say is, work out with your team, work out with your role, workout with your leader, what really makes the most sense to drive things forward. >>I >>You were, so >>That's what we, you were talking before about myths and you know, I wanna talk about team member performance cuz there's a lot of people believe that if, if you're not in the office, you have disadvantages, people in the office have the advantage cuz they get FaceTime. Is is that a myth? You know, is there some truth to that? What, what do you think about that? >>Well, for us, you know, we look, again, we just looked at the data. So we said we don't wanna create a have and have not culture that you're talking about. We really wanna have an inclusive culture. We wanna be outcome driven, we're meritocracy. But we went and we looked at the data. So pre pandemic, we looked at things like performance, we looked at rewards and recognition, we looked at attrition rates, we looked at sentiment, Do you feel like your leader is inspiring? And we found no meaningful differences in any of that or in engagement between those who worked fully remote, fully in the office or some combination between. So our data would bust that myth and say, it doesn't, you don't have to be in an office and be seen to get ahead. We have equitable opportunity. Now, having said that, you always have to be watching that data. And that's something that we'll continue to do and make sure that we are creating equal opportunity regardless of where you work. >>And it's personal too, I think, I think some people can be really productive at home. I happen to be one that I'm way more productive in the office cause the dogs aren't barking. I have less distractions. And so I think we think, and, and I think the takeaway that in just in talking to, to, to you Jen and, and folks at Dell is, you know, whatever works for you, we're we're gonna, we're gonna support. So I I wanted to switch gears a little bit, talk about leadership and, and very specifically empathic leadership has been said to be, have a big impact on attracting talent, retaining talent, but, but it's hard to have empathy sometimes. And I know I saw some stats in a recent Dell study. It was like two thirds the people felt like their organization underestimates the people requirements. And I, I ask myself, I'm like, what am I missing? I hope, you know, with our folks, so especially as it relates to, to transformation programs. So how can human resource practitioners support business leaders generally, specifically as it relates to leading with empathy? >>I think empathy's always been important. You have to develop trust. You can have the best strategy in the world, right? But if you don't feel like your leader understands who you are, appreciates the the value that you bring to the company, then you're not gonna get very far. So I think empathetic leadership has always been part of the foundation of a trusting, strong relationship between a leader and a team member. But if I think we look back on the last two years, and I imagine it'll be even more so as we go forward, empathetic leadership will be even more important. There's so much going on in the world, politically, socially, economically, that taking that time to say you want your team members to see you as credible, that you and confident that you can take us forward, but also that, you know, and understand me as a human being. >>And that to me is really what it's about. And I think with regard to transformation that you brought up, I think one of the things we forget about is leaders. We've probably been thinking about a decision or transformation for months or weeks and we're ready to go execute, we're ready to go operationalize that thing. And so sometimes when we get to that point, because we've been talking about it for so long, we send out the email, we have the all hands and we just say we're ready to go. But our team members haven't always been on that journey for those months that we have. And so I think that empathetic moment to say, Okay, not everybody is on a change curve where I am. Let's take a pause, let me put myself in their shoes and really think about how we bring everybody along. >>You know, Jen, in the spirit of myth busting, I mean I'm one of those people who felt like that a business is gonna have a hard time, harder time fostering this culture of collaboration and innovation post isolation economy as they, they could pre covid. But you know, I noticed there's a, there's an announcement today that came across my desk, I think it's from Newsweek. Yes. And, and it's the list of top hundred companies recognized for employee motivation satisfaction. And it was really interesting because you, you always see, oh, we're the top 10 or the top hundred, But this says as a survey of 1.4 million employees from companies ranging from 50 to 10,000 employees. And it recognizes the companies that put respect, caring, and appreciation for their employees at the center of their business model. And they doing so have earned the loyalty and respect of the people who work for them. >>Number one on the list is Dell sap. So congratulations SAP was number two. I mean, there really isn't any other tech company on there, certainly no large tech companies on there. So I always see these lists, they go, Yeah, okay, that's cool, top a hundred, whatever. But top one in, in, in an industry where there's only two in the top is, is pretty impressive. And how does that relate to fostering my earlier skepticism of a culture of collaboration? So first of all, congratulations, you know, how'd you do it? And how are you succeeding in, in this new world? >>Well thanks. It does feel great to be number one, but you know, it doesn't happen by accident. And I think while most companies have a, a culture and a spouse values, we have ours called the culture code. But it's really been very important to us that it's not just a poster on the wall or or words on paper. And so we embed our culture code into all of our HR practices, that whole ecosystem from recognition of rewards to performance evaluation, to interviewing, to development. We build it into everything. So it really reflects who we are and you experience it every day. And then to make sure that we're not, you know, fooling ourselves, we ask all of our employees, do you feel like the behaviors you see and the experience you have every day reflects the culture code? And 94% of our team members say that, in fact it does. So I think that that's really been kind of the secret to our success. If you, if you listen to Michael Dell, he'll always say, you know, the most special thing about Dell is our culture and our people. And that comes through being very thoughtful and deliberate to preserve and protect and continue to focus on our culture. >>Don't you think too that repetition and, well first of all, belief in that cultural philosophy is, is important. And then kind of repeating, like you said, Yeah, it's not just a poster in the wall, but I remember like, you know, when we're kids, your parents tell you, okay, power positive thinking, do one to others as others, you know, you have others do it to you. Don't make the say you're gonna do some dumb things but don't do the same dumb things twice and you sort of fluff it up. But then as you mature you say, Wow, actually those were, >>They might have had a >>Were instilled in me and now I'm bringing them forward and, you know, paying it forward. But, but so i, it, it, my, I guess my, my point is, and it's kind of a point observation, but I'll turn it into a question, is isn't isn't consistency and belief in your values really, really important? >>I couldn't agree with you more, right? I think that's one of those things that we talk about it all the time and as an HR professional, you know, it's not the HR people just talking about our culture, it's our business leaders, it's our ceo, it's our COOs ev, it's our partners. We share our culture code with our partners and our vendors and our suppliers and, and everybody, this is important. We say when you interact with anybody at Dell Technologies, you should expect that this is the experience that you're gonna get. And so it is something that we talk about that we embed in, into everything that we do. And I think it's, it's really important that you don't just think it's a one and done cuz that's not how things really, really work >>Well. And it's a culture of respect, you know, high performance, high expectations, accountability at having followed the company and worked with the company for many, many years. You always respect the dignity of your partners and your people. So really appreciate your time Jen. Again, congratulations on being number one. >>Thank you so much. >>You're very welcome. Okay. You've been watching a special presentation of the cube inside Dell Technology Summit 2022. Remember, these episodes are all available on demand@thecube.net and you can check out s silicon angle.com for all the news and analysis. And don't forget to check out wikibon.com each week for a new episode of breaking analysis. This is Dave Valante, thanks for watching and we'll see you next time.

>>Okay, we're back with Jen Vera, who's the Chief Human Resource Officer of Dell, and we're gonna discuss people, culture and hybrid work and leadership in the post isolation economy. Jen, the conversations that we had at Dell Tech World this past May around the new work environment were some of the most interesting and engaging that I had personally. So I'm really eager to, to get the update. It's great to see you again. Thanks for coming on the cube. >>Thanks for having me, Dave. There's been a lot of change and just a short amount of time, so I'm excited to, to share some of our learnings with >>You. I, I mean, I bet there has, I mean, post pandemic companies, they're trying, everybody's trying to figure out the return to work and, and what it looks like. You know, last May there was really a theme of flexibility, but depending, we talked about, well, millennial or not young old, and it's just really was mixed, but, so how have you approached the topic? What, what are your policies? What's changed since we last talked? You know, what's working, what's still being worked? What would you recommend to other companies to over to you? >>Yeah. Well, you know, this isn't a topic that's necessarily new to Dell technology. So we've been doing hybrid before. Hybrid was a thing, so for over a decade we've been doing what we called connected workplace. So we have kind of a, a history and we have some great learnings from that. Although things did change for the entire world. You know, March of 2020, we went from kind of this hybrid to everybody being remote for a while. But what we wanted to do is, we're such a data driven company. There's so many headlines out there, you know, about all these things that people think could happen will happen, but there wasn't a lot of data behind it. So we took a step back and we asked our team members, How do you think we're doing? And we asked very kind of strong language, because we've been doing this for a while. >>We asked them, Do you think we're leading in the world of hybrid? And 86% of our team members said that we were, which is great, but we always know there's nuance right behind that macro level. So we, we asked them a lot of different questions and we just went on this kind of myth busting journey and we decided to test some of those things. We're hearing about Culture Willow Road or new team members will have trouble being connected or millennials will be different. And we really just collected a lot of data, asked our team members what their experiences. And what we have found is really, you don't have to be together in the office all the time to have a strong culture, a sense of connection, to be productive and to have a really healthy business. >>Well, I like that you were data driven around it with the data business here. So, but, but there is a lot of debate around your culture and how it suffers in a hybrid environment, how remote workers won't get, you know, promoted. And so I'm curious, you know, and I've, and I've seen some like-minded companies like Dell say, Hey, we, we want you guys to work the way you wanna work. But then they've, I've seen them adjust and say, Well, yeah, but we also want you to know in the office, so, so we can collaborate a little bit more. So what are you seeing at Dell and, and, and how do you maintain that cultural advantage that you're alluding to in this kinda strange new ever changing world? >>Yeah. Well, I think, look, one approach doesn't fiddle. So I don't think that the approach that works for Dell Technologies is necessarily the approach that works for every company. It works with our strategy and culture. It is really important that we listen to our team members and that we support them through this journey. You know, they tell us time and time again, one of the most special things about our culture is that we provide flexibility and choice. So we're not a mandate culture. We really want to make sure that our team members know that we want them to be their best and do their best. And not every individual role has the same requirements. Not every individual person has the same needs. And so we really wanna meet them where they are so that they can be productive. They feel connected to the team and to the company and engaged and inspired. >>So, you know, for, for us, it really does make sense to go forward with this. And so we haven't, we haven't taken a step back. We've been doing hybrid, we'll continue to do hybrid, but just like if you, you know, we talk about not being a mandate. I think the companies that say nobody will come in or you have to come in three days a week, all of that feels more limiting. And so what we really say is, work out with your team, work out with your role, workout with your leader, what really makes the most sense to drive things forward. >>I >>Mean, you talking, So that's >>What we do. You were talking before about myths and you know, I wanna talk about team member performance cuz there's a lot of people believe that if, if you're not in the office, you have disadvantages, People in the office have the advantage cuz they get FaceTime. Is is that a myth? You know, is there some truth to that? What, what do you think about that? >>Well, for us, you know, we look, again, we just looked at the data. So we said we don't wanna create a have and have not culture that you're talking about. We really wanna have an inclusive culture, We wanna be outcome driven, we're meritocracy. But we went and we looked at the data. So pre pandemic, we looked at things like performance, we looked at rewards and recognition, we looked at attrition rates, we looked at sentiment, Do you feel like your leader is inspiring? And we found no meaningful differences in any of that or in engagement between those who worked fully remote, fully in the office or some combination between. So our data would bust that myth and say, it doesn't, you don't have to be in an office and be seen to get ahead. We have equitable opportunity. Now, having said that, you always have to be watching that data and that's something that we'll continue to do and make sure that we are creating equal opportunity regardless of where you work. >>And it's personal too, I think, I think some people can be really productive at home. I happen to be one that I'm way more productive in the office cuz the dogs aren't barking. I have less distractions. And so, yeah, I think we think, and I think the takeaway that in just in talking to, to, to you Jen and, and folks at Dell is, you know, whatever works for you, we're we're gonna, we're gonna support. So I, I wanted to switch gears a little bit and talk about leadership and, and very specifically empathic leadership has been said to be, have a big impact on attracting talent, retaining talent, but, but it's hard to have empathy sometimes. And I know I saw some stats in a recent Dell study. It was like two thirds the people felt like their organization underestimates the people requirements. And I, I asked myself, I'm like, Hmm, what am I missing? You know, with our folks. So especially as it relates to, to transformation programs. So how can human resource practitioners support business leaders generally, specifically as it relates to leading with empathy? >>I think empathy's always been important. You have to develop trust. You can have the best strategy in the world, right? But if you don't feel like your leader understands who you are, appreciates the the value that you bring to the company, then you're not gonna get very far. So I think empathetic leadership has always been part of the foundation of a trusting, strong relationship between a leader and a team member. But if I think we look back on the last two years, and I imagine it'll be even more so as we go forward, empathetic leadership will be even more important. There's so much going on in the world, politically, socially, economically, that taking that time to say you want your team members to see you as credible, that you and confident that you can take us forward, but also that, you know, and understand me as a human being. >>And that to me is really what it's about. And I think with regard to transformation that you brought up, I think one of the things we forget about is leaders. We've probably been thinking about a decision or transformation for months or weeks and we're ready to go execute, we're ready to go operationalize that thing. And so sometimes when we get to that point, because we've been talking about it for so long, we send out the email, we have the all hands and we just say we're ready to go. But our team members haven't always been on that journey for those months that we have. And so I think that empathetic moment to say, Okay, not everybody is honest change curve where I am. Let's take a pause, let me put myself in their shoes and really think about how we bring everybody along the journey. >>You know, Jen, in the spirit of myth busting, I mean I'm one of those people who felt like that a business is gonna have a hard time, harder time fostering this culture of collaboration and innovation post isolation economy as they, they could pre covid. But you know, I notice there's, there's an announcement today that came across my desk, I think it's from Newsweek. Yes. And, and it's the list of top hundred companies recognized for employee motivation satisfaction. And it was really interesting because you know, you always see, oh, we're the top 10 or the top hundred, But this says as a survey of 1.4 million employees from companies ranging from 50 to 10,000 employees. And it recognizes the companies that put respect, caring, and appreciation for their employees at the center of their business model. And in doing so, have earned the loyalty and respect of the people who worked for them. >>Number one on the list is Dell sap. So congratulations. SAP was number two. I mean, there really isn't any other tech company on there, certainly no large tech companies on there. So I always see these lists like go, yeah, okay, that's cool, top a hundred, whatever. But top one in, in, in an industry where there's only two in the top is, is pretty impressive. And how does that relate to fostering my earlier skepticism of a culture of collaboration? So first of all, congratulations, you know, how'd you do it? And how are you succeeding in, in this new world? >>Well thanks. It does feel great to be number one, but you know, it doesn't happen by accident. And I think while most companies have a, a culture and a spouse values, we have ours called the culture code. But it's really b been very important to us that it's not just a poster on the wall or or words on paper. And so we embed our culture code into all of our HR practices, that whole ecosystem from recognition rewards to performance evaluation, to interviewee to development. We build it into everything. So it really reflects who we are and you experience it every day. And then to make sure that we're not, you know, fooling ourselves, we ask all of our employees, do you feel like the behaviors you see and the experience you have every day reflects the culture code? And 94% of our team members say that, in fact it does. So I think that that's really been kind of the secret to our success. If you, if you listen to Michael Dell, he'll always say, you know, the most special thing about Dell is our culture and our people. And that comes through being very thoughtful and deliberate to preserve and protect and continue to focus on our culture. >>Don't you think too that repetition and, well first of all, belief in that cultural philosophy is, is important. And then kind of repeating, like you said, Yeah, it's not just a poster on the wall, but I remember like, you know, when we're kids, your parents tell you, okay, power positive thinking, do one to others as others, you know, you have others do it to you. Don't make this, you're gonna do some dumb things but don't do the same dumb things twice and you sort of fluff it up. But then as you mature you say, Wow, actually those were, >>They might have had a, values >>Were instilled in me and now I'm bringing them forward and, you know, paying it forward. But, but, so I guess my, my point is, and it's kind of a point observation, but I'll turn it into a question, is isn't isn't consistency and belief in your values really, really important? >>I couldn't agree with you more, right? I think that's one of those things that we talk about it all the time and as an HR professional, you know, it's not the HR people just talking about our culture, it's our business leaders, it's our ceo, it's our COOs, it's our partners. We share our culture code with our partners and our vendors and our suppliers and, and everybody, this is important. We say when you interact with anybody at Dell Technologies, you should expect that this is the experience that you're gonna get. And so it is something that we talk about that we embed in, into everything that we do. And I think it's, it's really important that you don't just think it's a one and done cuz that's not how things really, really work >>Well. And it's a culture of respect. You know, high performance, high expectations, accountability at having followed the company and worked with the company for many, many years. You'd always respect the dignity of your partners and your people. So really appreciate your time Jen. Again, congratulations on being number one. >>Thank you so much. >>You're very welcome. Okay, you've been watching a special presentation of the Cube inside Dell Technology Summit 2022. Remember, these episodes are all available on demand@thecube.net and you can check out silicon angle.com for all the news and analysis. And don't forget to check out wikibon.com each week for a new episode of breaking analysis. This is Dave Ante, thanks for watching and we'll see you next time.

>>Oracle continues to enhance my sequel Heatwave at a very rapid pace. The company is now in its fourth major release since the original announcement in December 2020. 1 of the main criticisms of my sequel, Heatwave, is that it only runs on O. C I. Oracle Cloud Infrastructure and as a lock in to Oracle's Cloud. Oracle recently announced that heat wave is now going to be available in AWS Cloud and it announced its intent to bring my sequel Heatwave to Azure. So my secret heatwave on AWS is a significant TAM expansion move for Oracle because of the momentum AWS Cloud continues to show. And evidently the Heatwave Engineering team has taken the development effort from O. C I. And is bringing that to A W S with a number of enhancements that we're gonna dig into today is senior vice president. My sequel Heatwave at Oracle is back with me on a cube conversation to discuss the latest heatwave news, and we're eager to hear any benchmarks relative to a W S or any others. Nippon has been leading the Heatwave engineering team for over 10 years and there's over 100 and 85 patents and database technology. Welcome back to the show and good to see you. >>Thank you. Very happy to be back. >>Now for those who might not have kept up with the news, uh, to kick things off, give us an overview of my sequel, Heatwave and its evolution. So far, >>so my sequel, Heat Wave, is a fully managed my secret database service offering from Oracle. Traditionally, my secret has been designed and optimised for transaction processing. So customers of my sequel then they had to run analytics or when they had to run machine learning, they would extract the data out of my sequel into some other database for doing. Unlike processing or machine learning processing my sequel, Heat provides all these capabilities built in to a single database service, which is my sequel. He'd fake So customers of my sequel don't need to move the data out with the same database. They can run transaction processing and predicts mixed workloads, machine learning, all with a very, very good performance in very good price performance. Furthermore, one of the design points of heat wave is is a scale out architecture, so the system continues to scale and performed very well, even when customers have very large late assignments. >>So we've seen some interesting moves by Oracle lately. The collaboration with Azure we've we've covered that pretty extensively. What was the impetus here for bringing my sequel Heatwave onto the AWS cloud? What were the drivers that you considered? >>So one of the observations is that a very large percentage of users of my sequel Heatwave, our AWS users who are migrating of Aurora or so already we see that a good percentage of my secret history of customers are migrating from GWS. However, there are some AWS customers who are still not able to migrate the O. C. I to my secret heat wave. And the reason is because of, um, exorbitant cost, which was charges. So in order to migrate the workload from AWS to go see, I digress. Charges are very high fees which becomes prohibitive for the customer or the second example we have seen is that the latency of practising a database which is outside of AWS is very high. So there's a class of customers who would like to get the benefits of my secret heatwave but were unable to do so and with this support of my secret trip inside of AWS, these customers can now get all the grease of the benefits of my secret he trip without having to pay the high fees or without having to suffer with the poorly agency, which is because of the ws architecture. >>Okay, so you're basically meeting the customer's where they are. So was this a straightforward lifted shift from from Oracle Cloud Infrastructure to AWS? >>No, it is not because one of the design girls we have with my sequel, Heatwave is that we want to provide our customers with the best price performance regardless of the cloud. So when we decided to offer my sequel, he headed west. Um, we have optimised my sequel Heatwave on it as well. So one of the things to point out is that this is a service with the data plane control plane and the console are natively running on AWS. And the benefits of doing so is that now we can optimise my sequel Heatwave for the E. W s architecture. In addition to that, we have also announced a bunch of new capabilities as a part of the service which will also be available to the my secret history of customers and our CI, But we just announced them and we're offering them as a part of my secret history of offering on AWS. >>So I just want to make sure I understand that it's not like you just wrapped your stack in a container and stuck it into a W s to be hosted. You're saying you're actually taking advantage of the capabilities of the AWS cloud natively? And I think you've made some other enhancements as well that you're alluding to. Can you maybe, uh, elucidate on those? Sure. >>So for status, um, we have taken the mind sequel Heatwave code and we have optimised for the It was infrastructure with its computer network. And as a result, customers get very good performance and price performance. Uh, with my secret he trade in AWS. That's one performance. Second thing is, we have designed new interactive counsel for the service, which means that customers can now provision there instances with the council. But in addition, they can also manage their schemas. They can. Then court is directly from the council. Autopilot is integrated. The council we have introduced performance monitoring, so a lot of capabilities which we have introduced as a part of the new counsel. The third thing is that we have added a bunch of new security features, uh, expose some of the security features which were part of the My Secret Enterprise edition as a part of the service, which gives customers now a choice of using these features to build more secure applications. And finally, we have extended my secret autopilot for a number of old gpus cases. In the past, my secret autopilot had a lot of capabilities for Benedict, and now we have augmented my secret autopilot to offer capabilities for elderly people. Includes as well. >>But there was something in your press release called Auto thread. Pooling says it provides higher and sustained throughput. High concerns concerns concurrency by determining Apple number of transactions, which should be executed. Uh, what is that all about? The auto thread pool? It seems pretty interesting. How does it affect performance? Can you help us understand that? >>Yes, and this is one of the capabilities of alluding to which we have added in my secret autopilot for transaction processing. So here is the basic idea. If you have a system where there's a large number of old EP transactions coming into it at a high degrees of concurrency in many of the existing systems of my sequel based systems, it can lead to a state where there are few transactions executing, but a bunch of them can get blocked with or a pilot tried pulling. What we basically do is we do workload aware admission control and what this does is it figures out, what's the right scheduling or all of these algorithms, so that either the transactions are executing or as soon as something frees up, they can start executing, so there's no transaction which is blocked. The advantage to the customer of this capability is twofold. A get significantly better throughput compared to service like Aurora at high levels of concurrency. So at high concurrency, for instance, uh, my secret because of this capability Uh oh, thread pulling offers up to 10 times higher compared to Aurora, that's one first benefit better throughput. The second advantage is that the true part of the system never drops, even at high levels of concurrency, whereas in the case of Aurora, the trooper goes up, but then, at high concurrency is, let's say, starting, uh, level of 500 or something. It depends upon the underlying shit they're using the troopers just dropping where it's with my secret heatwave. The truth will never drops. Now, the ramification for the customer is that if the truth is not gonna drop, the user can start off with a small shape, get the performance and be a show that even the workload increases. They will never get a performance, which is worse than what they're getting with lower levels of concurrency. So this let's leads to customers provisioning a shape which is just right for them. And if they need, they can, uh, go with the largest shape. But they don't like, you know, over pay. So those are the two benefits. Better performance and sustain, uh, regardless of the level of concurrency. >>So how do we quantify that? I know you've got some benchmarks. How can you share comparisons with other cloud databases especially interested in in Amazon's own databases are obviously very popular, and and are you publishing those again and get hub, as you have done in the past? Take us through the benchmarks. >>Sure, So benchmarks are important because that gives customers a sense of what performance to expect and what price performance to expect. So we have run a number of benchmarks. And yes, all these benchmarks are available on guitar for customers to take a look at. So we have performance results on all the three castle workloads, ol DB Analytics and Machine Learning. So let's start with the Rdp for Rdp and primarily because of the auto thread pulling feature. We show that for the IPCC for attended dataset at high levels of concurrency, heatwave offers up to 10 times better throughput and this performance is sustained, whereas in the case of Aurora, the performance really drops. So that's the first thing that, uh, tend to alibi. Sorry, 10 gigabytes. B B C c. I can come and see the performance are the throughput is 10 times better than Aurora for analytics. We have done a comparison of my secret heatwave in AWS and compared with Red Ship Snowflake Googled inquiry, we find that the price performance of my secret heatwave compared to read ship is seven times better. So my sequel, Heat Wave in AWS, provides seven times better price performance than red ship. That's a very, uh, interesting results to us. Which means that customers of Red Shift are really going to take the service seriously because they're gonna get seven times better price performance. And this is all running in a W s so compared. >>Okay, carry on. >>And then I was gonna say, compared to like, Snowflake, uh, in AWS offers 10 times better price performance. And compared to Google, ubiquity offers 12 times better price performance. And this is based on a four terabyte p PCH workload. Results are available on guitar, and then the third category is machine learning and for machine learning, uh, for training, the performance of my secret heatwave is 25 times faster compared to that shit. So all the three workloads we have benchmark's results, and all of these scripts are available on YouTube. >>Okay, so you're comparing, uh, my sequel Heatwave on AWS to Red Shift and snowflake on AWS. And you're comparing my sequel Heatwave on a W s too big query. Obviously running on on Google. Um, you know, one of the things Oracle is done in the past when you get the price performance and I've always tried to call fouls you're, like, double your price for running the oracle database. Uh, not Heatwave, but Oracle Database on a W s. And then you'll show how it's it's so much cheaper on on Oracle will be like Okay, come on. But they're not doing that here. You're basically taking my sequel Heatwave on a W s. I presume you're using the same pricing for whatever you see to whatever else you're using. Storage, um, reserved instances. That's apples to apples on A W s. And you have to obviously do some kind of mapping for for Google, for big query. Can you just verify that for me, >>we are being more than fair on two dimensions. The first thing is, when I'm talking about the price performance for analytics, right for, uh, with my secret heat rape, the cost I'm talking about from my secret heat rape is the cost of running transaction processing, analytics and machine learning. So it's a fully loaded cost for the case of my secret heatwave. There has been I'm talking about red ship when I'm talking about Snowflake. I'm just talking about the cost of these databases for running, and it's only it's not, including the source database, which may be more or some other database, right? So that's the first aspect that far, uh, trip. It's the cost for running all three kinds of workloads, whereas for the competition, it's only for running analytics. The second thing is that for these are those services whether it's like shit or snowflakes, That's right. We're talking about one year, fully paid up front cost, right? So that's what most of the customers would pay for. Many of the customers would pay that they will sign a one year contract and pay all the costs ahead of time because they get a discount. So we're using that price and the case of Snowflake. The costs were using is their standard edition of price, not the Enterprise edition price. So yes, uh, more than in this competitive. >>Yeah, I think that's an important point. I saw an analysis by Marx Tamer on Wiki Bond, where he was doing the TCO comparisons. And I mean, if you have to use two separate databases in two separate licences and you have to do et yelling and all the labour associated with that, that that's that's a big deal and you're not even including that aspect in in your comparison. So that's pretty impressive. To what do you attribute that? You know, given that unlike, oh, ci within the AWS cloud, you don't have as much control over the underlying hardware. >>So look hard, but is one aspect. Okay, so there are three things which give us this advantage. The first thing is, uh, we have designed hateful foreign scale out architecture. So we came up with new algorithms we have come up with, like, uh, one of the design points for heat wave is a massively partitioned architecture, which leads to a very high degree of parallelism. So that's a lot of hype. Each were built, So that's the first part. The second thing is that although we don't have control over the hardware, but the second design point for heat wave is that it is optimised for commodity cloud and the commodity infrastructure so we can have another guys, what to say? The computer we get, how much network bandwidth do we get? How much of, like objects to a brand that we get in here? W s. And we have tuned heat for that. That's the second point And the third thing is my secret autopilot, which provides machine learning based automation. So what it does is that has the users workload is running. It learns from it, it improves, uh, various premieres in the system. So the system keeps getting better as you learn more and more questions. And this is the third thing, uh, as a result of which we get a significant edge over the competition. >>Interesting. I mean, look, any I SV can go on any cloud and take advantage of it. And that's, uh I love it. We live in a new world. How about machine learning workloads? What? What did you see there in terms of performance and benchmarks? >>Right. So machine learning. We offer three capabilities training, which is fully automated, running in France and explanations. So one of the things which many of our customers told us coming from the enterprise is that explanations are very important to them because, uh, customers want to know that. Why did the the system, uh, choose a certain prediction? So we offer explanations for all models which have been derailed by. That's the first thing. Now, one of the interesting things about training is that training is usually the most expensive phase of machine learning. So we have spent a lot of time improving the performance of training. So we have a bunch of techniques which we have developed inside of Oracle to improve the training process. For instance, we have, uh, metal and proxy models, which really give us an advantage. We use adaptive sampling. We have, uh, invented in techniques for paralysing the hyper parameter search. So as a result of a lot of this work, our training is about 25 times faster than that ship them health and all the data is, uh, inside the database. All this processing is being done inside the database, so it's much faster. It is inside the database. And I want to point out that there is no additional charge for the history of customers because we're using the same cluster. You're not working in your service. So all of these machine learning capabilities are being offered at no additional charge inside the database and as a performance, which is significantly faster than that, >>are you taking advantage of or is there any, uh, need not need, but any advantage that you can get if two by exploiting things like gravity. John, we've talked about that a little bit in the past. Or trainee. Um, you just mentioned training so custom silicon that AWS is doing, you're taking advantage of that. Do you need to? Can you give us some insight >>there? So there are two things, right? We're always evaluating What are the choices we have from hybrid perspective? Obviously, for us to leverage is right and like all the things you mention about like we have considered them. But there are two things to consider. One is he is a memory system. So he favours a big is the dominant cost. The processor is a person of the cost, but memory is the dominant cost. So what we have evaluated and found is that the current shape which we are using is going to provide our customers with the best price performance. That's the first thing. The second thing is that there are opportunities at times when we can use a specialised processor for vaccinating the world for a bit. But then it becomes a matter of the cost of the customer. Advantage of our current architecture is on the same hardware. Customers are getting very good performance. Very good, energetic performance in a very good machine learning performance. If you will go with the specialised processor, it may. Actually, it's a machine learning, but then it's an additional cost with the customers we need to pay. So we are very sensitive to the customer's request, which is usually to provide very good performance at a very low cost. And we feel is that the current design we have as providing customers very good performance and very good price performance. >>So part of that is architectural. The memory intensive nature of of heat wave. The other is A W s pricing. If AWS pricing were to flip, it might make more sense for you to take advantage of something like like cranium. Okay, great. Thank you. And welcome back to the benchmarks benchmarks. Sometimes they're artificial right there. A car can go from 0 to 60 in two seconds. But I might not be able to experience that level of performance. Do you? Do you have any real world numbers from customers that have used my sequel Heatwave on A W s. And how they look at performance? >>Yes, absolutely so the my Secret service on the AWS. This has been in Vera for, like, since November, right? So we have a lot of customers who have tried the service. And what actually we have found is that many of these customers, um, planning to migrate from Aurora to my secret heat rape. And what they find is that the performance difference is actually much more pronounced than what I was talking about. Because with Aurora, the performance is actually much poorer compared to uh, like what I've talked about. So in some of these cases, the customers found improvement from 60 times, 240 times, right? So he travels 100 for 240 times faster. It was much less expensive. And the third thing, which is you know, a noteworthy is that customers don't need to change their applications. So if you ask the top three reasons why customers are migrating, it's because of this. No change to the application much faster, and it is cheaper. So in some cases, like Johnny Bites, what they found is that the performance of their applications for the complex storeys was about 60 to 90 times faster. Then we had 60 technologies. What they found is that the performance of heat we have compared to Aurora was 100 and 39 times faster. So, yes, we do have many such examples from real workloads from customers who have tried it. And all across what we find is if it offers better performance, lower cost and a single database such that it is compatible with all existing by sequel based applications and workloads. >>Really impressive. The analysts I talked to, they're all gaga over heatwave, and I can see why. Okay, last question. Maybe maybe two and one. Uh, what's next? In terms of new capabilities that customers are going to be able to leverage and any other clouds that you're thinking about? We talked about that upfront, but >>so in terms of the capabilities you have seen, like they have been, you know, non stop attending to the feedback from the customers in reacting to it. And also, we have been in a wedding like organically. So that's something which is gonna continue. So, yes, you can fully expect that people not dressed and continue to in a way and with respect to the other clouds. Yes, we are planning to support my sequel. He tripped on a show, and this is something that will be announced in the near future. Great. >>All right, Thank you. Really appreciate the the overview. Congratulations on the work. Really exciting news that you're moving my sequel Heatwave into other clouds. It's something that we've been expecting for some time. So it's great to see you guys, uh, making that move, and as always, great to have you on the Cube. >>Thank you for the opportunity. >>All right. And thank you for watching this special cube conversation. I'm Dave Volonte, and we'll see you next time.

>>Hey, everyone. Welcome to the AWS partner, showcase women in tech. I'm Lisa Martin from the cube. And today we're gonna be looking into the exciting evolution of women in the tech industry. I'm going to be joined by Danielle GShock, the ISP PSA director at AWS. And we have the privilege of speaking with some wicked smart women from Teradata NetApp. JFI a 10th revolution group, company and honeycomb.io. We're gonna look at some of the challenges and biases that women face in the tech industry, especially in leadership roles. We're also gonna be exploring how are these tech companies addressing diversity, equity and inclusion across their organizations? How can we get more young girls into stem earlier in their careers? So many questions. So let's go ahead and get started. This is the AWS partner showcase women in tech. Hey, everyone. Welcome to the AWS partner showcase. This is season one, episode three. And I'm your host, Lisa Martin. I've got two great guests here with me to talk about women in tech. Hillary Ashton joins us the chief product officer at Terry data. And Danielle Greshaw is back with us, the ISV PSA director at AWS ladies. It's great to have you on the program talking through such an important topic, Hillary, let's go ahead and start with you. Give us a little bit of an intro into you, your background, and a little bit about Teradata. >>Yeah, absolutely. So I'm Hillary Ashton. I head up the products organization. So that's our engineering product management office of the CTO team. Um, at Teradata I've been with Terra data for just about three years and really have spent the last several decades. If I can say that in the data and analytics space, um, I spent time, uh, really focused on the value of, of analytics at scale, and I'm super excited to be here at Teradata. I'm also a mom of two teenage boys. And so as we talk about women in tech, I think there's, um, uh, lots of different dimensions and angles of that. Um, at Teradata, we are partnered very deeply with AWS and happy to talk a little bit more about that, um, throughout this discussion as well. >>Excellent. A busy mom of two teen boys. My goodness. I don't know how you do it. Let's now look, Atter data's views of diversity, equity and inclusion. It's a, the, it's a topic that's important to everyone, but give us a snapshot into some of the initiatives that Terra data has there. >>Yeah, I have to say, I am super proud to be working at Teradata. We have gone through, uh, a series of transformations, but I think it starts with culture and we are deeply committed to diversity, equity and inclusion. It's really more than just a statement here. It's just how we live our lives. Um, and we use, uh, data to back that up. Um, in fact, we were named one of the world's most ethical companies for the 13th year in a row. Um, and all of our executive leadership team has taken an oath around D E and I that's available on LinkedIn as well. So, um, in fact, our leadership team reporting into the CEO is just about 50 50, um, men and women, which is the first time I've worked in a company where that has been the case. And I think as individuals, we can probably appreciate what a huge difference that makes in terms of not just being a representative, but truly being on a, on a diverse and equitable, uh, team. And I think it really, uh, improves the behaviors that we can bring, um, to our office. >>There's so much value in that. It's I impressive to see about a 50 50 at the leadership level. That's not something that we see very often. Tell me how you, Hillary, how did you get into tech? Were you an engineering person by computer science, or did you have more of a zigzaggy path to where you are now? >>I'm gonna pick door number two and say more zigzaggy. Um, I started off thinking, um, that I started off as a political science major or a government major. Um, and I was probably destined to go into, um, the law field, but actually took a summer course at Harvard. I did not go to Harvard, but I took a summer course there and learned a lot about multimedia and some programming. And that really set me on a trajectory of how, um, data and analytics can truly provide value and, and outcomes to our customers. Um, and I have been living that life ever since. Um, I graduated from college, so, um, I was very excited and privileged in my early career to, uh, work in a company where I found after my first year that I was managing, um, uh, kids, people who had graduated from Harvard business school and from MIT Sloan school. Um, and that was super crazy, cuz I did not go to either of those schools, but I sort of have always had a natural knack for how do you take technology and, and the really cool things that technology can do, but because I'm not a programmer by training, I'm really focused on the value that I'm able to help, um, organizations really extract value, um, from the technology that we can create, which I think is fantastic. >>I think there's so much value in having a zigzag path into tech. You bring Danielle, you and I have talked about this many times you bring such breadth and such a wide perspective. That really is such a value. Add to teams. Danielle, talk to us from AWS's perspective about what can be done to encourage more young women to get and under and underrepresented groups as well, to get into stem and stay. >>Yeah, and this is definitely a challenge as we're trying to grow our organization and kind of shift the numbers. And the reality is, especially with the more senior folks in our organization, unless you bring folks with a zigzag path, the likelihood is you won't be able to change the numbers that you have. Um, but for me, it's really been about, uh, looking at that, uh, the folks who are just graduating college, maybe in other roles where they are adjacent to technology and to try to spark their interest and show that yes, they can do it because oftentimes it's really about believing in themselves and, and realizing that we need folks with all sorts of different perspectives to kind of come in, to be able to help really, um, provide both products and services and solutions for all types of people inside of technology, which requires all sorts of perspectives. >>Yeah, the diverse perspectives. There's so much value and there's a lot of data that demonstrates how much value revenue impact organizations can make by having diversity, especially at the leadership level. Hillary, let's go back to you. We talked about your career path. You talked about some of the importance of the focus on de and I at Tarana, but what are, what do you think can be done to encourage, to sorry, to recruit more young women and under groups into tech, any, any carrot there that you think are really important that we need to be dangling more of? >>Yeah, absolutely. And I'll build on what Danielle just said. I think the, um, bringing in diverse understandings, um, of, of customer outcomes, I mean, I, the we've really moved from technology for technology's sake and I know AWS and entirety to have had a lot of conversations on how do we drive customer outcomes that are differentiated in the market and really being customer centric and technology is wonderful. You can do wonderful things with it. You can do not so wonderful things with it as well, but unless you're really focused on the outcomes and what customers are seeking, um, technology is not hugely valuable. And so I think bringing in people who understand, um, voice of customer who understand those outcomes, and those are not necessarily the, the, the folks who are PhD in mathematics or statistics, um, those can be people who understand a day in the life of a data scientist or a day in the life of a citizen data scientist. And so really working to bridge the high impact technology with the practical kind of usability, usefulness of data and analytics in our cases, I think is something that we need more of in tech and sort of demystifying tech and freeing technology so that everybody can use it and having a really wide range of people who understand not just the bits and bites and, and how to program, but also the value in outcomes that technology through data and analytics can drive. >>Yeah. You know, we often talk about the hard skills, but this, their soft skills are equally, if not more important that even just being curious, being willing to ask questions, being not afraid to be vulnerable, being able to show those sides of your personality. I think those are important for, for young women and underrepresented groups to understand that those are just as important as some of the harder technical skills that can be taught. >>That's right. >>What do you think about from a bias perspective, Hillary, what have you seen in the tech industry and how do you think we can leverage culture as you talked about to help dial down some of the biases that are going on? >>Yeah. I mean, I think first of all, and, and there's some interesting data out there that says that 90% of the population, which includes a lot of women have some inherent bias in their day, day behaviors when it comes to to women in particular. But I'm sure that that is true across all kinds of, of, um, diverse and underrepresented folks in, in the world. And so I think acknowledging that we have bias and actually really learning how, what that can look like, how that can show up. We might be sitting here and thinking, oh, of course I don't have any bias. And then you realize that, um, as you, as you learn more about, um, different types of bias, that actually you do need to kind of, um, account for that and change behaviors. And so I think learning is sort of a fundamental, um, uh, grounding for all of us to really know what bias looks like, know how it shows up in each of us. >>Um, if we're leaders know how it shows up in our teams and make sure that we are constantly getting better, we're, we're not gonna be perfect anytime soon. But I think being on a path to improvement to overcoming bias, um, is really, is really critical. And part of that is really starting the dialogue, having the conversations, holding ourselves and each other accountable, um, when things aren't going in, in a, in a Coptic way and being able to talk openly about that, that felt, um, like maybe there was some bias in that interaction and how do we, um, how do we make good on that? How do we change our, our behavior? Fundamentally of course, data and analytics can have some bias in it as well. And so I think as we look at the, the technology aspect of bias, um, looking at at ethical AI, I think is a, a really important, uh, additional area. And I'm sure we could spend another 20 minutes talking about that, but I, I would be remiss if I didn't talk more about sort of the bias, um, and the over the opportunity to overcome bias in data and analytics as well. >>Yeah. The opportunity to overcome it is definitely there you bring up a couple of really good points, Hillary. It, it starts with awareness. We need to be aware that there are inherent biases in data in thought. And also to your other point, hold people accountable ourselves, our teammates, that's critical to being able to, to dial that back down, Daniel, I wanna get your perspective on, on your view of women in leadership roles. Do you think that we have good representation or we still have work to do in there? >>I definitely think in both technical and product roles, we definitely have some work to do. And, you know, when I think about, um, our partnership with Teradata, part of the reason why it's so important is, you know, Teradata solution is really the brains of a lot of companies. Um, you know, the what, how, what they differentiate on how they figure out insights into their business. And it's, it's all about the product itself and the data and the same is true at AWS. And, you know, we really could do some work to have some more women in these technical roles, as well as in the product, shaping the products. Uh, just for all the reasons that we just kind of talked about over the last 10 minutes, um, in order to, you know, move bias out of our, um, out of our solutions and also to just build better products and have, uh, better, you know, outcomes for customers. So I think there's a bit of work to do still. >>I agree. There's definitely a bit of work to do, and it's all about delivering those better outcomes for customers at the end of the day, we need to figure out what the right ways are of doing that and working together in a community. Um, we've had obviously a lot had changed in the last couple of years, Hillary, what's your, what have you seen in terms of the impact that the pandemic has had on this status of women in tech? Has it been a pro is silver lining the opposite? What are you seeing? >>Yeah, I mean, certainly there's data out there that tells us factually that it has been, um, very difficult for women during COVID 19. Um, women have, uh, dropped out of the workforce for a wide range of, of reasons. Um, and, and that I think is going to set us back all of us, the, the Royal us or the Royal we back, um, years and years. Um, and, and it's very unfortunate because I think we we're at a time when we're making great progress and now to see COVID, um, setting us back in, in such a powerful way. I think there's work to be done to understand how do we bring people back into the workforce. Um, how do we do that? Understanding work life balance, better understanding virtual and remote, working better. I think in the technology sector, um, we've really embraced, um, hybrid virtual work and are, are empowering people to bring their whole selves to work. >>And I think if anything, these, these zoom calls have, um, both for the men and the women on my team. In fact, I would say much more. So for the men on my team, I'm seeing, I was seeing more kids in the background, more kind of split childcare duties, more ability to start talking about, um, other responsibilities that maybe they had, uh, especially in the early days of COVID where maybe daycares were shut down. And, um, you had, you know, maybe a parent was sick. And so we saw quite a lot of, um, people bringing their whole selves to the office, which I think was, was really wonderful. Um, uh, even our CEO saw some of that. And I think, um, that that really changes the dialogue, right? It changes it to maybe scheduling meetings at a time when, um, people can do it after daycare drop off. >>Um, and really allowing that both for men and for women makes it better for, for women overall. So I would like to think that this hybrid working, um, environment and that this, um, uh, whole view into somebody's life that COVID has really provided for probably for white collar workers, if I'm being honest for, um, people who are in a, at a better point of privilege, they don't necessarily have to go into the office every day. I would like to think that tech can lead the way in, um, you know, coming out of the, the old COVID. I don't know if we have a new COVID coming, but the old COVID and really leading the way for women and for people, um, to transform how we do work, um, leveraging data and analytics, but also, um, overcoming some of the, the disparities that exist for women in particular in the workforce. >>Yeah, I think there's, there's like we say, there's a lot of opportunity there and I like your point of hopefully tech can be that guiding light that shows us this can be done. We're all humans at the end of the day. And ultimately if we're able to have some sort of work life balance, everything benefits, our work or more productive, higher performing teams impacts customers, right? There's so much value that can be gleaned from, from that hybrid model and embracing for humans. We need to be able to, to work when we can, we've learned that you don't have to be, you know, in an office 24, 7 commuting, crazy hours flying all around the world. We can get a lot of things done in a ways that fit people's lives rather than taking command over it. Wanna get your advice, Hillary, if you were to talk to your younger self, what would be some of the key pieces of advice you would say? And Danielle and I have talked about this before, and sometimes we, we would both agree on like, ask more questions. Don't be afraid to raise your hand, but what advice would you give your younger self and that younger generation in terms of being inspired to get into tech >>Oh, inspired and being in tech? You know, I think looking at technology as, in some ways, I feel like we do a disservice to, um, inclusion when we talk about stem, cuz I think stem can be kind of daunting. It can be a little scary for people for younger people. When I, when I go and talk to folks at schools, I think stem is like, oh, all the super smart kids are over there. They're all like maybe they're all men. And so, um, it's, it's a little, uh, intimidating. Um, and stem is actually, you know, especially for, um, people joining the workforce today. It's actually how you've been living your life since you were born. I mean, you know, stem inside and out because you walk around with a phone and you know how to get your internet working and like that is technology right. >>Fundamentally. And so demystifying stem as something that is around how we, um, actually make our, our lives useful and, and, and how we can change outcomes. Um, through technology I think is maybe a different lens to put on it. So, and there's absolutely for, for hard sciences, there's absolutely a, a great place in the world for folks who wanna pursue that and men and women can do that. So I, I don't want to be, um, uh, setting the wrong expectations, but I, I think stem is, is very holistic in, um, in the change that's happening globally for us today across economies, across global warming, across all kinds of impactful issues. And so I think everybody who's interested in, in some of that world change can participate in stem. It just may be through a different, through a different lens than how we classically talk about stem. >>So I think there's great opportunity to demystify stem. I think also, um, what I would tell my younger self is choose your bosses wisely. And that sounds really funny. That sounds like inside out almost, but I think choose the person that you're gonna work for in your first five to seven years. And it might be more than one person, but be, be selective, maybe be a little less selective about the exact company or the exact title. I think picking somebody that, you know, we talk about mentors and we talk about sponsors and those are important. Um, but the person you're gonna spend in your early career, a lot of your day with a lot, who's gonna influence a lot of the outcomes for you. That is the person that you, I think want to be more selective about, um, because that person can set you up for success and give you opportunities and set you on course to be, um, a standout or that person can hold you back. >>And that person can put you in the corner and not invite you to the meetings and not give you those opportunities. And so we're in an economy today where you actually can, um, be a little bit picky about who you go and work for. And I would encourage my younger self. I actually, I just lucked out actually, but I think that, um, my first boss really set me, um, up for success, gave me a lot of feedback and coaching. Um, and some of it was really hard to hear, but it really set me up for, for, um, the, the path that I've been on ever since. So it, that would be my advice. >>I love that advice. I it's brilliant. I didn't think it choose your bosses wisely. Isn't something that we primarily think about. I think a lot of people think about the big name companies that they wanna go after and put on a resume, but you bring up a great point. And Danielle and I have talked about this with other guests about mentors and sponsors. I think that is brilliant advice and also more work to do to demystify stem. But luckily we have great family leaders like the two of you helping us to do that. Ladies, I wanna thank you so much for joining me on the program today and talking through what you're seeing in de and I, what your companies are doing and the opportunities that we have to move the needle. Appreciate your time. >>Thank you so much. Great to see you, Danielle. Thank you Lisa, to see you. >>My pleasure for my guests. I'm Lisa Martin. You're watching the AWS partner showcase season one, episode three. Hey everyone. Welcome to the AWS partner showcase. This is season one, episode three, with a focus on women in tech. I'm your host, Lisa Martin. I've got two guests here with me, Sue Peretti, the EVP of global AWS strategic alliances at Jefferson Frank, a 10th revolution group company, and Danielle brushoff. One of our cube alumni joins us ISV PSA director, ladies. It's great to have you on the program talking about a, a topic that is near and dear to my heart at women in tech. >>Thank you, Lisa. >>So let's go ahead and start with you. Give the audience an understanding of Jefferson Frank, what does the company do and about the partnership with AWS? >>Sure. Um, so let's just start, uh, Jefferson Frank is a 10th revolution group company. And if you look at it, it's really talent as a service. So Jefferson Frank provides talent solutions all over the world for AWS clients, partners and users, et cetera. And we have a sister company called revelent, which is a talent creation company within the AWS ecosystem. So we create talent and put it out in the ecosystem. Usually underrepresented groups over half of them are women. And then we also have, uh, a company called rubra, which is a delivery model around AWS technology. So all three companies fall under the 10th revolution group organization. >>Got it. Danielle, talk to me a little bit about from AWS's perspective and the focus on hiring more women in technology and about the partnership. >>Yes. I mean, this has definitely been a focus ever since I joined eight years ago, but also just especially in the last few years we've grown exponentially and our customer base has changed. You know, we wanna have, uh, an organization interacting with them that reflects our customers, right. And, uh, we know that we need to keep pace with that even with our growth. And so we've very much focused on early career talent, um, bringing more women and underrepresented minorities into the organization, sponsoring those folks, promoting them, uh, giving them paths to growth, to grow inside of the organization. I'm an example of that. Of course I benefit benefited from it, but also I try to bring that into my organization as well. And it's super important. >>Tell me a little bit about how you benefited from that, Danielle. >>Um, I just think that, um, you know, I I've been able to get, you know, a seat at the table. I think that, um, I feel as though I have folks supporting me, uh, very deeply and wanna see me succeed. And also they put me forth as, um, you know, a, represent a representative, uh, to bring more women into the organization as well. And I think, um, they give me a platform, uh, in order to do that, um, like this, um, but also many other, uh, spots as well. Um, and I'm happy to do it because I feel that, you know, if you always wanna feel that you're making a difference in your job, and that is definitely a place where I get that time and space in order to be that representative to, um, bring more, more women into benefiting from having careers in technology, which there's a lot of value there, >>A lot of value. Absolutely. So back over to you, what are some of the trends that you are seeing from a gender diversity perspective in tech? We know the, the numbers of women in technical positions, uh, right. There's so much data out there that shows when girls start dropping up, but what are some of the trends that you are seeing? >>So it's, that's a really interesting question. And, and Lisa, I had a whole bunch of data points that I wanted to share with you, but just two weeks ago, uh, I was in San Francisco with AWS at the, at the summit. And we were talking about this. We were talking about how we can collectively together attract more women, not only to, uh, AWS, not only to technology, but to the AWS ecosystem in particular. And it was fascinating because I was talking about, uh, the challenges that women have and how hard to believe, but about 5% of women who were in the ecosystem have left in the past few years, which was really, really, uh, something that shocked everyone when we, when we were talking about it, because all of the things that we've been asking for, for instance, uh, working from home, um, better pay, uh, more flexibility, uh, better maternity leave seems like those things are happening. >>So we're getting what we want, but people are leaving. And it seemed like the feedback that we got was that a lot of women still felt very underrepresented. The number one thing was that they, they couldn't be, you can't be what you can't see. So because they, we feel collectively women, uh, people who identify as women just don't see enough women in leadership, they don't see enough mentors. Um, I think I've had great mentors, but, but just not enough. I'm lucky enough to have a pres a president of our company, the president of our company, Zoe Morris is a woman and she does lead by example. So I'm very lucky for that. And Jefferson, Frank really quickly, we put out a hiring a salary and hiring guide a career and hiring guide every year and the data points. And that's about 65 pages long. No one else does it. Uh, it gives an abundance of information around, uh, everything about the AWS ecosystem that a hiring manager might need to know. But there is what, what I thought was really unbelievable was that only 7% of the people that responded to it were women. So my goal, uh, being that we have such a very big global platform is to get more women to respond to that survey so we can get as much information and take action. So >>Absolutely 7%. So a long way to go there. Danielle, talk to me about AWS's focus on women in tech. I was watching, um, Sue, I saw that you shared on LinkedIn, the Ted talk that the CEO and founder of girls and co did. And one of the things that she said was that there was a, a survey that HP did some years back that showed that, um, 60%, that, that men will apply for jobs if they only meet 60% of the list of requirements. Whereas with females, it's far, far less, we've all been in that imposter syndrome, um, conundrum before. But Danielle, talk to us about AWS, a specific focus here to get these numbers up. >>I think it speaks to what Susan was talking about, how, you know, I think we're approaching it top and bottom, right? We're looking out at what are the, who are the women who are currently in technical positions and how can we make AWS an attractive place for them to work? And that's all a lot of the changes that we've had around maternity leave and, and those types of things, but then also, um, more flexible working, uh, can, you know, uh, arrangements, but then also, um, early, how can we actually impact early, um, career women and actually women who are still in school. Um, and our training and certification team is doing amazing things to get, um, more girls exposed to AWS, to technology, um, and make it a less intimidating place and have them look at employees from AWS and say like, oh, I can see myself in those people. >>Um, and kind of actually growing the viable pool of candidates. I think, you know, we're, we're limited with the viable pool of candidates, um, when you're talking about mid to late career. Um, but how can we, you know, help retrain women who are coming back into the workplace after, you know, having a child and how can we help with military women who want to, uh, or underrepresented minorities who wanna move into AWS, we have a great military program, but then also just that early high school, uh, career, you know, getting them in, in that trajectory. >>Sue, is that something that Jefferson Frank is also able to help with is, you know, getting those younger girls before they start to feel there's something wrong with me. I don't get this. Talk to us about how Jefferson Frank can help really drive up that in those younger girls. >>Uh, let me tell you one other thing to refer back to that summit that we did, uh, we had breakout sessions and that was one of the topics. What can cuz that's the goal, right? To make sure that, that there are ways to attract them. That's the goal? So some of the things that we talked about was mentoring programs, uh, from a very young age, some people said high school, but then we said even earlier, goes back to you. Can't be what you can't see. So, uh, getting mentoring programs, uh, established, uh, we also talked about some of the great ideas was being careful of how we speak to women using the right language to attract them. And some, there was a teachable moment for, for me there actually, it was really wonderful because, um, an African American woman said to me, Sue and I, I was talking about how you can't be what you can't see. >>And what she said was Sue, it's really different. Um, for me as an African American woman, uh, or she identified, uh, as nonbinary, but she was relating to African American women. She said, your white woman, your journey was very different than my journey. And I thought, this is how we're going to learn. I wasn't offended by her calling me out at all. It was a teachable moment. And I thought I understood that, but those are the things that we need to educate people on those, those moments where we think we're, we're saying and doing the right thing, but we really need to get that bias out there. So here at Jefferson, Frank, we're, we're trying really hard to get that careers and hiring guide out there. It's on our website to get more women, uh, to talk to it, but to make suggestions in partnership with AWS around how we can do this mentoring, we have a mentor me program. We go around the country and do things like this. We, we try to get the education out there in partnership with AWS. Uh, we have a, a women's group, a women's leadership group, uh, so much that, that we do, and we try to do it in partnership with AWS. >>Danielle, can you comment on the impact that AWS has made so far, um, regarding some of the trends and, and gender diversity that Sue was talking about? What's the impact that's been made so far with this partnership? >>Well, I mean, I think just being able to get more of the data and have awareness of leaders, uh, on how <laugh>, you know, it used to be a, a couple years back, I would feel like sometimes the, um, uh, solving to bring more women into the organization was kind of something that folks thought, oh, this is Danielle is gonna solve this. You know? And I think a lot of folks now realize, oh, this is something that we all need to solve for. And a lot of my colleagues who maybe a couple years ago, didn't have any awareness or didn't even have the tools to do what they needed to do in order to improve the statistics on their, or in their organizations. Now actually have those tools and are able to kind of work with, um, work with companies like Susan's work with Jefferson Frank in order to actually get the data and actually make good decisions and feel as though, you know, they, they often, these are not lived experiences for these folks, so they don't know what they don't know. And by providing data and providing awareness and providing tooling and then setting goals, I think all of those things have really turned, uh, things around in a very positive way. >>And so you bring up a great point about from a diversity perspective, what is Jefferson Frank doing to, to get those data points up, to get more women of, of all well, really underrepresented minorities to, to be able to provide that feedback so that you can, can have the data and gleamy insights from it to help companies like AWS on their strategic objectives. >>Right? So as I, when I go back to that higher that, uh, careers in hiring guide, that is my focus today, really because the more data that we have, I mean, the, and the data takes, uh, you know, we need people to participate in order to, to accurately, uh, get a hold of that data. So that's why we're asking, uh, we're taking the initiative to really expand our focus. We are a global organization with a very, very massive database all over the world, but if people don't take action, then we can't get the right. The, the, the data will not be as accurate as we'd like it to be. Therefore take better action. So what we're doing is we're asking people all over the, all over the world to participate on our website, Jefferson frank.com, the se the high, uh, in the survey. So we can learn as much as we can. >>7% is such a, you know, Danielle and I we're, we've got to partner on this just to sort of get that message out there, get more data so we can execute, uh, some of the other things that we're doing. We're, we're partnering in. As I mentioned, more of these events, uh, we're, we're doing around the summits, we're gonna be having more ed and I events and collecting more information from women. Um, like I said, internally, we do practice what we preach and we have our own programs that are, that are out there that are within our own company where the women who are talking to candidates and clients every single day are trying to get that message out there. So if I'm speaking to a client or one of our internal people are speaking to a client or a candidate, they're telling them, listen, you know, we really are trying to get these numbers up. >>We wanna attract as many people as we can. Would you mind going to this, uh, hiring guide and offering your own information? So we've gotta get that 7% up. We've gotta keep talking. We've gotta keep, uh, getting programs out there. One other thing I wanted to Danielle's point, she mentioned, uh, women in leadership, the number that we gathered was only 9% of women in leadership within the AWS ecosystem. We've gotta get that number up, uh, as well because, um, you know, I know for me, when I see people like Danielle or, or her peers, it inspires me. And I feel like, you know, I just wanna give back, make sure I send the elevator back to the first floor and bring more women in to this amazing ecosystem. >>Absolutely. That's not that metaphor I do too, but we, but to your point to get that those numbers up, not just at AWS, but everywhere else we need, it's a help me help use situation. So ladies underrepresented minorities, if you're watching go to the Jefferson Frank website, take the survey, help provide the data so that the woman here that are doing this amazing work, have it to help make decisions and have more of females and leadership roles or underrepresented minorities. So we can be what we can see. Ladies, thank you so much for joining me today and sharing what you guys are doing together to partner on this important. Cause >>Thank you for having me, Leah, Lisa, >>Thank you. My pleasure for my guests. I'm Lisa Martin. You're watching the cubes coverage of the AWS partner showcase. Thanks for your time. Hey everyone. Welcome to the AWS partner showcase season one, episode three women in tech. I'm your host, Lisa Martin. We've got two female rock stars here with me next. Stephanie Curry joins us the worldwide head of sales and go to market strategy for AWS at NetApp and Danielle GShock is back one of our QM ISV PSA director at AWS. Looking forward to a great conversation, ladies, about a great topic, Stephanie, let's go ahead and start with you. Give us an overview of your story, how you got into tech and what inspired you. >>Thanks so much, Lisa and Danielle. It's great to be on this show with you. Um, thank you for that. Uh, my name's Stephanie cur, as Lisa mentioned, I'm the worldwide head of sales for, uh, AWS at NetApp and run a global team of sales people that sell all things AWS, um, going back 25 years now, uh, when I first started my career in tech, it was kind of by accident. Um, I come from a different background. I have a business background and a technical background from school, um, but had been in a different career and I had an opportunity to try something new. Um, I had an ally really that reached out to me and said, Hey, you'd be great for this role. And I thought, I'd take a chance. I was curious. Um, and, uh, it, it turned out to be a 25 year career, um, that I'm really, really excited about and, and, um, really thankful for that person, for introducing me to the, to the industry >>25 years in counting. I'm sure Danielle, we've talked about your background before. So what I wanna focus on with you is the importance of diversity for high performance. I know what a machine AWS is, and Stephanie'll come back to you with the same question, but talk about that, Danielle, from your perspective, that importance, um, for diversity to drive the performance. >>Yeah. Yeah. I truly believe that, you know, in order to have high performing teams, that you have to have people from all different types of backgrounds and experiences. And we do find that oftentimes being, you know, field facing, if we're not reflecting our customers and connecting with them deeply, um, on, on the levels that they're at, we, we end up missing them. And so for us, it's very important to bring people of lots of different technical backgrounds experiences. And of course, both men, women, and underrepresented minorities and put that forth to our customers, um, in order to make that connection and to end up with better outcomes. So >>Definitely it's all about outcomes, Stephanie, your perspective and NetApp's perspective on diversity for creating highly performant teams and organizations. >>I really aligned with Danielle on the comment she made. And in addition to that, you know, just from building teams in my, um, career know, we've had three times as many women on my team since we started a year ago and our results are really showing in that as well. Um, we find the teams are stronger, they're more collaborative and to Danielle's point really reflective, not only our partners, but our customers themselves. So this really creates connections, which are really, really important to scale our businesses and, and really, uh, meet the customer where they're at as well. So huge proponent of that ourselves, and really finding that we have to be intentional in our hiring and intentional in how we attract diversity to our teams. >>So Stephanie let's stay with you. So a three X increase in women on the team in a year, especially the kind of last year that we've had is really incredible. I, I like your, I, your thoughts on there needs to be a, there needs to be focus and, and thought in how teams are hired. Let's talk about attracting and retaining those women now, especially in sales roles, we all know the number, the percentages of women in technical roles, but what are some of the things that, that you do Stephanie, that NetApp does to attract and retain women in those sales roles? >>The, the attracting part's really interesting. And we find that, you know, you, you read the stats and I'd say in my experience, they're also true in the fact that, um, a lot of women would look at a job description and say, I can't do a hundred percent of that, that, so I'm not even going to apply with the women that we've attracted to our team. We've actually intentionally reached out and targeted those people in a good way, um, to say, Hey, we think you've got what it takes. Some of the feedback I've got from those women are, gosh, I didn't think I could ever get this role. I didn't think I had the skills to do that. And they've been hired and they are doing a phenomenal job. In addition to that, I think a lot of the feedback I've got from these hires are, Hey, it's an aggressive sales is aggressive. Sales is competitive. It's not an environment that I think I can be successful in. And what we're showing them is bring those softer skills around collaboration, around connection, around building teams. And they do, they do bring a lot of that to the team. Then they see others like them there and they know they can be successful cuz they see others like them on the team, >>The whole concept of we can't be what we can't see, but we can be what we can't see is so important. You said a couple things, Stephanie, that really stuck with me. And one of them was an interview on the Cub I was doing, I think a couple weeks ago, um, about women in tech. And the stat that we talked about was that women will apply will not apply for a job unless they meet 100% of the skills and the requirements that it's listed, but men will, if they only meet 60. And I, that just shocked me that I thought, you know, I, I can understand that imposter syndrome is real. It's a huge challenge, but the softer skills, as you mentioned, especially in the last two years, plus the ability to communicate, the ability to collaborate are incredibly important to, to drive that performance of any team of any business. >>Absolutely. >>Danielle, talk to me about your perspective and AWS as well for attracting and retaining talent. And, and, and particularly in some of those challenging roles like sales that as Stephanie said, can be known as aggressive. >>Yeah, for sure. I mean, my team is focused on the technical aspect of the field and we definitely have an uphill battle for sure. Um, two things we are focused on first and foremost is looking at early career women and that how we, how can we bring them into this role, whether in they're in support functions, uh, cl like answering the phone for support calls, et cetera, and how, how can we bring them into this organization, which is a bit more strategic, more proactive. Um, and then the other thing that as far as retention goes, you know, sometimes there will be women who they're on a team and there are no other women on that team. And, and for me, it's about building community inside of AWS and being part of, you know, we have women on solution architecture organizations. We have, uh, you know, I just personally connect people as well and to like, oh, you should meet this person. Oh, you should talk to that person. Because again, sometimes they can't see someone on their team like them and they just need to feel anchored, especially as we've all been, you know, kind of stuck at home, um, during the pandemic, just being able to make those connections with women like them has been super important and just being a, a long tenured Amazonian. Um, that's definitely one thing I'm able to, to bring to the table as well. >>That's so important and impactful and spreads across organizations in a good way. Daniel let's stick with you. Let's talk about some of the allies that you've had sponsors, mentors that have really made a difference. And I said that in past tense, but I also mean in present tense, who are some of those folks now that really inspire you? >>Yeah. I mean, I definitely would say that one of my mentors and someone who, uh, ha has been a sponsor of my career has, uh, Matt YK, who is one of our control tower GMs. He has really sponsored my career and definitely been a supporter of mine and pushed me in positive ways, which has been super helpful. And then other of my business partners, you know, Sabina Joseph, who's a cube alum as well. She definitely has been, was a fabulous partner to work with. Um, and you know, between the two of us for a period of time, we definitely felt like we could, you know, conquer the world. It's very great to go in with a, with another strong woman, um, you know, and, and get things done, um, inside of an organization like AWS. >>Absolutely. And S I've, I've agreed here several times. So Stephanie, same question for you. You talked a little bit about your kind of, one of your, uh, original early allies in the tech industry, but talk to me about allies sponsors, mentors who have, and continue to make a difference in your life. >>Yeah. And, you know, I think it's a great differentiation as well, right? Because I think that mentors teach us sponsors show us the way and allies make room for us at the table. And that is really, really key difference. I think also as women leaders, we need to make room for others at the table too, and not forget those softer skills that we bring to the table. Some of the things that Danielle mentioned as well about making those connections for others, right. And making room for them at the table. Um, some of my allies, a lot of them are men. Brian ABI was my first mentor. Uh, he actually is in the distribution, was in distribution, uh, with advent tech data no longer there. Um, Corey Hutchinson, who's now at Hashi Corp. He's also another ally of mine and remains an ally of mine, even though we're not at the same company any longer. Um, so a lot of these people transcend careers and transcend, um, um, different positions that I've held as well and make room for us. And I think that's just really critical when we're looking for allies and when allies are looking for us, >>I love how you described allies, mentors and sponsors Stephanie. And the difference. I didn't understand the difference between a mentor and a sponsor until a couple of years ago. Do you talk with some of those younger females on your team so that when they come into the organization and maybe they're fresh outta college, or maybe they've transitioned into tech so that they can also learn from you and understand the importance and the difference between the allies and the sponsors and the mentors? >>Absolutely. And I think that's really interesting because I do take, uh, an extra, uh, approach an extra time to really reach out to the women that have joined the team. One. I wanna make sure they stay right. I don't want them feeling, Hey, I'm alone here and I need to, I need to go do something else. Um, and they are located around the world, on my team. They're also different age groups, so early in career, as well as more senior people and really reaching out, making sure they know that I'm there. But also as Danielle had mentioned, connecting them to other people in the community that they can reach out to for those same opportunities and making room for them >>Make room at the table. It's so important. And it can, you never know what a massive difference and impact you can make on someone's life. And I, and I bet there's probably a lot of mentors and sponsors and allies of mine that would be surprised to know, uh, the massive influence they've had Daniel back over. Let's talk about some of the techniques that you employ, that AWS employees to make the work environment, a great place for women to really thrive and, and be retained as Stephanie was saying. Of course that's so important. >>Yeah. I mean, definitely I think that the community building, as well as we have a bit more programmatic mentorship, um, we're trying to get to the point of having a more programmatic sponsorship as well. Um, but I think just making sure that, um, you know, both everything from, uh, recruit to onboard to ever boarding that, uh, they they're the women who come into the organization, whether it's they're coming in on the software engineering side or the field side or the sales side that they feel as that they have someone, uh, working with them to help them drive their career. Those are the key things that were, I think from an organizational perspective are happening across the board. Um, for me personally, when I run my organization, I'm really trying to make sure that people feel that they can come to me at any time open door policy, make sure that they're surfacing any times in which they are feeling excluded or anything like that, any challenges, whether it be with a customer, a partner or with a colleague. Um, and then also of course, just making sure that I'm being a good sponsor, uh, to, to people on my team. Um, that is key. You can talk about it, but you have to start with yourself as well. >>That's a great point. You you've got to, to start with yourself and really reflect on that. Mm-hmm <affirmative> and look, am I, am I embodying what it is that I need? And not that I know they need that focused, thoughtful intention on that is so importants, let's talk about some of the techniques that you use that NetApp uses to make the work environment a great place for those women are marginalized, um, communities to really thrive. >>Yeah. And I appreciate it and much like Danielle, uh, and much like AWS, we have some of those more structured programs, right around sponsorship and around mentorship. Um, probably some growth there, opportunities for allies, because I think that's more of a newer concept in really an informal structure around the allies, but something that we're growing into at NetApp, um, on my team personally, I think, um, leading by example's really key. And unfortunately, a lot of the, um, life stuffs still lands on the women, whether we like it or not. Uh, I have a very, uh, active husband in our household, but I still carry when it push comes to shove it's on me. Um, and I wanna make sure that my team knows it's okay to take some time and do the things you need to do with your family. Um, I'm I show up as myself authentically and I encourage them to do the same. >>So it's okay to say, Hey, I need to take a personal day. I need to focus on some stuff that's happening in my personal life this week now, obviously to make sure your job's covered, but just allowing some of that softer vulnerability to come into the team as well, so that others, um, men and women can feel they can do the same thing. And that it's okay to say, I need to balance my life and I need to do some other things alongside. Um, so it's the formal programs, making sure people have awareness on them. Um, I think it's also softly calling people out on biases and saying, Hey, I'm not sure if you know, this landed that way, but I just wanted to make you aware. And usually the feedback is, oh my gosh, I didn't know. And could you coach me on something that I could do better next time? So all of this is driven through our NetApp formal programs, but then it's also how you manifest it on the teams that we're leading. >>Absolutely. And sometimes having that mirror to reflect into can be really eye-opening and, and allow you to, to see things in a completely different light, which is great. Um, you both talked about, um, kind of being what you, uh, can see, and, and I know both companies are upset customer obsessed in a good way. Talk to me a little bit, Danielle, go back over to you about the AWS NetApp partnership. Um, some of that maybe alignment on, on performance on obviously you guys are very well aligned, uh, in terms of that, but also it sounds like you're quite aligned on diversity and inclusion. >>Well, we definitely do. We have the best partnerships with companies in which we have these value alignments. So I think that is a positive thing, of course, but just from a, from a partnership perspective, you know, from my five now plus years of being a part of the APN, this is, you know, one of the most significant years with our launch of FSX for NetApp. Um, with that, uh, key key service, which we're making available natively on AWS. I, I can't think of a better Testament to the, to the, um, partnership than that. And that's doing incredibly well and it really resonates with our customers. And of course it started with customers and their need for NetApp. Uh, so, you know, that is a reflection, I think, of the success that we're having together. >>And Stephanie talk to, uh, about the partnership from your perspective, NetApp, AWS, what you guys are doing together, cultural alignment, but also your alignment on really bringing diversity into drive performance. >>Yeah, I think it's a, a great question. And I have to say it's just been a phenomenal year. Our relationship has, uh, started before our first party service with FSX N but definitely just, um, uh, the trajectory, um, between the two companies since the announcement about nine months ago has just taken off to a, a new level. Um, we feel like an extended part of the family. We worked together seamlessly. A lot of the people in my team often say we feel like Amazonians. Um, and we're really part of this transformation at NetApp from being that storage hardware company into being an ISV and a cloud company. And we could not do this without the partnership with AWS and without the, uh, first party service of Fs XM that we've recently released. Um, I think that those joint values that Danielle referred to are critical to our success, um, starting with customer obsession and always making sure that we are doing the right thing for the customer. >>We coach our team teams all the time on if you are doing the right thing for the customers, you cannot do anything wrong. Just always put the customer at the, in the center of your decisions. And I think that there is, um, a lot of best practice sharing and collaboration as we go through this change. And I think a lot of it is led by the diverse backgrounds that are on the team, um, female, male, um, race and so forth, and just to really, uh, have different perspectives and different experiences about how we approach this change. Um, so we definitely feel like a part of the family. Uh, we are absolutely loving, uh, working with the AWS team and our team knows that we are the right place, the right time with the right people. >>I love that last question for each of you. And I wanna stick with you Stephanie advice to your younger self, think back five years. What advice would you seen what you've accomplished and maybe the thet route that you've taken along the way, what would you advise your youngest Stephanie self. >>Uh, I would say keep being curious, right? Keep being curious, keep asking questions. And sometimes when you get a no, it's not a bad thing, it just means not right now and find out why and, and try to get feedback as to why maybe that wasn't the right opportunity for you. But, you know, just go for what you want. Continue to be curious, continue to ask questions and find a support network of people around you that wanna help you because they are there and they, they wanna see you be successful too. So never be shy about that stuff. >><laugh> absolutely. And I always say failure does not have to be an, a bad F word. A no can be the beginning of something. Amazing. Danielle, same question for you. Thinking back to when you first started in your career, what advice would you give your younger self? >>Yeah, I think the advice I'd give my younger self would be, don't be afraid to put yourself out there. Um, it's certainly, you know, coming from an engineering background, maybe you wanna stay behind the scenes, not, not do a presentation, not do a public speaking event, those types of things, but back to what the community really needs, this thing. Um, you know, I genuinely now, uh, took me a while to realize it, but I realized I needed to put myself out there in order to, um, you know, allow younger women to see what they could be. So that would be the advice I would give. Don't be afraid to put yourself out there. >>Absolutely. That advice that you both gave are, is so fantastic, so important and so applicable to everybody. Um, don't be afraid to put yourself out there, ask questions. Don't be afraid of a, no, that it's all gonna happen at some point or many points along the way. That can also be good. So thank you ladies. You inspired me. I appreciate you sharing what AWS and NetApp are doing together to strengthen diversity, to strengthen performance and the advice that you both shared for your younger selves was brilliant. Thank you. >>Thank you. >>Thank you >>For my guests. I'm Lisa Martin. You're watching the AWS partner showcase. See you next time. Hey everyone. Welcome to the AWS partner showcase season one, episode three women in tech. I'm your host, Lisa Martin. I've got two female rock stars joining me. Next Vero Reynolds is here engineering manager, telemetry at honeycomb, and one of our cube alumni, Danielle Ock ISV PSA director at AWS. Join us as well. Ladies. It's great to have you talking about a very important topic today. >>Thanks for having us. >>Yeah, thanks for having me. Appreciate it. >>Of course, Vera, let's go ahead and start with you. Tell me about your background and tech. You're coming up on your 10th anniversary. Happy anniversary. >>Thank you. That's right. I can't believe it's been 10 years. Um, but yeah, I started in tech in 2012. Um, I was an engineer for most of that time. Uh, and just recently as a March, switched to engineering management here at honeycomb and, um, you know, throughout my career, I was very much interested in all the things, right. And it was a big FOMO as far as trying a few different, um, companies and products. And I've done things from web development to mobile to platforms. Um, it would be apt to call me a generalist. Um, and in the more recent years I was sort of gravitating more towards developer tool space. And for me that, uh, came in the form of cloud Foundry circle CI and now honeycomb. Um, I actually had my eye on honeycomb for a while before joining, I came across a blog post by charity majors. >>Who's one of our founders and she was actually talking about management and how to pursue that and whether or not it's right, uh, for your career. And so I was like, who is this person? I really like her, uh, found the company. They were pretty small at the time. So I was sort of keeping my eye on them. And then when the time came around for me to look again, I did a little bit more digging, uh, found a lot of talks about the product. And on the one hand they really spoke to me as the solution. They talked about developers owning their coding production and answering questions about what is happening, what are your users seeing? And I felt that pain, I got what they were trying to do. And also on the other hand, every talk I saw at the time was from, uh, an amazing woman <laugh>, which I haven't seen before. Uh, so I came across charity majors again, Christine Y our other founder, and then Liz Jones, who's our principal developer advocate. And that really sealed the deal for me as far as wanting to work here. >>Yeah. Honeycomb is interesting. This is a female founded company. You're two leaders. You mentioned that you like the technology, but you were also attracted because you saw females in the leadership position. Talk to me a little bit about what that's like working for a female led organization at honeycomb. >>Yeah. You know, historically, um, we have tried not to over index on that because there was this, uh, maybe fear awareness of, um, it taking away from our legitimacy as an engineering organization, from our success as a company. Um, but I'm seeing that, uh, rhetoric shift recently because we believe that with great responsibility, uh, with great power comes great responsibility, and we're trying to be more intentional as far as using that attribute of our company. Um, so I would say that for me, it was, um, a choice between a few offers, right. And that was a selling point for sure, because again, I've never experienced it and I've really seen how much they walk that walk. Um, even me being here and me moving into management, I think were both, um, ways in which they really put a lot of trust and support in me. And so, um, I it's been a great ride. >>Excellent. Sounds like it. Before we bring Danielle in to talk about the partnership. I do wanna have you there talk to the audience a little bit about honeycomb, what technology it's delivering and what are its differentiators. >>Yeah, absolutely. Um, so honeycomb is an observability tool, uh, that enables engineers to answer questions about the code that runs in production. And, um, we work with a number of various customers. Some of them are Vanguards, slack. Hello, fresh, just to name a couple, if you're not familiar with observability tooling, it's akin to traditional application performance monitoring, but we believe that observability is succeeding APM because, uh, APM tools were built at the time of monoliths and they just weren't designed to help us answer questions about complex distributed systems that we work with today, where things can go wrong anywhere in that chain. And you can't predict what you're gonna need to ask ahead of time. So some of the ways that we are different is our ability to store and query really rich data, which we believe is the key to understanding those complex systems. >>What I mean by rich data is, um, something that has a lot of attributes. So for example, when an error happens, knowing who it happened to, which user ID, which, um, I don't know, region, they were in, um, what, what, what they were doing at the time and what was happening at the rest of your system. And our ingest engine is really fast. You can do it in as little as three seconds and we call data like this. I said, kind of rich data, contextual data. We refer it as having high ality and high dimensionality, which are big words. But at the end of the day, what that means is we can store and we can query the data. We can do it really fast. And to give you an example of how that looks for our customers, let's say you have a developer team who are using comb to understand and observe their system. >>And they get a report that a user is experiencing a slowdown or something's wrong. They can go into comb and figure out that this only happens to users who are using a particular language pack with their app. And they operated their app last week, that it only happens when they are trying to upload a file. And so it's this level of granularity and being able to zoom in and out, um, under your data that allows you to understand what's happening, especially when you have an incident going on, right. Or your really important high profile customer is telling you that something's wrong. And we can do that. Even if everything else in your other tools looks fine, right? All of your dashboards are okay. You're not actually getting paged on it, but your customers are telling you that something's wrong. Uh, and we believe that's where we shine in helping you there. >>Excellent. It sounds like that's where you really shine that real time visibility is so critical these days. Danielle, Danielle, wanna bring you into the conversation. Talk to us a little bit about the honeycomb partnership from the AWS lens. >>Yeah. So excuse me, observability is obviously a very important, uh, segment in the cloud space, very important to AWS, um, because a lot of all of our customers, uh, as they build their systems distributed, they need to be able to see where, where things are happening in the complex systems that they're building. And so honeycomb is a, is an advanced technology partner. Um, they've been working with us for quite some time and they have a, uh, their solution is listed on the marketplace. Um, definitely something that we see a lot of demand with our customers and they have many integrations, uh, which, you know, we've seen is key to success. Um, being able to work seamlessly with the rest of the services inside of the AWS platform. And I know that they've done some, some great things with people who are trying to develop games on top of AWS, uh, things in that area as well. And so, uh, very important partner in the observa observability market that we have >>Back to you, let's kind of unpack the partnership, the significance that honeycomb ha is getting from being partners with an organization as potent and pivotal as AWS. >>Yeah, absolutely. Um, I know this predates me to some extent, but I know for a long time, AWS and honeycomb has really pushed the envelope together. And, um, I think it's a beneficial relationship for both ends. There's kind of two ways of looking at it. On the one side, there is our own infrastructure. So honeycomb runs on AWS and actually one of our critical workloads that supports that fast query engine that I mentioned uses Lambda. And it does so in a pretty Orthodox way. So we've had a longstanding conversation with the AWS team as far as drawing outside those lines and kind of figuring out how to use this technology in a way that works for us and hopefully will work for other customers of theirs as well. Um, that also allows us to ask for early access for certain features when they become available. >>And then that way we can be sort of the Guinea pigs and try things out, um, in a way that migrates our system and optimizes our own performance, but also allows again, other customers of AWS to follow in that path. And then the other side of that partnership is really supporting our customers who are both honeycomb users and AWS users, because it's, as you imagine, quite a big overlap, and there are certain ways in which we can allow our customers to more easily get their data from AWS to honeycomb. So for example, last year we built a tool, um, based on the new Lambda extension capability that allowed our users who run their applications in Lambdas to get that telemetry data out of their applications and into honeycomb. And it man was win, win. >>Excellent. So I'm hearing a lot of synergies from a technology perspective, you're sticking with you, and then Danielle will bring you in, let's talk about how honeycomb supports D and I across its organization. And how is that synergistic with AWS's approach? Yeah, >>Yeah, absolutely. So I sort of alluded to that hesitancy to over index on the women led aspect of ourselves. Um, but again, a lot of things are shifting, we're growing a lot. And so we are recognizing that we need to be more intentional with our DEI initiatives, and we also notice that we can do better and we should do better. And to that, and we're doing a few things differently, um, that are pretty recent initiatives. We are partnering with organizations that help us target specific communities that are underrepresented in tech. Um, some examples would be after tech hu Latinas in tech among, um, a number of others. And another initiative is DEI head start. That's something that is an internal, um, practice that we started that includes reaching out to underrepresented applicants before any new job for honeycomb becomes live. So before we posted to LinkedIn, before it's even live on our job speech, and the idea there is to kind of balance our pipeline of applicants, which the hope is will lead to more diverse hires in the long term. >>That's a great focus there. Danielle, I know we've talked about this before, but for the audience, in terms of the context of the honeycomb partnership, the focus at AWS for D E and I is really significant, unpack that a little bit for us. >>Well, let me just bring it back to just how we think about it, um, with the companies that we work with, but also in, in terms of, you know, what we want to be able to do, excuse me, it's very important for us to, you know, build products that reflect, uh, the customers that we have. And I think, you know, working with, uh, a company like honeycomb that is looking to differentiate in a space, um, by, by bringing in, you know, the experiences of many different types of people I genuinely believe. And I'm sure Vera also believes that by having those diverse perspectives, that we're able to then build better products for our customers. Um, and you know, it's one of, one of our leadership principles, uh, is, is rooted in this. I write a lot, it asks for us to seek out diverse perspectives. Uh, and you can't really do that if everybody kind of looks the same and thinks the same and has the same background. So I think that is where our de and I, um, you know, I thought process is rooted and, you know, companies like honeycomb that give customers choice and differentiate and help them, um, to do what they need to do in their unique, um, environments is super important. So >>The, the importance of thought diversity cannot be underscored enough. It's something that is, can be pivotal to organizations. And it's very nice to hear that that's so fundamental to both companies, Barry, I wanna go back to you for a second. You, I think you mentioned this, the DEI head start program, that's an internal program at honeycomb. Can you shed a little bit of light on that? >>Yeah, that's right. And I actually am in the process of hiring a first engineer for my team. So I'm learning a lot of these things firsthand, um, and how it works is we try to make sure to pre-load our pipeline of applicants for any new job opening we have with diverse candidates to the best of our abilities, and that can involve partnering with the organizations that I mentioned or reaching out to our internal network, um, and make sure that we give those applicants a head start, so to speak. >>Excellent. I like that. Danielle, before we close, I wanna get a little bit of, of your background. We've got various background in tag, she's celebrating her 10th anniversary. Give me a, a short kind of description of the journey that you've navigated through being a female in technology. >>Yeah, thanks so much. I really appreciate, uh, being able to share this. So I started as a software engineer, uh, back actually in the late nineties, uh, during the, the first.com bubble and, uh, have, have spent quite a long time actually as an individual contributor, um, probably working in software engineering teams up through 2014 at a minimum until I joined AWS, uh, as a customer facing solutions architect. Um, I do think spending a lot of time, hands on definitely helped me with some of the imposter syndrome, um, issues that folks suffer from not to say I don't at all, but it, it certainly helped with that. And I've been leading teams at AWS since 2015. Um, so it's really been a great ride. Um, and like I said, I'm very happy to see all of our engineering teams change, uh, as far as their composition. And I'm, I'm grateful to be part of it. >>It's pretty great to be able to witness that composition change for the better last question for each of you. And we're almost out of time and Danielle, I'm gonna stick with you. What's your advice, your recommendations for women who either are thinking about getting into tech or those who may be in tech, maybe they're in individual positions and they're not sure if they should apply for that senior leadership position. What do you advise them to do? >>I mean, definitely for the individual contributors, tech tech is a great career, uh, direction, um, and you will always be able to find women like you, you have to maybe just work a little bit harder, uh, to join, have community, uh, in that. But then as a leader, um, representation is very important and we can bring more women into tech by having more leaders. So that's my, you just have to take the lead, >>Take the lead, love that there. Same question for you. What's your advice and recommendations for those maybe future female leaders in tech? >>Yeah, absolutely. Um, Danielle mentioned imposter syndrome and I think we all struggle with it from time to time, no matter how many years it's been. And I think for me, for me, the advice would be if you're starting out, don't be afraid to ask, uh, questions and don't be afraid to kind of show a little bit of ignorance because we've all been there. And I think it's on all of us to remember what it's like to not know how things work. And on the flip side of that, if you are a more senior IC or, uh, in a leadership role, also being able to model just saying, I don't know how this works and going and figuring out answers together because that was a really powerful shift for me early in my career is just to feel like I can say that I don't know something. >>I totally agree. I've been in that same situation where just ask the question because you I'm guaranteed, there's a million outta people in the room that probably has the, have the same question and because of imposter syndrome, don't wanna admit, I don't understand that. Can we back up, but I agree with you. I think that is, um, one of the best things. Raise your hand, ask a question, ladies. Thank you so much for joining me talking about honeycomb and AWS, what you're doing together from a technology perspective and the focus efforts that each company has on D E and I, we appreciate your insights. Thank you so much for having us great talking to you. My pleasure, likewise for my guests, I'm Lisa Martin. You're watching the AWS partner showcase women in check. Welcome to the AWS partner showcase I'm Lisa Martin, your host. This is season one, episode three, and this is a great episode that focuses on women in tech. I'm pleased to be joined by Danielle Shaw, the ISV PSA director at AWS, and the sponsor of this fantastic program. Danielle, it's great to see you and talk about such an important topic. >>Yes. And I will tell you, all of these interviews have just been a blast for me to do. And I feel like there has been a lot of gold that we can glean from all of the, um, stories that we heard on these interviews and good advice that I myself would not have necessarily thought of. So >>I agree. And we're gonna get to set, cuz advice is one of the, the main things that our audience is gonna hear. We have Hillary Ashton, you'll see from TETA there, Reynolds joins us from honeycomb, Stephanie Curry from NetApp and Sue Paris from Jefferson Frank. And the topics that we dig into are first and foremost, diversity equity and inclusion. That is a topic that is incredibly important to every organization. And some of the things Danielle that our audiences shared were really interesting to me. One of the things that I saw from a thematic perspective over and over was that like D Reynolds was talking about the importance of companies and hiring managers and how they need to be intentional with de and I initiatives. And that intention was a, a, a common thing that we heard. I'm curious what your thoughts are about that, that we heard about being intentional working intentionally to deliver a more holistic pool of candidates where de I is concerned. What are your, what were some of the things that stuck out to you? >>Absolutely. I think each one of us is working inside of organizations where in the last, you know, five to 10 years, there's been a, you know, a strong push in this direction, mostly because we've really seen, um, first and foremost, by being intentional, that you can change the, uh, the way your organization looks. Um, but also just that, you know, without being intentional, um, there was just a lot of, you know, outcomes and situations that maybe weren't great for, um, you know, a healthy, um, and productive environment, uh, working environment. And so, you know, a lot of these companies have made a big investments and put forth big initiatives that I think all of us are involved in. And so we're really excited to get out here and talk about it and talk about, especially as these are all partnerships that we have, how, you know, these align with our values. So >>Yeah, that, that value alignment mm-hmm <affirmative> that you bring up is another thing that we heard consistently with each of the partners, there's a cultural alignment, there's a customer obsession alignment that they have with AWS. There's a D E and I alignment that they have. And I, I think everybody also kind of agreed Stephanie Curry talked about, you know, it's really important, um, for diversity on it, on, on impacting performance, highly performant teams are teams that are more diverse. I think we heard that kind of echoed throughout the women that we talked to in >>This. Absolutely. And I absolutely, and I definitely even feel that, uh, with their studies out there that tell you that you make better products, if you have all of the right input and you're getting all many different perspectives, but not just that, but I can, I can personally see it in the performing teams, not just my team, but also, you know, the teams that I work alongside. Um, arguably some of the other business folks have done a really great job of bringing more women into their organization, bringing more underrepresented minorities. Tech is a little bit behind, but we're trying really hard to bring that forward as well to in technical roles. Um, but you can just see the difference in the outcomes. Uh, at least I personally can just in the adjacent teams of mine. >>That's awesome. We talked also quite a bit during this episode about attracting women and underrepresented, um, groups and retaining them. That retention piece is really key. What were some of the things that stuck out to you that, um, you know, some of the guests talked about in terms of retention? >>Yeah. I think especially, uh, speaking with Hillary and hearing how, uh, Teradata is thinking about different ways to make hybrid work work for everybody. I think that is definitely when I talk to women interested in joining AWS, oftentimes that might be one of the first, uh, concerns that they have. Like, am I going to be able to, you know, go pick my kid up at four o'clock at the bus, or am I going to be able to, you know, be at my kids' conf you know, conference or even just, you know, have enough work life balance that I can, um, you know, do the things that I wanna do outside of work, uh, beyond children and family. So these are all very important, um, and questions that especially women come and ask, but also, um, you know, it kind of is a, is a bellwether for, is this gonna be a company that allows me to bring my whole self to work? And then I'm also gonna be able to have that balance that I need need. So I think that was something that is, uh, changing a lot. And many people are thinking about work a lot differently. >>Absolutely. The pandemic not only changed how we think about work, you know, initially it was, do I work from home or do I live at work? And that was legitimately a challenge that all of us faced for a long time period, but we're seeing the hybrid model. We're seeing more companies be open to embracing that and allowing people to have more of that balance, which at the end of the day, it's so much better for product development for the customers, as you talked about there's, it's a win-win. >>Absolutely. And, you know, definitely the first few months of it was very hard to find that separation to be able to put up boundaries. Um, but I think at least I personally have been able to find the way to do it. And I hope that, you know, everyone is getting that space to be able to put those boundaries up to effectively have a harmonious, you know, work life where you can still be at home most of the time, but also, um, you know, have that cutoff point of the day or at least have that separate space that you can feel that you're able to separate the two. >>Yeah, absolutely. And a lot of that from a work life balance perspective leads into one of the next topics that we covered in detail with, and that's mentors and sponsors the differences between them recommendations from, uh, the women on the panel about how to combat imposter syndrome, but also how to leverage mentors and sponsors throughout your career. One of the things that, that Hillary said that I thought was fantastic, advice were mentors and sponsors are concerned is, is be selective in picking your bosses. We often see people, especially younger folks, not necessarily younger folks. I shouldn't say that that are attracted to a company it's brand maybe, and think more about that than they do the boss or bosses that can help guide them along the way. But I thought that was really poignant advice that Hillary provided something that I'm gonna take into consideration myself. >>Yeah. And I honestly hadn't thought about that, but as I reflect through my own career, I can see how I've had particular managers who have had a major impact on helping me, um, with my career. But, you know, if you don't have the ability to do that, or maybe that's not a luxury that you have, I think even if you're able to, you know, find a mentor for a period of time or, um, you know, just, just enable for you to be able to get from say a point a to point B just for a temporary period. Um, just so you can grow into your next role, have a, have a particular outcome that you wanna drive, have a particular goal in mind find that person who's been there and done that and can really help you get through. If you don't have the luxury of picking your manager mentor, who can help you get to the next step. >>Exactly. That, that I thought that advice was brilliant and something that I hadn't really considered either. We also talked with several of the women about imposter syndrome. You know, that's something that everybody, I think, regardless of gender of your background, everybody feels that at some point. So I think one of the nice things that we do in this episode is sort of identify, yes, imposter syndrome is real. This is, this is how it happened to me. This is I navigated around or got over it. I think there's some great advice there for the audience to glean as well about how to dial down the imposter syndrome that they might be feeling. >>Absolutely. And I think the key there is just acknowledging it. Um, but also just hearing all the different techniques on, on how folks have dealt with it because everybody does, um, you know, even some of the smartest, most confident men I've, I've met in, uh, industry still talk to me about how they have it and I'm shocked by it oftentimes, but, um, it is very common and hopefully we, we talk about some good techniques to, to deal with that. >>I think we do, you know, one of the things that when we were asking the, our audience, our guests about advice, what would they tell their younger selves? What would they tell young women or underrepresented groups in terms of becoming interested in stem and in tech and everybody sort of agreed on me, don't be afraid to raise your hand and ask questions. Um, show vulnerabilities, not just as the employee, but even from a leadership perspective, show that as a leader, I, I don't have all the answers. There are questions that I have. I think that goes a long way to reducing the imposter syndrome that most of us have faced at some point in our lives. And that's just, don't be afraid to ask questions. You never know, oh, how can people have the same question sitting in the room? >>Well, and also, you know, for folks who've been in industry for 20, 25 years, I think we can just say that, you know, it's a, it's a marathon, it's not a sprint and you're always going to, um, have new things to learn and you can spend, you know, back to, we talked about the zing and zagging through careers, um, where, you know, we'll have different experiences. Um, all of that kind of comes through just, you know, being curious and wanting to continue to learn. So yes, asking questions and being vulnerable and being able to say, I don't know all the answers, but I wanna learn is a key thing, uh, especially culturally at AWS, but I'm sure with all of these companies as well, >>Definitely I think it sounded like it was really ingrained in their culture. And another thing too, that we also talked about is the word, no, doesn't always mean a dead end. It can often mean not right now or may, maybe this isn't the right opportunity at this time. I think that's another important thing that the audience is gonna learn is that, you know, failure is not necessarily a bad F word. If you turn it into opportunity, no isn't necessarily the end of the road. It can be an opener to a different door. And I, I thought that was a really positive message that our guests, um, had to share with the, the audience. >>Yeah, totally. I can, I can say I had a, a mentor of mine, um, a very, uh, strong woman who told me, you know, your career is going to have lots of ebbs and flows and that's natural. And you know that when you say that, not right now, um, that's a perfect example of maybe there's an ebb where it might not be the right time for you now, but something to consider in the future. But also don't be afraid to say yes, when you can. <laugh> >>Exactly. Danielle, it's been a pleasure filming this episode with you and the great female leaders that we have on. I'm excited for the audience to be able to learn from Hillary Vera, Stephanie Sue, and you so much valuable content in here. We hope you enjoy this partner showcase season one, episode three, Danielle, thanks so much for helping >>Us with it's been a blast. I really appreciate it >>All audience. We wanna enjoy this. Enjoy the episode.

(bright music) >> Welcome to the AWS Partner Showcase. I'm Lisa Martin, your host. This is season one episode three and this is a great episode that focuses on women in tech. I'm pleased to be joined by Danielle Greshock, the ISV PSA director at AWS, and a sponsor of this fantastic program. Danielle, it's great to see you and talk about such an important topic. >> Yes, and I will tell you all of these interviews have just been a blast for me to do and I feel like there has been a lot of gold that we can glean from all of the stories that we heard on these interviews and good advice that I myself would not have necessarily thought of. >> I agree, and we're going to get to (indistinct) 'cause advice is one of the the main things that our audience is going to hear. We have Hillary Ashton, you'll see from Teradata. Vera Reynolds joins us from Honeycomb. Stephanie Curry from NetApp. And Sue Persichetti from Jefferson Frank and the topics that we dig into are, first and foremost, diversity equity and inclusion, that is a topic that is incredibly important to every organization. And some of the things, Danielle, that our audiences shared were really interesting to me. One of the things that I saw, from a thematic perspective, over and over, was that, like Vera Reynolds was talking about, the importance of companies and hiring managers and how they need to be intentional with DE&I initiatives and that intention was a common theme that we heard. I'm curious what your thoughts are about that, that we heard about being intentional, working intentionally to deliver a more holistic pool of candidates where DE&I is concerned. What were some of the things that stuck out to you? >> Absolutely, I think each one of us is working inside of organizations where, in the last five to 10 years, there's been a strong push in this direction, mostly because we've really seen, first and foremost by being intentional, that you can change the way your organization looks. But also just that without being intentional there was just a lot of outcomes and situations that maybe weren't great for a healthy and productive environment, working environment. And so a lot of these companies have made big investments and put forth big initiatives that I think all of us are involved in and so we're really excited to get out here and talk about it and talk about, especially as these are all partnerships that we have, how these align with our values. >> Yeah, that value alignment that you bring up is another theme that we heard consistently with each of the partners. There's a cultural alignment. There's a customer obsession alignment that they have with AWS. There's a DE&I alignment that they have and I think everybody also kind of agreed, Stephanie Curry talked about, it's really important for diversity on impacting performance, highly performant teams are teams that are more diverse. I think we heard that kind of echoed throughout the women that we talked to in this episode. >> Absolutely, and I definitely even feel that there are studies out there that tell you that you make better products if you have all of the right input and you're getting many different perspectives. But not just that, I can personally see it in the performing teams, not just my team, but also the teams that I work alongside. Arguably some of the other business folks have done a really great job of bringing more women into their organization, bringing more underrepresented minorities, tech is a little bit behind but we're trying really hard to bring that forward as well in technical roles. But you can just see the difference in the outcomes. At least I personally can, just in the adjacent teams of mine. >> That's awesome, we talked also quite a bit during this episode about attracting women and underrepresented groups and retaining them. That retention piece is really key. What were some of the things that stuck out to you that some of the guests talked about in terms of retention? >> Yeah, I think, especially speaking with Hillary and hearing how Teradata is thinking about different ways to make hybrid work work for everybody, I think that is definitely, when I talk to women interested in joining AWS, oftentimes that might be one of the first concerns that they have. Like, am I going to be able to go pick my kid up at four o'clock at the bus? Or, am I going to be able to be at my kid's conference? Or even just have enough work life balance that I can do the things that I want to do outside of work, beyond children and family. So these are all very important questions that especially women come and ask, but also it kind of is a bellwether for, is this going to be a company that allows me to bring my whole self to work and then I'm also going to be able to have that balance that I need. So I think that was something that is changing a lot and many people are thinking about work a lot differently. >> Absolutely, the pandemic not only changed how we think about work. You know, initially it was, do I work from home or do I live at work, and that was legitimately a challenge that all of us faced for a long time period, but we're seeing the hybrid model, we're seeing more companies be open to embracing that and allowing people to have more of that balance, which, at the end of the day, it's so much better for product development for the customers, as you talked about, it's a win-win. >> Absolutely, and definitely the first few months of it was very hard to find that separation, to be able to put up boundaries, but I think, at least I personally, have been able to find the way to do it and I hope that everyone is getting that space to be able to put those boundaries up, to effectively have a harmonious work life where you can still be at home most of the time, but also have that cutoff point of the day or at least have that separate space that you can feel that you're able to separate the two. >> Yeah absolutely, and a lot of that, from a work life balance perspective, bleeds into one of the next topics that we covered in detail and that's mentors and sponsors, the differences between them, recommendations from the women on the panel about how to combat imposter syndrome, but also how to leverage mentors and sponsors throughout your career. One of the things that Hillary said that I thought was fantastic advice, where mentors and sponsors are concerned, is be selective in picking your bosses. We often see people, especially younger folks, not necessarily younger folks, I shouldn't say that, that are attracted to a company, it's brand maybe, and think more about that than they do the boss or bosses that can help guide them along the way, but I thought that was really poignant advice that Hillary provided, something that I'm going to take into consideration myself. >> Yeah, and I honestly hadn't thought about that but as I reflect through my own career I can see how I've had particular managers who have had a major impact on helping me with my career. But if you don't have the ability to do that or maybe that's not a luxury that you have, I think even if you're able to find a mentor for a period of time or just enable for you to be able to get from, say a point A to point B, just for a temporary period, just so you can grow into your next role. Have a particular outcome that you want to drive. Have a particular goal in mind. Find that person who's been there and done that and they can really help you get through. If you don't have the luxury of picking your manager, at least be able to pick a mentor who can help you get to the next step. >> Exactly, I thought that advice was brilliant and it's something that I hadn't really considered either. We also talked with several of the women about imposter syndrome. You know that's something that everybody, I think regardless of gender, of your background, everybody feels that at some point. So I think one of the nice things that we do in this episode is sort of identify, yes, imposter syndrome is real, this is how it happened to me, this is how I navigated around or got over it. I think there's some great advice there for the audience to glean as well, about how to dial down the imposter syndrome that they might be feeling. >> Absolutely and I think the key there is just acknowledging it but also just hearing all the different techniques on how folks have dealt with it because everybody does. Even some of the smartest, most confident men I've met in industry still talk to me about how they have it and I'm shocked by it oftentimes, but it is very common and hopefully we talk about some good techniques to deal with that. >> I think we do. You know, one of the things that, when we were asking our guests about advice, what would they tell their younger selves, what would they tell young women or underrepresented groups in terms of becoming interested in STEM and in tech, and everybody sort of agreed on the, don't be afraid to raise your hand and ask questions. Show vulnerabilities, not just as the employee, but even from a leadership perspective, show that as a leader. I don't have all the answers. There are questions that I have. I think that goes a long way to reducing the imposter syndrome that most of us have faced at some point in our lives and that's just, don't be afraid to ask questions. You never know how many people have the same question sitting in the room. >> Well and also, for folks who've been in industry for 20, 25 years, I think we can just say that it's a marathon, it's not a sprint, and you're always going to have new things to learn and you can spend, back to we talked about the zigging and zagging through careers where we'll have different experiences, all of that kind of comes through just being curious and wanting to continue to learn. So yes, asking questions and being vulnerable and being able to say, "I don't know all the answers but I want to learn," is a key thing, especially culturally at AWS, but I'm sure with all of these companies as well. >> Definitely I think it sounded like it was really ingrained in their culture. And another thing too that we also talked about is the word no doesn't always mean a dead end. It can often mean, not right now, or maybe this isn't the right opportunity at this time. I think that's another important thing that the audience is going to learn is that failure is not necessarily a bad F word if you turn it into opportunity. No isn't necessarily the end of the road. It can be an opener to a different door and I thought that was a really positive message that our guests had to share with the audience. >> Yeah totally, I can say I had a mentor of mine, a very strong woman who told me, your career is going to have lots of ebbs and flows and that's natural and that when you say that, not right now, that's a perfect example of maybe there's an ebb where it might not be the right time for you now, but something to consider in the future. But also don't be afraid to say yes, when you can. >> Exactly, Danielle, it's been a pleasure filming this episode with you and the great female leaders that we have on. I'm excited for the audience to be able to learn from Hillary, Vera, Stephanie, Sue, and you. So much valuable content in here. We hope you enjoy this Partner Showcase. Season one episode three. Danielle, thank you so much for helping us. >> Thank you. Thank you, it's been a blast. I really appreciate it. >> All right, audience, we want to thank you. Enjoy the episode. (upbeat music)

(bright music) >> Everyone, it's nice to see you. Welcome to the "AWS Partner Showcase". I'm Lisa Martin, your host. This is season one, episode three, and this is a great episode that focuses on women in tech. I'm pleased to be joined by Danielle Greshock, the ISV PSA Director at AWS, and the sponsor of this fantastic program. Danielle, it's great to see you, and talk about such an important topic. >> Yes, and I will tell you all of these interviews have just been a blast for me to do, and I feel like there has been a lot of gold that we can glean from all of the stories that we heard on these interviews and good advice that I myself would not have necessarily thought of. So-- >> I agree, and we're going to get to that. 'Cause advice is one of the main things that our audience is going to hear. We have Hillary Ashton, you'll see from Teradata, Vera Reynolds joins us from Honeycomb, Stephanie Curry from NetApp and Sue Persichetti from Jefferson Frank. And the topics that we dig into are first and foremost, diversity, equity and inclusion. That is a topic that is incredibly important to every organization. And some of the things, Danielle, that our audiences shared were really interesting to me. One of the things that I saw from a thematic perspective over and over was that like Vera Reynolds was talking about the importance of companies and hiring managers and how they need to be intentional with DE&I initiatives. And that intention was a common thing that we heard. I'm curious what your thoughts are about that, that we heard about being intentional, working intentionally to deliver a more holistic pool of candidates where DE&I is concerned. What were some of the things that stuck out to you? >> Absolutely, I think each one of us is working in the inside of organizations where in the last five to 10 years there's been a strong push in this direction. Mostly because we've really seen first and foremost by being intentional, that you can change the way your organization looks. But also just that without being intentional, there was just a lot of outcomes and situations that maybe weren't great for a healthy and productive working environment. And so a lot of these companies have made big investments and put forth big initiatives that I think all of us are involved in. And so we're really excited to get out here and talk about it and talk about, especially as these are all partnerships that we have, how these align with our values. >> Yeah, that value alignment that you bring up is another thing that we heard consistently with each of the partners. There's a cultural alignment, there's a customer obsession alignment that they have with AWS, there's a DE&I alignment that they have. And I think everybody also kind of agreed. Stephanie Curry talked about it's really important for diversity on impacting performance. Highly performing teams are teams that are more diverse. I think we heard that kind of echoed throughout the women that we talked to in this episode. >> Absolutely, and I definitely even feel that there are studies out there that tell you that you make better products if you have all of the right input and you're getting many different perspectives. But not just that, but I can personally see it in the performing teams, not just my team, but also the teams that I work alongside. Arguably some of the other business folks have done a really great job of bringing more women into their organization, bringing more underrepresented minorities. Tech is a little bit behind, but we're trying really hard to bring that forward as well in technical roles. But you can just see the difference in the outcomes. At least I personally can just in the adjacent teams of mine. >> That's awesome. We talked also quite a bit during this episode about attracting women and underrepresented groups and retaining them. That retention piece is really key. What were some of the things that stuck out to you that some of the guests talked about in terms of retention? >> Yeah, I think especially speaking with Hillary and hearing how Teradata is thinking about different ways to make hybrid work work for everybody. I think that is definitely... When I talk to women interested in joining AWS, oftentimes that might be one of the first concerns that they have. Like, am I going to be able to go pick my kid up at four o'clock at the bus? Or am I going to be able to be at my kids' conference, or even just have enough work-life balance that I can do the things that I want to do outside of work beyond children and family. So these are all very important questions that especially women come and ask, but also it kind of is a bellwether for, is this going to be a company that allows me to bring my whole self to work? And then I'm also going to be able to have that balance that I need. So I think that was something that is changing a lot and many people are thinking about work a lot differently. >> Absolutely, the pandemic not only changed how we think about work. Initially it was, do I work from home or do I live at work? And that was legitimately a challenge that all of us faced for a long time period. But we're seeing the hybrid model, we're seeing more companies be open to embracing that and allowing people to have more of that balance which at the end of the day it's so much better for product development for the customers as you talked about, it's a win-win. >> Absolutely. And definitely the first few months of it was very hard to find that separation to be able to put up boundaries. But I think at least I personally have been able to find the way to do it and I hope that everyone is getting that space to be able to put those boundaries up to effectively have a harmonious work life. Where you can still be at home most of the time, but also have that cutoff point of the day or at least have that separate space that you can feel that you're able to separate the two. >> Yeah, absolutely. And a lot of that from a work-life balance perspective leads into one of the next topics that we covered in detail. And that's mentors and sponsors, the differences between them, recommendations from the women on the panel about how to combat imposter syndrome, but also how to leverage mentors and sponsors throughout your career. One of the things that Hillary said that I thought was fantastic advice where mentors and sponsors are concerned is be selective in picking your bosses. We often see people, especially younger folks, not necessarily younger folks, I shouldn't say that, that are attracted to a company, its brand maybe, and think more about that than they do the boss or bosses that can help guide them along the way. But I thought that was really poignant advice that Hillary provided, something that I'm going to take into consideration myself. >> Yeah, and I honestly hadn't thought about that, but as I reflect through my own career, I can see how I've had particular managers who have had a major impact on helping me with my career. But if you don't have the ability to do that or maybe that's not a luxury that you have, I think even if you're able to find a mentor for a period of time or just enable for you to be able to get from say a point A to point B just for a temporary period, just so you can grow into your next role, have a particular outcome that you want to drive, have a particular goal in mind. Find that person who's been there and done that and they can really help you get through if you don't have the luxury of picking your manager, at least be able to pick a mentor who can help you get to the next step. >> Exactly, I thought that advice was brilliant and something that I hadn't really considered either. We also talked with several other women about imposter syndrome. That's something that everybody, I think regardless of gender, of your background, everybody feels that at some point. So I think one of the nice things that we do in this episode is sort of identify, yes, imposter syndrome is real. This is how it happened to me, this is how I navigated around it or got over it. I think there's some great advice there for the audience to glean as well about how to dial down the imposter syndrome that they might be feeling. >> Absolutely. And I think the key there is just acknowledging it, but also just hearing all the different techniques on how folks have dealt with it, because everybody does. Even some of the smartest, most confident men I've met in industry still talk to me about how they have it. And I'm shocked by it oftentimes, but it is very common. And hopefully we talk about some good techniques to deal with that. >> I think we do. One of the things that when we were asking our guests about advice, what would they tell their younger selves, what would they tell young women or underrepresented groups in terms of becoming interested in STEM and in tech. And everybody sort of agreed on the don't be afraid to raise your hand and ask questions. Show vulnerabilities, not just as the employee, but even from a leadership perspective, show that as a leader, I don't have all the answers. There are questions that I have. I think that goes a long way to reducing the imposter syndrome that most of us have faced at some point in our lives. And that's just, don't be afraid to ask questions. You never know how many people have the same question sitting in the room. >> Well, and also for folks who've been in industry for 20, 25 years, I think we can just say that it's a marathon, it's not a sprint, and you're always going to have new things to learn. And you can spend... Back to we talked about the zigging and zagging through careers where we'll have different experiences. All of that kind of comes through just being curious and wanting to continue to learn. So yes, asking questions and being vulnerable and being able to say, I don't know all the answers but I want to learn is a key thing, especially culturally at AWS, but I'm sure with all of these companies as well. >> Definitely I think it sounded like it was really ingrained in their culture. And another thing too that we also talked about is the word, no, doesn't always mean a dead end, it can often mean, not right now or maybe this isn't the right opportunity at this time. I think that's another important thing that the audience is going to learn is that failure is not necessarily a bad F-word if you turn it into opportunity. No isn't necessarily the end of the road. It can be an opener to a different door. And I thought that was a really positive message that our guests had to share with the audience. >> Yeah, totally. I can say I had a mentor of mine, a very strong woman who told me, "Your career is going to have lots of ebbs and flows, and that's natural." And that when you say that, not right now, that's a perfect example of maybe there's an ebb where it might not be the right time for you now, but something to consider in the future. But also don't be afraid to say yes when you can. >> Exactly. Danielle, it's been a pleasure filming this episode with you and the great female leaders that we have on. I'm excited for the audience to be able to learn from Hillary, Vera, Stephanie, Sue and you. So much valuable content in here. We hope you enjoy this partner showcase season one episode three. Danielle, thanks so much for helping us with this. >> Thank you. Thank you, it's been a blast, I really appreciate it. >> All right. Audience, we want to thank you, enjoy the episode. (gentle music)

>> Okay. We're now going to go into the customer panel, and we'd like to welcome Angelo Fausti, who's a software engineer at the Vera C. Rubin Observatory, and Caleb Maclachlan who's senior spacecraft operations software engineer at Loft Orbital. Guys, thanks for joining us. You don't want to miss folks this interview. Caleb, let's start with you. You work for an extremely cool company, you're launching satellites into space. Of course doing that is highly complex and not a cheap endeavor. Tell us about Loft Orbital and what you guys do to attack that problem. >> Yeah, absolutely. And thanks for having me here by the way. So Loft Orbital is a company that's a series B startup now, who, and our mission basically is to provide rapid access to space for all kinds of customers. Historically, if you want to fly something in space, do something in space, it's extremely expensive. You need to book a launch, build a bus, hire a team to operate it, have a big software teams, and then eventually worry about, a bunch like, just a lot of very specialized engineering. And what we're trying to do is change that from a super specialized problem that has an extremely high barrier of access, to a infrastructure problem. So that it's almost as simple as deploying a VM in AWS or GCP is getting your programs, your mission deployed on orbit with access to different sensors, cameras, radios, stuff like that. So, that's kind of our mission and just to give a really brief example of the kind of customer that we can serve. There's a really cool company called Totum Labs, who is working on building IoT cons, an IoT constellation for, internet of things, basically being able to get telemetry from all over the world. They're the first company to demonstrate indoor IoT which means you have this little modem inside a container that container that you track from anywhere in the world as it's going across the ocean. So, and it's really little, and they've been able to stay a small startup that's focused on their product, which is the, that super crazy, complicated, cool radio, while we handle the whole space segment for them, which just, you know, before Loft was really impossible. So that's our mission is providing space infrastructure as a service. We are kind of groundbreaking in this area and we're serving a huge variety of customers with all kinds of different missions, and obviously generating a ton of data in space that we've got to handle. >> Yeah. So amazing Caleb, what you guys do. Now, I know you were lured to the skies very early in your career, but how did you kind of land in this business? >> Yeah, so, I guess just a little bit about me. For some people, they don't necessarily know what they want to do like earlier in their life. For me I was five years old and I knew I want to be in the space industry. So, I started in the Air Force, but have stayed in the space industry my whole career and been a part of, this is the fifth space startup that I've been a part of actually. So, I've kind of started out in satellites, spent some time in working in the launch industry on rockets, then, now I'm here back in satellites and honestly, this is the most exciting of the different space startups that I've been a part of. >> Super interesting. Okay. Angelo, let's talk about the Rubin Observatory. Vera C. Rubin, famous woman scientist, galaxy guru. Now you guys, the Observatory, you're up way up high, you get a good look at the Southern sky. And I know COVID slowed you guys down a bit, but no doubt you continued to code away on the software. I know you're getting close, you got to be super excited, give us the update on the Observatory and your role. >> All right. So, yeah. Rubin is a state of the art observatory that is in construction on a remote mountain in Chile. And, with Rubin we'll conduct the large survey of space and time. We're going to observe the sky with eight meter optical telescope and take 1000 pictures every night with 2.2 Gigapixel camera. And we are going to do that for 10 years, which is the duration of the survey. >> Yeah, amazing project. Now, you earned a doctor of philosophy so you probably spent some time thinking about what's out there, and then you went out to earn a PhD in astronomy and astrophysics. So, this is something that you've been working on for the better part of your career, isn't it? >> Yeah, that's right, about 15 years. I studied physics in college. Then I got a PhD in astronomy. And, I worked for about five years in another project, the Dark Energy Survey before joining Rubin in 2015. >> Yeah, impressive. So it seems like both your organizations are looking at space from two different angles. One thing you guys both have in common of course is software, and you both use InfluxDB as part of your data infrastructure. How did you discover InfluxDB, get into it? How do you use the platform? Maybe Caleb you could start. >> Yeah, absolutely. So, the first company that I extensively used InfluxDB in, was a launch startup called Astra. And we were in the process of designing our first generation rocket there, and testing the engines, pumps, everything that goes into a rocket. And, when I joined the company our data story was not very mature. We were collecting a bunch of data in LabVIEW and engineers were taking that over to MATLAB to process it. And at first, there, you know, that's the way that a lot of engineers and scientists are used to working. And at first that was, like people weren't entirely sure that that was, that needed to change. But, it's, something, the nice thing about InfluxDB is that, it's so easy to deploy. So as, our software engineering team was able to get it deployed and, up and running very quickly and then quickly also backport all of the data that we collected this far into Influx. And, what was amazing to see and is kind of the super cool moment with Influx is, when we hooked that up to Grafana, Grafana as the visualization platform we used with Influx, 'cause it works really well with it. There was like this aha moment of our engineers who are used to this post process kind of method for dealing with their data, where they could just almost instantly easily discover data that they hadn't been able to see before, and take the manual processes that they would run after a test and just throw those all in Influx and have live data as tests were coming, and, I saw them implementing like crazy rocket equation type stuff in Influx, and it just was totally game changing for how we tested. >> So Angelo, I was explaining in my open, that you could add a column in a traditional RDBMS and do time series, but with the volume of data that you're talking about in the example that Caleb just gave, you have to have a purpose built time series database. Where did you first learn about InfluxDB? >> Yeah, correct. So, I work with the data management team, and my first project was the record metrics that measured the performance of our software, the software that we used to process the data. So I started implementing that in our relational database. But then I realized that in fact I was dealing with time series data and I should really use a solution built for that. And then I started looking at time series databases and I found InfluxDB, and that was back in 2018. The, another use for InfluxDB that I'm also interested is the visits database. If you think about the observations, we are moving the telescope all the time and pointing to specific directions in the sky and taking pictures every 30 seconds. So that itself is a time series. And every point in that time series, we call a visit. So we want to record the metadata about those visits in InfluxDB. That time series is going to be 10 years long, with about 1000 points every night. It's actually not too much data compared to other problems. It's really just a different time scale. >> The telescope at the Rubin Observatory is like, pun intended, I guess the star of the show. And I believe I read that it's going to be the first of the next gen telescopes to come online. It's got this massive field of view, like three orders of magnitude times the Hubble's widest camera view, which is amazing. Like, that's like 40 moons in an image, amazingly fast as well. What else can you tell us about the telescope? >> This telescope it has to move really fast. And, it also has to carry the primary mirror which is an eight meter piece of glass. It's very heavy. And it has to carry a camera which has about the size of a small car. And this whole structure weighs about 300 tons. For that to work, the telescope needs to be very compact and stiff. And one thing that's amazing about it's design is that, the telescope, this 300 tons structure, it sits on a tiny film of oil, which has the diameter of human hair. And that makes an, almost zero friction interface. In fact, a few people can move this enormous structure with only their hands. As you said, another aspect that makes this telescope unique is the optical design. It's a wide field telescope. So, each image has, in diameter the size of about seven full moons. And, with that, we can map the entire sky in only three days. And of course, during operations everything's controlled by software and it is automatic. There's a very complex piece of software called the Scheduler, which is responsible for moving the telescope, and the camera, which is recording 15 terabytes of data every night. >> And Angelo, all this data lands in InfluxDB, correct? And what are you doing with all that data? >> Yeah, actually not. So we use InfluxDB to record engineering data and metadata about the observations. Like telemetry, events, and commands from the telescope. That's a much smaller data set compared to the images. But it is still challenging because you have some high frequency data that the system needs to keep up, and, we need to store this data and have it around for the lifetime of the project. >> Got it. Thank you. Okay, Caleb, let's bring you back in. Tell us more about the, you got these dishwasher size satellites, kind of using a multi-tenant model, I think it's genius. But tell us about the satellites themselves. >> Yeah, absolutely. So, we have in space some satellites already that as you said, are like dishwasher, mini fridge kind of size. And we're working on a bunch more that are a variety of sizes from shoebox to, I guess, a few times larger than what we have today. And it is, we do shoot to have effectively something like a multi-tenant model where we will buy a bus off the shelf. The bus is what you can kind of think of as the core piece of the satellite, almost like a motherboard or something where it's providing the power, it has the solar panels, it has some radios attached to it. It handles the attitude control, basically steers the spacecraft in orbit, and then we build also in-house, what we call our payload hub which is, has all, any customer payloads attached and our own kind of Edge processing sort of capabilities built into it. And, so we integrate that, we launch it, and those things because they're in lower Earth orbit, they're orbiting the earth every 90 minutes. That's, seven kilometers per second which is several times faster than a speeding bullet. So we have one of the unique challenges of operating spacecraft in lower Earth orbit is that generally you can't talk to them all the time. So, we're managing these things through very brief windows of time, where we get to talk to them through our ground sites, either in Antarctica or in the North pole region. >> Talk more about how you use InfluxDB to make sense of this data through all this tech that you're launching into space. >> We basically, previously we started off when I joined the company, storing all of that as Angelo did in a regular relational database. And we found that it was so slow and the size of our data would balloon over the course of a couple days to the point where we weren't able to even store all of the data that we were getting. So we migrated to InfluxDB to store our time series telemetry from the spacecraft. So, that's things like power level, voltage, currents, counts, whatever metadata we need to monitor about the spacecraft, we now store that in InfluxDB. And that has, now we can actually easily store the entire volume of data for the mission life so far without having to worry about the size bloating to an unmanageable amount, and we can also seamlessly query large chunks of data. Like if I need to see, you know, for example, as an operator, I might want to see how my battery state of charge is evolving over the course of the year, I can have, plot in an Influx that loads that in a fraction of a second for a year's worth of data because it does, intelligent, it can intelligently group the data by assigning time interval. So, it's been extremely powerful for us to access the data. And, as time has gone on, we've gradually migrated more and more of our operating data into Influx. >> Yeah. Let's talk a little bit about, we throw this term around a lot of, you know, data driven, a lot of companies say, "Oh yes, we're data driven." But you guys really are, I mean, you got data at the core. Caleb, what does that mean to you? >> Yeah, so, you know, I think the, and the clearest example of when I saw this be like totally game changing is what I mentioned before at Astra where our engineer's feedback loop went from a lot of kind of slow researching, digging into the data to like an instant, instantaneous almost, seeing the data, making decisions based on it immediately rather than having to wait for some processing. And that's something that I've also seen echoed in my current role. But to give another practical example, as I said, we have a huge amount of data that comes down every orbit and we need to be able to ingest all of that data almost instantaneously and provide it to the operator in near real time, about a second worth of latency is all that's acceptable for us to react to see what is coming down from the spacecraft. And building that pipeline is challenging from a software engineering standpoint. My primary language is Python which isn't necessarily that fast. So what we've done is started, and the goal of being data-driven is publish metrics on individual, how individual pieces of our data processing pipeline are performing into Influx as well. And we do that in production as well as in dev. So we have kind of a production monitoring flow. And what that has done is allow us to make intelligent decisions on our software development roadmap where it makes the most sense for us to focus our development efforts in terms of improving our software efficiency, just because we have that visibility into where the real problems are. And sometimes we've found ourselves before we started doing this, kind of chasing rabbits that weren't necessarily the real root cause of issues that we were seeing. But now that we're being a bit more data driven there, we are being much more effective in where we're spending our resources and our time, which is especially critical to us as we scale from supporting a couple of satellites to supporting many, many satellites at once. >> Yeah, of course is how you reduced those dead ends. Maybe Angelo you could talk about what sort of data-driven means to you and your teams. >> I would say that, having real time visibility to the telemetry data and metrics is crucial for us. We need to make sure that the images that we collect with the telescope have good quality, and, that they are within the specifications to meet our science goals. And so if they are not, we want to know that as soon as possible and then start fixing problems. >> Caleb, what are your sort of event, you know, intervals like? >> So I would say that, as of today on the spacecraft, the event, the level of timing that we deal with probably tops out at about 20 Hertz, 20 measurements per second on things like our gyroscopes. But, the, I think the core point here of the ability to have high precision data is extremely important for these kinds of scientific applications and I'll give an example from when I worked at, on the rockets at Astra. There, our baseline data rate that we would ingest data during a test is 500 Hertz. So 500 samples per second, and in some cases we would actually need to ingest much higher rate data, even up to like 1.5 kilohertz, so extremely, extremely high precision data there where timing really matters a lot. And, you know, I can, one of the really powerful things about Influx is the fact that it can handle this. That's one of the reasons we chose it, because, there's, times when we're looking at the results of a firing where you're zooming in, you know, I talked earlier about how on my current job we often zoom out to look at a year's worth of data. You're zooming in to where your screen is preoccupied by a tiny fraction of a second, and you need to see same thing as Angelo just said, not just the actual telemetry, which is coming in at a high rate, but the events that are coming out of our controllers, so that can be something like, "Hey, I opened this valve at exactly this time," and that goes, we want to have that at, micro, or even nanosecond precision so that we know, okay, we saw a spike in chamber pressure at this exact moment, was that before or after this valve opened? That kind of visibility is critical in these kind of scientific applications, and absolutely game changing to be able to see that in near real time, and with, a really easy way for engineers to be able to visualize this data themselves without having to wait for us software engineers to go build it for them. >> Can the scientists do self-serve or do you have to design and build all the analytics and queries for your scientists? >> Well, I think that's absolutely, from my perspective that's absolutely one of the best things about Influx and what I've seen be game changing is that, generally I'd say anyone can learn to use Influx. And honestly, most of our users might not even know they're using Influx, because, the interface that we expose to them is Grafana, which is a generic graphing, open source graphing library that is very similar to Influx zone Chronograf. >> Sure. >> And what it does is, it provides this almost, it's a very intuitive UI for building your queries. So, you choose a measurement and it shows a dropdown of available measurements. And then you choose the particular fields you want to look at, and again, that's a dropdown. So, it's really easy for our users to discover and there's kind of point and click options for doing math, aggregations. You can even do like perfect kind of predictions all within Grafana, the Grafana user interface, which is really just a wrapper around the APIs and functionality that Influx provides. >> Putting data in the hands of those who have the context, the domain experts is key. Angelo, is it the same situation for you, is it self-serve? >> Yeah, correct. As I mentioned before, we have the astronomers making their own dashboards because they know what exactly what they need to visualize. >> Yeah, I mean, it's all about using the right tool for the job. I think for us, when I joined the company we weren't using InfluxDB and we were dealing with serious issues of the database growing to an incredible size extremely quickly, and being unable to like even querying short periods of data was taking on the order of seconds, which is just not possible for operations. >> Guys, this has been really formative, it's pretty exciting to see how the edge, is mountaintops, lower Earth orbits, I mean space is the ultimate edge, isn't it? I wonder if you could answer two questions to wrap here. You know, what comes next for you guys? And is there something that you're really excited about that you're working on? Caleb maybe you could go first and then Angelo you can bring us home. >> Basically what's next for Loft Orbital is more satellites, a greater push towards infrastructure, and really making, our mission is to make space simple for our customers and for everyone. And we're scaling the company like crazy now, making that happen. It's extremely exciting, an extremely exciting time to be in this company and to be in this industry as a whole. Because there are so many interesting applications out there, so many cool ways of leveraging space that people are taking advantage of, and with companies like SpaceX and the, now rapidly lowering cost of launch it's just a really exciting place to be in. We're launching more satellites, we are scaling up for some constellations, and our ground system has to be improved to match. So, there's a lot of improvements that we're working on to really scale up our control software to be best in class and make it capable of handling such a large workload, so. >> Are you guys hiring? >> We are absolutely hiring, so I would, we have positions all over the company, so, we need software engineers, we need people who do more aerospace specific stuff. So absolutely, I'd encourage anyone to check out the Loft Orbital website, if this is at all interesting. >> All right, Angelo, bring us home. >> Yeah. So what's next for us is really getting this telescope working and collecting data. And when that's happened is going to be just a deluge of data coming out of this camera and handling all that data is going to be really challenging. Yeah, I want to be here for that, I'm looking forward. Like for next year we have like an important milestone, which is our commissioning camera, which is a simplified version of the full camera, it's going to be on sky, and so yeah, most of the system has to be working by then. >> Nice. All right guys, with that we're going to end it. Thank you so much, really fascinating, and thanks to InfluxDB for making this possible, really groundbreaking stuff, enabling value creation at the Edge, in the cloud, and of course, beyond at the space. So, really transformational work that you guys are doing, so congratulations and really appreciate the broader community. I can't wait to see what comes next from having this entire ecosystem. Now, in a moment, I'll be back to wrap up. This is Dave Vellante, and you're watching theCUBE, the leader in high tech enterprise coverage. >> Welcome. Telegraf is a popular open source data collection agent. Telegraf collects data from hundreds of systems like IoT sensors, cloud deployments, and enterprise applications. It's used by everyone from individual developers and hobbyists, to large corporate teams. The Telegraf project has a very welcoming and active Open Source community. Learn how to get involved by visiting the Telegraf GitHub page. Whether you want to contribute code, improve documentation, participate in testing, or just show what you're doing with Telegraf. We'd love to hear what you're building. >> Thanks for watching Moving the World with InfluxDB, made possible by Influx Data. I hope you learned some things and are inspired to look deeper into where time series databases might fit into your environment. If you're dealing with large and or fast data volumes, and you want to scale cost effectively with the highest performance, and you're analyzing metrics and data over time, times series databases just might be a great fit for you. Try InfluxDB out. You can start with a free cloud account by clicking on the link in the resources below. Remember, all these recordings are going to be available on demand of thecube.net and influxdata.com, so check those out. And poke around Influx Data. They are the folks behind InfluxDB, and one of the leaders in the space. We hope you enjoyed the program, this is Dave Vellante for theCUBE, we'll see you soon. (upbeat music)

>>Time series data is any data that's stamped in time in some way that could be every second, every minute, every five minutes, every hour, every nanosecond, whatever it might be. And typically that data comes from sources in the physical world like devices or sensors, temperature, gauges, batteries, any device really, or things in the virtual world could be software, maybe it's software in the cloud or data and containers or microservices or virtual machines. So all of these items, whether in the physical or virtual world, they're generating a lot of time series data. Now time series data has been around for a long time, and there are many examples in our everyday lives. All you gotta do is punch up any stock, ticker and look at its price over time and graphical form. And that's a simple use case that anyone can relate to and you can build timestamps into a traditional relational database. >>You just add a column to capture time and as well, there are examples of log data being dumped into a data store that can be searched and captured and ingested and visualized. Now, the problem with the latter example that I just gave you is that you gotta hunt and Peck and search and extract what you're looking for. And the problem with the former is that traditional general purpose databases they're designed as sort of a Swiss army knife for any workload. And there are a lot of functions that get in the way and make them inefficient for time series analysis, especially at scale. Like when you think about O T and edge scale, where things are happening super fast, ingestion is coming from many different sources and analysis often needs to be done in real time or near real time. And that's where time series databases come in. >>They're purpose built and can much more efficiently support ingesting metrics at scale, and then comparing data points over time, time series databases can write and read at significantly higher speeds and deal with far more data than traditional database methods. And they're more cost effective instead of throwing processing power at the problem. For example, the underlying architecture and algorithms of time series databases can optimize queries and they can reclaim wasted storage space and reuse it. At scale time, series databases are simply a better fit for the job. Welcome to moving the world with influx DB made possible by influx data. My name is Dave Valante and I'll be your host today. Influx data is the company behind InfluxDB. The open source time series database InfluxDB is designed specifically to handle time series data. As I just explained, we have an exciting program for you today, and we're gonna showcase some really interesting use cases. >>First, we'll kick it off in our Palo Alto studios where my colleague, John furrier will interview Evan Kaplan. Who's the CEO of influx data after John and Evan set the table. John's gonna sit down with Brian Gilmore. He's the director of IOT and emerging tech at influx data. And they're gonna dig into where influx data is gaining traction and why adoption is occurring and, and why it's so robust. And they're gonna have tons of examples and double click into the technology. And then we bring it back here to our east coast studios, where I get to talk to two practitioners, doing amazing things in space with satellites and modern telescopes. These use cases will blow your mind. You don't want to miss it. So thanks for being here today. And with that, let's get started. Take it away. Palo Alto. >>Okay. Today we welcome Evan Kaplan, CEO of influx data, the company behind influx DB. Welcome Evan. Thanks for coming on. >>Hey John, thanks for having me >>Great segment here on the influx DB story. What is the story? Take us through the history. Why time series? What's the story >><laugh> so the history history is actually actually pretty interesting. Um, Paul dicks, my partner in this and our founder, um, super passionate about developers and developer experience. And, um, he had worked on wall street building a number of time series kind of platform trading platforms for trading stocks. And from his point of view, it was always what he would call a yak shave, which means you had to do a ton of work just to start doing work, which means you had to write a bunch of extrinsic routines. You had to write a bunch of application handling on existing relational databases in order to come up with something that was optimized for a trading platform or a time series platform. And he sort of, he just developed this real clear point of view is this is not how developers should work. And so in 2013, he went through why Combinator and he built something for, he made his first commit to open source in flu DB at the end of 2013. And, and he basically, you know, from my point of view, he invented modern time series, which is you start with a purpose-built time series platform to do these kind of workloads. And you get all the benefits of having something right outta the box. So a developer can be totally productive right away. >>And how many people in the company what's the history of employees and stuff? >>Yeah, I think we're, I, you know, I always forget the number, but it's something like 230 or 240 people now. Um, the company, I joined the company in 2016 and I love Paul's vision. And I just had a strong conviction about the relationship between time series and IOT. Cuz if you think about it, what sensors do is they speak time, series, pressure, temperature, volume, humidity, light, they're measuring they're instrumenting something over time. And so I thought that would be super relevant over long term and I've not regretted it. >>Oh no. And it's interesting at that time, go back in the history, you know, the role of databases, well, relational database is the one database to rule the world. And then as clouds started coming in, you starting to see more databases, proliferate types of databases and time series in particular is interesting. Cuz real time has become super valuable from an application standpoint, O T which speaks time series means something it's like time matters >>Time. >>Yeah. And sometimes data's not worth it after the time, sometimes it worth it. And then you get the data lake. So you have this whole new evolution. Is this the momentum? What's the momentum, I guess the question is what's the momentum behind >>You mean what's causing us to grow. So >>Yeah, the time series, why is time series >>And the >>Category momentum? What's the bottom line? >>Well, think about it. You think about it from a broad, broad sort of frame, which is where, what everybody's trying to do is build increasingly intelligent systems, whether it's a self-driving car or a robotic system that does what you want to do or a self-healing software system, everybody wants to build increasing intelligent systems. And so in order to build these increasing intelligent systems, you have to instrument the system well, and you have to instrument it over time, better and better. And so you need a tool, a fundamental tool to drive that instrumentation. And that's become clear to everybody that that instrumentation is all based on time. And so what happened, what happened, what happened what's gonna happen? And so you get to these applications like predictive maintenance or smarter systems. And increasingly you want to do that stuff, not just intelligently, but fast in real time. So millisecond response so that when you're driving a self-driving car and the system realizes that you're about to do something, essentially you wanna be able to act in something that looks like real time, all systems want to do that, want to be more intelligent and they want to be more real time. And so we just happen to, you know, we happen to show up at the right time in the evolution of a >>Market. It's interesting near real time. Isn't good enough when you need real time. >><laugh> yeah, it's not, it's not. And it's like, and it's like, everybody wants, even when you don't need it, ironically, you want it. It's like having the feature for, you know, you buy a new television, you want that one feature, even though you're not gonna use it, you decide that your buying criteria real time is a buying criteria >>For, so you, I mean, what you're saying then is near real time is getting closer to real time as possible, as fast as possible. Right. Okay. So talk about the aspect of data, cuz we're hearing a lot of conversations on the cube in particular around how people are implementing and actually getting better. So iterating on data, but you have to know when it happened to get, know how to fix it. So this is a big part of how we're seeing with people saying, Hey, you know, I wanna make my machine learning algorithms better after the fact I wanna learn from the data. Um, how does that, how do you see that evolving? Is that one of the use cases of sensors as people bring data in off the network, getting better with the data knowing when it happened? >>Well, for sure. So, so for sure, what you're saying is, is, is none of this is non-linear, it's all incremental. And so if you take something, you know, just as an easy example, if you take a self-driving car, what you're doing is you're instrumenting that car to understand where it can perform in the real world in real time. And if you do that, if you run the loop, which is I instrumented, I watch what happens, oh, that's wrong? Oh, I have to correct for that. I correct for that in the software. If you do that for a billion times, you get a self-driving car, but every system moves along that evolution. And so you get the dynamic of, you know, of constantly instrumenting watching the system behave and do it. And this and sets up driving car is one thing. But even in the human genome, if you look at some of our customers, you know, people like, you know, people doing solar arrays, people doing power walls, like all of these systems are getting smarter. >>Well, let's get into that. What are the top applications? What are you seeing for your, with in, with influx DB, the time series, what's the sweet spot for the application use case and some customers give some >>Examples. Yeah. So it's, it's pretty easy to understand on one side of the equation that's the physical side is sensors are sensors are getting cheap. Obviously we know that and they're getting the whole physical world is getting instrumented, your home, your car, the factory floor, your wrist, watch your healthcare, you name it. It's getting instrumented in the physical world. We're watching the physical world in real time. And so there are three or four sweet spots for us, but, but they're all on that side. They're all about IOT. So they're think about consumer IOT projects like Google's nest todo, um, particle sensors, um, even delivery engines like rapid who deliver the Instacart of south America, like anywhere there's a physical location do and that's on the consumer side. And then another exciting space is the industrial side factories are changing dramatically over time. Increasingly moving away from proprietary equipment to develop or driven systems that run operational because what, what has to get smarter when you're building, when you're building a factory is systems all have to get smarter. And then, um, lastly, a lot in the renewables sustainability. So a lot, you know, Tesla, lucid, motors, Cola, motors, um, you know, lots to do with electric cars, solar arrays, windmills, arrays, just anything that's gonna get instrumented that where that instrumentation becomes part of what the purpose >>Is. It's interesting. The convergence of physical and digital is happening with the data IOT. You mentioned, you know, you think of IOT, look at the use cases there, it was proprietary OT systems. Now becoming more IP enabled internet protocol and now edge compute, getting smaller, faster, cheaper AI going to the edge. Now you have all kinds of new capabilities that bring that real time and time series opportunity. Are you seeing IOT going to a new level? What was the, what's the IOT where's the IOT dots connecting to because you know, as these two cultures merge yeah. Operations, basically industrial factory car, they gotta get smarter, intelligent edge is a buzzword, but I mean, it has to be more intelligent. Where's the, where's the action in all this. So the >>Action, really, it really at the core, it's at the developer, right? Because you're looking at these things, it's very hard to get an off the shelf system to do the kinds of physical and software interaction. So the actions really happen at the developer. And so what you're seeing is a movement in the world that, that maybe you and I grew up in with it or OT moving increasingly that developer driven capability. And so all of these IOT systems they're bespoke, they don't come out of the box. And so the developer, the architect, the CTO, they define what's my business. What am I trying to do? Am I trying to sequence a human genome and figure out when these genes express theself or am I trying to figure out when the next heart rate monitor's gonna show up on my apple watch, right? What am I trying to do? What's the system I need to build. And so starting with the developers where all of the good stuff happens here, which is different than it used to be, right. Used to be you'd buy an application or a service or a SA thing for, but with this dynamic, with this integration of systems, it's all about bespoke. It's all about building >>Something. So let's get to the developer real quick, real highlight point here is the data. I mean, I could see a developer saying, okay, I need to have an application for the edge IOT edge or car. I mean, we're gonna have, I mean, Tesla's got applications of the car it's right there. I mean, yes, there's the modern application life cycle now. So take us through how this impacts the developer. Does it impact their C I C D pipeline? Is it cloud native? I mean, where does this all, where does this go to? >>Well, so first of all, you're talking about, there was an internal journey that we had to go through as a company, which, which I think is fascinating for anybody who's interested is we went from primarily a monolithic software that was open sourced to building a cloud native platform, which means we had to move from an agile development environment to a C I C D environment. So to a degree that you are moving your service, whether it's, you know, Tesla monitoring your car and updating your power walls, right. Or whether it's a solar company updating the arrays, right. To degree that that service is cloud. Then increasingly remove from an agile development to a C I C D environment, which you're shipping code to production every day. And so it's not just the developers, all the infrastructure to support the developers to run that service and that sort of stuff. I think that's also gonna happen in a big way >>When your customer base that you have now, and as you see, evolving with infl DB, is it that they're gonna be writing more of the application or relying more on others? I mean, obviously there's an open source component here. So when you bring in kind of old way, new way old way was I got a proprietary, a platform running all this O T stuff and I gotta write, here's an application. That's general purpose. Yeah. I have some flexibility, somewhat brittle, maybe not a lot of robustness to it, but it does its job >>A good way to think about this is versus a new way >>Is >>What so yeah, good way to think about this is what, what's the role of the developer slash architect CTO that chain within a large, within an enterprise or a company. And so, um, the way to think about it is I started my career in the aerospace industry <laugh> and so when you look at what Boeing does to assemble a plane, they build very, very few of the parts. Instead, what they do is they assemble, they buy the wings, they buy the engines, they assemble, actually, they don't buy the wings. It's the one thing they buy the, the material for the w they build the wings, cuz there's a lot of tech in the wings and they end up being assemblers smart assemblers of what ends up being a flying airplane, which is pretty big deal even now. And so what, what happens with software people is they have the ability to pull from, you know, the best of the open source world. So they would pull a time series capability from us. Then they would assemble that with, with potentially some ETL logic from somebody else, or they'd assemble it with, um, a Kafka interface to be able to stream the data in. And so they become very good integrators and assemblers, but they become masters of that bespoke application. And I think that's where it goes, cuz you're not writing native code for everything. >>So they're more flexible. They have faster time to market cuz they're assembling way faster and they get to still maintain their core competency. Okay. Their wings in this case, >>They become increasingly not just coders, but designers and developers. They become broadly builders is what we like to think of it. People who start and build stuff by the way, this is not different than the people just up the road Google have been doing for years or the tier one, Amazon building all their own. >>Well, I think one of the things that's interesting is is that this idea of a systems developing a system architecture, I mean systems, uh, uh, systems have consequences when you make changes. So when you have now cloud data center on premise and edge working together, how does that work across the system? You can't have a wing that doesn't work with the other wing kind of thing. >>That's exactly. But that's where the that's where the, you know, that that Boeing or that airplane building analogy comes in for us. We've really been thoughtful about that because IOT it's critical. So our open source edge has the same API as our cloud native stuff that has enterprise on pre edge. So our multiple products have the same API and they have a relationship with each other. They can talk with each other. So the builder builds it once. And so this is where, when you start thinking about the components that people have to use to build these services is that you wanna make sure, at least that base layer, that database layer, that those components talk to each other. >>So I'll have to ask you if I'm the customer. I put my customer hat on. Okay. Hey, I'm dealing with a lot. >>That mean you have a PO for <laugh> >>A big check. I blank check. If you can answer this question only if the tech, if, if you get the question right, I got all this important operation stuff. I got my factory, I got my self-driving cars. This isn't like trivial stuff. This is my business. How should I be thinking about time series? Because now I have to make these architectural decisions, as you mentioned, and it's gonna impact my application development. So huge decision point for your customers. What should I care about the most? So what's in it for me. Why is time series >>Important? Yeah, that's a great question. So chances are, if you've got a business that was, you know, 20 years old or 25 years old, you were already thinking about time series. You probably didn't call it that you built something on a Oracle or you built something on IBM's DB two, right. And you made it work within your system. Right? And so that's what you started building. So it's already out there. There are, you know, there are probably hundreds of millions of time series applications out there today. But as you start to think about this increasing need for real time, and you start to think about increasing intelligence, you think about optimizing those systems over time. I hate the word, but digital transformation. Then you start with time series. It's a foundational base layer for any system that you're gonna build. There's no system I can think of where time series, shouldn't be the foundational base layer. If you just wanna store your data and just leave it there and then maybe look it up every five years. That's fine. That's not time. Series time series is when you're building a smarter, more intelligent, more real time system. And the developers now know that. And so the more they play a role in building these systems, the more obvious it becomes. >>And since I have a PO for you and a big check, yeah. What is, what's the value to me as I, when I implement this, what's the end state, what's it look like when it's up and running? What's the value proposition for me. What's an >>So, so when it's up and running, you're able to handle the queries, the writing of the data, the down sampling of the data, they're transforming it in near real time. So that the other dependencies that a system that gets for adjusting a solar array or trading energy off of a power wall or some sort of human genome, those systems work better. So time series is foundational. It's not like it's, you know, it's not like it's doing every action that's above, but it's foundational to build a really compelling, intelligent system. I think that's what developers and archs are seeing now. >>Bottom line, final word. What's in it for the customer. What's what, what's your, um, what's your statement to the customer? What would you say to someone looking to do something in time series on edge? >>Yeah. So, so it's pretty clear to clear to us that if you're building, if you view yourself as being in the build business of building systems that you want 'em to be increasingly intelligent, self-healing autonomous. You want 'em to operate in real time that you start from time series. But I also wanna say what's in it for us influx what's in it for us is people are doing some amazing stuff. You know, I highlighted some of the energy stuff, some of the human genome, some of the healthcare it's hard not to be proud or feel like, wow. Yeah. Somehow I've been lucky. I've arrived at the right time, in the right place with the right people to be able to deliver on that. That's that's also exciting on our side of the equation. >>Yeah. It's critical infrastructure, critical, critical operations. >>Yeah. >>Yeah. Great stuff, Evan. Thanks for coming on. Appreciate this segment. All right. In a moment, Brian Gilmore director of IOT and emerging technology that influx day will join me. You're watching the cube leader in tech coverage. Thanks for watching >>Time series data from sensors systems and applications is a key source in driving automation and prediction in technologies around the world. But managing the massive amount of timestamp data generated these days is overwhelming, especially at scale. That's why influx data developed influx DB, a time series data platform that collects stores and analyzes data influx DB empowers developers to extract valuable insights and turn them into action by building transformative IOT analytics and cloud native applications, purpose built and optimized to handle the scale and velocity of timestamped data. InfluxDB puts the power in your hands with developer tools that make it easy to get started quickly with less code InfluxDB is more than a database. It's a robust developer platform with integrated tooling. That's written in the languages you love. So you can innovate faster, run in flex DB anywhere you want by choosing the provider and region that best fits your needs across AWS, Microsoft Azure and Google cloud flex DB is fast and automatically scalable. So you can spend time delivering value to customers, not managing clusters, take control of your time series data. So you can focus on the features and functionalities that give your applications a competitive edge. Get started for free with influx DB, visit influx data.com/cloud to learn more. >>Okay. Now we're joined by Brian Gilmore director of IOT and emerging technologies at influx data. Welcome to the show. >>Thank you, John. Great to be here. >>We just spent some time with Evan going through the company and the value proposition, um, with influx DV, what's the momentum, where do you see this coming from? What's the value coming out of this? >>Well, I think it, we're sort of hitting a point where the technology is, is like the adoption of it is becoming mainstream. We're seeing it in all sorts of organizations, everybody from like the most well funded sort of advanced big technology companies to the smaller academics, the startups and the managing of that sort of data that emits from that technology is time series and us being able to give them a, a platform, a tool that's super easy to use, easy to start. And then of course will grow with them is, is been key to us. Sort of, you know, riding along with them is they're successful. >>Evan was mentioning that time series has been on everyone's radar and that's in the OT business for years. Now, you go back since 20 13, 14, even like five years ago that convergence of physical and digital coming together, IP enabled edge. Yeah. Edge has always been kind of hyped up, but why now? Why, why is the edge so hot right now from an adoption standpoint? Is it because it's just evolution, the tech getting better? >>I think it's, it's, it's twofold. I think that, you know, there was, I would think for some people, everybody was so focused on cloud over the last probably 10 years. Mm-hmm <affirmative> that they forgot about the compute that was available at the edge. And I think, you know, those, especially in the OT and on the factory floor who weren't able to take Avan full advantage of cloud through their applications, you know, still needed to be able to leverage that compute at the edge. I think the big thing that we're seeing now, which is interesting is, is that there's like a hybrid nature to all of these applications where there's definitely some data that's generated on the edge. There's definitely done some data that's generated in the cloud. And it's the ability for a developer to sort of like tie those two systems together and work with that data in a very unified uniform way. Um, that's giving them the opportunity to build solutions that, you know, really deliver value to whatever it is they're trying to do, whether it's, you know, the, the out reaches of outer space or whether it's optimizing the factory floor. >>Yeah. I think, I think one of the things you also mentions genome too, dig big data is coming to the real world. And I think I, OT has been kind of like this thing for OT and, and in some use case, but now with the, with the cloud, all companies have an edge strategy now. So yeah, what's the secret sauce because now this is hot, hot product for the whole world and not just industrial, but all businesses. What's the secret sauce. >>Well, I mean, I think part of it is just that the technology is becoming more capable and that's especially on the hardware side, right? I mean, like technology compute is getting smaller and smaller and smaller. And we find that by supporting all the way down to the edge, even to the micro controller layer with our, um, you know, our client libraries and then working hard to make our applications, especially the database as small as possible so that it can be located as close to sort of the point of origin of that data in the edge as possible is, is, is fantastic. Now you can take that. You can run that locally. You can do your local decision making. You can use influx DB as sort of an input to automation control the autonomy that people are trying to drive at the edge. But when you link it up with everything that's in the cloud, that's when you get all of the sort of cloud scale capabilities of parallelized, AI and machine learning and all of that. >>So what's interesting is the open source success has been something that we've talked about a lot in the cube about how people are leveraging that you guys have users in the enterprise users that IOT market mm-hmm <affirmative>, but you got developers now. Yeah. Kind of together brought that up. How do you see that emerging? How do developers engage? What are some of the things you're seeing that developers are really getting into with InfluxDB >>What's? Yeah. Well, I mean, I think there are the developers who are building companies, right? And these are the startups and the folks that we love to work with who are building new, you know, new services, new products, things like that. And, you know, especially on the consumer side of IOT, there's a lot of that, just those developers. But I think we, you gotta pay attention to those enterprise developers as well, right? There are tons of people with the, the title of engineer in, in your regular enterprise organizations. And they're there for systems integration. They're there for, you know, looking at what they would build versus what they would buy. And a lot of them come from, you know, a strong, open source background and they, they know the communities, they know the top platforms in those spaces and, and, you know, they're excited to be able to adopt and use, you know, to optimize inside the business as compared to just building a brand new one. >>You know, it's interesting too, when Evan and I were talking about open source versus closed OT systems, mm-hmm <affirmative> so how do you support the backwards compatibility of older systems while maintaining open dozens of data formats out there? Bunch of standards, protocols, new things are emerging. Everyone wants to have a control plane. Everyone wants to leverage the value of data. How do you guys keep track of it all? What do you guys support? >>Yeah, well, I mean, I think either through direct connection, like we have a product called Telegraph, it's unbelievable. It's open source, it's an edge agent. You can run it as close to the edge as you'd like, it speaks dozens of different protocols in its own, right? A couple of which MQTT B, C U a are very, very, um, applicable to these T use cases. But then we also, because we are sort of not only open source, but open in terms of our ability to collect data, we have a lot of partners who have built really great integrations from their own middleware, into influx DB. These are companies like ke wear and high bite who are really experts in those downstream industrial protocols. I mean, that's a business, not everybody wants to be in. It requires some very specialized, very hard work and a lot of support, um, you know, and so by making those connections and building those ecosystems, we get the best of both worlds. The customers can use the platforms they need up to the point where they would be putting into our database. >>What's some of customer testimonies that they, that share with you. Can you share some anecdotal kind of like, wow, that's the best thing I've ever used. This really changed my business, or this is a great tech that's helped me in these other areas. What are some of the, um, soundbites you hear from customers when they're successful? >>Yeah. I mean, I think it ranges. You've got customers who are, you know, just finally being able to do the monitoring of assets, you know, sort of at the edge in the field, we have a customer who's who's has these tunnel boring machines that go deep into the earth to like drill tunnels for, for, you know, cars and, and, you know, trains and things like that. You know, they are just excited to be able to stick a database onto those tunnel, boring machines, send them into the depths of the earth and know that when they come out, all of that telemetry at a very high frequency has been like safely stored. And then it can just very quickly and instantly connect up to their, you know, centralized database. So like just having that visibility is brand new to them. And that's super important. On the other hand, we have customers who are way far beyond the monitoring use case, where they're actually using the historical records in the time series database to, um, like I think Evan mentioned like forecast things. So for predictive maintenance, being able to pull in the telemetry from the machines, but then also all of that external enrichment data, the metadata, the temperatures, the pressure is who is operating the machine, those types of things, and being able to easily integrate with platforms like Jupyter notebooks or, you know, all of those scientific computing and machine learning libraries to be able to build the models, train the models, and then they can send that information back down to InfluxDB to apply it and detect those anomalies, which >>Are, I think that's gonna be an, an area. I personally think that's a hot area because I think if you look at AI right now, yeah. It's all about training the machine learning albums after the fact. So time series becomes hugely important. Yeah. Cause now you're thinking, okay, the data matters post time. Yeah. First time. And then it gets updated the new time. Yeah. So it's like constant data cleansing data iteration, data programming. We're starting to see this new use case emerge in the data field. >>Yep. Yeah. I mean, I think you agree. Yeah, of course. Yeah. The, the ability to sort of handle those pipelines of data smartly, um, intelligently, and then to be able to do all of the things you need to do with that data in stream, um, before it hits your sort of central repository. And, and we make that really easy for customers like Telegraph, not only does it have sort of the inputs to connect up to all of those protocols and the ability to capture and connect up to the, to the partner data. But also it has a whole bunch of capabilities around being able to process that data, enrich it, reform at it, route it, do whatever you need. So at that point you're basically able to, you're playing your data in exactly the way you would wanna do it. You're routing it to different, you know, destinations and, and it's, it's, it's not something that really has been in the realm of possibility until this point. Yeah. Yeah. >>And when Evan was on it's great. He was a CEO. So he sees the big picture with customers. He was, he kinda put the package together that said, Hey, we got a system. We got customers, people are wanting to leverage our product. What's your PO they're sell. He's selling too as well. So you have that whole CEO perspective, but he brought up this notion that there's multiple personas involved in kind of the influx DB system architect. You got developers and users. Can you talk about that? Reality as customers start to commercialize and operationalize this from a commercial standpoint, you got a relationship to the cloud. Yep. The edge is there. Yep. The edge is getting super important, but cloud brings a lot of scale to the table. So what is the relationship to the cloud? Can you share your thoughts on edge and its relationship to the cloud? >>Yeah. I mean, I think edge, you know, edges, you can think of it really as like the local information, right? So it's, it's generally like compartmentalized to a point of like, you know, a single asset or a single factory align, whatever. Um, but what people do who wanna pro they wanna be able to make the decisions there at the edge locally, um, quickly minus the latency of sort of taking that large volume of data, shipping it to the cloud and doing something with it there. So we allow them to do exactly that. Then what they can do is they can actually downsample that data or they can, you know, detect like the really important metrics or the anomalies. And then they can ship that to a central database in the cloud where they can do all sorts of really interesting things with it. Like you can get that centralized view of all of your global assets. You can start to compare asset to asset, and then you can do those things like we talked about, whereas you can do predictive types of analytics or, you know, larger scale anomaly detections. >>So in this model you have a lot of commercial operations, industrial equipment. Yep. The physical plant, physical business with virtual data cloud all coming together. What's the future for InfluxDB from a tech standpoint. Cause you got open. Yep. There's an ecosystem there. Yep. You have customers who want operational reliability for sure. I mean, so you got organic <laugh> >>Yeah. Yeah. I mean, I think, you know, again, we got iPhones when everybody's waiting for flying cars. Right. So I don't know. We can like absolutely perfectly predict what's coming, but I think there are some givens and I think those givens are gonna be that the world is only gonna become more hybrid. Right. And then, you know, so we are going to have much more widely distributed, you know, situations where you have data being generated in the cloud, you have data gen being generated at the edge and then there's gonna be data generated sort sort of at all points in between like physical locations as well as things that are, that are very virtual. And I think, you know, we are, we're building some technology right now. That's going to allow, um, the concept of a database to be much more fluid and flexible, sort of more aligned with what a file would be like. >>And so being able to move data to the compute for analysis or move the compute to the data for analysis, those are the types of, of solutions that we'll be bringing to the customers sort of over the next little bit. Um, but I also think we have to start thinking about like what happens when the edge is actually off the planet. Right. I mean, we've got customers, you're gonna talk to two of them, uh, in the panel who are actually working with data that comes from like outside the earth, like, you know, either in low earth orbit or you know, all the way sort of on the other side of the universe. Yeah. And, and to be able to process data like that and to do so in a way it's it's we gotta, we gotta build the fundamentals for that right now on the factory floor and in the mines and in the tunnels. Um, so that we'll be ready for that one. >>I think you bring up a good point there because one of the things that's common in the industry right now, people are talking about, this is kind of new thinking is hyper scale's always been built up full stack developers, even the old OT world, Evan was pointing out that they built everything right. And the world's going to more assembly with core competency and IP and also property being the core of their apple. So faster assembly and building, but also integration. You got all this new stuff happening. Yeah. And that's to separate out the data complexity from the app. Yes. So space genome. Yep. Driving cars throws off massive data. >>It >>Does. So is Tesla, uh, is the car the same as the data layer? >>I mean the, yeah, it's, it's certainly a point of origin. I think the thing that we wanna do is we wanna let the developers work on the world, changing problems, the things that they're trying to solve, whether it's, you know, energy or, you know, any of the other health or, you know, other challenges that these teams are, are building against. And we'll worry about that time series data and the underlying data platform so that they don't have to. Right. I mean, I think you talked about it, uh, you know, for them just to be able to adopt the platform quickly, integrate it with their data sources and the other pieces of their applications. It's going to allow them to bring much faster time to market on these products. It's gonna allow them to be more iterative. They're gonna be able to do more sort of testing and things like that. And ultimately it will, it'll accelerate the adoption and the creation of >>Technology. You mentioned earlier in, in our talk about unification of data. Yeah. How about APIs? Cuz developers love APIs in the cloud unifying APIs. How do you view view that? >>Yeah, I mean, we are APIs, that's the product itself. Like everything, people like to think of it as sort of having this nice front end, but the front end is B built on our public APIs. Um, you know, and it, it allows the developer to build all of those hooks for not only data creation, but then data processing, data analytics, and then, you know, sort of data extraction to bring it to other platforms or other applications, microservices, whatever it might be. So, I mean, it is a world of APIs right now and you know, we, we bring a very sort of useful set of them for managing the time series data. These guys are all challenged with. It's >>Interesting. You and I were talking before we came on camera about how, um, data is, feels gonna have this kind of SRE role that DevOps had site reliability engineers, which manages a bunch of servers. There's so much data out there now. Yeah. >>Yeah. It's like reigning data for sure. And I think like that ability to be like one of the best jobs on the planet is gonna be to be able to like, sort of be that data Wrangler to be able to understand like what the data sources are, what the data formats are, how to be able to efficiently move that data from point a to point B and you know, to process it correctly so that the end users of that data aren't doing any of that sort of hard upfront preparation collection storage's >>Work. Yeah. That's data as code. I mean, data engineering is it is becoming a new discipline for sure. And, and the democratization is the benefit. Yeah. To everyone, data science get easier. I mean data science, but they wanna make it easy. Right. <laugh> yeah. They wanna do the analysis, >>Right? Yeah. I mean, I think, you know, it, it's a really good point. I think like we try to give our users as many ways as there could be possible to get data in and get data out. We sort of think about it as meeting them where they are. Right. So like we build, we have the sort of client libraries that allow them to just port to us, you know, directly from the applications and the languages that they're writing, but then they can also pull it out. And at that point nobody's gonna know the users, the end consumers of that data, better than those people who are building those applications. And so they're building these user interfaces, which are making all of that data accessible for, you know, their end users inside their organization. >>Well, Brian, great segment, great insight. Thanks for sharing all, all the complexities and, and IOT that you guys helped take away with the APIs and, and assembly and, and all the system architectures that are changing edge is real cloud is real. Yeah, absolutely. Mainstream enterprises. And you got developer attraction too, so congratulations. >>Yeah. It's >>Great. Well, thank any, any last word you wanna share >>Deal with? No, just, I mean, please, you know, if you're, if you're gonna, if you're gonna check out influx TV, download it, try out the open source contribute if you can. That's a, that's a huge thing. It's part of being the open source community. Um, you know, but definitely just, just use it. I think when once people use it, they try it out. They'll understand very, >>Very quickly. So open source with developers, enterprise and edge coming together all together. You're gonna hear more about that in the next segment, too. Right. Thanks for coming on. Okay. Thanks. When we return, Dave LAN will lead a panel on edge and data influx DB. You're watching the cube, the leader in high tech enterprise coverage. >>Why the startup, we move really fast. We find that in flex DB can move as fast as us. It's just a great group, very collaborative, very interested in manufacturing. And we see a bright future in working with influence. My name is Aaron Seley. I'm the CTO at HBI. Highlight's one of the first companies to focus on manufacturing data and apply the concepts of data ops, treat that as an asset to deliver to the it system, to enable applications like overall equipment effectiveness that can help the factory produce better, smarter, faster time series data. And manufacturing's really important. If you take a piece of equipment, you have the temperature pressure at the moment that you can look at to kind of see the state of what's going on. So without that context and understanding you can't do what manufacturers ultimately want to do, which is predict the future. >>Influx DB represents kind of a new way to storm time series data with some more advanced technology and more importantly, more open technologies. The other thing that influx does really well is once the data's influx, it's very easy to get out, right? They have a modern rest API and other ways to access the data. That would be much more difficult to do integrations with classic historians highlight can serve to model data, aggregate data on the shop floor from a multitude of sources, whether that be P C U a servers, manufacturing execution systems, E R P et cetera, and then push that seamlessly into influx to then be able to run calculations. Manufacturing is changing this industrial 4.0, and what we're seeing is influx being part of that equation. Being used to store data off the unified name space, we recommend InfluxDB all the time to customers that are exploring a new way to share data manufacturing called the unified name space who have open questions around how do I share this new data that's coming through my UNS or my QTT broker? How do I store this and be able to query it over time? And we often point to influx as a solution for that is a great brand. It's a great group of people and it's a great technology. >>Okay. We're now going to go into the customer panel and we'd like to welcome Angelo Fasi. Who's a software engineer at the Vera C Ruben observatory in Caleb McLaughlin whose senior spacecraft operations software engineer at loft orbital guys. Thanks for joining us. You don't wanna miss folks this interview, Caleb, let's start with you. You work for an extremely cool company. You're launching satellites into space. I mean, there, of course doing that is, is highly complex and not a cheap endeavor. Tell us about loft Orbi and what you guys do to attack that problem. >>Yeah, absolutely. And, uh, thanks for having me here by the way. Uh, so loft orbital is a, uh, company. That's a series B startup now, uh, who and our mission basically is to provide, uh, rapid access to space for all kinds of customers. Uh, historically if you want to fly something in space, do something in space, it's extremely expensive. You need to book a launch, build a bus, hire a team to operate it, you know, have a big software teams, uh, and then eventually worry about, you know, a bunch like just a lot of very specialized engineering. And what we're trying to do is change that from a super specialized problem that has an extremely high barrier of access to a infrastructure problem. So that it's almost as simple as, you know, deploying a VM in, uh, AWS or GCP is getting your, uh, programs, your mission deployed on orbit, uh, with access to, you know, different sensors, uh, cameras, radios, stuff like that. >>So that's, that's kind of our mission. And just to give a really brief example of the kind of customer that we can serve. Uh, there's a really cool company called, uh, totem labs who is working on building, uh, IOT cons, an IOT constellation for in of things, basically being able to get telemetry from all over the world. They're the first company to demonstrate indoor T, which means you have this little modem inside a container container that you, that you track from anywhere in the world as it's going across the ocean. Um, so they're, it's really little and they've been able to stay a small startup that's focused on their product, which is the, uh, that super crazy complicated, cool radio while we handle the whole space segment for them, which just, you know, before loft was really impossible. So that's, our mission is, uh, providing space infrastructure as a service. We are kind of groundbreaking in this area and we're serving, you know, a huge variety of customers with all kinds of different missions, um, and obviously generating a ton of data in space, uh, that we've gotta handle. Yeah. >>So amazing Caleb, what you guys do, I, now I know you were lured to the skies very early in your career, but how did you kinda land on this business? >>Yeah, so, you know, I've, I guess just a little bit about me for some people, you know, they don't necessarily know what they wanna do like early in their life. For me, I was five years old and I knew, you know, I want to be in the space industry. So, you know, I started in the air force, but have, uh, stayed in the space industry, my whole career and been a part of, uh, this is the fifth space startup that I've been a part of actually. So, you know, I've, I've, uh, kind of started out in satellites, did spent some time in working in, uh, the launch industry on rockets. Then, uh, now I'm here back in satellites and you know, honestly, this is the most exciting of the difference based startups. That I've been a part of >>Super interesting. Okay. Angelo, let's, let's talk about the Ruben observatory, ver C Ruben, famous woman scientist, you know, galaxy guru. Now you guys the observatory, you're up way up high. You're gonna get a good look at the Southern sky. Now I know COVID slowed you guys down a bit, but no doubt. You continued to code away on the software. I know you're getting close. You gotta be super excited. Give us the update on, on the observatory and your role. >>All right. So yeah, Rubin is a state of the art observatory that, uh, is in construction on a remote mountain in Chile. And, um, with Rubin, we conduct the, uh, large survey of space and time we are going to observe the sky with, uh, eight meter optical telescope and take, uh, a thousand pictures every night with a 3.2 gig up peaks of camera. And we are going to do that for 10 years, which is the duration of the survey. >>Yeah. Amazing project. Now you, you were a doctor of philosophy, so you probably spent some time thinking about what's out there and then you went out to earn a PhD in astronomy, in astrophysics. So this is something that you've been working on for the better part of your career, isn't it? >>Yeah, that's that's right. Uh, about 15 years, um, I studied physics in college, then I, um, got a PhD in astronomy and, uh, I worked for about five years in another project. Um, the dark energy survey before joining rubing in 2015. >>Yeah. Impressive. So it seems like you both, you know, your organizations are looking at space from two different angles. One thing you guys both have in common of course is, is, is software. And you both use InfluxDB as part of your, your data infrastructure. How did you discover influx DB get into it? How do you use the platform? Maybe Caleb, you could start. >>Uh, yeah, absolutely. So the first company that I extensively used, uh, influx DBN was a launch startup called, uh, Astra. And we were in the process of, uh, designing our, you know, our first generation rocket there and testing the engines, pumps, everything that goes into a rocket. Uh, and when I joined the company, our data story was not, uh, very mature. We were collecting a bunch of data in LabVIEW and engineers were taking that over to MATLAB to process it. Um, and at first there, you know, that's the way that a lot of engineers and scientists are used to working. Um, and at first that was, uh, like people weren't entirely sure that that was a, um, that that needed to change, but it's something the nice thing about InfluxDB is that, you know, it's so easy to deploy. So as the, our software engineering team was able to get it deployed and, you know, up and running very quickly and then quickly also backport all of the data that we collected thus far into influx and what, uh, was amazing to see. >>And as kind of the, the super cool moment with influx is, um, when we hooked that up to Grafana Grafana as the visualization platform we used with influx, cuz it works really well with it. Uh, there was like this aha moment of our engineers who are used to this post process kind of method for dealing with their data where they could just almost instantly easily discover data that they hadn't been able to see before and take the manual processes that they would run after a test and just throw those all in influx and have live data as tests were coming. And, you know, I saw them implementing like crazy rocket equation type stuff in influx, and it just was totally game changing for how we tested. >>So Angelo, I was explaining in my open, you know, you could, you could add a column in a traditional RDBMS and do time series, but with the volume of data that you're talking about, and the example of the Caleb just gave you, I mean, you have to have a purpose built time series database, where did you first learn about influx DB? >>Yeah, correct. So I work with the data management team, uh, and my first project was the record metrics that measured the performance of our software, uh, the software that we used to process the data. So I started implementing that in a relational database. Um, but then I realized that in fact, I was dealing with time series data and I should really use a solution built for that. And then I started looking at time series databases and I found influx B. And that was, uh, back in 2018. The another use for influx DB that I'm also interested is the visits database. Um, if you think about the observations we are moving the telescope all the time in pointing to specific directions, uh, in the Skype and taking pictures every 30 seconds. So that itself is a time series. And every point in that time series, uh, we call a visit. So we want to record the metadata about those visits and flex to, uh, that time here is going to be 10 years long, um, with about, uh, 1000 points every night. It's actually not too much data compared to other, other problems. It's, uh, really just a different, uh, time scale. >>The telescope at the Ruben observatory is like pun intended, I guess the star of the show. And I, I believe I read that it's gonna be the first of the next gen telescopes to come online. It's got this massive field of view, like three orders of magnitude times the Hub's widest camera view, which is amazing, right? That's like 40 moons in, in an image amazingly fast as well. What else can you tell us about the telescope? >>Um, this telescope, it has to move really fast and it also has to carry, uh, the primary mirror, which is an eight meter piece of glass. It's very heavy and it has to carry a camera, which has about the size of a small car. And this whole structure weighs about 300 tons for that to work. Uh, the telescope needs to be, uh, very compact and stiff. Uh, and one thing that's amazing about it's design is that the telescope, um, is 300 tons structure. It sits on a tiny film of oil, which has the diameter of, uh, human hair. And that makes an almost zero friction interface. In fact, a few people can move these enormous structure with only their hands. Uh, as you said, uh, another aspect that makes this telescope unique is the optical design. It's a wide field telescope. So each image has, uh, in diameter the size of about seven full moons. And, uh, with that, we can map the entire sky in only, uh, three days. And of course doing operations everything's, uh, controlled by software and it is automatic. Um there's a very complex piece of software, uh, called the scheduler, which is responsible for moving the telescope, um, and the camera, which is, uh, recording 15 terabytes of data every night. >>Hmm. And, and, and Angela, all this data lands in influx DB. Correct. And what are you doing with, with all that data? >>Yeah, actually not. Um, so we are using flex DB to record engineering data and metadata about the observations like telemetry events and commands from the telescope. That's a much smaller data set compared to the images, but it is still challenging because, uh, you, you have some high frequency data, uh, that the system needs to keep up and we need to, to start this data and have it around for the lifetime of the price. Mm, >>Got it. Thank you. Okay, Caleb, let's bring you back in and can tell us more about the, you got these dishwasher size satellites. You're kind of using a multi-tenant model. I think it's genius, but, but tell us about the satellites themselves. >>Yeah, absolutely. So, uh, we have in space, some satellites already that as you said, are like dishwasher, mini fridge kind of size. Um, and we're working on a bunch more that are, you know, a variety of sizes from shoebox to, I guess, a few times larger than what we have today. Uh, and it is, we do shoot to have effectively something like a multi-tenant model where, uh, we will buy a bus off the shelf. The bus is, uh, what you can kind of think of as the core piece of the satellite, almost like a motherboard or something where it's providing the power. It has the solar panels, it has some radios attached to it. Uh, it handles the attitude control, basically steers the spacecraft in orbit. And then we build also in house, what we call our payload hub, which is, has all, any customer payloads attached and our own kind of edge processing sort of capabilities built into it. >>And, uh, so we integrate that. We launch it, uh, and those things, because they're in lower orbit, they're orbiting the earth every 90 minutes. That's, you know, seven kilometers per second, which is several times faster than a speeding bullet. So we've got, we have, uh, one of the unique challenges of operating spacecraft and lower orbit is that generally you can't talk to them all the time. So we're managing these things through very brief windows of time, uh, where we get to talk to them through our ground sites, either in Antarctica or, you know, in the north pole region. >>Talk more about how you use influx DB to make sense of this data through all this tech that you're launching into space. >>We basically previously we started off when I joined the company, storing all of that as Angelo did in a regular relational database. And we found that it was, uh, so slow in the size of our data would balloon over the course of a couple days to the point where we weren't able to even store all of the data that we were getting. Uh, so we migrated to influx DB to store our time series telemetry from the spacecraft. So, you know, that's things like, uh, power level voltage, um, currents counts, whatever, whatever metadata we need to monitor about the spacecraft. We now store that in, uh, in influx DB. Uh, and that has, you know, now we can actually easily store the entire volume of data for the mission life so far without having to worry about, you know, the size bloating to an unmanageable amount. >>And we can also seamlessly query, uh, large chunks of data. Like if I need to see, you know, for example, as an operator, I might wanna see how my, uh, battery state of charge is evolving over the course of the year. I can have a plot and an influx that loads that in a fraction of a second for a year's worth of data, because it does, you know, intelligent, um, I can intelligently group the data by, uh, sliding time interval. Uh, so, you know, it's been extremely powerful for us to access the data and, you know, as time has gone on, we've gradually migrated more and more of our operating data into influx. >>You know, let's, let's talk a little bit, uh, uh, but we throw this term around a lot of, you know, data driven, a lot of companies say, oh, yes, we're data driven, but you guys really are. I mean, you' got data at the core, Caleb, what does that, what does that mean to you? >>Yeah, so, you know, I think the, and the clearest example of when I saw this be like totally game changing is what I mentioned before at Astro where our engineer's feedback loop went from, you know, a lot of kind of slow researching, digging into the data to like an instant instantaneous, almost seeing the data, making decisions based on it immediately, rather than having to wait for some processing. And that's something that I've also seen echoed in my current role. Um, but to give another practical example, uh, as I said, we have a huge amount of data that comes down every orbit, and we need to be able to ingest all of that data almost instantaneously and provide it to the operator. And near real time, you know, about a second worth of latency is all that's acceptable for us to react to, to see what is coming down from the spacecraft and building that pipeline is challenging from a software engineering standpoint. >>Um, our primary language is Python, which isn't necessarily that fast. So what we've done is started, you know, in the, in the goal of being data driven is publish metrics on individual, uh, how individual pieces of our data processing pipeline are performing into influx as well. And we do that in production as well as in dev. Uh, so we have kind of a production monitoring, uh, flow. And what that has done is allow us to make intelligent decisions on our software development roadmap, where it makes the most sense for us to, uh, focus our development efforts in terms of improving our software efficiency. Uh, just because we have that visibility into where the real problems are. Um, it's sometimes we've found ourselves before we started doing this kind of chasing rabbits that weren't necessarily the real root cause of issues that we were seeing. Uh, but now, now that we're being a bit more data driven, there we are being much more effective in where we're spending our resources and our time, which is especially critical to us as we scale to, from supporting a couple satellites, to supporting many, many satellites at >>Once. Yeah. Coach. So you reduced those dead ends, maybe Angela, you could talk about what, what sort of data driven means to, to you and your teams? >>I would say that, um, having, uh, real time visibility, uh, to the telemetry data and, and metrics is, is, is crucial for us. We, we need, we need to make sure that the image that we collect with the telescope, uh, have good quality and, um, that they are within the specifications, uh, to meet our science goals. And so if they are not, uh, we want to know that as soon as possible and then, uh, start fixing problems. >>Caleb, what are your sort of event, you know, intervals like? >>So I would say that, you know, as of today on the spacecraft, the event, the, the level of timing that we deal with probably tops out at about, uh, 20 Hertz, 20 measurements per second on, uh, things like our, uh, gyroscopes, but the, you know, I think the, the core point here of the ability to have high precision data is extremely important for these kinds of scientific applications. And I'll give an example, uh, from when I worked at, on the rocket at Astra there, our baseline data rate that we would ingest data during a test is, uh, 500 Hertz. So 500 samples per second. And in some cases we would actually, uh, need to ingest much higher rate data, even up to like 1.5 kilohertz. So, uh, extremely, extremely high precision, uh, data there where timing really matters a lot. And, uh, you know, I can, one of the really powerful things about influx is the fact that it can handle this. >>That's one of the reasons we chose it, uh, because there's times when we're looking at the results of a firing where you're zooming in, you know, I talked earlier about how on my current job, we often zoom out to look, look at a year's worth of data. You're zooming in to where your screen is preoccupied by a tiny fraction of a second. And you need to see same thing as Angela just said, not just the actual telemetry, which is coming in at a high rate, but the events that are coming out of our controllers. So that can be something like, Hey, I opened this valve at exactly this time and that goes, we wanna have that at, you know, micro or even nanosecond precision so that we know, okay, we saw a spike in chamber pressure at, you know, at this exact moment, was that before or after this valve open, those kind of, uh, that kind of visibility is critical in these kind of scientific, uh, applications and absolutely game changing to be able to see that in, uh, near real time and, uh, with a really easy way for engineers to be able to visualize this data themselves without having to wait for, uh, software engineers to go build it for them. >>Can the scientists do self-serve or are you, do you have to design and build all the analytics and, and queries for your >>Scientists? Well, I think that's, that's absolutely from, from my perspective, that's absolutely one of the best things about influx and what I've seen be game changing is that, uh, generally I'd say anyone can learn to use influx. Um, and honestly, most of our users might not even know they're using influx, um, because what this, the interface that we expose to them is Grafana, which is, um, a generic graphing, uh, open source graphing library that is very similar to influx own chronograph. Sure. And what it does is, uh, let it provides this, uh, almost it's a very intuitive UI for building your queries. So you choose a measurement and it shows a dropdown of available measurements. And then you choose a particular, the particular field you wanna look at. And again, that's a dropdown, so it's really easy for our users to discover. And there's kind of point and click options for doing math aggregations. You can even do like perfect kind of predictions all within Grafana, the Grafana user interface, which is really just a wrapper around the APIs and functionality of the influx provides putting >>Data in the hands of those, you know, who have the context of domain experts is, is key. Angela, is it the same situation for you? Is it self serve? >>Yeah, correct. Uh, as I mentioned before, um, we have the astronomers making their own dashboards because they know what exactly what they, they need to, to visualize. Yeah. I mean, it's all about using the right tool for the job. I think, uh, for us, when I joined the company, we weren't using influx DB and we, we were dealing with serious issues of the database growing to an incredible size extremely quickly, and being unable to like even querying short periods of data was taking on the order of seconds, which is just not possible for operations >>Guys. This has been really formative it's, it's pretty exciting to see how the edge is mountaintops, lower orbits to be space is the ultimate edge. Isn't it. I wonder if you could answer two questions to, to wrap here, you know, what comes next for you guys? Uh, and is there something that you're really excited about that, that you're working on Caleb, maybe you could go first and an Angela, you can bring us home. >>Uh, basically what's next for loft. Orbital is more, more satellites, a greater push towards infrastructure and really making, you know, our mission is to make space simple for our customers and for everyone. And we're scaling the company like crazy now, uh, making that happen, it's extremely exciting and extremely exciting time to be in this company and to be in this industry as a whole, because there are so many interesting applications out there. So many cool ways of leveraging space that, uh, people are taking advantage of. And with, uh, companies like SpaceX and the now rapidly lowering cost, cost of launch, it's just a really exciting place to be. And we're launching more satellites. We are scaling up for some constellations and our ground system has to be improved to match. So there's a lot of, uh, improvements that we're working on to really scale up our control software, to be best in class and, uh, make it capable of handling such a large workload. So >>You guys hiring >><laugh>, we are absolutely hiring. So, uh, I would in we're we need, we have PE positions all over the company. So, uh, we need software engineers. We need people who do more aerospace, specific stuff. So, uh, absolutely. I'd encourage anyone to check out the loft orbital website, if there's, if this is at all interesting. >>All right. Angela, bring us home. >>Yeah. So what's next for us is really, uh, getting this, um, telescope working and collecting data. And when that's happen is going to be just, um, the Lu of data coming out of this camera and handling all, uh, that data is going to be really challenging. Uh, yeah. I wanna wanna be here for that. <laugh> I'm looking forward, uh, like for next year we have like an important milestone, which is our, um, commissioning camera, which is a simplified version of the, of the full camera it's going to be on sky. And so yeah, most of the system has to be working by them. >>Nice. All right, guys, you know, with that, we're gonna end it. Thank you so much, really fascinating, and thanks to influx DB for making this possible, really groundbreaking stuff, enabling value creation at the edge, you know, in the cloud and of course, beyond at the space. So really transformational work that you guys are doing. So congratulations and really appreciate the broader community. I can't wait to see what comes next from having this entire ecosystem. Now, in a moment, I'll be back to wrap up. This is Dave ante, and you're watching the cube, the leader in high tech enterprise coverage. >>Welcome Telegraph is a popular open source data collection. Agent Telegraph collects data from hundreds of systems like IOT sensors, cloud deployments, and enterprise applications. It's used by everyone from individual developers and hobbyists to large corporate teams. The Telegraph project has a very welcoming and active open source community. Learn how to get involved by visiting the Telegraph GitHub page, whether you want to contribute code, improve documentation, participate in testing, or just show what you're doing with Telegraph. We'd love to hear what you're building. >>Thanks for watching. Moving the world with influx DB made possible by influx data. I hope you learn some things and are inspired to look deeper into where time series databases might fit into your environment. If you're dealing with large and or fast data volumes, and you wanna scale cost effectively with the highest performance and you're analyzing metrics and data over time times, series databases just might be a great fit for you. Try InfluxDB out. You can start with a free cloud account by clicking on the link and the resources below. Remember all these recordings are gonna be available on demand of the cube.net and influx data.com. So check those out and poke around influx data. They are the folks behind InfluxDB and one of the leaders in the space, we hope you enjoyed the program. This is Dave Valante for the cube. We'll see you soon.

(upbeat music) >> Okay, we're now going to go into the customer panel. And we'd like to welcome Angelo Fausti, who's software engineer at the Vera C Rubin Observatory, and Caleb Maclachlan, who's senior spacecraft operations software engineer at Loft Orbital. Guys, thanks for joining us. You don't want to miss folks, this interview. Caleb, let's start with you. You work for an extremely cool company. You're launching satellites into space. Cause doing that is highly complex and not a cheap endeavor. Tell us about Loft Orbital and what you guys do to attack that problem? >> Yeah, absolutely. And thanks for having me here, by the way. So Loft Orbital is a company that's a series B startup now. And our mission basically is to provide rapid access to space for all kinds of customers. Historically, if you want to fly something in space, do something in space, it's extremely expensive. You need to book a launch, build a bus, hire a team to operate it, have big software teams, and then eventually worry about a lot of very specialized engineering. And what we're trying to do is, change that from a super specialized problem that has an extremely high barrier of access to a infrastructure problem. So that it's almost as simple as deploying a VM in AWS or GCP, as getting your programs, your mission deployed on orbit, with access to different sensors, cameras, radios, stuff like that. So that's kind of our mission. And just to give a really brief example of the kind of customer that we can serve. There's a really cool company called Totum labs, who is working on building an IoT constellation, for Internet of Things. Basically being able to get telemetry from all over the world. They're the first company to demonstrate indoor IoT, which means you have this little modem inside a container. A container that you track from anywhere on the world as it's going across the ocean. So it's really little. And they've been able to stay small startup that's focused on their product, which is that super crazy, complicated, cool radio, while we handle the whole space segment for them, which just, before Loft was really impossible. So that's our mission is, providing space infrastructure as a service. We are kind of groundbreaking in this area, and we're serving a huge variety of customers with all kinds of different missions, and obviously, generating a ton of data in space that we've got to handle. >> Yeah, so amazing, Caleb, what you guys do. I know you were lured to the skies very early in your career, but how did you kind of land in this business? >> Yeah, so I guess just a little bit about me. For some people, they don't necessarily know what they want to do, early in their life. For me, I was five years old and I knew, I want to be in the space industry. So I started in the Air Force, but have stayed in the space industry my whole career and been a part of, this is the fifth space startup that I've been a part of, actually. So I've kind of started out in satellites, did spend some time in working in the launch industry on rockets. Now I'm here back in satellites. And honestly, this is the most exciting of the different space startups that I've been a part of. So, always been passionate about space and basically writing software for operating in space for basically extending how we write software into orbit. >> Super interesting. Okay, Angelo. Let's talk about the Rubin Observatory Vera C. Rubin, famous woman scientists, Galaxy guru, Now you guys, the observatory are up, way up high, you're going to get a good look at the southern sky. I know COVID slowed you guys down a bit. But no doubt you continue to code away on the software. I know you're getting close. You got to be super excited. Give us the update on the observatory and your role. >> All right. So yeah, Rubin is state of the art observatory that is in construction on a remote mountain in Chile. And with Rubin we'll conduct the large survey of space and time. We are going to observe the sky with eight meter optical telescope and take 1000 pictures every night with 3.2 gigapixel camera. And we're going to do that for 10 years, which is the duration of the survey. The goal is to produce an unprecedented data set. Which is going to be about .5 exabytes of image data. And from these images will detect and measure the properties of billions of astronomical objects. We are also building a science platform that's hosted on Google Cloud, so that the scientists and the public can explore this data to make discoveries. >> Yeah, amazing project. Now, you aren't a Doctor of Philosophy. So you probably spent some time thinking about what's out there. And then you went on to earn a PhD in astronomy and astrophysics. So this is something that you've been working on for the better part of your career, isn't it? >> Yeah, that's right. About 15 years. I studied physics in college, then I got a PhD in astronomy. And I worked for about five years in another project, the Dark Energy survey before joining Rubin in 2015. >> Yeah, impressive. So it seems like both your organizations are looking at space from two different angles. One thing you guys both have in common, of course, is software. And you both use InfluxDB as part of your data infrastructure. How did you discover InfluxDB, get into it? How do you use the platform? Maybe Caleb, you can start. >> Yeah, absolutely. So the first company that I extensively used InfluxDB in was a launch startup called Astra. And we were in the process of designing our first generation rocket there and testing the engines, pumps. Everything that goes into a rocket. And when I joined the company, our data story was not very mature. We were collecting a bunch of data in LabVIEW. And engineers were taking that over to MATLAB to process it. And at first, that's the way that a lot of engineers and scientists are used to working. And at first that was, like, people weren't entirely sure that, that needed to change. But it's something, the nice thing about InfluxDB is that, it's so easy to deploy. So our software engineering team was able to get it deployed and up and running very quickly and then quickly also backport all of the data that we've collected thus far into Influx. And what was amazing to see and it's kind of the super cool moment with Influx is, when we hooked that up to Grafana, Grafana, is the visualization platform we use with influx, because it works really well with it. There was like this aha moment of our engineers who are used to this post process kind of method for dealing with their data, where they could just almost instantly, easily discover data that they hadn't been able to see before. And take the manual processes that they would run after a test and just throw those all in Influx and have live data as tests were coming. And I saw them implementing crazy rocket equation type stuff in Influx and it just was totally game changing for how we tested. And things that previously it would be like run a test, then wait an hour for the engineers to crunch the data and then we run another test with some changed parameters or a changed startup sequence or something like that, became, by the time the test is over, the engineers know what the next step is, because they have this just like instant game changing access to data. So since that experience, basically everywhere I've gone, every company since then, I've been promoting InfluxDB and using it and spinning it up and quickly showing people how simple and easy it is. >> Yeah, thank you. So Angelo, I was explaining in my open that, you know you could add a column in a traditional RDBMS and do time series. But with the volume of data that you're talking about in the example that Caleb just gave, you have to have a purpose built time series database. Where did you first learn about InfluxDB? >> Yeah, correct. So I worked with the data management team and my first project was the record metrics that measure the performance of our software. The software that we use to process the data. So I started implementing that in our relational database. But then I realized that in fact, I was dealing with time series data. And I should really use a solution built for that. And then I started looking at time series databases and I found InfluxDB, that was back in 2018. Then I got involved in another project. To record telemetry data from the telescope itself. It's very challenging because you have so many subsystems and sensors, producing data. And with that data, the goal is to look at the telescope harder in real time so we can make decisions and make sure that everything's doing the right thing. And another use for InfluxDB that I'm also interested, is the visits database. If you think about the observations, we are moving the telescope all the time and pointing to specific directions in the sky and taking pictures every 30 seconds. So that itself is a time series. And every point in the time series, we call that visit. So we want to record the metadata about those visits in InfluxDB. That time series is going to be 10 years long, with about 1000 points every night. It's actually not too much data compared to the other problems. It's really just the different time scale. So yeah, we have plans on continuing using InfluxDB and finding new applications in the project. >> Yeah and the speed with which you can actually get high quality images. Angelo, my understanding is, you use InfluxDB, as you said, you're monitoring the telescope hardware and the software. And just say, some of the scientific data as well. The telescope at the Rubin Observatory is like, no pun intended, I guess, the star of the show. And I believe, I read that it's going to be the first of the next gen telescopes to come online. It's got this massive field of view, like three orders of magnitude times the Hubble's widest camera view, which is amazing. That's like 40 moons in an image, and amazingly fast as well. What else can you tell us about the telescope? >> Yeah, so it's really a challenging project, from the point of view of engineering. This telescope, it has to move really fast. And it also has to carry the primary mirror, which is an eight meter piece of glass, it's very heavy. And it has to carry a camera, which is about the size of a small car. And this whole structure weighs about 300 pounds. For that to work, the telescope needs to be very compact and stiff. And one thing that's amazing about its design is that the telescope, this 300 tons structure, it sits on a tiny film of oil, which has the diameter of human hair, in that brings an almost zero friction interface. In fact, a few people can move this enormous structure with only their hands. As you said, another aspect that makes this telescope unique is the optical design. It's a wide field telescope. So each image has, in diameter, the size of about seven full moons. And with that we can map the entire sky in only three days. And of course, during operations, everything's controlled by software, and it's automatic. There's a very complex piece of software called the scheduler, which is responsible for moving the telescope and the camera. Which will record the 15 terabytes of data every night. >> And Angelo, all this data lands in InfluxDB, correct? And what are you doing with all that data? >> Yeah, actually not. So we're using InfluxDB to record engineering data and metadata about the observations, like telemetry events and the commands from the telescope. That's a much smaller data set compared to the images. But it is still challenging because you have some high frequency data that the system needs to keep up and we need to store this data and have it around for the lifetime of the project. >> Hm. So at the mountain, we keep the data for 30 days. So the observers, they use Influx and InfluxDB instance, running there to analyze the data. But we also replicate the data to another instance running at the US data facility, where we have more computational resources and so more people can look at the data without interfering with the observations. Yeah, I have to say that InfluxDB has been really instrumental for us, and especially at this phase of the project where we are testing and integrating the different pieces of hardware. And it's not just the database, right. It's the whole platform. So I like to give this example, when we are doing this kind of task, it's hard to know in advance which dashboards and visualizations you're going to need, right. So what you really need is a data exploration tool. And with tools like chronograph, for example, having the ability to query and create dashboards on the fly was really a game changer for us. So astronomers, they typically are not software engineers, but they are the ones that know better than anyone, what needs to be monitored. And so they use chronograph and they can create the dashboards and the visualizations that they need. >> Got it. Thank you. Okay, Caleb, let's bring you back in. Tell us more about, you got these dishwasher size satellites are kind of using a multi tenant model. I think it's genius. But tell us about the satellites themselves. >> Yeah, absolutely. So we have in space, some satellites already. That, as you said, are like dishwasher, mini fridge kind of size. And we're working on a bunch more that are a variety of sizes from shoe box to I guess, a few times larger than what we have today. And it is, we do shoot to have, effectively something like a multi tenant model where we will buy a bus off the shelf, the bus is, what you can kind of think of as the core piece of the satellite, almost like a motherboard or something. Where it's providing the power, it has the solar panels, it has some radios attached to it, it handles the altitude control, basically steers the spacecraft in orbit. And then we build, also in house, what we call our payload hub, which is has all any customer payloads attached, and our own kind of edge processing sort of capabilities built into it. And so we integrate that, we launch it, and those things, because they're in low Earth orbit, they're orbiting the Earth every 90 minutes. That's seven kilometers per second, which is several times faster than a speeding bullet. So we've got, we have one of the unique challenges of operating spacecraft in lower Earth orbit is that generally you can't talk to them all the time. So we're managing these things through very brief windows of time. Where we get to talk to them through our ground sites, either in Antarctica or in the North Pole region. So we'll see them for 10 minutes, and then we won't see them for the next 90 minutes as they zip around the Earth collecting data. So one of the challenges that exists for a company like ours is, that's a lot of, you have to be able to make real time decisions operationally, in those short windows that can sometimes be critical to the health and safety of the spacecraft. And it could be possible that we put ourselves into a low power state in the previous orbit or something potentially dangerous to the satellite can occur. And so as an operator, you need to very quickly process that data coming in. And not just the the live data, but also the massive amounts of data that were collected in, what we call the back orbit, which is the time that we couldn't see the spacecraft. >> We got it. So talk more about how you use InfluxDB to make sense of this data from all those tech that you're launching into space. >> Yeah, so we basically, previously we started off, when I joined the company, storing all of that, as Angelo did, in a regular relational database. And we found that it was so slow, and the size of our data would balloon over the course of a couple of days to the point where we weren't able to even store all of the data that we were getting. So we migrated to InfluxDB to store our time series telemetry from the spacecraft. So that thing's like power level voltage, currents counts, whatever metadata we need to monitor about the spacecraft, we now store that in InfluxDB. And that has, you know, now we can actually easily store the entire volume of data for the mission life so far, without having to worry about the size bloating to an unmanageable amount. And we can also seamlessly query large chunks of data, like if I need to see, for example, as an operator, I might want to see how my battery state of charge is evolving over the course of the year, I can have a plot in an Influx that loads that in a fraction of a second for a year's worth of data, because it does, you know, intelligent. I can intelligently group the data by citing time interval. So it's been extremely powerful for us to access the data. And as time has gone on, we've gradually migrated more and more of our operating data into Influx. So not only do we store the basic telemetry about the bus and our payload hub, but we're also storing data for our customers, that our customers are generating on board about things like you know, one example of a customer that's doing something pretty cool. They have a computer on our satellite, which they can reprogram themselves to do some AI enabled edge compute type capability in space. And so they're sending us some metrics about the status of their workloads, in addition to the basics, like the temperature of their payload, their computer or whatever else. And we're delivering that data to them through Influx in a Grafana dashboard that they can plot where they can see, not only has this pipeline succeeded or failed, but also where was the spacecraft when this occurred? What was the voltage being supplied to their payload? Whatever they need to see, it's all right there for them. Because we're aggregating all that data in InfluxDB. >> That's awesome. You're measuring everything. Let's talk a little bit about, we throw this term around a lot, data driven. A lot of companies say, Oh, yes, we're data driven. But you guys really are. I mean, you got data at the core. Caleb, what does that what does that mean to you? >> Yeah, so you know, I think, the clearest example of when I saw this, be like totally game changing is, what I mentioned before it, at Astra, were our engineers feedback loop went from a lot of, kind of slow researching, digging into the data to like an instant, instantaneous, almost, Seeing the data, making decisions based on it immediately, rather than having to wait for some processing. And that's something that I've also seen echoed in my current role. But to give another practical example, as I said, we have a huge amount of data that comes down every orbit, and we need to be able to ingest all that data almost instantaneously and provide it to the operator in near real time. About a second worth of latency is all that's acceptable for us to react to. To see what is coming down from the spacecraft and building that pipeline is challenging, from a software engineering standpoint. Our primary language is Python, which isn't necessarily that fast. So what we've done is started, in the in the goal being data driven, is publish metrics on individual, how individual pieces of our data processing pipeline, are performing into Influx as well. And we do that in production as well as in dev. So we have kind of a production monitoring flow. And what that has done is, allow us to make intelligent decisions on our software development roadmap. Where it makes the most sense for us to focus our development efforts in terms of improving our software efficiency, just because we have that visibility into where the real problems are. At sometimes we've found ourselves, before we started doing this, kind of chasing rabbits that weren't necessarily the real root cause of issues that we were seeing. But now, that we're being a bit more data driven, there, we are being much more effective in where we're spending our resources and our time, which is especially critical to us as we scaled from supporting a couple of satellites to supporting many, many satellites at once. >> So you reduce those dead ends. Maybe Angela, you could talk about what sort of data driven means to you and your team? >> Yeah, I would say that having real time visibility, to the telemetry data and metrics is crucial for us. We need to make sure that the images that we collect, with the telescope have good quality and that they are within the specifications to meet our science goals. And so if they are not, we want to know that as soon as possible, and then start fixing problems. >> Yeah, so I mean, you think about these big science use cases, Angelo. They are extremely high precision, you have to have a lot of granularity, very tight tolerances. How does that play into your time series data strategy? >> Yeah, so one of the subsystems that produce the high volume and high rates is the structure that supports the telescope's primary mirror. So on that structure, we have hundreds of actuators that compensate the shape of the mirror for the formations. That's part of our active updated system. So that's really real time. And we have to record this high data rates, and we have requirements to handle data that are a few 100 hertz. So we can easily configure our database with milliseconds precision, that's for telemetry data. But for events, sometimes we have events that are very close to each other and then we need to configure database with higher precision. >> um hm For example, micro seconds. >> Yeah, so Caleb, what are your event intervals like? >> So I would say that, as of today on the spacecraft, the event, the level of timing that we deal with probably tops out at about 20 hertz, 20 measurements per second on things like our gyroscopes. But I think the core point here of the ability to have high precision data is extremely important for these kinds of scientific applications. And I'll give you an example, from when I worked on the rockets at Astra. There, our baseline data rate that we would ingest data during a test is 500 hertz, so 500 samples per second. And in some cases, we would actually need to ingest much higher rate data. Even up to like 1.5 kilohertz. So extremely, extremely high precision data there, where timing really matters a lot. And, I can, one of the really powerful things about Influx is the fact that it can handle this, that's one of the reasons we chose it. Because there's times when we're looking at the results of firing, where you're zooming in. I've talked earlier about how on my current job, we often zoom out to look at a year's worth of data. You're zooming in, to where your screen is preoccupied by a tiny fraction of a second. And you need to see, same thing, as Angelo just said, not just the actual telemetry, which is coming in at a high rate, but the events that are coming out of our controllers. So that can be something like, hey, I opened this valve at exactly this time. And that goes, we want to have that at micro or even nanosecond precision, so that we know, okay, we saw a spike in chamber pressure at this exact moment, was that before or after this valve open? That kind of visibility is critical in these kinds of scientific applications and absolutely game changing, to be able to see that in near real time. And with a really easy way for engineers to be able to visualize this data themselves without having to wait for us software engineers to go build it for them. >> Can the scientists do self serve? Or do you have to design and build all the analytics and queries for scientists? >> I think that's absolutely from my perspective, that's absolutely one of the best things about Influx, and what I've seen be game changing is that, generally, I'd say anyone can learn to use Influx. And honestly, most of our users might not even know they're using Influx. Because the interface that we expose to them is Grafana, which is generic graphing, open source graphing library that is very similar to Influx zone chronograph. >> Sure. >> And what it does is, it provides this, almost, it's a very intuitive UI for building your query. So you choose a measurement, and it shows a drop down of available measurements, and then you choose the particular field you want to look at. And again, that's a drop down. So it's really easy for our users to discover it. And there's kind of point and click options for doing math, aggregations. You can even do like, perfect kind of predictions all within Grafana. The Grafana user interface, which is really just a wrapper around the API's and functionality that Influx provides. So yes, absolutely, that's been the most powerful thing about it, is that it gets us out of the way, us software engineers, who may not know quite as much as the scientists and engineers that are closer to the interesting math. And they build these crazy dashboards that I'm just like, wow, I had no idea you could do that. I had no idea that, that is something that you would want to see. And absolutely, that's the most empowering piece. >> Yeah, putting data in the hands of those who have the context, the domain experts is key. Angelo is it the same situation for you? Is it self serve? >> Yeah, correct. As I mentioned before, we have the astronomers making their own dashboards, because they know exactly what they need to visualize. And I have an example just from last week. We had an engineer at the observatory that was building a dashboard to monitor the cooling system of the entire building. And he was familiar with InfluxQL, which was the primarily query language in version one of InfluxDB. And he had, that was really a challenge because he had all the data spread at multiple InfluxDB measurements. And he was like doing one query for each measurement and was not able to produce what he needed. And then, but that's the perfect use case for Flux, which is the new data scripting language that Influx data developed and introduced as the main language in version two. And so with Flux, he was able to combine data from multiple measurements and summarize this data in a nice table. So yeah, having more flexible and powerful language, also allows you to make better a visualization. >> So Angelo, where would you be without time series database, that technology generally, may be specifically InfluxDB, as one of the leading platforms. Would you be able to do this? >> Yeah, it's hard to imagine, doing what we are doing without InfluxDB. And I don't know, perhaps it would be just a matter of time to rediscover InfluxDB. >> Yeah. How about you Caleb? >> Yeah, I mean, it's all about using the right tool for the job. I think for us, when I joined the company, we weren't using InfluxDB and we were dealing with serious issues of the database growing to a an incredible size, extremely quickly. And being unable to, like even querying short periods of data, was taking on the order of seconds, which is just not possible for operations. So time series database is, if you're dealing with large volumes of time series data, Time series database is the right tool for the job and Influx is a great one for it. So, yeah, it's absolutely required to use for this kind of data, there is not really any other option. >> Guys, this has been really informative. It's pretty exciting to see, how the edge is mountain tops, lower Earth orbits. Space is the ultimate edge. Isn't it. I wonder if you could two questions to wrap here. What comes next for you guys? And is there something that you're really excited about? That you're working on. Caleb, may be you could go first and than Angelo you could bring us home. >> Yeah absolutely, So basically, what's next for Loft Orbital is more, more satellites a greater push towards infrastructure and really making, our mission is to make space simple for our customers and for everyone. And we're scaling the company like crazy now, making that happen. It's extremely exciting and extremely exciting time to be in this company and to be in this industry as a whole. Because there are so many interesting applications out there. So many cool ways of leveraging space that people are taking advantage of and with companies like SpaceX, now rapidly lowering cost of launch. It's just a really exciting place to be in. And we're launching more satellites. We're scaling up for some constellations and our ground system has to be improved to match. So there is a lot of improvements that we are working on to really scale up our control systems to be best in class and make it capable of handling such large workloads. So, yeah. What's next for us is just really 10X ing what we are doing. And that's extremely exciting. >> And anything else you are excited about? Maybe something personal? Maybe, you know, the titbit you want to share. Are you guys hiring? >> We're absolutely hiring. So, we've positions all over the company. So we need software engineers. We need people who do more aerospace specific stuff. So absolutely, I'd encourage anyone to check out the Loft Orbital website, if this is at all interesting. Personal wise, I don't have any interesting personal things that are data related. But my current hobby is sea kayaking, so I'm working on becoming a sea kayaking instructor. So if anyone likes to go sea kayaking out in the San Francisco Bay area, hopefully I'll see you out there. >> Love it. All right, Angelo, bring us home. >> Yeah. So what's next for us is, we're getting this telescope working and collecting data and when that's happened, it's going to be just a delish of data coming out of this camera. And handling all that data, is going to be a really challenging. Yeah, I wonder I might not be here for that I'm looking for it, like for next year we have an important milestone, which is our commissioning camera, which is a simplified version of the full camera, is going to be on sky and so most of the system has to be working by then. >> Any cool hobbies that you are working on or any side project? >> Yeah, actually, during the pandemic I started gardening. And I live here in Two Sun, Arizona. It gets really challenging during the summer because of the lack of water, right. And so, we have an automatic irrigation system at the farm and I'm trying to develop a small system to monitor the irrigation and make sure that our plants have enough water to survive. >> Nice. All right guys, with that we're going to end it. Thank you so much. Really fascinating and thanks to InfluxDB for making this possible. Really ground breaking stuff, enabling value at the edge, in the cloud and of course beyond, at the space. Really transformational work, that you guys are doing. So congratulations and I really appreciate the broader community. I can't wait to see what comes next from this entire eco system. Now in the moment, I'll be back to wrap up. This is Dave Vallante. And you are watching The cube, the leader in high tech enterprise coverage. (upbeat music)

>>Mhm >>Yes, welcome to this cube conversation. I'm lisa martin excited about this conversation. It's combining my background in life sciences with technology. Please welcome Mike Tarsa Lee, the chief scientific officer at Tetra Science. Mike I'm so excited to talk to you today. >>Thank you lisa and thank you very much to the cube for hosting us. >>Absolutely. So we talk about cloud and data all the time. This is going to be a very interesting conversation especially because we've seen events of the last what are we on 14 months and counting have really accelerated the need for drug discovery and really everyone's kind of focused on that. But I want you to talk with our audience about Tetra science, Who you guys are, what you do and you were founded in 2014. You just raised 80 million in series B but give us an idea of who you are and what you do. >>Got it. Tetro Science, what are we? We are digital plumbers and that may seem funny but really we are taking the world of data and we are trying to resolve it in such a way that people can actually pipe it from the data sources they have in a vendor agnostic way to the data targets in which they need to consume that data. So bringing that metaphor a little bit more to life sciences, let's say that you're a chemist and you have a mass spec and an NMR and some other piece of technology and you need all of those to speak the same language. Right? Generally speaking, all of these are going to be made by different vendors. They're all going to have different control software and they're all going to have slightly different ways of sending their data in. Petro Science takes those all in. We bring them up to the cloud or cloud native solution. We harmonize them, we extract the data first and then we actually put it into what we call our special sauce are intermediate data schema to harmonize it. So you have sort of like a picture and a diagram of what the prototypical mass spec or H P. L. C. Or cell counting data should look like. And then we build pipelines to export that data over to where you need it. So if you need it to live in an L. N. Or a limb system or in a visualization tool like spot fire tableau. We got you covered. So again we're trying to pipe things from left to right from sources to targets and we're trying to do it with scientific context. >>That was an outstanding description. Data plumbers who have secret sauce and never would have thought I would have heard that when I woke up this morning. But I'm going to unpack this more because one of the things that I read in the press release that just went out just a few weeks ago announcing the series B funding, it said that that picture science is pioneering a $300 billion dollar Greenfield data market and operating this is what got my attention without a direct cloud native and open platform competitor. Why is that? >>That's right. If you look at the way pharma data is handled today, even those that long tend to be either on prem solutions with a sort of license model or a distribution into a company and therefore maintenance costs, professional services, etcetera. Or you're looking at somebody who is maybe cloud but their cloud second, you know, they started with their on prem journey and they said we should go and build out some puppies, we should go to the cloud migrate. However, we're cloud first cloud native. So that's one first strong point. And the second is that in terms of data harmonization and in terms of looking at data in a vendor agnostic way, um many companies claim to do it. But the real hard test of this, the metal, what will say is when you can look at this with the Scientific contextual ization we offer. So yes, you can collect the data and put it on a cloud. Okay great. Yes. You may be able to do an extract, transform and load and move it to somewhere else. Okay. But can you actually do that from front to back while retaining all the context of the data while keeping all of the metadata in the right place? With veracity, with G XP readiness, with data fidelity and when it gets over to the other side can somebody say oh yeah that's all the data from all the H. P. L. C. S we control. I got it. I see where it is. I see where to go get it, I see who created it. I see the full data train and validation landscape and I can rebuild that back and I can look back to the old raw source files if I need to. Um I challenge someone to find another direct company that's doing that today. >>You talk about that context and the thing that sort of surprises me is with how incredibly important scientific discovery is and has been for since the beginning of time. Why is why has nobody come out in the last seven years and tried to facilitate this for life sciences organizations. >>Right. I would say that people have tried and I would say that there are definitely strides being made in the open source community, in the data science community and inside pharma and biotech themselves on these sort of build motif, right. If you are inside of a company and you understand your own ontology and processes while you can probably design an application or a workflow using several different tools in order to get that data there. But will it be generally useful to the bioscience community? One thing we pride ourselves on is when we product eyes a connector we call or an integration, we actually do it with a many different companies, generic cases in mind. So we say, OK, you have an h p l C problem over at this top pharma, you have an HPC problem with this biotech and you have another one of the C R. O. Okay. What are the common points between all of those? Can we actually distill that down to a workflow? Everyone's going to need, for example a compliance workflow. So everybody needs compliance. Right. So we can actually look into an empower or a unicorn operation and we can say, okay, did you sign off on that? Did it come through the right way? Was the data corrupted etcetera? That's going to be generically useful to everybody? And that's just one example of something we can do right now for anybody in bio pharma. >>Let's talk about the events of the last 14 months or so mentioned 10 X revenue growth in 2020. Covid really really highlighted the need to accelerate drug discovery and we've seen that. But talk to me about some of the things that Tetra science has seen and done to facilitate that. >>Yeah, this past 14 months. I mean um I will say that the global pandemic has been a challenge for everyone involved ourselves as well. We've basically gone to a full remote workforce. Um We have tried our very best to stay on top of it with remote collaboration tools with vera, with GIT hub with everything. However, I'll say that it's actually been some of the most successful time in our company's history because of that sort of lack of any kind of friction from the physical world. Right? We've really been able to dig down and dig deep on our integrations are connections, our business strategy. And because of that, we've actually been able to deliver a lot of value to customers because, let's be honest, we don't actually have to be on prem from what we're doing since we're not an on prem solution and we're not an original equipment manufacturer, we don't have to say, okay, we're going to go plug the thing in to the H. P. L. C. We don't have to be there to tune the specific wireless protocols or you're a W. S. Protocols, it can all be done remotely. So it's about building good relationships, building trust with our colleagues and clients and making sure we're delivering and over delivering every time. And then people say great um when I elect a Tetra solution, I know what's going right to the cloud, I know I can pick my hosting options, I know you're going to keep delivering more value to me every month. Um Thanks, >>I like that you make it sound simple and that actually you bring up a great point though that the one of the many things that was accelerated this last year Plus is the need to be remote that need to be able to still communicate, collaborate but also the need to establish and really foster those relationships that you have with existing customers and partners as everybody was navigating very, very different challenges. I want to talk now about how you're helping customers unlock the problem that is in every industry data silos and point to point integration where things can talk to each other, Talk to me about how you're helping customers like where do they start with? Touch? Where do you start that? Um kind of journey to unlock data value? >>Sure. Journey to unlock data value. Great question. So first I'll say that customers tend to come to us, it's the oddest thing and we're very lucky and very grateful for this, but they tend to have heard about what we've done with other companies and they come to us they say listen, we've heard about a deployment you've done with novo Nordisk, I can say that for example because you know, it's publicly known. Um so they'll say, you know, we hear about what you've done, we understand that you have deep expertise in chromatography or in bio process. And they'll say here's my really sticky problem. What can you do here? And invariably they're going to lay out a long list of instruments and software for us. Um we've seen lists that go up past 2000 instruments. Um and they'll say, yeah, they'll say here's all the things we need connected, here's four or five different use cases. Um we'll bring you start to finish, we'll give you 20 scientists in the room to talk through them and then we to get somewhere between two and four weeks to think about that problem and come back and say here's how we might solve that. Invariably, all of these problems are going to have a data silos somewhere, there's going to be in Oregon where the preclinical doesn't see the biology or the biology doesn't see the screening etcetera. So we say, all right, give us one scientist from each of those, hence establishing trust, establishing input from everybody. And collaboratively we'll work with, you will set up an architecture diagram, will set up a first version of a prototype connector, will set up all this stuff they need in order to get moving, we'll deliver value upfront before we've ever signed a contract and will say, is this a good way to go for you? And they'll say either no, no, thank you or they'll say yes, let's go forward, let's do a pilot a proof of concept or let's do a full production rollout. And invariably this data silos problem can usually be resolved by again, these generic size connectors are intermediate data schema, which talks and moves things into a common format. Right? And then also by organizationally, since we're already connecting all these groups in this problem statement, they tend to continue working together even when we're no longer front and center, right? They say, oh we set up that thing together. Let's keep thinking about how to make our data more available to one another. >>Interesting. So culturally, within the organization it sounds like Tetra is having significant influences their, you know, the collaboration but also data ownership. Sometimes that becomes a sticky situation where there are owners and they want to read retain that control. Right? You're laughing? You've been through this before. I'd like to understand a little bit more though about the conversation because typically we're talking about tech but we're also talking about science. Are you having these technical conversations with scientists as well as I. T. What is that actual team from the customer perspective look >>like? Oh sure. So the technical conversation and science conversation are going on sometimes in parallel and sometimes in the same threat entirely. Oftentimes the folks who reach out to us first tend to be the scientists. They say I've got a problem, you know and and my research and and I. T. Will probably hear about this later. But let's go. And then we will invariably say well let's bring in your R. And D. I. T. Counterparts because we need them to help solve it right? But yes we are usually having those conversations in parallel at first and then we unite them into one large discussion. And we have varied team members here on the Tetris side we have me from science along with multiple different other PhD holders and pharma lifers in our business who actually can look at the scientific use cases and recommend best practices for that and visualizations. We also have a lot of solutions architects and delivery engineers who can look at it from the how should the platform assemble the solution and how can we carry it through? Um And those two groups are three groups really unite together to provide a unified front and to help the customer through and the customer ends up providing the same thing as we do. So they'll give us on the one call, right? Um a technical expert, a data and QA person and a scientist all in one group and they'll say you guys work together to make sure that our orders best represented here. Um And I think that that's actually a really productive way to do this because we end up finding out things and going deeper into the connector than we would have otherwise. >>It's very collaborative, which is I bet those are such interesting conversations to be a part of it. So it's part of the conversation there helping them understand how to establish a common vision for data across their organization. >>Yes, that that tends to be a sort of further reaching conversation. I'll say in the initial sort of short term conversation, we don't usually say you three scientists or engineers are going to change the fate of the entire orig. That's maybe a little outside of our scope for now. But yes, that first group tends to describe a limited solution. We help to solve that and then go one step past and then they'll nudge somebody else in the Oregon. Say, do you see what Petra did over here? Maybe you could use it over here in your process. And so in that way we sort of get this cultural buy in and then increased collaboration inside a single company. >>Talk to me about some customers that you've worked with it. Especially love to know some of the ones that you've helped in the last year where things have been so incredibly dynamic in the market. But give us an insight into maybe some specific customers that work with you guys. >>Sure. I'd love to I'll speak to the ones that are already on our case studies. You can go anytime detector science dot com and read all of these. But we've worked with Prelude therapeutics for example. We looked at a high throughput screening cascade with them and we were able to take an instrument that was basically unloved in a corner at T. Can liquid handler, hook it up into their Ln. And their screening application and bring in and incorporate data from an external party and do all of that together and merge it so they could actually see out the other side a screening cascade and see their data in minutes as opposed to hours or days. We've also worked as you've seen the press release with novo Nordisk, we worked on automating much of their background for their chromatography fleet. Um and finally we've also worked with several smaller biotechs in looking at sort of in stan shih ation, they say well we've just started we don't have an L. N. We don't have a limbs were about to buy these 50 instruments. Um what can you do with us and we'll actually help them to scope what their initial data storage and harmonization strategy should even be. Um so so we're really man, we're at everywhere from the enterprise where its fleets of thousands of instruments and we're really giving data to a large amount of scientists worldwide, all the way down to the small biotech with 50 people who were helping add value there. >>So big range there in terms of the data conversation, I'm curious has have you seen it change in the last year plus with respect to elevating to the C suite level or the board saying we've got to be able to figure this out because as we saw, you know, the race for the Covid 19 vaccine for example. Time to value and and to discovery is so critical. Is that C suite or board involved in having conversations with you guys? >>It's funny because they are but they are a little later. Um we tend to be a scientist and user driven um solution. So at the beginning we get a power user, an engineer or a R and D I. T. Person in who really has a problem to solve. And as they are going through and developing with us, eventually they're going to need either approval for the time, the resources or the budget and then they'll go up to their VP or their CIA or someone else at the executive level and say, let's start having more of this conversation. Um, as a tandem effort, we are starting to become involved in some thought leadership exercises with some larger firms. And we are looking at the strategic aspect through conferences, through white papers etcetera to speak more directly to that C suite and to say, hey, you know, we could fit your industry for dato motif. And then one other thing you said, time to value. So I'll say that the Tetro science executive team actually looks at that as a tract metric. So we're actually looking at driving that down every single week. >>That's outstanding. That's a hard one to measure, especially in a market that is so dynamic. But that time to value for your customers is critical. Again, covid sort of surfaced a number of things and some silver linings. But that being able to get hands on the day to make sure that you can actually pull insights from it accelerate facilitate drug discovery. That time to value there is absolutely critical. >>Yeah. I'll say if you look at the companies that really, you know, went first and foremost, let's look at Moderna right? Not our customer by the way, but we'll look at Madonna quickly as an example as an example are um, everything they do is automated, right? Everything they do is cloud first. Everything they do is global collaboration networks, you know, with harmonized data etcetera. That is the model we believe Everyone's going to go to in the next 3-5 years. If you look at the fact that Madonna went from sequence to initial vaccine in what, 50, 60 days, that kind of delivery is what the market will become accustomed to. And so we're going to see many more farmers and biotechs move to that cloud first. Distributed model. All data has to go in somewhere centrally. Everyone has to be able to benefit from it. And we are happy to help them get >>Well that's that, you know, setting setting a new record for pace is key there, but it's also one of those silver linings that has come out of this to show that not only was that critical to do, but it can be done. We have the technology, we have the brain power to be able to put those all user would harmonize those together to drive this. So give me a last question. Give me an insight into some of the things that are ahead for Tetra science the rest of this year. >>Oh gosh, so many things. One of the nice parts about having funding in the bank and having a dedicated team is the ability to do more. So first of course our our enterprise pharma and BioPharma clients, there are plenty more use cases, workflows, instruments. We've just about scratch the surface but we're going to keep growing and growing our our integrations and connectors. First of all right we want to be like a netflix for connectors. You know we just want you to come and say look do they have the connector? No well don't worry. They're going to have it in a month or two. Um so that we can be basically the almost the swiss army knife for every single connector you can imagine. Then we're going to be developing a lot more data apps so things that you can use to derive value from your data out. And then again, we're going to be looking at helping to educate everybody. So how is cloud useful? Why go to the system with harmonization? How does this influence your compliance? How can you do bi directional communication? There's lots of ways you can use. Once you have harmonized centralized data, you can do things with it to influence your order and drive times down again from days and weeks, two minutes and seconds. So let's get there. And I think we're going to try doing that over the next year. >>That's awesome. Never a dull moment. And I, you should partner with your marketing folks because we talked about, you talked about data plumbing the secret sauce and becoming the netflix of connectors. These are three gems that you dropped on this this morning mike. This has been awesome. Thank you for sharing with us what teacher science is doing, how you're really helping to fast track a lot of the incredibly important research that we're all really um dependent on and helping to heal the world through data. It's been a pleasure talking with you. >>Haley says I'm a real quickly. It's a team effort. The entire Tetro science team deserves credit for this. I'm just lucky enough to be able to speak to you. So thank you very much for the opportunity. >>And she about cheers to the whole touch of science team. Keep up the great work guys. Uh for mike Roselli, I'm lisa martin. You're watching this cube conversation. >>Mhm.

>>all right, We're five minutes after the hour. That's all aboard. Who's coming aboard? Welcome everyone to the tutorial track for our launchpad of them. So for the next couple of hours, we've got a SYRIZA videos and experts on hand to answer questions about our new product, Doctor Enterprise Container Cloud. Before we jump into the videos and the technology, I just want to introduce myself and my other emcee for the session. I'm Bill Milks. I run curriculum development for Mirant us on. And >>I'm Bruce Basil Matthews. I'm the Western regional Solutions architect for Moran Tissue esa and welcome to everyone to this lovely launchpad oven event. >>We're lucky to have you with us proof. At least somebody on the call knows something about your enterprise Computer club. Um, speaking of people that know about Dr Enterprise Container Cloud, make sure that you've got a window open to the chat for this session. We've got a number of our engineers available and on hand to answer your questions live as we go through these videos and disgusting problem. So that's us, I guess, for Dr Enterprise Container Cloud, this is Mirant asses brand new product for bootstrapping Doctor Enterprise Kubernetes clusters at scale Anything. The airport Abu's? >>No, just that I think that we're trying Thio. Uh, let's see. Hold on. I think that we're trying Teoh give you a foundation against which to give this stuff a go yourself. And that's really the key to this thing is to provide some, you know, many training and education in a very condensed period. So, >>yeah, that's exactly what you're going to see. The SYRIZA videos we have today. We're going to focus on your first steps with Dr Enterprise Container Cloud from installing it to bootstrapping your regional child clusters so that by the end of the tutorial content today, you're gonna be prepared to spin up your first documentary prize clusters using documented prize container class. So just a little bit of logistics for the session. We're going to run through these tutorials twice. We're gonna do one run through starting seven minutes ago up until I guess it will be ten fifteen Pacific time. Then we're gonna run through the whole thing again. So if you've got other colleagues that weren't able to join right at the top of the hour and would like to jump in from the beginning, ten. Fifteen Pacific time. We're gonna do the whole thing over again. So if you want to see the videos twice, you got public friends and colleagues that, you know you wanna pull in for a second chance to see this stuff, we're gonna do it all. All twice. Yeah, this session. Any any logistics I should add, Bruce that No, >>I think that's that's pretty much what we had to nail down here. But let's zoom dash into those, uh, feature films. >>Let's do Edmonds. And like I said, don't be shy. Feel free to ask questions in the chat or engineers and boosting myself are standing by to answer your questions. So let me just tee up the first video here and walk their cost. Yeah. Mhm. Yes. Sorry. And here we go. So our first video here is gonna be about installing the Doctor Enterprise Container Club Management cluster. So I like to think of the management cluster as like your mothership, right? This is what you're gonna use to deploy all those little child clusters that you're gonna use is like, Come on it as clusters downstream. So the management costs was always our first step. Let's jump in there >>now. We have to give this brief little pause >>with no good day video. Focus for this demo will be the initial bootstrap of the management cluster in the first regional clusters to support AWS deployments. The management cluster provides the core functionality, including identity management, authentication, infantry release version. The regional cluster provides the specific architecture provided in this case, eight of us and the Elsie um, components on the UCP Cluster Child cluster is the cluster or clusters being deployed and managed. The deployment is broken up into five phases. The first phase is preparing a big strap note on this dependencies on handling with download of the bridge struck tools. The second phase is obtaining America's license file. Third phase. Prepare the AWS credentials instead of the adduce environment. The fourth configuring the deployment, defining things like the machine types on the fifth phase. Run the bootstrap script and wait for the deployment to complete. Okay, so here we're sitting up the strap node, just checking that it's clean and clear and ready to go there. No credentials already set up on that particular note. Now we're just checking through AWS to make sure that the account we want to use we have the correct credentials on the correct roles set up and validating that there are no instances currently set up in easy to instance, not completely necessary, but just helps keep things clean and tidy when I am perspective. Right. So next step, we're just going to check that we can, from the bootstrap note, reach more antis, get to the repositories where the various components of the system are available. They're good. No areas here. Yeah, right now we're going to start sitting at the bootstrap note itself. So we're downloading the cars release, get get cars, script, and then next, we're going to run it. I'm in. Deploy it. Changing into that big struck folder. Just making see what's there. Right now we have no license file, so we're gonna get the license filed. Oh, okay. Get the license file through the more antis downloads site, signing up here, downloading that license file and putting it into the Carisbrook struck folder. Okay, Once we've done that, we can now go ahead with the rest of the deployment. See that the follow is there. Uh, huh? That's again checking that we can now reach E C two, which is extremely important for the deployment. Just validation steps as we move through the process. All right, The next big step is valid in all of our AWS credentials. So the first thing is, we need those route credentials which we're going to export on the command line. This is to create the necessary bootstrap user on AWS credentials for the completion off the deployment we're now running an AWS policy create. So it is part of that is creating our Food trucks script, creating the mystery policy files on top of AWS, Just generally preparing the environment using a cloud formation script you'll see in a second will give a new policy confirmations just waiting for it to complete. Yeah, and there is done. It's gonna have a look at the AWS console. You can see that we're creative completed. Now we can go and get the credentials that we created Today I am console. Go to that new user that's being created. We'll go to the section on security credentials and creating new keys. Download that information media Access key I D and the secret access key. We went, Yeah, usually then exported on the command line. Okay. Couple of things to Notre. Ensure that you're using the correct AWS region on ensure that in the conflict file you put the correct Am I in for that region? I'm sure you have it together in a second. Yes. Okay, that's the key. Secret X key. Right on. Let's kick it off. Yeah, So this process takes between thirty and forty five minutes. Handles all the AWS dependencies for you, and as we go through, the process will show you how you can track it. Andi will start to see things like the running instances being created on the west side. The first phase off this whole process happening in the background is the creation of a local kind based bootstrapped cluster on the bootstrap node that clusters then used to deploy and manage all the various instances and configurations within AWS. At the end of the process, that cluster is copied into the new cluster on AWS and then shut down that local cluster essentially moving itself over. Okay. Local clusters boat just waiting for the various objects to get ready. Standard communities objects here Okay, so we speed up this process a little bit just for demonstration purposes. Yeah. There we go. So first note is being built the best in host. Just jump box that will allow us access to the entire environment. Yeah, In a few seconds, we'll see those instances here in the US console on the right. Um, the failures that you're seeing around failed to get the I. P for Bastian is just the weight state while we wait for a W s to create the instance. Okay. Yes. Here, beauty there. Okay. Mhm. Okay. Yeah, yeah. Okay. On there. We got question. Host has been built on three instances for the management clusters have now been created. We're going through the process of preparing. Those nodes were now copying everything over. See that? The scaling up of controllers in the big Strap cluster? It's indicating that we're starting all of the controllers in the new question. Almost there. Yeah. Yeah, just waiting for key. Clark. Uh huh. Start to finish up. Yeah. No. What? Now we're shutting down control this on the local bootstrap node on preparing our I. D. C. Configuration. Fourth indication, soon as this is completed. Last phase will be to deploy stack light into the new cluster the last time Monitoring tool set way Go stack like to plan It has started. Mhm coming to the end of the deployment Mountain. Yeah, America. Final phase of the deployment. Onda, We are done. Okay, You'll see. At the end they're providing us the details of you. I log in so there's a keeper clogging. You can modify that initial default password is part of the configuration set up with one documentation way. Go Councils up way can log in. Yeah, yeah, thank you very much for watching. >>Excellent. So in that video are wonderful field CTO Shauna Vera bootstrapped up management costume for Dr Enterprise Container Cloud Bruce, where exactly does that leave us? So now we've got this management costume installed like what's next? >>So primarily the foundation for being able to deploy either regional clusters that will then allow you to support child clusters. Uh, comes into play the next piece of what we're going to show, I think with Sean O'Mara doing this is the child cluster capability, which allows you to then deploy your application services on the local cluster. That's being managed by the ah ah management cluster that we just created with the bootstrap. >>Right? So this cluster isn't yet for workloads. This is just for bootstrapping up the downstream clusters. Those or what we're gonna use for workings. >>Exactly. Yeah. And I just wanted to point out, since Sean O'Mara isn't around, toe, actually answer questions. I could listen to that guy. Read the phone book, and it would be interesting, but anyway, you can tell him I said that >>he's watching right now, Crusoe. Good. Um, cool. So and just to make sure I understood what Sean was describing their that bootstrap er knows that you, like, ran document fresh pretender Cloud from to begin with. That's actually creating a kind kubernetes deployment kubernetes and Docker deployment locally. That then hits the AWS a p i in this example that make those e c two instances, and it makes like a three manager kubernetes cluster there, and then it, like, copies itself over toe those communities managers. >>Yeah, and and that's sort of where the transition happens. You can actually see it. The output that when it says I'm pivoting, I'm pivoting from my local kind deployment of cluster AP, I toothy, uh, cluster, that's that's being created inside of AWS or, quite frankly, inside of open stack or inside of bare metal or inside of it. The targeting is, uh, abstracted. Yeah, but >>those air three environments that we're looking at right now, right? Us bare metal in open staff environments. So does that kind cluster on the bootstrap er go away afterwards. You don't need that afterwards. Yeah, that is just temporary. To get things bootstrapped, then you manage things from management cluster on aws in this example? >>Yeah. Yeah. The seed, uh, cloud that post the bootstrap is not required anymore. And there's no, uh, interplay between them after that. So that there's no dependencies on any of the clouds that get created thereafter. >>Yeah, that actually reminds me of how we bootstrapped doctor enterprise back in the day, be a temporary container that would bootstrap all the other containers. Go away. It's, uh, so sort of a similar, similar temporary transient bootstrapping model. Cool. Excellent. What will convict there? It looked like there wasn't a ton, right? It looked like you had to, like, set up some AWS parameters like credentials and region and stuff like that. But other than that, that looked like heavily script herbal like there wasn't a ton of point and click there. >>Yeah, very much so. It's pretty straightforward from a bootstrapping standpoint, The config file that that's generated the template is fairly straightforward and targeted towards of a small medium or large, um, deployment. And by editing that single file and then gathering license file and all of the things that Sean went through, um, that that it makes it fairly easy to script >>this. And if I understood correctly as well that three manager footprint for your management cluster, that's the minimum, right. We always insist on high availability for this management cluster because boy do not wanna see oh, >>right, right. And you know, there's all kinds of persistent data that needs to be available, regardless of whether one of the notes goes down or not. So we're taking care of all of that for you behind the scenes without you having toe worry about it as a developer. >>No, I think there's that's a theme that I think will come back to throughout the rest of this tutorial session today is there's a lot of there's a lot of expertise baked him to Dr Enterprise Container Cloud in terms of implementing best practices for you like the defaulter, just the best practices of how you should be managing these clusters, Miss Seymour. Examples of that is the day goes on. Any interesting questions you want to call out from the chap who's >>well, there was. Yeah, yeah, there was one that we had responded to earlier about the fact that it's a management cluster that then conduce oh, either the the regional cluster or a local child molester. The child clusters, in each case host the application services, >>right? So at this point, we've got, in some sense, like the simplest architectures for our documentary prize Container Cloud. We've got the management cluster, and we're gonna go straight with child cluster. In the next video, there's a more sophisticated architecture, which will also proper today that inserts another layer between those two regional clusters. If you need to manage regions like across a BS, reads across with these documents anything, >>yeah, that that local support for the child cluster makes it a lot easier for you to manage the individual clusters themselves and to take advantage of our observation. I'll support systems a stack light and things like that for each one of clusters locally, as opposed to having to centralize thumb >>eso. It's a couple of good questions. In the chat here, someone was asking for the instructions to do this themselves. I strongly encourage you to do so. That should be in the docks, which I think Dale helpfully thank you. Dale provided links for that's all publicly available right now. So just head on in, head on into the docks like the Dale provided here. You can follow this example yourself. All you need is a Mirante license for this and your AWS credentials. There was a question from many a hear about deploying this toe azure. Not at G. Not at this time. >>Yeah, although that is coming. That's going to be in a very near term release. >>I didn't wanna make promises for product, but I'm not too surprised that she's gonna be targeted. Very bracing. Cool. Okay. Any other thoughts on this one does. >>No, just that the fact that we're running through these individual pieces of the steps Well, I'm sure help you folks. If you go to the link that, uh, the gentleman had put into the chat, um, giving you the step by staff. Um, it makes it fairly straightforward to try this yourselves. >>E strongly encourage that, right? That's when you really start to internalize this stuff. OK, but before we move on to the next video, let's just make sure everyone has a clear picture in your mind of, like, where we are in the life cycle here creating this management cluster. Just stop me if I'm wrong. Who's creating this management cluster is like, you do that once, right? That's when your first setting up your doctor enterprise container cloud environment of system. What we're going to start seeing next is creating child clusters and this is what you're gonna be doing over and over and over again. When you need to create a cluster for this Deb team or, you know, this other team river it is that needs commodity. Doctor Enterprise clusters create these easy on half will. So this was once to set up Dr Enterprise Container Cloud Child clusters, which we're going to see next. We're gonna do over and over and over again. So let's go to that video and see just how straightforward it is to spin up a doctor enterprise cluster for work clothes as a child cluster. Undocumented brands contain >>Hello. In this demo, we will cover the deployment experience of creating a new child cluster, the scaling of the cluster and how to update the cluster. When a new version is available, we begin the process by logging onto the you I as a normal user called Mary. Let's go through the navigation of the U I so you can switch. Project Mary only has access to development. Get a list of the available projects that you have access to. What clusters have been deployed at the moment there. Nan Yes, this H Keys Associate ID for Mary into her team on the cloud credentials that allow you to create access the various clouds that you can deploy clusters to finally different releases that are available to us. We can switch from dark mode to light mode, depending on your preferences, Right? Let's now set up semester search keys for Mary so she can access the notes and machines again. Very simply, had Mississippi key give it a name, we copy and paste our public key into the upload key block. Or we can upload the key if we have the file available on our local machine. A simple process. So to create a new cluster, we define the cluster ad management nodes and add worker nodes to the cluster. Yeah, again, very simply, you go to the clusters tab. We hit the create cluster button. Give the cluster name. Yeah, Andi, select the provider. We only have access to AWS in this particular deployment, so we'll stick to AWS. What's like the region in this case? US West one release version five point seven is the current release Onda Attach. Mary's Key is necessary Key. We can then check the rest of the settings, confirming the provider Any kubernetes c r D r I p address information. We can change this. Should we wish to? We'll leave it default for now on. Then what components? A stack light I would like to deploy into my Custer. For this. I'm enabling stack light on logging on Aiken. Sit up the retention sizes Attention times on. Even at this stage, at any customer alerts for the watchdogs. E consider email alerting which I will need my smart host details and authentication details. Andi Slack Alerts. Now I'm defining the cluster. All that's happened is the cluster's been defined. I now need to add machines to that cluster. I'll begin by clicking the create machine button within the cluster definition. Oh, select manager, Select the number of machines. Three is the minimum. Select the instant size that I'd like to use from AWS and very importantly, ensure correct. Use the correct Am I for the region. I commend side on the route device size. There we go, my three machines obviously creating. I now need to add some workers to this custom. So I go through the same process this time once again, just selecting worker. I'll just add to once again, the AM is extremely important. Will fail if we don't pick the right, Am I for a boon to machine in this case and the deployment has started. We can go and check on the bold status are going back to the clusters screen on clicking on the little three dots on the right. We get the cluster info and the events, so the basic cluster info you'll see pending their listen cluster is still in the process of being built. We kick on, the events will get a list of actions that have been completed This part of the set up of the cluster. So you can see here we've created the VPC. We've created the sub nets on We've created the Internet gateway. It's unnecessary made of us and we have no warnings of the stage. Yeah, this will then run for a while. We have one minute past waken click through. We can check the status of the machine bulls as individuals so we can check the machine info, details of the machines that we've assigned, right? Mhm Onda. See any events pertaining to the machine areas like this one on normal? Yeah. Just watch asked. The community's components are waiting for the machines to start. Go back to Custer's. Okay, right. Because we're moving ahead now. We can see we have it in progress. Five minutes in new Matt Gateway on the stage. The machines have been built on assigned. I pick up the U. S. Thank you. Yeah. There we go. Machine has been created. See the event detail and the AWS. I'd for that machine. Mhm. No speeding things up a little bit. This whole process and to end takes about fifteen minutes. Run the clock forward, you'll notice is the machines continue to bold the in progress. We'll go from in progress to ready. A soon as we got ready on all three machines, the managers on both workers way could go on and we could see that now we reached the point where the cluster itself is being configured. Mhm, mhm. And then we go. Cluster has been deployed. So once the classes deployed, we can now never get around our environment. Okay, Are cooking into configure cluster We could modify their cluster. We could get the end points for alert alert manager on See here The griffon occupying and Prometheus are still building in the background but the cluster is available on you would be able to put workloads on it the stretch to download the cube conflict so that I can put workloads on it. It's again three little dots in the right for that particular cluster. If the download cube conflict give it my password, I now have the Q conflict file necessary so that I can access that cluster Mhm all right Now that the build is fully completed, we can check out cluster info on. We can see that Allow the satellite components have been built. All the storage is there, and we have access to the CPU. I So if we click into the cluster, we can access the UCP dashboard, right? Shit. Click the signing with Detroit button to use the SSO on. We give Mary's possible to use the name once again. Thing is, an unlicensed cluster way could license at this point. Or just skip it on. There. We have the UCP dashboard. You can see that has been up for a little while. We have some data on the dashboard going back to the console. We can now go to the griffon, a data just being automatically pre configured for us. We can switch and utilized a number of different dashboards that have already been instrumented within the cluster. So, for example, communities cluster information, the name spaces, deployments, nodes. Mhm. So we look at nodes. If we could get a view of the resource is utilization of Mrs Custer is very little running in it. Yeah. General dashboard of Cuba navies cluster one of this is configurable. You can modify these for your own needs, or add your own dashboards on de scoped to the cluster. So it is available to all users who have access to this specific cluster, all right to scale the cluster on to add a notice. A simple is the process of adding a mode to the cluster, assuming we've done that in the first place. So we go to the cluster, go into the details for the cluster we select, create machine. Once again, we need to be ensure that we put the correct am I in and any other functions we like. You can create different sized machines so it could be a larger node. Could be bigger disks and you'll see that worker has been added from the provisioning state on shortly. We will see the detail off that worker as a complete to remove a note from a cluster. Once again, we're going to the cluster. We select the node would like to remove. Okay, I just hit delete On that note. Worker nodes will be removed from the cluster using according and drawing method to ensure that your workouts are not affected. Updating a cluster. When an update is available in the menu for that particular cluster, the update button will become available. And it's a simple as clicking the button, validating which release you would like to update to. In this case, the next available releases five point seven point one. Here I'm kicking the update by in the background We will coordinate. Drain each node slowly go through the process of updating it. Andi update will complete depending on what the update is as quickly as possible. Girl, we go. The notes being rebuilt in this case impacted the manager node. So one of the manager nodes is in the process of being rebuilt. In fact, to in this case, one has completed already on In a few minutes we'll see that there are great has been completed. There we go. Great. Done. Yeah. If you work loads of both using proper cloud native community standards, there will be no impact. >>Excellent. So at this point, we've now got a cluster ready to start taking our communities of workloads. He started playing or APs to that costume. So watching that video, the thing that jumped out to me at first Waas like the inputs that go into defining this workload cost of it. All right, so we have to make sure we were using on appropriate am I for that kind of defines the substrate about what we're gonna be deploying our cluster on top of. But there's very little requirements. A so far as I could tell on top of that, am I? Because Docker enterprise Container Cloud is gonna bootstrap all the components that you need. That s all we have is kind of kind of really simple bunch box that we were deploying these things on top of so one thing that didn't get dug into too much in the video. But it's just sort of implied. Bruce, maybe you can comment on this is that release that Shawn had to choose for his, uh, for his cluster in creating it. And that release was also the thing we had to touch. Wanted to upgrade part cluster. So you have really sharp eyes. You could see at the end there that when you're doing the release upgrade enlisted out a stack of components docker, engine, kubernetes, calico, aled, different bits and pieces that go into, uh, go into one of these commodity clusters that deploy. And so, as far as I can tell in that case, that's what we mean by a release. In this sense, right? It's the validated stack off container ization and orchestration components that you know we've tested out and make sure it works well, introduction environments. >>Yeah, and and And that's really the focus of our effort is to ensure that any CVS in any of the stack are taken care of that there is a fixes air documented and up streamed to the open stack community source community, um, and and that, you know, then we test for the scaling ability and the reliability in high availability configuration for the clusters themselves. The hosts of your containers. Right. And I think one of the key, uh, you know, benefits that we provide is that ability to let you know, online, high. We've got an update for you, and it's fixes something that maybe you had asked us to fix. Uh, that all comes to you online as your managing your clusters, so you don't have to think about it. It just comes as part of the product. >>You just have to click on Yes. Please give me that update. Uh, not just the individual components, but again. It's that it's that validated stack, right? Not just, you know, component X, y and Z work. But they all work together effectively Scalable security, reliably cool. Um, yeah. So at that point, once we started creating that workload child cluster, of course, we bootstrapped good old universal control plane. Doctor Enterprise. On top of that, Sean had the classic comment there, you know? Yeah. Yeah. You'll see a little warnings and errors or whatever. When you're setting up, UCP don't handle, right, Just let it do its job, and it will converge all its components, you know, after just just a minute or two. But we saw in that video, we sped things up a little bit there just we didn't wait for, you know, progress fighters to complete. But really, in real life, that whole process is that anything so spend up one of those one of those fosters so quite quite quick. >>Yeah, and and I think the the thoroughness with which it goes through its process and re tries and re tries, uh, as you know, and it was evident when we went through the initial ah video of the bootstrapping as well that the processes themselves are self healing, as they are going through. So they will try and retry and wait for the event to complete properly on. And once it's completed properly, then it will go to the next step. >>Absolutely. And the worst thing you could do is panic at the first warning and start tearing things that don't don't do that. Just don't let it let it heal. Let take care of itself. And that's the beauty of these manage solutions is that they bake in a lot of subject matter expertise, right? The decisions that are getting made by those containers is they're bootstrapping themselves, reflect the expertise of the Mirant ISS crew that has been developing this content in these two is free for years and years now, over recognizing humanities. One cool thing there that I really appreciate it actually that it adds on top of Dr Enterprise is that automatic griffon a deployment as well. So, Dr Enterprises, I think everyone knows has had, like, some very high level of statistics baked into its dashboard for years and years now. But you know our customers always wanted a double click on that right to be able to go a little bit deeper. And Griffon are really addresses that it's built in dashboards. That's what's really nice to see. >>Yeah, uh, and all of the alerts and, uh, data are actually captured in a Prometheus database underlying that you have access to so that you are allowed to add new alerts that then go out to touch slack and say hi, You need to watch your disk space on this machine or those kinds of things. Um, and and this is especially helpful for folks who you know, want to manage the application service layer but don't necessarily want to manage the operations side of the house. So it gives them a tool set that they can easily say here, Can you watch these for us? And Miran tas can actually help do that with you, So >>yeah, yeah, I mean, that's just another example of baking in that expert knowledge, right? So you can leverage that without tons and tons of a long ah, long runway of learning about how to do that sort of thing. Just get out of the box right away. There was the other thing, actually, that you could sleep by really quickly if you weren't paying close attention. But Sean mentioned it on the video. And that was how When you use dark enterprise container cloud to scale your cluster, particularly pulling a worker out, it doesn't just like Territo worker down and forget about it. Right? Is using good communities best practices to cordon and drain the No. So you aren't gonna disrupt your workloads? You're going to just have a bunch of containers instantly. Excellent crash. You could really carefully manage the migration of workloads off that cluster has baked right in tow. How? How? Document? The brass container cloud is his handling cluster scale. >>Right? And And the kubernetes, uh, scaling methodology is is he adhered to with all of the proper techniques that ensure that it will tell you. Wait, you've got a container that actually needs three, uh, three, uh, instances of itself. And you don't want to take that out, because that node, it means you'll only be able to have to. And we can't do that. We can't allow that. >>Okay, Very cool. Further thoughts on this video. So should we go to the questions. >>Let's let's go to the questions >>that people have. Uh, there's one good one here, down near the bottom regarding whether an a p I is available to do this. So in all these demos were clicking through this web. You I Yes, this is all a p. I driven. You could do all of this. You know, automate all this away is part of the CSC change. Absolutely. Um, that's kind of the point, right? We want you to be ableto spin up. Come on. I keep calling them commodity clusters. What I mean by that is clusters that you can create and throw away. You know, easily and automatically. So everything you see in these demos eyes exposed to FBI? >>Yeah. In addition, through the standard Cube cuddle, Uh, cli as well. So if you're not a programmer, but you still want to do some scripting Thio, you know, set up things and deploy your applications and things. You can use this standard tool sets that are available to accomplish that. >>There is a good question on scale here. So, like, just how many clusters and what sort of scale of deployments come this kind of support our engineers report back here that we've done in practice up to a Zeman ia's like two hundred clusters. We've deployed on this with two hundred fifty nodes in a cluster. So were, you know, like like I said, hundreds, hundreds of notes, hundreds of clusters managed by documented press container fall and then those downstream clusters, of course, subject to the usual constraints for kubernetes, right? Like default constraints with something like one hundred pods for no or something like that. There's a few different limitations of how many pods you can run on a given cluster that comes to us not from Dr Enterprise Container Cloud, but just from the underlying kubernetes distribution. >>Yeah, E. I mean, I don't think that we constrain any of the capabilities that are available in the, uh, infrastructure deliveries, uh, service within the goober Netease framework. So were, you know, But we are, uh, adhering to the standards that we would want to set to make sure that we're not overloading a node or those kinds of things, >>right. Absolutely cool. Alright. So at this point, we've got kind of a two layered our protection when we are management cluster, but we deployed in the first video. Then we use that to deploy one child clustering work, classroom, uh, for more sophisticated deployments where we might want to manage child clusters across multiple regions. We're gonna add another layer into our architectural we're gonna add in regional cluster management. So this idea you're gonna have the single management cluster that we started within the first video. On the next video, we're gonna learn how to spin up a regional clusters, each one of which would manage, for example, a different AWS uh, US region. So let me just pull out the video for that bill. We'll check it out for me. Mhm. >>Hello. In this demo, we will cover the deployment of additional regional management. Cluster will include a brief architectures of you how to set up the management environment, prepare for the deployment deployment overview and then just to prove it, to play a regional child cluster. So, looking at the overall architecture, the management cluster provides all the core functionality, including identity management, authentication, inventory and release version. ING Regional Cluster provides the specific architecture provider in this case AWS on the LCN components on the D you speak Cluster for child cluster is the cluster or clusters being deployed and managed? Okay, so why do you need a regional cluster? Different platform architectures, for example aws who have been stack even bare metal to simplify connectivity across multiple regions handle complexities like VPNs or one way connectivity through firewalls, but also help clarify availability zones. Yeah. Here we have a view of the regional cluster and how it connects to the management cluster on their components, including items like the LCN cluster Manager we also Machine Manager were held. Mandel are managed as well as the actual provider logic. Mhm. Okay, we'll begin by logging on Is the default administrative user writer. Okay, once we're in there, we'll have a look at the available clusters making sure we switch to the default project which contains the administration clusters. Here we can see the cars management cluster, which is the master controller. And you see, it only has three nodes, three managers, no workers. Okay, if we look at another regional cluster similar to what we're going to deploy now, also only has three managers once again, no workers. But as a comparison, here's a child cluster This one has three managers, but also has additional workers associate it to the cluster. All right, we need to connect. Tell bootstrap note. Preferably the same note that used to create the original management plaster. It's just on AWS, but I still want to machine. All right. A few things we have to do to make sure the environment is ready. First thing we're going to see go into route. We'll go into our releases folder where we have the kozberg struck on. This was the original bootstrap used to build the original management cluster. Yeah, we're going to double check to make sure our cube con figures there once again, the one created after the original customers created just double check. That cute conflict is the correct one. Does point to the management cluster. We're just checking to make sure that we can reach the images that everything is working. A condom. No damages waken access to a swell. Yeah. Next we're gonna edit the machine definitions. What we're doing here is ensuring that for this cluster we have the right machine definitions, including items like the am I. So that's found under the templates AWS directory. We don't need to edit anything else here. But we could change items like the size of the machines attempts. We want to use that The key items to ensure where you changed the am I reference for the junta image is the one for the region in this case AWS region for utilizing this was no construct deployment. We have to make sure we're pointing in the correct open stack images. Yeah, okay. Set the correct and my save file. Now we need to get up credentials again. When we originally created the bootstrap cluster, we got credentials from eight of the U. S. If we hadn't done this, we would need to go through the u A. W s set up. So we're just exporting the AWS access key and I d. What's important is CAAs aws enabled equals. True. Now we're sitting the region for the new regional cluster. In this case, it's Frankfurt on exporting our cube conflict that we want to use for the management cluster. When we looked at earlier Yeah, now we're exporting that. Want to call the cluster region Is Frank Foods Socrates Frankfurt yet trying to use something descriptive It's easy to identify. Yeah, and then after this, we'll just run the bootstrap script, which will complete the deployment for us. Bootstrap of the regional cluster is quite a bit quicker than the initial management clusters. There are fewer components to be deployed. Um, but to make it watchable, we've spent it up. So we're preparing our bootstrap cluster on the local bootstrap node. Almost ready on. We started preparing the instances at W s and waiting for that bastard and no to get started. Please. The best you nerd Onda. We're also starting to build the actual management machines they're now provisioning on. We've reached the point where they're actually starting to deploy. Dr. Enterprise, this is probably the longest face. Yeah, seeing the second that all the nerds will go from the player deployed. Prepare, prepare. Yeah, You'll see their status changes updates. He was the first night ready. Second, just applying second already. Both my time. No waiting from home control. Let's become ready. Removing cluster the management cluster from the bootstrap instance into the new cluster running the date of the U. S. All my stay. Ah, now we're playing Stockland. Switch over is done on. Done. Now I will build a child cluster in the new region very, very quickly to find the cluster will pick. Our new credential has shown up. We'll just call it Frankfurt for simplicity a key and customs to find. That's the machine. That cluster stop with three managers. Set the correct Am I for the region? Yeah, Do the same to add workers. There we go test the building. Yeah. Total bill of time Should be about fifteen minutes. Concedes in progress. It's going to expect this up a little bit. Check the events. We've created all the dependencies, machine instances, machines, a boat shortly. We should have a working cluster in Frankfurt region. Now almost a one note is ready from management. Two in progress. Yeah, on we're done. Clusters up and running. Yeah. >>Excellent. So at this point, we've now got that three tier structure that we talked about before the video. We got that management cluster that we do strapped in the first video. Now we have in this example to different regional clustering one in Frankfurt, one of one management was two different aws regions. And sitting on that you can do Strap up all those Doctor enterprise costumes that we want for our work clothes. >>Yeah, that's the key to this is to be able to have co resident with your actual application service enabled clusters the management co resident with it so that you can, you know, quickly access that he observation Elson Surfboard services like the graph, Ana and that sort of thing for your particular region. A supposed to having to lug back into the home. What did you call it when we started >>the mothership? >>The mothership. Right. So we don't have to go back to the mother ship. We could get >>it locally. Yeah, when, like to that point of aggregating things under a single pane of glass? That's one thing that again kind of sailed by in the demo really quickly. But you'll notice all your different clusters were on that same cluster. Your pain on your doctor Enterprise Container Cloud management. Uh, court. Right. So both your child clusters for running workload and your regional clusters for bootstrapping. Those child clusters were all listed in the same place there. So it's just one pane of glass to go look for, for all of your clusters, >>right? And, uh, this is kind of an important point. I was, I was realizing, as we were going through this. All of the mechanics are actually identical between the bootstrapped cluster of the original services and the bootstrapped cluster of the regional services. It's the management layer of everything so that you only have managers, you don't have workers and that at the child cluster layer below the regional or the management cluster itself, that's where you have the worker nodes. And those are the ones that host the application services in that three tiered architecture that we've now defined >>and another, you know, detail for those that have sharp eyes. In that video, you'll notice when deploying a child clusters. There's not on Lee. A minimum of three managers for high availability management cluster. You must have at least two workers that's just required for workload failure. It's one of those down get out of work. They could potentially step in there, so your minimum foot point one of these child clusters is fine. Violence and scalable, obviously, from a >>That's right. >>Let's take a quick peek of the questions here, see if there's anything we want to call out, then we move on to our last want to my last video. There's another question here about, like where these clusters can live. So again, I know these examples are very aws heavy. Honestly, it's just easy to set up down on the other us. We could do things on bare metal and, uh, open stack departments on Prem. That's what all of this still works in exactly the same way. >>Yeah, the, uh, key to this, especially for the the, uh, child clusters, is the provision hers? Right? See you establish on AWS provision or you establish a bare metal provision or you establish a open stack provision. Or and eventually that list will include all of the other major players in the cloud arena. But you, by selecting the provision or within your management interface, that's where you decide where it's going to be hosted, where the child cluster is to be hosted. >>Speaking off all through a child clusters. Let's jump into our last video in the Siri's, where we'll see how to spin up a child cluster on bare metal. >>Hello. This demo will cover the process of defining bare metal hosts and then review the steps of defining and deploying a bare metal based doctor enterprise cluster. So why bare metal? Firstly, it eliminates hyper visor overhead with performance boost of up to thirty percent. Provides direct access to GP use, prioritize for high performance wear clothes like machine learning and AI, and supports high performance workloads like network functions, virtualization. It also provides a focus on on Prem workloads, simplifying and ensuring we don't need to create the complexity of adding another opera visor. Lay it between so continue on the theme Why Communities and bare metal again Hyper visor overhead. Well, no virtualization overhead. Direct access to hardware items like F p G A s G p us. We can be much more specific about resource is required on the nodes. No need to cater for additional overhead. Uh, we can handle utilization in the scheduling. Better Onda we increase the performances and simplicity of the entire environment as we don't need another virtualization layer. Yeah, In this section will define the BM hosts will create a new project will add the bare metal hosts, including the host name. I put my credentials I pay my address the Mac address on then provide a machine type label to determine what type of machine it is for later use. Okay, let's get started. So well again. Was the operator thing. We'll go and we'll create a project for our machines to be a member off helps with scoping for later on for security. I begin the process of adding machines to that project. Yeah. So the first thing we had to be in post, Yeah, many of the machine A name. Anything you want, que experimental zero one. Provide the IAP my user name type my password. Okay. On the Mac address for the common interface with the boot interface and then the i p m I i p address These machines will be at the time storage worker manager. He's a manager. Yeah, we're gonna add a number of other machines on will. Speed this up just so you could see what the process looks like in the future. Better discovery will be added to the product. Okay. Okay. Getting back there we have it are Six machines have been added, are busy being inspected, being added to the system. Let's have a look at the details of a single note. Yeah, you can see information on the set up of the node. Its capabilities? Yeah. As well as the inventory information about that particular machine. I see. Okay, let's go and create the cluster. Yeah, So we're going to deploy a bare metal child cluster. The process we're going to go through is pretty much the same as any other child cluster. So we'll credit custom. We'll give it a name, but if it were selecting bare metal on the region, we're going to select the version we want to apply. No way. We're going to add this search keys. If we hope we're going to give the load. Balancer host I p that we'd like to use out of dress range on update the address range that we want to use for the cluster. Check that the sea ideal blocks for the Cuban ladies and tunnels are what we want them to be. Enable disabled stack light. Yeah, and soothe stack light settings to find the cluster. And then, as for any other machine, we need to add machines to the cluster. Here. We're focused on building communities clusters, so we're gonna put the count of machines. You want managers? We're gonna pick the label type manager and create three machines is the manager for the Cuban eighties. Casting Okay thing. We're having workers to the same. It's a process. Just making sure that the worker label host level are I'm sorry. On when Wait for the machines to deploy. Let's go through the process of putting the operating system on the notes validating and operating system deploying doctor identifies Make sure that the cluster is up and running and ready to go. Okay, let's review the bold events waken See the machine info now populated with more information about the specifics of things like storage and of course, details of a cluster etcetera. Yeah, yeah, well, now watch the machines go through the various stages from prepared to deploy on what's the cluster build? And that brings us to the end of this particular demo. You can see the process is identical to that of building a normal child cluster we got our complaint is complete. >>All right, so there we have it, deploying a cluster to bare metal. Much the same is how we did for AWS. I guess maybe the biggest different stepwise there is there is that registration face first, right? So rather than just using AWS financials toe magically create PM's in the cloud. You got a point out all your bare metal servers to Dr Enterprise between the cloud and they really come in, I guess three profiles, right? You got your manager profile with a profile storage profile which has been labeled as allocate. Um, crossword cluster has appropriate, >>right? And And I think that the you know, the key differentiator here is that you have more physical control over what, uh, attributes that love your cat, by the way, uh, where you have the different attributes of a server of physical server. So you can, uh, ensure that the SSD configuration on the storage nodes is gonna be taken advantage of in the best way the GP use on the worker nodes and and that the management layer is going to have sufficient horsepower to, um, spin up to to scale up the the environments, as required. One of the things I wanted to mention, though, um, if I could get this out without the choking much better. Um, is that Ah, hey, mentioned the load balancer and I wanted to make sure in defining the load balancer and the load balancer ranges. Um, that is for the top of the the cluster itself. That's the operations of the management, uh, layer integrating with your systems internally to be able to access the the Cube Can figs. I I p address the, uh, in a centralized way. It's not the load balancer that's working within the kubernetes cluster that you are deploying. That's still cube proxy or service mesh, or however you're intending to do it. So, um, it's kind of an interesting step that your initial step in building this, um and we typically use things like metal L B or in gen X or that kind of thing is to establish that before we deploy this bear mental cluster so that it can ride on top of that for the tips and things. >>Very cool. So any other thoughts on what we've seen so far today? Bruce, we've gone through all the different layers. Doctor enterprise container clouds in these videos from our management are regional to our clusters on aws hand bear amount, Of course, with his dad is still available. Closing thoughts before we take just a very short break and run through these demos again. >>You know, I've been very exciting. Ah, doing the presentation with you. I'm really looking forward to doing it the second time, so that we because we've got a good rhythm going about this kind of thing. So I'm looking forward to doing that. But I think that the key elements of what we're trying to convey to the folks out there in the audience that I hope you've gotten out of it is that will that this is an easy enough process that if you follow the step by steps going through the documentation that's been put out in the chat, um, that you'll be able to give this a go yourself, Um, and you don't have to limit yourself toe having physical hardware on prim to try it. You could do it in a ws as we've shown you today. And if you've got some fancy use cases like, uh, you you need a Hadoop And and, uh, you know, cloud oriented ai stuff that providing a bare metal service helps you to get there very fast. So right. Thank you. It's been a pleasure. >>Yeah, thanks everyone for coming out. So, like I said we're going to take a very short, like, three minute break here. Uh, take the opportunity to let your colleagues know if they were in another session or they didn't quite make it to the beginning of this session. Or if you just want to see these demos again, we're going to kick off this demo. Siri's again in just three minutes at ten. Twenty five a. M. Pacific time where we will see all this great stuff again. Let's take a three minute break. I'll see you all back here in just two minutes now, you know. Okay, folks, that's the end of our extremely short break. We'll give people just maybe, like one more minute to trickle in if folks are interested in coming on in and jumping into our demo. Siri's again. Eso For those of you that are just joining us now I'm Bill Mills. I head up curriculum development for the training team here. Moran Tous on Joining me for this session of demos is Bruce. Don't you go ahead and introduce yourself doors, who is still on break? That's cool. We'll give Bruce a minute or two to get back while everyone else trickles back in. There he is. Hello, Bruce. >>How'd that go for you? Okay, >>Very well. So let's kick off our second session here. I e just interest will feel for you. Thio. Let it run over here. >>Alright. Hi. Bruce Matthews here. I'm the Western Regional Solutions architect for Marantz. Use A I'm the one with the gray hair and the glasses. Uh, the handsome one is Bill. So, uh, Bill, take it away. >>Excellent. So over the next hour or so, we've got a Siris of demos that's gonna walk you through your first steps with Dr Enterprise Container Cloud Doctor Enterprise Container Cloud is, of course, Miranda's brand new offering from bootstrapping kubernetes clusters in AWS bare metal open stack. And for the providers in the very near future. So we we've got, you know, just just over an hour left together on this session, uh, if you joined us at the top of the hour back at nine. A. M. Pacific, we went through these demos once already. Let's do them again for everyone else that was only able to jump in right now. Let's go. Our first video where we're gonna install Dr Enterprise container cloud for the very first time and use it to bootstrap management. Cluster Management Cluster, as I like to describe it, is our mother ship that's going to spin up all the other kubernetes clusters, Doctor Enterprise clusters that we're gonna run our workloads on. So I'm gonna do >>I'm so excited. I can hardly wait. >>Let's do it all right to share my video out here. Yeah, let's do it. >>Good day. The focus for this demo will be the initial bootstrap of the management cluster on the first regional clusters. To support AWS deployments, the management cluster provides the core functionality, including identity management, authentication, infantry release version. The regional cluster provides the specific architecture provided in this case AWS and the Elsom components on the UCP cluster Child cluster is the cluster or clusters being deployed and managed. The deployment is broken up into five phases. The first phase is preparing a bootstrap note on its dependencies on handling the download of the bridge struck tools. The second phase is obtaining America's license file. Third phase. Prepare the AWS credentials instead of the ideas environment, the fourth configuring the deployment, defining things like the machine types on the fifth phase, Run the bootstrap script and wait for the deployment to complete. Okay, so here we're sitting up the strap node. Just checking that it's clean and clear and ready to go there. No credentials already set up on that particular note. Now, we're just checking through aws to make sure that the account we want to use we have the correct credentials on the correct roles set up on validating that there are no instances currently set up in easy to instance, not completely necessary, but just helps keep things clean and tidy when I am perspective. Right. So next step, we're just gonna check that we can from the bootstrap note, reach more antis, get to the repositories where the various components of the system are available. They're good. No areas here. Yeah, right now we're going to start sitting at the bootstrap note itself. So we're downloading the cars release, get get cars, script, and then next we're going to run it. Yeah, I've been deployed changing into that big struck folder, just making see what's there right now we have no license file, so we're gonna get the license filed. Okay? Get the license file through more antis downloads site signing up here, downloading that license file and putting it into the Carisbrook struck folder. Okay, since we've done that, we can now go ahead with the rest of the deployment. Yeah, see what the follow is there? Uh huh. Once again, checking that we can now reach E C two, which is extremely important for the deployment. Just validation steps as we move through the process. Alright. Next big step is violating all of our AWS credentials. So the first thing is, we need those route credentials which we're going to export on the command line. This is to create the necessary bootstrap user on AWS credentials for the completion off the deployment we're now running in AWS policy create. So it is part of that is creating our food trucks script. Creating this through policy files onto the AWS, just generally preparing the environment using a cloud formation script, you'll see in a second, I'll give a new policy confirmations just waiting for it to complete. And there is done. It's gonna have a look at the AWS console. You can see that we're creative completed. Now we can go and get the credentials that we created. Good day. I am console. Go to the new user that's being created. We'll go to the section on security credentials and creating new keys. Download that information media access Key I. D and the secret access key, but usually then exported on the command line. Okay, Couple of things to Notre. Ensure that you're using the correct AWS region on ensure that in the conflict file you put the correct Am I in for that region? I'm sure you have it together in a second. Okay, thanks. Is key. So you could X key Right on. Let's kick it off. So this process takes between thirty and forty five minutes. Handles all the AWS dependencies for you. Um, as we go through, the process will show you how you can track it. Andi will start to see things like the running instances being created on the AWS side. The first phase off this whole process happening in the background is the creation of a local kind based bootstrapped cluster on the bootstrap node that clusters then used to deploy and manage all the various instances and configurations within AWS at the end of the process. That cluster is copied into the new cluster on AWS and then shut down that local cluster essentially moving itself over. Yeah, okay. Local clusters boat. Just waiting for the various objects to get ready. Standard communities objects here. Yeah, you mentioned Yeah. So we've speed up this process a little bit just for demonstration purposes. Okay, there we go. So first note is being built the bastion host just jump box that will allow us access to the entire environment. Yeah, In a few seconds, we'll see those instances here in the US console on the right. Um, the failures that you're seeing around failed to get the I. P for Bastian is just the weight state while we wait for AWS to create the instance. Okay. Yeah. Beauty there. Movies. Okay, sketch. Hello? Yeah, Okay. Okay. On. There we go. Question host has been built on three instances for the management clusters have now been created. Okay, We're going through the process of preparing. Those nodes were now copying everything over. See that scaling up of controllers in the big strapped cluster? It's indicating that we're starting all of the controllers in the new question. Almost there. Right? Okay. Just waiting for key. Clark. Uh huh. So finish up. Yeah. No. Now we're shutting down. Control this on the local bootstrap node on preparing our I. D. C configuration, fourth indication. So once this is completed, the last phase will be to deploy stack light into the new cluster, that glass on monitoring tool set, Then we go stack like deployment has started. Mhm. Coming to the end of the deployment mountain. Yeah, they were cut final phase of the deployment. And we are done. Yeah, you'll see. At the end, they're providing us the details of you. I log in. So there's a key Clark log in. Uh, you can modify that initial default possible is part of the configuration set up where they were in the documentation way. Go Councils up way can log in. Yeah. Yeah. Thank you very much for watching. >>All right, so at this point, what we have we got our management cluster spun up, ready to start creating work clusters. So just a couple of points to clarify there to make sure everyone caught that, uh, as advertised. That's darker. Enterprise container cloud management cluster. That's not rework loans. are gonna go right? That is the tool and you're gonna use to start spinning up downstream commodity documentary prize clusters for bootstrapping record too. >>And the seed host that were, uh, talking about the kind cluster dingy actually doesn't have to exist after the bootstrap succeeds eso It's sort of like, uh, copies head from the seed host Toothy targets in AWS spins it up it then boots the the actual clusters and then it goes away too, because it's no longer necessary >>so that bootstrapping know that there's not really any requirements, Hardly on that, right. It just has to be able to reach aws hit that Hit that a p I to spin up those easy to instances because, as you just said, it's just a kubernetes in docker cluster on that piece. Drop note is just gonna get torn down after the set up finishes on. You no longer need that. Everything you're gonna do, you're gonna drive from the single pane of glass provided to you by your management cluster Doctor enterprise Continue cloud. Another thing that I think is sort of interesting their eyes that the convict is fairly minimal. Really? You just need to provide it like aws regions. Um, am I? And that's what is going to spin up that spending that matter faster. >>Right? There is a mammal file in the bootstrap directory itself, and all of the necessary parameters that you would fill in have default set. But you have the option then of going in and defining a different Am I different for a different region, for example? Oh, are different. Size of instance from AWS. >>One thing that people often ask about is the cluster footprint. And so that example you saw they were spitting up a three manager, um, managing cluster as mandatory, right? No single manager set up at all. We want high availability for doctrine Enterprise Container Cloud management. Like so again, just to make sure everyone sort of on board with the life cycle stage that we're at right now. That's the very first thing you're going to do to set up Dr Enterprise Container Cloud. You're going to do it. Hopefully exactly once. Right now, you've got your management cluster running, and they're gonna use that to spend up all your other work clusters Day today has has needed How do we just have a quick look at the questions and then lets take a look at spinning up some of those child clusters. >>Okay, e think they've actually been answered? >>Yeah, for the most part. One thing I'll point out that came up again in the Dail, helpfully pointed out earlier in surgery, pointed out again, is that if you want to try any of the stuff yourself, it's all of the dogs. And so have a look at the chat. There's a links to instructions, so step by step instructions to do each and every thing we're doing here today yourself. I really encourage you to do that. Taking this out for a drive on your own really helps internalizing communicate these ideas after the after launch pad today, Please give this stuff try on your machines. Okay, So at this point, like I said, we've got our management cluster. We're not gonna run workloads there that we're going to start creating child clusters. That's where all of our work and we're gonna go. That's what we're gonna learn how to do in our next video. Cue that up for us. >>I so love Shawn's voice. >>Wasn't that all day? >>Yeah, I watched him read the phone book. >>All right, here we go. Let's now that we have our management cluster set up, let's create a first child work cluster. >>Hello. In this demo, we will cover the deployment experience of creating a new child cluster the scaling of the cluster on how to update the cluster. When a new version is available, we begin the process by logging onto the you I as a normal user called Mary. Let's go through the navigation of the u I. So you can switch Project Mary only has access to development. Uh huh. Get a list of the available projects that you have access to. What clusters have been deployed at the moment there. Man. Yes, this H keys, Associate ID for Mary into her team on the cloud credentials that allow you to create or access the various clouds that you can deploy clusters to finally different releases that are available to us. We can switch from dark mode to light mode, depending on your preferences. Right. Let's now set up some ssh keys for Mary so she can access the notes and machines again. Very simply, had Mississippi key give it a name. We copy and paste our public key into the upload key block. Or we can upload the key if we have the file available on our machine. A very simple process. So to create a new cluster, we define the cluster ad management nodes and add worker nodes to the cluster. Yeah, again, very simply, we got the clusters tab we had to create cluster button. Give the cluster name. Yeah, Andi, select the provider. We only have access to AWS in this particular deployment, so we'll stick to AWS. What's like the region in this case? US West one released version five point seven is the current release Onda Attach. Mary's Key is necessary key. We can then check the rest of the settings, confirming the provider any kubernetes c r D a r i p address information. We can change this. Should we wish to? We'll leave it default for now and then what components of stack light? I would like to deploy into my custom for this. I'm enabling stack light on logging, and I consider the retention sizes attention times on. Even at this stage, add any custom alerts for the watchdogs. Consider email alerting which I will need my smart host. Details and authentication details. Andi Slack Alerts. Now I'm defining the cluster. All that's happened is the cluster's been defined. I now need to add machines to that cluster. I'll begin by clicking the create machine button within the cluster definition. Oh, select manager, Select the number of machines. Three is the minimum. Select the instant size that I'd like to use from AWS and very importantly, ensure correct. Use the correct Am I for the region. I convinced side on the route. Device size. There we go. My three machines are busy creating. I now need to add some workers to this cluster. So I go through the same process this time once again, just selecting worker. I'll just add to once again the am I is extremely important. Will fail if we don't pick the right. Am I for a Clinton machine? In this case and the deployment has started, we can go and check on the bold status are going back to the clusters screen on clicking on the little three dots on the right. We get the cluster info and the events, so the basic cluster info you'll see pending their listen. Cluster is still in the process of being built. We kick on, the events will get a list of actions that have been completed This part of the set up of the cluster. So you can see here. We've created the VPC. We've created the sub nets on. We've created the Internet Gateway. It's unnecessary made of us. And we have no warnings of the stage. Okay, this will then run for a while. We have one minute past. We can click through. We can check the status of the machine balls as individuals so we can check the machine info, details of the machines that we've assigned mhm and see any events pertaining to the machine areas like this one on normal. Yeah. Just last. The community's components are waiting for the machines to start. Go back to customers. Okay, right. Because we're moving ahead now. We can see we have it in progress. Five minutes in new Matt Gateway. And at this stage, the machines have been built on assigned. I pick up the U S. Yeah, yeah, yeah. There we go. Machine has been created. See the event detail and the AWS. I'd for that machine. No speeding things up a little bit this whole process and to end takes about fifteen minutes. Run the clock forward, you'll notice is the machines continue to bold the in progress. We'll go from in progress to ready. A soon as we got ready on all three machines, the managers on both workers way could go on and we could see that now we reached the point where the cluster itself is being configured mhm and then we go. Cluster has been deployed. So once the classes deployed, we can now never get around. Our environment are looking into configure cluster. We could modify their cluster. We could get the end points for alert Alert Manager See here the griffon occupying and Prometheus are still building in the background but the cluster is available on You would be able to put workloads on it at this stage to download the cube conflict so that I can put workloads on it. It's again the three little dots in the right for that particular cluster. If the download cube conflict give it my password, I now have the Q conflict file necessary so that I can access that cluster. All right, Now that the build is fully completed, we can check out cluster info on. We can see that all the satellite components have been built. All the storage is there, and we have access to the CPU. I. So if we click into the cluster, we can access the UCP dashboard, click the signing with the clock button to use the SSO. We give Mary's possible to use the name once again. Thing is an unlicensed cluster way could license at this point. Or just skip it on. Do we have the UCP dashboard? You could see that has been up for a little while. We have some data on the dashboard going back to the console. We can now go to the griffon. A data just been automatically pre configured for us. We can switch and utilized a number of different dashboards that have already been instrumented within the cluster. So, for example, communities cluster information, the name spaces, deployments, nodes. Um, so we look at nodes. If we could get a view of the resource is utilization of Mrs Custer is very little running in it. Yeah, a general dashboard of Cuba Navies cluster. What If this is configurable, you can modify these for your own needs, or add your own dashboards on de scoped to the cluster. So it is available to all users who have access to this specific cluster. All right to scale the cluster on to add a No. This is simple. Is the process of adding a mode to the cluster, assuming we've done that in the first place. So we go to the cluster, go into the details for the cluster we select, create machine. Once again, we need to be ensure that we put the correct am I in and any other functions we like. You can create different sized machines so it could be a larger node. Could be bigger group disks and you'll see that worker has been added in the provisioning state. On shortly, we will see the detail off that worker as a complete to remove a note from a cluster. Once again, we're going to the cluster. We select the node we would like to remove. Okay, I just hit delete On that note. Worker nodes will be removed from the cluster using according and drawing method to ensure that your workloads are not affected. Updating a cluster. When an update is available in the menu for that particular cluster, the update button will become available. And it's a simple as clicking the button validating which release you would like to update to this case. This available releases five point seven point one give you I'm kicking the update back in the background. We will coordinate. Drain each node slowly, go through the process of updating it. Andi update will complete depending on what the update is as quickly as possible. Who we go. The notes being rebuilt in this case impacted the manager node. So one of the manager nodes is in the process of being rebuilt. In fact, to in this case, one has completed already. Yeah, and in a few minutes, we'll see that the upgrade has been completed. There we go. Great. Done. If you work loads of both using proper cloud native community standards, there will be no impact. >>All right, there. We haven't. We got our first workload cluster spun up and managed by Dr Enterprise Container Cloud. So I I loved Shawn's classic warning there. When you're spinning up an actual doctor enterprise deployment, you see little errors and warnings popping up. Just don't touch it. Just leave it alone and let Dr Enterprises self healing properties take care of all those very transient temporary glitches, resolve themselves and leave you with a functioning workload cluster within victims. >>And now, if you think about it that that video was not very long at all. And that's how long it would take you if someone came into you and said, Hey, can you spend up a kubernetes cluster for development development A. Over here, um, it literally would take you a few minutes to thio Accomplish that. And that was with a W s. Obviously, which is sort of, ah, transient resource in the cloud. But you could do exactly the same thing with resource is on Prem or resource is, um physical resource is and will be going through that later in the process. >>Yeah, absolutely one thing that is present in that demo, but that I like to highlight a little bit more because it just kind of glides by Is this notion of, ah, cluster release? So when Sean was creating that cluster, and also when when he was upgrading that cluster, he had to choose a release. What does that didn't really explain? What does that mean? Well, in Dr Enterprise Container Cloud, we have released numbers that capture the entire staff of container ization tools that will be deploying to that workload costume. So that's your version of kubernetes sed cor DNs calico. Doctor Engineer. All the different bits and pieces that not only work independently but are validated toe work together as a staff appropriate for production, humanities, adopted enterprise environments. >>Yep. From the bottom of the stack to the top, we actually test it for scale. Test it for CVS, test it for all of the various things that would, you know, result in issues with you running the application services. And I've got to tell you from having, you know, managed kubernetes deployments and things like that that if you're the one doing it yourself, it can get rather messy. Eso This makes it easy. >>Bruce, you were staying a second ago. They I'll take you at least fifteen minutes to install your release. Custer. Well, sure, but what would all the other bits and pieces you need toe? Not just It's not just about pressing the button to install it, right? It's making the right decision. About what components work? Well, our best tested toe be successful working together has a staff? Absolutely. We this release mechanism and Dr Enterprise Container Cloud. Let's just kind of package up that expert knowledge and make it available in a really straightforward, fashionable species. Uh, pre Confederate release numbers and Bruce is you're pointing out earlier. He's got delivered to us is updates kind of transparent period. When when? When Sean wanted toe update that cluster, he created little update. Custer Button appeared when an update was available. All you gotta do is click. It tells you what Here's your new stack of communities components. It goes ahead. And the straps those components for you? >>Yeah, it actually even displays at the top of the screen. Ah, little header That says you've got an update available. Do you want me to apply? It s o >>Absolutely. Another couple of cool things. I think that are easy to miss in that demo was I really like the on board Bafana that comes along with this stack. So we've been Prometheus Metrics and Dr Enterprise for years and years now. They're very high level. Maybe in in previous versions of Dr Enterprise having those detailed dashboards that Ravana provides, I think that's a great value out there. People always wanted to be ableto zoom in a little bit on that, uh, on those cluster metrics, you're gonna provides them out of the box for us. Yeah, >>that was Ah, really, uh, you know, the joining of the Miranda's and Dr teams together actually spawned us to be able to take the best of what Morantes had in the open stack environment for monitoring and logging and alerting and to do that integration in in a very short period of time so that now we've got it straight across the board for both the kubernetes world and the open stack world. Using the same tool sets >>warm. One other thing I wanna point out about that demo that I think there was some questions about our last go around was that demo was all about creating a managed workplace cluster. So the doctor enterprise Container Cloud managers were using those aws credentials provisioned it toe actually create new e c two instances installed Docker engine stalled. Doctor Enterprise. Remember all that stuff on top of those fresh new VM created and managed by Dr Enterprise contain the cloud. Nothing unique about that. AWS deployments do that on open staff doing on Parramatta stuff as well. Um, there's another flavor here, though in a way to do this for all of our long time doctor Enterprise customers that have been running Doctor Enterprise for years and years. Now, if you got existing UCP points existing doctor enterprise deployments, you plug those in to Dr Enterprise Container Cloud, uh, and use darker enterprise between the cloud to manage those pre existing Oh, working clusters. You don't always have to be strapping straight from Dr Enterprises. Plug in external clusters is bad. >>Yep, the the Cube config elements of the UCP environment. The bundling capability actually gives us a very straightforward methodology. And there's instructions on our website for exactly how thio, uh, bring in import and you see p cluster. Um so it it makes very convenient for our existing customers to take advantage of this new release. >>Absolutely cool. More thoughts on this wonders if we jump onto the next video. >>I think we should move press on >>time marches on here. So let's Let's carry on. So just to recap where we are right now, first video, we create a management cluster. That's what we're gonna use to create All our downstream were closed clusters, which is what we did in this video. Let's maybe the simplest architectures, because that's doing everything in one region on AWS pretty common use case because we want to be able to spin up workload clusters across many regions. And so to do that, we're gonna add a third layer in between the management and work cluster layers. That's gonna be our regional cluster managers. So this is gonna be, uh, our regional management cluster that exists per region that we're going to manage those regional managers will be than the ones responsible for spending part clusters across all these different regions. Let's see it in action in our next video. >>Hello. In this demo, we will cover the deployment of additional regional management. Cluster will include a brief architectural overview, how to set up the management environment, prepare for the deployment deployment overview, and then just to prove it, to play a regional child cluster. So looking at the overall architecture, the management cluster provides all the core functionality, including identity management, authentication, inventory and release version. ING Regional Cluster provides the specific architecture provider in this case, AWS on the L C M components on the d you speak cluster for child cluster is the cluster or clusters being deployed and managed? Okay, so why do you need original cluster? Different platform architectures, for example AWS open stack, even bare metal to simplify connectivity across multiple regions handle complexities like VPNs or one way connectivity through firewalls, but also help clarify availability zones. Yeah. Here we have a view of the regional cluster and how it connects to the management cluster on their components, including items like the LCN cluster Manager. We also machine manager. We're hell Mandel are managed as well as the actual provider logic. Okay, we'll begin by logging on Is the default administrative user writer. Okay, once we're in there, we'll have a look at the available clusters making sure we switch to the default project which contains the administration clusters. Here we can see the cars management cluster, which is the master controller. When you see it only has three nodes, three managers, no workers. Okay, if we look at another regional cluster, similar to what we're going to deploy now. Also only has three managers once again, no workers. But as a comparison is a child cluster. This one has three managers, but also has additional workers associate it to the cluster. Yeah, all right, we need to connect. Tell bootstrap note, preferably the same note that used to create the original management plaster. It's just on AWS, but I still want to machine Mhm. All right, A few things we have to do to make sure the environment is ready. First thing we're gonna pseudo into route. I mean, we'll go into our releases folder where we have the car's boot strap on. This was the original bootstrap used to build the original management cluster. We're going to double check to make sure our cube con figures there It's again. The one created after the original customers created just double check. That cute conflict is the correct one. Does point to the management cluster. We're just checking to make sure that we can reach the images that everything's working, condone, load our images waken access to a swell. Yeah, Next, we're gonna edit the machine definitions what we're doing here is ensuring that for this cluster we have the right machine definitions, including items like the am I So that's found under the templates AWS directory. We don't need to edit anything else here, but we could change items like the size of the machines attempts we want to use but the key items to ensure where changed the am I reference for the junta image is the one for the region in this case aws region of re utilizing. This was an open stack deployment. We have to make sure we're pointing in the correct open stack images. Yeah, yeah. Okay. Sit the correct Am I save the file? Yeah. We need to get up credentials again. When we originally created the bootstrap cluster, we got credentials made of the U. S. If we hadn't done this, we would need to go through the u A. W s set up. So we just exporting AWS access key and I d. What's important is Kaz aws enabled equals. True. Now we're sitting the region for the new regional cluster. In this case, it's Frankfurt on exporting our Q conflict that we want to use for the management cluster when we looked at earlier. Yeah, now we're exporting that. Want to call? The cluster region is Frankfurt's Socrates Frankfurt yet trying to use something descriptive? It's easy to identify. Yeah, and then after this, we'll just run the bootstrap script, which will complete the deployment for us. Bootstrap of the regional cluster is quite a bit quicker than the initial management clusters. There are fewer components to be deployed, but to make it watchable, we've spent it up. So we're preparing our bootstrap cluster on the local bootstrap node. Almost ready on. We started preparing the instances at us and waiting for the past, you know, to get started. Please the best your node, onda. We're also starting to build the actual management machines they're now provisioning on. We've reached the point where they're actually starting to deploy Dr Enterprise, he says. Probably the longest face we'll see in a second that all the nodes will go from the player deployed. Prepare, prepare Mhm. We'll see. Their status changes updates. It was the first word ready. Second, just applying second. Grady, both my time away from home control that's become ready. Removing cluster the management cluster from the bootstrap instance into the new cluster running a data for us? Yeah, almost a on. Now we're playing Stockland. Thanks. Whichever is done on Done. Now we'll build a child cluster in the new region very, very quickly. Find the cluster will pick our new credential have shown up. We'll just call it Frankfurt for simplicity. A key on customers to find. That's the machine. That cluster stop with three manages set the correct Am I for the region? Yeah, Same to add workers. There we go. That's the building. Yeah. Total bill of time. Should be about fifteen minutes. Concedes in progress. Can we expect this up a little bit? Check the events. We've created all the dependencies, machine instances, machines. A boat? Yeah. Shortly. We should have a working caster in the Frankfurt region. Now almost a one note is ready from management. Two in progress. On we're done. Trust us up and running. >>Excellent. There we have it. We've got our three layered doctor enterprise container cloud structure in place now with our management cluster in which we scrap everything else. Our regional clusters which manage individual aws regions and child clusters sitting over depends. >>Yeah, you can. You know you can actually see in the hierarchy the advantages that that presents for folks who have multiple locations where they'd like a geographic locations where they'd like to distribute their clusters so that you can access them or readily co resident with your development teams. Um and, uh, one of the other things I think that's really unique about it is that we provide that same operational support system capability throughout. So you've got stack light monitoring the stack light that's monitoring the stack light down to the actual child clusters that they have >>all through that single pane of glass that shows you all your different clusters, whether their workload cluster like what the child clusters or usual clusters from managing different regions. Cool. Alright, well, time marches on your folks. We've only got a few minutes left and I got one more video in our last video for the session. We're gonna walk through standing up a child cluster on bare metal. So so far, everything we've seen so far has been aws focus. Just because it's kind of easy to make that was on AWS. We don't want to leave you with the impression that that's all we do, we're covering AWS bare metal and open step deployments as well documented Craftsman Cloud. Let's see it in action with a bare metal child cluster. >>We are on the home stretch, >>right. >>Hello. This demo will cover the process of defining bare metal hosts and then review the steps of defining and deploying a bare metal based doctor enterprise cluster. Yeah, so why bare metal? Firstly, it eliminates hyper visor overhead with performance boost of up to thirty percent provides direct access to GP use, prioritize for high performance wear clothes like machine learning and AI, and support high performance workouts like network functions, virtualization. It also provides a focus on on Prem workloads, simplifying and ensuring we don't need to create the complexity of adding another hyper visor layer in between. So continuing on the theme Why communities and bare metal again Hyper visor overhead. Well, no virtualization overhead. Direct access to hardware items like F p g A s G p, us. We can be much more specific about resource is required on the nodes. No need to cater for additional overhead. We can handle utilization in the scheduling better Onda. We increase the performance and simplicity of the entire environment as we don't need another virtualization layer. Yeah, In this section will define the BM hosts will create a new project. Will add the bare metal hosts, including the host name. I put my credentials. I pay my address, Mac address on, then provide a machine type label to determine what type of machine it is. Related use. Okay, let's get started Certain Blufgan was the operator thing. We'll go and we'll create a project for our machines to be a member off. Helps with scoping for later on for security. I begin the process of adding machines to that project. Yeah. Yeah. So the first thing we had to be in post many of the machine a name. Anything you want? Yeah, in this case by mental zero one. Provide the IAP My user name. Type my password? Yeah. On the Mac address for the active, my interface with boot interface and then the i p m i P address. Yeah, these machines. We have the time storage worker manager. He's a manager. We're gonna add a number of other machines on will speed this up just so you could see what the process. Looks like in the future, better discovery will be added to the product. Okay, Okay. Getting back there. We haven't Are Six machines have been added. Are busy being inspected, being added to the system. Let's have a look at the details of a single note. Mhm. We can see information on the set up of the node. Its capabilities? Yeah. As well as the inventory information about that particular machine. Okay, it's going to create the cluster. Mhm. Okay, so we're going to deploy a bare metal child cluster. The process we're going to go through is pretty much the same as any other child cluster. So credit custom. We'll give it a name. Thank you. But he thought were selecting bare metal on the region. We're going to select the version we want to apply on. We're going to add this search keys. If we hope we're going to give the load. Balancer host I p that we'd like to use out of the dress range update the address range that we want to use for the cluster. Check that the sea idea blocks for the communities and tunnels are what we want them to be. Enable disabled stack light and said the stack light settings to find the cluster. And then, as for any other machine, we need to add machines to the cluster. Here we're focused on building communities clusters. So we're gonna put the count of machines. You want managers? We're gonna pick the label type manager on create three machines. Is a manager for the Cuban a disgusting? Yeah, they were having workers to the same. It's a process. Just making sure that the worker label host like you are so yes, on Duin wait for the machines to deploy. Let's go through the process of putting the operating system on the notes, validating that operating system. Deploying Docker enterprise on making sure that the cluster is up and running ready to go. Okay, let's review the bold events. We can see the machine info now populated with more information about the specifics of things like storage. Yeah, of course. Details of a cluster, etcetera. Yeah, Yeah. Okay. Well, now watch the machines go through the various stages from prepared to deploy on what's the cluster build, and that brings us to the end of this particular do my as you can see the process is identical to that of building a normal child cluster we got our complaint is complete. >>Here we have a child cluster on bare metal for folks that wanted to play the stuff on Prem. >>It's ah been an interesting journey taken from the mothership as we started out building ah management cluster and then populating it with a child cluster and then finally creating a regional cluster to spread the geographically the management of our clusters and finally to provide a platform for supporting, you know, ai needs and and big Data needs, uh, you know, thank goodness we're now able to put things like Hadoop on, uh, bare metal thio in containers were pretty exciting. >>Yeah, absolutely. So with this Doctor Enterprise container cloud platform. Hopefully this commoditized scooping clusters, doctor enterprise clusters that could be spun up and use quickly taking provisioning times. You know, from however many months to get new clusters spun up for our teams. Two minutes, right. We saw those clusters gets better. Just a couple of minutes. Excellent. All right, well, thank you, everyone, for joining us for our demo session for Dr Enterprise Container Cloud. Of course, there's many many more things to discuss about this and all of Miranda's products. If you'd like to learn more, if you'd like to get your hands dirty with all of this content, police see us a training don Miranda's dot com, where we can offer you workshops and a number of different formats on our entire line of products and hands on interactive fashion. Thanks, everyone. Enjoy the rest of the launchpad of that >>thank you all enjoy.

(soft music) >> From around the globe, It's theCube with digital coverage of VeeamON 2020 brought to you by Veeam. Hi buddy. Welcome to the cubes coverage of VeeamON 2020, (laughs) the virtual version of VeeamON. and I'm here with Justin Warren who's the chief analyst and managing director of Pivot Nine. Justin, Good to see you. How are things down under? >> Not too bad. It was a bit of a rough start to the year. But things are looking a little bit better here in the middle of the year. It's tough times. >> And of course Justin, you may, you guys may know, as a many times you post and of course our other almost daily CUBE host these days, Stu Minivan joining us to unpack the Veeam keynotes, the trends in the marketplace. How you doing Stu? >> I'm doing great, Dave. Yeah. As you said, rather than us flying all around the country, we're in doing remote interviews every day, Its different, 2020.(laughs) >> So this has been quite a year, obviously. Because of course it was from Veeam's perspective, started out with that blockbuster exit $5 billion exit to private equity slash VC, insight capital, insight partners which was just an awesome thing for the founders. And some of the employees and actually going forward now, I think the balance of the employees really they'll have an opportunity to grow the valuation of the company even further. I think that's what we've seen with insight. I mean they want exits, so it's like they used to talk about, Ratmir Used to talk about Act Two (laughs) well now we're going to see it play out guys. So just some high level stats, a billion dollars last year in bookings. They're really shifting to an ARR model in a big way, 375,000 customers, 160 countries, 4,200 employees. Justin, do you remember when you first ran into Veeam at like some VMUG somewhere, who are these guys? Wow. They've certainly made it. >> They really have. And it's honest surprising but also not . They've feeling when I first encountered Veeam was that it's like well, who is this people? Yeah. What are they doing? It was very much SMB. It was very much practitioner, a very technical focus and people who used it just loved the product because back then the informal tagline was, it just were. And in those days it really was amazing. That there was a product that was simple and easy to use and worked on it, all of the things that they needed it to do. And I had a very, very VM focused back in that time. Hence the name of the entire company was go Veeam. And to see it grow from that one even then was quite a broad base but a very much an SMB market and see it grow across the entire industry. It's pretty remarkable. There is no really any ... Not many other companies who've pulled off this kind of growth momentum. >> Yeah. I mean Justin I think you nailed it there. I think back it's a company that hasn't stayed at a steady state still though. In the virtualization community, there were ripple effects. When Veeam went beyond just doing VMware and started to do Microsoft. Then a few years ago, I remember after we were doing the Q bed at the show, there was such a real push forward to extend the relationship with Microsoft, to the cloud. One of the things that we think we see loud and clear at this show is that VMware relationship early strong and as VMware goes to various cloud environment, Veeam can go along with that so that the relationship stays strong, but they're also in a lot of the public clouds and expanding beyond what they're doing. Yep. They're moving into the enterprising and I think one of the things we'll dig into is how enterprising is Veeam today. But absolutely it could company that very different than they were two or three years ago. And Dave, as you correctly pointed out now there's not the, who is this weird privately held company? Who's the ownership? I think there's a little bit of a more of a understanding as to, they're a big player in the space. And a little bit more a understanding as to where things go going forward. >> Well, I want to get your take on sort of their, we're going to go through a lot today, but the vision, that Danny Allan laid out in his keynote. And I think it's quite interesting. I mean, given the energy and the VC money coming into the market behind Cohesity and Rubrik the noise that they're making, what he put up as their vision is the most trusted provider of backup solutions, that deliver cloud data management. So as you guys well know, Cohesity and Rubrik really pushing this notion of data management, which means a lot of things to a lot of people. It's interesting to note that Veeam, first of all, new management, new CEO, Danny Allan, and now CTO, and obviously in a strategy role. So he's putting forth this kind of back to basics a mentality but then leapfrogging and trying to leapfrogging the data management narrative into the cloud, bringing cloud into it, super-gluing and cloud and data management which I think is really smart because when you think about multicloud data management for data protection It's got to be about cloud native and it's got to be somebody who's got no agenda around hardware or even necessarily a public cloud agenda. And Veeam wants to the be that Company. What do you think of that messaging Justin? >> I think broadly speaking, I think Veeam can pull it off. I do have some concerns around the whole data management thought. On the first thing of just being able to pull this off across the industry, I think vein is well-placed because it's always been about software. And it's always been about partnership. Though Veeam has been channel , It has been a hundred percent channel back in the day, very, very little direction. If any, at all, they are very strong on partnerships. They will partner with anybody because basically they don't really mind who else you deal with. They just want your backup to be done through Veeam. And the backup is very strong. That is what they are great at. So the risks they may own the data management side is it we've seen this play before pretty much ever backup company at some point just to talk about, Hey, we have a couple of your data. It's kind of sitting there and not really doing anything. What if we would attend this into something else and start using it for other purposes? But it's never really paid off for anybody. No, One's really done anything with their backup data in it in a true sense because we haven't seen anyone else become very good at that and be known throughout the industry of OES. Once you've backed up your data to the scene, you can then do all of these others stuff with it. I can't name anyone who's actually been quite successful at that but I can name plenty of people who've grown. >> Well Commvault is certainly tried actually guys, once you bring up the good competitive slide I want to that's a good lead in Justin. So what this data from our data partner, ETR Enterprise Technology Research, those whose watch our breaking analysis every week you see that we use this data extensively. And basically what we're showing here is the fundamental methodology that ETR uses is this thing called net score, which is kind of like net promoter score. It basically asks customers, are you buying? Are you increasing spending or decreasing spending takes the less subtracted from the more, and then you get a net score. That's the vertical axis. And it's an indicator of spending velocity, the horizontal axis it's labeled market share. It's not like IDC counts market share. It's a measure of mark pervasiveness within the survey. Then it's calculated by the mentions of the vendor divided by the total number of mentions within that sector. Now what we're showing here is a comparison of pure play data protection vendors and you can see there's no Dell EMC there's no IBM because they're not pure plays. I can't cut the data by data protection. So I got put fourth the pure plays. But let's walk through this so you could see here is you've got the pervasive company in the upper left. You can see the net scores and they could see the so the shared ends. This is 1,269 survey respondents. And you can see the shared end is the presence of these companies within that 1269, then CIOs and IT practitioners. So you can see Commvault very high presence but then interestingly and I guess not surprisingly Veeam right there. And then it drops off Veritas, Rubrik and Cohesity, and you can see where the heat map is on the vertical axis Rubrik, One of the highest net score is in the data set, and you've got Cohesity also very high, not as great of a presence in the data set. You can see Veeam very respectable. This was a 15 year old company with a relatively high net score. Really, really respectable, as I say in the solidly in the mid thirties and then Commvault getting into the pink zone and then Veritas in the red zone, low net score. And not as great as you're great at presence, which some concerns there for Veritas. So that's guys, that's the horses on the track. Anything there surprise you? Was it Veritas's position, it doesn't really surprise me, but it is remarkable just how our wife and the rest of the players that they are. And certainly that matches in the conversations the way having here with customers and others in industry. The nine Veritas just does not come out in the way that it used to. It used to be, I would have say that it would be, it used to be neck and neck with Commvault. Now we really don't hear the name Vera Tasman at all. Which is as a long time participant in the industry, Veritas was very much part of my career very early on. They were a stand by name. They were very well respected. But say seeing that sort of thing happened to it a great company, like Veritas it's a bit sad. Really? >> Well, you mean look at you're right. The Veritas was always the gold standard of a company with no hardware agenda. Who's going to be the Veritas of X? You would always use that sort of line or phrase. But now Stu, when I think about the opportunities here, It seems like multicloud is going to within the data protection space, is going to be run by somebody who can do cloud native. So in other words, running cloud native on, Azure, AWS and Google, maybe Alibaba, but cloud native, being able to take advantage of those native services on the cloud. Somebody who's got an on-prem presence who can bring that cloud experience on-prem. Who actually can do it also across clouds, a very, very high performance, low latency, very efficient, low cost. So in thinking about that multi-cloud landscapes, do how do you assess the horses on the track? >> Yeah, well, you know, Dave, first of all, one of the things Justin said, Veeam is partner-driven. One of the conversations I'm having for VeeamON is with the partner Alliance team, they are a hundred percent partner driven. And also for so many years, we talk about one of the negatives about Veeam is, Oh, well, most of their customer base is SMB, well, if you look at the cloud, one of the knocks against cloud for a long time was, Oh, it's just the really small companies that are doing a lot of clouds. Well, my data managers whether I'm a small company or a big company, so a lot of these pieces come together, Veeam has really been able to move into that cloud environment. What they're doing, sans across them . Data protection seems to be one of those areas when you talk about, the mantras, the industry like Amazon and say, okay when are they going to eat your business? Well, you know, Amazon's got a strong storage team. But data protection. They've got some very basic functionality in there but there's a robust ecosystem and companies like Veeam, I can capitalize on. >> Well, you mentioned the there in the enterprise, of course we all know the story of there a couple of years ago, there was a big enterprise, of course, they brought in some executives from VMware, some really high quality folks. They struck relationships with companies like HPE and Cisco. I think HPE in particular is it's paid off quite well but everybody wants to do business with Cisco cause they're very partner friendly and it's interesting. They kind of pull back from that not kind of. They pull back on that major initiative, the high price, direct sales people. And I remember doing a breaking analysis when Veeam got acquired or maybe it was even previous to that and making the comment to that yeah. They had to pull back on that, but I dug into the ETR data. Veeam actually has quite a presence in large companies. Maybe it's division of a large company, or maybe it's shadow IT, I don't know. People who just you don't want the simple backup but they're VMware customers. And it seems to me they really have an opportunity to go up market. Maybe kind of to reset that enterprise strategy. What do you guys think? >> Yeah, I think that's was what they were trying to do a couple of years ago. So I think hotly, they just didn't succeed quickly as they had hoped. There was also a little bit of an issue, which is something I remember speaking to the Retina Mayor about some years ago. About the challenge of being able to serve these different markets, because what SMB wants is quite different to what an enterprise want. And being able to fulfill both of those needs simultaneously from one company it's really challenging because things that you do for enterprise annoy SMB, the things that around ran complexity to be able to deal with the inherently complex environments that are enterprise. SMB just doesn't have that issue. Whereas if you can only do things in SMB type ways that annoys the enterprise, being able to satisfy both of those markets in a way that they both happy with. And so that no one else feels neglected that's pretty much what they wish that were struggling with nothing. So the hot pivot to enterprise they existing customer base, which then was rolling mostly SMB. They started to feel a little bit neglected. No, it was just a bit of a stumble. I think it feels like they've reset now and understood how to do these in a slightly more gentle fashion. But we can call it that. So rather than going for that really aggressive push into enterprise, they are just following the natural momentum, which is people who've come from SMB. And some of those medium companies grow into very large companies and bring them with them and others just that people as they move through their career will grow from a small company to maybe a medium company. And then they'll end up in a division of an enterprise scale and they used to Veeam and they want to bring what they they know in like they want to bring that experience to the company that they now work at. That is a sort of natural flow there I think for them that is only now showing the fruit of what was actually laid down a few years ago. >> Well, and I think there was something else going on there too, which is, we now know the company was positioning for an exit that was up for sale. So enterprise is very expensive, it's time consuming. The ROI is often times very long. That's why you see enterprise startups raising gobs of money and they just ,i think weren't getting the ROI. And when you think about insight, this is one of the more forward thinking, great PE or VC firms they'll live with rule of 40, right, where a rule of 35 or 80 rule of 50, where it's not just about growth, it's about growth plus EBIT. And if you add those up and it adds the 40 or 45 or 35 or whatever their target is, I don't know exactly what Insights looking forward but that's the combination that drives value. So my guess is they wanted to dial up EBIT and give it or the sale. And they might've had specific targets, who knows. That were being negotiated but i think that probably had something to do with it. And as well as you're pointing out, Justin, it takes time but us to If we look into some of the things that we're hearing from the messaging, some of the announcements and we'll get into that. Big, big discussion around digital transformation. One of the first, if not the first to do a backup for office 365, another a new version of Veeam backup for AWS. Oh. So there were some enterprisey types of things that they were there were talking about, a little glimpse at version 11.Any thoughts there, Stu. >> Yeah. Well, David, it's interesting, Justin put up a really good point there when you opt digital transformation Dave. Well, one of the things we've been saying for years, the difference between a company before and after that is you're leveraging the data. So, If I look at Veeam and say, do I protect the data absolutely? Do I secure your data? I'm involved with that. Actually one of the leadership changes, they just hired their first CSO. So bigger push for security, that'll help them a lot in what they do with it, public sector, that's where the CSO actually came from the public by that will help them. But what I didn't, haven't heard as much yet, is okay. I'm a piece of that data. And if you're going to the cloud, I can manage, I can protected and secure it. But how do I help connect people to get more value out of the data and leverage that data? So I think Justin nailed it with that. So many pieces that are important about data that Veeam does do. But that the discussion we always have in AI is be able to take that raw data and converting it into insights and out facts. >> Well, to Justin's point earlier about data management. And I want to to pick up on what you were saying about security, obviously everybody's talking about ransomware, but to me, you're talking about the CSO. The role of the CSO is obviously of course evolving it's Al board level topic. CSO, oftentimes was off as a peer, I say off, but as a peer to the CIO on purpose, they didn't want the CSO to report to the CIO cause it would have been like the Fox watching the hen house. But i think cause it was this sort of failure equals fire mentality and they wanted the truth. But I think now people have transparent discussions at the board about security. Hey, we know we're going to get penetrated. It's all about our response. Obviously we have to deal with the layers, but we're exposed, everybody's exposed. So I think increasingly organizations are realizing that it's a team sport, you've got to get everybody involved, the lines of business, the users being responsible. And of course IT, my point is that security and data protection are now becoming two sides of the same point. Almost like privacy. We've shared that before. So when you think about digital transformation, you think about data protection as part of your security portfolio? Not just something that you bolt on as an afterthought. And I think in many respects, Justin, that's maybe a bigger market opportunity for a lot of these data protection companies and backup companies, than the so-called opaque data management that you're referring to before. >> Yeah. I'd agree with that because what I'm saying from the security side of the market, particularly within large enterprise is a change in mindset from a prevention to a resilient, that kind of mindset around it and how to deal with it. Though previously there was a lot of either we'll just ignore it cause there's not really a problem and it's not going to happen to us. Then it became a kind of a fear response of just, we want to prevent it ever happening to us. Now it's kind of we've gone to an acceptance. And when going through the Kubler Ross. A framework for dealing with grief. People aren't understanding that sooner or later bad things are going to happen to us. What we need to figure out is how we deal with it when it does. And that's the mindset that you need to have when you're talking about data protection. So it's the same kind of mindset that you need for security. And now people are starting to look at, okay, how do we firstly detect if we've actually got a problem, if there's a breach or if there's a risk, how do we notice that we know that that's happening? And then once we noticed that, what do we do about it? So that's things like catching it early so that when you you'll recovery is small, which is the same general idea around software development of fail fast. You want to just pick the failures early so that you can correct them all. Basically if you find yourself in a hole stop digging and then once you've figured that out, okay now how do we recover from this in a way that is minimally disruptive to the business. And that could be like recovering from ransomware, having grilly solid backup. So you can restore weekly, that's the best protection against ransomware that you can have. Then you can start trying to figure out, okay, we know we can recover if it happens to us now let's just try to reduce the number of times that this does actually happen. That's the general idea that I'm seeing come through. More often with CSOs, with CIOs and with board level conversation. >> I want to come back to Justin and then Stu with your final thoughts. Justin, what do you take on this Veeam universal license? Was this a case of, hey we had so much complexity across our portfolio like that you're going to the Italian restaurant, you're just here you want everything in the menu or there's too much to figure out just the order for me. And they're trying to clean that up or do you see this as sort of a more innovative licensing approach? That's more cloud friendly. What do you make of that? >> I think it's a bit of both. think it's part of VeeamON thoughts as well again, from back in the very early parts of the company, the idea was that it just works. It should be simple and easy to use. So it's completely on brand for Veeam to have a simple and easy to use licensing model. There's a lot of criticism from enterprise and particularly from medium and small business, well overly complicated licensing models. We see people wrestling daily with the billing system within AWS. We see people frustrated with the licensing approach of Oracle. We see them seemingly frustrated when you not figuring out exactly what have I lost since then, what happened and what am I not licensed for in, Microsoft ecosystem. So for them to have a simple and easy to use licensing approach, it just fits right in with the rest of what the company is doing. It does also simplify the way that they organize and operate their company, as they have to deal with lots and lots of different partners, having a complicated licensing system on top of all of those other complicated licensing systems would just make their own job much, much harder. So this way it actually works for them as well as for their customers. >> Yeah. Simplicity is the watch word there Stu and I get, I mean, I get the sense in speaking to the customers, partners, that Veeam well has basically has the philosophy make it easy to and we'll sell more. We're not going to try to micromanage, to maximize revenue. You heard this certainly from some of their big partners who said that Veeam made it transparent. Our sales people for commissions and their salespeople and really make it easy to do business with. So Stu I'll give you the last word here. >> Yeah. So I think, as you mentioned, Veeam also listening and seeing what their partners are doing. So we've watched companies like AWS, trying to make a little bit simpler as to if I'm choosing compute, I don't have to be locked into one model a aisle, pay those across the environment or pure storage and other partner of Veeams. If I stay a customer, I make it easy to be able to move from one generation the next though, that cloud like model absolutely is what we expect. And when you talk to customers today, we know the only constant is change. I actually loved in the keynote. There was a I believe it was Satya Nadella that they quoted and said that, we've seen more change in the last two months that we normally would see in a decade. So Veeam being agile, moving, listening to their customers, learning with their partners and making sure that they've got things in the modern consumption model. >> Well, guys, thanks for helping us break down the VeeamON 2020, some of the trends in the market place.Some of the commentary and the keynote. Justin Warren Stu Minivan. Appreciate your time. >> Thank you very much. >> Thanks Dave. >> I thank you for watching everybody. This is Dave Vellante for Stu and Justin and the entire cube team, people right there. We'll be back with our coverage of VeeamON 2020, right after this short break. (soft 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] [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