Intel workshop in Shangai
by asegurap＠redhat.com
Hi List,
You might be interested in the Intel oVirt workshop schedule. Here it is:
Wednesday, May 8, 2013 - Operations Track
08:30-09:00 Opening remarks and Keynote : Intel Open Source Strategy Jackson He (Intel)
09:00-10:00 oVirt Introduction Doron Fediuck (Red Hat)
10:00-11:00 oVirt Architecture Overview Dan Kenigsberg (Red Hat)
11:00-11:15 Coffee Break
11:15 - 12:15 Deploying and testing oVirt using nested virtualization Mark Wu (IBM)
12:15-13:30 Lunch
13:30-14:30 oVirt SLA overview Doron Fediuck (Red Hat)
14:30-15:00 oVirt storage system and IBM's activity Shu Ming (IBM)
15:00-15:15 Coffee Break
15:15-16:15 Troubleshooting oVirt Tal Nisan (Red Hat)
16:15-17:00 Converged Infrastructure with oVirt and Gluster Theron Conrey (Red Hat)
Wednesday, May 8th, 2013 - oVirt / Gluster Integration Track
Time Title Speaker
08:30-09:00 Opening remarks and Keynote : Intel Open Source Strategy Jackson He
09:00-10:00 Gluster Community Overview and Roadmap John Mark Walker (Red Hat)
10:00-11:00 Gluster Architecture Overview To be announced
11:00-11:15 Coffee break
11:15-12:15 oVirt Configurations and Gluster Tal Nisan (Red Hat)
12:15-13:30 Lunch
13:30-14:30 Converged Infrastructure with oVirt and Gluster Theron Conrey (Red Hat)
14:30-15:30 Gluster and Swift Object Store (UFO) John Mark Walker (Red Hat)
15:30-15:45 Coffee break
15:45-16:45 Developing with GlusterFS - translator framework, libgfapi and more Vijay Bellur (Red Hat)
Thursday, May 9, 2013 - Developer Track
Time Title Speaker
09:00-10:00 oVirt-node overview Ying Cui and Guohua Ouyang (Red Hat)
10:00-11:00 Packaging oVirt for Ubuntu Zhengsheng Zhou (IBM)
11:00 - 11:15 Coffee Break
11:15-12:15 oVirt SLA- MoM as host level enforcement agent Doron Fediuck (Red Hat)
12:15-13:30 Lunch
13:30-14:30 Trusted Compute Pools Deep Dive Gang Wei
14:30-15:30 KVM Nested Virtualization to be announced
15:30-15:45 Coffee break
15:30-17:00 The present and future of SetupNetwork in oVirt Dan Kenisberg (Red Hat)
17:00-17:30 Closing remarks and closing keynote
Thursday, May 9, 2013 - Self paced labs / oVirt Install
Time Title Speaker
09:00-12:00 oVirt Hands-on Workshop To be announced
12:00-13:30 Lunch
13:30-16:00 oVirt and Gluster configurations To be announced
11 years
fail to connect qemu process's channel
by bigclouds
hi,all
my demo waiting all the time.
vdsm can neither connect vm channel.
--------------vdsm.log--------------
vmChannels::103::vdsm::(_handle_unconnected) Trying to connect fileno 18.-
----------------------my demo---------
import os, sys
import time
import socket
import logging
sys.path.append("/usr/share/vdsm")
from vmChannels import Listener
import threading
import guestIF
import supermcvda
import json
_guestSocketFile = "/var/lib/libvirt/qemu/channels/winxp.com.redhat.rhevm.vdsm"
_sock = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
_sock.setblocking(1)
try:
_sock.connect(_guestSocketFile)
except Exception as err:
print err
exit(1)
args={'__name__':'log-off'}
message = (json.dumps(args) + '\n').encode('utf8')
time.sleep(1)
_sock.send(message)
print _sock.recv(2 ** 10)
11 years
Is vdsm still maintained for Fedora 17?
by wudxw＠linux.vnet.ibm.com
Hi Dan,
Since the repo of virt-preview for fedora17 is not maintained after
fedora 18 was released, it could be difficult to install the packages
vdsm master branch requires on fedora17.
So do we still maintain vdsm for fedora17? Do we need consider if the
patch to upstream will cause break on fedora17?
Thanks.
Mark
11 years
Re: [vdsm] [Users] questions about vdsm supervdsmserver
by ybronhei＠redhat.com
Hey bigclouds,
Supervdsm allows vdsm to run root commands, like mount, dmidecode, lsblk, scan folders that are unprivileged for vdsm user, and more. Due to this method we avoid executing root commands using execv with sudo, that way we don't create subprocess for each operation.
We have to have supervdsm as external deamon, as it runs as different user (root, vdsm runs as user vdsm). Supervdsm deamon doesn't related to libvirt or uses libvirt at all, most of supervdsm functionality is used by vdsm in different flows. you can check supervdsm API in supervdsmServer.py and see where we call it.
We need to have only one instance of supervdsm with a socket file under /var/run/vdsm/ , supervdsm creates this file and vdsm communicate with it.
Due to your netstat output, most of the time you should have 2 or 3 entries
unix 2 [ ACC ] STREAM LISTENING 18895145 /var/run/vdsm/svdsm.sock
unix 2 [ ] STREAM CONNECTED 18895172 /var/run/vdsm/svdsm.sock
unix 3 [ ] STREAM CONNECTED 18895158 /var/run/vdsm/svdsm.sock
(multiprocessing package implementation, you can check there)
might be that other subprocesses or subthreads also hold a request to svdsm.sock at the time you checked,
I don't understand the reason for /var/run/mcvda folder at all.. maybe you changed something in the configuration? is it always appear? what else do you have under this folder?
Normal run shouldn't have more entries as far as I checked.
In addition, I'm working on making supervdsm external service, you can take a look and maybe help me with review :)
[http://gerrit.ovirt.org/#/c/11051/]
Regards,
Yaniv Bronhaim.
----- Original Message -----
> From: "bigclouds" <bigclouds(a)163.com>
> To: users(a)ovirt.org
> Sent: Friday, April 26, 2013 9:59:47 AM
> Subject: [Users] questions about vdsm supervdsmserver
>
> hi,all.
> i have 2 questions about supervdsmserver,
> 1.why it is created separately as a daemon?
> its many function have never been used, and its function can be done by
> calling libvirt directly, why supervdsmserver is need?
> 2.it seems that only one supervdsmserver should be exist, by killing old ones
> to assure that . but look at this, and please explain to me.
> unix 2 [ ACC ] STREAM LISTENING 1339963 4968/python /var/run/vdsm/svdsm.sock
> unix 2 [ ACC ] STREAM LISTENING 384165 39716/python &nb sp;
> /var/run/vdsm/svdsm.sock
> unix 2 [ ACC ] STREAM LISTENING 1100509 49487/python /var/run/vdsm/svdsm.sock
> unix 2 [ ACC ] STREAM LISTENING 1326232 3813/python /var/run/mcvda/svdsm.sock
> unix 3 [ ] STREAM CONNECTED 1448193 4968/python /var/run/mcvda/svdsm.sock
> unix 3 [ ] STREAM CONNECTED 1447937 4968/python /var /run/mcvda/svdsm.sock
> unix 3 [ ] STREAM CONNECTED 1424959 4968/python /var/run/mcvda/svdsm.sock
> unix 3 [ ] STREAM CONNECTED 1414835 4968/python /var/run/mcvda/svdsm.sock
> unix 3 [ ] STREAM CONNECTED 1327873 3813/python /var/run/mcvda/svdsm.sock
> unix 2 [ ] STREAM CONNECTED 1309612 49487/python & nbsp;
> /var/run/mcvda/svdsm.sock
> unix 3 [ ] STREAM CONNECTED 384221 39716/python /var/run/mcvda/svdsm.sock
> thanks
>
>
>
> _______________________________________________
> Users mailing list
> Users(a)ovirt.org
> http://lists.ovirt.org/mailman/listinfo/users
>
11 years
