5 ms·
They'd have to download your custom image, probably hundred of megabytes or gigabytes, each time upon starting new instance. This makes no sense on WAN. It’s mu
by deno 14y ago
They'd have to download your custom image, probably hundred of megabytes or gigabytes, each time upon starting new instance. This makes no sense on WAN. It’s much better for both contributors (less stuff to download) and clients (less time wasted waiting) to only download your application stack.
It’s not EC2 alternative, this is a different kind of service.
- donavanm 14y agoI think you miss my point. Currently (AFAIK) the provider/dom0 must download and run a windows executable. Many people have no windows hosts, but do have existing xen/kvm dom0s running. If grid spot provided their service as a xen/kvm client image I would be able to host it. There's no requirement for the host to download the client image multiple times. I'd imagine you have something like ephemeral domu disk and use kmods to provide a control plane and network tunnel.
- deno 14y ago> Many people have no windows hosts, but do have existing xen/kvm dom0s running. If grid spot provided their service as a xen/kvm client image I would be able to host it. They should provide their image instead of the binary. Theirs, rather than their clients. Got you know! But I don’t think their audience will have much use for it. Well it’s unlikely to be a priority, anyway. > Don't get suckered in to providing 1:1 IPv4 with your proxy model. BTW, he doesn’t. It’s all proxied through single IP on different ports. E.g. this is what I got: ssh gridspot_user@69.4.239.76 -p 25502