I was able to download.

This issue is now resolved. I had to issue the command git checkout master before the standard upgrade process would work again.

The argument I'm trying to make is 1) protect olivier from the customers that would abuse the support and 2) make it so that the good customers (big and small) don't get raked over the coals.

Which likely means a per-core cost (or per host* (really doesn't make sense)) and some sort of tiered support plans, like @bnrstnr 4 tickets a year or some such system.

Which is highly effective, cost wise for everyone. Olivier won't get rapped by shitty customers, and customers can up their support level to "Please wipe my ass Tier" if they so choose.

@DustinB3403 said in Xen Orchestra - Feature Restrictions:

@dbeato said in Xen Orchestra - Feature Restrictions:

I am using the community edition.

Are you having some issue or just making a statement?

Making a statement, my issue with notifications as I chatted you, I will post something about it.

@danp his installation is pre-service creation.

IMO time to rebuild and get current.

@Pete-S said in Xen Orchestra - Community Edition - Installing with Yarn:

@travisdh1 said in Xen Orchestra - Community Edition - Installing with Yarn:

@DustinB3403 said in Xen Orchestra - Community Edition - Installing with Yarn:

@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?

I can reach this without being logged in:
https://raw.githubusercontent.com/Jarli01/xenorchestra_installer/master/xo_install.sh

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.

@stacksofplates said in A script to pull updates from GH or use History:

@DustinB3403 said in A script to pull updates from GH or use History:

So to clarify here, the goal is to allow admins an easy way to pull the most current update script. Not to run it for them on a set schedule.

(reason being is if we auto-force an update, and that update breaks their system, I don't want to have that on my mind)

I don't understand the hangup here. The cron job I pasted above does not update anything. It doesn't run any scripts. It doesn't force anything. Where this is coming from I have no idea.

This is from sidebar conversations regarding the topic. It has nothing to do with the cron job you posted.

@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.