Best posts made by olivier

@DustinB3403 The changelog is just telling we "fixed" this issue since the last release. It doesn't mean it was not done 1 month ago. Greenkeeper is monitoring all the GH XO repo since then.

So you'll have to find the super slow bottleneck

My lab is pretty simple, if you need more info on how I achieved those speeds, tell me

There is no magic: you need to have enough write speed on the target and read speed on the source.

@BRRABill it's a known issue already in the first post of the dedicated feedback topic: https://xen-orchestra.com/forum/topic/250/xoa-v5-feedback/2

Probably a consequence of the increasing pressure coming from here: https://bugs.xenserver.org/browse/XSO-581

This is added to "Wishlist" and transmitted to a XS product manager.

Why not make a manual run? (the "play" button) without enabling the job.

Closed means the issue is "finished": without extra comment or specific tag (like duplicate, invalid or won't fix), it means that's solved.

You can follow links to see what fixed the issue (in the "via #1347" or the commit hash).

TL;DR: issues fixed. Will be released in the "next wagon".

@Fetakungen xo-server output when the issue is triggered.

Clicking on those link won't destroy the universe: go click and see where are you going

One send you to a Pull Request (PR), a piece of code written by someone and send "sent for review". Julien (lead dev) checked the diff (code modified) and then merged it in the next-release branch.

The other link directly to a commit fixing the issue

edit: a PR can embed multiple commits

Main reason to have not thin pro by default is the quality of code for working on files rather than blocks (with LVM).

In file situation, XenServer has to write metadata twice (like in NFS situation by the way). Historically (and today until SmapiV3), the code managing files is a mess.

Personally, I never encountered problems using files (in fact I encountered less issues using NFS).

About ISOs repo: design pattern to work with ISO is shit. And that's really hard to do anything like this on our level (ie with XAPI calls). I hate this because people without XS knowledge often blame us for that We can't stream ISOs, those repo are read only and everything you can imagine to be complicated to workaround. If you want to read more, see https://github.com/vatesfr/xo-web/issues/288 for discussion.

@scottalanmiller said in What You Need to Know About XenServer:

@olivier An aside, have you considered selling general XS support? Even for those not necessarily running XO? Just wondered if it was ever considered as a lower cost alternative to inclusive support from Citrix might be a valuable market offering.

@DustinB3403 said in What You Need to Know About XenServer:

Also @olivier I think it would be a great opportunity as well for you to offer general XS support as well.

I don't think you really imagine the colossal amount of work needed to do that. I got ONE customer with XS support included, and during the XS7 disk bug, I spent almost an entire week helping him. Multiply this by more or less 100, and you see the problem. It's not doable with our current size: we can't sell something we can't be sure to deliver. Plus we'll need a team able to be up 24/7, which needs around 8 people dedicated to at least having someone covering a time slot.

@DustinB3403 That's exactly what I've done with one client, and I'm stopping there.

@BRRABill I like use refurb parts for that, like https://www.servershop24.de/en/components/controller/sas/hp-smart-array-p400-raid-controller-256-mb-sas-pci-e-447029-001-low-profile/a-105422/

Unbeatable price/perf ratio.

That sound really overcomplicated to serve just some ISOs. I wonder if I won't offer a "public" NFS in read only with most popular ISO, a kind of ISO as a service

@Francesco-Provino said in What You Need to Know About XenServer:

@olivier or via cloudinit, exactly, I just forgot to add it.

The thing is we already have CloudInit support, so it would be a shame to not using it

@BRRABill said in What You Need to Know About XenServer:

My new take on XS is to not touch XS. It's like Fight Club.

The easy way for ISOs I found was...

a) set up a new Linux Mint VM
b) set up an anonymous share
c) add ISOs
d) done

Windows works, but it;s hard to do anonymous shares, I've always found. You could create a user, which I did initially, but I've since moved to a small Mint instance and haven't looked back.

That's a way to do it also yes. In general, I've got always a physical machine (eg for backup) with enough space to do that. Doesn't require much bandwidth and power to simply share ISOs.

@JaredBusch XenServer wasn't designed for home usage, but for companies which already have plenty of shares (NFS/SMB). It explains why it's not meant like this "in a easy way".

But it will work with a local ISO storage, it's just not really user friendly.

You can force host to go into pool.

@Danp In general, it takes around 72h to have it in here. Feel free to wait to avoid manual install. There is nothing we could do about this.

No need to reboot, you are not on Windows xo-server runs in memory, so to get last version, you need to restart the process. That's all.