Based on https://docs.google.com/document/d/1XVC6r6lgS8_I8HefT1z-T-zDRHNMs1ZkzaWGbz5umv4/edit?tab=t.0 , we have decided to add custom user metadata to OVN builds.

The fields we decided on are as follows:

• nightly_build: This is set true for our nightly OVN builds.
• candidate_build: This is set true for OVN builds that OVN QE should run the full testsuite on.

The way we set this metadata is by using the --custom-user-metadata option to rhpkg build. How this gets passed into ovn-sync is up to the developer.

For our current nightly builds, we will set nighty_build to true. In addition to the current nightly builds, we will need to perform an additional build at the end of the week for each supported OVN version with candidate_build set to true.

To perform this additional candidate build, we will increment the base release number in the configuration of the OVN builds by one and then perform the build. This will ensure that we do not run afoul of the build system by attempting to create the same OVN build more than once.

There is one additional catch: we should not waste QE resources if we do not need to. Therefore, if there have been no changes to a particular version of OVN within the week, then there is no reason to create a new candidate build. Therefore, we will need to add safeguards to check if there are any new changes to the OVN version in the previous week before moving forward with the new candidate build.