Goals of Ansible support for Fedora Server Edition Roles #194

Closed
opened 2026-04-30 07:37:20 +00:00 by pboy · 4 comments
Owner

According to Fedora Server technical specifications Ansible is the tool to support administration and installation of Fedora Server Edition roles.

Goals

  • We want to support installation, configuration and administration of our supported services ('roles' as defined by our Technical Specification Document) by Ansible.
  • Essentially, we provide ready-to-use Ansible roles for specific Fedora Server roles (like NFS), which would automate the manual setup described in the existing documentation. Both procedures should, in principle, produce the same result. Ansible can also provide additional functionality.
  • Ansible content should easily be customized by sysadmins to conform to their environment and configuration choices and should include hooks that allow an Ansible-savvy administrator to integrate additional tasks.

Implementation principles

  • Wherever possible, existing Ansible roles should be utilized.
  • It may be necessary to develop custom code, e.g. for Fedora-specific services.
  • All Ansible content should be self-contained and self-sufficient. They should not depend on external online resources.

Output items

  • Ansible content comes with user documentation explaining how to use it.
  • A contributor documentation outlines the implementation principles.
  • A user documentation provides guidance for administrators on how to develop Ansible support for their own services. It is aimed at both new and experienced administrators.
  • Ansible content deployed via rpm should conform to Packaging Guidelines (both the general ones and the Ansible-specific ones).
  • Ansible content should be installable either on the administrator's workstation or on a server that can then be used to configure itself and other servers.

Deployment

  • Distribution is to be carried out either via RPM or via download from the Server Ansible repository. (Forgejo supports the provisioning of releases). Details are yet to be decided.
According to [Fedora Server technical specifications](https://docs.fedoraproject.org/en-US/server-working-group/docs/server-technical-specification/) Ansible is the tool to support administration and installation of [Fedora Server Edition roles](https://docs.fedoraproject.org/en-US/server-working-group/docs/server-technical-specification/#_4_server_roles). ### Goals * We want to support installation, configuration and administration of our supported services ('roles' as defined by our [Technical Specification Document](https://docs.fedoraproject.org/en-US/server-working-group/docs/server-technical-specification/#_4_server_roles)) by Ansible. * Essentially, we provide ready-to-use Ansible roles for specific Fedora Server roles (like NFS), which would automate the manual setup described in the existing documentation. Both procedures should, in principle, produce the same result. Ansible can also provide additional functionality. * Ansible content should easily be customized by sysadmins to conform to their environment and configuration choices and should include hooks that allow an Ansible-savvy administrator to integrate additional tasks. ### Implementation principles * Wherever possible, existing Ansible roles should be utilized. * It may be necessary to develop custom code, e.g. for Fedora-specific services. * All Ansible content should be self-contained and self-sufficient. They should not depend on external online resources. ### Output items * Ansible content comes with user documentation explaining how to use it. * A contributor documentation outlines the implementation principles. * A user documentation provides guidance for administrators on how to develop Ansible support for their own services. It is aimed at both new and experienced administrators. * Ansible content deployed via rpm should conform to Packaging Guidelines (both the general ones and the Ansible-specific ones). * Ansible content should be installable either on the administrator's workstation or on a server that can then be used to configure itself and other servers. ### Deployment * Distribution is to be carried out either via RPM or via download from the Server Ansible repository. (Forgejo supports the provisioning of releases). Details are yet to be decided.

Hi! I can help with docs - I can write a beginner-friendly page on how to use these Ansible roles to set up a Fedora Server (install, inventory, basic config, run, and how to customize).

Hi! I can help with docs - I can write a beginner-friendly page on how to use these Ansible roles to set up a Fedora Server (install, inventory, basic config, run, and how to customize).
Author
Owner

@jonashub Thanks a lot. At the moment we are struggling to get the Ansible support we want to achieve getting up and running. Can you also contribute to create support? Not necessarily by developing roles, but by using existing roles for a specific task?

@jonashub Thanks a lot. At the moment we are struggling to get the Ansible support we want to achieve getting up and running. Can you also contribute to create support? Not necessarily by developing roles, but by using existing roles for a specific task?

Absolutely, happy to help! I just want to make sure I understand, do you mean you’d like me to test the support by actually using the existing Ansible roles for specific Fedora Server tasks, and then report back how it goes?

Absolutely, happy to help! I just want to make sure I understand, do you mean you’d like me to test the support by actually using the existing Ansible roles for specific Fedora Server tasks, and then report back how it goes?
Author
Owner

Current status

The goals were agreed upon at our meeting April 29, 2026

**Current status** The goals were agreed upon at our [meeting April 29, 2026](https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-04-29/fedora-server.2026-04-29-17.00.log.html)
pboy closed this issue 2026-05-21 11:47:22 +00:00
Sign in to join this conversation.
No milestone
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
server/tickets#194
No description provided.