[INTPAK-189] Improve Apex proposed-change-distro upgrade logic

Relates — Fri, 29 Jun 2018 19:10:23 +0000

There's work ongoing to use OPNFV Apex images in ODL CI as a quick way to stand up real OpenStack+ODL deployments. The logic needs to build an ODL distro from a proposed change, then update the version of ODL in the Apex images with the proposed distro. The logic currently does this, but in a hacky way. Per trozet:

Well I solved it, but in a hacky way. When the job goes to update odl, it brings down docker container. It then extracts the tar.gz netvirt distro into /opt. Then it copies a systemd unit file, creates the odl user and group. I use puppet tags to avoid puppet-opendaylight trying to install the ODL repo or RPM. You can see it all here:
https://gerrit.opnfv.org/gerrit/#/c/59017/5/odl-pipeline/lib/odl_reinstaller/odl_reinstaller.py

Not the greatest code in the world, but it works for now. If we had an RPM built with the patch set that would be much cleaner, but if you don't have time then don't worry about it for now.

So eventually should consider improving that upgrade logic with RPM-native upgrades. This relates to INTPAK-20 and ~~INTPAK-161~~.

OpenDaylight JIRA

[INTPAK-189] Improve Apex proposed-change-distro upgrade logic