On Wed, Jul 28, 2010 at 07:56, Manuel Franceschini <[email protected]> wrote: > Hi all, > > I'm not sure about a couple of somehow related design decisions, so I > thought I'd ask here. > > As of now Ganeti binds its daemons to '0.0.0.0' per default. This, > obviously, becomes an issue if we want to support both IPv4 and IPv6. > We want to support the following setups: > > a) pure IPv4 > b) IPv6 as primary and IPv4 as secondary > > In case b) we need to bind the daemons to '::'. To achieve that we > have the following options: > > i) Pass a different bind_address for each daemon startup > ii) Let lib/daemon.py get the primary ip version (which will be a > future cluster parameter) from the config, and bind '0.0.0.0' or '::' > accordingly. > > To me option ii) seems cleaner. I'm not sure, however, to retrieve the > primary ip version from the config or ssconf. It seems, the primary ip > version would be a good candidate for ssconf. What do you guys think? > Any feedback/suggestions is more than welcome!
primary ip version? as in primary IP family? Also note that for some OSes, when you bind to an IPv6 socket, don't automatically make you listen on IPv4 too (e.g. recent Debian). So with a single socket it's either IPv4 *or* IPv6. iustin
