[PATCH 0/2] NM management detection
From: Ondrej Lichtner <olichtne(a)redhat.com>
These two patches add support for detecting if a device is managed by NM. This
is useful for combining the two approaches lnst can use for configuration. The
functionality for mixed configuration was already there, but it wouldn't work
because lnst would try to use NM for both managed and not managed devices. Now
the mixed configuration should work.
It is important to note that it is impossible to have several devices in a
master-slave relationship where some of them are configured by NM and some in
the traditional way. In these cases LNST will throw an exception and stop the
test execution.
This is a bit impractical because the controller can't detect which interfaces
are managed when it's matching the recipe topology against what the pool offers,
so fixing this exception will require manual intervention from the user. But
since this is a corner case of a corner case the user should probably know what
he's doing when this occurs.
Other than this restriction lnst should be able to mix configration of sepparate
eth interfaces (without a master), and groups of interfaces (in a master-slave
relationship) which are all configured in the same way.
Ondrej Lichtner (2):
NmConfigDevice: add NM management check functions
Slave: use function is_nm_managed
lnst/Slave/NetConfig.py | 2 +-
lnst/Slave/NetConfigDevice.py | 17 ++++---
lnst/Slave/NetTestSlave.py | 6 ++-
lnst/Slave/NmConfigDevice.py | 101 +++++++++++++++++++++++++++++++++++++++++-
4 files changed, 114 insertions(+), 12 deletions(-)
--
1.8.3.1