G'day AlexSSS,
My understanding of how the BBOSP has evolved is that hot swap disks have never been considered to be a mandatory architectural/engineering design goal.
It's always possible to implement this with the right combination of backplane and storage controller, combined with the ability to identify your failed disk and of course your OS being able to deal with this.
However this also necessitates a physical design that allows you to open a running chassis and keep it all running with all the complexity that entails.
It's a lot simpler to do a design - and then implement that design to scale - where you don't care about shutting down a pod and in fact BB even talk about how they batch this process for efficiency rather than doing the conventional enterprise 'hot swap onsite' or 'onsite technician replacement within 4 hours'.
So i think to answer your question:
- It's possible - but not on the platform 'as is'
- You'd have to do further engineering yourself
- It would be better to put the engineering effort into your application such that you can take a pod down without a service impact
When wearing my 'enterprise' hat I love the idea of hot swap everything (or at least, power and disks being the two things most likely to fail). When wearing my 'research infrastructure' and 'cloud/scaleable platform' hat, not so much.
Hope this helps.
regards,
-jason
-----
P: 0402 489 637 M:
+61 402 489 637 E:
jason....@gmail.com
On 22/02/2015, at 7:32 AM,
alexs...@gmail.com wrote:
> You speak about theoretical opportunity, but not about practical implementation. In that case there would be no need for hot-swap controller's (
http://wellic.com/cat/d748/2.html). And server baskets would be very simple, and it not so.
>
> Whether a question in that it is possible to derive a disk from BackBlaze Pod v4 without consequences for disks or for a platform.
>
>