June 2013 - vdsm-devel - Fedora Mailing-Lists

by Douglas Schilling Landgraf

Hi, Is it only me failing on tests/alignmentScanTests.py on a fresh clone of vdsm tree? $ cat /etc/fedora-release Fedora release 19 (Schrödinger’s Cat) $ ./autogen.sh --system && make && make rpm zombieReaperTests testProcessDiedBeforeBeingTracked OK testProcessDiesAfterBeingTracked OK ====================================================================== FAIL: test_help_response (alignmentScanTests.AlignmentScanTests) ---------------------------------------------------------------------- Traceback (most recent call last): File "/home/fedora/rpmbuild/BUILD/vdsm-4.11.0/tests/alignmentScanTests.py", line 56, in test_help_response "alignment of virtual machine partitions"), -1) AssertionError: -1 == -1 -------------------- >> begin captured logging << -------------------- Storage.Misc.excCmd: DEBUG: '/usr/bin/virt-alignment-scan --help' (cwd None) Storage.Misc.excCmd: DEBUG: SUCCESS: <err> = ''; <rc> = 0 --------------------- >> end captured logging << --------------------- ---------------------------------------------------------------------- Ran 272 tests in 288.602s FAILED (SKIP=23, failures=1) make[4]: *** [check-local] Error 1 make[4]: Leaving directory `/home/fedora/rpmbuild/BUILD/vdsm-4.11.0/tests' make[3]: *** [check-am] Error 2 make[3]: Leaving directory `/home/fedora/rpmbuild/BUILD/vdsm-4.11.0/tests' make[2]: *** [check-recursive] Error 1 make[2]: Leaving directory `/home/fedora/rpmbuild/BUILD/vdsm-4.11.0/tests' make[1]: *** [check-recursive] Error 1 make[1]: Leaving directory `/home/fedora/rpmbuild/BUILD/vdsm-4.11.0' error: Bad exit status from /var/tmp/rpm-tmp.3i1rpi (%check) RPM build errors: Bad exit status from /var/tmp/rpm-tmp.3i1rpi (%check) make: *** [rpm] Error 1 -- Cheers Douglas

10 years, 10 months

2
4
0 / 0

environment encoding, LC_ALL and vdsm tests

by Martin Sivak

Hi, recently I discovered an issue with our Jenkins test environment. It was failing in testHooks.py because my Gerrit name contains diacritics and our code tried to decode it as ascii. Traceback (most recent call last): File "/usr/lib64/python2.6/unittest.py", line 278, in run testMethod() File "/ephemeral0/vdsm_unit_tests_gerrit_el/tests/hooksTests.py", line 125, in test_deviceCustomProperties params={'customProperty': ' rocks!'}) File "/ephemeral0/vdsm_unit_tests_gerrit_el/vdsm/hooks.py", line 70, in _runHooksDir scriptenv[k] = unicode(v).encode('utf-8') UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 12: ordinal not in range(128) The relevant code is here: hooks.py: 60 scriptenv = os.environ.copy() ... 69 for k, v in scriptenv.iteritems(): 70 scriptenv[k] = unicode(v).encode('utf-8') My first instinct was to decode it using the proper encoding: source_encoding = sys.stdin.encoding or locale.getpreferredencoding() for k, v in scriptenv.iteritems(): scriptenv[k] = v.decode(source_encoding).encode('utf-8') But it still did not work. So I tried to print out the environment and encodings that are used when make check is being run and got this: sys.stdin.encoding == None locale.getpreferredencoding() -> ANSI_X3.4-1968 os.environ['LC_ALL'] == 'C' os.environ['LANG'] == 'en_US.UTF-8' Please notice the encoding part, my system and terminal are using utf-8, but vdsm reads the environment values using ANSI. That is obviously wrong and can't work. So i tried to investigate it further and found out we force LC_ALL to C in vdsmd.init, run_tests.sh.in and run_tests_local.sh.in. I also found the commit that introduced this - 107644dbad9af250c00e7f25fc51a92c6250d442 - and finally understood where the issue was. Although I understand the reasons for the patch, I do not agree with it. If we are executing other tools and parse their output, we should be preparing and passing the updated locale _only_ to those tools. We should not be setting the locale we need for parsing stuff to the whole vdsm daemon. Our current practice of setting LC_ALL to C no matter on what terminal or system we are starting vdsmd is causing us the above mentioned issue, because the environment can (and does) contain data in the system encoding. This essentially prevents anybody with utf-8 chars in their names to submit anything to vdsm. So I would like to start a discussion about this that will lead to the necessary fixes and change in our current practice :) -- Martin Sivák msivak(a)redhat.com Red Hat Czech RHEV-M SLA / Brno, CZ

10 years, 10 months

4
5
0 / 0

vdsm sync meeting June 17th 2013

by asegurap＠redhat.com

VDSM sync meeting Monday June 17th 2013 ======================================= - Dan requests reviews for pending patches from Mei Liu and himself ( http://gerrit.ovirt.org/#/c/15356/8 ) for mom. - Toni to fix the problem with Mark's patch that Dan reviewed so that it can be merged together with the smaller following patches. - Federico has three high priority patches for features and two lower priority ones that need reviews in order to make it for the release deadline. They are related to disk extension and image upload/download (glance): + http://gerrit.ovirt.org/#/c/15442 - constants: unify the BLANK_UUID def... + http://gerrit.ovirt.org/#/c/14589 - volume: add the BLOCK_SIZE constant +1 + http://gerrit.ovirt.org/#/c/14590 - volume: add the extendVolumeSize method + http://gerrit.ovirt.org/#/c/15614 - vm: add the live diskSizeExtend method +1 + http://gerrit.ovirt.org/#/c/14955 - image: add support to upload/download images - Adam and others to review Gluster patches: + http://gerrit.ovirt.org/#/c/13785/ + http://gerrit.ovirt.org/#/c/11094/ - Is there a filing for Qemu image handling reported by virt team? - Reminder to follow wiki feature page process closely to maximize changes to have features added to a release. - Multiple gateways are being worked on to fix dhcp races and comments by reviewers. - NetReloaded after multiple gateways. Try to get up to iproute2 configurator. - Cross-distro support: + Netreloaded with iproute2 plus persistence would help. + init scripts separation (proposed by Yaniv to make ready for 3.3). - Cloud-init integration by Greg Padgett. There is a vdsm patch that should be taken care of in terms of reviewing http://gerrit.ovirt.org/#/c/14347/

10 years, 10 months

7
15
0 / 0

AUTO: Yih-Herng Chuang/Seattle/IBM is out of the office, (returning 06/24/2013)

by Yih-Herng Chuang

I am out of the office until 06/24/2013. For FSM security tech issues, please contact project manager Mark Rayner. For others, please contact my manager John Aguiar. I will respond your email when I am back to work. Note: This is an automated response to your message "vdsm-devel Digest, Vol 25, Issue 13" sent on 06/23/2013 2:44:22. This is the only notification you will receive while this person is away.

10 years, 10 months

1
0
0 / 0

why does VDSM use the SPM to manage and protect the LVM meta-data ?

by tsiren tsi

Hi, As is known to all, sanlock can manage and protect the meta-data which would be modified one by one. Sanlock can be used as the cluster lock with the ids file and lease file. Paxos lease ensures the consistence between all the nodes. In the condition of modifying LVM meta-data(create, delete, extend, and etc) , the sanlock acquire function would be called to lock the block(LUN). Once the operation finished, we could call the sanlock release function to unlock the block.In this case, we could no longer maintain the two modules(mailbox and SPM). I think that it would be simplify the realization of VDSM. Does anyone consider this question? If we just used the sanlock as the cluster lock, could be the frequent usage of lock(or aquire) and unlock(or release) a performance bottleneck of sytem? Appreciate for your repy, thank you

10 years, 10 months

2
1
0 / 0

Need help on fixing VDSM node non-operational error

by tjeyasin＠redhat.com

Hi All, Currently I am facing some issues while adding a node to an engine. Host comes up initially. Then goes to Non-operational state. On trying to activate the host, it again comes up. Then goes to Non-operational state again and so on. The following message is seen in the engine Events log multiple times - Bridged network ovirtmgmt is attached to multiple interfaces: eth2,eth0 on Host ... The following is seen in the engine logs - 2013-06-06 20:52:23,003 INFO [org.ovirt.engine.core.vdsbroker.VdsUpdateRunTimeInfo] (DefaultQuartzScheduler_Worker-16) Host '...' moved to Non-Operational state because interface/s 'eth0, ' are down which needed by network/s 'ovirtmgmt, ' in the current cluster Additional info: The host is a physical machine. The contents of the file /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt - # cat /etc/sysconfig/network-scripts/ifcfg-ovirtmgmt DEVICE=ovirtmgmt TYPE=Bridge ONBOOT=yes DELAY=0 BOOTPROTO=dhcp NM_CONTROLLED=no The contents of /etc/sysconfig/network-scripts/ifcfg-eth2 # cat /etc/sysconfig/network-scripts/ifcfg-eth2 DEVICE="eth2" BRIDGE="ovirtmgmt" BOOTPROTO="dhcp" HWADDR="00:25:90:93:62:02" IPV6INIT="yes" IPV6_AUTOCONF="yes" NM_CONTROLLED="yes" ONBOOT="yes" TYPE="Ethernet" The contents of /etc/sysconfig/network-scripts/ifcfg-eth0 - # cat /etc/sysconfig/network-scripts/ifcfg-eth0 DEVICE="eth0" HWADDR="00:25:90:7C:2C:7A" NM_CONTROLLED="yes" ONBOOT="yes" Can someone give some suggestion for this issue! Thanks and Regards, Tim

10 years, 10 months

2
3
0 / 0

what is 'qcow2 on LV' and how node communicate

by bigclouds

hi,all 1.it seems that vdsm has the capability to thin providing lv(logical volume), could you please explain the theory of it? 2.i did not notice any code throught which NODE can communicate with each other, called mail-box. if it varies depends on volume type(block,fs), and what is and how they communicate via mail-box? thanks so much.

10 years, 10 months

2
1
0 / 0

Ovirt live build failure

by obasan＠redhat.com

Hello everyone. The jenkins ovirt live job is failing due to libvirt dependency: Error creating Live CD : Failed to build transaction : vdsm-4.11.0-28.git634b9f4.fc18.x86_64 requires libvirt >= 1.0.2-1 http://jenkins.ovirt.org/job/ovirt_live_create_iso/151/artifact/ovirt-liv... Does anyone have an idea how to solve it? the only thing I thought about is compiling libvirt from source in the job itself. Thanks Ohad

10 years, 10 months

3
3
0 / 0

Can anyone tell me the function of these two files(IDS and LEASE) in VDSM? FW: [About the IDS and LEASE file in VDSM] Why don't merge those two files into one file with the different file offset?

by Qixiaozhen

Can anyone tell me the function of these two files(IDS and LEASE)? Thanks 发件人: Qixiaozhen 发送时间: 2013年6月13日 21:57 收件人: 'vdsm-devel(a)lists.fedorahosted.org' 抄送: Luohao (brian); Wangshen (C); Xujunxi 主题: [About the IDS and LEASE file in VDSM] Why don't merge those two files into one file with the different file offset? Hi, all I hava a question about the IDS and lease file in the VDSM. In the demo code of sanlock, these two files are contained in the same file. In the VDSM 4.09, the offset of IDS is 0. However, the value of offset in version 4.10 is 'SDM_LEASE_OFFSET = 512 * 2048'. The comment in the code explains that the differences for them are just for upgrade. According to my understanding, the content of IDS file contains the current cluster lock of the domain, and those in Lease file are the heart-beat info. Why don't merge those two files into one file with the different file offset? In 4.09/4.10, we maintance two files. I think that 'two files' is much more complex than 'one file'. Could anyone explain this for me? Thx sample code in sanlock(version 2.7), the cluster lock and heart-beat info are contained in 'disk': HOST_ID = 1 LOCKSPACE_NAME = "lockspace1" RESOURCE_NAME = "resource1" def main(): print "Creating the sanlock disk" fd, disk = tempfile.mkstemp() # the lease file and ids file are contained in ‘disk’ os.close(fd) offset = sanlock.get_alignment(disk) SNLK_DISKS = [(disk, offset)] print "Registering to sanlock" fd = sanlock.register() print "Initializing '%s'" % (LOCKSPACE_NAME,) sanlock.write_lockspace(LOCKSPACE_NAME, disk) print "Initializing '%s' on '%s'" % (RESOURCE_NAME, LOCKSPACE_NAME) sanlock.write_resource(LOCKSPACE_NAME, RESOURCE_NAME, SNLK_DISKS) print "Acquiring the id '%i' on '%s'" % (HOST_ID, LOCKSPACE_NAME) sanlock.add_lockspace(LOCKSPACE_NAME, HOST_ID, disk) try: print "Acquiring '%s' on '%s'" % (RESOURCE_NAME, LOCKSPACE_NAME) sanlock.acquire(LOCKSPACE_NAME, RESOURCE_NAME, SNLK_DISKS, slkfd=fd, version=0) print "Releasing '%s' on '%s'" % (RESOURCE_NAME, LOCKSPACE_NAME) sanlock.release(LOCKSPACE_NAME, RESOURCE_NAME, SNLK_DISKS, slkfd=fd) finally: print "Releasing the id '%i' on '%s'" % (HOST_ID, LOCKSPACE_NAME) sanlock.rem_lockspace(LOCKSPACE_NAME, HOST_ID, disk) print "Removing the sanlock disk" os.remove(disk) if __name__ == '__main__': main()

10 years, 10 months

1
0
0 / 0

[About the IDS and LEASE file in VDSM] Why don't merge those two files into one file with the different file offset?

by Qixiaozhen

Hi, all I hava a question about the IDS and lease file in the VDSM. In the demo code of sanlock, these two files are contained in the same file. In the VDSM 4.09, the offset of IDS is 0. However, the value of offset in version 4.10 is 'SDM_LEASE_OFFSET = 512 * 2048'. The comment in the code explains that the differences for them are just for upgrade. According to my understanding, the content of IDS file contains the current cluster lock of the domain, and those in Lease file are the heart-beat info. Why don't merge those two files into one file with the different file offset? In 4.09/4.10, we maintance two files. I think that 'two files' is much more complex than 'one file'. Could anyone explain this for me? Thx sample code in sanlock(version 2.7), the cluster lock and heart-beat info are contained in 'disk': HOST_ID = 1 LOCKSPACE_NAME = "lockspace1" RESOURCE_NAME = "resource1" def main(): print "Creating the sanlock disk" fd, disk = tempfile.mkstemp() # the lease file and ids file are contained in 'disk' os.close(fd) offset = sanlock.get_alignment(disk) SNLK_DISKS = [(disk, offset)] print "Registering to sanlock" fd = sanlock.register() print "Initializing '%s'" % (LOCKSPACE_NAME,) sanlock.write_lockspace(LOCKSPACE_NAME, disk) print "Initializing '%s' on '%s'" % (RESOURCE_NAME, LOCKSPACE_NAME) sanlock.write_resource(LOCKSPACE_NAME, RESOURCE_NAME, SNLK_DISKS) print "Acquiring the id '%i' on '%s'" % (HOST_ID, LOCKSPACE_NAME) sanlock.add_lockspace(LOCKSPACE_NAME, HOST_ID, disk) try: print "Acquiring '%s' on '%s'" % (RESOURCE_NAME, LOCKSPACE_NAME) sanlock.acquire(LOCKSPACE_NAME, RESOURCE_NAME, SNLK_DISKS, slkfd=fd, version=0) print "Releasing '%s' on '%s'" % (RESOURCE_NAME, LOCKSPACE_NAME) sanlock.release(LOCKSPACE_NAME, RESOURCE_NAME, SNLK_DISKS, slkfd=fd) finally: print "Releasing the id '%i' on '%s'" % (HOST_ID, LOCKSPACE_NAME) sanlock.rem_lockspace(LOCKSPACE_NAME, HOST_ID, disk) print "Removing the sanlock disk" os.remove(disk) if __name__ == '__main__': main()

10 years, 10 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

vdsm-devel June 2013