planned jenkins and resources downtime
by Evgheni Dereveanchin
Hi everyone,
As part of a planned maintenance window I am going to
apply OS updates and reboot the Jenkins master along
with our resources file server.
Affected services:
jenkins.ovirt.org
resources.ovirt.org
This means that no new jobs will be started on the Jenkins
and our repositories will be unavailable for a short
period of time.
I will follow up on this email once all services
are back up and running.
Regards,
Evgheni Dereveanchin
7 years, 5 months
Re: [ovirt-devel] [JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
by Vojtech Szocs
Hi,
> Any patches sent on this?
I'd like to help.
Looking at the recent Engine (master) build:
http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_...
$ rpm -qlp ovirt-engine-webadmin-portal-4.1.0-0.0.master.20161125171318.gitae69c34.el7.centos.noarch.rpm
it shows we still build all [browser x language] GWT permutations,
basically there are tons of <md5>.cache.js files in `webadmin.war`
directory (each one represents a single permutation).
In automation/build-artifacts.sh, we could add some variable that
controls what kind of GWT build to do (e.g. GWT_BUILD_MODE):
1, snapshot GWT build: all supported browsers x en_US (only)
=> 3 x 1 = 3 GWT permutations
2, full GWT build: all supported browsers x all supported locales
=> 3 x 9 = 27 (!) GWT permutations
With "snapshot GWT build", we should do:
rpmbuild \
.. existing stuff
-D "ovirt_build_locales 0" \
.. existing stuff
GWT_BUILD_MODE can default to "full GWT build".
But how do we override GWT_BUILD_MODE when doing non-release builds?
Regards,
Vojtech
----- Original Message -----
> From: "eyal edri [Administrator] (oVirt JIRA)" <jira(a)ovirt-jira.atlassian.net>
> To: infra(a)ovirt.org
> Sent: Sunday, November 6, 2016 4:29:02 PM
> Subject: [JIRA] (OVIRT-416) [standard-ci] build-artifacts should reuse the artifacts built on check-merged if any
>
>
> [
> https://ovirt-jira.atlassian.net/browse/OVIRT-416?page=com.atlassian.jira...
> ]
>
> eyal edri [Administrator] commented on OVIRT-416:
> -------------------------------------------------
>
> Any patches sent on this?
> Also, wanted to mention #OVIRT-751 is handling similar purpose with enabling
> better maven caching, so it might suffice as a starting point in optimizing
> ovirt-engine runtime for builds.
>
> > [standard-ci] build-artifacts should reuse the artifacts built on
> > check-merged if any
> > -------------------------------------------------------------------------------------
> >
> > Key: OVIRT-416
> > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-416
> > Project: oVirt - virtualization made easy
> > Issue Type: Improvement
> > Reporter: David Caro Estevez
> > Assignee: infra
> >
> > Right now most projects just rebuild twice the artifacts, what for some
> > means a big waste of resources, if we could just reuse what was built
> > previously there would be no rebuilding.
> > Something to take into account is that the distributions that check-merged
> > and build-artifacts run for might not match, so you can be running
> > check-merged only on fc23 but building artifacts for fc23, fc22 an el7 (as
> > an example), maybe we should not allow different distros on each stage?|
>
>
>
> --
> This message was sent by Atlassian JIRA
> (v1000.499.4#100018)
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
7 years, 5 months
oVirt 4.1.0 beta1 compose planned
by Sandro Bonazzola
Fyi oVirt developers,
An oVirt compose is planned for this Thursday 11:00 AM TLV time (10:00 AM
CET).
Please note this will be the first oVirt 4.1 beta compose and will be done
taking master snapshot in its state at compose time. If you've pending
fixes to be published please ping me at least 40 minutes before the
scheduled time.
A list of pending blockers is available here:
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4....
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 5 months
Create soft-host-to-vm-affinity-support feature
by Yanir Quinn
Hi,
I have posted a pull request for soft-host-to-vm-affinity-support feature :
https://github.com/oVirt/ovirt-site/pull/611
The feature comes to support the following use case:
*Certain set of VMs form a logical management unit should run on a certain
set of hosts for SLA or management (e.g. a separate rack for each
customer). The VMs can run anywhere in case the dedicated rack needs to be
turned off, but should return to their dedicated hosts once the rack is
back up.*
comments/remarks/other suggestions will be appreciated.
--
Yanir Quinn
SLA / ovirt
7 years, 5 months
[Call for Vote] moVirt as a Full oVirt Project
by Brian Proffitt
All:
The moVirt Project was initially accepted as an oVirt incubator project in
February 2015. It has been a successful subproject for quite some time and
it is well due for being accepted as a full oVirt project. I believe it is
appropriate to post a Call for Vote on the Devel and Board lists.
http://www.ovirt.org/develop/projects/project-movirt/
A “healthy” project, as determined by the oVirt Board, can be found at
http://www.ovirt.org/develop/projects/adding-a-new-project/
Voting will be open until 1200 UTC Nov. 30, 2016. A net total of +7 votes
should be received to formalize this project as an full oVirt project.
Please use the following vote process:
+1
Yes, agree, or the action should be performed. On some issues, this vote
must only be given after the voter has tested the action on their own
system(s).
±0
Abstain, no opinion, or I am happy to let the other group members decide
this issue. An abstention may have detrimental affects if too many people
abstain.
-1
No, I veto this action. All vetos must include an explanation of why the
veto is appropriate. A veto with no explanation is void.
Thank you!
Brian Proffitt
Principal Community Analyst
Open Source and Standards
@TheTechScribe
574.383.9BKP
7 years, 5 months
oVirt 4.0.6 RC3 merge / branch / tag / bugzilla reminder
by Sandro Bonazzola
All stable branch maintainers, please make sure to
merge all relevant open bugs until Wednesday morning 11:00 AM TLV time
(10:00 AM CET).
For each package that need to be built (i.e oVirt product) please make sure
every bug in MODIFIED has the right Target Release and Target Milestone.
A Target release should state the version of the package you're building
and should include the same version you used for the tag you just used for
this build. (e.g. for ovirt-engine, tag: ovirt-engine-4.0.6, tr: 4.0.6)
A list of bugs that require attention is here:
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4....
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 5 months
oVirt 4.0.6 RC3 build planned
by Sandro Bonazzola
Fyi oVirt developers,
An oVirt build is planned for this Wednesday 11:00 AM TLV time (10:00 AM
CET).
Taking into consideration the time it takes for Jenkins to run a full CI
everything need to be backported by Tuesday 11PM.
Please make sure to mark as verified and CR +2 so it will be ready for
merging Wednesday morning.
A list of pending blockers is available here:
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A4....
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
7 years, 5 months
[VDSM] Flaky network tests
by Nir Soffer
Hi all,
I'm seeing new random network test failures - see bellow.
The interesting thing is I don't see these errors at all in travis.
Maybe mark this as brokne_on_ci?
21:35:54 ======================================================================
21:35:54 ERROR: test_event_groups
(network.netlink_test.NetlinkEventMonitorTests)
21:35:54 ----------------------------------------------------------------------
21:35:54 Traceback (most recent call last):
21:35:54 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/testValidation.py",
line 97, in wrapper
21:35:54 return f(*args, **kwargs)
21:35:54 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/tests/network/netlink_test.py",
line 94, in test_event_groups
21:35:54 for event in mon_a:
21:35:54 File
"/home/jenkins/workspace/vdsm_master_check-patch-fc24-x86_64/vdsm/lib/vdsm/network/netlink/monitor.py",
line 115, in __iter__
21:35:54 raise MonitorError(E_TIMEOUT)
21:35:54 MonitorError: 2
21:35:54 -------------------- >> begin captured logging << --------------------
21:35:54 2016-11-27 21:35:18,631 DEBUG (MainThread) [root]
/usr/bin/taskset --cpu-list 0-3 /sbin/ip link add name dummy_0JsyI
type dummy (cwd None) (commands:69)
21:35:54 2016-11-27 21:35:18,944 DEBUG (MainThread) [root] SUCCESS:
<err> = ''; <rc> = 0 (commands:93)
21:35:54 2016-11-27 21:35:18,962 DEBUG (MainThread) [root]
/usr/bin/taskset --cpu-list 0-3 /sbin/ip -4 addr add dev dummy_0JsyI
192.0.2.1/24 (cwd None) (commands:69)
21:35:54 2016-11-27 21:35:19,342 DEBUG (MainThread) [root] SUCCESS:
<err> = ''; <rc> = 0 (commands:93)
21:35:54 2016-11-27 21:35:19,353 DEBUG (MainThread) [root]
/usr/bin/taskset --cpu-list 0-3 /sbin/ip link set dev dummy_0JsyI up
(cwd None) (commands:69)
21:35:54 2016-11-27 21:35:19,649 DEBUG (MainThread) [root] SUCCESS:
<err> = ''; <rc> = 0 (commands:93)
21:35:54 2016-11-27 21:35:19,661 DEBUG (MainThread) [root]
/usr/bin/taskset --cpu-list 0-3 /sbin/ip link del dev dummy_0JsyI (cwd
None) (commands:69)
21:35:54 2016-11-27 21:35:19,948 DEBUG (MainThread) [root] SUCCESS:
<err> = ''; <rc> = 0 (commands:93)
21:35:54 --------------------- >> end captured logging << ---------------------
7 years, 5 months
