- Infra - oVirt List Archives

[JIRA] (OVIRT-835) Install a Zool server and integrate with oVirt infra
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-835?page=com.atlassian.jira.p… ] Barak Korren updated OVIRT-835: ------------------------------- Epic Link: OVIRT-400 > Install a Zool server and integrate with oVirt infra > ---------------------------------------------------- > > Key: OVIRT-835 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-835 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Barak Korren > Assignee: infra > Priority: Highest > > Setup zool.phx.ovirt.org > Install Zool and all zervices needed to run it > Integrate Zool with oVirt Gerrit and Jenkins -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-835) Install a Zool server and integrate with oVirt infra
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

Barak Korren created OVIRT-835: ---------------------------------- Summary: Install a Zool server and integrate with oVirt infra Key: OVIRT-835 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-835 Project: oVirt - virtualization made easy Issue Type: New Feature Components: Jenkins Reporter: Barak Korren Assignee: infra Priority: Highest Setup zool.phx.ovirt.org Install Zool and all zervices needed to run it Integrate Zool with oVirt Gerrit and Jenkins -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-833) consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-833?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-833: ------------------------------------ It can be done with some API calls to check who is in which group. I don`t think it will load Gerrit that much - every job run already does a git clone - and it a much heavier operation then a simple API call. > consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-833 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-833 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: infra > > On top of patch senders, maintainers should be emailed if a job such as > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-x86_64/ > fails 5 straight times. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-734) [std ci] add Zuul to gate check-merged jobs
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-734?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-734: ----------------------------------------------- Assignee: Barak Korren (was: infra) > [std ci] add Zuul to gate check-merged jobs > -------------------------------------------- > > Key: OVIRT-734 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-734 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins > Reporter: eyal edri [Administrator] > Assignee: Barak Korren > Priority: High > > Today we run check-merged.sh jobs in CI just post merge without any gating to reject a failing code. > So what happens is a regression which passed check-patch might fail check-merged and we'll only see it after it already broken the branch. > Introducing Zuul to be gating before merge can solve this, and also solve any rebase issues we might have when merging the code. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-833) consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-833?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-833: ------------------------------------------------- How will we do that? doesn't it mean it needs a dynamic configuration to update the job configuration? It will need to find the maintainers on each job run, it will add significant load issues to Gerrit just to get a static info. > consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-833 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-833 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: infra > > On top of patch senders, maintainers should be emailed if a job such as > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-x86_64/ > fails 5 straight times. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-816) Please enable gh-pages for ovirt-engine-sdk
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-816?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-816: ----------------------------------------------- Assignee: eyal edri [Administrator] (was: infra) page is published here: http://ovirt.github.io/ovirt-engine-sdk/v4.1/latest/ http://ovirt.github.io/ovirt-engine-sdk/v4.0/latest/ I'm checking why the default index.html isn't shown, maybe it needs a different style > Please enable gh-pages for ovirt-engine-sdk > ------------------------------------------- > > Key: OVIRT-816 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-816 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Gerrit/git > Reporter: Ondra Machacek > Assignee: eyal edri [Administrator] > > Please enable gh-pages[1] for ovirt-engine-sdk[2]. > Enable it for gh-pages branch. > Thanks. > [1] https://github.com/ovirt/ovirt-engine-sdk/ > [2] https://help.github.com/articles/configuring-a-publishing-source-for-github… -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-833) consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-833?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-833: ------------------------------------ And we need to be able to figure out the maintainers automatically from Gerrit > consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-833 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-833 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: infra > > On top of patch senders, maintainers should be emailed if a job such as > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-x86_64/ > fails 5 straight times. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-833) consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers
by Barak Korren (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-833?page=com.atlassian.jira.p… ] Barak Korren commented on OVIRT-833: ------------------------------------ I don't think this kind of thing should be specified in the repo itself - because std-ci is supposed to be portable and agnostic to the environment it runs in. Instead, we might consider setting up such a notification across the board to project maintainers. > consistent failure in check-merged or build artifactrs should be mailed to vdsm-*-maintainers > ---------------------------------------------------------------------------------------------- > > Key: OVIRT-833 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-833 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: danken > Assignee: infra > > On top of patch senders, maintainers should be emailed if a job such as > http://jenkins.ovirt.org/job/vdsm_master_build-artifacts-fc24-x86_64/ > fails 5 straight times. -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-825) re: Assistance
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-825?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-825: -------------------------------------------- Blocked By: pending move to devel list Status: Blocked (was: To Do) > re: Assistance > -------------- > > Key: OVIRT-825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-825 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Billy Boulden > Assignee: infra > Attachments: image002.png > > > Hello, > Having issues installing and configuring OVIRT with the virtual switch. Need to speak with someone > Billy Boulden, C|EH, C|HFI > Systems Engineer > Information Systems Worldwide > A Wholly-Owned Subsidiary of ECS Federal. Inc. > 3865 Wilson Blvd, #600 > Arlington, VA 22203 > Phone: 571-482-4900 x6004 -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0

[JIRA] (OVIRT-829) 26531 infra-support
by eyal edri [Administrator] (oVirt JIRA) 13 Nov '16

13 Nov '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-829?page=com.atlassian.jira.p… ] eyal edri [Administrator] deleted OVIRT-829: -------------------------------------------- > 26531 infra-support > ------------------- > > Key: OVIRT-829 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-829 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: m.kos(a)lycos.com > Assignee: infra > -- This message was sent by Atlassian JIRA (v1000.526.2#100018)

1 0