May 2018 - Infra - oVirt List Archives

[CQ]: 91277, 2 (ovirt-engine-api-model) failed "ovirt-master" system tests
by oVirt Jenkins 17 May '18

17 May '18

Change 91277,2 (ovirt-engine-api-model) 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/91277/2 For failed test results see: http://jenkins.ovirt.org/job/ovirt-master_change-queue-tester/7622/

1 0

[JIRA] (OVIRT-2031) Use the systemd-nspawn mode for mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2031: ----------------------------------- Summary: Use the systemd-nspawn mode for mock Key: OVIRT-2031 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2031 Project: oVirt - virtualization made easy Issue Type: Improvement Components: mock_runner Reporter: Barak Korren Assignee: infra Mock has long had the ability to use a full container via systemd-nspawn as opposed to a plain chroot. If we can leverage this, we can get many of the benefits of using containers without rebuilding our whole system on a new container backend. There were many issue in the past that prevented us from using that functionality. This ticket if for collecting tickets tracking these issues together. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2031) Use the systemd-nspawn mode for mock
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2031?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2031: -------------------------------- Epic Link: OVIRT-400 > Use the systemd-nspawn mode for mock > ------------------------------------ > > Key: OVIRT-2031 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2031 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: mock_runner > Reporter: Barak Korren > Assignee: infra > Labels: tracker > > Mock has long had the ability to use a full container via systemd-nspawn as opposed to a plain chroot. If we can leverage this, we can get many of the benefits of using containers without rebuilding our whole system on a new container backend. > There were many issue in the past that prevented us from using that functionality. This ticket if for collecting tickets tracking these issues together. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2029: -------------------------------- Issue Type: Improvement (was: Task) > Add cache pre-seed functionality to JJB > --------------------------------------- > > Key: OVIRT-2029 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. > To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2030: ----------------------------------- Summary: Add cache-based deletion option to JJB Key: OVIRT-2030 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2030 Project: oVirt - virtualization made easy Issue Type: Improvement Components: JJB Reporter: Barak Korren Assignee: infra JJB currently supports two ways to delete jobs: # The {{delete}} command which deletes specific jobs that are specified on the command line # The {{--delete-old}] option to the {{update}} command which delete all jobs in Jenkins that are not included in the current update. Both thes options do not do what we want whic is to delete all jobs not included in the current update that were previously manage by JJB. To get this functionality we've made our scripts check the difference between to current and previous commits to find out which jobs were deleted. Instead we would like JJB to have the option for the {{update}} command to inspect the job cache from previous run (Or generated as explained in OVIRT-2029), and delete jobs found there that are not included in current update. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2030) Add cache-based deletion option to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2030?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2030: -------------------------------- Epic Link: OVIRT-400 > Add cache-based deletion option to JJB > -------------------------------------- > > Key: OVIRT-2030 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2030 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > JJB currently supports two ways to delete jobs: > # The {{delete}} command which deletes specific jobs that are specified on the command line > # The {{--delete-old}] option to the {{update}} command which delete all jobs in Jenkins that are not included in the current update. > Both thes options do not do what we want whic is to delete all jobs not included in the current update that were previously manage by JJB. > To get this functionality we've made our scripts check the difference between to current and previous commits to find out which jobs were deleted. Instead we would like JJB to have the option for the {{update}} command to inspect the job cache from previous run (Or generated as explained in OVIRT-2029), and delete jobs found there that are not included in current update. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2029: ----------------------------------- Summary: Add cache pre-seed functionality to JJB Key: OVIRT-2029 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 Project: oVirt - virtualization made easy Issue Type: Task Components: JJB Reporter: Barak Korren Assignee: infra Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2029) Add cache pre-seed functionality to JJB
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-2029?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-2029: -------------------------------- Epic Link: OVIRT-400 > Add cache pre-seed functionality to JJB > --------------------------------------- > > Key: OVIRT-2029 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2029 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: JJB > Reporter: Barak Korren > Assignee: infra > Labels: upstream-contribution > > Since we run JJB from STDCI, we cannot have it rely on the existence of a persistent cache from its previous operation. Since JJB is most efficient when it has such a cache, our STDCI script generates such a cache for it from the contents of the previous commit. > To do that we essentially had to implement parts of the JJB internals (The cache handling) on our own. It desirable to have an option in JJB that would do that instead. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

[JIRA] (OVIRT-2028) Re: [Infra-private] Please remove ykleinbe@redhat.com from infra@ovirt.org
by Barak Korren (oVirt JIRA) 17 May '18

17 May '18

Barak Korren created OVIRT-2028: ----------------------------------- Summary: Re: [Infra-private] Please remove ykleinbe(a)redhat.com from infra(a)ovirt.org Key: OVIRT-2028 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-2028 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Barak Korren Assignee: infra Forwarding to infra-support to get a Jira ticet. On 15 May 2018 at 10:34, Yaniv Kaul <ykaul(a)redhat.com> wrote: > He has left Red Hat long ago, and his email has been forwarded to Allon, > which recently left Red Hat - and now I'm getting those emails. > > TIA, > Y. > > _______________________________________________ > Infra-private mailing list -- infra-private(a)ovirt.org > To unsubscribe send an email to infra-private-leave(a)ovirt.org > oVirt Code of Conduct: https://www.ovirt.org/community/about/community- > guidelines/ > List Archives: > > -- Barak Korren RHV DevOps team , RHCE, RHCi Red Hat EMEA redhat.com | TRIED. TESTED. TRUSTED. | redhat.com/trusted -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100085)

1 0

Re: [ovirt-users] Re: [ovirt-devel] Re: Mailing-Lists upgrade
by Nir Soffer 17 May '18

17 May '18

On Tue, May 8, 2018 at 11:56 AM Zach Brown <zachb1121(a)gmail.com> wrote: > It sounds like the mailing list just upgraded. I'm not sure if it's a bug > or not... But I unsubscribed from this list a long time ago (months ago) > and am now suddenly getting emails from it again. > > Just thought I'd give a heads up in case something may have gone wonky. > Another issue, old links to the mailing list are broken now: https://lists.ovirt.org/mailman/listinfo/devel Try to google "ovirt devel mailing list" to get the old links. We need to configure the http server to redirect to the new mailing list info page when old links are accessed. Nir > > On Tue, May 8, 2018, 3:04 AM Eyal Edri <eedri(a)redhat.com> wrote: > >> Great news! so happy to see this :) >> Thanks for the efforts for making it happen! >> >> On Tue, May 8, 2018 at 6:47 AM, Marc Dequènes (Duck) <duck(a)redhat.com> >> wrote: >> >>> I forgot to cross-post to other lists. Please read announcement below. >>> >>> On 05/08/2018 12:45 PM, Marc Dequènes (Duck) wrote: >>> > Quack, >>> > >>> > On 04/28/2018 09:34 AM, Marc Dequènes (Duck) wrote: >>> > >>> >> A few months ago we had to rollback the migration because of a nasty >>> >> bug. This is fixed in recent versions of Mailman 3 so we're >>> rescheduling >>> >> it on Tuesday 8th during the slot 11:00-12:00 JST. >>> > >>> > Just a word to say the migration happened and no problem was detected. >>> > >>> > The archive posts reindexation is not finished yet, and greylisting is >>> > slowing down things a bit, but it should soon be over. Some information >>> > like post count and little graphs in the web UI are handled via regular >>> > cron jobs and should also soon be accurate. >>> > >>> > Old links to the archives, for pre-migration posts, are still working. >>> > Posts URLS were not stable in Mailman 2 but been synced in >>> > https://lists.ovirt.org/pipermail/ >>> > >>> > You can contact me directly by mail or IRC, or open a JIRA ticket if >>> you >>> > hit any problem. >>> > >>> > \_o< >>> > >>> >>> >>> _______________________________________________ >>> >> Devel mailing list -- devel(a)ovirt.org >>> >> To unsubscribe send an email to devel-leave(a)ovirt.org >>> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s >>> >> >> >> >> -- >> >> Eyal edri >> >> >> MANAGER >> >> RHV DevOps >> >> EMEA VIRTUALIZATION R&D >> >> >> Red Hat EMEA <https://www.redhat.com/> >> <https://red.ht/sig> TRIED. TESTED. TRUSTED. <https://redhat.com/trusted> >> phone: +972-9-7692018 <+972%209-769-2018> >> irc: eedri (on #tlv #rhev-dev #rhev-integ) >> _______________________________________________ >> > Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> > _______________________________________________ > Users mailing list -- users(a)ovirt.org > To unsubscribe send an email to users-leave(a)ovirt.org >

2 6