February 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1123) Migrate glance.ovirt.org to PHX production DC
by eyal edri [Administrator] (oVirt JIRA) 09 Feb '17

09 Feb '17

eyal edri [Administrator] created OVIRT-1123: ------------------------------------------------ Summary: Migrate glance.ovirt.org to PHX production DC Key: OVIRT-1123 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1123 Project: oVirt - virtualization made easy Issue Type: Task Reporter: eyal edri [Administrator] Assignee: infra We considered it for a while and it seems PHX is stable enough already so would make sense to migrate glance there, to save costs and also improve speeds since OST is using it. Might be tricky to install w/o OpenStack, worth consulting with the developers team on best practice. Also, there might be Ansible playbooks [~bkorren(a)redhat.com] already wrote that might help deploy it. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0

[JIRA] (OVIRT-1123) Migrate glance.ovirt.org to PHX production DC
by eyal edri [Administrator] (oVirt JIRA) 09 Feb '17

09 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1123?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1123: --------------------------------------------- Epic Link: OVIRT-399 > Migrate glance.ovirt.org to PHX production DC > --------------------------------------------- > > Key: OVIRT-1123 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1123 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > We considered it for a while and it seems PHX is stable enough already so would make sense to migrate glance there, to save costs and also improve speeds since OST is using it. > Might be tricky to install w/o OpenStack, worth consulting with the developers team on best practice. > Also, there might be Ansible playbooks [~bkorren(a)redhat.com] already wrote that might help deploy it. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0

[oVirt Jenkins] test-repo_ovirt_experimental_4.1 - Build #539 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 09 Feb '17

09 Feb '17

Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/539/, Build Number: 539, Build Status: FAILURE

1 1

oVirt infra daily report - unstable production jobs - 225
by jenkins＠jenkins.phx.ovirt.org 09 Feb '17

09 Feb '17

------=_Part_124_493736225.1486594808257 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Good morning! Attached is the HTML page with the jenkins status report. You can see it also here: - http://jenkins.ovirt.org/job/system_jenkins-report/225//artifact/exported-a… Cheers, Jenkins ------=_Part_124_493736225.1486594808257 Content-Type: text/html; charset=us-ascii; name=upstream_report.html Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename=upstream_report.html Content-ID: <upstream_report.html> <!DOCTYPE html><head><style type="text/css"> table.gridtable { border-collapse: collapse; table-layout:fixed; width:1600px; font-family: monospace; font-size:13px; } .head { font-size:20px; font-family: arial; } .sub { font-size:18px; background-color:#e5e5e5; font-family: arial; } pre { font-family: monospace; display: inline; white-space: pre-wrap; white-space: -moz-pre-wrap !important; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word; } </style> </head> <body> <table class="gridtable" border=2> <tr><th colspan=2 class=head> RHEVM CI Jenkins Daily Report - 08/02/2017 </th></tr><tr><th colspan=2 class=sub> <font color="blue"><a href="http://jenkins.ovirt.org/">00 Unstable Critical</a></font> </th></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-live_master_experimental_create-iso-el7-…">ovirt-live_master_experimental_create-iso-el7-x86_64</a> </td><td> <h3>This job generates a nightly iso of ovirt-live using experimental repos</h3> </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-node-ng_ovirt-master-experimental_build-…">ovirt-node-ng_ovirt-master-experimental_build-artifacts-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/ovirt-system-tests_master_check-patch-el7-x86_…">ovirt-system-tests_master_check-patch-el7-x86_64</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_4.1_check-closure_fc24_merged/">repos_4.1_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_el7_merged/">repos_master_check-closure_el7_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/repos_master_check-closure_fc24_merged/">repos_master_check-closure_fc24_merged</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> <tr><td> <a href="http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_4.1/">test-repo_ovirt_experimental_4.1</a> </td><td> This job is automatically updated by jenkins job builder, any manual change will be lost in the next update. If you want to make permanent changes, check out the <a href="http://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;h=refs/heads/master;hb=…"> jenkins</a> repo.  </td></tr> ------=_Part_124_493736225.1486594808257--

1 0

[JIRA] (OVIRT-1122) document tests needed before PHX oVirt upgrades
by Evgheni Dereveanchin (oVirt JIRA) 08 Feb '17

08 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1122?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1122: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > document tests needed before PHX oVirt upgrades > ----------------------------------------------- > > Key: OVIRT-1122 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1122 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The production oVirt setup in PHX hosts critical CI services and unexpected downtime is very visible to both developers and end users. To minimize risks I perform upgrade tests in a lab environment before each major version upgrade. This ticket is to document the steps needed to simulate the PHX environment and its workloads and describe tests themselves. > We should probably publish the resulting guide on readthedocs. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0

[JIRA] (OVIRT-1122) document tests needed before PHX oVirt upgrades
by Evgheni Dereveanchin (oVirt JIRA) 08 Feb '17

08 Feb '17

Evgheni Dereveanchin created OVIRT-1122: ------------------------------------------- Summary: document tests needed before PHX oVirt upgrades Key: OVIRT-1122 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1122 Project: oVirt - virtualization made easy Issue Type: Task Components: General Reporter: Evgheni Dereveanchin Assignee: infra The production oVirt setup in PHX hosts critical CI services and unexpected downtime is very visible to both developers and end users. To minimize risks I perform upgrade tests in a lab environment before each major version upgrade. This ticket is to document the steps needed to simulate the PHX environment and its workloads and describe tests themselves. We should probably publish the resulting guide on readthedocs. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0

[JIRA] (OVIRT-1121) Install test oVirt Engine instance in PHX
by Evgheni Dereveanchin (oVirt JIRA) 08 Feb '17

08 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1121?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1121: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > Install test oVirt Engine instance in PHX > ----------------------------------------- > > Key: OVIRT-1121 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1121 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General, Hosting > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > The current oVirt instance in PHX runs critical workloads which causes upgrade delays. We can set up another instance that will run less important loads (i.e. Jenkins slaves). This can be updated more often, including beta and snapshot versions of oVirt as potential downtime will not have a negative impact on CI. > The Engine can run as a VM in the existing oVirt instance and it can manage a couple of hypervisors with Jenkins slaves. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0

[JIRA] (OVIRT-1121) Install test oVirt Engine instance in PHX
by Evgheni Dereveanchin (oVirt JIRA) 08 Feb '17

08 Feb '17

Evgheni Dereveanchin created OVIRT-1121: ------------------------------------------- Summary: Install test oVirt Engine instance in PHX Key: OVIRT-1121 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1121 Project: oVirt - virtualization made easy Issue Type: Task Components: General, Hosting Reporter: Evgheni Dereveanchin Assignee: infra The current oVirt instance in PHX runs critical workloads which causes upgrade delays. We can set up another instance that will run less important loads (i.e. Jenkins slaves). This can be updated more often, including beta and snapshot versions of oVirt as potential downtime will not have a negative impact on CI. The Engine can run as a VM in the existing oVirt instance and it can manage a couple of hypervisors with Jenkins slaves. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0

[JIRA] (OVIRT-1120) create a staging Gerrit server
by Evgheni Dereveanchin (oVirt JIRA) 08 Feb '17

08 Feb '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1120?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1120: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > create a staging Gerrit server > ------------------------------ > > Key: OVIRT-1120 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1120 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Gerrit/git > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > To test new plugins on both Jenkins and Gerrit it's good to have a test Gerrit instance. It can be a VM in PHX. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0

[JIRA] (OVIRT-1120) create a staging Gerrit server
by Evgheni Dereveanchin (oVirt JIRA) 08 Feb '17

08 Feb '17

Evgheni Dereveanchin created OVIRT-1120: ------------------------------------------- Summary: create a staging Gerrit server Key: OVIRT-1120 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1120 Project: oVirt - virtualization made easy Issue Type: Task Components: Gerrit/git Reporter: Evgheni Dereveanchin Assignee: infra To test new plugins on both Jenkins and Gerrit it's good to have a test Gerrit instance. It can be a VM in PHX. -- This message was sent by Atlassian JIRA (v1000.747.0#100028)

1 0