(upbeat music) >> Welcome to theCube's coverage of AWS Storage Day. We're here with a couple of AWS product experts. Covering AWS's migration and transfer services, Randy Boutin is the general manager of AWS DataSync, and Mat Matthews, GM of AWS Transfer Family. Guys, good to see you again. Thanks for coming on. >> Dave, thanks. >> So look, we saw during the pandemic, the acceleration to cloud migration. We've tracked that, we've quantified that. What's driving that today? >> Yeah, so Dave, great to be back here. Saw you last year at Storage Day. >> Nice to be in studio too, isn't it? Thanks, guys, for coming in. >> We've conquered COVID. >> So yeah, I mean, this is a great question. I think digital transformation is really what's driving a lot of the focus right now from companies, and it's really not about just driving down costs. It's also about what are the opportunities available once you get into the cloud in terms of, what does that unlock in terms of innovation? So companies are focused on the usual things, optimizing costs, but ensuring they have the right security and agility. You know, a lot has happened over the last year, and companies need to be able to react, right? They need to be able to react quickly, so cloud gives them a lot of these capabilities, but the real benefit that we see is that once your data's in the cloud, it opens up the power of the cloud for analytics, for new application development, and things of that sort, so what we're seeing is that companies are really just focused on understanding cloud migration strategy, and how they can get their data there, and then use that to unlock that data for the value. >> I mean, if I've said it once, I've said it 100 times, if you weren't a digital business during the pandemic, you were out of business. You know, migration historically is a bad word in IT. Your CIOs see it and go, "Ugh." So what's the playbook for taking years of data on-prem, and moving it into the cloud? What are you seeing as best practice there? >> Yeah, so as you said, the migration historically has been painful, right? And it's a daunting task for any business or any IT executive, but fortunately, AWS has a broad suite of capabilities to help enable these migrations. And by that, I mean, we have tools to help you understand your existing on-prem workloads, understand what services in the AWS offering align to those needs, but also help you estimate the cost, right? Cost is a big part of this move. We can help you estimate that cost, and predict that cost, and then use tools like DataSync to help you move that data when that time comes. >> So you're saying you help predict the cost of the migration, or the cost of running in the cloud? >> Running in the cloud, right. Yeah, we can help estimate the run time. Based on the performance that we assess on-prem, we can then project that into a cloud service, and estimate that cost. >> So can you guys explain DataSync? Sometimes I get confused, DataSync, what's the difference between DataSync and Storage Gateway? And I want to get into when we should use each, but let's start there if we could. >> Yeah, sure, I'll take that. So Storage Gateway is primarily a means for a customer to access their data in the cloud from on-prem. All right, so if you have an application that you want to keep on-prem, you're not ready yet to migrate that application to the cloud, Gateway is a strong solution, because you can move a lot of that data, a lot of your cold or long tail data into something like S3 or EFS, but still access it from your on-prem location. DataSync's all about data movement, so if you need to move your data from A to B, DataSync is your optimized solution to do that. >> Are you finding that people, that's ideally a one time move, or is it actually, sometimes you're seeing customers do it more? Again, moving data, if I don't- Move as much data as you need to, but no more, to paraphrase Einstein. >> What we're seeing in DataSync is that customers do use DataSync for their initial migration. They'll also, as Matt was mentioning earlier, once you get your data into the cloud, that flywheel of potential starts to take hold, and customers want to ultimately move that data within the cloud to optimize its value. So you might move from service to service. You might move from EFS to S3, et cetera, to enable the cloud flywheel to benefit you. DataSync does that as well, so customers use us to initially migrate, they use us to move within the cloud, and also we just recently announced service for other clouds, so you can actually bring data in now from Google and Azure as well. >> Oh, how convenient. So okay, so that's cool. So you helped us understand the use cases, but can we dig one more layer, like what protocols are supported? I'm trying to understand really the right fit for the right job. >> Yeah, so that's really important. So for transfer specifically, one of the things that we see with customers is you've got obviously a lot of internal data within your company, but today it's a very highly interconnected world, so companies deal with lots of business partners, and historically they've used, there's a big prevalence of using file transfer to exchange data with business partners, and as you can imagine, there's a lot of value in that data, right? Sometimes it's purchase orders, inventory data from suppliers, or things like that. So historically customers have had protocols like SFTP or FTP to help them interface with or exchange data or files with external partners. So for transfer, that's what we focus on is helping customers exchange data over those existing protocols that they've used for many years. And the real focus is it's one thing to migrate your own data into the cloud, but you can't force thousands or tens of thousands sometimes of partners to also work in a different way to get you their data, so we want to make that very seamless for customers using the same exact protocols like SFTP that they've used for years. We just announced AS2 protocol, which is very heavily used in supply chains to exchange inventory and information across multi-tiers of partners, and things of that nature. So we're really focused on letting customers not have to impact their partners, and how they work and how they exchange, but also take advantage of the data, so get that data into the cloud so they can immediately unlock the value with analytics. >> So AS2 is specifically in the context of supply chain, and I'm presuming it's secure, and kind of governed, and safe. Can you explain that a little bit? >> Yeah, so AS2 has a lot of really interesting features for transactional type of exchanges, so it has signing and encryption built in, and also has notification so you can basically say, "Hey, I sent you this purchase order," and to prove that you received it, it has capability called non-repudiation, which means it's actually a legal transaction. So those things are very important in transactional type of exchanges, and allows customers in supply chains, whether it's vendors dealing with their suppliers, or transportation partners, or things like that to leverage file transfer for those types of exchanges. >> So encryption, providence of transactions, am I correct, without having to use the blockchain, and all the overhead associated with that? >> It's got some built in capabilities. >> I mean, I love blockchain, but there's drawbacks. >> Exactly, and that's why it's been popular. >> That's really interesting, 'cause Andy Jassy one day, I was on a phone call with him and John Furrier, and we were talking up crypto and blockchain. He said, "Well, why do, explain to me." You know Jassy, right? He always wants to go deeper. "Explain why I can't do this with some other approach." And so I think he was recognizing some of the drawbacks. So that's kind of a cool thing, and it leads me- We're running this obviously today, August 10th. Yesterday we had our Supercloud event in Palo Alto on August 9th, and it's all about the ecosystem. One of the observations we made about the 2020s is the cloud is totally different now. People are building value on top of the infrastructure that you guys have built out over the last 15 years. And so once an organization's data gets into the cloud, how does it affect, and it relates to AS2 somewhat, how does it affect the workflows in terms of interacting with external partners, and other ecosystem players that are also in the cloud? >> Yeah, great, yeah, again, we want to try and not have to affect those workflows, take them as they are as much as possible, get the data exchange working. One of the things that we focus on a lot is, how do you process this data once it comes in? Every company has governance requirements, security requirements, and things like that, so they usually have a set of things that they need to automate and orchestrate for the data as it's coming in, and a lot of these companies use something called Managed File Transfer Solutions that allow them to automate and orchestrate those things. We also see that many times this is very customer specific, so a bank might have a certain set of processes they have to follow, and it needs to be customized. As you know, AWS is a great solution for building custom solutions, and actually today, we're just announcing a new set of of partners in a program called the Service Delivery Program with AWS Transfer Family that allows customers to work with partners that are very well versed in transfer family and related services to help build a very specific solution that allows them to build that automation orchestration, and keep their partners kind of unaware that they're interfacing in a different way. >> And once this data is in the cloud, or actually, maybe stays on-prem in some cases, but it basically plugs in to the AWS services portfolio, the whole security model, the governance model, shared responsibility comes in, is that right? It's all, sort of all in there? >> Yeah, that's right, that's exactly right, and we're working with it's all about the customer's needs, and making sure that their investment in AWS doesn't disrupt their existing workflows and their relationships with their customers and their partners, and that's exactly what Matt's been describing is we're taking a close look at how we can extend the value of AWS, integrate into our customer's workflows, and bring that value to them with minimal investment or disruption. >> So follow up on that. So I love that, because less disruption means it's easier, less friction, and I think of like, trying to think of examples. Think about data de-duplication like purpose-built backup appliances, right? Data domain won that battle, because they could just plug right in. Avamar, they were trying to get you to redo everything, okay, and so we saw that movie play out. At the same time, I've talked to CIOs that say, "I love that, but the cloud opens up all these cool new opportunities for me to change my operating model." So are you seeing that as well? Where okay, we make it easy to get in. We're not disrupting workflows, and then once they get in, they say, "Well if we did it this way, we'd take out a bunch of costs. We'd accelerate our business." What's that dynamic like? >> Exactly that, right. So that moved to the Cloud Continuum. We don't think it's going to be binary. There's always going to be something on-prem. We accept that, but there's a continuum there, so day one, they'll migrate a portion of that workload into the cloud, start to extract and see value there, but then they'll continue, as you said, they'll continue to see opportunities. With all of the various capabilities that AWS has to offer, all the value that represents, they'll start to see that opportunity, and then start to engage and consume more of those features over time. >> Great, all right, give us the bumper sticker. What's next in transfer services from your perspectives? >> Yeah, so we're obviously always going to listen to our customers, that's our focus. >> You guys say that a lot. (all laughing) We say it a lot. But yeah, so we're focused on helping customers again increase that level of automation orchestration, again that suite of capability, generally, in our industry, known as managed file transfer, when a file comes in, it needs to get maybe encrypted, or decrypted, or compressed, or decompressed, scanned for viruses, those kind of capabilities, make that easier for customers. If you remember last year at Storage Day, we announced a low code workflow framework that allows customers to kind of build those steps. We're continuing to add built-in capabilities to that so customers can easily just say, "Okay, I want these set of activities to happen when files come in and out." So that's really what's next for us. >> All right, Randy, we'll give you the last word. Bring us home. >> I'm going to surprise you with the customer theme. >> Oh, great, love it. >> Yeah, so we're listening to customers, and what they're asking for our support for more sources, so we'll be adding support for more cloud sources, more on-prem sources, and giving the customers more options, also performance and usability, right? So we want to make it easier, as the enterprise continues to consume the cloud, we want to make DataSync and the movement of their data as easy as possible. >> I've always said it starts with the data. S3, that was the first service, and the other thing I've said a lot is the cloud is expanding. We're seeing connections to on-prem. We're seeing connections out to the edge. It's just becoming this massive global system, as Werner Vogels talks about all the time. Thanks, guys, really appreciate it. >> Dave, thank you very much. >> Thanks, Dave. >> All right, keep it right there for more coverage of AWS Storage Day 2022. You're watching theCube. (upbeat music)

>>We'll go back to the queue. It's continuous coverage of AWS storage day. We're here in Seattle home with the Mariners home, with the Seahawks home of the Seattle storm. If you're a w NBA fan your cloud migration, according to our surveys and the ETR data that we use last year was number two initiative for it. Practitioners behind security. Welcome to this power panel on migration and transfer services. And I'm joined now by Matt Matthews. Who's the general manager of AWS transfer a family of services sitting. Roy is the GM of the snow family. And Randy boudin is the general manager of AWS data sync, gents. Welcome to good to see you. Thank you. So, Matt, you heard my narrative upfront, obviously it's top of mind for it. Pros, what are you seeing in the marketplace? >>Yeah, uh, certainly, um, many customers are currently executing on data migration strategies, uh, to the cloud. And AWS has been a primary choice for cloud storage for 15 years. Right. Um, but we still see many customers are evaluating, um, how to do their cloud migration strategies. And they're looking for, you know, um, uh, understanding what services can help them with those migrations. >>So said, well, why now? I mean, a lot of people might be feeling, you know, you got, you've got a hesitancy of taking a vaccine. What about hesitancy making a move? Maybe the best move is no movable. W why now? Why does it make sense? >>So AWS offers compelling, uh, cost savings to customers. I think with our global footprint that our 11 nines of durability are fully managed services. You're really getting the centralization benefits for the cloud, like all the resiliency and durability. And then besides that you are unlocking the on-prem data center and data store costs as well. So it's like a dual prong cost saving on both ends >>Follow up on that. If I may, I mean, again, the data was very clear cloud migration, top priority F for a lot of reasons, but at the same time migration, as you know, it's almost like a dirty word sometimes in it. So, so where do people even start? I mean, they've got so much data to migrate. How can they even handle >>That? Yeah. I'd recommend, uh, customers look at their cool and cold data. Like if they look at their backups and archives and they have not been used for long, I mean, it doesn't make sense to kind of keep them on prem, look at how you can move those and migrate those first and then slowly work your way up into like warm data and then hot data. >>Okay, great. Uh, so Randy, we know about the snow family of products. Of course, everybody's familiar with that, but what about online data migration? What can you tell us there? What's the, what are customers thinking >>About? Sure. So as you know, for many their journey to the cloud starts with data migration, right? That's right. So if you're, if you're starting that journey with, uh, an offline movement, you look to the snow family of products. If you, if you're looking for online, that's when you turn to data, sync data thinks that online data, movement, service data is it makes it fast and easy to move your data into AWS. The customers >>Figure out which services to use. Do you, how do you advise them on that? Or is it sort of word of mouth, peer to peer? How do they figure it out that that's squint through that? Yeah, >>So it comes down to a combination of things. So first is the amount of available bandwidth that you have, the amount of data that you're looking to move and the timeframe you have in which to do that. Right. So if you have a, high-speed say gigabit, uh, uh, network, uh, you can move data very quickly using data sync. If, if you have a slower network or perhaps you don't want to utilize your existing network for this purpose, then the snow family of products makes a lot of sense. Call said, that's it? Call center. That's >>My answer. Yeah, there you go. Oh, you'll >>Joke. Right. See Tam that's Chevy truck access method. You put it right on there and break it over. How about, you know, Matt, I wonder if we could talk maybe about some, some customer examples, any, any favorites that you see are ones that stand out in various industries? >>Yeah. So one of the things we're seeing is certainly getting your data to the cloud is, is important, but also customers want to migrate their applications to the cloud. And when they, when they do that, they, uh, the many applications still need ongoing data transfers from third parties, from ex partners and customers and, and whatnot. So, great example of this is, uh, FINRA and their partnership with AWS. So a FINRA is the single largest, um, uh, regulatory body for securities in the U S and they take in 335 billion market events per day, over 600,000 of their member brokers, registered brokers. So, uh, they use, um, AWS transfer family, uh, secure file transfers, uh, to get that data in an aggregated in, in S3, so they can, um, analyze it and, and, uh, really kind of, uh, understand that data so they can protect investors. So that's, that's a great example. >>So it's not just seeding the cloud, right? It's the ongoing population of it. How about, I mean, how do you guys see this shaping up the future? We all talk about storage silos. I see this as, you know, the cloud is in some ways a silo Buster. Okay. We've got all this data in the cloud now, but you know, you can not apply machine learning. There are other tooling, so what's the north star here. >>Yeah. It's really the north star of getting, you know, we want to unlock, uh, not only get the data in the cloud, but actually use it to unlock the benefits of the cloud has to offer. Right. That's really what you're getting at, aggregating all that data, uh, and using the power of the cloud to really, um, you know, harness that power to analyze the data. It's >>A big, big challenge that customers have. I mean, you guys are obsessed listening to customers, you know, w what kinds of things do you see in the future? Sid and Randy, maybe, maybe see if you can start, >>Uh, I'll start with the I'll kind of dovetail, on example, a Matthews, uh, I'll talk about a customer join, who moved 3.4 petabytes of data to the cloud joined was a streaming service provider out of Germany. They had prohibitive on-prem costs. They saved 500 K per year by moving to the cloud. And by moving to the cloud, they get much more of the data by being able to fine tune their content to local audiences and be more reactive and quicker, a reaction to business changes. So centralizing in the cloud had its benefits of access, flexibility, agility, and faster innovation, and faster time to market. Anything you'd add, right. >>Yeah, sure. So we have a customer Takara bio they're a biotech company. Uh, they're working with genome sequencing, right? So data rich information coming out of those sequencers, they're collecting and analyzing this data daily and sending it up into AWS for analysis, um, and, uh, by using data sync in order to do that, they've improved their data transfer rate by three times. And they've reduced their, uh, overhead six by 66% in terms of their process. >>Guys get, must be blown away by this. I mean, we've all sort of lived in this, so I'm prem world and you sort of lay it out infrastructure, and then you go onto the next one, but the use cases are so diverse. The industry, examples. Matt will give you the last >>Word here. Yeah, no, w w what are we looking to do? You know, we, we always want to listen to our customers, uh, but you know, collectively our, our services and working across other services, AWS, we really, uh, want to help customers not only move their data in the crowd, but also unlock the power of that data. And really, um, you know, uh, we think there's a big opportunity across their migration and transfer services to help customers choose, choose the right service, uh, based on their, where they are in their cloud migration, uh, and, and all the different things they're dealing with. >>I've said a number of times the next 10 years is not going to be like the last 10 years. It's like the cloud is growing up. You know, it's out of the infancy stage. Maybe it's an adolescent. So I don't really know exactly, but guys, thanks so much for coming to the cube and sharing your insights and information. Appreciate it. And thank you for watching everybody keep it right there. More great content from AWS storage day in Seattle.

>>Mhm >>Hello and welcome to today's session of the 2021 AWS Global Public Sector Partner Awards And I'm delighted to introduce our next guests. They are chris Saks Ceo of think stack and Michael Matthews President Ceo at mutual Credit Union. I'm your host for the cube Natalie. Ehrlich of course. And we're going to highlight the most impactful nonprofit partner award. Thank you gentlemen for joining the program. >>Thank you so much for having us. >>Terrific. Well delighted for you to be here. And Michael, I'd love to start with you. How did you figure out that cloud technology was critical to the future of mutual credit union? >>It's kind of by chance, Natalie, we're sitting down, we're looking at uh, racks of equipment in our I. T. Room and trying to keep everything up to date, um software updated, become a full time job and all of my staff and sat around and it come to a point where we were spending more time keeping upgrades, keeping servers upgraded. And we asked we reached out the things that they were a network provider at the time and we said, hey, whatever, what are our options? And they came back with several options and one of them was a W. S. And we explored it and uh we've not looked back. >>Terrific. Well, can you explain in further detail how you identified some of the gaps and what stood out to you about think stack, how this uh collaboration happened specifically? >>Well, some of the major gaps that you have is, you know, we're in Vicksburg Mississippi and I would say it's probably not the I. T mecca of the United States and staffing. What was a huge requirement for us if you're gonna make a move such as this, you've got to have the staffing and then along with the staffing is okay if you go out and we hire all these individuals to help help with this journey, are they going to become bored and you know, if we uh personally, if if I asked think stack, they would say, oh yes, don't do that hire us, but that's their job there, there there are parker vendor and so we went out, we asked other vendors that we use and what are the chances of us doing this and it was slim to none. And this type of technology you want, somebody who you can call and and all honesty, I want to be able to call chris and say chris, I'm having a problem versus, you know, one of my team called me and say we're having a problem, I'd rather call it and I love the vendor relationship. It has worked out well. Our major gaps in staffing though, Natalie >>what about staffing? >>That was our major gap. >>Oh God, it got it. Well, chris let's move on to you now. I'd love it if you could explain, you know, in some detail for our audience about the methodology of your company and also how you help your clients visualize their transformation processes. >>Yeah, for sure. Thanks Natalie. So we work with credit unions around the country and many of them are facing similar challenges to Michael at mutual. And in addition to staffing, they're often challenged with just the uncertain future of technology and that can include things like hurricanes, wildfires, various different disasters, pandemics and having to work remotely. But it also includes all of the opportunities that exist in transformative technologies for credit union. They need to keep pace with organizations like Robin Hood and stash and some of these other organizations that are providing cutting edge mobile apps and technology to their customers. And so how do you as an organization generally, that's a small nonprofit organization. How do you build the technology that will allow you to have a foundation to respond and react to whatever the world happens to throw actually, be that an opportunity to take advantage of for growth or some kind of risk from a cyber attack to a natural disaster. So what we try to do with our clients is take a very human centered approach first. And the idea behind that is to not walk in the door and talk about all the wonderful benefits of AWS or any other particular technology, but rather look at What do you expect. So if you take Michael, for example, you know, sitting down with him and trying to look out 10 years, what do you expect the industry to look like? What do you expect your organization to look like in? What goals do you have as a credit? You need to take advantage of those opportunities and to mitigate those risks. Once you identify those business needs, we can start looking at the humans that are involved in that experience. And so that would obviously be the employees and partners and vendors that support and make up the team at the credit union. And then obviously it's their current members and then any other members that they want to attract. And so you have to look at both sides of this. How how do you work securely efficiently? Um, as an employee on the flip side, how do you serve your members as well as you can serve them with cutting edge technology with technology that's always up and available. And then obviously with, with utmost security. So as we identify and build that picture, uh, we we generally do that with stick figures Natalie so we try to go in and and you know take um different personas and we use journey mapping and we use strategic foresight and various other exercise that help us uh literally paint a picture. Um and then from there we kind of back into that and say okay in order for you to accomplish these things into Have the organization that you want to have the next 10 years, what is your technology foundation and footprint need to look like to support that. And that's where we start to then back into that design which typically would include some type of public cloud services like AWS among other technologies from a cyber security perspective to build out that foundation and then allow them To respond and react to whatever the world throws at him over the next 10 years. >>Terrific. Well Michael would love to get your insight. How did you experience that human centered design focus, that think stack uh you know, is known for >>I think that's what says things take apart. You know, we there's numerous vendors you can go direct, there's there's plenty of software, there's plenty of technology out there you can buy. And as a credit union we can go out, we can just about get anything we wanted. But when we have a problem that we're trying to solve, it's not about that, it's about sitting down with chris his team and saying chris this this is a problem. We recently had one in password management, but we just this is a problem we're having. How do we solve this problem? And so the focus is not about trying to sell you another software. The focus is about solving the problem and having your staff and your team work more efficiently and effectively at their task. At the end of the day, you know, we're not arty people were in the financial service business. We rely on the solutions that we have to to help us do our jobs better and serve our members more effectively. >>Yeah, well, chris uh, you know, from your perspective, obviously human centered designed a really big component of your business, but what other key feature set your business apart from the competitive landscape? >>So I think the human centered design bleeds into another area that we really pride ourselves on, which is which is education and what I will call plain talk. So again, as Michael said, these organizations are our financial services, they're not technology experts, so you need to be able to communicate to those teams, those boards of directors, executive teams in a way that they can understand, and it can be uh somewhat difficult to talk about complex technical problems, um but when you boil it down back to that experience level, or you boil it down to a picture, it becomes a little easier to talk about. And what we want to be able to do as a partner is make sure our clients have confidence in the services or the products that they're purchasing, that they understand. How is this investment going to impact our credit union? How is this going to impact our members? And is this the right investment? It investments are, are significant. So we need to make sure that both parties understand the expectations of that investment and why they're doing that. So we take a lot of pride in the education and then probably the biggest piece uh and you know, it's one of those things that can be unappreciated, but its cybersecurity building, our infrastructure's with the tools and the processes and and the techniques so that everyone stays secure. I can tell you that there is nothing that would derail a digital transformation of an organization faster than a breach. So it's very important for us to make sure that those organizations, that everything that we do as fun as it is to talk about transformational technology equally as important that everything stays secure as we do it. >>Yeah. Well, excellent point. Certainly cybersecurity going to be a top uh topic for 2021 and beyond. Now, Michael, I'd like to move to you um what were the expected and unexpected business outcomes as a result of this partnership? >>Well, now we we we expected to have issues in the transition, which we really didn't um, I'll be honest with you, we we expected to have failures of servers. We expected stuff not to work because we were told by some of our other vendors that this will not work in a W S. Um and we were very surprised that most everything worked on AWS and it worked even better. Um some of the unexpected. So one of the main drivers of us moving to AWS was, I told you we had were limited on Rackspace I T room is when we want to implement a new service today, everything requires its own server. So everything needs an independent service, virtual server or physical server. We did not know how fast that could be done. So we would send a ticket in uh and we would say, hey, we need a new server here. The specs we're putting on this vendor, this is our time frame and we will get an email back the next morning. The servers ready to go where before? We weren't we didn't have that. That that was not an option. The main delay for new projects was to build up time and we weren't expecting that speech. No longer was that we all we expected that hey, we're not in a rush, but it'll be at least three months. And so now the team has to be ready to go as soon as you send the request in that we need this server is done uh and its speed up, speed up our time from uh, the idea our concept to going live with projects and we weren't that was something we had to get adjusted to. >>Yeah. And following up on that. What were some of the rational as well as the emotional impacts as a result of this collaboration? >>All right too. Two things and I don't know if they meet their, meet your that answer your question directly. But so one item we had in in a call, it's been several weeks back is when is the last time that anyone had to call it? Said, hey, I'm not working. My my can't access the server or I can complete dysfunction. And it's not been that way. We we've seen significantly improved up time, not only externally for our members who are logging in to do home banking or any other, any other feature, but internally for our staff we saw and I think it's just the entire transformation just made our company more resilient. What that was. I was as the metric we were seeing fewer instances of downtime. If we have downtown now, it's a power. We had an ice storm here in Mississippi, which is rare. Uh and we were down for a day. Um and if you lose internet today at any business you're down um The emotional side of I tell you, and it's been several years back on July four, we had a major major failure and our entire network was down and we this is prior to us moving to AWS and I'll just tell you I go home at night, this is the peace of mind that you can't put a dollar value on. I go home at night. And the last thing I'm worried about is my I. T. Network. I'm not worried about up time, I'm not worried about members, you know, going on facebook or any other social media and saying hey we can't we can't access your site what's going on and we don't have that anymore. And you know, I'm sure we could have had it any other way. But I leave that to the process of us moving from an in house holding everything on premise to moving to AWS, not only did it want to improve the results of those servers were able to back up to do different things, but it is to improve the overall working, working the functionality of our network. And I like I said I you can't put a dollar on this peace of mind and that is something I don't think there's any metric out there. You can measure, you can't measure that, but you know me and my team, we see it all the time. So >>Yeah, I agree, a peace of mind is certainly a priceless now Chris Let's move to you if you could outline to our audience some of the solutions that you provide, some of your other clients as well. Just give us a fuller picture of the services that you provide. Let's perhaps talk about, you know, 24/7 socks um services as well as data loss prevention or anything else that you think would be of interest to our audience? >>Yeah, for sure. So so obviously we I like to think of us like we design so we come in and we like to help you design and and figure out what your network needs to look like. That's not only your server and production network but also routing, switching. So Land Win S T Win various other networking projects equally. It's important that you can access the cloud as it is to move to the cloud, help with with productivity suite collaboration tools. Um and then finally, cyber security is a big part of that as well. So we try to come in and and look at all those things on the cybersecurity side. Very similar concept of what we do on the, on the cloud side, which is well design the tools and the infrastructure on the perimeter of the network, the configuration of any cloud environments, um such that they're secure and appropriate for your organization. Uh look at active directory or whatever organizational user management system you have to be using, implement those tools. Um and then as you mentioned, Natalie, we have a 24 x seven socks um with analysts watching that um that are all things that employees watching that board responding and reacting um using our our sin platform. And then we also have a 24 by seven uh network operations center or knocked. Um that is managing both the on site uh tools and network as well as any cloud uh networks that that they may have, keeping them up to date, doing all the routine maintenance, I will say from a cyber security perspective while it's not called the sock, the knock is just as important for cybersecurity as is the knock because we see that many cybersecurity attacks are often just taking advantage of systems that are not kept up to date. So the knock and that preventative maintenance is so important. So we do that for a lot of our clients. Some people pick and choose certain features. Some people use all of our services. >>Yeah. Terrific. Is that what you mean by security that's made to order? >>Yeah, exactly. Um you know, I think that's true of all technology. Um the biggest thing that we can do his look at the systems that you have during that design phase, we not only look at what technology should be should you be using, but also we take an assessment of your current team, What talent does your team have and where can we fill gaps if you have people that are doing security really well or you're doing preventative maintenance or some of these features? Uh Certainly you should keep that in house and we'll try to build services around those individuals that you have so that you're utilizing your talent to the best of your abilities and we're really fitting in um where you need us. >>Yeah. Terrific. Well, um you know, Michael, I'd like to shift to you now. What do you think will be the broader impact, you know, for the credit union industry? If others are not, you know, adopting the same kind of technologies um you know, to secure their cloud strategies. Mhm. >>I think whether credit unions want to or not, they're moving to the cloud. Um Most of our newest vendors are all cloud based. Um And so yes, he's either do it now or do it later. Which one do you want to be? And I do think that you're going to see more and more larger credit unions begin to move and it's scalable. It's more up time. It's easier to back up. A lot of people are hesitant. They don't want to take their information and move it out of town. They try to find a local data center are somewhere secure. And, and we looked at is what's the difference? You know, we, we we don't have latency issues with internet and fiber today. And so what is the difference of movement out of town and move to AWS by moving out of town? I still on the servers. I still leased the space. I still have to go over there. We have to have somebody there at all the time. And I'll be honest with you, I look at AWS as a trusted partner versus trying someone and then, and then it's not working locally and there's a lot of data centers you can, you can move to um I think I think it's going to come to the industry one way or the other. >>Yeah. Well, Terrific. Do you have any insight or you know, perhaps advice for another credit union who will, you know, like to take the next step? But, you know, as you mentioned, maybe a bit hesitant, >>I think doing your homework on it and looking at it as a, as a viable option is the first step. I know when I took it to my board and I talked about this um with chris and several people have so we we we talk about these things like the cloud, like it's this magical space and and our data is out there in Netherland and who knows where our data is. But when you break it down, you say, I have a East Coast data center and I have a West Coast data center. These are physical spaces where my dad is higher is held. Um I think it makes people think about a little differently. And and so when when you're if you're thinking about moving, if your if your in house today and you're thinking about how I'm gonna start outsourcing evaluate the cost, what are your ongoing cost, You know, who's gonna service you, Who's going to provide that service? And we've looked at other vendors over the years and I'll tell you, chris and his team have something unique that I found. Um I found very desirable in our situation is at our size and we're just under $300 million credit union. I don't think we have major projects that are too complicated to chris we're still, we're one of his better customers. I assume, chris me tell you something different in a minute, but we're not just a number, so I wouldn't go into a cube. You know, everybody knows each other. We're both small enough companies to where they're getting a lot bigger than we are now, but they're both small of companies where we're still, we we mean something to them, they care about moving to start versus just checking the box off. And so that's that's been our journey so far. Mhm. >>Yeah. Well, um, so, chris, uh, you know, first I want to know if Michael is one of your better customers, but uh, you know, really what I would I would really like to know is um, you know, what is your like, big sales pitch to? You know, as I mentioned to Michael, just some of those companies that are a little bit hesitant, a little bit on the edge. >>Michael is our best client of course because he's here doing this interview with us. No, um, you know, that that's something for us that are those, those human connections are, are, are so important and we do get very invested with any of the clients that we work with. But, um, in, in terms of the industry, I think Michael started to say at the beginning, which is, you're already there. We hear a lot of times from folks that they, I can't move to the cloud that the examiners or that the regulations do not allow them to be there. And that's, that's not true. Um, so what we're trying to do in partnership with KWS is educate the marketplaces as well as we can. Um, one of the biggest things that the cloud offers is this idea of flexibility and nimbleness and you know, unfortunately, I think Covid taught us that lesson, but there's, there's other lessons out there. I don't want to harp on Covid, I feel like that's all we talk about. Um, but if you look at any opportunity, whether it's a I machine learning, um, you know, Blockchain, pick the next technology, right? The reality is, none of us can really tell you where you're going to be in two years, maybe one year, three years, right? Like can you truly sit down after the past three years and tell me that you with no uncertainty, can tell me where your organization is going to be. And the reality is if you build your own data center right now, you have to make that guess Because you have to build something and designed for something and if you're making that investment, then you're doing that for the next probably 5-7 years. Whereas if you move to amazon you have the flexibility, whether that's scaling your organization up quickly, whether that's moving to the cloud, whether that's leveraging one of these technologies I just mentioned or in some cases even scaling back because things have hit a recession, we don't know what the future holds. But if you're in an environment like AWS, then you have the scalability and the flexibility to be able to move and pivot with that. And if you build your own and you happen to pick the wrong future, then then you could be in a bind and you've created your own limitations because you've decided to build for yourself. And I think that's the biggest thing is you can't build for yourself. You have to be flexible in this environment. That is that is the key. And the organizations that are flexible are the ones that are going to survive and thrive through all this uncertainty. Yeah. >>Well, really excellent point there. I totally agree with you. Wonderful to have you on our program. That was chris Saks Ceo of think stack as well as Michael Matthews, the president and Ceo at Mutual Credit Union. Thank you gentlemen for joining the show. Thanks so much. And that's all for this session of the AWS Global Public Sector Partner Awards. I'm your host Natalie or like thanks for >>watching. Mm.

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020. Special coverage sponsored by AWS Global Partner Network Welcome to the Cubes. Live coverage of AWS reinvent 2020. I'm Lisa Martin. I've got two guests joining me. Next. Chris Gru's director of Business development, AWS Marketplace Service catalog and Control Tower at AWS. Chris, welcome. >>Thank you. Welcome. Good to see you. >>Likewise. And Matthew Polly is an alumni of the Cube. He is back VP of worldwide business development alliances and channels at Crowdstrike Matthew, Welcome toe. Welcome back. >>Great to be here. Lisa, Thanks for having me. >>And I see you're in your garage, your f one car in the background. Very jealous. So we're gonna be talking a little bit about not f one today, but about what's going on. Some of the the news that's coming from the partner Keynote. So, Chris, let's start with you. What's going on? The AWS marketplace news and also give our audience a real good understanding of what the marketplace is. >>Yeah, sure. So So AWS marketplace is actually an eight year old service within the AWS family, and and our charter is really providing a fine by deploy and manage experience for third party software. And so what our organization does. We work with my issues like Crowdstrike, and we really try to get them to package up their software in that same consumption format that other customers are buying AWS services. It's already the best service already. Those customers are used to buying services like Red Shift, and that's three and a consumption format, and they want to be able to buy third party software in that same manner. And so that's really been our charter since we were launched eight years ago. We've had a lot of great mo mentum since our launch. We now have over 8000 listings available in the catalog, and we have over 1.5 million subscriptions going through the catalog. One of things that we announced earlier today is that we are up to 300,000 active customers. That's actually up from 260,000, which is our previous numbers. So we continue to see really good momentum in terms of adoption, from both our eyes, community publishing listings and then from our customers that are actually buying out of the catalog. We work on all types of formats of software, so we provide machine images in an Amazon machine image format. But we also published and make available SAS products, container products and algorithms and models to run in things like our sage maker environment. And then, as of this morning in the Global Partner Summit, we announced the ability to sell professional services through eight of this marketplace as well. >>So lots of expansion, lots of growth. I'd love to get Chris your take on this expansion into offering professional services. What does that mean? And how have your 300,000 plus customers been influential in that? >>Yeah. And so what we've seen is marketplaces evolved is the transaction sizes have actually gone up dramatically. A couple years ago we launched a feature called Private Offers, which allows eyes views to do a negotiated subscription, submit that to an AWS customer and that they accept that goes right on their bill. We've seen very good adoption that we've got thousands of private offers now going through the system and what we found when the transaction sizes started to grow. Both our eyes V s that we're using the platform, as well as the consulting partners that are partners with US through Amazon Partner Network. They typically attached services to those transactions So pure and eyes V you might wanna package on something like an installation service training services. Or it could just be a bespoke statement of work that goes along with your technology and then on the consulting partner side. Resellers want to attach those same type of services to the software that they re sell, and up until this morning we weren't able to do that. And so it provided a lot of friction to our customers or buyers because what they had to do is they actually had to bottom line those transactions, or they had to do those transactions outside of marketplace. And And that wasn't a good experience for either RSV community or restore community or customers. So now, with this launch, we could actually allow customers to buy those services from those Eyes v partners and those resellers. By virtue of doing that to marketplace and basically how it works. It's similar to our private offer experience. They just submit a private offer to that customer. They could upload a statement of work. And if that customer accept, it goes directly on their AWS bill and they did. This marketplace takes care of all the collection, and the building that goes goes along with that transaction. And so we're really excited about this. We had over 100 launch partners that we're ready to go as of this morning, and we think this is gonna be a great feature, is gonna get a lot of adoption. Crowdstrike, which is a company that Matthews with is one of our launch partners for that feature. And so we just think this is gonna be a game changer for us on a number of levels. It's really gonna open up the type of transactions that we can now do to market place. >>Well, you mentioned Ah, good f word frictionless. That's something that every business really aims to do to make that experience just as seamless as possible. So Matthew talk to us about crowdstrike being part of its professional services, launched the opportunities that that opens up for the marketplace, customers and your customers? >>Sure. So just a quick background on crowdstrike were an endpoint protection cybersecurity company that has historically been protecting laptops desktops on premise, uh, devices from from breaches, basically identifying indications of attack or indications of compromise that that may surface on those end points. We do that by having agents run on those devices and point back to our massive body of data that runs in the cloud A W s. In fact, and so collecting tons and tons of data petabytes upon petabytes of data, literally trillions of events per week were able to easily identify and apply machine learning and artificial intelligence, Um, to that corpus of data to be able to identify when there is adversary activity on those devices. Now we've gone through a bit of a digital transformation ourselves, and we're looking at now. Not only, or we have launched products here recently, that not only protect those on premise devices like the desktops, laptops and on premise servers, but also protect workloads that are running in the cloud E C. Two instances, or RDS instances. What have you in in AWS? Or we've also launched what crowdstrike calls are Falcon Horizon product, which is a cloud security posture management product to be able to give people visibility into configurations that may create risk for their cloud environments. And we've been leveraging marketplace for about two years now. Um, it's been a fantastic opportunity for us to really leverage that frictionless sales motion that Chris talked about reducing sale cycles for us and for our channel partners. We have a number of our channel partners that leverage the CPP Oh capability within within the AWS marketplace toe actually transact business with their customers. It's been a It's been a fantastic, um you know, mechanism for for crowdstrike, for our partners and for our customers. Um, you know, we've been part of the enterprise contract scenarios where we don't have to go through that process of negotiating an end user license contract. We've signed up for the enterprise contract. Many of our customers have signed up for that enterprise contracts with reduces the legal iterations to get a transaction done. So that's been fantastic. And what we're doing now with the you know, the professional services offering is we're standing up a few of our professional services, Um, you know, offerings on the AWS marketplace so that our customers and our channel partners can actually transact business through the AWS marketplace toe, acquire those particular professional services offerings. And the one that I think is most interesting is a kind of cloud security assessment where our professional services team will go in and actually evaluate our their configurations. Are there unmanaged, um, you know, accounts running in AWS or what have you that could represent a security risk and make recommendations about how to improve the overall security posture of that cloud environment, leveraging something like crowd strikes Falcon Horizon, as I mentioned earlier, or our cloud workload protection offering. So it >>really >>is about streamlining the procurement, offering them. You know, the ability to thio, offering customers the ability to acquire through the AWS marketplace, whether that's the crowdstrike product or the Crowdstrike service offerings. >>So, Matthew, I imagine given this year that we're all not sitting together face to face in Las Vegas. The events of this year have also brought a lot of challenges from a security perspective. We've seen Ransomware going up dramatically, but also in this massive pitot to work working remotely. I can imagine your customers big opportunity for Crowdstrike to help them when endpoints just scattered. So in terms of that, as well as the impact with what you're doing with AWS marketplace seems like a great opportunity to provide your customers with faster access to ensuring that they can guarantee the security off their all of their data, which is business critical. >>Yeah, 100%. So the kind of global pandemic and work from anywhere has driven demand for crowd strikes capabilities in two ways. Number one people leaving the office and going home. There's a proliferation of physical devices, laptops for people to actually work from home, which obviously need to be protected. And a lot of times these were people that were working from home for the first time. You know, no longer within the protection of the, you know, the corporate network. Maybe they're using a VPN or what have you? But they needed the added protection of an endpoint protection capability like crowd strikes. And the second is a lot of this digital transformation has been accelerated. We've had a few customers tell us they had a three year plan for for their their digital transformation, and a lot of that is moving on. Premise service involves moving on premise servers to the cloud, and they've had to accelerate that two months or even even weeks in cases. And that's driving. You know, huge demand for understanding how to ensure there maintaining the proper security posture for those cloud environments. So speed is key right now, making sure that you're protected and transacting those those you know, those those sale cycles quickly leveraging native US marketplace all is accelerating. >>Yes, speaking of that acceleration and we've talked about that a lot. Matthew. This acceleration of digital transformation years now crammed into months. Chris, let's wrap with you in light of that acceleration, how has that affected positively? The AWS marketplace Bringing in professional services, allowing your customers to have much more available to them, to transact directly and and in a frictionless way, when speed is so critical? >>Yeah, I mean what it really leads to. It just gives us more selection, right? So if you take a step back and you think about the you know, the infamous Amazon fire, well, one of the key components of what makes a fine we'll go a selection. And there was a lot of solutions that we had. We just couldn't sell through marketplace without having some kind of services attach. While there's a lot of products that you could just point, click and go. There are a lot of technology. Do you need to? Some have some kind of hand holding And so, you know, by virtue launching services, this actually opens up the amateur in terms of selection that we could bring into the catalog. One of things that we've been focused on as a late is bringing in business applications as an example. And a lot of times a business application might need services to go on, actually wrap around that solution cell and, you know, be part of that implementation. And so that's the other great thing about this is it's going to give us more selection, and that's just gonna let our customers buy more and more products out of this market place. But do that in this very easy format, where it literally just lets them put these transactions directly on the AWS bill. So we think it's gonna be a great you know, not only for movie deals faster but also providing more solutions to our customers and just giving a better selection experience of AWS customer >>and being able to do that all remotely, which is these days is table stakes. Chris. Matthew, Thank you so much for joining me today. Talking about what's new with the Amazon marketplace. What you guys are doing with professional services and crowdstrike. We appreciate your time. >>Yep. Thank you. Thanks. Lisa. Yep. >>From my guests. I'm Lisa Martin. You're watching the cubes. Live coverage of aws reinvent 2020.

>>from around the globe. It's the Cube with digital coverage of AWS reinvent 2020 sponsored by Intel and AWS. Yeah. Welcome to the cubes. Virtual coverage of 80 was reinvent 2020. I'm John for your host. We are the Cube virtual not there in person, but we're doing remote, as is a W s. Although there there on stage live. And we're here with Dave Brown, Vice President of the Sea, to compute. Great to see you again. Great keynote last night, kicking off everything for the opening night. Great stuff. >>Yeah, well, John, it's always good to be on the Cuban. Thanks for having me back. >>You know, you're in the hot seat these days in the sense of there's so much going on. I mean, Andy, that could do a three week announcement. Keynote. It was like in three hours of nonstop you take a break to go The bathroom. You missed two announcements, right? So, so much going on. You opened up reinvent 2020 with your announcement ec2 of mac instances. And there was a ton of compute. And the theme was really you know, reinventing and reimagining compute both. I want to get into that. But let's start with the hard news. Tell me about the Mac instances. Um, you had a great use case there, That kind of illustrated in your talk. But where is this coming from? It's obviously Mac developers are big, but is this market something that you guys saw from customers or was a necessity? Take us through the thinking around the Mac instance. Easy to for Mac instances, um are going for >>absolutely absolutely So I mean me personally Matthews, a longtime Matthews that we've often thought about. Could we ever bring Mac OS to AWS? Right This thing we've spoken about on and off for many, many years and, you know, it was about a year and a half about two years ago. You know, we're always hearing new use cases from customers, and that's kind of what we're doing. So we're saying what a customer is trying to do that we don't support today, and how would we support them in that? And we started a year from customers that they have been able to successfully migrate all of the AWS workloads to AWS. So most of the server workloads to AWS and then they've got this Mac bold workload that they just weren't able to bring to us. We just didn't support Max into. It was a great example who I had on stage with me last night where you know, they over the last couple of years have been moving Ah, lot of their workloads to AWS. And and then they had these Mac money sitting around that they had to manage themselves. And so we said, could we actually do this? And so that was the one thing the customer ask. And the other thing that we realized was with the nitro system in the work that we've been doing there over the last, you know, six years, seven years since 2012, Really? And just where we are from the From nitro system point of view, we were able to wrap a Mac money without making any changes to it with nitro cards plugging a FireWire to the thunderbolt port and and and actually control that device. And so it means that you get the best of Apple hardware, which is what Apple's all about is the hard way that they make and the way that their software works with it. together with the nitric system and the cards around that inte integrating with the rest of AWS. So we're giving you, you know, high speed secure networking. We're giving you great access to elastic block store Was just integrates natively into the magma Nias? Well, a So we realized that the technology was there, the customer asked, was there and then obviously went to Apple and worked with them very closely to make it happen. And so that's kind of how it all came together. And I was incredibly excited to announce it last night. And the feedback today has just been amazing. A lot of excitement. >>Yeah, take me through the use case because, you know, obviously there's two trends going on. There's custom chips and server list kind of thing happening where you guys, I mean, really doing a good job of the eye as layer, innovating there and then platform as a service. All that software on top. I totally get that. You could see that happening. Chips custom ships to Intel, A, M, D. And others. Now you got Mac hardware. Where's the innovation use case because one would start would say, Hey, why don't you care about whether it's Mac hardware or not. Because I'm server lists. I should be programming the infrastructure actually be getting compute generically. Where does the Mac tying come in? Because that's the first question I was thinking of was, I'm a Mac user. I love Mac, but I'm also got some windows actually going on now. And ultimately, do I really care if it's compute? What's your reaction to that? Yeah, >>absolutely. I mean, if you look at Apple's ecosystem today, right, they have millions of applications in the APP store. They have 28 million developers worldwide, actually building those applications just incredible. And many of those applications, all these millions in the In the APP store itself, there's many more applications that are both by enterprises and companies, right? We have an application that we use internally at Amazon is available on my phone. That's not in the APP store, and you know, many companies are doing that and to build applications for the ecosystem, they have to be built on Mac hardware. And that's just how Apple works, right? So if you wanna build for iPad or iPhone or even Apple TV and Apple watch, you have to build those applications on a Mac. And so what we see companies doing is, you know, the old develop a meme off. Well, it works on my computer, right when you build something, you don't wanna be bullied on your local laptop for production. So they typically have a fleet of machines that they either under somebody's desk or in a data center somewhere that they use for for building these Mac applications. And so it's not possible to build a Mac application on anything other than a Mac itself. And we when we looked at it, we really didn't feel that virtualization made sense, right? Apple? I mean, they have some some virtualization that they're able to do within Mac OS itself. But if you think about how do we solve the customer use case, it's really bringing apple hardware too easy to to solve the problem and giving customers that exactly same exact same experience that they have on prep. And if you look into it like that, models just worked right. We gave them better access. Uh, you know, they've been using that data which you normally say, Hey, don't don't run production workloads on a beta. But you know, I found out if I interview with the BPS at Intuit critique that they've actually moved 80% of their production pulled wear clothes too easy to already to run on the Mac instances. And so that, and that's in the space of two months. And so, just as seamless ability to move because it's the same hardware is kind of what we were going >>after. Great, thanks for sharing that and say, one thing I wanna point out is Mac does have their own chips as well. They're going custom chips. Amazon's going custom chips. And I think I think you nailed what I was trying to understand, which is this developer community for Mac. And there's some things that are purpose built for Mac devices. So on Mac ecosystem, get the marketplace as well as you know, that that was the hardware PCs and devices, and they're only doing more and more. So this brings me to the i o t. Um, piece of it, because Apple does make devices that people wear and I watch is, um, iPhones. I mean, they're not computers anymore. They're everything. So this kind of brings up the edge conversation. So whether it's an iPhone or a five G in a Metro or I'm a stadium watching a football game and there's some sensor camera vision industrial thing there, this is the new normal. This is where you guys are kind of eating, eating up the software side that that business, because there's new capabilities here. Can you explain how compute he's, particularly C two gets to the edges because no one wants to move data around. They wanna move, compute, not data, because data is expensive and it's and it's fat. So we we talked about that we keep on years ago, but you gotta move. Compute. So how does that work Take us through your vision? >>Absolutely. And this is This is a massively growing area for us. I mean, you mentioned Apple's new M one silicon Apple silicon that they just launched a swell, and we're super excited about Apple's been doing there. We've been doing the same thing with our grab. It's on two processor and really saving customers. An incredible amount on price performance. Tried customers moving and getting 40% improvement and price performance just by moving to grab it on too. It's just incredible. Um, in terms of the edge, you know, we started this journey. We started this journey quite some time ago and bringing, you know, Lambda functions to cloudwatch and things like that. How do we bring compute to the edge? We took a look at five G, which I think it's gonna feel a lot of this right if if we look at our cell phones today was actually just talking to the Apple team yesterday with the iPhone, only came out, you know, 13 years ago. It's kind of amazing to think just how much progress we've had and what four g did for the device that's in our pocket in terms of, you know, just how much we rely on that today and what we get. Well, five g is just a step function in both in terms of latency, but also in terms of throughput. And so, you know, one of the projects we announced last year with Verizon and we now Andy announced this morning we're also gonna be rolling out with Katy D I and SK Telecom and Vodafone next year. Um is a project always like that brings aws compute to the edge of the telco network. And so with Verizon, we now have eight locations around the U. S. Where we have AWS compute capacity. And what I mean by that is literally C five instances uh, G four GPU instances for customers that want to do influence and graphics processing on the edge. And that's embedded into the five G network on DSO customers. You know, we've got a number of customers that are doing a lot of interesting things with five G in the sports area, where they have five G cameras that are, you know, submitted directly to wavelength. We no longer need to drive a truck to a stadium to record a game. You just have five G cameras, um, to, you know, automated factories where they doing robotics in factories and yet really low latency. And they don't want the computer, the factory they wanted in five G and so just exciting area for us. That's growing really, really quickly. Thea Other thing we did is obviously with local zones. We launched our first local zones in L a X last year, Los Angeles on that's being used by the movie industry, so you know right now is a lot of exciting up and running off the covert and shut down for a period of time and filming the next release of all of our favorite episodes and across all of these various streaming platforms. And a lot of that work is actually the post production is being done on on AWS on G four instances within the Los Angeles region. So, you know, very low agency for colorization animation, special effects, all that sort of things happening there. What we heard from a lot of customers was they loved outposts as well, which is our offering to put a server into a data center. And you heard from riot games in Andy's Keynote, where they actually bought a number of outposts and put them all over the U. S. And also other places of the world to really lower the Leighton see for their latest game. And so what Andy also just announced is the availability off three additional local zones. So Atlanta, Miami and Houston Sorry, Boston Miami in Houston available today, and then additional 12 available local zones next year, and what that does is that sort of spreads AWS capacity compute capacity at the edge in all of our major metropolitan hubs all of their capacities on the AWS backbone as well, but brings customers that low latency connectivity that they're looking for. Gaming developers were, you know, every every millisecond counts in terms of gameplay on so super excited to be going after that use case, which I think, you know, it's difficult to tell what the next 10 years is gonna be like. But I think Layton's he's gonna have a big part to play in the types of applications we see on our phones going forward. >>Great stuff, final question for you as we wrap up, obviously with virtualization with virtualization. But you know, the cove it is. And he pointed out, People are gonna change, is gonna be winners and losers. He kind of clearly pointed out, But the people who do lean into the cloud who have been on the cloud or taking advantage of the tail winds of cove in because of the capabilities there are two bills air higher, and you should be happy for that. But they're also gonna have more demand for you to say, Hey, I need more services. So How do you speak to those people who are leaning in who are leveraging, more, compute? What should they be looking at? What kinds of services should be connecting into compute? How should they be thinking about the future of compute so that they can take advantage of those capabilities? The lower costs, higher performance? What things are complementary for these customers as they come in, not toe dip in the water kind of things against really driving. And what do they need? >>Yeah, absolutely. And this has been a big focus on us. You know, things has bean, as I cover in my keynote, which leadership session that I'm doing tomorrow Wednesday. You know, a lot of this year has been helping customers through covert and what covert is meant for their business. Whether that is cost savings for many of them or whether it's just demand, you know that they've never experienced are expected before. I mean, we've been incredibly hard at work in servicing those customers, right? I actually catch up with Scott Sikora. In my keynote. He leads our capacity team. We talked through what it meant and how we actually provided the capacity that our customers needed during Colbert Times. But for a customer moving to us, the first thing is obviously we wanna find ways to make them very successful in the cloud, but more importantly, lower price performance for them. So what we wanted to do is give them the best possible performance that's available at the lowest possible cost. And if you look at a number of the announcements that Andy made today, you know whether it's our latest graviton processor where you can, you know, when you move to arm. I think customers often overestimate how much work it will be to move to arm. And when I talked to them after they have moved, that's ahead. Wasn't actually that much work. We actually got it up and running relatively quickly. So what's simpler than people expect? But that's an opportunity to save 40% on price performance. You know these new newer workloads like our graphics. We just launched a new G four a D, which is an AMG based GPU solution, the first time we have had an AMG GPU on the EEC too. And that's also looking to say, if you know upwards of 40% price performance of other GPU offering so just incredibly exciting for graphics, work, clothes and then in the machine learning space. Like I think, if you know, machine learning is just become the new normal, like everybody is doing it. And you know, just three years ago, everybody was thinking about whether they should do it. How would how they would use it Now that it's a lot of companies are doing it. It's really How do you How do I use it more? And that comes down to again saving costs. And so what we know with without Inferential Chip and then the new Habbaniya chip we just announced it with with the work with Intel that we're doing and then a new trainee, um, ship for training, training. We're really working to lower the cost of machine learning. And so, like we've seen many customers like Alexa was a great use case the other day. Being able to lower the cost of inference for Alexa by 35% again just helps customers, you know, move to the cloud. But I mean, just generally, you know, we're trying to support customers everywhere where there were, you know, if there are many customers are in their own data centers looking to move to AWS. You know, we have great models that can support them with our existing compute. A new savings plan offering we announced last year just great for saving costs on getting the price down So a lot. You can look at it. You know, I could go on forever. Really. It >>Certainly it's certainly is MAWR. We'll we'll do a deeper dive follow up after reinvent, but it is a wake up call. As I wrote in my post, um, for a cloud on Finally, I've been saying this for years. Horizontal scalability is a disruption on the infrastructure side, but you've got vertical specialization with data to create great modern apse of machine learning. And I actually playing out in full display here is Andy said, um, net right now. So all this benefits and all these opportunities to disrupt horizontally and then leverage the data all tied together, all coming together. You're clear. Leading the team. Great Brown, vice president of E C. Two in charge of the team that's driving the future. Compute. Thanks for coming on The Cube Cube Live coverage. Thanks. >>Thanks for having me. >>Okay. I'm John for the Q back for more live coverage after this short break

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

>> Announcer: From theCUBE studios in Palo Alto and Boston, connecting with thought leaders all around the world, this is a CUBE conversation. >> Hi, I'm Stuart Miniman and welcome to this episode of CUBE conversations. I'm here from our Boston area studio. Happy to welcome to the program, Doug Matthews. He's the vice president of product management with Veritas coming to us from Atlanta. Doug, thanks so much for joining us. Nice to see you. >> Hey, great to see you Stuart and thanks for having me today. >> Yeah, so Doug obviously, 2020, there's a lot of change going on, globally, a lot of things happening financially, but one of the ongoing changes that we've been watching and has had huge ripple effects, is of course the impact on cloud. So why don't you bring us in a little bit. Tell us, what you work on, and how cloud has been impacting, what's happening with the data protection or resiliency in your world? >> Sure, so, Veritas Technologies is a long brand of focus on data protection. And we are highly focused on protecting data regardless of where it lives, whether it lives on a customer's premise or whether it lives in a cloud, public cloud architecture, or even in a cloud application. So, for us, this has been a transformational change as more and more people begin to adopt cloud services as the work from home trend starts and we're seeing them much higher emergence of ransomware. >> Yeah, so cloud of course, it is a unevenly distributed if you look at, if look at a countries, if you look at industries, >> Right. >> I'm wondering what you're hearing from customers, what's kind of the 2020 snapshot of where we are with the overall cloud wave. >> Sure, yeah. What we're seeing is a much more rapid adoption of cloud services as businesses and organizations begin to wrestle with the fact that they can't bring people into the office. So the work from home trend, the access to resources needs to be delivered through the cloud applications, even data centers. We're now beginning to see you some supply chain hiccups that are causing the supply chain fulfillment of server orders beginning to slow down. So customers are beginning to think more broadly about cloud gives you agility, operational ability to react to change. So people are accelerating their adoption of cloud resources because they're almost being forced to. >> Yeah, is there anything specific you're seeing are you getting any data maybe with coronavirus as to what service is in the cloud and what impact that's having on your customers? >> Yeah, so dramatic change, right. So for example, Azure Cloud Services are up something like 775%, which is just astounding number, VDI, Virtual Desktops up over 300%, and just massive of these cloud resources is just a continuing component trim. >> Yeah, and how about from a data protection standpoint and security. Obviously, we've seen that the malicious attacks have increased, unfortunately, and when you have more people outside of the enterprise walls itself, there's more things we need to make sure that our data is secure. >> Yeah, absolutely. And we have without a doubt seen a rise in ransomware attacks and malware attacks. What's interesting to note is increasingly the consumer is placing the blame for these attacks, less on the perpetrators and more on the organization and business leaders. For example, over 40% of consumers actually hold the business leader responsible where ransomware attack that their business suffers And (indistinct) percent would actually say that they would stop buying from an organization that suffers from a malware or has been a victim of an attack. So the mindset here is no longer place blame on the perpetrators, but on the business leader and owner that didn't protect their data in such a way that kept the user from being exposed. >> Yeah, Doug, why don't you bring us inside and explain how Veritas is helping in these environments to protect our data? >> Yeah, so I think the first thing is as a business leader begins to think about their cloud contract, they need to understand their SLAs and how that maps to what that cloud provider is going to provide for them. We actually found, recently, we produced a report called the "Truth in Cloud Report" and in that report, we talked to cloud architects and business leaders over 1600 of them that respond, and one of the things that we found pretty interesting is that 85% of the respondents said that the cloud service provider is responsible for protecting their data, but that's completely disconnected from the actual fact that over 53% or so of those that responded actually had an SLA that was higher than their cloud service provider would provide. So they believe it's supposed to be done by the cloud provider, but it isn't being done by the cloud provider to meet their needs. So people really need to think about and analyze who's protecting their data and how they're protected when they move into that cloud architecture. >> Yeah, I have to say I'm a little surprised to hear those results, the drum beat that I've heard from the security industry for the last couple of years has been about the shared responsibility model, there have been some rather public and highly visible failures where say somebody made a false assumption that was something would be turned on and the cloud service providers have come back and said, "Hey, you all, if there's these things you need to do and just because there's a lock on the door, if you don't lock it, we're not responsible for it". It is kind of the analogy I use. Shouldn't we, by 2020 now, where cloud is not new. I would have thought that we would have gotten through some of these rather basic understanding of who's responsible for what and ultimately who needs to answer for these things. >> Yeah, I think we're still in that adoption life cycle and I think there was the... We mapped this as a hype cycle of our own... We're people right in the adoption of cloud and we believe that classically cloud architects, probably 20 to 25% of organizations, have actually fully adopted cloud at this point and are aggressively adopting cloud, but there is such a rush now to get in from these business leaders and architects, who haven't really you've taken the time to frame and understand things that they're now being pulled along in this journey and rediscovering this thing. So we have to keep that drum beat up as some of the cloud laggers or more mainstream technology adopters are beginning to adopt cloud 'cause they haven't stayed aware. I completely agree with you. We've been talking about the shared responsibility model for a long time, but these survey results showed that it's still a problem. >> Doug, you make a great point. You talk about companies have had to compress their cycles and while normally they would have been able to really plan things, walk through what they were going to do, they're often rushing into things a little bit more. So what advice would you give other companies that are now been dipping their toe, but jumping into cloud or they need to accelerate what they're doing, what advice would you make sure that people don't get in a little over their skis or do something that they're going to regret? >> Sure, so the first thing I would say is, have a recovery plan and make sure you rehearse it. Again, back to the blame here is falling on business leaders, so don't get caught by it, make sure that you understand your recovery plan, make sure that you rehearse it and that it works. The second thing is, I would absolutely read that fine print of your contract and make sure that your required SLAs match up with what your cloud services provider provides, or you need to adapt technology that helps you to adjust to make sure that you achieve that SLA. And then the final thing as you're doing all this, so many people look at cloud for cost optimization as an outcome, make sure you don't overpay because the there are various levels of cloud storage, cloud storage is extremely expensive, cloud resources are expensive. Typically people think about the actual host itself or the instance itself, make sure that you think about the storage as well. So use things like deduplication or lower tiers of storage to optimize your cost efficiency. >> All right, so Doug as we mentioned earlier in the discussion Veritas has been around for awhile really well understood how you help customers, help connect us as to what you're doing for the cloud specifically. >> Sure, so specifically for cloud, let's focus on an upcoming release. I think most people that are probably watching this are familiar with our product called NetBackup, it's the enterprise leader in data protection. NetBackup is designed to solve the data protection challenges across all infrastructure whether it's your typical on premise infrastructure or new cloud architectures. So in these new cloud architectures, we've done things to make sure that you efficiently utilize cloud storage. So we do things like deduplication, we also control network bandwidth and make sure that you minimize rather your impact on network bandwidth. So you've minimize your overall cost requirements associated with cloud or data protection. The other thing that we're doing in this next release, which I think is really exciting is, we're going to take our cloud point solution and our resiliency platform solution, these solutions are designed to help customers, efficiently recover in cloud as well as do it in a very quick and automated fashion. And we're going to bake those into our NetBackup product. So the NetBackup consumer will automatically have access to these two new technologies that we've been developing for the last several years. So that's really exciting for us to be including those with our NetBackup product. >> All right, and Doug, when we talk about cloud, is this supported across any cloud or there are specific integrations that we should understand or just where does this fit in the entire, on a multicloud ecosystem? >> Yeah, so the one other thing, again, about NetBackup being a platform, it support over 1400 different data sources, over 800 different data targets, and that includes over 60 cloud providers, so it supports us this broad ecosystem of cloud architecture but where that makes sense, we always go deep. So we go deep with your traditional cloud providers, like AWS or Azure and provide that deeper level capability for those those cloud providers. >> All right, great. What else should we know about what's new from Veratis's cloud offering? >> Yeah, I think when we build our cloud solutions, we focus on a four stage lifecycle of a customer. For example, we realized that customer wants to migrate the cloud, they want to protect their resources in cloud, they want to be able to recover when the time comes and then optimize their cloud footprint. So we tend to focus in those four pillars to achieve success for our customers. >> Yeah, a question on that, I think about moving to the cloud, there's a lot of discussion about how do I modernize my environment and often it's I move to the cloud, but then how do I really become cloud native, if you will. So I'm making updates and I'm making changes. If I think about backup traditionally, it was, let me get something, let me put it in place and I'm going to run it that way for years. So how does Veritas make sure that as I'm modernizing as I'm making changes that my data is still going to be protected no matter where I am along that journey. >> Sure, so I think as customers are migrating to and adopting cloud, their first stage on the train or their first station that they come to on the train is that lift and shift approach. We're going to take everything from on premise and we're going to move it to the cloud. So we have technologies that will help our customer do that with automated failback, so they can set up the replication solution, push a button now they're up and running in cloud, hey, it didn't work, push the button and they're back down in their on premise environment, adjust and do it when it makes sense and they're ready to make it make it work. So we have a fairly robust set of technologies that can help in that lift and shift process, lift and shift process. The other thing that we provide is for those infrastructure as code guys, the guys that are further out that are thinking, how do I natively build cloud based solutions? We have a very full suite of APIs so that the customer can implement their infrastructure as code requirements right there through that Swagger interface that you would expect and deploy infrastructure as code environments in cloud, utilizing our enterprise class API. So we're purpose built to be able to help customers get the cloud, and then also support those cloud applications that are built there natively. >> Yeah, Doug, I'm wondering, do you have either a customer example, maybe anonymized you can share, or just any general cloud learnings about where your customers are and how Veritas is helping them? >> Sure, so one of the first things that we see customers try to accomplish is the move of their backup storage infrastructure into a longterm storage in cloud. So they might use it as a replacement for tape, they might use it as a replacement for disk, and they want to live in the cloud environment. So we have a capability, we call it CloudCatalyst that moves data very efficiently from on prem into the cloud, keeps it deduplicated, optimizes it for wide area network transmit, and really efficiently moves that data in the cloud, and then really what's important is once it gets in the cloud, it doesn't touch that data. So we have a large customer who's got over a couple of petabytes of data in Europe that wanted to make that migration to cloud, they were using another provider at the time, so we came in and we were actually able to save them over 98% of their overall operational cost associated with moving and migrating that data just based on this one capability. So that's a key element, right. As people are moving that data to cloud, make sure that it stays efficient, optimized, deduplicated in stored efficient. >> All right, Doug, I'll give you the final word. >> Yeah, I think my warning for customers is to make sure that they are well-protected with their data state in cloud. Understand what your cloud service provider provides, make sure that your SLOs, your service level objectives are going to be met by the technologies that you deploy in order to solve your cloud problems. And then think about things holistically, think about it first from the migration, then how you protect it, then once you get there, what do you do to recover, make you test that. And then once you've got everything kind of thought through and ready to implement, make sure that you've optimized it to be efficient in it's cost utilization and in it's operations. >> All right, well, Doug Matthews, thank you so much for the updates, we really appreciate you sharing us some important tips for customers as they go along their cloud journey. >> Thank you so much, Stuart. >> All right, I'm Stuart Miniman and thank you for watching theCUBE. (gentle music)

>>From New York city. It's the cube covering. Welcome to the new edge brought to you by systems. >>Hey, welcome back everybody. Jeff, Rick here with the cube. We are in Manhattan at the top of Goldman Sachs. It is a great view if you ever get an opportunity to come up here, I think 43 floors over the Hudson you could see forever. But this is the cloud events. So the clouds are here and we're excited to be here is the Penn Penn Sandow launch in the name of the event is welcome to the new edge, which is a pretty interesting play. We hear a lot about edge but we haven't really heard of that company really focusing on the edge as their primary go to market activity and really thinking about the edge first. So we're excited to have the cofounder cube Olam and many time guests a Sony Gian Deni. She's the co founder and chief business officer. So many great to see you. Good to see you too. >>And our hosts here at Goldman Sachs is uh, Josh Matthews. He's a managing director of technology at Goldman. Josh. Great to see you. You too. And thank you and thanks for hosting us. Nice. A nice place to come to work every day. So great conversation today. Congratulations on the launch of the company over two years in stealth mode. Talk a little bit about that. What is it like to be in stealth mode for so long and you guys raised big money, you've got a big team, you're doing heavy duty technology. What's it been like to finally open up the curtains and tell everybody what you've been? >>It's clearly very interesting and exciting. Normally it's taken me nine months to deliver a baby this time it's been two and a half years of being instilled while we have been getting ready for this baby to come out. So it's phenomenally exciting that too to be sharing the stage with our customers and our investors and our strategic partners. >>Yeah, I thought it was pretty interesting that you're launching with customers and when you really told the story on stage of how early you engaged with Josh and his team, um, first I want to get your kinda your perspective. Why were you doing that so early and what did that ultimately do with some of the design decisions that you guys made? And then we'll come back to Josh as to, you know, his participation. >>So I think whenever you conduct technology transitions, having a sense from customers that have the ability to look out two to three years is very important because when you're capturing market transitions, doing it with customer inputs is far more relevant than going about it alone. Uh, the other key thing about this architectural shift is that it allows the flexibility for every customer to go take pieces of how they want to bring the cloud architectures and bring it into their environment. So understanding that use case and understanding the compelling reasons of what problems both technological and business can be solving and having that perspective into the product definition and the design and the influence that customers like Josh you've had is why we are sitting here and talking about them in production. Uh, as opposed to, yeah, we're thinking about where we are. We are looking at it from a proof of concept perspective. Right. >>And Josh, your, your perspective, you said earlier today that, you know, as long as a sign is involved, you're, you're, uh, you're happy to jump in and see what she's been working on. So how, >>you know, how did you get involved, how did they reach out to you and, and what is it like working on, you know, technology so early in its development that you get to actually have some serious influence? Well, it's an amazing opportunity, um, to get exactly what you want, um, exactly what you know is going to solve problems for the business here. Um, you know, and the other thing is, you know, we've worked with this team, uh, through almost every spinning. Uh, I think it was a little young for the, maybe the first one. Um, but, uh, otherwise this team has worked with them through at least 15 years or more. So we knew the track record for execution and then for us on this product, I mean, it was an opportunity because it's truly a startup. Um, you know, Sony and the team brought us in. >>Uh, we kind of just put out problems on the table that we were trying to solve and then, you know, they came up with the product and the idea and we were able to put together, you know, yeah, these are our priority one, two, three that we want to go for. And you know, we've just been developing alongside them. So both software and, you know, driving what the feature set is. Right. So what were some of those problems guys? Price seemed like forever ago when you started this conversation, but as you kind of looked forward a couple of years back that you could see that were coming, that you needed addressed. You know, it's funny, we started with kind of like, well we think containerization is going to be explosive and, and you know, really everything's on virtual machines or bare metal, mostly virtual machines. So one, you know, as containers come out, how do we track them, secure them, um, how do we even secure, uh, you know, the virtual machines and our environment cause they're, you know, over almost a quarter million of them. >>The idea of being able to put, um, network policy, that's I would say incorruptible, not actually on the server, but at, you know, that's why we use firewalls, right? So solving that security problem was number one. The other one was being able to have the telemetry to see what's happening, what's changing, um, and troubleshoot at, you know, at the network layer from every single server. Again, it's all about scale. Like things were just scaling and the throughput's going up, traditional methods of being able to see what's on your network. You can't look in the middle, it just can't keep up. It's just speeds and feeds. So being able to push those things to the edge. And then lastly, it really happened more, um, through the process here. But about a year and a half ago, um, we began segmenting our network the same way a 5g provider does with a technology called segment routing. >>And we just said, that's kind of our follow on technologies to, you know, put the network in the server and put this segment routing capability all the way out at the edge. So, you know, some things we foresaw and other things we've just developed. You know, it's been, it's been two and a half years. So, um, it's been a great partnership and you know, I think more, more features will come. Well Sony, you and the team, but it's been talked about all day long, have have a history of multiple times that you've kind of brought these big transformational technologies. Um, head what, what did you guys see a couple of years back and kind of this progression, you saw this opportunity >>to do something a little bit different than you've done in the past, which is actually go out, raise, raise around and uh, and do a real startup. What was the opportunity that you saw this? >>So we saw a number of challenges and opportunities. At the same time, we, we clearly saw that, uh, the cloud architectures that have been built by the leaders, like the incumbents like AWS today have a lot of the intelligence that is being pushed into their, their respective compute platforms. Uh, and we also noticed that at the same time, while that was what was needed to build the first generation of the cloud, the new age applications, and even as gardener has predicted that 75% of all enterprise data and applications will be processed at the edge by 2025. If that happens, then you need that intelligence at the edge. You need the ability to go do it where the action is, which is at the edge. And very consistently we found that the architectures, including scale out storage, we're also driving the need for this intelligence to be on in a scale-out manner. >>So if you're going to scale out computing, you need the services to be going hand in hand with that scale. Our computer architecture for the enterprises so they can simplify their architectures and bring the cloud models that have only existed in the cloud world, into their own data centers and their own private clouds. So there were these technology transitions we saw were coming down the pike. It's easier said now in 2019 it wasn't so simple in 2017 because we had to look at these multiple technology transitions. And surprisingly, when we call those things out, as we were shaping the company's strategy, getting validation of the use cases from customers like Josh was pivotally important because it was for the validating that this would be the direction that the enterprises and the cloud customers would be taking. So the reason you start with a vision, you start with looking at where the technology transitions are going to be occurring and getting the customers that are looking farther out validated plays a very important role so that you can go and focus on the biggest problems that you need to go and solve. Right, right. >>It just seems like the, the, the big problem, um, for most layman's is, is the old one, which, why networking exists in the first place, which is do you bring the data to the compute or do you bring the compute to the data? And now as you said, in kind of this hyper distributed world, um, that's not really a viable answer either one, right? Because the two are blended and have to be together so that you don't necessarily have to move one to the other or the other back the other direction. So, and then the second piece that you talked about over and over in your, in your presentation with security and you know, everybody talks about security all the time. Everybody gets hacked every day. Um, and there's this constant theme that security has to be baked in, you know, kind of throughout the process as opposed to kind of bolted on at the end. You guys took that approach from day, just speak >>it into the architecture. Yes. That was crucially important because when you are trying to address the needs of the enterprise, particularly in regulated markets like financial services, you want to be in a position where you have thought about it and baked it into the platform ground up. Uh, and so when we are building the program of a process, so we had the opportunity to go put the right elements on it. In order to make it tamper proof, we had to go think about encrypting all the traffic and communication between our policy manager and the distributed services platforms at the edge. We also then took it a step further to say, now if there were to be a bad actor that were to attack from an operating system vulnerability perspective, how do we ensure that we can contain that bad actor as opposed to being propagated over the infrastructure? So those elements are things you cannot bolt on at design time, or when you need to go put those into the design day one, right. Only on top of that foundation, then can you build a very secure set of services, whether it's encryption, whether it's distributed via services, so on and so forth. >>Uh, and Josh, I'm curious on your take as we've seen kind of software defined everything, uh, slowly take over as opposed to, you know, kind of single purpose machines or single purpose appliances, et cetera. Yep. Really a different opportunity for you to control. Um, but also to see a lot of talk today about, about policy management. A lot of talk about, um, observability and as you said now even segmentation of the networks, like you segment the nodes and you segment everything else. You know, how, how do you see this kind of software defined everything continuing to evolve and what does it enable you to do that you can't do with just a static device? I mean, the approach we took, um, we started like, you know, years ago, about six years ago was saying we can get computers, uh, deployed for our applications. No problem. Uh, and you know, at, at on demand and in our internal cloud, now we can do it as a hybrid cloud solution. >>One of the biggest problems we had in software defined was how do you put security policy, firewall policy, um, with that compute and in, you know, our industry, there's lots of segmentation for material nonpublic information. Um, compliance, you know, it could be internet facing, B2B facing. Uh, we do that today. We program various firewall vendors automatically. Uh, we allow our application developers to create, um, these policies and push them through as code and then program the firewall. What we were really looking to do here is distribute that. So we F day one in getting pen Sandow into production was to use our uh, our firewall system. It's called pinnacle. We, um, we programmed from pinnacle directly into the Penn Songdo Venice manager via API and then it, you know, uses its inventory systems to push those things out. So for us, software defined has been around, I like to call it the store front, but for the developer it's network policy, it's load balancing. >>Um, and, and that's really what they see. Those are the big products on the net. Everything else is just packet forwarding to them. So we wanted with pen Sandow at least starting with security to have that bar set day one and then get, you know, all the benefits of scale, throughput and having the policies close to the, on the edge. You know, we're back to talking about the edge. We want to right there with the, with the deployment, with the workload or the application. And that's, that's what we're doing right off the bat. Yeah. What are the things you mentioned in your talk was w is, you know, kind of in the theme of atomic computing, right? You want to get smaller and smaller units so that you can apply and redeploy based on wherever the workload is and in the change. And you said you've now been able to, you know, basically take things out of dedicated, you know, kind of a dedicated space, dedicated line and dedicated job so that you can now put them in a more virtualized situation. >>Exactly. Grab more resources as you need them. Well, you'd think the architecture, I mean even just theater of the mind is just, you're saying, I'm going to put this specific thing that I have to secure behind these firewalls. So it's one cabinet of computers or a hundred it's still behind a set of firewalls. It's a very North, South, you know, get in and get out here. You're talking about having that same level of security and I think that's novel, right? There hasn't been, if you look at virtual firewalls or you know, IP tables on Linux, I mean it's corruptible. It's, it's, it can be attacked on the computer. And once it's, you know, once you've been attacked in that, that that attack vector has been, you know, hit your, your compromised. This is a separate management plane. Um, you know, separate control plane. The server doesn't see it. >>That security is provided. It's at scale, it's East, West. The more computers that have the pen Sandow, you know, architecture inside of them, the, you know, the wider you can go, right. And then the North South goes away. I'm just curious to get your perspective. Um, as you know, everyone is a technology company. At the same time, technology budgets are going down, people are hard to hire. Uh, your data is growing exponentially and everything's a security threat. Yes. So as you get up in the morning, get ready to drive to work and you're drinking your coffee, I mean, how do you, you know, kind of communicate to make sure to senior management knows kind of what your objectives are in this, this kind of ongoing challenge to do more with less. And it, even though it's an increasingly strategic place or is it actually is what the company does now, it just happens to wrap it around your plane services or financial services or travel or whatever. >>Uh, I think your eye, and I had said it to John before, um, it has to come from that budget has to come from somewhere. So I think a combination of, of one that's less, well, I'll say the one that's easier to quantify is you're going to take budget from say appliance manufacturer and move it to a distributed edge and you're going to hopefully save some money while you do it. Um, you're going to do it at scale. You're gonna do it at, you know, high throughput and the security is the same or better. So that's, that's one, that's one place to take capital from. The other one is to say, can I use the next computer? Yes. Because I don't have to deploy these other new computers behind this stack of firewalls. Is there agility there? Is there efficiency, um, on my buying less servers and using, you know, more of what I have and doing it, you know, able to deploy faster. >>And it's harder to quantify. I think if you could, you know, over time, see I bought 20% less server, uh, capacity or, you know, x86 capacity, that's a savings. And the other one that's very hard to quantify, but it's always nice to have the development community. And we've had it recently where they say, Hey, this took me a month to deploy instead of a year. Um, and you know, the purchase cycles, uh, you know, for procurement and deployment, they're long, you know, in enterprise you want them to be quick, but they're really not. So all of those things add up. And that's the story. You know, I would tell, you know, any manager, right? Yeah, >>yeah. I think, you know, the old historic way that utilization rates were just so, so, so, so low between CPU and memory, everything else. Cause if nothing else, because to get another box, you know, could take a long time. Yeah. Well, final, final question for you, Tony. You talked about architectures and being locked into architectures and you and you talked about you guys are already looking forward, you know, to kind of your next rev, your next release, kind of your next step forwards. What, where do you see kind of the direction, don't give away any secrets, but um, you know, kind of where you guys going. What are your priorities now that you've launched? You got a little bit more money in the bank. >>Well, our biggest priorities will be to focus on customer success is to make sure that the customer journey is indeed replicable at scale, is to enable the partner's success. Uh, so in addition to Goldman Sachs, the ability to go and replicate it across the federated markets, whether it's global financial services, healthcare, federal, and partnering with each B enterprise so that they can on their platform, amplify the value of this architecture, not just on the compute platforms but on, in other areas. And the third one clearly is for our cloud customers is to make sure that they are in a position to build a world class cloud architecture on top of which then they can build their own, deliver their own services, their own secret sauces, uh, so that they can Excel at whatever that cloud is. Whether it's to become the leading edge platform as a service customer, whether it is to be the leading edge of software's a service platform customer. So it's all about the execution as a, as you heard in that room. And that's fundamentally what we're going to strive to be, is to be a great execution machine and keep our heads down and focused on making our customers and our partners very successful. >>Well, certainly, congratulations again to you and the team on the launch today. And Josh, thank you for hosting this terrific event and being an early customer. Yeah. Yeah. Happy to be. Alright. I'm Jetta. Sone. Josh, we're the topic. Goldman Sachs at the Penn Sandow the new welcome to the new edge. Thanks for watching. We'll see you next time.

Okay, this presentation includes forward looking statements that are subject to risks and uncertainties. Actual results may differ materially as a result of various risk factors including those described in the 10 k's 10 q's and eight ks. Vm ware files with the SEC, ladies and gentlemen, Sunjay Buddha for the jazz mafia from Oakland, California. Good to be with you. Welcome to late night with Jimmy Fallon. I'm an early early morning with Sanjay Poonen and two are set. It's the first time we're doing a live band and jazz and blues is my favorite. You know, I prefer a career in music, playing with Eric Clapton and that abandoned software, but you know, life as a different way. I'll things. I'm delighted to have you all here. Wasn't yesterday's keynote. Just awesome. Off the charts. I mean pat and Ray, you just guys, I thought it was the best ever keynote and I'm not kissing up to the two of you. If you know pat, you can't kiss up to them because if you do, you'll get an action item list at 4:30 in the morning that sten long and you'll be having nails for breakfast with him but bad it was delightful and I was so inspired by your tattoo that I decided to Kinda fell asleep in batter ass tattoo parlor and I thought one wasn't enough so I was gonna one up with. I love Vm ware. Twenty years. Can you see that? What do you guys think? But thank you all of you for being here. It's a delight to have you folks at our conference. Twenty 5,000 of you here, 100,000 watching. Thank you to all of the vm ware employees who helped put this together. Robin Matlock, Linda, Brit, Clara. Can I have you guys stand up and just acknowledge those of you who are involved? Thank you for being involved. Linda. These ladies worked so hard to make this a great show. Everybody on their teams. It's the life to have you all here. I know that we're gonna have a fantastic time. The title of my talk is pioneers of the possible and we're going to go through over the course of the next 90 minutes or so, a conversation with customers, give you a little bit of perspective of why some of these folks are pioneers and then we're going to talk about somebody who's been a pioneer in the world but thought to start off with a story. I love stories and I was born in a family with four boys and my parents I grew up in India were immensely creative and naming that for boys. The eldest was named Sanjay. That's me. The next was named Santosh Sunday, so if you can get the drift here, it's s a n, s a n s a n and the final one. My parents got even more creative and colon suneel sun, so you could imagine my mother going south or Sunday do. I meant Sanjay you and it was always that confusion and then I come to the United States as an immigrant at age 18 and people see my name and most Americans hadn't seen many Sundays before, so they call me Sanjay. I mean, of course it of sounds like v San, so sanjay, so for all of your V, San Lovers. Then I come to California for years later work at apple and my Latino friends see my name and it sorta sounds like San Jose, so I get called sand. Hey, okay. Then I meet some Norwegian friends later on in my life, nordics. The J is a y, so I get called San Year. Your my Italian friend calls me son Joe. So the point of the matter is, whatever you call me, I respond, but there's certain things that are core to my DNA. Those that people know me know that whatever you call me, there's something that's core to me. Maybe I like music more than software. Maybe I want my tombstone to not be with. I was smart or stupid that I had a big heart. It's the same with vm ware. When you think about the engines that fuel us, you can call us the VM company. The virtualization company. Server virtualization. We seek to be now called the digital foundation company. Sometimes our competitors are not so kind to us. They call us the other things. That's okay. There's something that's core to this company that really, really stands out. They're sort of the engines that fuel vm ware, so like a plane with two engines, innovation and customer obsession. Innovation is what allows the engine to go faster, farther and constantly look at ways in which you can actually make the better and better customer obsession allows you to do it in concert with customers and my message to all of you here is that we want to both of those together with you. Imagine if 500,000 customers could see the benefit of vsphere San Nsx all above cloud foundation being your products. We've been very fortunate and blessed to innovate in everything starting with Sova virtualization, starting with software defined storage in 2009. We were a little later to kind of really on the hyperconverged infrastructure, but the first things that we innovate in storage, we're way back in 2009 when we acquired nicer and began the early works in software defined networking in 2012 when we put together desktop virtualization, mobile and identity the first time to form the digital workspace and as you heard in the last few days, the vision of a multi cloud or hybrid cloud in a virtual cloud networking. This is an amazing vision couple that innovation with an obsession and customer obsession and an NPS. Every engineer and sales rep and everybody in between is compensated on NPS. If something is not going well, you can send me an email. I know you can send pat an email. You can send the good emails to me and the bad emails to Scott Dot Beto said Bmr.com. No, I'm kidding. We want all of you to feel like you're plugged into us and we're very fortunate. This is your vote on nps. We've been very blessed to have the highest nps and that is our focus, but innovation done with customers. I shared this chart last year and it's sort of our sesame street simple chart. I tell our sales rep, this is probably the one shot that gets used the most by our sales organization. If you can't describe our story in one shot, you have 100 powerpoints, you probably have no power and very The fact of the matter is that the data center is sort of like a human body. little point. You've got your heart that's Compute, you've got the storage, maybe your lungs, you've got the nervous system that's networking and you've got the brains of management and what we're trying to do is help you make that journey to the cloud. That's the bottom part of the story. We call it the cloud foundation, the top part, and it's all serving apps. The top part of that story is the digital workspace, so very simply put that that's the desktop, moving edge and mobile. The digital workspace meets the cloud foundation. The combination is a digital foundation Where does, and we've begun this revolution with a company. That's what we end. focus on impact, not just make an impression making an impact, and there's three c's that all of us collectively have had an impact on cost very clearly. I'm going to walk you through some of that complexity and carbon and the carbon data was just fascinating to see some of that yesterday, uh, from Pat, these fierce guarded off this revolution when we started this off 20 years ago. These were stories I just picked up some of the period people would send us electricity bills of what it looked like before and after vsphere with a dramatic reduction in cost, uh, off the tune of 80 plus percent people would show us 10, sometimes 20 times a value creation from server consolidation ratios. I think of the story goes right. Intel initially sort of fought vm ware. I didn't want to have it happen. Dell was one of the first investors. Pat Michael, do I have that story? Right? Good. It's always a job fulfilling through agree with my boss and my chairman as opposed to disagree with them. Um, so that's how it got started. And true with over the, this has been an incredible story. This is kind of the revenue that you've helped us with over the 20 years of existence. Last year was about a billion but I pulled up one of the Roi Charts that somebody wrote in 2006. collectively over a year, $50 million, It might've been my esteemed colleague, Greg rug around that showed that every dollar spent on vm ware resulted in nine to $26 worth of economic value. This was in 2006. So I just said, let's say it's about 10 x of economic value, um, to you. And I think over the years it may have been bigger, but let's say conservative. It's then that $50 million has resulted in half a trillion worth of value to you if you were willing to be more generous and 20. It's 1 trillion worth of value over the that was the heart. years. Our second core product, This is one of my favorite products. How can you not like a product that has part of your name and it. We sent incredible. But the Roi here is incredible too. It's mostly coming from cap ex and op ex reduction, but mostly cap x. initially there was a little bit of tension between us and the hardware storage players. Now I think every hardware storage layer begins their presentation on hyperconverged infrastructure as the pathway to the private cloud. Dramatic reduction. We would like this 15,000 customers have we send. We want every one of the 500,000 customers. If you're going to invest in a private cloud to begin your journey with, with a a hyperconverged infrastructure v sound and sometimes we don't always get this right. This store products actually sort of the story of the of the movie seabiscuit where we sort of came from behind and vm ware sometimes does well. We've come from behind and now we're number one in this category. Incredible Roi. NSX, little not so obvious because there's a fair amount spent on hardware and the trucks would. It looks like this mostly, and this is on the lefthand side, a opex mostly driven by a little bit of server virtualization and a network driven architecture. What we're doing is not coming here saying you need to rip out your existing hardware, whether it's Cisco, juniper, Arista, you get more value out of that or more value potentially out of your Palo Alto or load balancing capabilities, but what we're saying is you can extend the life, optimize your underlay and invest more in your overlay and we're going to start doing more and software all the way from the l for the elephant seven stack firewalling application controllers and make that in networking stack, application aware, and we can dramatically help you reduce that. At the core of that is an investment hyperconverged infrastructure. We find often investments like v San could trigger the investments. In nsx we have roi tools that will help you make that even more dramatic, so once you've got compute storage and networking, you put it together. Then with a lot of other components, we're just getting started in this journey with Nsx, one of our top priorities, but you put that now with the brain. Okay, you got the heart, the lungs, the nervous system, and the brain where you do three a's, sort of like those three c's. You've got automation, you've got analytics and monitoring and of course the part that you saw yesterday, ai and all of the incredible capabilities that you have here. When you put that now in a place where you've got the full SDDC stack, you have a variety of deployment options. Number one is deploying it. A traditional hardware driven type of on premise environment. Okay, and here's the cost we we we accumulate over 2,500 pms. All you could deploy this in a private cloud with a software defined data center with the components I've talked about and the additional cost also for cloud bursting Dr because you're usually investing that sometimes your own data centers or you have the choice of now building an redoing some of those apps for public cloud this, but in many cases you're going to have to add on a cost for migration and refactoring those apps. So it is technically a little more expensive when you factor in that cost on any of the hyperscalers. We think the most economically attractive is this hybrid cloud option, like Vm ware cloud and where you have, for example, all of that Dr Capabilities built into it so that in essence folks is the core of that story. And what I've tried to show you over the last few minutes is the economic value can be extremely compelling. We think at least 10 to 20 x in terms of how we can generate value with them. So rather than me speak more than words, I'd like to welcome my first panel. Please join me in welcoming on stage. Are Our guests from brinks from sky and from National Commercial Bank of Jamaica. Gentlemen, join me on stage. Well, gentlemen, we've got a Indian American. We've got a kiwi who now lives in the UK and we've got a Jamaican. Maybe we should talk about cricket, which by the way is a very exciting sport. It lasts only five days, but nonetheless, I want to start with you Rohan. You, um, brings is an incredible story. Everyone knows the armored trucks and security. Have you driven in one of those? Have a great story and the stock price has doubled. You're a cio that brings business and it together. Maybe we can start there. How have you effectively being able to do that in bridging business and it. Thank you Sanjay. So let me start by describing who is the business, right? Who is brinks? Brinks is the number one secure logistics and cash management services company in the world. Our job is to protect our customers, most precious assets, their cash, precious metals, diamonds, jewelry, commodities and so on. You've seen our trucks in your neighborhoods, in your cities, even in countries across the world, right? But the world is going digital and so we have to ratchet up our use of digital technologies and tools in order to continue to serve our customers in a digital world. So we're building a digital network that extends all the way out to the edges and our edges. Our branches are our messengers and their handheld devices, our trucks and even our computer control safes that we place on our customer's premises all the way back to our monitoring centers are processing centers in our data centers so that we can receive events that are taking place in that cash ecosystem around our customers and react and be proactive in our service of them and at the heart of this digital business transformation is the vm ware product suite. We have been able to use the products to successfully architect of hybrid cloud data center in North America. Awesome. I'd like to get to your next, but before I do that, you made a tremendous sacrifice to be here because you just had a two month old baby. How is your sleep getting there? I've been there with twins and we have a nice little gift for you for you here. Why don't you open it and show everybody some side that something. I think your two month old will like once you get to the bottom of all that day. I've. I'm sure something's in there. Oh Geez. That's the better one. Open it up. There's a Vm, wear a little outfit for your two month. Alright guys, this is great. Thank you all. We appreciate your being here and making the sacrifice in the midst of that. But I was amazed listening to you. I mean, we think of Jamaica, it's a vacation spot. It's also an incredible place with athletes and Usain bolt, but when you, the not just the biggest bank in Jamaica, but also one of the innovators and picking areas like containers and so on. How did you build an innovation culture in the bank? Well, I think, uh, to what rughead said the world is going to dissolve and NCB. We have an aspiration to become the Caribbean's first digital bank. And what that meant for us is two things. One is to reinvent or core business processes and to, to ensure that our customers, when they interact with the bank across all channels have a, what we call the Amazon experience and to drive that, what we actually had to do was to work in two moons. Uh, the first movement we call mode one is And no two, which is stunning up a whole set of to keep the lights on, keep the bank running. agile labs to ensure that we could innovate and transform and grow our business. And the heart of that was on the [inaudible] platform. So pks rocks. You guys should try it. We're going to talk about. I'm sure that won't be the last hear from chatting, but uh, that's great. Hey, now I'd like to get a little deeper into the product with all of you folks and just understand how you've engineered that, that transformation. Maybe in sort of the order we covered in my earlier comments in speech. Rohan, you basically began the journey with the private cloud optimization going with, of course vsphere v San and the VX rail environment to optimize your private cloud. And then of course we'll get to the public cloud later. But how did that work out for you and why did you pick v San and how's it gone? So Sunday we started down this journey, the fourth quarter of 2016. And if you remember back then the BMC product was not yet a product, but we still had the vision even back then of bridging from a private data center into a public cloud. So we started with v San because it helped us tackle an important component of our data center stack. Right. And we could get on a common platform, common set of processes and tools so that when we were ready for the full stack, vmc would be there and it was, and then we could extend past that. So. Awesome. And, and I say Dave with a name like Dave Matthews, you must have like all these musicians, like think you're the real date, my out back. What's your favorite Dave Matthew's song or it has to be crashed into me. Right. Good choice rash. But we'll get to music another time. What? NSX was obviously a big transformational capability, February when everyone knows what sky and media and wireless and all of that stuff. Networking is at the core of what you do. Why did you pick Nsx and what have you been able to achieve with it? So I mean, um, yeah, I mean there's, like I say, sky's yeah, maybe your organization. It's incredibly fast moving industry. It's very innovative. We've got a really clever people in, in, in, in house and we need to make sure our product guys and our developers can move at pace and yeah, we've got some great. We've got really good quality metric guys. They're great guys. But the problem is that traditional networking is just fundamentally slow is there's, there's not much you can do about it, you know, and you know to these agile teams here to punch a ticket, get a file, James. Yeah. That's just not reality. We're able to turn that round so that the, the, the devops ops and developers, they can just use terraform and do everything. Yeah, it's, yeah, we rigs for days to seconds and that's in the Aes to seconds with an agile software driven approach and giving them much longer because it would have been hardware driven. Absolutely. And giving the tool set to the do within boundaries. You have scenes with boundaries, developers so they can basically just do, they can do it all themselves. So you empower the developers in a very, very important way. Within a second you had, did you use our insight tools too on top of that? So yes, we're considered slightly different use case. I mean, we're, yeah, we're in the year. You've got general data protection regulations come through and that's, that's, that's a big deal. And uh, and the reality is from what an organization's compliance isn't getting right? So what we've done been able to do is any convenience isn't getting any any less, using vr and ai and Nsx, we're able to essentially micro segment off a lot of Erica our environments which have a lot, much higher compliance rate and you've got in your case, you know, plenty of stores that you're managing with visa and tens of thousands of Vms to annex. This is something at scale that both of you have been able to achieve about NSX and vsn. Pretty incredible. And what I also like with the sky story is it's very centered around Dev ops and the Dev ops use case. Okay, let's come to your Ramon. And obviously I was, when I was talking to the Coobernetti's, uh, you know, our Kubernetes Platform, team pks, and they told me one of the pioneer and customers was National Commercial Bank of Jamaica. I was like, wow, that's awesome. Let's bring you in. And when we heard your story, it's incredible. Why did you pick Coobernetti's as the container platform? You have many choices of what you could have done in terms of companies that are other choices. Why did you pick pks? So I think, well, what happened to, in our interviews cases, we first looked at pcf, which we thought was a very good platform as well. Then we looked at the integration you can get with pqrs, the security, the overland of Nsx, and it made sense for us to go in that direction because you offered 11 team or flexibility on our automation that we could drive through to drive the business. So that was the essence of the argument that we had to make. So the key part with the NSX integration and security and, and the PKS. Uh, and while we've got a few more chairs from the heckler there, I want you to know, Chad, I've got my pks socks on. That's how much I had so much fear. And if he creates too much trouble with security, we can be emotional. I'm out of the arena, you know. Anyway. Um, I wanted to put this chart up because it's very important for all of you, um, and the audience to know that vm ware is making a significant commitment to Coobernetti's. Uh, we feel that this is, as pat talked about it before, something that's going to be integrated into everything we do. It's going to become like a dial tone. Um, and this is just the first of many things you're going to see a vm or really take this now as a consistent thing. And I think we have an opportunity collectively because a lot of people think, oh, you know, containers are a threat to vm ware. We actually think it's a headwind that's going to become a tailwind for us. Just the same way public cloud has been. So thank you for being one of our pioneer and early customers. And Are you using the kubernetes platform in the context of running in a vsphere environment? Yes, we are. We're onto Venice right now. Uh, we have. Our first application will be a mobile banking APP which will be launched in September and all our agile labs are going to be on pbs moving forward medic. So it's really a good move for us. Dave, I know that you've, not yet, I mean you're looking in the context potentially about is your, one of the use cases of Nsx for you containers and how do you view Nsx in that? Absolutely. For us that was the big thing about t when it refresh rocked up is that the um, you know, not just, you know, Sda and on a, on vsphere, but sdn on openstack sdn into their container platform and we've got some early visibility of the, uh, of the career communities integration on there and yeah, it was, it was done right from the start and that's why when we talked to the pks Yeah, it's, guys again, the same sort of thing. it's, it's done right from the start. And so yeah, certainly for us, the, the NSX, everywhere as they come and control plane as a very attractive proposition. Good. Ron, I'd like to talk to you a little bit about how you viewed the public, because you mentioned when we started off this journey, we didn't have Mr. Cloud and aws, we approached to when we were very early on in that journey and you took a bet with us, but it was part of your data center reduction. You're kind of trying to almost to obliterate one data center as you went from three to one. Tell us that story and how the collaboration worked out on we amber cloud. What's the use case? So as I said, our vision was always to bridge to a So we wanted to be able to use public cloud environments to incubate new public cloud, right? applications until they stabilize to flex to the cloud. And ultimately disaster recovery in the cloud. That was the big use case for us. We ran a traditional data center environment where, you know, we run across four regions in the world. Each region had two to three data centers. One was the primary and then usually you had a disaster recovery center where you had all your data hosted, you had certain amount of compute, but it was essentially a cold center, right? It, it sat idle, you did your test once a year. That's the environment we were really looking to get out of. Once vmc was available, we were able to create the same vm ware environment that we currently have on prem in the cloud, right? The same network and security stack in both places and we were actually able to then decommission our disaster recovery data center, took it off, it's took it off and we move. We've got our, our, all of our mission critical data now in the, uh, in the, uh, aws instance using BMC. We have a small amount of compute to keep it warm, but thanks to the vm ware products, we have the ability now to ratchet that up very quickly in a Dr situation, run production in the cloud until we stabilized and then bring that workload back. Would it be fair to tell everybody here, if you are looking at a Dr or that type of bursting scenario, there's no reason to invest in a on premise private cloud. That's really a perfect use case of We, I know certainly we had breaks. this, right? Sorry. Exactly. Yeah. We will no longer have a, uh, a physical Dr a center available anywhere. So you've optimized your one data center with the private cloud stack will be in cloud foundation effectively starting off a decent and you've optimized your hybrid cloud journey, uh, with we cloud. I know we're early on in the journey with Nsx and branch, so we'll come back to that conversation may next year we discover new things about this guy I just found out last night that he grew up in the same town as me in Bangalore and went to the same school. So we will keep a diary of the schools at rival schools, but the last few years with the same school, uh, Dave, as you think about the future of where you want to this use case of network security, what are some of the things that are on your radar over the course of the next couple of months and quarters? So I think what we're really trying to do is, um, you know, computers, this is a critical thing decided technology conference, computers and networks are a bit boring, but rather we want to make them boring. We want to basically sweep them away from so that our people, our customers, our internal customers don't have to think about it were the end that we can make him, that, that compliance, that security, that whole, that whole framework around it. Um, regardless of where that work, right live as living on premise, off premise, everywhere you know. And, and even Aisha potentially out out to the edge. How big were your teams? Very quickly, as we wrap up this, how big are the teams that you have working on network is what was amazing. I talked to you was how nimble and agile you're with lean teams. How big was your team? The, the team during the, uh, the SDDC stack is six people. Six, six. Eight. Wow. There's obviously more that more. And we're working on that core data center and your boat to sleep between five and seven people. For it to brad to both for the infrastructure and containers. Yes. Rolling on your side. It's about the same. Amazing. Well, very quickly maybe 30 seconds. Where do you see the world going? Rolling. So, you know, it brings, I pay attention to two things. One is Iot and we've talked a little bit about that, but what I'm looking for there as digital signals continue to grow is injecting things like machine learning and artificial intelligence in line into that flow back so we can make more decisions closer to the source. Right. And the second thing is about cash. So even though cash volume is increasing, I mean here we are in Vegas, the number one cash city in the US. I can't ignore the digital payments and crypto currency and that relies on blockchain. So focusing on what role does blockchain play in the global world as we go forward and how can brings, continue to bring those services, blockchain and Iot. Very rare book. Well gentlemen, thank you for being with us. It's a pleasure and an honor. Ladies and gentlemen, give it up for three guests. Well, um, thank you very much. So as you saw there, it's great to be able to see and learn from some of these pioneering customers and the hopefully the lesson you took away was wherever your journey is, you could start potentially with the private cloud, embark on the journey to the public cloud and then now comes the next part which is pretty exciting, which is the journey off the desktop and removal what digital workspace. And that's the second part of this that I want to explore with a couple of customers, but before I do that, I wanted to set the context of why. What we're trying to do here also has economic value. Hopefully you saw in the first set of charts the economic value of starting with the heart, the lungs, any of that software defined data center and moving to the ultimate hybrid cloud had economic value. We feel the same thing here and it's because of fundamental shift that started off in the last seven, 10 years since iphone. The fact of the matter is when you look at your fleet of your devices across tablets, phones and laptops today is a heterogeneous world. Twenty years ago when the company started, it was probably all Microsoft devices, laptops now phones, tablets. It's a mixture and it was going to be a mixture for the rest of them. I think for the foreseeable time, with very strong, almost trillion market cap companies and in this world, our job is to ensure that heterogeneous digital workspace can be very easily managed and secured. I have a little soft corner for this business because the first three years of my five years here, I ran this business, so I know a thing about these products, but the fact of the matter is that I think the opportunity here is if you think about the 7 billion people in the world, a billion of them are working for some company or the other. The others are children or may not be employed or retired and every one of them have a phone today. Many of them phones and laptops and they're mixed and our job is to ensure that we bring simplicity to this place. You saw a little bit that cacophony yesterday and Pat's chart, and unfortunately a lot of today's world of managing and securing that disparate is a mountain of morass. Okay? No offense to any of the vendors named in there, but it shouldn't be your job to be that light piece of labor at the top of the mountain to put it all together, which costs you potentially at least $50 per user per month. We can make the significantly cheaper with a unified platform, workspace one that has all of those elements, so how have we done that? We've taken those fundamental principles at 70 percent, at least reduction of simplicity and security. A lot of the enterprise companies get security, right, but we don't get simplicity all always right. Many of the consumer companies like right? But maybe it needs some help and facebook, it's simplicity, security and we've taken both of those and said it is possible for you to actually like your user experience as opposed to having to really dread your user experience in being able to get access to applications and how we did this at vm ware, was he. We actually teamed with the Stanford Design School. We put many of our product managers through this concept of design thinking. It's a really, really useful concept. I'd encourage every one of you. I'm not making a plug for the Stanford design school at all, but some very basic principles of viability, desirability, feasibility that allow your product folks to think like a consumer, and that's the key goal in undoing that. We were able to design of these products with the type of simplicity but not compromise at all. Insecurity, tremendous opportunity ahead of us and it gives me great pleasure to bring onstage now to guests that are doing some pioneering work, one from a partner and run from a customer. Please join me in welcoming Maria par day from dxc and John Market from adobe. Thank you, Maria. Thank you Maria and John for being with us. Maria, I want to start with you. A DXC is the coming together of two companies and CSC and HP services and on the surface on the surface of it, I think it was $50,000, 100,000. If it was exact numbers, most skeptics may have said such a big acquisition is probably going to fail, but you're looking now at the end of that sort of post merger and most people would say it's been a success. What's made the dxc coming together of those two very different cultures of success? Well, first of all, you have to credit a lot of very creative people in the space. One of the two companies came together, but mostly it is our customers who are making us successful. We are choosing to take our customers the next generation digital platform. The message is resonating, the cultures have come together, the individuals have come together, the offers have come together and it's resonating in the marketplace, in the market and with our customers and with our partners. So you shouldn't have doubted it. I, I wasn't one of the skeptics, maybe others were. And my understanding is the d and the C Yes. If, and dxc is the digital and customer. if you look at the logo, it's, it's more of an infinity, so digital transformation for customers. But truthfully it's um, we wanted to have a new start to some very powerful companies in the industry and it really was a instead of CSC and HP, a new logo and a new start. And I think, you know, if this resonates very well with what I started off my keynote, which is talking about innovation and customers focused on digital and Adobe, obviously not just a household name, customers, John, many of folks who use your products, but also you folks have written the playbook on a transformation of on premise going cloud, right? A SAS products and now we've got an incredible valuations relative. How has that affected the way you think in it in terms of a cloud first type of philosophy? Uh, too much of how you implement, right? From an IT perspective, we're really focused on the employee experience. And so as we transitioned our products to the cloud, that's where we're working towards as well from an it, it's all about innovation and fostering that ability for employees to create and do some amazing products. So many of those things I talked about like design thinking, uh, right down the playbook, what adobe does every day and does it affect the way in which you build, sorry, deploy products 92. Yeah, I mean fundamentally it comes down to those basics viability and the employee experience. And we've believe that by giving employees choice, we're enabling them to do amazing work. Rhonda, Maria, you obviously you were in the process of rolling out some our technology inside dxc. So I want to focus less on the internal implementation as much as what you see from other clients I shared sort of that mountain of harassed so much different disparate tools. Is that what you hear from clients and how are you messaging to them, what you think the future of the digital workspaces. And I joined partnership. Well Sanjay, your picture was perfect because if you look at the way end user compute infrastructure had worked for years, decades in the past, exactly what we're doing with vm ware in terms of automation and driving that infrastructure to the cloud in many ways. Um, companies like yours and mine having the courage to say the old way of on prem is the way we made our license fees, the way move made our professional services in the past. And now we have to quickly take our customers to a new way of working, a fast paced digital cloud transformation. We see it in every customer that we're dealing with everyday of the week What are some of the keyboard? Every vertical. I mean we're, we're seeing a lot in the healthcare and in a variety of verticals. industry. I'm one of the compelling things that we're seeing in the marketplace right now is the next gen worker in terms of the GIG economy. I'm employees might work for one company at 10:00 in the morning and another company at We have to be able to stand those employees are 10 99 employees up very 2:00 in the afternoon. quickly, contract workers from around the world and do it securely with governance, risk and compliance quickly. Uh, and we see that driving a lot of the next generation infrastructure needs. So the users are going from a company like dxc with 160,000 employees to what we think in the future will be another 200, 300,000 of 'em, uh, partners and contract workers that we still have to treat with the same security sensitivity and governance of our w two employees. Awesome. John, you were one of the pioneer and customers that we worked with on this notion of unified endpoint management because you were sort of a similar employee base to Vm ware, 20,000 odd employees, 1000 plus a and you've got a mixture of devices in your fleet. Maybe you can give us a little bit of a sense. What percentage do you have a windows and Mac? So depending on the geography is we're approximately 50 percent windows 50 slash 50 windows and somewhat similar to how vm ware operates. What is your fleet of mobile phones look like in terms of primarily ios? We have maybe 80 slash 20 or 70 slash 20 a apple and Ios? Yes. Tablets override kinds. It's primarily ios tablets. So you probably have something in the order of, I'm guessing adding that up. Forty or 50,000 devices, some total of laptops, tablets, phones. Absolutely split 60 slash 60,000. Sixty thousand plus. Okay. And a mixture of those. So heterogeneities that gear. Um, and you had point tools for many of those in terms of managing secure in that. Why did you decide to go with workspace one to simplify that, that management security experience? Well, you nailed it. It's all about simplification and so we wanted to take our tools and provide a consistent experience from an it perspective, how we manage those endpoints, but also for our employee population for them to be able to have a consistent experience across all of their devices. In the past it was very disconnected. It was if you had an ios device, the experience might look like this if you had a window is it would look like go down about a year ago is to bring that together again, this. And so our journey that we've started to simplicity. We want to get to a place where an employee can self provision their desktop just like they do their mobile device today. And what would, what's your expectations that you go down that journey of how quickly the onboarding time should, should be for an employee? It should be within 15, 20 minutes. We need to, we need to get it very rapid. The new hire orientation process needs to really be modified. It's no longer acceptable from everything from the it side ever to just the other recruiting aspects. An employee wants to come and start immediately. They want to be productive, they want to make contributions, and so what we want to do from an it perspective is get it out of the way and enable employees to be productive as And the onboarding then could be one way you latch him on and they get workspace quickly as possible. one. Absolutely. Great. Um, let's talk a little bit as we wrap up in the next few minutes, or where do you see the world going in terms of other areas that are synergistic, that workspace one collaboration. Um, you know, what are some of the things that you hear from clients? What's the future of collaboration? We're actually looking towards a future where we're less dependent on email. So say yes to that real real time collaboration. DXC is doing a lot with skype for business, a yammer. I'll still a lot with citrix, um, our tech teams and our development teams use slack and our clients are using everything, so as an integrator to this space, we see less dependent on the asynchronous world and a lot more dependence on the synchronous world and whatever tools that you can have to create real time. Um, collaboration. Now you and I spoke a little last night talking about what does that mean to life work balance when there's always a demanding realtime collaboration, but we're seeing an uptick in that and hopefully over the next few years a slight downtick in, in emails because that is not necessarily the most direct way to communicate all the time. And, and in that process, some of that sort of legacy environment starts to get replaced with newer tools, whether it's slack or zoom or we're in a similar experience. All of the above. All of the above. Are you finding the same thing, John Environment? Yeah, we're moving away. There's, I think what you're going to see transition is email becomes more of the reporting aspect, the notification, but the day to day collaboration is me to products like slack are teams at Adobe. We're very video focused and so even though we may be a very global team around the world, we will typically communicate over some form of video, whether it be blue jeans or Jabber or Blue Jeans for your collaboration. Yeah. whatnot. We've internally, we use Webex and, and um, um, and, and zoom in and also a lot of slack and we're happy to announce, I think at the work breakouts, we'll hear about the integration of workspace one with slack. We're doing a lot with them where I want to end with a final question with you. Obviously you're very passionate about a cause that we also love and I'm passionate about and we're gonna hear more about from Malala, which is more women in technology, diversity and inclusion and you know, especially there's a step and you are obviously a role model in doing that. What would you say to some of the women here and others who might be mentors to women in technology of how they can shape that career? Um, I think probably the women here are already rocking it and doing what you need to do. So mentoring has been a huge part of my career in terms of people mentoring me and if not for the support and I'm real acceptance of the differences that I brought to the workplace. I wouldn't, I wouldn't be sitting here today. So I think I might have more advice for the men than the women in the room. You're all, you have daughters, you have sisters, you have mothers and you have women that you work every day. Um, whether you know it or not, there is an unconscious bias out there. So when you hear things from your sons or from your daughters, she's loud. She's a little odd. She's unique. How about saying how wonderful is that? Let's celebrate that and it's from the little go to the top. So that would be, that would be my advice. I fully endorse that. I fully endorse that all of us men need to hear that we have put everyone at Vm ware through unconscious bias that it's not enough. We've got to keep doing it because it's something that we've got to see. I want my daughter to be in a place where the tech world looks like society, which is not 25, 30 percent. Well no more like 50 percent. Thank you for being a role model and thank you for both of you for being here at our conference. It's my pleasure. Thank you Thank you very much. Maria. Maria and John. So you heard you heard some of that and so that remember some of these things that I shared with you. I've got a couple of shirts here with these wonderful little chart in here and I'm not gonna. Throw it to the vm ware crowd. Raise your hand if you're a customer. Okay, good. Let's see how good my arm is. There we go. There's a couple more here and hopefully this will give you a sense of what we are trying to get done in the hybrid cloud. Let's see. That goes there and make sure it doesn't hit anybody. Anybody here in the middle? Right? There we go. Boom. I got two more. Anybody here? I decided not to bring an air gun in. That one felt flat. Sorry. All. There we go. One more. Thank you. Thank you. Thank you very much, but this is what we're trying to get that diagram once again is the cloud foundation. Folks. The bottom part, done. Very simply. Okay. I'd love a world one day where the only The top part of the diagram is the digital workspace. thing you heard from Ben, where's the cloud foundation? The digital workspace makes them cloud foundation equals a digital foundation company. That's what we're trying to get done. This ties absolutely a synchronously what you heard from pat because everything starts with that. Any APP, a kind of perspective of things and then below it are these four types of clouds, the hybrid cloud, the Telco Cloud, the cloud and the public cloud, and of course on top of it is device. I hope that this not just inspired you in terms of picking up a few, the nuggets from our pioneers. The possible, but every one of the 25,000 view possible, the 100,000 of you who are watching this will take people will meet at all the vm world and before forums. the show on the road and there'll be probably 100,000 We want every one of you to be a pioneer. It is absolutely possible for that to happen because that pioneering a capability starts with every one of you. Can we give a hand once again for the five customers that were onstage with us? That's great.

>> Voiceover: Live, from Atlanta, Georgia, it's theCUBE. Covering IFS World Conference 2018. Brought to you by, IFS. >> Rebecca: Welcome back to theCUBE's live coverage of IFS World Conference 2018 here in Atlanta, Georgia. I'm your host, Rebecca Knight, along with my co-host, Jeff Frick. It's been a great day here. >> Jeff: Yes. >> We've had a lot of wonderful conversations, great panels. Last one to go, you can tell the atmosphere is getting... >> They're wheeling out all the alcohol I think... >> Exactly. Exactly. >> ...for the reception this evening. >> But we have saved best for last. We have Dan Matthews, who is the CTO of IFS and Bas De Vos who is the Director of IFS Labs. So Bas and Dan, thanks so much for joining us. >> Thank you. >> You're welcome. >> So, when I talked, we've heard a lot about IFS Apps 10, and this is the big news, but what we haven't talked about too much is Arena. Can you describe to our viewers this new user experience, and what it means? >> Alright, well, IFS Arena, like you said, it's a new user experience via past applications, and that's something that's really important to us because it's important to our customers. Because what they want to do is, they want to put great tools in the hands of the people, right? And we all know when it comes to software, how great a tool is is a large part down to the user experience, so that's why we've done it. And what we've done is create something that we think is more inspired by really well-designed consumer software, but we've adapted that for these big enterprise applications like we are doing. >> It's pretty amazing in your keynote because you showed, I think five different UI's based on different devices in the prior versions, where now you're coming to kind of a standardized single (mumbles) experience across various platforms or across various devices to actually interact with the applications. That's got to be, feel good to get that down to kind of one responsive design. >> And to a degree, that's just rescinding to reality because you used to think about, you had your PC and you had a way of doing that. And then you go to your mobile app, or maybe, I mean, people are using so many different kinds devices today. So if we were to purpose build something just for your iPad, something for your phone, something for this, something for your TV, we'd be stuck forever, right? So what we did instead, is we said, "Let's build one experience that actually adapts "to all these different environments, "and get that really, really well." It's not that easy, but in the end, it's a much better way of approaching it. >> Right, and I thought the part that I liked was as when you're new to something, you don't necessarily want a high density of information in a screen or whatever, 'cause you're just not sure, you're learning, whatever, it's new. But then as you become more experienced, obviously your comfort zone goes up, you want a lot more dense information, and really, in your work platform you demoed earlier today, you have a lot of options whether you want kind of the more consumery, more picturey, less efficient way, or do you want the "I know this well, "and I want the thick content." >> And what we basically does, we flipped it upside down, 'cause if you look at Enterprise Software, and ERP, and has to management this kind of stuff, it always used to be designed for the professional, right? And then you would try to simplify it for the newbies that're coming into the business. Can we remove some things, hide some things away, configure some things? Now we've done it the other way around. So the default is it's designed for the novice person that's just coming in seeing this for the first time. And then as you learn, as you say, you can expand and grow, and they get sort of more rich in the data you're seeing. And this is really, really important right? Because people aren't staying that long in the jobs anymore. So if you think about people moving around, they know the business, but they might not know the business applications, so they basically come in, I'm a purchasing guy, come in, pick up the purchasing system directly, that's really really important. >> Needs to be intuitive? >> Yeah, make it intuitive first, and then progressively let people discover more, rather than give all the options and all the complexity and then expect them to simplify it. That's harder. >> So, Bas, I want to talk to you a little bit about the development process and how you come up with these kind of things. Can you describe how it works at IFS Labs, what approach you take? >> Yeah of course, and then perhaps Dan can add to this a little bit later as well. But because IFS Labs is just a part of the process, right? But if you look in our general development process, for us, it's very important to stay close to our customers, right? What do our customers need today? What do they need tomorrow? And we have to basically be able to deliver functionality they need for their problems right on time. And IFS Labs plays a part in that. We are basically (mumbles) for sending before that. So we approach it a little bit the other way around. So instead of looking at a customer problem and trying to find a solution for that, we basically look ahead. We look a couple of years in the future. What kind of technologies are coming up? What kind of possibilities are there, and can we find a problem for it? And that sounds strange, right? Because we're known in the business of finding problems. But it does allow us to experiment and come up with innovative solutions that might work for tomorrow. But before we actually move that into production, or hand it over to regular R&D development, well we do step back and go to our customers and say, "Hey wait a minute, this is what we are thinking Labs, "what do you think about that? "Does it work for you, does it help you?" and validate it with them. >> So it's an interesting challenge for Labs, for looking down the road, because, and Steve Jobs' famous quote, that we don't necessarily deliver just what our customers ask for. They're not asking for things that are down the road, so you got that responsibility to look down the road. On the other hand, nobody likes technology that doesn't have a problem to solve. So you got to be delicate. Because if you just build something for the sake of building something, maybe there's some ancillary value. But at the end of the day, someone's got to use it and they got to drive direct values. So how do you kind of play that balance beyond, "Yes we listen to customers, "but there's this other stuff coming "that maybe they're not too aware of"? >> Yeah that's true, totally true, I completely agree with you. And I think that is the role of IFS Labs, right? So if we look in the overall process, the fact that we have a Labs, we don't... A license to experiment with trying out stuff, validating it with our customers, we can basically... Try it out before we actually take a decision to build something that our customers are not waiting for. So exactly the problem you just sketched, I think that our interest, IFS Labs, to resolve that. >> We have seen this happening throughout history, right? So if you look at how IET started, for us, it started with a product in IFS labs, when together we want a customer learning and understanding how they should be applied to the kind of businesses and industries that we serve. And then it went into mainstream R&D development and then we have real solutions, and now we have customers, who've been live for years, using this kind of stuff. So that is exactly the process you want to have. Try it out, and when we have a grasp on how this relates to our customers, then we up the next level of investment and take it further. >> And then, similarly, we had a project in IFS Labs that, well we tried out, and after a couple of months or even longer we said, "This is not going to work "for our customers, it's actually not helping them today. "Might be a couple years from now, but today let's stop it." >> So was this how your kind of integration of AI and machine learning into the applications took place? You looked forward, this is a cool new thing we need to play, but at the same time, we're not going to name it after a smart dead guy. (group laughing) But really bake it into the applications where it makes the most sense. And that sounds like it's kind of your execution strategy. >> Yeah definitely and AIs are a very, very, very big topic, right? It's an umbrella for so many different types of applications. Dan was talking this morning about three main areas where we think AI makes most sense for our products. It's basically human-machine interaction, predictive maintenance and service, an automation. But each of those areas, they basically have their own... Own life cycle, right? So if you look at human-machine interaction, at the morning. This morning we were talking about the IFS Arena bot. We're actually in a proper development phase. So that's much further ahead in that cycle, while other AI related topics like doing mass-automation, only your (mumbles), that's earlier in the cycle and that's still in Labs. So although AI is a big umbrella topic, the different topics in there follow that same approach. >> Can you be a little more specific about the projects you're working on, or is it top secret? >> At the World Conference everybody wants to know our secrets, but luckily, at World Conference we share them. >> Jeff: This is between us four. >> Yeah nobody's listening, right? Or watching? (laughs) So yeah at this World Conference we're hosting an innovation area. And in the innovation area, we're showcasing a wide range of basically possible technologies and how you could apply them to future business. We basically took the approach of depicting an end-to-end automatous business. So basically go all the way from mining stuff, in a mine in the ground, to using that in a factory, to producing products for the customer. And we basically build all kinds of technologies in there to make that completely automatous. Might not all be possible today, but it's really there to inspire our customers to look ahead. Some examples of the things we're using, a block chain inside enterprisesque management, mixed reality with Microsoft HoloLens to do service repairs, digital twins in virtual reality, automatous vehicles. So there's a lot of interesting stuff going on there. >> That's great, those are the great buzzwords but you put them all within application, and they're just standalone. >> Dan: What it does really well, is it kind of illustrates how these technologies are used in context... >> Right. >> Dan: With all of these things. >> That's super. >> You are an IFS veteran, >> Yes. >> You came as a developer and now here you are, CTO. Tell our viewers a little bit about how the company has changed in your opinion, and also now as you are sort of making a bigger push into North America, what we can expect. >> Well, what else changed, if I go back and I've not been with this company for more than 20 years. But what I've seen is we've got a lot more professional. Of course, we're a big organization now, and the way we run things and the way the business is run is a lot more professional. If you go back to the late '90s, this was before the dot-com boom, everybody was pouring money into the IT industry, so that was not an objective. So we were doing R&D but we were also burning money. And I think after that bubble burst, we all learned to become proper business people as well. I'll tell you one that hasn't changed, though, and that really is the kind of atmosphere that is within the company, right? How close we are to our customers, and how the customers reality always comes first and how we all help each other support. That really hasn't changed despite the fact we're so much bigger and we're 20 years old and all that kind of stuff. >> So why do you think is it 'cause maintaining culture is really, really difficult and we go to a lot of shows and we often talk about if it's a founder-led, and if they're a good CEO to double benefit, to keep that culture, but when you got turned over at the top, how do you maintain the culture that you guys have built? >> I think in the beginning, I think it was a lot of that founder-led, right? It was really led by the founders and one of the founders was our CEO for many, many years. But then it kind of got ingrained a little bit, between the Scandinavia culture. That it's quite open, quite sort of friendly, helpful, lots of hierarchical. And that then sort of spread out as the business expanded into nationally. And we kept it also on the R&D side. We do a lot of R&D in Chalinka for example. Which has a surprisingly similar feeling in the culture, actually. So I think it just got so big and so strong in the company, that it just naturally, new people come in and naturally sort of carry on with that same way of being that we've had it before. >> Rebecca: They adopted and embraced it. >> Because that was the end, Dan said when he was doing his due diligence, right? The culture was a huge piece of why he came to the company. >> I think if they were the other way around, we have seen that when we brought businesses in as well, that is, right, these guys have a similar culture to us, great, fantastic business to bring into to the IFS family. >> Jeff: Sir, you were going to say? >> I was going to say, in the end also, you're attracting people to your company and the people that are staying are also the people that feel at at home, and that feel comfortable, and that feel, I'm a little bit shorter than Dan inside the company for two years now. But basically, I feel the same with the culture, right? And it fits me as a person, and therefore I think I'm inclined to stay longer at IFS than if the culture would not fit me. And as you attract people with the same mindset together. It only gets stronger. >> Right, well Dan and Bas, thank you so much. This has been really fun last panel of the day, so we appreciate it. >> Thank you. >> Good luck on your keynote on Thursday. >> Bas: Thank you very much. >> I'm Rebecca Knight for Jeff Frick. This has been IFS World Conference 2018. We will have more after this. (light techno music)

>> Announcer: Live from Atlanta, Georgia, it's the Cube. Covering IFS World Conference 2018. Brought to you by IFS. >> Welcome back to the Cube's live coverage of IFS World Conference 2018 here in Atlanta, Georgia. I'm your host, Rebecca Knight. We have a three-guest panel with us today. We have Mark Boulton who is the CMO, Antony Bourne, vice-president Global Industries Solutions, and Brian Sommer who is an analyst at TechVentive. Thank you so much for joining us, gentlemen. I really appreciate it. >> Happy to be here, thank you. >> Happy to be here, yeah. >> So this is a big, big event for IFS, WOCO, as it's known. So talk a little bit about what you're hearing already from customers and feedback that you're getting. >> Sure, well the first thing is that everyone's told us Atlanta was a great choice of venue. >> Rebecca: This time of year in particular. >> Well, just flown in actually, from London where the weather is not this good. But, we've had really good feedback so far and still only at the end of the first morning. But the opening keynotes and the reveal of IFS Apps 10 went really well. I think most people have been really pleased with the content that they're seeing on the whole. So feedback is good. We know it's a big investment in time and time out of the office for our customers to come here. So we need to make sure that it's time well spent, that they get value. And so far, the feedback is really good. They're learning stuff, they're seeing things for the first time. They're meeting their peers and connecting. So it's good. >> And before the cameras were rolling, we were talking about the customers interacting with each other. Not only just you and telling you how they're using your product, but also interacting with each other and talking about things that they have learned and sites that they have gleaned. So can you describe a little bit about what's happening? >> And that's a key thing because we love our customers, we love getting them together, we love them talking to each other. It's not just taking it from our words and taking it for granted, we want them to share the experience, we want them to say, okay, what to do in this scenario? How did you overcome this? So these events are fantastic. I've just been talking to a customer, now, before lunch, about how they want to upgrade based on what they've already seen. And we're only halfway through day one. And it's just like, I want to talk to my account manager, I want a meeting about what we're going to do and when we're going to be doing it. So it's a fantastic event, fantastic. >> So, how about you? What are you seeing in terms of this new release with IFS 10. I mean, what interests you most as an analyst? >> Well, I've got some clients who specifically ask me to be on the lookout for some things over here at today's show. And one of them was around the new user experience on release 10 product. They're looking for something that's a richer web-based kind of mobile type of experience, or consumer-user interface experience for them. And I think they'll be happy with what's been announced over here today. It will come out in phases, obviously, but it works on everything now. Every kind of device and that's what the client wanted to see. And I'll report that back. >> Just to echo what Brian said, we've had customers already contacting us about because there is a certain functionality which we've introduced to IFS Applications 10, which they really, really want so they've actually said okay even before we announced it, which we let them have some indication of what was happening and they said, we need that, we want that. So its future is looking really good for upgrades, as well as new customers. >> One of the things that we keep hearing a lot of how customer-focused, how customer-centric IFS is as a company. The metrics speak for themselves in terms of your NPS scores and the Gartner insights. So how, as CMO, how are you going to get the word out, really? Because IFS is kind of known one of the best kept secrets in the industry. >> And it's true that we don't have quite the brand recognition that maybe some of the huge, massive competitors have. But, within our industries, we are very well known and we're known for all the right things. Great products, well-implemented and well-supported. We are leaders in a lot of the markets in which we play. Events like this is actually one of the key objectives for us. Is to have a good presence from analysts and journalists, the influencers, we call them. We like to think we look after them very well. They get the inside track on things that we're working on. So we use a lot of tools to actually spread the word. But, our biggest advocates are our customers. The people that have our software and have worked with us, they genuinely do love the products. And for those that were in the main room this morning when we launched-- Dan Matthews, our CTO, he said one of our core objectives is to design a product that people love. And so literally our customers will go out, as our NPS scores indicate as you mentioned, they will do the job for us. They tell people; they tell them very positive things about their experience. We did some studies. The majority of our customers actually are more profitable than people than use our competitor products. They're must faster time to solution and things like that. So these are the things that our customers are saying about us and these are good things to be talked about for. >> Right. Brian, what would you say should be keeping companies up at night. I mean, IFS is doing a lot of the right things. As you said, you're going to report back, the customer will probably be happy with what they hear. But what are some of the things that maybe customers are saying or customers are needing that you're hearing? That kind of feedback that maybe IFS-- what would be sort of your best advice for the future? >> Well, I think IFS plays in a bunch of different parts of the world. There is no single answer that will solve every customer in every part of the planet. And there are some very realistic problems that some companies have in areas where there's spotty electric power, or spotty internet access, and the like. They're going to probably continue to want a non-premise kind of solution. There are others in developing countries where they've clearly bypassed an entire generation, or two, of technology and they want to straight into cloud. And I know these guys, they've got a number of different cloud modules, or applications, in field services, one of those areas. And field service is a great one for the cloud, simply because that's what business is all about. It's about a bunch of people carrying tablets, and cell phones, smart phones, whatever, in and out of customer locations. That's fine. But by-and-large, what do the clients want? Well, I think what they want more than anything nowadays, they want to get out of the data-center business and more and more clients are looking at utility computing. And they're expecting vendors, eventually, to get them out of maintaining and running data centers because they have more confidence that vendors, and or partner technology provider can do a better job at web-security, maybe, than they could in-house by themselves. >> Just to echo that. >> I think one of the key differentiators from the IFS offering is the fact that we give our customers choice. We say, what do you want? We have the solution for you. Do you want it on prem? Do you want is SAS? Do you want it in the cloud? What is best for you? So that's where we can offer the customers something different than what some of competition may offer. >> Right. >> And just one more thing on that topic. And Darren mentioned it in his keynote this morning. But in North America, 50% of their customers are deploying on cloud, now. And that's core ELP. But in FSN, it's not quite 100%, but it's almost. And that's not dependent on the geography. Wherever we sell that product in the world, most people are choosing to deploy on cloud. So that is really real now, that trend. People see the benefits. I think, obviously, the majority of the industry and markets, and cloud solutions, now. But there really are tangible benefits and I think the customers have got it, now. And the move is real. >> If I can add on, I think one of the big things that is changing, is that customer after customer, client, client, I go to, they got a name for a project they want to take on. It can be the factory, the future, it could be a modernization, ERP modernization, or IT modernization. It could be a process transformation, digital transformation, business process redesign, whatever. They've all got a name for something. They don't know quite what it is, they really have a hard time defining it. But, they're on this journey and what they're looking for is more than just a basic transaction processing ERP product. They want something that will handle, like, IOT technology. They want connectors that connect up things beyond the four walls of the enterprise. They want to connect up to their assets as well as to assets that are out in the field, either with customers, what have you. And that's really where the future of this base is going right now. >> One of the things that we've also heard about in the keynote was the real emphasis on time-to-value. The customer really wants to be able to see a return on investment almost immediately. Is it difficult to keep up? It's almost an unrealistic expectation to see that value right away. >> I think it's down to what solution they're trying to solve and the ease of use; the implementation. And as we've said, from an IFS point of view, we want users to love the application. That means it needs to be easier to use. With what we've introduced today, with IFS Applications 10, does make it easier for customers and users to actually get the benefits out of their solution as quickly as possible. >> And are you able to keep up with the pace of change? How do you keep up, I mean to say? >> There are a number of different ways. Because we focus on our core industries, we belong to industry organizations, we often have customer advisory meetings at customer premises. Because we invite all the customers to it, or as many as we can so that we can talk to them, they can give us feedback about what they want to see in a product going forward, and we can channel that, in addition to the trends that we see in the industry. Because we have a lot of people that have come from the industry, they have that experience embedded in them. So they know what the industry wants. But we need to keep up with the trends to ensure we give them that benefit once they implement the solution. >> And one of the things I would add is that time-to-value is improved if the product is a good fit in the first place. If you've got to do a lot of modifications-- first you're adding in cost, you're also adding time, and complexity and risk to the project. And the industry expertise that Andy talks about, which comes in from a number of directions into our RND and it's reflected in our product. At least we've done a number of charts over the last few versions of our software. And if you go back like 10 or 15 years, you'd see that maybe, 25%, 30% of the project was going into modifying the software to make it do what the customer needed before they could even turn it on live. Today, we have a lot of clients who've upgraded from eight to nine, or now nine to ten, and they've literally-- they're running standard software. And so there, your time-to-solution is really rapid. It's as quick as you can move data and so on. But if you're not modifying it, that's key. >> That's the key, exactly. Well, Mark, Antony, Brian, thank you so much for joining us, it's been a great conversation. >> Thank you. >> Thank you very much. >> No problem. >> I'm Rebecca Knight. We will have much more from IFS World Conference just after this. (upbeat techno music)