oVirt 3.6.4 RC1 build starting
by Rafael Martins
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
8 years, 9 months
[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by Yaniv Kaul (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.... ]
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)
8 years, 9 months
[JIRA] (OVIRT-154) [jenkins] look into using travis-ci.org for offloading ubunto/debian jobs
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-154?page=com.atlassian.jira... ]
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)
8 years, 9 months
[JIRA] (OVIRT-95) [jenkins] add job to run upgrade vdsm from version X to version Y
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-95?page=com.atlassian.jira.... ]
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)
8 years, 9 months
[JIRA] (OVIRT-316) port vdsm_master_install-rpm-sanity-fc22_created to dnf
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-316?page=com.atlassian.jira... ]
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)
8 years, 9 months
[JIRA] (OVIRT-383) Re: DB upgrade jobs are not using engine-setup
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-383?page=com.atlassian.jira... ]
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-s...
> >
> > 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)
8 years, 9 months
[JIRA] (OVIRT-439) Gerrit: enable gerrit hooks to move bug status on all oVirt projects
by eyal edri [Administrator] (oVirt JIRA)
eyal edri [Administrator] created OVIRT-439:
-----------------------------------------------
Summary: Gerrit: enable gerrit hooks to move bug status on all oVirt projects
Key: OVIRT-439
URL: https://ovirt-jira.atlassian.net/browse/OVIRT-439
Project: oVirt - virtualization made easy
Issue Type: Task
Reporter: eyal edri [Administrator]
Assignee: infra
Right now the Gerrit hooks located on the Gerrit server only handles VDSM & ovirt-engine projects.
There was a request from some maintainers to add support for more projects.
Please use this ticket to list the required projects to be added:
[~sbonazzola@redhat.com][~fabiand(a)redhat.com][~rbarry][~amarchuk]
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-03-014#72000)
8 years, 9 months
[JIRA] (OVIRT-422) Create jenkins job to compose ovirt 4.0 snaphost early builds
by eyal edri [Administrator] (oVirt JIRA)
[ https://ovirt-jira.atlassian.net/browse/OVIRT-422?page=com.atlassian.jira... ]
eyal edri [Administrator] edited comment on OVIRT-422 at 3/15/16 9:21 AM:
--------------------------------------------------------------------------
Last update on needed steps:
Current status:
"Stage 1" (first snapshot repo without images)
* a. oVirt nightlies are being published as usual
* b. A snapshot was created manually using repoman command, as described in [1]
* c ** missing **
* d. new release rpm for 4.0 was created manually [2]
* e ** missing **
* f. new softlink was created for latest pre-alpha releases [3]
"Stage 2" (final repo with images)
* a. new jobs [4] building node + appliance created using the rpm from [3]
Missing steps:
"Stage 1" (first snapshot repo without images)
* new jenkins job that will run the whole flow starting from 1b, work has started here [5] (@sandro, please correct if i'm wrong)
* new step for checking repoclosure needs to be added as step 'c', code can be taken from [6].
* automate the step of building the release rpm pointing to a specific release dir.
* create new release rpm that will always point to latest snapshot link [3]
* add sanity for first repo using lago, similar to [7], just using the new release rpm to run on the new snapshot (step 1e)
"Stage 2" (repo including images)
* run the job(s) to build appliance, node & ovirt-live using the rpm from [2]. (job for ovirt-live might needs fixing to use release rpm)
* push the new images to the new repo, using TBD job
* run repoclosure to make sure images are install-able, similar to [6]
* run lago sanity tests on whatever is possible (node/appliance/he)
* update softlink [3] to point to new repo with images
* make repo readonly
* move bugs to ON_QA [8]
* send email on release with links + changelog
[1] https://ovirt-jira.atlassian.net/browse/OVIRT-422
[2] http://resources.ovirt.org/pub/ovirt-4.0_prealpha2/rpm/el7/noarch/ovirt-r...
[3] http://resources.ovirt.org/pub/ovirt-4.0_prealpha-latest/
[4] [~fabiand(a)redhat.com] - can you share the links to the jobs?
[5] https://gerrit.ovirt.org/#/c/54626/
[6] http://jenkins.ovirt.org/job/repos_master_check-closure_merged/
[7] http://jenkins.ovirt.org/job/ovirt_master_system-tests/
[8] as first step we'll use the logic of extracting bugs from the commits msg for a list of projects (do we need approval from each maintainer?)
was (Author: eedri):
Last update on needed steps:
Current status:
"Stage 1" (first snapshot repo without images)
* a. oVirt nightlies are being published as usual
* b. A snapshot was created manually using repoman command, as described in [1]
* c ** missing **
* d. new release rpm for 4.0 was created manually [2]
* e ** missing **
* f. new softlink was created for latest pre-alpha releases [3]
"Stage 2" (final repo with images)
* a. new jobs [4] building node + appliance created using the rpm from [3]
Missing steps:
"Stage 1" (first snapshot repo without images)
* new jenkins job that will run the whole flow starting from 1b, work has started here [5] (@sandro, please correct if i'm wrong)
* new step for checking repoclosure needs to be added as step 'c', code can be taken from [6].
* automate the step of building the release rpm pointing to a specific release dir.
* create new release rpm that will always point to latest snapshot link [3]
* add sanity for first repo using lago, similar to [7], just using the new release rpm to run on the new snapshot (step 1e)
"Stage 2" (repo including images)
* run the job(s) to build appliance, node & ovirt-live using the rpm from [2]. (job for ovirt-live might needs fixing to use release rpm)
* push the new images to the new repo, using TBD job
* run repoclosure to make sure images are install-able, similar to [6]
* run lago sanity tests on whatever is possible (node/appliance/he)
* update softlink [3] to point to new repo with images
* make repo readonly
* move bugs to ON_QA [8]
* send email on release with links + changelog
[1] https://ovirt-jira.atlassian.net/browse/OVIRT-422
[2] http://resources.ovirt.org/pub/ovirt-4.0_prealpha2/rpm/el7/noarch/ovirt-r...
[3] http://resources.ovirt.org/pub/ovirt-4.0_prealpha-latest/
[4] [~fabiand(a)redhat.com] - can you share the links to the jobs?
[5] https://gerrit.ovirt.org/#/c/54626/
[6] http://jenkins.ovirt.org/job/repos_master_check-closure_merged/
[7] http://jenkins.ovirt.org/job/ovirt_master_system-tests/
[8] as first step we'll use the logic of extracting bugs from the commits msg for a list of projects (do we need approval from each maintainer?)
> Create jenkins job to compose ovirt 4.0 snaphost early builds
> -------------------------------------------------------------
>
> Key: OVIRT-422
> URL: https://ovirt-jira.atlassian.net/browse/OVIRT-422
> Project: oVirt - virtualization made easy
> Issue Type: Task
> Components: Jenkins, repoman
> Reporter: eyal edri [Administrator]
> Assignee: infra
> Priority: Highest
>
> We need a more static 4.0 snapshots that will be able to be consumed by people who want to verify a certain build without having a rolling nightly build.
> * Add a jjb jenkins job that will run manually/once a week and will create a snap 4.0 repo on
> resources.ovirt.org from latest nightlies (will need to create the repo on resources.ovirt.org/pub/ovirt-4.0/
> * Use repoman with the following cmd: "/usr/bin/repoman ovirt_4.0.0_snap1 add conf:ovirt-4.0-snapshots.repoman --keep-latest 1" [1]
> * This should collect all latest nightlies for 4.0 into a build dir called ovirt_4.0.0_snap1
> * We'll run repoclosure on it once the copy is finished
> * run sanity (either manually or via Lago manual if possible)
> * rhevh team run sanity on the node builds from nightly
> * Create latest_4.0.0_snapshot link to the repo and update it on each release + create new release rpm with that link.
> * Move bugs - either move all MODIFIED bugs with target milestone ovirt-4.0.0 or move only bugs with bug-url from the commit msg.
> * Send email to users/devel with info on release (list of bugs + link to release rpm).
> [2] cat ovirt-4.0-snapshots.repoman (the conf file)
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot:latest
> rec:http://plain.resources.ovirt.org/pub/ovirt-master-snapshot-static:latest
--
This message was sent by Atlassian JIRA
(v7.2.0-OD-03-014#72000)
8 years, 9 months
