I created a new organization for oVirt under:
https://hub.docker.com/u/ovirtinfra/
(ovirt wasn't available)

please let me know which permissions do you need to create the VDSM images repos under it.

I don't think this is a good solution, building the images takes
several minutes per
image locally on ssd, on the ci poor storage it will take ages and may
fail vdsm build-artifacts job.

Do you have proof for the 'poor storage'?
All slaves are using now local storage and should run quite fast, i'm not sure what speed you expect or need for this service, please elaborate.

Also, there is no reason to rebuild the images each time we build vdsm,
only when the dockerfiles were modified.

We can control that.

Anyway what is missing currently is not a way to build the images, but
a dockerhub account holding the existing images we already built.
Lets fix first this issue, and handle later the build process.

I was asking to put it on build-artifacts not only for the build, but also for standardization of the process so we'll support pushing to dockerhub globally via std ci.

On Fri, Nov 18, 2016 at 1:05 PM, eyal edri [Administrator] (oVirt

I don't think this is a good solution, building the images takes
several minutes per
image locally on ssd, on the ci poor storage it will take ages and may
fail vdsm build-artifacts job.

Also, there is no reason to rebuild the images each time we build vdsm,
only when the dockerfiles were modified.

Anyway what is missing currently is not a way to build the images, but
a dockerhub account holding the existing images we already built.

Lets fix first this issue, and handle later the build process.

@Nir Soffer can you build the images inside build-artifacts.sh script?

we want to support building docker images in standard CI.

If you can build the image and archive it via build-artifacts, we'll find the best way to deploy it to dockerhub via our CI infra.

Building and publishing Docker images should be quite simple to do from std-ci.
There is no technical reason why this couldn`t be done directly in VDSM's check-patch.sh or build-artifacts.sh. But maybe mock will require some tweaking.

But perhaps the docker files shouldn't be in the vdsm repo for the sake of not building them unnecessarily, this can also be avoided with a simple condition in the script file though.

Is it possible to do it from Gerrit and not GitHub?

@Barak Korren@Former user @Nadav Goldin - We haven't talked about managing containers for oVirt yet (except for using OpenShift for the monitoring app), thoughts?