@black3dynamite I used the old one, and it worked. I succesfully installed xo now. Normally, I'd like to know what went wrong, but it's too late and friday

Also we could achieve hyperconvergence "the other way" (unlike having a global shared filesystem like Gluster or Ceph) but use fine grained replication (per VM/VM disk). That's really interesting (data locality, tiering, thin pro etc.). Obviously, we'll collaborate to see how to integrate this in our stack

@bnrstnr said in XO behind proxy or exposed directly?: nly web server I wanted to use, would there be any benefit at all of using a reverse proxy instead of just forwarding 443 directly to XO? Still it would help for security purposes.

@danp pay range is a bit hard, that will be really variable depending on people applying. And I don't want that our lack of expertise hiring in US, combined with a poor pay range choice, make us miss opportunities. I'll update the work days, but it's pretty standard: M-F, no weekends.

FWIW, xo-server updated to 5.11.1 without issue.

That's where I was headed a year ago with this issue.

Staying up to date on the updates is pretty critical for XO. They update things frequently. You'll be running this update script a lot.

Thanks

A really nice thing about XO is you can import and not power on. So you can remove the NIC and then power on. If it works, you know you're in good shape.

@Jason said in Someone doesn't like local storage for large amounts of data: @stacksofplates said in Someone doesn't like local storage for large amounts of data: @FATeknollogee said in Someone doesn't like local storage for large amounts of data: @scottalanmiller Isn't that part of why we all virtualize so we don't have deal with raw? You can still snapshot raw. Raw can be an image file or a volume or a full disk. Raw doesn't mean not virtualized. @stacksofplates said in Someone doesn't like local storage for large amounts of data: @FATeknollogee said in Someone doesn't like local storage for large amounts of data: @scottalanmiller Isn't that part of why we all virtualize so we don't have deal with raw? You can still snapshot raw. Raw can be an image file or a volume or a full disk. Raw doesn't mean not virtualized. RAWs biggest limitation is you can't storage vmotion it. You can vmotion the pointer but if you are retiring a SAN or something you will be doing it manually. Ya I'm using KVM so I can either move the raw file or the volume to wherever I need it. It's really simple with qemu and lvm.

Found it: https://github.com/vatesfr/xo-web/issues/697

Brilliant Read, I've used Esxi and Hyper-V, good products, but I do have a inner love for Xencenter..

Open an issue and ideally send a PR with the fix: that would be your first (easy) contribution to the project