June 2016 - Infra - Ovirt List Archives

[JIRA] (OVIRT-614) ensure ovirt-guest-agent package is installed on all production VMs

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-614?page=com.atlassian.jira... ] Barak Korren commented on OVIRT-614: ------------------------------------ [~ederevea] live snapshots require the agent, as well as resource monitoring and IP info from the engine UI. I think thin memory allocation and ballooning work better when its installed as well. > ensure ovirt-guest-agent package is installed on all production VMs > ------------------------------------------------------------------- > > Key: OVIRT-614 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-614 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Puppet > Reporter: Nadav Goldin > Assignee: infra > > The package should be installed only on the VMs and not on the hypervisors. > On el7 the package is included in epel. -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-614) ensure ovirt-guest-agent package is installed on all production VMs

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-614?page=com.atlassian.jira... ] Evgheni Dereveanchin commented on OVIRT-614: -------------------------------------------- [~ngoldin(a)redhat.com] are you sure we need ovirt-guest-agent, won't qemu-guest-agent be enough? That agent should be enough for VM shutdown. Not sure about IP/FQDN info in the ENgine, yet I'm not sure why exactly you want this agent installed everywhere. > ensure ovirt-guest-agent package is installed on all production VMs > ------------------------------------------------------------------- > > Key: OVIRT-614 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-614 > Project: oVirt - virtualization made easy > Issue Type: Task > Components: Puppet > Reporter: Nadav Goldin > Assignee: infra > > The package should be installed only on the VMs and not on the hypervisors. > On el7 the package is included in epel. -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-610) Engine 4.0 build is failing

by Evgheni Dereveanchin (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-610?page=com.atlassian.jira... ] Evgheni Dereveanchin reassigned OVIRT-610: ------------------------------------------ Assignee: Evgheni Dereveanchin (was: infra) > Engine 4.0 build is failing > --------------------------- > > Key: OVIRT-610 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-610 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Piotr Kliczewski > Assignee: Evgheni Dereveanchin > > Please take a look at [1]. > [1] > http://jenkins.ovirt.org/job/ovirt-engine_4.0_check-merged-fc23-x86_64/19... -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-612: ------------------------------------------------- Hi Paulo. We don't add jenkins jobs directly on jenkins, as we use Jenkins Job Builder to add new jobs and also we have something called 'standard ci' which simplify dramatically the process of adding a new project. to move forward, I suggest you'll post here the source GitHub repos you're using (btw, if you are an oVirt project, you might consider migrating to gerrit.ovirt.org). In addition, please read [1] to see how the STD CI process works and once you're familiar with it, we can help you add the relevant jobs. For now it seems only 'build artifacts' will be needed, if you don't have any other sanity jobs. Also please add to this ticket the commands you're using to build the artifacts (basically you will need to add an 'automation' dir under the root of your projects and add build-artifacts.sh with the command to build it) > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira... ] eyal edri [Administrator] edited comment on OVIRT-612 at 6/28/16 10:07 AM: --------------------------------------------------------------------------- Hi Paulo. We don't add jenkins jobs directly on jenkins, as we use Jenkins Job Builder to add new jobs and also we have something called 'standard ci' which simplify dramatically the process of adding a new project. to move forward, I suggest you'll post here the source GitHub repos you're using (btw, if you are an oVirt project, you might consider migrating to gerrit.ovirt.org). In addition, please read [1] to see how the STD CI process works and once you're familiar with it, we can help you add the relevant jobs. For now it seems only 'build artifacts' will be needed, if you don't have any other sanity jobs. Also please add to this ticket the commands you're using to build the artifacts (basically you will need to add an 'automation' dir under the root of your projects and add build-artifacts.sh with the command to build it) [1] http://infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html was (Author: eedri): Hi Paulo. We don't add jenkins jobs directly on jenkins, as we use Jenkins Job Builder to add new jobs and also we have something called 'standard ci' which simplify dramatically the process of adding a new project. to move forward, I suggest you'll post here the source GitHub repos you're using (btw, if you are an oVirt project, you might consider migrating to gerrit.ovirt.org). In addition, please read [1] to see how the STD CI process works and once you're familiar with it, we can help you add the relevant jobs. For now it seems only 'build artifacts' will be needed, if you don't have any other sanity jobs. Also please add to this ticket the commands you're using to build the artifacts (basically you will need to add an 'automation' dir under the root of your projects and add build-artifacts.sh with the command to build it) > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

by Barak Korren (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira... ] Barak Korren commented on OVIRT-612: ------------------------------------ {quote} Barak Korren If oVirt support to qcow2 images to create new VMs, so it's possible to use them on top of oVirt. However, I guess the best options is host them on 'resources.ovirt.org' to make available anyone (using oVirt or not) to download them. About the 'libguestfs.org' style index file we can for sure use the same to support virt-builder or Lago. {quote} oVirt can useQCOW2 images, but its not trivial to make them available for it to use, at least not until [BZ1343077|https://bugzilla.redhat.com/show_bug.cgi?id=1343077] makes it out the door. {quote} About an automated build, we also can provide this, even with only 4 releases by year. We are using the infrastructure of GitHub (where our source control is hosted) to provide the RPMs and DEBs we build, so since a new version is available there, a new task to create an image with them can be set up. For that, I guess we also need access to oVirt Jenkins to create and configure the tasks, if possible. {quote} It it fairly easy to get stuff running on the oVirt Jenkins, all you need is a repo in oVirt Gerrit (if you don't have one, I can make one for you), and have scripts inside that repo that comply with the [oVirt CI standards|http://ovirt-infra-docs.readthedocs.io/en/latest/CI/Build_and_test_standards.html]. Once you have those running and creating images, we can cover the extra mile of getting the images on resources.ovirt.org. We need to consider how to structure the repos though, would we have one repo for all the images, or one per-image, or perhaps one repo with a branch per-image. With one repo, the build time can be longer, although you could try to parallelise from inside the build script (may be hard to debug). With multiple repos, you use more Gerrit resources and have more manual maintenance, but you can get Jenkins to parallelise for you. With branches, you can have Jenkins parallelise and 'git diff' can make maintenance easier, but you violate the principle of least surprise by making 'master' not mean what people are used to having it mean. > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-599) incorrect CI-1

by Juan Hernández (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-599?page=com.atlassian.jira... ] Juan Hernández commented on OVIRT-599: -------------------------------------- Currently the job uses the following command line: {noformat} clean install findbugs:findbugs -U -P findbugs-general -DskipTests -s artifactory-phx-ovirt-org-settings.xml {noformat} The only thing that needs to be removed is the "-P findbugs-general" option, as now it doesn't have any effect. However this only generates warning in the output of the job nothing serious. The CI-1 is real, but not related to new patches but to an earlier one, already merged. The failure is fixed by this patch that I just merged: restapi: Remove unused field from V3 disks server https://gerrit.ovirt.org/59828 Please rebase your patches and the failure will go away. All in all, it is convenient to remove the "-P findbugs-general" from the command line, but there is no real error to fix in the CI environment. > incorrect CI-1 > -------------- > > Key: OVIRT-599 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-599 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Mucha > Assignee: infra > > Hi, > I probably got false -1 from CI. > http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/20... > https://gerrit.ovirt.org/#/c/53833/ > but when invoked on localhost it builds without problem. > Can you look at it? > thanks, > M. -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

Re: Change in ovirt-engine[ovirt-engine-4.0]: aaa: Empty keystore passwd should be passed as null to KeySt...

by Martin Perina

Hi, could you please take a look? Thanks Martin On Mon, Jun 27, 2016 at 9:08 PM, Jenkins CI <gerrit2(a)gerrit.ovirt.org> wrote: > Jenkins CI has posted comments on this change. > > Change subject: aaa: Empty keystore passwd should be passed as null to > KeyStore.load > ...................................................................... > > > Patch Set 1: > > Build Failed > > http://jenkins.ovirt.org/job/ovirt-engine_4.0_find-bugs_created_test/35/ > : There was an infra issue, please contact infra(a)ovirt.org > > http://jenkins.ovirt.org/job/ovirt-engine_4.0_find-bugs_gerrit/177/ : > SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_4.0_check-patch-el7-x86_64/316/ > : SUCCESS > > http://jenkins.ovirt.org/job/ovirt-engine_4.0_check-patch-fc23-x86_64/315/ > : SUCCESS > > -- > To view, visit https://gerrit.ovirt.org/59857 > To unsubscribe, visit https://gerrit.ovirt.org/settings > > Gerrit-MessageType: comment > Gerrit-Change-Id: I0f9c3706ffe150f848f231ace3ec5995d3ee2d85 > Gerrit-PatchSet: 1 > Gerrit-Project: ovirt-engine > Gerrit-Branch: ovirt-engine-4.0 > Gerrit-Owner: Martin Peřina <mperina(a)redhat.com> > Gerrit-Reviewer: Jenkins CI > Gerrit-Reviewer: Martin Peřina <mperina(a)redhat.com> > Gerrit-Reviewer: Ravi Nori <rnori(a)redhat.com> > Gerrit-Reviewer: gerrit-hooks <automation(a)ovirt.org> > Gerrit-HasComments: No >

7 years, 9 months

2
1
0 / 0

[JIRA] (OVIRT-612) Support to FTP files for Kimchi Project

by Paulo Ricardo Paz Vital (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-612?page=com.atlassian.jira... ] Paulo Ricardo Paz Vital commented on OVIRT-612: ----------------------------------------------- [~bkorren(a)redhat.com] If oVirt support to qcow2 images to create new VMs, so it's possible to use them on top of oVirt. However, I guess the best options is host them on 'resources.ovirt.org' to make available anyone (using oVirt or not) to download them. About the 'libguestfs.org' style index file we can for sure use the same to support virt-builder or Lago. About an automated build, we also can provide this, even with only 4 releases by year. We are using the infrastructure of GitHub (where our source control is hosted) to provide the RPMs and DEBs we build, so since a new version is available there, a new task to create an image with them can be set up. For that, I guess we also need access to oVirt Jenkins to create and configure the tasks, if possible. > Support to FTP files for Kimchi Project > --------------------------------------- > > Key: OVIRT-612 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-612 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Paulo Ricardo Paz Vital > Assignee: infra > > Hello, > Kimchi is a sub-project of oVirt and we are planning to make available to users > simple qcow2 image files of Fedora 23, OpenSUSE 42.1 and Ubuntu 16.04 with > Kimchi installed in there. > We need support to store the files and make them available to download, in a > service like FTP. Since Kimchi mailing lists already use oVirt infrastructure, > I'd like to know if it's possible to be supported by oVirt and how to do that. > Thanks and best regards, Paulo. > -- > Paulo Ricardo Paz Vital > Linux Technology Center, IBM Systems > http://www.ibm.com/linux/ltc/ -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

[JIRA] (OVIRT-599) incorrect CI-1

by eyal edri [Administrator] (oVirt JIRA)

[ https://ovirt-jira.atlassian.net/browse/OVIRT-599?page=com.atlassian.jira... ] eyal edri [Administrator] commented on OVIRT-599: ------------------------------------------------- Sharon, Are those the new jobs? Juan, you mentioned that we don't use the findbugs profile anymore, which maven command should replace it? On Jun 27, 2016 8:29 PM, "Martin Mucha (oVirt JIRA)" < > incorrect CI-1 > -------------- > > Key: OVIRT-599 > URL: https://ovirt-jira.atlassian.net/browse/OVIRT-599 > Project: oVirt - virtualization made easy > Issue Type: By-EMAIL > Reporter: Martin Mucha > Assignee: infra > > Hi, > I probably got false -1 from CI. > http://jenkins.ovirt.org/job/ovirt-engine_master_dao-unit-tests_merged/20... > https://gerrit.ovirt.org/#/c/53833/ > but when invoked on localhost it builds without problem. > Can you look at it? > thanks, > M. -- This message was sent by Atlassian JIRA (v1000.98.4#100004)

7 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

Infra June 2016