April 2016 - Infra - oVirt List Archives

[JIRA] (OVIRT-487) Order the permissions in gerrit.ovirt.org
by David Caro Estevez (oVirt JIRA) 14 Apr '16

14 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-487?page=com.atlassian.jira.p… ] David Caro Estevez commented on OVIRT-487: ------------------------------------------ Might be worth it to give another look to something like https://github.com/openstack-infra/jeepyb > Order the permissions in gerrit.ovirt.org > ----------------------------------------- > > Key: OVIRT-487 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-487 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: Shlomo Ben David > Assignee: infra > -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-460) set up another slave for ovirt -system-test
by eyal edri [Administrator] (oVirt JIRA) 14 Apr '16

14 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-460?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-460: ------------------------------------------------- OK, now that srv16-26 are installed, feel free to take any of them and reinstall as f23, some of them were bought specifically for Lago. > set up another slave for ovirt -system-test > ------------------------------------------- > > Key: OVIRT-460 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-460 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anatoly > Assignee: infra > > Please bring up srv10 in phx for the node system tests -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-487) Order the permissions in gerrit.ovirt.org
by Shlomo Ben David (oVirt JIRA) 14 Apr '16

14 Apr '16

Shlomo Ben David created OVIRT-487: -------------------------------------- Summary: Order the permissions in gerrit.ovirt.org Key: OVIRT-487 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-487 Project: oVirt - virtualization made easy Issue Type: Task Reporter: Shlomo Ben David Assignee: infra -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-485) add documentation on how to add new vm to phx lab
by Nadav Goldin (oVirt JIRA) 14 Apr '16

14 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-485?page=com.atlassian.jira.p… ] Nadav Goldin commented on OVIRT-485: ------------------------------------ I can add it to infra-docs later, for the production vms: {quote}1. Any template we should be using?{quote} currently there are no templates in the Production cluster, so best is to provision with pxe(in foreman), choose latest CentOS 7.2. don't forget to add the root password. HDD - create root HDD in VM tab in foreman, and add afterwards another HDD via the engine for the data. {quote} 2. DNS/DHCP settings {quote} use phx.ovirt.org domain, and let it auto-suggest {quote} 3. High availablity settings for production VM {quote} not sure, actually didn't use that {quote} 4. Which DC/Cluster to add it to..{quote} Production cluster > add documentation on how to add new vm to phx lab > ------------------------------------------------- > > Key: OVIRT-485 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-485 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: infra > > We need to have the procedure on how to add a new VM to PHX DC, especially around production VMs: > 1. Any template we should be using? > 2. DNS/DHCP settings > 3. High availablity settings for production VM > 4. Which DC/Cluster to add it to.. > 5. Documentation for the new VM ( + backup needed ) -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[oVirt Jenkins] ovirt-engine_master_upgrade-from-3.6_el7_merged - Build # 2601 - Failure!
by jenkins＠ovirt.org 14 Apr '16

14 Apr '16

------=_Part_22_1805642273.1460588205860 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Project: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build: http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… Build Number: 2601 Build Status: Failure Triggered By: Triggered by Gerrit: https://gerrit.ovirt.org/53174 ------------------------------------- Changes Since Last Success: ------------------------------------- Changes for Build #2601 [Yevgeny Zaspitsky] webadmin: enable entering host ipv6 address in add host dialog ----------------- Failed Tests: ----------------- No tests ran. ------=_Part_22_1805642273.1460588205860--

1 0

[JIRA] (OVIRT-460) set up another slave for ovirt -system-test
by David Caro Estevez (oVirt JIRA) 13 Apr '16

13 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-460?page=com.atlassian.jira.p… ] David Caro Estevez commented on OVIRT-460: ------------------------------------------ yep, I need fc servers for lago, not centos > set up another slave for ovirt -system-test > ------------------------------------------- > > Key: OVIRT-460 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-460 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Anatoly > Assignee: infra > > Please bring up srv10 in phx for the node system tests -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-479) move from current nightly publisher to per package publish via std ci
by eyal edri [Administrator] (oVirt JIRA) 13 Apr '16

13 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-479?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-479: ----------------------------------------------- Assignee: dcaro (was: infra) > move from current nightly publisher to per package publish via std ci > --------------------------------------------------------------------- > > Key: OVIRT-479 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-479 > Project: oVirt - virtualization made easy > Issue Type: Task > Reporter: eyal edri [Administrator] > Assignee: dcaro > > Currently the nightly publisher is a single POF and highly dependent on job names of artifacts, and its enough for one job to get renamed or deleted to fail the entire publish of rpms. > Instead, we should move to how Lago is being deployed, which means each package is deploying itself rather than one central job. > It should be added as a standard CI feature, probably part of the build artifacts post merge code, so any new package that is added to standard ci can enjoy it. > We'll need to figure out how to create a central repo rather than a single repo per package which is what is done now in Lago. -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-251) chain ovirt-engine merge jobs
by eyal edri [Administrator] (oVirt JIRA) 13 Apr '16

13 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-251?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-251: ------------------------------------------------- Will this still be relevant in STD CI? We don't have too much jobs left outside of it for ovirt-engine, and we're planning to remove/replace existing ones. > chain ovirt-engine merge jobs > ----------------------------- > > Key: OVIRT-251 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-251 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Currently a merge event triggers: > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged > All of them performs builds at different stages. > I suggest to run first > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged > and if it finish with success, I suggest to use rpms built from > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged > for running: > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged > otherwise abort the chain as soon as it fails. > This will reduce the times we rebuild the same code and the slaves load. -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-178) [jenkins] create new job checking reports setup running on the same host running engine and dwh
by eyal edri [Administrator] (oVirt JIRA) 13 Apr '16

13 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-178?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-178: ----------------------------------------------- Assignee: sradco (was: infra) This is a task to add setup tests to dwh/reports - should probably be done using Lago. > [jenkins] create new job checking reports setup running on the same host running engine and dwh > ----------------------------------------------------------------------------------------------- > > Key: OVIRT-178 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-178 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: sradco > > We're missing a job that install ovirt-engine, ovirt-engine-dwh and ovirt-engine-reports and check that the setup works. > Job should be triggered at least on merge commit in ovirt-engine, ovirt-dwh and ovirt-reports projects including changes in file within packaging directory or spec changes. -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0

[JIRA] (OVIRT-443) gerrit gc job failing since gerrit upgrade
by eyal edri [Administrator] (oVirt JIRA) 13 Apr '16

13 Apr '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-443?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-443: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) > gerrit gc job failing since gerrit upgrade > ------------------------------------------- > > Key: OVIRT-443 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-443 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: High > > http://jenkins.ovirt.org/job/system_gerrit-garbage-collect/ -- This message was sent by Atlassian JIRA (v7.2.0-OD-05-030#72002)

1 0