[
https://ovirt-jira.atlassian.net/browse/OVIRT-758?page=com.atlassian.jira...
]
Nir Soffer commented on OVIRT-758:
----------------------------------
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.
Vdsm docker testing images
--------------------------
Key: OVIRT-758
URL:
https://ovirt-jira.atlassian.net/browse/OVIRT-758
Project: oVirt - virtualization made easy
Issue Type: By-EMAIL
Reporter: Nir Soffer
Assignee: infra
Hi all,
Vdsm includes now 2 Dockerfiles, building CentOS 7 and Fedora 24 images.
See
https://gerrit.ovirt.org/#/q/status:open+project:vdsm+branch:master+topic...
Currently I maintain the images in docker hub:
-
https://hub.docker.com/r/nirs/vdsm-centos/
-
https://hub.docker.com/r/nirs/vdsm-fedora/
I configured automatic build, so each time I push a change to this branch:
https://github.com/nirs/vdsm/tree/dockerfile
Docker go and rebuilds the images.
We want to move the images to docker hub ovirt account:
https://hub.docker.com/u/ovirt/
And configure vdsm github project so docker will rebuild
the images when we push a changes to the dockerfile branch,
or another solution to allow easy update of the images by
merging a new dockerfile.
Nir
--
This message was sent by Atlassian JIRA
(v1000.552.6#100018)