January 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-1024) enable github mirror to ovirt-container-node project
by ybronhei (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1024?page=com.atlassian.jira.… ] ybronhei commented on OVIRT-1024: --------------------------------- lets focus in this ticket on the sync with github/ovirt . please notify when the sync is ready for both projects On Thu, Jan 19, 2017 at 9:56 AM, Barak Korren (oVirt JIRA) < -- *Yaniv Bronhaim.* > enable github mirror to ovirt-container-node project > ---------------------------------------------------- > > Key: OVIRT-1024 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1024 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Because its not enabled by default, only by request as its a manual process. > Adding infra-support to create a ticket on it. > On Thu, Jan 12, 2017 at 5:41 PM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > do you know maybe why doesn't ovirt github in sync with the gerrit? ( > > https://github.com/ovirt/ovirt-container-node) > > > > Thanks. > > > > -- > > *Yaniv Bronhaim.* > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1047) Build and check KubeVirt Demo image
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1047?page=com.atlassian.jira.… ] eyal edri [Administrator] updated OVIRT-1047: --------------------------------------------- Blocked By: pending adding support for github projects to std ci Status: Blocked (was: To Do) Once we'll have the support in yaml, the maintianer should be able to add build artifacts under automation and build the image. > Build and check KubeVirt Demo image > ----------------------------------- > > Key: OVIRT-1047 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1047 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Fabian Deutsch > Assignee: infra > Priority: High > Labels: kubevirt > > Hey, > a job is needed which will build the following image: > https://github.com/kubevirt/demo > $ make clean build check > should do the job. virt-builder and guestfish are used. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1047) Build and check KubeVirt Demo image
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1047?page=com.atlassian.jira.… ] eyal edri [Administrator] commented on OVIRT-1047: -------------------------------------------------- We are currently working on adding support for GitHub project to be used in standard CI. The first project is ovirt-web-ui. Once we'll have the templates ready and merged, adding a new project like KubeVirt should be simple. > Build and check KubeVirt Demo image > ----------------------------------- > > Key: OVIRT-1047 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1047 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Reporter: Fabian Deutsch > Assignee: infra > Priority: High > Labels: kubevirt > > Hey, > a job is needed which will build the following image: > https://github.com/kubevirt/demo > $ make clean build check > should do the job. virt-builder and guestfish are used. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1024) enable github mirror to ovirt-container-node project
by Barak Korren (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1024?page=com.atlassian.jira.… ] Barak Korren commented on OVIRT-1024: ------------------------------------- [~ybronhei(a)redhat.com] Before you go running off to Github and Travis, did you actually try building the containers on our infra? Your repo is already in Gerrit so it shouldn't be hard for you to make Jenkins build containers from it. > enable github mirror to ovirt-container-node project > ---------------------------------------------------- > > Key: OVIRT-1024 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1024 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: eyal edri [Administrator] > Assignee: Evgheni Dereveanchin > > Because its not enabled by default, only by request as its a manual process. > Adding infra-support to create a ticket on it. > On Thu, Jan 12, 2017 at 5:41 PM, Yaniv Bronheim <ybronhei(a)redhat.com> wrote: > > do you know maybe why doesn't ovirt github in sync with the gerrit? ( > > https://github.com/ovirt/ovirt-container-node) > > > > Thanks. > > > > -- > > *Yaniv Bronhaim.* > > > > _______________________________________________ > > Infra mailing list > > Infra(a)ovirt.org > > http://lists.ovirt.org/mailman/listinfo/infra > > > > > -- > Eyal Edri > Associate Manager > RHV DevOps > EMEA ENG Virtualization R&D > Red Hat Israel > phone: +972-9-7692018 > irc: eedri (on #tlv #rhev-dev #rhev-integ) -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1050) Allow manual mirror manipulation for jobs
by Barak Korren (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1050?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1050: ----------------------------------- Assignee: Barak Korren (was: infra) > Allow manual mirror manipulation for jobs > ----------------------------------------- > > Key: OVIRT-1050 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1050 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: Barak Korren > > Right now all jobs that use the mirrors simply take the latest mirrors available when they get invoked. Sometime we may want to manually configure which mirror snapshots are used for a particular job. We should add job parameters and functionality to allow this. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1049) Rename EPEL mirrors to be Lago-compatible.
by Barak Korren (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1049?page=com.atlassian.jira.… ] Barak Korren reassigned OVIRT-1049: ----------------------------------- Assignee: Barak Korren (was: infra) > Rename EPEL mirrors to be Lago-compatible. > ------------------------------------------ > > Key: OVIRT-1049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1049 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: Barak Korren > Priority: High > > Lago requires that all repos have names that end with something like '-el6' or '-el7'. The EPEL mirrors however are currently simply called 'epel6' and 'epel7'. We have to rename the mirros or they won't get injected to OST runs. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1050) Allow manual mirror manipulation for jobs
by Barak Korren (oVirt JIRA) 19 Jan '17

19 Jan '17

Barak Korren created OVIRT-1050: ----------------------------------- Summary: Allow manual mirror manipulation for jobs Key: OVIRT-1050 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1050 Project: oVirt - virtualization made easy Issue Type: Improvement Components: Repositories Mgmt Reporter: Barak Korren Assignee: infra Right now all jobs that use the mirrors simply take the latest mirrors available when they get invoked. Sometime we may want to manually configure which mirror snapshots are used for a particular job. We should add job parameters and functionality to allow this. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1050) Allow manual mirror manipulation for jobs
by Barak Korren (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1050?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1050: -------------------------------- Epic Link: OVIRT-400 > Allow manual mirror manipulation for jobs > ----------------------------------------- > > Key: OVIRT-1050 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1050 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Components: Repositories Mgmt > Reporter: Barak Korren > Assignee: infra > > Right now all jobs that use the mirrors simply take the latest mirrors available when they get invoked. Sometime we may want to manually configure which mirror snapshots are used for a particular job. We should add job parameters and functionality to allow this. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1049) Rename EPEL mirrors to be Lago-compatible.
by Barak Korren (oVirt JIRA) 19 Jan '17

19 Jan '17

Barak Korren created OVIRT-1049: ----------------------------------- Summary: Rename EPEL mirrors to be Lago-compatible. Key: OVIRT-1049 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1049 Project: oVirt - virtualization made easy Issue Type: Improvement Reporter: Barak Korren Assignee: infra Priority: High Lago requires that all repos have names that end with something like '-el6' or '-el7'. The EPEL mirrors however are currently simply called 'epel6' and 'epel7'. We have to rename the mirros or they won't get injected to OST runs. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1049) Rename EPEL mirrors to be Lago-compatible.
by Barak Korren (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1049?page=com.atlassian.jira.… ] Barak Korren updated OVIRT-1049: -------------------------------- Epic Link: OVIRT-400 > Rename EPEL mirrors to be Lago-compatible. > ------------------------------------------ > > Key: OVIRT-1049 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1049 > Project: oVirt - virtualization made easy > Issue Type: Improvement > Reporter: Barak Korren > Assignee: infra > Priority: High > > Lago requires that all repos have names that end with something like '-el6' or '-el7'. The EPEL mirrors however are currently simply called 'epel6' and 'epel7'. We have to rename the mirros or they won't get injected to OST runs. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0