@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 🙂
@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.
@travisdh1 what issue are you referring too? As far as I recall everything that is needed is included in the appropriate script install/upgrade
It's git, not the scripts. Since you need to have your git user information entered for it to work, would be good to have it added to the instructions.
I don't understand. Do you have to have a github account and be logged in to be able to download anything from github?
No you don't have to actually have an account, it's a git requirement to put something in there though and we don't autofill that information in case someone wants to supply their account details.
@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.