Best posts made by olivier

@DustinB3403 That's something already crossed my mind. But it's not that easy to do. You can't emulate a XenServer infrastructure. So we got two choices: a fake interface or a real stuff but with limited rights to avoid bad things ^^ Again, can't be everywhere, not a priority.

@dustinb3403 said in What Are You Doing Right Now:

@black3dynamite said in What Are You Doing Right Now:

@dustinb3403 said in What Are You Doing Right Now:

@travisdh1 said in What Are You Doing Right Now:

@wirestyle22 said in What Are You Doing Right Now:

Did we just universally decide that XenServer sucks now? A year ago we were thrilled with it and now it's not even brought up anymore when we talk about type-1 hypervisors.

Yep. They took away a bunch of functionality in the free version with the last release. They made it not worth considering anymore compared to KVM or Hyper-V :pouting_face:

On a separate note @olivier and team are looking to create a fork of XenServer (XAPI toolstack) from the existing solution to be able to continue it.

The answer will be to use XO instead but is XenCenter open source or still a Citrix property?

Also are we expecting XO to be included when creating a fork of XenServer?

XenCenter is closed source and included free of charge (always has been). It, plus support for XenServer was what Citrix charged for.

XO and any fork of XenServer are ideally going to go along for a ride hand in hand.

Meaning XO would replace XenCenter, while being fully open source and free.

Not exactly. XenCenter is also open source but only a tool (heavy Windows client) to manage your VMs and that's it.
XenServer is almost 100% Open Source (except few things, like the license daemon, which is 100% legit!)

The problem is to be able to build XenServer from the sources, because there is no documentation to do so (and believe me, it's far more complicated than building XO!). But I started this: https://github.com/xcp-ng

The goal (ideally), we be to use your CentOS, add an extra repo, yum install xcp-ng and you have something almost 100% like XenServer (ie fully XO compatible) but not Citrix dependent and unlocking all possible features. Could we achieve this? I don't know. We'll try.

edit: oh and by the way, we'll push the Gluster driver soon (with a doc!), so for people who want to connect an existing Gluster storage as a XenServer storage repository, this would be pretty easy

@scottalanmiller said:

@DustinB3403 said:

@scottalanmiller said:

@olivier said:

@scottalanmiller We are not in US here. Investors don't believe in this. And a very few succeeded by doing that.

Basically you just said that your investors don't believe in making money.

I think what he said is he wouldn't have any investors if his company wasn't making money. Or at least a model to make money.

Good investors, the big ones, make their big money by investing when a company is small and betting big. If you are investing in a company already profitable, your opportunities for big wins are small.

What he is explaining is that they really only have traditional investors there, and this is a well known European problem, they lack the venture capital ecosystem that drives the US economy.

This.

@scottalanmiller should be the years of doing this, but I'm not sharing this view anymore. Well, ideally yes, I would like things working like that. But never found someone else with money here agree with that.

Connecting to another hypervisor is totally possible (and even by design), but it will require time AND money (ie: hiring more people)

I have TONS of ideas, (in fact all the ideas you gave here, already got them ). But how the heck I can accomplish this without showing investors they can trust me? I can't tell them "go big or go home". I need to demonstrate the business is viable at least.

So one thing after another. Or give me one million $ ^^

Oh and final thing about this AMA-ish stuff: the goal wasn't to complain about EU investors and giving them all the blame, but just to give a picture of the situation, explaining things. Have a nice day lads

@DustinB3403 Go ahead, I'll answer when I can

BTW, I made very interesting tests with ZFS on Linux + XOA delta backups.

Using LZ4 compression is very impressive. Maybe one day integrate the LZ4 compression on the fly into xo-server.

@johnhooks The only thing needed is a VDI named "XO_DELTA" something like that (visible in the SR view, in the VDI list).

And it's only needed to create delta. You don't need anything to import a backup, you can doing on a freshly installed XenServer (that's the point of a backup: to be useful in case you lost everything)

@johnhooks It stays until the next backup: then it's removed and replaced just after by a new delta snapshot. That's because a delta is always created by making a difference between 2 references (the current VM disk and a snapshot).

@johnhooks Depends of your XenServer SR type, not related to XO.

• LVMoiSCSI: thick provisioned (not for Dundee IIRC)
• NFS: thin pro
• Local LVM SR: thick pro

@johnhooks Sadly yes. That's the usual problem with thick pro storage. That's why NFS is always a good idea for shared SR.

I have to make some test to check how Dundee behave now with Local LVM and LVMoiSCSI.

@DustinB3403 Local Storage in LVM. Not file based.

@johnhooks To avoid the "re-importing" step that you need with classical backup

Backup:

• exporting somewhere (any filesystem)
• re importing when need (import time)

DR:

• streaming somewhere (another XenServer host)
• ready to start on the target if needed

edit: so it seems similar but it's not for the same use case.

@johnhooks If you are on a XenServer pre-Dundee, that's normal: LVM is not thin provisioned in this case.

Don't mix node and npm version.

BTW, it should work with latest node version now.

If you want to stick on stable, a workaround would be npm i [email protected]

That's because the install process went bad, due to lodash issue (we reported it here)

So before the npm i, do a npm i [email protected].

Check our twitter (@xenorchestra) or blog, you won't miss it

edit: if you registered in our website for a XOA download, you'll receive an email

@johnhooks haha nope, that's something designed with Paper, IIRC (by my associate, who is ergonomist and spend our IT budget in Apple iStuff hardware )

No new thing in the web UI for continuous delta, it's automatic. If you are on next-release, it should already work now.

edit: it's the same job/backup thing. So restart after update, and re-run your backup jobs. You'll see the oldest delta merged in the full.