- Devel - oVirt List Archives

Re: [ovirt-devel] [vdsm] compile vdsm and attach it to a engine.
by ybronhei 13 Jul '14

13 Jul '14

On 07/03/2014 05:11 AM, aaron Beein wrote: > Hi, > > Thank you for your great job on ovirt and vdsm. Now I devote myself to > compile vdsm on centos 6.3 host and attach it to a ovirt engine. But when I > attach the host which contains a compiled vdsm to a ovirt engine , the > status of the host is always ‘Non Responsive’(step 11 below). I reference > the links below: > > http://www.ovirt.org/Vdsm_Developers > > http://www.ovirt.org/Installing_VDSM_from_rpm > > > > The steps( 1-9 ) are executed on centos6.3 host, and the steps(10--11) are > executed on ovirt engine. So I would be very grateful if you can give me > some clues that if I've missed anything or I done something wrong. > > The attachment is the same as the bellow which makes it easier for you to > read. > 1 Deployment platform > > Centos6.3 > > Linux bogon 2.6.32-431.20.3.el6.x86_64 #1 SMP Thu Jun 19 21:14:45 UTC 2014 > x86_64 x86_64 x86_64 GNU/Linux > > Ip ： 10.1.8.252 > > CPU supports hardware virtualization extensions: > > # cat /proc/cpuinfo | egrep 'svm|vmx'| grep nx > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc > aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr > pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb > xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid > > flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca > cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx > rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc > aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr > pdcm pcid sse4_1 sse4_2 popcnt tsc_deadline_timer xsave lahf_lm arat epb > xsaveopt pln pts dts tpr_shadow vnmi flexpriority ept vpid > 2 Apply all updates # yum -y update 3 Installing required packages > > RHEL 6 users must add EPEL yum repository for installing python-ordereddict > and pyton-pthreading. The rpm bellow will install the epel yum repo and > required gpg keys. > > # yum install http://download.fedoraproject.org/pub/epel/6/i386/epel-release-6-8.noarch.r… > > RHEL 6 users must install a newer pep8 version than the one shipped in > EPEL6. Older pep8 versions have a bug that's tickled by vdsm. You can use > `pip`, or > > yum install http://danken.fedorapeople.org/python-pep8-1.4.5-2.el6.noarch.rpm > > oVirt repo: > > yum install http://resources.ovirt.org/releases/ovirt-release.noarch.rpm > > RHEL 6 users must add the glusterfs repository, providing newer glusterfs > not available on RHEL 6. Optionally install 'wget' if not present > > rpm -q wget 2> /dev/null || yum install wget > > wget -O /etc/yum.repos.d/glusterfs-epel.repo > *http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/glusterfs-epel.repo* > <http://download.gluster.org/pub/gluster/glusterfs/LATEST/EPEL.repo/glusterf…> > > Fedora and RHEL 6 users must verify the following packages are installed > before attempting to build: > > yum install make autoconf automake pyflakes logrotate gcc python-pep8 > libvirt-python python-devel \ > > python-nose rpm-build sanlock-python genisoimage python-ordereddict > python-pthreading libselinux-python\ > > python-ethtool m2crypto python-dmidecode python-netaddr > python-inotify python-argparse git \ > > python-cpopen bridge-utils libguestfs-tools-c pyparted openssl libnl > libtool gettext-devel python-ioprocess libvirt libvirt-client > libvirt-lock-sanlock > > 4 Getting the source > > cd /root > > git clone *http://gerrit.ovirt.org/p/vdsm.git* > <http://gerrit.ovirt.org/p/vdsm.git> > > cd vdsm > > 5 Building a Vdsm RPM > > ./autogen.sh –system > > > > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --libdir=/usr/lib --enable-hooks > > make rpm NOSE_EXCLUDE=.* > 6 Basic installation and start > > When building from source, you should enable the ovirt-beta repository, to > satisfy dependencies that are not available yet in the release repository. > > # cd ~/rpmbuild/RPMS > > # yum install --skip-broken > --enablerepo=ovirt-master-snapshot-static x86_64/* noarch/vdsm-xml* > noarch/vdsm-cli* noarch/vdsm-python-zombiereaper* > noarch/vdsm-*jsonrpc* > > > > Before starting vdsmd service for the first time vdsm requires some > configuration procedures for external services that being used by vdsmd. To > ease this process vdsm provides a utility (vdsm-tool). To perform full > reconfiguration of external services perform: > > # vdsm-tool configure --force > > (for more information read "vdsm-tool --help") > > > > > 7 Finally start the vdsmd service > > # service vdsmd start > > > 8 Yum install -y bridge-utils > > Configuring the bridge Interface as below > > Disable the network manager service by executing as root: > > systemctl stop NetworkManager.service > > systemctl disable NetworkManager.service > > > > service network start > > chkconfig network on > > Add the following content into a new file named: > */etc/sysconfig/network-scripts/ifcfg-ovirtmgmt*: > > DEVICE=ovirtmgmt > > TYPE=Bridge > > ONBOOT=yes > > DELAY=0 > > BOOTPROTO=static > > IPADDR=10.1.8.252 > > NETMASK=255.255.255.0 > > GATEWAY=10.1.8.254 > > Add the following line into the configuration file of your out going > interface (usually em1/eth0) the file is located at: > */etc/sysconfig/network-scripts/ifcfg-em1* (assuming the device is em1) > > BRIDGE=ovirtmgmt > > and remove the IPADDR, NETMASK and BOOTPROTO keys, since the interface > should not have an IP address of its own. Full Example > > DEVICE=em1 > > ONBOOT=yes > > BRIDGE=ovirtmgmt > > Restart the network service by executing: > > service network restart > > *Note that if any other bridge (from ovirtmgmt) is present at the time of > host installation, the bridge creation operation is skipped and you have to > change the bridge settings to correspond to above shown configuration > manually.* > > > > *9 Configuring VDSM* > > Add the following content into the file: */etc/vdsm/vdsm.conf* (you may > need to create that file): > > [vars] > > ssl = false > > Restart the vdsmd service by executing: > > service vdsmd restart > > If Vdsm was started earlier with ssl=true, it would refuse to start and you > may need to use the undocumented verb > > service vdsmd reconfigure you should perform - "vdsm-tool configure --force" without touching other conf files. you already did it, so nothing else required although, we you set InstallVds to true (few lines underneath), it means that when you add the host to engine it will perform all those deploying vdsm steps for you. So you don't have to do all those vdsm configuration and installation steps at all. > > service vdsmd start > > which edits */etc/libvirt/qemu.conf* and changes *spice_tls=1* to > *spice_tls=0*. > > > 10 Connect to overt-engine > > *ref: OVirt_-_connecting_development_vdsm_to_ovirt_engine > <http://www.ovirt.org/OVirt_-_connecting_development_vdsm_to_ovirt_engine>.* > > > > *su - postgres -c "psql engine -c \"UPDATE vdc_options set option_value = > 'true' where option_name = 'InstallVds'\""* > > > > *service overt-engine restart* > 11 Attach the host to the engine > > I login the engine Administration Portal , and attach the centos host to a > cluster. But it failed. > can you please attach logs (host deploy logs under /var/log/ovirt-engine/host-deploy , vdsm log under /var/log/vdsm (on host side) and engine log /var/log/ovirt-engine/engine.log) I forward the mail to devel(a)ovirt.org, vdsm-devel was merged to this one few months ago. > > > _______________________________________________ > vdsm-devel mailing list > vdsm-devel(a)lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > Regards. -- Yaniv Bronhaim.

1 0

[IMPORTANT] DB script numbering reminder
by Oved Ourfali 13 Jul '14

13 Jul '14

Hi Now that a branch was created for ovirt-engine-3.5, master is practically of version 3.6. So, when adding a DB script in a patch that is pushed to master, the numbering should start with 03_06_ABCD, where ABCD starts with 0010, second should be 0020, and so on... When this patch needs to be ported to 3.5 as well, the numbering there should be 03_05_EFGH, where EFGH is the next number in the stable branch. So, for example, if the last upgrade script in the stable branch starts with 03_05_0750, then the next should start with 03_05_0760, even if it starts with 03_06_0040 on master. Confused? we're here to help! Got it? go ahead and push some stuff! Have a great day, Oved

1 0

ovirt-guest-agent
by Sandro Bonazzola 12 Jul '14

12 Jul '14

Hi, looking at http://jenkins.ovirt.org/view/All/ I see that for ovirt-guest-agent there's only the following job: http://jenkins.ovirt.org/view/All/job/ovirt-guest-agent_master_gerrit/ This means that ovirt-guest-agent is not built nightly neither for master nor for stable and it's not published neither in nightly snapshot nor in official releases. I see that ovirt-guest-agent is shipped within Fedora and EPEL: http://koji.fedoraproject.org/koji/packageinfo?packageID=15434 so I suppose official release are shipped there. Do we need nightly builds? Also I see that http://www.ovirt.org/How_to_install_the_guest_agent_in_Fedora refers to obsolete layout / releases and the package is not shipped within oVirt repo for above considerations and should be updated accordingly. -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

4 4

[vdsm] VM recovery now depends on HSM
by Adam Litke 11 Jul '14

11 Jul '14

Hi all, As part of the new live merge feature, when vdsm starts and has to recover existing VMs, it calls VM._syncVolumeChain to ensure that vdsm's view of the volume chain matches libvirt's. This involves two kinds of operations: 1) sync VM object, 2) sync underlying storage metadata via HSM. This means that HSM must be up (and the storage domain(s) that the VM is using must be accessible. When testing some rather eccentric error flows, I am finding this to not always be the case. Is there a way to have VM recovery wait on HSM to come up? How should we respond if a required storage domain cannot be accessed? Is there a mechanism in vdsm to schedule an operation to be retried at a later time? Perhaps I could just schedule the sync and it could be retried until the required resources are available. Thanks for your insights. -- Adam Litke

4 7

[vdsm] logging levels and noise in the log
by Martin Sivak 11 Jul '14

11 Jul '14

Hi, we discussed the right amount of logging with Nir and Francesco while reviewing my patches. Francesco was against one DEBUG log message that could potentially flood the logs. But the message in question was important for me and SLA, because it was logging the VDSM changes in response to MoM command. Since DEBUG really is meant to be used for debug messages, I have one proposal: 1) Change the default log level of vdsm.log to INFO 2) Log (only) DEBUG messages to a separate file vdsm-debug.log 3) Make the vdsm-debug.log rotate faster (every hour, keep only last couple of hours?) so it does not grow too much This way the customer would be able to monitor INFO logs (much smaller) without all the noise and we would be able to collect the DEBUG part in case something happens. What do you think? -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ

7 11

Call for Papers Deadline In Two Days: Linux.conf.au
by Brian Proffitt 11 Jul '14

11 Jul '14

Conference: Linux.conf.au Information: Each year open source geeks from across the globe gather in Australia or New Zealand to meet their fellow technologists, share the latest ideas and innovations, and spend a week discussing and collaborating on open source projects. The conference is well known for the speakers and delegates depth of talent, and its focus on technical linux content. Possible topics: Virtualization, oVirt, KVM, libvirt, RDO, OpenStack, Foreman Date: January 12-15, 2015 Location: Auckland, New Zealand Website: http://lca2015.linux.org.au/ Call for Papers Deadline: July 13, 2014 Call for Papers URL: http://lca2015.linux.org.au/cfp Contact me for more information and assistance with presentations. -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

1 0

python-pthreading 0.1.3-2
by Douglas Schilling Landgraf 11 Jul '14

11 Jul '14

Hi, python-pthreading 0.1.3-2 is available to test. Please help giving karmas to achieve this version to stable branch as soon as possible. Changes included: - monkey_patch: Fail if it is too late to monkey-patch - Add the missing locked() interface F19: https://admin.fedoraproject.org/updates/python-pthreading-0.1.3-2.fc19 F20: https://admin.fedoraproject.org/updates/python-pthreading-0.1.3-2.fc20 EL6: https://admin.fedoraproject.org/updates/python-pthreading-0.1.3-2.el6 -- Cheers Douglas

2 1

[Documentation] Assistance Needed with User-Facing Documentation
by Brian Proffitt 10 Jul '14

10 Jul '14

All: The Red Hat ECS team has made a great effort to convert some of the more important downstream documentation to a MediaWiki format that we can post on oVirt.org as an official set of user- and admin-facing documentation. This is being done as a bootstrapping effort to get our upstream documentation up to date and take a big step towards making the upstream documentation the canonical source for documentation in the near future. Before that can happen, we need to get this RHEV-oriented information ported over to oVirt nomenclature and screenshots taken for oVirt and added to the documents as well. I have placed the three guides * Administration Guide[1] * User's Guide[2] * Installation Guide[3] on the oVirt site as unlinked pages. General wording has been changed from RHEV to oVirt, but not always. Each of these documents must be reviewed and completely adapted to oVirt 3.4 before they can be posted as official documentation. Specifically: * Review all text to ensure proper steps and descriptions for oVirt features and procedures * Review all text to remove downstream-specific text * Review all code for changes in package names on on-screen displays * Replace all downstream RHEV screenshots with upstream oVirt 3.4 screenshots (Max width: 1024px) I will be stepping through these documents to edit them in more detail under these guidelines, but help is most assuredly needed, in order to get this done in a timely manner. oVirt.org wiki users can visit these pages, review them, and add their changes. MediaWiki has limited version control, so it would be best to edit sections instead of entire documents, to minimize stepping on others' changes. Editing by section will also help us track the sections that have been edited, using the pages' histories. Thank you in advance for all of your help on this project... when finished, this will represent a significant improvement to oVirt's documentation, and make oVirt that much easier to use. Peace, Brian [1] http://www.ovirt.org/DraftAdministrationGuide [2] http://www.ovirt.org/DraftUserGuide [3] http://www.ovirt.org/DraftInstallationGuide -- Brian Proffitt oVirt Community Manager Project Atomic Community Lead Open Source and Standards, Red Hat - http://community.redhat.com Phone: +1 574 383 9BKP IRC: bkp @ OFTC

2 1

[ANN] oVirt 3.4.3 Release Candidate is now available
by Sandro Bonazzola 10 Jul '14

10 Jul '14

The oVirt development team is pleased to announce the availability of oVirt 3.4.3 Release Candidate as of Jul 10th 2014 for testing. oVirt is available now for Fedora 19 and Red Hat Enterprise Linux 6.5 (or similar). This release of oVirt includes numerous bug fixes. See the release notes [1] for a list of the new features and bugs fixed. The new repository ovirt-3.4-rc has been updated for delivering this release, please refer to release notes [1] for instructions on how to enable the repository and for Installation / Upgrade instructions. A new oVirt Live ISO will be available soon[2]. Feel free to join us testing it [3]! [1] http://www.ovirt.org/OVirt_3.4.3_Release_Notes [2] http://resources.ovirt.org/pub/ovirt-3.4-rc/iso/ [3] http://www.ovirt.org/Testing/oVirt_3.4.3_Testing -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

1 0

Exception during VM recovery causes VMs not being properly recovered
by Vinzenz Feenstra 10 Jul '14

10 Jul '14

Hi, With the current master of VDSM after restarting VDSM (e.g. after upgrading) I noticed that the VMs were not properly initialized and in PAUSED state. Once checking the logs I found that the cause was here: Thread-13::INFO::2014-07-10 12:11:56,400::vm::2244::vm.Vm::(_startUnderlyingVm) vmId=`db614831-3b4b-4010-a989-f7a5ae6fa5d0`::Skipping errors on recovery Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 2228, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 3312, in _run self._domDependentInit() File "/usr/share/vdsm/virt/vm.py", line 3204, in _domDependentInit self._syncVolumeChain(drive) File "/usr/share/vdsm/virt/vm.py", line 5686, in _syncVolumeChain volumes = self._driveGetActualVolumeChain(drive) File "/usr/share/vdsm/virt/vm.py", line 5665, in _driveGetActualVolumeChain sourceAttr = ('file', 'dev')[drive.blockDev] TypeError: tuple indices must be integers, not NoneType The reason here seems to be this: Thread-13::DEBUG::2014-07-10 12:11:56,393::vm::1349::vm.Vm::(blockDev) vmId=`db614831-3b4b-4010-a989-f7a5ae6fa5d0`::Unable to determine if the path '/rhev/data-center/00000002-0002-0002-0002-000000000002/41b6de4e-23da-481d-904d-9af24fc5f3ab/images/17206f99-38ab-45bc-ae9b-d36a66b00e4c/7b05de43-9d85-435f-8ae9-6ccde21548e4' is a block device Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 1346, in blockDev self._blockDev = utils.isBlockDevice(self.path) File "/usr/lib64/python2.6/site-packages/vdsm/utils.py", line 99, in isBlockDevice return stat.S_ISBLK(os.stat(path).st_mode) OSError: [Errno 2] No such file or directory: '/rhev/data-center/00000002-0002-0002-0002-000000000002/41b6de4e-23da-481d-904d-9af24fc5f3ab/images/17206f99-38ab-45bc-ae9b-d36a66b00e4c/7b05de43-9d85-435f-8ae9-6ccde21548e4' I am running the host on RHEL6.5 Note: I just rebooted the host and started a few more VMs again and when I restart VDSM I get the same errors again. -- Regards, Vinzenz Feenstra | Senior Software Engineer RedHat Engineering Virtualization R & D Phone: +420 532 294 625 IRC: vfeenstr or evilissimo Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com

2 1