4 ms·
I've just watched a presentation [0] linked by someone else in this thread and am quite impressed by the architecture and UX shown. But it seems to me that Coc
by sgeisler 9y ago
I've just watched a presentation [0] linked by someone else in this thread and am quite impressed by the architecture and UX shown.
But it seems to me that Cockpit is more about monitoring and doing ad-hoc changes and not permanent configuration. I base that assumption on the fact that for example there are multiple places where one can configure network interfaces in debian and there is no cli tool or api to persist network configuration created with ip (at least to my knowledge). I can imagine parsing and editing fstab automatically and 100% correctly to be tricky too.
On the other hand enabling or disabling systemd services is permanent by default and there are probably more cli tools that automatically persist changes done through them.
Can anybody more familiar to Cockpit shed some light on the persistence of most of the configuration options?
[0] https://media.ccc.de/v/ASG2017-99-cockpit_a_linux_sysadmin_session_in_your_browser https://media.ccc.de/v/ASG2017-99-cockpit_a_linux_sysadmin_s...
- evol262 9y agoCockpit uses hostnamed, networkmanager, and other services for configuration, not 'ip' or 'hostname'. Everything you can see is persistent.
- sgeisler 9y agoThank you very much for clearing this up. Since I'm not familiar with networkmanager in combination with other config: what happens if I configure some network interface using Cockpit that is already defined in /etc/network/interfaces.d/*? Will it just throw an error or could it bring my system into a broken/undefined state so that it wouldn't be reachable after the next reboot? If the latter is the case it would probably be unwise to install/use Cockpit on an already configured system.
- evol262 9y agoNetworkManager handles the config file management on its own. Debian appears to require a flag to enable this on its own: https://wiki.debian.org/NetworkManager#Enabling_Interface_Management https://wiki.debian.org/NetworkManager#Enabling_Interface_Ma... If it's enabled, networkmanager will parse out the files and present them over dbus, nmcli, etc. Changes with nmcli, gnome-network (which also uses NM), or other tooling will update the config files. The same ones in /etc/network/interfaces.d/ So, hypothetically: auto eth0 iface eth0 inet static address 192.168.40.112 netmask 255.255.255.0 gateway 192.168.40.1 dns-nameservers 8.8.8.8 NM/Cockpit will show all of this information. If you change the address to 192.168.40.113, the config file will be updated (but otherwise unchanged), and the address will change on the running interface. If it's not enabled, Cockpit will not see the interfaces at all.