Re: [vdsm] [RFC] ipv6 support of vdsm
- Original Message - > From: "Igor Lvovsky" > To: "Daniel P. Berrange" > Cc: vdsm-devel@lists.fedorahosted.org > Sent: Friday, November 9, 2012 7:34:53 AM > Subject: Re: [vdsm] [RFC] ipv6 support of vdsm > > > > - Original Message - > > From: "Daniel P. Berrange" > > To: "Dan Kenigsberg" > > Cc: vdsm-devel@lists.fedorahosted.org > > Sent: Friday, November 9, 2012 1:21:12 AM > > Subject: Re: [vdsm] [RFC] ipv6 support of vdsm > > > > On Fri, Nov 09, 2012 at 12:59:21AM +0200, Dan Kenigsberg wrote: > > > On Thu, Nov 08, 2012 at 10:35:23PM +0100, Daniel P. Berrange > > > wrote: > > > > On Thu, Nov 08, 2012 at 11:25:19PM +0200, Dan Kenigsberg wrote: > > > > > On Thu, Nov 08, 2012 at 06:58:09PM +0800, huntxu wrote: > > > > > > Hi, folks. > > > > > > > > > > > > Recently I am considering to implement ipv6 support for > > > > > > vdsm. > > > > > > First > > > > > > of all I > > > > > > would like to know whether there is already someone working > > > > > > on this > > > > > > feature. > > > > > > > > > > I am not aware of anyone working on ipv6 at the momemnt. You > > > > > are more > > > > > than welcome to lead the way! > > > > > > > > > > > If so, I might do something to help, however, if not, I > > > > > > would > > > > > > try to > > > > > > implement > > > > > > it with suggestions from this discussion. > > > > > > > > > > > > With ipv6 support vdsm is supposed to work properly in: > > > > > > * mixed environment, in which ipv4 and ipv6 addresses > > > > > > coexist > > > > > > * ipv6-pure environment > > > > > > > > > > > > My idea is: > > > > > > > > > > > > 1) Provide a mechanism to setup ipv6 address configuration > > > > > > of > > > > > > a host via > > > > > > XMLRPC/RestAPI. This would be done in the current > > > > > > ConfigNetwork module by > > > > > > modifying the network-scripts/ifcfg-* of the devices. Thus > > > > > > the host is > > > > > > able to access ipv6 network (with correct configuration). > > > > > > > > > > Host network configuration is an important part. We would > > > > > have > > > > > to report > > > > > ipv6 addresses, too. > > > > > > > > > > Please keep in mind, that we would like to move away from > > > > > direct ifcfg > > > > > mangaling since it's distribution-dependent, and not even the > > > > > common > > > > > practice in modern Fedoras. (sob) > > > > > > > > I'd love to see VDSM start to make use of libvirt's network > > > > interface > > > > APIs, since we added all that support for making transaction > > > > config > > > > changes for the benefit of VDSM :-) It of course supports IPv6 > > > > configuration already, and would get you portability to Debian, > > > > Suse > > > > and soon BSD via NetCF. > > > > > > Yeah, we are shamefully behind schedule here.. I hope Mark Wu is > > > going > > > to step up our pace (http://gerrit.ovirt.org/8618). > > > > > > Dan, this may be a good opportunity to raise my concerns about > > > netcf's > > > ifcfg-based implementation. How is NetCF going to interoperate > > > with > > > the > > > rise to fame of NetworkManager an systemd? If I recall correctly, > > > /etc/init.d/network, which is responsible of ifup'ing ifcfgs, is > > > not > > > even started by default on F17+. Due you have plans for a bleak > > > future > > > where ifcfg's are frowned upon? > > > > NetworkManager is able to read / write ifcfg files in > > /etc/sysconfig/network-scripts. Historically it would > > ignore any config that referred to bridging, since it > > did not support that. As and when NM supports things > > like bridging/bonding/vlans hopefully it will also get > > the ability to understand those ifcfg files. > > > > as we heard from
Re: [vdsm] [RFC] ipv6 support of vdsm
- Original Message - > From: "Daniel P. Berrange" > To: "Dan Kenigsberg" > Cc: vdsm-devel@lists.fedorahosted.org > Sent: Friday, November 9, 2012 1:21:12 AM > Subject: Re: [vdsm] [RFC] ipv6 support of vdsm > > On Fri, Nov 09, 2012 at 12:59:21AM +0200, Dan Kenigsberg wrote: > > On Thu, Nov 08, 2012 at 10:35:23PM +0100, Daniel P. Berrange wrote: > > > On Thu, Nov 08, 2012 at 11:25:19PM +0200, Dan Kenigsberg wrote: > > > > On Thu, Nov 08, 2012 at 06:58:09PM +0800, huntxu wrote: > > > > > Hi, folks. > > > > > > > > > > Recently I am considering to implement ipv6 support for vdsm. > > > > > First > > > > > of all I > > > > > would like to know whether there is already someone working > > > > > on this > > > > > feature. > > > > > > > > I am not aware of anyone working on ipv6 at the momemnt. You > > > > are more > > > > than welcome to lead the way! > > > > > > > > > If so, I might do something to help, however, if not, I would > > > > > try to > > > > > implement > > > > > it with suggestions from this discussion. > > > > > > > > > > With ipv6 support vdsm is supposed to work properly in: > > > > > * mixed environment, in which ipv4 and ipv6 addresses > > > > > coexist > > > > > * ipv6-pure environment > > > > > > > > > > My idea is: > > > > > > > > > > 1) Provide a mechanism to setup ipv6 address configuration of > > > > > a host via > > > > > XMLRPC/RestAPI. This would be done in the current > > > > > ConfigNetwork module by > > > > > modifying the network-scripts/ifcfg-* of the devices. Thus > > > > > the host is > > > > > able to access ipv6 network (with correct configuration). > > > > > > > > Host network configuration is an important part. We would have > > > > to report > > > > ipv6 addresses, too. > > > > > > > > Please keep in mind, that we would like to move away from > > > > direct ifcfg > > > > mangaling since it's distribution-dependent, and not even the > > > > common > > > > practice in modern Fedoras. (sob) > > > > > > I'd love to see VDSM start to make use of libvirt's network > > > interface > > > APIs, since we added all that support for making transaction > > > config > > > changes for the benefit of VDSM :-) It of course supports IPv6 > > > configuration already, and would get you portability to Debian, > > > Suse > > > and soon BSD via NetCF. > > > > Yeah, we are shamefully behind schedule here.. I hope Mark Wu is > > going > > to step up our pace (http://gerrit.ovirt.org/8618). > > > > Dan, this may be a good opportunity to raise my concerns about > > netcf's > > ifcfg-based implementation. How is NetCF going to interoperate with > > the > > rise to fame of NetworkManager an systemd? If I recall correctly, > > /etc/init.d/network, which is responsible of ifup'ing ifcfgs, is > > not > > even started by default on F17+. Due you have plans for a bleak > > future > > where ifcfg's are frowned upon? > > NetworkManager is able to read / write ifcfg files in > /etc/sysconfig/network-scripts. Historically it would > ignore any config that referred to bridging, since it > did not support that. As and when NM supports things > like bridging/bonding/vlans hopefully it will also get > the ability to understand those ifcfg files. > as we heard from NetworkManager guys the bridging/bonding/vlans should be support in rhel7, maybe already in rhel6.4 > Eventually we may well create a virInterface API driver > in libvirt that talks to NetworkManager via DBus, replacing > the use of netcf. This should be transparent to apps like > VDSM that used virInterface. This is actually why you want > to use libvirt's virInterface APIs instead of directly using > netcf. > Sounds good. Regards, Igor > Regards, > Daniel > -- > |: http://berrange.com -o- > | http://www.flickr.com/photos/dberrange/ :| > |: http://libvirt.org -o- > |http://virt-manager.org :| > |: http://autobuild.org -o- > |http://search.cpan.org/~danberr/ :| > |: http://entangle-photo.org -o- > | http://live.gnome.org/gtk-vnc :| > ___ > vdsm-devel mailing list > vdsm-devel@lists.fedorahosted.org > https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel > ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [RFC] ipv6 support of vdsm
On Fri, Nov 09, 2012 at 12:59:21AM +0200, Dan Kenigsberg wrote: > On Thu, Nov 08, 2012 at 10:35:23PM +0100, Daniel P. Berrange wrote: > > On Thu, Nov 08, 2012 at 11:25:19PM +0200, Dan Kenigsberg wrote: > > > On Thu, Nov 08, 2012 at 06:58:09PM +0800, huntxu wrote: > > > > Hi, folks. > > > > > > > > Recently I am considering to implement ipv6 support for vdsm. First > > > > of all I > > > > would like to know whether there is already someone working on this > > > > feature. > > > > > > I am not aware of anyone working on ipv6 at the momemnt. You are more > > > than welcome to lead the way! > > > > > > > If so, I might do something to help, however, if not, I would try to > > > > implement > > > > it with suggestions from this discussion. > > > > > > > > With ipv6 support vdsm is supposed to work properly in: > > > > * mixed environment, in which ipv4 and ipv6 addresses coexist > > > > * ipv6-pure environment > > > > > > > > My idea is: > > > > > > > > 1) Provide a mechanism to setup ipv6 address configuration of a host via > > > > XMLRPC/RestAPI. This would be done in the current ConfigNetwork module > > > > by > > > > modifying the network-scripts/ifcfg-* of the devices. Thus the host is > > > > able to access ipv6 network (with correct configuration). > > > > > > Host network configuration is an important part. We would have to report > > > ipv6 addresses, too. > > > > > > Please keep in mind, that we would like to move away from direct ifcfg > > > mangaling since it's distribution-dependent, and not even the common > > > practice in modern Fedoras. (sob) > > > > I'd love to see VDSM start to make use of libvirt's network interface > > APIs, since we added all that support for making transaction config > > changes for the benefit of VDSM :-) It of course supports IPv6 > > configuration already, and would get you portability to Debian, Suse > > and soon BSD via NetCF. > > Yeah, we are shamefully behind schedule here.. I hope Mark Wu is going > to step up our pace (http://gerrit.ovirt.org/8618). > > Dan, this may be a good opportunity to raise my concerns about netcf's > ifcfg-based implementation. How is NetCF going to interoperate with the > rise to fame of NetworkManager an systemd? If I recall correctly, > /etc/init.d/network, which is responsible of ifup'ing ifcfgs, is not > even started by default on F17+. Due you have plans for a bleak future > where ifcfg's are frowned upon? NetworkManager is able to read / write ifcfg files in /etc/sysconfig/network-scripts. Historically it would ignore any config that referred to bridging, since it did not support that. As and when NM supports things like bridging/bonding/vlans hopefully it will also get the ability to understand those ifcfg files. Eventually we may well create a virInterface API driver in libvirt that talks to NetworkManager via DBus, replacing the use of netcf. This should be transparent to apps like VDSM that used virInterface. This is actually why you want to use libvirt's virInterface APIs instead of directly using netcf. Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [RFC] ipv6 support of vdsm
On Thu, Nov 08, 2012 at 10:35:23PM +0100, Daniel P. Berrange wrote: > On Thu, Nov 08, 2012 at 11:25:19PM +0200, Dan Kenigsberg wrote: > > On Thu, Nov 08, 2012 at 06:58:09PM +0800, huntxu wrote: > > > Hi, folks. > > > > > > Recently I am considering to implement ipv6 support for vdsm. First > > > of all I > > > would like to know whether there is already someone working on this > > > feature. > > > > I am not aware of anyone working on ipv6 at the momemnt. You are more > > than welcome to lead the way! > > > > > If so, I might do something to help, however, if not, I would try to > > > implement > > > it with suggestions from this discussion. > > > > > > With ipv6 support vdsm is supposed to work properly in: > > > * mixed environment, in which ipv4 and ipv6 addresses coexist > > > * ipv6-pure environment > > > > > > My idea is: > > > > > > 1) Provide a mechanism to setup ipv6 address configuration of a host via > > > XMLRPC/RestAPI. This would be done in the current ConfigNetwork module by > > > modifying the network-scripts/ifcfg-* of the devices. Thus the host is > > > able to access ipv6 network (with correct configuration). > > > > Host network configuration is an important part. We would have to report > > ipv6 addresses, too. > > > > Please keep in mind, that we would like to move away from direct ifcfg > > mangaling since it's distribution-dependent, and not even the common > > practice in modern Fedoras. (sob) > > I'd love to see VDSM start to make use of libvirt's network interface > APIs, since we added all that support for making transaction config > changes for the benefit of VDSM :-) It of course supports IPv6 > configuration already, and would get you portability to Debian, Suse > and soon BSD via NetCF. Yeah, we are shamefully behind schedule here.. I hope Mark Wu is going to step up our pace (http://gerrit.ovirt.org/8618). Dan, this may be a good opportunity to raise my concerns about netcf's ifcfg-based implementation. How is NetCF going to interoperate with the rise to fame of NetworkManager an systemd? If I recall correctly, /etc/init.d/network, which is responsible of ifup'ing ifcfgs, is not even started by default on F17+. Due you have plans for a bleak future where ifcfg's are frowned upon? Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [RFC] ipv6 support of vdsm
On Thu, Nov 08, 2012 at 11:25:19PM +0200, Dan Kenigsberg wrote: > On Thu, Nov 08, 2012 at 06:58:09PM +0800, huntxu wrote: > > Hi, folks. > > > > Recently I am considering to implement ipv6 support for vdsm. First > > of all I > > would like to know whether there is already someone working on this > > feature. > > I am not aware of anyone working on ipv6 at the momemnt. You are more > than welcome to lead the way! > > > If so, I might do something to help, however, if not, I would try to > > implement > > it with suggestions from this discussion. > > > > With ipv6 support vdsm is supposed to work properly in: > > * mixed environment, in which ipv4 and ipv6 addresses coexist > > * ipv6-pure environment > > > > My idea is: > > > > 1) Provide a mechanism to setup ipv6 address configuration of a host via > > XMLRPC/RestAPI. This would be done in the current ConfigNetwork module by > > modifying the network-scripts/ifcfg-* of the devices. Thus the host is > > able to access ipv6 network (with correct configuration). > > Host network configuration is an important part. We would have to report > ipv6 addresses, too. > > Please keep in mind, that we would like to move away from direct ifcfg > mangaling since it's distribution-dependent, and not even the common > practice in modern Fedoras. (sob) I'd love to see VDSM start to make use of libvirt's network interface APIs, since we added all that support for making transaction config changes for the benefit of VDSM :-) It of course supports IPv6 configuration already, and would get you portability to Debian, Suse and soon BSD via NetCF. > > 5) The management connection is supposed to be able to switch between ipv4 > > and ipv6 on the fly (when host is under maintenance and with proper network > > configuration of the host). This requires another vdsm API. > > This problem is already with us - if vdsm.conf is configured to listen > on one address, and a setupNetwork call changes the management network > address to something else, I'm pretty sure that we'd get disconnected. > This bug is not widely noticed, since vdsm listens to all ip addresses > by default. > > 6) migration over ipv6, If you pass libvirt a hostname for the migration target, libvirt should will do correct DNS resolution to work with IPv6, and so should QEMU. If you pass libvirt a raw IPv4 address, then obviously you'll need some work to switch to passing IPv6 addrs. The main thing to be aware of is the need to use [] around the address if including it in a URI Regards, Daniel -- |: http://berrange.com -o-http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [RFC] ipv6 support of vdsm
On Thu, Nov 08, 2012 at 06:58:09PM +0800, huntxu wrote: > Hi, folks. > > Recently I am considering to implement ipv6 support for vdsm. First > of all I > would like to know whether there is already someone working on this > feature. I am not aware of anyone working on ipv6 at the momemnt. You are more than welcome to lead the way! > If so, I might do something to help, however, if not, I would try to > implement > it with suggestions from this discussion. > > With ipv6 support vdsm is supposed to work properly in: > * mixed environment, in which ipv4 and ipv6 addresses coexist > * ipv6-pure environment > > My idea is: > > 1) Provide a mechanism to setup ipv6 address configuration of a host via > XMLRPC/RestAPI. This would be done in the current ConfigNetwork module by > modifying the network-scripts/ifcfg-* of the devices. Thus the host is > able to access ipv6 network (with correct configuration). Host network configuration is an important part. We would have to report ipv6 addresses, too. Please keep in mind, that we would like to move away from direct ifcfg mangaling since it's distribution-dependent, and not even the common practice in modern Fedoras. (sob) > > 2) For incoming spice connections, qemu is able to listen to ipv6 address, > so we use a boolean option "spice_use_ipv6" which indicates whether qemu > should listen to incoming ipv6 or ipv4 connections. > > 3) Make the connection with ovirt-engine(management connection) also ipv6- > compatible. This requires modifying both XMLRPC and RestAPI servers to make > them able to bind to the ipv6 address of the host. Also we need another > boolean option "use_ipv6" to indicate what is the ip version of the > management connection. As former posters have noted, I'm not sure that a boolean flag is the best practice here. Currently, vdsm can listen to all ipv4 addresses, or to a single one, specified by vdsm.conf's management_address. This should be extended to allow ipv6 addresses. > > 4) Regarding the register process, all is the same with the current > workflow, > except for if we use ipv6 to register, we should firstly set "use_ipv6" to > True, then XMLRPC and RestAPI servers would be listening on the ipv6 > address > after vdsm restarts. ditto regarding use_ipv6 boolean. > > 5) The management connection is supposed to be able to switch between ipv4 > and ipv6 on the fly (when host is under maintenance and with proper network > configuration of the host). This requires another vdsm API. This problem is already with us - if vdsm.conf is configured to listen on one address, and a setupNetwork call changes the management network address to something else, I'm pretty sure that we'd get disconnected. This bug is not widely noticed, since vdsm listens to all ip addresses by default. 6) migration over ipv6, 7) connection to remote iscsi/nfs over ipv6. 8) guest ipv6 - I believe we're already there. ... and probably more. > > Suggestions are always welcome. Thanks. Good luck, it would be great to see progress here. Regards, Dan. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [RFC] ipv6 support of vdsm
Hi, huntxu píše v Čt 08. 11. 2012 v 18:58 +0800: > Hi, folks. > > Recently I am considering to implement ipv6 support for vdsm. First of all > I > would like to know whether there is already someone working on this > feature. > If so, I might do something to help, however, if not, I would try to > implement > it with suggestions from this discussion. > > With ipv6 support vdsm is supposed to work properly in: > * mixed environment, in which ipv4 and ipv6 addresses coexist > * ipv6-pure environment > > My idea is: > > 1) Provide a mechanism to setup ipv6 address configuration of a host via > XMLRPC/RestAPI. This would be done in the current ConfigNetwork module by > modifying the network-scripts/ifcfg-* of the devices. Thus the host is > able to access ipv6 network (with correct configuration). > > 2) For incoming spice connections, qemu is able to listen to ipv6 address, > so we use a boolean option "spice_use_ipv6" which indicates whether qemu > should listen to incoming ipv6 or ipv4 connections. beware that this is a can of worms: 1) spice server can not really listen on v6 only, you can only choose between v4 (default) or v6+v4 (if you set -spice ipv6,... or -spice addr=::,... and its libvirt domain xml equivalents) because "-spice ipv6" is just an equivalent of "-spice addr=::", not of IPV6_V6ONLY 2) spice server does not know or use SO_BINDTODEVICE 3) spice server can bind to a single IP address only: https://bugzilla.redhat.com/show_bug.cgi?id=787259 points 2 + 3 combined have several unfortunate consequences: 1. you can't have separate display network and mixed ipv4 + ipv6 spice-server at once -- IIRC that's most of current RHEV deployments 2. you can't have spice-server listening on multiple ipv6 addresses at once - that's requirement for essentially any serious ipv6 use 3. even if 1. and 2. would be resolved, the existing VM displays would break if there is any network configuration change (that is much more probable event than in ipv4 because of different network configuration mechanisms as far as I know -- but Pavel could correct me here). Using SO_BINDTODEVICE and bind to "::" (ipv6 wildcard) sounds like the best option here but there is a catch: this option is supported by linux kernel for root-processes only but qemu actually runs under regular "qemu" user... All of these make current spice ipv6 support limited to quite small subset of real-world use cases, a kind of proof-of-concept one. Pavel (CCd) could surely trow in several more examples of what can go wrong. Given all of these, I'd leave spice part as-is for now till these details are at least decided how they should look like... David > > 3) Make the connection with ovirt-engine(management connection) also ipv6- > compatible. This requires modifying both XMLRPC and RestAPI servers to make > them able to bind to the ipv6 address of the host. Also we need another > boolean option "use_ipv6" to indicate what is the ip version of the > management > connection. > > 4) Regarding the register process, all is the same with the current > workflow, > except for if we use ipv6 to register, we should firstly set "use_ipv6" to > True, then XMLRPC and RestAPI servers would be listening on the ipv6 > address > after vdsm restarts. > > 5) The management connection is supposed to be able to switch between ipv4 > and ipv6 on the fly (when host is under maintenance and with proper network > configuration of the host). This requires another vdsm API. > > Suggestions are always welcome. Thanks. > -- David Jaša, RHCE SPICE QE based in Brno GPG Key: 22C33E24 Fingerprint: 513A 060B D1B4 2A72 7F0D 0278 B125 CD00 22C3 3E24 ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
Re: [vdsm] [RFC] ipv6 support of vdsm
- Original Message - > From: "huntxu" > To: vdsm-devel@lists.fedorahosted.org > Sent: Thursday, November 8, 2012 12:58:09 PM > Subject: [vdsm] [RFC] ipv6 support of vdsm > > Hi, folks. > > Recently I am considering to implement ipv6 support for vdsm. First > of all > I > would like to know whether there is already someone working on this > feature. > If so, I might do something to help, however, if not, I would try to > implement > it with suggestions from this discussion. > > With ipv6 support vdsm is supposed to work properly in: > * mixed environment, in which ipv4 and ipv6 addresses coexist > * ipv6-pure environment > > My idea is: > > 1) Provide a mechanism to setup ipv6 address configuration of a host > via > XMLRPC/RestAPI. This would be done in the current ConfigNetwork > module by > modifying the network-scripts/ifcfg-* of the devices. Thus the host > is > able to access ipv6 network (with correct configuration). > > 2) For incoming spice connections, qemu is able to listen to ipv6 > address, > so we use a boolean option "spice_use_ipv6" which indicates whether > qemu > should listen to incoming ipv6 or ipv4 connections. > > 3) Make the connection with ovirt-engine(management connection) also > ipv6- > compatible. This requires modifying both XMLRPC and RestAPI servers > to make > them able to bind to the ipv6 address of the host. Also we need > another > boolean option "use_ipv6" to indicate what is the ip version of the > management > connection. > > 4) Regarding the register process, all is the same with the current > workflow, > except for if we use ipv6 to register, we should firstly set > "use_ipv6" to > True, then XMLRPC and RestAPI servers would be listening on the ipv6 > address > after vdsm restarts. > > 5) The management connection is supposed to be able to switch between > ipv4 > and ipv6 on the fly (when host is under maintenance and with proper > network > configuration of the host). This requires another vdsm API. > > Suggestions are always welcome. Thanks. This is great, although I don't understand why not listening to all incoming communication? Why does the application cares if it is connected from ipv4 or ipv6? it should accept any connection. If we can put ACL of valid sources, and then be ip type aware, but it is not implemented currently as far as I know, so no need to add this now. Regards, Alon. ___ vdsm-devel mailing list vdsm-devel@lists.fedorahosted.org https://lists.fedorahosted.org/mailman/listinfo/vdsm-devel
