June 2018 - Infra - oVirt List Archives

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-686: ---------------------------- Epic Link: (was: OVIRT-400) > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, monitoring > Reporter: eyal edri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-686: ---------------------------- Epic Link: (was: OVIRT-400) > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, monitoring > Reporter: eyal edri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2153) Fedora 28 ppc64le support
by sbonazzo (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2153?page=com.atlassian.jira.… ] sbonazzo commented on OVIRT-2153: --------------------------------- we want to expand testing for future updates, so I think having ppc64le support would be beneficial to the project. > Fedora 28 ppc64le support > ------------------------- > > Key: OVIRT-2153 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2153 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: sbonazzo > Assignee: infra > > Hi, > I see python-ovirt-engine-sdk4 failing on ppc64le for fc28 due to: "Unable > to find mock env" error. > I tend to think we should have ppc64le for fedora 28 but I see that mock > config are missing in jenkins and also the mirroring of the repos for > fedora 28 ppc64le are missing. > We should either drop ppc64le jobs for fc28 or add support for it. Adding > Ondra to share his thoughts on this. > -- > SANDRO BONAZZOLA > ASSOCIATE MANAGER, SOFTWARE ENGINEERING, EMEA ENG VIRTUALIZATION R&D > Red Hat EMEA <https://www.redhat.com/> > sbonazzo(a)redhat.com > <https://red.ht/sig> -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-686) Find a better way to show unstable status in CI
by eyal edri (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-686?page=com.atlassian.jira.p… ] eyal edri updated OVIRT-686: ---------------------------- Component/s: monitoring Jenkins Master > Find a better way to show unstable status in CI > ----------------------------------------------- > > Key: OVIRT-686 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-686 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Jenkins Master, monitoring > Reporter: eyal edri > Assignee: infra > Priority: Low > > Today we have the main view on jenkins.ovirt.org showing the unstable list of jobs, > While its effective in showing the current stable jobs, its not optimal in showing trends, history or dashboard view of the jenkins itself. > We need to find a jenkins plugin or a dashboard to show the current status of Jenkins in a more efficient and informative way. > There are numerous dashboards and view plugins, just need to find the right one for oVirt. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2191) remove the mountpoint creation phase from mock_runner
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2191?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2191: -------------------------------- Assignee: Barak Korren (was: infra) Status: In Progress (was: To Do) > remove the mountpoint creation phase from mock_runner > ----------------------------------------------------- > > Key: OVIRT-2191 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2191 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: Barak Korren > > There is a part in mock_runner code that runs mock in order to create mount points for things that are going to be bind mounted into it. Since mock 1.4.10 can create its own mount point we can remove that code from mock runner. > This should reduce the amount of times mock is called from mock_runner -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2192) remove separate initialization function from mock_runner.sh
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2192?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2192: -------------------------------- Epic Link: OVIRT-2189 > remove separate initialization function from mock_runner.sh > ----------------------------------------------------------- > > Key: OVIRT-2192 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2192 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > > Mock runner includes a function that runs mock to initialize the mock environment before it actually gets used. > Theoretically the initialization could have been done in the same {{mock}} invocation that makes use of it. It seems the reason for the separate initialization was that it could be done without including bind mount configuration, because there was a need to pre-create the mount points inside the chroot before bind mounts could be done. > Since mock 1.4.10, it can now create the mount points for bind mounts on its own, a separate hase for creating mount points is no longer needed and OVIRT-2191 tracks the work to remove it. > It seems that once the mount point creation phase is removed, the separate initialization could be removed as well. Preliminary testing showed that this may be more tricky then anticipated though, as the way 'chroothome' mock configuration option is configured by mock_runner causes issues for mock when bootstrap chroots are used (The reason this is not causing issue for the separate initialization is that this option only gets configured along with the bind mount options only when mock is invoked to do actual work). > To remove the separate initialization phase and reduce the amount of times mock is called from 3 to 2, we need to work around the issue above by either submitting a patch to mock itself or finding a work-around that could be used from {{mock_runner.sh}}. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2192) remove separate initialization function from mock_runner.sh
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

Barak Korren created OVIRT-2192: ----------------------------------- Summary: remove separate initialization function from mock_runner.sh Key: OVIRT-2192 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2192 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Barak Korren Assignee: infra Mock runner includes a function that runs mock to initialize the mock environment before it actually gets used. Theoretically the initialization could have been done in the same {{mock}} invocation that makes use of it. It seems the reason for the separate initialization was that it could be done without including bind mount configuration, because there was a need to pre-create the mount points inside the chroot before bind mounts could be done. Since mock 1.4.10, it can now create the mount points for bind mounts on its own, a separate hase for creating mount points is no longer needed and OVIRT-2191 tracks the work to remove it. It seems that once the mount point creation phase is removed, the separate initialization could be removed as well. Preliminary testing showed that this may be more tricky then anticipated though, as the way 'chroothome' mock configuration option is configured by mock_runner causes issues for mock when bootstrap chroots are used (The reason this is not causing issue for the separate initialization is that this option only gets configured along with the bind mount options only when mock is invoked to do actual work). To remove the separate initialization phase and reduce the amount of times mock is called from 3 to 2, we need to work around the issue above by either submitting a patch to mock itself or finding a work-around that could be used from {{mock_runner.sh}}. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2189) Imrpove mock_runner.sh speed, containment and maintainability
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2189?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2189: -------------------------------- Summary: Imrpove mock_runner.sh speed, containment and maintainability (was: Imrpove mock_runner.sh speed and containment) > Imrpove mock_runner.sh speed, containment and maintainability > ------------------------------------------------------------- > > Key: OVIRT-2189 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2189 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > > {{mock_runner.sh}} is the core of all STDCI, yet it has multiple issues and shortcomings that make it less the ideal. Many of the ways {{mock_runner.sh}} does things have to do with the way {{mock}} worked a few years ago when the script was first written. However, {{mock}} had been improved over time, and the new features it includes allow for making improvements to the way {{mock_runner.sh}} works without a very big time investment. > h3. Acceptance Criteria > # {{mock_runner.sh}} uses systemsd-nspawn for containment rather then simple chroot > # {{mock_runner.sh}} can start a chroot from cache in less then 10 seconds. > # {{mock_runner.sh}} does not reinstall the whole chroot if just a few packages in the *.packages file were changed. > # {{mock_runner.sh}} invokes {{mock}} only once when it runs > # {{mock_runner.sh}} can use the mock config files that are shipped with {{mock}} directly without the CI team having to maintain their own set of files. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2189) Imrpove mock_runner.sh speed and containment
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2189?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2189: -------------------------------- Description: {{mock_runner.sh}} is the core of all STDCI, yet it has multiple issues and shortcomings that make it less the ideal. Many of the ways {{mock_runner.sh}} does things have to do with the way {{mock}} worked a few years ago when the script was first written. However, {{mock}} had been improved over time, and the new features it includes allow for making improvements to the way {{mock_runner.sh}} works without a very big time investment. h3. Acceptance Criteria # {{mock_runner.sh}} uses systemsd-nspawn for containment rather then simple chroot # {{mock_runner.sh}} can start a chroot from cache in less then 10 seconds. # {{mock_runner.sh}} does not reinstall the whole chroot if just a few packages in the *.packages file were changed. # {{mock_runner.sh}} invokes {{mock}} only once when it runs # {{mock_runner.sh}} can use the mock config files that are shipped with {{mock}} directly without the CI team having to maintain their own set of files. was: {{mock_runner.sh}} is the core of all STDCI, yet it has multiple issues and shortcomings that make it less the ideal. Many of the ways {{mock_runner.sh}} does things have to do with the way {{mock}} worked a few years ago when the script was first written. However, {{mock}} had been improved over time, and the new features it includes allow for making improvements to the way {{mock_runner.sh}} works without a very big time investment. h3. Acceptance Criteria # {{mock_runner.sh}} uses systemsd-nspawn for containment rather then simple chroot # {{mock_runner.sh}} can start a chroot from cache in less then 10 seconds. # {{mock_runner.sh}} does not reinstall the whole chroot if just a few packages in the *.packages file were changed. # {{mock_runner.sh}} invokes {{mock}} only once when it runs > Imrpove mock_runner.sh speed and containment > -------------------------------------------- > > Key: OVIRT-2189 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2189 > Project: oVirt - virtualization made easy > Issue Type: Epic > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > > {{mock_runner.sh}} is the core of all STDCI, yet it has multiple issues and shortcomings that make it less the ideal. Many of the ways {{mock_runner.sh}} does things have to do with the way {{mock}} worked a few years ago when the script was first written. However, {{mock}} had been improved over time, and the new features it includes allow for making improvements to the way {{mock_runner.sh}} works without a very big time investment. > h3. Acceptance Criteria > # {{mock_runner.sh}} uses systemsd-nspawn for containment rather then simple chroot > # {{mock_runner.sh}} can start a chroot from cache in less then 10 seconds. > # {{mock_runner.sh}} does not reinstall the whole chroot if just a few packages in the *.packages file were changed. > # {{mock_runner.sh}} invokes {{mock}} only once when it runs > # {{mock_runner.sh}} can use the mock config files that are shipped with {{mock}} directly without the CI team having to maintain their own set of files. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0

[JIRA] (OVIRT-2191) remove the mountpoint creation phase from mock_runner
by Barak Korren (oVirt JIRA) 12 Jun '18

12 Jun '18

Barak Korren created OVIRT-2191: ----------------------------------- Summary: remove the mountpoint creation phase from mock_runner Key: OVIRT-2191 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2191 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Barak Korren Assignee: infra There is a part in mock_runner code that runs mock in order to create mount points for things that are going to be bind mounted into it. Since mock 1.4.10 can create its own mount point we can remove that code from mock runner. This should reduce the amount of times mock is called from mock_runner -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100087)

1 0