Re: [ovirt-devel] Packages for oVirt 3.5.1 RC
On 01/15, Sandro Bonazzola wrote: Il 15/01/2015 13:50, Sandro Bonazzola ha scritto: Thanks Alon for your input, here's the updated list: # oVirt Engine: # Hash: # * 4f0c48e - restapi: Option to override firewall during install # waiting on (fc20 done, el6 and el7 still building) http://jenkins.ovirt.org/job/manual-build-tarball/458/ Still building: Started 9 hr 16 min ago Build has been executing for 9 hr 16 min on fc20-vm01.phx.ovirt.org And since it's at 18 of 40 permutations while building the webadmin interface on EL7, I think it may be ready for tomorrow noon. Will try to release tomorrow afternoon if the job won't fail during the night. I need the tarball to rebuild, cna you tell me where to get it? Infra, we need to figure out what's wrong on those slaves. # vdsm-jsonrpc-java http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-el6-x86_64_merged/18/ http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-el7-x86_64_merged/15/ http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-fc20-x86_64_merged/22/ # ovirt-engine-extension-aaa-ldap http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/11/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/11/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/11/ARCH=x86_64,DISTRIBUTION=epel-7/ # ovirt-engine-extension-aaa-misc # Unchanged: # http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=fedora-20/ # http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-7/ # ovirt-engine-extension-logger-log4j # Unchanged: # http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=fedora-20/ # http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-7/ # DWH http://jenkins.ovirt.org/job/manual-build-tarball/452/label=el6/ http://jenkins.ovirt.org/job/manual-build-tarball/452/label=el7/ http://jenkins.ovirt.org/job/manual-build-tarball/452/label=fc20/ # Reports http://jenkins.ovirt.org/job/manual-build-tarball/453/label=el6/ http://jenkins.ovirt.org/job/manual-build-tarball/453/label=el7/ http://jenkins.ovirt.org/job/manual-build-tarball/453/label=fc20/ # Unchanged since 3.5 #ovirt-guest-tools # VDSM (from jenkins): http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-el6-x86_64_merged/154/ http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-el7-x86_64_merged/151/ http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-fc20-x86_64_merged/151/ # OTOPI http://jenkins.ovirt.org/job/otopi_any_create-rpms_manual/15/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/otopi_any_create-rpms_manual/15/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/otopi_any_create-rpms_manual/15/ARCH=x86_64,DISTRIBUTION=epel-7/ # oVirt Host Deploy http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-7/ # Hosted Engine Setup http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-el6-x86_64_merged/44/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-el7-x86_64_merged/38/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-fc20-x86_64_merged/43/ # Hosted Engine HA http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-el6-x86_64_merged/35/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-el7-x86_64_merged/26/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-fc20-x86_64_merged/34/ # Log Collector http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-el6-x86_64_merged/19/ http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-el7-x86_64_merged/8/ http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-fc20-x86_64_merged/18/ # ISO Uploader http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-el6-x86_64_merged/11/ http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-el7-x86_64_merged/1/ http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-fc20-x86_64_merged/11/ # Image Uploader
[ovirt-devel] vdsm: unit test breakage on el6
Some of oVirt-3.6 new features such as http://www.ovirt.org/Features/hostdev_passthrough would not be available on el6. However, we would like to be able to build and run legacy features on el6. Therefore, please avoid using fancy python 2.7 syntax. Unit tests on el6 should keep passing. Regards, Dan. http://jenkins.ovirt.org/job/vdsm_master_unit_tests_gerrit_el/14115/console ERROR: testParseSRIOV_PFDeviceParams (hostdevTests.HostdevTests) -- Traceback (most recent call last): File /home/jenkins/workspace/vdsm_master_unit_tests_gerrit_el/vdsm/tests/hostdevTests.py, line 470, in testParseSRIOV_PFDeviceParams deviceXML = hostdev._parse_device_params(_SRIOV_PF_XML) File /home/jenkins/workspace/vdsm_master_unit_tests_gerrit_el/vdsm/vdsm/hostdev.py, line 77, in _parse_device_params params['physfn'] = _pci_address_to_name(**address.attrib) File /home/jenkins/workspace/vdsm_master_unit_tests_gerrit_el/vdsm/vdsm/hostdev.py, line 42, in _pci_address_to_name function[2:]) ValueError: zero length field name in format ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
[ovirt-devel] Packages for oVirt 3.5.1 RC
Hi, We're going to compose 3.5.1 RC with the following packages. ACTION: please review the list and raise any change you need ASAP. # oVirt Engine: waiting on http://jenkins.ovirt.org/job/manual-build-tarball/458/ Hash: * 4f0c48e - restapi: Option to override firewall during install # vdsm-jsonrpc-java http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-el6-x86_64_merged/18/ http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-el7-x86_64_merged/15/ http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-fc20-x86_64_merged/22/ #ovirt-engine-extension-aaa-ldap http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=epel-7/ # ovirt-engine-extension-aaa-misc http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-7/ # ovirt-engine-extension-logger-log4j http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-7/ # DWH http://jenkins.ovirt.org/job/manual-build-tarball/452/label=el6/ http://jenkins.ovirt.org/job/manual-build-tarball/452/label=el7/ http://jenkins.ovirt.org/job/manual-build-tarball/452/label=fc20/ # Reports http://jenkins.ovirt.org/job/manual-build-tarball/453/label=el6/ http://jenkins.ovirt.org/job/manual-build-tarball/453/label=el7/ http://jenkins.ovirt.org/job/manual-build-tarball/453/label=fc20/ # Unchanged since 3.5 #ovirt-guest-tools # VDSM (from jenkins): http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-el6-x86_64_merged/154/ http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-el7-x86_64_merged/151/ http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-fc20-x86_64_merged/151/ # OTOPI http://jenkins.ovirt.org/job/otopi_master_create-rpms_merged/label=el6/671/ http://jenkins.ovirt.org/job/otopi_master_create-rpms_merged/label=el7/671/ http://jenkins.ovirt.org/job/otopi_master_create-rpms_merged/label=fc20/671/ # oVirt Host Deploy http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=epel-7/ # Hosted Engine Setup http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-el6-x86_64_merged/44/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-el7-x86_64_merged/38/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-fc20-x86_64_merged/43/ # Hosted Engine HA http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-el6-x86_64_merged/35/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-el7-x86_64_merged/26/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-fc20-x86_64_merged/34/ # Log Collector http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-el6-x86_64_merged/19/ http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-el7-x86_64_merged/8/ http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-fc20-x86_64_merged/18/ # ISO Uploader http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-el6-x86_64_merged/11/ http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-el7-x86_64_merged/1/ http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-fc20-x86_64_merged/11/ # Image Uploader http://jenkins.ovirt.org/job/ovirt-image-uploader_3.5_create-rpms-el6-x86_64_merged/11/ http://jenkins.ovirt.org/job/ovirt-image-uploader_3.5_create-rpms-el7-x86_64_merged/1/ http://jenkins.ovirt.org/job/ovirt-image-uploader_3.5_create-rpms-fc20-x86_64_merged/11/ # CLI http://jenkins.ovirt.org/job/ovirt-engine-cli_3.5_create-rpms_merged/label=el6/20/ http://jenkins.ovirt.org/job/ovirt-engine-cli_3.5_create-rpms_merged/label=el7/20/ http://jenkins.ovirt.org/job/ovirt-engine-cli_3.5_create-rpms_merged/label=fc20/20/ # Python SDK http://jenkins.ovirt.org/job/ovirt-engine-sdk_3.5_create-rpms_merged/label=el6/33/ http://jenkins.ovirt.org/job/ovirt-engine-sdk_3.5_create-rpms_merged/label=el7/33/ http://jenkins.ovirt.org/job/ovirt-engine-sdk_3.5_create-rpms_merged/label=fc20/33/ # Java SDK
Re: [ovirt-devel] [ovirt-users] [Feature review] Select network to be used for glusterfs
On Thu, Jan 15, 2015 at 12:34:18PM +0530, Sahina Bose wrote: I've updated the feature page with the REST API and other comments. On further thought, there will be no change to Add brick API, as the engine will select the network to be used based on the networks setup for the host. If Storage network role is associated with any of the networks, this will be used. Otherwise, the host's address will be used to add the brick. snip The paragraph above rules out the use case I lay below. Could you relate to it? Isn't it a reasonable use case? If I am not mistaken, it could make sense to have a setup with one brick using network A and another - using network B. Does your design support this? I think that this would be particularly important on upgraded clusters, where the management network is already used, but newly created bricks should start using another network. May I repeat my follow request? It would help me understand the content of the feature. Would you add a feature page section regarding modification to the Vdsm/Engine API? One last comment - may I ask that new APIs accept both ipv4 and ipv6 addresses? There is an ongoing effort to support ipv6 on Vdsm. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Packages for oVirt 3.5.1 RC
- Original Message - From: Sandro Bonazzola sbona...@redhat.com To: devel@ovirt.org, David Caro dcaro...@redhat.com, Juan Hernandez jhern...@redhat.com, Shirly Radco sra...@redhat.com, Alon Bar-Lev alo...@redhat.com, Yaniv Bronheim ybron...@redhat.com, Dan Kenigsberg dan...@redhat.com, Piotr Kliczewski pklic...@redhat.com, Saggi Mizrahi smizr...@redhat.com, Lev Veyde lve...@redhat.com, Martin Sivak msi...@redhat.com, Yaniv Dary yd...@redhat.com, Federico Simoncelli fsimo...@redhat.com, Michal Skrivanek mskri...@redhat.com, Allon Mureinik amure...@redhat.com, Alexander Wels aw...@redhat.com, Einav Cohen eco...@redhat.com, Lior Vernia lver...@redhat.com, Barak Korren bkor...@redhat.com, Eyal Edri ee...@redhat.com Sent: Thursday, January 15, 2015 11:14:39 AM Subject: Packages for oVirt 3.5.1 RC Hi, We're going to compose 3.5.1 RC with the following packages. ACTION: please review the list and raise any change you need ASAP. how much time from rc to release? #ovirt-engine-extension-aaa-ldap http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=epel-7/ we need fc21, no? we should keep the 1.0.1 release we already have, I cannot find artifacts in any of the past job. maybe I will release 1.0.2 for that release. but please do not distribute snapshots for this package. # ovirt-engine-extension-aaa-misc http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-7/ we need fc21, no? if not, just leave what we have in 3.5. # ovirt-engine-extension-logger-log4j http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-7/ same. # otopi I will release today 1.3.1. # oVirt Host Deploy http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=epel-7/ leave what we have in repo, maybe I will release today 1.3.1. #unboundid-ldapsdk http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-el6-x86_64_merged/1/ http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-el7-x86_64_merged/1/ http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-fc20-x86_64_merged/1/ leave what we have in repo. thanks! ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [ovirt-users] [RFC] oVirt mobile client
On Mon, Jan 05, 2015 at 04:17:58PM +0100, Michal Skrivanek wrote: Thank you, Tomas - Original Message - From: i iordanov iiorda...@gmail.com To: users us...@ovirt.org, devel@ovirt.org Cc: Sphoorti Joglekar sphoorti.jogle...@gmail.com Sent: Thursday, December 25, 2014 11:19:58 PM Subject: Re: [ovirt-users] [ovirt-devel] [RFC] oVirt mobile client Hey guys, Thanks for remembering about Opaque. For those who are not familiar with the project, it is an oVirt/RHEV graphics console client which supports the SPICE protocol so far. It uses libgovirt to connect to the oVirt/RHEV API. I also created a separate pure SPICE client (called aSPICE) for Android based on libspice. It would be nice if I got more feedback from Red Hat developers, but you guys are probably as busy as I am :). The app is getting attention on Google Play and people are using it successfully for their installations, it seems. I have plans to add the following features to Opaque, time permitting: - Ability to edit default settings, so that people who connect with console.vv file will be able to configure Audio, keyboard layout, etc. - The ability to allocate VMs from a pool. - The ability to control Audio Playback and Recording separately. I don't think Opaque needs to get portal-management functionality. I was contacted by an intern working on movirt (Sphoorti Joglekar, cc-ed), asking whether I would be willing to support a URI Intent scheme that movirt can use to launch aSPICE. I think I already have a pretty well specified URI scheme that may work for the purpose, so we'll see how that goes. I am wondering whether it wouldn't be better to launch aSPICE or Opaque with a console.vv file instead, though. I guess the developers of movirt will have to consider both options. At any rate, Opaque is far from dead. I'm security supporting it, I just don't find a lot of time to work on additional features. I am cc-ing Brian Proffitt, because at one point we discussed setting up Opaque as a sub-project of oVirt. I don't know whether there is any interest for that in Red Hat, or any interest at all in supporting mobile clients for oVirt/RHEV, etc. It would be nice to hear an official stance on the topic. (adding Brian properly this time) I think it makes sense to add it together with something…though maybe more related to SPICE clients. So adding Christophe for his thoughts… Opaque seems to be more an oVirt client than a SPICE client, so I'd tend to think it would be a better fit as an oVirt project. aSPICE would fit well together with other SPICE repositories, dunno if these are the same code base or not (?). On Jan 5, 2015, at 13:38 , Tomas Jelinek tjeli...@redhat.com wrote: One more question - does aSPICE support spice proxy? libgovirt is not parsing the proxy information at this point, so answer would be no. See http://lists.freedesktop.org/archives/spice-devel/2014-December/018475.html and its followup http://lists.freedesktop.org/archives/spice-devel/2015-January/018609.html Christophe pgpia9eQyGMuo.pgp Description: PGP signature ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] Packages for oVirt 3.5.1 RC
On 01/15, Sandro Bonazzola wrote: Il 15/01/2015 10:29, Alon Bar-Lev ha scritto: - Original Message - From: Sandro Bonazzola sbona...@redhat.com To: devel@ovirt.org, David Caro dcaro...@redhat.com, Juan Hernandez jhern...@redhat.com, Shirly Radco sra...@redhat.com, Alon Bar-Lev alo...@redhat.com, Yaniv Bronheim ybron...@redhat.com, Dan Kenigsberg dan...@redhat.com, Piotr Kliczewski pklic...@redhat.com, Saggi Mizrahi smizr...@redhat.com, Lev Veyde lve...@redhat.com, Martin Sivak msi...@redhat.com, Yaniv Dary yd...@redhat.com, Federico Simoncelli fsimo...@redhat.com, Michal Skrivanek mskri...@redhat.com, Allon Mureinik amure...@redhat.com, Alexander Wels aw...@redhat.com, Einav Cohen eco...@redhat.com, Lior Vernia lver...@redhat.com, Barak Korren bkor...@redhat.com, Eyal Edri ee...@redhat.com Sent: Thursday, January 15, 2015 11:14:39 AM Subject: Packages for oVirt 3.5.1 RC Hi, We're going to compose 3.5.1 RC with the following packages. ACTION: please review the list and raise any change you need ASAP. how much time from rc to release? RC should go out today, GA is scheduled for next week, 2015-01-21 see http://www.ovirt.org/OVirt_3.5.z_Release_Management #ovirt-engine-extension-aaa-ldap http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/9/ARCH=x86_64,DISTRIBUTION=epel-7/ Those are not available anymore, a new version is: http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/10/ we need fc21, no? we should keep the 1.0.1 release we already have, I cannot find artifacts in any of the past job. maybe I will release 1.0.2 for that release. but please do not distribute snapshots for this package. Above are not snapshot, are the last release build. fc21 is not targeted to 3.5.1. We don't have it working on master yet. VDSM team is releasing vdsm packages for F21 since the host side should be fine. In 3.5.0 we didn't have el7. In 3.5.1 we have it. I can discard the other builds and just add the el7 one then. # ovirt-engine-extension-aaa-misc http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-7/ we need fc21, no? if not, just leave what we have in 3.5. I can discard the other builds and just add the el7 one then. # ovirt-engine-extension-logger-log4j http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-7/ same. Those I suppose should be build number 6? (the above url just get latest, and that changes with time) http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/6/ # otopi I will release today 1.3.1. Ok, ping me when ready # oVirt Host Deploy http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/20/ARCH=x86_64,DISTRIBUTION=epel-7/ leave what we have in repo, maybe I will release today 1.3.1. I can discard the other builds and just add the el7 one then. is this required to be built for f21 in order to support vdsm running on f21? #unboundid-ldapsdk http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-el6-x86_64_merged/1/ http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-el7-x86_64_merged/1/ http://jenkins.ovirt.org/job/unboundid-ldapsdk_master_create-rpms-fc20-x86_64_merged/1/ leave what we have in repo. I can discard the other builds and just add the el7 one then. thanks! -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com -- David Caro Red Hat S.L. Continuous Integration Engineer - EMEA ENG Virtualization RD Tel.: +420 532 294 605 Email: dc...@redhat.com Web: www.redhat.com RHT Global #: 82-62605 pgpedvnYhg8BE.pgp Description: PGP signature ___ Devel mailing
Re: [ovirt-devel] Packages for oVirt 3.5.1 RC
Thanks Alon for your input, here's the updated list: # oVirt Engine: # Hash: # * 4f0c48e - restapi: Option to override firewall during install # waiting on (fc20 done, el6 and el7 still building) http://jenkins.ovirt.org/job/manual-build-tarball/458/ # vdsm-jsonrpc-java http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-el6-x86_64_merged/18/ http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-el7-x86_64_merged/15/ http://jenkins.ovirt.org/job/vdsm-jsonrpc-java_3.5_create-rpms-fc20-x86_64_merged/22/ # ovirt-engine-extension-aaa-ldap http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/11/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/11/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-ldap_any_create-rpms_manual/11/ARCH=x86_64,DISTRIBUTION=epel-7/ # ovirt-engine-extension-aaa-misc # Unchanged: # http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=fedora-20/ # http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-aaa-misc_any_create-rpms_manual/2/ARCH=x86_64,DISTRIBUTION=epel-7/ # ovirt-engine-extension-logger-log4j # Unchanged: # http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=fedora-20/ # http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-engine-extension-logger-log4j_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-7/ # DWH http://jenkins.ovirt.org/job/manual-build-tarball/452/label=el6/ http://jenkins.ovirt.org/job/manual-build-tarball/452/label=el7/ http://jenkins.ovirt.org/job/manual-build-tarball/452/label=fc20/ # Reports http://jenkins.ovirt.org/job/manual-build-tarball/453/label=el6/ http://jenkins.ovirt.org/job/manual-build-tarball/453/label=el7/ http://jenkins.ovirt.org/job/manual-build-tarball/453/label=fc20/ # Unchanged since 3.5 #ovirt-guest-tools # VDSM (from jenkins): http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-el6-x86_64_merged/154/ http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-el7-x86_64_merged/151/ http://jenkins.ovirt.org/job/vdsm_3.5_create-rpms-fc20-x86_64_merged/151/ # OTOPI http://jenkins.ovirt.org/job/otopi_any_create-rpms_manual/15/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/otopi_any_create-rpms_manual/15/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/otopi_any_create-rpms_manual/15/ARCH=x86_64,DISTRIBUTION=epel-7/ # oVirt Host Deploy http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=fedora-20/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-6/ http://jenkins.ovirt.org/job/ovirt-host-deploy_any_create-rpms_manual/ARCH=x86_64,DISTRIBUTION=epel-7/ # Hosted Engine Setup http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-el6-x86_64_merged/44/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-el7-x86_64_merged/38/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-setup_3.5_create-rpms-fc20-x86_64_merged/43/ # Hosted Engine HA http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-el6-x86_64_merged/35/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-el7-x86_64_merged/26/ http://jenkins.ovirt.org/job/ovirt-hosted-engine-ha_3.5_create-rpms-fc20-x86_64_merged/34/ # Log Collector http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-el6-x86_64_merged/19/ http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-el7-x86_64_merged/8/ http://jenkins.ovirt.org/job/ovirt-log-collector_3.5_create-rpms-fc20-x86_64_merged/18/ # ISO Uploader http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-el6-x86_64_merged/11/ http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-el7-x86_64_merged/1/ http://jenkins.ovirt.org/job/ovirt-iso-uploader_3.5_create-rpms-fc20-x86_64_merged/11/ # Image Uploader http://jenkins.ovirt.org/job/ovirt-image-uploader_3.5_create-rpms-el6-x86_64_merged/11/ http://jenkins.ovirt.org/job/ovirt-image-uploader_3.5_create-rpms-el7-x86_64_merged/1/ http://jenkins.ovirt.org/job/ovirt-image-uploader_3.5_create-rpms-fc20-x86_64_merged/11/ # CLI http://jenkins.ovirt.org/job/ovirt-engine-cli_3.5_create-rpms_merged/label=el6/20/ http://jenkins.ovirt.org/job/ovirt-engine-cli_3.5_create-rpms_merged/label=el7/20/ http://jenkins.ovirt.org/job/ovirt-engine-cli_3.5_create-rpms_merged/label=fc20/20/ # Python SDK http://jenkins.ovirt.org/job/ovirt-engine-sdk_3.5_create-rpms_merged/label=el6/33/ http://jenkins.ovirt.org/job/ovirt-engine-sdk_3.5_create-rpms_merged/label=el7/33/
Re: [ovirt-devel] spice proxy support in govirt
Hey,
On Sun, Dec 28, 2014 at 02:34:10AM -0600, i iordanov wrote:
Hello,
My apologies for the partial mail sent out, I hit a strange key
combination by mistake :). As I was saying, this bug got closed not
long ago:
Sorry for the late reply, was on holidays for a while, came back just now :)
I looked into the latest code of govirt, and I don't see support for
SpiceProxy in there. Would you be so kind as to add this feature?
I quickly cooked/compile-tested the attached patch, if you have time to
test it, let me know how it works, otherwise I'll get back to that later
(need to get lot of email under control first ;)
Christophe
diff --git a/govirt/ovirt-vm-display.c b/govirt/ovirt-vm-display.c
index a8a0942..0a8adc6 100644
--- a/govirt/ovirt-vm-display.c
+++ b/govirt/ovirt-vm-display.c
@@ -39,6 +39,7 @@ struct _OvirtVmDisplayPrivate {
char *host_subject;
gboolean smartcard;
gboolean allow_override;
+char *proxy_url;
};
G_DEFINE_TYPE(OvirtVmDisplay, ovirt_vm_display, G_TYPE_OBJECT);
@@ -55,6 +56,7 @@ enum {
PROP_HOST_SUBJECT,
PROP_SMARTCARD,
PROP_ALLOW_OVERRIDE,
+PROP_PROXY_URL,
};
static void ovirt_vm_display_get_property(GObject *object,
@@ -95,6 +97,9 @@ static void ovirt_vm_display_get_property(GObject *object,
case PROP_ALLOW_OVERRIDE:
g_value_set_boolean(value, display-priv-allow_override);
break;
+case PROP_PROXY_URL:
+g_value_set_string(value, display-priv-proxy_url);
+break;
default:
G_OBJECT_WARN_INVALID_PROPERTY_ID(object, prop_id, pspec);
}
@@ -141,6 +146,9 @@ static void ovirt_vm_display_set_property(GObject *object,
case PROP_ALLOW_OVERRIDE:
display-priv-allow_override = g_value_get_boolean(value);
break;
+case PROP_PROXY_URL:
+g_free(display-priv-proxy_url);
+display-priv-proxy_url = g_value_dup_string(value);
default:
G_OBJECT_WARN_INVALID_PROPERTY_ID(object, prop_id, pspec);
}
@@ -153,6 +161,7 @@ static void ovirt_vm_display_finalize(GObject *object)
g_free(display-priv-address);
g_free(display-priv-ticket);
g_free(display-priv-host_subject);
+g_free(display-priv-proxy_url);
G_OBJECT_CLASS(ovirt_vm_display_parent_class)-finalize(object);
}
@@ -252,6 +261,14 @@ static void
ovirt_vm_display_class_init(OvirtVmDisplayClass *klass)
FALSE,
G_PARAM_READWRITE |
G_PARAM_STATIC_STRINGS));
+g_object_class_install_property(object_class,
+PROP_PROXY_URL,
+g_param_spec_string(proxy-url,
+Proxy URL,
+URL of the proxy to
use to access the VM,
+NULL,
+G_PARAM_READWRITE |
+
G_PARAM_STATIC_STRINGS));
}
static void ovirt_vm_display_init(G_GNUC_UNUSED OvirtVmDisplay *display)
diff --git a/govirt/ovirt-vm-xml.c b/govirt/ovirt-vm-xml.c
index 7790887..22d50af 100644
--- a/govirt/ovirt-vm-xml.c
+++ b/govirt/ovirt-vm-xml.c
@@ -44,6 +44,7 @@ static gboolean vm_set_display_from_xml(OvirtVm *vm,
const char *certificate_key = g_intern_string(certificate);
const char *smartcard_key = g_intern_string(smartcard_enabled);
const char *allow_override_key = g_intern_string(allow_override);
+const char *proxy_key = g_intern_string(proxy);
if (root == NULL) {
return FALSE;
@@ -120,6 +121,11 @@ static gboolean vm_set_display_from_xml(OvirtVm *vm,
}
}
+node = g_hash_table_lookup(root-children, proxy_key);
+if (node != NULL) {
+g_object_set(G_OBJECT(display), proxy-url, node-content, NULL);
+}
+
/* FIXME: this overrides the ticket/expiry which may
* already be set
*/
pgpCYXDH7pkzc.pgp
Description: PGP signature
___
Devel mailing list
Devel@ovirt.org
http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] spice proxy support in govirt
Hi Christophe, I am quite busy during the week, but I'll try to find time during the weekend. Thanks! iordan On Thu, Jan 15, 2015 at 8:04 AM, Christophe Fergeau cferg...@redhat.com wrote: Hey, On Sun, Dec 28, 2014 at 02:34:10AM -0600, i iordanov wrote: Hello, My apologies for the partial mail sent out, I hit a strange key combination by mistake :). As I was saying, this bug got closed not long ago: Sorry for the late reply, was on holidays for a while, came back just now :) I looked into the latest code of govirt, and I don't see support for SpiceProxy in there. Would you be so kind as to add this feature? I quickly cooked/compile-tested the attached patch, if you have time to test it, let me know how it works, otherwise I'll get back to that later (need to get lot of email under control first ;) Christophe -- The conscious mind has only one thread of execution. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [ovirt-users] [RFC] oVirt mobile client
Hi Christophe, They share a part of their code-base, primarily in the native implementation. However, Opaque has a substantially reimplemented UI. They both live in the same repository, though, and the plan was to bring them closer together over time. I see aSPICE as analogous to spicy and Opaque as analogous to virt-viewer. Cheers, iordan On Thu, Jan 15, 2015 at 8:22 AM, Christophe Fergeau cferg...@redhat.com wrote: On Mon, Jan 05, 2015 at 04:17:58PM +0100, Michal Skrivanek wrote: Thank you, Tomas - Original Message - From: i iordanov iiorda...@gmail.com To: users us...@ovirt.org, devel@ovirt.org Cc: Sphoorti Joglekar sphoorti.jogle...@gmail.com Sent: Thursday, December 25, 2014 11:19:58 PM Subject: Re: [ovirt-users] [ovirt-devel] [RFC] oVirt mobile client Hey guys, Thanks for remembering about Opaque. For those who are not familiar with the project, it is an oVirt/RHEV graphics console client which supports the SPICE protocol so far. It uses libgovirt to connect to the oVirt/RHEV API. I also created a separate pure SPICE client (called aSPICE) for Android based on libspice. It would be nice if I got more feedback from Red Hat developers, but you guys are probably as busy as I am :). The app is getting attention on Google Play and people are using it successfully for their installations, it seems. I have plans to add the following features to Opaque, time permitting: - Ability to edit default settings, so that people who connect with console.vv file will be able to configure Audio, keyboard layout, etc. - The ability to allocate VMs from a pool. - The ability to control Audio Playback and Recording separately. I don't think Opaque needs to get portal-management functionality. I was contacted by an intern working on movirt (Sphoorti Joglekar, cc-ed), asking whether I would be willing to support a URI Intent scheme that movirt can use to launch aSPICE. I think I already have a pretty well specified URI scheme that may work for the purpose, so we'll see how that goes. I am wondering whether it wouldn't be better to launch aSPICE or Opaque with a console.vv file instead, though. I guess the developers of movirt will have to consider both options. At any rate, Opaque is far from dead. I'm security supporting it, I just don't find a lot of time to work on additional features. I am cc-ing Brian Proffitt, because at one point we discussed setting up Opaque as a sub-project of oVirt. I don't know whether there is any interest for that in Red Hat, or any interest at all in supporting mobile clients for oVirt/RHEV, etc. It would be nice to hear an official stance on the topic. (adding Brian properly this time) I think it makes sense to add it together with something…though maybe more related to SPICE clients. So adding Christophe for his thoughts… Opaque seems to be more an oVirt client than a SPICE client, so I'd tend to think it would be a better fit as an oVirt project. aSPICE would fit well together with other SPICE repositories, dunno if these are the same code base or not (?). On Jan 5, 2015, at 13:38 , Tomas Jelinek tjeli...@redhat.com wrote: One more question - does aSPICE support spice proxy? libgovirt is not parsing the proxy information at this point, so answer would be no. See http://lists.freedesktop.org/archives/spice-devel/2014-December/018475.html and its followup http://lists.freedesktop.org/archives/spice-devel/2015-January/018609.html Christophe -- The conscious mind has only one thread of execution. ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
Re: [ovirt-devel] [ovirt-users] [Feature review] Select network to be used for glusterfs
On 01/15/2015 02:27 PM, Dan Kenigsberg wrote: On Thu, Jan 15, 2015 at 12:34:18PM +0530, Sahina Bose wrote: I've updated the feature page with the REST API and other comments. On further thought, there will be no change to Add brick API, as the engine will select the network to be used based on the networks setup for the host. If Storage network role is associated with any of the networks, this will be used. Otherwise, the host's address will be used to add the brick. snip The paragraph above rules out the use case I lay below. Could you relate to it? Isn't it a reasonable use case? If I am not mistaken, it could make sense to have a setup with one brick using network A and another - using network B. Does your design support this? I think that this would be particularly important on upgraded clusters, where the management network is already used, but newly created bricks should start using another network. On upgraded clusters, the user would have to assign a network with the role Storage network. Any newly created brick would then start using this, rather than the management network. I'm not sure if the use case where each brick on a host is added using different networks is a common one (apart from the upgrade scenario, that is). If it is, we could provide an Advanced edit option in the UI to select network in Add Bricks dialog. The entity design supports setting different network per brick and the REST API already provides a way to set this as an optional parameter. May I repeat my follow request? It would help me understand the content of the feature. Sorry, I missed these before! Would you add a feature page section regarding modification to the Vdsm/Engine API? http://www.ovirt.org/Features/Select_Network_For_Gluster#Change_to_VDSM_API http://www.ovirt.org/Features/Select_Network_For_Gluster#Change_to_REST_API One last comment - may I ask that new APIs accept both ipv4 and ipv6 addresses? There is an ongoing effort to support ipv6 on Vdsm. Glusterfs does not support ipv6 yet, so addition of bricks using ipv6 addresses would not work. thanks, sahina ___ Devel mailing list Devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/devel
