>> From theCUBE Studios in Palo Alto in Boston, bringing you data driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. >> After a two-year epic run in tech, 2022 has been an epically bad year. Through yesterday, The NASDAQ composite is down 30%. The S$P 500 is off 21%. And the Dow Jones Industrial average 16% down. And the poor holders at Bitcoin have had to endure a nearly 60% decline year to date. But judging by the attendance and enthusiasm, in major in-person tech events this spring. You'd never know that tech was in the tank. Moreover, walking around the streets of Las Vegas, where most tech conferences are held these days. One can't help but notice that the good folks of Main Street, don't seem the least bit concerned that the economy is headed for a recession. Hello, and welcome to this weeks Wiki Bond Cube Insights powered by ETR. In this Breaking Analysis we'll share our main takeaways from the first half of 2022. And talk about the outlook for tech going forward, and why despite some pretty concerning headwinds we remain sanguine about tech generally, but especially enterprise tech. Look, here's the bumper sticker on why many folks are really bearish at the moment. Of course, inflation is high, other than last year, the previous inflation high this century was in July of 2008, it was 5.6%. Inflation has proven to be very, very hard to tame. You got gas at $7 dollars a gallon. Energy prices they're not going to suddenly drop. Interest rates are climbing, which will eventually damage housing. Going to have that ripple effect, no doubt. We're seeing layoffs at companies like Tesla and the crypto names are also trimming staff. Workers, however are still in short supply. So wages are going up. Companies in retail are really struggling with the right inventory, and they can't even accurately guide on their earnings. We've seen a version of this movie before. Now, as it pertains to tech, Crawford Del Prete, who's the CEO of IDC explained this on theCUBE this very week. And I thought he did a really good job. He said the following, >> Matt, you have a great statistic that 80% of companies used COVID as their point to pivot into digital transformation. And to invest in a different way. And so what we saw now is that tech is now where I think companies need to focus. They need to invest in tech. They need to make people more productive with tech and it played out in the numbers. Now so this year what's fascinating is we're looking at two vastly different markets. We got gasoline at $7 a gallon. We've got that affecting food prices. Interesting fun fact recently it now costs over $1,000 to fill an 18 wheeler. All right, based on, I mean, this just kind of can't continue. So you think about it. >> Don't put the boat in the water. >> Yeah, yeah, yeah. Good luck if ya, yeah exactly. So a family has kind of this bag of money, and that bag of money goes up by maybe three, 4% every year, depending upon earnings. So that is sort of sloshing around. So if food and fuel and rent is taking up more, gadgets and consumer tech are not, you're going to use that iPhone a little longer. You're going to use that Android phone a little longer. You're going to use that TV a little longer. So consumer tech is getting crushed, really it's very, very, and you saw it immediately in ad spending. You've seen it in Meta, you've seen it in Facebook. Consumer tech is doing very, very, it is tough. Enterprise tech, we haven't been in the office for two and a half years. We haven't upgraded whether that be campus wifi, whether that be servers, whether that be commercial PCs as much as we would have. So enterprise tech, we're seeing double digit order rates. We're seeing strong, strong demand. We have combined that with a component shortage, and you're seeing some enterprise companies with a quarter of backlog, I mean that's really unheard of. >> And higher prices, which also profit. >> And therefore that drives up the prices. >> And this is a theme that we've heard this year at major tech events, they've really come roaring back. Last year, theCUBE had a huge presence at AWS Reinvent. The first Reinvent since 2019, it was really well attended. Now this was before the effects of the omicron variant, before they were really well understood. And in the first quarter of 2022, things were pretty quiet as far as tech events go But theCUBE'a been really busy this spring and early into the summer. We did 12 physical events as we're showing here in the slide. Coupa, did Women in Data Science at Stanford, Coupa Inspire was in Las Vegas. Now these are both smaller events, but they were well attended and beat expectations. San Francisco Summit, the AWS San Francisco Summit was a bit off, frankly 'cause of the COVID concerns. They were on the rise, then we hit Dell Tech World which was packed, it had probably around 7,000 attendees. Now Dockercon was virtual, but we decided to include it here because it was a huge global event with watch parties and many, many tens of thousands of people attending. Now the Red Hat Summit was really interesting. The choice that Red Hat made this year. It was purposefully scaled down and turned into a smaller VIP event in Boston at the Western, a couple thousand people only. It was very intimate with a much larger virtual presence. VeeamON was very well attended, not as large as previous VeeamON events, but again beat expectations. KubeCon and Cloud Native Con was really successful in Spain, Valencia, Spain. PagerDuty Summit was again a smaller intimate event in San Francisco. And then MongoDB World was at the new Javits Center and really well attended over the three day period. There were lots of developers there, lots of business people, lots of ecosystem partners. And then the Snowflake summit in Las Vegas, it was the most vibrant from the standpoint of the ecosystem with nearly 10,000 attendees. And I'll come back to that in a moment. Amazon re:Mars is the Amazon AI robotic event, it's smaller but very, very cool, a lot of innovation. And just last week we were at HPE Discover. They had around 8,000 people attending which was really good. Now I've been to over a dozen HPE or HPE Discover events, within Europe and the United States over the past decade. And this was by far the most vibrant, lot of action. HPE had a little spring in its step because the company's much more focused now but people was really well attended and people were excited to be there, not only to be back at physical events, but also to hear about some of the new innovations that are coming and HPE has a long way to go in terms of building out that ecosystem, but it's starting to form. So we saw that last week. So tech events are back, but they are smaller. And of course now a virtual overlay, they're hybrid. And just to give you some context, theCUBE did, as I said 12 physical events in the first half of 2022. Just to compare that in 2019, through June of that year we had done 35 physical events. Yeah, 35. And what's perhaps more interesting is we had our largest first half ever in our 12 year history because we're doing so much hybrid and virtual to compliment the physical. So that's the new format is CUBE plus digital or sometimes just digital but that's really what's happening in our business. So I think it's a reflection of what's happening in the broader tech community. So everyone's still trying to figure that out but it's clear that events are back and there's no replacing face to face. Or as I like to say, belly to belly, because deals are done at physical events. All these events we've been to, the sales people are so excited. They're saying we're closing business. Pipelines coming out of these events are much stronger, than they are out of the virtual events but the post virtual event continues to deliver that long tail effect. So that's not going to go away. The bottom line is hybrid is the new model. Okay let's look at some of the big themes that we've taken away from the first half of 2022. Now of course, this is all happening under the umbrella of digital transformation. I'm not going to talk about that too much, you've had plenty of DX Kool-Aid injected into your veins over the last 27 months. But one of the first observations I'll share is that the so-called big data ecosystem that was forming during the hoop and around, the hadoop infrastructure days and years. then remember it dispersed, right when the cloud came in and kind of you know, not wiped out but definitely dampened the hadoop enthusiasm for on-prem, the ecosystem dispersed, but now it's reforming. There are large pockets that are obviously seen in the various clouds. And we definitely see a ecosystem forming around MongoDB and the open source community gathering in the data bricks ecosystem. But the most notable momentum is within the Snowflake ecosystem. Snowflake is moving fast to win the day in the data ecosystem. They're providing a single platform that's bringing different data types together. Live data from systems of record, systems of engagement together with so-called systems of insight. These are converging and while others notably, Oracle are architecting for this new reality, Snowflake is leading with the ecosystem momentum and a new stack is emerging that comprises cloud infrastructure at the bottom layer. Data PaaS layer for app dev and is enabling an ecosystem of partners to build data products and data services that can be monetized. That's the key, that's the top of the stack. So let's dig into that further in a moment but you're seeing machine intelligence and data being driven into applications and the data and application stacks they're coming together to support the acceleration of physical into digital. It's happening right before our eyes in every industry. We're also seeing the evolution of cloud. It started with the SaaS-ification of the enterprise where organizations realized that they didn't have to run their own software on-prem and it made sense to move to SaaS for CRM or HR, certainly email and collaboration and certain parts of ERP and early IS was really about getting out of the data center infrastructure management business called that cloud 1.0, and then 2.0 was really about changing the operating model. And now we're seeing that operating model spill into on-prem workloads finally. We're talking about here about initiatives like HPE's Green Lake, which we heard a lot about last week at Discover and Dell's Apex, which we heard about in May, in Las Vegas. John Furrier had a really interesting observation that basically this is HPE's and Dell's version of outposts. And I found that interesting because outpost was kind of a wake up call in 2018 and a shot across the bow at the legacy enterprise infrastructure players. And they initially responded with these flexible financial schemes, but finally we're seeing real platforms emerge. Again, we saw this at Discover and at Dell Tech World, early implementations of the cloud operating model on-prem. I mean, honestly, you're seeing things like consoles and billing, similar to AWS circa 2014, but players like Dell and HPE they have a distinct advantage with respect to their customer bases, their service organizations, their very large portfolios, especially in the case of Dell and the fact that they have more mature stacks and knowhow to run mission critical enterprise applications on-prem. So John's comment was quite interesting that these firms are basically building their own version of outposts. Outposts obviously came into their wheelhouse and now they've finally responded. And this is setting up cloud 3.0 or Supercloud, as we like to call it, an abstraction layer, that sits above the clouds that serves as a unifying experience across a continuum of on-prem across clouds, whether it's AWS, Azure, or Google. And out to both the near and far edge, near edge being a Lowes or a Home Depot, but far edge could be space. And that edge again is fragmented. You've got the examples like the retail stores at the near edge. Outer space maybe is the far edge and IOT devices is perhaps the tiny edge. No one really knows how the tiny edge is going to play out but it's pretty clear that it's not going to comprise traditional X86 systems with a cool name tossed out to the edge. Rather, it's likely going to require a new low cost, low power, high performance architecture, most likely RM based that will enable things like realtime AI inferencing at that edge. Now we've talked about this a lot on Breaking Analysis, so I'm not going to double click on it. But suffice to say that it's very possible that new innovations are going to emerge from the tiny edge that could really disrupt the enterprise in terms of price performance. Okay, two other quick observations. One is that data protection is becoming a much closer cohort to the security stack where data immutability and air gaps and fast recovery are increasingly becoming a fundamental component of the security strategy to combat ransomware and recover from other potential hacks or disasters. And I got to say from our observation, Veeam is leading the pack here. It's now claiming the number one revenue spot in a statistical dead heat with the Dell's data protection business. That's according to Veeam, according to IDC. And so that space continues to be of interest. And finally, Broadcom's acquisition of Dell. It's going to have ripple effects throughout the enterprise technology business. And there of course, there are a lot of questions that remain, but the one other thing that John Furrier and I were discussing last night John looked at me and said, "Dave imagine if VMware runs better on Broadcom components and OEMs that use Broadcom run VMware better, maybe Broadcom doesn't even have to raise prices on on VMware licenses. Maybe they'll just raise prices on the OEMs and let them raise prices to the end customer." Interesting thought, I think because Broadcom is so P&L focused that it's probably not going to be the prevailing model but we'll see what happens to some of the strategic projects rather like Monterey and Capitola and Thunder. We've talked a lot about project Monterey, the others we'll see if they can make the cut. That's one of the big concerns because it's how OEMs like the ones that are building their versions of outposts are going to compete with the cloud vendors, namely AWS in the future. I want to come back to the comment on the data stack for a moment that we were talking about earlier, we talked about how the big data ecosystem that was once coalescing around hadoop dispersed. Well, the data value chain is reforming and we think it looks something like this picture, where cloud infrastructure lives at the bottom. We've said many times the cloud is expanding and evolving. And if companies like Dell and HPE can truly build a super cloud infrastructure experience then they will be in a position to capture more of the data value. If not, then it's going to go to the cloud players. And there's a live data layer that is increasingly being converged into platforms that not only simplify the movement in ELTing of data but also allow organizations to compress the time to value. Now there's a layer above that, we sometimes call it the super PaaS layer if you will, that must comprise open source tooling, partners are going to write applications and leverage platform APIs and build data products and services that can be monetized at the top of the stack. So when you observe the battle for the data future it's unlikely that any one company is going to be able to do this all on their own, which is why I often joke that the 2020s version of a sweaty Steve Bomber running around the stage, screaming, developers, developers developers, and getting the whole audience into it is now about ecosystem ecosystem ecosystem. Because when you need to fill gaps and accelerate features and provide optionality a list of capabilities on the left hand side of this chart, that's going to come from a variety of different companies and places, we're talking about catalogs and AI tools and data science capabilities, data quality, governance tools and it should be of no surprise to followers of Breaking Analysis that on the right hand side of this chart we're including the four principles of data mesh, which of course were popularized by Zhamak Dehghani. So decentralized data ownership, data as products, self-serve platform and automated or computational governance. Now whether this vision becomes a reality via a proprietary platform like Snowflake or somehow is replicated by an open source remains to be seen but history generally shows that a defacto standard for more complex problems like this is often going to emerge prior to an open source alternative. And that would be where I would place my bets. Although even that proprietary platform has to include open source optionality. But it's not a winner take all market. It's plenty of room for multiple players and ecosystem innovators, but winner will definitely take more in my opinion. Okay, let's close with some ETR data that looks at some of those major platform plays who talk a lot about digital transformation and world changing impactful missions. And they have the resources really to compete. This is an XY graphic. It's a view that we often show, it's got net score on the vertical access. That's a measure of spending momentum, and overlap or presence in the ETR survey. That red, that's the horizontal access. The red dotted line at 40% indicates that the platform is among the highest in terms of spending velocity. Which is why I always point out how impressive that makes AWS and Azure because not only are they large on the horizontal axis, the spending momentum on those two platforms rivals even that of Snowflake which continues to lead all on the vertical access. Now, while Google has momentum, given its goals and resources, it's well behind the two leaders. We've added Service Now and Salesforce, two platform names that have become the next great software companies. Joining likes of Oracle, which we show here and SAP not shown along with IBM, you can see them on this chart. We've also plotted MongoDB, which we think has real momentum as a company generally but also with Atlas, it's managed cloud database as a service specifically and Red Hat with trying to become the standard for app dev in Kubernetes environments, which is the hottest trend right now in application development and application modernization. Everybody's doing something with Kubernetes and of course, Red Hat with OpenShift wants to make that a better experience than do it yourself. The DYI brings a lot more complexity. And finally, we've got HPE and Dell both of which we've talked about pretty extensively here and VMware and Cisco. Now Cisco is executing on its portfolio strategy. It's got a lot of diverse components to its company. And it's coming at the cloud of course from a networking and security perspective. And that's their position of strength. And VMware is a staple of the enterprise. Yes, there's some uncertainty with regards to the Broadcom acquisition, but one thing is clear vSphere isn't going anywhere. It's entrenched and will continue to run lots of IT for years to come because it's the best platform on the planet. Now, of course, these are just some of the players in the mix. We expect that numerous non-traditional technology companies this is important to emerge as new cloud players. We've put a lot of emphasis on the data ecosystem because to us that's really going to be the main spring of digital, i.e., a digital company is a data company and that means an ecosystem of data partners that can advance outcomes like better healthcare, faster drug discovery, less fraud, cleaner energy, autonomous vehicles that are safer, smarter, more efficient grids and factories, better government and virtually endless litany of societal improvements that can be addressed. And these companies will be building innovations on top of cloud platforms creating their own super clouds, if you will. And they'll come from non-traditional places, industries, finance that take their data, their software, their tooling bring them to their customers and run them on various clouds. Okay, that's it for today. Thanks to Alex Myerson, who is on production and does the podcast for Breaking Analysis, Kristin Martin and Cheryl Knight, they help get the word out. And Rob Hoofe is our editor and chief over at Silicon Angle who helps edit our posts. Remember all these episodes are available as podcasts wherever you listen. All you got to do is search Breaking Analysis podcast. I publish each week on wikibon.com and siliconangle.com. You can email me directly at david.vellante@siliconangle.com or DM me at dvellante, or comment on my LinkedIn posts. And please do check out etr.ai for the best survey data in the enterprise tech business. This is Dave Vellante for theCUBE's Insights powered by ETR. Thanks for watching be well. And we'll see you next time on Breaking Analysis. (upbeat music)

>>The cube presents HPE discover 2022 brought to you by HPE. >>Hello, everybody. Welcome to day three of the Cube's coverage of HPE discover 2022 we're live from Las Vegas and the Venetian convention center. This is I, I counted him up. I think this is the 14th HP HP slash HPE. Discover that we've done really excited to welcome in Alexia Clements. She's the vice president of go to market for HPE GreenLake cloud services. That's all the rage everybody's talking about. Green, all the wood behind the arrow, as the saying goes, welcome to the queue. Good to see >>You. Thank you so much for having me thrilled to be here. >>You walk up Janet Jackson last night, >>Epic. Wow. She killed it. She was awesome. >>I thought the band was super tight, but the other thing was the place was >>Packed. It was >>Nice. You know, what happens is a lot of time they put the band in the getaway day, you know, and nobody stays, but wow, the, the hall was jammed. >>It was great. It was, you could feel the momentum and the excitement. And it was just a great way to, to kind of end the, the HP discover. So it was great. >>Yeah. I mean, I, I mentioned that we've been to a lot of HP slash HPE discovers and, and this one was different in the sense that I think first of all, 8,000 people, yep. People are excited to get back together, but I think, you know, HPE has a spring in its step and the customers are kind of interested. It's much more focused than some of the past HPE discoverers, which was kind of hard to get my hands around. Sometimes the business was sort of an Antonio's pulled that together. So what's changed since the last time we were face to face. >>We're transforming and hope you all saw that on the, on the floor here. So, um, we're absolutely trans going through a transformation and, you know, I, I think we're, you know, we're shifting to an edge to cloud platform company. And with that, it's, it's how we approach our customers differently and our partners and, you know, we're hoping that, uh, we showed this week and that, that we're different and we're transforming. >>So how do you spend your time Mo mostly in front of customers having conversations about what, what their needs are and aligning is that right? >>Yeah. So, um, I, I lead the, the go to market for GreenLake. So that's everything around how we're driving our as a service go to market strategy, how we're driving programs, enablement, how we're really in the end, how we're executing on that as a service strategy from a sales perspective. >>So what do you hear? Of course, a lot of that involves partners. Yep. Right. I mean, that's kind of the route to market. Absolutely. The HPE prefers for obvious reasons, although others don't necessarily share that, but, but, so what are you hearing from the partner ecosystem and the customers that their biggest challenges are now that we're entering the let's call it the post isolation economy? <laugh> >>Yeah. I mean, the reality is, is digital transformations are hard and I think some customers, um, who haven't necessarily moved forward on it or, you know, maybe they move forward and they're realizing, Hey, I'm stuck and I'm not, I'm not getting to where I wanna be and really, you know, driving that end state. So, I mean, I, I would just say overall, I think things are like, customers are, are struggling if they didn't, you know, they're falling behind a little bit. And I think through the conversations that we're having and through HP green, like it gives customers choice. And so really, um, I mean, what, you know, I spend my time with, and, and when we're talking to customers and partners, it's about helping customers on that digital transformation journey and understanding what are they trying to drive? What business outcomes are they trying to drive and how we can help them get there. So >>I, I often call it the force March to digital yep. With the pandemic. Um, and, and I, I was looking at a survey recently, I think it was put on by couch base. And it was probably on a thousand respondents and it was a CIO survey and they asked who's, who's responsible for the digital transformation at the organization and overwhelmingly it was the it organization. And I said, uhoh, that's the problem now. But it made sense to me because when the economy shut down, everybody went to it and said help, right. Make this work somehow. Right. But, but what, that doesn't seem to me to be the right prescription for a successful digital transformation. Do you agree with that? And what do you see as a successful template for DX? >>Well, I think what, what we see is that really the lines of business are desperate to move fast and they're really looking for their it partners to help them in that journey and, and, and drive, you know, whether it be, you know, drive them, you know, drive orders, drive, you know, they need it to help them in that journey. And so really it's gotta be a partnership between the two organizations. And what we're trying to do with HP GreenLake is kind of abstract that almost. So, Hey, we're gonna give it to you in an, as a service and you're gonna get all of these components. And all you have to think about is where do I need to grow and what are the outcomes that I'm looking for? So that's what it's gotta be. There's gotta be tight alignment, I think between the lines of business and it, and sometimes those two don't know how to talk to each other. >>Mm-hmm <affirmative> so that's another way of, of really trying to speak to the business leaders and say, what are you trying to do? Where do you need to go? And what do you need to get? And, and a lot of times they don't even know what they need to get there. So that's where we need to have those different conversations with our customers to, and that's where we look for our partners to help us in that. So really having those different conversations to progress, um, what, you know, what customers are really looking to, to drive, >>How, how does GreenLake specifically accelerate that transformation? Where does it fit? Maybe you can kind of take us through, you know, a, a generic example of how that works. >>Yeah. I mean, a great example is, you know, especially with the pandemic is desktop, Hey, you now need to, you know, everybody's working from different locations. So, you know, desktop as a service VDI as a service, and, you know, you're putting it in a, you know, per whatever, you know, per you can, whatever variable pricing you want, but think about it, you have that one pay as you go. And so the it organization, all they have to think about is that's my, you know, per, per unit price there. So that's a great example of how we saw, like, especially during the pandemic, that was something that was, you know, a huge area of focus organizations. What's >>The spectrum that you see in terms of, you know, the maturity model, if you will, a digital transformation. I mean, if you weren't in a digital business during the pandemic, you were pretty much out of business. Yeah. And with very few exceptions. Um, and so, okay. So on the one end, you have folks that sort of were forced into it. You, my forced March scenario, others were actually moving quite a bit along before the pandemic, others were kind of given at lip service and maybe doing a few projects. What do you see as that spectrum? >>I think if you're not transforming, you're falling behind. And so everybody needs to be, you know, looking to the future and understanding, you know, really trying to get aggressive on that. And that's what we're seeing. We're seeing companies who, you know, aren't moving fast on that or falling behind. >>Do you see a bifurcation? I'm sure you do those that say, yeah, I want as a service and others that say, look, I I'm really well capitalized. I'm gonna gimme the, gimme the CapEx. I'm gonna put it in and run it myself. And is there a relationship between that approach and their digital transformation maturity, or is it kind of just really their preference? >>I, I mean, for us, we're meeting customers where they're at on their journey and their multi-cloud journey. So some, and, and what I'm seeing is that every customer today has multiple clouds, whether that be their, you know, their kind of, MultiGen it, the, the legacy stuff that they've gotta deal with. They've got stuff in public clouds, and they're trying to really transform and figure out how do I work all of that in like, how do I move forward with that new operating model? And so what I'm seeing is, you know, we're gonna meet customers where they're at on their journey. So some are gonna continue to go down that path in a, how they've always purchased their it. And others are really, you know, more often than not, we're seeing, they want that as a service cloudlike to have all the benefits of cloud, but yet still have it on their prem or in a colo or, you know, at the edge. So I do see some of those customers who are thinking differently, right. That, and they're the ones that are more apt to be a little bit more aggressive on their digital transformation. They're, they're open to the possibility if that makes sense. No, >>It does. It makes total sense. I, I, I think, you know, on the one hand they're a lot of customers are trying to build their own cloud. Yep. Um, so you mention multicloud, I'm not gonna go to Amazon to help me with my multicloud strategy. That's not, that's not gonna be my preferr. Yeah. I might talk to Microsoft about it a little bit. Google's got Antos and that's kind of interesting, but you know, Google's not enterprise, they got good data, but so, but there are other choices out there. Why HPE for my cloud hybrid multi-cloud strategy, give us the >>Sticker. It's, it's the best of both worlds for customers. So it enables them to have the security. It enables them to grow, to, to be in their data centers or in colos at the edge. It allows them to not over provision. It allows them to pay as they go and pay as they grow there's. Um, and then it also really is that ease factor. So it it's that thinking about it as I have, I already, I know what my pricing is. I know what that predictability is from a pricing perspective and what my costs are gonna be. So all of those things really re that all those messages resonate with customers, >>Right? L thanks so much for coming on. We got the trains are backing up super tight schedule today. This is wall to wall coverage of HPE. Discover. Thank you. Thank >>You so much for having me appreciate it. >>You're SU very welcome. All right. Keep it right there. Dave ante is here. John furrier, HPE discover 2022 from Las Vegas. We're live. We'll be right back.

>>Hello, and welcome to this cubes presentation with unstoppable domains. It's a showcase we're featuring all the best content in web three. And with unstabled a showcase I'm John furrier, your host of the cube. We've got a great guest here, Matt Miscavige. Covich who's the chief revenue officer of unstoppable domains. Matt, welcome to the showcase. Appreciate it. >>Thank you for having me. So >>The theme of this segment is the potential of the web three marketplace with unstoppable domains, the chief revenue officer, you guys have a very intriguing, interesting concept. That's going extremely well. Congratulations, but you're using NFTs for access and domains. Of course, the, the metaverse is huge. People want their own domains, but it's not just like real estate in the sense of a website. It's bigger than that. It's a lot going on. So take us through what is the value proposition and what is the product? >>Absolutely. So for the past 20 years, most of us have been interacting on the internet. Using usernames issued to us by big corporations like Facebook, Google, Twitter, tech talks, Snapchat, et cetera. Whenever we get these usernames for free it's because we in our data are the product as some of the recent leaks. And the media has shown incentives. Individuals and companies are not always aligned. And most importantly, individuals are not in control of their own digital identity and the data, which means they can economically benefit from the value they create online. Think of Twitter as a two-sided marketplace with 0% revenue share back to its creators. We're now having in the creator economy and we believe that individuals should see the economic rewards of what they do in create online. That's all we're trying to do here at unstoppable domains is provide user own take control identity to four and a half billion internet users. >>It's interesting to see change that's happening with web three. And just in cultural terms, users are expecting to be part of the creative, the personality of the company. There's this almost this disintermediation of the middleman. You know, whether it's an ad network or a gatekeeper of any kind people going direct, right? So if I'm an artist, I can go direct to my fans. >>Exactly. So web through really shifts the power away from aggregators, aggregators and marketplaces have been some of the best business models. The last 20 years onto the internet, the web three is going to dramatically change that over the next decade, paying more power back in the hands of consumers. >>What type of companies do you guys work with and partner with that we see out there, what's give us some examples of the kinds of companies you're doing business with and partnering with. >>Yeah. So let's talk about use cases. First actually is the big use case that we identified initially for NFT domain names was around cryptocurrency transfers. Anyone who's ever bought cryptocurrency and tried to transfer it between the council while it's is familiar with these awkwardly long hexadecimal strings of random numbers and letters, where if you make a single type of money is lost forever. That's a pretty scary experience that exists today in our $2 trillion asset class with 250 million users. So the first set of partners that we worked on integrating with who actually cook the wilds and exchanges. So we will allow users to do is replace all their long hexadecimal wallet addresses with a single human readable name, like John dot NFT or Maxim needs give each dot crypto to allow for simple crypto transfers. >>And how did the exchange work with you guys on that as it is? Is it a plugin? Is it co-locating code together? What's the, what's the, what's the relationship between exchanges and unstoppable domains? >>Yeah, absolutely. A great question. So exchange has actually have to do a little bit of an engineering lift to work with us, and they can do that by either using our resolution libraries or using one of our API APIs or in order to look up an unstoppable name and figure out all the wallet addresses that's associated with that name. So today we work with dozens of the world's top exchanges and wallets ranging from Oko DX to Coinbase wallet, to trust wallet, to bread wallet, and many, many others. >>I got to ask you on the wallet side, is that a requirement in terms of having specific code and are there wallets that you work well with? Explain the wallet dynamic between unstoppable domains and wallets. >>Yeah. So while it's all have this huge usability problem for their users, because every single cryptocurrency held by every single one of their users has a different hexadecimal wallet address. And once again, every user is subject to the same human fallacies and errors, where they make a single type where their money can be lost forever. So we enable these wallets to do is to make crypto transfer as simple and as less scary than the current status code by giving the users on a sub well name that they can use to attach to all the waltz addresses on the backend. So companies like trust world, for example, which has 10 million users or Coinbase wallet. When you go to the crypto transfer fields, they can just type in an unstoppable name. They'll correctly, route the currency to the right person, to the right world, without any chance for human error. >>You know, when these big waves come, I gotta ask you this question. Cause a lot of people in the mainstream are getting into it. Now reminds me of the web wave that hit the big thing was how many people are coming online. It was one of the key metrics and how many web pages are being developed was another metric, which meant that people were building out web pages. And it's hard to look back and think, wow, that was actually a KPI. So internet users and webpages were the two proxies cause then search and just came out and everything else happened. So I'm going to ask you, there are people watching, they're seeing that on commercials on TV, they're seeing it everywhere stadiums are named after crypto companies. So the bottom line is people want to know how NFT domains take the fear out of working with crypto and sending crypto. >>Yeah, absolutely. So imagine if we had to navigate the web using IP addresses rather than typing in google.com, you'd have to type in a random string of words and numbers that you'd have to memorize. That would be super painful for users. And didn't, it wouldn't have gotten to where it is today with this, you know, almost 5 billion people online, the history of computer networks. We have human readable naming systems built on top. In every single instance. It's almost crazy that we got to a $2 trillion asset class with 250 million users worldwide 13 years after this, the Toshi white paper without a human readable naming system, other than supple domains and a few of our competitors, that's a fundamental problem that we need to solve in order to go from 250 million crypto users in 2022 to 5 billion crypto users, a decade from now. >>And just to point out and not to look back and maybe make a correlation, but I will, if you look at the naming system of DNS, what it did to IP addresses, that's one major innovation that enabled the web. Then you look at what keyword navigation has done on top of DNS, what that did for the industry. And that basically birthed Googled keywords, basically ads. So that's trillions and trillions of dollars again. Now shifting to you guys, is that how you see it? Obviously it's decentralized, so what's different. Okay. I get, so if you compare, Hey, Google was successful, you know, keyword advertising industry for less than 25 years or 20 years. >>Yeah. Yeah. What's different. Now is the technology inflection points. So blockchains have evolved to a point where they enable high throughput, high transaction volume and true decentralized ownership. The NFT standard, which is only a couple of years old know, has taken off massively around trading of profile pictures like crypto punks and the boy apes yacht club where they use cases extended much more than just, you know, a cool JPEG that goes up in value two or three X year over year. There is the true use case here around ownership of identity ownership over a data set, decentralized log-in authentication and permission data sharing. One of the sad things that happened in Jeanette on the internalized decade really was that the platforms built out have now allowed developers to built on top of them and a trustless permissionless way. Developers who build applications on top of some of the early monopolies in the last decade, got the rules changed on them. APIs, cutoff, new fees instituted. That's not going to happen in web three because all permissionless custody in a user's own wallet, we cannot take the way they will continue to exist in eternity, regardless of what happens to unstoppable domains, which gives developers a lot more confidence in building new products for the web three identity standard that we're building out. >>You guys amazing is that's a whole nother generational shift. I'm always been a big fan of abstractions when innovation is needed, when they're problems that need to be solved, messes to be cleaned up. Good abstraction layer on top of new architecture is really, really phenomenal. I guess the key question for I have for you is, you know, the queue, we have all this video where where's our NFT should, how should we implement NFTs? >>There's a couple of different ways you could think about it. You could do proof of attendance, protocol NFTs, which are really interesting way for users to show that they were at particular events. So just in the same way that people collect, t-shirts some conferences, people will be collecting. And if Ts to show, there were in person attending in person cultural moments, whether they were acquired an event online or offline, you could do NFTs for employees to show that they were at your company during certain periods of the company's growth. So think of replacing the resume with a cryptographically secure resume like this on the blockchain and perpetuity. Now more than half of all the resumes contain lies, which is a pretty gnarly problem as a hiring manager, or you constantly have to sort through as ways that this can impact that side of the market as well. >>I saw some, and I think it was a use case for everything. Appreciate that. And of course we can have the most favorite, cute moments. It could be a cube host NFT at 40 apes out there. Why not have a board cube host going on and, and >>Auction for charity on open? >>All right, great stuff. Now let's get into some of the cool tech nerd stuff, which is really the login piece, which I think is fascinating. The having NFTs be a login mechanism is another great innovation. Okay. So this is cool. Cause it's like think of it as one click and FTS, if you will. What's the response been on this? Log-in with unstoppable for that product? What some of the use gates is. Can you give some examples of the momentum and traction? >>Yeah, absolutely. So we launched the product less than 90 days ago. We already have 90 committed or integrated partners live today with a login product. And this replaces login with Google login with Facebook, with a way that's user owned and user controlled. And over time, people will be capturing additional information back to their NFP domain names, such as their reputation, their history, things they've done online and be able to permission to share that with applications that they interact with in order to get any rewards, once you own all your data and you can choose to share it with companies or incentivize you to share data. For example, imagine you just bought a new house and you have 3000 square feet to furnish. You could tell that fact and prove it to a company like Wayfair. Would they be incentivized to give you discounts? We're spending 10, 20, $30,000 and you'll do all of your purchasing there rather than spread across other e-commerce retailers. For sure they would. But right now, when you go to that website, you're just another random email address. They have no idea who you are, what you've done, what your credit score is, whether you house buyer or not. But if you could permission to share that to using a log-in open software product, I mean the web would just be much, much different. >>And I think one of the things too, as these, I call them analog old school companies, old guard companies is referred to in the cube talk here, but we were still always called that old guard is the people who aren't innovating. You could think about companies having more community too, because if you have more sharing and you have this marketplace concept and you have these new dynamics of how people are working together, sharing will provide more transparency, but yet security on identity. Therefore things are going to be happening organically. That's a community dynamic. What's your view on that? And what's your reaction >>Communities are such an important part of web three and the cryptos ecosystem in general, people are very tightly knit and they all support each other. There's a huge amount of collaboration in this space because we're all trying to onboard the next billion users into the ecosystem. And we know we have some fundamental challenges and problems to solve, whether it's complex wallet addresses, whether it's the lack of portable data sharing, whether it's just simple education, right? I'm sure, you know, tens of millions of people got into crypto for the first time during the super bowl face on some of those awesome ads that ran. >>Yeah. Love the QR code. That's a direct response. I remember when the QR code has been around for a long time. I remember in the nineties, late nineties, it was a thing, a device at red QR codes that did navigation to a webpage. So I mean, QR codes are super cool, great way to get, and we all using it to, with the pandemic to ordering food. So I think QR codes are here to stay. In fact, we should have a QR code on all of our images here on the screen too. So we'll work on that, but I gotta ask you on the project side, now let's get into the devs and kind of the applications, the users that are adopting unstoppable and this new way of doing things, why are they gravitating towards this login concepts? Can you give some examples and put, give some color commentary to why are these D application distribute application guys and gals programming and with you guys? >>Yeah. They all believe that the potential for why we're trying to create a round user own the controlled identity. We're the only company in the market right now with a product that's live and working today. There's been a lot of promises made and we're the first ones to actually deliver to companies like cook finance, for example, are seeing the benefit of being able to have their users go through a simple process to check in and authenticate into the application, using your NFT domain name, rather than having to create an email address and password combination as a login, which inevitably leads to problems such as lost passwords, password resets, all those fun things that we used to deal with on a daily basis. >>Okay. So now I got to ask you the kind of partnerships you guys are looking at doing. I can only imagine the old, old school days you had a registry and you had registrars, you had a sales mechanism. I noticed you guys are selling NFT kind of like domain names on your website. Is that a kind of a current situation? Is that going to be ongoing? How do you envision your business model evolving and what kind of partnerships do you see coming along? >>Yeah, absolutely. So we're working with a lot of different companies from browsers that took changes to wallets, to individual NFT projects, to more recently even exploring partnership, partnership opportunities with fashion brands. For example, the Tyree market is moving so so fast. And what we're trying to essentially do here is create the standard naming system for web three. So a big part of that for us, we'll be working with partners like blockchain.com and with circle who's behind the DC coin on creating registries, such as dot blockchain and dot coin and making those available to tens of millions and ultimately hundreds of millions and billions of users worldwide. We want an ensemble domain name to be the first asset that every user in crypto gets, even before they buy their Bitcoin Ethereum or dovish coin. >>It makes a lot of sense obstruct the way the long hexadecimal string. We all know that we all write down putting a safe, hopefully you don't forget about it. You know, I always say, make sure you tell someone where your addresses. So in case something happens, you don't lose all that crypto. All good stuff. I got to ask the question around the ecosystem. Okay, can you share your view and vision of either your purse, yourself or the company when you have this kind of new market, you have all kinds of, and we meant the web was a good example, right? Web pages, you need web development tools. You had HTML by hand. Then you had all these tools. So you had tools and platforms and things kind of came well, grew together. How was the web three stakeholder ecosystem space evolving? What's what are some of the white spaces? What are some of the clearly defined areas that are developing? >>Yeah, I mean, we've seen an explosion in new smart contract blockchains and the past couple of years actually going live, which is really interesting because they support a huge number of different use cases, different trade-offs on each. We recently partnered and moved over a primary infrastructure to polygon, which is a leading EVM compatible smart chain, which allows us to provide free gas fees to users for maintaining and managing their domain name. So we're trying to move all obstacles around user adoption. Here. We all need to have Ethereum in your wallet. You know, it'd be an unstoppable domains customer or user. You don't have to worry about paying transaction fees. Every time you want to update the wallet, addresses associated with your domain name. We want to make this really big and accessible for everybody. And that means driving down costs as much as possible. Yeah, >>It's a whole nother wave. It's a wave that's built on the shoulders of others. It's a shift and infrastructure, new capabilities, new new applications. I think it's a, it's a great thing. You guys doing the naming system makes a lot of sense. This abstraction layer creates that ease of use. It simplifies things makes things easier. I mean, this is, was the promise of, of these abstraction layers. Final question. If I want to get involved, say we want to do a cube NFT with unstoppable. How do we work with you? How do we engage? Can you give a quick plug on what companies can do to engage with you guys on a business level? >>Yeah, absolutely. So we're looking to partner with wallets, exchanges, browsers, and companies who are in the crypto space already and realize they have a huge problem around usability with crypto transfers and wild addresses. Additionally, we're looking to partner with decentralized applications as well as web to companies who perhaps want to offer log-in with unstoppable domain functionality. In addition to, or in replacement of the login with Google and log-in with Facebook buttons that we all know and love. And we're looking to work with fashion brands and companies in the sports sector who perhaps want to claim their unstoppable names, free of charge from us. I might add in order to use that on Twitter or other marketing materials that they may have out there in the world to signal that they're not only forward looking, but that they're supportive of this huge wave that we're all riding at the most. >>May I great insight, chief revenue officer ensemble domains. Thanks for coming on the showcase, the cube and unstoppable domain share in the insights. Thanks for coming on. Okay. This cubes coverage here with the unstoppable domain showcase. I'm John furrier, your host. Thanks for watching.

(upbeat music) >> The cloud is evolving. You know, it's no longer a set of remote services somewhere off in the cloud, in the distance. It's expanding. It's moving to on-prem. On-prem workloads are connecting to the cloud. They're spanning clouds in a way that hides the plumbing and simplifies deployment, management, security, and governance. So hybrid multicloud is the next big thing in infrastructure, and at the recent Nutanix .NEXT conference, we got a major dose of that theme, and with me to talk about what we heard at that event, what we learned, why it matters, and what it means to customers are Monica Kumar, who's the senior vice president of marketing and cloud go-to-market at Nutanix, and Tarkan Maner, who's the chief commercial officer at Nutanix. Guys, great to see you again. Welcome to the theCUBE. >> Great to be back here. >> Great to see you, Dave. >> Okay, so you just completed another .NEXT. As an analyst, I like to evaluate the messaging at an event like this, drill into the technical details to try to understand if you're actually investing in the things that you're promoting in your keynotes, and then talk to customers to see how real it is. So with that as a warning, you guys are all in on hybrid multicloud, and I have my takeaways that I'd be happy to share, but, Tarkan, what were your impressions, coming out of the event? >> Look, you had a great entry. Our goal, as Monica is going to outline, too, cloud is not a destination. It's an operating model. Our customers are basically using cloud as a business model, as an operating model. It's not just a bunch of techno mumbo-jumbo, as, kind of, you outlined. We want to make sure we make cloud invisible to the customer so they can focus on what they need to focus on as a business. So as part of that, we want to make sure the workloads, the apps, they can run anywhere the way the customer wants. So in that context, you know, our entire story was bringing customer workloads, use-cases, partner ecosystem with ISVs and cloud providers and service providers and ISPs we're working with like Citrix on end user computing, like Red Hat on cloud native, and also bringing the right products, both in terms of infrastructure capability and management capability for both operators and application developers. So bringing all these pieces together and make it simple for the customer to use the cloud as an operating model. That was the biggest goal here. >> Great, thank you. Monica, anything you'd add in terms of your takeaways? >> Well, I think Tarkan said it right. We are here to make cloud complexity invisible. This was our big event to get thousands of our customers, partners, our supporters together and unveil our product portfolio, which is much more simplified, now. It's a cloud platform. And really have a chance to show them how we are building an ecosystem around it, and really bringing to life the whole notion of hybrid multicloud computing. >> So, Monica, could you just, for our audience, just summarize the big news that came out of .NEXT? >> Yeah, we actually made four different announcements, and most of them were focused around, obviously, our product portfolio. So the first one was around enhancements to our cloud platform to help customers build modern, software-defined data centers to speed their hybrid multicloud deployments while supporting their business-critical applications, and that was really about the next version of our flagship, AOS six, availability. We announced the general availability of that, and key features really included things like built-in virtual networking, disaster recovery enhancements, security enhancements that otherwise would need a lot of specialized hardware, software, and skills are now built into our platform. And, most importantly, all of this functionality being managed through a single interface, right? Which significantly decreases the operational overhead. So that was one announcement. The second announcement was focused around data services and really making it easy for customers to simplify data management, also optimize big data and database workloads. We announced capability that now improves performances of database workloads by 2x, big data workloads by 3x, so lots of great stuff there. We also announced a new service called Nutanix Data Lens, which is a new unstructured data governance service. So, again, I don't want to go into a lot of details here. Maybe we can do it later. That was our second big announcement. The third announcement, which is really around partnerships, and we'll talk more about that, is with Microsoft. We announced the preview of Nutanix Clusters and Azure, and that's really taking our entire flagship Nutanix platform and running it on Azure. And so, now, we are in preview on that one, and we're super excited about that. And then, last but not least, and I know Tarkan is going to go into a lot more detail, is we announced a strategic partnership with Citrix around the whole future of hybrid work. So lots of big news coming out of it. I just gave you a quick summary. There's a lot more around this, as well. >> Okay. Now, I'd like to give you my honest take, if you guys don't mind, and, Tarkan, I'll steal one of your lines. Don't hate me, okay? So the first thing I'm going to say is I think, Nutanix, you have the absolute right vision. There's no question in my mind. But what you're doing is not trivial, and I think it's going to play out. It's going to take a number of years. To actually build an abstraction layer, which is where you're going, as I take it, as a platform that can exploit all the respective cloud native primitives and run virtually any workload in any cloud. And then what you're doing, as I see it, is abstracting that underlying technology complexity and bringing that same experience on-prem, across clouds, and as I say, that's hard. I will say this: the deep dives that I got at the analyst event, it convinced me that you're committed to this vision. You're spending real dollars on focused research and development on this effort, and, very importantly, you're sticking to your true heritage of making this simple. Now, you're not alone. All the non-hyperscalers are going after the multicloud opportunity, which, again, is really challenging, but my assessment is you're ahead of the game. You're certainly focused on your markets, but, from what I've seen, I believe it's one of the best examples of a true hybrid multicloud-- you're on that journey-- that I've seen to date. So I would give you high marks there. And I like the ecosystem-building piece of it. So, Tarkan, you could course-correct anything that I've said, and I'd love for you to pick up on your comments. It takes a village, you know, you're sort of invoking Hillary Clinton, to bring the right solution to customers. So maybe you could talk about some of that, as well. >> Look, actually, you hit all the right points, and I don't hate you for that. I love you for that, as you know. Look, at the end of the day, we started this journey about 10 years ago. The last two years with Monica, with the great executive team, and overall team as a whole, big push to what you just suggested. We're not necessarily, you know, passionate about cloud. Again, it's a business model. We're passionate about customer outcomes, and some of those outcomes sometimes are going to also be on-prem. That's why we focus on this terminology, hybrid multicloud. It is not multicloud, it's not just private cloud or on-prem and non-cloud. We want to make sure customers have the right outcomes. So based on that, whether those are cloud partners or platform partners like HPE, Dell, Supermicro. We just announced a partnership with Supermicro, now, we're selling our software. HPE, we run on GreenLake. Lenovo, we run on TruScale. Big support for Lenovo. Dell's still a great partner to us. On cloud partnerships, as Monica mentioned, obviously Azure. We had a big session with AWS. Lots of new work going on with Red Hat as an ISV partner. Tying that also to IBM Cloud, as we move forward, as Red Hat and IBM Cloud go hand in hand, and also tons of workarounds, as Monica mentioned. So it takes a village. We want to make sure customer outcomes deliver value. So anywhere, for any app, on any infrastructure, any cloud, regardless standards or protocols, we want to make sure we have an open system coverage, not only for operators, but also for application developers, develop those applications securely and for operators, run and manage those applications securely anywhere. So from that perspective, tons of interest, obviously, on the Citrix or the UC side, as Monica mentioned earlier, we also just announced the Red Hat partnership for cloud services. Right before that, next we highlighted that, and we are super excited about those two partnerships. >> Yeah, so, when I talked to some of your product folks and got into the technology a little bit, it's clear to me you're not wrapping your stack in containers and shoving it into the cloud and hosting it like some do. You're actually going much deeper. And, again, that's why it's hard. You could take advantage of those things, but-- So, Monica, you were on the stage at .NEXT with Eric Lockhart of Microsoft. Maybe you can share some details around the focus on Azure and what it means for customers. >> Absolutely. First of all, I'm so grateful that Eric actually flew out to the Bay Area to be live on stage with us. So very super grateful for Eric and Azure partnership there. As I said earlier, we announced the preview of Nutanix Clusters and Azure. It's a big deal. We've been working on it for a while. What this means is that a select few organizations will have an opportunity to get early access and also help shape the roadmap of our offering. And, obviously, we're looking forward to then announcing general availability soon after that. So that's number one. We're already seeing tremendous interest. We have a large number of customers who want to get their hands on early access. We are already working with them to get them set up. The second piece that Eric and I talked about really was, you know, the reason why the work that we're doing together is so important is because we do know that hybrid cloud is the preferred IT model. You know, we've heard that in spades from all different industries' research, by talking to customers, by talking to people like yourselves. However, when customers actually start deploying it, there's lots of issues that come up. There's limited skill sets, resources, and, most importantly, there's a disparity between the on-premises networking security management and the cloud networking security management. And that's what we are focused on, together as partners, is removing that barrier, the friction between on-prem and Azure cloud. So our customers can easily migrate their workloads in Azure cloud, do cloud disaster recovery, create a burst into cloud for elasticity if they need to, or even use Azure as an on-ramp to modernize applications by using the Azure cloud services. So that's one big piece. The second piece is our partnership around Kubernetes and cloud native, and that's something we've already provided to the market. It's GA with Azure and Nutanix cloud platform working together to build Kubernetes-based applications, container-based applications, and run them and manage them. So there's a lot more information on nutanix.com/azure. And I would say, for those of our listeners who want to give it a try and who want their hands on it, we also have a test drive available. You can actually experience the product by going to nutanix.com/azure and taking the test drive. >> Excellent. Now, Tarkan, we saw recently that you announced services. You've got HPE GreenLake, Lenovo, their Azure service, which is called TruScale. We saw you with Keith White at HPE Discover. I was just with Keith White this week, by the way, face to face. Awesome guy. So that's exciting. You got some investments going on there. What can you tell us about those partnerships? >> So, look, as we talked through this a little bit, the HPE relationship is a very critical relationship. One of our fastest growing partnerships. You know, our customers now can run a Nutanix software on any HPE platform. We call it DX, is the platform. But beyond that, now, if the customers want to use HPE service as-a-service, now, Nutanix software, the entire stack, it's not only hybrid multicloud platform, the database capability, EUC capability, storage capability, can run on HPE's service, GreenLake service. Same thing, by the way, same way available on Lenovo. Again, we're doing similar work with Dell and Supermicro, again, giving our customers choice. If they want to go to a public club partner like Azure, AWS, they have that choice. And also, as you know, I know Monica, you're going to talk about this, with our GSI partnerships and new service provider program, we're giving options to customers because, in some other regions, HPE might not be their choice or Azure not be choice, and a local telco might the choice in some country like Japan or India. So we give options and capability to the customers to run Nutanix software anywhere they like. >> I think that's a really important point you're making because, as I see all these infrastructure providers, who are traditionally on-prem players, introduce as-a-service, one of the things I'm looking for is, sure, they've got to have their own services, their own products available, but what other ecosystem partners are they offering? Are they truly giving the customers choice? Because that's, really, that's the hallmark of a cloud provider. You know, if we think about Amazon, you don't always have to use the Amazon product. You can use actually a competitive product, and that's the way it is. They let the customers choose. Of course, they want to sell their own, but, if you innovate fast enough, which, of course, Nutanix is all about innovation, a lot of customers are going to choose you. So that's key to these as-a-service models. So, Monica, Tarkan mentioned the GSIs. What can you tell us about the big partners there? >> Yeah, definitely. Actually, before I talk about GSIs, I do want to make sure our listeners understand we already support AWS in a public cloud, right? So Nutanix totally is available in general, generally available on AWS to use and build a hybrid cloud offering. And the reason I say that is because our philosophy from day one, even on the infrastructure side, has been freedom of choice for our customers and supporting as large a number of platforms and substrates as we can. And that's the notion that we are continuing, here, forward with. So to talk about GSIs a bit more, obviously, when you say one platform, any app, any cloud, any cloud includes on-prem, it includes hyperscalers, it includes the regional service providers, as well. So as an example, TCS is a really great partner of ours. We have a long history of working together with TCS, in global 2000 accounts across many different industries, retail, financial services, energy, and we are really focused, for example, with them, on expanding our joint business around mission critical applications deployment in our customer accounts, and specifically our databases with Nutanix Era, for example. Another great partner for us is HCL. In fact, HCL's solution SKALE DB, we showcased at .NEXT just yesterday. And SKALE DB is a fully managed database service that HCL offers which includes a Nutanix platform, including Nutanix Era, which is our database service, along with HCL services, as well as the hardware/software that customers need to actually run their business applications on it. And then, moving on to service providers, you know, we have great partnerships like with Cyxtera, who, in fact, was the service provider partner of the year. That's the award they just got. And many other service providers, including working with, you know, all of the edge cloud, Equinix. So, I can go on. We have a long list of partnerships, but what I want to say is that these are very important partnerships to us. All the way from, as Tarkan said, OEMs, hyperscalers, ISVs, you know, like Red Hat, Citrix, and, of course, our service provider, GSI partnerships. And then, last but not least, I think, Tarkan, I'd love for you to maybe comment on our channel partnerships as well, right? That's a very important part of our ecosystem. >> No, absolutely. You're absolutely right. Monica. As you suggested, our GSI program is one of the best programs in the industry in number of GSIs we support, new SP program, enterprise solution providers, service provider program, covering telcos and regional service providers, like you suggested, OVH in France, NTT in Japan, Yotta group in India, Cyxtera in the US. We have over 50 new service providers signed up in the last few months since the announcement, but tying all these things, obviously, to our overall channel ecosystem with our distributors and resellers, which is moving very nicely. We have Christian Alvarez, who is running our channel programs globally. And one last piece, Dave, I think this was important point that Monica brought up. Again, give choice to our customers. It's not about cloud by itself. It's outcomes, but cloud is an enabler to get there, especially in a hybrid multicloud fashion. And last point I would add to this is help customers regardless of the stage they're in in their cloud migration. From rehosting to replatforming, repurchasing or refactoring, rearchitecting applications or retaining applications or retiring applications, they will have different needs. And what we're trying to do, with Monica's help, with the entire team: choice. Choice in stage, choice in maturity to migrate to cloud, and choice on platform. >> So I want to close. First of all, I want to give some of my impressions. So we've been watching Nutanix since the early days. I remember vividly standing around the conference call with my colleague at the time, Stu Miniman. The state-of-the-art was converged infrastructure, at the time, bolting together storage, networking, and compute, very hardware centric. And the founding team at Nutanix told us, "We're going to have a software-led version of that." And you popularized, you kind of created the hyperconverged infrastructure market. You created what we called at the time true private cloud, scaled up as a company, and now you're really going after that multicloud, hybrid cloud opportunity. Jerry Chen and Greylock, they just wrote a piece called Castles on the Cloud, and the whole concept was, and I say this all the time, the hyperscalers, last year, just spent a hundred billion dollars on CapEx. That's a gift to companies that can add value on top of that. And that's exactly the strategy that you're taking, so I like it. You've got to move fast, and you are. So, guys, thanks for coming on, but I want you to both-- maybe, Tarkan, you can start, and Monica, you can bring us home. Give us your wrap up, your summary, and any final thoughts. >> All right, look, I'm going to go back to where I started this. Again, I know I go back. This is like a broken record, but it's so important we hear from the customers. Again, cloud is not a destination. It's a business model. We are here to support those outcomes, regardless of platform, regardless of hypervisor, cloud type or app, making sure from legacy apps to cloud native apps, we are there for the customers regardless of their stage in their migration. >> Dave: Right, thank you. Monica? >> Yeah. And I, again, you know, just the whole conversation we've been having is around this but I'll remind everybody that why we started out. Our journey was to make infrastructure invisible. We are now very well poised to helping our customers, making the cloud complexity invisible. So our customers can focus on business outcomes and innovation. And, as you can see, coming out of .NEXT, we've been firing on all cylinders to deliver this differentiated, unified hybrid multicloud platform so our customers can really run any app, anywhere, on any cloud. And with the simplicity that we are known for because, you know, our customers love us. NPS 90 plus seven years in a row. But, again, the guiding principle is simplicity, portability, choice. And, really, our compass is our customers. So that's what we are focused on. >> Well, I love not having to get on planes every Sunday and coming back every Friday, but I do miss going to events like .NEXT, where I meet a lot of those customers. And I, again, we've been following you guys since the early days. I can attest to the customer delight. I've spent a lot of time with them, driven in taxis, hung out at parties, on buses. And so, guys, listen, good luck in the next chapter of Nutanix. We'll be there reporting and really appreciate your time. >> Thank you so much. >> Thank you so much, Dave. >> All right, and thank you for watching, everybody. This is Dave Vellante for theCUBE, and, as always, we'll see you next time. (light music)

>>Hey, welcome to the live panel. My name is Brett. I am your host, and indeed we are live. In fact, if you're curious about that, if you don't believe us, um, let's just show a little bit of the browser real quick to see. Yup. There you go. We're live. So, all right. So how this is going to work is I'm going to bring in some guests and, uh, in one second, and we're going to basically take your questions on the topic designer of the day, that continuous integration testing. Uh, thank you so much to my guests welcoming into the panel. I've got Carlos, Nico and Mandy. Hello everyone. >>Hello? All right, >>Let's go. Let's go around the room and all pretend we don't know each other and that the internet didn't read below the video who we are. Uh, hi, my name is Brett. I am a Docker captain, which means I'm supposed to know something about Docker. I'm coming from Virginia Beach. I'm streaming here from Virginia Beach, Virginia, and, uh, I make videos on the internet and courses on you to me, Carlos. Hey, >>Hey, what's up? I'm Carlos Nunez. I am a solutions architect, VMware. I do solution things with computers. It's fun. I live in Dallas when I'm moving to Houston in a month, which is where I'm currently streaming. I've been all over the Northeast this whole week. So, um, it's been fun and I'm excited to meet with all of you and talk about CIA and Docker. Sure. >>Yeah. Hey everyone. Uh, Nico, Khobar here. I'm a solution engineer at HashiCorp. Uh, I am streaming to you from, uh, the beautiful Austin, Texas. Uh, ignore, ignore the golden gate bridge here. This is from my old apartment in San Francisco. Uh, just, uh, you know, keeping that, to remember all the good days, um, that that lived at. But, uh, anyway, I work at Patrick Corp and I work on all things, automation, um, and cloud and dev ops. Um, and I'm excited to be here and Mandy, >>Hi. Yeah, Mandy Hubbard. I am streaming from Austin, Texas. I am, uh, currently a DX engineer at ship engine. Um, I've worked in QA and that's kind of where I got my, uh, my Docker experience and, um, uh, moving into DX to try and help developers better understand and use our products and be an advocate for them. >>Nice. Well, thank you all for joining me. Uh, I really appreciate you taking the time out of your busy schedule to be here. And so for those of you in chat, the reason we're doing this live, because it's always harder to do things live. The reason we're here is to answer a question. So we didn't come with a bunch of slides and demos or anything like that. We're here to talk amongst ourselves about ideas and really here for you. So we've, we obviously, this is about easy CII, so we're, we're going to try to keep the conversation around testing and continuous integration and all the things that that entails with containers. But we may, we may go down rabbit holes. We may go veer off and start talking about other things, and that's totally fine if it's in the realm of dev ops and containers and developer and ops workflows, like, Hey, it's, it's kinda game. >>And, uh, these people have a wide variety of expertise. They haven't done just testing, right? We, we live in a world where you all kind of have to wear many hats. So feel free to, um, ask what you think is on the top of your mind. And we'll do our best to answer. It may, might not be the best answer or the correct answer, but we're going to do our best. Um, well, let's get it start off. Uh, let's, let's get a couple of topics to start off with. Uh, th the, the easy CGI was my, one of my three ideas. Cause he's the, one of the things that I'm most excited about is the innovation we're seeing around easier testing, faster testing, automated testing, uh, because as much as we've all been doing this stuff for, you know, 15 years, since 20 years since the sort of Jenkins early days, um, it it's, it seems like it's still really hard and it's still a lot of work. >>So, um, let's go around the room real quick, and everybody can just kind of talk for a minute about like your experience with testing and maybe some of your pain points, like what you don't like about our testing world. Um, and we can talk about some pains, cause I think that will lead us to kind of talk about what, what are the things we're seeing now that might be better, uh, ideas about how to do this. I know for me, uh, testing, obviously there's the code part, but just getting it automated, but mostly getting it in the hands of developers so that they can control their own testing. And don't have to go talk to a person to run that test again, or the mysterious Jenkins platform somewhere. I keep mentioning Jenkins cause it's, it is still the dominant player out there. Um, so for me, I'm, I'm, I, I don't like it when I'm walking into a room and there's, there's only one or two people that know how the testing works or know how to make the new tests go into the testing platform and stuff like that. So I'm always trying to free those things so that any of the developers are enabled and empowered to do that stuff. So someone else, Carlos, anybody, um, >>Oh, I have a lot of opinions on that. Having been a QA engineer for most of my career. Um, the shift that we're saying is everyone is dev ops and everyone is QA. Th the issue I see is no one asked developers if they wanted to be QA. Um, and so being the former QA on the team, when there's a problem, even though I'm a developer and we're all running QA, they always tend to come to the one of the former QA engineers. And they're not really owning that responsibility and, um, and digging in. So that's kind of what I'm saying is that we're all expected to test now. And some people, well, some people don't know how it's, uh, for me it was kind of an intuitive skill. It just kind of fit with my personality, but not knowing what to look for, not knowing what to automate, not even understanding how your API end points are used by your front end to know what to test when a change is made. It's really overwhelming for developers. And, um, we're going to need to streamline that and, and hold their hands a little bit until they get their feet wet with also being QA. >>Right. Right. So, um, uh, Carlos, >>Yeah, uh, testing is like, Tesla is one of my favorite subjects to talk about when I'm baring with developers. And a lot of it is because of what Mandy said, right? Like a lot of developers now who used to write a test and say, Hey, QA, go. Um, I wrote my unit tests. Now write the rest of the test. Essentially. Now developers are expected to be able to understand how testing, uh, testing methodologies work, um, in their local environments, right? Like they're supposed to understand how to write an integration tasks federate into and tasks, a component test. And of course, how to write unit tests that aren't just, you know, assert true is true, right? Like more comprehensive, more comprehensive, um, more high touch unit tests, which include things like mocking and stubbing and spine and all that stuff. And, you know, it's not so much getting those tests. Well, I've had a lot of challenges with developers getting those tests to run in Docker because of usually because of dependency hell, but, um, getting developers to understand how to write tests that matter and mean something. Um, it's, it's, it can be difficult, but it's also where I find a lot of the enjoyment of my work comes into play. So yeah. I mean, that's the difficulty I've seen around testing. Um, big subject though. Lots to talk about there. >>Yeah. We've got, we've already got so many questions coming in. You already got an hour's worth of stuff. So, uh, Nico 81st thoughts on that? >>Yeah, I think I definitely agree with, with other folks here on the panel, I think from a, um, the shift from a skillset perspective that's needed to adopt the new technologies, but I think from even from, uh, aside from the organizational, um, and kind of key responsibilities that, that the new developers have to kinda adapt to and, and kind of inherit now, um, there's also from a technical perspective as there's, you know, um, more developers are owning the full stack, including the infrastructure piece. So that adds a lot more to the plate in Tim's oaf, also testing that component that they were not even, uh, responsible for before. Um, and, um, also the second challenge that, you know, I'm seeing is that on, you know, the long list of added, um, uh, tooling and, you know, there's new tool every other day. Um, and, um, that kind of requires more customization to the testing, uh, that each individual team, um, any individual developer Y by extension has to learn. Uh, so the customization, uh, as well as the, kind of the scope that had, uh, you know, now in conferences, the infrastructure piece, um, uh, both of act to the, to the challenges that we're seeing right now for, um, for CGI and overall testing, um, uh, the developers are saying, uh, in, in the market today. >>Yeah. We've got a lot of questions, um, about all the, all the different parts of this. So, uh, let me just go straight to them. Cause that's why we're here is for the people, uh, a lot of people asking about your favorite tools and in one of this is one of the challenges with integration, right? Is, um, there is no, there are dominant players, but there, there is such a variety. I mean, every one of my customers seems like they're using a different workflow and a different set of tools. So, and Hey, we're all here to just talk about what we're, what we're using, uh, you know, whether your favorite tools. So like a lot of the repeated questions are, what are your favorite tools? Like if you could create it from scratch, uh, what would you use? Pierre's asking, you know, GitHub actions sounds like they're a fan of GitHub actions, uh, w you know, mentioning, pushing the ECR and Docker hub and, uh, using vs code pipeline, I guess there may be talking about Azure pipelines. Um, what, what's your preferred way? So, does anyone have any, uh, thoughts on that anyone want to throw out there? Their preferred pipeline of tooling? >>Well, I have to throw out mine. I might as Jenkins, um, like kind of a honorary cloud be at this point, having spoken a couple of times there, um, all of the plugins just make the functionality. I don't love the UI, but I love that it's been around so long. It has so much community support, and there are so many plugins so that if you want to do something, you don't have to write the code it's already been tested. Um, unfortunately I haven't been able to use Jenkins in, uh, since I joined ship engine, we, most of our, um, our, our monolithic core application is, is team city. It's a dotnet application and TeamCity plays really well with.net. Um, didn't love it, uh, Ms. Jenkins. And I'm just, we're just starting some new initiatives that are using GitHub actions, and I'm really excited to learn, to learn those. I think they have a lot of the same functionality that you're looking for, but, um, much more simplified in is right there and get hubs. So, um, the integration is a lot more seamless, but I do have to go on record that my favorite CICT tools Jenkins. >>All right. You heard it here first people. All right. Anyone else? You're muted? I'm muted. Carlin says muted. Oh, Carla says, guest has muted themselves to Carlos. You got to unmute. >>Yes. I did mute myself because I was typing a lot, trying to, you know, try to answer stuff in the chat. And there's a lot of really dark stuff in there. That's okay. Two more times today. So yeah, it's fine. Yeah, no problem. So totally. And it's the best way to start a play more. So I'm just going to go ahead and light it up. Um, for enterprise environments, I actually am a huge fan of Jenkins. Um, it's a tool that people really understand. Um, it has stood the test of time, right? I mean, people were using Hudson, but 15 years ago, maybe longer. And, you know, the way it works, hasn't really changed very much. I mean, Jenkins X is a little different, but, um, the UI and the way it works internally is pretty familiar to a lot of enterprise environments, which is great. >>And also in me, the plugin ecosystem is amazing. There's so many plugins for everything, and you can make your own if you know, Java groovy. I'm sure there's a perfect Kotlin in there, but I haven't tried myself, but it's really great. It's also really easy to write, um, CIS code, which is something I'm a big fan of. So Jenkins files have been, have worked really well for me. I, I know that I can get a little bit more complex as you start to build your own models and such, but, you know, for enterprise enterprise CIO CD, if you want, especially if you want to roll your own or own it yourself, um, Jenkins is the bellwether and for very good reason now for my personal projects. And I see a lot on the chat here, I think y'all, y'all been agreed with me get hub actions 100%, my favorite tool right now. >>Um, I love GitHub actions. It's, it's customizable, it's modular. There's a lot of plugins already. I started using getting that back maybe a week after when GA and there was no documentation or anything. And I still, it was still my favorite CIA tool even then. Um, and you know, the API is really great. There's a lot to love about GitHub actions and, um, and I, and I use it as much as I can from my personal project. So I still have a soft spot for Travis CAI. Um, you know, they got acquired and they're a little different now trying to see, I, I can't, I can't let it go. I just love it. But, um, yeah, I mean, when it comes to Seattle, those are my tools. So light me up in the comments I will respond. Yeah. >>I mean, I, I feel with you on the Travis, the, I think, cause I think that was my first time experiencing, you know, early days get hub open source and like a free CIA tool that I could describe. I think it was the ammo back then. I don't actually remember, but yeah, it was kind of an exciting time from my experience. There was like, oh, this is, this is just there as a service. And I could just use it. It doesn't, it's like get hub it's free from my open source stuff. And so it does have a soft spot in my heart too. So yeah. >>All right. We've got questions around, um, cam, so I'm going to ask some questions. We don't have to have these answers because sometimes they're going to be specific, but I want to call them out because people in chat may have missed that question. And there's probably, you know, that we have smart people in chat too. So there's probably someone that knows the answer to these things. If, if it's not us, um, they're asking about building Docker images in Kubernetes, which to me is always a sore spot because it's Kubernetes does not build images by default. It's not meant for that out of the gate. And, uh, what is the best way to do this without having to use privileged containers, which privileged containers just implying that yeah, you, you, it probably has more privileges than by default as a container in Kubernetes. And that is a hard thing because, uh, I don't, I think Docker doesn't lie to do that out of the gate. So I don't know if anyone has an immediate answer to that. That's a pretty technical one, but if you, if you know the answer to that in chat, call it out. >>Um, >>I had done this, uh, but I'm pretty sure I had to use a privileged, um, container and install the Docker Damon on the Kubernetes cluster. And I CA I can't give you a better solution. Um, I've done the same. So, >>Yeah, uh, Chavonne asks, um, back to the Jenkins thing, what's the easiest way to integrate Docker into a Jenkins CICB pipeline. And that's one of the challenges I find with Jenkins because I don't claim to be the expert on Jenkins. Is there are so many plugins because of this, of this such a huge ecosystem. Um, when you go searching for Docker, there's a lot that comes back, right. So I, I don't actually have a preferred way because every team I find uses it differently. Um, I don't know, is there a, do you know if there's a Jenkins preferred, a default plugin? I don't even know for Docker. Oh, go ahead. Yeah. Sorry for Docker. And jacon sorry, Docker plugins for Jenkins. Uh, as someone's asking like the preferred or easy way to do that. Um, and I don't, I don't know the back into Jenkins that well, so, >>Well, th the new, the new way that they're doing, uh, Docker builds with the pipeline, which is more declarative versus the groovy. It's really simple, and their documentation is really good. They, um, they make it really easy to say, run this in this image. So you can pull down, you know, public images and add your own layers. Um, so I don't know the name of that plugin, uh, but I can certainly take a minute after this session and going and get that. Um, but if you really are overwhelmed by the plugins, you can just write your, you know, your shell command in Jenkins. You could just by, you know, doing everything in bash, calling the Docker, um, Damon directly, and then getting it working just to see that end to end, and then start browsing for plugins to see if you even want to use those. >>The plugins will allow more integration from end to end. Some of the things that you input might be available later on in the process for having to manage that yourself. But, you know, you don't have to use any of the plugins. You can literally just, you know, do a block where you write your shell command and get it working, and then decide if, for plugins for you. Um, I think it's always under important to understand what is going on under the hood before you, before you adopt the magic of a plugin, because, um, once you have a problem, if you're, if it's all a lockbox to you, it's going to be more difficult to troubleshoot. It's kind of like learning, get command line versus like get cracking or something. Once, once you get in a bind, if you don't understand the underlying steps, it's really hard to get yourself out of a bind, versus if you understand what the plugin or the app is doing, then, um, you can get out of situations a lot easier. That's a good place. That's, that's where I'd start. >>Yeah. Thank you. Um, Camden asks better to build test environment images, every commit in CII. So this is like one of those opinions of we're all gonna have some different, uh, or build on build images on every commit, leveraging the cash, or build them once outside the test pile pipeline. Um, what say you people? >>Uh, well, I I've seen both and generally speaking, my preference is, um, I guess the ant, the it's a consultant answer, right? I think it depends on what you're trying to do, right. So if you have a lot of small changes that are being made and you're creating images for each of those commits, you're going to have a lot of images in your, in your registry, right? And on top of that, if you're building those images, uh, through CAI frequently, if you're using Docker hub or something like that, you might run into rate limiting issues because of Docker's new rate, limiting, uh, rate limits that they put in place. Um, but that might be beneficial if the, if being able to roll back between those small changes while you're testing is important to you. Uh, however, if all you care about is being able to use Docker images, um, or being able to correlate versions to your Docker images, or if you're the type of team that doesn't even use him, uh, does he even use, uh, virgins in your image tags? Then I would think that that might be a little, much you might want to just have in your CIO. You might want to have a stage that builds your Docker images and Docker image and pushes it into your registry, being done first particular branches instead of having to be done on every commit regardless of branch. But again, it really depends on the team. It really depends on what you're building. It really depends on your workflow. It can depend on a number of things like a curse sometimes too. Yeah. Yeah. >>Once had two points here, you know, I've seen, you know, the pattern has been at every, with every, uh, uh, commit, assuming that you have the right set of tests that would kind of, uh, you would benefit from actually seeing, um, the, the, the, the testing workflow go through and can detect any issue within, within the build or whatever you're trying to test against. But if you're just a building without the appropriate set of tests, then you're just basically consuming almond, adding time, as well as all the, the image, uh, stories associated with it without treaty reaping the benefit of, of, of this pattern. Uh, and the second point is, again, I think if you're, if you're going to end up doing a per commit, uh, definitely recommend having some type of, uh, uh, image purging, um, uh, and, and, and garbage collection process to ensure that you're not just wasting, um, all the stories needed and also, um, uh, optimizing your, your bill process, because that will end up being the most time-consuming, um, um, you know, within, within your pipeline. So this is my 2 cents on this. >>Yeah, that's good stuff. I mean, those are both of those are conversations that could lead us into the rabbit hole for the rest of the day on storage management, uh, you know, CP CPU minutes for, uh, you know, your build stuff. I mean, if you're in any size team, more than one or two people, you immediately run into headaches with cost of CIA, because we have now the problem of tools, right? We have so many tools. We can have the CIS system burning CPU cycles all day, every day, if we really wanted to. And so you re very quickly, I think, especially if you're on every commit on every branch, like that gets you into a world of cost mitigation, and you probably are going to have to settle somewhere in the middle on, uh, between the budget, people that are saying you're spending way too much money on the CII platform, uh, because of all these CPU cycles, and then the developers who would love to have everything now, you know, as fast as possible and the biggest, biggest CPU's, and the biggest servers, and have the bills, because the bills can never go fast enough, right. >>There's no end to optimizing your build workflow. Um, we have another question on that. This is another topic that we'll all probably have different takes on is, uh, basically, uh, version tags, right? So on images, we, we have a very established workflow in get for how we make commits. We have commit shots. We have, uh, you know, we know get tags and there's all these things there. And then we go into images and it's just this whole new world that's opened up. Like there's no real consensus. Um, so what, what are your thoughts on the strategy for teams in their image tag? Again, another, another culture thing. Um, commander, >>I mean, I'm a fan of silver when we have no other option. Um, it's just clean and I like the timestamp, you know, exactly when it was built. Um, I don't really see any reason to use another, uh, there's just normal, incremental, um, you know, numbering, but I love the fact that you can pull any tag and know exactly when it was created. So I'm a big fan of bar, if you can make that work for your organization. >>Yep. People are mentioned that in chat, >>So I like as well. Uh, I'm a big fan of it. I think it's easy to be able to just be as easy to be able to signify what a major changes versus a minor change versus just a hot fix or, you know, some or some kind of a bad fix. The problem that I've found with having teams adopt San Bernardo becomes answering these questions and being able to really define what is a major change, what is a minor change? What is a patch, right? And this becomes a bit of an overhead or not so much of an overhead, but, uh, uh, uh, a large concern for teams who have never done versioning before, or they never been responsible for their own versioning. Um, in fact, you know, I'm running into that right now, uh, with, with a client that I'm working with, where a lot, I'm working with a lot of teams, helping them move their applications from a legacy production environment into a new one. >>And in doing so, uh, versioning comes up because Docker images, uh, have tags and usually the tax correlate to versions, but some teams over there, some teams that I'm working with are only maintaining a script and others are maintaining a fully fledged JAK, three tier application, you know, with lots of dependencies. So telling the script, telling the team that maintains a script, Hey, you know, you should use somber and you should start thinking about, you know, what's major, what's my number what's patch. That might be a lot for them. And for someone or a team like that, I might just suggest using commit shots as your versions until you figure that out, or maybe using, um, dates as your version, but for the more for the team, with the larger application, they probably already know the answers to those questions. In which case they're either already using Sember or they, um, or they may be using some other version of the strategy and might be in December, might suit them better. So, um, you're going to hear me say, it depends a lot, and I'm just going to say here, it depends. Cause it really does. Carlos. >>I think you hit on something interesting beyond just how to version, but, um, when to consider it a major release and who makes those decisions, and if you leave it to engineers to version, you're kind of pushing business decisions down the pipe. Um, I think when it's a minor or a major should be a business decision and someone else needs to make that call someone closer to the business should be making that call as to when we want to call it major. >>That's a really good point. And I add some, I actually agree. Um, I absolutely agree with that. And again, it really depends on the team that on the team and the scope of it, it depends on the scope that they're maintaining, right? And so it's a business application. Of course, you're going to have a product manager and you're going to have, you're going to have a product manager who's going to want to make that call because that version is going to be out in marketing. People are going to use it. They're going to refer to and support calls. They're going to need to make those decisions. Sember again, works really, really well for that. Um, but for a team that's maintaining the scripts, you know, I don't know, having them say, okay, you must tell me what a major version is. It's >>A lot, but >>If they want it to use some birds great too, which is why I think going back to what you originally said, Sember in the absence of other options. I think that's a good strategy. >>Yeah. There's a, there's a, um, catching up on chat. I'm not sure if I'm ever going to catch up, but there's a lot of people commenting on their favorite CII systems and it's, and it, it just goes to show for the, the testing and deployment community. Like how many tools there are out there, how many tools there are to support the tools that you're using. Like, uh, it can be a crazy wilderness. And I think that's, that's part of the art of it, uh, is that these things are allowing us to build our workflows to the team's culture. Um, and, uh, but I do think that, you know, getting into like maybe what we hope to be at what's next is I do hope that we get to, to try to figure out some of these harder problems of consistency. Uh, one of the things that led me to Docker at the beginning to begin with was the fact that it wa it created a consistent packaging solution for me to get my code, you know, off of, off of my site of my local system, really, and into the server. >>And that whole workflow would at least the thing that I was making at each step was going to be the same thing used. Right. And that, that was huge. Uh, it was also, it also took us a long time to get there. Right. We all had to, like Docker was one of those ones that decade kind of ideas of let's solidify the, enter, get the consensus of the community around this idea. And we, and it's not perfect. Uh, you know, the Docker Docker file is not the most perfect way to describe how to make your app, but it is there and we're all using it. And now I'm looking for that next piece, right. Then hopefully the next step in that, um, that where we can all arrive at a consensus so that once you hop teams, you know, okay. We all knew Docker. We now, now we're all starting to get to know the manifests, but then there's this big gap in the middle where it's like, it might be one of a dozen things. Um, you know, so >>Yeah, yeah. To that, to that, Brett, um, you know, uh, just maybe more of a shameless plug here and wanting to kind of talk about one of the things that I'm on. So excited, but I work, I work at Tasha Corp. I don't know anyone, or I don't know if many people have heard of, um, you know, we tend to focus a lot on workflows versus technologies, right. Because, you know, as you can see, even just looking at the chat, there's, you know, ton of opinions on the different tooling, right. And, uh, imagine having, you know, I'm working with clients that have 10,000 developers. So imagine taking the folks in the chat and being partnered with one organization or one company and having to make decisions on how to build software. Um, but there's no way you can conversion one or, or one way or one tool, uh, and that's where we're facing in the industry. >>So one of the things that, uh, I'm pretty excited about, and I don't know if it's getting as much traction as you know, we've been focused on it. This is way point, which is a project, an open source project. I believe we got at least, uh, last year, um, which is, it's more of, uh, it's, it is aim to address that really, uh, uh, Brad set on, you know, to come to tool to, uh, make it extremely easy and simple. And, you know, to describe how you want to build, uh, deploy or release your application, uh, in, in a consistent way, regardless of the tools. So similar to how you can think of Terraform and having that pluggability to say Terraform apply or plan against any cloud infrastructure, uh, without really having to know exactly the details of how to do it, uh, this is what wave one is doing. Um, and it can be applied with, you know, for the CIA, uh, framework. So, you know, task plugability into, uh, you know, circle CEI tests to Docker helm, uh, Kubernetes. So that's the, you know, it's, it's a hard problem to solve, but, um, I'm hopeful that that's the path that we're, you know, we'll, we'll eventually get to. So, um, hope, you know, you can, you can, uh, see some of the, you know, information, data on it, on, on HashiCorp site, but I mean, I'm personally excited about it. >>Yeah. Uh I'm to gonna have to check that out. And, um, I told you on my live show, man, we'll talk about it, but talk about it for a whole hour. Uh, so there's another question here around, uh, this, this is actually a little bit more detailed, but it is one that I think a lot of people deal with and I deal with a lot too, is essentially the question is from Cameron, uh, D essentially, do you use compose in your CIO or not Docker compose? Uh, because yes I do. Yeah. Cause it, it, it, it solves so many problems am and not every CGI can, I don't know, there's some problems with a CIO is trying to do it for me. So there are pros and cons and I feel like I'm still on the fence about it because I use it all the time, but also it's not perfect. It's not always meant for CIA. And CIA sometimes tries to do things for you, like starting things up before you start other parts and having that whole order, uh, ordering problem of things anyway. W thoughts and when have thoughts. >>Yes. I love compose. It's one of my favorite tools of all time. Um, and the reason why it's, because what I often find I'm working with teams trying to actually let me walk that back, because Jack on the chat asked a really interesting question about what, what, what the hardest thing about CIS for a lot of teams. And in my experience, the hardest thing is getting teams to build an app that is the same app as what's built in production. A lot of CGI does things that are totally different than what you would do in your local, in your local dev. And as a result of that, you get, you got this application that either doesn't work locally, or it does work, but it's a completely different animal than what you would get in production. Right? So what I've found in trying to get teams to bridge that gap by basically taking their CGI, shifting the CII left, I hate the shift left turn, but I'll use it. >>I'm shifting the CIO left to your local development is trying to say, okay, how do we build an app? How do we, how do we build mot dependencies of that app so that we can build so that we can test our app? How do we run tests, right? How do we build, how do we get test data? And what I found is that trying to get teams to do all this in Docker, which is normally a first for a lot of teams that I'm working with, trying to get them all to do all of this. And Docker means you're running Docker, build a lot running Docker, run a lot. You're running Docker, RM a lot. You ran a lot of Docker, disparate Docker commands. And then on top of that, trying to bridge all of those containers together into a single network can be challenging without compose. >>So I like using a, to be able to really easily categorize and compartmentalize a lot of the things that are going to be done in CII, like building a Docker image, running tests, which is you're, you're going to do it in CII anyway. So running tests, building the image, pushing it to the registry. Well, I wouldn't say pushing it to the registry, but doing all the things that you would do in local dev, but in the same network that you might have a mock database or a mock S3 instance or some of something else. Um, so it's just easy to take all those Docker compose commands and move them into your Yammel file using the hub actions or your dankest Bob using Jenkins, or what have you. Right. It's really, it's really portable that way, but it doesn't work for every team. You know, for example, if you're just a team that, you know, going back to my script example, if it's a really simple script that does one thing on a somewhat routine basis, then that might be a lot of overhead. Um, in that case, you know, you can get away with just Docker commands. It's not a big deal, but the way I looked at it is if I'm, if I'm building, if I build something that's similar to a make bile or rate file, or what have you, then I'm probably gonna want to use Docker compose. If I'm working with Docker, that's, that's a philosophy of values, right? >>So I'm also a fan of Docker compose. And, um, you know, to your point, Carlos, the whole, I mean, I'm also a fan of shifting CEI lift and testing lift, but if you put all that logic in your CTI, um, it changes the L the local development experience from the CGI experience. Versus if you put everything in a compose file so that what you build locally is the same as what you build in CGI. Um, you're going to have a better experience because you're going to be testing something more, that's closer to what you're going to be releasing. And it's also very easy to look at a compose file and kind of, um, understand what the dependencies are and what's happening is very readable. And once you move that stuff to CGI, I think a lot of developers, you know, they're going to be intimidated by the CGI, um, whatever the scripting language is, it's going to be something they're going to have to wrap their head around. >>Um, but they're not gonna be able to use it locally. You're going to have to have another local solution. So I love the idea of a composed file use locally, um, especially if he can Mount the local workspace so that they can do real time development and see their changes in the exact same way as it's going to be built and tested in CGI. It gives developers a high level of confidence. And then, you know, you're less likely to have issues because of discrepancies between how it was built in your local test environment versus how it's built in NCI. And so Docker compose really lets you do all of that in a way that makes your solution more portable, portable between local dev and CGI and reduces the number of CGI cycles to get, you know, the test, the test data that you need. So that's why I like it for really, for local dev. >>It'll be interesting. Um, I don't know if you all were able to see the keynote, but there was a, there was a little bit, not a whole lot, but a little bit talk of the Docker, compose V two, which has now built into the Docker command line. And so now we're shifting from the Python built compose, which was a separate package. You could that one of the challenges was getting it into your CA solution because if you don't have PIP and you got down on the binary and the binary wasn't available for every platform and, uh, it was a PI installer. It gets a little nerdy into how that works, but, uh, and the team is now getting, be able to get unified with it. Now that it's in Golang and it's, and it's plugged right into the Docker command line, it hopefully will be easier to distribute, easier to, to use. >>And you won't have to necessarily have dependencies inside of where you're running it because there'll be a statically compiled binary. Um, so I've been playing with that, uh, this year. And so like training myself to do Docker going from Docker dash compose to Docker space, compose. It is a thing I I'm almost to the point of having to write a shell replacement. Yeah. Alias that thing. Um, but, um, I'm excited to see what that's going, cause there's already new features in it. And it, these built kit by default, like there's all these things. And I, I love build kit. We could make a whole session on build kit. Um, in fact there's actually, um, maybe going on right now, or right around this time, there is a session on, uh, from Solomon hikes, the seat, uh, co-founder of Docker, former CTO, uh, on build kit using, uh, using some other tool on top of build kit or whatever. >>So that, that would be interesting for those of you that are not watching that one. Cause you're here, uh, to do a check that one out later. Um, all right. So another good question was caching. So another one, another area where there is no wrong answers probably, and everyone has a different story. So the question is, what are your thoughts on CII build caching? There's often a debate between security. This is from Quentin. Thank you for this great question. There's often a debate between security reproducibility and build speeds. I haven't found a good answer so far. I will just throw my hat in the ring and say that the more times you want to build, like if you're trying to build every commit or every commit, if you're building many times a day, the more caching you need. So like the more times you're building, the more caching you're gonna likely want. And in most cases caching doesn't bite you in the butt, but that could be, yeah, we, can we get the bit about that? So, yeah. Yeah. >>I'm going to quote Carlos again and say, it depends on, on, you know, how you're talking, you know, what you're trying to build and I'm quoting your colors. Um, yeah, it's, it's got, it's gonna depend because, you know, there are some instances where you definitely want to use, you know, depends on the frequency that you're building and how you're building. Um, it's you would want to actually take advantage of cashing functionalities, um, for the build, uh, itself. Um, but if, um, you know, as you mentioned, there could be some instances where you would want to disable, um, any caching because you actually want to either pull a new packages or, um, you know, there could be some security, um, uh, disadvantages related to security aspects that would, you know, you know, using a cache version of, uh, image layer, for example, could be a problem. And you, you know, if you have a fleet of build, uh, engines, you don't have a good grasp of where they're being cashed. We would have to, um, disable caching in that, in that, um, in those instances. So it, it would depend. >>Yeah, it's, it's funny you have that problem on both sides of cashing. Like there are things that, especially in Docker world, they will cash automatically. And, and then, and then you maybe don't realize that some of that caching could be bad. It's, it's actually using old, uh, old assets, old artifacts, and then there's times where you would expect it to cash, that it doesn't cash. And then you have to do something extra to enable that caching, especially when you're dealing with that cluster of, of CIS servers. Right. And the cloud, the whole clustering problem with caching is even more complex, but yeah, >>But that's, that's when, >>Uh, you know, ever since I asked you to start using build kits and able to build kit, you know, between it's it's it's reader of Boston in, in detecting word, you know, where in, in the bill process needs to cash, as well as, uh, the, the, um, you know, the process. I don't think I've seen any other, uh, approach there that comes close to how efficient, uh, that process can become how much time it can actually save. Uh, but again, I think, I think that's, for me that had been my default approach, unless I actually need something that I would intentionally to disable caching for that purpose, but the benefits, at least for me, the benefits of, um, how bill kit actually been processing my bills, um, from the builds as well as, you know, using the cash up until, you know, how it detects the, the difference in, in, in the assets within the Docker file had been, um, you know, uh, pretty, you know, outweigh the disadvantages that it brings in. So it, you know, take it each case by case. And based on that, determine if you want to use it, but definitely recommend those enabling >>In the absence of a reason not to, um, I definitely think that it's a good approach in terms of speed. Um, yeah, I say you cash until you have a good reason not to personally >>Catch by default. There you go. I think you catch by default. Yeah. Yeah. And, uh, the trick is, well, one, it's not always enabled by default, especially when you're talking about cross server. So that's a, that's a complexity for your SIS admins, or if you're on the cloud, you know, it's usually just an option. Um, I think it also is this, this veers into a little bit of, uh, the more you cash the in a lot of cases with Docker, like the, from like, if you're from images and checked every single time, if you're not pinning every single thing, if you're not painting your app version, you're at your MPN versions to the exact lock file definition. Like there's a lot of these things where I'm I get, I get sort of, I get very grouchy with teams that sort of let it, just let it all be like, yeah, we'll just build two images and they're totally going to have different dependencies because someone happened to update that thing and after whatever or MPM or, or, and so I get grouchy about that, cause I want to lock it all down, but I also know that that's going to create administrative burden. >>Like the team is now going to have to manage versions in a very much more granular way. Like, do we need to version two? Do we need to care about curl? You know, all that stuff. Um, so that's, that's kind of tricky, but when you get to, when you get to certain version problems, uh, sorry, uh, cashing problems, you, you, you don't want those set those caches to happen because it, if you're from image changes and you're not constantly checking for a new image, and if you're not pinning that V that version, then now you, you don't know whether you're getting the latest version of Davion or whatever. Um, so I think that there's, there's an art form to the more you pen, the less you have, the less, you have to be worried about things changing, but the more you pen, the, uh, all your versions of everything all the way down the stack, the more administrative stuff, because you're gonna have to manually change every one of those. >>So I think it's a balancing act for teams. And as you mature, I to find teams, they tend to pin more until they get to a point of being more comfortable with their testing. So the other side of this argument is if you trust your testing, then you, and you have better testing to me, the less likely to the subtle little differences in versions have to be penned because you can get away with those minor or patch level version changes. If you're thoroughly testing your app, because you're trusting your testing. And this gets us into a whole nother rant, but, uh, yeah, but talking >>About penny versions, if you've got a lot of dependencies isn't that when you would want to use the cash the most and not have to rebuild all those layers. Yeah. >>But if you're not, but if you're not painting to the exact patch version and you are caching, then you're not technically getting the latest versions because it's not checking for all the time. It's a weird, there's a lot of this subtle nuance that people don't realize until it's a problem. And that's part of the, the tricky part of allow this stuff, is it, sometimes the Docker can be almost so much magic out of the box that you, you, you get this all and it all works. And then day two happens and you built it a second time and you've got a new version of open SSL in there and suddenly it doesn't work. Um, so anyway, uh, that was a great question. I've done the question on this, on, uh, from heavy. What do you put, where do you put testing in your pipeline? Like, so testing the code cause there's lots of types of testing, uh, because this pipeline gets longer and longer and Docker building images as part of it. And so he says, um, before staging or after staging, but before production, where do you put it? >>Oh man. Okay. So, um, my, my main thought on this is, and of course this is kind of religious flame bait, so sure. You know, people are going to go into the compensation wrong. Carlos, the boy is how I like to think about it. So pretty much in every stage or every environment that you're going to be deploying your app into, or that your application is going to touch. My idea is that there should be a build of a Docker image that has all your applications coded in, along with its dependencies, there's testing that tests your application, and then there's a deployment that happens into whatever infrastructure there is. Right. So the testing, they can get tricky though. And the type of testing you do, I think depends on the environment that you're in. So if you're, let's say for example, your team and you have, you have a main branch and then you have feature branches that merged into the main branch. >>You don't have like a pre-production branch or anything like that. So in those feature branches, whenever I'm doing CGI that way, I know when I freak, when I cut my poll request, that I'm going to merge into main and everything's going to work in my feature branches, I'm going to want to probably just run unit tests and maybe some component tests, which really, which are just, you know, testing that your app can talk to another component or another part, another dependency, like maybe a database doing tests like that, that don't take a lot of time that are fascinating and right. A lot of would be done at the beach branch level and in my opinion, but when you're going to merge that beach branch into main, as part of a release in that activity, you're going to want to be able to do an integration tasks, to make sure that your app can actually talk to all the other dependencies that it talked to. >>You're going to want to do an end to end test or a smoke test, just to make sure that, you know, someone that actually touches the application, if it's like a website can actually use the website as intended and it meets the business cases and all that, and you might even have testing like performance testing, low performance load testing, or security testing, compliance testing that would want to happen in my opinion, when you're about to go into production with a release, because those are gonna take a long time. Those are very expensive. You're going to have to cut new infrastructure, run those tests, and it can become quite arduous. And you're not going to want to run those all the time. You'll have the resources, uh, builds will be slower. Uh, release will be slower. It will just become a mess. So I would want to save those for when I'm about to go into production. Instead of doing those every time I make a commit or every time I'm merging a feature ranch into a non main branch, that's the way I look at it, but everything does a different, um, there's other philosophies around it. Yeah. >>Well, I don't disagree with your build test deploy. I think if you're going to deploy the code, it needs to be tested. Um, at some level, I mean less the same. You've got, I hate the term smoke tests, cause it gives a false sense of security, but you have some mental minimum minimal amount of tests. And I would expect the developer on the feature branch to add new tests that tested that feature. And that would be part of the PR why those tests would need to pass before you can merge it, merge it to master. So I agree that there are tests that you, you want to run at different stages, but the earlier you can run the test before going to production. Um, the fewer issues you have, the easier it is to troubleshoot it. And I kind of agree with what you said, Carlos, about the longer running tests like performance tests and things like that, waiting to the end. >>The only problem is when you wait until the end to run those performance tests, you kind of end up deploying with whatever performance you have. It's, it's almost just an information gathering. So if you don't run your performance test early on, um, and I don't want to go down a rabbit hole, but performance tests can be really useless if you don't have a goal where it's just information gap, uh, this is, this is the performance. Well, what did you expect it to be? Is it good? Is it bad? They can get really nebulous. So if performance is really important, um, you you're gonna need to come up with some expectations, preferably, you know, set up the business level, like what our SLA is, what our response times and have something to shoot for. And then before you're getting to production. If you have targets, you can test before staging and you can tweak the code before staging and move that performance initiative. Sorry, Carlos, a little to the left. Um, but if you don't have a performance targets, then it's just a check box. So those are my thoughts. I like to test before every deployment. Right? >>Yeah. And you know what, I'm glad that you, I'm glad that you brought, I'm glad that you brought up Escalades and performance because, and you know, the definition of performance says to me, because one of the things that I've seen when I work with teams is that oftentimes another team runs a P and L tests and they ended, and the development team doesn't really have too much insight into what's going on there. And usually when I go to the performance team and say, Hey, how do you run your performance test? It's usually just a generic solution for every single application that they support, which may or may not be applicable to the application team that I'm working with specifically. So I think it's a good, I'm not going to dig into it. I'm not going to dig into the rabbit hole SRE, but it is a good bridge into SRE when you start trying to define what does reliability mean, right? >>Because the reason why you test performance, it's test reliability to make sure that when you cut that release, that customers would go to your site or use your application. Aren't going to see regressions in performance and are not going to either go to another website or, you know, lodge in SLA violation or something like that. Um, it does, it does bridge really well with defining reliability and what SRE means. And when you have, when you start talking about that, that's when you started talking about how often do I run? How often do I test my reliability, the reliability of my application, right? Like, do I have nightly tasks in CGI that ensure that my main branch or, you know, some important branch I does not mean is meeting SLA is meeting SLR. So service level objectives, um, or, you know, do I run tasks that ensure that my SLA is being met in production? >>Like whenever, like do I use, do I do things like game days where I test, Hey, if I turn something off or, you know, if I deploy this small broken code to production and like what happens to my performance? What happens to my security and compliance? Um, you can, that you can go really deep into and take creating, um, into creating really robust tests that cover a lot of different domains. But I liked just using build test deploy is the overall answer to that because I find that you're going to have to build your application first. You're going to have to test it out there and build it, and then you're going to want to deploy it after you test it. And that order generally ensures that you're releasing software. That works. >>Right. Right. Um, I was going to ask one last question. Um, it's going to have to be like a sentence answer though, for each one of you. Uh, this is, uh, do you lint? And if you lint, do you lent all the things, if you do, do you fail the linters during your testing? Yes or no? I think it's going to depend on the culture. I really do. Sorry about it. If we >>Have a, you know, a hook, uh, you know, on the get commit, then theoretically the developer can't get code there without running Melinta anyway, >>So, right, right. True. Anyone else? Anyone thoughts on that? Linting >>Nice. I saw an additional question online thing. And in the chat, if you would introduce it in a multi-stage build, um, you know, I was wondering also what others think about that, like typically I've seen, you know, with multi-stage it's the most common use case is just to produce the final, like to minimize the, the, the, the, the, the image size and produce a final, you know, thin, uh, layout or thin, uh, image. Uh, so if it's not for that, like, I, I don't, I haven't seen a lot of, you know, um, teams or individuals who are actually within a multi-stage build. There's nothing really against that, but they think the number one purpose of doing multi-stage had been just producing the minimalist image. Um, so just wanted to kind of combine those two answers in one, uh, for sure. >>Yeah, yeah, sure. Um, and with that, um, thank you all for the great questions. We are going to have to wrap this up and we could go for another hour if we all had the time. And if Dr. Khan was a 24 hour long event and it didn't sadly, it's not. So we've got to make room for the next live panel, which will be Peter coming on and talking about security with some developer ex security experts. And I wanted to thank again, thank you all three of you for being here real quick, go around the room. Um, uh, where can people reach out to you? I am, uh, at Bret Fisher on Twitter. You can find me there. Carlos. >>I'm at dev Mandy with a Y D E N D Y that's me, um, >>Easiest name ever on Twitter, Carlos and DFW on LinkedIn. And I also have a LinkedIn learning course. So if you check me out on my LinkedIn learning, >>Yeah. I'm at Nicola Quebec. Um, one word, I'll put it in the chat as well on, on LinkedIn, as well as, uh, uh, as well as Twitter. Thanks for having us, Brett. Yeah. Thanks for being here. >>Um, and, and you all stay around. So if you're in the room with us chatting, you're gonna, you're gonna, if you want to go to see the next live panel, I've got to go back to the beginning and do that whole thing, uh, and find the next, because this one will end, but we'll still be in chat for a few minutes. I think the chat keeps going. I don't actually know. I haven't tried it yet. So we'll find out here in a minute. Um, but thanks you all for being here, I will be back a little bit later, but, uh, coming up next on the live stuff is Peter Wood security. Ciao. Bye.

(digital music) >> From theCUBE Studios in Palo Alto in Boston, bringing you data-driven insights from theCUBE and ETR. This is Breaking Analysis with Dave Vellante. >> The storage business as we know it has changed forever. On-prem storage was once a virtually unlimited and untapped bastion of innovation, VC funding and lucrative exits. Today it's a shadow of its former self and the glory days of storage will not return. Hello everyone, and welcome to this week's Wikibon CUBE Insights Powered by ETR. In this breaking analysis, we'll lay out our premise for what's happening in the storage industry, and share some fresh insights from our ETR partners, and data that supports our thinking. We've had three decades of tectonic shifts in the storage business. From the simplified history of this industry shows us there've been five major waves of innovation spanning five decades. The dominant industry model has evolved from what was first the mainframe centric vertically integrated business, but of course by IBM and it became a disintegrated business that saw between like 70 or 80 Winchester disk drive companies that rose and then fell. They served a booming PC industry in this way it was led by the likes of Seagate. Now Seagate supplied the emergence of an intelligent controller based external disc array business that drove huge margins for functions that while lucrative was far cheaper than captive storage from system vendors, this era of course was led by EMC and NetApp. And then this business was disrupted by a flash and software defined model that was led by Pure Storage and also VMware. Now the future of storage is being defined by cloud and intelligent data management is being led by AWS and a three letter company that we'll just call TBD, otherwise known as Jump Ball Incorporated. Now, let's get into it here, the impact of AWS cannot be overstated now while legacy storage players, they're sick and tired of talking about the cloud, the reality cannot be ignored. The cloud has been the most disruptive force in storage over the past 10 years, and we've reported on the spending impact extensively. But cloud is not the only factor pressuring the on-prem storage business, flash has killed what we call performance by spindles. In other words, the practice of adding more disk drives to keep performance from tanking. So much flash has been injected into the data center that that no longer is required. But now as you drill down into the cloud, AWS has been by far the most significant factor in our view. Lots of people talked about object storage before AWS, but there sure wasn't much spending going on, S3 changed that. AWS is getting much more aggressive about expanding its storage portfolio and its offerings. S3 came out in 2006 and it was the very first AWS service and then Elastic Block Service EBS came out a couple of years later, nobody really paid much attention. Well last fall at storage day, we saw AWS announce a number of services, many fire-related and this year we saw four new announcements of Amazon at re:Invent. We think AWS' storage revenue will surpass 8 billion this year and could be as high as 10 billion. There's not much data out there, but this would mean that AWS' storage biz is larger than that of a NetApp, which means AWS is larger than every traditional storage player with the exception of Dell. Here's a little glimpse of what's coming at the legacy storage business. It's a clip of the vice-president of AWS storage, her name is Mahlon Thompson Bukovec, watch this. Okay now, you may say Dave, what the heck does that have to do with anything? Yeah, I don't know, but as an older white guy, that's been in this business for awhile, I just think it's badass that this woman boxes and runs a business that we think is approaching $10 billion. Now let's take a quick look at the storage announcements AWS made at re:Invent. The company made four announcements this year, let me try to be brief, the first is EBS io2 Block Express Volumes, got to love the names. AWS was claims this is the first storage area network or sand for the cloud and it offers up to 256,000 IOPS and 4,000 megabytes per second throughput and 64 terabytes of capacity. Hey, sounds pretty impressive right, Well let's dig in a little bit okay, first of all, this is not the first sand in the cloud, at least in my view there may be others but Pure Storage announced cloud block store in 2019 at its annual accelerate customer conference and it's pretty comparable here. Maybe not so much in the speeds and feeds, but the concept of better block storage in the cloud with higher availability. Now, as you may also be saying, what's the big deal? The performance come on, we can smoke that we're on-prem vendor We can bury that. Compared to what we do, AWS' announcement is really not that impressive okay, let me give you a point of comparison there's a startup out there called VAST Data. Just there for you and closure with bundled storage and compute can do 400,000 IOPS and 40,000 megabytes per second and that can be scaled, so yeah, I get it. And AWS also announced that io2 two was priced at 20% less than previous generation volumes, which you might say is also no big deal and I would agree 20% is not as aggressive as the average price decline per gigabyte of any storage technology. AWS loves to make a big deal about its price declines, it's essentially following the industry trends but the point is that this feature will be great for a lot of workloads and it's fully integrated with AWS services meaning for example, it will be very convenient for AWS customers to invoke this capability for example Aurora and other AWS databases through its RDS service, just another easy button for developers to push. This is specially important as we see AWS rapidly expanding its machine learning in AI capabilities with SageMaker, it's embedding ML into things like Redshift and driving analytics, so integration is very key for its customers. Now, is Amazon retail going to run its business on io2 volumes? I doubt it. I believe they're running on Oracle and they need much better performance, but this is a mainstream service for the EBS masses to tap. Now, the other notable announcement was EBS Gp3 volumes. This is essentially a service that lets let you programmatically set SLAs for IOPS and throughput independently without needing to add additional storage. Again, you may be saying things like, well atleast I remember when SolidFire let me do this several years ago and gave me more than 3000 IOPS and 125 megabytes per a second performance, but look, this is great for mainstream customers that want more consistent and predictable performance and that want to set some kind of threshold or floor and it's integrated again into the AWS stack. Two other announcements were made, one that automatically tiers data to colder storage tiers and a replication service. On the former, data migrates to tier two after 90 days of inaccess and tier three, after 180 days. AWS remember, they hired a bunch of folks out of EMC years ago and they put them up in the Boston Seaport area, so they've acquired lots of expertise in a lot of different areas I'm not sure if tiering came out of that group but look, this stuff is not rocket science, but it saves customers money. So these are tried and true techniques that AWS is applying but the important thing is it's in the cloud. Now for sure we'd like to see more policy options than say for example, a fixed 90 day or 180 day policy and more importantly we'd like to see intelligent tiering where the machine is smart enough to elevate and promote certain datasets when they're needed for instance, at the end of a quarter for comparison purposes or at the end of the year, but as NFL Hall of Fame Coach Hank Stram would have said, AWS is matriculating the ball down the field. Okay, let's look at some of the data that supports what we're saying here in our premise today. This chart shows spending across the ETR taxonomy. It depicts the net score or spending velocity for different sectors. We've highlighted storage, now don't put too much weight on the January data because the survey was just launched, but you can see storage continues to be a back burner item relative to some other spending priorities. Now as I've reported, CIOs are really focused on cloud, containers, container orchestration, automation, productivity and other key areas like security. Now let's take a look at some of the financial data from the storage crowd. This chart shows data for eight leading names in storage and we put storage in quotes because as we said earlier, the market is shifting and for sure companies like Cohesity and Rubrik, they're not positioning as storage players in fact, that's the last thing they want to do. Rather they're category creators around data management or intelligent data management but their inadjacency to storage, they're partnering with all the primary storage companies and they're in the ETR taxonomy. Okay, so as you can see, we're showing the year over year, quarterly revenue growth for the leading storage companies. NetApp is a big winner, they're growing at a whopping 2%. They beat expectations, but expectations were way down so you can see in the right most column upper right, we've added the ETR net score from October and net score of 10% says that if you ask customers, are you spending more or less with a company, there are 10% of the customers that are essentially spending more than are spending less, get into that a little further later. For comparison, a company like Snowflake, it has a net score approaching 70% Pure Storage used to be that high several years ago or high sixties anyway. So 10% is in the red zone and yet NetApp, is the big winner this quarter. Now Nutanix isn't really again a storage company, but they're an adjacency and they sell storage and like many of these companies, it's transitioning to a subscription pricing model, so that puts pressure on the income statement, that's why they went out and did a deal with Bain, Bain put in $750 million to help Bridge that transition so that's kind of an interesting move. Every company in this chart is moving to an annual recurring revenue model and that as a service approach is going to be the norm by the end of the decade. HPE's doing it with GreenLake, Dell has announced Apex, virtually every company is headed in this direction. Now speaking of HPE, it's Nimble business that has momentum, but other parts of the storage portfolio are quite a bit softer. Dell continues to see pressure on its storage business although VxRail is a bright spot. Everybody's got a bright spot, everybody's got new stuff that's growing much faster than the old stuff, the problem is the old stuff is much much bigger than the new stuff. IBM's mainframe storage cycle, well that's seems to have run its course, they had been growing for the last several quarters that looks like it's over. And so very very cyclical businesses here now as you can see, The data protection data management companies, they are showing spending momentum but they're not public so we don't have revenue data. But you got to wonder with all the money these guys have raised and the red hot IPO and tech markets, why haven't these guys gone public? The answer has to be that they're either not ready or maybe their a numbers weren't where they want them to be, maybe they're not predictable enough, maybe they don't have their operational act together or maybe they need to you get that in order, some combination of those factors is likely. They'll tell you, they'll give other answers if you ask them, but if they had their stuff together they'd be going out right now. Now here's another look at the spending data in terms of net score, which is again spending velocity. The ETR here is measuring the percent of respondents that are adopting new, spending more, spending flat, spending less or retiring the platform. So net score is adoptions, which is the lime green plus the spending more, which is the forest green. Add those two and then subtract spending less, which is the pink and then leaving the platform, which is the bright red, what's left over is net score. So, let's look at the picture here, Cohesity leads all players in the storage taxonomy, the ETR storage taxonomy, again they don't position that way, but that's the way the customers are answering. They've got 55% net score which is really solid and you can see the data in the upper right-hand corner, it's followed by Nutanix. Now they're really not again in the scope of Pure play storage play but speaking of Pure, its net score has come down from its high of 73% in January, 2016. It's not going to climb back up there, but it's going to be interesting to see if Pure net scorecard rebound in a post COVID world. We're also watching what Pure does in terms of unifying file and object and how it's fairing in cloud and what it does with the Portworx acquisition which is really designed to bring forth a new programming model. Now, Dell is doing fine with VxRail, but VSAN is well off its net score highs which we're in the 60% plus range a couple of years ago, VSAN is definitely been a factor from VMware, but again that's come off its highs, HPE with Nimble still has some room to improve, I think it actually will I think that these figures that we're showing here they're are somewhat depressed by the COVID factor, I expect Nimble is going to bounce back in future surveys. Dell and NetApp are the big leaders in terms of presence or market share in the data other than VMware, 'cause VMware has a lot of instances, it's software defined that's why they're so prominent. And with VMware's large share you'd expect them to have net scores that are tepid and you can see a similar pattern with IBM. So Dell, NetApp, tepid net scores as is IBM because of their large market share VMware, kind of a newer entry into the play and so doing pretty well there from a net score standpoint. Now Commvault like Cohesity and Rubrik is really around intelligent data management, trying to go beyond backup into business recovery, data protection, DevOps, bringing that analytics, bringing that to the cloud, we didn't put Veeam in here and we probably should have. They had pre-COVID net scores well in to the thirties and they have a steadily increasing share of the market, so we expect good things from Veeam going forward. They were acquired earlier this year by Insight, capital private equity firm. So big changes there as well, that was their kind of near-term exit maybe more to come. But look, it's all relative, this is a large and mature market that is moving to the cloud and moving to other adjacencies. And the core is still primary storage, that's the main supreme prerequisite and everything else flows from there, data protection, replication, everything else. This chart gives you another view of the competitive landscape, it's that classic XY chart it plots net score in the vertical axis and market share on the horizontal axis, market share remember is a measure of presence in the dataset. Now think about this from the CIO's perspective, they have their on-prem estate, got all this infrastructure and they're putting a brick wall around their core systems. And what do they want out of storage for that class of workload? They want it to perform consistently, they want it to be efficient and they want it to be cost-effective, so what are they going to do? they're going to consolidate, They're going to consolidate the number of vendors, they're going to consolidate the storage, they're going to minimize complexity, yeah, they're going to worry about the blast radius, but there's ways to architect around that. The last thing they want to worry about is managing a zillion storage vendors this business is consolidating, it has been for some time, we've seen the number of independent storage players that are going public as consolidated over the years, and it's going to continue. so on-prem storage arrays are not giving CIOs the innovation and strategic advantage back when things like storage virtualization, space efficient snapshots, data de-duplication and other storage services were worth maybe taking a flyer on a feature product like for example, a 3PAR or even a Data Domain. Now flash gave the CIOs more headroom and better performance and so as I said earlier, they're not just buying spindles to increase performance, so as more and more work gets pushed to the cloud, you're seeing a bunkering in on these large scale mission-critical workloads. As you saw earlier, the legacy storage market is consolidating and has been for a while as I just said, it's essentially becoming a managed decline business where RnD is going to increasingly get squeezed and go to other areas, both from the vendor community and on the buy-side where they're investing on things like cloud, containers and in building new layers in their business and of course the DX, the Digital Transformation. I mentioned VAST Data before, it is a company that's growing and another company that's growing is Infinidat and these guys are traditional storage on-prem models they don't bristle If I say traditional they're nexgen if you will but they don't own a cloud, so they were selling to the data center. Now Infinidat is focused on petabyte scale and as they say, they're growing revenues, they're having success consolidating storage that thing that I just talked about. Ironically, these are two Israeli founder based companies that are growing and you saw earlier, this is a share shift the market is not growing overall the part of that's COVID, but if you exclude cloud, the market is under pressure. Now these two companies that I'm mentioning, they're kind of the exception to the rule here, they're tiny in the grand scheme of things, they're really not going to shift the market and their end game is to get acquired so they can still share, but they're not going to reverse these trends. And every one on this chart, every on-prem player has to have a cloud strategy where they connect into the cloud, where they take advantage of native cloud services and they help extend their respective install bases into the cloud, including having a capability that is physically proximate to the cloud with a colo like an Equinix or some other approach. Now, for example at re:Invent, we saw that AWS has hybrid strategy, we saw that evolving. AWS is trying to bring AWS to the edge and they treat the data center as just another edge note, so outposts and smaller versions of outposts and things like local zones are all part of bringing AWS to the edge. And we saw a few companies Pure, Infinidant, Veeam come to mind that are connecting to outpost. They saw the Qumulo was in there, Clumio, Commvault, WekaIO is also in there and I'm sure I'm missing some so, DM me, email me, yell at me, I'm sorry I forgot you but you get the point. These companies that are selling on-prem are connecting to the cloud, they're forced to connect to the cloud much in the same way as they were forced to join the VMware ecosystem and try to add value, try to keep moving fast. So, that's what's going on here, what's the prognosis for storage in the coming year? Well, where've of all the good times gone? Look, we would never bet against data but the days of selling storage controllers that masks the deficiencies of spinning disc or add embedded hardware functions or easily picking off a legacy install base with flash, well, those days are gone. Repatriation, it ain't happening it's maybe tiny little pockets. CIOs are rationalizing their on-premises portfolios so they can invest in the cloud, AI, machine learning, machine intelligence, automation and they're re-skilling their teams. Low latency high bandwidth workloads with minimal jitter, that's the sweet spot for on-prem it's becoming the mainframe of storage. CIOs are also developing a cloud first strategy yes, the world is hybrid but what does that mean to CIOs? It means you're going to have some work in the cloud and some work on-prem, there's a hybrid We've got both. Everything that can go to the cloud, will go to the cloud, in our opinion and everything that can't or shouldn't won't. Yes, people will make mistakes and they'll "repatriate" but generally that's the trend. And the CIOs they're building an abstraction layer to connect workloads from an observability and manageability standpoint so they can maintain control and manage lock-in risk, they have options. Everything that doesn't go to the cloud will likely have some type of hybridicity to it, the reverse won't likely be the case. For vendors, cloud strategies involve supporting your install basis migration to the cloud, that's where they're going, that's where they want to go, they want your help there's business to be made there so enabling low latency hybrids in accommodating subscription models, well, that's a whole another topic, but that's the trend that we see and you rethink the business that you're in, for instance, data management and developing an edge strategy that recognizes that edge workloads are going to require new architecture and that's more efficient than what we've seen built around general purpose systems, and wow, that's a topic for another day. You're seeing this whole as a service model really reshape the entire cultures in the way in which the on-prem vendors are operating no longer is it selling a box that has dramatically marked up controllers and disc drives, it's really thinking about services that could be invoked in the cloud. Now remember, these episodes are all available as podcasts, wherever you listen, just search Breaking Analysis podcasts and please subscribe, I'd appreciate that checkout etr.plus for all the survey action. We also publish a full report every week on wikibon.com and siliconangle.com. A lot of ways to get in touch. You can email me at david.vellante@siliconangle.com. you could DM me @dvellante on Twitter, comment on our LinkedIn posts, I always appreciate that. This is Dave Vellante for theCUBE Insights Powered by ETR. Thanks for watching everyone stay safe and we'll see you next time. (upbeat music)

>>with me are and Crystal Graham, a k a a C. She's the C R O of talent, and Chris Degnan is the C R. O of Snowflake. We have to go to market heavies on this section, folks. Welcome to the Cube. >>Thank you. >>Thanks for having us. >>That's our pleasure. And so let's let's talk about digital transformation, right? Everybody loves to talk about it. It zone overused term. I know, but what does it mean? Let's talk about the vision of the data cloud for snowflake and digital transformation. A. C. We've been hearing a lot about digital transformation over the past few years. It means a lot of things to a lot of people. What are you hearing from customers? How are they thinking about when I come, sometimes called DX and what's important to them? Maybe address some of the challenges even that they're facing >>Dave. That's a great question to our customers. Digital transformation literally means staying in business or not. Um, it's that simple. Um, the reality is most agree on the opportunity to modernize data management infrastructure that they need to do that to create the speed and efficiency and cost savings that digital transformation promises. But but now it's beyond that. What's become front and center for our customers is the need for trusted data, supported by an agile infrastructure that and allow a company to pivot operations as they need. Um, let me give you an example of that. One of our customers, a medical device company, was on their digital journey when Cove it hit. They started last year in 2019, and as the pandemic hit at the earlier part of this year, they really needed to take a closer look at their supply chain. On went through an entire supply chain optimization, having been completely disrupted in the you think about the logistics, the transportation, the location of where they needed to get parts, all those things when they were actually facing a need to increase production by about 20 times. In order to meet the demand on DSO, you can imagine what that required them to do and how reliant they were on clean, compliant, accurate data that they could use to make extremely critical decisions for their business. And in that situation, not just for their business but decisions. That would be the about saving lives, so the stakes have gotten a lot higher, and that's that's just one industry. It's it's really across all industries. So when you think about that, really, when you talk to any of our customers, digital transformation is really mean. It really means now having the confidence in data to support the business at critical times with accurate, trusted information. >>Chris, I've always said a key part of digital transformation is really putting data at the core of everything you know, Not not the manufacturing plant, that the core in the data around it, but putting data at the center. It seems like that's what Snowflake is bringing to the table. Can you comment? >>Yeah. I mean, I think if if I look across what's happening and especially a Z A. C said, you know, through co vid is customers are bringing more and more data sets. They wanna make smarter business decisions based on data making, data driven decisions. And we're seeing acceleration of of data moving to the cloud because they're just in abundance of data. And it's challenging to actually manage that data on premise and and as we see those those customers move those large data sets. Think what A C said is spot on is that customers don't just want to have their data in the cloud. But they actually want to understand what the data is, understand, who has access to that data, making sure that they're actually making smart business decisions based on that data. And I think that's where the partnership between both talent and stuff like are really tremendous, where you know we're helping our customers bring their data assets to to the cloud, really landing it and allowing them to do multiple, different types of workloads on top of this data cloud platform and snowflake. And then I think again what talent is bringing to the table is really helping the customer make sure that they trust the data that they're actually seeing. And I think that's a really important aspect of digital transformation today. >>Awesome and I want to get into the partnership. But I don't wanna leave the pandemic just yet. A c. I want to ask you how it's affected customer priorities and timelines with regard to modernizing their data operations and what I mean to that they think about the end and life cycle of going from raw data insights and how they're approaching those life cycles. Data quality is a key part of, you know, a good data quality. You're gonna I mean, obviously you want to reiterate, and you wanna move fast. But if if it's garbage out, then you got to start all over again. So what are you seeing in terms of the effect of the pandemic and the urgency of modernizing those data operations? >>Yeah, but like Chris just said it accelerated things for those companies that hadn't quite started their digital journey. Maybe it was something that they had budgeted for but hadn't quite resourced completely many of them. This is what it took to to really get them off the dying from that perspective, because there was no longer the the opportunity to wait. They needed to go and take care of this really critical component within their business. So, um, you know what? What Covic, I think, has taught companies have taught all of us is how vulnerable even the largest. Um, you know, companies on most robust enterprises could be those companies that had already begun Their digital transformation, maybe even years ago, had already started that process and we're in a better. We're in a great position in their journey. They fared a lot better and we're able to be agile. Were able Thio in a shift. Priorities were able to go after what they needed to do toe to run their businesses better and be able to do so with riel clarity and confidence. And I think that's really the second piece of it is, um or the last six months people's lives have really depended on the data people's lives that have really dependent on uncertainty. The pandemic has highlighted the importance of reliable and trustworthy information, not just the proliferation of data. And as Chris mentioned this data being available, it's really about making sure that you can use that data as an asset Ondas and that the greatest weapon we all have, really there is the information and good information to make a great business decisions. >>Of course, Chris, the other thing we've seen is the acceleration toe to the cloud, which is obviously you're born in the cloud. It's been a real tailwind. What are you seeing in that regard from your I was gonna say in the field, but from your zoom >>advantage. Yeah, well, I think you know, a C talked about supply chain, um, analytics in in her previous example. And I think one of the things that that we did is we hosted a data set. The covert data set over 19 data set within snowflakes, data marketplace. And we saw customers that were, you know, initially hesitant to move to the cloud really accelerate there. They're used to just snowflake in the cloud with this cove Cove. A data set on Ben. We had other customers that are, you know, in the retail space, for example, and use the cova data set to do supply chain analytics and and and accelerated. You know, it helped them make smarter business decisions on that. So So I'd say that you know, Cove, it has, you know, made customers that maybe we're may be hesitant to to start their journey in the cloud, move faster. And I've seen that, you know, really go at a blistering pace right now. >>You know, you just talked about, you know, value because it's all about value. But the old days of data quality in the early days of Chief Data, Officer all the focus was on risk avoidance. How do I get rid of data? How long do I have to keep it? And that has flipped dramatically. You know, sometime during the last decade, >>you can't get away too much from the need for quality data and and govern data. I think that's the first step. You can't really get to, um, you know, to trust the data without those components. And but to your point, the chief Data officers role, I would say, has changed pretty significantly. And in the round tables that I've participated in over the last, you know, several months. It's certainly a topic that they bring to the table that they'd like Thio chat with their peers about in terms of how they're navigating through the balance, that they still need toe to manage to the quality they still need to manage to the governance they still need. Thio ensure that that they're delivering that trusted information to the business. But now, on the flip side as well, they're being relied upon to bring new insights. And that's on bit's, um, really requiring them to work more cross functionally than they may have needed to in the past where that's been become a big part of their job is being that evangelist for data the evangelist. For that, those insights and being able to bring in new ideas for how the business can operate and identified, you know, not just not just operational efficiencies, but revenue opportunities, ways that they can shift. All you need to do is take a look at, for example, retail. You know, retail was heavily impacted by the pandemic this year on git shows how easily an industry could be could be just kind of thrown off its course simply by by a just a significant change like that. Andi need to be able to to adjust. And this is where, um when I've talked to some of the CEOs of the retail customers that we work with, they've had to really take a deep look at how they can leverage their the data at their fingertips to identify new in different ways in which they can respond to customer demands. So it's a it's a whole different dynamic. For sure, I it doesn't mean that that you walk away from the other and the original part of the role of the or the areas in which they were maybe more defined a few years ago when the role of the chief data officer became very popular. I do believe it's more of a balance at this point and really being able to deliver great value to the organization with the insights that they could bring >>well, is he stayed on that for a second. So you have this concept of data health, and I guess what kind of getting tad is that In the early days of Big Data Hadoop, it was just a lot of rogue efforts going on. People realize, Wow, there's no governance And what what seems like what snowflake and talent are trying to do is to make that the business doesn't have to worry about it. Build, build that in, don't bolt it on. But what's what's this notion of data health that you talk about? >>Companies can measure and do measure just about everything, every aspect of their business health. Um, except what's interesting is they don't have a great way to measure the health of their data, and this is an asset that they truly rely on. Their future depends on is that health of their data. And so if we take a little bit of a step back, maybe let's take a look at an example of a customer experiences to kind of make a little bit of a delineation between the differences of data, data, quality, data trust in what data health truly is. We work with a lot of health, a lot of hotel chains. And like all companies today, hotels collect a ton of information. There's mountains of information, private information about their customers through the loyalty clubs and all the information that they collect from there, the front desk, the systems that store their data. You can start to imagine the amount of information that a hotel chain has about an individual, and frequently that information has, you know, errors in it, such as duplicate entries, you know. Is it a Seagram, or is it in Chris Telegram? Same person, Slightly different, depending on how I might have looked or how I might have checked in at the time. And sometimes the data is also mismanaged, where because it's in so many different locations, it could be accessed by the wrong person of someone that wasn't necessarily intended to have that kind of visibility. And so these are examples of when you look at something like that. Now you're starting to get into, you know, privacy regulations and other kinds of things that could be really impactful to a business if data is in the wrong hands or the wrong data is in the wrong hands. So, you know, in a world of misinformation and mistrust, which is around us every single day, um, talent has really invented a way for businesses to verify the veracity, the accuracy of their data. And that's where data health really comes in Is being able to use a trust score to measure the data health on. That's what we have recently introduced is this concept of the trust score, something that can actually provide and measure, um, at the accuracy and the health of the data all the way down to an individual report. We believe that that that truly, you know, provides the explainable trust issue resolution, the kinds of things that companies are looking for in that next stage of overall data management. >>Thank you, Chris. Bring us home. So, one of the key aspects of what snowflake is doing is building out the ecosystem is very, very important. Really talk about how how you guys we're partnering and adding value in particular things that you're seeing customers do today within the ecosystem or with the help of the ecosystem and stuff like that they weren't able to do previously. >>Yeah. I mean, I think you know a C mentioned it. You mentioned it. You know, we spent I spent a lot of my zoom days talking Thio, chief data officers and as I'm talking to the chief data officers that they are so concerned their responsibility on making sure that the business users air getting accurate data so that they view that as data governance is one aspect of it. But the other aspect is the circumference of the data of where it sits and who has access to that data and making sure it's super secure. And I think you know, snowflake is a tremendous landing spot being a data warehouse or data cloud data platform as a service, you know, we take care of all the, you know, securing that data. And I think where talent really helps our customer base is helps them exactly What what is he talked about is making sure that you know myself as a business users someone like myself who's looking at data all the time, trying to make decisions on how many sales people I wanna hire house my forecast coming. You know, how's the how's the product working all that stuff? I need to make sure that I'm actually looking at at good data. And I think the combination of all sitting in a single repository like snowflake and then layering it on top or laying a tool like talent on top of it, where I can actually say, Yeah, that is good data. It helps me make smarter decisions faster. And ultimately, I think that's really where the ecosystem plays. An incredibly important, important role for snowflake in our customers, >>guys to great cast. I wish we had more time, but we gotta go on dso Thank you so much for sharing your perspectives. A great conversation

>> Hello everyone, and welcome back to The Data Cloud Summit 2020. We're going to dig into the all-important ecosystem, and focus in little bit on the intersection of the data cloud and trust. And with me are Ann-Christel Graham, AKA A.C., she's the CRO of Talend, and Chris Degnan is the CRO of Snowflake. We have the go-to-market heavies on this section, folks. Welcome to theCUBE. >> Thank you. >> Thanks for having us. >> Yeah, it's our pleasure. And so let's talk about digital transformation, right? Everybody loves to talk about it. It's an overused term, I know, but what does it mean? Let's talk about the vision of the data cloud for Snowflake and digital transformation. A.C., we've been hearing a lot about digital transformation over the past few years. It means a lot of things to a lot of people. What are you hearing from customers? How are they thinking about what I sometimes call DX? And what's important to them, maybe address some of the challenges even that they're facing? >> Dave, that's a great question. To our customers, digital transformation literally means staying in business or not. It's that simple. The reality is most agree on the opportunity to modernize data management infrastructure, that they need to do that to create the speed, and efficiency, and cost savings that digital transformation promises. But now it's beyond that. What's become front and center for our customers is the need for trusted data supported by an agile infrastructure that can allow a company to pivot operations as they need. Let me give you an example of that. One of our customers, a medical device company, was on their digital journey when COVID hit. They started last year in 2019. And as the pandemic hit, at the earlier part of this year, they really needed to take a closer look at their supply chain, and went through an entire supply chain optimization, having been completely disrupted in the, you think about the logistics, the transportation, the location of where they needed to get parts, all those things, when they were actually facing a need to increase production by about 20 times in order to meet the demand. And so you can imagine what that required them to do, and how reliant they were on clean, compliant, accurate data that they could use to make extremely critical decisions for their business. And in that situation, not just for their business, but decisions that would be about saving lives. So the stakes have gotten a lot higher and that's just one industry, it's really across all industries. So when you think about that, really, when you talk to any of our customers, digital transformation really means now having the confidence in data to support the business at critical times with accurate, trusted information. >> I mean, if you're not a digital business today, you're kind of out of business. Chris, I've always said a key part of digital transformation is really putting data at the core of everything. You know, not the manufacturing plant at the core and the data around it, but putting data at the center. And it seems like that's what Snowflake is bringing to the table. Can you comment? >> Yeah, I mean, I think if I look across what's happening, especially as A.C. said, you know, through COVID, is customers are bringing more and more data sets. They want to make smarter business decisions based on making data-driven decisions. And we are seeing acceleration of data moving to the cloud because there's just an abundance of data, and it's challenging to actually manage that data on-premise. And as we see those customers move those large data sets, I think what A.C. said is spot on, is that customers don't just want to have their data in the cloud, but they actually want to understand what the data is, understand who's has access to that data, making sure that they're actually making smart business decisions based on that data set. And I think that's where the partnership between both Talend and Snowflake are really tremendous, where, you know, we're helping our customers bring their data assets to to the cloud, really landing it, and allowing them to do multiple different types of workloads on top of this data cloud platform in Snowflake. And then I think, again, what Talend is bringing to the table is really helping the customer make sure that they trust the data that they're actually seeing. And I think that's a really important aspect of digital transformation today. >> Awesome, and I want to get into the partnership, but I don't want to leave the pandemic just yet. A.C., I want to ask you how it's affected customer priorities and timelines with regard to modernizing their data operations. And what I mean to that, I think about the end-to-end life cycle of going from kind of raw data to insights and how they're approaching those life cycles. Data quality is a key part of it. If you don't have good data quality, I mean, obviously you want to iterate, and you want to move fast, but if it's garbage out, then you got to to start all over again. So what are you seeing in terms of the effect of the pandemic and the urgency of modernizing those data operations? >> Yeah, well, like Chris just said, it accelerated things. For those companies that hadn't quite started their digital journey, maybe it was something that they had budgeted for, but hadn't quite resourced completely, many of them, this is what it took to really get them off the dime from that perspective, because there was no longer the opportunity to wait. They needed to go and take care of this really critical component within their business. So, you know, what COVID I think has taught companies, taught all of us, is how vulnerable even the largest companies and most robust enterprises can be. Those companies that had already begun their digital transformation, maybe even years ago, had already started that process and were in a great position in their journey, they fared a lot better, and we're able to be agile, were able to, you know, shift priorities, were able to go after what they needed to do to run their businesses better and be able to do so with real clarity and confidence. And I think that's really the second piece of it is for the last six months, people's lives have really depended on the data. People's lives have really depended on certainty. The pandemic has highlighted the importance of reliable and trustworthy information, not just the proliferation of data. And as Chris mentioned, just data being available. It's really about making sure that you can use that data as an asset. And that the greatest weapon we all have really there is the information and good information to make great business decisions. >> And, of course, Chris, the other thing we've seen is the acceleration to the cloud, which is obviously you (indistinct) born in the cloud. It's been a real tailwind. What are you seeing in that regard from your, I was going to say in the field, but from your Zoom vantage point. >> (laughs) Yeah, well, I think, you know, A.C. talked about supply chain analytics in her previous example. And I think one of the things that we did is we hosted a dataset, the COVID data set, COVID-19 dataset within Snowflake's data marketplace. And we saw customers that were, you know, initially hesitant to move to the cloud really accelerate their usage of Snowflake in the cloud with this COVID data set. And then we had other customers that are, you know, in the retail space, for example, and use the COVID data set to do supply chain analytics and accelerated, you know, it helped them make smarter business decisions on that. So, I'd say that, you know, COVID has made customers that were maybe hesitant to start their journey in the cloud move faster. And I've seen that, you know, really go at a blistering pace right now. >> You know, A.C., you just talked about value, 'cause it's all about value, but you know, the old days of data quality and the early days of chief data officer, all the focus was on risk avoidance, how do I get rid of data, how long do I have to keep it? And that has flipped dramatically, you know, sometime during the last decade. I wonder if you could talk about that a little bit. 'Cause I know you talk to a lot of CDOs out there, and have you seen that flip, where the value piece is really dwarfing that risk piece? And not that you can ignore the risk, but that's almost table stakes. What are your thoughts? >> You know, that's interesting, saying it's almost table stakes. I think you can't get away too much from the need for quality data and governed data. I think that's the first step, you can't really get to trust the data without those components. And, but to your point, the chief data officer's role, I would say, has changed pretty significantly. And in the round tables that I've participated in over the last, you know, several months, it's certainly a topic that they bring to the table that they'd like to, you know, chat with their peers about in terms of how they're navigating through the balance, that they still need to manage to the quality, they still need to manage to the governance, they still need to ensure that they're delivering that trusted information to the business. But now on the flip side as well, they're being relied upon to bring new insights and it's really requiring them to work more cross-functionally than they may have needed to in the past, where that's become a big part of their job is being that evangelist for data, the evangelist for those insights, and being able to bring in new ideas for how the business can operate. And identify, you know, not just operational efficiencies, but revenue opportunities, ways that they can shift. All you need to do is take a look at, for example, retail. You know, retail was heavily impacted by the pandemic this year, and it shows how easily an industry can be just kind of thrown off its course simply by just a significant change like that. And they need to be able to adjust. And this is where, when I've talked to some of the CDOs of the retail customers that we work with, they've had to really take a deep look at how they can leverage the data at their fingertips to identify new and different ways in which they can respond to customer demands. So it's a whole different dynamic, for sure. It doesn't mean that you walk away from the other end, the original part of the role or the areas in which they were maybe more defined a few years ago when the role of the chief data officer became very popular. I do believe it's more of a balance at this point, and really being able to deliver great value to the organization with the insights that they can bring. >> Well A.C., stay on that for a second. So you have this concept of data health, and I guess what I'm kind of getting at is that the early days of big data, Hadoop, it was just a lot of rogue efforts going on. People realized, wow, there there's no governance. And what's what seems like with Snowflake and Talend are trying to do is to make that so the business doesn't have to worry about it, build that in, don't bolt it on. But what's this notion of data health that you talk about? >> Well, it's interesting. Companies can measure and do measure just about everything, every aspect of their business health. Except what's interesting is they don't have a great way to measure the health of their data. And this is an asset that they truly rely on. Their future depends on is that health of their data. And so if we take a little bit of a step back, maybe let's take a look at an example of a customer experience just to kind of make a little bit of a delineation between the differences of data quality, data trust, and what data health truly is. We work with a lot of hotel chains, and like all companies today, hotels collect a ton of information. There's mountains of information, private information about their customers, through the loyalty clubs, and all the information that they collect from their the front desk, the systems that store their data. You can start to imagine the amount of information that a hotel chain has about an individual. And frequently, that information has errors in it, such as duplicate entries, you know, is it A.C. Graham, or is it Ann-Christel Graham? Same person, slightly different, depending on how I might've looked, or how I might've checked in at the time. And sometimes the data's also mismanaged, where because it's in so many different locations, it could be accessed by the wrong person, if someone that wasn't necessarily intended to have that kind of visibility. And so these are examples of when you look at something like that, now you're starting to get into, you know, privacy regulations, and other kinds of things that can be really impactful to a business if data's in the wrong hands or if the wrong data is in the wrong hands. So, you know, in a world of misinformation and mistrust, which is around us every single day, Talend has really invented a way for businesses to verify the veracity, the accuracy of their data. And that's where data health really comes in is being able to use a trust score to measure the data health. And that's what we've recently introduced is this concept of the trust score, something that can actually provide and measure the accuracy and the health of the data, all the way down to an individual report. And we believe that that truly provides the explainable trust, issue resolution, the kinds of things that companies are looking for in that next stage of overall data management. >> Thank you. Chris, bring us home. So one of the key aspects of what Snowflake is doing is building out the ecosystem. It's very, very important. Maybe talk about how you guys are partnering and adding value, in particular things that you're seeing customers do today within the ecosystem or with the help of the ecosystem and Snowflake, that they weren't able to do previously? >> Yeah, I mean, I think, you know, A.C. mentioned it, you mentioned it. I spend a lot of my Zoom days talking to chief data officers. And as I'm talking to these chief data officers, they are so concerned, their responsibility on making sure that the business users are getting accurate data, so that they view that as data governance, as one aspect of it. But the other aspect is the circumference of the data, of where it sits, and who has access to that data, and making sure it's super secure. And I think, you know, Snowflake is a tremendous landing spot, being a data warehouse or a cloud data platform as a service. You know, we take care of all the securing that data. And I think where Talend really helps our customer base is helps them exactly what A.C. talked about, is making sure that myself as a business user, someone like myself, who's looking at data all the time, trying to make decisions on how many salespeople I want to hire, how's my forecast coming, you know, how's the product working, all that stuff. I need to make sure that I'm actually looking at good data. And I think the combination of it all sitting in a single repository like Snowflake, and then layering a tool like Talend on top of it where I can actually say, yeah, that is good data, it helps me make smarter decisions faster. And ultimately, I think that's really where the ecosystem plays an incredibly important role for Snowflake and our customers >> Guys, two great guests. I wish we had more time, but we got to go. And so thank you so much for sharing your perspectives, a great conversation. >> Thank you for having us, Dave. >> Thanks Dave. >> All right, and thank you for watching. Keep it right there. We'll be back with more from The Data Cloud Summit 2020.

>>Hello, everyone. And welcome back to the data cloud. Summer 2020. We're >>gonna >>dig into the all important ecosystem and focusing a little bit on the intersection of the data Cloud and trust and with Me are and Crystal Graham, aka A C. She's the C R O of talent, and Chris Degnan is the C R. O of Snowflake. We have to go to market heavies on this section, folks. Welcome to the Cube. >>Thank you. >>Thanks for having us. >>That's our pleasure. And so let's let's talk about digital transformation, right? Everybody loves to talk about it. It zone overused term. I know, but what does it mean? Let's talk about the vision of the data cloud for snowflake and digital transformation. A. C. We've been hearing a lot about digital transformation over the past few years. It means a lot of things to a lot of people. What are you hearing from customers? How are they thinking about when I come, sometimes called DX and what's important to them? Maybe address some of the challenges even that they're facing where you >>thought. Absolutely. Dave, you know, digital transformation means literally staying in business or not. Um, That's what you hear from customers. Thes days. Eso, you know, most still agree on that. The opportunity Thio modernized data management, bringing efficiencies and scale and cost savings through digital transformation. But now it's really beyond that. What's become front and center is the need for trusted data. Um, and you know, one of the things we could talk a little bit about their Let me give you an example what that means. It's It's really having a agile infrastructure that will allow a company to pivot operations as they need. There's a company that I recently spoke with one of our customers that's in a medical device in the medical device industry, and they had started their digital journey last year. Um, so they were in a really good position when Cove it hit in February. At the time, they needed to take a complete look at their supply chain and optimize it. In fact, they needed to find ways that they could really change their production to a degree of about 20 times more in a given day thing, what they had been doing prior to co vid. And so when you think about what that required them to do. They really needed to rely on trusted, clean, compliant data, um, in an agile, ready to adapt infrastructure. And that's really what digital transformation was to them. And I think that's an example of when you talk to customers today, and they define what digital transformation means to them. You'll find examples like that that demonstrate that in times it's it's really about the difference between, you know, life or death saving lives, staying in business. >>Right? Well, thank you for that. And you're right on. I mean, if you're not a digital business today, you're kind of out of business. And, Chris, I've always said a key part of digital transformation is really putting data at the core of everything. You know, Not not the manufacturing plant, that the core in the data around it, but putting data at the center. It seems like that's what Snowflake is bringing to the table. Can you comment? >>Yeah. I mean, I think if if I look across what's happening and especially a Z A. C said you know, through co vid is customers are bringing more and more data sets. They wanna make smarter business decisions based on data making data driven decisions. And we're seeing acceleration of data moving to the cloud because there's just an abundance of data and it's challenging to actually manage that data on premise and and, as we see those, those customers move those large data sets. Think what A C said is spot on is that customers don't just want to have their data in the cloud. But they actually want to understand what the data is, understand, who has access to that data, making sure that they're actually making smart business decisions based on that data. And I think that's where the partnership between both talent and snowflake are really tremendous, where you know we're helping our customers bring their data assets to to the cloud, really landing it and allowing them to do multiple, different types of workloads on top of this data cloud platform and snowflake. And then I think again what talent is bringing to the table is really helping the customer make sure that they trust the data that they're actually seeing. And I think that's a really, um, important aspect of digital transformation today. >>Awesome and I want to get into the partnership, but I don't wanna leave the pandemic just yet. I wanna ask you how it's affected customer priorities and timelines with regard to modernizing their data operations. And what I mean to that I think about the end and life cycle of going from raw data insights and how they're approaching those life cycles. Data quality is a key part of If you have good data quality, you're gonna I mean, obviously you want to reiterate and you wanna move fast. But if if it's garbage out, then you got to start all over again. So what are you seeing in terms of the effect of the pandemic and the urgency of modernizing those data operations? >>Yeah, but like Chris just said it accelerated things for those companies that hadn't quite started their digital journey. Maybe it was something that they had budgeted for but hadn't quite resourced completely many of them. This is what it took to to really get them off the dying from that perspective, because there was no longer the the opportunity to wait. They needed to go and take care of this really critical component within their their business. So, um, you know what? What cove? In I think has taught cos. Taught all of us is how vulnerable even the largest. Um, you know, companies on most robust enterprises could be, um, those companies that had already begun their digital transformation, maybe even years ago had already started that process. And we're in a better. We're in a great position in their journey. They fared a lot better, and we're able to be agile. Were able Thio in a shift. Priorities were able to go after what they needed to do toe to run their businesses better and be able to do so with riel clarity and confidence. And I think that's really the second piece of it is, um, for the last six months, people's lives have really depended on the data people's lives that have really dependent on uncertainty. The pandemic has highlighted the importance of reliable and trustworthy information, not just the proliferation of data. And as Chris mentioned this data being available, it's really about making sure that you can use that data as an asset Ondas and and that the greatest weapon we all have, really there is the information and good information to make great business decisions. >>Of course, Chris The other thing we've seen is the acceleration toe, the cloud, which is obviously you're born in the cloud. It's been a real tailwind. What are you seeing in that regard from your I was gonna say in the field. But from your zoom vantage >>point? Yeah, well, I think you know, a C talked about supply chain, um, analytics in in her previous example. And I think one of the things that we did is we hosted a data set. The covert data set over 19 data set within snowflakes, data marketplace. And we saw customers that were, you know, initially hesitant to move to the cloud really accelerate. They're used to just snowflake in the cloud with this cove. It covert data set on Ben. We had other customers that are, you know, in the retail space, for example, and use the cova data set to do supply chain analytics and and and accelerated. You know, it helped them make smarter business decisions on that. So So I'd say that you know, Cove, it has, you know, made customers that maybe we're may be hesitant to to start their journey in the cloud, move faster. And I've seen that, you know, really go at a blistering pace right now. >>You know, you just talked about value because it's all about value. But the old days of data quality in the early days of Chief Data officer, all the focus was on risk avoidance. How do I get rid of data? How long do I have to keep it? And that has flipped dramatically. You know, sometime during the last decade, I wonder if you could talk about that a little bit because I know you talked to a lot of CDOs out there. And have you seen that that flip, that where the value pieces really dwarfing that risk, peace. And not that you can. You can ignore the risk that. But that's almost table stakes. What are your thoughts? >>Um, you know, that's interesting. Saying it's it's almost table stakes. I think we can't get away too much from the need for quality data and and govern data. I think that's the first step. You can't really get to, um, you know, to trust the data without those components. And but to your point, the chief data officers role, I would say, has changed pretty significantly and in the round tables that I've participated in over the last, you know, several months. It's certainly a topic that they bring to the table that they'd like Thio chat with their peers about in terms of how they're navigating through the balance that they still need. Thio manage to the quality they still need to manage to the governance. They still need toe to ensure that that they're delivering, um, that trusted information to the business. But now, on the flip side as well, they're being relied upon to bring new insights. And that's, um, it Z really require them to work more cross functionally than they may have needed to in the past. Where that's been become a big part of their job is being that evangelist for data the evangelist. For that, those insights and being able to bring in new ideas for how the business can operate and identified, you know, not just not just operational efficiencies, but revenue opportunities, ways that they can shift. All you need to do is take a look at, for example, retail. Um, you know, retail was heavily impacted by the pandemic this year on git shows how easily an industry could be could be just kind of thrown off its course simply by by a just a significant change like that. They need to be able to to adjust. And this is where, um, when I've talked to some of the CEOs of the retail customers that we work with, they've had to really take a deep look at how they can leverage their the data at their fingertips to identify new in different ways in which they can respond to customer demands. So it's a it's a whole different dynamic for sure. It doesn't mean that that you walk away from the other and the original part of the role of the or the areas in which they were maybe more defined a few years ago when the role of the chief data officer became very popular. I do believe it's more of a balance at this point and really being able to deliver great value to the organization with the insights that they could bring >>Well, a C stay on that for a second. So you have this concept of data health, and I guess what kind of getting tad is that the early days of big data Hadoop. It was a lot of rogue efforts going on. People realize, Wow, there's no governance And what what seems like what snowflake and talent are trying to do is to make that the business doesn't have to worry about it. Build that in, don't bolted on. But what's what's this notion of of data health that you talk about? >>Well, the companies you know, it's it's It's interesting Cos can measure and do measure just about everything, every aspect of their business. Health. Um, except what's interesting is they don't have a great way to measure the health of their data. And this is an asset that they truly rely on. Their future depends on is that health of their data? And so if we take a little bit of a step back, maybe let's take a look at an example of a customer experiences to kind of make a little bit of a delineation between the differences of data data, quality data, trust on what data health truly is, We work with a lot of health, a lot of hotel chains, and like all companies today, hotels collect a ton of information. There's mountains of information. Um private information about their customers through the loyalty clubs and all the information that they collect from there the front desk, the systems that store their data. You can start to imagine the amount of information that a hotel chain has about an individual. And, uh, frequently that information has, you know, errors in it, such as duplicate entries, you know. Is it a Seagram or is it in Chris Telegram? Same person, Slightly different, depending on how I might have looked or how I might have checked in at the time. And sometimes the data is also mismanaged, where because it's in so many different locations, it could be accessed by the wrong person of someone that wasn't necessarily intended to have that kind of visibility. And so these are examples of when you look at something like that. Now you're starting to get into, um, you know, privacy regulations and other kinds of things that could be really impactful to a business if data is in the wrong hands or the wrong data is in the wrong hands. So you know, in a world of misinformation and mistrust, which is around us every single day, um, talent has really invented a way for businesses to verify the veracity, the accuracy of their data. And that's where data health really comes in is being able to use a trust score to measure the data health on. That's what we have recently introduced. Is this concept of the trust score, something that can actually provide and measure the accuracy and the health of the data all the way down to an individual report on? We believe that that that truly, you know, provides the explainable trust issue resolution, the kinds of things that companies are looking for in that next stage of overall data management. >>Thank you, Chris. Bring us home. So one of the key aspects of what snowflake is doing is building out the ecosystem is very, very important. Maybe talk about how how you guys air partnering and adding value in particular things that you're seeing customers do today within the ecosystem or with the help of the ecosystem and stuff like that they weren't able to do previously. >>Yeah. I mean, I think you know a C mentioned it. You mentioned it. You know, we spent I spent a lot of my zoom days talking Thio chief data officers and as I'm talking to the chief data officers that they are so concerned their responsibility on making sure that the business users air getting accurate data so that they view that as data governance is one aspect of it. But the other aspect is the circumference of the data of where it sits and who has access to that data and making sure it's super secure. And I think you know, snowflake is a tremendous landing spot, being a data warehouse or data cloud data platform as a service, you know, we take care of all, you know, securing that data. And I think we're talent really helps our customer base is helps them. Exactly what it is he talked about is making sure that you know myself as a business users someone like myself who's looking at data all the time, trying to make decisions on how many sales people I wanna hire. How's my forecast coming? How's the product working all that stuff? I need to make sure that I'm actually looking at at good data, and I think the combination of all sitting in a single repository like snowflake and then layering it on top or laying a tool like talent on top of it, where I can actually say, Yeah, that is good data. It helps me make smarter decisions faster. And ultimately, I think that's really where the ecosystem plays. An incredibly important, important role for snowflake in our customers, >>guys to great guests. I wish we had more time, but we got to go on. DSo Thank you so much for sharing your perspective is a great conversation. >>Thank you for having a Steve. >>All right. Thank you for watching. Keep it right there. We'll be back with more from the data cloud Summit 2020.

ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 alright so we've got a fantastic event today really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event this is not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a take-off of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any powerpoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got Simone Rashard Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the u.s. it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Frank kibrit you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission critical they care about visibility they care about control they care about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers did they see the same thing we're gonna validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is architecture again with IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're gonna talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day 2 operations what does that mean well day 1 is one day of your life that's who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do I operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix we as leaders do we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CCI ease where Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when to try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of tube Jon Fourier okay awesome great great speech they're awesome I'd totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix were we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel two customer panels before that Gartner is going to come on talk about the industry we have a global system integrators we talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask someone rashard to come on stage from Gartner check it all up [Applause] okay so kicking things off sitting started gartner the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer in a 92 a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering at the marketplace with hybrid cloud and now moving quickly to multi cloud is really was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow I to your application people are some kind of DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right with different account and they create mesh to manage them and their direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides that the audinate that are sent removing that to that cloud and I ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the ad hoc way doesn't scale at some point idea has to save them because they don't think about the two they don't think about operations they have a bunch of VPC and multiple clouds the other way that if you do the left and shift wake they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these ways are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct then that's what I call the optimal phase but even that they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS has accounts there's subscription and in adarand GCP their projects it's a real mess so they realize well I can't really like concentrate use the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that I still wanna manage the cloud from an API to interview I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they really building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway I'm just a joke what do you see in terms of where people are in that multi-cloud so a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in deserve one app in individuals one get happen Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never going to happen what I've seen with enterprise is I'm gonna put the workload in the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking team be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while their network part of the cloud connectivity to the cloud is kind of simple I agree IPSec VP and I reckon Express that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which free cloud providers right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean this is the day-to-day operations after you know the natural let's add an app let's add a server let's troubleshoot a problem so so your life something changes how would he do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's been a hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi cloud wave that's coming as cloud native networking well there's no you know official garner definition but I can create one on and if another spot is do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't even understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose api's where is that optimization where's the focus well I take what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of the cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of you right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plane out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that plane out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and ship or they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco monks bring you star and the cloud recall that each guy anywhere right so everyone what and and then there's cloud vision for my red star and contrail is in the cloud so they just want to bring the management plane in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not truly cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive clown that so close one letter yeah so that was a big con surgeon reinvent take the tea out of cloud native it's cloud naive that went super viral you guys got t-shirts now I know you love but yeah but that really ultimately is kind of double edged sword you got to be you can be naive on the on the architecture side and rolling out but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in Cisco you it's a little bit more native than other ones because they're really scr in the cloud you can't you you really like configure API so the cloud and NSX is going that way and so is Arista but they're incumbent they have their own tools is difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know a network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like al kira for example that just started now that doing more connectivity but they wanna create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week oh the only b2 networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like aviation others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in AWS you can user it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck Nets a cops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you this programmability their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get every line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this VP see but this VP see automatically being associate to your account you cannot go out on the internet you have to go to the transit VP see so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI mace which for us old folks know what that means but you guys know what this means I want to ask you the question as you look at the future of networking here a couple of objectives oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well as I said earlier that once you you could easily provision in the cloud you can easily connect to that cloud is when you start troubleshooting application in the cloud and try to scale so this that's where the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead to 20% extra functionality that of course every Enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that Cambrian explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always gonna be that extra functionality the in in an automated and simple way that you talked about but yet powerful with up with the visible in control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggers who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some the signals that are going on in their environment what are some of the thresholds or things that are going on that there can pay attention to well well once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robber will hit the road but as I said it's easier to prove it it's ok it's 80s it's easy use a transit gateway put a few V PCs and you're done and use create some presents like equinox and do Direct Connect and Express route with Azure that looks simple is the operations that's when they'll realize ok now I need to understand our car networking works I also need a tool that give me visibility and control not button tell me that I need to understand the basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi Bob because you think about what's happening it kind of has that same vibe of interoperability choice multi-vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client server and internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this more because honestly public cloud check hybrid cloud they're working on that that gets on-premise is done now multi clouds right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what there's cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start with especially an incumbent one so it's tempting to say on and I have a bunch of f5 experts nothing against that five I'm going to bring my five in the cloud when you can use a needle be that automatically understand Easy's and auto scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that met I'm going to use legacy stuff and then you have to start thinking okay what about visibility control about the tree cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming someone in charge with Gardner thanks for sharing informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in the business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of that data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement with aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for her aviatrix already working in Amazon and now works in Missouri as well before we knew what GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake assure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at 3 o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build or done in hours I think the most important thing about a matrix is it provides me a Beatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments David should Nick with fact set guys welcome to the stage for this digital event come on up [Applause] [Music] hey good to see you thank you okay okay customer panelist is my favorite part we get to hear the real scoop gets a gardener given this the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with a live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and is soon gonna be a lot more coming so we want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets and different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting which what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation 'el opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on bram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we're we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources from Azure like HPC you know as your ad things like that even recently Google Google Analytics our journey has evolved into more of a multi cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you you know had some comments about architecture matters it all starts I mean every Enterprise I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a fun architecture perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network marketer and we call it networking security net SEC yeah versus Justice Network yeah and that fourth generation architectures be based primarily upon Palo Alto Networks an aviatrix I have Atrix doing the orchestration piece of it but that journey came because of the need for simplicity ok the need for a multi cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around how we provision networks but cloud formation has become a little bit like the new manual for us so we we're now having issues with having the to automate that component and making it consistent with our on premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that SEO and brought to the to the web side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was some of the that's probably the biggest list and there is that when you think you finally figured it out you have it right Amazon will change something as you or change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective we like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's that I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those that we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gate without a trans a gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and in evolve later and maybe optimize or change the way you're doing things in the future but don't sit around and wait you can't I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model how do I do my day one work so that I'm not you know spending 80 percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice the architect I don't know what else I can do that simplicity operations is key right all right so the holistic view of j2 operation you mentioned let's can jump in day one is your your your getting stuff set up day two is your life after all right this is kind of what you're getting at David so what does that look like what are you envisioning as you look at that 20 mile stare at post multi-cloud world what are some of the things that you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router seoi and troubleshooting things on in an ad hoc nature so moving more towards the DevOps model yes anything on that day - yeah I would love to add something so in terms of day 2 operations you can you can either sort of ignore the day 2 operations for a little while where you get well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to realize it's it's such as such a big gap I think that's key because for us we're moving to more of an event-driven operations in the past monitoring got the job done it's impossible to modern monitor something there's nothing there when the event happens all right so the event-driven application and then detection is important yeah I think Gardiner was all about the cloud native wave coming into networking that's going to be here thing I want to get your guys perspectives I know you have different views of how you came on into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies the network's laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have a requirement to encrypt and they never get the question should I encryption or not encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely expense in some cases so we have been mandated that we have to encrypt everything leave from the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you've got a lot of complexity in your network what do you guys look at the future for yours environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance of things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secured in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting and get a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's okay we want to hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like encryption and things like so you're encrypting tunnels and crypting the path and those things are it should it should should be second nature really when you when you look at building those back ends and managing them with your team it becomes really painful so tools like a Beatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I'll see aviatrix is here they're their supplier to this sector but you guys are customers everyone's pitching you stuff people are not going to buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's that what's it like we're API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like it's definitely it's definitely API driven we we definitely look at the at the PAP i structure of the vendors provide before we select anything that that is always first in mind and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking and more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what do what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on site and they're gonna sit with you for your day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so I you know having having some ease-of-use and the team being comfortable with it and understanding it is really important Bobby how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore but what's the Volvic a bake-off last year for us do you win so but that's different now because now when you when you get the product you can install the product and they double your energy or have it in a matter of minutes and so the key is is they can you be operational you know within hours or days instead of weeks but but do we also have the flexibility to customize it to meet your needs could you want to be you want to be put into a box with the other customers when you have needs that your pastor cut their needs yeah almost see the challenge that you guys are living where you've got the cloud immediate value depending how you can roll up any solutions but then you have might have other needs so you got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and experimenting with the different concepts of cloud and and really leveraging the the native constructs of each cloud but but there's a there's a breaking point for sure you don't you don't get to scale this like Alexa mom said and you have to focus on being able to deliver a developer they're their sandbox or they're their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so use a lot more stuff to be coming pretty quickly hides area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms-up organization Nick pops you're kind of like off a little bit it's not how it works I mean what is the reality in terms of implementing you know in as fast as possible because the business benefits are but it's not always clear in the technology how to move that fast yeah what are some of the barriers one of the blockers what are the enablers I think the reality is is that you may not think you're multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements and then secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go yeah scale is a big part of what I see is the competitive advantage to a lot these clouds and needs to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the upfront from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business need and and like like you said it's whether whether you're in denial or not of the multi cloud fact that then your company is in already that's it becomes really important for you to move quickly yeah and I a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or Azure and just helping facilitate things they're doing the you know the heavy lifting API work for you or are they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know makes you have designed yourself into a corner so the closer they're more than cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will it make sense tgw is a game changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool give you the beauty of both worlds you can use tgw with a gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go Mull one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint do you agree with that premise and then witness multi-cloud stitch them all together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction that value but the the network problem is still the same doesn't go away yeah yeah yeah I mean you don't want to be trying to fit a square into a round Hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the network infrastructure is there secure is available and is multi cloud capable yeah I'm at the end of the day you guys just validating that it's the networking game now cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate it thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John fritz T Blaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Koopa welcome to stage [Applause] all right thank you thank you okay he's got all the the cliff notes from the last session welcome back rinse and repeat yeah yeah we're going to go under the hood a little bit I think I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move a pack from A to B and you get workloads exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds and that's like I mean almost sounds impossible to me what's your take yeah I mean it it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to iterate and make improvements over the time we get to Justin's over here so I have to be careful when I point a question in Justin they both have the answer but okay journeys what's the journey been like I mean is there phases we heard that from Gartner people come in to multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from our perspective we started out very much focused on one cloud and as we started doing errands we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tore in the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are available and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really that's the enabler for this multi cloud trend but you guys taken we'll start with Amit what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it matter of how you are going to build your networks how we are gonna run security how we are going to do egress ingress out of it so it's a big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditionally on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make a sense of all of that and I think that's where tools like a v8 ryx make a lot of sense in that space from our site it's it's really simple its latency its bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea our job is to enable them not to disable them do you think you guys think infrastructure is code which I love that I think it's that's the future it is we saw that with DevOps but I do start getting the networking is it getting down to the network portion where it's network is code because storage and compute working really well is seeing all kubernetes and service master and network as code reality is it there is got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same unit yeah and even security groups and then on top an aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us was similar on-premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored Confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made because it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now I want to pick up on what you said to you others agree that the center of architect of gravity is here I'm now pushing what I do in the cloud back into on pram and and then so first that and then also in the journey where are you at from 0 to 100 of actually in the journey to cloud DUI you 50% there are you 10% yes I mean are you evacuating data centers next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together right in our case the data gravity sold mostly on Prem but our network is now extending out to the app tier that's going to be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of you know lift and shift and when did that start and we started about three years ago okay okay go by it's a very different story it started from a garage and one hundred percent on the clock it's a business spend management platform as a software-as-a-service one hundred percent on the cloud it was like ten years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask user you guys mentioned DevOps I mean obviously we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this isn't about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interesting we we have moved from having a backbone that we bought that we own that would be data center connectivity we now I work for as or as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth I think availability with your sim pop3 things guys SLA I mean you just do ping times between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workload I mean SL leis will be all over the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and what our ability is hour is there and our authority needs to operate on that so it's solely use the software dashboard look at the times and look at the latency in the old days strong so on open so on you try to figure it out and then your day is you have to figure out just and what's your answer to that because you're in the middle of it yeah I mean I think the the key thing there is that we have to plan for that failure we have to plan for that latency and our applications it's starting start tracking in your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment or was it was it from day one now there are two divisions one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so it has a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot network load or you are going to run machine learning or AI so that you have you would have that preference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting is how do I solve or guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just on your thoughts on that I think any comment on that so actually multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as those are acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are haiku people using them but Google's got a great Network Google's networks pretty damn good and then you got a sure what's the difference between the clouds who where they've evolved something whether they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes Azure better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is the approach is different in many places Google has a different approach very devops friendly and you can run your workload like your network can spend regions time I mean but our application ready to accept that MS one is evolving I mean I remember ten years back Amazon's network was a flat network we will be launching servers and 10.0.0.0 mode multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the I mean I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of that in mine is your architectural and solution for example Amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has advantages there to market and so it has seen what asier did wrong it's seen what AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the the inability or the ability for Amazon to limit layer 2 broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional Network facilities to us it's just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive question so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like when is the new land so if you think about what the land was at a data center when is the new link you get talking about the cloud impact so that means st when the old st was kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high speed but now when you take the win and make essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah I think it's the it's a thing that you have to work with your application architect so if you are managing networks and if you're a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the Layton sees and and the reliability has to be worked through the application there land when same concept as it be yesterday I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native when we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way than it was in a land that's what we're seeing so much infrastructure as code yeah yeah so for me I'll go back again to this its bandwidth and its latency right that bet define those two land versus win but the other thing that's comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to protect what's inside of it so for us we're able to deliver VRS or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning that's architecture thoughts on security are you guys are dealing with it yeah start from the base have app to have security built in have TLS have encryption on the data I transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principals day Security's day zero every day and so we we always build it into our design we load entire architecture into our applications it's encrypt everything it's TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff was interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now he being sure he's gonna got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to you know supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us its main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive and think that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for twenty years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we have we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's are you being closed-minded native being open-minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total B yes what what triggers use it so that I have two lines out of movies that are really I can if the if I say them without actually thinking them it's like 1.21 jigowatts how you're out of your mind from Back to the Future right somebody's gonna be a bank and then and then Martin ball and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speeds would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and okay 220 221 anytime I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need to benchmark yourself don't don't listen to the marketing on that that's that's all I'm a what triggers you and the bsp I think if somebody explains you a not simple they cannot explain you in simplicity then that's a good one all right guys thanks for the great insight great panel how about a round of applause practitioners DX easy solutions integrating company than we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba corkle will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs its when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products that incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the lance cloud connectivity there's a new line of networking services that we're getting into as our clients move into hybrid cloud networking it is much different than our traditional based services an aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a v8 church we were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed for work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole in their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basic law providing services we're taking our customers on a journey to simplify and optimize their IT infrastructure aviatrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John Ford with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native networking we heard from the customer panel you can see the diversity of where people come into the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk journey to multi cloud what do you guys seeing yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are exactly you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we were having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying we're starting to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the apps and then we evolved into that next journey which is a foundational approach to what are some of the problem statement customers are solving when they come to you what are the top things that are on their my house or the ease of use of jelly all that stuff but what specifically they did digging into yeah some complexity I think when you look at multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do and this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard part is now upon us are you referring to networking what is specifically were you getting at Tara so the easy parts done now so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises that are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the >> so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it okay in our internal environment as yeah you know we're a huge company or right customer zero or an IT so we're experiencing that internal okay and every one of our other customers so I have another question oh I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway d XE @ wwt massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that it worldwide technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking but simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the at the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I what I get excited about is not just putting yours in our lab and showing customers how it works it's Co developing a solution with you figuring out hey how can we make this better right mr. piller is a huge thing Jenna insecurity alone Network everything's around visibility what automation do you see happening in terms of progression order of operations if you will it's the low-hanging fruit what are people working on now and what are what are some of the aspirational goals around when you start thinking about multi cloud and automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were going to integrate those solutions you know we like to build everything with recipes where Network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of a VHS let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference architectures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi cloud in terms of you know customers want choice didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and be risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud applications a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an Billy approaches how do things interoperate we test it out we validate it we build a reference architecture it says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it invisibility so I think the visibility is what's what I see lacking across the industry today and the cloud needed that's been a big topic yep okay in terms of aviatrix that you guys see them coming in there one of the ones that are emerging and the new brands emerging with multi cloud you still got the old guard incumbents with huge footprints how our customers dealing with that that kind of component in dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question while we were defining de to operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does de two operations mean what's the definition of that yeah so I think from our perspective my experience we you know de to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve that the the cloud is very dynamic the the nature of how that fast is expanding the number of features is astonishing trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is that what's what happens there they call you up and say hey I need multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's looks like typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we got a factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what does VPC sharing you know what is a private link and Azure how does that impact your business you know customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts George oh yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah when I then is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to meet their connectivity needs it so the patterns are similar great final question for you guys I want to ask you to paint a picture of what success looks like and you know for name customers you don't forget in reveal of kind of who they are but what does success look like in multi-cloud as you as you paint a picture for the folks here and watching on the live stream it's if someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in that is you build that network foundation an architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi-cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off Prem and so collectively I think the key is also is that we provide them an hld you got to start with in a high-level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed had a success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen what what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators [Applause] [Music] okay welcome back from the live feed I'm shuffle with the cube Steve Eleni CEO of aviatrix my co-host our next panel is the aviatrix certified engineers also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foster min from Attica Stacy linear from Terra data and Jennifer Reid with Victor Davis to the stage I was just gonna I was just gonna rip you guys and say where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear there above the clouds soaring to new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like a squadron leader Roger and leader yeah squadron leader so he's got a bunch of aces underneath him but share your perspective day-in-the-life Jeff we'll start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm eagerly working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but networking in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hmm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the V PCs and on the instant side is a security group or is it going on print and this is something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this such for 25 years but I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software and they work takes care of itself yes I'll be will get I'll come back to that I want to come back to that that problem solved with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in network have always been the network's fault and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you got a full stack DevOps you gotta know a lot more times another hundred and these times are changing yeah they say you're a squadron leader I get that right what is what does a squadron leader first can you describe what it is I think probably just leading all the network components of it but not they from my perspective when to think about what you asked them was it's about no issues and no escalation soft my day is a good that's a good day yes it's a good day Jennifer you mentioned the Amazon thing this brings up a good point you know when you have these new waves come in you have a lot of new things newly use cases a lot of the finger-pointing it's that guy's problem that girl's problem so what is how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in well is where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Stephen the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear but what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are full logs well as long as we turned on the flow logs when they built it you know and there's like each one of those little things that well if they had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before we came on up on stage about your career you've been networking all your time and then you know you're now entering a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about you know that's dimmer fault I walk in bare feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young P so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way or you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and old guys that's where we thrive Jennifer you mentioned you you got in from the Marines health spa when you got into networking how what was it like then and compared it now almost like we heard earlier static versus dynamic don't be static cuz then you just set the network you got a perimeter yeah no there was no such thing ya know so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it now I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network crimped five cat5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that it became Victor Davis but we went to help one of our customers Davis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this were the program abilities it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how a double u.s. senator and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable cuz we heard the global si help the business issues what does it mean to do that is it code is that networking is it configuration is that aviatrix what is the I mean op C aviatrix is the ASA certification but what is it about the multi cloud that makes it multi networking and multi vendor easy answer is yes so you got to be a generalist getting your hands and all you have to be right it takes experience because it's every every cloud vendor has their own certification whether that's hops and advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not gonna solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through with those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe months ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed good is that watching leader would put there yeah is that something that you see in your organization's are you recommending that to people do you see I mean I'm just I guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I say from my side because we operate in the multi cloud environment so it really helps and it's beneficial for us yeah I think I would add that uh networking guys have always needed to use certifications to prove that they know what they know right it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters buying helps give you validity um so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics and enough of the understandings that you have the tools necessary right so I guess my final question for you guys is why an eighth certification is relevant and then second part is share what the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why shouldn't someone want to be an ace-certified I'm uses the right engineer I think my views a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get no I mean they're backwards so when you've got the training and the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding of ok so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network definitions eating eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that's just the next progression there I would say I expand that to more automation engineers because we have those now probably extended as well well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but I've never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes them better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who have tradition down on Prem networking they can understand how that's going to work in the cloud - well I know we've got just under 30 seconds left I want to get one more question than just one more for the folks watching that are maybe younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacey we'll start with you we'll go down I'd say it's probably fundamental right if you don't deliver solutions networking use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you you've come from top down now you're gonna start looking from bottom up and you want those different systems to cross communicate and say you built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the how the pipes are working and because know what's going some plumbing that's right and the works a how to code it that's right awesome thank you guys for great insights ace certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John Currier yeah so great event great event I'm not going to take long we've got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the Aces you know for those of you out on the stream here become a certified right it's great for your career it's great for knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the Cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community bh6 comm starting a community at multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as to start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more importantly where they're going in that in-state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we saw we help you cook define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their twenty-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music]

ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 all right so we've got a fantastic event today really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a take-off of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any powerpoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got Simone Rashard Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the u.s. it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Frank kibrit you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission critical they care about visibility they care about control they care about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers do they see the same thing we're gonna validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're gonna talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day 2 operations what does that mean well day 1 is one day of your life that's who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do I operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix as leaders knew we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CC IES where Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of Tube John Fourier okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel two customer panels before that Gartner is going to come on talk about the industry we have a global system integrators we talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask someone rashard to come on stage from Gartner we'll check it all up [Applause] [Music] okay so kicking things off certain started gartner the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer in the 90 to a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering at the marketplace with hybrid cloud and now moving quickly to multi cloud is really I was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow whitey or application people or some kind of DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right with a different account and they create mesh to manage them and their direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides the data that are sent removing that to that cloud and I ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the adduct way doesn't scale at some point idea has to save them because they don't think about the two they don't think about operations they have a bunch of VPC and multiple clouds the other way that if you do the left and shift wake they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these ways are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct then that's I would I call the up optimal phase but even that they they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS has accounts there's subscription and in adarand GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that I still wanna manage the cloud from an API to interview I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they really building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway I'm just a joke what do you see in terms of where people are in that multi cloud a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in deserve one app in individuals one get happened Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never going to happen what I've seen with enterprise is I'm gonna put the workload in the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking team be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run Network part of the cloud connectivity to the cloud is kind of simple I agree IPSec VP and I reckon Express that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud provider right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean this is the day-to-day operations after it you know the natural let's add an app let's add a server let's troubleshoot a problem so what so your life something changes how would he do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's been a hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi-cloud wave that's coming as cloud native networking well there's no you know official garner definition but I can create one on another spot it's do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't even understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose api's where is that optimization where's the focus well I take what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of the cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of you right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plane out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that plane out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and ship or they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco monks bring you star in the cloud recall that each guy anywhere right so everyone what and and then there's cloud vision for my red star and contrail is in the cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not truly cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive clown that close one letter yeah so that was a big con surgeon i reinvent take the tea out of cloud native its cloud naive i went super viral you guys got t-shirts now i know you love it but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling out but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in cisco you it's a little bit more native than other ones because they're really ACI in the cloud you call you you really like configure api so the cloud and nsx is going that way and so is Arista but they're incumbent they have their own tools it's difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know and network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week oh the only b2 networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like AV X and others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in AWS you can user it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck Nets a cops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this program their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it via line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this VP see but this VP see automatically being your associate to your account you cannot go out on the internet you have to go to the transit VP C so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI mace which for us old folks know that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objectives oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well I as I said earlier that once you you could easily provision in the cloud you can easily connect to that cloud is when you start troubleshooting application in the cloud and try to scale so this that's where the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead the 20% extra functionality that of course every enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always gonna be that extra functionality the in in an automated and simple way that you talked about but yet powerful with up with the visibility and control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggards who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some the signals that are going on in their environment what are some of the threshold or things that are going on that there can pay attention to well well once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robber will hit the road but as I said it's easier to prove it it's okay it's 80s it's easy user transit gateway put a few V pcs and you're done and use create some presents like equinox and do Direct Connect and Express route with Azure that looks simple is the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not button tell me that I need to understand the basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi-vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server and internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this market because honestly public check hybrid cloud they're working on that that gets on-premise is done now multi-class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what their cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start to it especially an incumbent one so it's tempting to say on and I have a bunch of f5 experts nothing against f5 I'm going to bring my five in the cloud when you can use a needle be that automatically understand ease ease and auto-scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that net I'm going to use legacy stuff and then you have to start thinking okay what about visibility control about the tree cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming someone in charge with Gardner thanks for sharing thank you appreciate it [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of them data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement with aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for aviatrix already working in Amazon and now works in Missouri as well before we knew it GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake assure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build are done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments and David should Nick with fact set guys welcome to the stage for this digital event come on up [Music] hey good to see you thank you okay okay customer panelist is my favorite part we get to hear the real scoop we got the gardener giving us the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with the live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and it's soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets in different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation 'el opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on pram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into mortal multi-cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi-cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you you know had some comments about architecture matters it all starts I mean every Enterprise that I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep adverse adjusters network and that fourth generation or architectures be based primarily upon Palo Alto Networks an aviatrix a matrix doing the orchestration piece of it but that journey came because of the need for simplicity okay I need for multi-cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having to to automate that component and making it consistent with our on-premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that SD when brought to the to the wine side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was some of the there was a path that's probably the biggest list and there is when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those there we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gate without a transit Gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and in evolve later and maybe optimize or change the way you're doing things in the future but don't sit around and wait you can I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's the David yeah talking as earlier about day two operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice the architect I don't know what else I can do that simplicity of operations is key alright so the holistic view of day to operation you mentioned let's can jump in day one is your your your getting stuff set up day two is your life after all right this is kinda what you're getting at David so what does that look like what are you envisioning as you look at that 20 mile stair out post multi-cloud world what are some of the things that you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router CLI and troubleshooting things on in an ad hoc nature so moving more towards the DevOps model is anything on that day - yeah I would love to add something so in terms of day 2 operations you can you can either sort of ignore the day 2 operations for a little while where you get well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to realize it's it's such a such a big gap I think that's key because for us we're moving to more of an event-driven or operations in the past monitoring got the job done it's impossible to modern monitor something there's nothing there when the event happens all right so the event-driven application and then detect is important yeah I think garden was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the networks laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an intern crypt and they they ever get the question should I encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you've got a lot of complexity in your network what do you guys look at the future for yours environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance of things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting and get a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok we want to hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I see AV traces here they're they're a supplier to the sector but you guys are customers everyone's pitching you stuff people are not gonna buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like where API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like um it's definitely it's definitely API driven we we definitely look at the at that the API structure of the vendors provide before we select anything that that is always first in mind and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking become more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what it what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on site and they're gonna sit with you for your day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important Bobby how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's the Volvic bake-off last year first you win so but that's different now because now when you you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so the key is is they can you be operational you know within hours or days instead of weeks but but do we also have the flexibility to customize it to meet your needs could you want to be you won't be put into a box with the other customers we have needs that surpass their cut their needs yeah I almost see the challenge that you guys are living where you've got the cloud immediate value to make an roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's a there's a breaking point for sure you don't you don't get to scale this I like like Simone said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've got a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization think pause you're kind of like off a little bit it's not how it works I mean what is the reality in terms of implementing you know and as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers one of the blockers what are the enabler I think the reality is is that you may not think you're multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements in a secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to allow these clouds and used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the moment from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business team and and like like you said it's whether whether you're in denial or not of the multi cloud fact that your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or sure and just helping facilitate things they're doing the you know the heavy lifting API work for you or they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know makes you have designed yourself into a corner so the closer they're more cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will it make sense tgw is a game-changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool give you the beauty of both worlds you can use tgw with a gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go Mull one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint do you agree with that premise and then wit is multi clouds did you mall together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction that add value but the the network problem is still the same doesn't go away yeah yeah I mean you don't want to be trying to fit a square into a round hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the network infrastructure is there secure is available and is multi cloud capable yeah I'm at the end of the day you guys just validating that it's the networking game now how cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John fritz T Blaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Cooper welcome to stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move a pack from A to B and you get workloads exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your take yeah I mean it's it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to ET rate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like - we started out very much focused on one cloud and as we started doing errands we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are of and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really that's the enabler for this multi cloud trend but you guys taken we'll start with Amit what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it's the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make them a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea now our job is to enable them not to disable them do you think you guys think infrastructure as code which I love that I think it's that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network as code because storage and compute working really well is seeing all kubernetes on ServiceMaster and network is code reality is it there is it still got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way we get to do it yeah and even security groups and then on top and aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us it was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made because it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on Prem and wait and then so first that and then also in the journey where are you at from zero to a hundred of actually in the journey to cloud do you 50% there are you 10% yes I mean are you evacuating data centers next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together right in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's going to be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of you know lift and shift and when did that start and we started about three years ago okay okay go by it's a very different story it started from a garage and one hundred percent on the clock it's a business spend management platform as a software-as-a-service one hundred percent on the cloud it was like ten years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you Sora you guys mentioned DevOps I mean obviously we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this layer this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interestingly we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for soar as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth availability with your sim pop3 things guys SLA I mean you just do ping times are between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads I mean s LA's will be all over the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and whatever ability is our is there and our authority needs to operate on that so it's so you use the software dashboard look at the times and look at the latency in the old days strong so on open so on you try to figure it out and then your days you have to figure out just what she reinsert that because you're in the middle of it yeah I mean I think the the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that start thinking start tracking in your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment was it was it from day one no there were two reasons one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot Network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting is how do I solve or guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just in your thoughts on anything any common uh so actually a multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are how could people using them but Google's got a great network Google's networks pretty damn good and then you got a sure what's the difference between the clouds who with they've evolved something whether they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is approaches different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network and spend regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the yeah I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architectural solution for example amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has advantages its third to market and so has seen what Asia did wrong it seemed with AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the inability or the ability for Amazon to limit layer 2 broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional Network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you could talking about the cloud impact so that means st when the old st way is kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high-speed but now when you take the win and make it essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah I think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you are a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there Lanois same concept is that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's where is what you're seeing so much infrastructure as code yeah yes so for me I'll go back again to this its bandwidth and its latency right that bet define those two land versus win but the other thing that's comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to to protect what's inside of it so for us we're able to deliver vr af-s or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning this architecture thoughts on security are you guys are dealing with it yeah start from the base have apt to have security built in have TLS have encryption on the data I transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principles day Security's day zero every day and so we we always build it into our design build into our architecture into our applications it's encrypt everything it's TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff is interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive and think that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's are you being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total BS but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's getting a bang and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need to benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great time how about a round of applause DX easy solutions integrating company than we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba corkle will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products have incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the Lyons cloud connectivity is a new line of networking services so we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services and aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a VA Church were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed to work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole and their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT maybe Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John Ford with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we just heard from the customer panel you can see the diversity of where people come in to the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are exactly you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we're having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the and then we evolved into the next journey which is a foundational approach to what are some of the problem statement customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they digging into yeah so complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we tis anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard part's now upon us are you referring to networking what is specifically were you getting at Terrance's the easy parts done now so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the - so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it not okay in our internal environment as you know we're a huge company or as customers so we're experiencing that internal okay and every one of our other customers so I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c + w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking let's simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I would I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better right visibility's a huge thing jump in security alone network everything's around visibility what automation do you see happening in terms of progression order of operations if you will it's a low-hanging fruit what are people working on now what are what are some of the aspirational goals around when you start thinking about multi cloud and automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were gonna integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of a VHS let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference textures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi-cloud in terms of you know customers want choice they didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and be risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an interoperability approach is how do things interoperate we test it out we validate it we build a reference architecture it says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it in visibility so I think the visibility is what's what I see lacking across the industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in they're one of the ones that are emerging and the new brands emerging but multi-cloud you still got the old guard incumbents with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question while we were defining day two operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve the the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonish trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is that what's what happens do they call you up and say hey I need some multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's looks like typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got a factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what is VP she's sharing you know what is a private Lincoln or how does that impact your business we have customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I then is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to beep their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't forget in reveal kind of who they are but what does success look like in multi-cloud as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in that as you build that network foundation that architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off from and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen what what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good point guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators Hey [Applause] [Music] okay welcome back from the live feed I'm chef for with the cube Steve Eleni CEO of aviatrix my co-host our next panel is the aviatrix certified engineers also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foster min from Attica Stacy linear from Teradata and Jennifer Reid with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds towards a new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like a Squadron Leader Roger and leader yeah Squadron Leader so he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer will start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm eagerly working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but now working in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hmm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the VP C's and on the instance side is a security group or is it going on print and this is something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and I actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be we'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in network have always been the network's fault sure and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another hundred and these times are changing they see your squadron leader I get that right what is what is a squadron leader first can you describe what it is I think it probably just leading all the network components of it but are they from my perspective when to think about what you asked them was it's about no issues and no escalation soft my day is like that's a good outcome that's a good day it's a good day Jennifer you mentioned the Amazon thing this brings up a good point you know when you have these new waves come in you have a lot of new things newly use cases a lot of the finger-pointing it's that guys problem that girls problem so what is how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in those where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Stephen the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear but what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are full logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about you know that's dimmer fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young P so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way or you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and that's old guys that's where we thrive Jennifer you mentioned you you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static cuz back then you just said the network you got a perimeter yeah no there was no such thing ya know so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it now I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this within the program abilities it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global si you help the business issues what does it mean to do that is it code is that networking is it configuration is that aviatrix what is the amine oxy aviatrix is a certification but what is it about the multi cloud that makes it multi networking and multi vendor and easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that's hops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not going to solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six months ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed a good is that watching leader would put there yeah something that you see in your organizations are you recommending that to people do you see I mean I'm just I would guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I say from my side because we operate in the multi cloud environment so it really helps an official for us I think I would add that networking guys have always needed to use certifications to prove that they know what they know it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters buying helps give you validity so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics enough of the understandings that you have the tools necessary right so okay I guess my final question for you guys is why an eighth certification is relevant and then second part is share what the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why shouldn't someone want to be an ace-certified I'm used to right engineer I think my views a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get no I mean they're backwards so when you've got the training and the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding it okay so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network definition getting eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that's just the next progression I don't say I expend that to more automation engineers because we have those nails probably well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but I've never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who've tradition down on prime networking they can understand how that's going to work in the cloud too well I know we got just under 30 seconds left but I want to get one more question than just one more for the folks watching that are you may be younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacey we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions no we're going use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you've come from top-down now you're gonna start looking from bottom up and you want those different systems to cross communicate and say you've built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the how the pipes are working you guys know what's going some plumbing that's right and they gotta know how it works I had a code it it's right awesome thank you guys for great insights ace certain ABS your certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not gonna take long we got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the Cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community aviatrix comm starting a community a multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as to start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more importantly where they're going and define that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we solve we help you define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their twenty-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] you

[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] you you you you [Music] [Music] [Music] [Music] ladies and gentlemen please take your seats good morning ladies and gentlemen this is your captain speaking we will soon be taking off on our way to altitude please keep your seatbelts fastened and remain in your seats we will be experiencing turbulence until we are above the clouds ladies and gentlemen we are now cruising at altitude sit back and enjoy the ride [Music] altitude is a community of thought leaders and pioneers cloud architects and enlightened network engineers who have individually and are now collectively leading their own IT teams and the industry on a path to lift cloud networking above the clouds empowering Enterprise IT to architect design and control their own cloud network regardless of the turbulent clouds beneath them it's time to gain altitude ladies and gentlemen Steve Mulaney president and CEO of aviatrix the leader of multi cloud networking [Music] [Applause] all right good morning everybody here in Santa Clara as well as to the what millions of people watching the livestream worldwide welcome to altitude 2020 alright so we've got a fantastic event today I'm really excited about the speakers that we have today and the experts that we have and really excited to get started so one of the things I wanted to just share was this is not a one-time event it's not a one-time thing that we're gonna do sorry for the aviation analogy but you know sherry way aviatrix means female pilot so everything we do as an aviation theme this is a take-off for a movement this isn't an event this is a takeoff of a movement a multi-cloud networking movement and community that we're inviting all of you to become part of and-and-and why we're doing that is we want to enable enterprises to rise above the clouds so to speak and build their network architecture regardless of which public cloud they're using whether it's one or more of these public clouds so the good news for today there's lots of good news but this is one good news is we don't have any PowerPoint presentations no marketing speak we know that marketing people have their own language we're not using any of that in those sales pitches right so instead what are we doing we're going to have expert panels we've got some owners chart of Gartner here we've got 10 different network architects cloud architects real practitioners they're going to share their best practices and there are real-world experiences on their journey to the multi cloud so before we start and everybody know what today is in the US it's Super Tuesday I'm not gonna get political but Super Tuesday there was a bigger Super Tuesday that happened 18 months ago and maybe eight six employees know what I'm talking about 18 months ago on a Tuesday every Enterprise said I'm gonna go to the cloud and so what that was was the Cambrian explosion for cloud for the price so Franco Bree you know what a Cambrian explosion is he had to look it up on Google 500 million years ago what happened there was an explosion of life where it went from very simple single-cell organisms to very complex multi-celled organisms guess what happened 18 months ago on a Tuesday I don't really know why but every enterprise like I said all woke up that day and said now I'm really gonna go to cloud and that Cambrian explosion of cloud went meant that I'm moving from very simple single cloud single use case simple environment to a very complex multi cloud complex use case environment and what we're here today is we're gonna go and dress that and how do you handle those those those complexities and when you look at what's happening with customers right now this is a business transformation right people like to talk about transitions this is a transformation and it's actually not just the technology transformation it's a business transformation it started from the CEO and the boards of enterprise customers where they said I have an existential threat to the survival of my company if you look at every industry who they're worried about is not the other 30 year old enterprise what they're worried about is the three year old enterprise that's leveraging cloud that's leveraging AI and that's where they fear that they're going to actually get wiped out right and so because of this existential threat this is CEO lead this is board led this is not technology led it is mandated in the organization's we are going to digitally transform our enterprise because of this existential threat and the movement to cloud is going to enable us to go do that and so IT is now put back in charge if you think back just a few years ago in cloud it was led by DevOps it was led by the applications and it was like I said before their Cambrian explosion is very simple now with this Cambrian explosion and enterprises getting very serious and mission-critical they care about visibility they care about control that about compliance conformance everything governance IT is in charge and and and that's why we're here today to discuss that so what we're going to do today is much of things but we're gonna validate this journey with customers did they see the same thing we're going to validate the requirements for multi-cloud because honestly I've never met an enterprise that is not going to be multi-cloud many are one cloud today but they all say I need to architect my network for multiple clouds because that's just what the network is there to support the applications and the applications will run and whatever cloud it runs best in and you have to be prepared for that the second thing is is is architecture again with the IT in charge you architecture matters whether it's your career whether it's how you build your house it doesn't matter horrible architecture your life is horrible forever good architecture your life is pretty good so we're going to talk about architecture and how the most fundamental and critical part of that architecture and that basic infrastructure is the network if you don't get that right nothing works right way more important and compute way more important than storm dense storage network is the foundational element of your infrastructure then we're going to talk about day two operations what does that mean well day 1 is one day of your life who you wire things up they do and beyond I tell everyone in networking and IT it's every day of your life and if you don't get that right your life is bad forever and so things like operations visibility security things like that how do I get my operations team to be able to handle this in an automated way because it's not just about configuring it in the cloud it's actually about how do i operationalize it and that's a huge benefit that we bring as aviatrix and then the last thing we're going to talk and it's the last panel we have I always say you can't forget about the humans right so all this technology all these things that we're doing it's always enabled by the humans at the end of the day if the humans fight it it won't get deployed and we have a massive skills gap in cloud and we also have a massive skill shortage you have everyone in the world trying to hire cloud network architects right there's just not enough of them going around so at aviatrix we as leaders ooh we're gonna help address that issue and try to create more people we created a program and we call the ACE program again an aviation theme it stands for aviatrix certified engineer very similar to what Cisco did with CCI es what Cisco taught you about IP networking a little bit of Cisco we're doing the same thing we're gonna teach network architects about multi-cloud networking and architecture and yeah you'll get a little bit of aviatrix training in there but this is the missing element for people's careers and also within their organization so we're gonna we're gonna go talk about that so great great event great show when to try to keep it moving I'd next want to introduce my my host he's the best in the business you guys have probably seen him multiple million times he's the co CEO and co-founder of joob John Ferrier [Applause] okay awesome great great speech they're awesome I totally agree with everything you said about the explosion happening and I'm excited here at the heart of Silicon Valley to have this event it's a special digital event with the cube and aviatrix where we live streaming to millions of people as you said maybe not a million maybe not really take this program to the world this is a little special for me because multi-cloud is the hottest wave and cloud and cloud native networking is fast becoming the key engine of the innovation so we got an hour and a half of action-packed programming we have a customer panel to customer panels before that Gartner is going to come out and talk about the industry we have a global system integrators they talk about how they're advising and building these networks and cloud native networking and then finally the Aces the aviatrix certified engineer is gonna talk more about their certifications and the expertise needed so let's jump right in and let's ask some own rashard to come on stage from Gartner we'll kick it all up [Applause] [Music] okay so kicking things off certain started gardener the industry experts on cloud really kind of more to your background talk about your background before you got the gardener yeah before because gardener was a chief network architect of a fortune five companies with thousands of sites over the world and I've been doing everything and IT from a C programmer the ninety-two a security architect to a network engineer to finally becoming a network analyst so you rode the wave now you're covering in the marketplace with hybrid cloud and now moving quickly to multi cloud is really was talking about cloud natives been discussed but the networking piece is super important how do you see that evolving well the way we see Enterprise adapt in cloud first thing you do about networking the initial phases they either go in a very ad hoc way is usually led by non non IT like a shadow IT or application people are sometime a DevOps team and it's it just goes as it's completely unplanned decreed VP sees left and right as with different account and they create mesh to manage them and they have direct connect or Express route to any of them so that's what that's a first approach and on the other side again it within our first approach you see what I call the lift and shift way we see like Enterprise IT trying to basically replicate what they have in a data center in the cloud so they spend a lot of time planning doing Direct Connect putting Cisco routers and f5 and Citrix and any checkpoint Palo Alto divides that the atoms that are sent removing that to that cloud they ask you the aha moments gonna come up a lot of our panels is where people realize that it's a multi cloud world I mean they either inherit clouds certainly they're using public cloud and on-premises is now more relevant than ever when's that aha moment that you're seeing where people go well I got to get my act together and get on this well the first but even before multi-cloud so these two approach the first one like the ad hoc way doesn't scale at some point idea has to save them because they don't think about the - they don't think about operations we have a bunch of VPC and multiple clouds the other way that if you do the left and shift week they cannot take any advantages of the cloud they lose elasticity auto-scaling pay by the drink these feature of agility features so they both realize okay neither of these words are good so I have to optimize that so I have to have a mix of what I call the cloud native services within each cloud so they start adapting like other AWS constructor is your construct or Google construct and that's what I call the optimal phase but even that they realize after that they are very different all these approaches different the cloud are different identities is completely difficult to manage across clouds I mean for example AWS as accounts there's subscription and in as ER and GCP their projects it's a real mess so they realize well I can't really like concentrate used the cloud the cloud product and every cloud that doesn't work so I have I'm doing multi cloud I like to abstract all of that still wanna manage the cloud from an epi xx view I don't necessarily want to bring my incumbent data center products but I have to do that in a more API driven cloud they're not they're not scaling piece and you were mentioning that's because there's too many different clouds yes that's the piece there so what are they doing whether they read they building different development teams as its software what's the solution well this the solution is to start architecting the cloud that's the third phase I call that the multi cloud architect phase where they have to think about abstraction that works across cloud fact even across one cloud it might not scale as well if you start having like 10,000 security group in AWS that doesn't scale you have to manage that if you have multiple VPC it doesn't scale you need a third-party identity provider so it barely scales within one cloud if you go multiple cloud it gets worse and worse see way in here what's your thoughts I thought we said this wasn't gonna be a sales pitch for aviatrix you just said exactly what we do so anyway up just a joke what do you see in terms of where people are in that multi cloud like a lot of people you know everyone I talked to started in one cloud right but then they look and they say okay but I'm now gonna move to adjourn I'm gonna move do you see a similar thing well yes they are moving but they're not there's not a lot of application that use a tree cloud at once they move one app in Azure one app in individuals one get app in Google that's what we see so far okay yeah I mean one of the mistakes that people think is they think multi-cloud no one is ever gonna go multi-cloud for arbitrage they're not gonna go and say well today I might go into Azure because I got a better rate of my instance that's never do you agree with that's never gonna happen what I've seen with enterprise is I'm gonna put the work load and the app the app decides where it runs best that may be a sure maybe Google and for different reasons and they're gonna stick there and they're not gonna move let me ask you infrastructure has to be able to support from a networking King be able to do that do you agree with that yes I agree and one thing is also very important is connecting to that cloud is kind of the easiest thing so though while I run network part of the cloud connectivity to the cloud is kind of simple you know I agree IPSec VPN and I reckon Express route that's a simple part what's difficult and even a provisioning part is easy you can use terraform and create v pieces and v nets across which we cloud providers right what's difficult is the day-to-day operations so it's what to find a to operations what is that what does that actually mean it's just the day-to-day operations after you know the natural let's add an app that's not a server let's troubleshoot a problem so what ending so your life if something changes now what do you do so what's the big concerns I want to just get back to this cloud native networking because everyone kind of knows with cloud native apps are that's the hot trend what is cloud native networking how do you how do you guys define that because that seems to be the oddest part of the multi cloud wave that's coming as cloud native networking well there's no you know official gardener definition but I can create one on another spot is do it I just want to leverage the cloud construct and a cloud epi I don't want to have to install like like for example the first version was let's put a virtual router that doesn't understand and then the cloud environment right if I have if I have to install a virtual machine it has to be cloud aware it has to understand the security group if it's a router it has to be programmable to the cloud API and and understand the cloud environment you know one things I hear a lot from either see Saussure CIOs or CXOs in general is this idea of I'm definitely on going API so it's been an API economy so API is key on that point but then they say okay I need to essentially have the right relationship with my suppliers aka clouds you call it above the clouds so the question is what do i do from an architecture standpoint do I just hire more developers and have different teams because you mentioned that's a scale point how do you solve this this problem of okay I got AWS I got GCP or Azure or whatever do I just have different teams or just expose API guys where is that optimization where's the focus well I think what you need from an android point of view is a way a control plane across the three clouds and be able to use the api of that cloud to build networks but also to troubleshoot them and do they to operation so you need a view across a three cloud that takes care of routing connectivity that's you know that's the aviatrix plug of view right there so so how do you see so again your Gartner you you you you see the industry you've been a network architect how do you see this this plan out what are the what are the legacy incumbent client-server on-prem networking people gonna do well these versus people like aviatrix well how do you see that playing out well obviously all the incumbent like Arista cisco juniper NSX right they want to basically do the lift and chip are they want to bring and you know VM I want to bring in a section that cloud they call that NSX everywhere and cisco wants bring you star in the cloud they call that each guy anywhere right so everyone what and and then there's cloud vision for my red star and Khan trailers in a cloud so they just want to bring the management plain in the cloud but it's still based most of them it's still based on putting a VM them in controlling them right you you extend your management console to the cloud that's not really cloud native right cloud native you almost have to build it from scratch we like to call that cloud naive well not so close one letter yeah so that was a big culture to reinvent take the tea out of cloud native it's cloud naive that went super viral you guys got t-shirts now I know you love yeah but yeah but that really ultimately is kind of a double-edged sword you got to be you can be naive on the on the architecture side and rolling up but also suppliers are can be naive so how would you define who's naive and who's not well in fact they're evolving as well so for example in Cisco you it's a little bit more native than other ones because they're really scr in the cloud you can't you you really like configure API so the cloud and NSX is going that way and so is Arista but they're incumbent they have their own tools is difficult for them they're moving slowly so it's much easier to start from scratch Avenue like and you know a network happiness started a few years ago there's only really two aviatrix was the first one they've been there for at least three or four years and there's other ones like Al Kyra for example that just started now that doing more connectivity but they want to create an overlay network across the cloud and start doing policies and trying abstracting all the clouds within one platform so I gotta ask you I interviewed an executive at VMware Sanjay Pune and he said to me at RSA last week I was only be two networking vendors left Cisco and VMware what's your respect what's your response to that obviously I mean when you have these waves as new brands that emerge like aviation others though I think there'll be a lot of startups coming out of the woodwork how do you respond to that comment well there's still a data center there's still like a lot of action on campus and there's the one but from the cloud provisioning and clown networking in general I mean they're behind I think you know in fact you don't even need them to start to it you can if you're small enough you can just keep if you're in a table us you can use it with us construct they have to insert themselves I mean they're running behind they're all certainly incumbents I love the term Andy Jesse's that Amazon Web Services uses old guard new guard to talk about the industry what does the new guard have to do the new and new brands that emerge in is it be more DevOps oriented neck net sec Ops is that net ops is the programmability these are some of the key discussions we've been having what's your view on how you see this ability their most important part is they have to make the network's simple for the dev teams and from you cannot have that you cannot make a phone call and get it V line in two weeks anymore so if you move to that cloud you have to make the cloud construct as simple enough so that for example a dev team could say okay I'm going to create this V PC but this V PC automatically being your associate your account you cannot go out on the internet you have to go to the transit VPC so there's a lot of action in terms of the I am part and you have to put the control around them too so to make it as simple as possible you guys both I mean you're the COC aviatrix but also you guys a lot of experience going back to networking going back to I call the OSI days which for us old folks know what that means but you guys know this means I want to ask you the question as you look at the future of networking here a couple of objections oh the cloud guys they got networking we're all set with them how do you respond to the fact that networking is changing and the cloud guys have their own networking what some of the pain points that's going on premises and these enterprises so are they good with the clouds what needs what are the key things that's going on in networking that makes it more than just the cloud networking what's your take on well as I said earlier that once you you could easily provision in the cloud you can easily connect to the cloud is when you start troubleshooting application in the cloud and try to scale so this that's what the problem occurs see what you're taking on it and you'll hear from the from the customers that that we have on stage and I think what happens is all the cloud the clouds by definition designed to the 80/20 rule which means they'll design 80% of the basic functionality and they'll lead to 20% extra functionality that of course every Enterprise needs they'll leave that to ISVs like aviatrix because why because they have to make money they have a service and they can't have huge instances for functionality that not everybody needs so they have to design to the common and that's they all do it right they have to and then the extra the problem is that can be an explosion that I talked about with enterprises that's holy that's what they need that they're the ones who need that extra 20% so that's that's what I see is is there's always going to be that extra functionality that in an automated and simple way that you talked about but yet powerful with up with the visible in control that they expect of on prep that that's that kind of combination that yin and the yang that people like us are providing some I want to ask you were gonna ask some of the cloud architect customer panels it's the same question this pioneers doing some work here and there's also the laggers who come in behind the early adopters what's gonna be the tipping point what are some of those conversations that the cloud architects are having out there or what's the signs that they need to be on this multi cloud or cloud native networking trend what are some of the signals that are going on their environment what are some of the thresholds or things that are going on that there can pay attention to well one once they have application and multiple cloud and they have they get wake up at 2:00 in the morning to troubleshoot them they don't know it's important so I think that's the that's where the robbery will hit the road but as I said it's easier to prove it it's okay it's a TBS it's easy use a transit gateway put a few V PCs and you're done and you create some presents like equinox and do Direct Connect and Express route with Azure that looks simple as the operations that's when they'll realize okay now I need to understand our car networking works I also need a tool that give me visibility and control not but I'm telling you that I need to understand a basic underneath it as well what are some of the day in the life scenarios that you envision happening with multi cloud because you think about what's happening it kind of has that same vibe of interoperability choice multi vendor because you have multi clouds essentially multi vendor these are kind of old paradigms that we've lived through the client-server an internet working wave what are some of those scenarios of success and that might be possible it would be possible with multi cloud and cloud native networking well I think once you have good enough visibility to satisfy your customers you know you not only like to keep the service running an application running but to be able to provision fast enough I think that's what you want to achieve small final question advice for folks watching on the live stream if they're sitting there as a cloud architect or a CXO what's your advice to them right now in this because honestly public cloud check hybrid cloud they're working on that that kids on premise is done now multi class right behind it what's your advice the first thing they should do is really try to understand cloud networking for each of their cloud providers and then understand the limitation and is what there's cloud service provider offers enough or you need to look to a third party but you don't look at a third party to start with especially an incumbent one so it's tempting to say I have a bunch of f5 experts nothing against f5 I'm going to bring my five in a cloud when you can use a needle be that automatically understand is ease and auto scaling and so on and you understand that's much simpler but sometimes you need you have five because you have requirements you have like AI rules and that kind of stuff that you use for years you cannot do it's okay I have requirement and that met I'm going to use legacy stuff and then you have to start taking okay what about visibility control about the three cloud but before you do that you have to understand the limitation of the existing cloud providers so first try to be as native as possible until things don't work after that you can start taking multi-cloud great insight somewhat thank you for coming summit in charge with Gardner thanks for sharing thank you appreciate it thanks [Applause] informatica is known as the leading enterprise cloud data management company we are known for being the top in our industry in at least five different products over the last few years especially we've been transforming into a cloud model which allows us to work better with the trends of our customers in order to see agile and effective in a business you need to make sure that your products and your offerings are just as relevant in all these different clouds than what you're used to and what you're comfortable with one of the most difficult challenges we've always had is that because we're a data company we're talking about data that a customer owns some of that data may be in the cloud some of that data may be on Prem some of that data may be actually in their data center in another region or even another country and having that data connect back to our systems that are located in the cloud has always been a challenge when we first started our engagement myth aviatrix we only had one plan that was Amazon it wasn't till later that a jerk came up and all of a sudden we found hey the solution we already had in place for her aviatrix already working in Amazon and now works in Missouri as well before we knew what GCP came up but it really wasn't a big deal for us because we already had the same solution in Amazon and integer now just working in GCP by having a multi cloud approach we have access to all three of them but more commonly it's not just one it's actually integrations between multiple we have some data and ensure that we want to integrate with Amazon we have some data in GCP that we want to bring over to a data Lake measure one of the nice things about aviatrix is that it gives a very simple interface that my staff can understand and use and manage literally hundreds of VPNs around the world and while talking to and working with our customers who are literally around the world now that we've been using aviatrix for a couple years we're actually finding that even problems that we didn't realize we had were actually solved even before we came across the problem and it just worked cloud companies as a whole are based on reputation we need to be able to protect our reputation and part of that reputation is being able to protect our customers and being able to protect more importantly our customers data aviatrix has been helpful for us in that we only have one system that can manage this whole huge system in a simple easy direct model aviatrix is directly responsible for helping us secure and manage our customers not only across the world but across multiple clouds users don't have to be VPN or networking experts in order to be able to use the system all the members on my team can manage it all the members regardless of their experience can do different levels of it one of the unexpected two advantages of aviatrix is that I don't have to sell it to my management the fact that we're not in the news at three o'clock in the morning or that we don't have to get calls in the middle of the night no news is good news especially in networking things that used to take weeks to build or done in hours I think the most important thing about a matrix is it provides me consistency aviatrix gives me a consistent model that I can use across multiple regions multiple clouds multiple customers okay welcome back to altitude 2020 for the folks on the livestream I'm John for Steve Mulaney with CEO of aviatrix for our first of two customer panels on cloud with cloud network architects we got Bobby Willoughby they gone Luis Castillo of National Instruments David should Nick with fact set guys welcome to the stage for this digital event come on up [Applause] [Music] hey good to see you thank you okay okay customer pal this is my favorite part we get to hear the real scoop against a gardener given this the industry overview certainly multi clouds very relevant and cloud native networking is the hot trend with a live stream out there and the digital event so guys let's get into it the journey is you guys are pioneering this journey of multi cloud and cloud native networking and the soon gonna be a lot more coming so I want to get into the journey what's it been like is it real you got a lot of scar tissue and what are some of the learnings yeah absolutely so multi cloud is whether or not we we accepted as a network engineers is a reality like Steve said about two years ago companies really decided to to just to just bite the bullet and and and move there whether or not whether or not we we accept that fact we need to now create a consistent architecture across across multiple clouds and that that is challenging without orchestration layers as you start managing different different tool sets and different languages across different clouds so that's it's really important that to start thinking about that guys on the other panelists here there's different phases of this journey some come at it from a networking perspective some come in from a problem troubleshooting what's what's your experiences yeah so from a networking perspective it's been incredibly exciting it's kind of a once-in-a-generation --all opportunity to look at how you're building out your network you can start to embrace things like infrastructure as code that maybe your peers on the systems teams have been doing for years but it just never really worked on bram so it's really it's really exciting to look at all the opportunities that we have and then all the interesting challenges that come up that you that you get to tackle an effect said you guys are mostly AWS right yep right now though we're we are looking at multiple clouds we have production workloads running in multiple clouds today but a lot of the initial work has been with Amazon and you've seen it from a networking perspective that's where you guys are coming at it from yep yeah we evolved more from a customer requirement perspective started out primarily as AWS but as the customer needed more resources to measure like HPC you know as your ad things like that even recently Google at Google Analytics our journey has evolved into more of a multi cloud environment Steve weigh in on the architecture because this has been the big conversation I want you to lead this second yeah so I mean I think you guys agree the journey you know it seems like the journey started a couple years ago got real serious the need for multi cloud whether you're there today of course it's gonna be there in the future so that's really important I think the next thing is just architecture I'd love to hear what you had some comments about architecture matters it all starts I mean every Enterprise I talk to maybe talk about architecture and the importance of architecture maybe Bobby it's a particular perspective we sorted a journey five years ago Wow okay and we're just now starting our fourth evolution of our network architect and we'll call it networking security net sec yep versus Justice Network and that fourth generation architectures be based primarily upon Palo Alto Networks an aviatrix I have a trick to in the orchestration piece of it but that journey came because of the need for simplicity ok the need for a multi cloud orchestration without us having to go and do reprogramming efforts across every cloud as it comes along right I guess the other question I also had around architectures also Louis maybe just talk about I know we've talked a little bit about you know scripting right and some of your thoughts on that yeah absolutely so so for us we started we started creating the network constructs with cloud formation and we've we've stuck with that for for the most part what's interesting about that is today on premise we have a lot of a lot of automation around around around how we provision networks but cloud formation has become a little bit like the new manual for us so we're now having issues with having the to automate that component and making it consistent with our on premise architecture making it consistent with Azure architecture and Google cloud so it's really interesting to see to see companies now bring that layer of abstraction that sty and brought to the do the web side now it's going up into into the into the cloud networking architecture so on the fourth generation of you mentioned you're in the fourth gen architecture what do you guys what have you learned is there any lessons scar tissue what to avoid what worked what was the middle it was a path that's probably the biggest lesson there is that when you think you finally figured it out you have it right Amazon will change something as you change something you know transit gateways a game changer so in listening to the business requirements is probably the biggest thing we need to do up front but I think from a simplicity perspective we like I said we don't want to do things four times we want to do things one time we won't be able to write to an API which aviatrix has and have them do the orchestration for us so that we don't have to do it four times how important is architecture in the progression is it you guys get thrown in the deep end to solve these problems or you guys zooming out and looking at it it's a I mean how are you guys looking at the architecture I mean you can't get off the ground if you don't have the network there so all of those now we've gone through similar evolutions we're on our fourth or fifth evolution I think about what we started off with Amazon without a direct connect gateway about a trans a gateway without a lot of the things that are available today kind of the 80/20 that Steve was talking about just because it wasn't there doesn't mean we didn't need it so we needed to figure out a way to do it we couldn't say oh you need to come back to the network team in a year and maybe Amazon will have a solution for it right you need to do it now and it evolved later and maybe optimized for change the way you're doing things in the future but don't sit around and wait you can't I'd love to have you guys each individually answer this question for the live stream because it comes up a lot a lot of cloud architects out in the community what should they be thinking about the folks that are coming into this proactively and/or realizing the business benefits are there what advice would you guys give them an architecture what should be they be thinking about and what are some guiding principles you could share so I would start with looking at an architecture model that that can that can spread and and give consistency they're different to different cloud vendors that you will absolutely have to support cloud vendors tend to want to pull you into using their native toolset and that's good if only it was realistic to talk about only one cloud but because it doesn't it's it's it's super important to talk about and have a conversation with the business and with your technology teams about a consistent model so that's David yeah talking as we prepare about a day to operations so how do I design how do I do my day one work so that I'm not you know spending eighty percent of my time troubleshooting or managing my network because I'm doing that then I'm missing out on ways that I can make improvements or embrace new technologies so it's really important early on to figure out how do I make this as low maintenance as possible so that I can focus on the things that the team really should be focusing on Bobby your advice to the architect I don't know what else I can do that simplicity of operations is key right all right so the holistic view of j2 operation you mentioned let's could jump in day one is you're you're you're getting stuff set up day two is your life after all right this is kind of what you're getting at David so what does that look like what are you envisioning as you look at that 20 miles their outpost multi-cloud world what are some of the things then you want in a day to operations yeah infrastructure is code is really important to us so how do we how do we design it so that we can fit start making network changes and fitting them into like a release pipeline and start looking at it like that rather than somebody logging into a router seoi and troubleshooting things on in an ad hoc nature so moving more towards a DevOps model there's anything on that day - yeah I would love to add something so in terms of date to operations you can you can either sort of ignore the day - operations for a little while where you get well well you get your feet wet or you can start approaching it from the beginning the fact is that the the cloud native tools don't have a lot of maturity in that space and when you run into an issue you're gonna end up having a bad day going through millions and millions of logs just to try to understand what's going on so that's something that that the industry just now is beginning to to realize it's it's such as such a big gap I think that's key because for us we're moving to more of an event-driven operations in the past monitoring got the job done it's impossible to modern monitor something that it's nothing there when the event happens all right so the event-driven application and then detection is important yeah I think Gardner was all about the cloud native wave coming into networking that's gonna be a serious thing I want to get you guys perspectives I know you have different views of how you come into the journey and how you're executing and I always say the beauties in the eye of the beholder and that kind of applies how the network's laid out so Bobby you guys do a lot of high-performance encryption both on AWS and Azure that's kind of a unique thing for you how are you seeing that impact with multi cloud yeah and that's a new requirement for us to where we we have an equipment to encrypt and they they never get the question should i encryption and I'll encrypt the answer is always yes you should encrypt when you can encrypt for our perspective we we need to migrate a bunch of data from our data centers we have some huge data centers and then getting that data to the cloud is the timely experiencing some cases so we have been mandated that we have to encrypt everything leaving the data center so we're looking at using the aviatrix insane mode appliances to be able to encrypt you know 10 20 gigabits of data as it moves to the cloud itself David you're using terraform you got fire Ned you got a lot of complexity in your network what do you guys look at the future for your environment yeah so something exciting that or yeah now is fire net so for our security team they obviously have a lot of a lot of knowledge base around Palo Alto and with our commitments to our clients you know it's it's it's not very easy to shift your security model to a specific cloud vendor right so there's a lot of stuck to compliance or things like that where being able to take some of what you've you know you've worked on for years on Bram and put it in the cloud and have the same type of assurance that things are gonna work and be secure in the same way that they are on prem helps make that journey into the cloud a lot easier and Louis you guys got scripting you got a lot of things going on what's your what's your unique angle on this yeah no absolutely so full disclosure I'm not a not not an aviatrix customer yet it's ok wanna hear the truth that's good Ellis what are you thinking about what's on your mind no really when you when you talk about implementing the tool like this it's really just really important to talk about automation and focus on on value so when you talk about things like encryption and things like so yeah encrypting tunnels and encrypting the paths and those things are it should it should should be second nature really when you when you look at building those backends and managing them with your team it becomes really painful so tools like aviatrix that that add a lot of automation it's out of out of sight out of mind you can focus on the value and you don't have to focus on so I gotta ask you guys I'll see aviatrix is here they're their supplier to the sector but you guys are customers everyone's pitching you stuff these people are not gonna here to buy my stuff how do you guys have that conversation with the suppliers like the cloud vendors and other folks what's the what's it like we're API all the way you got to support this what are some of the what are some of your requirements how do you talk to and evaluate people that walk in and want to knock on your door and pitch you something what's the conversation like it's definitely it's definitely API driven we we definitely look at the at the PAP i structure of the vendors provide before we select anything that that is always first of mine and also what a problem are we really trying to solve usually people try to sell or try to give us something that isn't really valuable like implementing a solution on the on the on the cloud isn't really it doesn't really add a lot of value that's where we go David what's your conversation like with suppliers you have a certain new way to do things as as becomes more agile and essentially the networking and more dynamic what are some of the conversation is with the either incumbents or new new vendors that you're having what do what do you require yeah so ease of use is definitely definitely high up there we've had some vendors come in and say you know hey you know when you go to set this up we're gonna want to send somebody on-site and they're gonna sit with you for a day to configure it and that's kind of a red flag what wait a minute you know do we really if one of my really talented engineers can't figure it out on his own what's going on there and why is that so you know having having some ease-of-use and the team being comfortable with it and understanding it is really important probably how about you I mean the old days was do a bake-off and you know the winner takes all I mean is it like that anymore what's involving take off last year first you win so but that's different now because now you and you when you get the product you can install the product in AWS energy or have it up and running a matter of minutes and so key is is that it can you be operational you know within hours or days instead of weeks right but do we also have the flexibility to customize it to meet your needs could you want to be you want to be put into a box with the other customers we have needs that surpassed or cut their needs yeah I almost see the challenge of you guys are living where you've got the cloud immediate value depending on roll-up any solutions but then you have might have other needs so you've got to be careful not to buy into stuff that's not shipping so you're trying to be proactive at the same time deal with what you got I mean how do you guys see that evolving because multi-cloud to me is definitely relevant but it's not yet clear how to implement across how do you guys look at this baked versus you know future solutions coming how do you balance that so again so right now we we're we're taking the the ad hoc approach and and experimenting with the different concepts of cloud and really leveraging the the native constructs of each cloud but but there's it there's a breaking point for sure you don't you don't get to scale this I like like Seamon said and you have to focus on being able to deliver a developer they're their sandbox or their play area for the for the things that they're trying to build quickly and the only way to do that is with the with with some sort of consistent orchestration layer that allows you to so you've spent a lot more stuff to be coming pretty quickly IDEs area I do expect things to start to start maturing quite quite quickly this year and you guys see similar trend new stuff coming fast yeah you know part of the biggest challenge we've got now is being able to segment within the network being able to provide segmentation between production on production workloads even businesses because we support many businesses worldwide and and isolation between those is a key criteria there so the ability to identify and quickly isolate those workloads is key so the CIOs that are watching or that are saying hey take that he'll do multi cloud and then you know the bottoms up organization take pause you're kind of like off it's not how it works I mean what is the reality in terms of implementing you know in as fast as possible because the business benefits are clear but it's not always clear in the technology how to move that fast yeah what are some of the barriers what are the blockers what are the enablers I think the reality is is that you may not think your multi-cloud but your business is right so I think the biggest barriers there is understanding what the requirements are and how best to meet those requirements Inc and then secure manner because you need to make sure that things are working from a latency perspective that things work the way they did and get out of the mind shift that you know it was a cheery application in the data center it doesn't have to be a Tier three application in the cloud so lift and shift is is not the way to go scale is a big part of what I see is the competitive advantage to lot of these clouds and they used to be proprietary network stacks in the old days and then open systems came that was a good thing but as clouds become bigger there's kind of an inherent lock in there with the scale how do you guys keep the choice open how're you guys thinking about interoperability what are some of the conversations and you guys are having around those key concepts well when we look at when we look at the problem from a networking perspective it it's really key for you to just enable enable all the all the clouds to be to be able to communicate between them developers will will find a way to use the cloud that best suits their their business need and and like like you said it's whether whether you're in denial or not of the multi cloud fact that then your company is in already that's it becomes really important for you to move quickly yeah and a lot of it also hinges on how well is the provider embracing what that specific cloud is doing so are they are they swimming with Amazon or Azure and just helping facilitate things they're doing the you know the heavy lifting API work for you or are they swimming upstream and they're trying to hack it all together in a messy way and so that helps you you know stay out of the lock-in because they're you know if they're doing if they're using Amazon native tools to help you get where you need to be it's not like Amazon's gonna release something in the future that completely you know you have designed yourself into a corner so the closer they're more than cloud native they are the more the easier it is to to deploy but you also need to be aligned in such a way that you can take advantage of those cloud native technologies will they make sense tgw is a game changer in terms of cost and performance right so to completely ignore that would be wrong but you know if you needed to have encryption you know teach Adobe's not encrypted so you need to have some type of a gateway to do the VPN encryption you know so the aviatrix tool gives you the beauty of both worlds you can use tgw or the Gateway Wow real quick in the last minute we have I want to just get a quick feedback from you guys I hear a lot of people say to me hey the I picked the best cloud for the workload you got and then figure out multi cloud behind the scenes so that seems to be do you guys agree with that I mean is it do I go mole to one cloud across the whole company or this workload works great on AWS that work was great on this from a cloud standpoint you agree with that premise and then witness multi-cloud stitch them all together yeah from from an application perspective it it can be per workload but it can also be an economical decision certain enterprise contracts will will pull you in one direction to add value but the the network problem is still the same go away yeah yeah I mean you don't want to be trying to fit a square into a round Hall right so if it works better on that cloud provider then it's our job to make sure that that service is there and people can use it agree you just need to stay ahead of the game make sure that the then they're working for structure is there secure is available and is multi cloud capable yeah I'm at the end the day you guys just validating that it's the networking game now cloud storage compute check networking is where the action is awesome thanks for your insights guys appreciate you coming on the panel appreciate Thanks thank you [Applause] [Music] [Applause] okay welcome back on the live feed I'm John for its Dee Mulaney my co-host with aviatrix I'm with the cube for the special digital event our next customer panel got great another set of cloud network architects Justin Smith was aura Justin broadly with Ellie Mae and Amit Oh tree job with Koopa Pokemon stage [Applause] all right thank you thank you oK you've got all the cliff notes from the last session welcome rinse and repeat yeah yeah we're going to go under the hood a little bit I think I think they nailed the what we've been reporting and we've been having this conversation around networking is where the action is because that's the end of the day you got a move attack from A to B and you get work gloves exchanging data so it's really killer so let's get started Amit what are you seeing as the journey of multi cloud as you go under the hood and say okay I got to implement this I have to engineer the network make it enabling make it programmable make it interoperable across clouds I mean that's like I mean almost sounds impossible to me what's your taking yeah I mean it it seems impossible but if you are running an organization which is running infrastructure as a cordon all right it is easily doable like you can use tools out there that's available today you can use third-party products that can do a better job but but put your architecture first don't wait architecture may not be perfect put the best architecture that's available today and be agile to iterate and make improvements over the time we got to Justin's over here so I have to be careful when I point a question adjusting they both have to answer but okay journeys what's the journey been like I mean is there phases we heard that from Gardner people come into multi cloud and cloud native networking from different perspectives what's your take on the journey Justin yeah I mean from Mars like to we started out very much focused on one cloud and as we started doing Atkins we started doing new products the market the need for multi cloud comes very apparent very quickly for us and so you know having an architecture that we can plug in play into and be able to add and change things as it changes is super important for what we're doing in the space just in your journey yes for us we were very ad hoc oriented and the idea is that we were reinventing all the time trying to move into these new things and coming up with great new ideas and so rather than it being some iterative approach with our deployments that became a number of different deployments and so we shifted that tour and the network has been a real enabler of this is that it there's one network and it touches whatever cloud we want it to touch and it touches the data centers that we need it to touch and it touches the customers that we need it to touch our job is to make sure that the services that are available and one of those locations are available in all of the locations so the idea is not that we need to come up with this new solution every time it's that we're just iterating on what we've already decided to do before we get the architecture section I want to ask you guys a question I'm a big fan of you know let the app developers have infrastructure as code so check but having the right cloud run that workload I'm a big fan of that if it works great but we just heard from the other panel you can't change the network so I want to get your thoughts what is cloud native networking and is that the engine really got the enabler for this multi cloud trend but you guys taken we'll start with a mint what do you think about that yeah so you are gonna have workloads running in different clouds and the workloads would have affinity to one cloud over other but how you expose that it's matter of how you are going to build your networks how we are going to run security how we are going to do egress ingress out of it so it means the big problem how do you split says what's the solution what's the end the key pain points and problem statement I mean the key pain point for most companies is how do you take your traditional on-premise network and then blow that out to the cloud in a way that makes sense you know IP conflicts you have IP space you pub public eye peas and premise as well as in the cloud and how do you kind of make a sense of all of that and I think that's where tools like aviatrix make a lot of sense in that space from our site it's it's really simple it's a latency and bandwidth and availability these don't change whether we're talking about cloud or data center or even corporate IT networking so our job when when these all of these things are simplified into like s3 for instance and our developers want to use those we have to be able to deliver that and for a particular group or another group that wants to use just just GCP resources these aren't we have to support these requirements and these wants as opposed to saying hey that's not a good idea our job is to enable them not to disable them do you think I do you guys think infrastructure has code which I love that I think that's the future it is we saw that with DevOps but I just start getting the networking is it getting down to the network portion where it's network is code because stores and compute working really well is seeing all kubernetes and service master and network is code reality is that there is got work to do it's absolutely there I mean you mentioned net DevOps and it's it's very real I mean in Cooper we build our networks through terraform and on not only just out of fun build an API so that we can consistently build V nets and VPC all across in the same way three guys do it yeah and even security groups and then on top an aviatrix comes in we can peer the networks bridge bridge all the different regions through code same with you guys but yeah think about this everything we deploy is done with automation and then we also run things like lambda on top to make changes in real time we don't make manual changes on our network in the data center funny enough it's still manual but the cloud has enabled us to move into this automation mindset and and all my guys that's what they focus on is is bringing what now what they're doing in the cloud into the data center which is kind of opposite of what it should be that's full or what it used to be it's full DevOps then yes yeah I mean for us was similar on premise still somewhat very manual although we're moving more Norton ninja and terraform concepts but everything in the production environment is colored confirmation terraform code and now coming into the datacenter same I just wanted to jump in on a Justin Smith one of the comment that you made cuz it's something that we always talk about a lot is that the center of gravity of architecture used to be an on-prem and now it's shifted in the cloud and once you have your strategic architecture what you--what do you do you push that everywhere so what you used to see at the beginning of cloud was pushing the architecture on prem into cloud now i want to pick up on what you said to you others agree that the center of architect of gravity is here i'm now pushing what i do in the cloud back into on-prem and what and then so first that and then also in the journey where are you at from 0 to 100 of actually in the journey to cloud do you 50% there are you 10% are you vacuum datacenters next year I mean were you guys at yeah so there's there's two types of gravity that you typically are dealing with with no migration first is data gravity and your data set and where that data lives and then the second is the network platform that interrupts all that together in our case the data gravity sold mostly on Prem but our network is now extend out to the app tier that's gonna be in cloud right eventually that data gravity will also move to cloud as we start getting more sophisticated but you know in our journey we're about halfway there about halfway through the process we're taking a handle of lift and shift and when did that start and we started about three years ago okay okay cool bye it's a very different story it started from a garage and 100% on the clock it's a business spend management platform as a software as a service 100% on the cloud it was like 10 years ago right yes yeah you guys are riding the wave love that architecture Justin I want to ask you is or you guys mentioned DevOps I mean honestly we saw the huge observability wave which is essentially network management for the cloud in my opinion right yeah it's more dynamic but this is about visibility we heard from the last panel you don't know what's being turned on or turned off from a services standpoint at any given time how is all this playing out when you start getting into the DevOps down well this this is the big challenge for all of us as visibility when you talk transport within a cloud you know we very interesting we have moved from having a backbone that we bought that we owned that would be data center connectivity we now I work for as or as a subscription billing company so we want to support the subscription mindset so rather than going and buying circuits and having to wait three months to install and then coming up with some way to get things connected and resiliency and redundancy I my backbone is in the cloud I use the cloud providers interconnections between regions to transport data across and and so if you do that with their native solutions you you do lose visibility there there are areas in that that you don't get which is why controlling you know controllers and having some type of management plane is a requirement for us to do what we're supposed to do and provide consistency while doing it a great conversation I loved when you said earlier latency bandwidth I think availability with your sim pop3 things guys SLA I mean you just do ping times between clouds it's like you don't know what you're getting for round-trip times this becomes a huge kind of risk management black hole whatever you want to call blind spot how are you guys looking at the interconnects between clouds because you know I can see that working from you know ground to cloud I'm per cloud but when you start doing with multi clouds workloads SLA is will be all of the map won't they just inherently but how do you guys view that yeah I think we talked about workload and we know that the workloads are going to be different in different clouds but they are going to be calling each other so it's very important to have that visibility that you can see how data is flowing at what latency and what our ability is hour is there and our authority needs to operate on that so it's solely use the software dashboard look at the times and look at the latency in the old day is strong so on open so on you try to figure it out and then your day is you have to figure out just what's your answer to that because you're in the middle of it yeah I mean I think the key thing there is that we have to plan for that failure we have to plan for that latency in our applications that's starting start tracking your SLI something you start planning for and you loosely couple these services and a much more micro services approach so you actually can handle that kind of failure or that type of unknown latency and unfortunately the cloud has made us much better at handling exceptions a much better way you guys are all great examples of cloud native from day one and you guys had when did you have the tipping point moment or the Epiphany of saying a multi clouds real I can't ignore it I got to factor it into all my design design principles and and everything you're doing what's it was there a moment over that was it from day one now there are two divisions one was the business so in business there was some affinity to not be in one cloud or to be in one cloud and that drove from the business side so as a cloud architect our responsibility was to support that business and other is the technology some things are really running better in like if you are running dot network load or you are going to run machine learning or AI so that you have you would have that reference of one cloud over other so it was the bill that we got from AWS I mean that's that's what drives a lot of these conversations is the financial viability of what you're building on top of it which is so we this failure domain idea which is which is fairly interesting how do I solve our guarantee against a failure domain you have methodologies with you know back-end direct connects or interconnect with GCP all of these ideas are something that you have to take into account but that transport layer should not matter to whoever we're building this for our job is to deliver the frames in the packets what that flows across how you get there we want to make that seamless and so whether it's a public Internet API call or it's a back-end connectivity through Direct Connect it doesn't matter it just has to meet a contract that you signed with your application folks yeah that's the availability piece just on your thoughts on that I think any comment on that so actually multi clouds become something much more recent in the last six to eight months I'd say we always kind of had a very much an attitude of like moving to Amazon from our private cloud is hard enough why complicate it further but the realities of the business and as we start seeing you know improvements in Google and Asia and different technology spaces the need for multi cloud becomes much more important as well as our acquisition strategies I matured we're seeing that companies that used to be on premise that we typically acquire are now very much already on a cloud and if they're on a cloud I need to plug them into our ecosystem and so that's really change our multi cloud story in a big way I'd love to get your thoughts on the clouds versus the clouds because you know you compare them Amazon's got more features they're rich with features I see the bills are hiking people using them but Google's got a great network he googles networks pretty damn good and then you got Asher what's the difference between the clouds who where they evolve something where they peak in certain areas better than others what what are the characteristics which makes one cloud better do they have a unique feature that makes as you're better than Google and vice versa what do you guys think about the different clouds yeah to my experience I think there is the approach is different in many places Google has a different approach very DevOps friendly and you can run your workload like the your network can span regions time I mean but our application ready to accept that MS one is evolving I mean I remember 10 years back Amazon's Network was a flat network we will be launching servers and 10.0.0.0 so so the VP sees concept came out multi-account came out so they are evolving as you are at a late start but because they have a late start they saw the pattern and they they have some mature set up on the I mean I think they're all trying to say they're equal in their own ways I think they all have very specific design philosophies that allow them to be successful in different ways and you have to kind of keep that in mind as you architect your own solution for example Amazon has a very much a very regional affinity they don't like to go cross region in their architecture whereas Google is very much it's a global network we're gonna think about as a global solution I think Google also has a banjo it's third to market and so it has seen what a sure did wrong it's seen what AWS did wrong and it's made those improvements and I think that's one of their big advantage at great scale to Justin thoughts on the cloud so yeah Amazon built from the system up and Google built from the network down so their ideas and approaches are from a global versus or regional I agree with you completely that that is the big number one thing but the if you look at it from the outset interestingly the the inability or the ability for Amazon to limit layer two broadcasting and and what that really means from a VPC perspective changed all the routing protocols you can use all the things that we have built inside of a data center to provide resiliency and and and make things seamless to users all of that disappeared and so because we had to accept that at the VPC level now we have to accept it at the LAN level Google's done a better job of being able to overcome those things and provide those traditional network facilities to us just great panel can go all day here's awesome so I heard we could we'll get to the cloud native naive questions so kind of think about what's not even what's cloud is that next but I got to ask you had a conversation with a friend he's like Wayne is the new land so if you think about what the land was at a datacenter when is the new link you get talking about the cloud impact so that means st when the old st winds kind of changing into the new land how do you guys look at that because if you think about it what lands were for inside a premises was all about networking high speed but now when you take a win and make the essentially a land do you agree with that and how do you view this trend and is it good or bad or is it ugly and what's what you guys take on this yeah i think it's a it's a thing that you have to work with your application architect so if you are managing networks and if you're a sorry engineer you need to work with them to expose the unreliability that would bring in so the application has to hand a lot of this the difference in the latencies and and the reliability has to be worked through the application there land when same concept as that BS I think we've been talking about for a long time the erosion of the edge and so is this is just a continuation of that journey we've been on for the last several years as we get more and more cloud native and we start about API is the ability to lock my data in place and not be able to access it really goes away and so I think this is just continuation that thing I think it has challenges we start talking about weighing scale versus land scale the tooling doesn't work the same the scale of that tooling is much larger and the need to automation is much much higher in a way and than it was in a land that's what you're seeing so much infrastructure as code yeah yeah so for me I'll go back again to this its bandwidth and its latency right that that define those two land versus when but the other thing that comes up more and more with cloud deployments is where is our security boundary and where can I extend this secure aware appliance or set of rules to protect what's inside of it so for us we're able to deliver VRS or route forwarding tables for different segments wherever we're at in the world and so they're they're trusted to talk to each other but if they're gonna go to someplace that's outside of their their network then they have to cross a security boundary and where we enforce policy very heavily so for me there's it's not just land when it's it's how does environment get to environment more importantly that's a great point and security we haven't talked to yet but that's got to be baked in from the beginning that's architecture thoughts on security are you guys are dealing with it yeah start from the base have app to app security built-in have TLS have encryption on the data a transit data at rest but as you bring the application to the cloud and they are going to go multi-cloud talking to over the Internet in some places well have apt web security I mean I mean our principals day security is day zero every day and so we we always build it into our design we want our architecture into our applications its encrypt everything its TLS everywhere it's make sure that that data is secured at all times yeah one of the cool trends at RSA just as a side note was the data in use encryption piece which is a homomorphic stuff was interesting all right guys final question you know we heard on the earlier panel was also trending at reinvent we take the tea out of cloud native it spells cloud naive okay they got shirts now aviatrix kind of got this trend going what does that mean to be naive so if you're to your peers out there watching a live stream and also the suppliers that are trying to supply you guys with technology and services what's naive look like and what's native look like when is someone naive about implementing all this stuff so for me it's because we are in hundred-percent cloud for us it's main thing is ready for the change and you will you will find new building blocks coming in and the network design will evolve and change so don't be naive insane that it's static you wall with the change I think the big naivety that people have is that well I've been doing it this way for 20 years and been successful it's going to be successful in cloud the reality is that's not the case you have to think some of the stuff a little bit differently and you need to think about it early enough so that you can become cloud native and really enable your business on cloud yeah for me it's it's being open minded right the the our industry the network industry as a whole has been very much I am smarter than everybody else and we're gonna tell everybody how it's going to be done and we had we fell into a lull when it came to producing infrastructure and and and so embracing this idea that we can deploy a new solution or a new environment in minutes as opposed to hours or weeks or four months in some cases is really important and and so you know it's not me being closed-minded native being open minded exactly and and it took a for me it was that was a transformative kind of where I was looking to solve problems in a cloud way as opposed to looking to solve problems in this traditional old-school way all right I know we're out of time but I ask one more question so you guys so good it could be a quick answer what's the BS language when you the BS meter goes off when people talk to you about solutions what's the kind of jargon that you hear that's the BS meter going off what are people talking about that in your opinion you here you go that's total B yes but what triggers use it so that I have two lines out of movies that are really I can if I say them without actually thinking them it's like 1.21 jigowatts are you out of your mind from Back to the Future right somebody's giving you all these and then and then Martin Mull and and Michael Keaton and mr. mom when he goes to 22 21 whatever it takes yeah those two right there if those go off in my mind somebody's talking to me I know they're full of baloney so a lot of speech would be a lot of speeds and feeds a lot of data did it instead of talking about what you're actually doing and solutioning for you're talking about well I does this this this and any time I start seeing the cloud vendor start benchmarking against each other it's your workload is your workload you need a benchmark yourself don't don't listen to the marketing on that that's that's all what triggers you and the bsp I think if somebody explains you and not simple they cannot explain you in simplicity then that's good all right guys thanks for the great insight great pen how about a round of applause DX easy solutions integrating company that we service customers from all industry verticals and we're helping them to move to the digital world so as a solutions integrator we interface with many many customers that have many different types of needs and they're on their IT journey to modernize their applications into the cloud so we encounter many different scenarios many different reasons for those migrations all of them seeking to optimize their IT solutions to better enable their business we have our CPS organization it's cloud platform services we support AWS does your Google Alibaba porco will help move those workloads to wherever it's most appropriate no one buys the house for the plumbing equally no one buys the solution for the networking but if the plumbing doesn't work no one likes the house and if this network doesn't work no one likes a solution so network is ubiquitous it is a key component of every solution we do the network connectivity is the lifeblood of any architecture without network connectivity nothing works properly planning and building a scalable robust network that's gonna be able to adapt with the application needs its critical when encountering some network design and talking about speed the deployment aviatrix came up in discussion and we then further pursued an area DHT products that incorporated aviatrix is part of a new offering that we are in the process of developing that really enhances our ability to provide cloud connectivity for the lance cloud connectivity there's a new line of networking services that we're getting into as our clients moving the hybrid cloud networking it is much different than our traditional based services an aviatrix provides a key component in that service before we found aviatrix we were using just native peering connections but there wasn't a way to visualize all those peering connections and with multiple accounts multiple contacts for security with a v8 church we were able to visualize those different peering connections of security groups it helped a lot especially in areas of early deployment scenarios were quickly able to then take those deployment scenarios and turn them into scripts that we can then deploy repeatedly their solutions were designed for work with the cloud native capabilities first and where those cloud native capabilities fall short they then have solution sets that augment those capabilities I was pleasantly surprised number one with the aviatrix team as a whole in their level of engagement with us you know we weren't only buying the product we were buying a team that came on board to help us implement and solution that was really good to work together to learn both what aviatrix had to offer as well as enhancements that we had to bring that aviatrix was able to put into their product and meet our needs even better aviatrix was a joy to find because they really provided us the technology that we needed in order to provide multi cloud connectivity that really added to the functionality that you can't get from the basically providing services we're taking our customers on a journey to simplify and optimize their IT infrastructure baby Atrix certainly has made my job much easier okay welcome back to altitude 2020 for the digital event for the live feed welcome back I'm John fray with the cube with Steve Mulaney CEO aviatrix for the next panel from global system integrators the folks who are building and working with folks on their journey to multi cloud and cloud native networking we've got a great panel George Buckman with dxc and Derek Monahan with wwt welcome to the stage [Applause] [Music] okay you guys are the ones out there advising building and getting down and dirty with multi cloud and cloud native network and we start from the customer panel you can see the diversity of where people come into the journey of cloud it kind of depends upon where you are but the trends are all clear cloud native networking DevOps up and down the stack this has been the main engine what's your guys take of the disk Jerry to multi cloud what do you guys seeing yep yeah it's it's critical I mean we're seeing all of our enterprise customers enter into this they've been through the migrations of the easy stuff you know now they're trying to optimize and get more improvement so now the tough stuffs coming on right and you know they need their data processing near where their data is so that's driving them to a multi cloud environment okay we heard some of the edge stuff I mean you guys are you've seen this movie before but now it's a whole new ballgame what's your take yeah so I'll give you a hint so our practice it's not called the cloud practice it's the multi cloud practice and so if that gives you a hint of how we approach things it's very consultative and so when we look at what the trends are let's look a little year ago about a year ago we were having conversations with customers let's build a data center in the cloud let's put some VP C's let's throw some firewalls with some DNS and other infrastructure out there and let's hope it works this isn't a science project so what we're trying we're starting to see is customers are starting to have more of a vision and we're helping with that consultative nature but it's totally based on the business and you got to start understanding how the lines of business are using the apps and then we evolved into that next journey which is a foundational approach to what are some of the problem statements customers are solving when they come to you what are the top things that are on their my house or the ease of use of Julie all that stuff but what specifically they did digging into yeah some complexity I think when you look at a multi cloud approach in my view is network requirements are complex you know I think they are but I think the approach can be let's simplify that so one thing that we try to do this is how we talk to customers is let's just like you simplify an aviatrix simplifies the automation orchestration of cloud networking we're trying to simplify the design the planning implementation of infrastructure across multiple workloads across multiple platforms and so the way we do it is we sit down we look at not just use cases and not just the questions in common we anticipate we actually build out based on the business and function requirements we build out a strategy and then create a set of documents and guess what we actually build in the lab and that lab that we platform we built proves out this reference architecture actually works absolutely we implement similar concepts I mean we they're proven practices they work great so well George you mentioned that the hard parts now upon us are you referring to networking what is specifically were you getting at Tara says the easy parts done that so for the enterprises themselves migrating their more critical apps or more difficult apps into the environments you know they've just we've just scratched the surface I believe on what enterprises that are doing to move into the cloud to optimize their environments to take advantage of the scale and speed to deployment and to be able to better enable their businesses so they're just now really starting the >> so do you get you guys see what I talked about them in terms of their Cambrian explosion I mean you're both monster system integrators with you know top fortune enterprise customers you know really rely on you for for guidance and consulting and so forth and boy they're networks is that something that you you've seen I mean - does that resonate did you notice a year and a half ago and all of a sudden the importance of cloud for enterprise shoot up yeah I mean we're seeing it okay in our internal environment as you know we're a huge company or as customers are in 30 so we're experiencing that internal okay and every one of our other customers so I I have another question oh but I don't know the answer to this and the lawyer never asks a question that you don't know the answer to but I'm gonna ask it anyway DX c @ w WT massive system integrators why aviatrix yep so great question Steve so I think the way we approach things I think we have a similar vision a similar strategy how you approach things how we approach things that world by technology number one we want to simplify the complexity and so that's your number one priorities let's take the networking but simplify it and I think part of the other point I'm making is we have we see this automation piece as not just an afterthought anymore if you look at what customers care about visibility and automation is probably the at the top three maybe the third on the list and I think that's where we see the value and I think the partnership that we're building and what I what I get excited about is not just putting yours in our lab and showing customers how it works is Co developing a solution with you figuring out hey how can we make this better Bank visibily is a huge thing jump in security alone network everything's around visibility what automation you see happening in terms of progression order of operations if you will it's the low-hanging fruit what are people working on now and what are what are some of the aspirational goals around when you start thinking about multi cloud an automation yep so I wanted to get back to answer that question I want to answer your question you know what led us there and why aviatrix you know in working some large internal IT projects and and looking at how we were going to integrate those solutions you know we like to build everything with recipes where network is probably playing catch-up in the DevOps world but with a DevOps mindset looking to speed to deploy support all those things so when you start building your recipes you take a little of this a little of that and you mix it all together well when you look around you say wow look there's this big bag of athe let me plop that in that solves a big part of my problems that I have to speed to integrate speed to deploy and the operational views that I need to run this so that was 11 years about reference architectures yeah absolutely so you know they came with a full slate of reference architectures already the out there and ready to go that fit our needs so it's very very easy for us to integrate those into our recipes what do you guys think about all the multi vendor interoperability conversations that have been going on choice has been a big part of multi cloud in terms of you know customers want choice didn't you know they'll put a workload in the cloud that works but this notion of choice and interoperability is become a big conversation it is and I think our approach and that's why we talk to customers is let's let's speed and D risk of that decision making process and how do we do that because the interoperability is key you're not just putting it's not just a single vendor we're talking you know many many vendors I mean think about the average number of cloud application as a customer uses a business and enterprise business today you know it's it's above 30 it's it's skyrocketing and so what we do and we look at it from an Billee approach is how do things interoperate we test it out we validate it we build a reference architecture says these are the critical design elements now let's build one with aviatrix and show how this works with aviatrix and I think the the important part there though is the automation piece that we add to it invisibility so I think the visibility is what's what I see lack in cross industry today and the cloud needed that's been a big topic okay in terms of aviatrix as you guys see them coming in there one of the ones that are emerging and the new brands emerging with multi cloud you still got the old guard incumbent with huge footprints how our customers dealing with that that kind of component and dealing with both of them yeah I mean where we have customers that are ingrained with a particular vendor and you know we have partnerships with many vendors so our objective is to provide the solution that meets that client and you they all want multi vendor they all want interoperability correct all right so I got to ask you guys a question what we were defining day to operations what does that mean I mean you guys are looking at the big business and technical components of architecture what does day to Operations mean what's the definition of that yeah so I think from our perspective my experience we you know day to operations whether it's it's not just the you know the orchestration piece and setting up and let it a lot of automate and have some you know change control you're looking at this from a data perspective how do I support this ongoing and make it easy to make changes as we evolve that the the cloud is very dynamic the the nature of how the fast is expanding the number of features is astonishing trying to keep up to date with a number of just networking capabilities and services that are added so I think day to operation starts with a fundable understanding of you know building out supporting a customer's environments and making it the automation piece easy from from you know a distance I think yeah and you know taking that to the next level of being able to enable customers to have catalog items that they can pick and choose hey I need this network connectivity from this cloud location back to this on pram and being able to have that automated and provisioned just simply by ordering it for the folks watching out there guys take a minute to explain as you guys are in the trenches doing a lot of good work what are some of the engagement that you guys get into how does that progress what is the what's what happens there they call you up and say hey I need multi-cloud or you're already in there I mean take us through why how someone can engage to use a global si to come in and make this thing happen what's typical engagement look like yeah so from our perspective we typically have a series of workshops in a methodology that we kind of go along the journey number one we have a foundational approach and I don't mean foundation meaning the network foundation that's a very critical element we got a factor in security we've got to factor in automation so we think about foundation we do a workshop that starts with education a lot of times we'll go in and we'll just educate the customer what does VPC sharing you know what is a private link and asher how does that impact your business you know customers I want to share services out in an ecosystem with other customers and partners well there's many ways to accomplish that so our goal is to you know understand those requirements and then build that strategy with them thoughts Georgia yeah I mean I'm one of the guys that's down in the weeds making things happen so I'm not the guy on the front line interfacing with the customers every day but we have a similar approach you know we have a consulting practice that will go out and and apply their practices to see what those and when do you parachute in yeah and when I've been is I'm on the back end working with our offering development leads for the networking so we understand or seeing what customers are asking for and we're on the back end developing the solutions that integrate with our own offerings as well as enable other customers to just deploy quickly to meet their connectivity needs it so the patterns are similar right final question for you guys I want to ask you to paint a picture of what success looks like and you know the name customers didn't again reveal kind of who they are but what does success look like in multi-cloud as you as you paint a picture for the folks here and watching on the live stream it's someone says hey I want to be multi-cloud I got to have my operations agile I want full DevOps I want programmability security built in from day zero what does success look like yeah I think success looks like this so when you're building out a network the network is a harder thing to change than some other aspects of cloud so what we think is even if you're thinking about that second cloud which we have most of our customers are on to public clouds today they might be dabbling in is you build that network foundation at architecture that takes in consideration where you're going and so once we start building that reference architecture out that shows this is how to sit from a multi-cloud perspective not a single cloud and let's not forget our branches let's not forget our data centers let's not forget how all this connects together because that's how we define multi-cloud it's not just in the cloud it's on Prem and it's off Prem and so collectively I think the key is also is that we provide them an hld you got to start with a high level design that can be tweaked as you go through the journey but you got to give a solid structural foundation and that networking which we think most customers think as not not the network engineers but as an afterthought we want to make that the most critical element before you start the journey Jorge from your seed how do you success look for you so you know it starts out on these journeys often start out people not even thinking about what is gonna happen with what their network needs are when they start their migration journey to the cloud so I want this success to me looks like them being able to end up not worrying about what's happening in the network when they move to the cloud good guys great insight thanks for coming on share and pen I've got a round of applause the global system integrators [Applause] [Music] okay welcome back from the live feed I'm chef for with the q Steve Valenti CEO of aviatrix my co-host our next panel is the aviatrix certified engineer is also known as aces this is the folks that are certified their engineering they're building these new solutions please welcome Toby Foss from informatica Stacy linear from Teradata and Jennifer Reed with Victor Davis to the stage I was just gonna I was just gonna rip you guys see where's your jackets and Jen's got the jacket on okay good love the aviatrix aces pile of gear they're above the clouds story to new heights that's right so guys aviatrix aces love the name I think it's great certified this is all about getting things engineered so there's a level of certification I want to get into that but first take us through the day in the life of an ace and just to point out Stacey's a squad leader so he's like it Squadron Leader Roger and leader yeah Squadron Leader he's got a bunch of aces underneath him but share your perspective day-in-the-life Jennifer we'll start with you sure so I have actually a whole team that works for me both in the in the North America both in the US and in Mexico and so I'm really working to get them certified as well so I can become a squad leader myself but it's important because one of the the critical gaps that we've found is people having the networking background because they're you graduate from college and you have a lot of computer science background you can program you've got Python but networking in packets they just don't get and so just taking them through all the processes that it's really necessary to understand when you're troubleshooting is really critical mm-hm and because you're gonna get an issue where you need to figure out where exactly is that happening on the network you know is my my issue just in the V PC is and on the instant side is a security group or is it going on print and is this something actually embedded within Amazon itself I mean I should troubleshot an issue for about six months going back and forth with Amazon and it was the vgw VPN because they were auto-scaling on two sides and we ended up having to pull out the Cisco's and put in aviatrix so I could just say okay it's fixed and actually actually helped the application teams get to that and get it solved yeah but I'm taking a lot of junior people and getting them through that certification process so they can understand and see the network the way I see the network I mean look I've been doing this for 25 years when I got out when I went in the Marine Corps that's what I did and coming out the network is still the network but people don't get the same training they get they got in the 90s it's just so easy just write some software they work takes care of itself yes he'll be will good I'll come back to that I want to come back to that problem solve with Amazon but Toby I think the only thing I have to add to that is that it's always the network fault as long as I've been in never I've always been the network's fault and I'm even to this day you know it's still the network's fault and part of being a network guy is that you need to prove when it is and when it's not your fault and that means you need to know a little bit about a hundred different things to make that and now you've got a full stack DevOps you got to know a lot more times another 100 and these times are changing yeah they say you're Squadron Leader I get that right what is what is the squadron leader first can you describe what it is I think probably just leading all the network components of it but not they from my perspective when to think about what you ask them was it's about no issues and the escalation soft my day is a good outcome that's a good day it's a good day again every mission the Amazon this brings up a good point you know when you have these new waves come in you have a lot of new things new we use cases a lot of the finger-pointing it's that guys problem that girls problem so what how do you solve that and how do you get the young guns up to speed is there training is that this is where the certification comes in was where the certification is really going to come in I know when we we got together at reinvent one of the the questions that that we had with Steve and the team was what what should our certification look like you know she would just be teaching about what aviatrix troubleshooting brings to bear like what should that be like and I think Toby and I were like no no no that's going a little too high we need to get really low because the the better someone can get at actually understanding what actually happening in the network and and where to actually troubleshoot the problem how to step back each of those processes because without that it's just a big black box and they don't know you know because everything is abstracted in Amazon Internet and Azure and Google is substracted and they have these virtual gateways they have VPNs that you just don't have the logs on it's you just don't know and so then what tools can you put in front of them of where they can look because there are four logs well as long as they turned on the flow logs when they built it you know and there's like each one of those little things that well if they'd had decided to do that when they built it it's there but if you can come in later to really supplement that with training to actual troubleshoot and do a packet capture here as it's going through then teaching them how to read that even yeah Toby we were talking before he came on up on stage about your career you've been networking all your time and then you know you're now mentoring a lot of younger people how is that going because the people who come in fresh they don't have all the old war stories they don't know you talk about yeah that's never fault I walk in Mayr feet in the snow when I was your age I mean it's so easy now right they say what's your take on how you train the young piece so I've noticed two things one is that they are up to speed a lot faster in generalities of networking they can tell you what a network is in high school level now where I didn't learn that too midway through my career and they're learning it faster but they don't necessarily understand why it's that way here you know everybody thinks that it's always slash 24 for a subnet and they don't understand why you can break it down smaller why it's really necessary so the the ramp up speed is much faster for these guys that are coming in but they don't understand why and they need some of that background knowledge to see where it's coming from and why is it important and old guys that's where we thrive Jennifer you mentioned you got in from the Marines health spa when you got into networking how what was it like then and compare it now most like we've heard earlier static versus dynamic don't be static because back then you just said the network you got a perimeter yeah I know there was no such thing yeah no so back in the day I mean I mean we had banyan vines for email and you know we had token ring and I had to set up token ring networks and figure out why that didn't work because how many of things were actually sharing it but then actually just cutting fiber and running fiber cables and dropping them over you know shelters to plug them in and oh crap they swung it too hard and shattered it and how I gotta be great polished this thing and actually shoot like to see if it works I mean that was the network current five cat 5 cables to run an Ethernet you know and then from that just said network switches dumb switches like those were the most common ones you had then actually configuring routers and you know logging into a Cisco router and actually knowing how to configure that and it was funny because I had gone all the way up and was a software product manager for a while so I've gone all the way up the stack and then two and a half three years ago I came across to to work with entity group that became Victor Davis but we went to help one of our customers Avis and it was like okay so we need to fix the network okay I haven't done this in 20 years but all right let's get to it you know because it really fundamentally does not change it's still the network I mean I've had people tell me well you know when we go to containers we will not have to worry about the network and I'm like yeah you don't I do and then with this with and programmability is it really interesting so I think this brings up the certification what are some of the new things that people should be aware of that come in with the aviatrix ace certification what are some of the highlights can you guys share some of the some of the highlights around the certifications I think some of the importance is that it's it doesn't need to be vendor specific for network generality or basic networking knowledge and instead of learning how Cisco does something or how Palo Alto does something we need to understand how and why it works as a basic model and then understand how each vendor has gone about that problem and solved it in a general that's true in multi cloud as well you can't learn how cloud networking works without understanding how AWS integer and GCP are all slightly the same but slightly different and some things work and some things don't I think that's probably the number one take I think having a certification across clouds is really valuable because we heard the global s eyes cover the business issues what does it mean to do that is it code is that networking is the configuration is that aviatrix what is the I mean obviate races the ACE certifications but what is it about the multi cloud that makes it multi networking and multi vendor easy answer is yes so you got to be a general let's go to your hands and all you have to be it takes experience because it's every every cloud vendor has their own certification whether that is ops and [Music] advanced networking and advanced security or whatever it might be yeah they can take the test but they have no idea how to figure out what's wrong with that system and the same thing with any certification but it's really getting your hands in there and actually having to troubleshoot the problems you know actually work the problem you know and calm down it's going to be okay I mean because I don't know how many calls I've been on or even had aviatrix join me on it's like okay so everyone calm down let's figure out what's happening it's like we've looked at that screen three times looking at it again it's not gonna solve that problem right but at the same time you know remaining calm but knowing that it really is I'm getting a packet from here to go over here it's not working so what could be the problem you know and actually stepping them through those scenarios but that's like you only get that by having to do it you know and seeing it and going through it and then I have a question so we you know I just see it we started this program maybe six ago we're seeing a huge amount of interest I mean we're oversubscribed on all the training sessions we've got people flying from around the country even with coronavirus flying to go to Seattle to go to these events were oversubscribed good is that watching leader would put there yeah is that something that you see in your organization's are you recommending that to people do you see I mean I'm just I guess I'm surprised I'm not surprised but I'm really surprised by the demand if you would of this multi-cloud network certification because it really isn't anything like that is that something you guys can comment on or do you see the same things in your organization's I see from my side because we operate in the multi cloud environment so it really helps and it's beneficial for us yeah I think I would add that uh networking guys have always needed to use certifications to prove that they know what they know right it's not good enough to say yeah I know IP addresses or I know how a network works and a couple little check marks or a little letters by your name helps give you validity um so even in our team we can say hey you know we're using these certifications to know that you know enough of the basics and enough of the understandings that you have the tools necessary right so I guess my final question for you guys is why an eighth certification is relevant and then second part is share with the livestream folks who aren't yet a certified or might want to jump in to be AVH or certified engineers why is it important so why is it relevant and why should someone want to be an ace-certified I'm used to write engineer I think my view is a little different I think certification comes from proving that you have the knowledge not proving that you get a certification to get know I mean they're backwards so when you've got the training in the understanding and the you use that to prove and you can like grow your certification list with it versus studying for a test to get a certification and have no understanding of ok so that who is the right person that look at this is saying I'm qualified is it a network engineer is it a DevOps person what's your view you know is it a certain you know I think cloud is really the answer it's the as we talked like the edge is getting eroded so is the network initially eating eroded we're getting more and more of some network some DevOps some security lots and lots of security because network is so involved in so many of them that it's just the next progression I would say I expand that to more automation engineers because we have those nails probably extended as well well I think that the training classes themselves are helpful especially the entry-level ones for people who may be quote-unquote cloud architects but have never done anything and networking for them to understand why we need those things to really work whether or not they go through to eventually get a certification is something different but I really think fundamentally understanding how these things work it makes them a better architect makes some better application developer but even more so as you deploy more of your applications into the cloud really getting an understanding even from our people who have tradition down on Prem networking they can understand how that's going to work in the cloud - well I know we've got just under 30 seconds left but I want to get one more question and just one more for the folks watching that are you maybe younger that don't have that networking training from your experiences each of you can answer why is it should they know about networking what's the benefit what's in it for them motivate them share some insights and why they should go a little bit deeper in networking Stacy we'll start with you we'll go down let's say it's probably fundamental right if you want to deliver solutions networking use the very top I would say if you fundamental of an operating system running on a machine how those machines talk together as a fundamental change is something that starts from the base and work your way up right well I think it's a challenge because you you've come from top-down now you're gonna start looking from bottom-up and you want those different systems to cross communicate and say you built something and you're overlapping IP space not that that doesn't happen but how can I actually make that still operate without having to reappear e-platform it's like those challenges like those younger developers or sis engineers can really start to get their hands around and understand those complexities and bring that forward in their career they got to know the pilot pipes are working and some plumbing that's right works at how to code it that's right awesome thank you guys for great insights ace certain babies you're certified engineers also known as aces give a round of applause thank you okay all right that concludes my portion thank you Steve thanks for have Don thank you very much that was fantastic everybody round of applause for John for you yeah so great event great event I'm not going to take long we've got we've got lunch outside for that for the people here just a couple of things just call to action right so we saw the Aces you know for those of you out on the stream here become a certified right it's great for your career it's great for not knowledge is is fantastic it's not just an aviatrix thing it's gonna teach you about cloud networking multi-cloud networking with a little bit of aviatrix exactly what the cisco CCIE program was for IP network that type of the thing that's number one second thing is is is is learn right so so there's a there's a link up there for the four to join the community again like I started this this is a community this is the kickoff to this community and it's a movement so go to what a v8 community a bh6 comm was starting a community at multi cloud so you know get get trained learn I'd say the next thing is we're doing over a hundred seminars in across the United States and also starting into Europe soon will come out and will actually spend a couple hours and talk about architecture and talk about those beginning things for those of you on the you know on the livestream in here as well you know we're coming to a city near you go to one of those events it's a great way to network with other people that are in the industry as well as start to learn and get on that multi-cloud journey and then I'd say the last thing is you know we haven't talked a lot about what aviatrix does here and that's intentional we want you you know leaving with wanting to know more and schedule get with us in schedule a multi our architecture workshop session so we we sit out with customers and we talk about where they're at in that journey and more important where they're going and to find that end state architecture from networking compute storage everything and everything you heard today every panel kept talking about architecture talking about operations those are the types of things that we saw we help you cook define that canonical architecture that system architecture that's yours so for so many of our customers they have three by five plotted lucid charts architecture drawings and it's the customer name slash aviatrix arc network architecture and they put it on their whiteboard that's what what we and that's the most valuable thing they get from us so this becomes their 20-year network architecture drawing that they don't do anything without talking to us and look at that architecture that's what we do in these multi hour workshop sessions with customers and that's super super powerful so if you're interested definitely call us and let's schedule that with our team so anyway I just want to thank everybody on the livestream thank everybody here hopefully it was it was very useful I think it was and joined the movement and for those of you here join us for lunch and thank you very much [Applause] [Music] [Applause] [Music] you

>> Announcer: Live from Las Vegas, it's theCUBE. Covering Splunk.conf19, brought to you by Splunk. >> Okay, welcome back everyone. We are here inside for Splunk.conf, their 10th-year conference. We've been here seven years. I'm John Furrier, the host. Our next guest is Sherrie Caltagirone, founder and executive director of the Global Emancipation Network, a cutting-edge company and organization connecting different groups together to fight that battle combating human trafficking with the power of data analytics. We're in a digital world. Sherrie, thanks for coming in. >> Thank you so much for having me. >> So love your mission. This is really close to my heart in terms of what you're doing because with digital technologies, there's a unification theme here at Splunk, unifying data sets, you hear on the keynotes. You guys got a shout-out on the keynote, congratulations. >> Sherrie: We did, thank you. >> So unifying data can help fight cybersecurity, fight the bad guys, but also there's other areas where unification comes in. This is what you're doing. Take a minute to explain the Global Emancipation Network. >> Yeah, thank you. So what we do is we are a data analytics and intelligence nonprofit, dedicated to countering all forms of human trafficking, whether it's labor trafficking, sex trafficking, or any of the sub types, men, women, and children all over the world. So when you think about that, what that really means is that we interact with thousands of stakeholders across law enforcement, governments, nonprofits, academia, and then private sector as well. And all of those essentially act as data silos for human trafficking data. And when you think about that as trafficking as a data problem or you tackle it as a data problem, what that really means is that you have to have a technology and data-led solution in order to solve the problem. So that's really our mission here is to bring together all of those stakeholders, give them easy access to tools that can help improve their counter posture. >> And where are you guys based and how big is the organization? What's the status? Give a quick plug for where you guys are at and what the current focus is. >> Yeah, perfect, so I am based in San Luis Obispo, California. We have just started a brand new trafficking investigations hub out at Cal Poly there. They're a fantastic organization whose motto is learn by doing, and so we are taking the trafficking problem and the tangential other issues, so like we mentioned, cyber crime, wildlife trafficking, drugs trafficking, all of this sort of has a criminal convergence around it and applying technology, and particularly Splunk, to that. >> Yeah, and I just want to make a note 'cause I think it's important to mention. Cal Poly's doing some cutting-edge work. Alison Robinson, Bill Britton, who runs the program over there, they got a great organization. They're doing a lot of data-oriented from media analysis, data, big focus there. Cal Poly quite a big organization. >> They are, and they're doing some wonderful things. AWS just started an innovation hub called the DX Hub there that we are a part of, really trying to tackle these really meaty problems here that are very data-centric and technology-centric. And Cal Poly's the best place to do that. >> Great, let's get into some of the details. One of the things around the news, obviously seeing Mark Zuckerberg doing the tour, Capitol Hill, DC, Georgetown, free speech, data. Facebook has been kind of blamed for breaking democracy. At the same time, it's a platform. They don't consider themselves as an editorial outlet. My personal opinion, they are, but they hide behind that platform. So bad things have happened, good things can happen. So you're seeing technology kind of being pigeonholed as bad. Tech for bad, there's also a tech for good. Pat Gelsinger, the CEO of VMware, publicly said technology's neutral. We humans can shape it. So you guys are looking at it from shaping it for good. How are you doing it? What are some of the things that are going on technically from a business standpoint that is shaping and unifying the data? >> Yeah, I mean, it's absolutely certain that technology has facilitated human trafficking and other ills throughout the world. It's a way that people bring their product, in this case, sadly, human beings, to the market to reach buyers, right? And technology absolutely facilitates that. But, as you mentioned, we can use that against them. So actually here at Conf we are bringing together for a first time the partnership that we did with Splunk for Good, Accenture, and Global Emancipation Network to help automatically classify and score risky businesses, content, ads, and individuals there to help not only with mitigating risk and liability for the private sector, whether it's social media giants or if it's transportation, hospitality, you name it, but also help ease the burden of content moderators. And that's the other side of it. So when you live in this space day in and day out, you really exact a mental toll here. It's really damaging to the individual who sits and reads this material and views photos over and over again. So using technology is a way to automate some of those investigations, and the identification of that content could be helpful in a variety of ways. >> In a way, it's a whole other adversary formula to try to identify. One of the things that Splunk, as we've been here at Splunk Conference, they've been about data from day one. A lot of data and then grew from there, and they have this platform. It's a data problem, and so one of the things that we're seeing here is diverse data, getting at more data makes AI smarter, makes things smarter. But that's hard. Diverse data might be in different data sets or silos, different groups. Sharing data's important, so getting that diverse data, how difficult is it for you guys? Because the bad guys can hide. They're hiding in from Craigslist to social platforms. You name it, they're everywhere. How do you get the data? What's the cutting-edge ingestion? Where are the shadows? Where are the blind spots? How do you guys look at that? Because it's only getting bigger. >> Absolutely, so we do it through a variety of different ways. We absolutely see gathering and aggregating and machining data the most central thing to what we do at Global Emancipation Network. So we have a coalition, really, of organizations that we host their scrapers and crawlers on and we run it through our ingestion pipeline. And we are partnered with Microsoft and AWS to store that data, but everything goes through Splunk as well. So what is that data, really? It's data on the open web, it's on the deep web. We have partners as well who look at the dark web, too, so Recorded Future, who's here at Conf, DeepL as well. So there's lots of different things on that. Now, honestly, the data that's available on the internet is easy for us to get to. It's easy enough to create a scraper and crawler, to even create an authenticated scraper behind a paywall, right? The harder thing is those privately held data sets that are in all of those silos that are in a million different data formats with all kinds of different fields and whatnot. So that is where it's a little bit more of a manual lift. We're always looking at new technologies to machine PDFs and that sort of thing as well. >> One of the things that I love about this business we're on, the wave we're on, we're in a digital media business, is that we're in pursuit of the truth. Trust, truth is a big part of what we do. We talk to people, get the data. You guys are doing something really compelling. You're classifying evil. Okay, this is a topic of your talk track here. Classifying evil, combating human trafficking with the power of data analytics. This is actually super important. Could you share why, for people that aren't following inside the ropes of this problem, why is it such a big problem to classify evil? Why isn't it so easy to do? What's the big story? What should people know about this challenge? >> Yeah, well, human trafficking is actually the second-most profitable crime in the world. It's the fastest-growing crime. So our best estimates are that there's somewhere between 20 million and 45 million people currently enslaved around the world. That's a population the size of Spain. That's nothing that an individual, or even a small army of investigators can handle. And when you think about the content that each of those produce or the traffickers are producing in order to advertise the services of those, it's way beyond the ability of any one organization or even, like I said, an army of them, to manage. And so what we need to do then is to be able to find the signal in the noise here. And there is a lot of noise. Even if you're looking at sex trafficking, particularly, there's consensual sex work or there's other things that are a little bit more in that arena, but we want to find that that is actually engaging in human trafficking. The talk that you mentioned that we're doing is actually a fantastic use case. This is what we did with Splunk for Good and Accenture. We were actually looking at doing a deep dive into the illicit massage industry in the US, and there are likely over 10,000 illicit massage businesses in the US. And those businesses, massages and spas, that are actually just a front for being a brothel, essentially. And it generates $2 billion a year. We're talking about a major industry here, and in that is a very large component of human trafficking. There's a very clear pipeline between Korea, China, down to New York and then being placed there. So what we ended up needing to do then, and again, we were going across data silos here, looking at state-owned data, whether it was license applications, arrest filings, legal cases, that sort of thing, down into the textual advertisements, so doing NLP work with weighted lexicons and really assigning a risk score to individual massage businesses to massage therapist business owners and then, again, to that content. So looking, again, how can we create a classifier to identify evil? >> It's interesting, I think about when you're talking about this is a business. This is a business model, this business continuity. There's a supply chain. This is a bona fide, underground, or overt business process. >> Yeah, absolutely, and you're right on that too that it is actually overt because at this point, traffickers actually operate with impunity for the most part. So actually framing it that way, as a market economy, whether it's shadowy and a little bit more in the black market or completely out in the open, it really helps us frame our identification, how we can manage disruptions, who need to be the stakeholders at the table for us in order to have a wider impact rather than just whack-a-mole. >> I was just talking with Sonia, one of our producers, around inclusiveness and this is so obviously a human passion issue. Why don't we just solve it? I mean, why doesn't someone like the elite class or world organization, just Davos, and people just say they're staring at this problem. Why don't they just say, "Hey, this is evil. "Let's just get rid of it." What's the-- >> Well, we're working on it, John, but the good thing is, and you're absolutely right, that there are a number of organizations who are actually working on it. So not just us, there's some other amazing nonprofits. But the tech sector's actually starting to come to the table as well, whether it's Splunk, it's Microsoft, it's AWS, it's Intel, IBM, Accenture. People are really waking up to how damaging this actually is, the impact that it has on GDP, the way that we're particularly needing to protect vulnerable populations, LGBTQ youth, children in foster care, indigenous populations, refugees, conflict zones. So you're absolutely right. I think, given the right tools and technology, and the awareness that needs to happen on the global stage, we will be able to significantly shrink this problem. >> It's classic arbitrage. If I'm a bad guy, you take advantage of the systematic problems of what's in place, so the current situation. Sounds like siloed groups somewhat funded, not mega-funded. This group over here, disconnect between communications. So you guys are, from what I could tell, pulling everyone together to kind of create a control plane of data to share information to kind of get a more holistic view of everything. >> Yeah, that's exactly it. Trying to do it at scale, at that. So I mentioned that at first we were looking at the illicit massage sector. We're moving over to the social media to look again at the recruitment side and content. And the financial sector is really the common thread that runs through all of it. So being able to identify, taking it back to a general use case here from cyber security, just indicators as well, indicators of compromise, but in our case, these are just words and lexicons, dollar values, things like that, down to behavioral analytics and patterns of behavior, whether people are moving, operating as call centers, network-like behavior, things that are really indicative of trafficking. And making sure that all of those silos understand that, are sharing the data they can, that's not overly sensitive, and making sure that we work together. >> Sherrie, you mentioned AWS. Teresa Carlson, I know she's super passionate about this. She's a leader. Cal Poly, we mentioned that. Splunk, you mentioned, how is Splunk involved? Are they the core technology behind this? Are they powering the-- >> They are, yeah, Splunk was actually with us from day one. We sat at a meeting, actually, at Microsoft and we were really just white boarding. What does this look like? How can we bring Splunk to bear on this problem? And so Splunk for Good, we're part of their pledge, the $10 million pledge over 10 years, and it's been amazing. So after we ingest all of our data, no matter what the data source is, whatever it looks like, and we deal with the ugliest and most unstructured data ever, and Splunk is really the only tool that we looked at that was able to deal with that. So everything goes through Splunk. From there, we're doing a series of external API calls that can really help us enrich that data, add correlations, whether it's spatial data, network analysis, cryptocurrency analysis, public records look-ups, a variety of things. But Splunk is at the heart. >> So I got to ask you, honestly, as this new architecture comes into play for attacking this big problem that you guys are doing, as someone who's not involved in that area, I get wow, spooked out by that. I'm like, "Wow, this is really bad." How can people help? What can people do either in their daily lives, whether it's how they handle their data, observations, donations, involvement? How do people get involved? What do you guys see as some areas that could be collaborating with? What do you guys need? How do people get involved? >> Yeah, one that's big for me is I would love to be able to sit in an interview like this, or go about my daily life, and know that what I am wearing or the things that I'm interacting with, my phone, my computer, weren't built from the hands of slave labor. And at this point, I really can't. So one thing that everybody can do is demand of the people that they are purchasing from that they're doing so in a socially viable and responsible way. So looking at supply chain management as well, and auditing specifically for human trafficking. We have sort of the certified, fair-trade certified organic seals. We need something like that for human trafficking. And that's something that we, the people, can demand. >> I think you're on the right track with that. I see a big business model wave where consumer purchasing power can be shifted to people who make the investments in those areas. So I think it's a big opportunity. It's kind of a new e-commerce, data-driven, social-impact-oriented economy. >> Yep, and you can see more and more, investment firms are becoming more interested in making socially responsible investments. And we just heard Splunk announce their $100 million social innovation fund as well. And I'm sure that human trafficking is going to be part of that awareness. >> Well, I'll tell you one of the things that's inspirational to me personally is that you're starting to see power and money come into helping these causes. My friend, Scott Tierney, just started a venture capital firm called Valo Ventures in Palo Alto. And they're for-profit, social impact investors. So they see a business model shift where people are getting behind these new things. I think your work is awesome, thank you. >> Yeah, thank you so much, I appreciate it. >> Thanks for coming on. Congratulations on the shout-out on the keynote. Appreciate it. The Global Emancipation Network, check them out. They're in San Luis Obispo, California. Get involved. This is theCUBE with bringing you the signal from the noise here at .conf. I'm John Furrier, back with more after this short break. (upbeat music)

>> From the Silicon Angle Media office in Boston, Massachusetts, It's theCUBE. (upbeat music) Now, here's your host, Stu Miniman. >> Hi. I'm Stu Miniman, and this is theCUBE's Boston area studio; our actually brand-new studio, and I'm really excited to have I believe is a first-time guest, a long-time caller, you know, a long time listener >> Yeah, yep. first time caller, good buddy of mine Dave Graham, who is the director, is a director of emerging technologies: messaging at Dell Technologies. Disclaimer, Dave and I worked together at a company some of you might have heard on the past, it was EMC Corporation, which was a local company. Dave and I both left EMC, and Dave went back, after Dell had bought EMC. So Dave, thanks so much for joining, it is your first time on theCUBE, yes? >> It is the first time on theCUBE. >> Yeah, so. >> Lets do some, Some of the first times that I actually interacted with, with this team here, you and I were bloggers and doing lots of stuff back in the industry, so it's great to be able to talk to you on-camera. >> Yeah, same here. >> All right, so Dave, I mentioned you were a returning former EMC-er, now Dell tech person, and you spent some time at Juniper, at some startups, but give our audience a little bit about your background and your passions. >> Oh, so background-wise, yep, so started my career in technology, if you will, at EMC, worked, started in inside sales of all places. Worked my way into a consulting/engineer type position within ECS, which was, obviously a pretty hard-core product inside of EMC now, or Dell Technologies now. Left, went to a startup, everybody's got to do a start up at some point in their life, right? Take the risk, make the leap, that was awesome, was actually one of those Cloud brokers that's out there, like Nasuni, company called Sertis. Had a little bit of trouble about eight months in, so it kind of fell apart. >> Yeah, the company did, not you. >> The company did! (men laughing) I was fine, you know, but the, yeah, the company had some problems, but ended up leaving there, going to Symantec of all places, so I worked on the Veritas side, kind of the enterprise side, which just recently got bought out by Avago, evidently just. >> Broadcom >> Broadcom, Broadcom, art of the grand whole Avago. >> Dave, Dave, you know we're getting up there in years and our tech, when we keep talking about something 'cause I was just reading about, right, Broadcom, which was of course Avago bought Broadcom in the second largest tech acquisition in history, but when they acquired Broadcom, they took on the name because most people know Broadcom, not as many people know Avago, even those of us with backgrounds in the chip semiconductor and all those pieces. I mean you got Brocade in there, you've got some of the software companies that they've bought over the time, so some of those go together. But yeah, Veritas and Symantec, those of us especially with some storage and networking background know those brands well. >> Absolutely, PLX's being the PCI switched as well, it's actually Broadcom, those things. So yeah, went from Symantec after a short period of time there, went to Juniper Networks, ran part of their Center of Excellence, kind of a data center overlay team, the only non-networking guy in a networking company, it felt like. Can't say that I learned a ton about the networking side, but definitely saw a huge expansion in the data center space with Juniper, which was awesome to see. And then the opportunity came to come back to Dell Technologies. Kind of a everything old becoming new again, right? Going and revisiting a whole bunch of folks that I had worked with 13, you know, 10 years ago. >> Dave, it's interesting, you know, I think about, talk about somebody like Broadcom, and Avago, and things like that. I remember reading blog posts of yours, that you'd get down to some of that nitty-level, you and I would be ones that would be the talk about the product, all right now pull the board out, let me look at all the components, let me understand, you know, the spacing, and the cooling, and all the things there, but you know here it's 2019, Dave. Don't you know software is eating the world? So, tell us a little bit about what you're working on these days, because the high-level things definitely don't bring to mind the low-level board pieces that we used to talk about many years ago. >> Exactly, yeah, it's no longer, you know, thermals and processing power as much, right? Still aspects of that, but a lot of what we're focused on now, or what I'm focused on now is within what we call the emerging technology space. Or horizon 2, horizon 3, I guess. >> Sounds like something some analyst firm came up with, Dave. (Dave laughing) >> Yeah, like Industry 4.0, 5.0 type stuff. It's all exciting stuff, but you know when you look at technologies like five, 5G, fifth generation wireless, you know both millimeter waves, sub six gigahertz, AI, you know, everything old becoming new again, right? Stuff from the fifties, and sixties that's now starting to permeate everything that we do, you're not opening your mouth and breathing unless you're talking about AI at some point, >> Yeah, and you bring up a great point. So, we've spent some time with the Dell team understanding AI, but help connect for our audience that when you talk high AI we're talking about, we're talking about data at the center of everything, and it's those applications, are you working on some of those solutions, or is it the infrastructure that's going to enable that, and what needs to be done at that level for things to work right? >> I think it's all of the above. The beauty of kind of Dell Technologies that you sit across, both infrastructure and software. You look at the efforts and the energies, stuff like VMware buying, BitFusion, right, as a mechanism trying to assuage some of that low-level hardware stuff. Start to tap into what the infrastructure guys have always been doing. When you bring that kind of capability up the stack, now you can start to develop within the software mindset, how, how you're going to access this. Infrastructure still plays a huge part of it, you got to run it on something, right? You can't really do serverless AI at this point, am I allowed to say that? (man laughing) >> Well, you could say that, I might disagree with you, because absolutely >> Eh, that's fine. there's AI that's running on it. Don't you know, Dave, I actually did my serverless 101 article that I had, I actually had Ashley Gorakhpurwalla, who is the General Manager of Dell servers, holding the t-shirt that "there is no serverless, it's just, you know, a function that you only pay the piece that you need when you need and everything there." But the point of the humor that I was having there is even the largest server manufacturer in the world knows that underneath that serverless discussion, absolutely, there is still infrastructure that plays there, just today it tends to primarily be in AWS with all of their services, but that proliferation, serverless, we're just letting the developers be developers and not have to think about that stuff, and I mean, Dave, the stuff we've had background, you know, we want to get rid of silos and make things simpler, I mean, it's the things we've been talking about for decades, it's just, for me it was interesting to look at, it is very much a developer application driven piece, top-down as opposed to so many of the virtualization and infrastructure as a service is more of a bottom-up, let me try to change this construct so that we can then provide what you need above it, it's just a slightly different way of looking at things. >> Yeah, and I think we're really trying to push for that stuff, so you know you can bundle together hardware that makes it, makes the development platform easy to do, right? But the efforts and energy of our partnerships, Dell has engaged in a lot of partnerships within the industry, NVIDIA, Intel, AMD, Graphcore, you name it, right? We're out in that space working along with those folks, but a lot of that is driven by software. It's, you write to a library, like Kudu, or, you know pyEight, you know, PyTorch, you're using these type of elements and you're moving towards that, but then it has to run on something, right? So we want to be in that both-end space, right? We want to enable that kind of flexibility capability, and obviously not prevent it, but we want to also expose that platform to as many people within the industry as possible so they can kind of start to develop on it. You're becoming a platform company, really, when it comes down to it. >> I don't want to get down the semantical arguments of AI, if you will, but what are you hearing from customers, and what's some kind of driving some of the discussions lately that's the reality of AI as opposed to some of just the buzzy hype that everybody talks about? >> Well I still think there's some ambiguity in market around AI versus automation even, so what people that come and ask us are well, "you know, I believe in this thing called artificial intelligence, and I want to do X, Y, and Z." And these particular workloads could be better handled by a simple, not to distill it down to the barest minimum, but like cron jobs, something that's, go back in the history, look at the things that matter, that you could do very very simply that don't require a large amount of library, or sort of an understanding of more advanced-type algorithms or developments that way. In the reverse, you still have that capability now, where everything that we're doing within industry, you use chat-bots. Some of the intelligence that goes into those, people are starting to recognize, this is a better way that I could serve my customers. Really, it's that business out kind of viewpoint. How do I access these customers, where they may not have the knowledge set here, but they're coming to us and saying, "it's more than just, you know, a call, an IVR system," you know, like an electronic IVR system, right? Like I come in and it's just quick response stuff. I need some context, I need to be able to do this, and transform my data into something that's useful for my customers. >> Yeah, no, this is such a great point, Dave. The thing I've asked many times, is, my entire career we've talked about intelligence and we've talked about automation, what's different about it today? And the reality is, is it used to be all right. I was scripting things, or I would have some Bash processes, or I would put these things together. The order of magnitude and scale of what we're talking about today, I couldn't do it manually if I wanted to. And that automation is really, can be really cool these days, and it's not as, to set all of those up, there is more intelligence built into it, so whether it's AI or just machine learning kind of underneath it, that spectrum that we talk about it, there's some real-use cases, a real lot of things that are happening there, and it definitely is, order of magnitudes more improved than what we were talking about say, back when we were both at EMC and the latest generation of Symmetrix was much more intelligent than the last generation, but if you look at that 10 years later, boy, it's, it is night and day, and how could we ever have used those terms before, compared to where we are today. >> Yeah it's, it's, somebody probably at some point coined the term, "exponential". Like, things become exponential as you start to look at it. Yeah, the development in the last 10 years, both in computing horsepower, and GPU/GPGPU horsepower, you know, the innovation around, you know FPGAs are back in a big way now, right? All that brainpower that used to be in these systems now, you now can benefit even more from the flexibility of the systems in order to get specific workloads done. It's not for everybody, we all know that, but it's there. >> I'm glad you brought up FPGAs because those of us that are hardware geeks, I mean, some reason I studied mechanical engineering, not realizing that software would be a software world that we live in. I did a video with Amy Lewis and she's like, "what was your software-defined moments?" I'm like, "gosh, I'm the frog sitting in the pot, and, would love to, if I can't network-diagram it, or put these things together, networking guy, it's my background! So, the software world, but it is a real renaissance in hardware these days. Everything from the FPGAs you mentioned, you look at NVIDIA and all of their partners, and the competitors there. Anything you geeking out on the hardware side? >> I, yeah, a lot of the stuff, I mean, the era of GPU showed up in a big way, all right? We have NVIDIA to thank for that whole, I mean, the kudos to them for developing a software ecosystem alongside a hardware. I think that's really what sold that and made that work. >> Well, you know, you have to be able to solve that Bitcoin mining problem, so. >> Well, you know, depending on which cryptocurrency you did, EMD kind of snuck in there with their stuff and they did some of that stuff better. But you have that kind of competing architecture stuff, which is always good, competition you want. I think now that what we're seeing is that specific workloads now benefit from different styles of compute. And so you have the companies like Graphcore, or the chip that was just launched out of China this past week that's configurable to any type of network, enteral network underneath the covers. You see that kind of evolution in capability now, where general purpose is good, but now you start to go into reconfigurable elements so, I'll, FPGAs are some of these more advanced chips. The neuromorphic hardware, which is always, given my background in psychology, is always interesting to me, so anything that is biomorphic or neuromorphic to me is pinging around up here like, "oh, you're going to emulate the brain?" And Intel's done stuff, BraincChip's done stuff, Netspace, it's amazing. I just, the workloads that are coming along the way, I think are starting to demand different types or more effectiveness within that hardware now, so you're starting to see a lot of interesting developments, IPUs, TPUs, Teslas getting into the inferencing bit now, with their own hardware, so you see a lot of effort and energy being poured in there. Again, there's not going to be one ring to rule them all, to cop Tolkien there for a moment, but there's going to be, I think you're going to start to see the disparation of workloads into those specific hardware platforms. Again, software, it's going to start to drive the applications for how you see these things going, and it's going to be the people that can service the most amount of platforms, or the most amount of capability from a single platform even, I think are the people who are going to come out ahead. And whether it'll be us or any of our August competitors, it remains to be seen, but we want to be in that space we want to be playing hard in that space as well. >> All right Dave, last thing I want to ask you about is just career. So, it's interesting, at Vmworld, I kind of look at it in like, "wow, I'm actually, I'm sitting at a panel for Opening Acts, which is done by the VMunderground people the Sunday, day before VMworld really starts, talking about jobs and there's actually three panels, you know, careers, and financial, and some of those things, >> I'm going to be there, so come on by, >> Maybe I should join startin' at 1 o'clock Monday evening, I'm actually participating in a career cafe, talking about people and everything like that, so all that stuff's online if you want to check it out, but you know, right, you said psychology is what you studied but you worked in engineering, you were a systems engineer, and now you do messaging. The hardcore techies, there's always that boundary between the techies and the marketings, but I think it's obvious to our audience when they hear you geeking out on the TPUs and all the things there that you are not just, you're quite knowledgeable when it comes about the technology, and the good technical marketers I find tend to come from that kind of background, but give us a little bit, looking back at where you've been and where you're going, and some of those dynamics. >> Yeah, I was blessed from a really young age with a father who really loved technology. We were building PCs, like back in the eighties, right, when that was a thing, you know, "I built my AMD 386 DX box" >> Have you watched the AMC show, "Halt and Catch Fire," when that was on? >> Yeah, yeah, yeah, so there was that kind of, always interesting to me, and I, with the way my mind works, I can't code to save my life, that's my brother's gift, not mine. But being able to kind of assemble things in my head was kind of always something that stuck in the back. So going through college, I worked as a lab resident as well, working in computer labs and doing that stuff. It's just been, it's been a passion, right? I had the education, was very, you know, that was my family, was very hard on the education stuff. You're going to do this. But being able to follow that passion, a lot of things fell into place with that, it's been a huge blessing. But even in grad school when I was getting my Masters in clinical counseling, I ran my own consulting business as well, just buying and selling hardware. And a lot of what I've done is just I read and ask a ton of questions. I'm out on Twitter, I'm not the brightest bulb in the, of the bunch, but I've learned to ask a lot of questions and the amount of community support in that has gotten me a lot of where I am as well. But yeah, being able to come out on this side, marketing is, like you're saying, it's kind of an anathema to the technical guys, "oh those are the guys that kind of shine the, shine the turd, so to speak," right? But being able to come in and being able to kind of influence the way and make sure that we're technically sound in what we're saying, but you have to translate some of the harder stuff, the more hardcore engineering terms into layman's terms, because not everybody's going to approach that. A CIO with a double E, or an MS in electrical engineering are going on down that road are very few and far between. A lot of these folks have grown up or developed their careers in understanding things, but being able to kind of go in and translate through that, it's been a huge blessing, it's nice. But always following the areas where, networking for me was never a strong point, but jumping in, going, "hey, I'm here to learn," and being willing to learn has been one of the biggest, biggest things I think that's kind of reinforced that career process. >> Yeah, definitely Dave, that intellectual curiosity is something that serves anyone in the tech industry quite well, 'cause, you know, nobody is going to be an expert on everything, and I've spoken to some of the brightest people in the industry, and even they realize nobody can keep up with all of it, so that being able to ask questions, participate, and Dave, thank you so much for helping me, come have this conversation, great as always to have a chat. >> Ah, great to be here Stu, thanks. >> Alright, so be sure to check out the theCUBE.net, which is where all of our content always is, what shows we will be at, all the history of where we've been. This studio is actually in Marlborough, Massachusetts, so not too far outside of Boston, right on the 495 loop, we're going to be doing lot more videos here, myself and Dave Vellante are located here, we have a good team here, so look for more content out of here, and of course our big studio out of Palo Alto, California. So if we can be of help, please feel free to reach out, I'm Stu Miniman, and as always, thanks for watching theCUBE. (upbeat electronic music)

>> Narrator: Live from Washington D.C. It's the Cube, covering AWS Public Sector Summit. Brought to you by Amazon Web Services. >> Welcome back everyone, to the Cube's live coverage of the AWS Public Sector Summit here in our nations capitol. I'm your host Rebecca Knight, along with my cohost John Furrier. We have Allison Robinson joining us, she is the AVP IT operations at Cal Poly University. Thanks so much for coming on the Cube. >> Thank you for having me. >> So, talk about your big announcement yesterday in terms of ground station. This is one of John's favorite topics, so tell us more about what you announced. >> So yesterday there was an announcement that Cal Poly through our digital transformation hub, and that hub exists to do innovated things with the greater good through the public sector and helping with challenges that they're trying to learn more about and solve problems. And so, through that group, we announced the initiative to do cube satellite in connection with ground station at AWS, to be able to help people that use these satellites be able to test these satellites and collect data and share it ultimately, with others. 'Cause there's a problem, they're not expensive satellites but that means you don't have a lot of money to work with. And so to be able to test and make sure your communications are good and the infrastructure is there, is kind of missing in the whole environment. And now, that's going to be solved. >> And you're able to get many more shots and pay as you go, not necessarily have to, as you said, put up your own satellite yourself. >> Exactly, you can put the satellite up. The problem was the infrastructure to communicate back with it. So, the ground station, those antenna are approximately located to AWS regions. So you can now bring the data, process it, store it, analyze it, and then ultimately share it. That, again, being for the public good, we want to make sure the date we're collecting is in the AWS registry, data set registry. So that people can access that information, that's important. >> Allison, talk about the relationship with AWS, how did it get started? I mean your involved with these cool projects like ground station, which I'm a big fan of. 'Cause I think the impact to IOT, just forest fires in California could be a real... >> Allison: Right. >> Saver right there. Just using data, back hauling data for whatever is going to be a great thing. But you got a relationship with AWS, that goes beyond, not just ground station, there's other things going on. Take a minute to explain the relationship with AWS. >> So, the vice president of IT at Cal Poly, Bill Britton, began his position with Cal Poly about two years ago. And took a look at the data center and had to ask the question, do we invest here on prem or do we have to look for something else? And that began the conversation of, we need to do something about our data center, it looks like Amazon has the tools we need to modernize our technical environment. Both in how we work, how people work, our processes and our technical infrastructure. And so, that began the work of, we announced two years ago, I didn't work for Cal Poly yet. They announced there, the President and Bill announced that we were all in. The data center was going to AWS. I happened to be presenting on a different topic, and we connected there, and a year later, we made a connection and I have been at Cal Poly now for a year to help them get to the AWS data center. >> Lot of smart people Cal Poly, I know, I looked at the university. Great computer science, great everything. You guys got a lot of smart people, so what was it like to actually, as this starts to evolve, the progression of the modernization. Take us through where you guys are on progress, what are some of the cool things going on. What's the result of this shift? What are some of the notable highlights? >> It's really exciting, because we really did take an approach of we've got to look at, not just as AWS and a new tool. Which you have to work so differently, in dev ops and agily. We said okay, then we've got to figure out our processes to be able to work that way. We have to change as an organization. So we were more structured around those technical silos. And we became a service management group for like, who do we serve and what are they trying to accomplish? And that's the focus of everything we do. So from idea to service we have a process to handle to that. And AWS, we're all in on their tools too.6 So they completely facilitate that process6. >> You have a lot of stake holders, so you have impact at the student body level, faculty, institution overall.6 >> Right. >> What are some of the game changers that you see? Obviously the ground station, you got great R and D coming in with Amazon. What's the impact? >> The digital transformation hub is part of the IT organization as well. And our community outreach and giving students actual hands on experience to work with the public sector, whether it be law enforcement, or maybe a city trying to deal with a homeless situation. They actually are engaged with professionals and learning about problems and solutions. And in ten weeks, we work on quarters, and our quarters are ten weeks, which align perfectly to exactly how long it takes an engagement with the digital hub to find what's possible in terms of solutions to problems. >> So talk about the students of today. I mean, we hear a lot about them. And I want to hear you, you're teaching them, you're helping to educate this new generation of people who we hope will make huge, great waves in industry, private industry, as well as state, local, and the federal government. >> Allison: Right. >> What do you see as their strengths, their weaknesses, and what are they looking at in terms of building careers? >> You know, they, I really do love working with the students. They are incredible. It makes me wonder sometimes, I don't think I'd get into college now, times have changed. And they really care, they care, that's why the public, being able to work through these to serve the greater good of the public and share that data after actually means so much more to them. Than if it were just a class project, because they want to make a difference. They care about social justice and making sure that we're green and efficient with how we use our earth resources. And so this maps around a lot of the challenges. The homelessness that I mentioned before, and how we've worked with that. Or making sure that we can make cities safer. They care about that deeply. And they have access to a lot of resources. This past fall's incoming class was born in the year 2000. They've never not known a time with computers. They do math homework, they're not reading, they're actually doing homework on their phones. Their very mobilely engaged, very digitally engaged. And we're going to see wonderful things from them, because they think so differently about these things. >> It sounds as though the education that you're providing is very practical, in the sense that you're having your students work with the state and local governments on these issues like homelessness and climate change. Can you talk about some of the projects that their doing? >> So our mantra is learn by doing. And you come in and you are admitted to a major. And you begin working in that major right away. Every student finishes their last quarter with a senior project. And you actually produce an outcome and have something you can talk about, both as the product and the process to get there. I was recently invited to the senior projects showcase for the graphic arts department. And, in common, they all had technology. And some where, one of the students we had just contracted for some software, and thank you so much you helped make the difference with that. So that's neat, when you get to see to make that difference. But even though it's graphic arts, in every way technology was key to what they do. And they have, really, you know students come from some great backgrounds too, where they've had some great access to information and technology and really think differently about it. Engineering students are winning awards and doing really great things. So it's fun to see and be a part of. Great energy. >> What about the culture within your department itself? I mean, you're not only educating the next generation but you're also doing research yourself. Can you talk about, particularly, as a partner, as working so closely with AWS, which has such a famous culture of innovation and of taking risks and tolerating failure, because the more failures you'll have, you'll ultimately get there someday. So can you talk a little bit about the culture within Cal Poly? >> It's hard, because IT people are usually very analytical and there's a right and a wrong. So that sense of it's okay to get it wrong, isn't popular generally. So, that starts with me, I had to get up and say we may not get it right, but rarely do we get it wrong. We might get parts of it wrong, we adjust. It's okay to get it wrong. We've got to figure things out, all of this is new. And as I've been there longer and really work with people through different things, they believe that from me now. There's not judgment. I once worked at a place where it'd go on your permanent record. Well, try and get somebody to try something innovated if you have a problem and it goes on your permanent record. So I don't have that now. >> Rebecca: It'd be a career ender. >> Yeah. >> Bill: Yeah. >> I have a lot of people getting it, and we're trying it. And you can work so fast in the AWS environment, that if it isn't right, blow it away and start over again. >> In some organization you were a renegade if you tried something new. You know, oh my God, don't touch that third rail. >> Allison: Yeah. >> Here, you guys are doing, it's progressive in the sense that you're trying new things. >> Learn by doing is a call to action, but it also gives you that space to try. >> Bill: Yeah, be creative. >> It's learning. >> What's your impression of the show here in DC? Obviously, it's our fourth year covering public sector. I've been following them a couple years earlier, but the first four years covering live broadcasting, reporting. But, besides the growth, what's your takeaway? >> I need to be cloned. (laughter) >> There are so many things happening here. >> You need a digital twin. >> There you go. >> You can solve that, Allison. >> There's going to be a lot of people that say, no don't clone her, don't do it. But there's so much information and the innovation that AWS does. Sometimes it's like exciting to hear, and it's like oh where was that a month ago when we were working on that? So we just have to stay on our toes and we have to keep engaged with AWS and what they're doing and what we can use from them to make our environment better. And move even faster. >> You got to keep, keeping pace is also a hard thing. Because they're introducing so many new things. At amazon. We're very fortunate again in our partnership, actually that does translate into the IT operations organization. That we've been working with them on some services that they do. We can tell them, hey this isn't quite working, and they honestly listen to us. And deliver what they ask on a road map, sometimes sooner than later too. So it's been a great partnership. >> That's interesting, a company that actually delivers on what you ask for. >> Exactly, exactly. And we have scaled, you know it's a small town there's 24,000 students, you have your faculty and staff. So when we try something with them, we have the opportunity for big impacts right away. >> That's awesome, well, congratulations, great work >> Thank you. >> On the DX hubs fascinating ground station. Great projects, students and you guys to play around and help that grow. Because that's going to be a great service. >> Yes, we're excited. We can't wait to get going. >> Rebecca: Thanks for coming the Cube Allison. >> Thank you. >> We will have more of the Cubes live coverage of the AWS Public Sector Summit here in Washington DC. Stay tuned. (upbeat beat music)

>> Narrator: Live from Anaheim, California, it's The CUBE covering Nutanix .NEXT 2019. Brought to you by Nutanix. >> Cameraman: Izzy! >> Welcome back, everyone, to The CUBES's live coverage of Nutanix .NEXT here in Anaheim, California. I'm your host, Rebecca Knight, along with my co-host, John Furrier. We have two guests for this segment, we have Phil Davis, he is the president of Hybrid IT Hewlett Packard Entrerprise. Thanks so much for coming on The CUBE, Phil? >> Great to be here. >> And we have Chris Kaddaras, he is the SVP America's Nutanix. Thank you so much, Chris. >> Right, thanks for having me. >> So, two weeks, this partnership between Nutanix and HPE, two weeks old, newly announced. Chris, I wanna ask you, explain to our viewers a little bit about it and how it came about. What is the partnership? >> Sure, now I think the way the partnership came about was really around customer and partner demand, right? The marketplace was really looking for two great companies to get together and provide a solution for what they wanted to kind of cure their problems. The two components of the partnership effectively is, one component is the Nutanix sales teams are gonna be selling their Nutanix solutions and appliances with a great HPE computing infrastructure involved in that appliance. So, that's the first big group part, and I'll let Phil talk about the second part of the relationship. >> Yeah, and the second part is really around how do we enable a consumption model for our customers? I mean, if you think about what's going on with the public cloud, customers wanna be able to scale up or scale down and kind of pay as they go. And so, HPE has been leading with an offering we call Green Lake. It's a couple-billion-dollar business growing over 50% a year, so it kind of shows you the interest in it, and we also, therefore, offer the Nutanix solution on our infrastructure and then wrap that with a consumption model service that allows customers that flexibility. So, those are the two elements of the partnership. >> So, you're selling Nutanix with your Green Lake. >> Embedded in the Green Lake offering, that's correct. >> And Nutanix has selling Compute with their sales worth. >> Phil: Exactly right. >> Chris: Yeah, so with our DX solution, yeah with HPE Compute. >> Got it. Now, you guys have indirect and direct sales, both sides, channel play, is it a channel partnership or both, can you just explain the go-to market? >> Yeah, and I think that what you'll see is there's just a lot of alignment, a lot of synergy. Both companies are very, very channel friendly. I mean, HPE's a 75 plus year old company and our very first sale as a company went through the channel, right? So, our whole DNA is wired towards the channel. Over 70% of our business goes through the channel. So, what we've really made sure is that we make this very, very easy for the channel to consume and also, be paid and compensated on. So, it flows through all the standard HPE channel compensation and programs that we have in play. So, absolutely, very friendly for the channel. >> Yeah, and I think this will work really well for both channel communities that we have. We have a lot of Nutanix channel partners that have not been, for whatever reason, have not been selling HPE and now, they have a perfect opportunity to sell HPE Compute platforms with our DX appliance. We also have a lot of great channel partners who want a better consumption model where customers are looking to flex up and down. We have not been able to provide that for Nutanix software solutions. So, to adopt Green Lake for some of these partners will be a fantastic offering for their customers. >> Maybe just a dove-tail on that comment, one of the things we've worked really hard in the last year is to make Green Lake more channel friendly. Channel reps tend to get paid as the margin comes in. So, if you spread that out over time, they don't make the same money. So, we've changed the rebate 17% up front for the channel partners, we've simplified the offering, we made it quicker, so we're doing a lot to make Green Lake much easier for our channel partners and a lot of excitement about being able to offer Nutanix with Green Lake as well. >> What's the timing on the channel rollout? Is it rolling out now? Is it instantly growing out? Is there timing on-- >> Phil: Instantly. >> Instantly? >> So, we've already briefed the channel, we are making it available, we're providing all the quotes, we have a ton of material available online through our online portals and tools for the channel partners, we have FAQs, we have marketing materials, we have, actually, letters already built up for the channel. So, it's now. >> So, I gotta ask the hard question here because I think one of the things I see that's really awesome is the channel's gonna love this because Nutanix has a channel generated opportunity. Their challenge in that opportunity is when they do a POC, they usually win the business. That's kind of a direct sales model that's favored Nutanix for their success. This is gonna bring a lot of mojo to the channel bringing HPE and Nutanix together for this unique solution. I'm sure the reaction's been positive. Are they seeing an up-step in more POCs and more action with customers? >> Phil: You wanna take that? >> Yeah, we're seeing a lot, actually. So, I was just there actually reviewing my team yesterday. We have a list of now starting to get towards 100 customers that we think we can align with together, right? And multiple go to markets. We have Green Lake opportunities, we have DX opportunities, which is Nutanix on HPE. We also have a lot of opportunities around Nutanix software only on HPE Compute that a lot of customers wanna consume as well in a different way. So, we're seeing that really start to scale. We haven't done the first POC of DX because it hasn't released to the market yet, right? We are doing POCs on software only on HPE servers, but the DX solution will be releasing in the next few months. So Phil, I know the HPE channel pretty well and they love services, wrapping services around an offering. Can you talk about how this impacts from the services side because I gotta be looking at my chops if I'm a dealer partner because I can bring this new solution in and I can wrap cloud-like capabilities around it. >> Yeah, and you look at a lot of our partners, the hardware-only business is getting pressure. And so, a lot of our partners are doing exactly what you just described. They're trying to move more and more into services. And you're right, there's a whole sweep of services the partners can wrap around this. Everything from advisory, upfront, because all of these workloads run on some sort of legacy environment. So, when they do bring in a hyperconverged, they need to move the workloads. So partners can help with that, supporting maintenance, implementation, all the way through to kind of day-to-day break fix. So, there's a range on services. Obviously, HPE has a pretty big services capability. We make those available through our channel partner as well, so if they wanna sell to HPE services they can do that, or if they wanna deliver 'em themselves, they can do that as well. >> I wanna ask you about the customers. You made this point on main stage that you, sort of, likened back to the Henry Ford quote where you can have any color, as long as it's black and the current marketplace was anything you want as long as it's in my stack, and this is how we're gonna do it. So, giving them more choice, more flexibility, what are you hearing so far? What was the problem in terms of their workload and why things were stiffeled or stunted, and now what do you hope this is going to do? >> Well, as I mentioned on main stage, everybody wants to make it easy to get on to their stack and really, really hard to move off of their stack, right? Whether you're a public cloud company, you want all your microservices, you want all the data trapped there, so it's not easy to move and some of our joint competitors are actually trying to lock you into the complete top-down stack. So, the feedback, so far, from customers and partners has been very, very, very positive because one of the things, I've been in the industry 29 years. One of the things that I can tell you is no one company is gonna out-innovate the entire industry. And so, what customers want is to be able to pick and choose the solutions that best meet their needs. And that's really what this partnership, I think, really embodies is the ability to give customers choice at multiple levels within that stack. Choice in the public cloud, choice on prem, choice of hypervisors, and that's really resonating. >> Yeah, and that's really Nutanix's design point, right? Is around choice, right? Choice at every level of a stack that you can have. And this provides us with the biggest choice in the marketplace at this point and time that was missing from our portfolio. The other piece that you mentioned that I'd like to point out is that the thing that a lot of people haven't been talking about is the services component. You know, Nutanix is a great company, we've grown a lot. But one place that we haven't grown to an extent is in the services side. We have a small services organization that really helps our customers, but we really need a services organization that can help our customers transform. And help our customers through a transformation of their underlying infrastructure and reduce the risk of change. And this HPE relationship will help us do that as well. >> And the other thing, too, that's interesting with Cloud and you guys are in the middle of demodernizing the data center, HPE's been there forever in the data center, is the private cloud has shown that the data center's still relevant. However, if you start going cloud-based stuff, integration's huge. So integrating, not just packaging our solutions, customers need to integrate all this stuff. This has been a key part of Nutanix and HPE. How do you guys see this going forward from an integration standpoint? Because on the product side, it's gotta integrate, and then in the customer environment you mentioned the consumption piece. Can you guys just expand on what that means? >> Sure. Yeah, we saw Dheeraj's presentation this morning, right? And Sunil's, our entire design point is how do we make everything invisible, right? How do we make those integration points invisible? Now, we all know that there's a traditional architecture you need to migrate from to take advantage of some of these things. And that's where the risk is, how do you get from A to B into these environments? As I mentioned, we do have a services organization that helps there, but we could use, now we have one of the largest partners in the industry that could help us do that. I think that's a key component. We will always try to innovate being Nutanix, we will always try to innovate in software, right? Let's try to figure out how we can make this so much easier, move it up the stack to make sure this is the easiest thing to migrate and have choice for customers. >> Yeah, and I think, maybe, just to add to that, if you think about it from a customer view in, right? A lot of customers moved a lot of things very quickly to the public cloud and the public cloud will continue to grow fast, but they're also learning some things. It's not quite as cheap as they thought it was gonna be, like twice as expensive. Moving data around is very expensive. The public cloud is charging you to get your own data back out. Data sovereignty matters a lot more than it used to with things like GDPR in Europe. More and more of the data's getting created at the edge. It's not in the cloud or the data center. And so, what we're seeing is customers are now thinking about things as you mentioned, we're kind of hybrid, and they're talking about the right mix. What's the right mix of public? What's the right mix of private? Where should the data live? And that's a tough story and that's a tough journey for them to go on, so they want help up front with the advisory services, they want help in being able to architect that, implement it, and then, in many cases, even kind of run that. And with nearly 25,000 services professionals around the globe, we have a unique footprint to help customers along that journey. >> It's an interesting deal, it's very, I think, gonna be pretty big. So, congratulations. >> Phil: Thank you. >> It was great having you both on The Cube, Phil and Chris. >> Thank you very much, thanks. >> Thanks for having us. >> I'm Rebecca Knight for John Furrier, we will have so much more from Nutanix .NEXT here in Anaheim, California, so stay with us. (electronic dance music)