|
|
|
|
|
by steve1977
973 days ago
|
|
> Wouldn't it be great to power down an idle server, knowing that it can be switched on seconds before you actually need it? considering you would still need to boot the VMs then, once the Oxide system is up, I’m not sure if this is such a big win. And at a certain scale you’d probably have something like multiple systems and VMware vMotion or alternatives anyway. So if the ESXi host (for example) takes a while to boot, I wouldn’t care too much. And, economics of elasticity - you’d still have to buy the Oxide server, even if it’s idle. |
|
To be honoust, I'm using containers most of the time these days but even the full blown windows VMs I'm orchestrating boot in less than 20s, assuming the hypervisor is operational. I think that's about on par with public cloud, no?
> [...] vMotion [...] ESXi.
Is VMware still a thing? Started with virsh, kvm/qemu a decade ago and never looked back.
> And, economics of elasticity - you’d still have to buy the Oxide server, even if it’s idle.
That's a big part of the equation indeed. This is where hyperscalers have an advantage that Oxide at some point in the future might enjoy as well. Interesting to see how much of that they will be willing to share with their customers...