On Wed, Nov 25, 2020 at 10:33 AM Imobach González Sosa wrote:

Hi all,

If you are into systems management, you most likely have heard about Cockpit[1]. In a nutshell, it offers a good looking web-based interface to perform system tasks, like inspecting the logs, applying system updates, configuring the network, managing services, and so on.

Recently, the YaST team got informed that MicroOS developers wanted to offer Cockpit as an option for system management tasks. Unfortunately, Cockpit does not have support for Wicked[2], a network configuration framework included in SUSE-based distributions. So we were given the task of solving that problem.

Today we are announcing the first public release of such a module[3]. You can read the full announcement in our blog[4].

Bear in mind that it is still a work in progress (actually, there is a silly UI bug with routes handling that we are fixing now), but some basic use cases are already supported and we would love to get from feedback from you.

Is there a reason that the built-in network module using NetworkManager wouldn't work? There seems to be a fair bit of work in upstream projects (Cockpit, nmstate, netplan, etc.) in integrating around NetworkManager. -- 真実はいつも一つ！/ Always, there's only one truth!

On Wed, Nov 25, 2020 at 11:29 AM Imobach González Sosa wrote:

El miércoles, 25 de noviembre de 2020 16:19:04 (WET) usted escribió:

...

On Wed, Nov 25, 2020 at 10:33 AM Imobach González Sosa

wrote:

...

Hi all,

If you are into systems management, you most likely have heard about Cockpit[1]. In a nutshell, it offers a good looking web-based interface to perform system tasks, like inspecting the logs, applying system updates, configuring the network, managing services, and so on.

Recently, the YaST team got informed that MicroOS developers wanted to offer Cockpit as an option for system management tasks. Unfortunately, Cockpit does not have support for Wicked[2], a network configuration framework included in SUSE-based distributions. So we were given the task of solving that problem.

Today we are announcing the first public release of such a module[3]. You can read the full announcement in our blog[4].

Bear in mind that it is still a work in progress (actually, there is a silly UI bug with routes handling that we are fixing now), but some basic use cases are already supported and we would love to get from feedback from you. Is there a reason that the built-in network module using NetworkManager wouldn't work? There seems to be a fair bit of work in upstream projects (Cockpit, nmstate, netplan, etc.) in integrating around NetworkManager.

Hi Neal,

I am not sure whether I got your question. Basically Wicked does not work at this point with any of those tools (nmstate, netplan and so on). AFAIK, they are aware of such efforts but they have not done any integration work yet. So, if for some reason you are using Wicked, the original module will not work.

If you are using NetworkManager (by default in openSUSE), then you are fine with the stock module.

My confusion is that the implication of this module's existence is that we're not using NetworkManager and thus networking is busted in Cockpit. Hence the question. -- 真実はいつも一つ！/ Always, there's only one truth!

On 11/26/20 3:15 AM, Imobach González Sosa wrote:

El miércoles, 25 de noviembre de 2020 16:30:54 (WET) usted escribió:

...

On Wed, Nov 25, 2020 at 11:29 AM Imobach González Sosa

wrote:

...

El miércoles, 25 de noviembre de 2020 16:19:04 (WET) usted escribió:

...

On Wed, Nov 25, 2020 at 10:33 AM Imobach González Sosa

wrote:

...

Hi all,

If you are into systems management, you most likely have heard about Cockpit[1]. In a nutshell, it offers a good looking web-based interface to perform system tasks, like inspecting the logs, applying system updates, configuring the network, managing services, and so on.

Recently, the YaST team got informed that MicroOS developers wanted to offer Cockpit as an option for system management tasks. Unfortunately, Cockpit does not have support for Wicked[2], a network configuration framework included in SUSE-based distributions. So we were given the task of solving that problem.

Today we are announcing the first public release of such a module[3]. You can read the full announcement in our blog[4].

Bear in mind that it is still a work in progress (actually, there is a silly UI bug with routes handling that we are fixing now), but some basic use cases are already supported and we would love to get from feedback from you.

Is there a reason that the built-in network module using NetworkManager wouldn't work? There seems to be a fair bit of work in upstream projects (Cockpit, nmstate, netplan, etc.) in integrating around NetworkManager.

Hi Neal,

I am not sure whether I got your question. Basically Wicked does not work at this point with any of those tools (nmstate, netplan and so on). AFAIK, they are aware of such efforts but they have not done any integration work yet. So, if for some reason you are using Wicked, the original module will not work.

If you are using NetworkManager (by default in openSUSE), then you are fine with the stock module.

My confusion is that the implication of this module's existence is that we're not using NetworkManager and thus networking is busted in Cockpit. Hence the question.

Hi,

OK, I understand. This module is only relevant if you are using Wicked (thus, you are not using NetworkManager). I would expect that the vast majority of openSUSE users are running NetworkManager.

When I last checked the openSUSE installer still defaulted to wicked rather then NetworkMangager for any non Gnome / KDE / XFCE installs so there is a reasonable chance that many people interested in a webui for configuring a "Remote" system are still running wicked. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B