>>Well, welcome everybody to our last session of the day. I want to introduce you to Sean O'Meara. Orfield Cto. Hey, Sean. >>Hey, Nick. Good afternoon. It's been a crazy day. It has. It's been a busy run up to today in a busy day with a lot of great things going on. You know, we've heard from Adrian on his strategy this morning. The great way the Marantz is moving forward. We announced our new product line. You know, we spoke about the new doctor Enterprise Container Cloud line, New future for Mirant. Us. We had a great lineup of customers share their story. We introduced lanes following on the lanes launch a couple of weeks ago. Andi, we're introducing new great projects like our mosque project. New way to deliver open stack going into the future on then in parallel sel. This We ran a great tutorial tracker teachers you all about how to use these new products, and hopefully you'll go and everyone had opportunity to go and look through guys. Yeah. What's next? What is next? Yeah, lots going on. A lot of new things that we're thinking about for the future. Obviously, a lot of work to do on what we have right now. A lot of great things coming. But, you know, we've had this opportunity to talk about all these cool things that are coming down the road. And everybody these days seems to be talking about topics like edge computing or hybrid cloud. Or, you know, hyper scale data centers, even things like disaster recovery is a service. Andi, you know, we talk a lot about things like hyper converged, but frankly, it's boring. It's one thing a little. Good morning. Uh, you know, you and I have been talking about these topics for a while now, and I think it's about time when we spoke about some of the cool things that we're thinking about for the future, not necessarily looking out for the road map, but ideas for the future. Things that may could have an impact on the way we do business going to. So today we're gonna talk a little bit about things like pervasive computing. A nick, what is pervasive computing. >>Well, basically pervasive computing is when everything that you interact with, for the most part, is computerized. So in some ways, we're already there in that You know your phone is a computer. Your refrigerator may have a computer in it. Um, your smart watch your car has a computer in it. And the the most obvious sign of that is this whole Internet of things where, you know your vacuum is, uh is connected to your phone and all of that. And so pervasive computing is this, uh is this sense of you don't even really think about it. You just kind of assume that everything is computerized. >>So how is that different from ubiquitous computing? >>Oh, God. You hit, You hit my hot button. Okay, so if you look, there are a lot of places that will say that pervasive computing and ubiquitous computing are the same thing, but not the same thing. Don't use them interchangeably. They're not the same thing. You big. What is computing is where you can do your computing virtually anywhere. So, for example, you know, I've got, uh I've got a document. I started it on my laptop. I can then go and finish it sitting on the beach on my phone. Or, you know, I can go and do it in a coffee shop or a library. or wherever. So the idea of ubiquitous computing is similar in that, yes, there's computing everywhere, but it's more about your data being universally accessible. So essentially it is cloud computing. That is what this whole ubiquitous computing thing is about. >>Okay on that then differs from pervasive computing in the fact that pervasive is the devices that we have all around us versus the access to those devices. >>Exactly. It's it's really it's more about the data. So ubiquitous computing is more about My data is stored in some central place, and I could hit it from anywhere. There is a device, whereas pervasive computing is there is a device almost everywhere. Okay, so yeah, >>So why Why do we as Moran takes care about the vice of computing? >>Well, pervasive computing brings up a whole lot of new issues, and it's coming up really fast. I mean, you last night I was watching, you know, commercial where you know, somebody a woman's coming out and starting her car with her phone. Um, which sounds really cool. Um, but you know what they say Anything that you can access, you know, with your computer is hackable. So, you know, there are security issues that need to be considered when it comes to all of this, but that's that's the downside. But there's just this huge upside on pervasive computing that it's so exciting when you think about this. I mean, think about a world where remember I said your refrigerator might be attached to the network. Well, what if you could rent out space on your refrigerator to somebody someplace else in a secure way? Of course. You know what? If you could define your personal network as all of these devices that you own and it doesn't matter where your workloads run or, you know, you could define all of this stuff in such a way that the connectivity between objects is really huge. Um, so you know, I mean, you look at things like, you know, I f t t you know, it's like get a notification when the International space station passes over your house. Okay? I don't know why I would need that. Um, but it's the kind of thing that people >>would have a nine year old. You can run him outside and show Z. Oh, >>there you go. There you go. So I mean, that kind of level of connectivity between objects is really really it gives us this new level off. Uh, this new level of functionality that we would never even considered even 10 years ago. Um, it also extends the life of objects that we already have. So, you know, maybe you've got that, uh, that computerized vacuum cleaner, and you don't like the way that it you don't like the pattern that uses in your house. So you re program it or, uh Or I watched. I watched a guy decide that he didn't want to buy multiple vacuums for his house. So he programmed his programa will act Hume to fly between floors. It was actually pretty funny. Um, I it's some people just have too much time. >>It's driving the whole world of programmable at all levels. Really? Like the projects coming out of the car industry of creating a programmable car would fit into that category. Then, I >>suppose absolutely, absolutely needs developer tool kits. Um, that make it possible for anybody to re program these devices that you never would have thought of reprogramming before. So it's important. So do >>we want to talk about the questions. We would love people to give us some feedback on at this stage. >>I would love to talk about these questions. So what we did is we put together, uh, we put together a place for you to answer questions. If you're not watching this live. If you're watching this live, please go ahead. Drop your ideas in the chat. We would love to discuss them, you know. Do you want to see more of this? Or does it? Conversely, Does it scare you, Sean? You What? >>What do you >>think about these questions? >>Well, I mean, for me, the idea of the connected world at one level, the engineering me loves the idea. Another level. It comes to these questions of privacy. Vegas questions off. How do I control this going into the future? What prevents somebody from taking over my flying vacuum cleaner? I'm using it, you know? So it's an interesting question. I think there's a lot of cool, cool ideas. Yeah, and a lot of work to be done. I really want to hear other people's ideas as well and see how we can take this into the future. >>Definitely, definitely. I mean, look I mean, we're joking about it, but, you know, when somebody hacks into your grandmother's insulin pump, maybe not so funny. >>Yeah, a very real risk. >>A very real risk. A very real risk. But yeah, I mean, we'd love Thio. We'd love to hear how you'd like to see this used. So that's that's my That's kind of what I've been thinking about thes days. Um, but, you know, Sean, uh, now, you I know you are really concerned about this whole issue of developers and how they feel about infrastructure. So I would love to hear what you've got to say on that. >>Yeah, I'd like to sex, but a bit about that. You know, we we've done a lot of work over the last few years looking at how developing our history has been very focused on operations, but without big drive towards supporting developers providing better infrastructure for developers. One of the interesting things that keeps coming up to the four on Do you know, the way the world is changing is that big question is, do developers actually give a damn about infrastructure in any way, shape or form? Um, you know, ultimately more and more development languages and tools abstract that underlying infrastructure. What communities does is basically abstract. The infrastructure away, Um, mawr and more options. They're coming to market, which you can quite literally creating application without out of a writing a line of code. Um, so this morning, way Dio, we're doing it all the time, sometimes without even realizing it on. I think the definition of what a developer is is also changing to a certain extent. So you know the big question, which I have on which I'd like to understand Maureen, from talking to low developers is due. Developers care about infra What is it that you expect from infrastructure? What do they want going into the future? How are they going to interact with that infrastructure? I My personal opinion is that they don't really care about infrastructure, that they're going to find more ways to completely abstract away from that. And they just want to focus on delivering applications faster and getting value to market. But I might be wrong, and I'd really like to hear people's impact ideas and thoughts on that >>on. And that's exactly and that's why we're asking this question. Developers out there. Do you care? Or do you just want the whole thing completely abstracted away from you >>on? If you do care why, If you don't, what would you like to see? Another. It's a couple of questions to ask, but really like to hear those opinions on bond. You know, Do you just want the operations guys to live with it? You never want to hear about it again, just fine. It's actually good to say that we'll work it out. >>Yes, and that there's nothing. There's nothing wrong with pushing that up stack >>pretty much what we're trying to do here. >>Well, it is what we're trying to do. But at the same time, we want to do what's good for developers. And if you developers or like No, don't don't do that. Well, we want to know because, you know, we don't wanna work away here and some ivory tower and wind up with something that's not good for >>you after school. So cool. So, yeah, there are some other interesting things we're talking about. >>I know, I know. This is This is one of my favorites. This is one of my favorites. >>Zoo this? Yes. While >>we're on the subject of not getting involved with the infrastructure. Go ahead, Sean. Tell us about it. >>Thing is a pet topic of mine and something that that we've spoken about a lot. And thanks something that we we have spent many nights talking about. The idea is AI ops using artificial intelligence to drive operations within our infrastructure. And so a lot of people ask me, You know why? Um, essentially, What the hell is a I out on? I have answered this question many times, and it does often seem that we all take this AI ops thing for granted or look at it in a different way. To me, it is essentially, it's it's automation on steroids. That's what it boils down Thio. It's using intelligence systems that to replace the human cerebellum. I mean, let's just be blunt about this. We're trying to replace humans. Onda reason for that is we humans less meat sacks are airplane. We make mistakes all the time and compared to computers were incredibly slow. Um, you know, that's really the simplest point with the scale of modern infrastructure that we're dealing with the sheer volume. I mean, we've gone from, you know, thousands to tens of thousands of the EMS to now hundreds and thousands of containers spread across multiple time zones. Multiple places. We need to come up with better ways of managing this on the old fashioned stick through mechanism of automation. It's just too limited for that. Right >>when we say we want to replace meat sacks, we mean in a good way. >>We mean in a good way. I know it's a bit of a harsh way of putting it. Um, ultimately, humans have ability for creativity that machines just don't have. But machines can do other things, and they could do analysis of data a lot faster than we can. Quite often, we have to present that data to humans to have invalidate that information. But, you know, one of the options for us is to use artificial intelligence, quantified data, um, correlated, you know, look for root cause and then provide that information to us in such a way that we can make valid decisions based on that information a lot faster than we could otherwise, >>right? So what are the what are the implications? What are the practical implications of doing this so >>practically we can analyze massive amounts of data a lot faster than a single human. Could we even just a normal type system that's searching? We We have the tools to learn by looking at data and have machines do it a lot faster than we can. We can take action faster based on that data, because we get the data foster. We can take action and much more complex action that involves maybe many different layers of tasking much, much faster. Um, on we could start to do maintenance operations and maintenance tasks without having to wait for human beings to wake up or get to an office. But more importantly, we could start making tasks happen very complex tasks in a very specific orders, with much less potential for error. And those are the kinds of areas we're looking at. >>That's that's true. So how do you kind of see this moving forward? I mean, obviously, we're not gonna go from nothing to Skynet, and hopefully we never get to Skynet. Well, >>depends if you are in control of Skynet or not. Ultimately, Dionysus little computer. Um, practically speaking, we have a few things Thio hoops to jump through our suppose before we can look at where else is going to be really effective on the first one is a trust issue. We have to learn to trust it. And to do that, we have to put in a position where it can learn and start providing us that data analysis on that inference and then having humans validated. That's practically the very first step. No, it's a trust issue. You know, we've seen been watching sci fi for the last 30 years. Class on. Do you know the computers take over? Well, ultimately, is that real or not? Um, if we look at how we gonna get there? Probably midterm. Adaptive maintenance, maybe infrastructure orchestration. Smart allocation of resource is across cloud services. Well, >>we can talk for a minute About what that would would actually look like. So, I mean, we could talk about, you know, abs, midterms. I mean, in a practical sense, how would that actually work? >>Yeah, Okay. It's a great question. So, practically speaking, the first thing we're gonna do is we're going to start to collect all this data. We're gonna find all this data. I mean, the modern computer systems that we have infrastructure systems. We are producing many hundreds of gigabytes, sometimes terabytes of logging data every day. The majority of it gives far 13. I mean, we throw the majority of their logging information away or if it's not thrown away, it's stored some way for security purposes and never analyzed. So let's start by taking their data and actually analyzing it. To do that, we have laid and correlated, >>so we >>gotta put it all together. We've got a match it and we've got to start building patents. We're going to start looking for the patterns. This is where I is particularly good at starting to help us. Bold patterns start to look for those patterns. Initially, humans will have to do some training. Um, once we have that patent, once we've got that working, we can now start having the AI systems start to do some affairs. E, here's the recalls. So we the system can tell us based on the data based on the patterns we've been learning. We know from the past debt. If those three network links get full bad example, we're gonna have a failure in Region X, right. So start telling us while those network links of filling up tell us before they fall rather than after their full always they're falling up as we see trending information now seems like a simple I could do trending information with just normal monitoring systems. But if I can start to correlate that with greater users in, you know, Beijing Office versus Users in California office filling up those links and different times of the day, I can now start to make much more clever decisions, which is a human on its own, to try and correlate that information, which is be insane once you've done that way to go to the next stage, which is not to have the system act do actions for us. Based on that information right now, we're starting to get close to the scan it. Speaking of this doesn't have to be a big, complex pile of change. Smart ai solution. I have data on that AI solution is talking to my existing automation solutions to action. That change. That's how I see this moving forward, >>right? So essentially you, instead of saying, you know, deploy this too. Uh, this workload to AWS, you would say deploy this. Yeah, And then the system would look and go. Okay, It's this kind of workload. At this time of day at this size, it's gonna interact with this and this and this. And so it's gonna be best off in this region of this cloud provider on then. Uh, you know, two days from now, when the prices drop, we're gonna put it over there, >>even taking a different different. Spoken exactly that it could be. The Beijing office is coming online. Let's move the majority of the workload to a cloud that's closer to them. Reducing the network bandwidth. Yeah, and inference. Andi Also reducing the impact on international lines as Beijing winds down for the day, I can just move the majority of the workload into California on board Europe. In between, it's very simple examples, but have humans do that would be very complex and very time consuming >>exactly. And end. Just having humans notice those patterns would be difficult. But once you have the system noticing those patterns, then the humans could start to think, How can I take advantage of this, you know, So as you are talking about much longer term in the actual applicant patients themselves. So you know, everything can be optimized that way so >>everybody may optimized way can optimize down to the way we even potentially write applications in the future. Humans were still deciding the base logic. Humans were still deciding the creative components of that. Right as we as we build things, we can start to optimize them, breaking down into smaller and smaller units that are much more specific. But the complexity goes up. When we do that right. I want to use AI and AI solutions to start to manage that complexity across multiple spaces. Multiple time zones, etcetera. >>Exactly. Exactly. So. So that's the question, you know. What do you guys think? You know, we really want to know >>on Dhere again. You know, we mentioned this around the beginning, but do you think you could trust in a iob sedition? What would it take for you to trust in our absolution? And where do you practically see it being used in the short term? >>Yeah, that's that's the big question is where do you see it being used? Where would you like it to be used, you know? Is there something that you don't think would be possible, but you would like to see it, you know. But the main thing is, on a practical matter, what would you like to see? >>Let me ask. The question is like a different way. Do you have a problem that we could solve within a isolation today? E, They're really well >>right. A re a world problem. And And assuming that, you know, we are not gonna, you know, take over the world. >>Yeah. Important. My evil plan is to take over the world with >>man. I'm so sorry. First >>had to let that draw. >>I did. I did. I'm so sorry. Okay, Alright. So that's so That's a I ops. And we like I said, if you're watching this live, throw in the chat. We want to hear your ideas. If your, um if you're doing this, if you're watching this on the replay, go to the survey because we way, we really want to hear your ideas and your opinions. All right, So moving right along. All right. What the heck are you know, kernels? >>Uh, lovely questions. So, you know, the whole world is talking about containers today way we're talking about containers today. But containers like VMS or just one way to handle compute Andi. They're more and more ideas that are out there today, and people have been trying different ways off, shrinking the size of the compute environment. COMPUTER Paxil Another cool way of looking at this and saying That's been around for a little while. But it's getting your attraction to learn to sing called unique kernels, and what they are is they're basically highly optimized. Execute a bles that include the operating system, Um, there on OS settle libraries, um, and some very simplified application code all mixed into a very, very tiny package. Easiest way to describe them. They're super simplified. And I were talking about in the eye ops discussion this idea off taking everything into smaller and smaller individual functions but creating a certain level of complexity. Well, if we look at uni kernels, those are those smaller and smaller bundles and functions. They interact directly with the hardware or through a hyper visor. Um, so actually, no overhead. I mean the overhead If you just look at what a modern you clinics operating system is made up of these days, there are so many different parts and components. Even just the colonel has got anything from, you know, 5 to 7 different parts to it. Plus, of course, drivers and a boot loader. Then we look at the system libraries that set on top of that, you know? And then they're demons and utilities and shells and scream components and, you know, additional colonel stacks that go on top of that for hyper visors. What we're trying to say is, what, This text of space, I'm >>getting tired. Just listening, >>Thio. I'm tired talking about it. You know that the unique colonel, really, it just takes over their complexity. It puts the application the OS on the basic libraries necessary. That application in tow, one really tiny package. Um, yeah. Give you an idea what we're talking about here. We're talking about memory footprints or time package footprints in the kilobytes. You know, a small container is considered 100 make plus, we're talking kilobytes. We're talking memory utilization in the kilobyte two megabytes space because there's no no fact, no fluff, no unnecessary components. And then only the CPU that it needs. >>So Bill Gates was right 6. 40 k is all anybody will ever need >>Potentially. Yeah, right. E, there was there was an IBM CEO who said even less at some point. So we'll see >>how that go. What goes around comes around. >>But one of the really interesting things about this small size, which is really critical, is how fast they can boot. Yeah, we're talking boot times measured in 30 seconds. Wow, We're talking the ability to spin up specific functions only when you need them. Now, if we look at the knock on effect of that, we're looking at power saving. Who knew? Run the app when I need it because there's no Leighton. See to start it up. The app is tiny so I can pack a lot mawr into a lot less space game power seconds. But when I start looking at where you were talking about earlier, which the basic compute idea in the world all of a sudden that tiny little arm chips it in my raspberry pi that's running my fridge, My raspberry pi equivalent that's running my fridge no longer has a fact operating system around it. I can run tens thousands, potentially off these very tiny specific devices when I need them. Wow, I'm kind of excited about it. I'm excited by the idea. You >>can hear that >>I'm a hardware geek from from many, many moons ago on DSO. I kind of like the idea of being able to better utilize along this very low powered hardware that we have lying around and really take it into the future. Well, that's good. Yeah. So I'm not going to kill, not going to kill containers. But it is a parallel technology that I'm very interested in >>that that is true. Now what does it I mean in terms of, like, attack surface. That means it's got a much smaller attack surface, though, right? >>Yeah. Great. Great point. I mean, there's no there's no fluff. There's no extra components in the system. Therefore, the attack surface is very, very small. Um, you know, and because they're so small and can be distributed much, much faster and much more easily updating and upgrading them as much easier way can we can upgrade a 60 k b file across a GPRS connection on which I certainly can't do with 600 make, uh, four gig VM 600 made container. You know, just unrealistic. Um, e >>I was just going to say so. So now these. You know, kernels, they're they're so small. And they have on Lee what they absolutely need. Now, how do you access the hardware? >>So the hardware is accessed via hyper visor. So you have to have some kind of hyper visor running on top of the hard way. But because Because we need very little from their type adviser, we don't actually need to interact with that very much. It could be a very cut down operating system. Very, very simplified operating system. We're also not trying to run another layer on top of that. We're not We're not ending up with multiple potential VMS or something underneath it were completely removed. That layer, um, the the drivers, the necessary drivers are built into that particular colonel device. >>Oh, okay. That makes sense. >>Tiny footprint easily distributed, um, and once again, very specialized, >>right? Right. Well, that makes sense. Okay. So, yeah, I mean, I guess so. These these individual stacks, you know, comparing virtual machines to containers to unit colonels, there just a completely different architecture. But I can see how that would How That would work where you have the hi perverse. A little hyper buys are on top of rented teeth. OK, so moving right along certain. Where do we see these being used? >>Um, it's early days, although there are some very good practical applications out there. There's a big, big ecosystem of people trying different ways for this I o ts off the obvious immediate place. I i o t s a quick, easy place for something very specialized. Um, what's interesting to me? And you mentioned this earlier. You know, we're talking about medical devices. We're talking about potentially disposable medical devices. Now, if I can keep those devices to run on really low power very, very cheap, um, CPUs and all of a sudden I've got a device that is available to a lot more people. I don't need a massive, powerful CPU. I just need saying that runs a very specific function really fast, A very small scale. I could do well disposable devices. I can build medical devices that are so small we can potentially swallow them and other areas which are really interesting. And I spoke a little bit about it, but it's energy efficiency. Where We need to be very, very energy efficient. No. And that can also impact on massively scalable systems where I want to deal with tens of thousands of potential transactions from users going into a system. I can spin them up only when I need them. I don't need to keep them running all the time again. It comes back to that low latency on then. Anyway, that an incredibly fast food time is valuable. Um, a car, you know, Think about it. If if my if my electric car is constantly draining that battery when it's parked in the garage and I'm traveling or if it takes 20 minutes from my car to boot up its clinics. Colonel, when I wanted, I'm going to get very irritated. Well, >>that and if you have a specific function, you know, like, identify that thing, Yeah, it would be good if you haven't smashed into it before. Identified it as a baby carriage e dark today. Yes. >>So, Nick, you know, these is all really interesting topics. Um, yeah. We spoke about air ops. We spoke about the impact is gonna have on humans. Um, all of these changes to the world that we're living in from computer systems, the impact it's having on our lives biggest. An interesting question about the ethics of all of this >>ethics of all of this. Yes, because let's be let's be realistic. There are actual riel concerns when it comes to privacy, when it comes to how corporations operate, when it comes to how governments operate. Um, there are areas of the world's where, how all of this has has moved, it's absolutely I'll be honest, absolutely terrifying the economic disparity. Um, but when you really come right down to it, um, it's all about the human control over the technology because all of these ethical issues are are in our hands. Okay, we could joke about Sky Net. We can joke about things like that, but this is one place that technology can't help us. We have to do this. We have to be aware of what's going on. We have to be aware. Are they using facial recognition? Uh, you know, when you go to X y Z, are they using recidivism algorithms in sentencing? And how is that? How is that going? Is it? Are those algorithms fair? Certain groups get longer sentences because historical data, uh, is skewed. Be educated. Know how this works? Don't be afraid of any of this. None of this is, uh, none of this is rocket science. Really? Come right down to it. I mean, it's it's not simple, but you can learn this. You can do it. >>Ask good questions. Be interested to be part of the part of the discussion. Not just a passive bystander. >>Exactly. Don't just complain about what you think is going on. Learn about what is actually going on and be active, where you see something that needs to be fixed. So that's what that's what we can do about it. We need to be aware that there's an issue or potential issues, and we need to step in and fix it. So that z myself box, I'll step down zone >>important topic. And it's one that we all can have influence on on bits one. Those who are us who are actually involved in building these systems for the future. We can help make sure that the rules are there. That's right. Systems are built correctly on that. We have open dialogues and discussions around these points and topics and on going away, was she? I think we're coming to the end of the time on hopefully we've kept everybody interested in some of the things that we think are cool for the future. And we're putting our efforts into E O. But I think we need to wrap this up now. So, Nick, great chatting to you is always >>always, always a pleasure, Sean. >>It's been an amazing week. Um, been amazing. Couple of weeks, everybody leading up to this event on bond. No, thank you, everybody for listening to us. Please go and download and try. Dr. Enterprise, Uh, the container card is available. Will post the links here to better understand what we've been doing. Go and have a look through the tutorial track. You'll hear my voice. I'm sure you'll hear next voice and make other people's voices through those tutorials. Hopefully, we keep you all interested and then going download and try lens, Please. Finally, we want your feedback. We're interested to hear what you think would be the great ideas. Good, Bad. Otherwise let us know what you think about products. We are striving to make them better all the time. >>Absolutely. And we want your involvement. Was it all right? Thank you all. Bye bye. Yeah,