Unlike the old rack mount options for the trashcan Mac Pro units (eg https://photos.imgix.com/racking-mac-pros), it doesn't seem like much thought has been given here to a front-to-back airflow.
I'm also surprised they're touting the density of this solution— seems like the obvious thing would be to put the Minis on their sides. A 4U chassis has 17.5cm vertical space in it, and a Mac Mini is 17cm wide. With the Mini being 2in in height, that suggests 8-9 Minis in a 4U rack, vs 2 Minis in a 2U rack for Scaleway's trays.
EDIT: Here's a commercially-available solution that's 6/4U: https://www.mk1manufacturing.com/Rack-Mount-for-6-M4-mac-min..., you'd think it could basically be this but with the management plane behind or in front. And as others have said, making the management plane be more shared, so it's not 1:1.
Yeah sorry for mixing units like that. I think of it as a 19" rack and know that refers to the width, but I had to look up the height of a 4U chassis and Google told it to me in cm, so then I went with that for that dimension.
Totally fine, my brain just isn't used to processing imperial measurements in the same sentence as metric, so I thought the conversion might help others in the same place!
Sounds like 2 per 1U to me. I think it's power efficiency that limits filling a rack with typical 1U servers in most plans. The power efficiency here is probably not really impressive enough given so many power units, etc.
Yeah I'm a bit confused on that. In the picture, each row is definitely taller than the power strip, plus 1U is 44.45mm in height, whereas the current-gen Mac Mini is 50mm high.
I'm pretty sure the drawers are 2U, but given that I don't know how they would get 96 nodes in a standard 42U rack.
Yep! I would have thought about doing a 3d printed "tray" that goes under the mini and routes front/cold and back/hot air to the exterior of the rack...
I was interested in provisioning one of these a few months back through Scaleway, but couldn't navigate their sign-up process without it dumping me back to the start everytime. Nor did I receive a reply when I e-mailed their support e-mail.
I don't know if that's changed (they had odd pricing too, like Startup vs. Business, of which the difference wasn't clear), but aware. I hope someone has more success than I did.
Grim environment in the rodeo. The /home/directory, which the Rasberry-Pi doesn't align or distill as a symbolic markup language in .async or transport layer protocol and refers to /dev/ spinlock rolling release kernel version recursion or discursiveness.
Scaleway's site and support is horrible, as you've found. But their pricing and offerings are solid and their network is... OK. For the price, they're better than Hetzner... if you can get signed up!
Totally different experience here! For a project I wanted to try “euro cloud”. Something comparable to digital ocean. No need for hyperscaler functionality.
It has been great. Good terraform provider and reliable service. I like their console, although the design feel very vaporwave to me.
Of course stuff can be better, but it is rapidly improving. The way they implemented grafana + user management was shit. But that’s fixed. Grafana still feels bolted on however. And login is a bit weird with their dedibox or whatever button next to the cloud offering. But no where near as confusing as aws is!
Also bumped on a bug in their terraform provider, found a related bug report, contributed some info and it was fixed within two weeks.
Quite happy so far. Running serverless sql, serverless containers. Secrets management and some iam config. No big stuff but quite sure it is capable to run a decently sized saas.
I won't comment on the reliability of their services, as I've not experienced it. I was signing up specifically to provision a M1 mac mini, and couldn't navigate it. It was unfortunate, but worth a comment, in case others experience the same issue (or someone else could point me in the right direction).
Continuing to act like these ugly hacks are a normal way of doing business, is a continual signal to Apple that they don't need to build a rack-mount PC or server ever again.
If their developer community grew a pair and made themselves heard, then maybe the billion dollar company would do their effing job and provide a proper rackable development platform.
Which they had many years ago, before they morphed into a company that builds telephones and furniture that occasionally functions as a computer.
Instead we pretend like extension cords and gluing Raspberry Pi's together is totally ok for professional purposes.
I get it, you did what you had to do, but you're not the only example.
They have the knowledge and it's existed in the past (Xserve) but they will never do it again because they design and sell furniture now.
Tell me they couldn't design a Mac Mini with holes for rack ears, built in BMC or serial console.... even if it was a specialty product people would pay a premium
I totally agree on your comment by the way, it's not ideal at all, I'm not even working on the project anymore, every update, every feature is always a pain as we had to do reverse engineering.
Everything on this project is "hackie", it is not a solution for the future, the day Apple will change their license or break retro compatibility, the project will have no chance to survive.
So yes, the mac mini is absolutely not designed to be placed in a DC, a special product for that purpose would be better.
So it's a risky bet from a technical point of view.
> Continuing to act like these ugly hacks are a normal way of doing business, is a continual signal to Apple that they don't need to build a rack-mount PC or server ever again.
They technically still have the Rack Mac Pro, but that's such a half-assed offering that it's easy to forget it exists. It's a huge 5U chassis but if you look at the internals it's comical how little of the space is actually used for anything, because they kept the same layout as the Intel version which was designed to host multiple high-power GPUs, but dropped dGPU support in the Apple Silicon transition.
not sure why the attach rpi for every mac mini, wouldn't it be cheaper to have one rpi and 9 mac minis connectd to 10 port switch? I also wished one day to make cluster out of Apple TVs - they are very cheap (~150usd for version with ethernet) and most likely the new upcoming version will have more powerful A-series apple sillicon. I guess tvOS is just very restricted.
They’re connected to a single USB-C cable. For many technical reasons you can’t have a simple kvm which switches inputs. You’ll need to continuously power all 9 minis some way.
All nine USB-C cables will need a continuous, active connection.
To do this, you will need a smart controller that switches which port it’s talking to.
Or you can stick a relatively cheap device on every mini and and connect it to the network.
Having a “controller” for every mini means you can swap single units in both hardware and software very easily. There’s a one-to-one relationship and you don’t have to deal with pairing.
Just spitballing here, but if your interface to these things is USB-C, you should be able to boot them off an image that has a standard SSH key and then you can get in and ID them from a serial number or MAC address. I don't see the identification part as being a huge part of what's gained with the 1:1 configuration.
Is video forwarding part of the product offering, or simply considered required for management functions?
Either way, I probably agree that a raspi per unit probably makes sense at a scale of a few dozen racks, but it would be interesting to do the math on when it would be price-efficient to have a 1:n management node scheme. I don't imagine there are many USB-C hubs that support being display sinks on the downstream ports (if that's even possible at all) but perhaps you could use an FPGA to synthesize a small ARM core with a bunch of native USB-C interfaces capable of doing it?
> not sure why the attach rpi for every mac mini, wouldn't it be cheaper to have one rpi and 9 mac minis connectd to 10 port switch?
Simple... they're (likely) running something on the Raspberry Pi's that sets them up as USB gadgets, aka the Mac Mini "sees" a virtual keyboard and mouse. That's enough to manage remote provisioning.
To replicate that they'd need a KVM switch which doesn't have some weird edge case in how exactly it does USB-C switching, and it needs to be remotely controlled. A Pi is cheaper plus the failure modes of a Pi are more understood than the failure mode of some weird ass KVM switch someone cobbled together in China.
Simpler design... let alone constraints of the USB and/or other interfaces in use. Not to mention 1:1 of management port access to system access, where other solutions may be problematic.
Scaleway has some of the best prices for cloud Mac Minis and has better deals than the scam that is AWS's overpriced cloud Mac Minis.
Going with AWS for cloud Mac Minis is the quickest way to lose a lot of money if you don't know what to do with it and to flush as much cash down the drain as quickly as possible.
Fans generally are used to move cold air from in front of a rack behind the rack. There appear to be no fans at all here except those in the mini,which would cause the problem you discuss. I’m talking about supplemental cooling with a high volume low noise fan in a 2 or 3u enclosure.
It might be that they're limited by something else in their existing racks; say power or networking ports, so this is an easy hack to get into their existing rack scheme.
Aluminium designed in as heat sink perhaps? But not sure if this is so relevant in an actively cooled DC setting as passive buried under cables at a home workspace!
We were a little team, doing the API dev, the infra, the hardware and countless things.
The product is improving and it was impossible to even imagine remoing the case as we spent so many time wiring everything, going to DC and setting up everything.
Yes the team is actually doing all of this, even going to DC installing the macs in the racks.
But I agree that for a big scale, this is a good solution. (cf: github)
Agree, removing the case is a lot of effort. Github does a lot of fancy things but you might want to consider how much they're charging by the minute as well
Our way is quite efficient & we're able to quickly adapt to new HW gens
Hah so, I have a couple of old Mac Minis in my homelab that I use very occassionally but would like to access over the Internet (say, via Tailscale etc.) Ideally they'd be sleeping most of the time to conserve power, and only be kicked awake when needed, e.g. by a Wake-on-Lan packet.
Unfortunately I would need another device active at all times to listen for commands and send that packet on demand. I was toying with the idea of using a Raspberry Pi connected to the router to perform that specific function, but I never got around to it.
Funny to see that idea scaled up to a server rack!
My experience with a mac mini in a small R&D team has been a nightmare : the OS sucks so much for anything that is not a single user (at a time) on the machine, coming from the Systemd/Linux world
Yes, the experience is pretty bad, we were doing baremetal, so I assume there were only a single user on it.
The tooling and its documentation was really bad too, actually we based ourselves on the asahi project and its documentation and some open-source project that did a lot of work on reverse engineering all of the system we used.
From a user based perspective, using the remote desktop feature was a pain and I don't think any of our users were actually using it, the main use was : CI, AI training and bitcoin mining.
Good to see you :), there a lot of good questions ! I'm not working on the project anymore so you'll be able to reply with better answer.
But still had a really good experience with you guys.
Yeah, I was hoping for more detail as well. I'm guessing they did something similar to what I did to make my Pi control computers.[0]
The Raspberry Pi 4 can emulate a USB keyboard and mouse, and there are inexpensive adapters that allow it to capture display output. You can also hook it up to a relay to cycle power for an external device.
As others have pointed out, keyboard / mouse emulation is pretty useful, but it's also quite quirky.
We use MDM to automate configuration delivery as much as possible, I think it's been mentioned as well (although we're not zero touch yet).
You might want to look at Asahi Linux's Central Scrutinizer for some insights on the fancier stuff that can be done over the USB-C port.
You'd think that from an environmental point of view, Apple would be able to sell packs of Mac Mini boards without the case and packaging for people doing this; with no physical board or electronic change, it would be easy.
It’s madness that Apple can dictate that you have to sell it for at least 24h, not less. Ideally the manufacturer shouldn’t dictate how the property is being rented.
> The compact size of the Mac mini, which packs a powerful System on a Chip (SoC) into a tiny footprint.The energy efficiency of Apple silicon (M-series) chips, which allows high density without overheating or excessive power draw.
This really adds nothing to the article, and looks like AI fluff to me.
Combine that with there being a bold section in like every single paragraph, I'm going to assume yes
The thing that got me was always referring to Scaleway in the third person. e.g. this read like the response I get when I ask AI to review code:
> Scaleway’s solution to that problem was ingenious: embedding a Raspberry Pi module with each Mac mini.
(I realize this may be an artifact of a corporate style guide, but I'd much prefer "Our solution to that problem was embedding . . ." Both because the "was ingenious" doesn't add a ton and reads like puffery and because this is Scaleway's own blog and referring to yourself in the third person is grating.)
It doesn't? If you didn't know those two things, they seem highly relevant to the subject being discussed. They define SoC, which might be an acronym you've known since high school (I did, but I'm a total nerd), and it justifies why use Mac minis instead of what usually gets used.
As to whether it was AI generated or not, who cares? It's useful information if you didn't know it already, and if those words came out of matrix math or someone non-technical with a BS in communications, does it really matter to you? Are you going hungry tonight because the money that went to creating those words went to Nvidia and not Sarah in Marketing? Sarah in Marketing might be out of a job soon, but her boyfriend has a good job that's not threatened by AI, so I hope she'll be fine, but I don't know. Is that the underlying worry here?
There is an emdash in the article though, you didn't think to call that out too?
Identifying MAC spoofing in client network interfaces, which allow DNS poisoning or encrypted layer credential from a client address. Whether there is pragmatic use to spoof, or a secondary drive with no identifier.
20 years ago the company I worked for used a Mac-Mini for video transcoding, because there was some DRM issue we had to deal with, I don't remember the specifics.
running macOS, which runs Xcode, which is required for making and signing iOS and macOS apps, Witcher, then sold on the App Store for money dust justifying spending money on their, or a similar service.
I guess the Mac Pro Rack Edition technically exists, but that's needlessly huge (5U!) for a single node, ungodly expensive, and doesn't have server amenities like a BMC, so it's not exactly flying off the shelves.
This sounds rather entitled. They’re building their own servers for their infrastructure needs. No different than any of the other behemoths with their own data centers.
I'm also surprised they're touting the density of this solution— seems like the obvious thing would be to put the Minis on their sides. A 4U chassis has 17.5cm vertical space in it, and a Mac Mini is 17cm wide. With the Mini being 2in in height, that suggests 8-9 Minis in a 4U rack, vs 2 Minis in a 2U rack for Scaleway's trays.
EDIT: Here's a commercially-available solution that's 6/4U: https://www.mk1manufacturing.com/Rack-Mount-for-6-M4-mac-min..., you'd think it could basically be this but with the management plane behind or in front. And as others have said, making the management plane be more shared, so it's not 1:1.