OOM Gating

OOM gating has been introduced for Dublin.

It consists in running a deployment followed by a set of tests on patchset submission in OOM repository.

The CI part is managed on gitlab.com and the deployment executed on ONAP Orange lab.

The goal is to provide a feedback - and ultimately to vote - on code change prior to merge to consolidate the Master branch.

The developer can evaluate the consequences of his/her patchset on a fresh installation.

Please note that it is just an indicator, as it is based on the OOM Master branch, the errors reported in the results may be due to already existing code and may not be connected to the patch.

It is trivial to guess when the patch has nothing to do with the errors, but in some cases some pods or helm charts may be failed prior to the patchset modifying code from the same component.

The goal is to converge towards a rolling release, it means that Master would be always valid but it may take some time and would require some evolution on the management of docker versioning.

The Gating process can be described as follows:

On patchset submission, the gating chain is triggered. It can be seen in the gerrit History windows.

Please note that if you resubmit an amednded patch, it will retrigger a deployment and testing sequence. For the moment there is no filter so even a doc change triggers the pipeline.

At the end of the processing the ONAP jobDeployer reports the results

If you follow the link you will reach the xtesting-onap gitlab page (on gitlab.com).

Note you need a gitlab account to access to these pages.

This link is unique and corresponds to the gating pipeline corresponding to the patch.

You can download the artifact that corresponds to this specific test.

If you download all the results, you need first to select the pipeline.

You should see the following menu

Then if you want to download the artifact with all the results, you must select the page stage, then click on download.