@ieugen Read the blog post that XCP-NG posted today on this very topic, but even if the decided to stick with CentOS 8 Stream for the future base platform, they have selective control over which packages/updates would get released for XCP-NG.

I've already switched my CentOS 8.x installs to CentOS 8 Stream. Fedora is too buggy and too far upstream of RedHat for my personal taste. CentOS 8 Steam is supposed to be positioned between Fedora and RedHat, so they might just hit the sweet spot.

Of course, if XCP-NG switched to Ubuntu LTS releases as the base going forward, I wouldn't cry about that either, so I anticipate this announcement from RedHat won't really affect XCP-NG and we'll look back on this and realize it was not a big deal.

@badrAZ said in Orphan VDIs after every backup:

issue

Thanks, I've subscribed to the github issue and will build XO as soon as I see the pull request is applied.

@olivierlambert Thanks. Patches came out for XCP-NG 8 today and I powered up my 2nd XCP-NG server to apply pool patches, the load balancer promptly took it down...

Lesson learned, I guess I need to temporary disable my density policy before I power up the 2nd server!

@ieugen Read the blog post that XCP-NG posted today on this very topic, but even if the decided to stick with CentOS 8 Stream for the future base platform, they have selective control over which packages/updates would get released for XCP-NG.

I've already switched my CentOS 8.x installs to CentOS 8 Stream. Fedora is too buggy and too far upstream of RedHat for my personal taste. CentOS 8 Steam is supposed to be positioned between Fedora and RedHat, so they might just hit the sweet spot.

Of course, if XCP-NG switched to Ubuntu LTS releases as the base going forward, I wouldn't cry about that either, so I anticipate this announcement from RedHat won't really affect XCP-NG and we'll look back on this and realize it was not a big deal.

Hi, I just read about the XO load balancer plugin and have enabled it with a density based plan. Pretty cool, it moved all of my VMs to one XCP-NG host (in a pool of 2) and powered down the 2nd host.

Am I correct that if the thresholds I specified in the density plan are exceeded for CPU utilization and/or memory, the load balancer will automatically power on my 2nd XCP-NG host and migrate some VMs to it?

Pretty cool feature!

I run an Ubuntu 20.04 LTS virtual machine that has all of my docker containers running... One of the containers is Portainer, which provides a nice web gui to manage the docker containers.

I see @olivierlambert mentioned a plug-in that makes the containers visible to XO. I wasn't aware such a thing exists, but I'm going to go google it now and see if I can get that working...

Makes sense now that you mention it... Perhaps I should have realized that because obviously the backups only run on my primary XO instance. Thanks!

OK... Perhaps it's my environment, I have a main XO VM that I don't update that frequently, everything checks out OK there...

Weekly or so, I update another XO LAB VM that is at the latest level. After updating my XO LAB instance today, it shows the backups and snapshots as detached. The other XO VM does not show any detached snapshots or backups, etc.

Hi, I just upgraded to the latest commit as shown here:

[info] Updating xen-orchestra from '626e2fcb1' to '2aed2fd53'

XO now shows that all of my backups are detached and not associated with a backup job as well as detached snapshots, which I believe is a bug.

Please review and let me know if you have any questions, thanks.

@badrAZ I've rebuilt XO and confirm that the suspended VDI snapshots are no longer listed as orphans, thanks!

@badrAZ said in Orphan VDIs after every backup:

issue

Thanks, I've subscribed to the github issue and will build XO as soon as I see the pull request is applied.

@Danp I had already removed the orphans today, however, I'll check again tomorrow because it happens every day. All of my backups are delta backups and they all use the "with memory" option.

I'll post more info tomorrow after my backups run again overnight. It's sort of odd that I'm left with orphan VDIs after every backup, because if I don't delete them, they're replaced by new orphans the following night, etc.