just a personal opinion I'm leaving here, no follow-up needed.

If I want to run containers I use OKD.
I've always seen all the comments about keeping the dom0 controller to a minimum, docker alone adds a 2GB overhead to it, no more problems in adding stuff to it.

Thanks! Don't miss Daniel Stenberg stories, they are gold (eg: being insulted because someone found some curl sources in a bigger software). Some gems with the right tag in his blog: https://daniel.haxx.se/blog/tag/funny/

As I already explained in different places, what matters is the hypervisor, kernel, OVS and such important packages. We can still backport security fixes ourselves on various packages inside the OS.

XCP-ng is only partially based on CentOS, only using non-critical CentOS packages (NOT the kernel, NOT Xen, NOT OVS, SMAPI/XAPI aren't packaged in CentOS etc.).

XCP-ng is NOT your regular distro, it's an appliance where we backport relevant security fixes.

Be sure that next major version won't even have SSH access enabled by default.

We are very well aware about all of this. But we are not a distro entirely based on RHEL at all (again, all the network, kernel, storage and compute plus many other things are NOT coming from RHEL).

On a personal point of view, I'm a strong proponent of Copyleft licenses and the greater good, in the original spirit of free software. To me, there's a real moral contract between the software editors and the users. You can read my detailed opinion in this blog post: https://virtualize.sh/blog/the-moral-contract/

Due to those personal opinions, I'm really unhappy with RedHat move (and behind Alma and Rocky), but this is NOT clashing with our position for the next major release. So no, we won't be directly disrupted by this move.

@ryzen3 feel free to open a feature request on XO GH repository with many details as you can, so we can create the feature 🙂

We just released XCP-ng 8.3 beta 1 !

I opened a new thread for us to discuss it and for you to provide feedback: https://xcp-ng.org/forum/topic/7464/xcp-ng-8-3-beta

Thanks for all the feedback already provided here, and see you on this new thread!

In order not to miss anything (and, let's be honest, for me to be sure that messages on the new thread reach you all), the best course of action is: open the new thread right now and use the "watch" button.
53fac025-6e0c-465b-97ab-5ca73a97bd93-image.png

And let's answer this common and legitimate question: how to upgrade from alpha to beta ? Well, there's nothing to do, just update as usual. In fact, you might already be in beta state. However, as indicated in the blog post, we need a lot of testing of the installer, so it's also an option to start from the installation ISO again.

Great news! Thanks for the feedback 🙂

Good news!!

@stormi

@stormi said in New patch - sudo:

Better not install security patches that require a reboot without rebooting. All you create is a discrepancy between what resides in memory and what is on disk, and in rare cases things may break, for no added security.

Isn't this only true with specific patches? I'm no expert here so really just curious. Regardless I ALWAYS plan to reboot with ANY patches coming out and think others should do the same.

@stormi said in New patch - sudo:

We want to provide better metadata associated with updates, for XO to display. This is not ready yet, so for the time being, check the instructions for each update on the official blog. The update tag will list only update announcement: https://xcp-ng.org/blog/tag/update/

This is great news, love to see it!

I'd like to get first to build our XO Packer plugin, that will help us a load to build those 🙂 So as soon we got it, we'll create more templates, including Fedora 🙂

I've set up a test-environment and indeed it worked. Commvault was (is?) checking for specific version/agent string when connecting to XS/CHV/XCP-ng and in older versions refused to connect to XCP-ng.

I successfully installed the agent on a proxy-vm (it uses a proxy to ro-mount the VM-VHDs and backup the content), connected the pool, delivered the VM-inventory and also ran a successful backup:
171c0956-e3e2-4fb9-a93b-48a2be6751bb-grafik.png

In other words: If you're using Commvault (11.28+) you're not any longer locked on Citrix.

So as everyone could spot, XenServer is now a dedicated business unit inside Cloud Software Group. Funnily enough, they are back with the old name, and are more independent.

IMHO, that's good news, and we hope to continue to develop our partnership with them!

It is, and it's XOSTOR 😉

Don't get me wrong: constructive feedback is ALWAYS welcome 🙂
This is just the pricing "cards", but there's already the information that you have initial setup assistance, upgrade help and direct access to XCP-ng devs. Sounds more than just "send us an email when you need". What would you have wrote then?

Also, regarding not paying the project but hire people to contribute on it: I'm very fine with it!

@KPS Hi. This thread is now inactive sop please open a new thread dedicated to your issue.

You can import the VHD file via our REST API, see https://xen-orchestra.com/docs/restapi.html#vdi-import

Great. Thanks for checking this. 🙂