XCP-ng updates from Xen Orchestra

----
XCP-ng updates from Xen Orchestra
// Xen Orchestra

You may already know: we decided to have a better update mechanism in XCP-ng (vs XenServer). We are using the RedHat way with yum.

But it would have been interesting to also be able to update directly from an UI, or to avoid updating each host one by one.

Guess what? That's why we developped a XAPI (XenServer/XCP-ng API) plugin! You'll see it's now very easy to keep all your hosts up-to-date, but also have more transparency on what's going on!

This feature is coming in XO 5.20 available in 2 days!

Install the plugin

The plugin will be included in the next XCP-ng release. Until this, you'll have to install it, with a simple yum install xcp-ng-updater command. Yes, that's it!

Updates via Xen Orchestra

Here, I'm taking as an example a freshly installed XCP-ng 7.4.1. Since our release, some patches are available.

First, just go into the Home/Pool view in Xen Orchestra, and you'll see that some pools need updates:

"XCP Pool" needs to be updated (it's not XenServer but XCP-ng based): clearly, there is 6 packages in that case. If you click on the pool, you can go into the dedicated view and "Patches" tab:

By clicking on "Install pool patches", all your hosts will be updated automatically! But wait, there is more? You want to know what's need to be updated? Click on the host, and go into the "Patches" view:

And you can even see the changelog (here, the only changelog available is for microcode_ctl):

Anyway, as soon your patches/udaptes are installed, we'll display that the updated hosts need to be rebooted:

Hovering on it:

Same in the host view, you can't miss it:

Note: It's up to you to do it anytime you like (always start by the the pool master by the way). Update won't reboot anything automatically. You are the admin, you know when it's the best time to do so.

If you don't have the plugin installed, you'll see a message explaining how to do so:

In the end, updating XCP-ng is very simple, and still following the "upstream" way: using yum and a repository. This is the proof that's possible to achieve!

----

Read in my feedly

Sent from my iPhone