January 2017 - Infra - oVirt List Archives

[JIRA] (OVIRT-873) Implement Standard-CI with containers
by eyal edri [Administrator] (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-873?page=com.atlassian.jira.p… ] eyal edri [Administrator] reassigned OVIRT-873: ----------------------------------------------- Assignee: Barak Korren (was: infra) > Implement Standard-CI with containers > ------------------------------------- > > Key: OVIRT-873 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-873 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Reporter: Barak Korren > Assignee: Barak Korren > > oVirt's Standard-CI is currently implemented using mock, and this has worked well for us so far. > Changing the implementation to use containers will provide several benefits: > * Faster start-up times - Most container provides have some form of image layering and caching that will be faster as bringing up a basic OS image then installing it with yum like mock does. > * Broader OS support - mock can only run on the Red Hat family of operating systems, and can only emulate those operating systems. Most container providers can both run on and emulate a broader range of operating systems. > * Better isolation and cleanup - Mock only isolates the file system, containers can isolate the file system as well as the networking layer and the process space. > Depending on the container provider, we may gain additional benefits: > * Some container providers like Kubernetes, can manage distributed compute resources across many nodes. This means can can stop managing Jenkins slaves and instead just have the Jenkins master start up containers on the provider. > * Some providers like OpenShift have built-in CI processes for creating and testing container images. > *Note:* At some point, David started an effort going this way: https://gerrit.ovirt.org/#/c/54376/ -- 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 Evgheni Dereveanchin (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1024?page=com.atlassian.jira.… ] Evgheni Dereveanchin updated OVIRT-1024: ---------------------------------------- Resolution: Done Status: Done (was: To Do) Manual replication triggered, projects in sync. > 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

Re: Change in ovirt-engine[master]: packaging: Configure hosts for metrics: Fixes
by Yedidyah Bar David 19 Jan '17

19 Jan '17

On Thu, Jan 19, 2017 at 9:54 AM, Code Review <gerrit(a)ovirt.org> wrote: > From Jenkins CI: > > Jenkins CI has posted comments on this change. > > Change subject: packaging: Configure hosts for metrics: Fixes > ...................................................................... > > > Patch Set 2: > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc24-x86_6… : FAILURE 07:33:58 [INFO] ------------------------------------------------------------------------ 07:33:58 [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.4.0:java (generate-code) on project restapi-definition: An exception occured while executing the Java class. null: InvocationTargetException: NullPointerException -> [Help 1] Any idea? > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc24-x86_64/2… : FAILURE > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-el7-x86_64/33… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-fc25-x86_6… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.1_el7_merge… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_build-artifacts-el7-x86_64… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-3.6_el7_merge… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_check-merged-fc25-x86_64/2… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-master_el7_me… : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_merge… : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/70722 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: Ia665d1b127da5cec58d2b156954748eda0244fa6 > Gerrit-PatchSet: 2 > Gerrit-Project: ovirt-engine > Gerrit-Branch: master > Gerrit-Owner: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Rafael Martins <rmartins(a)redhat.com> > Gerrit-Reviewer: Sandro Bonazzola <sbonazzo(a)redhat.com> > Gerrit-Reviewer: Yedidyah Bar David <didi(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No -- Didi

3 2

[oVirt Jenkins] test-repo_ovirt_experimental_master - Build #4839 - FAILURE!
by jenkins＠jenkins.phx.ovirt.org 19 Jan '17

19 Jan '17

------=_Part_310_2029852094.1484824157007 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Build: http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_master/4839/, Build Number: 4839, Build Status: FAILURE ------=_Part_310_2029852094.1484824157007--

1 1

[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: --------------------------------- last sync was in 2015 - I don't plan to merge something today, but I need it to be updated On Thu, Jan 19, 2017 at 11:21 AM, Evgheni Dereveanchin (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-1024) enable github mirror to ovirt-container-node project
by Evgheni Dereveanchin (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1024?page=com.atlassian.jira.… ] Evgheni Dereveanchin commented on OVIRT-1024: --------------------------------------------- The mirror existed on GitHub, just replication didn't work. Adjusted gerrit config, let's see if it works after next push to the repo. > 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)

2 1

[JIRA] (OVIRT-1052) Allow to run OST with Lago unstable
by Gal Ben Haim (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1052?page=com.atlassian.jira.… ] Gal Ben Haim reassigned OVIRT-1052: ----------------------------------- Assignee: Daniel Belenky (was: infra) > Allow to run OST with Lago unstable > ----------------------------------- > > Key: OVIRT-1052 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1052 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Reporter: Gal Ben Haim > Assignee: Daniel Belenky > > We want to run OST with Lago unstable in order to verify our chnages. > Lago unstable repo: http://resources.ovirt.org/repos/lago/unstable/0.0/latest/rpm/ -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1052) Allow to run OST with Lago unstable
by Gal Ben Haim (oVirt JIRA) 19 Jan '17

19 Jan '17

Gal Ben Haim created OVIRT-1052: ----------------------------------- Summary: Allow to run OST with Lago unstable Key: OVIRT-1052 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1052 Project: oVirt - virtualization made easy Issue Type: New Feature Reporter: Gal Ben Haim Assignee: infra We want to run OST with Lago unstable in order to verify our chnages. Lago unstable repo: http://resources.ovirt.org/repos/lago/unstable/0.0/latest/rpm/ -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1051) foreman 1.7 incompatible with oVirt 4.0
by Evgheni Dereveanchin (oVirt JIRA) 19 Jan '17

19 Jan '17

[ https://ovirt-jira.atlassian.net/browse/OVIRT-1051?page=com.atlassian.jira.… ] Evgheni Dereveanchin reassigned OVIRT-1051: ------------------------------------------- Assignee: Evgheni Dereveanchin (was: infra) > foreman 1.7 incompatible with oVirt 4.0 > --------------------------------------- > > Key: OVIRT-1051 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1051 > Project: oVirt - virtualization made easy > Issue Type: Bug > Reporter: Evgheni Dereveanchin > Assignee: Evgheni Dereveanchin > > After upgrading the Engine in PHX to 4.0 ( OVIRT-779 ) our Foreman can no longer talk to it as it talks to missing endpoints: > There was an error listing VMs: 404 Resource Not Found > Opening this ticket to investigate the options - either upgrade Foreman or decommission it as we're not using it that much any more. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0

[JIRA] (OVIRT-1051) foreman 1.7 incompatible with oVirt 4.0
by Evgheni Dereveanchin (oVirt JIRA) 19 Jan '17

19 Jan '17

Evgheni Dereveanchin created OVIRT-1051: ------------------------------------------- Summary: foreman 1.7 incompatible with oVirt 4.0 Key: OVIRT-1051 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-1051 Project: oVirt - virtualization made easy Issue Type: Bug Reporter: Evgheni Dereveanchin Assignee: infra After upgrading the Engine in PHX to 4.0 ( OVIRT-779 ) our Foreman can no longer talk to it as it talks to missing endpoints: There was an error listing VMs: 404 Resource Not Found Opening this ticket to investigate the options - either upgrade Foreman or decommission it as we're not using it that much any more. -- This message was sent by Atlassian JIRA (v1000.695.1#100025)

1 0