Xen Orchestra Backup, Single VM Failing
-
@DustinB3403 I was only joking
-
Next, he'll be telling you to call 0118 999 881 999 119 725...3.
-
This number will give you better looking support team, faster response time and a lot more! So remember, dial 0118 999 881 999 119 725...3!
-
WTF is X OS
-
-
Xen Orchestra Source
-
@anonymous said:
Xen Orchestra Source
I have never seen that acronym used. Did he just make it up
-
XO = Xen Orchestra. There is only one thing that is XO.
There is XOA, but it is still XO. Just XO managed by someone.
So unless you say you use XOA, the assumption would have to be XO not managed by anyone and the only way to get XO if it is not XOA is obviously the source distribution.
Trying to call it XOS is just trying to intentionally confuse things.
Note sorry for the multi part response. I was driving and using Siri earlier.
-
@JaredBusch said:
WTF is X OS
I asked the same thing. There isn't any product with those initials that I can find.
-
@JaredBusch said:
XO = Xen Orchestra. There is only one thing that is XO.
There is XOA, but it is still XO. Just XO managed by someone.
So unless you say you use XOA, the assumption would have to be XO not managed by anyone and the only way to get XO if it is not XOA is obviously the source distribution.
Trying to call it XOS is just trying to intentionally confuse things.
Note sorry for the multi part response. I was driving and using Siri earlier.
I had this exact same conversation with him via IM last night. I said that using XOS was confusing as it doesn't exist as a product name, there is no means to figure out what it implies and no way to look it up. There is nothing called Xen Orchestra Source so even the source of the acronym remains a mystery. He said that he spoke to @olivier and he agreed that XOS was the right acronym, and that it should be used for clarity. But obviously it is exactly the opposite and no one knows what it means, no one searching will EVER find this and will bypass it because XOS is clearly not what someone using XO is looking for (even using XO in the title would be confusing for that, it's not a big enough product to not use its name in titles) so it is basically just hiding the info from everyone. Only the tags give away what product is being talked about.
-
For those wondering, the original title was: XOS Backup single VM Failing
Modding to something searchable and identifiable so that people know what the topic is.
-
As I said on the topic where he's asked:
@olivier said:
For me, it's mainly XO when talking about sources, XOA the appliance. But XOS if you like, it doesn't matter
-
-
But that's easy:
- XO stands for "Xen Orchestra"
- XOA is "Xen Orchestra virtual Appliance"
-
@olivier said:
But that's easy:
- XO stands for "Xen Orchestra"
- XOA is "Xen Orchestra virtual Appliance"
That's what I said!
-
@olivier said:
But that's easy:
- XO stands for "Xen Orchestra"
- XOA is "Xen Orchestra virtual Appliance"
Exactly!
There is no such thing as XOS. Because where else would you get XO but from the source? Even XOA uses the source, just managed by someone else and not the actual user.
-
More to the point -- did you figure out if there was a fix for this issue? I am having the same problem on my freshly installed XO setup.
-
@dafyre Did you remove it and re-add it? or did you want a better solution?
-
Any log output?
-
@anonymous said:
@dafyre Did you remove it and re-add it? or did you want a better solution?
I did remove and re-add it, but that did not fix it.
He thought that XO mean XOA and no term existed for XO itself.
