Hello,
we got 1.6.2 out, and for now we don't have fedora RPMs. With this
release, as I mentioned, we tried to simplify the way we handle
contributions and we opened up some community wiki part of our web site.
We didn't make it in time to have RPMs for Fedora, but with this release
we are having nightly builds, and we can get the RPMs in there easily
enough and perhaps once they pass long term testing, we can promote them
to the domwnload page.
In this regards I have few questions: we depend on libvirt to run
instances, and we are running into some problems. The first one is: how do
we give permission to the user eucalyptus to run instances? I think you
are using policykit, so how do we configure it correctly?
Also, we need to tell qemu-kvm to drop the console output in a file close
to where we run the instance, but we are having permissions problems. I
think that qemu is running as the user'qemu', so for now the quick fix was
to create the file in the right place, add the 'eucalyptus' user to the
'qemu' group and then start the instance. Is there a more elegant way?
Thanks for all feedback!
graziano
PS: I attach here the spec file after we did a first pass. Comments are
always welcomed of course.
On Thu, Feb 11, 2010 at 10:24:28AM -0600, Garrett Holmstrom wrote:
On Thu, Feb 11, 2010 at 1:46 AM, graziano obertelli
<graziano(a)eucalyptus.com> wrote:
> So, the reason's why Conflict is there, is beacause we need all the
> eucalyptus pacakges to be the same version. In our testing it happened
> that some older versions were left behind, making the experience failry
> miserable (failure modes in this case are very frustratring to chase). I
> can remove it, but how do I ensure that all eucalyptus pacakges installed
> are of the same version?
Just have every subpackage Require the main one with a versioned dependency:
Requires: %{name} = %{version}-%{release}
When one tries to update the main package the older subpackages'
dependencies will be unsatisfied, causing yum to pull in the new ones
to fix the problem. Conversely, when a subpackage is updated it will
require the newer version of the main package and pull it in.
> Does %global exists also in CentOS?
Yes.
> Hopefully I will have sometime tomorrow and over the weekend to work on
> the packaging and writing a better spec file (there are still quite a few
> point you mentioned that I have not tackled). Is that ok for me to post
> the spec file (once I get something which works) on this list to have more
> feedback?
I certainly wouldn't mind. Then again it isn't difficult to pull up
the current version in Bazaar either.
The euca2ools spec file from the tarballs doesn't work on Fedora at
all because it simply assumes the machine runs CentOS with Python 2.5.
Perhaps I can try working on a version that works but is still
relatively portable.
_______________________________________________
cloud mailing list
cloud(a)lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/cloud
--
Graziano Obertelli
Eucalyptus Systems, Inc.
130 Castilian St. Goleta, CA 93117
Office: 805-845-8000
www.eucalyptus.com