Re: [Users] otopi needed on oVirt node?

I don't follow. If these are not ovirt-nodes, then no otopi and no ovirt-host-deploy should exist, unless these are all-in-one.

----- Original Message ----- > From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; > To: "Alon Bar-Lev" <alonbl(a)redhat.com&gt; > Cc: "users" <users(a)ovirt.org&gt;, "Mike Burns" <mburns(a)redhat.com&gt; > Sent: Tuesday, March 19, 2013 4:45:57 PM > Subject: Re: [Users] otopi needed on oVirt node? > > On Tue, Mar 19, 2013 at 3:23 PM, Alon Bar-Lev <alonbl(a)redhat.com&gt; > wrote: >> >> >> ----- Original Message ----- >>> From: "Gianluca Cecchi" <gianluca.cecchi(a)gmail.com&gt; >>> To: "users" <users(a)ovirt.org&gt; >>> Sent: Tuesday, March 19, 2013 4:20:58 PM >>> Subject: [Users] otopi needed on oVirt node? >>> >>> Hello, >>> comparing rpm packages installed on two f18 systems that are nodes >>> of >>> a 3.2 cluster, I notice this difference: >>> >>>> otopi-1.0.0-1.fc18.noarch >>>> ovirt-host-deploy-1.0.1-1.fc18.noarch >> >> This is strange! are you sure the host is ovirt-node? >> >>> I think ovirt-host-deploy is not necessary and that I can remove >>> from >>> the only node where it is installed. >>> What about otopi? >> >> You need ovirt-host-deploy-offline, a single package, on >> ovirt-node. >> >> Alon > > > Based on yum.log f18ovn01 was the second node deployed when engine > and > first node were in version 3.2. > Installed and updated fedora18 > enabled ovirt-stable repo > installed node from webadmin gui (3.2 engine). > what I see in yum.log at the date of deploy is only for 4 packages: > Mar 11 14:34:18 Installed: python-ethtool-0.7-4.fc18.x86_64 > Mar 11 14:34:19 Installed: strace-4.7-2.fc18.x86_64 > Mar 11 14:34:19 Installed: atop-1.26-8.fc18.x86_64 > Mar 11 14:34:20 Installed: 2:libcacard-1.2.2-6.fc18.x86_64 > Mar 11 14:34:21 Installed: m2crypto-0.21.1-9.fc18.x86_64 > Mar 11 14:34:21 Installed: 2:qemu-kvm-tools-1.2.2-6.fc18.x86_64 > Mar 11 14:34:21 Installed: > yum-plugin-fastestmirror-1.1.31-10.fc18.noarch > > Mar 11 15:46:22 Installed: vdsm-python-4.10.3-9.fc18.x86_64 > Mar 11 15:46:22 Installed: vdsm-xmlrpc-4.10.3-9.fc18.noarch > Mar 11 15:46:55 Installed: vdsm-4.10.3-9.fc18.x86_64 > Mar 11 15:46:55 Installed: vdsm-cli-4.10.3-9.fc18.noarch > > Mar 11 17:22:13 Erased: kernel-3.8.2-206.fc18.x86_64 > Mar 11 17:22:28 Installed: kernel-3.7.8-202.fc18.x86_64 > Mar 19 14:06:40 Updated: bash-4.2.45-1.fc18.x86_64 > > > > > [g.cecchi@f18ovn01 ~]$ rpm -qa | egrep "ovirt|vdsm|host-|libvirt|kvm" > | sort > libvirt-0.10.2.3-1.fc18.x86_64 > libvirt-client-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-config-network-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-config-nwfilter-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-interface-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-libxl-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-lxc-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-network-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-nodedev-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-nwfilter-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-qemu-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-secret-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-storage-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-uml-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-xen-0.10.2.3-1.fc18.x86_64 > libvirt-lock-sanlock-0.10.2.3-1.fc18.x86_64 > libvirt-python-0.10.2.3-1.fc18.x86_64 > qemu-kvm-1.2.2-6.fc18.x86_64 > qemu-kvm-tools-1.2.2-6.fc18.x86_64 > vdsm-4.10.3-10.fc18.x86_64 > vdsm-cli-4.10.3-10.fc18.noarch > vdsm-python-4.10.3-10.fc18.x86_64 > vdsm-xmlrpc-4.10.3-10.fc18.noarch > > > [g.cecchi@f18ovn03 ~]$ rpm -qa | egrep "ovirt|vdsm|host-|libvirt|kvm" > | sort > libvirt-0.10.2.3-1.fc18.x86_64 > libvirt-client-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-config-network-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-config-nwfilter-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-interface-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-libxl-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-lxc-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-network-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-nodedev-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-nwfilter-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-qemu-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-secret-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-storage-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-uml-0.10.2.3-1.fc18.x86_64 > libvirt-daemon-driver-xen-0.10.2.3-1.fc18.x86_64 > libvirt-lock-sanlock-0.10.2.3-1.fc18.x86_64 > libvirt-python-0.10.2.3-1.fc18.x86_64 > ovirt-host-deploy-1.0.1-1.fc18.noarch > qemu-kvm-1.2.2-6.fc18.x86_64 > qemu-kvm-tools-1.2.2-6.fc18.x86_64 > vdsm-4.10.3-10.fc18.x86_64 > vdsm-cli-4.10.3-10.fc18.noarch > vdsm-python-4.10.3-10.fc18.x86_64 > vdsm-xmlrpc-4.10.3-10.fc18.noarch > > If it could be of any help, for a short time f18ovn03 has been an > all-in-one server. Then I purged all ovirt repo installed packages > and > then I deployed it as a node from another engine.... > Possibly I forgot to remove the ovirt-host-deploy > But f18ovn01 was born from scratch as a fedora 18 server and before > enabling on it the ovirt repo I ran an "rpm -qa" on both and then : > > yum install $(diff /tmp/f18ovn0*|grep -v ovirt |grep -v vdsm| grep > "^>" |cut -d ">" -f2 ) > > to align the packages not relatd to ovirt itself > then I deployed the node from webadmin gui > > BTW: both nodes work ok and both has been SPM during update to 3.2.1 > and both sustained live migration of linux and windows vm in both > directions.... > > Gianluca > _______________________________________________ Users mailing list Users(a)ovirt.org http://lists.ovirt.org/mailman/listinfo/users