April 2016 - Infra - Ovirt List Archives

[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: -------------------------------------------- Resolution: Done Status: Closed (was: New) db upgrade jobs moved into standard ci. if needed, please update code in check-patch.sh > 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 (v1000.5.0#72002)

8 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-384) DB upgrade jobs are not using engine-setup

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-384?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-384: -------------------------------------------- Resolution: Done Status: Closed (was: New) DB upgrade jobs moved to STD CI. If needed, please update code in check-patch.sh to use engine-setup. > DB upgrade jobs are not using engine-setup > ------------------------------------------ > > Key: OVIRT-384 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-384 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Eli Mesika > Assignee: snaftaly > > 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 -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

8 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-313) deleting yamlized jobs from git doesn't remove them from jenkins

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-313?page=com.atlassian.jira... ] eyal edri [Administrator] reassigned OVIRT-313: ----------------------------------------------- Assignee: Nadav Goldin (was: infra) > deleting yamlized jobs from git doesn't remove them from jenkins > ---------------------------------------------------------------- > > Key: OVIRT-313 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-313 > Project: oVirt - virtualization made easy > Issue Type: Bug > Components: Jenkins > Affects Versions: Production > Reporter: sbonazzo > Assignee: Nadav Goldin > Labels: yaml > > we have an issue with yamlized jobs: removing them from yaml doesn't disable them and doesn't delete them from jenkins. Example is: > http://jenkins.ovirt.org/job/vdsm_master_create-rpms-el6-x86_64_merged/ > that should have been disabled / removed after job dropped by yaml files with commit 7479c7cde296a6bf8b7202f7483e408470e7e58f -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

8 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-306) [Infra docs] add howto on adding yaml patch to ci

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-306?page=com.atlassian.jira... ] eyal edri [Administrator] reassigned OVIRT-306: ----------------------------------------------- Assignee: snaftaly (was: infra) I believe you had a draft somewhere on this? > [Infra docs] add howto on adding yaml patch to ci > ------------------------------------------------- > > Key: OVIRT-306 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-306 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: snaftaly > Priority: Highest > > we need a wiki explaining how to add a new job in jenkins via jjb. > it should be easy to anyone not familiar with jjb. > should contain guidelines on naming conventions and code in the job as well. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

8 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-306) [Infra docs] add howto on adding yaml patch to ci

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-306?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-306: -------------------------------------------- Summary: [Infra docs] add howto on adding yaml patch to ci (was: [wiki] write a wiki page on how developer can add a jenkins job via jjb) > [Infra docs] add howto on adding yaml patch to ci > ------------------------------------------------- > > Key: OVIRT-306 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-306 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: General > Affects Versions: Test > Reporter: eyal edri [Administrator] > Assignee: infra > Priority: Highest > > we need a wiki explaining how to add a new job in jenkins via jjb. > it should be easy to anyone not familiar with jjb. > should contain guidelines on naming conventions and code in the job as well. -- This message was sent by Atlassian JIRA (v1000.5.0#72002)

8 years, 8 months

1
0
0 / 0

[JIRA] (OVIRT-251) chain ovirt-engine merge jobs

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-251?page=com.atlassian.jira... ] eyal edri [Administrator] updated OVIRT-251: -------------------------------------------- Resolution: Done Status: Closed (was: New) not relevant anymore with STD CI. There is another ticket in general to create a pipeline of tests, this is in the hands of developers now, as all the code is in check-patch/check-merged and it can be modified to run as a chain if needed. > 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 (v1000.5.0#72002)

8 years, 8 months

1
0
0 / 0

Permissions to manually re-trigger jenkins-gerrit jobs

by Allon Mureinik

Hi guys, Can you grant me [username: amureini] permissions to manually retrigger gerrit jobs (http://jenkins.ovirt.org/gerrit_manual_trigger/)? Thanks, Allon

8 years, 8 months

2
2
0 / 0

Yaml-ized jobs: Can they be unstable?

by Fabian Deutsch

Hey, is there a way how a yamlized job can become unstable? I'd liek to run some sanity node tests after a run, and mark a run as unstable if this happens. According to the jenkins docs, a job is unstable if one or more publishers fail. Can this be achieved with yamlized jobs? - fabian

8 years, 8 months

2
2
0 / 0

Fwd: CloudSpin is back!

by Brian Proffitt

All: This is Donny, who worked with me to do an oVirt case study last year. He now works for Red Hat, and is interested in donating server space to the oVirt project, if needed. See the message below and let's get the discussion going! Peace, Brian ---------- Forwarded message ---------- From: Donny Davis <dondavis(a)redhat.com> Date: Sat, Apr 23, 2016 at 12:16 AM Subject: CloudSpin is back! To: Brian Proffitt <bproffit(a)redhat.com> Brian, As promised, CloudSpin is back. This time I am bringing a little more to the party. I have some (30) public ipv4 address for the community, I would assume mainly for committers or infra needs. IPv4 address are so hard to get a hold of outside the "cloud", but the one's I do have will be shared for a great project. I also have some dedicated HW servers for the ovirt project. There are currently 3 idle servers with ssd's and a 100+ GB of RAM each. Please let me know what you need, or the dev's want I have an all new DC, with 52TB of SAN storage, and a new blade chassis. Everything is on 10GBE fiber. The only change is the name, I didn't renew cloudspin in time and some **sh*l* took it from me... Anyways, I am on the fortnebula domain now. System status as of now is as follows Ovirt - 6 Nodes with 48GB each and 2x Quad core 2.93 GHZ procs (196 GB of RAM for each is enroute) Openstack - 4 Node with 96GB of ram and 2x Quad core 2.93 GHZ procs Openshift - 3 Node with 96GB of ram and 2x Quad core 2.93 GHZ procs One Critical systems SAN 2TB available (This SAN out preforms SSD storage) One General Storage SAN 52TB available You helped me get to Red Hat, which was my dream. I would like to give something back to the ovirt community that got me here. If the demand is higher for any particular system, then resources will be shifted to the system with the highest demand IE, I will de-commision openstack or openshift to meet the demands required. Also everything is on UPS, and a generator is also going to be installed in the next few weeks. I aim to provide 99% uptime to the ovirt project. Thanks again Brian Donny Davis dondavis(a)redhat.com DOD Public Sector Solution Architect RHCVA Cell 805 814 6800 -- Brian Proffitt Principal Community Analyst Open Source and Standards @TheTechScribe 574.383.9BKP

8 years, 8 months

3
2
0 / 0

ovirt-image-uploader_3.6_build-artifacts-el6-x86_64 failure

by Nadav Goldin

Hey Sandro, http://jenkins.ovirt.org/job/ovirt-image-uploader_3.6_build-artifacts-el6... is failing because: > DEBUG util.py:417: > http://resources.ovirt.org/pub/ovirt-master-snapshot/rpm/el6/repodata/rep...: > [Errno 14] HTTP Error 404 - Not Found > but there is no /rpm/el6 for ovirt-master-snapshot already. should it be ovirt-3.6-snapshot? Thanks Nadav

8 years, 8 months

3
5
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra April 2016