----- Original Message -----

From: "Eyal Edri" <eedri@redhat.com> To: "Simone Tiraboschi" <stirabos@redhat.com> Cc: "Tal Nisan" <tnisan@redhat.com>, "Piotr Kliczewski" <pkliczew@redhat.com>, "Dan Kenigsberg" <danken@redhat.com>, "Yaniv Bronheim" <ybronhei@redhat.com>, "Nir Soffer" <nsoffer@redhat.com>, "Juan Antonio Hernandez Fernandez" <juan.hernandez@redhat.com>, "Shirly Radco" <sradco@redhat.com>, "Yedidyah Bar David" <didi@redhat.com>, "Martin Sivak" <msivak@redhat.com>, "Francesco Romani" <fromani@redhat.com>, "Fabian Deutsch" <fdeutsch@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com>, "Lev Veyde" <lveyde@redhat.com>, "Rafael Martins" <rmartins@redhat.com>, "David Caro Estevez" <dcaro@redhat.com>, "devel" <devel@ovirt.org> Sent: Tuesday, June 14, 2016 4:32:19 PM Subject: Re: [ovirt-devel] oVirt 4.0 Nightly repo

example of what should have been done for vdsm: https://gerrit.ovirt.org/#/c/59168/

any of the project maintainers should check if his project has build for 4.0 in addition to master and update the same file as needed.

I posted this for ovirt-vmconsole: https://gerrit.ovirt.org/#/c/59158/ -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

----- Original Message -----

From: "Eyal Edri" <eedri@redhat.com> To: "Francesco Romani" <fromani@redhat.com> Cc: "Simone Tiraboschi" <stirabos@redhat.com>, "Tal Nisan" <tnisan@redhat.com>, "Piotr Kliczewski" <pkliczew@redhat.com>, "Dan Kenigsberg" <danken@redhat.com>, "Yaniv Bronheim" <ybronhei@redhat.com>, "Nir Soffer" <nsoffer@redhat.com>, "Juan Antonio Hernandez Fernandez" <juan.hernandez@redhat.com>, "Shirly Radco" <sradco@redhat.com>, "Yedidyah Bar David" <didi@redhat.com>, "Martin Sivak" <msivak@redhat.com>, "Fabian Deutsch" <fdeutsch@redhat.com>, "Sandro Bonazzola" <sbonazzo@redhat.com>, "Lev Veyde" <lveyde@redhat.com>, "Rafael Martins" <rmartins@redhat.com>, "David Caro Estevez" <dcaro@redhat.com>, "devel" <devel@ovirt.org> Sent: Tuesday, June 14, 2016 4:37:55 PM Subject: Re: [ovirt-devel] oVirt 4.0 Nightly repo

You don't need to do it francesco if vmconsole doesn't have a 4.0 branch (i saw you're still using master ?)

Yes, ovirt-vmconsole is tagged abd build from master.

In any case, see my previous patch which updates the publisher to publish the 4.0 rpms that the 4.0 build artifacts for vdsm is creating rather than master rpms.

Sure, will review, thanks for your patch. Bests, -- Francesco Romani RedHat Engineering Virtualization R & D Phone: 8261328 IRC: fromani

--JHITMubKSiIoiKCLExJ8foN2FBRtH0Q35 Content-Type: multipart/mixed; boundary="qrv430rJEi23QIbTFEhlgaaoflBObNa5w" From: Sven Kieske <s.kieske@mittwald.de> To: devel@ovirt.org Message-ID: <57626BFE.9040707@mittwald.de> X-Authenticated-mymxserver.com: Yes Subject: Re: [ovirt-devel] oVirt 4.0 Nightly repo References: <CAN8-ONooie-Qop2dPfthaatk=Lacqpq1St9Yg_vy0gROipG-XA@mail.gmail.com> <1616714012.70895771.1465918472171.JavaMail.zimbra@redhat.com> In-Reply-To: <1616714012.70895771.1465918472171.JavaMail.zimbra@redhat.com> --qrv430rJEi23QIbTFEhlgaaoflBObNa5w Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 14/06/16 17:34, Vojtech Szocs wrote:

Hi, =20 ovirt-engine-dashboard is currently built from master as well. =20 We should probably create a stable branch, e.g. ovirt-engine-dashboard-= 1.0.

Hi, speaking as an end user (mostly): please not yet-another-versioning in the great ovirt project. I'm already having severe issues tracking which engine versions works with which vdsm version, let alone track which datacenter and cluster version within each engine version works with which vdsm version and which features are (un)supported. Please don't add another different version to the already far to complex equation. I'd suggest you take the same version number as the supported ovirt-engine, you also should adjust release cycles of all the subprojects where possible (I know that doesn't work always). this would make every users life make so much less painful. keep up the great work! --=20 Mit freundlichen Gr=FC=DFen / Regards Sven Kieske Systemadministrator Mittwald CM Service GmbH & Co. KG K=F6nigsberger Stra=DFe 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Gesch=E4ftsf=FChrer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhause= n Komplement=E4rin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynha= usen --qrv430rJEi23QIbTFEhlgaaoflBObNa5w-- --JHITMubKSiIoiKCLExJ8foN2FBRtH0Q35 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) iQIcBAEBAgAGBQJXYmv+AAoJEMby9TMDAbQRfHAQAK3GwYF9uVVcjwBjGquLAojb DGHpyAL7vRAeI3p36b5SyqNIwa2Cu1EZ7EXmsjkx9vVdbK++eIFo+yrwsptBBb/L kGQ7gDv3CzyJWMIknsLtwiQzPdiiB+wv/ypXEr5RJTi13AEnjK+mZ3E1rgtKD3t9 nuJlkap/zMauvCHpGzX6Sltrc9oIwBeXlgrrRpHuZ2/LEOG5gzBHmDwkSPQrJz/A l0W56rIPJCIn9dU/7rXTEur5c0fpIHg0G8DyMWo+GM86o2iwzGu74ZdzcmB5IKZy Soy3w/H4Hm84tmAEgGwjVqogbb4y3XWljWI95zC2I92Mbxcoqw4ubSeCk/5rY6it mW0Bud/bGU+3+hpn6yBGT69hUCmXy4Tt9U6o4ifVnXem4Y6GZ9e1rd4M2pQjKaEb MoznU3DIbpAKUUhJ6jMhMZaqCQexy/7kZJe2NckI19rWnXn7wkAFQa7Gidn/DMoz 9qbfYRKo4ieKnMunrXQK8mdAAaHLjSTIpqgMFjiW98QEzbbvLO0sDp/54Sm7t6Hl 43f/ic8Eoz+pONPGkVsYxwuLoaDlVd+P19UYTa6eDGEzRJhcDruDQrJ8zIdANCGz LIhG2XhbvxOJFXsTR95DaM925s4e9EpcAIV/qT1Zm95EvaG68y0O5dCdwStvx5rD 91iOJajFFlIUNol1Q3Zk =U4vF -----END PGP SIGNATURE----- --JHITMubKSiIoiKCLExJ8foN2FBRtH0Q35--

I'm not sure what you mean or which versions you're referring to. Like every project there is the 'master' branch and nightlies which is latest and greatest (and probably the least stable, but still go over heavy CI tests). The oVirt project reached a point when the next stable major version (4.0) is nearing GA, and part of the process is to branch it to create rpms for it, in order to continue developing 4.1 (now master) and not to merge new features that may risk 4.0 stability the new branch has to be created. You as user/developer has the choice to choose which version to use, according to you needs: for e.g, at this time point, you choices are: 1. Use current stable: 3.6 rpms - most stable, only gets specific fixes and not major features - recommended for a production usage and if you don't need any of the new features [1] 2. Use current RC candidate for next major 4.0, which should be the next stable version soon and replace 3.6 as the latest stable version [2] 3. Use nightlies for every version - either 4.0, master, 3.6 - use at your own risk since these are not official releases and not going via extensive QA, although the automated tests for each version are improving over time and make the nightlies more and more stable. [3] Just to help better undertand, if you'll make the same decision in one more months for e.g, after 4.0 is GA, you choices will be: 1. use current stable 4.0 (unless you really want to use older 3.6) 2. use nightlies So the extra versions are temp version that are part of the development process and actually gives you an oppertunity to check out new features that are not available yet in a formal stable version. I hope it gives some info on the diff between all the versions. [1]. http://resources.ovirt.org/pub/ovirt-3.6/ [2] http://resources.ovirt.org/pub/ovirt-4.0-pre/ [3] http://resources.ovirt.org/pub/ovirt-4.0-snapshot(+-static), http://resources.ovirt.org/pub/ovirt-master-snapshot(+static) On Thu, Jun 16, 2016 at 12:16 PM, Vinzenz Feenstra <vfeenstr@redhat.com> wrote:

...

On Jun 16, 2016, at 11:06 AM, Sven Kieske <S.Kieske@mittwald.de> wrote:

On 14/06/16 17:34, Vojtech Szocs wrote:

...

Hi,

ovirt-engine-dashboard is currently built from master as well.

We should probably create a stable branch, e.g. ovirt-engine-dashboard-1.0.

Hi,

speaking as an end user (mostly):

please not yet-another-versioning in the great ovirt project.

I'm already having severe issues tracking which engine versions works with which vdsm version, let alone track which datacenter and cluster version within each engine version works with which vdsm version and which features are (un)supported.

Please don't add another different version to the already far to complex equation. +1 :-)

I'd suggest you take the same version number as the supported ovirt-engine, you also should adjust release cycles of all the subprojects where possible (I know that doesn't work always).

this would make every users life make so much less painful.

keep up the great work!

-- Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

-- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

Hi everyone, I think Sven was referring specifically to oVirt Dashboard component of oVirt Engine product. Dashboard (UI plugin) has its own repo [1] [1] https://gerrit.ovirt.org/#/admin/projects/ovirt-engine-dashboard with dedicated Jenkins job to build its RPM. When Engine is installed, Dashboard RPM is *automatically* installed & updated as well. You don't have to worry about tracking Dashboard RPM version installed on machine running your Engine. Dashboard is technically part of Engine because it relies on Engine UI plugin infra, it's not "standalone" like VDSM. TL;DR the fact that Dashboard has its own RPM shouldn't impact users, it's a logical part of Engine. Regards, Vojtech ----- Original Message -----

From: "Eyal Edri" <eedri@redhat.com> To: "Vinzenz Feenstra" <vfeenstr@redhat.com> Cc: "Unname" <devel@ovirt.org> Sent: Thursday, June 16, 2016 3:11:51 PM Subject: Re: [ovirt-devel] oVirt 4.0 Nightly repo

I'm not sure what you mean or which versions you're referring to. Like every project there is the 'master' branch and nightlies which is latest and greatest (and probably the least stable, but still go over heavy CI tests). The oVirt project reached a point when the next stable major version (4.0) is nearing GA, and part of the process is to branch it to create rpms for it, in order to continue developing 4.1 (now master) and not to merge new features that may risk 4.0 stability the new branch has to be created.

You as user/developer has the choice to choose which version to use, according to you needs: for e.g, at this time point, you choices are:

1. Use current stable: 3.6 rpms - most stable, only gets specific fixes and not major features - recommended for a production usage and if you don't need any of the new features [1] 2. Use current RC candidate for next major 4.0, which should be the next stable version soon and replace 3.6 as the latest stable version [2] 3. Use nightlies for every version - either 4.0, master, 3.6 - use at your own risk since these are not official releases and not going via extensive QA, although the automated tests for each version are improving over time and make the nightlies more and more stable. [3]

Just to help better undertand, if you'll make the same decision in one more months for e.g, after 4.0 is GA, you choices will be:

1. use current stable 4.0 (unless you really want to use older 3.6) 2. use nightlies

So the extra versions are temp version that are part of the development process and actually gives you an oppertunity to check out new features that are not available yet in a formal stable version. I hope it gives some info on the diff between all the versions.

[1]. http://resources.ovirt.org/pub/ovirt-3.6/ [2] http://resources.ovirt.org/pub/ovirt-4.0-pre/ [3] http://resources.ovirt.org/pub/ovirt-4.0-snapshot(+-static) , http://resources.ovirt.org/pub/ovirt-master-snapshot(+static)

On Thu, Jun 16, 2016 at 12:16 PM, Vinzenz Feenstra < vfeenstr@redhat.com > wrote:

...

On Jun 16, 2016, at 11:06 AM, Sven Kieske < S.Kieske@mittwald.de > wrote:

On 14/06/16 17:34, Vojtech Szocs wrote:

...

Hi,

ovirt-engine-dashboard is currently built from master as well.

We should probably create a stable branch, e.g. ovirt-engine-dashboard-1.0.

Hi,

speaking as an end user (mostly):

please not yet-another-versioning in the great ovirt project.

I'm already having severe issues tracking which engine versions works with which vdsm version, let alone track which datacenter and cluster version within each engine version works with which vdsm version and which features are (un)supported.

Please don't add another different version to the already far to complex equation. +1 :-)

I'd suggest you take the same version number as the supported ovirt-engine, you also should adjust release cycles of all the subprojects where possible (I know that doesn't work always).

this would make every users life make so much less painful.

keep up the great work!

-- Mit freundlichen Grüßen / Regards

Sven Kieske

Systemadministrator Mittwald CM Service GmbH & Co. KG Königsberger Straße 6 32339 Espelkamp T: +495772 293100 F: +495772 293333 https://www.mittwald.de Geschäftsführer: Robert Meyer St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen

_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

-- Eyal Edri Associate Manager RHEV DevOps EMEA ENG Virtualization R&D Red Hat Israel

phone: +972-9-7692018 irc: eedri (on #tlv #rhev-dev #rhev-integ)

_______________________________________________ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel

On Wed, Jun 15, 2016 at 4:07 PM, Dan Kenigsberg <danken@redhat.com> wrote:

On Tue, Jun 14, 2016 at 03:14:03PM +0200, Simone Tiraboschi wrote:

...

All stable branch maintainers, I just noticed that our oVirt 4.0 nightly repo ( http://resources.ovirt.org/pub/ovirt-4.0-snapshot/ ) still includes a lot of packages from master branches.

Can you please ensure that our jenkins is building your project packages in order to compose the 4.0 nightly repo from a stable branch?

If not, you have to push a patch like https://gerrit.ovirt.org/59150/ to correctly configure the publisher job for 4.0 nightly.

I see that Vdsm http://resources.ovirt.org/pub/ovirt-4.0-snapshot/rpm/el7Server/x86_64/

has both (correct) 4.18.2 builds and misleading 4.18.9999 ones such as vdsm-4.18.999-73.gitd35b8e7.el7.centos.x86_64.rpm

Can you manually remove them? they hide the correct builds.

Done