vdsm-devel February 2012

vdsm-devel@lists.stg.fedorahosted.org

31 participants
34 discussions

How to configure sharedFS ?
by deepakcs＠linux.vnet.ibm.com 02 Mar '12

02 Mar '12

I posted this to users@ovirt list, but no response, trying my chance here. ================================== Hi, From vdsm code i can see support for storage domain of type SHARED_FS But when trying to configure a new storage domain, i don't see SHARED_FS as a available domtype filed in the dropdown. I want to use shared FS to connect to try and connect to gluster mount point on my node, but unable to as I don't see that option. From http://www.ovirt.org/wiki/Features/PosixFSConnection - I understand that its the same as sharedFS, so what is PosixFSConnection then, is it just a new interface that provides a wrapper for what is sharedFS now ? The status of this says Done, but I don't see the UI part of this, am I missing something. Also pls let me know if usign sharedFS to make the node use gluster mount is correct or not ? thanx, deepak

2 5

Fedora Virtualization Test Day 2012-04-12
by abaron＠redhat.com 29 Feb '12

29 Feb '12

Hi all, $subject is a month and a half away. Any volunteers to driving vdsm testing forward for that day? https://fedoraproject.org/wiki/Test_Day:2012-04-12_Virtualization_Test_Day Regards, Ayal

3 2

Error using vdsClient
by deepakcs＠linux.vnet.ibm.com 29 Feb '12

29 Feb '12

Hello, Trying vdsClient for the first time. I am getting the below error for any cmd I am trying to use... [root@llm65 ~]# vdsClient llm65.in.ibm.com getVGList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in <module> code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 524, in getVGList vgs = self.s.getVGList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' [root@llm65 ~]# vdsClient llm65.in.ibm.com getConnectedStoragePoolsList Traceback (most recent call last): File "/usr/share/vdsm/vdsClient.py", line 1972, in <module> code, message = commands[command][0](commandArgs) File "/usr/share/vdsm/vdsClient.py", line 1056, in getConnectedStoragePoolsList pools = self.s.getConnectedStoragePoolsList() File "/usr/lib64/python2.7/xmlrpclib.py", line 1224, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python2.7/xmlrpclib.py", line 1575, in __request verbose=self.__verbose File "/usr/lib64/python2.7/xmlrpclib.py", line 1264, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python2.7/xmlrpclib.py", line 1294, in single_request response = h.getresponse(buffering=True) File "/usr/lib64/python2.7/httplib.py", line 1027, in getresponse response.begin() File "/usr/lib64/python2.7/httplib.py", line 407, in begin version, status, reason = self._read_status() File "/usr/lib64/python2.7/httplib.py", line 371, in _read_status raise BadStatusLine(line) BadStatusLine: '' Note : I am running the above on the host (llm65) & already have configured FC, storage via OE and via OE, I am able to create and run VMs also, but vdsClient fails to give the VG and SP lists. thanx, deepak

3 4

MOM Integration Plan
by agl＠us.ibm.com 29 Feb '12

29 Feb '12

Hi all, Very shortly Mark will be sending some patches for review that implement the long-awaited integration of mom with vdsm. I felt it would be easier to understand the changes to vdsm if they were explained a bit better. In support of this I have created a wiki page on ovirt.org with a diagram: http://ovirt.org/wiki/Features/MomIntegration To facilitate discussion, here is the text of that page: As discussed at the oVirt Workshop and elsewhere, integrating mom with vdsm will benefit oVirt by providing a mechanism for dynamic, policy-based tuning. This mechanism will pave the way for implementing memory ballooning policies, can enhance migration policy, and will replace the existing ksm tuning thread. MOM exists today as an independent library that can be used by python programs such as vdsm or in standalone mode (by using the accompanying momd program. Mom's operation is very configurable. The management policy is written in a Fortran-like language and is replaceable by the end user. Additionally, plugins allow you to customize the types of information collected and the manner in which it is collected. Similarly, Controller plugins permit a completely flexible control API to be created. To integrate mom, vdsm will initialize the mom library in a new thread and start it. Therefore, mom and vdsm will exist in the same process. Vdsm will configure the mom instance to use plugins and a policy that exclusively target the vdsm API. All statistics collection will occur via API calls and any management actions (including adjustments to KSM and VM balloons) will be done through the vdsm api as well. Mom will not use libvirt at all (not even to monitor for new VMs on the system). Packaging logistics: ------------------------- Mom is an independent package that is already in Fedora. Any changes to mom that are required to support this integration will be submitted to the mom project for inclusion. Vdsm will consume the standard MOM package as a python module/library. In order to control its mom instance, vdsm will ship a mom configuration file and a mom policy file that will set mom's default behavior. At startup, vdsmd will import mom and initialize it with the configuration and policy files. From that point on, mom will interact with vdsm through the well-defined API in API.py. New features needed in vdsm: --------------------------------------- In order to fully benefit from mom's capabilities, vdsm should implement the following extra features/APIs: - Collection of more memory statistics via ovirt-guest-agent including the current memory balloon value. - A vmBalloon API to set a new balloon target. -- Adam Litke <agl(a)us.ibm.com> IBM Linux Technology Center

2 1

dealing with a vestigial mailing list
by Karsten Wade 28 Feb '12

28 Feb '12

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 VDSM chose to stick with fedorahosted.org for Mailman (which is fine), but we had made a vdsm-devel(a)ovirt.org as part of a batch action and never took it down nor hid it. D'oh! http://lists.ovirt.org/mailman/listinfo/vdsm-devel I was thinking, should we send an email to that list directing people to go to the @fedorahosted address, then moderate everyone and hide the list? I shy away from vaporizing the list entirely "just in case". Also, there are real archives of unanswered questions - should we leave that up? http://lists.ovirt.org/pipermail/vdsm-devel/ (Can someone make sure those folks were responded to otherwise here or on IRC? If not, let me know and I can respond on vdsm-devel(a)ovirt.org with a pointer to this list, etc.) It was my mistake the @ovirt.org list stayed up there; all other locations on ovirt.org reference the fhosted list, it's just that people who look at lists.ovirt.org/mailman/listinfo will see vdsm-devel. So I'm offering to do the clean-up and just need to figure out what that entails Thoughts? Thanks! - - Karsten - -- name: Karsten 'quaid' Wade, Sr. Community Architect team: Red Hat Community Architecture & Leadership uri: http://communityleadershipteam.org http://TheOpenSourceWay.org gpg: AD0E0C41 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFPTScT2ZIOBq0ODEERAqw7AKCPtmQyd9hEt74bWsZwOzpteXzK1gCcCxnc 75KP9W21EtkMh4kpvpw1kU8= =NYrJ -----END PGP SIGNATURE-----

2 1

Remove and Add host does not work
by deepakcs＠linux.vnet.ibm.com 28 Feb '12

28 Feb '12

Hi, I had a host managed via OE, completely working fine. Was even able to create and run VMs off it. I tried removing the host from the OE (put host into maint. mode and then remove) and when i re-discover the same host, OE just keeps seeing it as Non-responsive. I am able to ssh into the host and see that none of the vdsm processes have been started. I tried doing "Confirm host has been rebooted" on the OE, did not help. I tried putting host into maint. mode and re-activating the host, just doesn't help I waited for ~45 mins thinking OE might connect to the host, start vdsm and get me the Up status but it failed. Do i need to manually start vdsm in such a scenario on the host ? Are there ways or methods to have OE forcibly start vdsm on the host ? thanx, deepak

3 9

create StorageDomain failed of LOCALFS in vdsm-4.9.4-0.18
by Royce Lv 28 Feb '12

28 Feb '12

Guys, Tried create StorageDomain in vdsm-4.9.4-0.18 with following parameters: sddef = '{ "id": "1ef32ac7-1e12-4823-8e8c-8c887333fe46", "type": "LOCALFS", "class":"Data", "version":"0", "name": "Test Domain", "remotePath": "/var/lib/vdsm/storagetmp1" }' and the Path "/var/lib/vdsm/storagetmp1" is newly created Things goes well in vdsm4.9.0 but doesn't work in vdsm4.9.4, The error message is: StorageServerAccessPermissionError: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path.: 'path = /rhev/data-center/mnt/_var_lib_vdsm_storagetmp1' I verified all access permission and make sure it is right.Trace is below: File "/usr/share/vdsm/storage/task.py", line 863, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 38, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 1929, in createStorageDomain domClass, typeSpecificArg, storageType, domVersion) File "/usr/share/vdsm/storage/localFsSD.py", line 66, in create cls._preCreateValidation(sdUUID, mntPoint, remotePath, version) File "/usr/share/vdsm/storage/localFsSD.py", line 39, in _preCreateValidation validateDirAccess(domPath) File "/usr/share/vdsm/storage/storage_connection.py", line 40, in validateDirAccess getProcPool().fileUtils.validateAccess(dirPath) File "/usr/share/vdsm/storage/processPool.py", line 53, in wrapper return self.runExternally(func, *args, **kwds) File "/usr/share/vdsm/storage/processPool.py", line 64, in runExternally return self._procPool.runExternally(*args, **kwargs) the following cmd caused this failure according to my log: CP Server Thread-18::DEBUG::2012-02-27 10:51:58,788::lvm::352::OperationMutex::(_reloadvgs) Operation 'lvm reload operation' got the operation mutex CP Server Thread-18::DEBUG::2012-02-27 10:51:58,789::lvm::287::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm vgs --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \\"a%35000c500382d9c53%\\", \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --noheadings --units b --nosuffix --separator | -o uuid,name,attr,size,free,extent_size,extent_count,free_count,tags,vg_mda_size,vg_mda_free 1ef32ac7-1e12-4823-8e8c-8c887333fe46' (cwd None) CP Server Thread-18::DEBUG::2012-02-27 10:51:59,178::lvm::287::Storage.Misc.excCmd::(cmd) FAILED: <err> = ' Volume group "1ef32ac7-1e12-4823-8e8c-8c887333fe46" not found\n'; <rc> = 5 CP Server Thread-18::WARNING::2012-02-27 10:51:59,182::lvm::356::Storage.LVM::(_reloadvgs) lvm vgs failed: 5 [] [' Volume group "1ef32ac7-1e12-4823-8e8c-8c887333fe46" not found'] since I use "LOCALFS" ,I think it should have nothing to do with lvm and I have no vg in my env.This log makes me confused.Will somebody pls take a look and help with it? Thank you in advance!

3 4

vdsm test release plan
by Royce Lv 28 Feb '12

28 Feb '12

Guys, We have unittest cases for VDSM REST API at hand and expect to merge them with VDSM test harness. So would someone provide a schedule of VDSM test release plan? Will it be released with VDSM or in another repository?We'd like to work with it as soon as possible. Thanks a lot!

3 3

Support for stateless nodes
by mburns＠redhat.com 27 Feb '12

27 Feb '12

There has been a lot of interest in being able to run stateless Nodes with ovirt-engine. ovirt-node has designed a way [1] to achieve this on the node side, but we need input from the engine and vdsm teams to see if we're missing some requirement or if there needs to be changes on the engine/vdsm side to achieve this. As it currently stands, every time you reboot an ovirt-node that is stateless, it would require manually removing the host in engine, then re-registering/approving it again in engine. Any thoughts, concerns, input on how to solve this? Thanks Mike [1] http://ovirt.org/wiki/Node_Stateless

6 20

Error creating fc based storage domain
by deepakcs＠linux.vnet.ibm.com 23 Feb '12

23 Feb '12

Hello, This is the error i see in vdsm.log Any pointers appreciated. Thread-237764::INFO::2012-02-21 22:04:52,785::logUtils::37::dispatcher::(wrapper) Run and protect: createVG(vgname='2b63c813-6bd5-4488-904c-dba1c8e52822', devlist=['3600a0b800017dd4f00000e2e4a4ab484'], options=None) Thread-237764::DEBUG::2012-02-21 22:04:52,788::lvm::287::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvcreate --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \\"a%3600a0b800017dcec00000f324a4ab9ef|3600a0b800017dcec00000f334a4aba67|3600a0b800017dcec00000f344a4aba75|3600a0b800017dcec00000f354a4aba8d|3600a0b800017dd4f00000e2e4a4ab484|3600a0b800017dd4f00000e2f4a4ab56c%\\", \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " --metadatasize 128m --metadatacopies 2 --metadataignore y /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484' (cwd None) Thread-237764::DEBUG::2012-02-21 22:04:52,854::lvm::287::Storage.Misc.excCmd::(cmd) FAILED: <err> = " Can't open /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484 exclusively. Mounted filesystem?\n"; <rc> = 5 Thread-237764::DEBUG::2012-02-21 22:04:52,857::lvm::287::Storage.Misc.excCmd::(cmd) '/usr/bin/sudo -n /sbin/lvm pvs --config " devices { preferred_names = [\\"^/dev/mapper/\\"] ignore_suspended_devices=1 write_cache_state=0 disable_after_error_count=3 filter = [ \\"a%3600a0b800017dcec00000f324a4ab9ef|3600a0b800017dcec00000f334a4aba67|3600a0b800017dcec00000f344a4aba75|3600a0b800017dcec00000f354a4aba8d|3600a0b800017dd4f00000e2e4a4ab484|3600a0b800017dd4f00000e2f4a4ab56c%\\", \\"r%.*%\\" ] } global { locking_type=1 prioritise_write_locks=1 wait_for_locks=1 } backup { retain_min = 50 retain_days = 0 } " -o vg_name,pv_name --noheading /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484' (cwd None) Thread-237764::DEBUG::2012-02-21 22:04:52,914::lvm::287::Storage.Misc.excCmd::(cmd) FAILED: <err> = ' No physical volume label read from /dev/mapper/3600a0b800017dd4f00000e2e4a4ab484\n Failed to read physical volume "/dev/mapper/3600a0b800017dd4f00000e2e4a4ab484"\n'; <rc> = 5 Thread-237764::ERROR::2012-02-21 22:04:52,916::task::855::TaskManager.Task::(_setError) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Unexpected error Traceback (most recent call last): File "/usr/share/vdsm/storage/task.py", line 863, in _run return fn(*args, **kargs) File "/usr/share/vdsm/logUtils.py", line 38, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/storage/hsm.py", line 1556, in createVG metadataSize=blockSD.VG_METADATASIZE) File "/usr/share/vdsm/storage/lvm.py", line 796, in createVG _initpvs(pvs, metadataSize) File "/usr/share/vdsm/storage/lvm.py", line 634, in _initpvs found, notFound) PhysDevInitializationError: Failed to initialize physical device: ('found: %s notFound: %s', {}, <generator object <genexpr> at 0x7fd8c031a780>) Thread-237764::DEBUG::2012-02-21 22:04:52,942::task::874::TaskManager.Task::(_run) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Task._run: 17d5267f-fe25-49d4-9a7d-e04f2785d3b7 ('2b63c813-6bd5-4488-904c-dba1c8e52822', ['3600a0b800017dd4f00000e2e4a4ab484']) {} failed - stopping task Thread-237764::DEBUG::2012-02-21 22:04:52,942::task::1201::TaskManager.Task::(stop) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::stopping in state preparing (force False) Thread-237764::DEBUG::2012-02-21 22:04:52,942::task::980::TaskManager.Task::(_decref) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::ref 1 aborting True Thread-237764::INFO::2012-02-21 22:04:52,943::task::1159::TaskManager.Task::(prepare) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::aborting: Task is aborted: 'Failed to initialize physical device' - code 601 Thread-237764::DEBUG::2012-02-21 22:04:52,943::task::1164::TaskManager.Task::(prepare) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Prepare: aborted: Failed to initialize physical device Thread-237764::DEBUG::2012-02-21 22:04:52,943::task::980::TaskManager.Task::(_decref) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::ref 0 aborting True Thread-237764::DEBUG::2012-02-21 22:04:52,943::task::915::TaskManager.Task::(_doAbort) Task=`17d5267f-fe25-49d4-9a7d-e04f2785d3b7`::Task._doAbort: force False

2 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

vdsm-devel February 2012