June 2018 - Infra - Ovirt List Archives

[JIRA] (OVIRT-891) Add support for verification / testing of containers in standard CI

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-891?page=com.atlassian.jira... ] Barak Korren updated OVIRT-891: ------------------------------- Resolution: Fixed Status: Done (was: To Do) We already have support for doing various things with containers in STDCI. > 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 > 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 (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira... ] Barak Korren updated OVIRT-886: ------------------------------- Epic Link: (was: OVIRT-400) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira... ] Barak Korren updated OVIRT-886: ------------------------------- Epic Link: (was: OVIRT-400) > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-886) Yum install does not throw error on missing package

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-886?page=com.atlassian.jira... ] Barak Korren updated OVIRT-886: ------------------------------- Component/s: (was: oVirt CI) mock_runner > Yum install does not throw error on missing package > --------------------------------------------------- > > Key: OVIRT-886 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-886 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: mock_runner > Reporter: Gil Shinar > Assignee: infra > Labels: mock_runner.sh, standard-ci > > When running el7 mock on fc24 (not necessary the issue) and one of the required packages is missing because a repository in .repos hadn't been added, yum will not fail and the package will not be installed -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira... ] Barak Korren updated OVIRT-914: ------------------------------- Epic Link: (was: OVIRT-400) > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira... ] Barak Korren updated OVIRT-914: ------------------------------- Epic Link: (was: OVIRT-400) > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-914) Better arch support for mock_runner.sh

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-914?page=com.atlassian.jira... ] Barak Korren updated OVIRT-914: ------------------------------- Component/s: (was: oVirt CI) mock_runner > Better arch support for mock_runner.sh > -------------------------------------- > > Key: OVIRT-914 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-914 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock_runner.sh, standard-ci > > We managed to us "{{mock_runner.sh}}" in multi-arch so far because it was flexible enough to allow us to select the chroot file. > The issue is that mock_runner does not actually *know* the arch we are running on so we can`t:: > * do different mounts per-arch > * install different packages per-arch > * have different {{check_*}} scripts per-arch -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira... ] Barak Korren updated OVIRT-921: ------------------------------- Epic Link: OVIRT-2189 > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira... ] Barak Korren updated OVIRT-921: ------------------------------- Epic Link: OVIRT-2189 > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira... ] Barak Korren updated OVIRT-921: ------------------------------- Component/s: (was: oVirt CI) mock_runner > Smarter cache handling for mock_runner.sh > ----------------------------------------- > > Key: OVIRT-921 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-921 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: mock, mock_runner.sh, performance, standard-ci > > We've improved our handing of mock caches in OVIRT-902, but it could be better. > Right now we're just deleting everything from {{mock_cleanup.sh}} every two days, but we could do things in a smarter and more refined way: > * Mock actually has two separate caches that could be handled separately: > *# The yum cache - Caches package that are installed in the chroot > *# The root cache - Keeps an archive of the whole chroot > * We can make the yum cache shared by all the chroots that use the same repos > * We can keep the yum cache for much longer since 'yum' will refresh it automatically. We can tune this from mock root config file: > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_age_days']}} > ** {{config_opts\['plugin_conf']\['yum_cache_opts']\['max_metadata_age_days']}} > * We can also control the chroot cache from the mock config file, this will allow us greated flexibility, like deciding that some chroots live longer: > ** {{config_opts\['plugin_conf']\['root_cache_opts']\['max_age_days']}} > * We can use a different compression algorithm for the chroot acche, this may yield better performance. > * We still need some cleanup in {{moch_cleanup.sh}} but only for chroot caches that ahvn't been in use for a long time. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

6 years

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2018