- Infra - oVirt List Archives

[JIRA] (OVIRT-440) Gerrit's project name change request
by eyal edri [Administrator] (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-440?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-440: ------------------------------------------------- I'm not sure its possible to rename, we might need to create a new git repo. [~dcaroest][~amarchuk] ? > Gerrit's project name change request > ------------------------------------ > > Key: OVIRT-440 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-440 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Amit Aviram > Assignee: infra > > Hello. > We've initiated the "vdsm-imaged" project, and need to change its name to > "ovirt-imageio". what should we do? -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

2 1

[JIRA] (OVIRT-440) Gerrit's project name change request
by Amit Aviram (oVirt JIRA) 15 Mar '16

15 Mar '16

Amit Aviram created OVIRT-440: --------------------------------- Summary: Gerrit's project name change request Key: OVIRT-440 URL: https://ovirt-jira.atlassian.net/browse/OVIRT-440 Project: oVirt - virtualization made easy Issue Type: By-EMAIL Reporter: Amit Aviram Assignee: infra Hello. We've initiated the "vdsm-imaged" project, and need to change its name to "ovirt-imageio". what should we do? -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

oVirt 3.6.4 RC1 build starting
by Rafael Martins 15 Mar '16

15 Mar '16

Fyi oVirt products maintainers, An oVirt build for an official release is going to start right now. If you're a maintainer for any of the projects included in oVirt distribution and you have changes in your package ready to be released please: - bump version and release to be GA ready - tag your release within git (implies a GitHub Release to be automatically created) - build your packages within jenkins / koji / copr / whatever - verify all bugs on MODIFIED have target release and target milestone set. Thanks, Rafael

1 0

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by Yaniv Kaul (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.pl… ] Yaniv Kaul commented on OVIRT-95: --------------------------------- Theoretically, of course. Practically, I'm not sure Lago is ready yet for upgrade tests (you need to add that upgrade tests to the previous version or something). Interesting topic to tackle actually - upgrade from 3.6 to master. Let me think about it a bit (especially concerned with the new repos and how we add them intelligently). > [jenkins] add job to run upgrade vdsm from version X to version Y > ----------------------------------------------------------------- > > Key: OVIRT-95 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: infra,vdsm,jenkins > > vdsm upgrade should be tested. (following on bug that was found). > suggested flow: > 1. install vdsm version X (e.g from 3.2) > 2. build latest vdsm version (3.3 or master) > 3. yum update vdsm > 4. check if service is up and running. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-154) [jenkins] look into using travis-ci.org for offloading ubunto/debian jobs
by eyal edri [Administrator] (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-154?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-154: -------------------------------------------- Resolution: Won't Do Status: Closed (was: New) Debian isn't in scope for now and no active work is being done for add jobs / support for it. If it will be relevant, we still might want to handle it on jenkins.ovirt.org with standard CI, rather than monitor 2 CI systems. > [jenkins] look into using travis-ci.org for offloading ubunto/debian jobs > ------------------------------------------------------------------------- > > Key: OVIRT-154 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-154 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: jenkins,ubunto > > travis-ci offers free jobs for open source projects, might worth adding there some jobs to run on ubunto/debian. > need to see who can manage it/handle it \\- can developers add it or it needs infra assistance. > some limitations/disadvantages: > \\- works only from github (will need to work from github mirrors) > \\- doesn't support per patch jobs, just per commit. > more info at: https://travis-ci.org/ -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by eyal edri [Administrator] (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.pl… ] eyal edri [Administrator] commented on OVIRT-95: ------------------------------------------------ [~ykaul][~ybronhei(a)redhat.com] Can we add a functional test based on Lago to vdsm to do this? Upgrade vdsm from 3.5->3.6, 3.6->3.6,3.6->4.0. > [jenkins] add job to run upgrade vdsm from version X to version Y > ----------------------------------------------------------------- > > Key: OVIRT-95 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-95 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Labels: infra,vdsm,jenkins > > vdsm upgrade should be tested. (following on bug that was found). > suggested flow: > 1. install vdsm version X (e.g from 3.2) > 2. build latest vdsm version (3.3 or master) > 3. yum update vdsm > 4. check if service is up and running. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-162) add pyflakes test job
by eyal edri [Administrator] (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-162?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-162: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) > add pyflakes test job > --------------------- > > Key: OVIRT-162 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-162 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Jenkins > Affects Versions: Test > Reporter: danken > Assignee: infra > > as requested in http://lists.ovirt.org/pipermail/infra/2014-April/005957.html , we'd like to have a fine-grained pyflakes tests that runs on every patch. > It can do a simple > ./autogen \--system > PEP8=true make check-local -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-251) chain ovirt-engine merge jobs
by eyal edri [Administrator] (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-251?page=com.atlassian.jira.p… ] eyal edri [Administrator] commented on OVIRT-251: ------------------------------------------------- [~sbonazzola(a)redhat.com] is this relevant also for 3.6 with standard ci? > chain ovirt-engine merge jobs > ----------------------------- > > Key: OVIRT-251 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-251 > Project: oVirt - virtualization made easy > Issue Type: New Feature > Components: Jenkins > Affects Versions: Test > Reporter: sbonazzo > Assignee: infra > > Currently a merge event triggers: > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged > All of them performs builds at different stages. > I suggest to run first > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_find-bugs_merged > and if it finish with success, I suggest to use rpms built from > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_create-rpms_merged > for running: > \\- http://jenkins.ovirt.org/job/ovirt-engine_3.5_upgrade-from-3.4_merged > otherwise abort the chain as soon as it fails. > This will reduce the times we rebuild the same code and the slaves load. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-316) port vdsm_master_install-rpm-sanity-fc22_created to dnf
by eyal edri [Administrator] (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-316?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-316: -------------------------------------------- Resolution: Fixed Status: Closed (was: New) closing due to no response from requester. please re-open if relevant. > port vdsm_master_install-rpm-sanity-fc22_created to dnf > ------------------------------------------------------- > > Key: OVIRT-316 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-316 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: danken > Assignee: infra > > Fedora 22 is going to have dnf instead of yum. Currently, the job fails with > bq. # yum install \-y /tmp/*rpm > bq. Yum command has been deprecated, use dnf instead. > due to that. > I did not verify my over-optimistic patch https://gerrit.ovirt.org/#/c/40306/ which is not enough to solve the issue. > Until this is done, the job should be disabled, as it persistently fails. -- This message was sent by Atlassian JIRA (v7.2.0-OD-03-014#72000)

1 0

[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
by eyal edri [Administrator] (oVirt JIRA) 15 Mar '16

15 Mar '16

[ https://ovirt-jira.atlassian.net/browse/OVIRT-383?page=com.atlassian.jira.p… ] eyal edri [Administrator] updated OVIRT-383: -------------------------------------------- Issue Type: Sub-task (was: By-EMAIL) Parent: OVIRT-384 > Re: DB upgrade jobs are not using engine-setup > ---------------------------------------------- > > Key: OVIRT-383 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-383 > Project: oVirt - virtualization made easy > Issue Type: Sub-task > Reporter: eyal edri [Administrator] > Assignee: snaftaly > > Also replacing support-infra with infra-support which is the right email to > open a ticket. > e. > On Wed, Jan 13, 2016 at 4:49 PM, Eyal Edri <eedri(a)redhat.com> wrote: > > Hi, > > > > The scripts used to run the job can be found here [1]. > > Specifically: > > > > ovirt-engine_upgrade-db.cleanup.sh > > ovirt-engine_upgrade-db.sh > > > > If you can submit a patch to replace the logic to use engine-setup > > instead, the jobs will update automatically via yaml to use the new logic. > > infra team can help with verification if needed. > > > > Eyal. > > > > [1] > > https://gerrit.ovirt.org/gitweb?p=jenkins.git;a=tree;f=jobs/confs/shell-scr… > > > > On Wed, Jan 13, 2016 at 4:36 PM, Eli Mesika <emesika(a)redhat.com> wrote: > > > >> Hi > >> > >> Currently DB upgrade jobs are using schema.sh script and not engine-setup > >> This may cause CI upgrade tests to be successful while they are actually > >> failed when running from engine-setup > >> Since we are using engine-setup to upgrade the database, CI tests must > >> use the same exact method in order to be reliable > >> I had faced this week 2 different cases when my patches passed CI but > >> failed actually engine-setup causing a loose of time to me and to other > >> that already rebased on a problematic patch. > >> > >> > >> Thanks > >> Eli Mesika > >> > >> _______________________________________________ > >> Infra mailing list > >> Infra(a)ovirt.org > >> http://lists.ovirt.org/mailman/listinfo/infra > >> > >> > >> > > > > > > -- > > Eyal Edri > > Associate Manager > > EMEA ENG Virtualization R&D > > Red Hat Israel > > > > phone: +972-9-7692018 > > irc: eedri (on #tlv #rhev-dev #rhev-integ) > > > -- > Eyal Edri > Associate Manager > 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 (v7.2.0-OD-03-014#72000)

1 0