December 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-892?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-892: ------------------------------- Labels: containers docker standard-ci (was: containers) > Allow for optional bind mounts in Standard-CI > --------------------------------------------- > > Key: OVIRT-892 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Labels: containers, docker, standard-ci > > Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist. > We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead. > We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options: > # Fail - what it used to do > # Create what it needs - what it does now > # Just ignore and not mound > Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-892?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-892: ------------------------------- Epic Link: OVIRT-400 > Allow for optional bind mounts in Standard-CI > --------------------------------------------- > > Key: OVIRT-892 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > > Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist. > We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead. > We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options: > # Fail - what it used to do > # Create what it needs - what it does now > # Just ignore and not mound > Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-892) Allow for optional bind mounts in Standard-CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

Barak Korren created OVIRT-892: ---------------------------------- Summary: Allow for optional bind mounts in Standard-CI Key: OVIRT-892 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-892 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: infra Standard-CI as supported a *.mounts file for a while. The way it works is that it fails if something it tries to mount does not exist. We recently changed it (in OVIRT-751) so that if something that it tries to mount does not exist, it create an empty directory and mounts it instead. We want to change the behaviour to make it more controllable so that we can specify in the mount file what to do if the thing we want to mount does not exist (And also what it should be, directory, file or a device), there are a few options: # Fail - what it used to do # Create what it needs - what it does now # Just ignore and not mound Option #3 is useful for situation where you mount sockets in order to connect to services on the host (Like Docker or Libvirt). If the bound mount is optional - we could gracefully handle the situation where the service is not running on the host by installing and running it from within the Standard-CI script. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

eyal edri [Administrator] created OVIRT-891: ----------------------------------------------- Summary: Add support for verification / testing of containers in standard CI Key: OVIRT-891 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-891 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra >From check-patch scripts, verifying docker files to running system test suit on the new image. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-890) Add support to publish containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

eyal edri [Administrator] created OVIRT-890: ----------------------------------------------- Summary: Add support to publish containers in standard CI Key: OVIRT-890 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-890 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra Mostly likely to Dockerhub or OpenShift registry. We'll need a pet project to try out the various options. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-889) Add support for building containers in standard CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

eyal edri [Administrator] created OVIRT-889: ----------------------------------------------- Summary: Add support for building containers in standard CI Key: OVIRT-889 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-889 Project: oVirt - virtualization made easy Issue Type: Sub-task Reporter: eyal edri [Administrator] Assignee: infra might be simple as bash command in build-containers.sh script or using a service like DockerHub of OpenShift, we need to examine both options and choose the most fit. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #3800 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 01 Dec '16

01 Dec '16

------=_Part_19_556033321.1480570134122 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/3800/, Build Number: 3800, Build Status: FAILURE ------=_Part_19_556033321.1480570134122--

4 10

[JIRA] (OVIRT-848) Add support for building containers in oVirt CI
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-848?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-848: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Add support for building containers in oVirt CI > ----------------------------------------------- > > Key: OVIRT-848 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-848 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: eyal edri [Administrator] > Assignee: Daniel Belenky > > more and more projects in oVirt are starting to build containers and using Docker files in their reops. > We need to start preparing oVirt CI to know how to handle containers and support containers the same way we support rpms today. > This will be a parent task with multiple sub-tasks that will follow, the following is a draft list of what we might need to do to add this support: > # Install Registry server ( maybe use openshift.ovirt.org ) > # Add for standard CI 'build-containers.sh' support > # Add verification steps for the build before publishing to registry > # Look at 3rd party OSS projects that might help and integrate with existing solutions -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-627) Implement Zuul as pre-merge action to run experimental flows
by eyal edri [Administrator] (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-627?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-627: ----------------------------------------------- Assignee: bkorren (was: infra) I guess this is the second step after we see Zuul integration works. I think the 1st thing we should do is create some sort of design diagram of how we want the flow to work and what input/output/triggers it should have. > Implement Zuul as pre-merge action to run experimental flows > ------------------------------------------------------------- > > Key: OVIRT-627 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-627 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: bkorren > > Today, we can test a patch per project on each of the ovirt versions using experimanal flow > i,e: > run build_artifacts with a patch -> deploy to experimental -> run test job > this is problematic since it actually deploys the build with the patch to the experimental repo which should only contain built pkg that are merged. > We need to either close the flow or add param to the build artifacts that says 'create temp repo/test repo' so the built rpm won't be part of the official tested repo and the link to latest_tested won't be updated if this option is triggered. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0

[JIRA] (OVIRT-888) mock build ignores unfound packages
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-888?page=com.atlassian.jira.p… ] Barak Korren closed OVIRT-888. ------------------------------ Resolution: Duplicate Duplicate of OVIRT-886 > mock build ignores unfound packages > ----------------------------------- > > Key: OVIRT-888 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-888 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: danken > Assignee: infra > > If I mis-specify a package in check-merged.packages (e.g. typo), Jenkins > silently ignores the problem and let check-merged.sh start. > Debugging the ensuing problems is a pain. If jenkins is unable to build > the specified environment, it should fail and report the error. -- This message was sent by Atlassian JIRA (v1000.606.0#100023)

1 0