February 2018 - Infra - oVirt List Archives

[CQ]: 87243, 1 (ovirt-engine-extension-aaa-misc) failed "ovirt-4.2" system tests, but isn't the failure root cause
by oVirt Jenkins 07 Feb '18

07 Feb '18

A system test invoked by the "ovirt-4.2" change queue including change 87243,1 (ovirt-engine-extension-aaa-misc) failed. However, this change seems not to be the root cause for this failure. Change 83287,1 (ovirt-engine-extension-aaa- misc) that this change depends on or is based on, was detected as the cause of the testing failures. This change had been removed from the testing queue. Artifacts built from this change will not be released until either change 83287,1 (ovirt-engine- extension-aaa-misc) is fixed and this change is updated to refer to or rebased on the fixed version, or this change is modified to no longer depend on it. For further details about the change see: https://gerrit.ovirt.org/#/c/87243/1 For further details about the change that seems to be the root cause behind the testing failures see: https://gerrit.ovirt.org/#/c/83287/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-4.2_change-queue-tester/573/

1 0

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

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Description: 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. was: There are multiple reasons why we may want to manage our bare-metal slaves with beaker: * 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. > 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#100079)

1 0

[JIRA] (OVIRT-1881) Setup (or loan) a beaker instance
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995258-24605-194 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1881?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1881: ----------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Setup (or loan) a beaker instance > --------------------------------- > > Key: OVIRT-1881 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: Evgheni Dereveanchin > Labels: beaker > > To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. > We need to check if we can use someone else's beaker server, and if not, setup our own. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995258-24605-194 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1881?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1881:</h3> <pre>Assignee: Evgheni Dereveanchin (was: infra)</pre> <blockquote><h3>Setup (or loan) a beaker instance</h3> <pre> Key: OVIRT-1881 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: Evgheni Dereveanchin Labels: beaker</pre> <p>To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. We need to check if we can use someone else's beaker server, and if not, setup our own.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995258-24605-194--

1 0

[JIRA] (OVIRT-1882) Figure out how to integrate Jenkins with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1882?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1882: ----------------------------------- Assignee: Barak Korren (was: infra) > Figure out how to integrate Jenkins with beaker > ----------------------------------------------- > > Key: OVIRT-1882 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Barak Korren > Assignee: Barak Korren > Labels: beaker > > If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. > One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. > It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1882) Figure out how to integrate Jenkins with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995238-13653-236 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1882: ----------------------------------- Summary: Figure out how to integrate Jenkins with beaker Key: OVIRT-1882 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995238-13653-236 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1882:</h3> <pre> Summary: Figure out how to integrate Jenkins with beaker Key: OVIRT-1882 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra</pre> <p>If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins.</p> <p>One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs.</p> <p>It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995238-13653-236--

1 0

[JIRA] (OVIRT-1882) Figure out how to integrate Jenkins with beaker
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995238-31531-315 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1882?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1882: -------------------------------- Epic Link: OVIRT-400 > Figure out how to integrate Jenkins with beaker > ----------------------------------------------- > > Key: OVIRT-1882 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Barak Korren > Assignee: infra > Labels: beaker > > If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. > One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. > It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995238-31531-315 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1882?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1882:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Figure out how to integrate Jenkins with beaker</h3> <pre> Key: OVIRT-1882 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1882 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra Labels: beaker</pre> <p>If we want to use beaker to manage bare-metal slaves, we need a way to connect them to Jenkins. One way is to run the swarm client on them, and pre-allocate the slaves in beaker, but this would negate the benefit of having beaker re-provision the slaves between job runs. It would be best if beaker could be configured as a cloud provider in Jenkins so that hosts will be provisioned dynamically as needed.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1517995238-31531-315--

1 0

[JIRA] (OVIRT-1881) Setup (or loan) a beaker instance
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1881?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1881: -------------------------------- Epic Link: OVIRT-403 > Setup (or loan) a beaker instance > --------------------------------- > > Key: OVIRT-1881 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: beaker > > To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. > We need to check if we can use someone else's beaker server, and if not, setup our own. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

[JIRA] (OVIRT-1881) Setup (or loan) a beaker instance
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

Barak Korren created OVIRT-1881: ----------------------------------- Summary: Setup (or loan) a beaker instance Key: OVIRT-1881 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1881 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra To work with Beaker a beaker manager server is needed, some PXE, DNS and DHCP setup is required as well. We need to check if we can use someone else's beaker server, and if not, setup our own. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0

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

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Description: There are multiple reasons why we may want to manage our bare-metal slaves with beaker: * 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. was: There are multiple reasons why we may want to manage our bare-metal slaves with beaker: * 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. > 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: > * 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#100079)

1 0

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

07 Feb '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1880?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1880: -------------------------------- Epic Link: OVIRT-403 > 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: > * 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. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079)

1 0