- Infra - oVirt List Archives

[JIRA] (OVIRT-1884) Scale up to multipile Jenkins masters
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517996808-26764-286 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1884: ----------------------------------- Summary: Scale up to multipile Jenkins masters Key: OVIRT-1884 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra There are several reasons why we would like to enable scaling up to multiple Jenkins masters: * We may reach a point where a single jenkins master will simple not be able to cope with the workload we have - this is especially true as we increase our use of heavy features like pipelines and blue ocean. * If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance. * As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance. This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517996808-26764-286 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1884:</h3> <pre> Summary: Scale up to multipile Jenkins masters Key: OVIRT-1884 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra</pre> <p>There are several reasons why we would like to enable scaling up to multiple Jenkins masters:</p> <ul><li><p>We may reach a point where a single jenkins master will simple not be able to cope with the workload we have – this is especially true as we increase our use of heavy features like pipelines and blue ocean.</p></li> <li><p>If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance.</p></li> <li><p>As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance.</p></li></ul> <p>This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one.</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> ------------=_1517996808-26764-286--

1 0

[JIRA] (OVIRT-1884) Scale up to multipile Jenkins masters
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517996808-12609-300 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1884?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1884: -------------------------------- Epic Link: OVIRT-400 > Scale up to multipile Jenkins masters > ------------------------------------- > > Key: OVIRT-1884 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master > Reporter: Barak Korren > Assignee: infra > Labels: scale > > There are several reasons why we would like to enable scaling up to multiple Jenkins masters: > * We may reach a point where a single jenkins master will simple not be able to cope with the workload we have - this is especially true as we increase our use of heavy features like pipelines and blue ocean. > * If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance. > * As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance. > This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517996808-12609-300 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1884?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1884:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Scale up to multipile Jenkins masters</h3> <pre> Key: OVIRT-1884 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1884 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Master Reporter: Barak Korren Assignee: infra Labels: scale</pre> <p>There are several reasons why we would like to enable scaling up to multiple Jenkins masters:</p> <ul><li><p>We may reach a point where a single jenkins master will simple not be able to cope with the workload we have – this is especially true as we increase our use of heavy features like pipelines and blue ocean.</p></li> <li><p>If we choose to start using OpenShift's embedded Jenkins, the approach there is that every project gets its own Jenkins instance.</p></li> <li><p>As we increase out reach and support more projects, some of them would not like to use an oVirt branded Jenkins instance.</p></li></ul> <p>This ticket would track the work we need to do to enable supporting multiple Jenkins master in out infra. Individual pieces of work should be created as separate tickets and be linked as blockers to this one.</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> ------------=_1517996808-12609-300--

1 0

[CQ]: 86521, 1 (ovirt-engine-sdk-ruby) failed "ovirt-master" system tests
by oVirt Jenkins 07 Feb '18

07 Feb '18

Change 86521,1 (ovirt-engine-sdk-ruby) is probably the reason behind recent system test failures in the "ovirt-master" change queue and needs to be fixed. This change had been removed from the testing queue. Artifacts build from this change will not be released until it is fixed. For further details about the change see: https://gerrit.ovirt.org/#/c/86521/1 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/5316/

1 0

[JIRA] (OVIRT-1883) Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995716-25255-216 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1883: ----------------------------------- Assignee: Barak Korren (was: infra) > Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) > ------------------------------------------------------------------------------- > > Key: OVIRT-1883 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: Barak Korren > Labels: beaker > > The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. > If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995716-25255-216 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1883:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)</h3> <pre> Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: Barak Korren Labels: beaker</pre> <p>The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches.</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> ------------=_1517995716-25255-216--

1 0

[JIRA] (OVIRT-1883) Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995701-11810-157 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1883: -------------------------------- Epic Link: OVIRT-400 > Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) > ------------------------------------------------------------------------------- > > Key: OVIRT-1883 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Slaves > Reporter: Barak Korren > Assignee: infra > Labels: beaker > > The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. > If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995701-11810-157 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1883?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1883:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)</h3> <pre> Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra Labels: beaker</pre> <p>The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches.</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> ------------=_1517995701-11810-157--

1 0

[JIRA] (OVIRT-1883) Figure out how to make caches work with re-provisioned hosts (E.g. from beaker)
by Barak Korren (oVirt JIRA) 07 Feb '18

07 Feb '18

This is a multi-part message in MIME format... ------------=_1517995701-29869-301 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1883: ----------------------------------- Summary: Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them. If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100079) ------------=_1517995701-29869-301 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1883:</h3> <pre> Summary: Figure out how to make caches work with re-provisioned hosts (E.g. from beaker) Key: OVIRT-1883 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1883 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Jenkins Slaves Reporter: Barak Korren Assignee: infra</pre> <p>The CI system currently relies on the fact that the Jenkins slaves are stateful, and stores various caches on them.</p> <p>If we move to a mechanism where slaves are provisioned dynamically, we need to consider ho to keep having effective caches.</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> ------------=_1517995701-29869-301--

1 0

[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