January 2018 - Infra - oVirt List Archives

Access to run OST
by Mor Kalfon 03 Jan '18

03 Jan '18

Dear Infra team, Would it be possible to get a permission to test my (first) patch in OST? https://gerrit.ovirt.org/#/c/85930/ Regards, -- Mor Kalfon RHV Networking Team Red Hat IL-Raanana Tel: +972-54-6514148

2 1

[JIRA] (OVIRT-1826) Re: [lago-project/lago] Log running ssh_script (#691)
by Barak Korren (oVirt JIRA) 03 Jan '18

03 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1826?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1826: -------------------------------- Resolution: Won't Fix Status: Done (was: To Do) no need to open a ticket for this, this is a task for lago maintainers, not the ovirt infa team (there is an intersection between the two groups, thoug, but lago tasks are tracked in github), and I'm sure they got enough emails about your PR by now) > Re: [lago-project/lago] Log running ssh_script (#691) > ----------------------------------------------------- > > Key: OVIRT-1826 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1826 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Yedidyah Bar David > Assignee: infra > > Can someone please approve me and/or review etc.? Thanks. > On Wed, Jan 3, 2018 at 12:40 PM, oVirt infra bot <notifications(a)github.com> > wrote: > > Hello contributor, thanks for submitting a PR for this project! > > > > I am the bot who triggers "standard-CI" builds for this project. > > As a security measure, I will not run automated tests on PRs that are not > > from white-listed contributors. > > > > In order to allow automated tests to run, please ask one of the project > > maintainers to review the code and then do one of the following: > > > > 1. Type ci test please on this PR to trigger automated tests for it. > > 2. Type ci add to whitelist on this PR to trigger automated tests for > > it and also add you to the contributor white-list so that your future PRs > > will be tested automatically. > > 3. If you are planning to contribute to more than one project, maybe > > it's better to ask them to add you to the project organization, so you'll > > be able to run tests for all the organization's projects. > > > > — > > You are receiving this because you authored the thread. > > Reply to this email directly, view it on GitHub > > <https://github.com/lago-project/lago/pull/691#issuecomment-354982144>, > > or mute the thread > > <https://github.com/notifications/unsubscribe-auth/AFHUmCbSUZh41h8QBFIbK5JIc…> > > . > > > -- > Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1826) Re: [lago-project/lago] Log running ssh_script (#691)
by Yedidyah Bar David (oVirt JIRA) 03 Jan '18

03 Jan '18

This is a multi-part message in MIME format... ------------=_1514976334-10643-377 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Yedidyah Bar David created OVIRT-1826: ----------------------------------------- Summary: Re: [lago-project/lago] Log running ssh_script (#691) Key: OVIRT-1826 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1826 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra Can someone please approve me and/or review etc.? Thanks. On Wed, Jan 3, 2018 at 12:40 PM, oVirt infra bot <notifications(a)github.com> wrote: > Hello contributor, thanks for submitting a PR for this project! > > I am the bot who triggers "standard-CI" builds for this project. > As a security measure, I will not run automated tests on PRs that are not > from white-listed contributors. > > In order to allow automated tests to run, please ask one of the project > maintainers to review the code and then do one of the following: > > 1. Type ci test please on this PR to trigger automated tests for it. > 2. Type ci add to whitelist on this PR to trigger automated tests for > it and also add you to the contributor white-list so that your future = PRs > will be tested automatically. > 3. If you are planning to contribute to more than one project, maybe > it's better to ask them to add you to the project organization, so you= 'll > be able to run tests for all the organization's projects. > > =E2=80=94 > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/lago-project/lago/pull/691#issuecomment-354982144>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/AFHUmCbSUZh41h8QBFIbK5= JIcoZtU3Daks5tG1kygaJpZM4RRklz> > . > --=20 Didi -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514976334-10643-377 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: quoted-printable <html><body> <h3>Yedidyah Bar David created OVIRT-1826:</h3> <pre> Summary: Re: [lago-project/lago] Log running ssh_script (#691) Key: OVIRT-1826 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1826 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Yedidyah Bar David Assignee: infra</pre> <p>Can someone please approve me and/or review etc.? Thanks.</p> <p>On Wed, Jan 3, 2018 at 12:40 PM, oVirt infra bot <notifications@githu= b.com> wrote:</p> <blockquote><p>Hello contributor, thanks for submitting a PR for this proje= ct!</p> <p>I am the bot who triggers “standard-CI” builds for this proj= ect. As a security measure, I will not run automated tests on PRs that are = not from white-listed contributors.</p> <p>In order to allow automated tests to run, please ask one of the project = maintainers to review the code and then do one of the following:</p> <pre>1. Type ci test please on this PR to trigger automated tests for it. 2. Type ci add to whitelist on this PR to trigger automated tests for it and also add you to the contributor white-list so that your future PRs will be tested automatically. 3. If you are planning to contribute to more than one project, maybe it's better to ask them to add you to the project organization, so you'll be able to run tests for all the organization's projects.</pre> <p>=E2=80=94 You are receiving this because you authored the thread. Reply = to this email directly, view it on GitHub <<a href=3D"https://github.com= /lago-project/lago/pull/691#issuecomment-354982144">https://github.com/lago= -project/lago/pull/691#issuecomment-354982144</a>>, or mute the thread &= lt;<a href=3D"https://github.com/notifications/unsubscribe-auth/AFHUmCbSUZh= 41h8QBFIbK5JIcoZtU3Daks5tG1kygaJpZM4RRklz">https://github.com/notifications= /unsubscribe-auth/AFHUmCbSUZh41h8QBFIbK5JIcoZtU3Daks5tG1kygaJpZM4RRklz</a>&= gt; .</p></blockquote> <p>— Didi</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#1000= 75)</p> <img src=3D"https://u4043402.ct.sendgrid.net/wf/open?upn=3Di5TMWGV99amJbNxJ= pSp2-2BJ33BSM3tuiUfRTk64K-2BOjHk0t8rl8MpMdxMsjDtQ-2B6XOX7pNdoswlBAGXkxIW25g= p1cBdrqzGA1YyFPKxhR1tde8I-2Fd-2F6hAZASgSEDnTN-2BZhF71Pw5-2BlaTduml3toFyueyT= BXC8wz9tCMysHoyhTf1KX-2FmOTQN1ncO7U5qung-2FXhk4qovCffitmeJ1CbPHJCRP42OFfxYJ= QfGsnB9WY00RngSd8AQuseAa94K5AINOnqPpoBIdp4o-2B84rOBKpo5a-2BdXHEbmx0ZG2D-2Bg= arfeigQE23OWLzb1Fe8tPEqDZTEkHF8Dunwxu4fKSbjoHmWN7UOND8mfhCZB38aS5ER4OcgHVeR= M8Te-2BCdk1R3lAsxiGikPm7J-2BblYqBfbDyRagyYryskP9m6ikhfLkpvLDEvFlo9OfMLwJHat= h7B82IkYrz" alt=3D"" width=3D"1" height=3D"1" border=3D"0" style=3D"height:= 1px !important;width:1px !important;border-width:0 !important;margin-top:0 = !important;margin-bottom:0 !important;margin-right:0 !important;margin-left= :0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-= right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514976334-10643-377--

1 0

[vdsm][tag][master] Vdsm tagged: v4.20.10
by Francesco Romani 03 Jan '18

03 Jan '18

Hi infra, we have a new Vdsm tag on branch master for oVirt 4.2.1: tag v4.20.10 Tagger: Francesco Romani <fromani(a)redhat.com> Date: Wed Jan 3 11:01:15 2018 +0100 Vdsm 4.20.10 for oVirt 4.2.1 RC 1 commit 00bc04e666b7660d052f04718a9cf10cf7848235 +++ NOTE ABOUT BRANCHING: * We are merging again patches targeted for 4.2.1 on master * We don't yet have plans to branch out ovirt-4.2 from master. Following the usual Vdsm habit, we will branch out late, *after* Engine does. Bests, -- Francesco Romani Senior SW Eng., Virtualization R&D Red Hat IRC: fromani github: @fromanirh

1 0

[JIRA] (OVIRT-1825) Document the process for setting up a "downstream" STDCI system
by Barak Korren (oVirt JIRA) 03 Jan '18

03 Jan '18

This is a multi-part message in MIME format... ------------=_1514960598-31600-208 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1825?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1825: ----------------------------------- Assignee: Barak Korren (was: infra) > Document the process for setting up a "downstream" STDCI system > --------------------------------------------------------------- > > Key: OVIRT-1825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1825 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: documentation, standard-ci > > With the introduction of so called "upstream source" dependencies, it had become possible to use the '{{jenkins}}' repo and the STDCI code in it as a library for building STDCI-compatible jenkins servers. > This process had been successfully used to setup the RHV CI system inside Red Hat. > The processes of setting up a non-oVirt STDCI server should be documented to make it accessible for others. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514960598-31600-208 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1825?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren reassigned OVIRT-1825:</h3> <pre>Assignee: Barak Korren (was: infra)</pre> <blockquote><h3>Document the process for setting up a “downstream” STDCI system</h3> <pre> Key: OVIRT-1825 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1825 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: Barak Korren Labels: documentation, standard-ci</pre> <p>With the introduction of so called “upstream source” dependencies, it had become possible to use the ‘{{jenkins}}’ repo and the STDCI code in it as a library for building STDCI-compatible jenkins servers. This process had been successfully used to setup the RHV CI system inside Red Hat. The processes of setting up a non-oVirt STDCI server should be documented to make it accessible for others.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514960598-31600-208--

1 0

[JIRA] (OVIRT-1825) Document the process for setting up a "downstream" STDCI system
by Barak Korren (oVirt JIRA) 03 Jan '18

03 Jan '18

Barak Korren created OVIRT-1825: ----------------------------------- Summary: Document the process for setting up a "downstream" STDCI system Key: OVIRT-1825 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1825 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra With the introduction of so called "upstream source" dependencies, it had become possible to use the '{{jenkins}}' repo and the STDCI code in it as a library for building STDCI-compatible jenkins servers. This process had been successfully used to setup the RHV CI system inside Red Hat. The processes of setting up a non-oVirt STDCI server should be documented to make it accessible for others. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1825) Document the process for setting up a "downstream" STDCI system
by Barak Korren (oVirt JIRA) 03 Jan '18

03 Jan '18

This is a multi-part message in MIME format... ------------=_1514960549-24874-409 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit [ https://ovirt-jira.atlassian.net/browse/OVIRT-1825?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1825: -------------------------------- Epic Link: OVIRT-400 > Document the process for setting up a "downstream" STDCI system > --------------------------------------------------------------- > > Key: OVIRT-1825 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1825 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: documentation, standard-ci > > With the introduction of so called "upstream source" dependencies, it had become possible to use the '{{jenkins}}' repo and the STDCI code in it as a library for building STDCI-compatible jenkins servers. > This process had been successfully used to setup the RHV CI system inside Red Hat. > The processes of setting up a non-oVirt STDCI server should be documented to make it accessible for others. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514960549-24874-409 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <pre>[ https://ovirt-jira.atlassian.net/browse/OVIRT-1825?page=com.atlassian.jira.… ]</pre> <h3>Barak Korren updated OVIRT-1825:</h3> <pre>Epic Link: OVIRT-400</pre> <blockquote><h3>Document the process for setting up a “downstream” STDCI system</h3> <pre> Key: OVIRT-1825 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1825 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra Labels: documentation, standard-ci</pre> <p>With the introduction of so called “upstream source” dependencies, it had become possible to use the ‘{{jenkins}}’ repo and the STDCI code in it as a library for building STDCI-compatible jenkins servers. This process had been successfully used to setup the RHV CI system inside Red Hat. The processes of setting up a non-oVirt STDCI server should be documented to make it accessible for others.</p></blockquote> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514960549-24874-409--

1 0

[JIRA] (OVIRT-1824) Document pusher.py
by Barak Korren (oVirt JIRA) 03 Jan '18

03 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1824?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1824: ----------------------------------- Assignee: Barak Korren (was: infra) > Document pusher.py > ------------------ > > Key: OVIRT-1824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1824 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: Barak Korren > Labels: documentation, poll-upstream-sources, standard-ci > > '{{pusher.py}}' is a tool for automated pushing and merging of patches. It is used as part of the upstream source polling process. > We should have some documentation about this tool in infra-docs apart from its built-in '{{--help}}' option. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1824) Document pusher.py
by Barak Korren (oVirt JIRA) 03 Jan '18

03 Jan '18

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1824?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1824: -------------------------------- Epic Link: OVIRT-400 > Document pusher.py > ------------------ > > Key: OVIRT-1824 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1824 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: oVirt CI > Reporter: Barak Korren > Assignee: infra > Labels: documentation, poll-upstream-sources, standard-ci > > '{{pusher.py}}' is a tool for automated pushing and merging of patches. It is used as part of the upstream source polling process. > We should have some documentation about this tool in infra-docs apart from its built-in '{{--help}}' option. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)

1 0

[JIRA] (OVIRT-1824) Document pusher.py
by Barak Korren (oVirt JIRA) 03 Jan '18

03 Jan '18

This is a multi-part message in MIME format... ------------=_1514960007-28457-369 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Barak Korren created OVIRT-1824: ----------------------------------- Summary: Document pusher.py Key: OVIRT-1824 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1824 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra '{{pusher.py}}' is a tool for automated pushing and merging of patches. It is used as part of the upstream source polling process. We should have some documentation about this tool in infra-docs apart from its built-in '{{--help}}' option. -- This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075) ------------=_1514960007-28457-369 Content-Type: text/html; charset="UTF-8" Content-Disposition: inline Content-Transfer-Encoding: 7bit <html><body> <h3>Barak Korren created OVIRT-1824:</h3> <pre> Summary: Document pusher.py Key: OVIRT-1824 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1824 Project: oVirt - virtualization made easy Issue Type: Improvement Components: oVirt CI Reporter: Barak Korren Assignee: infra</pre> <p>‘{{pusher.py}}’ is a tool for automated pushing and merging of patches. It is used as part of the upstream source polling process.</p> <p>We should have some documentation about this tool in infra-docs apart from its built-in ‘{{--help}}’ option.</p> <p>— This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100075)</p> <img src="https://u4043402.ct.sendgrid.net/wf/open?upn=i5TMWGV99amJbNxJpSp2-2BJ33BSM3…" alt="" width="1" height="1" border="0" style="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;"/> </body></html> ------------=_1514960007-28457-369--

1 0