----- Original Message -----
From: "huntxu" mhuntxu@gmail.com 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:
- 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).
- 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.
- 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.
- 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.
- 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.