mirror of
https://gitlab.freedesktop.org/NetworkManager/NetworkManager.git
synced 2026-01-11 00:30:23 +01:00
13f6f3a410
Completely refactor the team/JSON handling in libnm's NMSettingTeam and NMSettingTeamPort. - team handling was added as rh#1398925. The goal is to have a more convenient way to set properties than constructing JSON. This requires libnm to implement the hard task of parsing JSON (and exposing well-understood properties) and generating JSON (based on these "artificial" properties). But not only libnm. In particular nmcli and the D-Bus API must make this "simpler" API accessible. - since NMSettingTeam and NMSettingTeamPort are conceptually the same, add "libnm-core/nm-team-utils.h" and NMTeamSetting that tries to handle the similar code side-by-sdie. The setting classes now just delegate for everything to NMTeamSetting. - Previously, there was a very fuzzy understanding of the provided JSON config. Tighten that up, when setting a JSON config it regenerates/parses all other properties and tries to make the best of it. When modifying any abstraction property, the entire JSON config gets regenerated. In particular, don't try to merge existing JSON config with the new fields. If the user uses the abstraction API, then the entire JSON gets replaced. For example note that nm_setting_team_add_link_watcher() would not be reflected in the JSON config (a bug). That only accidentally worked because client would serializing the changed link watcher to GVariant/D-Bus, then NetworkManager would set it via g_object_set(), which would renerate the JSON, and finally persist it to disk. But as far as libnm is concerned, nm_setting_team_add_link_watcher() would bring the settings instance in an inconsistent state where JSON and the link watcher property disagree. Setting any property must immediately update both the JSON and the abstraction API. - when constucting a team setting from D-Bus, we would previously parse both "config" and abstraction properties. That is wrong. Since our settings plugins only support JSON, all information must be present in the JSON config anyway. So, when "config" is present, only the JSON must be parsed. In the best case, the other information is redudant and contributes nothing. In the worse case, they information differs (which might happen if the client version differs from the server version). As the settings plugin only supports JSON, it's wrong to consider redundant, differing information from D-Bus. - we now only convert string to JSON or back when needed. Previously, setting a property resulted in parsing several JSON multiple times (per property). All operations should now scale well and be reasonably efficient. - also the property-changed signals are now handled correctly. Since NMTeamSetting knows the current state of all attributes, it can emit the exact property changed signals for what changed. - we no longer use libjansson to generate the JSON. JSON is supposed to be a machine readable exchange format, hence a major goal is to be easily handled by applications. While parsing JSON is not so trivial, writing a well-known set of values to JSON is. The advantage is that when you build libnm without libjansson support, then we still can convert the artificial properties to JSON. - Requiring libjansson in libnm is a burden, because most of the time it is not needed (as most users don't create team configurations). With this change we only require it to parse the team settings (no longer to write them). It should be reasonably simple to use a more minimalistic JSON parser that is sufficient for us, so that we can get rid of the libjansson dependency (for libnm). This also avoids the pain that we have due to the symbol collision of libjansson and libjson-glib. https://bugzilla.redhat.com/show_bug.cgi?id=1691619 |
||
|---|---|---|
| .. | ||
| devices | ||
| dhcp | ||
| dns | ||
| dnsmasq | ||
| initrd | ||
| ndisc | ||
| platform | ||
| ppp | ||
| settings | ||
| supplicant | ||
| systemd | ||
| tests | ||
| vpn | ||
| main-utils.c | ||
| main-utils.h | ||
| main.c | ||
| meson.build | ||
| NetworkManagerUtils.c | ||
| NetworkManagerUtils.h | ||
| nm-act-request.c | ||
| nm-act-request.h | ||
| nm-active-connection.c | ||
| nm-active-connection.h | ||
| nm-audit-manager.c | ||
| nm-audit-manager.h | ||
| nm-auth-manager.c | ||
| nm-auth-manager.h | ||
| nm-auth-subject.c | ||
| nm-auth-subject.h | ||
| nm-auth-utils.c | ||
| nm-auth-utils.h | ||
| nm-checkpoint-manager.c | ||
| nm-checkpoint-manager.h | ||
| nm-checkpoint.c | ||
| nm-checkpoint.h | ||
| nm-config-data.c | ||
| nm-config-data.h | ||
| nm-config.c | ||
| nm-config.h | ||
| nm-connectivity.c | ||
| nm-connectivity.h | ||
| nm-core-utils.c | ||
| nm-core-utils.h | ||
| nm-dbus-manager.c | ||
| nm-dbus-manager.h | ||
| nm-dbus-object.c | ||
| nm-dbus-object.h | ||
| nm-dbus-utils.c | ||
| nm-dbus-utils.h | ||
| nm-dcb.c | ||
| nm-dcb.h | ||
| nm-dhcp4-config.c | ||
| nm-dhcp4-config.h | ||
| nm-dhcp6-config.c | ||
| nm-dhcp6-config.h | ||
| nm-dispatcher.c | ||
| nm-dispatcher.h | ||
| nm-firewall-manager.c | ||
| nm-firewall-manager.h | ||
| nm-hostname-manager.c | ||
| nm-hostname-manager.h | ||
| nm-iface-helper.c | ||
| nm-ip4-config.c | ||
| nm-ip4-config.h | ||
| nm-ip6-config.c | ||
| nm-ip6-config.h | ||
| nm-keep-alive.c | ||
| nm-keep-alive.h | ||
| nm-logging.c | ||
| nm-logging.h | ||
| nm-manager.c | ||
| nm-manager.h | ||
| nm-netns.c | ||
| nm-netns.h | ||
| nm-pacrunner-manager.c | ||
| nm-pacrunner-manager.h | ||
| nm-policy.c | ||
| nm-policy.h | ||
| nm-proxy-config.c | ||
| nm-proxy-config.h | ||
| nm-rfkill-manager.c | ||
| nm-rfkill-manager.h | ||
| nm-session-monitor.c | ||
| nm-session-monitor.h | ||
| nm-sleep-monitor.c | ||
| nm-sleep-monitor.h | ||
| nm-test-utils-core.h | ||
| nm-types.h | ||
| org.freedesktop.NetworkManager.conf | ||