- Infra - oVirt List Archives

[JIRA] (OVIRT-893) Build oVirt 4.1.0 beta1
by sbonazzo (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-893?page=com.atlassian.jira.p… ] sbonazzo updated OVIRT-893: --------------------------- Assignee: sbonazzo (was: infra) Status: In Progress (was: To Do) > Build oVirt 4.1.0 beta1 > ----------------------- > > Key: OVIRT-893 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-893 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: sbonazzo > Assignee: sbonazzo > Priority: Highest > -- 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

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-889: ------------------------------------------------- Its a sub-task of the general task, so we can track and work on each sub-task seperately > 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 > Labels: containers, docker > > 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

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

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-890?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-890: ------------------------------- Labels: containers docker standard-ci (was: ) > 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 > Labels: containers, docker, standard-ci > > 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-891) Add support for verification / testing of containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-891: ------------------------------------ I don't think this belongs in standard-CI, standard CI is for verifying _code_ not artifacts (no matter how fancy and fashionable they are). Verifying complete artifacts is what systems tests are for. > 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-889) Add support for building containers in standard CI
by Barak Korren (oVirt JIRA) 01 Dec '16

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-889: ------------------------------- Labels: containers docker (was: ) > 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 > Labels: containers, docker > > 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

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

01 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-889?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-889: ------------------------------------ Isn`t this a duplicate of OVIRT-848 ? Also I've repentantly stated - containers are NOT special, standard CI can already build RPMs, images and tarballs, so it does not need to be changed just so you could build containers. The whole point of standard-CI was that we don't have to change it every time a new shiny thing comes along. There is one issue with handling the situation of building containers in standard CI if and when standard CI itself will use containers (OVIRT-873), and the solution for that is to allow optional bind mounts so we can bind mount /var/run/docker.sock only if it exists (and not fail if it doesn't) - I made OVIRT-892 to specify and track this. > 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 > Labels: containers, docker > > 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

[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 (was: ) > 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: ------------------------------- 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