On Mon, Feb 08, 2010 at 03:29:21PM -0800, graziano obertelli wrote: > Hello, > > as you may know (or know now :)), Eucalyptus is in freeze for a 1.6.2 > release schedule by the end of the month, or the beginning of March, but > we would like to make an attempt to have packages for Fedora too for our > next release. > > As mentioned before, we already have a spec file, which produces packages > not good enough to be integrated in Fedora, but this will give us a head > start to flushing out the installation procedure on Fedora as well as > finding how to configure it properly. I would love for comments on how to > make things better on Fedora, and in order to do that, we have a source > tree available on launchpad for 1.6.2. Problem is that, for now, I'll be > working on a private branch which I'll merge if our Q&A will give the > green light on the packages: if there is interests in seeing it, I'm more > than happy to publish it where is convenient for Fedora. Is there interest > for it? Is there a preference of where to put the code? > > Also, if someone is working on axis2c, axis2 and/or rampartc, I'll be more > than happy to use those packages too. > > The timeline is a bit tight for us, so forgive me if I will make stupid > question, which may be answereed but some directed google search. The > first one of which is this one: so far we used xen as the hypervisor of > choice on CentOS (and RHEL), but I know that now both are included in > Fedora. Which one is the preferred one? Which one should be the Eucalyputs > default? > Currently Fedora does not ship Xen dom0 capable kernel, so using Xen on Fedora requires manually installing dom0 kernel first. (Fedora is planning to ship Xen dom0 kernel again when the dom0 patches are in upstream Linux kernel). So I guess kvm should be the default in Fedora. Xen support should be an option of course, many people are running Xen on Fedora. -- Pasi
