Help needed to debug segfault when using ctypes
by avishwan@redhat.com
Hi,
In following patch I am using ctypes to load libgfapi(GlusterFS API) to
get the Gluster volume statvfs information.
http://gerrit.ovirt.org/#/c/17822
I am getting *segfault* when I run
vdsClient 0 glusterVolumeSizeInfoGet volumeName=gv1
But I checked as below and it is working.
cd /usr/share/vdsm
python
>> from gluster import gfapi
>> print gfapi.volumeStatvfs("gv1")
posix.statvfs_result(f_bsize=4096L, f_frsize=4096L,
f_blocks=25803070L, f_bfree=19130426L, f_bavail=17819706L,
f_files=6553600L, f_ffree=5855876L, f_favail=5855876L, f_flag=4096L,
f_namemax=255L)
Please suggest how I can debug this issue.
--
Regards
Aravinda
10 years, 9 months
Upgrade mechanism
by amuller@redhat.com
While implementing a new form of network configuration persistence I needed a way to run 'upgrade code'.
That is, I need the ability to run a piece of code exactly once, on the first boot of VDSM.
My use case is related to unified network persistence - We intend to persist network information
in a new format, and on the first run of a new VDSM that contains unified network persistence code,
it needs to inspect the kernel state and construct the data in the new format. From then on,
it will be persisted and updated when the setupNetworks verb is received. The upgrade code, then,
needs to run only once.
Instead of implementing a unique and custom solution I thought to introduce a very simple and flexible
upgrade mechanism which suits my needs.
http://gerrit.ovirt.org/#/c/17726/
And the following patch is the actual upgrade code, which demonstrates how the upgrade mechanism is used:
http://gerrit.ovirt.org/#/c/18425/
Clarification: This upgrade mechanism is not related to yum upgrade in any way.
Infra guys (And everyone else) - Any feedback is welcome. Thanks!
10 years, 9 months
VDSM sync meeting August 26th 2013
by asegurap@redhat.com
vdsm-sync call August 26th 2013
================================
- Federico reminds people with oVirt-3.3 backporting needs to ping him.
- Toni asks about glusterfs-cli inclusion in el6 (<=6.4). The required packages
that are not on el6 EPEL are gonna be in ovirt repo. There will be an extra
repo as well for gluster requiriments.
- Toni asks reviews for http://gerrit.ovirt.org/#/c/18047/ vm.py refactor.
- Toni asks for storage review/work on functional storage tests (xmlrpc tests
were split on virt and storage tests) so that they will be more consistent
with the rest of new functional tests, mom, virt and networking (using
tests/functional/utils.py).
- Gluster team working on some bugs that will be sent as followup to this email
(management functionality related).
- Timothy Asir asks for reviews asked for patch
http://gerrit.ovirt.org/18345
work related to:
https://bugzilla.redhat.com/999795
10 years, 9 months
suggesting new Vdsm maintaniner(s)
by Dan Kenigsberg
Nominating Toni Puimedon and/or Mark Wu as maintainers
======================================================
During their recent year-or-two of participation in Vdsm development,
both Toni and Mark has demonstrated a genuine care for the health and
evolution of the the project.
They both carry this hard-to-quantify quality of serious-mindedness when
reviewing patches.
Toni's 73 committed patches touch everything that is related to network
configuration and reporting
27 vdsm/configNetwork.py
11 lib/vdsm/netinfo.py
8 vdsm/API.py
8 tests/configNetworkTests.py
7 vdsm/netinfo.py
7 vdsm/netconf/ifcfg.py
5 vdsm/libvirtvm.py
4 vdsm/netmodels.py
... similar to Mark's 80:
16 vdsm/configNetwork.py
12 vdsm/netconf/ifcfg.py
12 vdsm/libvirtvm.py
7 vdsm/clientIF.py
6 lib/vdsm/netinfo.py
5 vdsm/caps.py
5 vdsm/API.py
4 vdsm/vm.py
4 vdsm/netmodels.py
4 vdsm/Makefile.am
I suggest that both of them obtain +2/-2 rights, in the understanding
that they are to be used on net-related parts of the code. This is
particularly important given my nearing, relatively long, vacation.
What do you say?
Dan.
10 years, 10 months
vdsClient networking (addNetwork with existing bond)
by Sandro Bonazzola
Hi,
I'm trying to fix https://bugzilla.redhat.com/999577 which in short is
failing to create bridge specifying a bond interface as nic using vdsClient.
The failing command line is:
'/usr/bin/vdsClient', '-s', 'localhost', 'addNetwork', 'bridge=rhevm', 'vlan=', 'bond=',
'nics=bond2', 'force=False', 'bridged=True', 'BOOTPROTO=dhcp', 'ONBOOT=yes', 'blockingdhcp=true'
I suppose that 'nics=bond2' and 'bond=' are wrong.
I'm searching for a man page or something like that for understanding how to prepare the command line without success.
http://www.ovirt.org/VdsClient is outdated and says anything about networking.
I've seen in http://www.ovirt.org/Vdsm_Network that using a bond should be supported but for the supported topologies
there are no command line examples.
For:
bridge1 ----------- bond --- nic1
\
-- nic2
I suppose that the command line should have 'bond=bond' 'nics=nic1,nic2' is this right?
If the bond already exists is it enough specifying 'bond=bond', 'nics=' ?
--
Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com
10 years, 10 months
Re: [vdsm] [Users] oVirt Weekly Meeting Minutes -- 2013-08-21
by sabose@redhat.com
On 08/21/2013 08:32 PM, Mike Burns wrote:
> Minutes: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-08-21-14.01.html
> Minutes (text):
> http://ovirt.org/meetings/ovirt/2013/ovirt.2013-08-21-14.01.txt
> Log: http://ovirt.org/meetings/ovirt/2013/ovirt.2013-08-21-14.01.log.html
>
> ============================
> #ovirt: oVirt Weekly Meeting
> ============================
>
>
> Meeting started by oschreib at 14:01:24 UTC. The full logs are available
> at http://ovirt.org/meetings/ovirt/2013/ovirt.2013-08-21-14.01.log.html
> .
>
>
>
> Meeting summary
> ---------------
> * agenda and roll call (oschreib, 14:01:34)
> * 3.3 status update (oschreib, 14:01:42)
> * infra team update (oschreib, 14:02:04)
> * Conference and Workshop (oschreib, 14:02:11)
> * Other Topics (oschreib, 14:02:19)
>
> * 3.3 Release update (oschreib, 14:11:44)
> * ovirt 3.3 releae page and tracker: (oschreib, 14:11:57)
> * LINK: http://www.ovirt.org/OVirt_3.3_release-management (oschreib,
> 14:12:04)
> * LINK: https://bugzilla.redhat.com/show_bug.cgi?id=918494
> (oschreib, 14:12:12)
> * GA is one week from now (oschreib, 14:12:35)
> * RC build has been uploaded to ovirt.org, thanks mburns (oschreib,
> 14:13:00)
> * Blocker review (oschreib, 14:13:43)
> * Bug 988299 - Impossible to start VM from Gluster Storage Domain
> (engine, MODIFIED) (oschreib, 14:14:02)
> * probably fixed (oschreib, 14:16:19)
> * ACTION: sahina to verify 988299 is pushed (oschreib, 14:16:37)
> * Bug 994523 - [vdsm][multiple gateways] Keep ovirt management as
> default in the main routing table always (engine, MODIFIED)
> (oschreib, 14:17:08)
> * patch for 988299 is not merged yet (
> http://gerrit.ovirt.org/#/c/17994/ ) (mburns, 14:23:34)
> * need new vdsm build with this patch (mburns, 14:23:43)
> * Bug 994604 - Users cannot log into UserPortal (engine, MODIFIED)
> (oschreib, 14:24:52)
> * ACTION: ecohen to push into 3.3 branch (oschreib, 14:26:18)
> * ACTION: oschreib to rebuild engine afterwards (oschreib, 14:26:31)
> * Bug 997362 - [engine-config] /var/log/ovirt-engine/engine-config.log
> doesn't exist (engine, MODIFIED) (oschreib, 14:27:46)
> * ACTION: emesika to check with 997362 (oschreib, 14:32:10)
> * Blocker review done (oschreib, 14:32:18)
> * ACTION: oschreib to send mail on release go/no-go meeting
> (oschreib, 14:40:29)
>
> * workshops and conferences (mburns, 14:42:03)
> * ovirt developer meetings and planning to happen at KVM Forum (21-23
> October in Edinburgh) (mburns, 14:42:36)
> * there will be additional oVirt content during KVM Forum as well
> (mburns, 14:43:27)
> * dneary to make sure everyone that should be there is in attendance
> for ovirt dev meetings (mburns, 14:45:45)
> * jbrooks has been working on release notes, announcement, etc
> (mburns, 14:48:17)
> * ACTION: oschreib to check about 3.3 live distro (oschreib,
> 14:51:10)
>
> * infra update (mburns, 14:52:40)
> * extra storage in rackspace servers, so backups will be migrated
> there (mburns, 14:55:39)
> * new centos 6.4 slaves are only (mburns, 14:55:47)
> * new puppet classes added to manage jenkins slaves (mburns,
> 14:55:57)
> * more room for additional jenkins slaves (mburns, 14:56:04)
> * jenkins updates to latest LTS (long term stable) (mburns, 14:56:40)
> * hosted-engine-setup and ha builds are now built nightly and pushed
> to nightly repos (mburns, 14:58:03)
> * in process of adding network functional testing to jenkins (mburns,
> 14:58:56)
>
> * Other Topics (mburns, 14:59:49)
> * no other topics (mburns, 15:02:04)
>
> Meeting ended at 15:02:09 UTC.
>
>
>
>
> Action Items
> ------------
> * sahina to verify 988299 is pushed
Could someone from VDSM team help to get this patch merged-
http://gerrit.ovirt.org/#/c/17994?
thanks
sahina
> * ecohen to push into 3.3 branch
> * oschreib to rebuild engine afterwards
> * emesika to check with 997362
> * oschreib to send mail on release go/no-go meeting
> * oschreib to check about 3.3 live distro
>
>
>
>
> Action Items, by person
> -----------------------
> * ecohen
> * ecohen to push into 3.3 branch
> * emesika
> * emesika to check with 997362
> * oschreib
> * oschreib to rebuild engine afterwards
> * oschreib to send mail on release go/no-go meeting
> * oschreib to check about 3.3 live distro
> * sahina
> * sahina to verify 988299 is pushed
> * **UNASSIGNED**
> * (none)
>
>
>
>
> People Present (lines said)
> ---------------------------
> * oschreib (75)
> * mburns (52)
> * dneary (17)
> * ecohen (10)
> * eedri (9)
> * jbrooks (8)
> * sahina (7)
> * awels (6)
> * emesika (6)
> * amuller (4)
> * sbonazzo (4)
> * ovirtbot (4)
> * sgotliv (3)
> * knesenko (1)
> * lvernia (1)
> * mskrivanek (1)
>
>
>
>
> Generated by `MeetBot`_ 0.1.4
>
> .. _`MeetBot`: http://wiki.debian.org/MeetBot
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
10 years, 10 months
how vdsm implement qcow2 on lvm
by bigclouds
hi,all
could you tell me how vdsm implement qcow2 on lvm? and how lv of qcow2 fromat support backing file?
if the implememt is a normal way, now i find libguestfs does not recognize lvs(qcow2 format) with backing file
thanks
10 years, 10 months
Re: [vdsm] Jenkins job to run networking functional tests
by eedri@redhat.com
[adding devel lists]
Usually to get power user privileges you need get +1 community (mostly relevant people in your team/project).
saying you're familiar with jenkins and the project and is cabaple of adding jobs to the project.
I personally give +1 since i know you're contribution and experience.
Eyal.
----- Original Message -----
> From: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> To: "infra" <infra(a)ovirt.org>
> Sent: Monday, August 19, 2013 10:19:46 AM
> Subject: Jenkins job to run networking functional tests
>
> Hello everybody, following the previous discussion with Eyal,
> I need to get rights in order to create a jenkins job to
> achieve what stated in the subject.
>
> Is it the right place for such request?
>
> Cheers, Giuseppe
>
> ----- Forwarded Message -----
> | From: "Eyal Edri" <eedri(a)redhat.com>
> | To: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> | Cc: "infra" <infra(a)ovirt.org>
> | Sent: Sunday, August 18, 2013 2:06:22 PM
> | Subject: Re: running network functional tests
> |
> | Hi,
> |
> | Usually in these cases when a new job is requested to a specific
> | project/component,
> | A 'power user' for the relevant team (in your case network), is given
> | privileges on the Jenkins machine
> | to add any job required.
> |
> | I would propose the following:
> | 1. request power user access to jenkins.ovirt.org (if you don't already
> | have)
> | 2. add a new job with your functional test per commit (not per patch for
> | starts)
> | any infra member can assist you with the labels for slaves / os /etc...
> | 3. once that job is running properly, you can contact infra to assist in
> | converting it to a per-patch job
> | with the topic / field verification logic done.
> | 4. not sure if this is relevant to your tests, but all existing jenkins
> | slaves are VMs and not bare-metal.
> |
> | i hope this helps.
> |
> | Eyal.
> |
> | ----- Original Message -----
> | > From: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> | > To: "infra" <infra(a)ovirt.org>
> | > Sent: Friday, August 16, 2013 12:28:43 PM
> | > Subject: Fwd: running network functional tests
> | >
> | > ----- Forwarded Message -----
> | > | From: "Giuseppe Vallarelli" <gvallare(a)redhat.com>
> | > | To: "infra" <infra(a)ovirt.org>
> | > | Cc: "David Caro Estevez" <dcaroest(a)redhat.com>
> | > | Sent: Monday, August 12, 2013 10:58:04 AM
> | > | Subject: running network functional tests
> | > |
> | > | Hello everbody!
> | > | Just recently we added networking functional tests and we would like
> | > | to have them running when we submit patches network related, i.e.
> | > | going to affect network modules. Displaying success or failure
> | > | as it happens with the current unittests.
> | > |
> | > | Requirements/ideas:
> | > |
> | > | - OS Fedora 19/RHEL6.4 should not matter.
> | > |
> | > | - Kernel module used: bonding, dummy.
> | > |
> | > | - No more than one 'instance' of networkTests should run
> | > | on a specific host, simply because we use some global
> | > | constants to identify network name vlan id and so on.
> | > |
> | > | - Ideally we can use a previously proposed idea of commit tag
> | > | where for example @networking is provided in the commit msg
> | > | title to identify the need of running also the network
> | > | functional tests.
> | > |
> | > | - We should be able to run at the same time functional networking
> | > | tests and unit tests - I don't expect any conflicts.
> | > |
> | > | Would be cool to have a test run before -1s all networking patches
> | > | in case of problems :-)
> | > |
> | > | Let me know if more information are needed.
> | > |
> | > |
> | > | Cheers, Giuseppe
> | >
> | > Is there any update on the subject?
> | >
> | > Any estimate to have functional network tests running?
> | > I mind that we can run network functional tests upstream
> | > that will speed up our workflow and possibly decrease the
> | > regressions.
> | >
> | > Thanks Giuseppe
> | > _______________________________________________
> | > Infra mailing list
> | > Infra(a)ovirt.org
> | > http://lists.ovirt.org/mailman/listinfo/infra
> | >
> |
> _______________________________________________
> Infra mailing list
> Infra(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/infra
>
10 years, 10 months
In mailbox of VDSM, the data interchange was done by 'dd' command. What would be happened once the iscsi IPs in IPSAN were unreachable?
by Qixiaozhen
Hi, all
1) The type of storage domain was IPSAN.
2) All hosts worked well in the ovirt, and the mailboxes in SPM and other hosts were OK.
3) Something occurred in the switcher of the network, and all of the iscsi IPs in the IPSAN were unreachable.
4) What should be happened in this case?
In my opinion, the command named 'dd' would be stuck if the data-plane in the host was off. The monitor thread of HSM and SPM would be stuck on the 'dd' command.
How to recover the VDSM in this situation? Could asynchronous IO be taken into consideration?
Operation Test:
[root@qixiaozhen tmp]#
[root@qixiaozhen tmp]# iscsiadm -m session
tcp: [1] 172.50.16.21:3260,14 iqn.2006-08.com.huawei:oceanstor:21000022a100ecba:notconfig:172.50.16.21
tcp: [2] 172.50.16.20:3260,4 iqn.2006-08.com.huawei:oceanstor:21000022a100ecba:notconfig:172.50.16.20
tcp: [3] 172.40.16.20:3260,3 iqn.2006-08.com.huawei:oceanstor:21000022a100ecba:notconfig:172.40.16.20
tcp: [4] 172.40.16.21:3260,13 iqn.2006-08.com.huawei:oceanstor:21000022a100ecba:notconfig:172.40.16.21
[root@qixiaozhen tmp]# iptables -I INPUT -s 172.50.16.21 -j DROP
[root@qixiaozhen tmp]# iptables -I INPUT -s 172.50.16.20 -j DROP
[root@qixiaozhen tmp]# iptables -I INPUT -s 172.40.16.20 -j DROP
[root@qixiaozhen tmp]# iptables -I INPUT -s 172.40.16.21 -j DROP
[root@qixiaozhen tmp]#
[root@qixiaozhen tmp]# dd if=/dev/disk/by-id/scsi-360022a110000ecba3d5728bb00000015 of=/dev/null bs=1M count=1 iflag=direct <<<<<<<<<< iscsi ip is unreachable, operation is stuck here
^C^C^C
Thank you.
Qi
10 years, 10 months