Podcasts about open compute

Take a Network Break! In this week’s Red Alert we suggest an audit of your Azure environment after Microsoft says it patched four critical vulnerabilities. On the news front, Nvidia has brought the Multipath Reliable Connection (MCR) protocol to the Open Compute Project, AT&T rolls out quantum-resistant SD-WAN services, and HPE introduces new Wi-Fi automation... Read more »

Take a Network Break! In this week’s Red Alert we suggest an audit of your Azure environment after Microsoft says it patched four critical vulnerabilities. On the news front, Nvidia has brought the Multipath Reliable Connection (MCR) protocol to the Open Compute Project, AT&T rolls out quantum-resistant SD-WAN services, and HPE introduces new Wi-Fi automation... Read more »

Take a Network Break! In this week’s Red Alert we suggest an audit of your Azure environment after Microsoft says it patched four critical vulnerabilities. On the news front, Nvidia has brought the Multipath Reliable Connection (MCR) protocol to the Open Compute Project, AT&T rolls out quantum-resistant SD-WAN services, and HPE introduces new Wi-Fi automation... Read more »

When we say 'the cloud' what we mean is 'the data centre'. Globally, data centres are projected to consume over 1000 terawatt hours in 2026. What does that mean for energy production, distribution, and consumption? Guest Phil Harris, Cerio President and CEO, joins thinkenergy to shed light on something we all rely on but may not fully understand. From efficiency to sustainability, environmental concerns to Cerio's role improving how data centres manage energy. Listen in for the future of cloud computing.  - Related links  ●       Cerio: https://www.cerio.ai/ ●       Phil Harris on LinkedIn: https://www.linkedin.com/in/paharris/  ●       Trevor Freeman on LinkedIn: https://www.linkedin.com/in/trevor-freeman-p-eng-8b612114  ●       Hydro Ottawa: https://hydroottawa.com/en     To subscribe using Apple Podcasts: https://podcasts.apple.com/us/podcast/thinkenergy/id1465129405 To subscribe using Spotify: https://open.spotify.com/show/7wFz7rdR8Gq3f2WOafjxpl To subscribe on Libsyn: http://thinkenergy.libsyn.com/ --- Subscribe so you don't miss a video: https://www.youtube.com/user/hydroottawalimited Follow along on Instagram: https://www.instagram.com/hydroottawa Stay in the know on Facebook: https://www.facebook.com/HydroOttawa Keep up with the posts on X: https://twitter.com/thinkenergypod --- Transcript: Trevor Freeman  00:07 Welcome to think energy, a podcast that dives into the fast, changing world of energy through conversations with industry leaders, innovators and people on the front lines of the energy transition. Join me, Trevor Freeman, as I explore the traditional, unconventional and up and coming facets of the energy industry. If you have any thoughts, feedback or ideas for topics we should cover, please reach out to us at thinkenergy@hydroottawa.com. Hi everyone, and welcome back. Data centres have come up a number of times on this show, and for very good reason, they have become a key underpinning technology for so much of our lives, every time we pull out that phone from our pockets to pull up directions or buy something online or doom, scroll on your social media or new site of choice, every time you use your phone stream a movie, leverage an AI model, whatever you end up using it for, it's funny as I read this list, I'm sure there's like some university student out there who's thinking, man, what is this old man talking about? We don't use our phones for that, whatever the kids are doing these days, whatever we're doing these days with our phones, with our computers, our tablets, et cetera. All of that leverages infrastructure that most of us have never seen and, quite frankly, probably don't really understand we talk about the cloud like it's this amorphous, nebulous thing, but in reality, we're talking about real hardware in a real building that uses real energy, mainly electricity, a lot of water. And this isn't really new, like we've been leveraging centralized data centres for many years now, but what is changing is the scale of the data centres that we're seeing now, and the pace of growth in computing power that we need to do, the things that we want to do, and that our data centres are able to deliver. So just to throw a few numbers at it, the traditional data centre servers that maybe power the early days of on demand online streaming services, for example, they used anywhere from five to 15 kilowatts per rack. But modern server racks that are used to power AI searches, for example, can hit anywhere from 60 to 100 kilowatts per rack. This is great from a power output per rack perspective, but it means massive energy needs, and that is showing up in the size of load requests that we're seeing from new data centres. New data centres today are asking for service connections that are orders of magnitude higher than those built even just five years ago, globally, data centres are projected to consume over 1000 terawatts in 2026 or terawatt hours, sorry, in 2026 and just a quick kind of refresher from high school or wherever you would have learned this, a terawatt is 1000 gigawatts, which is 1000 megawatts. So 1000 terawatt hours, which is roughly equivalent to the annual electricity demand from the country of Japan, an entire country. So given all of this, there are a lot of incentives to find ways to maximize efficiency and reduce some of that energy demand, and that's where my next guest, Phil Harris and his company Cerio come into play. I'll let Phil get into the details of exactly what Cerio does, but essentially, their goal is to reimagine the data centre to maximize sustainability and reduce energy needs. Phil is Cerio's President and CEO, and has been in the networking and data centre industry for over 35 years, including at well known companies like Intel and Cisco. And I'm really excited about this conversation. One to understand, how do we make data centres a little bit more efficient, or maybe a lot more efficient, but also just to really understand, like, what are we talking about when we talk about a data centre? What is actually happening, what is physically inside these buildings, and we'll get into a little bit of that in our conversation. So Phil, welcome to the show.   Phil Harris  04:13 Well, thanks, Trevor. I appreciate it.   Trevor Freeman  04:13 So Phil, obviously we're here today to talk about your work building sustainable data centres, or trying to make data centres a little bit more sustainable. But before we get into that. You know, you've spent your career, you know, decades of your career at different tech giants. Let's call them in telecisco to to mention, you've seen quite a bit of change. No doubt, over your time, has that changed, like, does this industry change linearly? Does it grow fairly steady, or is it kind of big jumps? And are we on the cusp of any major shifts? What can you kind of tell us about the future of this, this sector, data, tech, etc?   Phil Harris  04:48 It's interesting, I think, as companies start, and I was at companies like Cisco, for example, when it was a very small company to when it was very large company. And this should be no surprise for anybody, the bigger the company gets, the harder. It is to change, and they really find that the only way they change is when they absolutely have to, not because they want to, and that's a combination of just inertia and shareholders expectations and a whole bunch of things. So I would say that the bigger the company is, the harder is them, for them to react. And so I think small, nimble companies tend to do much better when there's a lot of transformational technology and development and changes in the overall ecosystem we live in. I think just the second part of your question, you know, I look at the current situation as a point in time where a lot of companies will have to make some significant changes, simply because we're hitting too many walls, technological walls, commercial walls, geopolitical walls, that are really sort of confining what people can do. So I think what's going to about to happen is we're about to see a significant change, and this is not atypical in the industry. If we think about back into the into the start of what we would think of today as computer science around mainframes that were happening in the 60s. You know, for about a decade and a half, two decades, there was a lot of dominance around a particular way of doing things. And then some new innovational technology came along that rapidly changed, that scaled out, and it went from a very dominant set of players to a much larger number of smaller players who could then provide more innovation and more scale and more choice. And I think we're about to see that transition occurring as well.   Trevor Freeman  06:25 So is this, is there sort of like an analogous time, 10 years ago, 20 years ago? Are we on the cusp of, like, the big, the big change that we've seen before? Like, what would you compare this to? You know, in the last 2030, years?   Phil Harris  06:40 Yeah. I mean, I think there's been eras of compute. And if we say, I mean, we can find analogies outside of the compute world, but let's just stay in the compute, computing science world. I gave the mainframe example as one, and then we went to what we call client server, which scaled out rapidly. Telephony. We went from large, big telephone exchanges that started in in the government space, went to very large organizations. Now, basically we've completely scaled out how we make phone calls to use that now 20th century as a terminology. Nobody really makes telephone calls anymore. And we went through this with cloud computing and the Internet, where there was a change in the approach to the way we did things that suddenly gave us a scale out mentality, rather than a scale up mentality. And I think that's what we have to key in on here. Is it that we can take some of you? I was on a panel yesterday where we were talking about scale, and I say, well, to scale or not to scale? That is not the question. It's how do we scale? Do we continue to scale up, which is the current model, or do we start to think about scaling out, which is a more distributed model? So we go from a small number of big things to a large number of smaller things. And typically in computer science, whatever you want to start, storage, compute, memory, telephony, everything we've ever done goes through this arc.   Trevor Freeman  07:59 Yeah, it's it's interesting, and it's, there's obviously my brain's gonna immediately try and find those, those similarities between my world that I live in on the energy side of things. And it's the same question, like, there, there's, there is no path where we're not expanding the amount of energy we need. We're not going to be using more energy. But there are different ways to do that, and there are different paths we can take the business as usual that just grow, grow, grow, decentralized energy production and large scale transmission. Or there's a combination of like, grow those things, but also find alternative methods. More ders more sort of like close to consumer energy sources and storage, et cetera, et cetera. And people that listen to this podcast know I kind of go on ad nauseam about this. So lots of similarities. There another kind of framing or foundational thing that I want to talk through before we really get into the meat of our conversation is helping ground both myself and our listeners, and what exactly we're talking about here. So we, we all use, whether we know it or not, we use, you know, like cloud computing constantly, whether it's in our calls, how we're using the internet, using AI, more, more frequently. Now, what is the physical reality behind that? What's actually happening? What is the term data centre? What is a data centre for our listeners here? What does that look like?   Phil Harris  09:26 Yeah, let's start there. That's a great question. We started recognizing that the amount of power and space required for computers in companies and government in all sorts of different applications was getting larger than we could put in a room, in a closet near maybe where people were using it. We had to sort of create dedicated space, because the power requirements, the cooling requirements, just the noise. You can't hear this, but just in my basement, I have a few different compute systems that my wife continues to tell me is keeping my neighborhood awake. The reality is the environmentals of these things became very difficult. So we created these purpose built locations that had then different requirements in terms of access and facilities and power and cooling and staffing. And so they became a new way of thinking about building compute infrastructure at a building level, not just at the individual computers themselves. So a data is usually a very large room or building, I should say that houses large amounts of compute and storage and other networking equipment. There's a whole range of different technologies that go into a data centre that allows us to process information. That's what a data centre is. To give you some analogies in the US, there's about nearly 6000 data centres, depending on how you measure a data centre. In Canada, we have about 400 in Europe, there's about 750 that we can identify as standalone data centres. You can probably find more places where computers are outside of people's homes, but that's about the ratio we're looking at.   Trevor Freeman  10:59 And we're seeing, I think, and tell me if I'm wrong here, like, all this talk about the AI proliferation, data centre proliferation, we're seeing an expansion of these. Is that we're seeing the size of these data centres expand, or we're seeing just more of them popping up. Like, what does it mean when we say we're seeing, like, data centre growth because of AI, what does that mean?   Phil Harris  11:24 Well, it's fascinating, because now our worlds collide, because the way we now think about how to describe a data centre isn't in the square footage or the number of computers, it's in how much power it consumes, and we now measure it in megawatts, and it starts in 10 megawatts, or single digit megawatts, very small data centres, into average size data centres in the 10s of megawatts, up to now the hundreds and the gigawatts of consumption that you look at these hyperscalers. But I think we have to put this into a sort of a human scale. It helps us to put this in human scale. If I were to go back to ChatGPT actually about now, 15 months ago. ChatGPT-4. If you were to put that data centre footprint into the province of Ontario, for example, where you and I both are right now, it would be the equivalent of a million internal combustion engine cars driving 30 kilometers a day, if you ever drive up the 401 you probably don't want to see another million cars on the 401 Yeah, but that's the amount of energy that we can think of in terms of a data centre of that scale.   Trevor Freeman  12:33 Yeah, and again, kind of putting it in the electrical industry's terms, what we consider as a large load so we have a specific designation of a large load request that is anything five megawatts and higher. And like, up until recently, we would get one or two of those every once in a while, like, it's pretty rare to get a large load request. We are seeing large load requests coming in at a near constant pace now, like the number of large load requests we're getting, and a lot of it is because of this, not all because of data centres or anything like that, but a lot of them are certainly driven by that need for more more computing power, more facilities that support that.   Phil Harris  13:18 That's right. And at the same time, we're seeing a demand on on energy around now home, EV charging, and other aspects of the general distribution of the power, everything's taking a step function. But if I could just say one thing to your point about before I was seven megawatts, was a high load, then we may need to change that scale. It's almost inefficient to build a data centre unless you're somewhere above the 10 megawatt range, because at that point, get somebody else to do it for you.   Trevor Freeman  13:42 Interesting, yeah, and that's where it's sort of like, almost like, renting space in a data centre for a request of that size. Interesting, something that you know, I've seen kind of in your in your writing, on your on your blogs, is the idea that traditional data centres are really built for peak capacity, which absolutely mirrors the power industry. We build our electrical grids for peak capacity, and obviously that leads to a fair amount of inefficiencies. So if you're building just a peak capacity, if you're not at peak capacity, there is an inefficiency happening. There something that you identified. It's a stat from your research talks about graphics processing unit usage rates as low as 20 or 25% so I'm assuming that means kind of like three quarters of that hardware is sitting idle or not being used valuably. Tell us a little bit about what, what Cerio what you're doing, what your composable architecture specifically is doing to reclaim that wasted power and cooling capacity,   Phil Harris  14:44 Yeah, and so it starts off with your the premise you correctly raised is that, if we think about the the equipment, the physical equipment, and how we put these devices and these components together in a data centre, the same model we've been using today is, is about 3035, Years old in terms of individual compute systems, where we run applications, software that has memory and central processing units, those typical things you have in a laptop, or you have every computer. But then we put these accelerators, these GPUs, companies like Nvidia now are the one most valuable companies on the planet, if not the most valuable planet company on the planet, because that's the technology they develop. But we're trying to put these new class of accelerators into an existing compute model which wasn't designed for this. So then itself now starts to fragment the ability to leverage those resources in a data centre. And as you accurately said, it's interesting. If I could geek out on this a little bit for the energy consumer in the room, please. Do we think? We think about the notion not only the megawatts of power going into the data but we we think about what we call power usage efficiency. And that basically says, whatever the power delivered to a data centre, how much of that is applicable to the IT systems in that data centre, a good, well run, efficient data centre is about 1.2 that means about 1.2 times the amount of power that's used is delivered. Your home, for example, is about 30 times the amount of power we use is what's delivered. We are very inefficient from our home use, by the way. But that's another problem to solve in another podcast, but in this case, that's all true until we then ask the question, but what's actually being used at that equipment? And that's now in that 25 to 30% range at any point in time, and we refer to that as stranded and idle assets that, for whatever reason, aren't where the application is or aren't applicable to be used for the application that moment because they're in some other box, or it's a time of day when people use equipment. And by the way, equipment like that isn't being used 24 by seven, but it's drawing power 24 by seven, right? So there's lots of inherent inefficiencies in that model. So what we do is we provide the ability to dynamically have pools of resources where we can dynamically attach resources to a compute system as required, at the scale you're required, and allowing you to be much more efficient in the timing of that and the amount of equipment required to meet your end solution. And by doing that, we can increase the number of accelerators that you apply to a compute system, which inherently means you are much more efficient in those compute systems, because it's not just the computers. As I said before, there's storage, there's firewalls, there's load balances, there's networking equipment, all of that can now be much more efficiently used. All of that is drawing power.   Trevor Freeman  17:35 So is the idea, then, that the equipment not being used, or when you're at a lower demand time in terms of computing power, you've got physical equipment idling, sort of in more idle mode, drawing less resources that you can then ramp up so the peak amount of equipment still there. You're just being more efficient with it when it's not being used. And you've developed a way to sort of dynamically pull that in. Is that what I'm hearing.   Phil Harris  18:00 Exactly, I'll give you an example. A data centre here in Toronto wanted to have a block of 128 GPUs. They could have, they could they could service their customers with, with the current systems they were using previously to deploying our infrastructure, they had to require deploy, actually, 200 GPUs and a very large number of servers in the to house those GPUs. By deploying this area technology, they brought that down to 136 actual GPUs, and they reduced the number of compute platforms by a factor of four. So they reduced it by 75%.   Trevor Freeman  18:35 Yeah, that's fantastic,   Phil Harris  18:36 With exactly the same outcomes to their customers. With no no contention for resources, no oversubscription of resources, just more efficient use of those resources.   Trevor Freeman  18:46 Gotcha. So still able to meet that peak demand, but not sort of firing up that equipment when it's not needed.   Phil Harris  18:53 Well, not just not firing it, not having to have as much stranded equipment, because we can use all the equipment all the time.   Trevor Freeman  19:01 Gotcha. Okay, so in when I was kind of setting up that last question, I used the term composable architecture, and I'll admit that I pulled that from your material. Help me understand what that means. So you know that I've also seen you use composable infrastructure sounds a bit abstract, like, what? What are we talking about here? What does that actually look like?   Phil Harris  19:20 When a consumer, or someone who's building a data centre buys their computer equipment, they usually will actually buy the computers, the GPUs, the storage and other things at the same time, and they will get delivered together, and that box now becomes a unit of compute capacity. But the thing about that is whether you're able to use that entire capacity, the length in which that's a useful there's a lot of innovation churn right now as new things are coming through very quickly. But that box is now solid. You know, it's statically built for the rest of its life. Pretty much, it's very expensive. IBM did a study to take a server out of a rack, these big, six foot racks or bigger, where. These servers are housed with lots of wires going into them, power and data and all sorts of things. It's about $1,000 a minute to take one of those servers out of the rack and either change something that's broken, update something so they just don't get taken out of the rack. Because the average time to take a server out of the rack is about an hour. The math on that's pretty simple. So if I'm spending $60,000 to upgrade a 20,030 $1,000 server, I'm just gonna leave it there and buy another one. So that creates more of these stranded assets. So composability says, Let's separate these things into, as I said, pools of resources, compute accelerators and other devices, and have a fabric between them that allows us to, in real time, assemble a compute system that I need. That's the composing part as I need it, because I can now take the resources anywhere in my data centre, if you've got the right fabric, which we've built that allows you then to real time build that compute system with exactly the same capabilities, exactly the same performance, and without having to change any of your software or the way the service work. Everything has to be off the shelf to make this work, and that's what we've built.   Trevor Freeman  21:05 Got you. So, two of the terms, and you'll forgive me, this is sort of a new sector for me. Two of the terms that are used as metrics to determine performance are power usage, effectiveness, and you've kind of talked about, you know, GPU usage. Is the industry moving more towards that GPU usage metric? Is that just something that you guys are kind of leading the curve on? Or where are we at on that?   Phil Harris  21:34 Oh no, this is very much the industry way of describing not just efficiency, but requirements. And we use very weird terms for this. Every industry has their weird term. Weird terminology, and we're now moving to the for example, in AI, the number of tokens per second when you and I put a request or a question into ChatGPT or CoPilot or chord, whatever we use, those words get translated into tokens, actually numbers. Every compute system is just a big calculator. At the end of the day, we do, we do massive processing on numbers. How many of those tokens can I put into the system? How long does it take to process those tokens and give me a response? And the tokens per second, per watt is now what we're asking. So how many tokens a second, and what power per token is it costing me to process information? And that's the interesting way of thinking about how AI, for example, and that's value started this conversation will be measured is the most amount of tokens per second, per watt. Now, right now, we're focusing on tokens per second. We're not looking at the last denominator, which is watts. So that's why these data centres are getting so ridiculous. Ridiculously large. And you know, we even heard it in the in the State of the Union address in the United States earlier in the week, where, you know, there's now the administration pushing cloud vendors and AI vendors to say, Hey, pretty soon you're gonna be on your own about delivering power. Because, quite frankly, the way you're going. It's going to become untenable to think about that from a national grid perspective. Now, I think that may be a little bit into the future, but I don't think it's a completely unreasonable sentiment at this point.   Trevor Freeman  23:12 Yeah, and I mean, you're talking about, and we talked earlier about the just the scale of energy usage here is reaching a new height, a new level. And if we break it down to the individual racks, you know, these racks of servers or processors that you've got in your data centre, we're now talking about anywhere from 50 kilowatts to 100 kilowatts of cooling need. And that's the big driver of energy usage, I think, is correct here is the cooling need per rack multiplied by, of course, big numbers to get those, you know, 5-10-20-30, megawatt data cetnre we're talking about when we talk about cooling and we talk about, you know, hot spots within a data centre, how does your approach differ from kind of the standard way of doing it.   Phil Harris  24:02 So that's a great question, and I think we should explain why the cooling part, it's a bit like buying really good, expensive wagyu steak every day and then having to spend a lot of money on a gym membership to then go and burn off those calories. So we put all this power into power these compute systems, but then we have to keep them cool, and the harder they that, the faster they run, the more powerful they run, the hotter they get. But we need to cool them. So there's this relationship between the more power we draw, the more cooling we need, and cooling is becoming, as I said, that sort of trade off for performance. Now there's lots of exotic ways of cooling computer systems. We can just blow air across them. We can have a liquid like the radiator in your car, or we can literally drop these compute systems into bars of solvents. Ferdinand Porsche, I like to use of other industry analogies. Ferdinand Porsche, the guy who obviously designed the first Porsches and the VW Beetle, realized if I could distribute the heat of the engine block with a horizontal block, I could blow air across it. It was much more efficient than trying to put a radiator to actually cool down the engine block the way that other cars who have the engine in the front, and it's because of surface area. Now, if I've got to put all my GPUs and CPUs and memory close together, either in the same box or the same rack, that concentration of heat needs to be addressed with cooling. One of the ways we can address this is not only to be very selected when I compose the GPU, it's the only time it's drawing power, but also I can spread them out through my data centre by having a fabric that allows me to connect them to the compute systems with the same performance, but now I can distribute my heat generation. That means I can cool more efficiently, just like that Fernand Porsche analogy of the of the Porsche 911 because now heat over over, spread of distance and surface area is a more efficient way, which means it won't mean that we won't ever get to liquid cooling. I don't think immersion cooling is a good idea for lots of other reasons. It's a necessity, more than an optimization, but we can defer the complexity, the cost of those exotic cooling systems if we're more efficient in a way we use and design our data centres.   Trevor Freeman  26:18 And I guess there's a similar description there of, if you're concentrating all that heat in a specific, you know, physical area within a bigger building room, whatever you want to call it, that that cooling system is having to work to that peak cooling need, so to that hot spot effectively. But it's not working just on that spot. It's working across the whole physical area. If you're spreading that cooling need out across the whole room, one the peak is a little bit lower, and you're just more effectively using your whole cooling system. Is that fair to say?   Phil Harris  26:52 And that's exactly the right way of looking at this. And think about it from this perspective as well. The reason we have to cool is because if we don't call sufficiently, those devices become very unreliable and reduce a useful lifespan without going into who, because they keep this information confidential. But one large cloud provider in the US, for example, a GPU that normally has a lifespan of at least three years, is going down to about nine months right now. And the reason for that reduction the lifespan of the use of that GPU, is because of the heating characteristics within these boxes that are getting even with all these cooling mechanisms are becoming now a reduction in the lifespan. So that means we have to create even, remember, I said what it costs to take a system out of a rack. That means we don't have to apply an efficient and effective cooling strategy, our power strategy and cooling trategy, then we start hitting problems very quickly.   Trevor Freeman  27:50 Got you okay. Okay, so there's a mantra that I admit I hadn't seen before until kind of reading some of your material. It's, it's friends. Don't let friends build data centres. And I think it's referring to, you know, this, this move. And there's so many industries that kind of do this cycle of centralization to decentralization, and the sort of data movement went towards that centralization, and you saw these big, massive data centres. But there's, there's kind of a move now back to, let's call it decentralization or repatriation of data. And so for various geopolitical reasons, organizations, companies, governments, are wanting to pull their data back home and have it kind of be more in their control, living in their own servers. So how are you or how is Cerio helping companies kind of get back into the data centre business or repatriate their data without, kind of, you know, getting into the troubles that led for to that centralization in the first place?   Phil Harris  28:55 Yeah, and by the way, I can't take real credit for that quote. Cole Crawford, who was one of the early guys at Facebook before it became META, and was one of the leading voices in the Open Compute platform movement, which is try and standardize how we do these things. Cole is now the CEO of a company called Vapor IO, and what he was really saying is, it's so complicated and difficult to run data centres, let alone building the capital expense. AI isn't just one thing. There's lots of stages in the workflow of AI. We train these big models. You have heard of large language models like ChatGPT or copilot, but what we use them for the results of those trained models is what we call inference. Now you'll now hear about agentic AI, where we turn those results into actions. Okay, that's the agency part of agentic. Well, the use of AI in the corporate world is now becoming, as you said, both regulated, but from an intellectual property perspective, it's about how I control my data and my information. Because if I put that all into somebody else's large language model, I basically put. Populated somebody else's large language model with what might be my proprietary information or information that's very sensitive, and it's one of the reasons why you'll hear in the press about anthropic for example, trying to put guardrails around the use of their AI, because they're very sensitive to this. Most enterprises, governments of all sorts, have realized, though, they need to have run this in their own data centres, because they need to have control over this in control over this information and the use of this information, that's the repatriation you're talking about, moving these workloads now into the organization that previously said, Hey, cloud computing can take this problem. We're going to now figure out how enterprises, which are far many more of them in far more diverse locations, can now build their own data centres and get the right power, the right efficiency, the right capabilities at the right cost.   Trevor Freeman  30:47 Does that open the door? I mean, earlier, you talked about, you know, if we're talking about a five megawatt data centre, it's almost not worth it. You know, that's just sort of renting space in someone else's. How does that track with an organization that won't have enough data or enough computing power, whatever the metric is to warrant a 30 megawatt data centre for their own data, but wants to get that that control, wants to bring it more in house, is our is your technology helping those smaller data centres exist? Is that the correlation there?   Phil Harris  31:18 We can now move it into one of the things that we another couple of terms that may be an maybe not your your listeners may not be familiar with in the compute world or the data centre world, we talk of brownfield and Greenfield. Brownfield is that which is already there. Greenfield is something I have to build new. A lot of the Brownfield world is what is the predominant sort of quantity of compute power on the planet is primarily brownfield The question is, can I take that existing infrastructure and put the capabilities we've been describing in this discussion into those brownfields? So I can reduce the cost of the expansion of that because I can reuse the compute equipments there, I can now add just the discrete GPU technology, for example, into an existing data centre that doesn't therefore blow the power budget or the cooling envelope within that environment, but I can still now start taking advantage as I figure out what my larger plans are, and at the same time, how do we have a tier of providers? I'll give you an example. There's a company in, again, in Canada, think on who are building a data centre in in Ottawa, it's going to have its own liquid natural LNG as its source of power for its own power requirements. Why? Because they can have the power they need as they need it in that location, and they can provide that secure infrastructure for both government and private enterprises, and think on is certainly in Canada, one of those companies that's really seen to be a trusted partner in this. So it will be a bit of what can I do myself? How do I have a trusted partner? We think of sovereign AI a lot. That means trust more than anything, and that's becoming the new mechanism of thinking about this.   Trevor Freeman  33:04 Thinking about the environmental impact of tech and of data. We've talked about the energy usage here, but there's also the physical aspect to it. Of the pace of improvement in technology means we see obsolescence, or we see kind of technology being outdated fairly quickly. We all, like on the personal level. We all see this with our cell phones, our smartphones, our whatever tech we have at home that seems to be out of date fairly soon. I think that the stat, or that the saying that's out there is, you know, tech is kind of obsolete or becomes trash within three years. Obviously, this is not sustainable. Is this part of the drive of what you're doing? Is it? Are you looking to sort of extend the life of the physical equipment you've touched on this a little bit, but maybe expand a little bit on that?   Phil Harris  33:52 Yeah, this goes a little bit back to that Brownfield-Greenfield discussion. But one way of looking at I guess, is when I put all of these components into what the classic model, the current model, I put my central processing unit, my memory, my storage, my GPUs, all in the same box. What is the thing in that box that I want to take advantage of as new innovation happens, versus that which is happening over a slower evolutionary cycle? Well, right now, if I put everything in the same compute unit. Go back to my cost of taking that box out of the rack. I'm pretty much limited by the slowest innovation curve within that platform. Now as what I can take advantage over time. Interestingly, GPUs are innovating currently at a clip of about once a year. Nvidia comes out the new generation of GPUs once a year, but now we're getting more GPUs into the market. We're getting much more diversity, and that diversity means I'll have more options more often. But if my compute system itself is only innovating once every three years to your point, then if I don't decouple these things, if I don't have the ability to separate these innovations. Curves. I'm always stuck with the slowest innovation curve. One of the things we've done at serial with the fabric we've built and the platform we've built is to allow you now to, if you like, dislocate those innovation curves and those options, so as new technology comes along, I can apply it to the things that are innovating slower and still get the outcomes I'm looking for. And that will significantly increase the existing lifespan of equipment that's in people's data centre.   Trevor Freeman  35:26 So, looking at a data centre of the future, and not, you know, not far into the future, let's say 5-10, years from now, are we seeing some of the same technology still exist within that data centre, or is it, you know, everything gets cycled out within like, what's the generation of a data centre, for example? Like, how often, or how soon will we see it all cycle out?   Phil Harris  35:48 I think you there's a there's a technical answer to that, and the financial answer to that. The depreciation model, so that the capital infrastructure can be written off people's books over a three or five year window is very typical. So we see that there's just a financial inhibition to changing more or faster than that three to five year window. The technical churn, as I said, is happening much more rapidly in the technologies that are drawing most power but providing most capability. So one of the things that we're looking at is how companies now start leasing infrastructure, because if they lease the infrastructure, they can now recycle that and bring new technology in faster into their organizations. But to do that, you've got to have the ability to bring new technology in and not be stuck with these static systems that we have today. So there's a set of financial instruments, and now with work that Cerio is doing, technical capabilities that allow customers to really continue to innovate. So there's no real, hey, it's going to be all churned out in three years. I'll continue to innovate over those three years, reciting the technology that can stay where it is and bringing new technologies as it becomes available at the right financial model.   Trevor Freeman  36:56 I'm curious about what that innovation is. So you talked about Nvidia, kind of essentially a new GPU every year. There's a new version every year. What is the innovation? Are they just is it getting faster and more compute power, and therefore it's pulling more energy? And is that just like a perpetual increase, or is it kind of same compute power, less energy, like, do we ever see, I guess what I'm what I'm getting at with this little bit of a ramble here is, do we ever see that that rate of change in energy usage start to flatten out and come down while we still can grow our computing power? Or does energy usage just continue to grow? Like, are we on a bit of a path with no end right now,   Phil Harris  37:44 History taught us a little bit about this. Gordon Moore, who was one of the founders of Intel actually, we had this term called Moore's Law, and Moore's Law was basically this idea that every 18 months we'll double the number of transistors on a piece of silicon. Now, for those in the computer science world, we understand what that means. For the rest of the world, the Trans World. The transistor is the smallest unit of technology within the computer. It's the basic building block of how we build computers. The central processing is all the GPUs. They all come down to taking literally silicon and in a foundry, we call them, figuring out how to make as many transistors interconnect with each other in a in a smaller area as possible, or the most amount of transistors we can. So a bit of a geeky answer to your question. But the way that we look at how each innovation improves is, are we increasing the number of transistors, which means we can do more math? Remember, all we're doing is processing numbers.   Trevor Freeman  38:41 Per unit, per physical unit, right?   Phil Harris  38:43 Per physical unit.   Trevor Freeman  38:44 Okay.   Phil Harris  38:45 And the way we do that is in these big foundries that process all this silicon into these components. They have, what are called process nodes and the and literally how we etch a transistor, it's called lithography onto a piece of silicon. Tells us the power of that piece of silicon and the more I can etch. So we get into what we call the nanometer scale, or what we call a process node. So every time, if you really look into the spec sheets of Nvidia, every generation, they'll talk about how many nanometers their silicon process is based on. Because the smaller I can get that number, the more transistors I can have on the same amount of silicon, the more processing I have, but every transistor takes power. So with more transistors, I require more power, even though in the same physical space, it looks like the same amount of silicon. Therefore, your question was a great one. Do we ever get to zero nanometers? Well, no, we're going to hit a wall here eventually. So then the question is, that's the scale up model. Try and make one thing as big as possible. How about if we make lots of things powerful, but we have more of them in China, the last year, we heard of deep seek. Deep seek was a Chinese government sponsored effort to try and come up with a. Much more cost effective way of doing the equivalent to ChatGPT. They didn't do that with bigger GPUs. They did it with much smaller GPUs, but many more of them. And that comes back to how efficient I am in deploying lots of things together. And that goes back to my earlier point about we start with scale up. Inevitably, in the industry, we go to scale out.   Trevor Freeman  40:22 And is it fair to say that the power usage per transistor, is that fairly static? Like, is there efficiencies to gain there? Or your GPU is going to use more power because you're packing more transistors into it, and once you hit that wall, that's going to be the power consumption level, is that, right?   Phil Harris  40:43 Well, this is the games that these silicon manufacturers, like Intel, AMD, Nvidia, they're all trying to figure out how to sort of figure out new and interesting ways of packaging all of the silicon in these processing units. And we've got a whole industry and science around the packaging mechanism to make those tiles, and that we now think of them as little tiles of processing power, and some that will be doing very specific jobs. Some will be doing very general jobs. It's now getting to the point where the science around the packaging of these dyes or these tiles is as much as the of the of the innovation, as the actual tiles and the processing on them. So it's an extremely complex technical problem, and we are hitting some walls here, which is why I go back to my earlier point. We're now reaching a point where is it just a technical problem we're solving, or a technical, operational and commercial problem we have to think about? And this is that wall that wall that you asked me about right at the beginning of this conversation. Are we about to hit a wall? And the answer is, yes.   Trevor Freeman  41:46 Interesting. I mean, I'm always fascinated by like, what are the what are the really smart people in the industry focusing their time on? And it's so that's why we're talking to you. Of you know, you're looking at, how do we operationalize this. How do we get the most efficient combination and structure of what we're doing here? There's folks that are looking at, how do we pack the most computing power efficiency into these specific units? I guess there's an aspect of, how do we cool this in the in the most effective way, like, what's, how do we, you know, drive down the cooling power needed? What else is out there, in terms of, like, we have smart people focused on this efficiency. What's the thing that's missing from that, that sort of list?   Phil Harris  42:36 Well, I think maybe what's going on right now. And if I could just add a, unfortunately, just one more layer of complexity.  Remember said we were processing silicon? Well, the Earth's got lots of silicon, but we don't have lots of places to process that silicon. The companies that are formed to process silicon into these processing units, we call them foundries. The world's largest is TSMC, based in Taiwan. And then we have Intel, we have Samsung, we have a few others around the world. Global Foundry is another one. There is a limit, physical limit, because these foundries are huge and they take decades of development and optimization. So if we start breaking ground on a new foundry tomorrow, we'll see output in about five years. So we have a constrained supply. So if I'm if I'm Jensen at Nvidia or any of the big silicon manufacturers, I'm going to optimize that relatively constrained supply to where I'm going to get the best return on my investment. And that's why this scale up model is happening. So given that we know that we won't have any more foundry capacity of scale for another couple of years, at least, then the reality is we've got to think differently about how we're thinking about the processing of that silicon. Do I want just ever bigger processes that become more expensive, more limited in where I can deploy them. And quite frankly, the top 15 consumers in the world of silicon consume about 80% of that silicon, if not more. How do I democratize that? Again, it goes from scale up to a scale out model, where I can use that same processing capacity to produce more silicon.   Trevor Freeman  44:20 Fascinating. Yeah, I just, I took us down a little bit of a nerd out path. You had me really interested in that. Okay, so last question here, we hear this term for a bunch of different reasons. Around the world right now we're hearing this term democratizing, happening a lot, and I know you've talked about democratizing, AI, what does that mean? What does that mean to you, or describe that for us?   Phil Harris  44:48 Yeah, I think it really means. Going back to my last point about if 15 big consumers of silicon are going to consume the vast majority of verbal supply chain, that makes the. At a losing proposition for the rest of the organizations and the rest of the governments and the rest of the individuals on the planet. So how do we make sure that AI can be built both responsibly from a sustainability perspective, right? And I don't mean just the ecological side, but that's important here too, but also from the ability to I was on a panel yesterday between the UK Government and the Canadian government, where we're looking at how do countries around the world have the ability to control their own destiny? And there's this whole notion of sovereignty and AI sovereignty right now that isn't because people want to have closed walls around them, that you want to have choice. They don't want to be dictated to by very dominant players where they, quite frankly, don't have the buying power to compete. You know that the amount of capital going into some of the AI companies, we saw $30 billion going into anthropic last week. That's actually a small increase in their capitalization relative to the other big AI players on the planet. That's $30 billion so we've got to think to ourselves, is that a sustainable model commercially? And the answer is no. So we've got to have technology. We've got to have the right ability to deliver power. We've got to have the right designs of data centres that can keep them cooled in an effective and efficient and responsible way. And we've got to be able to give them enough power to make them viable, to make them useful. That's the democratization we all have to be focused on.   Trevor Freeman  46:25 And we need every, I guess, to sort of round of the point is we need everybody to be able, everybody being, you know, whatever, major industry, countries, whoever, to be able to access that equally, so that we don't have to rely on the major players out there in order to do those things you just said, gotcha.   Phil Harris  46:41 That's exactly right. And look, there'll always be a pyramid here. There always has been a technology. There's always still the big players, right? But the question is, have the big players the stifled out the ability for smaller players to come up, innovate, provide choice, provide alternative ways of looking at things, and that's what got to make sure that we keep the and this always relies on some new technology coming along that enables that. Sarah believes that we've created that next layer in the stack, if you like, of technologies that gives us that opportunity to rethink the innovation curve going forward.   Trevor Freeman  47:14 Very fascinating. Phil, thanks for your time. I really appreciate it. This has been super interesting. It's not an area that I often get to spend my time thinking about so is great to chat today. As as you know, we always kind of round out our interviews with the same series of questions to our guests. So what's a book that you've read that you think everybody should read?   Phil Harris  47:34 Well, I'm not sure I can recommend this for everybody. One of the people who basically, along the lines of some of the things I've been talking about today, who revolutionized the computer world was a gentleman by the name of Linus Torvald in Helsinki in Finland. At the time, he's now based in the States, he realized that there was a dominance around how the operating systems on computers, the things that run the software, was limiting, basically, innovation choice and forcing us down a very closed path. So he wrote something called Linux, which was a new operating system. So be on your phone, your TV, your microwave that's running Linux today. Interesting because there wasn't an operating system that we could then generally deploy. That meant there was more developers had the ability to write applications, more hardware vendors could now have software they could run on their on their platforms. He gave the world a new innovation curve. And every time this happens to my last point, good things happen. Very good things happen for the world, for every individual on the planet. And Linus was one of those individuals who saw that need. And so his book, just for fun, and he's a very quirky guy, as you can probably imagine, is a great book about his philosophical approach to what it takes to change really big problems. And I would encourage all of you just to even just read the first few chapters. It's a fascinating view of how an incredibly smart man, smart individual took on probably one of the biggest problems we had in the 20th and 21st Century of computing, and solved it by recognizing you take a different path.   Trevor Freeman  49:11 Yeah, very cool.   Phil Harris  49:12 As far as shows, um, I don't know. I'm one of these guys. I've got two 13 year old daughters. So my wife and I get to watch TV for a very limited amount of time where we can watch it, about the things we want to watch, so we tend to sort of cram things in. But I'm a huge Aaron Sorkin fan, so if I ever need something on a rainy day to go back just to think about how the world could be, I watch the West Wing. It's a show that's imaginary. It's got incredible script writing, it's got incredible character development, but it really talks about how to think about doing the right thing as well. Now, whether you agree with the politics or not, that's a different question, but just the thought that smart thinking solves big problems, again, sort of It's a bit like the Linus Torvald book. It just speaks to me about sometimes we can solve big problems. With individuals or people who just had the right way of thinking about things.   Trevor Freeman  50:00 Yeah, I think that's the kind of, you know, call it entertainment, because it is entertainment, but it's the entertainment that sticks with you, and that we go back to time and again, is the ones that we can also, like, see the the underlying philosophy, or, you know, theory of change that goes into that entertainment. And it's, it's fun to watch. It's, you know, either humorous or dramatic or whatever, but there's still that underlying message. And I think, yeah, West Wing is a great example of of that. There's a handful of those other sort of classic shows that are in that line too. A free round trip flight anywhere in the world. Where would you go?   Phil Harris  50:40 This is hard. My wife and I were talking about this the other day, and I've had the luxury of traveling just about everywhere. I think there's 15 countries on the planet I haven't been to, but if I ever want to go to one place is Bali. And there's two reasons. One, my wife and I went there for a honeymoon, and it was the beginning of the most important chapter of my life by far. And secondly, it's because it has that balance of everything. It's I love to scuba dive. I love the rainforests, the jungle, the architecture, the people, the food. It just brings everything into one package for me. And so it just again. It's those things that sort of speak to you emotionally and also intellectually. It's one of those things that I could always go back too.   Trevor Freeman  51:26 Fantastic. Who is someone that you admire?   Phil Harris  51:29 In history or today?   Trevor Freeman  51:32 You pick, anything.   Phil Harris  51:33 that's fascinating. I think historically it's under Brit it's hard not to go back to some of my forebears, or my country's forebears, Alan Turing, who, against all adversity, social, political, technical, came up with an inspirational way of thinking about solving what are deemed to be unsolvable. And again, it's a tragic story. I think we've all, if you see the movie that was made about his life, it's a very tragic story, but it's an inspirational story about how, again, if you just take a different approach to solving what seems to be an unsolvable problem, you can you get smart people together. Doesn't have to be a big army of people. I think so. Turing is one of those people that always comes back for me t think, wow, if I could have just some of his courage and some of his imagination and some of his intellect, I'd be a very happy person.   Trevor Freeman  52:29 Yeah, and it's almost, I mean, obviously, a brilliant man, but it's the willing to think in a different way, or willing to approach a problem in a different way that I mean, there's a long list in history of major turning points that are as a result of someone thinking in a different way or doing something in a different way. And I think that's a great example of it.   Phil Harris  52:49 Just about the entire course of human life are in the midpoint of the 20th century, change on that, that man's inspiration, that man's imagination.   Trevor Freeman  52:57 Yeah, and that's, that's not an understatement. That's fantastic. Okay, last question, what's something about, kind of the energy sector, or, you know, your sector that that you're really excited about, or something that you see in the future that you're really excited about?   Phil Harris  53:09 Actually, I see it now, to be honest, there are things in the future. Hey, I have two 13 year old kids. I want to have a sustainable ecology and world environment for them to live in and bring their own families up in. And I think about how we can use power more efficiently, but how we can make it look sustainability is important. I want to see renewable, sustainable energy for the general world as a thesis right now. It's how we can be much more efficient in the use of power and the right power delivery. And I think, as I said, I gave the think on example, that's incredibly exciting, because now, if we can do that at scale, that's an opportunity to do that democratization that I spoke about. So when I think about the things that really excited me about the data centre world, the world I live in, actually that power generation and power availability in a clean, effective, well managed fashion is exactly what we need right now, while the rest of us are solving these transistor problems.   Trevor Freeman  54:04 Yeah, it's, I mean, our listeners are probably going to roll their eyes, because I say this all the time, but one of the things that excites me the most is seeing like we're in a period of change, and that's a really exciting time to be working in this and I kind of hear that from you in your sector as well, and I see it in mine, in the energy sector of we're actually getting to see some of this innovation, some of these like leaps and bounds forward. That's not to say there aren't still problems. It's not to say there aren't steps backwards as well. But it's very cool to be working on this in a time when we're seeing that change, and that's kind of what I'm hearing from you as well. Indeed. Awesome. Phil, thanks so much for your time. I really appreciate it. This has been great. Chatting with you.   Phil Harris  54:42 Trevor, the pleasure is all mine. Thank you.   Trevor Freeman  54:44 Fantastic. Take care.   Phil Harris  54:46 Take care.   Trevor Freeman  54:47 Thanks for tuning in to another episode of the thinkenergy podcast. Don't forget to subscribe wherever you listen to podcasts, and it would be great if you could leave us a review. It really helps to spread the word. As always, we would love to hear from you whether. Feedback, comments or an idea for a show or a guest, you can always reach us at thinkenerg@hydroottawa.com.

In this episode, Pascal talks to Dharmesh J. (DJ) and Lisa about the vision for the open, scalable future of networking hardware for AI and to break down Meta's big announcements from the 2025 Open Compute Project (OCP) Summit. We dive into the OCP ecosystem, explore how AI is used to enhance our carbon modeling, and share our progress toward achieving Net Zero emissions across all scopes by 2030. Got feedback? Send it to us on Threads (https://threads.net/@metatechpod), Instagram (https://instagram.com/metatechpod) and don't forget to follow our host Pascal (https://mastodon.social/@passy, https://threads.net/@passy_). Fancy working with us? Check out https://www.metacareers.com/. Links OCP: https://www.opencompute.org/ OCP Summit 2025: https://engineering.fb.com/2025/10/13/data-infrastructure/ocp-summit-2025-the-open-future-of-networking-hardware-for-ai/  How Meta Is Leveraging AI To Improve the Quality of Scope 3 Emission Estimates for IT Hardware: https://engineering.fb.com/2025/10/14/data-center-engineering/how-meta-is-leveraging-ai-to-improve-the-quality-of-scope-3-emission-estimates-for-it-hardware/  Timestamps Intro 0:06 Introduction Lisa 1:49 Introduction DJ 3:16 What is OCP? 4:04 OCP's scale 5:24 Open vs closed hardware ecosystems 9:26 Examples of OCP projects 11:33 Sustainability in OCP 14:08 How did you get into OCP? 15:59 Marrying infrastructure growth with sustainability 19:05 Emissions scopes and tracking 25:07 Measuring scope 3 26:06 What components embed the most carbon? 30:47 DFE vs DFS 32:34 Hardware reuse 33:39 Outro 37:48

The equipment that fills data centers is evolving rapidly, driven by the need to fulfill the seemingly insatiable appetite of AI applications. The Open Compute Project (OCP) was founded by Meta/Facebook to promulgate equipment standards and its annual Summit has grown from a small specialized gathering, to an event that strains the capacity of the San Jose Convention Center. Senior research analyst Perkins Liu returns to offer his take on this meteoric growth with host Eric Hanselman. AI requirements are pushing ever greater scale both logically and physically, with the width of server racks doubling in the Open Rack Wide (ORW) specification to support greater density and better serviceability. The OCP Foundation is also working on silicon interoperability and is setting specifications for chiplet integration. Liquid cooling has moved from a nice to have feature to a required capability as a means to dissipate the huge amount of energy drawn by ever denser GPU arrays. Energy delivery is changing with the advent of higher voltage DC power. The early OCP efforts on 48 volt DC are paling in the face of new 800 volts designs. The OCP Foundation is also expanding its mission to include education, with the establishment of the OCP Academy. It aims to raise workforce skills in open hardware and will offer online training in data center technologies. That underscores not only the expansion of the OCP Foundation's mission, but also the increasing scale of the ecosystem that supports data center environments and complexity and interdependency that AI creates.   More S&P Global Content: Sustainability continues to drive datacenter infrastructure evolution Webinar: Talk to the Expert - Artificial intelligence, datacenters and energy: Is APAC ready for th… For S&P Global subscribers: Air cooling remains prevalent, but liquid cooling is gaining momentum – Highlights from VotE: Datac… Adjusted definitions of datacenter markets in China align with socioeconomic processes Datacenters increasingly use direct current to cope with AI workloads Credits: Host/Author: Eric Hanselman  Guest: Perkins Liu Producer/Editor: Feranmi Adeoshun Published With Assistance From: Sophie Carr, Kyra Smith

WASHINGTON, D.C.— At this year's Data Center World 2025, held earlier this month at the Walter E. Washington Convention Center, the halls were buzzing with what could only be described as industry sensory overload. As hyperscalers, hardware vendors, and infrastructure specialists converged on D.C., the sheer density of innovation underscored a central truth: the data center sector is in the midst of rapid, almost disorienting, expansion. That made it the perfect setting for the latest episode in our ongoing podcast miniseries with Nomad Futurist, aptly titled Nomads at the Frontier. This time, I sat down in person with Nabeel Mahmood, co-founder and board director of the Nomad Futurist Foundation—a rare face-to-face meeting after years of remote collaboration. “Lovely seeing you in person,” Mahmood said. “It's brilliant to get to spend some quality time at an event that's really started to hit its stride—especially in terms of content.” Mahmood noted a welcome evolution in conference programming: a shift away from vendor-heavy pitches and toward deeper, mission-driven dialogue about the sector's true challenges and future trajectory. “Events like these were getting overloaded by vendor speak,” he said. “We need to talk about core challenges, advancements, and what we're doing to improve and move forward.” A standout example of this renewed focus was a panel on disruptive sustainability, in which Mahmood joined representatives from Microsoft, AWS, and a former longtime lieutenant of Elon Musk's sustainability operations. “It's not just about e-cycling or carbon,” Mahmood emphasized. “We have to build muscle memory. We've got to do things for the right reasons—and start early.” That starting point, he argued, is education—but not in the traditional sense. Instead, Mahmood called for a multi-layered approach that spans K–12, higher education, and workforce reskilling. “We've come out from behind the Wizard of Oz curtain,” he said. “Now we're in the boardroom. We need to teach people not just how technology works, but why we use it—and how to design platforms with real intention.” Mahmood's remarks highlighted a growing consensus among forward-thinking leaders: data is no longer a support function. It is foundational. “There is no business, no government, no economy that can operate today—or in the future—without data,” he said. “So let's measure what we do. That's the KPI. That's the minimum threshold.” Drawing a memorable parallel, Mahmood compared this kind of education to swimming lessons. “Sure, you might not swim for 20 years,” he said. “But if you learned as a kid, you'll still be able to make it back to shore.” Inside-Out Sustainability and Building the Data Center Workforce of Tomorrow As our conversation continued, we circled back to Mahmood's earlier analogy of swimming as a foundational skill—like technology fluency, it stays with you for life. I joked that I could relate, recalling long-forgotten golf lessons from middle school. “I'm a terrible golfer,” I said. “But I still go out and do it. It's muscle memory.” “Exactly,” Mahmood replied. “There's a social element. You're able to enjoy it. But you still know your handicap—and that's part of it too. You know your limits.” Limits and possibilities are central to today's discourse around sustainability, especially as the industry's most powerful players—the hyperscalers—increasingly self-regulate in the absence of comprehensive mandates. I asked Mahmood whether sustainability had truly become “chapter and verse” for major cloud operators, or if it remained largely aspirational, despite high-profile initiatives. His answer was candid. “Yes and no,” he said. “No one's following a perfect process. There are some who use it for market optics—buying carbon credits and doing carbon accounting to claim carbon neutrality. But there are others genuinely trying to meet their own internal expectations.” The real challenge, Mahmood noted, lies in the absence of uniform metrics and definitions around terms like “circularity” or “carbon neutrality.” In his view, too much of today's sustainability push is “still monetarily driven… keeping shareholders happy and share value rising.” He laid out two possible futures. “One is that the government forces us to comply—and that could create friction, because the mandates may come from people who don't understand what our industry really needs. The other is that we educate from within, define our own standards, and eventually shape compliance bodies from the inside out.” Among the more promising developments Mahmood cited was the work of Rob Lawson-Shanks, whose innovations in automated disassembly and robotic circularity are setting a high bar for operational sustainability. “What Rob is doing is amazing,” Mahmood said. “His interest is to give back. But we need thousands of Robs—people who understand how it works and can repurpose that knowledge back into the tech ecosystem.” That call for deeper education led us to the second major theme of our conversation: preparing the next generation of data center professionals. With its hands-on community initiatives, Nomad Futurist is making significant strides in that direction. Mahmood described his foundation as “connective tissue” between industry stakeholders and emerging talent, partnering with organizations like Open Compute, Infrastructure Masons, and the iMasons Climate Accord. Earlier this year, Nomad Futurist launched an online Academy that now features five training modules, with over 200 hours of content development in the pipeline. Just as importantly, the foundation has built a community collaboration platform—native to the Academy itself—that allows learners to directly engage with content creators. “If a student has a question and the instructor was me or someone like you, they can just ask it directly within the platform,” Mahmood explained. “It creates comfort and accessibility.” In parallel, the foundation has beta launched a job board, in partnership with Infrastructure Masons, and is developing a career pathways platform. The goal: to create clear entry points into the data center industry for people of all backgrounds and education levels—and to help them grow once they're in. “Those old jobs, like the town whisperer, they don't exist anymore,” Mahmood quipped. “Now it's Facebook, Twitter, social media. That's how people get jobs. So we're adapting to that.” By providing tools for upskilling, career matching, and community-building, Mahmood sees Nomad Futurist playing a key role in preparing the sector for the inevitable generational shift ahead. “As we start aging out of this industry over the next 10 to 20 years,” he said, “we need to give people a foundation—and a reason—to take it forward.”

At Open Compute Summit this past week, key trends shaping the future of computing and infrastructure were discussed. One major concern is the global data center energy consumption, which is projected to triple by 2030, highlighting the urgent need for more efficient energy solutions. As technology advances, the shift from a 3nm process to a 2nm process is proving costly, with design costs estimated to reach a staggering $725 million, according to ARM. In response to both power demands and design challenges, liquid cooling is gaining momentum, emerging as a vital technology to improve efficiency and manage the increasing heat output from advanced computing systems. Time Stamps: 0:00 - Welcome to the Rundown 1:36 - BMC Starts Two New Companies 4:06 - CEO Indicted for Fraud 7:10 - Microsoft goes agentic AI 10:37 - Amazon Teams Up with US Department of Justice 14:30 - Perplexity Is getting Sued by Media Giants 16:44 - Sophos Acuires Secureworks 20:00 - Exciting Developments from Open Compute Summit 31:41 - The Weeks Ahead 32:56 - Thanks for Watching Hosts: Tom Hollingsworth: https://www.linkedin.com/in/networkingnerd/ Jon Swartz: https://www.linkedin.com/in/jonswartz/ Follow Gestalt IT Website: https://www.GestaltIT.com/ Twitter: https://www.twitter.com/GestaltIT LinkedIn: https://www.linkedin.com/company/Gestalt-IT #Rundown, #OCPSummit24, #AgenticAI, @NetworkingNerd, @JSwartz, @GestaltIT, @TechstrongGroup, @TechstrongTV, @TheFuturumGroup, @BMCSoftware, @Microsoft, @AWSCloud, @Sophos, @Secureworks, @perplexity_ai, @OpenComputePrj,

Kirk sits down with Rob Coyle and Dirk Van Slyke of the Open Compute Project to discuss the origins of the OCP and what they are doing to drive change in the future.

Steve Tuck, Co-Founder & CEO of Oxide Computer Company, joins Corey on Screaming in the Cloud to discuss his work to make modern computers cloud-friendly. Steve describes what it was like going through early investment rounds, and the difficult but important decision he and his co-founder made to build their own switch. Corey and Steve discuss the demand for on-prem computers that are built for cloud capability, and Steve reveals how Oxide approaches their product builds to ensure the masses can adopt their technology wherever they are. About SteveSteve is the Co-founder & CEO of Oxide Computer Company.  He previously was President & COO of Joyent, a cloud computing company acquired by Samsung.  Before that, he spent 10 years at Dell in a number of different roles. Links Referenced: Oxide Computer Company: https://oxide.computer/ On The Metal Podcast: https://oxide.computer/podcasts/on-the-metal TranscriptAnnouncer: Hello, and welcome to Screaming in the Cloud with your host, Chief Cloud Economist at The Duckbill Group, Corey Quinn. This weekly show features conversations with people doing interesting work in the world of cloud, thoughtful commentary on the state of the technical world, and ridiculous titles for which Corey refuses to apologize. This is Screaming in the Cloud.Corey: This episode is brought to us in part by our friends at RedHat. As your organization grows, so does the complexity of your IT resources. You need a flexible solution that lets you deploy, manage, and scale workloads throughout your entire ecosystem. The Red Hat Ansible Automation Platform simplifies the management of applications and services across your hybrid infrastructure with one platform. Look for it on the AWS Marketplace.Corey: Welcome to Screaming in the Cloud. I'm Corey Quinn. You know, I often say it—but not usually on the show—that Screaming in the Cloud is a podcast about the business of cloud, which is intentionally overbroad so that I can talk about basically whatever the hell I want to with whoever the hell I'd like. Today's guest is, in some ways of thinking, about as far in the opposite direction from Cloud as it's possible to go and still be involved in the digital world. Steve Tuck is the CEO at Oxide Computer Company. You know, computers, the things we all pretend aren't underpinning those clouds out there that we all use and pay by the hour, gigabyte, second-month-pound or whatever it works out to. Steve, thank you for agreeing to come back on the show after a couple years, and once again suffer my slings and arrows.Steve: Much appreciated. Great to be here. It has been a while. I was looking back, I think three years. This was like, pre-pandemic, pre-interest rates, pre… Twitter going totally sideways.Corey: And I have to ask to start with that, it feels, on some level, like toward the start of the pandemic, when everything was flying high and we'd had low interest rates for a decade, that there was a lot of… well, lunacy lurking around in the industry, my own business saw it, too. It turns out that not giving a shit about the AWS bill is in fact a zero interest rate phenomenon. And with all that money or concentrated capital sloshing around, people decided to do ridiculous things with it. I would have thought, on some level, that, “We're going to start a computer company in the Bay Area making computers,” would have been one of those, but given that we are a year into the correction, and things seem to be heading up into the right for you folks, that take was wrong. How'd I get it wrong?Steve: Well, I mean, first of all, you got part of it right, which is there were just a litany of ridiculous companies and projects and money being thrown in all directions at that time.Corey: An NFT of a computer. We're going to have one of those. That's what you're selling, right? Then you had to actually hard pivot to making the real thing.Steve: That's it. So, we might as well cut right to it, you know. This is—we went through the crypto phase. But you know, our—when we started the company, it was yes, a computer company. It's on the tin. It's definitely kind of the foundation of what we're building. But you know, we think about what a modern computer looks like through the lens of cloud.I was at a cloud computing company for ten years prior to us founding Oxide, so was Bryan Cantrill, CTO, co-founder. And, you know, we are huge, huge fans of cloud computing, which was an interesting kind of dichotomy. Instead of conversations when we were raising for Oxide—because of course, Sand Hill is terrified of hardware. And when we think about what modern computers need to look like, they need to be in support of the characteristics of cloud, and cloud computing being not that you're renting someone else's computers, but that you have fully programmable infrastructure that allows you to slice and dice, you know, compute and storage and networking however software needs. And so, what we set out to go build was a way for the companies that are running on-premises infrastructure—which, by the way, is almost everyone and will continue to be so for a very long time—access to the benefits of cloud computing. And to do that, you need to build a different kind of computing infrastructure and architecture, and you need to plumb the whole thing with software.Corey: There are a number of different ways to view cloud computing. And I think that a lot of the, shall we say, incumbent vendors over in the computer manufacturing world tend to sound kind of like dinosaurs, on some level, where they're always talking in terms of, you're a giant company and you already have a whole bunch of data centers out there. But one of the magical pieces of cloud is you can have a ridiculous idea at nine o'clock tonight and by morning, you'll have a prototype, if you're of that bent. And if it turns out it doesn't work, you're out, you know, 27 cents. And if it does work, you can keep going and not have to stop and rebuild on something enterprise-grade.So, for the small-scale stuff and rapid iteration, cloud providers are terrific. Conversely, when you wind up in the giant fleets of millions of computers, in some cases, there begin to be economic factors that weigh in, and for some on workloads—yes, I know it's true—going to a data center is the economical choice. But my question is, is starting a new company in the direction of building these things, is it purely about economics or is there a capability story tied in there somewhere, too?Steve: Yeah, it's actually economics ends up being a distant third, fourth, in the list of needs and priorities from the companies that we're working with. When we talk about—and just to be clear we're—our demographic, that kind of the part of the market that we are focused on are large enterprises, like, folks that are spending, you know, half a billion, billion dollars a year in IT infrastructure, they, over the last five years, have moved a lot of the use cases that are great for public cloud out to the public cloud, and who still have this very, very large need, be it for latency reasons or cost reasons, security reasons, regulatory reasons, where they need on-premises infrastructure in their own data centers and colo facilities, et cetera. And it is for those workloads in that part of their infrastructure that they are forced to live with enterprise technologies that are 10, 20, 30 years old, you know, that haven't evolved much since I left Dell in 2009. And, you know, when you think about, like, what are the capabilities that are so compelling about cloud computing, one of them is yes, what you mentioned, which is you have an idea at nine o'clock at night and swipe a credit card, and you're off and running. And that is not the case for an idea that someone has who is going to use the on-premises infrastructure of their company. And this is where you get shadow IT and 16 digits to freedom and all the like.Corey: Yeah, everyone with a corporate credit card winds up being a shadow IT source in many cases. If your processes as a company don't make it easier to proceed rather than doing it the wrong way, people are going to be fighting against you every step of the way. Sometimes the only stick you've got is that of regulation, which in some industries, great, but in other cases, no, you get to play Whack-a-Mole. I've talked to too many companies that have specific scanners built into their mail system every month looking for things that look like AWS invoices.Steve: [laugh]. Right, exactly. And so, you know, but if you flip it around, and you say, well, what if the experience for all of my infrastructure that I am running, or that I want to provide to my software development teams, be it rented through AWS, GCP, Azure, or owned for economic reasons or latency reasons, I had a similar set of characteristics where my development team could hit an API endpoint and provision instances in a matter of seconds when they had an idea and only pay for what they use, back to kind of corporate IT. And what if they were able to use the same kind of developer tools they've become accustomed to using, be it Terraform scripts and the kinds of access that they are accustomed to using? How do you make those developers just as productive across the business, instead of just through public cloud infrastructure?At that point, then you are in a much stronger position where you can say, you know, for a portion of things that are, as you pointed out, you know, more unpredictable, and where I want to leverage a bunch of additional services that a particular cloud provider has, I can rent that. And where I've got more persistent workloads or where I want a different economic profile or I need to have something in a very low latency manner to another set of services, I can own it. And that's where I think the real chasm is because today, you just don't—we take for granted the basic plumbing of cloud computing, you know? Elastic Compute, Elastic Storage, you know, networking and security services. And us in the cloud industry end up wanting to talk a lot more about exotic services and, sort of, higher-up stack capabilities. None of that basic plumbing is accessible on-prem.Corey: I also am curious as to where exactly Oxide lives in the stack because I used to build computers for myself in 2000, and it seems like having gone down that path a bit recently, yeah, that process hasn't really improved all that much. The same off-the-shelf components still exist and that's great. We always used to disparagingly call spinning hard drives as spinning rust in racks. You named the company Oxide; you're talking an awful lot about the Rust programming language in public a fair bit of the time, and I'm starting to wonder if maybe words don't mean what I thought they meant anymore. Where do you folks start and stop, exactly?Steve: Yeah, that's a good question. And when we started, we sort of thought the scope of what we were going to do and then what we were going to leverage was smaller than it has turned out to be. And by that I mean, man, over the last three years, we have hit a bunch of forks in the road where we had questions about do we take something off the shelf or do we build it ourselves. And we did not try to build everything ourselves. So, to give you a sense of kind of where the dotted line is, around the Oxide product, what we're delivering to customers is a rack-level computer. So, the minimum size comes in rack form. And I think your listeners are probably pretty familiar with this. But, you know, a rack is—Corey: You would be surprised. It's basically, what are they about seven feet tall?Steve: Yeah, about eight feet tall.Corey: Yeah, yeah. Seven, eight feet, weighs a couple 1000 pounds, you know, make an insulting joke about—Steve: Two feet wide.Corey: —NBA players here. Yeah, all kinds of these things.Steve: Yeah. And big hunk of metal. And in the cases of on-premises infrastructure, it's kind of a big hunk of metal hole, and then a bunch of 1U and 2U boxes crammed into it. What the hyperscalers have done is something very different. They started looking at, you know, at the rack level, how can you get much more dense, power-efficient designs, doing things like using a DC bus bar down the back, instead of having 64 power supplies with cables hanging all over the place in a rack, which I'm sure is what you're more familiar with.Corey: Tremendous amount of weight as well because you have the metal chassis for all of those 1U things, which in some cases, you wind up with, what, 46U in a rack, assuming you can even handle the cooling needs of all that.Steve: That's right.Corey: You have so much duplication, and so much of the weight is just metal separating one thing from the next thing down below it. And there are opportunities for massive improvement, but you need to be at a certain point of scale to get there.Steve: You do. You do. And you also have to be taking on the entire problem. You can't pick at parts of these things. And that's really what we found. So, we started at this sort of—the rack level as sort of the design principle for the product itself and found that that gave us the ability to get to the right geometry, to get as much CPU horsepower and storage and throughput and networking into that kind of chassis for the least amount of wattage required, kind of the most power-efficient design possible.So, it ships at the rack level and it ships complete with both our server sled systems in Oxide, a pair of Oxide switches. This is—when I talk about, like, design decisions, you know, do we build our own switch, it was a big, big, big question early on. We were fortunate even though we were leaning towards thinking we needed to go do that, we had this prospective early investor who was early at AWS and he had asked a very tough question that none of our other investors had asked to this point, which is, “What are you going to do about the switch?”And we knew that the right answer to an investor is like, “No. We're already taking on too much.” We're redesigning a server from scratch in, kind of, the mold of what some of the hyperscalers have learned, doing our own Root of Trust, we're doing our own operating system, hypervisor control plane, et cetera. Taking on the switch could be seen as too much, but we told them, you know, we think that to be able to pull through all of the value of the security benefits and the performance and observability benefits, we can't have then this [laugh], like, obscure third-party switch rammed into this rack.Corey: It's one of those things that people don't think about, but it's the magic of cloud with AWS's network, for example, it's magic. You can get line rate—or damn near it—between any two points, sustained.Steve: That's right.Corey: Try that in the data center, you wind into massive congestion with top-of-rack switches, where, okay, we're going to parallelize this stuff out over, you know, two dozen racks and we're all going to have them seamlessly transfer information between each other at line rate. It's like, “[laugh] no, you're not because those top-of-rack switches will melt and become side-of-rack switches, and then bottom-puddle-of-rack switches. It doesn't work that way.”Steve: That's right.Corey: And you have to put a lot of thought and planning into it. That is something that I've not heard a traditional networking vendor addressing because everyone loves to hand-wave over it.Steve: Well so, and this particular prospective investor, we told him, “We think we have to go build our own switch.” And he said, “Great.” And we said, “You know, we think we're going to lose you as an investor as a result, but this is what we're doing.” And he said, “If you're building your own switch, I want to invest.” And his comment really stuck with us, which is AWS did not stand on their own two feet until they threw out their proprietary switch vendor and built their own.And that really unlocked, like you've just mentioned, like, their ability, both in hardware and software to tune and optimize to deliver that kind of line rate capability. And that is one of the big findings for us as we got into it. Yes, it was really, really hard, but based on a couple of design decisions, P4 being the programming language that we are using as the surround for our silicon, tons of opportunities opened up for us to be able to do similar kinds of optimization and observability. And that has been a big, big win.But to your question of, like, where does it stop? So, we are delivering this complete with a baked-in operating system, hypervisor, control plane. And so, the endpoint of the system, where the customer meets is either hitting an API or a CLI or a console that delivers and kind of gives you the ability to spin up projects. And, you know, if one is familiar with EC2 and EBS and VPC, that VM level of abstraction is where we stop.Corey: That, I think, is a fair way of thinking about it. And a lot of cloud folks are going to pooh-pooh it as far as saying, “Oh well, just virtual machines. That's old cloud. That just treats the cloud like a data center.” And in many cases, yes, it does because there are ways to build modern architectures that are event-driven on top of things like Lambda, and API Gateway, and the rest, but you take a look at what my customers are doing and what drives the spend, it is invariably virtual machines that are largely persistent.Sometimes they scale up, sometimes they scale down, but there's always a baseline level of load that people like to hand-wave away the fact that what they're fundamentally doing in a lot of these cases, is paying the cloud provider to handle the care and feeding of those systems, which can be expensive, yes, but also delivers significant innovation beyond what almost any company is going to be able to deliver in-house. There is no way around it. AWS is better than you are—whoever you happen to—be at replacing failed hard drives. That is a simple fact. They have teams of people who are the best in the world of replacing failed hard drives. You generally do not. They are going to be better at that than you. But that's not the only axis. There's not one calculus that leads to, is cloud a scam or is cloud a great value proposition for us? The answer is always a deeply nuanced, “It depends.”Steve: Yeah, I mean, I think cloud is a great value proposition for most and a growing amount of software that's being developed and deployed and operated. And I think, you know, one of the myths that is out there is, hey, turn over your IT to AWS because we have or you know, a cloud provider—because we have such higher caliber personnel that are really good at swapping hard drives and dealing with networks and operationally keeping this thing running in a highly available manner that delivers good performance. That is certainly true, but a lot of the operational value in an AWS is been delivered via software, the automation, the observability, and not actual people putting hands on things. And it's an important point because that's been a big part of what we're building into the product. You know, just because you're running infrastructure in your own data center, it does not mean that you should have to spend, you know, 1000 hours a month across a big team to maintain and operate it. And so, part of that, kind of, cloud, hyperscaler innovation that we're baking into this product is so that it is easier to operate with much, much, much lower overhead in a highly available, resilient manner.Corey: So, I've worked in a number of data center facilities, but the companies I was working with, were always at a scale where these were co-locations, where they would, in some cases, rent out a rack or two, in other cases, they'd rent out a cage and fill it with their own racks. They didn't own the facilities themselves. Those were always handled by other companies. So, my question for you is, if I want to get a pile of Oxide racks into my environment in a data center, what has to change? What are the expectations?I mean, yes, there's obviously going to be power and requirements at the data center colocation is very conversant with, but Open Compute, for example, had very specific requirements—to my understanding—around things like the airflow construction of the environment that they're placed within. How prescriptive is what you've built, in terms of doing a building retrofit to start using you folks?Steve: Yeah, definitely not. And this was one of the tensions that we had to balance as we were designing the product. For all of the benefits of hyperscaler computing, some of the design center for you know, the kinds of racks that run in Google and Amazon and elsewhere are hyperscaler-focused, which is unlimited power, in some cases, data centers designed around the equipment itself. And where we were headed, which was basically making hyperscaler infrastructure available to, kind of, the masses, the rest of the market, these folks don't have unlimited power and they aren't going to go be able to go redesign data centers. And so no, the experience should be—with exceptions for folks maybe that have very, very limited access to power—that you roll this rack into your existing data center. It's on standard floor tile, that you give it power, and give it networking and go.And we've spent a lot of time thinking about how we can operate in the wide-ranging environmental characteristics that are commonplace in data centers that focus on themselves, colo facilities, and the like. So, that's really on us so that the customer is not having to go to much work at all to kind of prepare and be ready for it.Corey: One of the challenges I have is how to think about what you've done because you are rack-sized. But what that means is that my own experimentation at home recently with on-prem stuff for smart home stuff involves a bunch of Raspberries Pi and a [unintelligible 00:19:42], but I tend to more or less categorize you the same way that I do AWS Outposts, as well as mythical creatures, like unicorns or giraffes, where I don't believe that all these things actually exist because I haven't seen them. And in fact, to get them in my house, all four of those things would theoretically require a loading dock if they existed, and that's a hard thing to fake on a demo signup form, as it turns out. How vaporware is what you've built? Is this all on paper and you're telling amazing stories or do they exist in the wild?Steve: So, last time we were on, it was all vaporware. It was a couple of napkin drawings and a seed round of funding.Corey: I do recall you not using that description at the time, for what it's worth. Good job.Steve: [laugh]. Yeah, well, at least we were transparent where we were going through the race. We had some napkin drawings and we had some good ideas—we thought—and—Corey: You formalize those and that's called Microsoft PowerPoint.Steve: That's it. A hundred percent.Corey: The next generative AI play is take the scrunched-up, stained napkin drawing, take a picture of it, and convert it to a slide.Steve: Google Docs, you know, one of those. But no, it's got a lot of scars from the build and it is real. In fact, next week, we are going to be shipping our first commercial systems. So, we have got a line of racks out in our manufacturing facility in lovely Rochester, Minnesota. Fun fact: Rochester, Minnesota, is where the IBM AS/400s were built.Corey: I used to work in that market, of all things.Steve: Really?Corey: Selling tape drives in the AS/400. I mean, I still maintain there's no real mainframe migration to the cloud play because there's no AWS/400. A joke that tends to sail over an awful lot of people's heads because, you know, most people aren't as miserable in their career choices as I am.Steve: Okay, that reminds me. So, when we were originally pitching Oxide and we were fundraising, we [laugh]—in a particular investor meeting, they asked, you know, “What would be a good comp? Like how should we think about what you are doing?” And fortunately, we had about 20 investor meetings to go through, so burning one on this was probably okay, but we may have used the AS/400 as a comp, talking about how [laugh] mainframe systems did such a good job of building hardware and software together. And as you can imagine, there were some blank stares in that room.But you know, there are some good analogs to historically in the computing industry, when you know, the industry, the major players in the industry, were thinking about how to deliver holistic systems to support end customers. And, you know, we see this in the what Apple has done with the iPhone, and you're seeing this as a lot of stuff in the automotive industry is being pulled in-house. I was listening to a good podcast. Jim Farley from Ford was talking about how the automotive industry historically outsourced all of the software that controls cars, right? So, like, Bosch would write the software for the controls for your seats.And they had all these suppliers that were writing the software, and what it meant was that innovation was not possible because you'd have to go out to suppliers to get software changes for any little change you wanted to make. And in the computing industry, in the 80s, you saw this blow apart where, like, firmware got outsourced. In the IBM and the clones, kind of, race, everyone started outsourcing firmware and outsourcing software. Microsoft started taking over operating systems. And then VMware emerged and was doing a virtualization layer.And this, kind of, fragmented ecosystem is the landscape today that every single on-premises infrastructure operator has to struggle with. It's a kit car. And so, pulling it back together, designing things in a vertically integrated manner is what the hyperscalers have done. And so, you mentioned Outposts. And, like, it's a good example of—I mean, the most public cloud of public cloud companies created a way for folks to get their system on-prem.I mean, if you need anything to underscore the draw and the demand for cloud computing-like, infrastructure on-prem, just the fact that that emerged at all tells you that there is this big need. Because you've got, you know, I don't know, a trillion dollars worth of IT infrastructure out there and you have maybe 10% of it in the public cloud. And that's up from 5% when Jassy was on stage in '21, talking about 95% of stuff living outside of AWS, but there's going to be a giant market of customers that need to own and operate infrastructure. And again, things have not improved much in the last 10 or 20 years for them.Corey: They have taken a tone onstage about how, “Oh, those workloads that aren't in the cloud, yet, yeah, those people are legacy idiots.” And I don't buy that for a second because believe it or not—I know that this cuts against what people commonly believe in public—but company execs are generally not morons, and they make decisions with context and constraints that we don't see. Things are the way they are for a reason. And I promise that 90% of corporate IT workloads that still live on-prem are not being managed or run by people who've never heard of the cloud. There was a decision made when some other things were migrating of, do we move this thing to the cloud or don't we? And the answer at the time was no, we're going to keep this thing on-prem where it is now for a variety of reasons of varying validity. But I don't view that as a bug. I also, frankly, don't want to live in a world where all the computers are basically run by three different companies.Steve: You're spot on, which is, like, it does a total disservice to these smart and forward-thinking teams in every one of the Fortune 1000-plus companies who are taking the constraints that they have—and some of those constraints are not monetary or entirely workload-based. If you want to flip it around, we were talking to a large cloud SaaS company and their reason for wanting to extend it beyond the public cloud is because they want to improve latency for their e-commerce platform. And navigating their way through the complex layers of the networking stack at GCP to get to where the customer assets are that are in colo facilities, adds lag time on the platform that can cost them hundreds of millions of dollars. And so, we need to think behind this notion of, like, “Oh, well, the dark ages are for software that can't run in the cloud, and that's on-prem. And it's just a matter of time until everything moves to the cloud.”In the forward-thinking models of public cloud, it should be both. I mean, you should have a consistent experience, from a certain level of the stack down, everywhere. And then it's like, do I want to rent or do I want to own for this particular use case? In my vast set of infrastructure needs, do I want this to run in a data center that Amazon runs or do I want this to run in a facility that is close to this other provider of mine? And I think that's best for all. And then it's not this kind of false dichotomy of quality infrastructure or ownership.Corey: I find that there are also workloads where people will come to me and say, “Well, we don't think this is going to be economical in the cloud”—because again, I focus on AWS bills. That is the lens I view things through, and—“The AWS sales rep says it will be. What do you think?” And I look at what they're doing and especially if involves high volumes of data transfer, I laugh a good hearty laugh and say, “Yeah, keep that thing in the data center where it is right now. You will thank me for it later.”It's, “Well, can we run this in an economical way in AWS?” As long as you're okay with economical meaning six times what you're paying a year right now for the same thing, yeah, you can. I wouldn't recommend it. And the numbers sort of speak for themselves. But it's not just an economic play.There's also the story of, does this increase their capability? Does it let them move faster toward their business goals? And in a lot of cases, the answer is no, it doesn't. It's one of those business process things that has to exist for a variety of reasons. You don't get to reimagine it for funsies and even if you did, it doesn't advance the company in what they're trying to do any, so focus on something that differentiates as opposed to this thing that you're stuck on.Steve: That's right. And what we see today is, it is easy to be in that mindset of running things on-premises is kind of backwards-facing because the experience of it is today still very, very difficult. I mean, talking to folks and they're sharing with us that it takes a hundred days from the time all the different boxes land in their warehouse to actually having usable infrastructure that developers can use. And our goal and what we intend to go hit with Oxide as you can roll in this complete rack-level system, plug it in, within an hour, you have developers that are accessing cloud-like services out of the infrastructure. And that—God, countless stories of firmware bugs that would send all the fans in the data center nonlinear and soak up 100 kW of power.Corey: Oh, God. And the problems that you had with the out-of-band management systems. For a long time, I thought Drax stood for, “Dell, RMA Another Computer.” It was awful having to deal with those things. There was so much room for innovation in that space, which no one really grabbed onto.Steve: There was a really, really interesting talk at DEFCON that we just stumbled upon yesterday. The NVIDIA folks are giving a talk on BMC exploits… and like, a very, very serious BMC exploit. And again, it's what most people don't know is, like, first of all, the BMC, the Baseboard Management Controller, is like the brainstem of the computer. It has access to—it's a backdoor into all of your infrastructure. It's a computer inside a computer and it's got software and hardware that your server OEM didn't build and doesn't understand very well.And firmware is even worse because you know, firmware written by you know, an American Megatrends or other is a big blob of software that gets loaded into these systems that is very hard to audit and very hard to ascertain what's happening. And it's no surprise when, you know, back when we were running all the data centers at a cloud computing company, that you'd run into these issues, and you'd go to the server OEM and they'd kind of throw their hands up. Well, first they'd gaslight you and say, “We've never seen this problem before,” but when you thought you've root-caused something down to firmware, it was anyone's guess. And this is kind of the current condition today. And back to, like, the journey to get here, we kind of realized that you had to blow away that old extant firmware layer, and we rewrote our own firmware in Rust. Yes [laugh], I've done a lot in Rust.Corey: No, it was in Rust, but, on some level, that's what Nitro is, as best I can tell, on the AWS side. But it turns out that you don't tend to have the same resources as a one-and-a-quarter—at the moment—trillion-dollar company. That keeps [valuing 00:30:53]. At one point, they lost a comma and that was sad and broke all my logic for that and I haven't fixed it since. Unfortunate stuff.Steve: Totally. I think that was another, kind of, question early on from certainly a lot of investors was like, “Hey, how are you going to pull this off with a smaller team and there's a lot of surface area here?” Certainly a reasonable question. Definitely was hard. The one advantage—among others—is, when you are designing something kind of in a vertical holistic manner, those design integration points are narrowed down to just your equipment.And when someone's writing firmware, when AMI is writing firmware, they're trying to do it to cover hundreds and hundreds of components across dozens and dozens of vendors. And we have the advantage of having this, like, purpose-built system, kind of, end-to-end from the lowest level from first boot instruction, all the way up through the control plane and from rack to switch to server. That definitely helped narrow the scope.Corey: This episode has been fake sponsored by our friends at AWS with the following message: Graviton Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton, Graviton. Thank you for your l-, lack of support for this show. Now, AWS has been talking about Graviton an awful lot, which is their custom in-house ARM processor. Apple moved over to ARM and instead of talking about benchmarks they won't publish and marketing campaigns with words that don't mean anything, they've let the results speak for themselves. In time, I found that almost all of my workloads have moved over to ARM architecture for a variety of reason, and my laptop now gets 15 hours of battery life when all is said and done. You're building these things on top of x86. What is the deal there? I do not accept that if that you hadn't heard of ARM until just now because, as mentioned, Graviton, Graviton, Graviton.Steve: That's right. Well, so why x86, to start? And I say to start because we have just launched our first generation products. And our first-generation or second-generation products that we are now underway working on are going to be x86 as well. We've built this system on AMD Milan silicon; we are going to be launching a Genoa sled.But when you're thinking about what silicon to use, obviously, there's a bunch of parts that go into the decision. You're looking at the kind of applicability to workload, performance, power management, for sure, and if you carve up what you are trying to achieve, x86 is still a terrific fit for the broadest set of workloads that our customers are trying to solve for. And choosing which x86 architecture was certainly an easier choice, come 2019. At this point, AMD had made a bunch of improvements in performance and energy efficiency in the chip itself. We've looked at other architectures and I think as we are incorporating those in the future roadmap, it's just going to be a question of what are you trying to solve for.You mentioned power management, and that is kind of commonly been a, you know, low power systems is where folks have gone beyond x86. Is we're looking forward to hardware acceleration products and future products, we'll certainly look beyond x86, but x86 has a long, long road to go. It still is kind of the foundation for what, again, is a general-purpose cloud infrastructure for being able to slice and dice for a variety of workloads.Corey: True. I have to look around my environment and realize that Intel is not going anywhere. And that's not just an insult to their lack of progress on committed roadmaps that they consistently miss. But—Steve: [sigh].Corey: Enough on that particular topic because we want to keep this, you know, polite.Steve: Intel has definitely had some struggles for sure. They're very public ones, I think. We were really excited and continue to be very excited about their Tofino silicon line. And this came by way of the Barefoot networks acquisition. I don't know how much you had paid attention to Tofino, but what was really, really compelling about Tofino is the focus on both hardware and software and programmability.So, great chip. And P4 is the programming language that surrounds that. And we have gotten very, very deep on P4, and that is some of the best tech to come out of Intel lately. But from a core silicon perspective for the rack, we went with AMD. And again, that was a pretty straightforward decision at the time. And we're planning on having this anchored around AMD silicon for a while now.Corey: One last question I have before we wind up calling it an episode, it seems—at least as of this recording, it's still embargoed, but we're not releasing this until that winds up changing—you folks have just raised another round, which means that your napkin doodles have apparently drawn more folks in, and now that you're shipping, you're also not just bringing in customers, but also additional investor money. Tell me about that.Steve: Yes, we just completed our Series A. So, when we last spoke three years ago, we had just raised our seed and had raised $20 million at the time, and we had expected that it was going to take about that to be able to build the team and build the product and be able to get to market, and [unintelligible 00:36:14] tons of technical risk along the way. I mean, there was technical risk up and down the stack around this [De Novo 00:36:21] server design, this the switch design. And software is still the kind of disproportionate majority of what this product is, from hypervisor up through kind of control plane, the cloud services, et cetera. So—Corey: We just view it as software with a really, really confusing hardware dongle.Steve: [laugh]. Yeah. Yes.Corey: Super heavy. We're talking enterprise and government-grade here.Steve: That's right. There's a lot of software to write. And so, we had a bunch of milestones that as we got through them, one of the big ones was getting Milan silicon booting on our firmware. It was funny it was—this was the thing that clearly, like, the industry was most suspicious of, us doing our own firmware, and you could see it when we demonstrated booting this, like, a year-and-a-half ago, and AMD all of a sudden just lit up, from kind of arm's length to, like, “How can we help? This is amazing.” You know? And they could start to see the benefits of when you can tie low-level silicon intelligence up through a hypervisor there's just—Corey: No I love the existing firmware I have. Looks like it was written in 1984 and winds up having terrible user ergonomics that hasn't been updated at all, and every time something comes through, it's a 50/50 shot as whether it fries the box or not. Yeah. No, I want that.Steve: That's right. And you look at these hyperscale data centers, and it's like, no. I mean, you've got intelligence from that first boot instruction through a Root of Trust, up through the software of the hyperscaler, and up to the user level. And so, as we were going through and kind of knocking down each one of these layers of the stack, doing our own firmware, doing our own hardware Root of Trust, getting that all the way plumbed up into the hypervisor and the control plane, number one on the customer side, folks moved from, “This is really interesting. We need to figure out how we can bring cloud capabilities to our data centers. Talk to us when you have something,” to, “Okay. We actually”—back to the earlier question on vaporware, you know, it was great having customers out here to Emeryville where they can put their hands on the rack and they can, you know, put your hands on software, but being able to, like, look at real running software and that end cloud experience.And that led to getting our first couple of commercial contracts. So, we've got some great first customers, including a large department of the government, of the federal government, and a leading firm on Wall Street that we're going to be shipping systems to in a matter of weeks. And as you can imagine, along with that, that drew a bunch of renewed interest from the investor community. Certainly, a different climate today than it was back in 2019, but what was great to see is, you still have great investors that understand the importance of making bets in the hard tech space and in companies that are looking to reinvent certain industries. And so, we added—our existing investors all participated. We added a bunch of terrific new investors, both strategic and institutional.And you know, this capital is going to be super important now that we are headed into market and we are beginning to scale up the business and make sure that we have a long road to go. And of course, maybe as importantly, this was a real confidence boost for our customers. They're excited to see that Oxide is going to be around for a long time and that they can invest in this technology as an important part of their infrastructure strategy.Corey: I really want to thank you for taking the time to speak with me about, well, how far you've come in a few years. If people want to learn more and have the requisite loading dock, where should they go to find you?Steve: So, we try to put everything up on the site. So, oxidecomputer.com or oxide.computer. We also, if you remember, we did [On the Metal 00:40:07]. So, we had a Tales from the Hardware-Software Interface podcast that we did when we started. We have shifted that to Oxide and Friends, which the shift there is we're spending a little bit more time talking about the guts of what we built and why. So, if folks are interested in, like, why the heck did you build a switch and what does it look like to build a switch, we actually go to depth on that. And you know, what does bring-up on a new server motherboard look like? And it's got some episodes out there that might be worth checking out.Corey: We will definitely include a link to that in the [show notes 00:40:36]. Thank you so much for your time. I really appreciate it.Steve: Yeah, Corey. Thanks for having me on.Corey: Steve Tuck, CEO at Oxide Computer Company. I'm Cloud Economist Corey Quinn, and this is Screaming in the Cloud. If you've enjoyed this podcast, please leave a five-star review on your podcast platform of choice, whereas if you've hated this episode, please leave a five-star review on your podcast platform of choice, along with an angry ranting comment because you are in fact a zoology major, and you're telling me that some animals do in fact exist. But I'm pretty sure of the two of them, it's the unicorn.Corey: If your AWS bill keeps rising and your blood pressure is doing the same, then you need The Duckbill Group. We help companies fix their AWS bill by making it smaller and less horrifying. The Duckbill Group works for you, not AWS. We tailor recommendations to your business and we get to the point. Visit duckbillgroup.com to get started.

Bloomberg Intelligence Technology Analyst Woo Jin Ho hosts Open Compute Project (OCP) CEO George Tchaparian to discuss the current and future innovations introduced by the consortium. Since its inception in 2009, the consortium has grown to over 300 members and boasts $18 billion in OCP-recognized vendor revenues. We discuss OCPs latest projects, such as disaggregating motherboards and chips, bringing cloud technologies to telecom and enterprise users, and tackling climate change.

Ransom Cartel linked to REvil Do we need cybersecurity training for Gen Z? Open Compute Project announces Caliptra Thanks to this week's episode sponsor, SafeBase Security questionnaires. If those two words sent a shiver down your spine, you need to check out SafeBase. SafeBase's Smart Trust Center is a centralized source of truth for your organization's security and compliance information. After implementing SafeBase, many companies see a 90% reduction in custom questionnaires. Imagine how much time you'd save. Visit safebase.com to find out more.

In next week's episode of the Hewlett Packard Labs Podcast “From Research to Reality”, Dejan Milojicic hosts Jim Greener, Director of Silicon Design Lab in Hewlett Packard Labs. Jim takes us through history of Silicon Design and how the landscape changed from his early career days till today. Jim discusses a couple of successful projects and he hints at possible future of silicon design. We discuss how the whole industry, not only components, transformed through a disaggregation. On a personal side, Jim is the first interviewee who grew up, went to school and spent his whole career in one town. He explains the wonderful outdoor opportunities in and around Ft Collins, Colorado.

Guest Steve Helvie Panelists Eric Berry | Justin Dorfman | Richard Littauer Show Notes Hello and welcome to Sustain! The podcast where we talk about sustaining open source for the long haul. Our guest today is exceptional in many ways, so you don't want to miss this episode! On this episode, we have Steve Helvie, VP of Channel Development for the Open Compute Project (OCP). He helps to educate organizations on the benefits of open hardware designs and the value of “community-driven” engineering for the data center. Today, Steve tells us how the Open Compute Project started, how he got involved, how it generates revenue, what open hardware is, and the challenges he sees with open hardware. We also learn why Europe is always at the forefront of regulations when it comes to sustainability and designs. Download this episode now to find out much more! [00:00:39] Eric, Richard, and Justin tell us about their backgrounds since Steve was curious. [00:03:26] Steve tells us his background, what he does at Open Compute Project, and explains more about open hardware. [00:06:41] Steve mentions there are 200 projects in the Open Compute Project and Richard wonders what the minimum entry is, what you need to be one of these projects, and how much money is needed to think about having open hardware in his company. [00:12:04] Justin asks for Steve's insight on a supply chain attack when it comes to hardware and how does the OCP fix it. [00:14:56] Steve talks about sustainability with “save the earth and save money,” and how Europe is always at the forefront of regulations when it comes to sustainability and designs. [00:17:00] Steve had mentioned that he's invested in helping people have hardware and run hardware better for their own companies, and Richard sees this to be at ends with Cloud Native, so he asks Steve to talk about how he sees that conflict. [00:18:13] Richard wonders if Steve is helping to improve Uber's private cloud and partially the public cloud by allowing them to do work with OCP and with other managers, how has that not led towards a non-sustainable earth and how does he reckon with that conflict. [00:20:51] In talking about refreshing hardware, Justin tells us about a book he read called _Flash Boys. _He also tells us about how he talked to an ex-Googler when GCP was getting built, who told him that Google was importing thirty tons of hard drives every single day and asks Steve if this is a normal thing. [00:22:43] Richard wonders if a large amount of Steve's clients are Crypto. [00:23:37] Eric brings up Steve's background and wonders if he had an a-ha moment or was there a point in time where he thought this is bigger than just hardware. [00:26:00] Steve tells us besides memberships, how the OCP generates revenue. He talks about having to switch to virtual summits during COVID. The guys all chat about if they've seen memberships and activities increasing in the last year since going virtual. Steve shares a staggering number of virtual attendees at his recent event. [00:30:37] Richard wonders what challenges Steve sees for the entire field of open hardware. Steve mentions a great course he took on Open Source Technology Management that's worth checking out provided by Brandeis University. [00:35:29] Find out where you can follow Steve online. Quotes [00:08:02] “There is such a huge fear that someone's going to take my designs and copy them.” [00:08:28] “So, what big companies like, in any company really, is they like a dual sourcing strategy.” [00:08:40] “They like that one skew, give me consistency across the board that I can deploy in Asia, Europe, or America, but give me multiple suppliers that mitigates my supply chain risk.” [00:10:48] “The types of companies that are looking at Open Compute are companies that have an open source mindset, they have a Cloud Native mindset where software is going to define everything.” [00:11:26] “And that's the point of when that happens in industries you start to see this customer poll. It's happening now in Telcos. Fintech gets it, gaming gets it, traditional banking, traditional healthcare, insurance companies do not get it yet, but they will. It's going to come.” [00:14:32] “So, there's this second user economy or what we call circular economy that's happening now within what Google, Microsoft, Facebook, all the Hyperscalers now have a second use plan because they need to for sustainability.” [00:15:03] “What's happening in Europe is you have Europe is always at the forefront of regulations when it comes to sustainability and designs.” [00:15:21] “There are heat reuse out of data center initiatives. For example, the Netherlands, you cannot build a new data center in the Netherlands unless you have a heat reuse.” [00:19:11] “So, the only part that I can see that's redeeming about this fact is that OCP designs use a lot less energy between 30-50% less energy than a normal standard server.” [00:19:53] “We have large enterprises that are taking the hardware coming out of these Hyperscale Data Centers that oftentimes is less than three years old.” [00:20:02] “A lot of these Hyperscalers don't even keep their hardware for more than three years and they're out if it. That still has a lot of life for if I'm a small and medium sized business in anywhere else in the world, they can still use that hardware for five years.” [00:34:28] “Open software, you can crank through it, iterations, sprints. Open hardware, it's very dependent on chip cycles, product cycles, and yeah, it's a lot of hurry up and wait in hardware.” Spotlight [00:36:32] Eric's spotlight is Gitpod. [00:38:30] Justin's spotlights are Episodes 1-16 of Sustain the podcast are back home and Orbit. [00:38:59] Richard's spotlight is Strange Parts. [00:39:21] Steve's spotlight is Jason Mauck and his podcast called Mauck Me. Links Steve Helvie Twitter (https://twitter.com/stevehelvie) Steve Helvie Linkedin (https://www.linkedin.com/in/steve-helvie-37935712) Steve@opencompute.org (mailto:steve@opencompute.org) Open Compute Project (https://www.opencompute.org/) Open Compute Project Membership Tiers (https://www.opencompute.org/membership) Open Compute Project Open System Firmware (https://www.opencompute.org/projects/open-system-firmware) Flash Boys: A Wall Street Revolt by Michael Lewis (https://www.amazon.com/Flash-Boys-Wall-Street-Revolt/dp/0393351599) Committing To Cloud Native podcast-Google Cloud, Hay-doop, Mars Rover, AWS and more with Miles Ward of SADA-Episode 3 (https://podcast.curiefense.io/3) Brandeis University-Certificate in Open Source Technology Management micro courses (https://www.brandeis.edu/gps/professional-development/micro-courses/ostm/index.html) Sustain podcast-What OpenUK Does with Amanda Brock and Andrew Katz-Episode 49 (https://podcast.sustainoss.org/49) Gitpod (https://www.gitpod.io/) Sustain podcast-Episodes 1-5 (https://podcast.sustainoss.org/page/7) Sustain podcast-Episodes 6-16 (https://podcast.sustainoss.org/page/6) Orbit (https://orbit.love/) Strange Parts (https://strangeparts.com/) Jason Mauck Twitter (https://twitter.com/jasonmauck1?ref_src=twsrc%5Egoogle%7Ctwcamp%5Eserp%7Ctwgr%5Eauthor) Mauck Me podcast (https://mauckme.podbean.com/) Credits Produced by Richard Littauer (https://www.burntfen.com/) Edited by Paul M. Bahr at Peachtree Sound (https://www.peachtreesound.com/) Show notes by DeAnn Bahr at Peachtree Sound (https://www.peachtreesound.com/) Special Guest: Steve Helvie.

Check out our latest Podcast with Archna Haylock and Donald Mitchell about the Open Compute Project FoundationFrom PUE, Sustainability, Liquid Cooling to... Thread Standards... we covered it all!

Today's Network Break podcast discusses the growth of the infrastructure market based on Open Compute specs, the decline in switch and routing revenues, Cisco postponing its 2020 Cisco Live virtual event, VMware's latest acquisition, and more tech news.

Today's Network Break podcast discusses the growth of the infrastructure market based on Open Compute specs, the decline in switch and routing revenues, Cisco postponing its 2020 Cisco Live virtual event, VMware's latest acquisition, and more tech news.

Today's Network Break podcast discusses the growth of the infrastructure market based on Open Compute specs, the decline in switch and routing revenues, Cisco postponing its 2020 Cisco Live virtual event, VMware's latest acquisition, and more tech news.

Today's Network Break podcast discusses the growth of the infrastructure market based on Open Compute specs, the decline in switch and routing revenues, Cisco postponing its 2020 Cisco Live virtual event, VMware's latest acquisition, and more tech news. The post Network Break 287: Open Compute Infrastructure Makes Its Mark; Cisco Live Postponed appeared first on Packet Pushers.

Today's Network Break podcast discusses the growth of the infrastructure market based on Open Compute specs, the decline in switch and routing revenues, Cisco postponing its 2020 Cisco Live virtual event, VMware's latest acquisition, and more tech news. The post Network Break 287: Open Compute Infrastructure Makes Its Mark; Cisco Live Postponed appeared first on Packet Pushers.

Today's Network Break podcast discusses the growth of the infrastructure market based on Open Compute specs, the decline in switch and routing revenues, Cisco postponing its 2020 Cisco Live virtual event, VMware's latest acquisition, and more tech news. The post Network Break 287: Open Compute Infrastructure Makes Its Mark; Cisco Live Postponed appeared first on Packet Pushers.

Bill Carter, the CTO of the Open Compute Project joins us to discuss a new way of building a rack for a data center. The OCP uses a tool-less, modern, efficient design and best of all - the plans are open and available!

Bill Carter, the CTO of the Open Compute Project joins us to discuss a new way of building a rack for a data center. The OCP uses a tool-less, modern, efficient design and best of all - the plans are open and available!

The Open Compute Project with Bill Carter Bill Carter, the CTO of the Open Compute Project joins us to discuss a new way of building a rack for a data center. The OCP uses a tool-less, modern, efficient design and best of all - the plans are open and available! -- The Extra Credit Section -- For links to the articles and material referenced in this week's episode check out this week's page from our podcast dashboard! This Episode's Podcast Dashboard (http://podcast.asknoahshow.com/180) Phone Systems for Ask Noah provided by Voxtelesys (http://www.voxtelesys.com/asknoah) Join us in our dedicated chatroom #AskNoahShow on Freenode! -- Stay In Touch -- Find all the resources for this show on the Ask Noah Dashboard Ask Noah Dashboard (http://www.asknoahshow.com) Need more help than a radio show can offer? Altispeed provides commercial IT services and they’re excited to offer you a great deal for listening to the Ask Noah Show. Call today and ask about the discount for listeners of the Ask Noah Show! Altispeed Technologies (http://www.altispeed.com/) Contact Noah live [at] asknoahshow.com -- Twitter -- Noah - Kernellinux (https://twitter.com/kernellinux) Ask Noah Show (https://twitter.com/asknoahshow) Altispeed Technologies (https://twitter.com/altispeed)

Automation and open networking, a journey in time, challenges and possibilities with our expert on the subject, Tore Anderson. A comprehensive talk about the development of automation of servers and networks. Where servers today are highly automated with lots of administration tools like Puppet, Chef, Ansible, Salt, and so on. With networks it is a different story, where progress has not been as fast and where devices traditionally have been proprietary. However, with projects like “Open Compute” and white box switches things have started to happen.

Steve Helvie (steve@opencompute.org) is the VP of Channel for the Open Compute Project (OCP). In this role he helps to educate organisations on the benefits of open hardware designs and the value of “community-driven” engineering for the data centre. In this podcast we discuss how Open Sourcing hardware is helping innovation and creation of more […]

Steve Helvie is the VP of Channel for the Open Compute Project (OCP). In this role he helps to educate organisations on the benefits of open hardware designs and the value of “community-driven” engineering for the data centre. In this podcast we discuss how Open Sourcing hardware is helping innovation and creation of more efficient and better data centers.

Subscribe to Kernel of Truth on iTunes, Google Play, Spotify, Cast Box and Sticher! Click here for our previous episode. Early March is a busy time here at Cumulus Networks and part of the reason is the Open Compute Project Summit. Kernel of Truth hosts Brian O’Sullivan and Roopa Prabhu are joined by Scott Emery, project lead at … Continue reading Open Compute Project Summit 2020 →

Chuck's Python course: (Discounted at $10): https://bit.ly/2lsDZeo Chuck's SDN book: https://amzn.to/2lCp6WN Chuck's SDN Startup: http://www.tallac.com Connect with Chuck on LinkedIn here: https://www.linkedin.com/in/chuck-black-1017676/ Connect with David on LinkedIn here: https://www.linkedin.com/in/davidbombal/ In these series of videos David Bombal, CCIE and Chuck Black, Developer discuss the future of networking. SDN, Network automation, network programmability, APIs, NETCONF, REST APIs and lots of other technologies! What is Whitebox / Bare Metal switching? Open Compute Project? OpenStack? Cumulus Linux: https://cumulusnetworks.com/products/cumulus-linux/ Open Compute Project: https://www.opencompute.org/ Open vSwitch: http://www.openvswitch.org/ OpenStack: https://www.openstack.org/ Learn from someone who wrote SDN code. Who wrote SDN books. Who understands how SDN code actually works. David's details: YouTube: www.youtube.com/davidbombal Twitter: twitter.com/davidbombal Instagram: www.instagram.com/davidbombal/ LinkedinIn: www.linkedin.com/in/davidbombal/ #Whitebox #Bare_Metail_Switching #Whitebox_Switching

This week Matt & Steve talk through some of what they learned at recent industry events, including the moves that NVIDIA is making into the data center, some discussion of containers in the enterprise, a brief wrap-up from Nutanix's investor conference in New York, some light-thinking following Matt's first missed Open Compute Summit in a decade, and a bit of non-political discussion on Huawei. If you follow Data Center technology, as well as the players behind the what's happening, you'll be in good company with Matt KImball and Steve McDowell from Moor Insights & Strategy and the DataCentric Podcast. Timeline 00:30 - 08:00 NVIDIA GTC Wrap-Up: NVIDIA heads into the Enterprise 08:00 - 11:00 Impact of Containers on Data Center management frameworks 11:00 - 21:20 Nutanix Investor Day Wrap-Up: NTNX takes aim 21:20 - 30:00 Open Compute Summit: Why it still matters. 30:00 - 42:30 Huawei: A Serious Player, despite all the geopolitical noise around the company 42:30 - 44:44 Senseless Banter

Om Shownotes ser konstiga ut så finns de på webben här också: https://www.enlitenpoddomint.se/e/en-liten-podd-om-it-avsnitt-206  Detta är avsnitt 205 och spelades in den 10 mars, och eftersom gifta män lämnar mer dricks än singel-män (enligt den här boken) så handlar dagens avsnitt om:   FEEDBACK OCH BACKLOG * Mats är "lyckligare" än vanligt, David är lika "glad" han, Björn jobbar som vanligt på sälj, och Johan har inte haft nån VAB den här veckan. * Microsoft förnekar samarbete med app som spårar muslimer * Facebook har tagit bort 1,5 miljoner filmkopior på massakern i Nya Zealand    * BONUSLÄNK: facebook beskriver hur man vill stoppa ”revenge porn”    * BONUSLÄNK: JÄTTEÅNG artikel om facebook tänkt att det ska gå till    * BONUSLÄNK: en tidigare facebookanställd beskriver hur det är att jobba med att gå igenom anmälda postningar * Det finns gamla buggar i WinRAR. Se till att uppdatera     * BONUSLÄNK: Exempel på applikation som kan användas för patchning. (OBS: vi är INTE sponsrade eller liknande)      MICROSOFT: * Fundering: Är det så att Microsofts framtid är Företag och gaming (privatpersonmarknaden är liksom inte en av dem) * Open Compute project. Nått att bry sig om som vanlig dödlig? Microsoft verkar bry sig rätt mycket  * Man kan specialisera sig på allt!! Åka på konferens i San jose söndag 17/3 - tors 21/3 * Win10 19H1 är väl typ klar nu?  Vattenmärket är borta.        * BONUSLÄNK: en SUPERlång lista över nyheter * 800 Miljoner windows 10 datorer…    * BONUSLÄNK: Global marketshare for windows 7    * BONUSLÄNK: Shipments of chormebooks 2014-2023    * BONUSLÄNK: Global Apple Mac Sales 2002-2018    * BONUSLÄNK: fördelning i marknadsandel mellan olika Operativsystem     APPLE: * En större Ipad? Måste jag bry mig?     * BONUSLÄNK: Apple kommer att ha ett event i slutet av månaden  * Nice ny TV från LG (med homekit) * Spotify anmäler Apple   GOOGLE: * Antivirus på telefoner är bra… Fast bara om du valt rätt Antivirus    * BONUSLÄNK: Själva testet: https://www.av-comparatives.org/tests/android-test-2019-250-apps/   * Android Q får grejer kring privacy   * Nice för oss iPhone-människor! Google tangentbordet på iOS får stöd för google translate       TIPS: * Where in the world are Carmen Sandiego * Low Tech Magazine     PRYLLISTA: * David: https://www.sfbok.se/produkt/illuminati-2nd-edition-184099 * Björn: Speldator till sonen * Mats:  Pixel C! * Johan: https://www.engadget.com/2019/03/15/electric-mustang-teaser/     SAKER VI INTE TOG UPP: * https://www.theverge.com/2019/3/15/18266998/microsoft-skype-group-video-calls-50-participants * WWDC blir i San Jose den 3-7 juni: https://developer.apple.com/wwdc19/      EGNA LÄNKAR: * En Liten Podd Om IT på webben * En Liten Podd Om IT på Facebook     LÄNKAR TILL VART MAN HITTAR PODDEN FÖR ATT LYSSNA: * Apple Podcaster (iTunes) * Overcast * Acast * Spotify * Stitcher

Facebook was rapidly outgrowing its infrastructure in 2009. Classic data center design was not up to the task of the rapid influx of new users and data, photos and streaming video hitting Facebook’s servers. A small team of engineers spent the next two years designing a data center from the ground up to be cheaper, The post Open Compute Project with Steve Helvie appeared first on Software Engineering Daily.

CPNews Le D-Wave passe la seconde, mais manque d’interconnections… Et IBM prépare son ordinateur quantique polyvalent à 50 qbits. PowerVR annonce sa nouvelle génération de GPU : Furian. Xiaomi aussi lance sa puce maison : le S1. Préserver les interconnections avec du graphène, une solution d’avenir ? Enfin un CPU qui résiste aux charmes de Vénus... Un tic tock Emile ? Intel fait n’importe quoi lance un Xeon à 8898$. 24 coeurs, mais quand même ! Process - Architecture - Optimization - Snooze ? Après un Kaby Lake inutile sur desktop : les Core 8xxx seront toujours en 14nm... Le retour d’AMD : les Ryzen font très mal dans les PC… Et dans les serveurs aussi ! Un CPU ARM dans les Macbook, le début de la fin pour Intel ? Microsoft lance son projet Open Compute "Olympus" avec Intel / AMD / ARM inside... Sac à puces : le Dossier SoC Des bit slices aux "systems on chip" : 40 ans d’intégration. Les grandes familles CPU : ARM, x86, MIPS (Si si !), PowerPC, etc. Les concepteurs de puces : ARM, Apple, Intel, AMD, PowerVR, Freescale, NVIDIA, Samsung, Mediatek… Les vendeurs d’appareils : Apple, Sony, Samsung, Xiaomi, HP, Dell, Nintendo, Microsoft, etc... Les implémentations des concepteurs : Cortex, Denver, Moongoose, Kryo, Twister, Atom, Core, Jaguar, Ryzen, et les autres… Les grande familles GPU : Geforce, Radeon, Adreno, Mali, Intel GT, PowerVR… Les autres composants : DSP (Hexagon…), codec video (quicksync), puces sonores, contrôleurs mémoire / USB / Ethernet / Modem... Les bus internes... Les fondeurs : Intel, Glofo (a inclus IBM semi récemment), TSMC, Samsung, STMicro, NXP, Texas Instruments… Les Légo Systèmes sur puces qui vont dans les produits finis : Apple A7, Exynos 8xxx, Core i3 - XXXX, Atom truc, AMD A10-XXX, Snapdragon 835, Tegra X1, etc. SoCking : pleins d’exemples dans un GROS TABLEAU Produit Marque SoC Famille Architecture GPU Process Fondeur Iphone 6 Apple A9 ARMv8 Apple Twister Imagination PowerVR 16nm TSMC G5 LG Snapdragon 820 ARMv8 Qualcomm Kryo Adreno 530 14nm Samsung Galaxy S7 Samsung Exynos 8890 ARMv8 Samsung M1 (Mongoonse) ARM Mali T760 14nm Samsung Mate 8 Huawei Hisilicon Kirin 950 ARMv8 ARM Cortex A72 ARM Mali T880 16nm TSMC Surface Pro 4 Microsoft Core i5-6300U Intel Intel Core (« Skylake ») Intel HD520 14nm Intel Surface 3 Microsoft Atom X7 Intel Intel Atom « Cherry Trail » Intel HD 14nm Intel Transformer T100 Asus Atom Z3740 Intel Intel Atom « Bay Trail » Intel 22nm Intel Switch Nintendo NVIDIA Tegra X1 ARMv8 ARM Cortex A57 NVIDIA Geforce 20nm TSMC ? Wii U Nintendo Espresso PowerPC IBM PowerPC AMD Radeon (« Latte ») 45nm IBM Xbox 360 Microsoft Xenon PowerPC IBM PowerPC Xenos(Radeon X1900) 90 puis 65nm IBM puis Chartered PS3 Sony Cell PowerPC Cell NVIDIA RSX 90,65 et 45nm IBM PS Vita Sony CXD5315GG ARM ARM Cortex A9 Imagination PowerVR ?? Samsung ? PS4 Sony CXD90026G Intel AMD Jaguar AMD Radeon 28nm Glofo Xbox One Microsoft X887732 Intel AMD Jaguar AMD Radeon 28nm Glofo NES Mini Nintendo Allwinner R16 ARM ARM Cortex A7 ARM Mali 400 28nm ? ? Raspberry Pi 3 Raspberry Broadcom BCM2837 ARMv8 ARM Cortex A53 Broadcom VideoCore IV 40nm ? Sony 3DS Nintendo Nintendo 10480H ARM ARM11 DMP PICA200 45nm ?? Aura HD (liseuse) Kobo Freescale iMX507 ARM ARM Cortex A8 N/A ?? NXP SmartWatch 3 Sony Snapdragon 400 ARM ARM Cortex A7 Adreno 305 28nm TSMC Chromecast 2 Google Marvell Armada 1500 ARM ARM Cortex A7 ?? ?? ?? R7000 (routeur) Netgear BCM4709A0 (Broadcom) ARMv7 ARM Cortex A9 N/A 40nm ?? ES8000 (TV) Samsung Samsung Echo-P ARMv7 ARM Cortex A9 ARM Mali 400 ??? Samsung Mindstorm (jeux Lego) Lego EV3 ARM ARM9 N/A ?? ?? Drone Bebop 2 Parrot Parrot P7 ARM ARM Cortex A9 ARM Mali 400 ??? ??? Pepper Robot (1.6) Aldebaran Robotics Atom E3845 Intel Intel Atom Intel HD 22nm Intel Le Moment de zapper Math ! Comment une machine calcule-t-elle une racine carré ? Ca arrive même au meilleur : le bug du pentium…

Power Systems Design, Information to Power Your Designs

The Packet Pushers catch up on the latest developments from the Open Compute Project on networking, including new efforts that target the campus and WLANs, with guest Carlos Cardenas. The post PQ Show 94: The State Of Open Compute Networking appeared first on Packet Pushers.

The Packet Pushers catch up on the latest developments from the Open Compute Project on networking, including new efforts that target the campus and WLANs, with guest Carlos Cardenas. The post PQ Show 94: The State Of Open Compute Networking appeared first on Packet Pushers.

The Packet Pushers catch up on the latest developments from the Open Compute Project on networking, including new efforts that target the campus and WLANs, with guest Carlos Cardenas. The post PQ Show 94: The State Of Open Compute Networking appeared first on Packet Pushers.

On this episode of HetNet Happenings, host Sean Kinney, the managing editor for RCR Wireless News, takes a look at how the Open Compute Project is fostering innovation in the telecom industry with the adoption of white box servers and other hyperscale data center practices.

Aaron talks to Cole Crawford (CEO/Founder of Vapor.io, Founding executive director of Open Compute project and Co-founder of OpenStack) about momentum for Open Compute, rethinking how Data Center racks are designed, and the Vapor.io stack - OpenMist OS, Open DCRE and CORE. Interested in the O'Reilly OSCON? Want to register for OSCON now? Use promo code 20CLOUD for 20% off Details to win an OSCON pass coming soon! Check out the OSCON Schedule Free eBook from O'Reilly Media for Cloudcast Listeners! Check out an excerpt from the upcoming Docker Cookbook Links from the show: Vapor Homepage - http://www.vapor.io/ Topic 1 - Tell us about your background. It’s very extensive in both open source (software) and open hardware. Topic 2 - The company is described as “the first hyper converged and truly data defined data center solution”. Please translate that for us :) Topic 3 - For a small company, you have some large (conceptual) offerings - common hardware, rack-level provisioning, and this unique new rack model. Just how ambitious are you guys? (hardware with API’s!) Topic 4 - OpenMist OS (just launched). Let’s talk about each of the core pieces - Open DCRE (Data Center Runtime Environment). Is this an open BMC (Board Management Controller)? Topic 5 - Vapor CORE - This seems like RAID (Storage) meets BGP / HSRP (Networking) and compute scheduling (vCenter) all mashed together, with APIs to higher-level services (eg. Mesosphere or Docker) Topic 6 - Vapor Chamber - at first glance, this seems like The Big Green Egg (grill) for data center equipment. Fair analogy? Music Credit: Nine Inch Nails (nin.com)

Raejeanne Skillern, General Manager of the Cloud Service Provider Organization within the Data Center Group at Intel explains Intel’s involvement in the Open Compute Project and the technologies Intel will be highlighting at the 2015 Open Compute Summit in San Jose California. She discusses the launch of the new Intel® Xeon® Processor D-1500 Product Family, as well as how Intel will be demoing Rack Scale Architecture and other solutions at the Summit that are aligned with OCP specifications.

Intelligent Storage: Learn about modularized, high-availability and high density storage servers built by Wiwynn with 30 individually hot pluggable SAS/SATA HDDs built with Intel Atom processor C2000 product family