oVirt 3.6.3 RC2 build starting in 1 hour
by Sandro Bonazzola
Fyi oVirt products maintainers,
An oVirt build for an official release is going to start in 1 hour.
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
9 years, 1 month
ovirt-node 3.5 jenkins jobs
by Tolik Litovsky
Hi
The current version is 3.6 and there is no more 3.5 releases.
Following these I disable the 3.5 build jobs on jenkins.
--
Best regards
Tolik Litovsky
RHEV-H Team
Red Hat
Red Hat: trustworthy, transformative technology. Powered by the community.
Connect at redhat.com
9 years, 1 month
oVirt 3.6.3 RC2 build starting
by Rafael Martins
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.
--
Rafael Martins
9 years, 1 month
missing "jinja2"??
by Martin Mucha
Hi,
if I try to run engine now, I'm getting following, even if jinja2 is (manually) installed. How to fix that?
File "/home/mmucha/build/ovirt-engine/share/ovirt-engine/services/ovirt-engine/ovirt-engine.py", line 26, in <module>
from jinja2 import Template
ImportError: cannot import name Template
thanks,
M.
9 years, 1 month
sync meeting - Vdsm 2.2
by Dan Kenigsberg
(nir, piotr, danken)
- splitting supervdsmServer:
I think that its a good idea, and that https://gerrit.ovirt.org/#/c/52875/ is a good start.
It would give a nice separation of responsibility, and may serve as a
"teaser" for how Vdsm's public API can be broken apart.
Nir is worried that it would introduce instability for no immediate gain,
while distracting us from solving the supervdsmServer memory leak, or
possible security concens
- schema conversion: Piotr presented his https://gerrit.ovirt.org/#/c/52864/
which would convert the json-based schema into a cleaner yaml-based one,
which would be easier to version, validate, and obsolete.
- Nir was unhappy with recent changes to the contrib client:
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic...
would prefer using standard stomp client
- name discussion is stalling. some people are worried that a rename may
turn out to be expensive (release engineering, outher packages,
interal module and function name). Still, it would be fun to foresake
the non-pronounceable name "vdsm". ovirt-hostd seems like a front
runner at the moment.
- Nir has advocated trying to use https://trello.com/b/U3lsbVRU/maintenance to
maintain the list of our pending tasks. Let's try.
Ciao!
9 years, 1 month
Bug 1267508 - [RFE] Replace python-cheetah with python-jinja2 within ovirt-engine
by Sandro Bonazzola
ovirt-engine has been using python-cheetah for handling the templates
used within the project.
python-cheetah didn't receive updates since 2012 and is not available
on RHEL 7.2.
Since we're dropping el6 support in 4.0 we are migrating to a template
engine available in el7: python-jinja2[1] which is
available in 7.2 and still actively developed.
A patch has been pushed and is currently under review[2].
Please be sure to havepython-jinja2 installed on your EL7 development system.
Thanks,
[1] http://jinja.pocoo.org/
[2] https://gerrit.ovirt.org/52885
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
9 years, 1 month
outdated quickstart guide
by Sven Kieske
--D2pWjDbpFSSm51uhA8xxHJCNvkCFChAEl
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Hi,
I'm just installing ovirt 3.6.2 in a new dev setup
and noticed that the quickstart guide still just
mentions 3.4 and 3.5:
https://www.ovirt.org/Quick_Start_Guide#Install_oVirt_Engine_.28Fedora_.2=
F_Red_Hat_Enterprise_Linux_.2F_CentOS.29
maybe this can get adjusted?
PS: Any ETA for ovirt 3.6.3 yet?
--=20
Mit freundlichen Gr=C3=BC=C3=9Fen / Regards
Sven Kieske
Systemadministrator
Mittwald CM Service GmbH & Co. KG
K=C3=B6nigsberger Stra=C3=9Fe 6
32339 Espelkamp
T: +495772 293100
F: +495772 293333
https://www.mittwald.de
Gesch=C3=A4ftsf=C3=BChrer: Robert Meyer
St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhause=
n
Komplement=C3=A4rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad
Oeynhausen
--D2pWjDbpFSSm51uhA8xxHJCNvkCFChAEl
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
iQIcBAEBAgAGBQJWq4HsAAoJEMby9TMDAbQRjjwP/2A+R4/ogm04xCeI1jaxLDYF
AUevH59BKRr/Z4WWcSOquNWLaDWYvj4xPBsftvPtsxATWqAvhJsoV+mbnNWduH0h
25ja5CsgsblPYSZ2A0yQ+cCz+Vvohh5haCh0niXNblKyDdy/ROpakkMIr1N1Svuj
WdTZJe2ODwFxPSBVFqfL9tbwuIa4SXTT5XDVwo4hxBzdcy6q3tEMGzXZ7Pw3x2zt
V9YggMbtYjr1iRzlUc7InFxIsqD1fIaD+1J3RY28ogK0GkV4yEPr2ue2c37hsmlX
+WtfYyJfH9MoVabhbjCLYqK6DrR7CgPFjVdW7zSl1xZFIcrx//v/2nCDSgAPGCKM
YCWATndf7kt2xMoa6CD0jsIhTaOsaGKMsutHn7Xo7dy2nW7tERecZ4NClm2j6YUf
8TR9znPehfRAnqPhHsOri1tuxDSHt/6OT/GqUm0X4cYaYiZkd6OZs6AlIL8MPIqc
Nb+rIEujTgHz8a1MuKSva4pcJgC6aKj9RkIdklpFk5qbF4kTL8qPkRGFfh0PWdRT
fhe0iCBf+NfoJyFjgUyoVTFkNbKh3+F1Sj37atD1vT18TPEE8GSmZYn310qRZxJN
EOSgBp8YkK1y6GvhjcZZAlgTFLAqyMHq8O7ZeIl4oux5b6xrUH8lR1PDMd5lWGsF
CBW4ecd9YEw6QKFVR+5H
=HGCI
-----END PGP SIGNATURE-----
--D2pWjDbpFSSm51uhA8xxHJCNvkCFChAEl--
9 years, 1 month
Changing the name of VDSM in oVirt 4.0.
by Yaniv Dary
Hi,
I wanted to bring this up to get feedback on this proposed change. VDSM
doesn't align to other project under the oVirt umbrella like ovirt-engine,
ovirt-node, ovirt-guest-agent etc..
I suggest for ease of use and tracking we change the versioning to align to
the engine (4.0.0 in oVirt 4.0 GA) to make it easy to know which version
was in which release and also change the package naming to something like
ovirt-host-manager\ovirt-host-agent.
What do you think on this? What do you think the name should be?
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
9 years, 1 month
