[Engine-devel] ovirt-engine build segfault on Fedora 20
by Greg Sheremeta
Caution on upgrading your dev machine to Fedora 20. GWT compilation of "safari" (for Chrome) causes a segfault during the build. Strangely, the build appears to work, so I'm not sure what the net effect of the segfault is.
If you only compile for gecko (Firefox) [the default], you won't see the segfault.
In other words,
make clean install-dev PREFIX=$HOME/ovirt-engine DEV_EXTRA_BUILD_FLAGS_GWT_DEFAULTS="-Dgwt.userAgent=gecko1_8,safari"
causes the segfault
But
make install-dev PREFIX="$HOME/ovirt-engine"
works just fine.
I've duplicated this with with both OpenJDK and Oracle JDK.
If you'd like to duplicate, simple install a fresh F20 VM, and then run these commands:
1 sudo yum install nano
2 sudo nano /etc/hostname #set the hostname
3 sudo nano /etc/hosts #set the hostname
5 sudo yum install http://ovirt.org/releases/ovirt-release-fedora.noarch.rpm
6 sudo yum install git java-devel maven openssl postgresql-server m2crypto python-psycopg2 python-cheetah python-daemon libxml2-python jboss-as unzip otopi
7 mkdir projects
8 cd projects/
9 git clone git://gerrit.ovirt.org/ovirt-engine
10 cd ovirt-engine/
11 make install-dev PREFIX="$HOME/ovirt-engine"
Greg Sheremeta
Red Hat, Inc.
Sr. Software Engineer, RHEV
Cell: 919-807-1086
gshereme(a)redhat.com
10 years, 9 months
[Engine-devel] New gerrit flags behavior
by David Caro
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--uBNWC8njJPiGVqbVGpsO04mklfCaCVaix
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Hi everyone!
With the latest gerrit upgrade it has become easier to add the propagatio=
n of
the Code Review and Verified flags when doing a trivial rebase or when no=
code
was changed, so I've enabled those features for all the projects!
The change should become effective right away, so let me know if you have=
any
issues.
Enjoy!
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Email: dcaro(a)redhat.com
Web: www.redhat.com
RHT Global #: 82-62605
--uBNWC8njJPiGVqbVGpsO04mklfCaCVaix
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJS6PjbAAoJEEBxx+HSYmnD8V4IAIBrbYSMUPTtqrCqg3A46p10
OQfOvb/hm8dGQ4AQ1kP/7GmNYwzk7GjJxVCKZkXfsAaxu3yFSByfjiS9Y/UVF6C+
qWxyBZrifUFFZFBrCEZWlcu+7DbeZaJpu4F2lMwloD/RbydqVm31iHc3X+N6WkUs
IglFQkXIWiCJANA3BAdtG0/vIzlOpU7thmBnJVdWUOdxpG0yYMWJwU96M1sxBcqm
sDPbVOlk7UHIs1sSSmQDoQOV+U0o3HtskM8wD4lm62ecPrpqYXQqd4W7TmjXGtcy
UYwVR5VRa2xnJp6UjxJnaTu2ibYpbBs0L+p5RLf7uNUy7aEmqhc9RysHQpD6CpY=
=91bd
-----END PGP SIGNATURE-----
--uBNWC8njJPiGVqbVGpsO04mklfCaCVaix--
10 years, 9 months
[Engine-devel] [QE] oVirt 3.4.0 beta status
by Sandro Bonazzola
Hi,
oVirt 3.4.0 beta has been released and is actually on QA.
We're going to tart composing oVirt 3.4.0 beta2 this Thursday 2014-02-06 09:00 UTC from 3.4 branches.
This build will be used for a second Test Day scheduled for 2014-02-11.
The bug tracker [1] shows the following bugs blocking the release:
Whiteboard Bug ID Status Summary
gluster 1038988 POST Gluster brick sync does not work when host has multiple interfaces
gluster 1059606 POST Errors in rebalance and remove-brick status and sync
integration 1054080 POST gracefully warn about unsupported upgrade from legacy releases
integration 1058018 POST upgrade from 3.3 overwrites exports with acl None
There are still 393 bugs [2] targeted to 3.4.0.
Excluding node and documentation bugs we still have 238 bugs [3] targeted to 3.4.0.
Please review them as soon as possible.
Maintainers:
- Please remember to rebuild your packages before 2014-02-06 09:00 UTC if you want them to be included in 3.4.0 beta.
- Please add the bugs to the tracker if you think that 3.4.0 should not be released without them fixed.
- Please provide ETA on blockers bugs
- Please update the target to 3.4.1 or any next release for bugs that won't be in 3.4.0:
it will ease gathering the blocking bugs for next releases.
- Please fill release notes, the page has been created here [4]
- Please update http://www.ovirt.org/OVirt_3.4_TestDay before 2014-02-11
For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug.
Please also be prepared for upcoming oVirt 3.4.0 Test Day on 2014-02-11!
Thanks to all people already testing 3.4.0 beta!
[1] https://bugzilla.redhat.com/1024889
[2] http://red.ht/1eIRZXM
[3] http://red.ht/1auBU3r
[4] http://www.ovirt.org/OVirt_3.4.0_release_notes
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 9 months
[Engine-devel] oVirt 3.3.3 release
by Sandro Bonazzola
The oVirt development team is very happy to announce the general
availability of oVirt 3.3.3 as of February 3rd 2013. This release
solidifies oVirt as a leading KVM management application and open
source alternative to VMware vSphere.
oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5
(or similar).
This release of oVirt includes numerous bug fixes.
See the release notes [1] for a list of the new features and bugs fixed.
IMPORTANT NOTE: If you're upgrading from a previous version, please update
ovirt-release to the latest version (10.0.1-3) and verify you have the correct
repositories enabled by running the following commands
# yum update ovirt-release
# yum repolist enabled
before upgrading with the usual procedure. You should see the ovirt-3.3.3 and
ovirt-stable repositories listed in the output of the repolist command.
A new oVirt Node build will be available soon as well.
[1] http://www.ovirt.org/OVirt_3.3.3_release_notes
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 9 months
[Engine-devel] oVirt January 2014 Updates
by Itamar Heim
1. VERSIONS
- oVirt 3.3.3 in last phases
http://www.ovirt.org/OVirt_3.3.3_release_notes
- oVirt 3.4 with another slew of features is getting into test day,
beta, etc.
http://red.ht/1eo9TiS
2. WORKSHOPS
- Fosdem - oVirt stand wass packed as well as a virt & IaaS devroom,
with many oVirt talks. more details next time.
- more oVirt talks in cfgmgmtcamp and infra.next this week, including:
-- Hervé Leclerc "How we build a cloud with CentOS, oVirt, and
Cisco-UCS" Wednesday 5th February in Infrastructure.Next Ghent
http://bit.ly/1fjTJVC
-- oVirt Node being used as a Discovery Node in The Foreman project
talk at cfgmgmtcamp, february 3rd
http://bit.ly/1gAnneI
- oVirt Korea group meeting this Saturday in Seoul
Register here http://onoffmix.com/event/23134
- Open Virtualization Workshop in Tehran (26,27 February 2014) &
Isfahan (5,6 March 2014)
http://t.co/9PR3BxOnpd
3. USING oVirt
- More details on Wind River using ovirt
http://bit.ly/1i2LtLI
- New Case Study: Nieuwland Geo-Informati
http://www.ovirt.org/Nieuwland_case_study
- oVirt Node being used as a Discovery Node in The Foreman project
talk at cfgmgmtcamp, february 3rd
http://bit.ly/1gAnneI
4. Users
- Double the amount of emails on users mailing list- up from 800 to
1600 this month!
- Karli updated how to use spice with ovirt from OS X
http://www.ovirt.org/SPICE_Remote-Viewer_on_OS_X
- Opaque (spice android ovirt client) v1.1.8 beta released
https://plus.google.com/communities/116099119712127782216
- how to deploy windows guest agent on windows:
http://bit.ly/1kr5tJo
- Andrew Lau posted on working through Hosted Engine with 3.4.0 beta
http://bit.ly/1eobzZw
- Deep Dive into oVirt 3.3.3 by Li Jiansheng (chinese)
http://slidesha.re/1eFWQ8G
- Matthew Bingham posted a series of video on setting up ovirt:
Install oVirt 3.3.2
http://www.youtube.com/watch?v=GWT-m-oWSjQ
Optional export nfs mount for oVirt 3.3.2
http://www.youtube.com/watch?v=MLbPln5-2jE
Initial webgui oVirt 3.3.2 Steps for storage
http://www.youtube.com/watch?v=dL0_03ZICw4
Download and upload client iso to ISO_DOMAIN for oVirt 3.3.2
http://www.youtube.com/watch?v=pDzTHFSmvGE
10 years, 9 months
[Engine-devel] [ANN] engine-manage-domains arguments changed
by Martin Perina
Hi,
patch, that changes engine-manage-domains command line arguments from Java type (-someOption)
to standard long type (--some-option), was merged today. Please consult man page or run
engine-manage-domains --help to find out differences.
Thanks
Martin Perina
10 years, 9 months
Re: [Engine-devel] mom RPMs for 3.4
by Sandro Bonazzola
Il 03/02/2014 09:35, Amedeo Salvati ha scritto:
>
> Da: arch-bounces(a)ovirt.org
> A: "Dan Kenigsberg" danken(a)redhat.com,"Adam Litke" alitke(a)redhat.com
> Cc: engine-devel(a)ovirt.org,"arch" arch(a)ovirt.org,"VDSM Project Development" vdsm-devel(a)lists.fedorahosted.org
> Data: Mon, 03 Feb 2014 08:50:12 +0100
> Oggetto: Re: mom RPMs for 3.4
>
>> Il 01/02/2014 23:48, Dan Kenigsberg ha scritto:
>> > On Fri, Jan 31, 2014 at 04:56:12PM -0500, Adam Litke wrote:
>> >> On 31/01/14 08:36 +0100, Sandro Bonazzola wrote:
>> >>> Il 30/01/2014 19:30, Adam Litke ha scritto:
>> >>>> On 30/01/14 18:13 +0000, Dan Kenigsberg wrote:
>> >>>>> On Thu, Jan 30, 2014 at 11:49:42AM -0500, Adam Litke wrote:
>> >>>>>> Hi Sandro,
>> >>>>>>
>> >>>>>> After updating the MOM project's build system, I have used jenkins to
>> >>>>>> produce a set of RPMs that I would like to tag into the oVirt 3.4
>> >>>>>> release. Please see the jenkins job [1] for the relevant artifacts
>> >>>>>> for EL6[2], F19[3], and F20[4].
>> >>>>>>
>> >>>>>> Dan, should I submit a patch to vdsm to make it require mom >= 0.4.0?
>> >>>>>> I want to be careful to not break people's environments this late in
>> >>>>>> the 3.4 release cycle. What is the best way to minimize that damage?
>> >>>>>
>> >>>>> Hey, we're during beta. I prefer making this requirement explicit now
>> >>>>> over having users with supervdsmd.log retate due to log spam.
>> >>>>
>> >>>> In that case, Sandro, can you let me know when those RPMs hit the
>> >>>> ovirt repos (for master and 3.4) and then I will submit a patch to
>> >>>> vdsm to require the new version.
>> >>>
>> >>>
>> >>> mom 0.4.0 has been built in last night nightly job [1] and published to nightly by publisher job [2]
>> >>> so it's already available on nightly [3]
>> >>>
>> >>> For 3.4.0, it has been planned [4] a beta 2 release on 2014-02-06 so we'll include your builds in that release.
>> >>
>> >> I presume the scripting for 3.4 release rpms will produce a version
>> >> without the git-rev based suffix: ie. mom-0.4.0-1.rpm?
>> >>
>> >> I need to figure out how to handle a problem that might be a bit
>> >> unique to mom. MOM is used by non-oVirt users who install it from the
>> >> main Fedora repository. I think it's fine that we are producing our
>> >> own rpms in oVirt (that may have additional patches applied and may
>> >> resync to upstream mom code more frequently than would be desired for
>> >> the main Fedora repository). Given this, I think it makes sense to
>> >> tag the oVirt RPMs with a special version suffix to indicate that
>> >> these are oVirt produced and not upstream Fedora.
>> >>
>> >> For example:
>> >> The next Fedora update will be mom-0.4.0-1.f20.rpm.
>> >> The next oVirt update will be mom-0.4.0-1ovirt.f20.rpm.
>> >>
>> >> Is this the best practice for accomplishing my goals? One other thing
>> >> I'd like to have the option of doing is to make vdsm depend on an
>> >> ovirt distribution of mom so that the upstream Fedora version will not
>> >> satisfy the dependency for vdsm.
>> >
>> > What is the motivation for this? You would not like to bother Fedora
>> > users with updates that are required only for oVirt?
>> >
>> > Vdsm itself is built, signed, and distributed via Fedora.
>> > It is also copied into the ovirt repo, for completeness sake. Could MoM
>> > do the same?
>>
>> IMHO, if we're distributing mom and vdsm rpms through Fedora yum repository we should not duplicate it on ovirt yum repository.
>> Fedora package is signed and will differ from the one we're shipping within ovirt repo (which is unsigned)
>> We should provide on resource.ovirt.org only packages not available on "downstream" repositories (like nightly builds).
>
> why you can't sign your rpms???
We're working on that :-)
>
> on ovirt web page http://www.ovirt.org/Home you can change:
>
> Enhanced security: SELinux and Mandatory Access Control for VMs and hypervisor
>
> with:
>
> Enhanced security: SELinux and Mandatory Access Control for VMs and hypervisor (but not signed rpms)
>
> best regards
> a
>
>>
>>
>> >
>> > Dan.
>> >
>>
>>
>> --
>> Sandro Bonazzola
>> Better technology. Faster innovation. Powered by community collaboration.
>> See how it works at redhat.com
>> _______________________________________________
>> Arch mailing list
>> Arch(a)ovirt.org
>> http://lists.ovirt.org/mailman/listinfo/arch
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 9 months
