XO Team group | XCP-ng and XO forum

pdonias

@acebmxer Thanks for the report, we'll check that! Regarding themes, it will remain non-persistent until we implement the full theme system.

@jacob.becker Thanks for the detailed feedback, we'll see how we can improve that

Bastien Nollet

Hi @MajorP93,

This PR is only about changing the way we delete old logs (linked to a bigger work of making backups use XO tasks instead of their own task system), it won't fix the issue discussed in this topic.

florent

@DustyArmstrong I think we won't do too much on XO5 for now, and for xo6 we are trying to do everything with a UX designer to ensure coherence, at least until we have a full working app

florent

@LoTus111 the investigation is ongoing , no success for now

simonp

Thanks for the heads-up and thanks for the help !

florent

I think at least showing them could be a good idea. this is planned ( but low priority)

florent

@Pilow said in Detached VM Snapshots after Warm Migration:

@DustyArmstrong I have hard times to understand how the VM is aware of the XOA it is/was attached to...

a VM resides on a host
a Host in in a pool
a Pool is attached to a (or many) XO/XOA

how the hell your VM is aware of its previous XO ?

a running vm has a property resident_on exposed by xapi
the queries from pools are handled separatly, thus we can decorate all the object of a xapi with a $pool property
this is the server collection that track which server data we know, and which one are connected or not

Mots of the data lives in the xapi, that means that multiple XO can handle multiple pools. The exception are the SDN Controller ( best handled by only one XO) and the backups of the same VM.

florent

nice catch
you now know the internal magic of the xo backup .

simonp

@acebmxer

Thanks a lot, the first issue was resolved but your log indicates a separate issue.
We think we resolved it on the "debug_backups" branch, could you test it again ?

Anyways, if this fixes the backup issue, a fix should be available tomorrow Paris time on master.
In the mean time you can revert to the commit a3139 as explained in the first post.

Thanks again for your help.

XO Team

Posts

Member List