November 2013 - vdsm-devel - Fedora Mailing-Lists

by asegurap＠redhat.com

Hi List, I just built master with some gerrit patch and when installing in Fedora20 I get the following: Installing : vdsm-python-4.13.0-179.gite51bbc3.fc20.x86_64 1/7 Installing : vdsm-xmlrpc-4.13.0-179.gite51bbc3.fc20.noarch 2/7 Installing : vdsm-python-zombiereaper-4.13.0-179.gite51bbc3.fc20.noarch 3/7 Installing : vdsm-4.13.0-179.gite51bbc3.fc20.x86_64 4/7 Traceback (most recent call last): File "/usr/bin/vdsm-tool", line 145, in <module> sys.exit(main()) File "/usr/bin/vdsm-tool", line 142, in main return tool_command[cmd]["command"](*args[1:]) File "/usr/lib64/python2.7/site-packages/vdsm/tool/seboolsetup.py", line 59, in sebool_config setup_booleans(True) File "/usr/lib64/python2.7/site-packages/vdsm/tool/seboolsetup.py", line 41, in setup_booleans sebool_obj = seobject.booleanRecords() File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 2070, in __init__ semanageRecords.__init__(self, store) File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 205, in __init__ self.mylog = logger() File "/usr/lib/python2.7/site-packages/seobject/__init__.py", line 90, in __init__ self.audit_fd = audit.audit_open() OSError: [Errno 93] Protocol not supported OSError: Protocol not supported Installing : vdsm-debug-plugin-4.13.0-179.gite51bbc3.fc20.noarch 5/7 Installing : vdsm-reg-4.13.0-179.gite51bbc3.fc20.noarch 6/7 Installing : vdsm-cli-4.13.0-179.gite51bbc3.fc20.noarch 7/7 Verifying : vdsm-debug-plugin-4.13.0-179.gite51bbc3.fc20.noarch 1/7 Verifying : vdsm-reg-4.13.0-179.gite51bbc3.fc20.noarch 2/7 Verifying : vdsm-python-zombiereaper-4.13.0-179.gite51bbc3.fc20.noarch 3/7 Verifying : vdsm-cli-4.13.0-179.gite51bbc3.fc20.noarch 4/7 Verifying : vdsm-4.13.0-179.gite51bbc3.fc20.x86_64 5/7 Verifying : vdsm-xmlrpc-4.13.0-179.gite51bbc3.fc20.noarch 6/7 Verifying : vdsm-python-4.13.0-179.gite51bbc3.fc20.x86_64 Shouldn't the auditing be optional (I have audit=0 in the kernel cmdline). Best, Toni

10 years, 5 months

2
1
0 / 0

Pending Self-Hosted-Engine Patches in ovirt-3.3.2

by Dan Kenigsberg

An important feature of ovirt-3.3 has not made it to the ovirt-3.3.0 deadline: http://www.ovirt.org/Features/Self_Hosted_Engine. It would allow to run Engine as a VM on top one of the hosts controlled by itself, saving resources and allowing high availablity out-of-the-box. The feature was not ready on time for the ovirt-3.3.0 release but now its Engine-side patches are merged, and its Vdsm-side patches are pending aproval for entry into Vdsm's stable branch. http://gerrit.ovirt.org/20189 http://gerrit.ovirt.org/20190 http://gerrit.ovirt.org/20191 http://gerrit.ovirt.org/20192 http://gerrit.ovirt.org/20193 http://gerrit.ovirt.org/20194 http://gerrit.ovirt.org/20209 http://gerrit.ovirt.org/20300 http://gerrit.ovirt.org/21357 I suggest to take the pending patches into the ovirt-3.3 branch, and ship ovirt-3.3.2 with this feature enabled. We shall not release ovirt-3.3.2 before we are assured by quality engineering that we have no regression to main Vdsm code. If we do not receive this green light, and there's urgency to release ovirt-3.3.2, we'd fork and ship 3.3.2 only with the urgent fixes. Any objections? Dan.

10 years, 5 months

6
8
0 / 0

[QE] oVirt 3.3.2 beta status

by Sandro Bonazzola

Hi, we're going to branch and build oVirt 3.3.2 beta TODAY. A bug tracker is available at [1] and it shows only 3 bugs still blocking the release: Whiteboard Bug ID Summary storage 1022961 Running a VM from a gluster domain uses mount instead of gluster URI virt 1025829 sysprep floppy is not attached to Windows 2008 R2 machine - even when specifically checked in Run Once virt 1029885 cloud-init testcase does not work in engine 3.3.1 Please provide an ETA for the above bugs. The following is a list of the non-blocking bugs still open with target 3.3.2: Whiteboard Bug ID Summary infra 1017267 Plaintext user passwords in async_tasks database infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required,... infra 1020344 Power Managent with cisco_ucs problem integration 1022440 AIO - configure the AIO host to be a gluster cluster/host integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 oVirt Live - use motd to show the admin password integration 1026930 Package virtio-win and put it in ovirt repositories integration 1026933 pre-populate ISO domain with virtio-win ISO network 1019818 Support OpenStack Havana layer 2 agent integration network 987999 [oVirt] [provider] Add button shouldn't appear on specific provider network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost network 906313 [oVirt-webadmin] [setupNetworks] "No valid Operation for <network_name> and Unassigned Logical Networks panel" network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) storage 1029069 Live storage migration snapshot removal fails, probably due to unexpected qemu-img output storage 987917 [oVirt] [glance] API version not specified in provider dialog storage 1016118 async between masterVersion : can't connect to StoragePool ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck on first view... virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Please add the bugs to the tracker if you think that 3.3.2 should not be released without them fixed. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. Maintainers are welcomed to start filling release notes, the page has been created here [3] [1] https://bugzilla.redhat.com/1027349 [2] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing [3] http://www.ovirt.org/OVirt_3.3.2_release_notes Thanks, -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

10 years, 5 months

3
2
0 / 0

Multiple graphics framebuffers - VDSM support

by fkobzik＠redhat.com

Dear VDSM developers, I'm working on a patch that allows running a VM with multiple graphics framebuffers. This is handy when you want to run a VM with both SPICE and VNC. It's a 3.4 feature and it will certainly need a change in vdsm. Here is a list of changes in VDSM that are needed for this funcionality: a, Sending graphics/video (engine->vdsm) - currently we send two things: 1, "display" value (qxl/vnc [wat]) - vdsm uses this for determining if the graphics server is SPICE or VNC - this attribute is not really correct - it mixes up semantics of graphic framebuffer and videocard together. I believe this attribute should only contain information about the graphics ('spice', 'vnc' or 'spice,vnc' if you want both). if this the case, do you think we should rename the attribute to, let's say, 'graphics'? Is it even possible with regard to backward compatibility? or should I reuse 'display' attribute? 2, video device (json representation of the video card) - this is correct b, Reporting graphics ports (vdsm->engine) - currently we report 2 graphic ports ('displayPort' and 'secureDisplayPort') - if we want multiple framebuffers, we must report more ports (for VNC and SPICE together that would mean 3 ports (2 for spice, one for vnc). - there are two possible solutions for this: 1, ditch 'displayPort' and 'secureDisplayPort' and add new 'spicePort', 'spiceSecurePort', 'vncPort' fields or some kind of two level dict: { protocol -> secured/unsecured -> portNumber } 2, keep 'displayPort' and 'secureDisplayPort' and introduce new 'additionalDisplayPort' This would be friendlier to backward compatibility, but it's extremely ugly because of unclear semantics of the fields (in case of SPICE+VNC 'displayPort' and 'secureDisplayPort' would be related to SPICE, 'additionalDisplayPort' would be the VNC port. In case of VNC only, the 'displayPort' would be suddendly VNC port... ewww). I'd be very happy if you share your opinion about these changes. Cheers, Franta.

10 years, 5 months

3
4
0 / 0

addNetwork to use existing nic conf

by didi＠redhat.com

Hi all, While looking at [1], and reading the source of bridge.py of ovirt-hosted-engine-setup and of ovirt-host-deploy, I think the correct thing will be for addNetwork to not require either bootproto=dhcp or ipaddr/netmask/etc., but to take this from the existing conf of the nics to be put inside the bridge. Does this make sense? [1] https://bugzilla.redhat.com/show_bug.cgi?id=1013666 Thanks! -- Didi

10 years, 5 months

3
11
0 / 0

oVirt Updates - November 2013

by iheim＠redhat.com

Case Studies - Dave Neary just published his interview with Martin Goldstone and Gary Lloyd, system administrators at the Keele university http://www.ovirt.org/Keele_University_case_study (we'd be happy to have more case studies, please contact Dave if you are willing to do one - its mostly just an interview with him) oVirt 3.3 - 3.3.1 with a slew of updates is finally out. http://www.ovirt.org/OVirt_3.3.1_release_notes - 3.3.2 beta planned once we GA 3.3.1. - sample scheduler plugins available here http://www.ovirt.org/External_Scheduler_Samples oVirt 3.4 - planning is on going, please join and help make oVirt better http://lists.ovirt.org/pipermail/users/2013-October/017451.html (clearly, only items with devel owners will make it) Conferences - Einav presented at an oVirt booth in LISA 2013 (Washington, DC) - Fosdem virt & IaaS devroom CFP[1] is open till December 1st http://bit.ly/1gMXdUH We also requested a stand/table/booth to demo oVirt (we'd love if oVirt users visiting Fosdem would volunteer to help man the stand/demo) - KVM Forum/CloudOpen sessions available http://www.ovirt.org/KVM_Forum_2013 Cross Distro - guest agent packages are now available for OpenSUSE 12.3, 13.1 and Factory, and SLES 11 SP3. (thanks Vinzenz for pushing and René for testing) - Ubuntu packages pushed by Zhou Zheng Sheng. - How To: Get oVirt 3.2 All-In-One working on Scientific Linux 6.4 (With fixes!) http://bit.ly/17BstPj Related - How to manage multiple nodes with oVirt (Japanese) http://lab.space-i.com/?p=1252 - oVirt node has a new plugin, allowing it to be used for The Foreman host discovery http://www.youtube.com/watch?v=V8TugleqF64 - how to use virt-sysprep with oVirt/RHEV http://bit.ly/1hy54Xx - script to easily move VMs by name from export domain https://github.com/ppiersonbt/ovfmaker - some oVirt and Dell Equalogic issues discussions http://dell.to/1gN3TlX http://bit.ly/1cXrIH2 - Intro to oVirt on Fedora (Spanish) http://www.itrestauracion.com.ar/?p=1505 - Christophe Fergeau published libgovirt 0.3.0 (storage domains, cd-rom and certificate handling improvements) http://red.ht/HVl4U2 - helper script by Humble to print list of VMs and their nic/mac/ip http://bit.ly/1ePpMjF - Want to play with oVirt Neutron and GRE Tunneling? http://www.ovirt.org/OVirt_Neutron_GRE_Integration_-_How_To - How To: Install rhev-agents on Scientific Linux 6x http://bit.ly/1cZRydo - How To: Convert a server running on VMware ESXi 5x to oVirt 3.2 http://bit.ly/17x2X1O

10 years, 5 months

1
0
0 / 0

Re: [vdsm] Failing puppet runs due to python-cpopen

by ewoud＠kohlvanwijngaarden.nl

On Wed, Nov 20, 2013 at 01:04:26PM -0500, Nir Soffer wrote: > ----- Original Message ----- > > From: "Ewoud Kohl van Wijngaarden" <ewoud(a)kohlvanwijngaarden.nl> > > To: "Nir Soffer" <nsoffer(a)redhat.com> > > Sent: Wednesday, November 20, 2013 7:55:30 PM > > Subject: Re: Failing puppet runs due to python-cpopen > > > > On Wed, Nov 20, 2013 at 12:52:48PM -0500, Nir Soffer wrote: > > > ----- Original Message ----- > > > > From: "Ewoud Kohl van Wijngaarden" <ewoud+ovirt(a)kohlvanwijngaarden.nl> > > > > To: infra(a)ovirt.org, vdsm-devel(a)lists.fedorahosted.org > > > > Sent: Wednesday, November 20, 2013 7:45:39 PM > > > > Subject: Failing puppet runs due to python-cpopen > > > > > > > > Hello all, > > > > > > > > Currently we attempt to install python-cpopen, but puppet fails to do > > > > this. When I manually run it: > > > > > > > > [root@jenkins-slave-vm01 ~]# yum install python-cpopen > > > > Loaded plugins: versionlock > > > > Resolving Dependencies > > > > --> Running transaction check > > > > ---> Package python-cpopen.x86_64 0:1.2.3-2.fc19 will be installed > > > > Removing python-cpopen.x86_64 0:1.2.3-2.fc19 - u due to obsoletes from > > > > installed vdsm-python-cpopen-4.13.0-9.fc19.x86_64 > > > > --> Restarting Dependency Resolution with new changes. > > > > --> Running transaction check > > > > ---> Package python-cpopen.x86_64 0:1.2.3-2.fc19 will be installed > > > > --> Finished Dependency Resolution > > > > [root@jenkins-slave-vm01 ~]# > > > > > > > > Any advice here? > > > > > > On RHEL you have to remove vdsm-python-cpopen before it would install > > > python-cpopen. > > > > > > Maybe the automated job should check if vdsm-python-cpopen is installed and > > > remove it? > > > > But this is fc19. Should I still manually fix it? > > If you want to install vdsm, you probably should :-) > Personally I don't need to install vdsm, but jenkins insists :-). Should we no longer ensure python-cpopen is installed and just rely on vdsm to do the right thing? Also, I accidentally replied just to you instead of the list, so adding again.

10 years, 5 months

2
1
0 / 0

Failing puppet runs due to python-cpopen

by Ewoud Kohl van Wijngaarden

Hello all, Currently we attempt to install python-cpopen, but puppet fails to do this. When I manually run it: [root@jenkins-slave-vm01 ~]# yum install python-cpopen Loaded plugins: versionlock Resolving Dependencies --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-2.fc19 will be installed Removing python-cpopen.x86_64 0:1.2.3-2.fc19 - u due to obsoletes from installed vdsm-python-cpopen-4.13.0-9.fc19.x86_64 --> Restarting Dependency Resolution with new changes. --> Running transaction check ---> Package python-cpopen.x86_64 0:1.2.3-2.fc19 will be installed --> Finished Dependency Resolution [root@jenkins-slave-vm01 ~]# Any advice here?

10 years, 5 months

1
0
0 / 0

vdsm sync meeting minutes

by asegurap＠redhat.com

vdsm-sync meeting 2013-11-04 ============================== - #1022969 Gluster bug blocking ovirt-3.3.1 Maybe Eduardo can take a look. - CPOpen has been fixed and it is released properly (even in pypi). - Hosted engine patches exhibit some brittleness that make it advisable to create a separate branch for testing it. Federico proposes to push them to master once 3.3.1 is released. - We are to keep master working on F19 and el6 to ease testers task. We can ship some via oVirt repo on a case per case basis. Ask Mike Burns about the possibility of doing that.

10 years, 5 months

5
5
0 / 0

oVirt 3.3.2 beta status

by Sandro Bonazzola

Hi, we're going to branch and build oVirt 3.3.2 beta on Nov 27th. A bug tracker is available at [1] and it shows only 2 bugs blocking the release: Bug 1029792 - VDSM does not report the qemu version in capabilities, if qemu-kvm-rhev is used Bug 1029885 - cloud-init testcase does not work in engine 3.3.1 The following is a list of the bugs still open with target 3.3.2 or 3.3: Whiteboard Bug ID Summary 991267 [RFE] Add TUI information to log file. infra 987982 When adding a host through the REST API, the error message says that "rootPassword" is required, but ... infra 1017267 Plaintext user passwords in async_tasks database infra 1020344 Power Managent with cisco_ucs problem infra 1009899 exportDbSchema scripts generates output file with wrong name infra 1029792 VDSM does not report the qemu version in capabilities, if qemu-kvm-rhev is used integration 1026933 pre-populate ISO domain with virtio-win ISO integration 1026930 Package virtio-win and put it in ovirt repositories integration 1030437 RFE: Configuration of email notifications integration 1022440 AIO - configure the AIO host to be a gluster cluster/host integration 902979 ovirt-live - firefox doesn't trust the installed engine integration 1021805 oVirt Live - use motd to show the admin password network 988002 [oVirt] [network] Add button shouldn't appear on specific network network 987916 [oVirt] [provider] Dialog doesn't update unless focus lost network 987999 [oVirt] [provider] Add button shouldn't appear on specific provider network 906313 [oVirt-webadmin] [setupNetworks] "No valid Operation for <network_name> and Unassigned Logical Networks panel" network 1023722 [oVirt-webadmin][network] Network roles in cluster management should be radio buttons network 997197 Some AppErrors messages are grammatically incorrect (singular vs plural) storage 1016118 async between masterVersion : can't connect to StoragePool storage 987917 [oVirt] [glance] API version not specified in provider dialog storage 1029069 Live storage migration snapshot removal fails, probably due to unexpected qemu-img output ux 906394 [oVirt-webadmin] [network] Loading animation in network main tab 'hosts' and 'vms' subtab is stuck on first view... virt 1007940 Cannot clone from snapshot while using GlusterFS as POSIX Storage Domain Please set the target to 3.3.2 and add the bug to the tracker if you think that 3.3.2 should not be released without it fixed. Please also update the target to 3.3.3 or any next release for bugs that won't be in 3.3.2: it will ease gathering the blocking bugs for next releases. For those who want to help testing the bugs, I suggest to add yourself as QA contact for the bug and add yourself to the testing page [2]. [1] https://bugzilla.redhat.com/1027349 [2] http://www.ovirt.org/Testing/Ovirt_3.3.2_testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

10 years, 5 months

2
1
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

vdsm-devel November 2013