clustershell, which is what I use is great for administration of large numbers of machines.

In case you are not familiar with that method it is super simple.  You create a policy in PAM/SUDO and SSH key common to all machines, say 6000 of them.

You can then use cluster shell to copy a script to all 6000 machines, and then execute it, say for updating the time and date for example, checking the date time, installing RPMS....etc

You just put what commands associated with the key into what login ID you want to restrict.

But I don't really see a need for something like cockpit and never use it as it is too simplistic, like I am using a Microsoft product.

:-)

On Thu, May 2, 2024 at 3:07 PM John W. Himpel <john@jlhimpel.net> wrote:
All,

I notice that most of our Fedora Server documentation describes using
cockpit and command-line and graphical apps.

While I have no objection to this and I believe it works well for
maintaining a small number of servers and/or services, it is my belief
this becomes quite cumbersome for more than a handful of servers and/or
services.

I have been asked to edit the NFS Server service installation and setup
documentation currently found in the Staging Environment.  The docs
should cover both server side and client side procedures.  I am more
that willing to edit the procedures prescribed in that document.  But I
prefer using ansible to maintain my server environment.  It becomes
permanent documentation (in case I am no longer available) and it
becomes repeatable by only modifying the "environment files" if a
server requires a rebuild.

I am looking for the opinion and experience of the community in
deciding whether or not we should document both types of procedures.

--
_______________________________________________
server mailing list -- server@lists.fedoraproject.org
To unsubscribe send an email to server-leave@lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue