- Infra - oVirt List Archives

[JIRA] (OVIRT-922) Add new project to standard ci from github
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-922: ------------------------------------------------- Also, can you rename the repo to something with more context? ovirt-tests is very generic name ( we have system tests / functional tests/ unit tests ). If its ansbile, maybe worth calling it ovirt-ansible-tests or something else with ansible ) > Add new project to standard ci from github > ------------------------------------------ > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-898) Send committers in test experimental job's email
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-898?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-898: ----------------------------------------------- Assignee: Daniel Belenky (was: infra) > Send committers in test experimental job's email > ------------------------------------------------ > > Key: OVIRT-898 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-898 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Daniel Belenky > > I can get the job that triggered deploy experimental and test experimental and get commiters from that job. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-922) Add new project to standard ci from github
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-922: -------------------------------------------- Summary: Add new project to standard ci from github (was: Please create new jenkins machine for Ansible modules tests) > Add new project to standard ci from github > ------------------------------------------ > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-922) Please create new jenkins machine for Ansible modules tests
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-922: ------------------------------------------------- We don't maintain 'special' machines or mange them with any CM tools like we did in the past, instead we use mock to give an isolated environment for any testing you'd like to run and you have full control over what is running there. You will need to make your project part of the 'standard ci' flow and add automation dir under the root folder. ( see other projects for e.g, like ovirt-engine ). see [1] for detailed info. But, as an example, you said you need vagrant and ansible installed, then you'll just need to add them to the .packages file in the automation dir under check-patch or check-merge depends on when you want it tested. We don't support yet GitHub as a standard CI project, there is another ticket to add support for it ( as part of adding ovirt-web-ui project ), so it might take bit more time. (for projects in Gerrit is straightforward now) [1] http://infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html > Please create new jenkins machine for Ansible modules tests > ----------------------------------------------------------- > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-922) Please create new jenkins machine for Ansible modules tests
by Ondra Machacek (oVirt JIRA) 08 Dec '16

08 Dec '16

Ondra Machacek created OVIRT-922: ------------------------------------ Summary: Please create new jenkins machine for Ansible modules tests Key: OVIRT-922 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: Ondra Machacek Assignee: infra I would like to request a jenkins machine for Ansible modules tests. Those tests needs host with nested virtualization as it will create a few virtual machines for tests. Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. Then I would need some possibility to run this job from a hook from github, when new commit is pushed. The tests are described here for an idea: https://github.com/machacekondra/ovirt-tests Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-922) Please create new jenkins machine for Ansible modules tests
by Ondra Machacek (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-922?page=com.atlassian.jira.p… ] Ondra Machacek commented on OVIRT-922: -------------------------------------- CC [~mperina] [~oourfali(a)redhat.com] > Please create new jenkins machine for Ansible modules tests > ----------------------------------------------------------- > > Key: OVIRT-922 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-922 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Ondra Machacek > Assignee: infra > > I would like to request a jenkins machine for Ansible modules tests. > Those tests needs host with nested virtualization as it will create a few virtual machines for tests. > Actually, what I would need is similar machine which OST are using, but with preinstalled vagrant and ansible. > Then I would need some possibility to run this job from a hook from github, when new commit is pushed. > The tests are described here for an idea: > https://github.com/machacekondra/ovirt-tests > Would that be possible? -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-908) jenkins failures
by eyal edri [Administrator] (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-908?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-908: ----------------------------------------------- Assignee: Shlomo Ben David (was: infra) > jenkins failures > ---------------- > > Key: OVIRT-908 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-908 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Polednik > Assignee: Shlomo Ben David > > Hi, > after pushing update to my patch series[1], I've been greeted with > unhealthy amount of jenkins failures. Actually, it's a single fail > that affected all but one(!) patch. > The failure: ERROR: Command failed. See logs for output. [2] > Can we get these issues solved or have some > false-positive/false-negative protection (preferably both)? > [1] https://gerrit.ovirt.org/#/q/topic:hostdev-caching > [2] http://jenkins.ovirt.org/job/vdsm_master_check-patch-fc24-x86_64/5788/conso… > Regards, > mpolednik -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-899) Create locking on experimental flow
by Gil Shinar (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-899?page=com.atlassian.jira.p… ] Gil Shinar reassigned OVIRT-899: -------------------------------- Assignee: Daniel Belenky (was: infra) > Create locking on experimental flow > ----------------------------------- > > Key: OVIRT-899 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-899 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Gil Shinar > Assignee: Daniel Belenky > > In order to make experimental flow atomic, we need to do as follows: > in deploy.sh script and in start_testing_latest.sh we need to add a loop in the beginning of each script that does the following: > *while 1: > do > is_locked=$((echo aaa > my.lock) 2> /dev/null || echo is locked) > if [[ -z $is_locked ]]; then > break > else > sleep 5 > fi > done* > Wrap the whole script with a trap so in the end if each script we will be able to remove my.lock no matter what happened. -- This message was sent by Atlassian JIRA (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA) 08 Dec '16

08 Dec '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-921?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-921: ------------------------------- Labels: mock mock_runner.sh performance standard-ci (was: ) > 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: Jenkins > 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 (v1000.620.0#100023)

1 0

[JIRA] (OVIRT-921) Smarter cache handling for mock_runner.sh
by Barak Korren (oVirt JIRA) 08 Dec '16

08 Dec '16

Barak Korren created OVIRT-921: ---------------------------------- Summary: 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: Jenkins Reporter: Barak Korren Assignee: infra 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 (v1000.620.0#100023)

1 0