Am 24.06.2013 13:08, schrieb Matthew Miller:
On Mon, Jun 24, 2013 at 11:15:11AM +0930, Glen Turner wrote:
> Sun's tagline of "the network is the computer" was true. But for
servers
> these days "the computer is the network" is also the case. It's
nothing
> for a server today to statically NAT or bridge IPv4 to VMs. Even in that
> case it's best if the guest VM picks up its IPv4 addressing using DHCP.
>
> But in the future we'll want to do better than that: to move network
> routing onto the server itself. These new "data centre ethernet" protocols
> are not entirely implemented in kernel space. Some run quite complex BGP
> and MPLS control planes; others run IS-IS control planes.
So, the converse is that as actual workloads move to VMs (let alone cloud),
the host systems become a special case, and the "normal" case for a server
tends to become much more simple: either a single interface probably with
fixed-address DHCP, or in most complicated cases several interfaces on
specific networks known by convention
yes, and all these setups are more than satisfied with network.service
and do not need more complexity with a running daemon like NM
they are also not affected from the interface-renamings and race-conditions
which are the reson for biosdevname and the new systemd-replacement because
typically in a VM you have even with multiple interfaces the same NIC type
and driver