"12 pis in 1U" where 1U is defined as the height of a pi on its side plus shelf, rather than the definition of 1U in every other 19" rackmount data center
Cool spelling mistake found. It's already on our ToDo list and will be corrected soon.
Raspberry Pi Colocation
141–149 of 149 posts
Re: Raspberry Pi Colocation
#142A question to ExaMesh, in case someone from there happens to be reading: could you publically offer a guarantee and promise that not a single byte will be read off of (or written to) customers' SD cards or SSD drives before being installed, or after being uninstalled from your racks?
I personally vouch for our team, but think about it: your Pi is connected to the Internet. You are responsible for the security of the Pi (system security, updates, encryption ...). You send us the hardware in the mail. How many hands does the package go through? Of course, no one gets into the data center without access authorization, etc. pp.
Encryption of your data is the key here.
Re: Raspberry Pi Colocation
#143Can't believe they didn't call it Picolo.
Most domain extensions are already registered. And since we are from Germany, the term "Piccolo" sound very similar to "Picolo" but means something very different: https://de.wikipedia.org/wiki/Piccolo_(Sekt)
However, we would have definitely pursued an overlap/commonality of the word with, say, beer!
Re: Raspberry Pi Colocation
#144EDIS offered a colo service for free, back in the early RPi days. I had two gen 1.5 machines hosted with them; one with OwnCloud, and another hosted my music via SFTP.
gen 1.5? Are they still running those for free? I had "free" colocations in Sweden and Holland that then turned not free then got cancelled altogether. Pi clusters are best for home hosting on your own fiber. Also those Pi 4 need heatsinks like so: http://move.rupy.se/file/final_pi_2_4_hybrid.png
There were more than a handful of free Raspberry Pi colocations. However, since there is real manual work and infrastructure behind it, there are no such offers anymore, as far as we could check.
Re: Raspberry Pi Colocation
#145Hey this is sort of the mirror opposite of my startup (we try to bring the internet to your home-pi, rather than ship your home-pi to a datacenter!). Neat tho! I'm not entirely sure it's that power efficient versus a carved up hypervisor tho...
Very cool commenting on our product. Saw your PiBox on kickstarter and PH. Love it!
Re: Raspberry Pi Colocation
#146> What is the traffic limit? > It's 2021. We don't have a traffic limit for a Raspberry Pi. > What is the data transfer rate? > The data rate is synchronously set to 10 Mbit/s per Raspberry. It's 2021, and you think 10 Mbit/s is enough.
It's because they don't know how to do any kind of QoS
Re: Raspberry Pi Colocation
#147Earlier quoted context omitted.
One could power the equipment off the turbine when it's operating, and off an alternative supply otherwise. It seems a little silly to worry about where the specific electrons came from to power the equipment, though. If powering that equipment enables a wind turbine to produce more power than it would have without that equipment, then it seems like the existence of that equipment is "green" whether or not its power…
Wind turbines generate 690v three phase. It isn't stepped down until it gets to a substation near the consumer. The power needed onsite (lights, control systems, energy to start the blades spinning, etc) usually comes from a natural gas generator or a direct feed from a fossil fuel plant if one is nearby. Due to circular dependencies, you can't power them off the energy they generate.
I don't know anything about the domain, but I'm pretty sure it wouldn't be a big deal to tap off a few kilowatts or so using a secondary winding. Something similar to the alternator on a car perhaps. It doesn't need to be the same circuit and efficiency as the main power generation path.
What do you mean circular dependencies? You mean that you need an independent source of power for all the infrastructure to turn the turbines on when they're not currently generating? Sure, that makes sense. It seems like there's a ton of ways to implement that. Grid power, generators, batteries and solar panels, etc.
Re: Raspberry Pi Colocation
#148Earlier quoted context omitted.
I use a 40 port usb charging station to power my raspberry pi cluster, but I don't like it because the fan sounds like a hair dryer running
if you're using amazon.com/dp/B077R5BVVR/ removing just the outer enclosure and removing that fan should be safe, but it might not be the loudest fan... otherwise the quietest PC is the one in a different room, but you probably already know that
That's exactly the one I'm using, thanks! I was considering the fan, but I've also been worried about torching my house. I'll give it a shot.
I put some work into the frame the cluster is in, and it makes a pretty nice end table. My main pc is a little fanless industrial computer and I love it.
Re: Raspberry Pi Colocation
#149A question to ExaMesh, in case someone from there happens to be reading: could you publically offer a guarantee and promise that not a single byte will be read off of (or written to) customers' SD cards or SSD drives before being installed, or after being uninstalled from your racks?
I personally vouch for our team, but think about it: your Pi is connected to the Internet. You are responsible for the security of the Pi (system security, updates, encryption ...). You send us the hardware in the mail. How many hands does the package go through? Of course, no one gets into the data center without access authorization, etc. pp. Encryption of your data is the key here.
Thanks for the assurance. The concern with "mail order co-lo" is of course that the customers themselves don't travel to the DC to install and power up the server.