value in jobs is probably the most rewarding >>things I've ever been involved >>in And I bring that energy to the queue because the cube is where all the ideas are and where the experts are, where the people are And I think what's most exciting about the cube is that we get to talk to people who are making things happen, entrepreneurs ceo of companies, venture capitalists, people who are really on a day in and day out basis, building great companies and the technology business is just not a lot of real time live tv coverage and and the cube is a non linear tv operation. We do everything that the T. V guys on cable don't do. We do longer interviews. We asked tougher questions. We >>ask sometimes some light questions. We talked about the person and what >>they feel about it's not prompted and scripted. It's a conversation authentic and for shows that have the cube coverage and makes the show buzz that creates excitement. More importantly, it creates great content, great digital assets that can be shared instantaneously to the world. Over 31 million people have viewed the cube and that is the result of great content, great conversations and I'm so proud to be part of a Q with great team. Hi, I'm john barrier, Thanks for watching the cube boy. >>Okay, welcome back everyone cube coverage of AWS amazon web services public sector summit in person here in Washington D. C. I'm john Kerry host of the cube with Sandy carter and Lynn martin Vm ware Vice president of government education and healthcare. Great to see you both cube alumni's although she's been on since 2014 your first time in 2018 18 2018. Great to see you. Great to see you. Thanks for coming on. Yeah, thanks for having us. So VM ware and 80 of us have a huge partnership. We've covered that announcement when Andy and Pat nelson was the Ceo. Then a lots happened, a lot of growth. A lot of success. Congratulations. Thank you. What's the big news with AWS this year in >>public sector. So we just received our authorization to operate for Fed ramp high. Um and we actually have a lot of joint roadmap planning. You are kicking off our job today with the Department of Defense and I. L five for the defense customers is also in process. So um a lot of fruits of a long time of labor. So very excited, >>awesome. So explain what does the Fed ramp authority to operate mean? What is >>that all about? So I would say in a nutshell, it's really putting a commercial offering through the security protocols to support the federal government needs. Um and there's different layers of that depending on the end user customers. So Fed ramp i across this, across all the civilian and non classified workloads in the federal government. Um probably applicability for state, local government as well with the new state Gramp focus. Um Fed ramp. I will meet or exceed that. So it will be applicable across the other parts of the government as well and all operated, you know, in a controlled environment jointly. So you get the VM ware software stack on top of the platform from A W. S and all the services that is more VM >>ware, faster deployed usage, faster acceleration. >>Yeah, so I would say um today the government operates on VM ware across all of the government, state, local and federal, um some workloads are still on prem many and this will really accelerate that transformation journey to the cloud and be able to move workloads quicker onto the BMC on AWS platform without free architect in your >>application, without giving away any kind of VM World Secret because that's next week. What is the value proposition of VM ware cloud, on AWS? What is the, what is the, what is the main value proposition you guys see in the public >>sector? So I see three and then Sandy chime in their two, I would say, you know, the costs in general to operate In the Cloud vs on prem or significant savings, we've seen savings over 300% on some customers. Um the speed on the application movement I think is a >>huge >>unique benefit on BMC on AWS. So traditionally to move to native cloud, you have to really do a lot of application were to be able to move those workloads where on BMC on AWS to move them pretty fast. And it also leverages the investments that the government agencies have already made in their operational tools and things of that nature. So it's not like a full reinvestment for something new but really leveraging both the skill sets in the data center in the I. T. Shops and the tools and investments you've bought over the past. And then the third area I would say is really getting the agility and flexibility and speed of a cloud experience. >>What's your, what's your reaction to the partnership? >>You know, we were just talking uh in a survey to our customers and 67% of them said that the velocity of the migration really matters to them. And one of the things that we do really well together is migrate very quickly, so we have workloads that we've migrated that have taken you know weeks months uh as opposed to years as they go over, which is really powerful. And then also tomorrow VM ware is with us in a session on data led migration. We were talking about data earlier and VM ware cloud on Aws also helps to migrate over like sequel server, database oracle databases so that we can also leverage that data now on the cloud to make better decisions and >>real time decisions as >>well. It's been really interesting to watch the partnership and watching VM ware transform as well, not only the migrations are in play with the public sector, there's a lot of them, believe me, healthcare, you name every area. It's all, all those old systems are out there. You know, I'm talking about out there. But now with microservices and containers, you've got tansy and you got the whole cloud, native VM ware stack emerging that's going to allow customers to re factor This is a dynamic that is kind of under reported >>Migration is one thing. But I think, I think that the whole Tan Xue portfolio is one of the most interesting things going on in VM ware. And we also have some integration going on on D. M. C on AWS with tan to we don't have that pentagram. Yeah. For the government market, but it's on the road mapping plans and we have other customers And I would say, you know, some of my non federal government customers were able to move workloads in hours, not even days or weeks. There you go, literally back and forth. And very impressive on the BMC on AWS platform. So, um, as we expand things in with the Tan Xue platform is, you know, Sandy talked about this yesterday and our partners summit, Everyone's talking about containers and things like that. VM ware is doing a lot of investment around the cooper Netease plus the application migration work and things of that nature. >>I'd love to get you guys reaction to this comment because I've seen a lot of change. Obviously we're all seeing it. I've actually interviewed a bunch of aWS and VM ware customers and I would call um some of the categories skeptics the old school cloud holding the line. And then when the pandemic hit those skeptics flip over because they see the value. In fact I actually interviewed a skeptic who became an award winner who went on the record and said I love hey w I love the cloud. I was a skeptic because you saw the value the time to value. This is really a key dynamic. I know it's kind of thrown out a lot of digital transformation or I. T. Modernization but the agility and that kind of speed. It becomes the number one thing. What's your reaction to the skeptics converting? And then what happens >>next? Um So I think there's still a lot of folks in I. T. That our tree huggers or I call him several huggers uh um pick your term. And I think that um there is some concern about what their role will be. So I think one of the differences delivering cloud services to your internal constituents is really understand the business value of the applications and what that delivers from a mission perspective back to your client. And that's a shift for data center owners to really start thinking more from the customer mission perspective than or my servers running you know, do you have enough storage capacity blah blah blah. So I think that creates that skepticism and part of that's around what's my role going to be. So in the cloud transformation of a customer, there's all this old people part that becomes really the catalyst and I think the customers that have been very sad and really leverage that and then retool the business value back to the end users around the mission have done the best job. >>I mean we talk about this all the time, it's really hard to get the best debris partners together and then make it all work cloud, it becomes easier than doing it very bespoke or waterfall way >>Yeah, I have to say with the announcement yesterday, we're going to have a lot more partner with partners. So you and I have talked about this a few times where we bring partners together to work with each other. In fact, Lynn is going to go meet with one of those partners right after the interview um that want to really focus in on a couple of particular areas to really drive this and I think, you know, part of the, you know, as your re factoring or migrating VMro over the other big benefit is skills, people have really strong, these fear skills, the sand skills, >>operation >>operation tools Yeah. And so they want to preserve those, I think that's part of the beauty of doing VM ware cloud on Aws is you get to take those skills with you into the new world as well, >>you know, I was going to just ask the next question ai ops or day two operations, a big buzzword Yeah and that is essentially operation mindset, that devoPS DEVOps two is coming. Emily Freeman gave a keynote with our last event we had with with amazon public showcase revolution and devops devoPS 2.0 is coming which is now faster, security is built in the front end, so all these things are happening so now it's coming into the public sector with the GovCloud. So I have to ask you Lynn what are some of the big successes you've had with on the gulf cloudy, just Govcloud. >>So I would say we've had a lot of customers across the state local side especially um that weren't waiting for fed ramp and those customers were able to move like I mentioned this earlier and you guys just touched on it. So I think the benefit and the benefit, one of our best customers is Emmett Right? Absolutely mitt, God bless them. They've been on every cloud journey with VM ware since 2014 we moved in my three years now and talk about a skeptic. So although Mark is very revolutionary and tries new things, he was like oh who knows and literally when we moved those workloads it was minutes and the I. T shop day one there was no transformation work for them, it was literally using all the tools and things in that environment. So the progress of that and the growth of the applications that have been able to move their things. That took 2 to 3 years before we're all done within six months and really being able to expand those business values back out for the services that he delivers to the customers. So I think you'll see quite a bit across state, local federal government. You know, we have U. S. Marshals, thank them very much. They were our sponsor that we've been working with the last few years. We have a defense customer working with us around aisle five. >>Um you know, if we could also thank Coal Fire because Cold Fire is one of our joint partners talking about partner partners and they were played a critical role in helping BM We're cloud on AWS and get the fed ramp high certifications. >>They were R three p. O. We hired them for their exercise expertise with AWS as well as helping the BMR. >>Well the partnership with the war has been a really big success. Remember the naysayers when that was announced? Um it really has worked out well for you guys. Um I do want to ask you one more thing and we don't mind. Um One of the biggest challenges that you see the blockers or challenges from agencies moving to the cloud cover cloud because you know, people are always trying to get those blockers out of the way but it's an organizational culture is a process technology. What's your what's your take on that land. Um >>I think a lot does have to do with the people and the organizational history. I think somewhere you need a leader and a champion that really wants to change for good. I call Pat, used to call a tech for good. I love that. Right to really, you know, get things moving for the customers. I mean one of the things I'm most proud about supporting the government business in general though is really the focus on the mission is unparalleled, you know, in the sectors we support, you say, education or government or healthcare. Right? All three of those sectors, there's never any doubt on what that focuses. So I think the positives of it are like, how do you get into that change around that? And that could be systems, there's less what's VMC ON AWS as we mentioned, because the tools already in the environment so they know how to use it. But I do think there's a transformation on the data center teams and really becoming moving from technology to the business aspects a little bit more around the missions and things of that. >>What's interesting is that it's so, I mean, I actually love this environment even though it's kind of hard on everyone. Education and health care have been disrupted unprecedented ways and it's never gonna change back? Remember healthcare, hip data silos, silos, education don't spend on it. >>That education was the most remarkable part. Unbelievable. I started working in february before school started with one of the large cities everyone can guess and just the way they were able to pivot so fast was amazing and I don't think anybody, I think we did like five years of transformation in six months and it's never going to go back. >>I completely a great yes education. We just did a piece of work with CTS around the world and education is one of the most disrupted as you said health care and then the third one is government and all three of those are public sector. So the three most disruptive sectors or mission areas are in public sector which has created a lot of opportunity for us and our partnership to add value. I mean that's what we're all about right customer obsession working backwards from the customer and making sure that our partnership continues to add value to those customers >>while we love the tech action on the cube. Obviously we'd like to document and pontificate and talk about it. Digital revolution. Every application now is in play globally. Not just for I. T. But for society, public sector more than ever is the hottest area on the planet. >>Absolutely. And I would say that now our customers are looking at E. S. G. Environmental, they want to know what you're doing on sustainability. They want to know what you're doing for society. We just had a bid that came in and they wanted to understand our diversity plan and then open governance. They're looking for that openness. They're not just artificial intelligence but looking at explainable AI as well. So I think that we have a chance to impact environment societies and governance >>and you mentioned space earlier. Another way I talked with closure. I mean I'm an interview today too, but what's happening with space and what you can monitor disasters, understand how to deploy resources to areas that might have challenges, earthquakes or fires or other things. All new things are happening. >>Absolutely. And all that data people like to say, why are you spending money on space? There's so many problems here, but that data that comes from space is going to impact us here on earth. And so all the things that we're doing, all that data could be used with VM ware cloud on AWS as well. >>Well, you watch closely we got some space coverage coming. I got a big scoop. I'm gonna release soon about something behind the dark side of the moon on in terms of space sovereignty coming a lot of action, cybersecurity in space. That's really heavy right now. But >>aren't you glad that VMC cloud on AWS isn't hidden on the dark side of the moon. It's >>right on the congratulations. Thanks for coming on. You guys are doing great. Thanks for >>thanks for sharing. Congratulations. >>Okay, cube coverage here continues. AWS public sector summit in Washington D. C live for two days of coverage be right back. Thank you. Mhm. Mhm mm mm hmm.

>> From around the globe, It's theCUBE. With digital coverage of IBM Think 2021, brought to you by IBM. >> Hi, welcome back to theCUBE's coverage of IBM Think 2021 virtual. I'm John Furrier host of the CUBE. We got a great guest here. Brian Bouchard is the co-founder president and CEO of Alacrinet. Brian great to see you remoting in all the way from Puerto Rico to Palo Alto. >> That's right. >> Great to see you. >> Thanks for First of all, thanks John, for having me. I really appreciate the opportunity. >> Yeah, great to see you. Thanks for coming on. First of all, before we get into what you guys do and and how this all ties in to Think. What do you guys do at Alacrinet? Why the name? A it's good you're at the top of the list and alphabetically, but tell us the, the, the the secret behind the name and what you guys do. >> So, first of all Alacrinet is based on the root word alacrity which means a prompt and willing, a prompt a joyous prompt to, excuse me, to achieve a common goal. So we ultimately are a network of individuals with the traits of alacrity. So Alacrinet. So that's our name. >> Great. So what's your relationship with IBM and how you guys have been able to leverage the partnership program in the marketplace? Take us through the relationship. >> So, well, first of all Alacrinet is a platinum IBM business partner and it was awarded recently the 2020 IBM North American partner of the year award. And we were selected amongst 1600 other business partners across North America. We've been actually a consulting, an IT consulting company for almost 20 years now. And we were founded in 2002 in Palo Alto and we have focused specifically on cyber security since 2013. And then as part, go ahead. >> What are some of the things that you guys are working on? Because obviously, you know, the business is hot right now. Everyone's kind of looking at COVID saying we're going to double down on the most critical projects and no time for leisurely activities when it comes to IT. And cloud scale projects, you know mission critical stuff's happening what are you guys working on? >> So we're, we're focused on cybersecurity, our security services really compliment IBM's suite of security solutions and cover the full spectrum from our research and penetration testing, which helps identify vulnerabilities before a breach occurs. And we also have managed security services which helps prevent, detect and remediate attacks in real time. And then finally, we also have a security staffing division and a software resell division, which kind of rounds out the full amount of offerings that we have to provide protection for our clients. >> What are some of the biggest challenges you guys have as a business, and how's IBM helping you address those? >> Well, as you know, John, we all know the importance of cybersecurity in today's world, right? So it's increasing in both demand and importance and it's not expected to wane anytime soon. Cyber attacks are on the rise and there's no there's no expected end in sight to this. And in fact, just this week on 60 minutes, Jay Powell, the chairman of the federal reserve board he noted that cyber attacks were the number one threat to the stability of the US economy. Also this week, a public school in Buffalo New York was hacked with ransomware and the school you know, this, the school district is just contemplating you know, paying the ransom to the hackers. So there's literally thousands of these attacks happening every day, whether it's in local school district or a state government, or an enterprise even if you don't hear about them, they're happening In adding to the complexity that the cyber attackers pose is the complexity of the actual cybersecurity tools themselves. There isn't a single solution provider or a single technology, that can ensure a company's security. Our customers need to work with many different companies and disconnected tools and processes to build an individual strategy that can adequately protect their organizations. >> You know, I love this conversation whenever I talk to practitioners on cybersecurity, you know that first of all, they're super smart, usually cyber punks and they also have some kinds of eclectic backgrounds, but more importantly is that there's different approaches in terms of what you hear. Do you, do you put more if you add more firefighters, so to speak to put out the fires and solve the problems? Or do you spend your time preventing the fires from happening in the first place? You know, and you know, the buildings are burning down don't make fire fire, don't make wood make fire resistance, you know, more of a priority. So there's less fires needing firefighters So it's that balance. You throw more firefighters at the problem or do you make the supply or the material the business fireproof, what's your take on that? >> Yeah, well, it kind of works both ways. I mean, we've seen customers want it. They really want choice. They want to, in some cases they want to be the firefighter. And in some cases they want the firefighter to come in and solve their problems. So, the common problem set that we're seeing with our that our customers encounter is that they struggle one, with too many disparate tools. And then they also have too much data being collected by all these disparate tools. And then they have a lack of talent in their environment to manage their environments. So what we've done at Alacrinet is we've taken our cybersecurity practice and we've really specifically tailored our offerings to address these core challenges. So first, to address the too many disparate tools problem, we've been recommending that our clients look at security platforms like the IBM Cloud Pak for security the IBM Cloud Pak for security is built on a security platform that allows interoperability across various security tools using open standards. So our customers have been responding extremely positively to this approach and look at it as a way to future-proof their investments and begin taking advantage of interoperability with, and, tools integration. >> How about where you see your business going with this because, you know, there's not a shortage of need or demand How are you guys flexing with the market? What's the strategy? Are you going to use technology enablement? You're going to more human driven. Brian, how do you see your business unfolding? >> Well, actually really good. We're doing very well. I mean, obviously we made the, the top the business partner for IBM in 2020. They have some significant growth and a lot of interest. I think we really attack the market in a, in a with a good strategy which was to help defragment the market if you will. There's a lot of point solutions and a lot of point vendors that various, you know, they they spent specialized in one piece of the whole problem. And what we've decided to do is find them the highest priority list, every CSO and CIO has a tick list. So that how that, you know, first thing we need we need a SIM, we need an EDR, we need a managed service. We need, what's the third solution that we're doing? So we, we need some new talent in-house. So we actually have added that as well. So we added a security staffing division to help that piece of it as well. So to give you an idea of the cybersecurity market size it was valued at 150 billion in 2019 and that is expected to grow to 300 billion by 2027. And Alacrinet is well-positioned to consolidate the many fragmented aspects of the security marketplace and offer our customers more integrated and easier to manage solutions. And we will continue to help our customers select the best suite of solutions to address all types of cybersecurity, cybersecurity threats. >> You know, it's it's such a really important point you're making because you know, the tools just have piled up in the tool shed. I call it like that. It's like, it's like you don't even know what's in there anymore. And then you've got to support them. Then the world's changed. You get cloud native, the service areas increasing and then the CSOs are also challenged. Do I, how many CLAWs do I build on? Do I optimize my development teams for AWS or Azure? I mean, now that's kind of a factor. So, you have all this tooling going on they're building their own stuff they're building their own core competency. And yet the CSO still needs to be like maintaining kind of like a relevance list. That's almost like a a stock market for the for the products. You're providing that it sounds like you're providing that kind of service as well, right? >> Yeah, well, we, we distill all of the products that are out there. There's thousands of cybersecurity products out there in the marketplace and we kind of do all that distillation for the customer. We find using, you know, using a combination of things. We use Forrester and Gartner and all the market analysts to shortlist our proposed solutions that we offer customers. But then we also use our experience. And so since 2013, we've been deploying these solutions across organizations and corporations across America and we've, we've gained a large body of experience and we can take that experience and knowledge to our customers and help them, you know, make make some good decisions. So they don't have to, you know, make them go through the pitfalls that many companies do when selecting these types of solutions. >> Well congratulations, you've got a great business and you know, that's just a basic search making things easier for the CSO, more so they can be safe and secure in their environment. It's funny, you know, cyber warfare, you know the private companies have to fight their own battles got to build their own armies. Certainly the government's not helping them. And then they're confused even with how to handle all this stuff. So they need, they need your service. I'm just curious as this continues to unfold and you start to see much more of a holistic view, what's the IBM angle in here? How, why are you such a big partner of theirs? Is it because their customers are working with you they're bringing you into business? Is it because you have an affinity towards some of their products? What's the connection with IBM? >> All of the above. (chuckles) So I think it probably started with our affinity to IBM QRadar product. And we have, we have a lot of expertise in that and that solution. So that's, that's where it started. And then I think IBM's leadership in this space has been remarkable, really. So like what's happening now with the IBM Cloud Pak for security you know, building up a security platform to allow all these point solutions to work together. That's the roadmap we want to put our customers on because we believe that's the that's the future for this, this, this marketplace. >> Yeah. And the vision of hybrid cloud having that underpinning be with Red Hat it's a Linux kernel, model of all things >> Yeah. Super NetEase. >> Locked in >> It's portable, multiple, you can run it on Azure. IBM Cloud, AWS. It's portable. I mean, yeah, all this openness, as you probably know cyber security is really a laggard in the security in the information technology space as far as adopting open standards. And IBM is I think leading that charge and you'll be able to have a force multiplier with the open standards in this space. >> Open innovation with open source is incredible. I mean, if you, if, if if open source can embrace a common platform and build that kind of control plane and openness to allow thriving companies to just build out then you have an entire hybrid distributed architecture. >> Yeah. Well, I think companies want to use the best in breed. So when we, when we show these solutions to customers they want the best in breed. They always say, I don't, when it comes to security they don't want second best. They want the best it's out there because they're securing their crown jewels. So that makes sense. So the problem with, you know having all these different disparate solutions that are all top in their category none of them talk to each other. So we need to address that problem because without that being solved, this is just going to be more it's going to compound the complexity of the problems we solve day to day. >> Awesome. Congratulations, Brian, great story. You know entrepreneur built a great business over the years. I think the product's amazing. I think that's exactly what the market needs and just shows you what the ecosystem is all about. This is the power of the ecosystem. You know, a thousand flowers are blooming. You got a great product. IBM is helping as well. Good partnership, network effects built in and and still a lot more to do. Congratulations. >> Absolutely. >> Okay. >> Thank you very much >> Brian Bouchard >> Made my impression. I appreciate that >> Thanks for coming on theCUBE Appreciate it. I'm John Furrier with IBM thinks 2021 virtual coverage. Thanks for watching. (outro music plays)

>>mhm Yes. >>Welcome back to the Cube coverage of Red Hat summit 21 2021. I'm john for host of the Cubans virtual this year as we start preparing to come out of Covid a lot of great conversations here happening around technology. This is the emerging technology with Red hat segment. We've got three great guests steve watt manager, distinguished engineer at Red Hat hurl saying senior software engineer Red Hat and luke Hines, who's the senior software engineer as well. We got the engineering team steve, you're the the team leader, emerging tech within red hat. Always something to talk about. You guys have great tech chops that's well known in the industry and I'll see now part of IBM you've got a deep bench um what's your, how do you view emerging tech um how do you apply it? How do you prioritize, give us a quick overview of the emerging tech scene at Redhead? >>Yeah, sure. It's quite a conflated term. The way we define emerging technologies is that it's a technology that's typically 18 months plus out from commercialization and this can sometimes go six months either way. Another thing about it is it's typically not something on any of our product roadmaps within the portfolio. So in some sense, it's often a bit of a surprise that we have to react to. >>So no real agenda. And I mean you have some business unit kind of probably uh but you have to have first principles within red hat, but for this you're looking at kind of the moon shot, so to speak, the big game changing shifts. Quantum, you know, you got now supply chain from everything from new economics, new technology because that kind of getting it right. >>Yeah, I think we we definitely use a couple of different techniques to prioritize and filter what we're doing. And the first is something will pop up and it will be like, is it in our addressable market? So our addressable market is that we're a platform software company that builds enterprise software and so, you know, it's got to be sort of fit into that is a great example if somebody came up came to us with an idea for like a drone command center, which is a military application, it is an emerging technology, but it's something that we would pass on. >>Yeah, I mean I didn't make sense, but he also, what's interesting is that you guys have an open source D N A. So it's you have also a huge commercial impact and again, open sources of one of the 4th, 5th generation of awesomeness. So, you know, the good news is open source is well proven. But as you start getting into this more disruption, you've got the confluence of, you know, core cloud, cloud Native, industrial and IOT edge and data. All this is interesting, right. This is where the action is. How do you guys bring that open source community participation? You got more stakeholders emerging there before the break down, how that you guys manage all that complexity? >>Yeah, sure. So I think that the way I would start is that, you know, we like to act on good ideas, but I don't think good ideas come from any one place. And so we typically organize our teams around sort of horizontal technology sectors. So you've got, you know, luke who's heading up security, but I have an edge team, cloud networking team, a cloud storage team. Cloud application platforms team. So we've got these sort of different areas that we sort of attack work and opportunities, but you know, the good ideas can come from a variety of different places. So we try and leverage co creation with our customers and our partners. So as a good example of something we had to react to a few years ago, it was K Native right? So the sort of a new way of doing service um and eventing on top of kubernetes that was originated from google. Whereas if you look at Quantum right, ibms, the actual driver on quantum science and uh that originated from IBM were parole. We'll talk about exactly how we chose to respond to that. Some things are originated organically within the team. So uh luke talking about six law is a great example of that, but we do have a we sort of use the addressable market as a way to sort of focus what we're doing and then we try and land it within our different emerging technologies teams to go tackle it. Now. You asked about open source communities, which are quite interesting. Um so typically when you look at an open source project, it's it's there to tackle a particular problem or opportunity. Sometimes what you actually need commercial vendors to do is when there's a problem or opportunity that's not tackled by anyone open source project, we have to put them together to create a solution to go tackle that thing. That's also what we do. And so we sort of create this bridge between red hat and our customers and multiple different open source projects. And this is something we have to do because sometimes just that one open source project doesn't really care that much about that particular problem. They're motivated elsewhere. And so we sort of create that bridge. >>We got two great uh cohorts here and colleagues parole on the on the Quantum side and you got luke on the security side. Pro I'll start with you. Quantum is also a huge mentioned IBM great leadership there. Um Quantum on open shift. I mean come on. Just that's not coming together for me in my mind, it's not the first thing I think of. But it really that sounds compelling. Take us through, you know, um how this changes the computing landscape because heterogeneous systems is what we want and that's the world we live in. But now with distributed systems and all kinds of new computing modules out there, how does this makes sense? Take us through this? >>Um yeah john's but before I think I want to explain something which is called Quantum supremacy because it plays very important role in the road map that's been working on. So uh content computers, they are evolving and they have been around. But right now you see that they are going to be the next thing. And we define quantum supremacy as let's say you have any program that you run or any problems that you solve on a classical computer. Quantum computer would be giving you the results faster. So that is uh, that is how we define content supremacy when the same workload are doing better on content computer than they do in a classical computer. So the whole the whole drive is all the applications are all the companies, they're trying to find avenues where Quantum supremacy are going to change how they solve problems or how they run their applications. And even though quantum computers they are there. But uh, it is not as easily accessible for everyone to consume because it's it's a very new area that's being formed. So what, what we were thinking, how we can provide a mechanism that you can you don't connect this deal was you have a classical world, you have a country world and that's where a lot of thought process been. And we said okay, so with open shift we have the best of the classical components. You can take open shift, you can develop, deploy around your application in a country raised platform. What about you provide a mechanism that the world clothes that are running on open shift. They are also consuming quantum resources or they are able to run the competition and content computers take the results and integrate them in their normal classical work clothes. So that is the whole uh that was the whole inception that we have and that's what brought us here. So we took an operator based approach and what we are trying to do is establish the best practices that you can have these heterogeneous applications that can have classical components. Talking to our interacting the results are exchanging data with the quantum components. >>So I gotta ask with the rise of containers now, kubernetes at the center of the cloud native value proposition, what work clothes do you see benefiting from the quantum systems the most? Is there uh you guys have any visibility on some of those workloads? >>Uh So again, it's it's a very new, it's very it's really very early in the time and uh we talk with our customers and every customers, they are trying to identify themselves first where uh these contacts supremacy will be playing the role. What we are trying to do is when they reach their we should have a solution that they that they could uh use the existing in front that they have on open shift and use it to consume the content computers that may or may not be uh, inside their own uh, cloud. >>Well I want to come back and ask you some of the impact on the landscape. I want to get the look real quick because you know, I think security quantum break security, potentially some people have been saying, but you guys are also looking at a bunch of projects around supply chain, which is a huge issue when it comes to the landscape, whether its components on a machine in space to actually handling, you know, data on a corporate database. You guys have sig store. What's this about? >>Sure. Yes. So sick store a good way to frame six store is to think of let's encrypt and what let's encrypt did for website encryption is what we plan to do for software signing and transparency. So six Door itself is an umbrella organization that contains various different open source projects that are developed by the Six door community. Now, six door will be brought forth as a public good nonprofit service. So again, we're very much basing this on the successful model of let's Encrypt Six door will will enable developers to sign software artifacts, building materials, containers, binaries, all of these different artifacts that are part of the software supply chain. These can be signed with six door and then these signing events are recorded into a technology that we call a transparency log, which means that anybody can monitor signing events and a transparency log has this nature of being read only and immutable. It's very similar to a Blockchain allows you to have cryptographic proof auditing of our software supply chain and we've made six stores so that it's easy to adopt because traditional cryptographic signing tools are a challenge for a lot of developers to implement in their open source projects. They have to think about how to store the private keys. Do they need specialist hardware? If they were to lose a key then cleaning up afterwards the blast radius. So the key compromise can be incredibly difficult. So six doors role and purpose essentially is to make signing easy easy to adopt my projects. And then they have the protections around there being a public transparency law that could be monitored. >>See this is all about open. Being more open. Makes it more secure. Is the >>thief? Very much yes. Yes. It's that security principle of the more eyes on the code the better. >>So let me just back up, is this an open, you said it's gonna be a nonprofit? >>That's correct. Yes. Yes. So >>all of the code is developed by the community. It's all open source. anybody can look at this code. And then we plan alongside the Linux Foundation to launch a public good service. So this will make it available for anybody to use if your nonprofit free to use service. >>So luke maybe steve if you can way into on this. I mean, this goes back. If you look back at some of the early cloud days, people were really trashing cloud as there's no security. And cloud turns out it's a more security now with cloud uh, given the complexity and scale of it, does that apply the same here? Because I feel this is a similar kind of concept where it's open, but yet the more open it is, the more secure it is. And then and then might have to be a better fit for saying I. T. Security solution because right now everyone is scrambling on the I. T. Side. Um whether it's zero Trust or Endpoint Protection, everyone's kind of trying everything in sight. This is kind of changing the paradigm a little bit on software security. Could you comment on how you see this playing out in traditional enterprises? Because if this plays out like the cloud, open winds, >>so luke, why don't you take that? And then I'll follow up with another lens on it which is the operate first piece. >>Sure. Yes. So I think in a lot of ways this has to be open this technology because this way we have we have transparency. The code can be audited openly. Okay. Our operational procedures can be audit openly and the community can help to develop not only are code but our operational mechanisms so we look to use technology such as cuba netease, open ship operators and so forth. Uh Six store itself runs completely in a cloud. It is it is cloud native. Okay, so it's very much in the paradigm of cloud and yeah, essentially security, always it operates better when it's open, you know, I found that from looking at all aspects of security over the years that I've worked in this realm. >>Okay, so just just to add to that some some other context around Six Law, that's interesting, which is, you know, software secure supply chain, Sixth floor is a solution to help build more secure software secure supply chains, more secure software supply chain. And um so um there's there's a growing community around that and there's an ecosystem of sort of cloud native kubernetes centric approaches for building more secure software. I think we all caught the solar winds attack. It's sort of enterprise software industry is responding sort of as a whole to go and close out as many of those gaps as possible, reduce the attack surface. So that's one aspect about why 6th was so interesting. Another thing is how we're going about it. So we talked about um you mentioned some of the things that people like about open source, which is one is transparency, so sunlight is the best disinfectant, right? Everybody can see the code, we can kind of make it more secure. Um and then the other is agency where basically if you're waiting on a vendor to go do something, um if it's proprietary software, you you really don't have much agency to get that vendor to go do that thing. Where is the open source? If you don't, if you're tired of waiting around, you can just submit the patch. So, um what we've seen with package software is with open source, we've had all this transparency and agency, but we've lost it with software as a service, right? Where vendors or cloud service providers are taking package software and then they're making it available as a service but that operationalize ng that software that is proprietary and it doesn't get contributed back. And so what Lukes building here as long along with our partners down, Lawrence from google, very active contributor in it. Um, the, is the operational piece to actually run sixth or as a public service is part of the open source project so people can then go and take sixth or maybe run it as a smaller internal service. Maybe they discover a bug, they can fix that bug contributed back to the operational izing piece as well as the traditional package software to basically make it a much more robust and open service. So you bring that transparency and the agency back to the SAS model as well. >>Look if you don't mind before, before uh and this segment proportion of it. The importance of immune ability is huge in the world of data. Can you share more on that? Because you're seeing that as a key part of the Blockchain for instance, having this ability to have immune ability. Because you know, people worry about, you know, how things progress in this distributed world. You know, whether from a hacking standpoint or tracking changes, Mutability becomes super important and how it's going to be preserved in this uh new six doorway. >>Oh yeah, so um mutability essentially means cannot be changed. So the structure of something is set. If it is anyway tampered or changed, then it breaks the cryptographic structure that we have of our public transparency service. So this way anybody can effectively recreate the cryptographic structure that we have of this public transparency service. So this mutability provides trust that there is non repudiation of the data that you're getting. This data is data that you can trust because it's built upon a cryptographic foundation. So it has very much similar parallels to Blockchain. You can trust Blockchain because of the immutable nature of it. And there is some consensus as well. Anybody can effectively download the Blockchain and run it themselves and compute that the integrity of that system can be trusted because of this immutable nature. So that's why we made this an inherent part of Six door is so that anybody can publicly audit these events and data sets to establish that there tamper free. >>That is a huge point. I think one of the things beyond just the security aspect of being hacked and protecting assets um trust is a huge part of our society now, not just on data but everything, anything that's reputable, whether it's videos like this being deep faked or you know, or news or any information, all this ties to security again, fundamentally and amazing concepts. Um I really want to keep an eye on this great work. Um Pearl, I gotta get back to you on Quantum because again, you can't, I mean people love Quantum. It's just it feels like so sci fi and it's like almost right here, right, so close and it's happening. Um And then people get always, what does that mean for security? We go back to look and ask them well quantum, you know, crypto But before we get started I wanted, I'm curious about how that's gonna play out from the project because is it going to be more part of like a C. N. C. F. How do you bring the open source vibe to Quantum? >>Uh so that's a very good question because that was a plan, the whole work that we are going to do related to operators to enable Quantum is managed by the open source community and that project lies in the casket. So casket has their own open source community and all the modification by the way, I should first tell you what excuse did so cute skin is the dedicate that you use to develop circuits that are run on IBM or Honeywell back in. So there are certain Quantum computers back and that support uh, circuits that are created using uh Houston S ticket, which is an open source as well. So there is already a community around this which is the casket. Open source community and we have pushed the code and all the maintenance is taken care of by that community. Do answer your question about if we are going to integrate it with C and C. F. That is not in the picture right now. We are, it has a place in its own community and it is also very niche to people who are working on the Quantum. So right now you have like uh the contributors who who are from IBM as well as other uh communities that are specific specifically working on content. So right now I don't think so, we have the map to integrated the C. N. C. F. But open source is the way to go and we are on that tragic Torri >>you know, we joke here the cube that a cubit is coming around the corner can can help but we've that in you know different with a C. But um look, I want to ask you one of the things that while you're here your security guru. I wanted to ask you about Quantum because a lot of people are scared that Quantum is gonna crack all the keys on on encryption with his power and more hacking. You're just comment on that. What's your what's your reaction to >>that? Yes that's an incredibly good question. This will occur. Okay. And I think it's really about preparation more than anything now. One of the things that we there's a principle that we have within the security world when it comes to coding and designing of software and this aspect of future Cryptography being broken. As we've seen with the likes of MD five and Sha one and so forth. So we call this algorithm agility. So this means that when you write your code and you design your systems you make them conducive to being able to easily swap and pivot the algorithms that use. So the encryption algorithms that you have within your code, you do not become too fixed to those. So that if as computing gets more powerful and the current sets of algorithms are shown to have inherent security weaknesses, you can easily migrate and pivot to a stronger algorithms. So that's imperative. Lee is that when you build code, you practice this principle of algorithm agility so that when shot 256 or shot 5 12 becomes the shar one. You can swap out your systems. You can change the code in a very least disruptive way to allow you to address that floor within your within your code in your software projects. >>You know, luke. This is mind bender right there. Because you start thinking about what this means is when you think about algorithmic agility, you start thinking okay software countermeasures automation. You start thinking about these kinds of new trends where you need to have that kind of signature capability. You mentioned with this this project you're mentioning. So the ability to actually who signs off on these, this comes back down to the paradigm that you guys are talking about here. >>Yes, very much so. There's another analogy from the security world, they call it turtles all the way down, which is effectively you always have to get to the point that a human or a computer establishes that first point of trust to sign something off. And so so it is it's a it's a world that is ever increasing in complexity. So the best that you can do is to be prepared to be as open as you can to make that pivot as and when you need to. >>Pretty impressive, great insight steve. We can talk for hours on this panel, emerging tech with red hat. Just give us a quick summary of what's going on. Obviously you've got a serious brain trust going on over there. Real world impact. You talk about the future of trust, future of software, future of computing, all kind of going on real time right now. This is not so much R and D as it is the front range of tech. Give us a quick overview of >>Yeah, sure, yeah, sure. The first thing I would tell everyone is go check out next that red hat dot com, that's got all of our different projects, who to contact if you're interested in learning more about different areas that we're working on. And it also lists out the different areas that we're working on, but just as an overview. So we're working on software defined storage, cloud storage. Sage. Well, the creator of Cf is the person that leads that group. We've got a team focused on edge computing. They're doing some really cool projects around um very lightweight operating systems that and kubernetes, you know, open shift based deployments that can run on, you know, devices that you screw into the sheet rock, you know, for that's that's really interesting. Um We have a cloud networking team that's looking at over yin and just intersection of E B P F and networking and kubernetes. Um and then uh you know, we've got an application platforms team that's looking at Quantum, but also sort of how to advance kubernetes itself. So that's that's the team where you got the persistent volume framework from in kubernetes and that added block storage and object storage to kubernetes. So there's a lot of really exciting things going on. Our charter is to inform red hats long term technology strategy. We work the way my personal philosophy about how we do that is that Red hat has product engineering focuses on their product roadmap, which is by nature, you know, the 6 to 9 months. And then the longer term strategy is set by both of us. And it's just that they're not focused on it. We're focused on it and we spend a lot of time doing disambiguate nation of the future and that's kind of what we do. We love doing it. I get to work with all these really super smart people. It's a fun job. >>Well, great insights is super exciting, emerging tack within red hat. I'll see the industry. You guys are agile, your open source and now more than ever open sources, uh, product Ization of open source is happening at such an accelerated rate steve. Thanks for coming on parole. Thanks for coming on luke. Great insight all around. Thanks for sharing. Uh, the content here. Thank you. >>Our pleasure. >>Thank you. >>Okay. We were more, more redhead coverage after this. This video. Obviously, emerging tech is huge. Watch some of the game changing action here at Redhead Summit. I'm john ferrier. Thanks for watching. Yeah.

>>from around the globe. It's the Cube presenting Cuban cloud brought to you by silicon angle, everybody to Cuban cloud. My name is Dave Volonte, and I'll be here throughout the day with my co host, John Ferrier, who was quarantined in an undisclosed location in California. He's all good. Don't worry. Just precautionary. John, how are you doing? >>Hey, great to see you. John. Quarantine. My youngest daughter had covitz, so contact tracing. I was negative in quarantine at a friend's location. All good. >>Well, we wish you the best. Yeah, well, right. I mean, you know what's it like, John? I mean, you're away from your family. Your basically shut in, right? I mean, you go out for a walk, but you're really not in any contact with anybody. >>Correct? Yeah. I mean, basically just isolation, Um, pretty much what everyone's been kind of living on, kind of suffering through, but hopefully the vaccines are being distributed. You know, one of the things we talked about it reinvent the Amazon's cloud conference. Was the vaccine on, but just the whole workflow around that it's gonna get better. It's kind of really sucky. Here in the California area, they haven't done a good job, a lot of criticism around, how that's rolling out. And, you know, Amazon is now offering to help now that there's a new regime in the U. S. Government S o. You know, something to talk about, But certainly this has been a terrible time for Cove it and everyone in the deaths involved. But it's it's essentially pulled back the covers, if you will, on technology and you're seeing everything. Society. In fact, um, well, that's big tech MIT disinformation campaigns. All these vulnerabilities and cyber, um, accelerated digital transformation. We'll talk about a lot today, but yeah, it's totally changed the world. And I think we're in a new generation. I think this is a real inflection point, Dave. You know, modern society and the geo political impact of this is significant. You know, one of the benefits of being quarantined you'd be hanging out on these clubhouse APS, uh, late at night, listening to experts talk about what's going on, and it's interesting what's happening with with things like water and, you know, the island of Taiwan and China and U. S. Sovereignty, data, sovereignty, misinformation. So much going on to talk about. And, uh, meanwhile, companies like Mark injuries in BC firm starting a media company. What's going on? Hell freezing over. So >>we're gonna be talking about a lot of that stuff today. I mean, Cuba on cloud. It's our very first virtual editorial event we're trying to do is bring together our community. It's a it's an open forum and we're we're running the day on our 3 65 software platform. So we got a great lineup. We got CEO Seo's data Practitioners. We got a hard core technologies coming in, cloud experts, investors. We got some analysts coming in and we're creating this day long Siri's. And we've got a number of sessions that we've developed and we're gonna unpack. The future of Cloud computing in the coming decade is, John said, we're gonna talk about some of the public policy new administration. What does that mean for tech and for big tech in General? John, what can you add to that? >>Well, I think one of the things that we talked about Cove in this personal impact to me but other people as well. One of the things that people are craving right now is information factual information, truth texture that we call it. But hear this event for us, Davis, our first inaugural editorial event. Robbo, Kristen, Nicole, the entire Cube team Silicon angle, really trying to put together Morva cadence we're gonna doom or of these events where we can put out feature the best people in our community that have great fresh voices. You know, we do interview the big names Andy Jassy, Michael Dell, the billionaires with people making things happen. But it's often the people under there that are the rial newsmakers amid savory, for instance, that Google one of the most impressive technical people, he's gotta talk. He's gonna present democratization of software development in many Mawr riel people making things happen. And I think there's a communal element. We're going to do more of these. Obviously, we have, uh, no events to go to with the Cube. So we have the cube virtual software that we have been building and over years and now perfecting and we're gonna introduce that we're gonna put it to work, their dog footing it. We're gonna put that software toe work. We're gonna do a lot mawr virtual events like this Cuban cloud Cuban startup Cuban raising money. Cuban healthcare, Cuban venture capital. Always think we could do anything. Question is, what's the right story? What's the most important stories? Who's telling it and increase the aperture of the lens of the industry that we have and and expose that and fastest possible. That's what this software, you'll see more of it. So it's super exciting. We're gonna add new features like pulling people up on stage, Um, kind of bring on the clubhouse vibe and more of a community interaction with people to meet each other, and we'll roll those out. But the goal here is to just showcase it's cloud story in a way from people that are living it and providing value. So enjoy the day is gonna be chock full of presentations. We're gonna have moderated chat in these sessions, so it's an all day event so people can come in, drop out, and also that's everything's on demand immediately after the time slot. But you >>want to >>participate, come into the time slot into the cube room or breakout session. Whatever you wanna call it, it's a cube room, and the people in there chatting and having a watch party. So >>when you're in that home page when you're watching, there's a hero video there. Beneath that, there's a calendar, and you'll see that red line is that red horizontal line of vertical line is rather, it's a linear clock that will show you where we are in the day. If you click on any one of those sessions that will take you into the chat, we'll take you through those in a moment and share with you some of the guests that we have upcoming and and take you through the day what I wanted to do. John is trying to set the stage for the conversations that folks are gonna here today. And to do that, I wanna ask the guys to bring up a graphic. And I want to talk to you, John, about the progression of cloud over time and maybe go back to the beginning and review the evolution of cloud and then really talk a little bit about where we think it Z headed. So, guys, if you bring up that graphic when a W S announced s three, it was March of 2000 and six. And as you recall, John you know, nobody really. In the vendor and user community. They didn't really pay too much attention to that. And then later that year, in August, it announced E C two people really started. They started to think about a new model of computing, but they were largely, you know, chicken tires. And it was kind of bleeding edge developers that really leaned in. Um what? What were you thinking at the time? When when you saw, uh, s three e c to this retail company coming into the tech world? >>I mean, I thought it was totally crap. I'm like, this is terrible. But then at that time, I was thinking working on I was in between kind of start ups and I didn't have a lot of seed funding. And then I realized the C two was freaking awesome. But I'm like, Holy shit, this is really great because I don't need to pay a lot of cash, the Provisional Data center, or get a server. Or, you know, at that time, state of the art startup move was to buy a super micro box or some sort of power server. Um, it was well past the whole proprietary thing. But you have to assemble probably anyone with 5 to 8 grand box and go in, and we'll put a couple ghetto rack, which is basically, uh, you know, you put it into some coasting location. It's like with everybody else in the tech ghetto of hosting, still paying monthly fees and then maintaining it and provisioning that's just to get started. And then Amazon was just really easy. And then from there you just It was just awesome. I just knew Amazon would be great. They had a lot of things that they had to fix. You know, custom domains and user interface Council got better and better, but it was awesome. >>Well, what we really saw the cloud take hold from my perspective anyway, was the financial crisis in, you know, 709 It put cloud on the radar of a number of CFOs and, of course, shadow I T departments. They wanted to get stuff done and and take I t in in in, ah, pecs, bite sized chunks. So it really was. There's cloud awakening and we came out of that financial crisis, and this we're now in this 10 year plus boom um, you know, notwithstanding obviously the economic crisis with cove it. But much of it was powered by the cloud in the decade. I would say it was really about I t transformation. And it kind of ironic, if you will, because the pandemic it hits at the beginning of this decade, >>and it >>creates this mandate to go digital. So you've you've said a lot. John has pulled forward. It's accelerated this industry transformation. Everybody talks about that, but and we've highlighted it here in this graphic. It probably would have taken several more years to mature. But overnight you had this forced march to digital. And if you weren't a digital business, you were kind of out of business. And and so it's sort of here to stay. How do you see >>You >>know what this evolution and what we can expect in the coming decades? E think it's safe to say the last 10 years defined by you know, I t transformation. That's not gonna be the same in the coming years. How do you see it? >>It's interesting. I think the big tech companies are on, but I think this past election, the United States shows um, the power that technology has. And if you look at some of the main trends in the enterprise specifically around what clouds accelerating, I call the second wave of innovations coming where, um, it's different. It's not what people expect. Its edge edge computing, for instance, has talked about a lot. But industrial i o t. Is really where we've had a lot of problems lately in terms of hacks and malware and just just overall vulnerabilities, whether it's supply chain vulnerabilities, toe actual disinformation, you know, you know, vulnerabilities inside these networks s I think this network effects, it's gonna be a huge thing. I think the impact that tech will have on society and global society geopolitical things gonna be also another one. Um, I think the modern application development of how applications were written with data, you know, we always been saying this day from the beginning of the Cube data is his integral part of the development process. And I think more than ever, when you think about cloud and edge and this distributed computing paradigm, that cloud is now going next level with is the software and how it's written will be different. You gotta handle things like, where's the compute component? Is it gonna be at the edge with all the server chips, innovations that Amazon apple intel of doing, you're gonna have compute right at the edge, industrial and kind of human edge. How does that work? What's Leighton see to that? It's it really is an edge game. So to me, software has to be written holistically in a system's impact on the way. Now that's not necessarily nude in the computer science and in the tech field, it's just gonna be deployed differently. So that's a complete rewrite, in my opinion of the software applications. Which is why you're seeing Amazon Google VM Ware really pushing Cooper Netease and these service messes in the micro Services because super critical of this technology become smarter, automated, autonomous. And that's completely different paradigm in the old full stack developer, you know, kind of model. You know, the full stack developer, his ancient. There's no such thing as a full stack developer anymore, in my opinion, because it's a half a stack because the cloud takes up the other half. But no one wants to be called the half stack developer because it doesn't sound as good as Full Stack, but really Cloud has eliminated the technology complexity of what a full stack developer used to dio. Now you can manage it and do things with it, so you know, there's some work to done, but the heavy lifting but taking care of it's the top of the stack that I think is gonna be a really critical component. >>Yeah, and that that sort of automation and machine intelligence layer is really at the top of the stack. This this thing becomes ubiquitous, and we now start to build businesses and new processes on top of it. I wanna I wanna take a look at the Big Three and guys, Can we bring up the other The next graphic, which is an estimate of what the revenue looks like for the for the Big three. And John, this is I asked and past spend for the Big Three Cloud players. And it's It's an estimate that we're gonna update after earning seasons, and I wanna point a couple things out here. First is if you look at the combined revenue production of the Big Three last year, it's almost 80 billion in infrastructure spend. I mean, think about that. That Z was that incremental spend? No. It really has caused a lot of consolidation in the on Prem data center business for guys like Dell. And, you know, um, see, now, part of the LHP split up IBM Oracle. I mean, it's etcetera. They've all felt this sea change, and they had to respond to it. I think the second thing is you can see on this data. Um, it's true that azure and G C P they seem to be growing faster than a W s. We don't know the exact numbers >>because >>A W S is the only company that really provides a clean view of i s and pass. Whereas Microsoft and Google, they kind of hide the ball in their numbers. I mean, I don't blame them because they're behind, but they do leave breadcrumbs and clues about growth rates and so forth. And so we have other means of estimating, but it's it's undeniable that azure is catching up. I mean, it's still quite distance the third thing, and before I want to get your input here, John is this is nuanced. But despite the fact that Azure and Google the growing faster than a W s. You can see those growth rates. A W s I'll call this out is the only company by our estimates that grew its business sequentially last quarter. Now, in and of itself, that's not significant. But what is significant is because AWS is so large there $45 billion last year, even if the slower growth rates it's able to grow mawr and absolute terms than its competitors, who are basically flat to down sequentially by our estimates. Eso So that's something that I think is important to point out. Everybody focuses on the growth rates, but it's you gotta look at also the absolute dollars and, well, nonetheless, Microsoft in particular, they're they're closing the gap steadily, and and we should talk more about the competitive dynamics. But I'd love to get your take on on all this, John. >>Well, I mean, the clouds are gonna win right now. Big time with the one the political climate is gonna be favoring Big check. But more importantly, with just talking about covert impact and celebrating the digital transformation is gonna create a massive rising tide. It's already happening. It's happening it's happening. And again, this shift in programming, uh, models are gonna really kinda accelerating, create new great growth. So there's no doubt in my mind of all three you're gonna win big, uh, in the future, they're just different, You know, the way they're going to market position themselves, they have to be. Google has to be a little bit different than Amazon because they're smaller and they also have different capabilities, then trying to catch up. So if you're Google or Microsoft, you have to have a competitive strategy to decide. How do I wanna ride the tide If you will put the rising tide? Well, if I'm Amazon, I mean, if I'm Microsoft and Google, I'm not going to try to go frontal and try to copy Amazon because Amazon is just pounding lead of features and scale and they're different. They were, I would say, take advantage of the first mover of pure public cloud. They really awesome. It passed and I, as they've integrated in Gardner, now reports and integrated I as and passed components. So Gardner finally got their act together and said, Hey, this is really one thing. SAS is completely different animal now Microsoft Super Smart because they I think they played the right card. They have a huge installed base converted to keep office 3 65 and move sequel server and all their core jewels into the cloud as fast as possible, clarified while filling in the gaps on the product side to be cloud. So you know, as you're doing trends job, they're just it's just pedal as fast as you can. But Microsoft is really in. The strategy is just go faster trying. Keep pedaling fast, get the features, feature velocity and try to make it high quality. Google is a little bit different. They have a little power base in terms of their network of strong, and they have a lot of other big data capabilities, so they have to use those to their advantage. So there is. There is there is competitive strategy game application happening with these companies. It's not like apples, the apples, In my opinion, it never has been, and I think that's funny that people talk about it that way. >>Well, you're bringing up some great points. I want guys bring up the next graphic because a lot of things that John just said are really relevant here. And what we're showing is that's a survey. Data from E. T. R R Data partners, like 1400 plus CEOs and I T buyers and on the vertical axis is this thing called Net score, which is a measure of spending momentum. And the horizontal axis is is what's called market share. It's a measure of the pervasiveness or, you know, number of mentions in the data set. There's a couple of key points I wanna I wanna pick up on relative to what John just said. So you see A W S and Microsoft? They stand alone. I mean, they're the hyper scale er's. They're far ahead of the pack and frankly, they have fall down, toe, lose their lead. They spend a lot on Capex. They got the flywheel effects going. They got both spending velocity and large market shares, and so, but they're taking a different approach. John, you're right there living off of their SAS, the state, their software state, Andi, they're they're building that in to their cloud. So they got their sort of a captive base of Microsoft customers. So they've got that advantage. They also as we'll hear from from Microsoft today. They they're building mawr abstraction layers. Andy Jassy has said We don't wanna be in that abstraction layer business. We wanna have access to those, you know, fine grain primitives and eso at an AP level. So so we can move fast with the market. But but But so those air sort of different philosophies, John? >>Yeah. I mean, you know, people who know me know that I love Amazon. I think their product is superior at many levels on in its way that that has advantages again. They have a great sass and ecosystem. They don't really have their own SAS play, although they're trying to add some stuff on. I've been kind of critical of Microsoft in the past, but one thing I'm not critical of Microsoft, and people can get this wrong in the marketplace. Actually, in the journalism world and also in just some other analysts, Microsoft has always had large scale eso to say that Microsoft never had scale on that Amazon owned the monopoly on our franchise on scales wrong. Microsoft had scale from day one. Their business was always large scale global. They've always had infrastructure with MSN and their search and the distributive how they distribute browsers and multiple countries. Remember they had the lock on the operating system and the browser for until the government stepped in in 1997. And since 1997 Microsoft never ever not invested in infrastructure and scale. So that whole premise that they don't compete well there is wrong. And I think that chart demonstrates that there, in there in the hyper scale leadership category, hands down the question that I have. Is that there not as good and making that scale integrate in because they have that legacy cards. This is the classic innovator's dilemma. Clay Christensen, right? So I think they're doing a good job. I think their strategy sound. They're moving as fast as they can. But then you know they're not gonna come out and say We don't have the best cloud. Um, that's not a marketing strategy. Have to kind of hide in this and get better and then double down on where they're winning, which is. Clients are converting from their legacy at the speed of Microsoft, and they have a huge client base, So that's why they're stopping so high That's why they're so good. >>Well, I'm gonna I'm gonna give you a little preview. I talked to gear up your f Who's gonna come on today and you'll see I I asked him because the criticism of Microsoft is they're, you know, they're just good enough. And so I asked him, Are you better than good enough? You know, those are fighting words if you're inside of Microsoft, but so you'll you'll have to wait to see his answer. Now, if you guys, if you could bring that that graphic back up I wanted to get into the hybrid zone. You know where the field is. Always got >>some questions coming in on chat, Dave. So we'll get to those >>great Awesome. So just just real quick Here you see this hybrid zone, this the field is bunched up, and the other companies who have a large on Prem presence and have been forced to initiate some kind of coherent cloud strategy included. There is Michael Michael, multi Cloud, and Google's there, too, because they're far behind and they got to take a different approach than a W s. But as you can see, so there's some real progress here. VM ware cloud on AWS stands out, as does red hat open shift. You got VM Ware Cloud, which is a VCF Cloud Foundation, even Dell's cloud. And you'd expect HP with Green Lake to be picking up momentum in the future quarters. And you've got IBM and Oracle, which there you go with the innovator's dilemma. But there, at least in the cloud game, and we can talk about that. But so, John, you know, to your point, you've gotta have different strategies. You're you're not going to take out the big too. So you gotta play, connect your print your on Prem to your cloud, your hybrid multi cloud and try to create new opportunities and new value there. >>Yeah, I mean, I think we'll get to the question, but just that point. I think this Zeri Chen's come on the Cube many times. We're trying to get him to come on lunch today with Features startup, but he's always said on the Q B is a V C at Greylock great firm. Jerry's Cloud genius. He's been there, but he made a point many, many years ago. It's not a winner. Take all the winner. Take most, and the Big Three maybe put four or five in there. We'll take most of the markets here. But I think one of the things that people are missing and aren't talking about Dave is that there's going to be a second tier cloud, large scale model. I don't want to say tear to cloud. It's coming to sound like a sub sub cloud, but a new category of cloud on cloud, right? So meaning if you get a snowflake, did I think this is a tale? Sign to what's coming. VM Ware Cloud is a native has had huge success, mainly because Amazon is essentially enabling them to be successful. So I think is going to be a wave of a more of a channel model of indirect cloud build out where companies like the Cube, potentially for media or others, will build clouds on top of the cloud. So if Google, Microsoft and Amazon, whoever is the first one to really enable that okay, we'll do extremely well because that means you can compete with their scale and create differentiation on top. So what snowflake did is all on Amazon now. They kind of should go to azure because it's, you know, politically correct that have multiple clouds and distribution and business model shifts. But to get that kind of performance they just wrote on Amazon. So there's nothing wrong with that. Because you're getting paid is variable. It's cap ex op X nice categorization. So I think that's the way that we're watching. I think it's super valuable, I think will create some surprises in terms of who might come out of the woodwork on be a leader in a category. Well, >>your timing is perfect, John and we do have some questions in the chat. But before we get to that, I want to bring in Sargi Joe Hall, who's a contributor to to our community. Sargi. Can you hear us? All right, so we got, uh, while >>bringing in Sarpy. Let's go down from the questions. So the first question, Um, we'll still we'll get the student second. The first question. But Ronald ask, Can a vendor in 2021 exist without a hybrid cloud story? Well, story and capabilities. Yes, they could live with. They have to have a story. >>Well, And if they don't own a public cloud? No. No, they absolutely cannot. Uh hey, Sergey. How you doing, man? Good to see you. So, folks, let me let me bring in Sergeant Kohala. He's a He's a cloud architect. He's a practitioner, He's worked in as a technologist. And there's a frequent guest on on the Cube. Good to see you, my friend. Thanks for taking the time with us. >>And good to see you guys to >>us. So we were kind of riffing on the competitive landscape we got. We got so much to talk about this, like, it's a number of questions coming in. Um, but Sargi we wanna talk about you know, what's happening here in Cloud Land? Let's get right into it. I mean, what do you guys see? I mean, we got yesterday. New regime, new inaug inauguration. Do you do you expect public policy? You'll start with you Sargi to have What kind of effect do you think public policy will have on, you know, cloud generally specifically, the big tech companies, the tech lash. Is it gonna be more of the same? Or do you see a big difference coming? >>I think that there will be some changing narrative. I believe on that. is mainly, um, from the regulators side. A lot has happened in one month, right? So people, I think are losing faith in high tech in a certain way. I mean, it doesn't, uh, e think it matters with camp. You belong to left or right kind of thing. Right? But parlor getting booted out from Italy s. I think that was huge. Um, like, how do you know that if a cloud provider will not boot you out? Um, like, what is that line where you draw the line? What are the rules? I think that discussion has to take place. Another thing which has happened in the last 23 months is is the solar winds hack, right? So not us not sort acknowledging that I was Russia and then wish you watching it now, new administration might have a different sort of Boston on that. I think that's huge. I think public public private partnership in security arena will emerge this year. We have to address that. Yeah, I think it's not changing. Uh, >>economics economy >>will change gradually. You know, we're coming out off pandemic. The money is still cheap on debt will not be cheap. for long. I think m and a activity really will pick up. So those are my sort of high level, Uh, >>thank you. I wanna come back to them. And because there's a question that chat about him in a But, John, how do you see it? Do you think Amazon and Google on a slippery slope booting parlor off? I mean, how do they adjudicate between? Well, what's happening in parlor? Uh, anything could happen on clubhouse. Who knows? I mean, can you use a I to find that stuff? >>Well, that's I mean, the Amazons, right? Hiding right there bunkered in right now from that bad, bad situation. Because again, like people we said Amazon, these all three cloud players win in the current environment. Okay, Who wins with the U. S. With the way we are China, Russia, cloud players. Okay, let's face it, that's the reality. So if I wanted to reset the world stage, you know what better way than the, you know, change over the United States economy, put people out of work, make people scared, and then reset the entire global landscape and control all with cash? That's, you know, conspiracy theory. >>So you see the riches, you see the riches, get the rich, get richer. >>Yeah, well, that's well, that's that. That's kind of what's happening, right? So if you start getting into this idea that you can't actually have an app on site because the reason now I'm not gonna I don't know the particular parlor, but apparently there was a reason. But this is dangerous, right? So what? What that's gonna do is and whether it's right or wrong or not, whether political opinion is it means that they were essentially taken offline by people that weren't voted for that. Weren't that when people didn't vote for So that's not a democracy, right? So that's that's a different kind of regime. What it's also going to do is you also have this groundswell of decentralized thinking, right. So you have a whole wave of crypto and decentralized, um, cyber punks out there who want to decentralize it. So all of this stuff in January has created a huge counterculture, and I had predicted this so many times in the Cube. David counterculture is coming and and you already have this kind of counterculture between centralized and decentralized thinking and so I think the Amazon's move is dangerous at a fundamental level. Because if you can't get it, if you can't get buy domain names and you're completely blackballed by by organized players, that's a Mafia, in my opinion. So, uh, and that and it's also fuels the decentralized move because people say, Hey, if that could be done to them, it could be done to me. Just the fact that it could be done will promote a swing in the other direction. I >>mean, independent of of, you know, again, somebody said your political views. I mean Parlor would say, Hey, we're trying to clean this stuff up now. Maybe they didn't do it fast enough, but you think about how new parlor is. You think about the early days of Twitter and Facebook, so they were sort of at a disadvantage. Trying to >>have it was it was partly was what it was. It was a right wing stand up job of standing up something quick. Their security was terrible. If you look at me and Cory Quinn on be great to have him, and he did a great analysis on this, because if you look the lawsuit was just terrible. Security was just a half, asshole. >>Well, and the experience was horrible. I mean, it's not It was not a great app, but But, like you said, it was a quick stew. Hand up, you know, for an agenda. But nonetheless, you know, to start, get to your point earlier. It's like, you know, Are they gonna, you know, shut me down? If I say something that's, you know, out of line, or how do I control that? >>Yeah, I remember, like, 2019, we involved closing sort of remarks. I was there. I was saying that these companies are gonna be too big to fail. And also, they're too big for other nations to do business with. In a way, I think MNCs are running the show worldwide. They're running the government's. They are way. Have seen the proof of that in us this year. Late last year and this year, um, Twitter last night blocked Chinese Ambassador E in us. Um, from there, you know, platform last night and I was like, What? What's going on? So, like, we used to we used to say, like the Chinese company, tech companies are in bed with the Chinese government. Right. Remember that? And now and now, Actually, I think Chinese people can say the same thing about us companies. Uh, it's not a good thing. >>Well, let's >>get some question. >>Let's get some questions from the chat. Yeah. Thank you. One is on M and a subject you mentioned them in a Who do you see is possible emanate targets. I mean, I could throw a couple out there. Um, you know, some of the cdn players, maybe aka my You know, I like I like Hashi Corp. I think they're doing some really interesting things. What do you see? >>Nothing. Hashi Corp. And anybody who's doing things in the periphery is a candidate for many by the big guys, you know, by the hyper scholars and number two tier two or five hyper scholars. Right. Uh, that's why sales forces of the world and stuff like that. Um, some some companies, which I thought there will be a target, Sort of. I mean, they target they're getting too big, because off their evaluations, I think how she Corpuz one, um, >>and >>their bunch in the networking space. Uh, well, Tara, if I say the right that was acquired by at five this week, this week or last week, Actually, last week for $500 million. Um, I know they're founder. So, like I found that, Yeah, there's a lot going on on the on the network side on the anything to do with data. Uh, that those air too hard areas in the cloud arena >>data, data protection, John, any any anything you could adhere. >>And I think I mean, I think ej ej is gonna be where the gaps are. And I think m and a activity is gonna be where again, the bigger too big to fail would agree with you on that one. But we're gonna look at white Spaces and say a white space for Amazon is like a monster space for a start up. Right? So you're gonna have these huge white spaces opportunities, and I think it's gonna be an M and a opportunity big time start ups to get bought in. Given the speed on, I think you're gonna see it around databases and around some of these new service meshes and micro services. I mean, >>they there's a There's a question here, somebody's that dons asking why is Google who has the most pervasive tech infrastructure on the planet. Not at the same level of other to hyper scale is I'll give you my two cents is because it took him a long time to get their heads out of their ads. I wrote a piece of around that a while ago on they just they figured out how to learn the enterprise. I mean, John, you've made this point a number of times, but they just and I got a late start. >>Yeah, they're adding a lot of people. If you look at their who their hiring on the Google Cloud, they're adding a lot of enterprise chops in there. They realized this years ago, and we've talked to many of the top leaders, although Curry and hasn't yet sit down with us. Um, don't know what he's hiding or waiting for, but they're clearly not geared up to chicken Pete. You can see it with some some of the things that they're doing, but I mean competed the level of Amazon, but they have strength and they're playing their strength, but they definitely recognize that they didn't have the enterprise motions and people in the DNA and that David takes time people in the enterprise. It's not for the faint of heart. It's unique details that are different. You can't just, you know, swing the Google playbook and saying We're gonna home The enterprises are text grade. They knew that years ago. So I think you're going to see a good year for Google. I think you'll see a lot of change. Um, they got great people in there. On the product marketing side is Dev Solution Architects, and then the SRE model that they have perfected has been strong. And I think security is an area that they could really had a lot of value it. So, um always been a big fan of their huge network and all the intelligence they have that they could bring to bear on security. >>Yeah, I think Google's problem main problem that to actually there many, but one is that they don't They don't have the boots on the ground as compared to um, Microsoft, especially an Amazon actually had a similar problem, but they had a wide breath off their product portfolio. I always talk about feature proximity in cloud context, like if you're doing one thing. You wanna do another thing? And how do you go get that feature? Do you go to another cloud writer or it's right there where you are. So I think Amazon has the feature proximity and they also have, uh, aske Compared to Google, there's skills gravity. Larger people are trained on AWS. I think Google is trying there. So second problem Google is having is that that they're they're more focused on, I believe, um, on the data science part on their sort of skipping the cool components sort of off the cloud, if you will. The where the workloads needs, you know, basic stuff, right? That's like your compute storage and network. And that has to be well, talk through e think e think they will do good. >>Well, so later today, Paul Dillon sits down with Mids Avery of Google used to be in Oracle. He's with Google now, and he's gonna push him on on the numbers. You know, you're a distant third. Does that matter? And of course, you know, you're just a preview of it's gonna say, Well, no, we don't really pay attention to that stuff. But, John, you said something earlier that. I think Jerry Chen made this comment that, you know, Is it a winner? Take all? No, but it's a winner. Take a lot. You know the number two is going to get a big chunk of the pie. It appears that the markets big enough for three. But do you? Does Google have to really dramatically close the gap on be a much, much closer, you know, to the to the leaders in orderto to compete in this race? Or can they just kind of continue to bump along, siphon off the ad revenue? Put it out there? I mean, I >>definitely can compete. I think that's like Google's in it. Then it they're not. They're not caving, right? >>So But But I wrote I wrote recently that I thought they should even even put mawr oven emphasis on the cloud. I mean, maybe maybe they're already, you know, doubling down triple down. I just I think that is a multi trillion dollar, you know, future for the industry. And, you know, I think Google, believe it or not, could even do more. Now. Maybe there's just so much you could dio. >>There's a lot of challenges with these company, especially Google. They're in Silicon Valley. We have a big Social Justice warrior mentality. Um, there's a big debate going on the in the back channels of the tech scene here, and that is that if you want to be successful in cloud, you have to have a good edge strategy, and that involves surveillance, use of data and pushing the privacy limits. Right? So you know, Google has people within the country that will protest contract because AI is being used for war. Yet we have the most unstable geopolitical seen that I've ever witnessed in my lifetime going on right now. So, um, don't >>you think that's what happened with parlor? I mean, Rob Hope said, Hey, bar is pretty high to kick somebody off your platform. The parlor went over the line, but I would also think that a lot of the employees, whether it's Google AWS as well, said, Hey, why are we supporting you know this and so to your point about social justice, I mean, that's not something. That >>parlor was not just social justice. They were trying to throw the government. That's Rob e. I think they were in there to get selfies and being protesters. But apparently there was evidence from what I heard in some of these clubhouse, uh, private chats. Waas. There was overwhelming evidence on parlor. >>Yeah, but my point is that the employee backlash was also a factor. That's that's all I'm saying. >>Well, we have Google is your Google and you have employees to say we will boycott and walk out if you bid on that jet I contract for instance, right, But Microsoft one from maybe >>so. I mean, that's well, >>I think I think Tom Poole's making a really good point here, which is a Google is an alternative. Thio aws. The last Google cloud next that we were asked at they had is all virtual issue. But I saw a lot of I T practitioners in the audience looking around for an alternative to a W s just seeing, though, we could talk about Mano Cloud or Multi Cloud, and Andy Jassy has his his narrative around, and he's true when somebody goes multiple clouds, they put you know most of their eggs in one basket. Nonetheless, I think you know, Google's got a lot of people interested in, particularly in the analytic side, um, in in an alternative, hedging their bets eso and particularly use cases, so they should be able to do so. I guess my the bottom line here is the markets big enough to have Really? You don't have to be the Jack Welch. I gotta be number one and number two in the market. Is that the conclusion here? >>I think so. But the data gravity and the skills gravity are playing against them. Another problem, which I didn't want a couple of earlier was Google Eyes is that they have to boot out AWS wherever they go. Right? That is a huge challenge. Um, most off the most off the Fortune 2000 companies are already using AWS in one way or another. Right? So they are the multi cloud kind of player. Another one, you know, and just pure purely somebody going 200% Google Cloud. Uh, those cases are kind of pure, if you will. >>I think it's gonna be absolutely multi cloud. I think it's gonna be a time where you looked at the marketplace and you're gonna think in terms of disaster recovery, model of cloud or just fault tolerant capabilities or, you know, look at the parlor, the next parlor. Or what if Amazon wakes up one day and said, Hey, I don't like the cubes commentary on their virtual events, so shut them down. We should have a fail over to Google Cloud should Microsoft and Option. And one of people in Microsoft ecosystem wants to buy services from us. We have toe kind of co locate there. So these are all open questions that are gonna be the that will become certain pretty quickly, which is, you know, can a company diversify their computing An i t. In a way that works. And I think the momentum around Cooper Netease you're seeing as a great connective tissue between, you know, having applications work between clouds. Right? Well, directionally correct, in my opinion, because if I'm a company, why wouldn't I wanna have choice? So >>let's talk about this. The data is mixed on that. I'll share some data, meaty our data with you. About half the companies will say Yeah, we're spreading the wealth around to multiple clouds. Okay, That's one thing will come back to that. About the other half were saying, Yeah, we're predominantly mono cloud we didn't have. The resource is. But what I think going forward is that that what multi cloud really becomes. And I think John, you mentioned Snowflake before. I think that's an indicator of what what true multi cloud is going to look like. And what Snowflake is doing is they're building abstraction, layer across clouds. Ed Walsh would say, I'm standing on the shoulders of Giants, so they're basically following points of presence around the globe and building their own cloud. They call it a data cloud with a global mesh. We'll hear more about that later today, but you sign on to that cloud. So they're saying, Hey, we're gonna build value because so many of Amazon's not gonna build that abstraction layer across multi clouds, at least not in the near term. So that's a really opportunity for >>people. I mean, I don't want to sound like I'm dating myself, but you know the date ourselves, David. I remember back in the eighties, when you had open systems movement, right? The part of the whole Revolution OS I open systems interconnect model. At that time, the networking stacks for S N A. For IBM, decadent for deck we all know that was a proprietary stack and then incomes TCP I p Now os I never really happened on all seven layers, but the bottom layers standardized. Okay, that was huge. So I think if you look at a W s or some of the comments in the chat AWS is could be the s n a. Depends how you're looking at it, right? And you could say they're open. But in a way, they want more Amazon. So Amazon's not out there saying we love multi cloud. Why would they promote multi cloud? They are a one of the clouds they want. >>That's interesting, John. And then subject is a cloud architect. I mean, it's it is not trivial to make You're a data cloud. If you're snowflake, work on AWS work on Google. Work on Azure. Be seamless. I mean, certainly the marketing says that, but technically, that's not trivial. You know, there are latent see issues. Uh, you know, So that's gonna take a while to develop. What? Do your thoughts there? >>I think that multi cloud for for same workload and multi cloud for different workloads are two different things. Like we usually put multiple er in one bucket, right? So I think you're right. If you're trying to do multi cloud for the same workload, that's it. That's Ah, complex, uh, problem to solve architecturally, right. You have to have a common ap ice and common, you know, control playing, if you will. And we don't have that yet, and then we will not have that for a for at least one other couple of years. So, uh, if you if you want to do that, then you have to go to the lower, lowest common denominator in technical sort of stock, if you will. And then you're not leveraging the best of the breed technology off their from different vendors, right? I believe that's a hard problem to solve. And in another thing, is that that that I always say this? I'm always on the death side, you know, developer side, I think, uh, two deaths. Public cloud is a proxy for innovative culture. Right. So there's a catch phrase I have come up with today during shower eso. I think that is true. And then people who are companies who use the best of the breed technologies, they can attract the these developers and developers are the Mazen's off This digital sort of empires, amazingly, is happening there. Right there they are the Mazen's right. They head on the bricks. I think if you don't appeal to developers, if you don't but extensive for, like, force behind educating the market, you can't you can't >>put off. It's the same game Stepping story was seeing some check comments. Uh, guard. She's, uh, linked in friend of mine. She said, Microsoft, If you go back and look at the Microsoft early days to the developer Point they were, they made their phones with developers. They were a software company s Oh, hey, >>forget developers, developers, developers. >>You were if you were in the developer ecosystem, you were treated his gold. You were part of the family. If you were outside that world, you were competitors, and that was ruthless times back then. But they again they had. That was where it was today. Look at where the software defined businesses and starve it, saying it's all about being developer lead in this new way to program, right? So the cloud next Gen Cloud is going to look a lot like next Gen Developer and all the different tools and techniques they're gonna change. So I think, yes, this kind of developer ecosystem will be harnessed, and that's the power source. It's just gonna look different. So, >>Justin, Justin in the chat has a comment. I just want to answer the question about elastic thoughts on elastic. Um, I tell you, elastic has momentum uh, doing doing very well in the market place. Thea Elk Stack is a great alternative that people are looking thio relative to Splunk. Who people complain about the pricing. Of course it's plunks got the easy button, but it is getting increasingly expensive. The problem with elk stack is you know, it's open source. It gets complicated. You got a shard, the databases you gotta manage. It s Oh, that's what Ed Walsh's company chaos searches is all about. But elastic has some riel mo mentum in the marketplace right now. >>Yeah, you know, other things that coming on the chat understands what I was saying about the open systems is kubernetes. I always felt was that is a bad metaphor. But they're with me. That was the TCP I peep In this modern era, C t c p I p created that that the disruptor to the S N A s and the network protocols that were proprietary. So what KUBERNETES is doing is creating a connective tissue between clouds and letting the open source community fill in the gaps in the middle, where kind of way kind of probably a bad analogy. But that's where the disruption is. And if you look at what's happened since Kubernetes was put out there, what it's become kind of de facto and standard in the sense that everyone's rallying around it. Same exact thing happened with TCP was people were trashing it. It is terrible, you know it's not. Of course they were trashed because it was open. So I find that to be very interesting. >>Yeah, that's a good >>analogy. E. Thinks the R C a cable. I used the R C. A cable analogy like the VCRs. When they started, they, every VC had had their own cable, and they will work on Lee with that sort of plan of TV and the R C. A cable came and then now you can put any TV with any VCR, and the VCR industry took off. There's so many examples out there around, uh, standards And how standards can, you know, flair that fire, if you will, on dio for an industry to go sort of wild. And another trend guys I'm seeing is that from the consumer side. And let's talk a little bit on the consuming side. Um, is that the The difference wouldn't be to B and B to C is blood blurred because even the physical products are connected to the end user Like my door lock, the August door lock I didn't just put got get the door lock and forget about that. Like I I value the expedience it gives me or problems that gives me on daily basis. So I'm close to that vendor, right? So So the middle men, uh, middle people are getting removed from from the producer off the technology or the product to the consumer. Even even the sort of big grocery players they have their APs now, uh, how do you buy stuff and how it's delivered and all that stuff that experience matters in that context, I think, um, having, uh, to be able to sell to thes enterprises from the Cloud writer Breuder's. They have to have these case studies or all these sample sort off reference architectures and stuff like that. I think whoever has that mawr pushed that way, they are doing better like that. Amazon is Amazon. Because of that reason, I think they have lot off sort off use cases about on top of them. And they themselves do retail like crazy. Right? So and other things at all s. So I think that's a big trend. >>Great. Great points are being one of things. There's a question in there about from, uh, Yaden. Who says, uh, I like the developer Lead cloud movement, But what is the criticality of the executive audience when educating the marketplace? Um, this comes up a lot in some of my conversations around automation. So automation has been a big wave to automate this automate everything. And then everything is a service has become kind of kind of the the executive suite. Kind of like conversation we need to make everything is a service in our business. You seeing people move to that cloud model. Okay, so the executives think everything is a services business strategy, which it is on some level, but then, when they say Take that hill, do it. Developers. It's not that easy. And this is where a lot of our cube conversations over the past few months have been, especially during the cova with cute virtual. This has come up a lot, Dave this idea, and start being around. It's easy to say everything is a service but will implement it. It's really hard, and I think that's where the developer lead Connection is where the executive have to understand that in order to just say it and do it are two different things. That digital transformation. That's a big part of it. So I think that you're gonna see a lot of education this year around what it means to actually do that and how to implement it. >>I'd like to comment on the as a service and subject. Get your take on it. I mean, I think you're seeing, for instance, with HP Green Lake, Dell's come out with Apex. You know IBM as its utility model. These companies were basically taking a page out of what I what I would call a flawed SAS model. If you look at the SAS players, whether it's salesforce or workday, service now s a P oracle. These models are They're really They're not cloud pricing models. They're they're basically you got to commit to a term one year, two year, three year. We'll give you a discount if you commit to the longer term. But you're locked in on you. You probably pay upfront. Or maybe you pay quarterly. That's not a cloud pricing model. And that's why I mean, they're flawed. You're seeing companies like Data Dog, for example. Snowflake is another one, and they're beginning to price on a consumption basis. And that is, I think, one of the big changes that we're going to see this decade is that true cloud? You know, pay by the drink pricing model and to your point, john toe, actually implement. That is, you're gonna need a whole new layer across your company on it is quite complicated it not even to mention how you compensate salespeople, etcetera. The a p. I s of your product. I mean, it is that, but that is a big sea change that I see coming. Subject your >>thoughts. Yeah, I think like you couldn't see it. And like some things for this big tech exacts are hidden in the plain >>sight, right? >>They don't see it. They they have blind spots, like Look at that. Look at Amazon. They went from Melissa and 200 millisecond building on several s, Right, Right. And then here you are, like you're saying, pay us for the whole year. If you don't use the cloud, you lose it or will pay by month. Poor user and all that stuff like that that those a role models, I think these players will be forced to use that term pricing like poor minute or for a second, poor user. That way, I think the Salesforce moral is hybrid. They're struggling in a way. I think they're trying to bring the platform by doing, you know, acquisition after acquisition to be a platform for other people to build on top off. But they're having a little trouble there because because off there, such pricing and little closeness, if you will. And, uh, again, I'm coming, going, going back to developers like, if you are not appealing to developers who are writing the latest and greatest code and it is open enough, by the way open and open source are two different things that we all know that. So if your platform is not open enough, you will have you know, some problems in closing the deals. >>E. I want to just bring up a question on chat around from Justin didn't fitness. Who says can you touch on the vertical clouds? Has your offering this and great question Great CP announcing Retail cloud inventions IBM Athena Okay, I'm a huge on this point because I think this I'm not saying this for years. Cloud computing is about horizontal scalability and vertical specialization, and that's absolutely clear, and you see all the clouds doing it. The vertical rollouts is where the high fidelity data is, and with machine learning and AI efforts coming out, that's accelerated benefits. There you have tow, have the vertical focus. I think it's super smart that clouds will have some sort of vertical engine, if you will in the clouds and build on top of a control playing. Whether that's data or whatever, this is clearly the winning formula. If you look at all the successful kind of ai implementations, the ones that have access to the most data will get the most value. So, um if you're gonna have a data driven cloud you have tow, have this vertical feeling, Um, in terms of verticals, the data on DSO I think that's super important again, just generally is a strategy. I think Google doing a retail about a super smart because their whole pitches were not Amazon on. Some people say we're not Google, depending on where you look at. So every of these big players, they have dominance in the areas, and that's scarce. Companies and some companies will never go to Amazon for that reason. Or some people never go to Google for other reasons. I know people who are in the ad tech. This is a black and we're not. We're not going to Google. So again, it is what it is. But this idea of vertical specialization relevant in super >>forts, I want to bring to point out to sessions that are going on today on great points. I'm glad you asked that question. One is Alan. As he kicks off at 1 p.m. Eastern time in the transformation track, he's gonna talk a lot about the coming power of ecosystems and and we've talked about this a lot. That that that to compete with Amazon, Google Azure, you've gotta have some kind of specialization and vertical specialization is a good one. But of course, you see in the big Big three also get into that. But so he's talking at one o'clock and then it at 3 36 PM You know this times are strange, but e can explain that later Hillary Hunter is talking about she's the CTO IBM I B M's ah Financial Cloud, which is another really good example of specifying vertical requirements and serving. You know, an audience subject. I think you have some thoughts on this. >>Actually, I lost my thought. E >>think the other piece of that is data. I mean, to the extent that you could build an ecosystem coming back to Alan Nancy's premise around data that >>billions of dollars in >>their day there's billions of dollars and that's the title of the session. But we did the trillion dollar baby post with Jazzy and said Cloud is gonna be a trillion dollars right? >>And and the point of Alan Answer session is he's thinking from an individual firm. Forget the millions that you're gonna save shifting to the cloud on cost. There's billions in ecosystems and operating models. That's >>absolutely the business value. Now going back to my half stack full stack developer, is the business value. I've been talking about this on the clubhouses a lot this past month is for the entrepreneurs out there the the activity in the business value. That's the new the new intellectual property is the business logic, right? So if you could see innovations in how work streams and workflow is gonna be a configured differently, you have now large scale cloud specialization with data, you can move quickly and take territory. That's much different scenario than a decade ago, >>at the point I was trying to make earlier was which I know I remember, is that that having the horizontal sort of features is very important, as compared to having vertical focus. You know, you're you're more healthcare focused like you. You have that sort of needs, if you will, and you and our auto or financials and stuff like that. What Google is trying to do, I think that's it. That's a good thing. Do cook up the reference architectures, but it's a bad thing in a way that you drive drive away some developers who are most of the developers at 80 plus percent, developers are horizontal like you. Look at the look into the psyche of a developer like you move from company to company. And only few developers will say I will stay only in health care, right? So I will only stay in order or something of that, right? So they you have to have these horizontal capabilities which can be applied anywhere on then. On top >>of that, I think that's true. Sorry, but I'll take a little bit different. Take on that. I would say yes, that's true. But remember, remember the old school application developer Someone was just called in Application developer. All they did was develop applications, right? They pick the framework, they did it right? So I think we're going to see more of that is just now mawr of Under the Covers developers. You've got mawr suffer defined networking and software, defined storage servers and cloud kubernetes. And it's kind of like under the hood. But you got your, you know, classic application developer. I think you're gonna see him. A lot of that come back in a way that's like I don't care about anything else. And that's the promise of cloud infrastructure is code. So I think this both. >>Hey, I worked. >>I worked at people solved and and I still today I say into into this context, I say E r P s are the ultimate low code. No code sort of thing is right. And what the problem is, they couldn't evolve. They couldn't make it. Lightweight, right? Eso um I used to write applications with drag and drop, you know, stuff. Right? But But I was miserable as a developer. I didn't Didn't want to be in the applications division off PeopleSoft. I wanted to be on the tools division. There were two divisions in most of these big companies ASAP. Oracle. Uh, like companies that divisions right? One is the cooking up the tools. One is cooking up the applications. The basketball was always gonna go to the tooling. Hey, >>guys, I'm sorry. We're almost out of time. I always wanted to t some of the sections of the day. First of all, we got Holder Mueller coming on at lunch for a power half hour. Um, you'll you'll notice when you go back to the home page. You'll notice that calendar, that linear clock that we talked about that start times are kind of weird like, for instance, an appendix coming on at 1 24. And that's because these air prerecorded assets and rather than having a bunch of dead air, we're just streaming one to the other. So so she's gonna talk about people, process and technology. We got Kathy Southwick, whose uh, Silicon Valley CEO Dan Sheehan was the CEO of Dunkin Brands and and he was actually the c 00 So it's C A CEO connecting the dots to the business. Daniel Dienes is the CEO of you I path. He's coming on a 2:47 p.m. East Coast time one of the hottest companies, probably the fastest growing software company in history. We got a guy from Bain coming on Dave Humphrey, who invested $750 million in Nutanix. He'll explain why and then, ironically, Dheeraj Pandey stew, Minuteman. Our friend interviewed him. That's 3 35. 1 of the sessions are most excited about today is John McD agony at 403 p. M. East Coast time, she's gonna talk about how to fix broken data architectures, really forward thinking stuff. And then that's the So that's the transformation track on the future of cloud track. We start off with the Big Three Milan Thompson Bukovec. At one oclock, she runs a W s storage business. Then I mentioned gig therapy wrath at 1. 30. He runs Azure is analytics. Business is awesome. Paul Dillon then talks about, um, IDs Avery at 1 59. And then our friends to, um, talks about interview Simon Crosby. I think I think that's it. I think we're going on to our next session. All right, so keep it right there. Thanks for watching the Cuban cloud. Uh huh.

>>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.

>>Hello, everyone. My name is Rick Pew. I'm a senior product manager at Mirant. This and I have been working on the Doctor Enterprise Container Cloud for the last eight months. Today we're gonna be talking about multi cloud kubernetes. So the first thing to kind of look at is, you know, is multi cloud rial. You know, the terms thrown around a lot and by the way, I should mention that in this presentation, we use the term multi cloud to mean both multi cloud, which you know in the technical sense, really means multiple public clouds and hybrid cloud means public clouds. And on Prem, uh, we use in this presentation will use the term multi cloud to refer to all different types of multiple clouds, whether it's all public cloud or a mixture of on Prem and Public Cloud or, for that matter, multiple on Prem clouds as doctor and price container. Cloud supports all of those scenarios. So it really well, let's look at some research that came out of flex era in their 2020 State of the cloud report. You'll notice that ah, 33% state that they've got multiple public and one private cloud. 53% say they've got multiple public and multiple private cloud. So if you have those two up, you get 86% of the people say that they're in multiple public clowns and at least one private cloud. So I think at this stage we could say that multi cloud is a reality. According to 4 51 research, you know, a number of CEO stated that the strong driver their desire was to optimize cost savings across their private and public clouds. Um, they also wanted to avoid vendor lock in by operating in multiple clouds and try to dissuade their teams from taking too much advantage of a given providers proprietary infrastructure. But they also indicated that there the complexity of using multiple clouds hindered the rate of adoption of doing it doesn't mean they're not doing it. It just means that they don't go assed fast as they would like to go in many cases because of the complexity. And here it Miranda's. We surveyed our customers as well, and they're telling us similar things, you know. Risk management, through the diversification of providers, is key on their list cost optimization and the democratization of allowing their development teams, uh, to create kubernetes clusters without having to file a nightie ticket. But to give them a self service, uh, cloud like environment, even if it's on prem or multi cloud to give them the ability to create their own clusters, resize their own clusters and delete their own clusters without needing to have I t. Or of their operations teams involved at all. But there are some challenges with this, with the different clouds you know require different automation. Thio provisioned the underlying infrastructure or deploy and operating system or deployed kubernetes, for that matter, in a given cloud. You could say that they're not that complicated. They all have, you know, very powerful consoles and a P I s to do that. But did you get across three or four or five different clouds? Then you have to learn three or four or five different AP ice and Web consoles in order to make that happen on in. That scenario is difficult to provide self service for developers across all the cloud options, which is what you want to really accelerate your application innovation. So what's in it for me? You know We've got a number of roles and their prizes developers, operators and business leaders, and they have somewhat different needs. So when the developer side the need is flexibility to meet their development schedules, Number one you know they're under constant pressure to produce, and in order to do that, they need flexibility and in this case, the flexibility to create kubernetes clusters and use them across multiple clouds. Now they also have C I C D tools, and they want them to be able to be normalized on automated across all of the the on prim and public clouds that they're using. You know, in many cases they'll have a test and deployment scenario where they'll want to create a cluster, deploy their software, run their test, score the tests and then delete that cluster because the only point of that cluster, perhaps, was to test ah pipeline of delivery. So they need that kind of flexibility. From the operator's perspective, you know, they always want to be able to customize the control of their infrastructure and deployment. Uh, they certainly have the desire to optimize their optics and Capex fans. They also want to support their develops teams who many times their their customers through a p I access for on Prem and public clouds burst. Scaling is something operators are interested in, and something public clouds can provide eso the ability to scale out into public clouds, perhaps from there on prem infrastructure in a seamless manner. And many times they need to support geographic distribution of applications either for compliance or performance reasons. So having you know, data centers all across the world and be able to specifically target a given region, uh, is high on their list. Business leaders want flexibility and confidence to know that you know, they're on prim and public cloud uh, deployments. Air fully supported. They want to be able, like the operator, optimize their cloud, spends business leaders, think about disaster recovery. So having the applications running and living in different data centers gives them the opportunity to have disaster recovery. And they really want the flexibility of keeping private data under their control. On on Prem In certain applications may access that on Prem. Other applications may be able to fully run in the cloud. So what should I look for in a container cloud? So you really want something that fully automates these cluster deployments for virtual machine or bare metal. The operating system, uh, and kubernetes eso It's not just deploying kubernetes. It's, you know, how do I create my underlying infrastructure of a VM or bare metal? How do I deploy the operating system? And then, on top of all that, I want to be able to deploy kubernetes. Uh, you also want one that gives a unified cluster lifecycle management across all the clouds. So these clusters air running software gets updated. Cooper Netease has a new release cycle. Uh, they come out with something new. It's available, you know, How do you get that across all of your clusters? That air running in multiple clouds. We also need a container cloud that can provide you the visibility through logging, monitoring and alerting again across all the clouds. You know, many offerings have these for a particular cloud, but getting that across multiple clouds, uh, becomes a little more difficult. The Doctor Enterprise Container cloud, you know, is a very strong solution and really meets many of these, uh, dimensions along the left or kind of the dimensions we went through in the last slide we've got on Prem and public clouds as of RG A Today we're supporting open stack and bare metal for the on Prem Solutions and AWS in the public cloud. We'll be adding VM ware very soon for another on Prem uh, solution as well as azure and G C P. So thank you very much. Uh, look forward, Thio answering any questions you might have and we'll call that a rap. Thank you. >>Hi, Rick. Thanks very much for that. For that talk, I I am John James. You've probably seen me in other sessions. I do marketing here in Miran Tous on. I wanted to to take this opportunity while we had Rick to ask some more questions about about multi cloud. It's ah, potentially a pretty big topic, isn't it, Rick? >>Yeah. I mean, you know, the devil's in the details and there's, uh, lots of details that we could go through if you'd like, be happy to answer any questions that you have. >>Well, we've been talking about hybrid cloud for literally years. Um, this is something that I think you know, several generations of folks in the in the I. A s space doing on premise. I s, for example, with open stack the way Miran Tous Uh does, um, found, um, you know, thought that that it had a lot of potential. A lot of enterprises believed that, but there were There were things stopping people from from making it. Really, In many cases, um, it required a very, ah, very high degree of willingness to create homogeneous platforms in the cloud and on the premise. Um, and that was often very challenging. Um, but it seems like with things like kubernetes and with the isolation provided by containers, that this is beginning to shift, that that people are actually looking for some degree of application portability between their own Prem and there and their cloud environments. And that this is opening up, Uh, you know, investment on interest in pursuing this stuff. Is that the right perception? >>Yeah. So let's let's break that down a little bit. So what's nice about kubernetes is through the a. P. I s are the same. Regardless of whether it's something that Google or or a W s is offering as a platform as a service or whether you've taken the upstream open source project and deploy it yourself on parameter in a public cloud or whatever the scenario might be or could be a competitor of Frances's product, the Kubernetes A. P I is the same, which is the thing that really gives you that application portability. So you know, the container itself is contained arising, obviously your application and minimizing any kind of dependency issues that you might have And then the ability to deploy that to any of the coup bernetti clusters you know, is the same regardless of where it's running, the complexity comes and how doe I actually spend up a cluster in AWS and open stack and D M Where and gp An azure. How do I build that infrastructure and and spin that up and then, you know, used the ubiquitous kubernetes a p I toe actually deploy my application and get it to run. So you know what we've done is we've we've unified and created A I use the word normalized. But a lot of times people think that normalization means that you're kind of going to a lowest common denominator, which really isn't the case and how we've attacked the the enabling of multi cloud. Uh, you know, what we've done is that we've looked at each one of the providers and are basically providing an AP that allows you to utilize. You know, whatever the best of you know, that particular breed of provider has and not, uh, you know, going to at least common denominator. But, you know, still giving you a ah single ap by which you can, you know, create the infrastructure and the infrastructure could be on Prem is a bare metal infrastructure. It could be on preeminent open stack or VM ware infrastructure. Any of the public clouds, you know, used to have a a napi I that works for all of them. And we've implemented that a p i as an extension to kubernetes itself. So all of the developers, Dev ops and operators that air already familiar operating within the, uh, within the aapi of kubernetes. It's very, very natural. Extension toe actually be able to spend up these clusters and deploy them >>Now that's interesting. Without giving away, obviously what? Maybe special sauce. Um, are you actually using operators to do this in the Cooper 90? Sense of the word? >>Yes. Yeah, we've extended it with with C R D s, uh, and and operators and controllers, you know in the way that it was meant to be extended. So Kubernetes has a recipe on how you extend their A P I on that. That's what we used as our model. >>That, at least to me, makes enormous sense. Nick Chase, My colleague and I were digging into operators a couple of weeks ago, and that's a very elegant technology. Obviously, it's a it's evolving very fast, but it's remarkably unintimidating once you start trying to write them. We were able toe to compose operators around Cron and other simple processes and just, >>you know, >>a couple of minutes on day worked, which I found pretty astonishing. >>Yeah, I mean, you know, Kubernetes does a lot of things and they spent a lot of effort, um, in being able, you know, knowing that their a p I was gonna be ubiquitous and knowing that people wanted to extend it, uh, they spent a lot of effort in the early development days of being able to define that a p I to find what an operator was, what a controller was, how they interact. How a third party who doesn't know anything about the internals of kubernetes could add whatever it is that they wanted, you know, and follow the model that makes it work. Exactly. Aziz, the native kubernetes ap CSTO >>What's also fascinating to me? And, you know, I've I've had a little perspective on this over the past, uh, several weeks or a month or so working with various stakeholders inside the company around sessions related to this event that the understanding of how things work is by no means evenly distributed, even in a company as sort of tightly knit as Moran Tous. Um, some people who shall remain nameless have represented to me that Dr Underprice Container Cloud basically works. Uh, if you handed some of the EMS, it will make things for you, you know, and this is clearly not what's going on that that what's going on is a lot more nuanced that you are using, um, optimal resource is from each provider to provide, uh, you know, really coherent architected solutions. Um, the load balancing the d. N s. The storage that this that that right? Um all of which would ultimately be. And, you know, you've probably tried this. I certainly have hard to script by yourself in answerable or cloud formation or whatever. Um, this is, you know, this is not easy work. I I wrote a about the middle of last year for my prior employer. I wrote a dip lawyer in no Js against the raw aws a piece for deployment and configuration of virtual networks and servers. Um, and that was not a trivial project. Um, it took a long time to get thio. Uh, you know, a dependable result. And to do it in parallel and do other things that you need to do in order to maintain speed. One of the things, in fact, that I've noticed in working with Dr Enterprise Container Cloud recently, is how much parallelism it's capable of within single platforms. It's It's pretty powerful. I mean, if you want to clusters to be deployed simultaneously, that's not hard for Doc. Aerated price container cloud to dio on. I found it pretty remarkable because I have sat in front of a single laptop trying to churn out of cluster under answerable, for example, and just on >>you get into that serial nature, your >>poor little devil, every you know, it's it's going out and it's ssh, Indian Terminals and it's pretending it's a person and it's doing all that stuff. This is much more magical. Um, so So that's all built into the system to, isn't it? >>Yeah. Interesting, Really Interesting point on that. Is that you know, the complexity isn't not necessarily and just creating a virtual machine because all of these companies have, you know, spend a lot of effort to try to make that as easy as possible. But when you get into networking, load balancing, routing, storage and hooking those up, you know, two containers automating that if you were to do that in terror form or answerable or something like that is many, many, many lines of code, you know, people have to experiment. Could you never get it right the first or second or the third time? Uh, you know, and then you have to maintain that. So one of the things that we've heard from customers that have looked a container cloud was that they just can't wait to throw away their answerable or their terror form that they've been maintaining for a couple of years. The kind of enables them to do this. It's very brittle. If if the clouds change something, you know on the network side, let's say that's really buried. And it's not something that's kind of top of mind. Uh, you know, your your thing fails or maybe worse, you think that it works. And it's not until you actually go to use it that you notice that you can't get any of your containers. So you know, it's really great the way that we've simplified that for the users and again democratizing it. So the developers and Dev ops people can create these clusters, you know, with ease and not worry about all the complexities of networking and storage. >>Another thing that amazed me as I was digging into my first, uh, Dr Price container Cloud Management cluster deployment was how, uh, I want I don't want to use the word nuanced again, but I can't think of a better word. Nuanced. The the security thinking is in how things air set up. How, um, really delicate the thinking about about how much credential power you give to the deploy. Er the to the seed server that deploys your management cluster as opposed thio Um uh or rather the how much how much administrative access you give to the to the administrator who owns the entire implementation around a given provider versus how much power the seed server gets because that gets its own user right? It gets a bootstrap user specifically created so that it's not your administrator, you know, more limited visibility and permissions. And this whole hierarchy of permissions is then extended down into the child clusters that this management cluster will ultimately create. So that Dev's who request clusters will get appropriate permissions granted within. Ah, you know, a corporate schema of permissions. But they don't get the keys to the kingdom. They don't have access to anything they don't you know they're not supposed to have access to, but within their own scope, they're safe. They could do anything they want, so it's like a It's a It's a really neat kind of elegant way of protecting organizations against, for example, resource over use. Um, you know, give people the power to deploy clusters, and basically you're giving them the power toe. Make sure that a big bill hits you know, your corporate accounting office at the end of the billing cycle, um so there have to be controls and those controls exist in this, you know, in this. >>Yeah, And there's kind of two flavors of that. One is kind of the day one that you're doing the deployment you mentioned the seed servers, you know, And then it creates a bastion server, and then it creates, you know, the management cluster and so forth, you know, and how all those permissions air handled. And then once the system is running, you know, then you have full access to going into key cloak, which is a very powerful open source identity management tool on you have dozens of, you know, granular permissions that you can give to an individual user that gives them permission to do certain things and not others within the context of kubernetes eso. It's really well thought out. And the defaults, you know, our 80% right. You know, there's very few people are gonna have to go in and sort of change those defaults. You mentioned the corporate directory. You know, hooks right upto l bap or active directory can suck everybody down. So there's no kind of work from a day. One perspective of having to go add. You know everybody that you can think of different teams and groupings of of people. Uh, you know, that's kind of all given from the three interface to the corporate directory. And so it just makes kind of managing the users and and controlling who can do what? Uh, really easy. And, you know, you know, day one day two it's really almost like our one hour to write because it's just all the defaults were really well thought out. You can deploy, you know, very powerful doctor and price container cloud, you know, within an hour, and then you could just start using it. And you know, you can create users if you want. You can use the default users. That air set up a time goes on, you can fine tune that, and it's a really, really nice model again for the whole frictionless democratization of giving developers the ability to go in and get it out of, you know, kind of their way and doing what they want to do. And I t is happy to do that because they don't like dozens of tickets and saying, you know, create a cluster for this team created cluster for that team. You know, here's the size of these guys. Want to resize when you know let's move all that into a self service model and really fulfill the prophecy of, you know, speeding up application development. >>It strikes me is extremely ironic that one of the things that public cloud providers bless them, uh, have always claimed, is that their products provide this democratization when in the experience, I think my own experience and the experience of most of the AWS developers, for example, not toe you know, name names, um, that I've encountered is that an initial experience of trying to start start a virtual machine and figuring out how to log into it? A. W s could take the better part of an afternoon. It's just it's not familiar once you have it in your fingers. Boom. Two seconds, right. But, wow, that learning curve is steep and precipitous, and you slip back and you make stupid mistakes your first couple 1000 times through the loop. Um, by letting people skip that and letting them skip it potentially on multiple providers, in a sense, I would think products like this are actually doing the public cloud industry is, you know, a real surface Hide as much of that as you can without without taking the power away. Because ultimately people want, you know, to control their destiny. They want choice for a reason. Um, and and they want access to the infinite services And, uh, and, uh, innovation that AWS and Azure and Google are all doing on their platforms. >>Yeah, you know, and they're solving, uh, very broad problems in the public clouds, you know, here were saying, you know, this is a world of containers, right? This is a world of orchestration of these containers. And why should I have to worry about the underlying infrastructure, whether it's a virtual machine or bare metal? You know, I shouldn't care if I'm an application developer developing some database application. You know, the last thing I wanna worry about is how do I go in and create a virtual machine? Oh, this is running. And Google. It's totally different than the one I was creating. An AWS I can't find. You know where I get the I P address in Google. It's not like it was an eight of us, you know, and you have to relearn the whole thing. And that's really not what your job is. Anyways, your job is to write data base coat, for example. And what you really want to do is just push a button, deploy a nor kiss traitor, get your app on it and start debugging it and getting it >>to work. Yep. Yeah, it's It's powerful. I've been really excited to work with the product the past week or so, and, uh, I hope that folks will look at the links at the bottoms of our thank you slides and, uh, and, uh, avail themselves of of free trial downloads of both Dr Enterprise Container, Cloud and Lens. Thank you very much for spending this extra time with me. Rick. I I think we've produced some added value here for for attendees. >>Well, thank you, John. I appreciate your help. >>Have a great rest of your session by bike. >>Okay, Thanks. Bye.

>>C G technology is focused on data where we have long believed that data is in our DNA. We help maximize humanity's potential by delivering world class, precision engineered data solutions developed through sustainable and profitable partnerships. Included in our offerings are hard disk drives. As I'm sure many of you know, ah, hard drive consists of a slider also known as a drive head or transducer attached to a head gimbal assembly. I had stack assembly made up of multiple head gimbal assemblies and a drive enclosure with one or more platters, or just that the head stacked assembles into. And while the concept hasn't changed, hard drive technology has progressed well beyond the initial five megabytes, 500 quarter inch drives that Seagate first produced. And, I think 1983. We have just announced in 18 terabytes 3.5 inch drive with nine flatters on a single head stack assembly with dual head stack assemblies this calendar year, the complexity of these drives further than need to incorporate Edge analytics at operation sites, so G Edward stemming established the concept of continual improvement and everything that we do, especially in product development and operations and at the end of World War Two, he embarked on a mission with support from the US government to help Japan recover from its four time losses. He established the concept of continual improvement and statistical process control to the leaders of prominent organizations within Japan. And because of this, he was honored by the Japanese emperor with the second order of the sacred treasure for his teachings, the only non Japanese to receive this honor in hundreds of years. Japan's quality control is now world famous, as many of you may know, and based on my own experience and product development, it is clear that they made a major impact on Japan's recovery after the war at Sea Gate. The work that we've been doing and adopting new technologies has been our mantra at continual improvement. As part of this effort, we embarked on the adoption of new technologies in our global operations, which includes establishing machine learning and artificial intelligence at the edge and in doing so, continue to adopt our technical capabilities within data science and data engineering. >>So I'm a principal engineer and member of the Operations and Technology Advanced Analytics Group. We are a service organization for those organizations who need to make sense of the data that they have and in doing so, perhaps introduce a different way to create an analyzed new data. Making sense of the data that organizations have is a key aspect of the work that data scientist and engineers do. So I'm a project manager for an initiative adopting artificial intelligence methodologies for C Gate manufacturing, which is the reason why I'm talking to you today. I thought I'd start by first talking about what we do at Sea Gate and follow that with a brief on artificial intelligence and its role in manufacturing. And I'd like them to discuss how AI and machine Learning is being used at Sea Gate in developing Edge analytics, where Dr Enterprise and Cooper Netease automates deployment, scaling and management of container raised applications. So finally, I like to discuss where we are headed with this initiative and where Mirant is has a major role in case some of you are not conversant in machine learning, artificial intelligence and difference outside some definitions. To cite one source, machine learning is the scientific study of algorithms and statistical bottles without computer systems use to effectively perform a specific task without using explicit instructions, relying on patterns and inference Instead, thus, being seen as a subset of narrow artificial intelligence were analytics and decision making take place. The intent of machine learning is to use basic algorithms to perform different functions, such as classify images to type classified emails into spam and not spam, and predict weather. The idea and this is where the concept of narrow artificial intelligence comes in, is to make decisions of a preset type basically let a machine learn from itself. These types of machine learning includes supervised learning, unsupervised learning and reinforcement learning and in supervised learning. The system learns from previous examples that are provided, such as images of dogs that are labeled by type in unsupervised learning. The algorithms are left to themselves to find answers. For example, a Siris of images of dogs can be used to group them into categories by association that's color, length of coat, length of snout and so on. So in the last slide, I mentioned narrow a I a few times, and to explain it is common to describe in terms of two categories general and narrow or weak. So Many of us were first exposed to General Ai in popular science fiction movies like 2000 and One, A Space Odyssey and Terminator General Ai is a I that can successfully perform any intellectual task that a human can. And if you ask you Lawn Musk or Stephen Hawking, this is how they view the future with General Ai. If we're not careful on how it is implemented, so most of us hope that is more like this is friendly and helpful. Um, like Wally. The reality is that machines today are not only capable of weak or narrow, a I AI that is focused on a narrow, specific task like understanding, speech or finding objects and images. Alexa and Google Home are becoming very popular, and they can be found in many homes. Their narrow task is to recognize human speech and answer limited questions or perform simple tasks like raising the temperature in your home or ordering a pizza as long as you have already defined the order. Narrow. AI is also very useful for recognizing objects in images and even counting people as they go in and out of stores. As you can see in this example, so artificial intelligence supplies, machine learning analytics inference and other techniques which can be used to solve actual problems. The two examples here particle detection, an image anomaly detection have the potential to adopt edge analytics during the manufacturing process. Ah, common problem in clean rooms is spikes in particle count from particle detectors. With this application, we can provide context to particle events by monitoring the area around the machine and detecting when foreign objects like gloves enter areas where they should not. Image Anomaly detection historically has been accomplished at sea gate by operators in clean rooms, viewing each image one at a time for anomalies, creating models of various anomalies through machine learning. Methodologies can be used to run comparative analyses in a production environment where outliers can be detected through influence in an automated real Time analytics scenario. So anomaly detection is also frequently used in machine learning to find patterns or unusual events in our data. How do you know what you don't know? It's really what you ask, and the first step in anomaly detection is to use an algorithm to find patterns or relationships in your data. In this case, we're looking at hundreds of variables and finding relationships between them. We can then look at a subset of variables and determine how they are behaving in relation to each other. We use this baseline to define normal behavior and generate a model of it. In this case, we're building a model with three variables. We can then run this model against new data. Observations that do not fit in the model are defined as anomalies, and anomalies can be good or bad. It takes a subject matter expert to determine how to classify the anomalies on classify classification could be scrapped or okay to use. For example, the subject matter expert is assisting the machine to learn the rules. We then update the model with the classifications anomalies and start running again, and we can see that there are few that generate these models. Now. Secret factories generate hundreds of thousands of images every day. Many of these require human toe, look at them and make a decision. This is dull and steak prone work that is ideal for artificial intelligence. The initiative that I am project managing is intended to offer a solution that matches the continual increased complexity of the products we manufacture and that minimizes the need for manual inspection. The Edge Rx Smart manufacturing reference architecture er, is the initiative both how meat and I are working on and sorry to say that Hamid isn't here today. But as I said, you may have guessed. Our goal is to introduce early defect detection in every stage of our manufacturing process through a machine learning and real time analytics through inference. And in doing so, we will improve overall product quality, enjoy higher yields with lesser defects and produce higher Ma Jin's. Because this was entirely new. We established partnerships with H B within video and with Docker and Amaranthus two years ago to develop the capability that we now have as we deploy edge Rx to our operation sites in four continents from a hardware. Since H P. E. And in video has been an able partner in helping us develop an architecture that we have standardized on and on the software stack side doctor has been instrumental in helping us manage a very complex project with a steep learning curve for all concerned. To further clarify efforts to enable more a i N M l in factories. Theobald active was to determine an economical edge Compute that would access the latest AI NML technology using a standardized platform across all factories. This objective included providing an upgrade path that scales while minimizing disruption to existing factory systems and burden on factory information systems. Resource is the two parts to the compute solution are shown in the diagram, and the gateway device connects to see gates, existing factory information systems, architecture ER and does inference calculations. The second part is a training device for creating and updating models. All factories will need the Gateway device and the Compute Cluster on site, and to this day it remains to be seen if the training devices needed in other locations. But we do know that one devices capable of supporting multiple factories simultaneously there are also options for training on cloud based Resource is the stream storing appliance consists of a kubernetes cluster with GPU and CPU worker notes, as well as master notes and docker trusted registries. The GPU nodes are hardware based using H B E l 4000 edge lines, the balance our virtual machines and for machine learning. We've standardized on both the H B E. Apollo 6500 and the NVIDIA G X one, each with eight in video V 100 GP use. And, incidentally, the same technology enables augmented and virtual reality. Hardware is only one part of the equation. Our software stack consists of Docker Enterprise and Cooper Netease. As I mentioned previously, we've deployed these clusters at all of our operations sites with specific use. Case is planned for each site. Moran Tous has had a major impact on our ability to develop this capability by offering a stable platform in universal control plane that provides us, with the necessary metrics to determine the health of the Kubernetes cluster and the use of Dr Trusted Registry to maintain a secure repository for containers. And they have been an exceptional partner in our efforts to deploy clusters at multiple sites. At this point in our deployment efforts, we are on prem, but we are exploring cloud service options that include Miranda's next generation Docker enterprise offering that includes stack light in conjunction with multi cluster management. And to me, the concept of federation of multi cluster management is a requirement in our case because of the global nature of our business where our operation sites are on four continents. So Stack Light provides the hook of each cluster that banks multi cluster management and effective solution. Open source has been a major part of Project Athena, and there has been a debate about using Dr CE versus Dr Enterprise. And that decision was actually easy, given the advantages that Dr Enterprise would offer, especially during a nearly phase of development. Cooper Netease was a natural addition to the software stack and has been widely accepted. But we have also been a work to adopt such open source as rabbit and to messaging tensorflow and tensor rt, to name three good lab for developments and a number of others. As you see here, is well, and most of our programming programming has been in python. The results of our efforts so far have been excellent. We are seeing a six month return on investment from just one of seven clusters where the hardware and software cost approached close to $1 million. The performance on this cluster is now over three million images processed per day for their adoption has been growing, but the biggest challenge we've seen has been handling a steep learning curve. Installing and maintaining complex Cooper needs clusters in data centers that are not used to managing the unique aspect of clusters like this. And because of this, we have been considering adopting a control plane in the cloud with Kubernetes as the service supported by Miranda's. Even without considering, Kubernetes is a service. The concept of federation or multi cluster management has to be on her road map, especially considering the global nature of our company. Thank you.

>> Live from San Diego, California It's the queue covering Sisqo live US 2019 Tio by Cisco and its ecosystem barters >> Welcome back to the cubes coverage of Day one of Sisqo Live from Sunny San Diego on Lisa Martin, my co hostess student. A man and Stuart are pleased to welcome a couple of guests from this Cisco platform and Solutions Group. We've got Barbara Half Li, senior director of Business development Barbeque. Great to have you nice to be here. And Matt Ferguson, director of product development. Matt, Welcome. >> Thank you. Nice to be here. >> So we appreciate you guys being here right at the start of happy hour here in San Diego. Thank you. Some our drinking water. Right wing quick. Just getting so, Barbara. So here we are at this's the 30th year Cisco's partner and customer, then a lot. A lot happens in 30 years. A lot of change here we are customers in every industry, living in this multi cloud hybrid world for many reasons. >> What are some >> of the things from the business perspective that you're hearing from customers? What are they looking to Sisko to do to help them traverse this new multi cloud world successfully. >> Yeah, well, one of the things that we hear customers tell us often is how doe I manage this landscape. Many people think of the cloud is just Oh, I've got a public cloud or oh, I'm gonna have my cloud on primp. But really, with the explosion of devices and I ot right, people want to know. How do we take that data from the edge from the edge? What do I do with that data? Do I put it up in a public cloud immediately? Do I bring it back to do some kind of analysis on that data? Is it goto a polo? Does it come to the branch doesn't go to the headquarters and that landscapes Very complex. So you look across that landscape and as customers of either proactively adopted the public cloud or had to adopt multiple clouds because of acquisitions they've made, this landscape just gets incredibly complex very, very quickly. So when people come to Cisco, they basically looking for a couple of things. Number one security. Because putting the security wrapper around all of that right, it becomes paramount. People lose their jobs if they're data isn't protected, so they want help with their security. They also want to know what's the best cost mix, right? How do I have the right options available to me? But the other thing they really want is speed of innovation. I mean, we hear this over and over and over. Uh, I talked to a bank the other day. 100 year old bank, right? You think 100 year old bank, um, speed of innovation may not be top of their priority, but absolutely. I walked in and they held up the phone and they said, Our competitors Aire delivering capabilities faster for the mobile user. And every time our competitors releases a new application or a new feature, I lose market share. So it isn't about cost savings anymore. It's about speed of innovation, even for 100 year old bank. When they come to Cisco, they want to know. Can you help secure this landscape? Can you give me speed of innovation? And then, of course, every cloud started the networking layer as well, Right? So what innovations is Cisco doing on the networking side? So these are some of the things that's customers come to Cisco and they ask us, what can you do for us and the help that they want? It comes back to innovation every time. >> Barbara. Actually, I've talked to some of those 100 year old Cos they need it more than ever, because that five year old bank doesn't have all the legacy and they're already moving is fast. But it's an interesting point. Matt. You know, we've been tracking community since the early days. This year, it finally feels like it's gotten to a certain maturity level, such that I've talked to a number of customers talking about how that is a lever for their digital transformation, how they're modernizing their application, pork portfolio and not just, you know, the, you know, making of the sausage of how this, you know, container orchestration, layers going toe, you know, do something that most people won't understand. It's that connection with the business kind of building up. What what robber says They're bring us inside a little bit more. You know the community's piece of that, >> Yeah, it's absolutely been tremendous to see the CNC F and Kume con absolutely just take off on the number of people that are attending. I think you been at ease as as a technology is really starting to hit its stride in the mainstream. It's a combination. I think of a number of factors. You have the developer community that's starting to really sort of embrace containers as they sort of re fact to their applications. So you have that going on, and then you have the ops persona or the people that actually have to manage and deploy the Cuban in these clusters that are starting to dive in and go waken. Take this on. We know what it means to actually manage a Cuban aunties cluster. The thing that what we're bringing, I think at Cisco is, ah, a curated staff. The opinionated stack, the ability to manage those clusters ability to actually deploy those clusters, whether it's on prime in the private in the private cloud, or leveraging the AP eyes that eight of us or Google or sure would publicly provide so that you can manage those clusters in the in the actual public's places. Well, so you have a combination of factors that are starting to come together. They're really sort of said, This is the opportunity that we're starting to see it happen right now. >> How would container ization looking at that example that Barber gave of the 100 year old bank needing to transform quickly? Otherwise, there there's so much competition, but not from your perspective. How what are some of the biggest advantage is that a legacy organization like 100 year old make is going to get by adopting containers. >> Yeah, so containers is one thing. So speed of innovation where they actually have to take their application. Asians, let's, for example, as a developer, you're have taken your monolithic applications re factor than into micro services. Now you have one piece of code turning into multiple different pieces of code in containers. Now what you have to do is you have to manage those containers, and that's where Cuban aunties comes in to be ableto orchestrate. Those containers in Google has really sort of offered this technology to the community, and that's where I think you know. You have the history of Google's, you know, operational sort of expertise, the open source ability to take uber Netease and then Sisko to sort of wrap around the lifecycle management of those containers so that you can not think about how, like the note operating system, the doctor run time, all the pieces that make up that stack and let the developers just focus on their code. And that's really what we're trying to do is enable the developers to focus on their code and not have, you know, on entire team of folks managing the cluster itself. >> So, Barbara, it's an open source community. There's a lot of partners involved. So what leads customers? Teo, turn to Sisko for these type of solutions. What differentiates them >> when you when you look at a company trying to do it on their own, I'm going to go do it is a service I'm gonna offer. Containers is a service right to do it on their own. Could take a year or more. I talked to a entertainment company the other day, and they had been working on trying to just define the requirements to do a container platform for a year. So if they could come to a company like Cisco and they can buy the container platform, we have as a sass offering, have it up and running in a matter of hours, which we have presidents of it running up in a couple of couple of hours and then delivering containers is a service to their constituents. It makes the team you're oh, right when you also look at how much it takes to curate that and then maintain it over time, the ability for us to actually consume the changes from the open source community curate that and release it is very fast. So from a nightie perspective, a nightie administrators perspective, you're able to take that offer it to the community, allow them to do development wherever they want to develop, whether it's in the public cloud, whether it's on from but maintain that, control it within the community, then you've got something right, and I mean, Matt could talk about that, too. But But then he'll agree. When we go to all the customers what our container pop firm does, how it leverages Coover Netease. How fast we give the updates out to our customers, and at the price point they are why we're talking about a month, two months. It is a pretty phenomenal opportunity for administrators to get something up and running an offering to their community very, very quickly. >> Yeah, No, you bring up some great points. They remember a couple of years ago when I talk to most customers, it's like, Well, what's your stack? Well, I pull these 35 different tools and I build all this stuff and I'm like, and I'm sorry, Don't you remember when we went to Cloud? It's about getting rid of that undifferentiated heavy lifting. Exactly why is this mission critical for your business to build and maintain this stack? And of course, the interest is for most customers out there. I want to consume it in platforms and from vendors that I trust so that I can focus on what's important in my business and drive the those business drivers. So it was a maturity thing for some of those early customers. So that Ari there, I mean, because Sisko, you've got your Cisco Container platform. You partner with the aid of Lewis's Googles. The world. Yeah, you know, Are we getting that point where customers shouldn't need to even think about that? That there's that communities and service measures and all that stuff in the >> middle of the number one goal is simplicity. And and what I would say with the container platform is that we are leveraging the speed of innovation that's occurring at the public cloud. So we're not taking a a curated stack from Cisco and putting it on the public cloud. We're leveraging the speed of innovation that that the public cloud provides. But at the same time, we're also taking that that cluster and we're putting it on crime into a private cloud. And I say Right now you're the point you're making is spot on, You know you don't necessarily in an ice tea shop with developers managing that entire stack from top to bottom. You know, why would you want to do that? And a recent quote that I heard recently was you either purchase or buy the product or you are the product, and I think that's a fascinating way to look at it because, you know, you could do that, you could curate it. You could absolutely, from top to bond curate the entire stock. But what typically happens that we're seeing from customers is well, um, organizations move on. They might not necessarily know what was built. They might be code that goes, gets older and expires, or you know gets out of dates. And so now you get stuck in an environment where your not terrified. But there's a nervousness, trepidation of going. I don't know, Let's not break it. If it ain't broke, don't fix it. And that's a lot of times what happens in these stacks. So I think we're absolutely with the CCP and the public how we're starting to actually get to that. >> So, Barbara, last question for you talking about the speed of innovation and when you were describing the massive fast R A Y customers can get by working with you guys from a container solution perspective, it's It's a no brainer as we look at some of the things that we know were coming. The wave of connectivity changes. Five. G WiFi sex. What excites you about how Cisco's story from a container platform perspective is going to change? Change as you start building and crisis that continued building technologies for these networks that are primarily wireless and incredibly fast. >> I think that's exciting for me is the way we approach the architecture, er way we're looking at certainly being more open, everything we do, building it with open AP eyes uh, and and looking across that Cisco stack knowing that at this moment in time, if you would've asked us five years ago Where are you? In cloud, Right? If you would've asked us 10 years ago, what are you going to do in Cloud? But at this moment in time to look at how we differentiate ourselves like I mentioned, every cloud started to the network. You've got to secure the entire infrastructure. You've gotta have connectivity between the clouds. Hence the CCP, the container platform, right. You have to have cloud management. You have to have cloud analytics way. Bring all of that together. So if a company has made investments and Cisco in the past, those those investments are going to come forward in this new multi cloud, multi tool man's domain landscape. And they can leverage those investments while they continue to invest with Cisco in innovations. And and that's what that's what really excites me. I think also just the world of a I and ML and big data And how when excites me is that developers Khun develop anywhere they can use all the great tools that are available. And I love the idea that the control is back in the hands of the I t administrator. From a compliance standpoint from a governance stand like we're bringing that control back into developers hands while giving the speed of innovation and the ability to develop anywhere back to the line of business in the developers. That combination is just really exciting at this moment in time. >> Awesome. And here we are in the definite zone. This is a massive community of over nearly 600,000. Strong, definite. So can you imagine all the innovation going on in this room behind us on day one? We'll we thank you both so much, Barbara, and not for joining stew and me on the A kid this afternoon. Lots of exciting things to come. Francisco or just the as I think, Chuck said this morning, were just getting started. >> We are just getting started. >> Absolutely. >> Guys are pleasure. Forced to mint a man, I'm Lisa Martin and you're watching The Cube from Cisco Live 2019

>> Live from San Diego, California It's the queue covering Sisqo Live US 2019 Tio by Cisco and its ecosystem barkers. >> Welcome back to the cubes Coverage of Day One of Sisqo Live from Sunny San Diego on Lisa Martin, my co hostess, student, a Man and Stewart Air. Pleased to welcome a couple of guests from this Cisco platform in Solutions Group, We've got Barbara Half Li, senior director of Business development Barbeque. Great to Have You Iced Beer and Matt Ferguson, director of product development. Matt, Welcome. >> Thank you. Nice to be here. >> So we appreciate you guys being here right at the start of happy hour here in San Diego. Thank you. Some our drinking water. Right wing quick. Just getting so, Barbara. So here we are at this's the 30th year Cisco's partner and customer, then a lot. A lot happens in 30 years. A lot of change here we are customers in every industry, living in this multi cloud hybrid world for many reasons. >> What are some >> of the things from the business perspective that you're hearing from customers? What are they looking to Sisko to do to help them traverse this new multi cloud world successfully. >> Yeah, well, one of the things that we hear customers tell us often is how doe I manage this landscape. Many people think of the cloud is just Oh, I've got a public cloud or oh, I'm gonna have my cloud on primp. But really, with the explosion of devices and I ot right, people want to know. How do we take that data from the edge from the edge? What do I do with that data? Do I put it up in a public cloud immediately? Do I bring it back to do some kind of analysis on that data? Is it goto a polo? Does it come to the branch doesn't go to the headquarters and that lance games very complex. So you look across that landscape and as customers of either proactively adopted the public cloud or had to adopt multiple clouds because of acquisitions, they've made this lands. Skip just gets incredibly complex very, very quickly. So when people come to Cisco, they basically looking for a couple of things. Number one security. Because putting the security wrapper around all of that right, it becomes paramount. People lose their jobs if they're data isn't protected, so they want help with their security. They also want to know what's the best cost mix, right? How do I have the right options available to me? But the other thing they really want is speed of innovation. I mean, we hear this over and over and over. I talked to a bank the other day. 100 year old bank, right? You think 100 year old bank, um, speed of innovation may not be top of their priority, but absolutely. I walked in and they held up the phone and they said, Our competitors Aire delivering capabilities faster for the mobile user. And every time our competitors releases a new application or a new feature, I lose market share. So it isn't about cost savings anymore. It's about speed of innovation, even for 100 year old bank. When they come to Cisco, they want to know, Can you help secure this landscape? Can you give me speed of innovation? And then, of course, every cloud started the networking layer as well, right? So what innovation Cisco doing on the networking site? So these are some of the things that's customers come to Cisco and they ask us, what can you do for us and the help that they want? It comes back to innovation every time. >> Barbara. Actually, I've talked to some of those homes year old cos they need it more than ever, because that five year old bank doesn't have all the legacy and they're already moving is fast. But it's an interesting point. Matt. You know, we've been tracking community since the early days. This year, it finally feels like it's gotten to a certain maturity level, such that I've talked to a number of customers talking about how that is a lever for their digital transformation, how they're modernizing their application for portfolio and not just, you know, the, you know, making of the sausage of how this, you know, container orchestration, layers going toe, you know, do something that most people won't understand. It's that connection with the business kind of building up. What what? Barber says. They're bring us inside a little bit more. You know the community's piece of that, >> Yeah, it's absolutely been tremendous to see the CNC F and Kume con absolutely just take off on the number of people that are attending. I think humanity's as as a technology is really starting to hit its stride in the mainstream. It's a combination. I think of a number of factors. You have the developer community that's starting to really sort of embrace containers as they sort of re fact to their applications. So you have that going on, and then you have the ops persona or the people that actually have to manage and deploy the Cuban in these clusters that are starting to dive in and go waken. Take this on. We know what it means to actually manage a Cuban aunties cluster. The thing that what we're bringing, I think at Cisco is, ah, a curated staff. The opinionated stack, the ability to manage those clusters ability to actually deploy those clusters, whether it's on prime in the private in the private cloud, or leveraging the AP eyes that eight of us or Google or azure would publicly provide so that you can manage those clusters in the in the actual public's places. Well, so you have a combination of factors that are starting to come together. They're really sort of said, This is the opportunity, and we're starting to see it happen right now, >> how would container ization looking at that example, that Barber gave up 100 year old bank needing to transform quickly. Otherwise, there there's so much competition, but not from your perspective. How what are some of the biggest advantage is that a legacy organization like 100 year old make is going to get by adopting containers. >> Yeah, so containers is one thing. So speed of innovation where they actually have to take their application. Shins. Let's, for example, as a developer, you're have taken your monolithic applications re factor than into micro services. Now you have one piece of code turning into multiple different pieces of code in containers. Now what you have to do is you have to manage those containers, and that's where Cuban aunties comes in to be ableto orchestrate. Those containers in Google has really sort of offered this technology to the community, and that's where I think you know. You have the history of Google's, you know, operational sort of expertise, the open source ability to take uber Netease and then Sisko to sort of wrap around the lifecycle management of those containers so that you can not think about how, like note operating system, the doctor run time, all the pieces that make up that stack and let the developers just focus on their code. And that's really what we're trying to do is enable the developers to focus on their code and not have, you know, on entire team of folks managing the cluster itself. >> So, Barbara, it's an open source community. There's a lot of partners involved. So what leads customers? Teo, turn to Sisko for these type of solutions. What differentiates them >> when you when you look at a company trying to do it on their own, I'm going to go do it is a service I'm gonna offer. Containers is a service right to do it on their own. Could take a year or more. I talked to a entertainment company the other day, and they had been working on trying to just define the requirements to do a container platform for a year. So if they could come to a company like Cisco and they can buy the container platform, we have as a sass offering, have it up and running in a matter of hours, which we have presidents of it running up in a couple of couple of dollars and then delivering containers is a service to their constituents. It makes the team a hero, right when you also look at how much it takes to curate that and then maintain it over time, the ability for us to actually consume the changes from the open source community curate that and release it is very fast. So from a nightie perspective, a nightie administrators perspective, you're able to take that offer it to the community, allow them to do development wherever they want to develop, whether it's in the public cloud, whether it's on from but maintain that, control it within the community, then you've got something right, and I mean, that could talk about that, too. But but then he'll agree. When we go to all the customers what our container pop firm does, how it leverages Cooper Netease. How fast we give the updates out to our customers and at the price point, the r o. Why we're talking about a month, two months. It is a pretty phenomenal opportunity for administrators to get something up and running an offering to their community very, very quickly. >> Yeah, no, you bring up some great points. They remember a couple of years ago. When I talk to most customers, it's like, Well, what's your stack? Well, I pull these 35 different tools and I build all this stuff down like and I'm sorry, Don't you remember when we went to Cloud? It's about getting rid of that undifferentiated heavy lifting. Exactly why is this mission critical for your business to build and maintain this stack? And of course, the interest is for most customers out there. I want to consume it in platforms and from vendors that I trust so that I can focus on what's important in my business and drive the those business drivers. So it was a maturity thing for some of those early customers. So that Ari there, I mean, because Sisko, you've got your Cisco Container platform. You partner with the aid of Lewis's Googles. The world. Yeah, you know, Are we getting that point where customers shouldn't need to even think about that? That there's that communities and service measures and all that stuff in the >> middle of the number one goal is simplicity. And and what I would say with the container platform is that we are leveraging the speed of innovation that's occurring at the public cloud. So we're not taking a a curated stack from Cisco and putting it on the public cloud. We're leveraging the speed of innovation that that the public cloud provides. But at the same time, we're also taking that that cluster and we're putting it on prime into a private cloud. And I say Right now you're the point you're making is spot on, You know you don't necessarily in an ice tea shop with developers managing that entire stack from top to bottom, you know, why would you want to do that? And a recent quote that I heard recently was your either purchase or buy the product or you are the product, and I think that's a fascinating way to look at it because, you know, you could do that, you could curate it. You could absolutely, from top to bond curate the entire stock. But what typically happens that we're seeing from customers is well, organisations move on. They might not necessarily know what was built. They might be code that goes, gets older and expires or, you know, gets out of dates. And so now you get stuck in an environment where your not terrified. But there's a nervousness, trepidation of going. I don't know, Let's not break it. If it ain't broke, don't fix it. And that's a lot of times what happens in these stacks. So I think we're absolutely with The CCP and the public file were starting to actually get to that >> barber last question for you talking about the speed of innovation and when you were describing the massively fast R a y that customers can get by working with you guys from the container solution perspective, it's It's a no brainer because we look at some of the things that we know were coming. The wave of connectivity changes. Five. G. WiFi sex. What excites you about how Cisco's story from a container platform perspective is gonna change? Change as you start building and crisis that continued building technologies for these networks that are primarily wireless and incredibly fast. >> I think that's exciting for me is the way we approach the architecture, er way we're looking at certainly being more open. Everything we do, building it with open AP eyes, uh, and and looking across that Francisco stack knowing that at this moment in time, If you would've asked us five years ago Where are you? In cloud, right? If you would've asked us 10 years ago, what are you going to do in cloud? But at this moment in time to look at how we differentiate ourselves Like I mentioned, every cloud started to the network. You've got to secure the entire infrastructure. You've gotta have connectivity between the clouds. Hence the CCP, the container platform, right. You have to have cloud management. You have to have cloud analytics way. Bring all of that together. So if a company has made investments and Cisco in the past, those those investments are going to come forward in this new multi cloud, multi tool man domain landscape. And they can leverage those investments while they continue to invest with Cisco in innovations. And And that's what That's what really excites me. I think also just the world of a I and ML and big data. And how when excites me is that developers Khun develop anywhere they can use all the great tools that are available. And I love the idea that the control is back in the hands of the I T administrator from a compliance standpoint from a governance stand like we're bringing that control back into developers hands while giving the speed of innovation and the ability to develop anywhere back to the line of business in the developers. That combination is just really exciting at this moment in time. >> Awesome. And here we are in the definite zone. This is a massive community of over nearly 600,000. Strong, definite. So imagine all the innovation going on in this room behind us on day one. We'll we thank you both so much, Barbara, and not for joining stew and me on the kid this afternoon. Lots of exciting things to come. Francisco or just the as I think, Chuck said this morning, were just getting started. >> We are just getting started. >> Absolutely. >> Guys are pleasure. Forced to mint a man, I'm Lisa Martin and you're watching The Cube from Cisco Live 2019

>> from our studios in the heart of Silicon Valley. HOLLOWAY ALTO, California It is a cube conversation. >> Welcome to this Special Cube conversation here in Palo Alto, California at the Cube Studios at the Cube headquarters. I'm John for the host, like you were a Dustin Kirkland product manager and Google friend of the Cuban. The community with Cooper Netease been on the Cube Cube alumni. Dustin. Welcome to the Cube conversation. >> Thanks. John's a beautiful studio. I've never been in the studio and on the show floor a few times, but this is This is fun. >> Great to have you on a great opportunity to chat about Cooper Netease yet of what you do out some product man's working Google. But really more importantly on this conversation is about the fifth anniversary, the birthday of Cuba Netease. Today we're celebrating the fifth birthday of Cooper Netease. Still, it's still a >> toddler, absolutely still growing. You think about how you know Lennox has been around for a long time. Open stack has been around these other big projects that have been around for, you know, going on decades and Lenox this case and Cooper nineties. It's going so fast, but It's only five years old, you know. >> You know, I remember Adam Open Stack event in Seattle many, many years ago. That was six years ago. Pubes on his 10th year. So many of these look backs moments. This is one of them. I was having a beer with Lou Tucker. J J Kiss Matic was like one of the first comes at the time didn't make it, But we were talking about open stagger like this Cooper Netease thing. This is really hot. This paper, this initiative this could really be the abstraction layer to kind of bring all this cloud Native wasn't part of the time, but it was like more of an open stack. Try and move up to stack. And it turned out it ended up happening. Cooper Netease then went on to change the landscape of what containers did. Dr. Got a lot of credit for pioneering that got the big VC funding became a unicorn, and then containers kind of went into a different direction because of Cooper duties. >> Very much so. I mean, the modernization of software infrastructure has been coming for a long time, and Cooper nutty sort of brings it all brings it all together at this point, but putting software into a container. We've been doing that different forest for for a lot of time, uh, for a long time, but But once you have a lot of containers, what do you do with that? Right? And that was the problem that Cooper Nettie solved so eloquently and has, you know, now for a couple of years, and it just keeps getting better. >> You know, you mentioned modernization. Let's talk about that because I think the modernization the theme is now pretty much prevalent in every vertical. I'll be in D. C. Next week for the Amazon Webster was public sector Summit, where modernization of governments and nations are being discussed. Education, modernization of it. We've seen it here. The media business that were participating in is about not where you store the code. It's how you code. How you build is a mindset shift. This has been the rial revelation around the Dev Ops Movement Infrastructures Code, now called Cloud Native. Share your thoughts on this modernization mindset because it really is how you build. >> Yeah, I think the cross pollination actually across industries and we even we see that even just in the word containers, right and all the imagery around shipping and shipping containers, we've applied these age old concepts that have been I don't have perfected but certainly optimized over decades of, actually centuries or millennia of moving things across water in containers. Right. But we apply that to software and boom. We have the step function difference in the way that we we manage and we orchestrated and administer code. That's one example of that cross pollination, and now you're talking about, like optimizing optimized governments or economies but being able to maybe then apply other concepts that we've come a long way in computer science do de bop set a good example? You know, applying Dev ops principles to non computer feels. Just think about that for a second. >> It's mind blowing. And if you think about also the step function you mentioned because I think this actually changed a lot of the entrepreneurial landscape as well and also has shaped open source and, you know, big news this this quarter is map are going to shut down due one of the biggest do players. Cloudera merge with Horton Works fired their CEO, the founder Michael. So has retired, Some say forced out. I don't think so. I think it's more of his time. I'm Rodel still there. Open source is a business model, you know. Can we be the red hat for her? Duped the red? Not really kind of the viable, but it's evolving. So open source has been impacted by this step function. There's a business impact. Talk about the dynamics with step function both on the business side and on how software's built specifically open source. >> You know, you and I have been around open source for a long, long time. I think it started when I was in college in the late nineties on then through my career at IBM. And it's It's interesting how on the fringe open source was for so long and such so so much of my BM career. And then early time spent onside it at Red Hat. It was it was something that was it was different, was weird. It was. It was very much fringe where the right uh, but now it's in mainstream and it's everywhere, and it's so mainstream that it's almost the defacto standard to just start with open source. But you know, there's some other news that's been happening lately that she didn't bring up. But it's a really touchy aspect of open source right now on that's on some of the licenses and how those licenses get applied by software, especially databases. When offered as a service in the cloud. That's one of the big problems. I think that that's that we're we're working within the open >> source, summarize the news and what it means. What's what's happening? What's the news and what's the really business? Our technical impact to the licensing? What's the issue? What's the core issue? >> Yeah, eso without taking judgment any any way, shape or form on this, the the the TL D are on. This is a number of open source database is most recently cockroach D. B. I have adopted a different licensing model that is nonstandard from an open source perspective. Uh, and from one perspective, they're they're adopting these different licensing models because other vendors can take that software and offered as a service, yes, and in some some cases, like Amazon like Sure, you said, uh, and offered as a as a service, uh, and maybe contribute. Maybe pay money to the smaller startup or the open source community behind it. But not necessarily. Uh, and it's in some ways is quite threatening to open source communities and open source companies on other cases, quite empowering. And it's going to be interesting to see how that plays out. The tension between open sourcing software and eventually making money off of it is something that we've we've seen for, you know, at least 25. >> And it continues to go on today, and this is, to me a real fascinating area that I think is going to be super important to keep an eye on because you want to encourage contribution and openness. Att the same time we look at the scale of just the Lenox foundations numbers. It's pretty massive in terms of now, the open source contribution. When you factor in even China and other nations, it's it's on exponential growth, right? So is it just open source? Is the model not necessarily a business? Yeah. So this is the big question. No one knows. >> I think we crossed that. And open source is the model. Um, and this is where me is a product manager. That's worked around open source. I've spent a lot of time thinking about how to create commercial offerings around open source. I spent 10 years at Economical, the first half of which, as an engineer, the second half of which, as a product manager around, uh, about building services, commercial services around 12 And I learned quite a few things that now apply absolutely to communities as well as to a number of open source startups. That that I've advised on DH kind of given them some perspective on maybe some successful and unsuccessful ways to monetize that that opens. >> Okay, so doesn't talk about Let's get back to Coburg. And so I think this is the next level Talk track is as Cooper Netease has established itself and landed in the industry and has adoption. It's now an expansion votes the land adopted expand. We've seen adoption. Now it's an expansion mode. Where does it go from here? Because you look at the tale signs things like service meshes server. Listen, you get some interesting trends that going to support this expansionary stage of uber netease. What is your view about the next expansion everyway what >> comes next? Yeah, I I think I think the next stage is really about democratizing communities for workloads that you know. It's quite obvious where when communities is the right answer at the scale of a Google or a Twitter or Netflix or, you know, some of these massive services that it is obviously and clearly the best answer to orchestrating containers. Now I think the next question is, how does that same thing that works at that massive scale Also worked for me as a developer at a very small scale helped me develop my software. My small team of five or 10 people. Do I need a coup? Burnett. He's If I'm ah five or 10 person startup. Well, I mean, not the original sort of borde vision of communities. It's probably overkill, but actually the tooling has really advanced, and we now >> have >> communities that makes sense on very small scales. You've got things like a three s from from Rancher. You've got micro Kates from from my colleagues at economical other ways of making shrinking communities down to something that fits, perhaps on devices perhaps at the edge, beyond just the traditional data center and into remote locations that need to deploy manage applications >> on the Cooper Netease clustering the some of the tech side. You know, we've seen some great tech trends as mentioned in Claudia Horton. Works and map Our Let's Take Claudia and Horton work. Remember back in the old days when it was booming? Oh, they were so proud to talk about their clusters. I stood up all these clusters and then I would ask them, Well, what do you doing with it? Well, we're storing data. I think so. That became kind of this use case where standing up the cluster was the use case and they're like, OK, now let's put some data in it. It's a question for you is Coburn. Eddie's a little bit different. I'm not seeing they were seeing real use cases. What are people standing up? Cuban is clusters for what specific Besides the same Besides saying I've done it. Yeah, What's the what's the main use case that you're seeing this that has real value? >> Yeah, actually, there's you just jog t mind of really funny memory. You know, back in those big data days, I was CEO of a startup. We were encrypting data, and we were helping encrypt healthcare data for health care companies and the number of health care companies that I worked with at that time who said they had a big data problem and they had all of I don't know, 33 terabytes worth of worth of data that they needed to encrypt. It was kind of humorous sometimes like, Is that really a big, big data problem? This fits on a single disc, you know, Uh, but yeah, I mean, it's interesting how >> that the hype of of the tech was preceding. The reality needs needs, says Cooper Nettie. So I have a Cuban Eddie's cluster for blank. Fill in the blank. What are people saying? >> Yeah, uh, it's It's largely about the modernization. So I need to modernize my infrastructure. I'm going to adopt the platform. That's probably not, er, the old er job, a Web WebSphere type platform or something like that. I'm investing in hardware investing in Software Middle, where I'm investing in people, and I want all of those things to line up with where industry is going from a software perspective, and that's where Cooper Nighties is sort of the cornerstone piece of that Lennox Of course, that's That's pretty well established >> canoes delivery in an integration piece of is that the pipeline in was, that was the fit on the low hanging fruit use cases of Cooper Netease just development >> process. Or it's the operations it's the operations of now got software that I need to deploy across multiple versions, perhaps multiple sites. Uh, I need to handle that upgrade ideally without downtime in a way that you said service mash in a way that meshes together makes sense. I've got a roll out new certificates I need to address the security, vulnerability, thes air, all the things that Cooper and I used to such a better job at then, what people were doing previously, which was a whole lot of four loops, shell strips and sshh pushing, uh, pushing tar balls around. Maybe Debs or rpm's around. That is what Cooper not he's actually really solves and does an elegant job of solving as just a starting point. And that's just the beginning and, you know, without getting ve injury here, you know, Anthros is the thing that we had at Google have built around Cooper Netease that brings it to enterprise >> here the other day did a tweet. I called Anthem. I just typing too fast. I got a lot of crap on Twitter for that mission. And those multi cloud has been a big part of where Cubans seems to fit. You mentioned some of the licensing changes. Cloud has been a great resource for a lot of the new Web scale applications from all kinds of companies. Now, with several issues seeing a lot more than capabilities, how do you see the next shift with data State coming in? Because God stateless date and you got state full data. Yeah, this has become a conversation point. >> Yeah, I think Kelsey Hightower has said it pretty eloquently, as he usually does around the sort of the serval ist movement and lets lets developers focus on just their code and literally just their code, perhaps even just their function in just their piece of code, without having to be an expert on all of the turtles all the way, all the way down. That's the big difference about service have having written a couple of those functions. I can I can really invest my time on the couple of 100 lines of code that matter and not choosing a destro choosing a cougar Nati is choosing, you know, all the stack underneath. I simply choose the platform where I'm gonna drop that that function, compile it, uploaded and then riff and rub. On that >> fifth anniversary, Cooper Netease were riffing on Cooper Netease. Dustin Circle here inside the Cube Cube Alumni you were recently at the coop con in overseas in Europe, Barcelona, Barcelona, great city. Keeps been there many times. Do was there covering for us. Couldn't make this trip, Unfortunately, had a couple daughter's graduating, so I didn't make the trip. Sorry, guys. Um, what was the summary? What was the takeaway? Was the big walk away from that event? What synthesized? The main stories were the most important stories being >> told. >> Big news, big observations. >> It was a huge event to start with. It was that fear of Barcelona. Um, didn't take over the whole space. But I've been there a number of times from Mobile World Congress. But, you know, this is this is cube con in the same building that hosts all of mobile world Congress. So I think 8,000 attendees was what we saw. It's quite celebratory. You know, I think we were doing some some pre fifth birthday bash celebrations, Key takeaways, hybrid hybrid, Cloud, multi Cloud. I think that's the world that we've evolved into. You know, there was a lot of tension. I think in the early days about must stay on. Prem must go to the cloud. Everything's there's gonna be a winner and a loser and everything's gonna go one direction or another. I think the chips have fallen, and it's pretty obvious now that the world will exist in a very hybrid, multi cloud state. Ultimately, there's gonna be some stuff on Prem that doesn't move. There's going to be some stuff better hosted in one arm or public clouds. That's the multi cloud aspect, Uh, and there will be stubborn stuff at the edge and remote locations and vehicles on oil rigs at restaurants and stores and >> so forth. What's most exciting from a trans statement? What do you what? What's what's getting you excited from what you see on the landscape out there? >> So the tying all of that to Cooper Netease, Cuban aunties, is the thing that basically normalizes all of that. You write your application put it in a container and expect to communities to be there to scale that toe. Operate that top grade that to migrate that over time. From that perspective, Cooper nineties has really ticked, ticked all the boxes, and you've got a lot of choices now about which companies here, you're going to use it and where >> beyond communities, a lot of variety of projects coop flow, you got service messes out there a lot of difference. Project. What's What's a dark horse? What's something that sets out there that people should be paying attention to? That you see emerging? That's notable. That should be paying attention. To >> think is a combination of two things. One is pretty obvious, and that's a ML is coming like a freight train and is sort of the next layer of excitement. I think after Cooper, Netease becomes boring, which hopefully if we've done our jobs well, that communities layer gets settled and we'll evolve. But the sort of the hockey stick hopefully settles down and it becomes something super stable. Uh, the application of machine learning to create artificial intelligence conclusions, trends from things that is sort of the next big trend on then I would say another one If you really want the dark horse. I think it's around communications. And I think it's around the difference in the way that we communicate with one another across all forms of media voice, video chat, writing, how we interact with people, how we interact with our our tools with our software and in fact, how our software in Iraq's with us in our software acts with with other software that communications industry is, it's ripe for some pretty radical disruption. And you know some of the organizations and they're doing that. It's early early days on those >> changes. Final point you mentioned earlier in our conversation here about how Dev Ops is influencing impacting non tech and computer science. Really? What did you mean by that? >> Uh, well, I think you brought up unexpectedly and that that you were looking at the way Uh, some other industries are changing, and I think that cross pollination is actually quite quite powerful when you take and apply a skill and expertise you have outside of your industry. But it adds something new and interesting, too, to your professional environment. That's where you get these provocative operations. He's really creative, innovative things that you know. No one really saw it coming. >> Dave Ops principles apply to other disciplines. Yeah, agility. That's that's pointing down waterfall based processes. That's >> one phenomenal example. Imagine that for governments, right to remove some of the like the pain that you and I know. I've got to go and renew my license. My birthday's coming up. I gotta go to renew my driver's license. You know much. I'm dreading going to the the DMV Root >> Canal driver's license on the same. Exactly >> how waterfall is that experience. And could we could we beam or Mohr Agile More Dev Autopsy and some of our government across >> the U. S. Government's procurement practices airbase upon 1990 standards they still want Request a manual, a physical manual for every product violent? Who does that? >> I know that there are organizations trying to apply some open source principles to government. But I mean, think about, you know, just democracy and how being a little bit more open and transparent in the way that we are in open source code, the ability to accept patches. I have a side project, a passion for brewing beer and I love applying open source practices to the industry of brewing. And that's an example of where use professional work, Tio. Compliment a hobby. >> All right, we got to bring some cubic private label, some Q beer. >> If you like sour beer, I'm in the sour beer. >> That's okay. We like to get the pus for us. Final question for you. Five years from now, Cooper needs to be 10 years old. What's the world gonna look like when we wake up five years from now with two Cuban aunties? >> Yeah, I think, uh, I don't think we're struggling with the Cooper nutties. Uh, the community's layer. At that point, I think that's settled science, inasmuch as Lennox is pretty settled. Science, Yes, there's a release, and it comes out with incremental features and bug fixes. I think Cuban aunties is settled. Science management of of those containers is pretty well settled. Uh, five years from now, I think we end up with software, some software that that's writing software. And I don't quite mean that in the way That sounds scary, uh, and that we're eliminating developers, but I think we're creating Mohr powerful, more robust software that actually creates that that software and that's all built on top of the really strong, robust systems we have underneath >> automation to take the heavy lifting. But the human creation still keeping one of the >> humans Aaron the look it's were We're many decades away from humans being out of the loop on creative processes. >> Dustin Kirkland, he a product manager of Google Uh, Cooper Netease guru also keep alumni here in the studio talking about the coup. Burnett. He's 50 year anniversary. Of course, the kid was president creation during the beginning of the wave of communities. We love the trend we love Cloud would left home a tec. I'm Sean for here in Palo Alto. Thanks for watching.

>> from San Matteo. It's the Cube covering scaler. Innovation Day Brought to You by scaler. >> Welcome to this Special Cube Innovation Day. Here in San Mateo, California Scale is headquarters for a coast of the Cube. We're here with two great guests. Claudia Carpenter co founder Andy McAlister, Who's Dev evangelist? Uh, great to have you guys here a chat before we came on. Thanks for having us >> Great to be >> so scaler. It's all about the logs. The answer is in the logs. That's the title of the segment Them. I'll see the log files with a lot of exhaust in their data value extracting that, but it's got more operational impact. What's what's the Why is the answer in the locks? >> Because that's where the real information is. It's one thing to be able to tell that something is going around when your systems, but what is going wrong as engineers, what we tend to do is the old print. If it's like here's everything I can think of in this moment and leave it as breadcrumbs for myself to find later, then I need to go and look at those bread crumbs >> in a challenge. Of course, with this is that logs themselves are proliferating. There's lots of data. There's lots of services inside this logs, so you've gotta be able to find your answers as fast as possible. You can't afford Teo. Wait for something else. T lead you to them. You need to deep dive >> the way you guys have this saying it's the place to start. What does that mean? Why? Why is that the new approach? >> What We're trying to differentiate because there's this trend right now in the Dev Ops world towards metrics because they're much smaller to store it, pre digesting what's going on in your systems. And then you just play a lot of graphs and things like that. We agree with that. You do need to be able to see what's going on. You need to be able to set alerts. Metrics are good, but they only get you so far. A lot of people will go through. Look at metrics, dig through and then they stop, switch over and go to their logs. We like to start with the logs, build our metrics from them, and then we go direct to >> the source. I think a minute explain what you mean by metrics, because that has multiple meanings. Because the current way around metrics and you kind of talked about a new approach. Could you just take a minute? Explain what you meant by metrics and how logs are setting up the measures. The difference there. >> So to me, metrics is just counting things right? So at log files of these long textual representations of what's going on in my system and it's impossible to visually parce that I mean literally 10,000 lines. So you count. I've got five of this one in six of this one, and it's much smaller to store. I've got five of this one and six of this one, but that's also not very much information, so that's really the difference. >> But, you know, we have customers who use their metrics to help them indicate something might be wrong inside of here. The problem is, is that modern environments where we have instant gratification, needs and people you know, we'd be wait five seconds. Basically, it's a law sale online here. You need to know what's went wrong, not just where we went wrong or that something went wrong. So building for the logs to the metrics allows you to also have a perfect time back to that specific entrance ancient entrance that lets you be you out. What was wrong? >> He mention Claudia Death ops. And this is really kind of think of fun market because Dev Ops is now going mainstream and see the enterprise now started to adopt. It's still Jean Kim from Enterprise. Debs estimates only 3% of enterprise really there yet. So the action's on the cloud Native Public Cloud side where it's, you know, full blown, you know, cloud native more services. They're coming to see Cooper Netease things of that nature out there. And these services are being stood up and torn down while the rhythmically like. So with who the hell stores that data? That's the logs. The nature of log files and data is changing radically with Dev ops. I'm certainly this is going to be more complications but developers and figuring out what's what. How do you see that? What's your reaction to that trend? >> Yeah, so Dev Ops is a very exciting thing. At were Google. It was sort of like the new thing is the developers had to do their own operations, and that's where this comes from. Unfortunately, a lot of enterprise will just rename their ops people devil apps, and that's not the same thing. It's literally developers doing operations, Um, and right now that it's never been so exciting as as it is right now in the text axe, because you could get so much that's open source. Pre built glue this all these things together. But since you haven't written the code yourself, you've no way deal which going on. So it's kind of like Braille. You've got to go back and look and feel your way through it to figure out what's going on. And that's where logs come into play. >> The logs essentially, you know, lift up, get people eyesight into visibility of things that they care about. Absolute. So what's this red thing? Somebody read what is written? Rennes. >> One of the approaches. You'll hear things like golden signals. You'll hear youse, and you'll hear a red Corvette stands for rates, a rose and duration. And ready is a concept that says, How do you actually work with some of these complex technologies working with you're talking about and actually determined where your problems are. So if you think about it, rate is kind of how much traffic's going through a signal for this as a metric, it's accumulative number. So to back to Claudia's point, it's just number here. But if you're trapping goes up, you want to know what's going wrong here is self explanatory. Something broke, fix it, and then duration is how long things took. You talked about communities, Communities works hands in hands with this concept of micro services. Micro services are everywhere, and there were Khun B places that have thousands of little services, all serving the bigger need here. If one of them goes slow, you need to know what went slow as fast as possible. So rate duration and air is actually combined to give you the overall health of your system. While at the same point logs elect, you figure out what was causing >> the problem we'll take. I'm intrigued by what Claudia said. They're on this. You know, Braille concept is essentially a lot of people are flying blind date with what's going on, but you mentioned micro services. That's one area that's coming. Got state full data. Stateless data. They were given a P I economy. Certainly a state becomes important for these applications. You know, the developers don't may or may not know what's happening, so they need to have some intelligence. Also, security we've seen in the cloud. When you have a lot of people standing up instances whether it's on Amazon or other clouds, they don't actually have security on some of their things. So they got it. Figure out the trails of what the data looks like they need the log files to have understanding of. Did something happened? What happened? Why? What is the bottom line here? Claudia? What what people do to kind of get visibility So they're not flying blind as developers and organizations. >> Well, you gotta log everything you can within reason. They always have to take into account privacy and security. But logs much as you can and pull logs from every one of the components in your systems. The micro services that day was just talking about are so cool. And as engineers, we can't resist them way. Love, complexity >> and cool things. >> Things especially cool things and new things. >> New >> green things. Sorry, easily distracted. But there they are, harder to support. They can be a really difficult environment. So again it's back to bread crumbs, leaving that that trail and being able to go back and reconstruct what happened. >> Okay, what's the coolest thing about scaler since we thought about cool and relevant? You guys certainly in the relevant side thing. Check the box there. What's cool? What's cool about scaler telling us? >> That's great. Answer What isn't. But you know, honestly, when I came to work here, I no idea I was familiar with Log Management was really with long search and so forth. And the first time I actually saw the product, my jaw dropped. Okay, I now go to a trade show, for instance, and I'm showing people to use this. And I hit my return button to get my results. And you showed band with can be really bad and it stalls for 1/10 of a second, and I complain about it now. No, there is nothing quite as thrilling as getting your results as fast as you can think about them. Almost your thought processes the slow part of determining what's going on, and that is mind boggling. >> So the speed is the killer. >> The speed is like what killed me. But honestly, something that Chloe's been heavily involved in It takes you two minutes to get started. I mean, there's no long learning curve there. You get the product and you are there. You're ready to go >> close about ease of use and simplicity, because developers are fickle, but they're also loyal. Do you have a good product? They loved to get in that love the freebie. You know, the 30 day trial, They'll they'll kick the tires on anything. But the product isn't working. You hear about it when it does work. This mass traffic to people you know pound at the doorstep of the product. What's the compelling value proposition for the developer out there? Because they >> don't want to >> waste time. That's like the killer death to any product for development. Waste their time. They don't want to deal with it. >> So we live in the TL D our world right now. Frankly, if I have to read something, I usually move on on DH. That's the approach we take with scaler as well. Yes, we have some documentation, but I always feel like I have failed with the user interface design. If I require you to go read the documentation. So I try to take that into account with everything that we that we put out there making it really easy and fast it just jumping in, try stuff. >> How do you get to solve the complex complexity problem through attraction software? What's the secret sauce for the simplicity of this system? >> For me, it's a complete lack of patients. It's just like I wouldn't put up with that. I'm not gonna ask you to. Frankly, I view this sounds a little bit trite, but I've you Software's a relationship, and I view whoever is looking at it as a peer of mine, and I would be embarrassed if they couldn't figure it out if it wasn't obvious. But it is. We do have this sort of slope here of people who really know what's going on and people wanna optimize. This is your 80 20 split on people that don't know what just want to come in. I want both of them to be happy, so we need to blend those >> to talk about the value proposition of what you guys have because we've been covering you know log file mentioned Lock Management's Splunk events. We've gone, too. There's been no solution that I think may be going on 10 years old, that were once cutting edge. But the world changes so fast with Amazon Web services with Google Cloud with azure. Then get the international clouds out there as well. It's it's here. I mean, the scale is there, you got compute. You got the edge of the network right around the corner in the data problem's not going away. Log files going be needed. You have all this data exhausted, these value. >> If anything, there's always going to be more data that's out there. You're going to have more sources of that data coming in here. You're talking a little bit about you have the hybrid cloud. Where's part on prom? Part in the cloud. You could have multi clouds where across his boundaries. You're gonna have the wonderful coyote world where you have no idea when or where you're going to get an upload from too. This too and EJ environment. And you've got to worry about those and at the same time time, the logging, everything, the breadcrumbs. You have ephemeral events. They're not always there, and those are the ones that kill you. So the model is really simple and applaud Claudia for conning concept wise. But you're playing with concept of kiss, right? We'll hear its keep it simple and sophisticated at the same time. So I can teach you to do this demo in two minutes flat, and from there you can teach yourself everything else that this product's capable of doing it. That simple >> talk about who? The person out there that you want to use his product and why should they give scale or look what's in it for them. >> So for me, I think the perfect is to have Dev ops use it. It's developers. We really have designed a product less for ops and more for engineers. So one of the things that is different about scaler is you have somebody come in and set it up, parsed logs that ingestion of logs, which is different than splunk and sumo on DH. Then it's ready to use right out of the box. So for me, I think that our sweet spot, his engineers, because a lot of our formulations of things you do are more technical you're thinking about about you know what air the patterns here. I'm not going to say it's calculus, because then that wouldn't be simple. But it's along. Those >> engineers might be can also cloud Native is a really key party. People who were cloud native. We're actually looking at four in the cloud or cloud migration, >> right way C a lot. For instance, in the Croup. In any space from the Cloud Native Compute Foundation, we're seeing a tremendous instrument interest in Prometheus. We're seeing a lot of interest in usto with service mesh. The nice thing is that they are already all admitting logs themselves. And so, from our viewpoint, we bring them in. We put them together. So now you can look at each piece as it relates to the very other piece >> Claudia share with the folks who, watching this just some anecdotal use cases of what you guys have used internally, whether customers that give him a feel for how awesome scaler is and what's the what could they expect? >> Well, put me on the spot here. Um, >> I'll kick off. So we have a customer in Germany there need commerce shop, They have 1,000 engineers for here. When we started the product we replace because it was on a charge basis that was basically per user. They came back and they said, Oh my God, you don't understand our queries Air taking 15 minutes to get back By the time the quarry comes back, the engineer's forgotten why he asked the question for this. And so they loaded up. They rapidly discovered something unique. It's that they can discover things because anyone can use it. We now have 500 engineers that touch the log files every day, I will attest. Having written code myself, nobody reads log files for fun. But Scaler makes it easy to discover new things and new connections. And they actually look at what house >> discoveries of real value, proper >> discovery is a massive value proposition. Uh, where you figure out things that you don't know about back to that events thing that Claudia started about was, you can only measure the events that you can already considered. You can't measure things that didn't happen >> close. It quickly thought what the culture on David could chime in. What's the culture like here scaler? >> It is a unique culture and I know everyone probably says that about their startup, but we keep work life balance as a very important component. We're such nerds and unabashedly nerds. Wait, what we do. It's a joyful atmosphere to work in. Our founder, Steve Newman, is there in his flat, his flannel shirt, his socks cruising around. Um, and we are very much into our quality barcode. We have a lot of the principles of Google sort of combined into a start up. I mean to say it's a very honest environment, >> Sol. Heart problems make it a good environment. >> Yeah, and I value provide real values, are critical >> for me and have fun at the same point in time. The people here work hard, but they share what they're working on. They share information. They're not afraid to answer the what are you working on? Question. But we always managed to have fun. We are a pretty tight group that way. >> Well, thanks for sharing that insight. We have a lot of fun here in Innovation Day with the Q p. I'm John Furia. Thanks for watching

>> live from Barcelona, Spain. It's the key covering Cook Con Cloud, Native Con Europe twenty nineteen by Red Hat, The Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to the Cubes Live coverage of Cloud Native Con Cube Khan, twenty nineteen I'm student of my co host is Corey Quinn and happy to welcome back to the program. Doug Davis, who's a senior technical staff member and PM of a native and happens to be employed by IBM. Thanks so much for joining. Thanks for inviting me. Alright. So, Corey, I got really excited when he saw this Because server lists, uh, is something that, you know he's been doing for a while. I've been poking in, trying to understand all the pieces have done marvelous conflict couple of times and, you know, I guess, I guess layout for our audience a little bit, you know, Kay native. You know, I look at it kind of a bridging the solution, but, you know, we're talking. It's not the, you know, you know, containers or server. Listen, you know, we understand that world, they're spectrums, and there's overlap. So maybe is that is a set up. You know what is the service. Working groups, you know, Charter, Right. So >> the service Working Group is a Sand CF working group. It was originally started back in mid two thousand seventeen by the technical recite committee in Cincy. They basically wanted know what is service all about his new technology is that some of these get involved with stuff like that. So they started up the service working group and our main mission was just doing some investigation. And so the output of this working group was a white paper. Basically describing serval is how it compares with the other as is out there. What is the good use cases for when to use? It went out through it. Common architectures, basically just explaining what the heck is going on in that space. And then we also produced a landscape document basically laying out what's out there from a proprietors perspective as well is open source perspective. And then the third piece was at the tail end of the white paper set of recommendations for the TOC or seen staff in general. What should they do? Do next and basic came down to three different things. One was education. We want to be educate the community on what services, when it's appropriate >> stuff like that >> to what should wait. I'm sorry I'm getting somebody thinks my head recommendations. What other projects we pull into the CNC f others other service projects, you know, getting encouraged in the joint to grow the community. And, third, >> what should we >> do around improbability? Because obviously, when it comes to open source standards of stuff like that, we want in our ability portability, stuff like that. And one of the low hang your food so they identified was, Well, service seems to be all about events. So there's something inventing space we can do and we recognize well, if we could help the processing of events as it moves from Point A to point B, that might help people in terms of middleware in terms of routing, of events, filtering events, stuff like that. And so that's how these convents project that started. Right? And so that's where most of service working group members are nowadays. Is cloud events working or project, and they're basically divine, Eva said. Specification around cloud events, and you kind of think of it as defining metadata to add to your current events because we're not going to tell you. Oh, here's yet another one size fits all cloud of in format, right? It's Take your current events. Sprinkle a little extra metadata in there just to help routing. And that's really what it's all about. >> One of the first things people say about server list is quoted directly from the cover of Missing the Point magazine Server list Runs on servers. Wonderful. Thank you for your valuable contribution. Go away slightly less naive is, I think, an approach, and I've seen a couple of times so far at this conference. When talking to people that they think of it in terms of functions as a service of being able to take arbitrary code and run it. I have a wristwatch I can run arbitrary code on. That's not really the point. It's, I think you're right. It's talking more about the event model and what that unlocks As your application. Mohr less starts to become more self aware. Are you finding that acceptance of that point is taking time to take root? >> Yeah, I think what's interesting is when we first are looking. A serval is, I think, very a lot of people did think of service equals function of the service, and that's all it was. I think what we're finding now is this this mode or people are more open to the idea of sort of as you. I think you're alluding to merging of these worlds because we look at the functionality of service offers things like event base, which really only means is the messages coming in? It just happens to look like an event. Okay, fine. Mrs comes in you auto scale based upon, you know, loaded stuff like that scale down to zero is a one of the key. Thought it was really like all these other things are all these features. Why should you limit those two service? Why not a past platform? Why not? Container is a service. Why would you want those just for one little as column? And so my goal with things like a native though I'm glad you mentioned it is because I think Canada does try to span those, and I'm hoping it kind of merges them altogether and says, Look, I don't care what you call it. Use this piece of technology because it does what you need to do If you want to think of it as a pass. Go for I don't care. This guy over here he wants think that is a FAZ Great. It's the same piece of technology. Does the feature do what you need? Yes or no? Ignore that, nor the terminology around it more than anything else. >> So I agree. Ueda Good, Great discussion with the user earlier and he said from a developer standpoint, I actually don't want to think too much about which one of these pass I go down. I want to reduce the friction for them and make it easy. So you know, how does K native help us move towards that? You know, ideal >> world, right? And I think so fine. With what I said earlier, One of the things I think a native does, aside from trying to bridge all the various as columns is I also look a K native as a simplification of communities because as much as everybody here loves communities, it is kind of complicated, right? It is not the easiest thing in the world to use, and it kind of forced you to be a nightie expert which almost goes against the direction we were headed. When you think of Cloud Foundry stuff like that where it's like, Hey, you don't worry about this something, we're just give us your code, right? Cos well says, No, you gotta know about networks, Congress on values, that everything else it's like, I'm sorry, isn't this going the wrong way? Well, Kania tries to back up a little, say, give you all the features of Cooper Netease, but in a simplified platform or a P I experience that you can get similar Tokat. Foundry is Simo, doctor and stuff, but gives you all the benefits of communities. But the important thing is if for some reason you need to go around K native because it's a little too simplified or opinionated, you could still go around it to get to the complicated stuff. And it's not like you're leaving that a different world or you're entering a different world because it's the same infrastructure they could. This stuff that you deploy on K native can integrate very nicely with the stuff you deploy through vanilla communities if you have to. So it is really nice emerging these two worlds, and I'm I'm really excited by that. >> One thing that I found always strange about server list is a first. It was defined by what it's not and then quickly came to be defined almost by its constraints. If you take a look at public cloud offerings around this, most notably a ws land other there, many others it comes down well. You can only run it for experience, time or on Lee runs in certain run times, or it's something the cold starts become a problem. I think that taking a viewpoint from that perspective artificially hobbles what this might wind up on locking down the road just because these constraints move. And right now it might be a bit of a toy. I don't think it will be as it because it needs to become more capable. The big value proposition that I keep hearing around server listen I've mostly bought into has been that it's about business logic and solving the things that Air corps to your business and not even having to think about infrastructure. Where do you stand on that >> viewpoint? I completely agree. I think a lot of the limitations you see today are completely artificial I kind of understand why they're there, because the way things have progressed, But again, it's one reason I excited like a native is because a lot of those limitations aren't there. Now. Kay native doesn't have its own set of limitations. And personally, I do want to try to remove those. Like I said, I would love it if K native, aside from the service features it offers up, became these simplified incriminate his experience. So if you think about what you could do with Coronet is right, you can deploy a pod and they can run forever until the system decides to crash. For some reason, right, why not do that with a native and you can't stay with a native? Technically, I have demos that I've been running here where I set the men scale the one it lives forever, and teenager doesn't care right? And so deploying an application through K native communities. I don't care that it's the same thing to me. And so, yes, I do want to merge in those two worlds. I wantto lower those constraints as long as you keep it a simplified model and support the eighty to ninety percent of those use cases that it's actually meant to address. Leave the hard stuff for going around it a little. >> Alright, So, Doug, you know, it's often times, you know, we get caught in this bubble of arguing over, you know? You know what we call it, how the different pieces are. Yesterday you had a practitioner Summit four server list. So what? I want to hear his You know, whats the practitioners of you put What are they excited about? What are they using today and what are the things that they're asking for? Help it become, you know, Maur were usable and useful for them in the future. >> So in full disclosure, we actually kind of a quiet audience, so they weren't very vocal. But what little I did here is they seemed very excited by K native and I think a lot of it was because we were just talking about sort of the merging of the worlds because I do think there is still some confusion around, as you said, when to use one versus the other. And I think a native is helping to bring those together. And I did hear some excitement around that in terms of what people actually expect from us going the future. I don't know the honest They didn't actually say a whole lot there. I had my own personal opinion, and lot of is what already stayed in terms of emerging. Stop having me pick a technology or pick a terminology, right? Let me just pick technology gets my job done and hopefully that one will solve a lot of my needs. But for the most part, I think it was really more about Kenya than anything else yesterday. >> I think like Lennox before it. Any technology? At some point you saw this with virtual ization with cloud, with containers with Cooper Netease. And now we're starting to seriously with server lists where some of its most vocal proponents are also so the most obnoxious in that they're looking at this from a perspective of what's your problem? I'm not even going to listen to the answer. The solution is filling favorite technology here. So to that end today, what workloads air not appropriate for surveillance in your >> mind? Um, so this is hardly the answer because I have the IBM Army running through my head because what's interesting is. I do hear people talk about service is good for this and not this or you can date. It was good for this and not this. And I hear those things, and I'm not sure I actually buy it right. I actually think that the only limitations that I've seen in terms of what you should not run on time like he needed or any of the platform is whatever that platform actually finds you, too. So, for example, on eight of us, they may have time limited in terms of how long you can run. If that's a problem for you, don't use it to me. That's not an artifact of service. That's artifact of that particular choice of how the implement service with K native they don't have that problem. You could let it run forever if you want. So in terms of what workloads or good or bad, I honestly I don't have a good answer for that because I don't necessary by some of the the stories I'm hearing, I personally think, try to run everything you can through something like Cain native, and then when it fails, go someplace else is the same story had when containers first came around, they would say, You know when to use viens roses containers. My go to answer was, always try containers first. Your life would be a whole lot easier when it doesn't work, then look at the other things because I don't want to. I don't want to try to pigeonhole something like surly or K native and say, Oh, don't even think about it for these things because it may actually worked just fine for you, right? I don't want people to believe negative hype in a way that makes sense, >> and that's very fair. I tend to see most of the constraints around. This is being implementation details of specific providers and that that will dictate answers to that question. I don't want to sound like I'm coming after you, and that's very thoughtful of measured >> thank you Usual response back. Teo >> I'LL give you the tough one. The critical guy had in Seattle when I looked at K Native is there's a lot of civilised options out there yet, but when I talked to users, the number one out there is a ws lambda, and number two is probably as your functions and as of Seattle, neither of those was fully integrated since then. I talked a little startup called I Believe his Trigger Mash that that has made some connections between Lambda on K Native. And there was an announcement a couple of weeks ago, Kedia or Keita? That's azure and some kind of future to get Teo K native. So it feels like it's a maturity thing. And, you know, what can you tell us about, you know, the big cloud guys on Felicia? Google's involved IBM Red Hat on and you know Oracle are involved in K Native. So where do those big cloud players? Right? >> So from my perspective, what I think Kenya has going for it over the others is one A lot of other guys do run on Cooper Netease. I feel like they're sort of like communities as well as everything else, like some of them can run. Incriminate is Dr anything else, and so they're not necessary. Tightly integrated and leveraging the carbonates features the way Kay native is doing, and I think that's a little bit unique right there. But the other thing that I think K native has going for it is the community around it. I think people were doing were noticing. Is that what you said? There's a lot of other players out there and his heart feel the choose and what? I think Google did a great job of this sort of bringing the community together and said, Look, can we stop bickering and develop a sort of common infrastructure like communities is that we can all then base our surveillance platforms on, and I think that rallying cry to bring the community together across a common base is something a little bit unique for K native. When you compare it with the others, I think that's a big draw for people. Least from my perspective. I know it from IBM Zzzz Well, because community is a big thing for us, obviously. >> Okay, so will there be a bridge to those other cloud players soon as their road map? For that, >> we think a native itself. Yeah, I am not sure I can answer that one, because I'm not sure I heard a lot of of talk about bridging per se. I know that when you talk about things like getting events from other platforms and stuff, obviously, through the eventing side of a native. We do. But from a serving perspective, I'm not sure I hold her old water. From that perspective, you have to be >> honest. All right, Well, Doug Davis, we're done for This one really appreciate all the updates there. And I definitely look forward, Teo, seeing the progress that the servant working group continues to do, so thank you so much. Thank you for having me. Alright for Corey Quinn. I'm stupid and will be back with more coverage here on the Cube. Thanks for watching.

>> about >> fifteen live from basically about a room that is a common club native con Europe twenty nineteen by Red Hat, The >> Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to the Cubes. Live coverage of Cloud Native Con Cube Khan, twenty nineteen I'm stupid in my co host is Corey Quinn and having a welcome back to the program, Doug Davis, who's a senior technical staff member and PM of a native. And he happens to be employed by IBM. Thanks so much for joining. Thanks for inviting me. Alright, So Corey got really excited when he saw this because server Lis is something that you know he's been doing for a while. I've been poking in, trying to understand all the pieces have done marvelous conflict couple of times and, you know, I guess, I guess layout for our audience a little bit, you know, k native. You know, I look at it kind of a bridging a solution, but, you know, we're talking. It's not the, you know, you know, containers or server lists. And, you know, we understand that world. They're spectrums and there's overlap. So maybe as that is a set up, you know, What is the surveillance working groups? You know, Charter. Right. So >> the service Working Group is a Sand CF working group. It was originally started back in mid two thousand seventeen by the technical recite committee in Cincy. They basically wanted know what is service all about his new technology is that some of these get involved with stuff like that. So they started up the service working group and our main mission was just doing some investigation. And so the output of this working group was a white paper. Basically describing serval is how it compares with the other as is out there. What is the good use cases for when to use that went out through it? Common architectures, basically just explaining what the heck is going on in that space. And then we also produced a landscape document basically laying out what's out there from a proprietors perspective as well is open source perspective. And then the third piece was at the tail end of the white paper set of recommendations for the TOC or seen stuff in general. What do they do next? And basic came down to three different things. One was education. We want to be educate the community on what services when it's appropriate stuff like that. Two. What should wait? I'm sorry I'm getting somebody Thinks my head recommendations. What other projects we pull into the CNC f others other service projects, you know, getting encouraged in the joint to grow the community. And third, what should we do around improbability? Because obviously, when it comes to open source standards of stuff like that, we want in our ability, portability stuff like that and one of the low hang your food should be identified was, well, service seems to be all about events. So there's something inventing space we could do, and we recognize well, if we could help the processing of events as it moves from Point A to point B, that might help people in terms of middleware in terms of routing, of events, filtering events, stuff like that. And so that's how these convents project that started. Right? And so that's where most of service working group members are nowadays. Is cod events working or project, and they're basically divine, Eva said specification around cloud events, and you kind of think of it as defining metadata to add to your current events because we're not going to tell you. Oh, here's yet another one size fits all cloud of in format, right? It's Take your current events. Sprinkle a little extra metadata in there just to help routing. And that's really what it's all about. >> One of the first things people say about server list is quoted directly from the cover of Missing the Point magazine Server list Runs on servers. Wonderful. Thank you for your valuable contribution. Go away slightly less naive is, I think, an approach, and I've seen a couple of times so far at this conference. When talking to people that they think of it in terms of functions as a service of being able to take arbitrary code and running, I have a wristwatch I can run arbitrary code on. That's not really the point. It's, I think you're right. It's talking more about the event model and what that unlocks As your application. Mohr less starts to become more self aware. Are you finding that acceptance of that viewpoint is taking time to take root? >> Yeah, I think what's interesting is when we first are looking. A serval is, I think, very a lot of people did think of service equals function of the service, and that's all it was. I think what we're finding now is this this mode or people are more open to the idea of sort of as you. I think you're alluding to merging of these worlds because we look at the functionality of service offers, things like event based, which really only means is the messages coming in? It just happens to look like an event. Okay, fine. Mrs comes in you auto scale based upon, you know, loaded stuff like that scale down to zero is a the monkey thought it was really like all these other things are all these features. Why should you limit those two service? Why not a past platform? Why not? Container is a service. Why would you want those just for one little as column? And so my goal with things like a native though I'm glad you mentioned it is because I think he does try to span those, and I'm hoping it kind of merges them altogether and says, Look, I don't care what you call it. Use this piece of technology because it does what you need to do. If you want to think of it as a pass, go for I don't care. This guy over here he wants think that is a FAZ Great. It's the same piece of technology. Does the feature do what you need? Yes or no? Ignore that, nor the terminology around it more than anything >> else. So I agree. Ueda Good, Great discussion with the user earlier and he said from a developer standpoint, I actually don't want to think too much about which one of these pass I go down. I want to reduce the friction for them and make it easy. So you know, how does K native help us move towards that? You know, ideal >> world, right? And I think so fine. With what I said earlier, One of the things I think a native does, aside from trying to bridge all the various as columns is I also look a K native as a simplification of communities because as much as everybody here loves communities, it is kind of complicated, right? It is not the easiest thing in the world to use, and it kind of forced you to be a nightie expert which almost goes against the direction we were headed. When you think of Cloud Foundry stuff like that where it's like, Hey, you don't worry about this something, we're just give us your code, right? Cos well says No, you gotta know about Network Sing Gris on values that everything else it's like, I'm sorry, isn't this going the wrong way? Well, Kania tries to back up a little, say, give you all the features of Cooper Netease, but in a simplified platform or a P I experience that you can get similar Tokat. Foundry is Simo, doctor and stuff, but gives you all the benefits of communities. But the important thing is if for some reason you need to go around K native because it's a little too simplified or opinionated, you could still go around it to get to the complicated stuff. And it's not like you're leaving that a different world or you're entering a different world because it's the same infrastructure they could stuff that you deploy on. K Native can integrate very nicely with the stuff you deploy through vanilla communities if you have to. So it is really nice emerging these two worlds, and I'm I'm really excited by that. >> One thing that I found always strange about server list is at first it was defined by what it's not and then quickly came to be defined almost by its constraints. If you take a look at public cloud offerings around this, most notably a ws land other there, many others it comes down well. You can only run it for experience time or it only runs in certain run times. Or it's something the cold starts become a problem. I think that taking a viewpoint from that perspective artificially hobbles what this might wind up on locking down the road just because these constraints move. And right now it might be a bit of a toy. I don't think it will be as it because it needs to become more capable. The big value proposition that I keep hearing around server listen I've mostly bought into has been that it's about business logic and solving the things that Air Corps to your business and not even having to think about infrastructure. Where do you stand on that >> viewpoint? I completely agree. I think a lot of the limitations you see today are completely artificial. I kind of understand why they're there, because the way things have progressed. But again, that's one reason I excited like a native is because a lot of those limitations aren't there. Now, Kay native doesn't have its own set of limitations. And personally, I do want to try to remove those. Like I said, I would love it if K native, aside from the serval ISS features it offers up, became these simplified, incriminate his experience. So if you think about what you could do with Coronet is right, you could deploy a pod and they can run forever until the system decides to crash. For some reason, right, why not do that with a native and you can't stay with a native? Technically, I have demos that I've been running here where I set the men scale the one it lives forever, and teenager doesn't care right? And so deploying an application through K native communities. I don't care that it's the same thing to me. And so, yes, I do want to merge in those two worlds. I wantto lower those constraints as long as you keep it a simplified model and support the eighty to ninety percent of those use cases that it's actually meant to address. Leave the hard stuff for going around it a little. >> Alright, So, Doug, you know, it's often times, you know, we get caught in this bubble of arguing over, you know? You know what we call it, how the different pieces are. Yesterday you had a practitioner Summit four server list. So what? I want to hear his You know, whats the practitioners of you put What are they excited about? What are they using today and what are the things that they're asking for? Help it become, you know, Maur were usable and useful for them in the future. >> So in full disclosure, we actually kind of a quiet audience, so they weren't very vocal. But what little I did here is they seem very excited by K native and I think a lot of it was because we were just talking about that sort of merging of the worlds because I do think there is still some confusion around, as you said when you use one verse of the other and I think a native is helping to bring those together. And I did hear some excitement around that in terms of what people actually expect from us going in the future. I don't know. Be honest. They didn't actually say a whole lot there. I had my own personal opinion, and lot of years would already stayed in terms of emerging. Stop having me pick a technology or pick a terminology, right? Let me just pick the technology. It gets my job done and hopefully that one will solve a lot of my needs. But for the most parts, I think it was really more about Kaneda than anything else. Yesterday, >> I think like Lennox before it. Any technology? At some point you saw this with virtual ization with cloud, with containers with Cooper Netease. And now we're starting to Syria to see with server lists where some of its most vocal proponents are also the most obnoxious in that they're looking at this from a perspective of what's your problem? I'm not even going to listen to the answer. The absolution is filling favorite technology here. So to that end today, what workloads air not appropriate for surveillance in your mind? >> Um, >> so this is hardly an answer because I have the IBM Army running through my head because what's interesting is I do hear people talk about service is good for this and not this or you can date. It is good for this and not this. And I hear those things, and I'm not sure I actually buy it right. I actually think that the only limitations that I've seen in terms of what you should not run on time like he needed or any of the platform is whatever that platform actually finds you, too. So, for example, on eight of us, they may have time limited in terms of how long you can run. If that's a problem for you, don't use it to me. That's not an artifact of service. That's artifact of that particular choice of how the implement service with K native they don't have that problem. You could let it run forever if you want. So in terms of what workloads or good or bad, I honestly I don't have a good answer for that because I don't necessary by some of the the stories I'm hearing, I personally think, try to run everything you can through something like Cain native, and then when it fails, go someplace else is the same story had when containers first came around. They would say, You know when to use BMS vs Containers. My go to answer was, always try containers first. Your life will be a whole lot easier when it doesn't work, then look at the other things because I don't want to. I don't want to try to pigeonhole something like surly or K native and say, Oh, don't even think about it for these things because it may actually worked just fine for you, right? I don't want people to believe negative hype in a way that makes sense, >> and that's very fair. I tend to see most of the constraints around. This is being implementation details of specific providers and that that will dictate answers to that question. I don't want to sound like I'm coming after you, and that's very thoughtful of measured with >> thank you. That's the usual response back. So don't >> go. I'Ll give you the tough one critical guy had in Seattle. Okay, when I looked at K Native is there's a lot of civilised options out there yet, but when I talked to users, the number one out there is a ws Lambda, and number two is probably as your functions. And as of Seattle, neither of those was fully integrated. Since then, I talk to a little startup called Believers Trigger Mash, that that has made some connections between Lambda Ah, and a native. And there was an announcement a couple of weeks ago, Kedia or Keita? That's azure and some kind of future to get Teo K native. So it feels like it's a maturity thing. And, you know, what can you tell us about, you know, the big cloud guys on Felicia? Google's involved IBM Red Hat on and you know Oracle are involved in K Native. So where do those big cloud players? Right? >> So from my perspective, what I think Kenya has going for it over the others is one A lot of other guys do run on Cooper Netease. I feel like they're sort of like communities as well as everything else, like some of them can run. Incriminate is Dr anything else, and so they're not necessary, tightly integrated and leveraging the community's features the way Kay Native is doing. And I think that's a little bit unique right there. But the other thing that I think K native has going for it is the community around it? I think people were doing were noticing. Is that what you said? There's a lot of other players out there, and it's hard for people to choose. And what? I think Google did a great job of this sort of bringing the community together and said, Look, can we stop bickering and develop a sort of common infrastructure? Like Who Burnett is is that we can all then base our surveillance platforms on, and I think that rallying cry to bring the community together across a common base is something a little bit unique for K native. When you compare it with the others, I think that's a big draw for people. Least from my perspective. I know it from IBM Zzzz Well, because community is a big thing for us, >> obviously. Okay, so will there be a bridge to those other cloud players soon as their road map? For that, >> we think a native itself. Yeah, I am not sure I can answer that one, because I'm not sure I heard a lot of talk about bridging per se. I know that when you talk about things like getting events from other platforms and stuff. Obviously, through the eventing side of a native we do went from a serving perspective. I'm not sure I hold her old water. From that perspective, you have >> to be honest. All right, Well, Doug Davis, we're done for This one. Really appreciate all the updates there. And I definitely look forward, Teo, seeing the progress that the servant working group continues to do, so thank you so much. Thank you for having me. Alright for Corey Quinn. I'm stupid and will be back with more coverage here on the Cube. Thanks for watching.

>> live from Barcelona, Spain. It's the key covering KubeCon Cloud, Native Con Europe twenty nineteen by Red Hat, the Cloud, Native Computing Foundation and Ecosystem Partners. >> Welcome back to Barcelona, Spain >> were here of the era, and seventy seven hundred people are here for the KubeCon Cloud NativeCon, twenty, nineteen, Off student. My co host for the two days of coverage is Corey Quinn, and joining Me are the two co chairs of this CNC event. Janet Cooper, who is also thie, suffer engineer with Google and having done the wrap up on stage in the keynote this morning, find Lyle's a senior staff engineer with BM where thank you both for joining us, >> Thank you. >> Thanks for having me. >> So let's start. We're celebrating five years of Kubernetes as damn calm laid out this morning. You know, of course, you know came from Google board in over a decade of experience there. So it just helps out the state for us. >> Um, so I started working on communities since before the 1.4 release and then steal a project Montana today. And I feel so proud to see, uh, the progress off this project and its has grown exponentially. And today we have already thirty one thousand contributors and expect it to grow even more if you can. >> All right. So, Brian, you work with some of the original people that helped create who Burnett ease because you came to be and where, by way of the FTO acquisition, seventy seven hundred people here we said it. So it's, you know, just about the size of us feel that we had in Seattle a few months ago Way Expect that San Diego is going to be massive when we get there in the fall. But you know, talk to us is the co chair, you know, What's it mean to, you know, put something like this together? >> Well, so as ah is a long time open source person and seeing you know, all these companies move around for, you know, decades. Now it's nice to be a part of something that I saw from the sidelines for so, so long. I'm actually... it's kind of surreal because I didn't do anything special to get here. I just did what I was doing. And you know, Jan and I just wound up here together, so it's a great feeling, and it's the best part about it is whenever I get off stage and I walked outside and I walked back. It's like a ten minute walk each way. So many people are like, Yeah, you really made my morning And that's that's super special. >> Yeah. I mean, look, you know, we're we're huge fans of open source in general and, you know, communities, especially here. So look, there was no, you know, you both have full time jobs, and you're giving your time to support this. So thank you for what you did. And, you know, we know it takes an army to put together in a community. Some of these people, we're Brian, you know, you got upstate talk about all the various project. There's so many pieces here. We've only have a few minutes. Any kind of major highlights You wanna pull from the keynote? >> So the biggest. Actually, I I've only highlight won the open census open. Tracing merge is great, because not only because it's going to make a better product, but he had two pretty good pieces of software. One from Google, actually, literally both from Google. Ultimately, But they realize that. Hey, we have the same goals. We have similar interfaces. And instead of going through this arms race, what they did is sable. This is what we'LL do. We'LL create a new project and will merge them. That is, you know, that is one of the best things about open source. You know, you want to see this in a lot of places, but people are mature enough to say, Hey, we're going to actually make something bigger and better for everyone. And that was my favorite update. >> Yeah, well, I tell you, and I'm doing my job well, because literally like during the keynote, I reached out to Ben. And Ben and Morgan are going to come on the program to talk about that merging later today. That was interested. >> I've often been accused of having that first language being snark, and I guess in that light, something that I'm not particularly clear on, and this is not the setup for a joke. But one announcement that was made on stage today was that Tiller is no longer included in the current version of Wasn't Helm. Yes, yes, And everyone clapped and applauded, and my immediate response was first off. Wow, if you were the person that wrote Tiller, that probably didn't feel so good given. Everyone was copping and happy about it. But it seems that that was big and transformative and revelatory for a lot of the audience. What is Tiller and why is it perceived as being less than awesome? >> All right, so I will give you a disclaimer, >> please. >> The disclaimer is I do not work on the helm project... Wonderful >> ...so anything that I say should be fact checked. >> Excellent. >> So Well, so here's the big deal. When Tiller, when Helm was introduced, they had this thing called Tiller. And what tiller did was it ran at a basically a cluster wide level to make sure that it could coordinate software being installed and Kubernetes named Spaces or groups how Kubernetes applications are distributed. So what happens is is that that was the best vector for security problems. Basically, you had this root level piece of software running, and people were figuring out ways to get around it. And it was a big security hole. What >> they've done Just a component. It's an attack platform. It >> was one hundred percent. I mean, I remember bit. Nami actually wrote a block post. You know, disclaimer of'em were just bought that bit na me. >> Yes, I insisted It's called Bitten, am I? But we'LL get to that >> another. This's a disclaimer, You know, There Now you know there now my co workers But they wrote they were with very good article about a year and a half ago about just all the attack vectors, but and then also gave us solution around that. Now you don't need that solution. What you get by default. Now something is much more secure. And that's the most important piece. And I think the community really loves Helm, and now they have helm with better defaults. >> So, Janet, a lot of people at the show you talk about, you know, tens of thousands of contributors to it. But that being said, there's still a lot of the world that is just getting started. Part of the key note. And I knew you wrote something running workloads and cover Netease talk a little bit about how we're helping you know, those that aren't yet, you know, on board with you getting into the community ship. >> So I work on the C gaps. So she grabs one of the sub fracture that own is the work wells AP Eyes. That's why I had that. What post? About running for closing covered alleys. So basically, you you're using coronaries clarity, baby eyes to run a different type of application, and we call it were close. So you have stay full state wears or jobs and demons and you have different guys to run those clothes in the communities. And then for those who are just getting started, maybe start with, uh, stay last were close. That's the easiest one. And then for people who are looking Teo, contribute war I. I encouraged you to start with maybe small fixes, maybe take some documents or do some small P R's and you're reputations from there and star from small contributions and then feel all the way up. >> Yeah, so you know, one of one of the things when I look out there, you know, it's a complex ecosystem now, and, you know, there's a lot of pieces in there, you know, you know, trend we see is a lot of customers looking for manage services. A lot of you know, you know, I need opinions to help get me through all of these various pieces. You know what? What do you say to those people? And they're coming in And there's that, you know, paradox of choice When they, you know, come, come looking. You know, all the options out there. >> So I would say, Start with something simple that works. And then you can always ask others for advice for what works, What doesn't work. And you can hear from their success stories or failure stories. And then I think I recently he saw Block post about Some people in the community is collecting a potential failure stories. There is also a talk about humanity's fellow, the stories. So maybe you can go there and learn from the old those mistakes and then how to build a better system from there. >> I'd love that. We have to celebrate those failures that we hopefully can learn from them. Find anything on that, You know, from your viewpoint. >> Eso Actually, it's something I research is developer experience for you. Bernetti. So my communities is this whole big ping. I look on top of it and I'm looking at the outside in howto developers interact with Burnett, ese. And what we're seeing is that there's lots of room for opportunities and Mohr tools outside of the main community space that will help people actually interact with it because that's not really communities. Developers responsibility, you know, so one anything that I think that we're doing now is we're looking and this is something that we're doing and be aware that I can talk about is that we're looking at a P ice we're looking at. We realize that client go, which is the way that you burnett ese talks with sapi eyes, and a lot of people are using out externally were looking at. But what does it actually mean for human to use this and a lot of my work is just really around. Well, that's cool for computers. Now, what if a human has to use it? So what we're finding is that no. And I'm going to talk about this in my keynote tomorrow. You know, we're on this journey, and Kubernetes is not the destination. Coover Netease is the vehicle that is getting us to the destination that we don't even know what it is. So there's lots of spaces that we can look around to improve Kubernetes without even touching Cooper Netease itself, because actually, it's pretty good and it's fairly stable in a lot of cases. But it's hard, and that's the best part. So that's, you know, lots of work for us, the salt >> from my perspective. One of the turning points in Kou Burnett is a success. Story was when it got beyond just Google. Well, folks working on it. For better or worse, Google has a certain step of coding standards, and then you bring it to the real world, where there are people who are, Let's be honest, like me, where my coding standard is. I should try to right some some days, and not everything winds up having the same constraints. Not everything has the same approach. To some extent, it really feels like a tipping point for all of it was when you wind up getting to a position where people are bringing their real world workload that don't look like anything, anyone would be able to write a googol and keep their job. But still having to work with this, there was a wound up being sort of blossoming effect really accelerating the project. Conversely, other large infrastructure projects we need not mention when they had that tipping point in getting more people involved, they sort of imploded on themselves. I'm curious. Do you have any thoughts as to why you Burnett? He started thriving where other projects and failed trying to do the same things. >> I have something you go first. And >> I think the biggest thing about cybernetics is the really strong community and the ecosystem and also communities has the extensive bility for you to build on top of communities. We've seen people building from works, and then the platform is different platforms. Open source platforms on top of you. Burnett is so other people can use on other layers. Hyah. Layers off stacks on top of fraternities. Just use those open source. So, for example, we have the CRD. It's an A P I that allows you to feel your own customized, overnighted style FBI, so they're using some custom for couple databases. You could just create your own carbonated style FBI and call out your database or other stuffs, and then you can combine them into your own platform. And that's very powerful because everywhere. I can just use the same FBI, the Carbonari style idea to manage almost everything and that enables a Teo be able to, you know, on communities being adopted in different industry, such as I o t. A and Lord. >> So actually, this is perfect because the sleaze and so what I was going to say The secret of community is that we don't talk about actually job, Ada says. It's a lot, but it's a communities is a platform for creating platforms. So Kubernetes really is almost built on itself. You can extend Cooper. Netease like communities extends itself with the same semantics that it lets users extended. So Janet was talking about >> becoming the software that is eating the world. Yeah, it >> literally is. So Janet talked about the CRD sees custom resource definitions. It's the same. It's the same mechanism that Kubernetes uses to add new features. So whenever you're using these mechanisms, you're using Kou Burnett. He's basically the Cooper Nate's infrastructure to create. So really, what it is is that this is the tool kit for creating your solutions. What is why I say that Kubernetes is not an end point its its journey. >> So the cloud native system. >> So you know what? Yeah, and I like I like the limits analogy that people talk about. Like Coburn. Eighties is is like clinics. If you think about how Lennox you know little l. Lennox. Yeah. You know, I'm saying little l olynyk sub Let's put together. Yeah, you Burnett. He's like parts of communities would be system. And it's it's all these components come together the creature operating system, and that's the best part about it. >> Okay, so for me, the people that are not the seventy seven hundred that air here give them a little bit of, you know, walk around the show and some of the nooks and crannies that they might not know, like, you know, for myself having been to a number of these like Boy, there were so many half day and full day workshops yesterday there were, like, at least, like fifteen or seventeen or something like that that I saw, You know, obviously there's some of the big keynote. The Expo Hall is sprawling it, you know, I've been toe, you know, fifteen twenty thousand people show here This sex Bohol feels is bustling ahs that one is and well as tons of breakout session. So, you know, give us some of the things that people would have been missing if they didn't come to the show here. >> So just for the record, if you missed the show, you can still watch all the videos online. And then you can also watch the lifestream for keynotes so on. I personally love the applicant the different ways for a customizing covered at ease. So there's Ah, customizing overnight is track. And also there's the apple that applications track and I personally love that. And also I like the color case studies So you can't go to the case studies track to see on different users and users off Cooper, Natty shared. There were war stories, >> Yes, So I think that she will miss. There's a few things that you'll miss if you if you're not here in Barcelona right now, the first thing is that this convention center is huge. It's a ten minute walk from the door to where we're sitting right now, but more seriously, one. The things you'LL miss is that before the conference starts, there are there are a whole bunch of summits, Red had had a summit and fewer people had some. It's yesterday where they talk about things. There's the training sessions, which a lot of cases aren't recorded. And then another thing is that the special interest groups, the cigs. So Cooper ninety six, they all get together and they have faced the face discussions and then generally one from yesterday We're not. We're not recorded. So what you're missing is the people who actually make this big machine turn. They get together face to face and they first of all, they built from a rotary. But they get to discuss items that have require high bit of bandwith that you really can't do over again of issue or email, or even even a slack call like you can actually get this thing solved. And the best thing is watching these people. And then you watch the great ideas that in, you know, three, six months to a year become like, really big thing. So I bet yesterday, so something was discussed. Actually, I know of some things that we discussed yesterday that might fundamentally change how we deal with communities. So that's that is the value of being here and then the third thing is like when you come to a conference like this, where there's almost a thousand people, there's a lot of conversations that happened between, you know, the Expo Hall and the session rooms. And there's, um there's, you know, people are getting jobs here, People are finding new friends and people are learning. And before thing and I'll end with This is that I walk around looking for people who come in on the on the diversity scholarships, and I would not hear their stories if I did not come. So I met two people. I met a young lady from New Zealand who got the scholarship and flew here, you know, and super smart, but is in New Zealand and university, and I get to hear her insights with life. And then I get to share how you could be better in the same thing. I met a gentleman from Zimbabwe yesterday was going to school and take down, and what I hear is that there's so many smart people without opportunities, so if you're looking for opportunities, it's in these halls. There's a lot of people who have either money for you or they have re sources were really doesn't have a job or just you know what? Maybe there's someone you can call whenever you're stuck. So there is a lot of benefit to come into these. If you can get here, >> talent is evenly distributed. Opportunity is not. So I think the diversity scholarship program is one of the most inspirational things I saw mentioned out of a number of inspirational things that >> I know. It's It's my favorite part of communities. You know, I am super lucky that I haven't employees that our employer that can afford to send me here. Then I'm also super lucky that I probably couldn't afford to send myself here if I wanted to. And I do as much as I can to get people >> here. Well, Brian and Janet thank you so much for all you did to put this and sharing it with our community here. I'Ll repeat something that I said in Seattle. Actually, there was a lot of cloud shows out there. But if you're looking for you know, that independent cloud show that you know, lives in this multi hybrid cloud, whatever you wanna call it world you know this is one of the best out there. And the people? Absolutely. If you don't come with networking opportunities, we had into it on earlier, and they talked about how you know, this is the kind of place you come and you find a few people that you could hire to train the hundreds of people inside on all of the latest cloud native pieces. >> Can I say one thing, please? Brian S O, this is This is significant and it's significant for Janet and I. We are in the United States. We are, you know, Janet is a minority and I am a minority. This is the largest open source conference in the world. Siri's This is the largest open source conference in Europe. When we do, when we do, it ended a year. Whenever we do San Diego, it'Ll be the largest open source conference in the world. And look who's running it. You know, my new co chair is also a minority. This is amazing. And I love that. It shows that people who look like us we can come up here and do these things because like you said, opportunity is is, you know, opportunities the hard thing. Talent is everywhere. It's all over the place. And I'm glad we had a chance to do this. >> All right. Well, Brian, Janet, thank you so much for all of that. And Cory and I will be back with more coverage after this brief break. Thank you for watching the cues.