Comments on: Project Kronos: XenAPI on Debian and Ubuntu

By: Xen host: vm’s management best practises - Admins Goodies

Xen host: vm’s management best practises - Admins Goodies — Mon, 07 May 2012 02:33:35 +0000

[...] http://blog.xen.org/index.php/2011/07/22/project-kronos/ [...]

By: blog.xen.org

blog.xen.org — Mon, 16 Apr 2012 10:05:33 +0000

[...] course, project Kronos is almost completed, which will help Xen support in OpenStack. You can find information about [...]

By: what’s the XCP « prajna

what’s the XCP « prajna — Tue, 10 Apr 2012 08:44:14 +0000

[...] http://blog.xen.org/index.php/2011/07/22/project-kronos/ [...]

By: Announcing Project Zeus: XenAPI in Fedora, CentOS and the EPEL – blog.xen.org

Tue, 28 Feb 2012 18:39:04 +0000

[...] Zeus, our port of the XCP toolstack to Fedora and CentOS (through the EPEL). This is a follow-on to Project Kronos, which brought the XCP toolstack to Debian-based systems. This will give users the ability to do [...]

By: Xen @ Build a Cloud Day Boston – blog.xen.org

Xen @ Build a Cloud Day Boston – blog.xen.org — Thu, 22 Dec 2011 08:00:50 +0000

[...] spent a lot of time (and presented in more detail) presentations on Project Kronos, which in a very short time has been developed and is nearing a initial release. Stay tuned to the [...]

By: lexalt

lexalt — Mon, 12 Dec 2011 09:57:34 +0000

Just to reiterate what I posted elsewhere…

I would much prefer that “a ‘yum install xapi’ on Fedora” be developed first.

I’ve run into MANY problems in trying to get Xen working properly using Ubuntu 11.10 as Dom0. In contrast, Xen works pretty much out-of-the box with Fedora 16. So with this in mind, and given the relationship between Fedora and RHEL, I’m not sure why you guys didn’t focus on “Xapi for Fedora” first. Seems like that would have been an easier and quicker route to getting a product out to users. Is it too late to target “Xapi for Fedora” as your first priority for now, and then come back to “Xapi for Ubuntu” later, such as when Xen is more stable on Ubuntu? (Of course, if “Xapi for Ubuntu” will be released soon, then that would be great too. I just hope for a working version of EITHER as soon as possible.)

As for other alternatives, I’m currently testing Cloudmin with Fedora 16 on my home server. I wish I could just use the current XCP (or Citrix XenServer), but unfortunately, the current XCP doesn’t have driver support for my Atheros NIC. (CentOS 5.6 also seems to lack out-of-box support for my Atheros NIC, which probably explains why XCP doesn’t support my NIC.)

A bit off topic, but…

I hope that future editions of XCP will be based Fedora instead than CentOS. I mean, what’s the point of offering a repackaged XenServer? Rather than just clone XenServer, XCP should be the cutting edge alternative, much like Fedora is the cutting edge alternative to RHEL.

By: blog.opennebula.org » Archives » Building OpenNebula Clouds on Xen Cloud Platform

Mon, 24 Oct 2011 08:17:57 +0000

[...] way back to 2008, OpenNebula 1 and Xen 3.1. This renewed collaboration, together with projects such Kronos which will deliver XCP with different Linux distributions, will make building rich Xen based clouds [...]

By: Xen @ OpenStack Design Summit – blog.xen.org

Xen @ OpenStack Design Summit – blog.xen.org — Fri, 07 Oct 2011 04:20:36 +0000

[...] Design Summit are now in the books. It’s been great to meet the development community. Project Kronos was very well received and Chuck Short offered to take a closer look at helping us package it for [...]

By: Xen at OpenStack Design Summit and Conference – blog.xen.org

Xen at OpenStack Design Summit and Conference – blog.xen.org — Fri, 30 Sep 2011 16:24:24 +0000

[...] the summit, I’ll be leading a session on Project Kronos. There will also be a session on XenServer and KVM feature [...]

By: Mike McClurg

Mike McClurg — Thu, 29 Sep 2011 07:03:08 +0000

Actually, the Kronos xapi packages require Xen 4.1.

Remus is integrated into Xen 4.1, so the functionality would be present, but xapi has no mechanism for controlling it. I would imagine that activating Remus underneath xapi would really confuse xapi and probably leave your system in an unstable state.

There has been some talk on the xen-api mailing list about adding Remus support to xapi, bu there are no concrete plans yet.