- Infra - oVirt List Archives

[JIRA] (OVIRT-1880) Manage bare metals with beaker
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) We're not going to use Beaker directly, we'll use CentOS CI and Duffy instead. > Manage bare metals with beaker > ------------------------------ > > Key: OVIRT-1880 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1880 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > > There are multiple reasons why we may want to manage our bare-metal slaves with [beaker|https://beaker-project.org/] > * It will allow us to have auto-reprovisioning for them, perhaps even after every job > * It will allow us to scale up to multiple jenkins masters while sharing host resources > * If may allow us to safely move `global_setup.sh` to be executed before a jobs starts and not by the job itself. > There are probably multiple pieces of work to be carried out here, each will be tracked in a different ticket that will be set as a blocker to this ticket. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1885) Remove slave/resource management from Jenkins
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1885?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1885: ------------------------------------- Removing OVIRT-1880 as a blocker and adding OVIRT-2178 as we're probably not going to use beaker directly for B.M. slaves and instead rely on CentOS CI and Duffy. > Remove slave/resource management from Jenkins > --------------------------------------------- > > Key: OVIRT-1885 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1885 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: scale > > The way out infra is configure right now, resource allocation and management is done by Jenkins itself. This means that all resources need to pre-allocated to Jenkins in the form of slaves. > If we want to have separate Jenkins masters, our current configuration will force us to hard-split the resources between different Jenkins masters. > If we want to share our pool of resources between multiple masters, it means that resource allocation needs to move out of Jenkins to external tools. > Potential tools for different types of resources are: > * Beaker for managing physical hosts > * oVirt + a Jenkins could provider plugin for managing VMs > * OpenShift for managing containers (As a replacement for chroots). -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2173) STDCI build summary to include details about the STDCI event
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2173?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-2173: ------------------------------------- Need to be clearer on this - we need to show what was the exact event - was a commit pushed to the branch? Was a new PR submitted? Was a PR or a patch merged? Was it simpy a comment on the PR/patch? > STDCI build summary to include details about the STDCI event > ------------------------------------------------------------ > > Key: OVIRT-2173 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2173 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Standard CI (Pipelines) > Reporter: Daniel Belenky > Assignee: infra > > As an STDCI user I want to have quick view of the event details such as who is the change owner, what branch it was pushed to, and etc so I won't have to extract this information from the SCM. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2186) Auto-update the distribution-gpg-keys package on the mirrors server
by Barak Korren (oVirt JIRA) 11 Jun '18

11 Jun '18

Barak Korren created OVIRT-2186: ----------------------------------- Summary: Auto-update the distribution-gpg-keys package on the mirrors server Key: OVIRT-2186 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2186 Project: oVirt - virtualization made easy Issue Type: Improvement Components: CI Mirrors Reporter: Barak Korren Assignee: infra Have the mirror sync job auto-update the distribution-gpg-keys package on the mirrors server so that issues like OVIRT-1298 do not occur. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[oVirt Jenkins] ovirt-system-tests_hc-basic-suite-4.2 - Build # 248 - Failure!
by jenkins＠jenkins.phx.ovirt.org 10 Jun '18

10 Jun '18

Project: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/ Build: http://jenkins.ovirt.org/job/ovirt-system-tests_hc-basic-suite-4.2/248/ Build Number: 248 Build Status: Failure Triggered By: Started by timer ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #248 [Eitan Raviv] network: introduce wait for 'powering up' or 'up' ----------------- Failed Tests: ----------------- No tests ran.

1 1

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1448) Enable devs to specifiy patch dependencies for OST
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1448?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1448: -------------------------------- Epic Link: OVIRT-2184 (was: OVIRT-400) > Enable devs to specifiy patch dependencies for OST > -------------------------------------------------- > > Key: OVIRT-1448 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1448 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > We have an issue with our system ATM where if there are patches for different projects that depend on one another, the system is unaware of that dependency. > What typically happens in this scenario is that sending the dependent patch makes the experimental test fail and keep failing until the other patch is also merged. > The change queue will handle this better, but the typical behaviour for it would be to reject both patches, unless they are somehow coordinated to make it into the same test. > The change queue core code already includes the ability to track and understand dependencies between changes. What is missing is the ability for developers to specify theses dependencies. > We would probably want to adopt OpenStack's convention here. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1462?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1462: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Generate more detailed output from change-queue tests > ----------------------------------------------------- > > Key: OVIRT-1462 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM. > This information includes: > # If the test failed because a build job failed, and which build job made it fail. > # If the test failed during OST run, which suits failed. > This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1462) Generate more detailed output from change-queue tests
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1462?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1462: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Generate more detailed output from change-queue tests > ----------------------------------------------------- > > Key: OVIRT-1462 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1462 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > The change-queue tester jobs can have some additional information that may be useful for understanding issues but is not reported anywhere ATM. > This information includes: > # If the test failed because a build job failed, and which build job made it fail. > # If the test failed during OST run, which suits failed. > This information should, at least, be presented in the test results screen, but may also be preserved and included in the email or Gerrit notifications about failing changes. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-1504) Include more patch information in CQ jobs output
by Barak Korren (oVirt JIRA) 10 Jun '18

10 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1504?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1504: -------------------------------- Epic Link: OVIRT-2185 (was: OVIRT-400) > Include more patch information in CQ jobs output > ------------------------------------------------ > > Key: OVIRT-1504 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1504 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Change Queue > Reporter: Barak Korren > Assignee: infra > Labels: change-queue > > It would be useful to include more information about checked patches in the UI of the CQ jobs and in email messages generated by them. > The information to include would be: > # The patch commit message > # The patch Git SHA > # The Gerrit change ID > The information should be included in: > # The email messages sent by the change queue > # As a popup text when clicking or hovering over an icon that will be displayed for the job build in the build history. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0