What Are You Doing Right Now

olivier

@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

@olivier XenCenter got made open source? It wasn't for a VERY long time.

scottalanmiller

@olivier said in What Are You Doing Right Now:

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.

That's definitely what would be nice. Base CentOS 7 install, add a repo and away you go.

olivier

@scottalanmiller said in What Are You Doing Right Now:

@olivier XenCenter got made open source? It wasn't for a VERY long time.

https://github.com/xenserver/xenadmin

To be fair, I don't know in what way it could be useful, but anyway it is!

scottalanmiller

@olivier said in What Are You Doing Right Now:

@scottalanmiller said in What Are You Doing Right Now:

@olivier XenCenter got made open source? It wasn't for a VERY long time.

https://github.com/xenserver/xenadmin

To be fair, I don't know in what way it could be useful, but anyway it is!

Pretty new, I just found it too.

https://xenserver.org/partners/developing-products-for-xenserver/21-xencenter-development/88-xc-dev-home.html

I agree, it's garbage so who cares.

olivier

@scottalanmiller said in What Are You Doing Right Now:

That's definitely what would be nice. Base CentOS 7 install, add a repo and away you go.

That's the goal, yes. Is it doable? Can't tell for now! (because… I don't know!)

olivier

@scottalanmiller I think we used this to read how VM.create was used, but a more efficient way was to create a "XAPI proxy" to intercept all calls between XenCenter and XenServer, with all parameters (because you know, when you don't have a documentation…)

Obsolesce

Why not port XC or whatever to KVM? Why stick with XenAnything?

scottalanmiller

@tim_g said in What Are You Doing Right Now:

Why not port XC or whatever to KVM? Why stick with XenAnything?

Well XC is crap, XO primarily exists because XC is such garbage.

It's XAPI that would need to be ported and it's a big undertaking.

Obsolesce

@scottalanmiller said in What Are You Doing Right Now:

@tim_g said in What Are You Doing Right Now:

Why not port XC or whatever to KVM? Why stick with XenAnything?

Well XC is crap, XO primarily exists because XC is such garbage.

It's XAPI that would need to be ported and it's a big undertaking.

I'm not very familiar with Zen components. I don't have plans to touch it unless it would ever become a job requirement in some way.

I guess what I'm asking, is why continue down the path of ZenAnything?