I won't be against it obviously. But I'm not the one making the choice 
administrators
Private
Posts
-
RE: Tesco and XCP-ng
-
RE: XCP-ng 8.3 updates announcements and testing
As this is my first time installing these update candidates,
Actually we moved first batch of packages that landed in testing to candidates repo, to avoid mix up in the second batch that just landed in testing repo. Since nothing new appeared in candidate you should probably already had them before, home this is clarifying what is actually happening
Next yum update should just pull the latest stable versions?
Not if you already have installed then from testing (or candidate) repo, because versions are same, it's only the distribution channel that change, no impact for testers.
I'm not sure what you understood from @scarfantennae's question, but that we moved packages from xcp-ng-testing to xcp-ng-candidates doesn't seem on topic here.
The question is: "now that I've applied this update candidates from the testing repositories, am I definitively in testing mode?".
The answer is: no, because:
- The
--enable-reposwitch only applies to the two commands you ran: clearing the cache and applying updates. The repositories remain disabled by default, so yes, next time you update you'll only get stable updates if there are any. - Either the exact packages that you installed will be pushed as official updates (in which case there will be nothing for you to do), or we'll push newer updates that will supersede them automatically next time you update.
Hope it's clear.
- The
-
RE: Slow response between XCP-NG and cloud stack syncing
Hi,
XCP-ng got an event system that will propagate things like this instantly, at least that's the way it works normally
- Do you have the same behaviour in Xen Orchestra?
- Have you reported the issue to CloudStack?
- If you have an XCP-ng support subscription, you can also open a ticket so we can take a look on XCP-ng status to catch any obvious issue.
