On Tue, Dec 04, 2018 at 05:29:31PM +0000, Richard W.M. Jones wrote:
This patch is just for discussion. There are still a couple of
issues
that I'm trying to fix.
Sorry if I missed the original discussion on that, but why is copying
the static IP configuraition even considered to be a good thing?
For one, it's unlikely that the IP address will remain valid in the
target environment.
For two, in a typical cloud setup static IP addresses are configured by
some sort of a cloud-specific management agent, and bypassing it is
likely to cause conflicts.
For three, network configuration is a notoriously complex thing. I
think I can recall a dozen of network configuration systems in Linux
that claimed to provide the ultimate solution to all problems and none
that delivered to the promise. I guess in Windows the situation is
hardly much simpler. Creating yet another universal solution doesn't
appear to be in scope for v2v (if realistic at all); and I'm not sure
that having a very limited solution for a very basic use case only is
better than explicitly telling the user not to rely on v2v for network
configuration.
Roman.