Want to compare insecure_nbd but doesn't seem to work (secure does)
-
@sluflyer06 we did a rework on NBD, to be able to use it everywhere, paving the way for some nice features like retry on network error
but it may have an impact on block based backup. I will make a branch which should alleviate this today
-
@sluflyer06 can you test the speed with this branch based on master https://github.com/vatesfr/xen-orchestra/pull/6840
The backup job must have only one remote , which must be block based, and without a continuous replication
Warning : this is not production ready, this branch is only to find where the potential gains are.
-
@florent How would I verify for testing if its insecure NBD or not? I switched to your branch and rebuilt, I see the same message about not allowed but dunno if that matters.
-
@sluflyer06 For now , I get back to the first problem : NBD should be faster than xapi export ( or at least as fast)
now I 'm working on enabling insecure
edit : the not allowed is only to inform the user that it can't be set through XO, but it should be used for backup if present
-
@florent like Oliver was telling me, to compare secure to secure, it is faster than https,.still curious if anyway to try insecure.
Also. Is there a way to update XO (from sources) without losing the config.yaml or just a minor inconvenience until NBD is fully rolled into XO? (I assume we'll get told when we don't have to run custom config for NBD whenever it's ready?)
-
@sluflyer06 the warning on XO is to discourage the mass. But you can really try
you can make a config.toml file in
~/.config/xo-server/config.*.toml, it should be loaded , and won't be changed by an XO update . https://github.com/JsCommunity/app-conf
