Jenkins overload and cancellation of ~1000 jobs
by David Caro
--kTN++mu+z+U/mv0o
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Hi everyone,
Earlier today there was a huge load peak in jenkins that ended up with
a job queue > 1000, we just removed from the queue most of the jobs to
avoid stop servicing other projects (like for example the jobs related
to releases and similar).
That means that a lot of patches (mostly ovirt-engine) might get -1 or
at least an error from jenkins, feel free to manually retrigger those
patches here [1]
[1] http://jenkins.ovirt.org/gerrit_manual_trigger/
Sorry for the inconveniences,
--=20
David Caro
Red Hat S.L.
Continuous Integration Engineer - EMEA ENG Virtualization R&D
Tel.: +420 532 294 605
Email: dcaro(a)redhat.com
IRC: dcaro|dcaroest@{freenode|oftc|redhat}
Web: www.redhat.com
RHT Global #: 82-62605
--kTN++mu+z+U/mv0o
Content-Type: application/pgp-signature; name="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJWngxhAAoJEEBxx+HSYmnD19wH/0/BSDKvPAt7M0T05n/dUiEZ
0xguxFMViuxG2OUPh7eS1PbD//r4AVB6J5SLWR1I3STK0ltf+XhRoJ9+3yPPjVFr
KkJp05djyxxQPYnsQ6GydspQeVRiuhic2lDmd1Vjx8XO4bz/bKK9dYnuvLLCIeL9
qmNPix7/x4wCr8K2eMza7UJaW0S+TL3AthzwIir7w25B5GyETDoRnig/sZsGw+VD
J6w9COFsEFVoMachGrvOE64cOD2CI0oK4Kb9xGolVJCIayzlnDy0zsaNYexJt/Cm
GHRgNovo4h6f7WV35q8Hd7nKOJKFriW/AYGnFLs8NjAChipFNdQdoIMPugwPWoU=
=k0X2
-----END PGP SIGNATURE-----
--kTN++mu+z+U/mv0o--
8 years, 10 months
[vdsm] New schema format proposal
by Piotr Kliczewski
I would like to propose new format for schema that we use in vdsm. I
started to work on a patch [1] where I explore how the new file should
look like. I have couple of goals which I would like to achieve by
doing this transformation:
1. I would like to use this file to verify engine code. Currently we
check only vdsm which leads to compatibility issues.
2. I would like to base new jsonrpc based replacement for vdsClient on
it. I want to create dynamic client which would use new format
(description used as help when calling verbs)
3. Simplify Bridge.py
4. Extend the schema to add events
5. Explore ideas around api evolution and contract definition.
Once we agree on the format I will work on script which will translate
one format to the other.
Thanks,
Piotr
[1] https://gerrit.ovirt.org/#/c/52404
8 years, 10 months
oVirt 3.6.2 RC3 build starting
by Sandro Bonazzola
Fyi oVirt products maintainers,
An oVirt build for an official release is going to start right now.
If you're a maintainer for any of the projects included in oVirt
distribution and you have changes in your package ready to be released
please:
- bump version and release to be GA ready
- tag your release within git (implies a GitHub Release to be automatically
created)
- build your packages within jenkins / koji / copr / whatever
- verify all bugs on MODIFIED have target release and target milestone set.
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
8 years, 10 months
oVirt Node Next - Sprint 2 Summary
by Fabian Deutsch
Hey,
during our second sprint, lasting 3 weeks, ending on January 15, the
Node team worked on the following items:
Add ovirt-release-host-node
---------------------------------------
This subpackage of ovirt-release now has all teh dependencies which
are expected to be available on node. In addition to vdsm, this
package also depends on cockpit and imgbased.
In addition this file carries systemd presets, to enable the relevant
services, it also provides the firewalld configuration of Node.
It also set's the VARIANT fields in teh os-release file to identify
node in a non-invasive way.
https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=tree;f=ovirt-releas...
Add branding to ovirt-release-host-node
--------------------------------------------------------
This is part of the next sprint but already completed: The release
file now also provides oVirt branding for cockpit!
https://gerrit.ovirt.org/gitweb?p=ovirt-release.git;a=tree;f=ovirt-releas...
Move imgbased to gerrit
-----------------------------------
imgbased is the component taking care of the image management on node.
Previously it was hosted on github, now it's on gerrit:
https://gerrit.ovirt.org/gitweb?p=imgbased.git
Yaml-ize imgbased and ovirt-node-ng jobs
------------------------------------------------------------
The ovirt-node-ng repository holds the image recipe (and nothing
else), this repo was created adn yaml-ized and is building on jenkins.
The job for imgbased was also yamlized and is alos building on jenkins:
http://jenkins.ovirt.org/job/imgbased_master_build-artifacts-el7-x86_64/
http://jenkins.ovirt.org/job/ovirt-node-ng_master_build-artifacts-fc23-x8...
Next
-------
In the next sprint - 3 - the team will focus on further stabilizing
the jenkins builds, creating the update rpm and creating the required
disk layout during installation.
The bottom line is that the ovirt-node-ng image is now regularly build
in u/s - still a bit flaky, but it's there. The squashfs can be used
for installing node, as described here:
http://lists.ovirt.org/pipermail/devel/2016-January/012073.html
On behalf of the Node team
fabian
8 years, 10 months
Hello statement on Ovirt VM.
by 신민수
------=_Part_281022_45727591.1453190793531
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: base64
77u/IEhlcmUgaXMgU291dGggS29yZWEuIEN1cnJlbnQgdGhyb3VnaCB0aGUgb3ZpcnQgZW5naW4g
eW91IHRyeSB0byBpbnN0YWxsIHRoZSBWTSBhZnRlciBjcmVhdGluZyBNaW50IE9TLiBOb3QgaW5z
dGFsbCB0aGUgc2NyZWVuIG1vdmVzIGR1cmluZyBzZXR1cCwgaXQgd2lsbCBzdG9wIGFzIGl0IGlz
LiBXZSB3aWxsIGxldCB5b3Uga25vdyB5b3UgZG8gbm90IGhhdmUgdGhlIHN1cHBvcnQgZm9yIHBv
c3NpYmx5IGlzIE9uY2UgZnJvbSBvdmlydCBlbmdpbiBtaW50IG9zLiBXZWJzaXRlIGFkZHJlc3Mg
b2YgbWludCBPUyBpcywgaHR0cDogLy9oYW1vbmlrci5vcmcvIGlzIGhlcmUuIFdpdGhvdXQgZG93
bmxvYWQgYW5kIGluc3RhbGwgdGhlIExpdmUgQ0QsIHdlIHdpbGwgY29udGFjdCB5b3UuIENvdWxk
IHlvdSBwbGVhc2UgY29uZmlybS4gVGhhbmsgeW91IHZlcnkgbXVjaC4gCiAgCj09PT09PT09PT09
PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PQoo7KO8KeqwleybkOyLnOyKpO2FnCDs
mIHrj5nsp4Dsgqwg7Iug66+87IiYIOuMgOumrApUZWwgOiAwMzMtNjMxLTg1MDEsIDg1MDIgCkZh
eCA6IDAzMy02MzEtODUwMwpNb2IgOiAwMTAtODcxMy0xMzE0IAplLW1haWwgOiBtc3NoaW5Aa3dz
eXN0ZW0uY28ua3IKbXNzaGluQG5hdmVyLmNvbQphZGQgOiDqsJXsm5Drj4Qg7IaN7LSI7IucIOq1
kOuPmSA3MzctNyDslYTrgqjtlITrnbzsnpAgMTMxNO2YuCAKKOyjvCnqsJXsm5Dsi5zsiqTthZwg
7JiB64+Z7KeA7IKsCj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PQ==
------=_Part_281022_45727591.1453190793531
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64
PGh0bWw+PGhlYWQ+PHN0eWxlPnB7bWFyZ2luLXRvcDowcHg7bWFyZ2luLWJvdHRvbTowcHg7fTwv
c3R5bGU+PC9oZWFkPjxib2R5PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZToxMHB0OyBmb250LWZhbWls
eTpHdWxpbTsiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDEwcHQ7Ij7vu788L3NwYW4+IDxzcGFu
IGNsYXNzPSJocHMiPkhlcmU8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmlzPC9zcGFuPiA8c3Bh
biBjbGFzcz0iaHBzIj5Tb3V0aCBLb3JlYTwvc3Bhbj48c3Bhbj4uPC9zcGFuPiA8c3BhbiBjbGFz
cz0iaHBzIj5DdXJyZW50PC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj50aHJvdWdoIHRoZTwvc3Bh
bj4gPHNwYW4gY2xhc3M9ImhwcyI+b3ZpcnQgZW5naW48L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMi
PnlvdSB0cnkgdG88L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmluc3RhbGw8L3NwYW4+IDxzcGFu
IGNsYXNzPSJocHMiPnRoZTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+Vk08L3NwYW4+IDxzcGFu
IGNsYXNzPSJocHMiPmFmdGVyIGNyZWF0aW5nPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5NaW50
IE9TLjwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+Tm90PC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBz
Ij5pbnN0YWxsPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj50aGUgc2NyZWVuPC9zcGFuPiA8c3Bh
biBjbGFzcz0iaHBzIj5tb3Zlczwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+ZHVyaW5nIHNldHVw
PC9zcGFuPjxzcGFuPiw8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPml0PC9zcGFuPiA8c3BhbiBj
bGFzcz0iaHBzIj53aWxsIHN0b3A8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmFzIGl0IGlzPC9z
cGFuPjxzcGFuPi48L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPldlIHdpbGwgbGV0IHlvdSBrbm93
PC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj55b3UgZG8gbm90IGhhdmU8L3NwYW4+IDxzcGFuIGNs
YXNzPSJocHMiPnRoZTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+c3VwcG9ydDwvc3Bhbj4gPHNw
YW4gY2xhc3M9ImhwcyI+Zm9yPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5wb3NzaWJseTwvc3Bh
bj4gPHNwYW4gY2xhc3M9ImhwcyI+aXM8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPk9uY2U8L3Nw
YW4+IDxzcGFuIGNsYXNzPSJocHMiPmZyb208L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPm92aXJ0
IGVuZ2luIG1pbnQgb3MuPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5XZWJzaXRlPC9zcGFuPiA8
c3BhbiBjbGFzcz0iaHBzIj5hZGRyZXNzPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5vZjwvc3Bh
bj4gPHNwYW4gY2xhc3M9ImhwcyI+bWludDwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+T1M8L3Nw
YW4+IDxzcGFuIGNsYXNzPSJocHMiPmlzPC9zcGFuPjxzcGFuPiwgaHR0cDogLy9oYW1vbmlrci5v
cmcvPC9zcGFuPiA8c3BhbiBjbGFzcz0iaHBzIj5pcyBoZXJlPC9zcGFuPjxzcGFuPi48L3NwYW4+
IDxzcGFuIGNsYXNzPSJocHMiPldpdGhvdXQ8L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPmRvd25s
b2FkIGFuZCBpbnN0YWxsIHRoZTwvc3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+TGl2ZSBDRCw8L3Nw
YW4+IDxzcGFuIGNsYXNzPSJocHMiPndlIHdpbGwgY29udGFjdCB5b3U8L3NwYW4+PHNwYW4+Ljwv
c3Bhbj4gPHNwYW4gY2xhc3M9ImhwcyI+Q291bGQgeW91IHBsZWFzZSBjb25maXJtPC9zcGFuPjxz
cGFuPi48L3NwYW4+IDxzcGFuIGNsYXNzPSJocHMiPlRoYW5rIHlvdSB2ZXJ5IG11Y2guPC9zcGFu
PjxwPiZuYnNwOzwvcD4gPHA+Jm5ic3A7PC9wPj09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PT09PT09PTxicj4o7KO8KeqwleybkOyLnOyKpO2FnCDsmIHrj5nsp4Dsgqwg7Iug
66+87IiYIOuMgOumrDxicj5UZWwgOiAwMzMtNjMxLTg1MDEsIDg1MDIgPGJyPkZheCA6IDAzMy02
MzEtODUwMzxicj5Nb2IgOiAwMTAtODcxMy0xMzE0IDxicj5lLW1haWwgOiBtc3NoaW5Aa3dzeXN0
ZW0uY28ua3I8YnI+bXNzaGluQG5hdmVyLmNvbTxicj5hZGQgOiDqsJXsm5Drj4Qg7IaN7LSI7Iuc
IOq1kOuPmSA3MzctNyDslYTrgqjtlITrnbzsnpAgMTMxNO2YuCA8YnI+KOyjvCnqsJXsm5Dsi5zs
iqTthZwg7JiB64+Z7KeA7IKsPGJyPj09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09PT09
PT09PT09PT09PTwvZGl2PjwvYm9keT48L2h0bWw+Cjx0YWJsZSBzdHlsZT0iZGlzcGxheTpub25l
Ij48dHI+PHRkPjxpbWcgc3JjPSJodHRwOi8vbWFpbC5uYXZlci5jb20vcmVhZFJlY2VpcHQvbm90
aWZ5Lz9pbWc9ODlSb1d6a05XNHU5aEFubUtIM0NLenRsSzR1cnBBS3dGb0MwTXFNbGF4dW1GenVs
TXFVckZxSTRGeDBTdHpGWHA2VVpLU2w1V0xsNTF6bHFEQkZkcDZkNU1yZVJob1J2cEJwMFd1SW4x
QkZkYlpsVCUyQjQwWiUyQlZsVGI0YiUzRC5naWYiIGJvcmRlcj0iMCI+PC90ZD48L3RyPjwvdGFi
bGU+
------=_Part_281022_45727591.1453190793531--
8 years, 10 months
Topic for next Vdsm call - 19.1
by Yaniv Bronheim
Things I plan to raise. feel free to add more
1. Plans to handle async processes without using death signal.
2. Vdsm messaging - I'll ask Piotr to elaborate about infra plans for that
topic (what about the external broker plans? any standard plan to
communicate with vdsm? such as for supervdsm and mom).
3. Contract for events and new apis - where it stands.
4. py.test - If someone can pick up the migration to py test
--
*Yaniv Bronhaim.*
8 years, 10 months
Subject: Looking for advice regarding user portal development.
by Thomas Shaw
Evening all,
I'm a student from the UK, currently studying Bsc (Hons) Computer Forensics
& Security, looking for a bit of advice regarding front-end development for
the oVirt user portal. For my final year project I’m going to be extending
the current user portal to produce a user interface that fits the needs of
Computer Security education.
I want to create an interface that supports the workflow of a tutor
configuring one to many virtual machines / networks for a scenario based
lab session. The project will involve developing two different interfaces
depending on whether a student or tutor is logged in.
The project is going to be based on a paper that was presented in the UK at
the first Cybersecurity Education and Training conference as part of the
Vibrant Workshop, and is available in full here:
http://z.cliffe.schreuders.org/publications/VibrantWorkshop2015%20-%20An%...
The tutor portal will have an avenue for tutors to upload images and a way
to group templates of virtual machines for students to clone. The student
portal will have one webpage with a list of their owned VMs on the left,
like the current user portal, and all lab VM templates on the right
organised/grouped by lab. Students will be able to clone a VM or group of
VM's from the right with a couple of clicks at most.
I'm planning on forking the user-portal code and making changes here. I
want a different interface to appear for the students and the tutors.
Initial thoughts were to do this based on the 'Role' concept within oVirt -
I plan on creating 2 new user group’s with predefined roles, Student and
Tutor, and having the tutor-only functionality appear on an additional tab
which only appears if the logged in user has the Tutor role.
We have a powerful development server at university which is currently
running oVirt 3.6 with 3 nodes. As of right now I've set up the engine
development environment on Fedora 23. I'm still getting familiar with the
code and build process and have not yet deployed a build to the server.
It is my hope and intention that any work I produce will be of value to the
greater community and will open source all work. I would really appreciate
any input / advice in developing for the user portal and hope to produce
something make my code changes more likely to be accepted upstream.
Thanks for reading,
Thomas Shaw
8 years, 10 months
oVirt 3.6.2 RC3 merge / tag / bugzilla reminder
by Sandro Bonazzola
All stable branch maintainers, please make sure to
- merge all relevant open bugs until tuesday morning 11:00 AM TLV time.
-
https://bugzilla.redhat.com/buglist.cgi?quicksearch=target_milestone%3A3....
Every package build (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-3.6.2.6, tr: 3.6.2.6)
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
8 years, 10 months
[ANN] Team in Whiteboard is not more, long live oVirt Team custom field.
by Yaniv Dary
Hi All,
For a long time now we have been using the whiteboard free-text field to
set the team that owns each ticket in Bugzilla. This causes several issues:
- The usage was not documented.
- We had issue reporting on that field.
- People can make mistakes setting it (mis-spelling the team for example).
Today Bugzilla team has completed setting oVirt Team field for all open
bugs (NEW-> VERIFIED). From today we will be moving to using it. The
documentation for this field is updated in Bugzilla, so if you are not sure
on what team to set the ticket, click on the field itself and you will have
a detailed help page.
Please update all queries to use it! It should be easy to do so by changing
the field you search on from 'Whiteboard' to 'oVirt Team'.
Next Tuesday (26/01/16) I will request removal of all whiteboard team
values. Please make sure to fix you queries beforehand.
Thanks!
Yaniv Dary
Technical Product Manager
Red Hat Israel Ltd.
34 Jerusalem Road
Building A, 4th floor
Ra'anana, Israel 4350109
Tel : +972 (9) 7692306
8272306
Email: ydary(a)redhat.com
IRC : ydary
8 years, 10 months
