diff --git a/README.md b/README.md index 7b64cbc..afa3b67 100644 --- a/README.md +++ b/README.md @@ -1,24 +1,89 @@ -# Fedora-server repository +# Fedora Server Edition User Documentation -This repository is used by [Server working group]( http://fedoraproject.org/wiki/Server). +This repository contains the sources for the Fedora Server Documentation. -### It currently contains: +## Contributing to this documentation -* Docs directory for documentation. -* Tickets (issues) for the Server group. +Steps to do to contribute to the documentation: -### Basic instructions on how to contribute to this repository +Fork this repository, so you are not pushing updates directly into the main branch. -[Git for docs writers](https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/contributions-quick-repo/) +Start adding the actual ASCIIDoc content. While writing, make sure your new source files are included in the nav.adoc configuration file of the module you are using (./modules/ROOT/ ). +Also make sure to use local preview often to check your markup. -Note: Replace master with main on all occations on above document: +Once you finish, commit your changes and push them to your fork. -* For example: instead of -`git checkout master` use `git checkout main` +Use forge to make a pull request from your fork to the repository’s main branch. -### Previewing docs: +Someone will see your pull request and either merge it, or provide feedback if there is something you should change. Work with the people commenting to make sure your contributions are up to standards. -To build and preview docs, run: +## The overall documentation structure + +``` +|-- README.md +|-- antora.yml ....................... 1. +|-- docsbuilder.sh ................... 2. +|-- LICENSE ......................... 3. +|-- nginx.conf ....................... 4. +|-- site.yml ......................... 5. +`-- modules + `-- ROOT/ ........................ 6. + |-- assets + | |-- attachments/ ......... 7. + | `-- images/ .............. 8. + |-- nav.adoc ................. 9. + |-- pages ................... 10. + | |-- index.adoc + | |-- administration/ + | | |-- index.adoc + | | `-- ......adoc + | |-- containerization/ + | | |-- index.adoc + | | `-- ......adoc + | |-- installation/ + | | |-- index.adoc + | | `-- ......adoc + | |-- services/ + | | |-- index.adoc + | | `-- ......adoc + | |-- tutorials/ + | | |-- index.adoc + | | `-- ......adoc + | `-- somedir/ + | |-- index.adoc + | `-- ......adoc + | + `-- partials/ .................11. + +``` +1. Metadata definition. +2. A script that does a local build. It shows a preview of the site in a web browser on localhost:8080 by running a local web server. Uses podman/docker. +3. Licence information for the documentation. +4. Configuration for the local web server mentioned above. +5. A definition file for the build script. +6. A "root module of this documentation component". Please read below for an explanation. +7. Directory containing **attachments** to be used on any page. +8. Directory containing **Iiages** to be used on any page. +9. **Menu definition.** Also defines the hierarchy of all the pages. +10. **Pages with the actual content.** They are organised into subdirectories for specific area of information. +11. Snippets of adoc files reusable in various documentations, organised into subdirectories for specific area of information. + +## Components and Modules + +Antora introduces two new terms: + +* **Component** — Simply put, a component is a part of the documentation website with its own menu. Components can also be versioned. In the Fedora Docs, we use separate components for user documentation, the Fedora Project, Fedora council, Mindshare, FESCO, but also for subprojects such as CommOps or Modulartity. +* **Module** — A component can be broken down into multiple modules. Modules still share a single menu on the site, but their sources can be stored in different git repositories, even owned by different groups. The default module is called "ROOT" (that's what is in this example). If you don't want to use multiple modules, only use "ROOT". But to define more modules, simply duplicate the "ROOT" directory and name it anything you want. You can store modules in one or more git repositories. + +## Local preview + +This repo includes a script to build and preview the contents of this repository. + +**NOTE**: Please note that if you reference pages from other repositories, such links will be broken in this local preview as it only builds this repository. If you want to rebuild the whole Fedora Docs site, please see [the Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o/) for instructions. + +The script works on Fedora (using Podman) and macOS (using Docker). + +To build and preview the site, run: ``` $ ./docsbuilder.sh @@ -26,6 +91,65 @@ $ ./docsbuilder.sh The result will be available at http://localhost:8080 +### Installing Podman on Fedora +Newer Fedora Workstations comes with Podman preinstalled by default — if you do not have it, you need to install it using the following command: +``` +$ sudo dnf install podman +``` +### Preview as a part of the whole Fedora Docs site + +You can also build the whole Fedora Docs site locally to see your changes in the whole context. +This is especially useful for checking if your `xref` links work properly. + +To do this, you need to clone the main [Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o), modify the `site.yml` file to reference a repo with your changes, and build it. +Steps: + +Clone the main repository and cd into it: + +``` +$ git clone https://pagure.io/fedora-docs/docs-fp-o.git +$ cd docs-fp-o +``` + +Find a reference to the repository you're changing in the `site.yml` file, and change it so it points to your change. +So for example, if I made a modification to the Modularity docs, I would find: + +``` +... + - url: https://pagure.io/fedora-docs/modularity.git + branches: + - master +... +``` + +And replaced it with a pointer to my fork: +``` +... + - url: https://pagure.io/forks/asamalik/fedora-docs/modularity.git + branches: + - master +... +``` + +I could also point to a local repository, using `HEAD` as a branch to preview the what's changed without the need of making a commit. + +**Note:** I would need to move the repository under the `docs-fp-o` directory, because the builder won't see anything above. +So I would need to create a `repositories` directory in `docs-fp-o` and copy my repository into it. + +``` +... + - url: ./repositories/modularity + branches: + - HEAD +... +``` + +To build the whole site, I would run the following in the `docs-fp-o` directory. + +``` +$ ./docsbuilder.sh +``` +For more information see [Git for docs writers](https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/contributions-quick-repo/) diff --git a/docs/antora.yml b/antora.yml similarity index 93% rename from docs/antora.yml rename to antora.yml index e47d647..e26efdc 100644 --- a/docs/antora.yml +++ b/antora.yml @@ -5,12 +5,12 @@ name: fedora-server # Title will be visible on the page. -title: Fedora Server Documentation +title: Fedora Server User Documentation # If you don't plan to have multiple versions of the docs (for example, to # document multiple versions of some software), you can ignore this field. # Otherwise, change "master" to a specific version. -version: master +version: main # We encourage you to name the index page as "index.adoc". If you absolutely # have to use a different name, please reflect it here. You can ignore this diff --git a/docs/README.md b/docs/README.md deleted file mode 100644 index b121585..0000000 --- a/docs/README.md +++ /dev/null @@ -1,140 +0,0 @@ -# Fedora Server Documentation - -This directory contains the sources for the Fedora Server Documentation. - -## Contributing to this documentation - -Steps to do to contribute to the documentation: - -Fork this repository, so you are not pushing updates directly into the main branch. - -Start adding the actual ASCIIDoc content. While writing, make sure your new source files are included in the nav.adoc configuration file of the module you are using (./modules/ROOT/ ). -Also make sure to use local preview often to check your markup. - -Once you finish, commit your changes and push them to your fork. - -Use Pagure to make a pull request from your fork to the repository’s main branch. - -Someone will see your pull request and either merge it, or provide feedback if there is something you should change. Work with the people commenting to make sure your contributions are up to standards. - -## This step needs to be done only once when first version of the site is finished. -Your new content will need to be published for the first time, and at the moment this does not happen automatically. Send an e-mail to the docs mailing list asking for your content to be published. - -The information below is on contributing to this repository (Taken from https://pagure.io/fedora-docs/template) - -## Structure - -``` -|-- README.md -|-- antora.yml ....................... 1. -|-- build.sh ......................... 2. -|-- preview.sh ....................... 3. -|-- site.yml ......................... 4. -`-- modules - `-- ROOT ......................... 5. - |-- assets - | `-- images ............... 6. - | `-- pizza.png - |-- nav.adoc ................. 7. - `-- pages .................... 8. - |-- architecture.adoc - |-- community.adoc - |-- faq.adoc - |-- index.adoc - |-- pizza-dough.adoc - `-- pizza-oven.adoc -``` - -1. Metadata definition. -2. A script that does a local build. Uses podman/docker. -3. A script that shows a preview of the site in a web browser by running a local web server. Uses podman/docker. -4. A definition file for the build script. -5. A "root module of this documentation component". Please read below for an explanation. -6. **Images** to be used on any page. -7. **Menu definition.** Also defines the hierarchy of all the pages. -8. **Pages with the actual content.** They can be also organised into subdirectories if desired. - -## Components and Modules - -Antora introduces two new terms: - -* **Component** — Simply put, a component is a part of the documentation website with its own menu. Components can also be versioned. In the Fedora Docs, we use separate components for user documentation, the Fedora Project, Fedora council, Mindshare, FESCO, but also for subprojects such as CommOps or Modulartity. -* **Module** — A component can be broken down into multiple modules. Modules still share a single menu on the site, but their sources can be stored in different git repositories, even owned by different groups. The default module is called "ROOT" (that's what is in this example). If you don't want to use multiple modules, only use "ROOT". But to define more modules, simply duplicate the "ROOT" directory and name it anything you want. You can store modules in one or more git repositories. - -## Local preview - -This repo includes scripts to build and preview the contents of this repository. - -**NOTE**: Please note that if you reference pages from other repositories, such links will be broken in this local preview as it only builds this repository. If you want to rebuild the whole Fedora Docs site, please see [the Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o/) for instructions. - -Both scripts work on Fedora (using Podman) and macOS (using Docker). - -To build and preview the site, run: - -``` -$ ./build.sh && ./preview.sh -``` - -The result will be available at http://localhost:8080 - -### Installing Podman on Fedora - -Newer Fedora Workstations comes with Podman preinstalled by default — if you do not have it, you need to install it using the following command: - -``` -$ sudo dnf install podman -``` - -### Preview as a part of the whole Fedora Docs site - -You can also build the whole Fedora Docs site locally to see your changes in the whole context. -This is especially useful for checking if your `xref` links work properly. - -To do this, you need to clone the main [Fedora Docs build repository](https://pagure.io/fedora-docs/docs-fp-o), modify the `site.yml` file to reference a repo with your changes, and build it. -Steps: - -Clone the main repository and cd into it: - -``` -$ git clone https://pagure.io/fedora-docs/docs-fp-o.git -$ cd docs-fp-o -``` - -Find a reference to the repository you're changing in the `site.yml` file, and change it so it points to your change. -So for example, if I made a modification to the Modularity docs, I would find: - -``` -... - - url: https://pagure.io/fedora-docs/modularity.git - branches: - - master -... -``` - -And replaced it with a pointer to my fork: -``` -... - - url: https://pagure.io/forks/asamalik/fedora-docs/modularity.git - branches: - - master -... -``` - -I could also point to a local repository, using `HEAD` as a branch to preview the what's changed without the need of making a commit. - -**Note:** I would need to move the repository under the `docs-fp-o` directory, because the builder won't see anything above. -So I would need to create a `repositories` directory in `docs-fp-o` and copy my repository into it. - -``` -... - - url: ./repositories/modularity - branches: - - HEAD -... -``` - -To build the whole site, I would run the following in the `docs-fp-o` directory. - -``` -$ ./build.sh && ./preview.sh -``` diff --git a/fedora-ansible/README.md b/fedora-ansible/README.md deleted file mode 100644 index 3e2dbac..0000000 --- a/fedora-ansible/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# fedora-ansible - -This directory contains Ansible scripts and documentation for Fedora Server Edition supported services. diff --git a/fedora-ansible/docs/README.md b/fedora-ansible/docs/README.md deleted file mode 100644 index f29bf66..0000000 --- a/fedora-ansible/docs/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# fedora-ansible/docs - -This directory contains documentation about Ansible for Fedora Server Edition supported services. diff --git a/fedora-ansible/files/README.md b/fedora-ansible/files/README.md deleted file mode 100644 index 9d65253..0000000 --- a/fedora-ansible/files/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# fedora-ansible/files - -This directory contains files for Fedora Server Edition supported services. diff --git a/fedora-ansible/roles/README.md b/fedora-ansible/roles/README.md deleted file mode 100644 index 210fc24..0000000 --- a/fedora-ansible/roles/README.md +++ /dev/null @@ -1,3 +0,0 @@ -# fedora-ansible/roles - -This directory contains Ansible roles for Fedora Server Edition supported services. diff --git a/docs/modules/ROOT/assets/attachments/nspawn-autostart-libvirt-hook.tgz b/modules/ROOT/assets/attachments/nspawn-autostart-libvirt-hook.tgz similarity index 100% rename from docs/modules/ROOT/assets/attachments/nspawn-autostart-libvirt-hook.tgz rename to modules/ROOT/assets/attachments/nspawn-autostart-libvirt-hook.tgz diff --git a/docs/modules/ROOT/assets/attachments/services/httpd-basic-setup/zvhost-static-html.template b/modules/ROOT/assets/attachments/services/httpd-basic-setup/zvhost-static-html.template similarity index 100% rename from docs/modules/ROOT/assets/attachments/services/httpd-basic-setup/zvhost-static-html.template rename to modules/ROOT/assets/attachments/services/httpd-basic-setup/zvhost-static-html.template diff --git a/docs/modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.ks b/modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.ks similarity index 100% rename from docs/modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.ks rename to modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.ks diff --git a/docs/modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.tdl b/modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.tdl similarity index 100% rename from docs/modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.tdl rename to modules/ROOT/assets/attachments/tutorials/imagefactory/fedora-server-kvm-dev.tdl diff --git a/docs/modules/ROOT/assets/images/.DS_Store b/modules/ROOT/assets/images/.DS_Store similarity index 100% rename from docs/modules/ROOT/assets/images/.DS_Store rename to modules/ROOT/assets/images/.DS_Store diff --git a/docs/modules/ROOT/assets/images/Logo_server.png b/modules/ROOT/assets/images/Logo_server.png similarity index 100% rename from docs/modules/ROOT/assets/images/Logo_server.png rename to modules/ROOT/assets/images/Logo_server.png diff --git a/docs/modules/ROOT/assets/images/Logo_server2.png b/modules/ROOT/assets/images/Logo_server2.png similarity index 100% rename from docs/modules/ROOT/assets/images/Logo_server2.png rename to modules/ROOT/assets/images/Logo_server2.png diff --git a/docs/modules/ROOT/assets/images/installation/grub-boot-screen-f40.png b/modules/ROOT/assets/images/installation/grub-boot-screen-f40.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/grub-boot-screen-f40.png rename to modules/ROOT/assets/images/installation/grub-boot-screen-f40.png diff --git a/docs/modules/ROOT/assets/images/installation/grub-boot-screen-f41.png b/modules/ROOT/assets/images/installation/grub-boot-screen-f41.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/grub-boot-screen-f41.png rename to modules/ROOT/assets/images/installation/grub-boot-screen-f41.png diff --git a/docs/modules/ROOT/assets/images/installation/grub-boot-screen.png b/modules/ROOT/assets/images/installation/grub-boot-screen.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/grub-boot-screen.png rename to modules/ROOT/assets/images/installation/grub-boot-screen.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-local-010.png b/modules/ROOT/assets/images/installation/interactive-local-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-local-010.png rename to modules/ROOT/assets/images/installation/interactive-local-010.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-local-015.png b/modules/ROOT/assets/images/installation/interactive-local-015.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-local-015.png rename to modules/ROOT/assets/images/installation/interactive-local-015.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-local-020-f40.png b/modules/ROOT/assets/images/installation/interactive-local-020-f40.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-local-020-f40.png rename to modules/ROOT/assets/images/installation/interactive-local-020-f40.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-local-020.png b/modules/ROOT/assets/images/installation/interactive-local-020.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-local-020.png rename to modules/ROOT/assets/images/installation/interactive-local-020.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-local-050.png b/modules/ROOT/assets/images/installation/interactive-local-050.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-local-050.png rename to modules/ROOT/assets/images/installation/interactive-local-050.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-local-070.png b/modules/ROOT/assets/images/installation/interactive-local-070.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-local-070.png rename to modules/ROOT/assets/images/installation/interactive-local-070.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-remote-010.png b/modules/ROOT/assets/images/installation/interactive-remote-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-remote-010.png rename to modules/ROOT/assets/images/installation/interactive-remote-010.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-remote-015.png b/modules/ROOT/assets/images/installation/interactive-remote-015.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-remote-015.png rename to modules/ROOT/assets/images/installation/interactive-remote-015.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-summaryscreen-f40.png b/modules/ROOT/assets/images/installation/interactive-summaryscreen-f40.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-summaryscreen-f40.png rename to modules/ROOT/assets/images/installation/interactive-summaryscreen-f40.png diff --git a/docs/modules/ROOT/assets/images/installation/interactive-summaryscreen.png b/modules/ROOT/assets/images/installation/interactive-summaryscreen.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/interactive-summaryscreen.png rename to modules/ROOT/assets/images/installation/interactive-summaryscreen.png diff --git a/docs/modules/ROOT/assets/images/installation/on-sbc-020.png b/modules/ROOT/assets/images/installation/on-sbc-020.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/on-sbc-020.png rename to modules/ROOT/assets/images/installation/on-sbc-020.png diff --git a/docs/modules/ROOT/assets/images/installation/on-sbc-030.png b/modules/ROOT/assets/images/installation/on-sbc-030.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/on-sbc-030.png rename to modules/ROOT/assets/images/installation/on-sbc-030.png diff --git a/docs/modules/ROOT/assets/images/installation/on-sbc-060.png b/modules/ROOT/assets/images/installation/on-sbc-060.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/on-sbc-060.png rename to modules/ROOT/assets/images/installation/on-sbc-060.png diff --git a/docs/modules/ROOT/assets/images/installation/on-sbc-090.png b/modules/ROOT/assets/images/installation/on-sbc-090.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/on-sbc-090.png rename to modules/ROOT/assets/images/installation/on-sbc-090.png diff --git a/docs/modules/ROOT/assets/images/installation/on-sbc-100.png b/modules/ROOT/assets/images/installation/on-sbc-100.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/on-sbc-100.png rename to modules/ROOT/assets/images/installation/on-sbc-100.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/.DS_Store b/modules/ROOT/assets/images/installation/sw-raid/.DS_Store similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/.DS_Store rename to modules/ROOT/assets/images/installation/sw-raid/.DS_Store diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/001-installationdestination.png b/modules/ROOT/assets/images/installation/sw-raid/001-installationdestination.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/001-installationdestination.png rename to modules/ROOT/assets/images/installation/sw-raid/001-installationdestination.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/101-custom-start.png b/modules/ROOT/assets/images/installation/sw-raid/101-custom-start.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/101-custom-start.png rename to modules/ROOT/assets/images/installation/sw-raid/101-custom-start.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/105-custom-biosboot-1.png b/modules/ROOT/assets/images/installation/sw-raid/105-custom-biosboot-1.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/105-custom-biosboot-1.png rename to modules/ROOT/assets/images/installation/sw-raid/105-custom-biosboot-1.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/110-custom-biosboot-2.png b/modules/ROOT/assets/images/installation/sw-raid/110-custom-biosboot-2.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/110-custom-biosboot-2.png rename to modules/ROOT/assets/images/installation/sw-raid/110-custom-biosboot-2.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/120-custom-efi-1.png b/modules/ROOT/assets/images/installation/sw-raid/120-custom-efi-1.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/120-custom-efi-1.png rename to modules/ROOT/assets/images/installation/sw-raid/120-custom-efi-1.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/125-custom-efi-2.png b/modules/ROOT/assets/images/installation/sw-raid/125-custom-efi-2.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/125-custom-efi-2.png rename to modules/ROOT/assets/images/installation/sw-raid/125-custom-efi-2.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/130-custom-finalbootform.png b/modules/ROOT/assets/images/installation/sw-raid/130-custom-finalbootform.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/130-custom-finalbootform.png rename to modules/ROOT/assets/images/installation/sw-raid/130-custom-finalbootform.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/140-custom-generated-root.png b/modules/ROOT/assets/images/installation/sw-raid/140-custom-generated-root.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/140-custom-generated-root.png rename to modules/ROOT/assets/images/installation/sw-raid/140-custom-generated-root.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/145-custom-lvm-properties.png b/modules/ROOT/assets/images/installation/sw-raid/145-custom-lvm-properties.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/145-custom-lvm-properties.png rename to modules/ROOT/assets/images/installation/sw-raid/145-custom-lvm-properties.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/201-adv-custom-start.png b/modules/ROOT/assets/images/installation/sw-raid/201-adv-custom-start.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/201-adv-custom-start.png rename to modules/ROOT/assets/images/installation/sw-raid/201-adv-custom-start.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/205-adv-custom-biosboot.png b/modules/ROOT/assets/images/installation/sw-raid/205-adv-custom-biosboot.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/205-adv-custom-biosboot.png rename to modules/ROOT/assets/images/installation/sw-raid/205-adv-custom-biosboot.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/210-adv-custom-uefi.png b/modules/ROOT/assets/images/installation/sw-raid/210-adv-custom-uefi.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/210-adv-custom-uefi.png rename to modules/ROOT/assets/images/installation/sw-raid/210-adv-custom-uefi.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/212-adv-custom-uefilist.png b/modules/ROOT/assets/images/installation/sw-raid/212-adv-custom-uefilist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/212-adv-custom-uefilist.png rename to modules/ROOT/assets/images/installation/sw-raid/212-adv-custom-uefilist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/215-adv-custom-boot.png b/modules/ROOT/assets/images/installation/sw-raid/215-adv-custom-boot.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/215-adv-custom-boot.png rename to modules/ROOT/assets/images/installation/sw-raid/215-adv-custom-boot.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/217-adv-custom-bootlist.png b/modules/ROOT/assets/images/installation/sw-raid/217-adv-custom-bootlist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/217-adv-custom-bootlist.png rename to modules/ROOT/assets/images/installation/sw-raid/217-adv-custom-bootlist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/220-adv-custom-syspv.png b/modules/ROOT/assets/images/installation/sw-raid/220-adv-custom-syspv.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/220-adv-custom-syspv.png rename to modules/ROOT/assets/images/installation/sw-raid/220-adv-custom-syspv.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/222-adv-custom-syspvlist.png b/modules/ROOT/assets/images/installation/sw-raid/222-adv-custom-syspvlist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/222-adv-custom-syspvlist.png rename to modules/ROOT/assets/images/installation/sw-raid/222-adv-custom-syspvlist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/224-adv-custom-sysvgform.png b/modules/ROOT/assets/images/installation/sw-raid/224-adv-custom-sysvgform.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/224-adv-custom-sysvgform.png rename to modules/ROOT/assets/images/installation/sw-raid/224-adv-custom-sysvgform.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/226-adv-custom-sysgvlist.png b/modules/ROOT/assets/images/installation/sw-raid/226-adv-custom-sysgvlist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/226-adv-custom-sysgvlist.png rename to modules/ROOT/assets/images/installation/sw-raid/226-adv-custom-sysgvlist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/230-adv-custom-usrpv.png b/modules/ROOT/assets/images/installation/sw-raid/230-adv-custom-usrpv.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/230-adv-custom-usrpv.png rename to modules/ROOT/assets/images/installation/sw-raid/230-adv-custom-usrpv.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/234-adv-custom-usrvg.png b/modules/ROOT/assets/images/installation/sw-raid/234-adv-custom-usrvg.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/234-adv-custom-usrvg.png rename to modules/ROOT/assets/images/installation/sw-raid/234-adv-custom-usrvg.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/236-adv-custom-usrvglist.png b/modules/ROOT/assets/images/installation/sw-raid/236-adv-custom-usrvglist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/236-adv-custom-usrvglist.png rename to modules/ROOT/assets/images/installation/sw-raid/236-adv-custom-usrvglist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/240-adv-custom-rootfsform.png b/modules/ROOT/assets/images/installation/sw-raid/240-adv-custom-rootfsform.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/240-adv-custom-rootfsform.png rename to modules/ROOT/assets/images/installation/sw-raid/240-adv-custom-rootfsform.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/244-adv-custom-rootfslist.png b/modules/ROOT/assets/images/installation/sw-raid/244-adv-custom-rootfslist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/244-adv-custom-rootfslist.png rename to modules/ROOT/assets/images/installation/sw-raid/244-adv-custom-rootfslist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/250-adv-custom-varlogform.png b/modules/ROOT/assets/images/installation/sw-raid/250-adv-custom-varlogform.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/250-adv-custom-varlogform.png rename to modules/ROOT/assets/images/installation/sw-raid/250-adv-custom-varlogform.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/254-adv-custom-varloglist.png b/modules/ROOT/assets/images/installation/sw-raid/254-adv-custom-varloglist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/254-adv-custom-varloglist.png rename to modules/ROOT/assets/images/installation/sw-raid/254-adv-custom-varloglist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/260-adv-custom-usrhomeform.png b/modules/ROOT/assets/images/installation/sw-raid/260-adv-custom-usrhomeform.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/260-adv-custom-usrhomeform.png rename to modules/ROOT/assets/images/installation/sw-raid/260-adv-custom-usrhomeform.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/264-adv-custom-usrhomelist.png b/modules/ROOT/assets/images/installation/sw-raid/264-adv-custom-usrhomelist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/264-adv-custom-usrhomelist.png rename to modules/ROOT/assets/images/installation/sw-raid/264-adv-custom-usrhomelist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/270-adv-custom-srvform.png b/modules/ROOT/assets/images/installation/sw-raid/270-adv-custom-srvform.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/270-adv-custom-srvform.png rename to modules/ROOT/assets/images/installation/sw-raid/270-adv-custom-srvform.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/274-adv-custom-srvlist.png b/modules/ROOT/assets/images/installation/sw-raid/274-adv-custom-srvlist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/274-adv-custom-srvlist.png rename to modules/ROOT/assets/images/installation/sw-raid/274-adv-custom-srvlist.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/280-adv-libvirtform.png b/modules/ROOT/assets/images/installation/sw-raid/280-adv-libvirtform.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/280-adv-libvirtform.png rename to modules/ROOT/assets/images/installation/sw-raid/280-adv-libvirtform.png diff --git a/docs/modules/ROOT/assets/images/installation/sw-raid/284-adv-custom-libvirtlist.png b/modules/ROOT/assets/images/installation/sw-raid/284-adv-custom-libvirtlist.png similarity index 100% rename from docs/modules/ROOT/assets/images/installation/sw-raid/284-adv-custom-libvirtlist.png rename to modules/ROOT/assets/images/installation/sw-raid/284-adv-custom-libvirtlist.png diff --git a/docs/modules/ROOT/assets/images/penguin.jpg b/modules/ROOT/assets/images/penguin.jpg similarity index 100% rename from docs/modules/ROOT/assets/images/penguin.jpg rename to modules/ROOT/assets/images/penguin.jpg diff --git a/docs/modules/ROOT/assets/images/serverinstall-sbc-020.png b/modules/ROOT/assets/images/serverinstall-sbc-020.png similarity index 100% rename from docs/modules/ROOT/assets/images/serverinstall-sbc-020.png rename to modules/ROOT/assets/images/serverinstall-sbc-020.png diff --git a/docs/modules/ROOT/assets/images/serverinstall-sbc-030.png b/modules/ROOT/assets/images/serverinstall-sbc-030.png similarity index 100% rename from docs/modules/ROOT/assets/images/serverinstall-sbc-030.png rename to modules/ROOT/assets/images/serverinstall-sbc-030.png diff --git a/docs/modules/ROOT/assets/images/serverinstall-sbc-060.png b/modules/ROOT/assets/images/serverinstall-sbc-060.png similarity index 100% rename from docs/modules/ROOT/assets/images/serverinstall-sbc-060.png rename to modules/ROOT/assets/images/serverinstall-sbc-060.png diff --git a/docs/modules/ROOT/assets/images/serverinstall-sbc-090.png b/modules/ROOT/assets/images/serverinstall-sbc-090.png similarity index 100% rename from docs/modules/ROOT/assets/images/serverinstall-sbc-090.png rename to modules/ROOT/assets/images/serverinstall-sbc-090.png diff --git a/docs/modules/ROOT/assets/images/serverinstall-sbc-100.png b/modules/ROOT/assets/images/serverinstall-sbc-100.png similarity index 100% rename from docs/modules/ROOT/assets/images/serverinstall-sbc-100.png rename to modules/ROOT/assets/images/serverinstall-sbc-100.png diff --git a/docs/modules/ROOT/assets/images/services/httpd-basic-setup-030.png b/modules/ROOT/assets/images/services/httpd-basic-setup-030.png similarity index 100% rename from docs/modules/ROOT/assets/images/services/httpd-basic-setup-030.png rename to modules/ROOT/assets/images/services/httpd-basic-setup-030.png diff --git a/docs/modules/ROOT/assets/images/services/nfs-server-inst-001.png b/modules/ROOT/assets/images/services/nfs-server-inst-001.png similarity index 100% rename from docs/modules/ROOT/assets/images/services/nfs-server-inst-001.png rename to modules/ROOT/assets/images/services/nfs-server-inst-001.png diff --git a/docs/modules/ROOT/assets/images/services/nfs-server-inst-005.png b/modules/ROOT/assets/images/services/nfs-server-inst-005.png similarity index 100% rename from docs/modules/ROOT/assets/images/services/nfs-server-inst-005.png rename to modules/ROOT/assets/images/services/nfs-server-inst-005.png diff --git a/docs/modules/ROOT/assets/images/services/nfs-server-inst-009.png b/modules/ROOT/assets/images/services/nfs-server-inst-009.png similarity index 100% rename from docs/modules/ROOT/assets/images/services/nfs-server-inst-009.png rename to modules/ROOT/assets/images/services/nfs-server-inst-009.png diff --git a/docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/030-create-thinpool-en.png b/modules/ROOT/assets/images/tutorials/imagefactory-kvm/030-create-thinpool-en.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/030-create-thinpool-en.png rename to modules/ROOT/assets/images/tutorials/imagefactory-kvm/030-create-thinpool-en.png diff --git a/docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/035-show-thinpool-en.png b/modules/ROOT/assets/images/tutorials/imagefactory-kvm/035-show-thinpool-en.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/035-show-thinpool-en.png rename to modules/ROOT/assets/images/tutorials/imagefactory-kvm/035-show-thinpool-en.png diff --git a/docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/040-create-thinvolume-en.png b/modules/ROOT/assets/images/tutorials/imagefactory-kvm/040-create-thinvolume-en.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/040-create-thinvolume-en.png rename to modules/ROOT/assets/images/tutorials/imagefactory-kvm/040-create-thinvolume-en.png diff --git a/docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/045-show-thinvolume-en.png b/modules/ROOT/assets/images/tutorials/imagefactory-kvm/045-show-thinvolume-en.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/045-show-thinvolume-en.png rename to modules/ROOT/assets/images/tutorials/imagefactory-kvm/045-show-thinvolume-en.png diff --git a/docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/050-format-thinvolume-en.png b/modules/ROOT/assets/images/tutorials/imagefactory-kvm/050-format-thinvolume-en.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/050-format-thinvolume-en.png rename to modules/ROOT/assets/images/tutorials/imagefactory-kvm/050-format-thinvolume-en.png diff --git a/docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/055-show-thinvolumes-en.png b/modules/ROOT/assets/images/tutorials/imagefactory-kvm/055-show-thinvolumes-en.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/055-show-thinvolumes-en.png rename to modules/ROOT/assets/images/tutorials/imagefactory-kvm/055-show-thinvolumes-en.png diff --git a/docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/059-list-volumes-en.png b/modules/ROOT/assets/images/tutorials/imagefactory-kvm/059-list-volumes-en.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/imagefactory-kvm/059-list-volumes-en.png rename to modules/ROOT/assets/images/tutorials/imagefactory-kvm/059-list-volumes-en.png diff --git a/docs/modules/ROOT/assets/images/tutorials/wordpress/fedora-default-page.png b/modules/ROOT/assets/images/tutorials/wordpress/fedora-default-page.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/wordpress/fedora-default-page.png rename to modules/ROOT/assets/images/tutorials/wordpress/fedora-default-page.png diff --git a/docs/modules/ROOT/assets/images/tutorials/wordpress/initial-installation-page.png b/modules/ROOT/assets/images/tutorials/wordpress/initial-installation-page.png similarity index 100% rename from docs/modules/ROOT/assets/images/tutorials/wordpress/initial-installation-page.png rename to modules/ROOT/assets/images/tutorials/wordpress/initial-installation-page.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-01.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-01.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-01.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-01.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-02.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-02.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-02.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-02.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-03.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-03.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-03.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-03.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-04.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-04.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-04.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-04.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-05.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-05.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-05.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-05.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-30.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-30.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-30.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-30.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-32.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-32.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-32.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-32.png diff --git a/docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-35.png b/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-35.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-35.png rename to modules/ROOT/assets/images/virtualization/diskimg-fedoraserver-35.png diff --git a/docs/modules/ROOT/assets/images/virtualization/nested-cpu-type.png b/modules/ROOT/assets/images/virtualization/nested-cpu-type.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/nested-cpu-type.png rename to modules/ROOT/assets/images/virtualization/nested-cpu-type.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-010.png b/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-010.png rename to modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-010.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-020.png b/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-020.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-020.png rename to modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-020.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-030.png b/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-030.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-030.png rename to modules/ROOT/assets/images/virtualization/vm-install-cloudimg-centos9-030.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-cockpit-010.png b/modules/ROOT/assets/images/virtualization/vm-install-cockpit-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-cockpit-010.png rename to modules/ROOT/assets/images/virtualization/vm-install-cockpit-010.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-fedoraserver-010.png b/modules/ROOT/assets/images/virtualization/vm-install-diskimg-fedoraserver-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-fedoraserver-010.png rename to modules/ROOT/assets/images/virtualization/vm-install-diskimg-fedoraserver-010.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-010.png b/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-010.png rename to modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-010.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-020.png b/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-020.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-020.png rename to modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-020.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-030.png b/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-030.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-030.png rename to modules/ROOT/assets/images/virtualization/vm-install-diskimg-virtbuilder-030.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-010.png b/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-010.png rename to modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-010.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-020.png b/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-020.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-020.png rename to modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-020.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-030.png b/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-030.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-030.png rename to modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-030.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-040.png b/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-040.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-040.png rename to modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-040.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-050.png b/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-050.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-050.png rename to modules/ROOT/assets/images/virtualization/vm-install-fedoraserver-cockpit-050.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-001.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-001.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-001.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-001.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-003.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-003.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-003.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-003.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-005.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-005.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-005.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-005.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-006.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-006.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-006.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-006.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-007.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-007.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-007.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-007.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-008.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-008.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-008.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-008.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-009.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-009.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-009.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-009.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-010.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-010.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-010.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-010.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-015.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-015.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-015.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-015.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-020.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-020.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-020.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-020.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-025.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-025.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-025.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-025.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-027.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-027.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-027.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-027.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-030.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-030.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-030.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-030.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-031.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-031.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-031.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-031.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-033.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-033.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-033.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-033.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-034.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-034.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-034.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-034.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-036.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-036.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-036.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-036.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-038.png b/modules/ROOT/assets/images/virtualization/vm-management-cockpit-038.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-management-cockpit-038.png rename to modules/ROOT/assets/images/virtualization/vm-management-cockpit-038.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-01.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-01.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-01.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-01.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-02.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-02.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-02.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-02.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-03.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-03.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-03.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-03.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-04.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-04.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-04.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-04.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-05.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-05.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-05.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-05.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-06.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-06.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-06.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-06.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-07.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-07.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-07.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-07.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-08.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-08.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-08.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-08.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-09.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-09.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-09.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-09.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-10.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-10.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-10.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-10.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-11.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-11.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-11.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-11.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-12.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-12.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-12.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-12.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-13.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-13.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-13.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-13.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-14.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-14.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-14.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-14.png diff --git a/docs/modules/ROOT/assets/images/virtualization/vm-proxmox-15.png b/modules/ROOT/assets/images/virtualization/vm-proxmox-15.png similarity index 100% rename from docs/modules/ROOT/assets/images/virtualization/vm-proxmox-15.png rename to modules/ROOT/assets/images/virtualization/vm-proxmox-15.png diff --git a/docs/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc similarity index 100% rename from docs/modules/ROOT/nav.adoc rename to modules/ROOT/nav.adoc diff --git a/docs/modules/ROOT/pages/.DS_Store b/modules/ROOT/pages/.DS_Store similarity index 100% rename from docs/modules/ROOT/pages/.DS_Store rename to modules/ROOT/pages/.DS_Store diff --git a/docs/modules/ROOT/pages/administration/dnsmasq.adoc b/modules/ROOT/pages/administration/dnsmasq.adoc similarity index 100% rename from docs/modules/ROOT/pages/administration/dnsmasq.adoc rename to modules/ROOT/pages/administration/dnsmasq.adoc diff --git a/docs/modules/ROOT/pages/administration/index.adoc b/modules/ROOT/pages/administration/index.adoc similarity index 100% rename from docs/modules/ROOT/pages/administration/index.adoc rename to modules/ROOT/pages/administration/index.adoc diff --git a/docs/modules/ROOT/pages/administration/point-to-point-connection.adoc b/modules/ROOT/pages/administration/point-to-point-connection.adoc similarity index 100% rename from docs/modules/ROOT/pages/administration/point-to-point-connection.adoc rename to modules/ROOT/pages/administration/point-to-point-connection.adoc diff --git a/docs/modules/ROOT/pages/administration/virtual-routing-bridge.adoc b/modules/ROOT/pages/administration/virtual-routing-bridge.adoc similarity index 100% rename from docs/modules/ROOT/pages/administration/virtual-routing-bridge.adoc rename to modules/ROOT/pages/administration/virtual-routing-bridge.adoc diff --git a/docs/modules/ROOT/pages/containerization/index.adoc b/modules/ROOT/pages/containerization/index.adoc similarity index 100% rename from docs/modules/ROOT/pages/containerization/index.adoc rename to modules/ROOT/pages/containerization/index.adoc diff --git a/docs/modules/ROOT/pages/containerization/systemd-nspawn-setup.adoc b/modules/ROOT/pages/containerization/systemd-nspawn-setup.adoc similarity index 100% rename from docs/modules/ROOT/pages/containerization/systemd-nspawn-setup.adoc rename to modules/ROOT/pages/containerization/systemd-nspawn-setup.adoc diff --git a/docs/modules/ROOT/pages/index.adoc b/modules/ROOT/pages/index.adoc similarity index 100% rename from docs/modules/ROOT/pages/index.adoc rename to modules/ROOT/pages/index.adoc diff --git a/docs/modules/ROOT/pages/installation/index.adoc b/modules/ROOT/pages/installation/index.adoc similarity index 100% rename from docs/modules/ROOT/pages/installation/index.adoc rename to modules/ROOT/pages/installation/index.adoc diff --git a/docs/modules/ROOT/pages/installation/interactive-local.adoc b/modules/ROOT/pages/installation/interactive-local.adoc similarity index 100% rename from docs/modules/ROOT/pages/installation/interactive-local.adoc rename to modules/ROOT/pages/installation/interactive-local.adoc diff --git a/docs/modules/ROOT/pages/installation/interactive-remote.adoc b/modules/ROOT/pages/installation/interactive-remote.adoc similarity index 100% rename from docs/modules/ROOT/pages/installation/interactive-remote.adoc rename to modules/ROOT/pages/installation/interactive-remote.adoc diff --git a/docs/modules/ROOT/pages/installation/on-sbc.adoc b/modules/ROOT/pages/installation/on-sbc.adoc similarity index 100% rename from docs/modules/ROOT/pages/installation/on-sbc.adoc rename to modules/ROOT/pages/installation/on-sbc.adoc diff --git a/docs/modules/ROOT/pages/installation/postinstallation-tasks.adoc b/modules/ROOT/pages/installation/postinstallation-tasks.adoc similarity index 100% rename from docs/modules/ROOT/pages/installation/postinstallation-tasks.adoc rename to modules/ROOT/pages/installation/postinstallation-tasks.adoc diff --git a/docs/modules/ROOT/pages/installation/sw-raid-upon-installation.adoc b/modules/ROOT/pages/installation/sw-raid-upon-installation.adoc similarity index 100% rename from docs/modules/ROOT/pages/installation/sw-raid-upon-installation.adoc rename to modules/ROOT/pages/installation/sw-raid-upon-installation.adoc diff --git a/docs/modules/ROOT/pages/server-communicating.adoc b/modules/ROOT/pages/server-communicating.adoc similarity index 100% rename from docs/modules/ROOT/pages/server-communicating.adoc rename to modules/ROOT/pages/server-communicating.adoc diff --git a/docs/modules/ROOT/pages/server-faq.adoc b/modules/ROOT/pages/server-faq.adoc similarity index 100% rename from docs/modules/ROOT/pages/server-faq.adoc rename to modules/ROOT/pages/server-faq.adoc diff --git a/docs/modules/ROOT/pages/server-on-sbc/index.adoc b/modules/ROOT/pages/server-on-sbc/index.adoc similarity index 100% rename from docs/modules/ROOT/pages/server-on-sbc/index.adoc rename to modules/ROOT/pages/server-on-sbc/index.adoc diff --git a/docs/modules/ROOT/pages/services/filesharing-nfs-installation.adoc b/modules/ROOT/pages/services/filesharing-nfs-installation.adoc similarity index 100% rename from docs/modules/ROOT/pages/services/filesharing-nfs-installation.adoc rename to modules/ROOT/pages/services/filesharing-nfs-installation.adoc diff --git a/docs/modules/ROOT/pages/services/httpd-basic-setup.adoc b/modules/ROOT/pages/services/httpd-basic-setup.adoc similarity index 100% rename from docs/modules/ROOT/pages/services/httpd-basic-setup.adoc rename to modules/ROOT/pages/services/httpd-basic-setup.adoc diff --git a/docs/modules/ROOT/pages/services/postgresql-setup.adoc b/modules/ROOT/pages/services/postgresql-setup.adoc similarity index 100% rename from docs/modules/ROOT/pages/services/postgresql-setup.adoc rename to modules/ROOT/pages/services/postgresql-setup.adoc diff --git a/docs/modules/ROOT/pages/tutorials/imagefactory.adoc b/modules/ROOT/pages/tutorials/imagefactory.adoc similarity index 100% rename from docs/modules/ROOT/pages/tutorials/imagefactory.adoc rename to modules/ROOT/pages/tutorials/imagefactory.adoc diff --git a/docs/modules/ROOT/pages/tutorials/wordpress-installation.adoc b/modules/ROOT/pages/tutorials/wordpress-installation.adoc similarity index 100% rename from docs/modules/ROOT/pages/tutorials/wordpress-installation.adoc rename to modules/ROOT/pages/tutorials/wordpress-installation.adoc diff --git a/docs/modules/ROOT/pages/usecase-gui-addon.adoc b/modules/ROOT/pages/usecase-gui-addon.adoc similarity index 100% rename from docs/modules/ROOT/pages/usecase-gui-addon.adoc rename to modules/ROOT/pages/usecase-gui-addon.adoc diff --git a/docs/modules/ROOT/pages/virtualization/index.adoc b/modules/ROOT/pages/virtualization/index.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/index.adoc rename to modules/ROOT/pages/virtualization/index.adoc diff --git a/docs/modules/ROOT/pages/virtualization/installation.adoc b/modules/ROOT/pages/virtualization/installation.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/installation.adoc rename to modules/ROOT/pages/virtualization/installation.adoc diff --git a/docs/modules/ROOT/pages/virtualization/nested-virtualization.adoc b/modules/ROOT/pages/virtualization/nested-virtualization.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/nested-virtualization.adoc rename to modules/ROOT/pages/virtualization/nested-virtualization.adoc diff --git a/docs/modules/ROOT/pages/virtualization/vm-install-cloudimg-centos9.adoc b/modules/ROOT/pages/virtualization/vm-install-cloudimg-centos9.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/vm-install-cloudimg-centos9.adoc rename to modules/ROOT/pages/virtualization/vm-install-cloudimg-centos9.adoc diff --git a/docs/modules/ROOT/pages/virtualization/vm-install-diskimg-fedoraserver.adoc b/modules/ROOT/pages/virtualization/vm-install-diskimg-fedoraserver.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/vm-install-diskimg-fedoraserver.adoc rename to modules/ROOT/pages/virtualization/vm-install-diskimg-fedoraserver.adoc diff --git a/docs/modules/ROOT/pages/virtualization/vm-install-diskimg-proxmox.adoc b/modules/ROOT/pages/virtualization/vm-install-diskimg-proxmox.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/vm-install-diskimg-proxmox.adoc rename to modules/ROOT/pages/virtualization/vm-install-diskimg-proxmox.adoc diff --git a/docs/modules/ROOT/pages/virtualization/vm-install-diskimg-virtbuilder.adoc b/modules/ROOT/pages/virtualization/vm-install-diskimg-virtbuilder.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/vm-install-diskimg-virtbuilder.adoc rename to modules/ROOT/pages/virtualization/vm-install-diskimg-virtbuilder.adoc diff --git a/docs/modules/ROOT/pages/virtualization/vm-install-fedoraserver-cockpit.adoc b/modules/ROOT/pages/virtualization/vm-install-fedoraserver-cockpit.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/vm-install-fedoraserver-cockpit.adoc rename to modules/ROOT/pages/virtualization/vm-install-fedoraserver-cockpit.adoc diff --git a/docs/modules/ROOT/pages/virtualization/vm-management-cockpit.adoc b/modules/ROOT/pages/virtualization/vm-management-cockpit.adoc similarity index 100% rename from docs/modules/ROOT/pages/virtualization/vm-management-cockpit.adoc rename to modules/ROOT/pages/virtualization/vm-management-cockpit.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/cockpit-check-accessibility.adoc b/modules/ROOT/partials/installation/post-install/cockpit-check-accessibility.adoc similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/cockpit-check-accessibility.adoc rename to modules/ROOT/partials/installation/post-install/cockpit-check-accessibility.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/cockpit-secure-access.adoc b/modules/ROOT/partials/installation/post-install/cockpit-secure-access.adoc similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/cockpit-secure-access.adoc rename to modules/ROOT/partials/installation/post-install/cockpit-secure-access.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/convenient-user-login.adoc b/modules/ROOT/partials/installation/post-install/convenient-user-login.adoc similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/convenient-user-login.adoc rename to modules/ROOT/partials/installation/post-install/convenient-user-login.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/disable-password-login.adoc b/modules/ROOT/partials/installation/post-install/disable-password-login.adoc similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/disable-password-login.adoc rename to modules/ROOT/partials/installation/post-install/disable-password-login.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/install-fail2ban.adoc b/modules/ROOT/partials/installation/post-install/install-fail2ban.adoc similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/install-fail2ban.adoc rename to modules/ROOT/partials/installation/post-install/install-fail2ban.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/manage-dnf-updates.adoc b/modules/ROOT/partials/installation/post-install/manage-dnf-updates.adoc similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/manage-dnf-updates.adoc rename to modules/ROOT/partials/installation/post-install/manage-dnf-updates.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/setup-esmpt.adoc b/modules/ROOT/partials/installation/post-install/setup-esmpt.adoc similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/setup-esmpt.adoc rename to modules/ROOT/partials/installation/post-install/setup-esmpt.adoc diff --git a/docs/modules/ROOT/partials/installation/post-install/splitter.adoc.txt b/modules/ROOT/partials/installation/post-install/splitter.adoc.txt similarity index 100% rename from docs/modules/ROOT/partials/installation/post-install/splitter.adoc.txt rename to modules/ROOT/partials/installation/post-install/splitter.adoc.txt diff --git a/preview.sh b/preview.sh deleted file mode 100755 index 341d6ab..0000000 --- a/preview.sh +++ /dev/null @@ -1,13 +0,0 @@ -#!/bin/bash - -echo "Deprecated. Use the docsbuilder.sh script instead" -echo "" -echo "The preview is available at http://localhost:8080" -echo "" -echo "Spaces:" -echo " * User Documentation .. http://localhost:8080/fedora-server/ #(default)" -echo " * Working Group pages.. http://localhost:8080/server-working-group/" -echo "" -sleep 2 -./docsbuilder.sh -p - diff --git a/site.yml b/site.yml index bd38b73..a07aab1 100644 --- a/site.yml +++ b/site.yml @@ -1,14 +1,11 @@ site: - title: Local Preview - Fedora server informations + title: Local Preview - Fedora Server User Documentation start_page: fedora-server::index.adoc content: sources: - url: . branches: HEAD - start_path: docs - - url: . - branches: HEAD - start_path: wg + start_path: ./ ui: bundle: url: https://gitlab.com/fedora/docs/docs-website/ui-bundle/-/jobs/artifacts/HEAD/raw/build/ui-bundle.zip?job=bundle-stable diff --git a/wg/README.md b/wg/README.md deleted file mode 100644 index ec3c390..0000000 --- a/wg/README.md +++ /dev/null @@ -1,4 +0,0 @@ -# Fedora Server Working Group - -This directory contains the sources for the Fedora Server Working Group. - diff --git a/wg/antora.yml b/wg/antora.yml deleted file mode 100644 index 89e129d..0000000 --- a/wg/antora.yml +++ /dev/null @@ -1,22 +0,0 @@ -# Name will be mostly visible in the URL. Treat it as an identifier. -# Tip: If you want to use the local preview scripts that come with this -# repository, please change this value in the site.yml file as well. (under -# site/start_page) -name: server-working-group - -# Title will be visible on the page. -title: Fedora Server Working Group - -# If you don't plan to have multiple versions of the docs (for example, to -# document multiple versions of some software), you can ignore this field. -# Otherwise, change "master" to a specific version. -version: master - -# We encourage you to name the index page as "index.adoc". If you absolutely -# have to use a different name, please reflect it here. You can ignore this -# field otherwise. -start_page: ROOT:index.adoc - -# This lists all the menu definitions of your component. -nav: -- modules/ROOT/nav.adoc diff --git a/wg/modules/ROOT/assets/attachments/archive/._FedoraServerDocpageProposal_v1-0.pdf b/wg/modules/ROOT/assets/attachments/archive/._FedoraServerDocpageProposal_v1-0.pdf deleted file mode 100644 index 4ca327f..0000000 Binary files a/wg/modules/ROOT/assets/attachments/archive/._FedoraServerDocpageProposal_v1-0.pdf and /dev/null differ diff --git a/wg/modules/ROOT/assets/attachments/archive/FedoraServerDocpageProposal_v1-0.pdf b/wg/modules/ROOT/assets/attachments/archive/FedoraServerDocpageProposal_v1-0.pdf deleted file mode 100644 index 1354a68..0000000 Binary files a/wg/modules/ROOT/assets/attachments/archive/FedoraServerDocpageProposal_v1-0.pdf and /dev/null differ diff --git a/wg/modules/ROOT/assets/attachments/srv-template.adoc b/wg/modules/ROOT/assets/attachments/srv-template.adoc deleted file mode 100644 index 63d260a..0000000 --- a/wg/modules/ROOT/assets/attachments/srv-template.adoc +++ /dev/null @@ -1,81 +0,0 @@ -= ARTICLE_TITLE -AUTHOR_1; AUTHOR_2; AUTHOR_3 -:revnumber: Fxy -:revdate: yyyy-mm-dd -//:page-aliases: OPTIONAL in case you want to forward from an previous address - -// Optional free form useful additional information as comment - - -[abstract] ------- -Mission statement of 2-3 sentences in one line, no between sentences, just one final ------- - - -// Please, comment-in the Warning below when you start and publish in stg -// Comment-out (or remove) when committed in main (public version) -//[WARNING] -//==== -//**You are in the Fedora Server documentation staging area!** -// -//These documents are not approved yet and may be incomplete and/or incorrect. Take everything here with a grain of salt! You would probably prefer to study the link:++https://docs.fedoraproject.org/en-US/fedora-server/++[published documentation]. -// -//**Status of this document**: Work in progress. -//**Status of this document**: Review in progress -//**Status of this document**: Updating the public version -//==== - - -== Overview -// Please, give a short overview of the process, -// maybe add some more generell introduction if appropriate - -You may refer to other parts of Fedora Server documentation, e.g. mention the xref:index.adoc[Server homepage] or the xref:installation/postinstallation-tasks.adoc[post-installation guide] of the installation section (subdir). - -== Installation -// Optionally a short overview - -STEP 01:: Description of Step - -STEP 02:: Description of Step -+ -Don't forget to provide code examples -+ -+ -[source,] ----- -[…]# lvcreate -L 40G -T fedora/srv -V 30G -T fedora/srv -n nfs -[…]# lvs -[…]# mkfs.xfs /dev/fedora/nfs ----- - - -== Initial configuration -// Optionally a short overview - -STEP 01:: Description of Step -+ -Include an image -+ -.Optional subtitle -image::services/nfs-server-inst-001.png[] -// Images belong in the directory ~/docs/modules/ROOT/assets/images/[DIRNAME]/[NAME.png] - -STEP 02:: Description of Step -+ -You may also offer something xref:attachment$services/httpd-basic-setup/zvhost-static-html.template[to download] - -== Administration -// Alternatively a separat Administration document - - -== Final test -// Optional - - -== Troubleshooting -// Optional, if applicable - -== Additional information -// Specifically a link to upstream documentation if available diff --git a/wg/modules/ROOT/assets/images/Banner_serverwg-768x325.png b/wg/modules/ROOT/assets/images/Banner_serverwg-768x325.png deleted file mode 100644 index 53fe811..0000000 Binary files a/wg/modules/ROOT/assets/images/Banner_serverwg-768x325.png and /dev/null differ diff --git a/wg/modules/ROOT/assets/images/Logo_server-working-group.png b/wg/modules/ROOT/assets/images/Logo_server-working-group.png deleted file mode 100644 index 4d15938..0000000 Binary files a/wg/modules/ROOT/assets/images/Logo_server-working-group.png and /dev/null differ diff --git a/wg/modules/ROOT/assets/images/Logo_server.png b/wg/modules/ROOT/assets/images/Logo_server.png deleted file mode 100644 index eeaad84..0000000 Binary files a/wg/modules/ROOT/assets/images/Logo_server.png and /dev/null differ diff --git a/wg/modules/ROOT/assets/images/Logo_server2.png b/wg/modules/ROOT/assets/images/Logo_server2.png deleted file mode 100644 index eeaad84..0000000 Binary files a/wg/modules/ROOT/assets/images/Logo_server2.png and /dev/null differ diff --git a/wg/modules/ROOT/assets/images/archive/._webui-editor-0010.png b/wg/modules/ROOT/assets/images/archive/._webui-editor-0010.png deleted file mode 100644 index 211f556..0000000 Binary files a/wg/modules/ROOT/assets/images/archive/._webui-editor-0010.png and /dev/null differ diff --git a/wg/modules/ROOT/assets/images/archive/._webui-editor-0020.png b/wg/modules/ROOT/assets/images/archive/._webui-editor-0020.png deleted file mode 100644 index 6ad79f3..0000000 Binary files a/wg/modules/ROOT/assets/images/archive/._webui-editor-0020.png and /dev/null differ diff --git a/wg/modules/ROOT/assets/images/archive/webui-editor-0010.png b/wg/modules/ROOT/assets/images/archive/webui-editor-0010.png deleted file mode 100644 index 3a40af3..0000000 Binary files a/wg/modules/ROOT/assets/images/archive/webui-editor-0010.png and /dev/null differ diff --git a/wg/modules/ROOT/assets/images/archive/webui-editor-0020.png b/wg/modules/ROOT/assets/images/archive/webui-editor-0020.png deleted file mode 100644 index baffbd6..0000000 Binary files a/wg/modules/ROOT/assets/images/archive/webui-editor-0020.png and /dev/null differ diff --git a/wg/modules/ROOT/nav.adoc b/wg/modules/ROOT/nav.adoc deleted file mode 100644 index e18abb7..0000000 --- a/wg/modules/ROOT/nav.adoc +++ /dev/null @@ -1,19 +0,0 @@ -* Goals -** xref:docs/product-requirements-document.adoc[The Product Requirement Document] -** xref:docs/server-technical-specification.adoc[Technical Specification] -// ** Personas (target users) -* Members and Governance -** xref:wg-members.adoc[Members] -** xref:docs/server-governance-charter.adoc[Governance Charter] -* xref:wg-communicating.adoc[Communicating and Meeting] -// xref:wg-minutes-current.adoc[Current meeting minutes] KEEP as :page-aliases: -** xref:wg-minutes-2025.adoc[Current meeting minutes] -** xref:wg-minutes-2024.adoc[Meeting minutes 2024] -** xref:wg-minutes-2023.adoc[Meeting minutes 2023] -** xref:wg-minutes-2022.adoc[Meeting minutes 2022] -** xref:wg-minutes-2021.adoc[Meeting minutes 2020/2021] -** xref:wg-minutes-2013.adoc[Meeting minutes prior to 2021] -* xref:usr-docs-maintenance/index.adoc[User Docs Maintenance] -** xref:usr-docs-maintenance/webui-page-editor.adoc[Working with the Web based page editor] -** xref:usr-docs-maintenance/local-authoring.adoc[Working in a local authoring environment] -* xref:archive/index.adoc[Archive of Older Pages] diff --git a/wg/modules/ROOT/pages/archive/index.adoc b/wg/modules/ROOT/pages/archive/index.adoc deleted file mode 100644 index 55c2971..0000000 --- a/wg/modules/ROOT/pages/archive/index.adoc +++ /dev/null @@ -1,29 +0,0 @@ -= Archive -The Fedora Server Edition Working Group -:page-authors: {author} -// :revnumber: F37-F38 -:revdate: 2023-04-24 - -For reference and documentation of the Server Edition evolution process, we continue to provide older versions of various documents for review. - - - -== Archived approved documents - -* xref:archive/product-requirements-document-2014.adoc["Product Requirements Document" (initial version 2014)] -* xref:archive/product-requirements-document-2021.adoc["Product Requirements Document" (renwed version 2021)] -* xref:archive/server-technical-specification-2014.adoc["Fedora Server Technical Specification" (initial version 2014)] - - -== Server related documents - - - -== Research - - -== Proposals - - -== Working group work plannings -* WG work project xref:archive/initial-docs-plan.adoc[Buildup of a renewed documentation on Fedora Server specific topics] planning \ No newline at end of file diff --git a/wg/modules/ROOT/pages/archive/initial-docs-plan.adoc b/wg/modules/ROOT/pages/archive/initial-docs-plan.adoc deleted file mode 100644 index ffbdcee..0000000 --- a/wg/modules/ROOT/pages/archive/initial-docs-plan.adoc +++ /dev/null @@ -1,106 +0,0 @@ -= Buildup of a renewed documentation on Fedora Server specific topics -The Fedora Server Edition Working Group -:page-authors: {author} -// :revnumber: F37-F38 -// :revdate: 2023-04-xx - -[NOTE] -==== -*Archived Content* Initial planning to build up a server user documentation. -==== - -== Goals == - -* Build up a documentation which will be part of the fedora link:https://docs.fedoraproject.org[docs landing page] -* Maybe: Additional information to central "System Administrator's Guide" documentation -* Maybe: Additional information to the central "Installation Guide" - - -== Planned content for start of publication == - -.First Start Content -[width="100%",options="header"] -|==================== -| Page | Author | Reviewer | Status -| Landing Page | pboy | pwsmith | done & ready -| Server Installation | pboy | nirik | done & ready -| Installation on SBC | pboy | swefredde | done & ready -| Server Administration | pboy | eseyman | done & ready -| Server Post installation tasks | pboy | nirik | done & ready -| Server Virtualisation | pboy | swefredde | done & ready -| Add Virtualisation Support | pboy | swefredde | done & ready -| VMs based on Cloud Images | pboy| IRC WG | done & ready -| FAQ | copperi | IRC WG | done & ready -| Getting in Touch | copperi | IRC WG | done & ready -|==================== - -=== Reviewer tasks === -* Check for technical and content accuracy. Contact the author in case of questions. -* Checking spelling and syntax -* Especially in the case of non-English speaking authors refine the wording and phrases - -To to get the document files and to provide feedback follow the "how to Contribute" information. - -== How to Contribute == - -There are several ways to contribute. A non-intrusive way allows to comment or add to a single document. For longer-term engagement, it makes sense to set up a complete authoring environment. - -Details are described on a [https://fedoraproject.org/wiki/Server/Documentation/How_To_Contribute separate page ]. - -== The next steps == - -* Concretization of the planning. We need -** a rough overall plan of the content -** exemplary topics / themes -** to find contributors / authors - -* Set up Working Environment -** Staging Area -** Preparation of publishing pipelines - -* Define Milestones -** Most important: minimum requirement for going online - -== Preliminary planning proposal == - -Recently I came across an informative article: link:https://opensource.com/article/20/4/documentation?utm_campaign=intrel["What is good documentation for software projects?"]. It's not brand new, but it's a good summary of what to look for in a documentation project. - -=== Team === -We need skill sets from multiple roles  - -* *Authors/Writers* with a deep understanding of the software being described, who create texts, of course -* *Information Architects* who understands how to structure material -* *Reviewers* with a deep understanding of the software being described, who ensure technical correctness -* *Editor/Reader*, especially English native speakers, who proofread the wording and spelling -* *Administrator* who keeps up the build pipelines and correct web formatting and presentation -* *Coordinator*, who keeps an eye on the overall plan and helps to align all the processes and people - -=== Guidelines === - -Notes on the structure of the texts. For example, it would be necessary to regulate: - -* Specification of author(s), date of creation, last update, Fedora version with which representations were tested. -* Start with a short summary of the subject matter, objective and desired outcome. (paragraph of 2-3 sentences) -* Divide longer sequences into sections with subheadings and short explanations -* Provide each step with a brief explanation/justification, if possible, a general instruction structure and a concrete example. - -=== Overall Conceptualization of Server Documentation Content === - -As a first Draft we may discuss (see also -xref:attachment$archive/FedoraServerDocpageProposal_v1-0.pdf[first draft of a proposal] -// link:{attachmentsdir}/archive/FedoraServerDocpageProposal_v1-0.pdf[first draft of a proposal] -for a concept to improve documentation) - -* Navigation Items -** Home / Landing Page Fedora Server Documentation -** Post-installation Procedures / Security Hardening -** Fedora Server Example Use Cases -** Tutorials -** Trouble Shooting Guide / Known Issues -** People, policies, and Working Methods -* Details Home / Landing Page -* Details Post Installation -* Details Example Use Cases -* Details Tutorials -* Details People, Policies, ... - diff --git a/wg/modules/ROOT/pages/archive/product-requirements-document-2014.adoc b/wg/modules/ROOT/pages/archive/product-requirements-document-2014.adoc deleted file mode 100644 index 7ae9eae..0000000 --- a/wg/modules/ROOT/pages/archive/product-requirements-document-2014.adoc +++ /dev/null @@ -1,184 +0,0 @@ -= Product Requirements Document - -[WARNING] -==== -This is the 2014 version of this document, approved by WG 17 January 2014, https://fedorahosted.org/fesco/ticket/1222[approved by FESCo 22 January 2014]. It is outdated and no longer valid. *Unless you are doing historical research, see the xref:docs/product-requirements-document.adoc[2021 Fedora Server Edition PRD]* -==== - -== Document Purpose and Overview - -=== What this document describes - -This is the http://en.wikipedia.org/wiki/Product_requirements_document[Product Requirements Document] for the Fedora Server. It: - -* Provides a high-level market overview of the infrastructure server market as it pertains to the Fedora Server; this includes items which may not be within our actual scope/ability to accomplish at the current time. -* Provides deeper understanding of the types of users who could use Fedora for their application and infrastructure needs. This includes describing their main day-to-day tasks, common problems, etc. The perspective here is not necessarily limited to system administrators, or developers, but a combination of many types of users and roles. -* Ties common issues and needs of potential users/consumers of the Fedora Server product to high-level product needs, from a "functional" standpoint. - -This document does not dictate implementation details. The goals in this document will drive the continued implementation of this product. - -=== Fedora Server Vision Statement - -Fedora Server is the preferred [community] platform for system administrators and developers seeking to deploy applications and services that use the latest technology on a stable foundation with effective resource utilization. - -=== Fedora Server Mission Statement - -Fedora Server is a common base platform with "featured server roles" built on top of it. We commit to produce, test, and distribute these server roles. - -=== Market Opportunity - -The server operating system market is mature, but constantly evolving. Fedora Server has opportunity for adoption as people deploy new applications and services as well as migrate legacy applications to new platforms. - -With the increased complexity of IT and software, system administrators find it more difficult to devote large amounts of time to dealing with individual technologies, specifically: - -* Detailed understanding of the underlying technology, as has traditionally been required for Open Source server solutions, is often not feasible. -* The constant focus of Fedora to ship the latest upstream releases of software, combined with a short lifecycle and lack of tooling, require frequently spending significant amounts of time migrating from one Fedora release to another. - -These impositions on system administrators are a significant barrier to further growth of Fedora, and we believe that by improving the product we can remove these requirements and barriers, opening Fedora up to a much larger user base that has so far been limited to non-Linux server solutions. - -Fedora, being a leading-edge Linux distribution, is the ideal place to design such server improvements for the Linux ecosystem together with real-world users to make them available to early adopters. - -=== Product Objectives - -Fedora Server consists of a release that can be used at various scales. For example, it could be used in the following example environments: - -* A single server that runs an application or service. -* A platform for an entire data center. -* The platform to deploy an Infrastructure-as-a-Service (IaaS) private cloud. - -Fedora Server is meant to be used for the following purposes: - -* An operating platform for important infrastructure tasks (DNS, DHCP, etc.) and server applications (file/storage server, database server, user-developed web applications, etc.) -* A platform for deploying Infrastructure-as-a-Service systems for best deployment of Fedora Cloud images. -* Infrastructure to allow efficiently managing many servers as a single unit. The product only commits to producing basic tools, but the infrastructure will allow more advanced tools to be created. - -The Fedora Server product will also provide one or more "roles" that can be used to easily spin up a service or application. Roles will be introduced gradually as development and testing allow, but it is a primary objective to offer useful roles built on top of the base server offering. More information about what roles are is provided elsewhere in this document. - -=== Secondary Objectives - -Aside from the adoption and development of applications on top of the Fedora Server platform, we have a few secondary goals that should be helped by wider adoption: - -* More testing of Fedora images with additional bug reports. -* Better feedback about product direction and potential improvements. This is separate from "bug reports" in that we hope to engage the audience and receive detailed feedback about use cases, desired features, developing trends in cloud management, etc. -* More patches and contributions that will help improve the product, and Fedora in general. Assuming we're successful, some users should take an interest in helping to develop our product. - -== User Profiles, Primary Use Cases and Goals - -=== Personas - -We will use a set of personas to describe our target users and their respective needs. This document will list the personas in their simplified forms, with detailed explanations of each one available on their respective wiki pages. - -1. System Administrator "Macgyver" -* Administrator with limited hardware and personnel resources to work with -* Needs to be able to do "a lot with a little" -2. DevOps Engineer/Administrator -* Focus is on time-to-deploy and time-to-recover as opposed to uptime -* Value is achieved by delivering the latest capabilities fastest -* Needs to be able to deliver quickly to PaaS, SaaS and bare-metal servers -3. Traditional Application Developer -* Needs a platform with API and ABI stability guarantees -* Focus will be on minimizing risk when making changes -* Cannot tolerate rapid changes in core functionality -4. Junior Enterprise System Administrator -* Simplify automation to manage repetitive tasks -* Needs intuitive mechanisms to effect common changes -5. Decision Maker -* Makes purchasing decisions and directs technology choices -* Interacts with upstream FOSS communities to identify potential value - -=== Use Cases - -The Fedora Server will need to address the following use-cases: - -1. The user must be able to easily deploy and configure any supported Fedora Server role. (Examples may include: FreeIPA Domain Controller, BIND DNS, DHCP, Database server, iSCSI target, File/Storage server, OpenStack Hypervisor Node.) -2. The user must be able to query, monitor, configure and manage a Fedora Server remotely using stable and consistent public interfaces. -3. The user must be able to simply enroll the Fedora Server into a FreeIPA or Active Directory domain. -4. Users must be able to control and contain the resources consumed by services running on the system. -5. Users must be able to rapidly re-deploy services in accordance with their DevOps practices using Fedora Server. -6. Users must be able to create, manipulate and terminate large numbers of containers using a stable and consistent interface. -7. The user must be able to install and manage Fedora Server in a headless mode where the display framework is inactive. - -=== Featured Server Roles - -A Featured Server role is an installable component of Fedora Server that provides a well-integrated service on top of the Fedora Server platform. These prepared roles simplify deployment and management of a service compared to setting up an upstream server from scratch; their use is recommended but optional; existing users of upstream servers based on Fedora RPMs will not be impeded. - -Initially, we will test and support only a single role per server; installing several non-conflicting roles is expected, but we will not be testing every combination. - -==== Mandatory Requirements - -[IMPORTANT] -==== -Mandatory requirements are exactly as they sound: if any one of these requirements is not met, the server role is ineligible for elevation to "featured" status. -==== - -1. The Server Role *must* be packaged in such a way that it is possible to install the complete set as a unit. AKA "One-click Install". [Use Case 1] -2. The Server Role *must* provide an API or similar stable external interface for configuring the role post-installation. Exceptions to this rule may be granted if and only if Optional Requirement 2 (below) is met and it can be demonstrated that the default method of operation is the only reasonable method of operation. [Use Case 1] -* If the API is provided by the Fedora project it must be built using a common framework to all Fedora developed Role APIs. If upstream provides such an API, it is permissible to use that. -3. The Server Role *must* provide an API to interrogate the configurable settings of the role as identified by Mandatory Requirement 2. [Use Case 2] -4. The Server Role *must* add to the functionality of the Fedora Server. In other words, a Server Role cannot be considered "Featured" if its purpose is to further reduce the minimal system. -5. A Server Role *must* have an identified point of contact that agrees to maintain the Server Role in Fedora. If this person or group becomes unresponsive, the Server Role will necessarily be demoted from Featured status. A Server role *must* be possible to trivially update to fix security vulnerabilities, and maintained to provide security fixes in a timely manner. -6. A Server Role *must* be installable without a local graphical utility. [Use Case 7] -7. If a Server Role packages multiple upstream projects together as a suite or solution, updates to any of these projects *must* be coordinated for concurrent release to allow testing of the complete system. -8. A Server Role *must* automatically use and sufficiently implement specified system-wide settings (e.g. a LDAP source for account information, CA certificates, and similar domain-originated or system-wide configuration) - -==== Conditional Requirements - -[IMPORTANT] -==== -This is not a list of things you should ignore. Rather, this is a list of things that if you implement them, you are committing that they must continue to behave that way in the future. -==== - -1. The Server Role *may* be packaged in such a way that it can be uninstalled as a complete unit. The mechanism to accomplish this removal must remain consistent. [Use Case 1] -2. The Server Role *may* provide a sane, usable default. If it does so, it must remain capable of accepting input through its configuration API to change this default. [Use Case 1] -3. The Server Role *may* provide an API to interrogate additional useful information about the running service(s) provided by the Server Role. The content here is up to the Server Role to define, but should be treated as stable (e.g an update should never remove the ability to monitor something). [Use Case 2] -4. The Server Role *may* provide a specification of its needed resources to the Fedora Server in a standard format. (e.g. Memory requirements) If this is provided, the Fedora Server *may* use this information to create isolated services such as VMs or containers in which to run the Server Role. [Use Case 4] -5. The Server Role may request operation in an isolated environment (with or without implementing Optional Requirement 4). If it does so, the Server Role must indicate (using a standard Fedora Server API) what form(s) of isolation it supports. Fedora Server must honor this. [Use Case 4] -6. A Server Role *may* provide a remote graphical (which includes web-based) configuration tool. -7. A Server Role *may* implement all of the other requirements by integrating with the Fedora Server-designated infrastructure (commands, APIs, and the like). This is preferred but not mandatory if the upstream provides a different way to achieve the same objective. - -== Logistical Concerns - -=== Delivery Mechanisms - -Fedora Server will produce two main installation resources, a netinstall image and an offline install iso image that allows one to install and configure featured roles offline. - -Supported installation methods: - -* Automated ("mass") install within a larger Linux infrastructure (e.g. PXE is an option, may have LDAP/IPA). -* Manual install without a supporting infrastructure (e.g. the very first Linux server). -* Where possible, existing servers and installed roles should be upgradable to new releases with minimal involvement by the admin. -* Individual roles should be installable at server install time (e.g. in Anaconda) and post-install. - -==== Where to obtain - -Users will be able to obtain these images from the Fedora Project website and mirror networks. - -=== Measuring Success - -In order to measure success we will monitor (somewhat arbitrary) numbers over time. The list of metrics we take in account will be adapted over time to measure specific efforts within the framework of the Server Working Group goals. - -The initial basic set of metrics will be: - -* Usage of Fedora Server images in AWS or other public cloud providers that publish such aggregated data. -* Number of contributors that explicitly contribute to the Fedora Server effort in some way. We'll try to gather data from sources that are easily measurable (commits, builds, etc..). -* Number of third party repositories or projects that decide to target Fedora Server. - -This last point may be a stretch goal - admittedly it will require some time before this becomes really measurable, but in a 2-year time frame this kind of adoption should be discernable. - -== About this Document - -=== Authors - -Contributors to this document include: - -* https://fedoraproject.org/wiki/User:Sgallagh[Stephen Gallagher] -* https://fedoraproject.org/wiki/User:Jperrin[Jim Perrin] -* https://fedoraproject.org/wiki/User:Davidstrauss[David Strauss] -* https://fedoraproject.org/wiki/User:Tuanta[Truong Anh. Tuan] -* https://fedoraproject.org/wiki/User:Duffy[Máirín Duffy] -* https://fedoraproject.org/wiki/User:Nirik[Kevin Fenzi] -* https://fedoraproject.org/wiki/User:Mitr[Miloslav Trmač] -* https://fedoraproject.org/wiki/User:Simo[Simo Sorce] -* https://fedoraproject.org/wiki/User:Adamw[Adam Williamson] -* https://fedoraproject.org/wiki/User:Jzb[Joe Brockmeier] - diff --git a/wg/modules/ROOT/pages/archive/product-requirements-document-2021.adoc b/wg/modules/ROOT/pages/archive/product-requirements-document-2021.adoc deleted file mode 100644 index 3b840b7..0000000 --- a/wg/modules/ROOT/pages/archive/product-requirements-document-2021.adoc +++ /dev/null @@ -1,170 +0,0 @@ -= Product Requirements Document - -[NOTE] -==== -This is the 2021 version of the document, finalized at the *IRC Working Group Meeting* on https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-06-23-16.59.html[June 23, 2021] and approved by *FESCo vote* as of https://pagure.io/Fedora-Council/tickets/issue/375[July 9, 2021]. -==== - -This document provides an overview of what Fedora Server Edition is, the goals and objectives, and what it is designed for. It is written from a user’s point of view to allow people to understand what the Server Edition should do, what it is useful for, and what to expect from it in the future. - -== Fedora Server Vision - -Fedora Server is a real-world incarnation of the https://docs.fedoraproject.org/en-US/project/[Fedora Project's vision] for organizations, individual users, and developers to develop, deploy, and maintain applications and services – freely, autonomously, and under their own control. - -== Fedora Server Mission - -*As a user, you gain the opportunity to use the server of the future right now.* - -Fedora Server provides a stable, flexible, and universally-adaptable base for the everyday provisioning of services and applications by organizations and individuals, based on the latest technology and is available quickly after the upstream releases. - -*As a developer or system integrator, you gain an eye on the server of the future.* - -Fedora Server is also a platform for developers and system integrators, which provides an implementation of the latest server technology for exploring and evaluating. - -== Market Opportunity - -The server operating system market is mature and yet, constantly evolving. The technologies that are in the midst of changing computing, such as e.g. cloud or containers, depend, at the end of the day, on servers running on bare metal and capable of handling the requirements of those technologies‘. - -Fedora Server, being a leading-edge Linux distribution, is the ideal place for developers, system administrators and DevOps specialists to keep up-to-date with these low-level technologies. Fedora Server provides the opportunity to explore these features and provide a stable place to deploy applications, both new and legacy. - -Fedora Server provides a stable foundation, with balanced resource utilization, yet delivering the latest technologies giving administrators every day exposure to the latest tooling as soon as it is usable. - -== Why use Fedora Server? - -Fedora Server has so many genuine advantages that it is hard to list them all. The nine most important ones are: - -* The twice-yearly, release cycle allows for the inclusion of the latest versions of system and application software almost immediately. Users and system administrators are empowered to swiftly respond to new market options and changing or expanding customer requirements. -* A sophisticated release and quality assurance process enables a high level of reliability and stability, despite the fast release cycle. This achieves an excellent balance between ‘bleeding edge’ and maturity for use in mainstream deployments. -* Fedora Server includes enterprise-grade security, resulting in carefully pre-configured releases, offering uncompromising security without extensive configuration work by system administrators. -* A great variety of available software, all included in that release process, opens up a wide range of possibilities for flexibility in building a server according to the specific needs and wishes of a customer or end-user. -* The latest, stable, modern system administration tools (e.g. cockpit) noticeably reduces the burden of system administration. -* Strict alignment with other Fedora editions as well as the twice-yearly releases are associated with less disruptive upgrades – several small updates are easier to manage than a few big ones. -* The upgrade process itself is very simple and straightforward, without requiring re-installation. Skipping one release is also viable, in case new capabilities are not immediately needed. All in all, Fedora is decidedly system administrator friendly. -* Fedora Server ensures utmost freedom from restrictions imposed by commercial interests or corporate feature management and excellent backwards hardware compatibility. -* Developers find an excellent development environment for the next generation server as well as application software with the latest software versions available. - -== Server Edition Objectives - -Fedora Server Edition offers a highly flexible and adoptable multi-purpose server platform, usable at every scale. - -* A platform for important infrastructure tasks and basic services (DNS, DHCP, FreeIPA, and others) -* A platform for various important, dedicated server applications (file/storage server, database server, user-developed web applications, etc.) -* A platform for deploying Infrastructure-as-a-Service systems for best deployment of Fedora Cloud images. -* A platform for deploying containerized applications supporting multiple container technologies, among which the system administrator can choose according to custom requirements. -* A platform for virtual machines, as host as well as guest system, supporting different technologies, among which the system administrator can choose according to custom requirements. -* Infrastructure to allow efficiently managing many servers as a single unit. The product only commits to producing basic tools, but the infrastructure will allow more advanced tools to be created. -* An operating platform capable to run any combination of forementioned services all according to very different needs of users rsp system administrators (multipurpose feature). - -Fedora Server can be used as a standalone server that runs an application or service as well as a member of a cluster in a data center. As a result of strict adherence to open standards, it natively cooperates with different server technologies and implementations. - -=== Additional Overall Objectives - -Aside from the adoption and development of the Fedora Server platform, we have additional goals that are fundamental in any case: - -* Security-minded: secure by design - extending into TPM support, disk encryption enablement -* Community-driven: Intense feedback about product direction and potential improvements. This is separate from “bug reports” in that we hope to engage the audience and receive detailed feedback about use cases, desired features, developing trends in cloud management, etc. We encourage more patches and contributions that will help improve the Server Edition, and Fedora in general. - -== Primary Use Cases, User Profiles, and most important Features - -=== Use Cases - -The Fedora Server will need to address the following use-cases: - -* On premise server for small and medium-sized enterprises hosting mail service, calendar, and branch specific (probably containerized) software – either single node deployment or multi-node deployment with automatic failover -* Dedicated SOHO server, ‘bare metal’ rented from a remote provider and under its own full control, offering various services. Public access through VMs for security reasons. -* Single node or multi-node deployment in an enterprise data center providing up-to-date software versions according to domain specific requirements in a stable and secure OS, capable to provide different runtime environments – native, VM, different container systems – driven by domain specific demands. -* Personal home server, located ‘on premise’ in own flat / house and used as NAS, backup device, and for applications such as mail repository, contact database, calendar, ebook library, media server, etc. -* Development box, providing developers with the latest software version and excellent developing tools - -=== User Profiles - -We will use a set of personas to describe our target users and their respective needs. We list the typical personas by brief title and a short list of key characteristics. - -==== System Administrator "Macgyver" - -* Administrator with limited hardware and personnel resources to work with -* Requires simple automation to cope with repetitive tasks -* Needs to be able to do “a lot with a little” - -==== DevOps Engineer/Administrator - -* Focus is on time-to-deploy and time-to-recover as opposed to uptime -* Value is achieved by delivering the latest capabilities fastest -* Needs to be able to deliver quickly to PaaS, SaaS and bare-metal servers - -==== Application Developer - -* Needs a platform with API and ABI stability guarantees -* Focus will be on minimizing risk when making changes -* Needs latest technology in virtualization and containerization -* Likes a platform similar to the workstation - -==== Decision Maker - -* Makes purchasing decisions and directs technology choices -* Interacts with upstream FOSS communities to identify potential value - -==== The Home Admin - -* I need a somewhat stable machine, with a graphical interface (Cockpit) and just want to start a couple of containers and/or virtual machines to have nextcloud running on it. -* I need some gitea here, some gitlab there, some jenkins, some photoprism, minecraft, etc. Can I build a NAS easily? -* I am ok with updates and reboots over night, but it should work. It would be awesome to have mDNS and a Web UI. - -==== The Hyperscaler - -* I treat my servers as “cattle, not pets”. Overall uptime is more important than individual server uptime -* I want to have a reliable platform for virtualization, core services and container. It should be out of my way, so I can focus on scaling, monitoring, implementation -* I want to automate server installation, and configurations for hostname, timeserver, hardening, etc. In addition I want to deploy typical services like mariadb, httpd, nginx, redis, nodejs, java, etc. in a reproducible way. To see what the machines are doing, I need a well documented way to manage, monitor and backup them. -* My Security Team also wants me to disable unneeded services, disable legacy protocols, enable hardening on several levels. - -==== The Remixer / "Let’s build upon it" - -* I love how Fedora works and I want to create something upon it. -* I need a very well documented build process and maybe tools to produce new install images -* Removing the branding should be possible with some compiler flags or variables, so I don’t need to mess with the code itself. -* I have a raspberry/intel nuc/etc. and playing a bit with new stuff. - -=== Most Important Features - -* The user can easily deploy and configure any supported Fedora Server application as well as rapidly re-deploy services in accordance with their DevOps practices. (Examples range from BIND DNS, DHCP, Database server, iSCSI target, File/Storage server, up to OpenStack Hypervisor Node, and the like) -* The user can query, monitor, configure and manage a Fedora Server and the resources consumed by services remotely using stable and consistent public interfaces. -* The user can deploy and configure Fedora Server to provide domain infrastructure with FreeIPA and Samba Active Directory solutions. Fedora Server can become Domain Controller in a newly established domain or join existing domain as a Domain Controller or a Domain Member. -* Users can create, manipulate and terminate large numbers of virtual machines and containers using a stable and consistent interface. -* The user is enabled to install and manage Fedora Server in a headless mode, either directly on the command line or supported by Cockpit, a lightweight Web GUI. - -== Logistical Concerns - -=== Delivery Mechanisms - -Fedora Server Edition produces two main installation resources, a netinstall image and an offline install iso image. - -Supported installation methods: - -* Automated (“mass”) install within a larger Linux infrastructure (e.g. PXE is an option, may have LDAP/IPA). -* Manual install without a supporting infrastructure (e.g. the very first Linux server). -* Existing servers should be upgradable to new releases with minimal involvement by the admin. - -Users will be able to obtain these images from the Fedora Project website and mirror networks. - -=== Documentation - -Fedora Server Edition documentation will be made available in a dedicated section of the Fedora documentation project. For selected topics, we strive for integration into the generic Fedora documentation. - -== About this Document - -This document resulted from a broad discussion of the Fedora Server Edition working group. Contributors include: - -* Alexander Bokovoy -* Peter Boy (editor) -* Davide Cavalca -* Kevin Fenzi -* Stephen Gallagher -* John Himpel -* David Kaufmann -* Jan Kuparinen -* Eduard Lucena -* Michel Salim -* Stephen Smoogen -* Langdon White -* Adam Williamson - diff --git a/wg/modules/ROOT/pages/archive/server-technical-specification-2014.adoc b/wg/modules/ROOT/pages/archive/server-technical-specification-2014.adoc deleted file mode 100644 index 248d117..0000000 --- a/wg/modules/ROOT/pages/archive/server-technical-specification-2014.adoc +++ /dev/null @@ -1,174 +0,0 @@ -= Fedora Server Technical Specification -The Fedora Server Edition Working Group -:revdate: 2014-11-06 - -[NOTE] -==== -.*This is an approved document* -It was originally approved by the Server Working Group on January 17, 2014, and by FESCo on January 22, 2014. - -It is now *archived* and no longer valid. -==== - - -[abstract] -This document aims to describe the technical characteristics of the Fedora Server product in detail. This includes provided services and APIs, installed software, and the like. Some of the desired characteristics may not be entirely achievable in the first version of the Server product, and will be approximated. - -The content of this specification unavoidably overlaps with the work of the Base Working Group, and needs to be aligned with their deliverables. - -== Core Services and Features - -This section should describe the core services of the platform and their intended use. The items here should refer back to the xref:archive/product-requirements-document-2014.adoc[Product Requirements Document (2014)] for a functional justification. - -=== Supported Architectures and Install Media - -Fedora Server will run on and provide install media for i686, x86_64, and armv7hl servers. - -There will be two official install media for the Fedora Server - -* A network installation media (either a traditional netinst.iso or a boot.fedoraproject.org style) -* A local installation media providing the default package set as well as any featured roles that are meaningfully installed without a network connection. -** The local installation media will be allowed a maximum size to fit on a 4.0GB USB device. -** The local installation media can be pointed at network resources to make available a larger package set. - -=== File system - -The default file system type for Fedora Server installs will be XFS running atop LVM for all partitions except /boot. The /boot partition will remain a non-LVM partition due to technological limitations of the bootloader. - -File-system layout will be discussed with the Anaconda team and reasonable defaults will be selected based on a combination of the number of available, selected disks and the available memory on the system (for determining SWAP space). - -An option will be provided in the Fedora Server installer to enable disk encryption. - -=== Service management - -Systemd provides ways to control and monitor the activity and status of system services, resources they require, and the like. System services must provide systemd units to be included in the Fedora Server standard installation. See the link:++http://0pointer.de/public/systemd-man/systemd.unit.html++[systemd documentation]. - -=== Logging - -Fedora Server will store log files locally by default and will also support sending full log data to an external server to the maximum extent possible. For writing to logs, we recommend the syslog or journal APIs rather than managing application-specific log files. OpenLMI will provide an API for reading the logs. - -We will use rsyslog for forwarding data to a central server. The logs of programs using the recommended APIs will be locally stored in the journal database and automatically forwarded; other programs should include appropriate configuration for rsyslog such that their log output is included in the rsyslog-forwarded data stream. - -=== Networking - -Network devices and connections will be controlled by NetworkManager by default. Server Roles that may need to interact with the network configuration must do so through the public NetworkManager D-BUS API. - -=== Firewall - -A firewall in its default configuration may not interfere with the normal operation of programs installed by default. - -On a pristine system, the only open incoming ports are SSH and Cockpit. When Roles are deployed, they may elect to open one or more ports based on the most likely need. Roles *must* provide an interface that describes which ports they want open and which ones they currently have opened. The admin must be able to easily modify this configuration. - -Roles that open ports by default must have the set of ports approved by majority vote of the Server Working Group. - -If the user hasn't specified firewall status explicitly, interactive role deployment will inform the user whether the service's ports have been opened by default. It must be possible to query the API for the required state of the firewall to support the role, which can then be compared to the active firewalld state. - -The OpenLMI project will provide a public, external API to manage firewalld centrally. (This is not yet scheduled for a Fedora release, but is a medium-term plan.) - -=== SELinux - -SELinux will be enabled in enforcing mode, using the targeted policy. The Fedora Server standard install and all promoted Server Roles must operate in enforcing mode. - -=== Problem reporting - -Problems and error conditions (e.g. kernel oopses, Selinux AVCs, application crashes, OOM, disk errors) should all be reported in the systemd journal. - -Support for sending this information to a central place (like abrt does for crashes today) is mandatory. - -=== Account handling - -SSSD will provide the backing storage for identity management. The Fedora Server is expected to nearly always be configured for 'centrally-managed' user information; it must be possible to configure it to rely on a directory service for this information. Fedora Server will provide and support the realmd project for joining FreeIPA and Active Directory domains automatically. Interacting with other identity sources will remain a manual configuration effort. - -=== Software updates - -Software updates on the Fedora Server must be possible to perform either locally using command-line tools (e.g. yum/dnf) or centrally by common management systems (e.g. Puppet, Chef, Satellite, Spacewalk, OpenLMI). - -=== Miscellaneous system information - -System locale, timezone, hostname, etc. will be managed through the services provided by systemd for this purpose. -See developer documentation for -link:++http://www.freedesktop.org/wiki/Software/systemd/localed/++[localed], -link:++http://www.freedesktop.org/wiki/Software/systemd/timedated/++[timedated] and -link:++[http://www.freedesktop.org/wiki/Software/systemd/hostnamed/++[hostnamed]. - -=== Virtualization - -libvirt-daemon will be used to manage virtualization capabilities. - -=== Accessibility - -Accessibility support on the Fedora Server will be limited to devices supporting the vision-impaired on the console. - -Accessibility support in the optional graphical environment will be aligned with the Fedora Workstation offering. - -=== Input Methods - -The input method support for the Fedora Server console access will be limited to LOCALE support in the command shell. - -Input method support in the optional graphical console will be aligned with the Fedora Workstation offering. - -=== Graphics and Display Manager - -The Fedora Server does not mandate a graphical environment at this time. If the administrator elects to install a desktop, they should choose a display manager themselves at this time. - -=== Appearance - -The default user-experience for the Fedora Server will be the bash shell on the console and the Cockpit web management console. - -=== System Installer - -The desired installation experience for the Fedora Server product is to limit the pre-installation user interaction to the minimum. The storage configuration UI should provide a single sensible default and an alternative, fully customizable configuration UI. - -Package selection will be supplementary. There will be no option in the installer to install less than the Fedora Server standard installation. Options to install Fedora Server Roles will be provided, as well as a UI to install other software from the Fedora Project repositories. - -Fedora Server will expect to be the sole citizen on the system. Support for coexisting with other operating systems is not a goal. - -Fedora Server will use kickstart as implemented by pyKickstart and Anaconda as the unattended installation mechanism. - -== Server Roles - -The Server Roles listed below are approved to be worked on in the Fedora 21 timeframe. - -The public D-BUS API to support Server Roles will be provided from the Cockpit Project. - -=== Role Definition Requirements -Roles will be required to provide both a D-BUS API and a web management plugin for the Cockpit management console. During the development of the first few Fedora Server Roles, the Cockpit project will drive the effort of designing this interface. - -Roles will be required to support the following API: - -* A mechanism to install the packages necessary to deploy the role. This may include an API for specifying optional components at this time. -* A mechanism to deploy a role whose packages are installed on the system by providing the necessary information to provision it. -* A mechanism to install optional components of a role after deployment. -* A configuration interface to modify high-level configuration options. -* A query interface providing metadata information about the role (not all roles must implement all parts of this, bold lines are mandatory): -** *A list of system services provided by the role, as well as data about whether those services are currently running (or enabled, in the case of socket-activated services)* -** *A list of the ports that the role operates on, as well as data about whether those ports are currently firewalled.* -** *A mechanism to open and close ports that the role operates on for some or all interfaces.* -** *If the Role is designed to operate on the network, it should automatically open those ports (see firewall during deployment.* -** A list of files on the filesystem that should be included in a backup set. -** An interface to set processor affinity, memory limits, etc. where sensible. -** Whether the role is running in a container. - -=== Supported Roles === - -==== Domain Controller - -The Fedora Server Domain Controller Role will be provided by the FreeIPA project. - -This Server Role is a blocker for the release of Fedora Server in Fedora 21. - -==== Database Server - -The Fedora Server Database Server will be provided by the PostgreSQL project. - -This Server Role is a nice-to-have for the release of Fedora Server in Fedora 21. - - - -== Core Package list - -List the core packages of the product. This list includes all packages that will be shipping on the core media. This is the mandatory minimal list of packages that needs to be installed on a system at all times for it to qualify as a Fedora Server install. This package list will be the priority focus for QA and bug fixing. - -=== Package list - - \ No newline at end of file diff --git a/wg/modules/ROOT/pages/docs/key-services-ansible-support.adoc b/wg/modules/ROOT/pages/docs/key-services-ansible-support.adoc deleted file mode 100644 index 309ab31..0000000 --- a/wg/modules/ROOT/pages/docs/key-services-ansible-support.adoc +++ /dev/null @@ -1,108 +0,0 @@ -= Facilitated deployment of key services by combining rpm and Ansible - -Goal is to explore *Ansible* to provide easy installation and pre-configuration for key services in Fedora Server Edition. It is all about improving, systematizing and simplifying its system management. - -This page is intended to organize and structure the discussion. It is work in progress, not documentation of finished procedures. - -It is intended to be uses as a kind of (simple) content federation tool. We specify items to discuss here, discuss on mailing list or IRC meetings and bring their results together here. - -== Use Cases – What do we want to achieve - -=== 1. Installation of (Java) Application Server - the Wildfly Example - -Specific stakeholders so far: pboy, jwhimpel - -==== Description - -Wildfly is an eminently important and widely used application on Fedora Server Edition. Unfortunately, experience has shown that building a wildfly rpm package is not feasible. This does not only apply to Fedora, but also to at least most, if not all other distributions. As a consequence, the system administrator not only has to perform the software configuration - which is already complex and extensive in itself - but also its installation, including the embedding into the server ''systemd'' runtime system. - -As a way out, many instructions for manual installation can be found, which follow different ways and installation systematics. Many are incomplete or even faulty and lead to system malfunctions. - -*Goal* is to ensure a systematic, reproduceable and smooth integration into the Fedora way of installing software. - -==== Tasks to Perform ==== - -* Installation of the appropriate Java version -* Installation of backend software, specifically a database (postgresql or an alternative) -* Deploying a systemd service configuration -* Download of Wildfly software from upstream -* Installation of Wildfly in an appropriate location -* Configure Wildfly as a standalone or domain service -* Managing updates -* Optionally connect Wildfly to a Web frontend (httpd) - -==== Implementation Notes - -* *Systemd Service*, could be a plain dedicated service created either via Ansible or as an rpm. Alternatively it could be a generic Java service addressable as jservice@wildfly, jservice@glassfish, etc. - -* *Software download*, one option is to provide a script that simple informs that an installation of the software is required to use it. it would be a similiar approach as the postgresql dbinit process. Another option is to provide a Ansible artifact that informs and asks for permission to download the software, alternatively to pick it up from a local storage, manually perpared by system administrator. - -* *Installation location*, generally _/opt_ would be appropriate. Another option to explore is to install wildfly as an unexpanded jar as a Java library file and inject links to /etc, /var/lib/webapps etc as java packages as tomcat would do. - -* An *Ansible role* for installing and configuring will be really ambitious. It has to ensure that all installations of this type follow the same principles and comply with the Fedora guidelines for installing Java software. - -* I would envision continuing using rpm packages (not coprs and not flatpacks) for basic software installation. I would envision a git-like repository maintained by the Fedora Server working group (along with other stakeholders) to provide the server-ansible-roles necessary to integrate all of the pieces together. The key to making all of this work is good, user-focused, up-to-date documentation on the wiki, web site and in the server-ansible-roles. - -==== Potential reasons for obstacles - -* Fedora policies (may) prohibit some steps or may require further adjustments - -==== Miscellaneous Notes - -* prebuilt containers as a stopgap option -** not everywhere a container is a good or even a feasible solution (administrative overhead, disposable strategy, additional workflow and build environment, etc.) - -=== 2. Installation of a complex service using different Fedora packages - the example Mail Service - -==== Description -A small site without an experienced Systems Administrator wishes to host their own email server. This would normally involve installing postfix, sendmail or some other Message Transfer Agent (MTA). It would also normally involve installing dovecot or some other Message Delivery Agent (MDA). While rpms exist for the above services, the rpms contain generic configuration files that require manual “tweaking” before the services will work together as one unit. - -One potential server-ansible-role might install the postfix rpm. Another server-ansible role might install the sendmail rpm. Yet another rpm might install the dovecot rpm. A yet-to-be-developed server-ansible-role might configure postfix and dovecot to work together. A second yet-to-be developed server-ansible-role might configure sendmail and dovecot to work together. - -The site may wish to only allow for secure transmissions between the MTA and the sending User Agent (UA) as well as between the MDA and the UA. That would involve installing the the certbot rpm, requesting the necessary certificates from the Letsencrypt CA, and configuring the MTA and MDA configuration files to provide secure transmissions. A server-ansible-role could do all of this assuming the MTA was postfix and another server-ansible-role could do all of this assuming the MTA was sendmail. - -The site may wish to implement Spamassassin, Clamav, DKIM, DMARC and SPF in a matter similar to that described above. - -Other possibilities include configuring the MTA and MDA to host multiple virtual domains and/or virtual users. This would require installing an RPM for a database of choice and making all the necessary configuration file changes required to integrate it into the sites MTA/MDA infrastructure. - -For a site considering migration from other OS’s to Fedora, completing this process could take days if not weeks. With all the old and outdated documentation on the web, it almost becomes a trial and error situation. With carefully crafted server-ansible-roles, it should be a matter of instructions on how to access the server-ansible-roles repository and providing well-documented defaults/main.yml and vars/main.yml files. The unfamiliar Systems Administrator then only needs to provide the site-specific values in the Ansible variables files. - -==== Miscellaneous Notes -* A mail service includes several different packages, e.g. Postfix, Dovecot, SpamAssassin, OpenDKIM, etc., which must be configured to work together. -* There are guides that often contain configuration instructions that do not apply to Fedora or packages for various reasons not available in Fedora -** *Goal* is to provide an easy way to a cross-package and coordinated configuration of a service. - -*Cons* - -* There are so many different possible Installation options -** We may need to develop different prototype use cases, each containing customization capabilities. - -== Linux System Roles - -There is a project that provides a collection of Ansible Playbooks for typical system administration tasks: -* https://linux-system-roles.github.io -* https://github.com/linux-system-roles -* https://ansible.github.io/workshops/exercises/ansible_rhel_90/6-system-roles/ - -Topics to discuss: - -. Do the scripts play well with Fedora Server? -. Do we want to encourage the use of those scripts and how? -. How can we make them (better) usable in Fedora Server? -. Can we use them as a kind of base library for more complex, cross-package services? -. What new system-roles can we provide? - -== Fedora Policy requirements - -Fedora policies impose requirements on artifacts that Fedora distributes. Obviously, some of the current rules are: - -* Helper rpms that only contain the systemd environment and an installation script do not comply with Fedora policy - -* Packaged Ansible roles, collections and things should be referencing packages and leverage Fedora content rather than external stuff -* Fedora containers as well should leverage Fedora content - -We need to investigate the regulations and analyze the possibilities they provide. - -== How to distribute / distribution options - -* downloadable from server-wg home page (??) \ No newline at end of file diff --git a/wg/modules/ROOT/pages/docs/product-requirements-document.adoc b/wg/modules/ROOT/pages/docs/product-requirements-document.adoc deleted file mode 100644 index b528d33..0000000 --- a/wg/modules/ROOT/pages/docs/product-requirements-document.adoc +++ /dev/null @@ -1,176 +0,0 @@ -= Product Requirements Document - -[NOTE] -==== -Updated document as finalized at the *IRC Working Group Meeting* on https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-06-23-16.59.html[June 23, 2021] and approved by *FESCo vote* as of https://pagure.io/Fedora-Council/tickets/issue/375[July 9, 2021]. Update was finalized at the *IRC Working Group Meeting* on https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-04-20-17.00.html[April 20, 2022]. Fesco approvement pending. -==== - -This document provides an overview of what Fedora Server Edition is, the goals and objectives, and what it is designed for. It is written from a user’s point of view to allow people to understand what the Server Edition should do, what it is useful for, and what to expect from it in the future. - -== Fedora Server Vision - -Fedora Server is a real-world incarnation of the https://docs.fedoraproject.org/en-US/project/[Fedora Project's vision] for organizations, individual users, and developers to develop, deploy, and maintain applications and services – freely, autonomously, and under their own control. - -== Fedora Server Mission - -*As a user, you gain the opportunity to use the server of the future right now.* - -Fedora Server provides a stable, flexible, and universally-adaptable base for the everyday provisioning of services and applications by organizations and individuals, based on the latest technology and is available quickly after the upstream releases. - -*As a developer or system integrator, you gain an eye on the server of the future.* - -Fedora Server is also a platform for developers and system integrators, which provides an implementation of the latest server technology for exploring and evaluating. - -== Market Opportunity - -The server operating system market is mature and yet, constantly evolving. The technologies that are in the midst of changing computing, such as e.g. cloud or containers, depend, at the end of the day, on servers running on bare metal and capable of handling the requirements of those technologies‘. - -Fedora Server, being a leading-edge Linux distribution, is the ideal place for developers, system administrators and DevOps specialists to keep up-to-date with these low-level technologies. Fedora Server provides the opportunity to explore these features and provide a stable place to deploy applications, both new and legacy. - -Fedora Server provides a stable foundation, with balanced resource utilization, yet delivering the latest technologies giving administrators every day exposure to the latest tooling as soon as it is usable. - -== Why use Fedora Server? - -Fedora Server has so many genuine advantages that it is hard to list them all. The nine most important ones are: - -* The twice-yearly, release cycle allows for the inclusion of the latest versions of system and application software almost immediately. Users and system administrators are empowered to swiftly respond to new market options and changing or expanding customer requirements. -* A sophisticated release and quality assurance process enables a high level of reliability and stability, despite the fast release cycle. This achieves an excellent balance between ‘bleeding edge’ and maturity for use in mainstream deployments. -* Fedora Server includes enterprise-grade security, resulting in carefully pre-configured releases, offering uncompromising security without extensive configuration work by system administrators. -* A great variety of available software, all included in that release process, opens up a wide range of possibilities for flexibility in building a server according to the specific needs and wishes of a customer or end-user. -* The latest, stable, modern system administration tools (e.g. cockpit) noticeably reduces the burden of system administration. -* Strict alignment with other Fedora editions as well as the twice-yearly releases are associated with less disruptive upgrades – several small updates are easier to manage than a few big ones. -* The upgrade process itself is very simple and straightforward, without requiring re-installation. Skipping one release is also viable, in case new capabilities are not immediately needed. All in all, Fedora is decidedly system administrator friendly. -* Fedora Server ensures utmost freedom from restrictions imposed by commercial interests or corporate feature management and excellent backwards hardware compatibility. -* Developers find an excellent development environment for the next generation server as well as application software with the latest software versions available. - -== Server Edition Objectives - -Fedora Server Edition offers a highly flexible and adoptable multi-purpose server platform, usable at every scale. - -* A platform for important infrastructure tasks and basic services (DNS, DHCP, FreeIPA, and others) -* A platform for various important, dedicated server applications (file/storage server, database server, user-developed web applications, etc.) -* A platform for deploying Infrastructure-as-a-Service systems for best deployment of Fedora Cloud images. -* A platform for deploying containerized applications supporting multiple container technologies, among which the system administrator can choose according to custom requirements. -* A platform for virtual machines, as host as well as guest system, supporting different technologies, among which the system administrator can choose according to custom requirements. -* Infrastructure to allow efficiently managing many servers as a single unit. The product only commits to producing basic tools, but the infrastructure will allow more advanced tools to be created. -* An operating platform capable to run any combination of forementioned services all according to very different needs of users rsp system administrators (multipurpose feature). - -Fedora Server can be used as a standalone server that runs an application or service as well as a member of a cluster in a data center. As a result of strict adherence to open standards, it natively cooperates with different server technologies and implementations. - -=== Additional Overall Objectives - -Aside from the adoption and development of the Fedora Server platform, we have additional goals that are fundamental in any case: - -* Security-minded: secure by design - extending into TPM support, disk encryption enablement -* Community-driven: Intense feedback about product direction and potential improvements. This is separate from “bug reports” in that we hope to engage the audience and receive detailed feedback about use cases, desired features, developing trends in cloud management, etc. We encourage more patches and contributions that will help improve the Server Edition, and Fedora in general. - -== Primary Use Cases, User Profiles, and most important Features - -=== Use Cases - -The Fedora Server will need to address the following use-cases: - -* On premise server for small and medium-sized enterprises hosting mail service, calendar, and branch specific (probably containerized) software – either single node deployment or multi-node deployment with automatic failover -* Dedicated SOHO server, ‘bare metal’ rented from a remote provider and under its own full control, offering various services. Public access through VMs for security reasons. -* Single node or multi-node deployment in an enterprise data center providing up-to-date software versions according to domain specific requirements in a stable and secure OS, capable to provide different runtime environments – native, VM, different container systems – driven by domain specific demands. -* Personal home server, located ‘on premise’ in own flat / house and used as NAS, backup device, and for applications such as mail repository, contact database, calendar, ebook library, media server, etc. -* Development box, providing developers with the latest software version and excellent developing tools - -=== User Profiles - -We will use a set of personas to describe our target users and their respective needs. We list the typical personas by brief title and a short list of key characteristics. - -==== System Administrator "Macgyver" - -* Administrator with limited hardware and personnel resources to work with -* Requires simple automation to cope with repetitive tasks -* Needs to be able to do “a lot with a little” - -==== DevOps Engineer/Administrator - -* Focus is on time-to-deploy and time-to-recover as opposed to uptime -* Value is achieved by delivering the latest capabilities fastest -* Needs to be able to deliver quickly to PaaS, SaaS and bare-metal servers - -==== Application Developer - -* Needs a platform with API and ABI stability guarantees -* Focus will be on minimizing risk when making changes -* Needs latest technology in virtualization and containerization -* Likes a platform similar to the workstation - -==== Decision Maker - -* Makes purchasing decisions and directs technology choices -* Interacts with upstream FOSS communities to identify potential value - -==== The Home Admin - -* I need a somewhat stable machine, with a graphical interface (Cockpit) and just want to start a couple of containers and/or virtual machines to have nextcloud running on it. -* I need some gitea here, some gitlab there, some jenkins, some photoprism, minecraft, etc. Can I build a NAS easily? -* I am ok with updates and reboots over night, but it should work. It would be awesome to have mDNS and a Web UI. - -==== The Hyperscaler - -* I treat my servers as “cattle, not pets”. Overall uptime is more important than individual server uptime -* I want to have a reliable platform for virtualization, core services and container. It should be out of my way, so I can focus on scaling, monitoring, implementation -* I want to automate server installation, and configurations for hostname, timeserver, hardening, etc. In addition I want to deploy typical services like mariadb, httpd, nginx, redis, nodejs, java, etc. in a reproducible way. To see what the machines are doing, I need a well documented way to manage, monitor and backup them. -* My Security Team also wants me to disable unneeded services, disable legacy protocols, enable hardening on several levels. - -==== The Remixer / "Let’s build upon it" - -* I love how Fedora works and I want to create something upon it. -* I need a very well documented build process and maybe tools to produce new install images -* Removing the branding should be possible with some compiler flags or variables, so I don’t need to mess with the code itself. -* I have a raspberry/intel nuc/etc. and playing a bit with new stuff. - -=== Most Important Features - -* The user can easily deploy and configure any supported Fedora Server application as well as rapidly re-deploy services in accordance with their DevOps practices. (Examples range from BIND DNS, DHCP, Database server, iSCSI target, File/Storage server, up to OpenStack Hypervisor Node, and the like) -* The user can query, monitor, configure and manage a Fedora Server and the resources consumed by services remotely using stable and consistent public interfaces. -* The user can deploy and configure Fedora Server to provide domain infrastructure with FreeIPA and Samba Active Directory solutions. Fedora Server can become Domain Controller in a newly established domain or join existing domain as a Domain Controller or a Domain Member. -* Users can create, manipulate and terminate large numbers of virtual machines and containers using a stable and consistent interface. -* The user is enabled to install and manage Fedora Server in a headless mode, either directly on the command line or supported by Cockpit, a lightweight Web GUI. - -== Logistical Concerns - -=== Delivery Mechanisms - -Fedora Server Edition generates installation resources for different scenarios - -* an offline install ISO image for a full local installation -* a net install ISO image for booting into an online installation -* a virtual disk image to be imported into a Fedora Server Edition KVM virtual environment -* a disk image for installation on supported aarch64 single board computers (SBC) - -Supported installation methods are: - -* Manual install without a supporting infrastructure (e.g. the very first Linux server). -* Automated (“mass”) install within a larger Linux infrastructure (e.g. PXE is an option, may have LDAP/IPA). - -Existing servers should be upgradable to new releases with minimal involvement by the admin. - -Users will be able to obtain these images from the Fedora Project website and mirror networks. - -=== Documentation - -Fedora Server Edition documentation will be made available in a dedicated section of the Fedora documentation project. For selected topics, we strive for integration into the generic Fedora documentation. - -== About this Document - -This document resulted from a broad discussion of the Fedora Server Edition working group. Contributors include: - -* Alexander Bokovoy -* Peter Boy (editor) -* Davide Cavalca -* Kevin Fenzi -* Stephen Gallagher -* John Himpel -* David Kaufmann -* Jan Kuparinen -* Eduard Lucena -* Michel Salim -* Stephen Smoogen -* Langdon White -* Adam Williamson - diff --git a/wg/modules/ROOT/pages/docs/server-governance-charter.adoc b/wg/modules/ROOT/pages/docs/server-governance-charter.adoc deleted file mode 100644 index 3de08ae..0000000 --- a/wg/modules/ROOT/pages/docs/server-governance-charter.adoc +++ /dev/null @@ -1,30 +0,0 @@ -= Federa Server WG Governance Charter -Stephen Daley; Peter Boy -:page-authors: {author}, {author_2} -:revnumber: all -:revdate: 2023-04-18 - - - -[abstract] -.*This is an approved document*, -It was originally approved by the Server Working Group on November 5, 2013, and by FESCo on November 6, 2013, The latest version was approved September 12, 2017. - - -This document describes the governing structure for the Fedora Server WG. - -== Membership - -The Fedora Server Working Group has a variable number of members. This group is primarily an organizational team; they exist solely to establish quorum during voting meetings. - -Any WG member may voluntarily exit their chair at any time. New members may be added to the Working Group by being nominated by an existing member, then getting a +1 vote and zero -1 votes from three existing members within a two-week period. After that window is up, the person is added to the group. - -The current composition of the Server Working Group can usually be found at the Server landing page. - -== Making Decisions - -Because Fedora is a global project, members of the working group may be distributed across multiple timezones. It may be possible to have real-time IRC meetings or Google+ hangouts, but in general we will conduct business on the mailing list or announce either IRC meetings or Google+ hangout events in advance should they take place. - -The Server Working Group strives to work on consensus and only vote on things where it’s clear people aren’t going to be convinced to agree. Many of our decisions can be made through "lazy consensus." Under this model, an intended action is announced on the mailing list, discussed, and if there is no controversy or dissenting views with a few days, simply done. - -For bigger issues, they must be discussed and voted on in a public IRC meeting. Public IRC meetings are generally held most weeks on Tuesdays at 4:00pm Eastern US time in link:https://web.libera.chat/?channels=#fedora-meeting[#fedora-meeting] on Libera. For an IRC meeting to be held, at least three Working Group members must be present. Votes are accepted by all participants in the meeting (not just those of Working Group members), so the community is highly encouraged to join. In the case where an interested party can not make it to a meeting, they can pre-vote via the mailing list. \ No newline at end of file diff --git a/wg/modules/ROOT/pages/docs/server-technical-specification.adoc b/wg/modules/ROOT/pages/docs/server-technical-specification.adoc deleted file mode 100644 index eb4a636..0000000 --- a/wg/modules/ROOT/pages/docs/server-technical-specification.adoc +++ /dev/null @@ -1,264 +0,0 @@ -= Fedora Server Technical Specification - -[NOTE] -==== -.*This is an approved document* -Updated version as finalized at the *Server Working Group IRC Meeting* on https://meetbot.fedoraproject.org/fedora-meeting/2022-08-17/fedora-server.2022-08-17-17.00.html[August 17, 2022] -==== - -[abstract] -This document aims to describe the technical characteristics and properties of the Fedora Server Edition in detail. This includes provided services, installed software, and the like. It also defines characteristics and features that are not yet or not fully implemented in the current Fedora Server Edition release. - - -== Preamble - -Fedora Server provides a stable, flexible, and universally-adaptable base for the everyday provisioning of services and applications by organizations and individuals, based on the latest technology and available quickly after the upstream releases. It aims to empower users to deploy the services they need, whether using proven mature techniques or current technical developments, under their own control and adapted to their own needs. For this purpose, it provides a broad spectrum of available techniques from which users can choose completely independently and without predetermined valuations. - -== Overview - -The specification defines implementation details, implementation variants, and especially extensions. They constitute a detailing and technical elaboration of the goals and principles as stated in the https://docs.fedoraproject.org/en-US/server-working-group/docs/product-requirements-document/[Fedora Server Product Requirements Document]. - -Specifically, it covers the following topics - -* *Core Features* -+ -describes the basic features and properities. They constitute the base system, which is installed by the (graphical) installer by default. -* *System Administration* -+ -describes properties and capabilities of the default administration interface -* *Advanced Features* -+ -describes additional features that are not part of the default (graphical) installation but require subsequent administrative action -* *Server Roles* -+ -describe various services which Fedora Server can validly and concurrently offer to users. Additionally, these are specifically supported by Ansible provided administratve assistance. - -The features and properties specified here are the basis for the specification of Fedora Server release criteria and release blockers. - -== 1. Core Features -This section describes the basic properties and features of the platform and their intended use. - -=== 1.1 Supported Architectures and Install Media - -Fedora Server will definitely run on and provide install media for x86_64 and aarch64 servers. The project may provide install media for additional architectures. But these are not part of standard quality management and may be available ephemerally. - -* A *network installation media* providing a minimal package set allowing to boot the system, connect to Internet and contact the Fedora media server to download packages to be installed. -* A *local installation media* providing the default package set as well as any featured services that are meaningfully installed without a network connection. - ** It can additionally point at network resources to make available an ever larger package set. - ** Nevertheless, this media should be friendly to regions with limited Internet connection stability and performance. Thus, it is a trade-off between completeness and practical download size.. -* A *virtual machine disk image* for simplified installation of Fedora Server Edition in a KVM virtual environment. The image reproduces the Server Edition completely and without restrictions, as far as features are usable in a virtual environment. -* A raw *aarch64 disk image* for installation on a Singe Board Computer (SBC). - -=== 1.2 File System and Storage Organization - -Fedora Server gives the highest priority to maximum reliability and security of data with a maximum of possible performance. - -To achieve this goal, Fedora Server encourages strict _separation of system and user data_ and encourages to further isolate user data, e.g. by services. Any system maintenance must be possible with the least risk of endangering or compromising user data (e.g. by temporarly unmounting) and an error somewhere on the local disk storage should remain as isolated as possible and without system-wide impact. - -Thus, Fedora Server Edition's _default installation_ - -* creates the necessary standard partitions to boot the server (BiosBoot, EFI, /boot) -* creates a Volume Group with one Logical Volume of a reasonable minimal size to accomodate the root file system and system files using _XFS_ -* leaves the remaining space untouched for customization by the system administrator for user data, services or other uses. The installer must also support the following common options - ** enlarge the one logical volume to accomodate custom data as well without any separation (_not recommended_) - ** create one or more logical volumes to accomodate custom data - ** or even create an additional Volume Group dedicated to custom data - -The installer also provides a custom partitioning interface to accommodate use cases beyond the scope of default partitioning. - -Additionally, the installer shall provide an option to enable disk encryption. - -=== 1.3 Basic service and daemon management - -Systemd provides ways to control and monitor the activity and status of system services, resources they require, and the like. All system services must provide systemd units to be included in the Fedora Server standard installation. - -=== 1.4 SELinux - -SELinux will be enabled in enforcing mode, using the targeted policy. It must fully protect any installable system component and functional application. - -Fedora Server Edition must include a user-friendly mechanism for identifying SELinux denials and find workarounds. Currently, Cockpit's SELinux module provides this functionality. - -Additionally, any Server Role we provide MUST also provide options to appropriately modify the system's SELinux configuration (adjusting booleans, for example). - -=== 1.5 Networking - -By default, NetworkManager controls and manages all network devices and connections. Any modifications or adjustments to the network configuration must use the NetworkManager configuration tools or the public NetworkManager D-BUS API. - -Installation or First Boot must create a permanent configuration file for each physical network device found, or at least a stub configuratin file. Primarily, DHCP is to be used and enabled if available. Both must allow the system administrator to customize the default configuration without restriction. - -=== 1.6 Firewall - -The default method in Fedora Server is _firewalld_. It is part of the basic initial installation and not deselectable. - -The default initial configuration must provide the highest security possible with the ability of remote administration. But it may not interfere with the normal operation of programs installed by default. - -Therefore, on a pristine default system, the only open incoming ports are SSH and Cockpit. - -Configuration of ssh allows root access only with key-based login, if at all. - -Additionally, any Server Role we provide MUST also provide options to appropriately display and modify firewalld's configuration options. - -=== 1.7 Account handling - -SSSD will provide the backing storage for identity management. The Fedora Server is expected to nearly always be configured for ‘centrally-managed’ user information; it must be possible to configure it to rely on a directory service for this information. Fedora Server will provide and support the realmd project for joining FreeIPA and Active Directory domains automatically. Interacting with other identity sources will remain a manual configuration effort. - -=== 1.8 Logging - -Fedora Server uses systemd-journald and rsyslog for system logging. It's recommended all applications submit logs to systemd-journald. - -It stores log files locally by default and also supports sending full log data to an external server to the maximum extent possible. It uses rsyslog for forwarding data to a central server. - -=== 1.9 Miscellaneous System Information - -System locale, timezone, hostname, etc. will be managed through the services provided by systemd for this purpose, specifically - -* localed: localectl -* timedated: timedatectl -* hostnamed: hostnamectl - -=== 1.10 System Installer - -The desired installation experience for the Fedora Server product is to limit the pre-installation user interaction to the minimum. The storage configuration UI does provide a single sensible default and an alternative, fully customizable configuration UI. - -Package selection will be supplementary. - -Fedora Server expects to be the sole citizen on the system. Support for coexisting with other operating systems is not a goal. - -Fedora Server supports kickstart as implemented by pyKickstart and Anaconda as the unattended installation mechanism. - - - -== 2. System Administration - -=== 2.1 Appearance - -The primary system management tool is CLI using bash on a system console. Locally, the default Fedora Server boots to a text terminal login screen. It expects the system administrator to type the required commands or using bash scripts or to use Ansible roles and plays. - -The local login prompt must also display any appropriate information needed to establish remote administration of the system, in particular, Cockpit's access URL (see next paragraph). - -For remote installation, ssh and sftp are installed and activated by default. Additionally, Cockpit is installed and activated by default and provides a Web based graphical Interface to assist remote system administration. - -The Fedora Server does _not provide a local graphical environment_. If the administrator elects to install a desktop, they should choose and install a display manager themselves. - -=== 2.2 Input Methods - -The input method support for the Fedora Server console access is the LOCALE support in the command shell. - -=== 2.3 Accessibility - -Accessibility support on the Fedora Server will be limited to devices supporting the vision-impaired on the console. - -=== 2.4 Software updates - -Software updates on the Fedora Server must be possible to perform either locally using command-line tools (dnf), remote using _ssh_ or _Cockpit_, or centrally by common management systems (e.g. _Satellite_, _Ansible_). - -=== 2.5 Problem reporting - -Problems and error conditions (e.g. kernel oopses, Selinux AVCs, application crashes, OOM, disk errors) should all be reported in the systemd journal. -Support for sending this information to a central place (like abrt does for crashes today) is mandatory. - - - - -== 3. Advanced Features - -=== 3.1 Virtualization - -==== 3.1.1 KVM / Libvirt - -libvirt-daemon will be used to manage virtualization capabilities. - -==== 3.1.2 XEN based Virtualization - -XEN based Virtualisation is available in Fedora and installable with Fedora Server. While it may work, Xen virtualization is not officially supported on Fedora Server. - -=== 3.2 Containerization - -Fedora Server Editions does support various different container technologies. - -==== 3.2.1 Podman Application Container -Podman must be installable and usable right out of the box. - -==== 3.2.2 Systemd-nspawn System- and Application Container -A systemd-nspawn container must be installable and usable right out of the box. - - -==== 3.2.3 Libvirt LXC System Container -A Libvirt LXC container must be installable and usable right out of the box. - -== 4. Server Roles - -Server Roles are a high level set of software services with additional administrative support to smoothness integrate into Fedora Server Edition and validated to operate concurrently and conflict-free in Fedora Server. An example is Mail Service, that includes various system services as postfix, dovecot and alike. - -Server Roles are supposed to get developed in the Fedora 37 – 40 time frame. - -=== 4.1 Server Roles Requirements - -Supported Server Services are supposed facilitate the following functions - -* A mechanism to install the packages necessary to deploy the service. -* A mechanism to deploy a service whose packages are already installed on the system by providing the necessary information and procedures to provision it. -* A mechanism to install optional components of a service after deployment. -* A configuration interface to modify high-level configuration options. -* A helper tool (preferrable based on LVM snapshot) to perform a backup or alternativ a list of files on the filesystem that should be included in a backup set. - -Depending on practical experience, Server Roles may additionally need a query interface providing metadata information about the service (not all services must implement all parts of this): - - * A list of system services provided by the Supported Server Service, as well as data about whether those services are currently running (or enabled, in the case of socket-activated services) - * A list of the ports that the role operates on, as well as data about whether those ports are currently firewalled. - * A mechanism to open and close ports that the server service operates on for some or all interfaces. - * If the Server Service is designed to operate on the network, it should automatically open those ports (see Firewall) during deployment. - * An interface to set processor affinity, memory limits, etc. where sensible. - -=== 4.2 Server Role Administration - -Ansible is the projected administration tool. - -=== 4.3 Projected Server Roles - -==== 4.3.1 Domain Controller - -The Fedora Server Domain Controller Service will be provided by the FreeIPA project. -This Server Service is a blocker for the release of Fedora Server. - -==== 4.3.2 Database Management System (DBMS) - -The Fedora Server Database Management Systemn is provided by the PostgreSQL project. -This Server Service is a blocker for the release of Fedora Server. - -==== 4.3.3 Local Network File Server service - -The Fedora Server Fileservice will be provided by the Samba project. - -==== 4.3.4 WEB Server service - -The Fedora Server Web Server will be provided by the Apache project. - -==== 4.3.5 Web Application Server service - -The Fedora Server Web Application Server service will be provided by the Wildfly project. - -==== 4.3.6 Mail Service - -The Fedora Server Mail Service will be provided by the Postfix project and supporting projects like Dovecot, Spamassassin, Dkim, etc. - -== 5. Appendix - -=== 5.1 Core Package list - -This list includes all packages the core media are shipping with the current release. It is the _mandatory minimal list of packages_ that needs to be installed on a system at all times for it to qualify as a _Fedora Server_ install. This package lists the priority focus for QA and bug fixing. -To produce the list, issue the following command: - -_TBD_ - -=== 5.2 Authors - -Contributors to this document include: - -* Stephen Gallagher (sgallagh) -* Peter Boy (pboy) -* Jason Beard (cooltshirtguy) -* John Himpel (jwhimpel) -* Chris Murphy (cmurf) -* Emmanuel Seyman (eseyman) -* Adam Williamson (adamw) diff --git a/wg/modules/ROOT/pages/index.adoc b/wg/modules/ROOT/pages/index.adoc deleted file mode 100644 index 2554963..0000000 --- a/wg/modules/ROOT/pages/index.adoc +++ /dev/null @@ -1,77 +0,0 @@ -= Fedora Server Working Group -The Fedora Server Edition working group; Peter Boy (pboy); Stephen Daley (mowest) -:page-authors: {author}, {author_2}, {author_3} -// :revnumber: all -:revdate: 2024-03-18 - -:page-authors: {author} - -image::Banner_serverwg-768x325.png[Server] - -[NOTE] -==== -We are currently in the process to migrate our pages from Wiki to the new Fedora docs location. The information here is not yet complete. For the time being you may refer to our https://fedoraproject.org/wiki/Server[Wiki] as well. -==== - -The Fedora Server Working Group is the team of people working on putting together the Fedora Server Edition, the official Fedora server distribution. You can read https://lists.fedoraproject.org/pipermail/server/2013-October/000222.html[the initial announcement] of this initiative in the mailing list archive. - -Here you will find information about the overall ideas and goals behind Fedora Server Edition, who is working on it, how the work is organized and how we ensure long-term reliability, attractiveness and availability. And, of course, you can learn where and _how you can contribute_ to Fedora Server Edition and _become a member_ of our team. - -**Everyone interested in Fedora Server Edition is cordially invited**. - -[NOTE] -==== -Here you will not find any user documentation for Fedora Server Edition, nor any information on why and how to employ a Fedora Server. We maintain a dedicated https://docs.fedoraproject.org/en-US/fedora-server/[Fedora Server user documentation] for that purpose. -==== - -== Our vision -Anyone should be able to confidently obtain, configure and deploy software services that address their needs using readily-available and trustworthy recipes. (https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-06/serversig.2016-09-06-20.00.html[September 6, 2016 meeting]). - -== Our mission - -Fedora Server Edition is an ecosystem ideal for creating and operating validated service roles addressing most computing needs (https://meetbot.fedoraproject.org/fedora-meeting-1/2016-09-06/serversig.2016-09-06-20.00.html[September 6, 2016 meeting]). - - -== Currently ongoing and long term work projects - -. xref:docs/key-services-ansible-support.adoc[Facilitated deployment of key services by combining rpm and Ansible] -. https://pagure.io/fedora-server/issue/88[Review installation media] -. Testing Release 40 - -== Planned work projects - -. Improved support for off-premise Kickstart and pxe installation -. Revisiting defaults... filesystem/partitioning -. Easy integration into multi-node environments with tools like Ansible - -== Completed or deferred work projects - -1. xref:docs/product-requirements-document.adoc[Revision of the Fedora Server 'Product Requirement Document' (PRD)] (finalized IRC 2021-06-23) -2. https://pagure.io/fedora-server/issue/68[Explore opportunities for cooperation with Cloud WG / SIG] -3. xref:archive/initial-docs-plan.adoc[Buildup of a renewed documentation on Fedora Server specific topics] (finalized end of 2021) -4. https://pagure.io/fedora-server/issue/53[Facilitated and improved support for Fedora Server Edition VMs] (finalized mid 2022) - -== You are welcome to join and to contribute - -You don’t have to be a programmer, a developer or a technical nerd to contribute to the development of Fedora Server. We are especially interested in feedback from our users and potential new users. - -* Please, tell us about your usage of Fedora Server -* Tell us about the problems you faced and how you solved them - -Use one of the options below! - -=== Getting in touch - -1. Using the *mailing list* at server@lists.fedoraproject.org is probably the easiest and most efficient method. Each member of the group has signed up and keeps an eye on it. Everyone can see the list and look at it. You only have to subscribe to the list to write a message. - -2. Another good option is to join one (or more) of our regular chat meetings. We currently meet regularly *every 1st and 3rd Wednesday* on Matrix, room 'https://chat.fedoraproject.org/#/room/#meeting:fedoraproject.org[Fedora Meeting]'. You need to login with your _Fedora account_. -+ -The meeting time varies between summer and winter time. It is *18:00 UTC for winter* time and *17:00 UTC for summer* time. In this way, the local time remains constant for countries with a time changeover. This currently applies to all members of the Working Group. You may check your local time using e.g. `date -d '2021-11-17 17:00UTC'` on your Fedora Server terminal. -+ -Either introduce yourself at the beginning during 'roll call' and and we can arrange how to do things. Or simply wait for the last topic, which is usually "open floor". Take this opportunity to ask your question, make an announcement, etc. But sometimes we are short of time here. So the former option could be better. - -3. Another option is to post in our matrix room 'https://chat.fedoraproject.org/#/room/#server:fedoraproject.org[Server]'. You must also be logged in to do this. Keep in mind that this is a synchronous communication channel and not everyone is online all the time. So it may take a while for someone to reply. -+ -We also have an IRC chat channel at #fedora-server@irc.libera.chat. You just need to join the fedora channel and can visit any group. It's a very quiet channel today, where Fedora has switched to Matrix as the main communication channel. Be patient. It may take some time until someone does notice it and will answer. Mind you, IRC is a slow, calm medium. - -__Don't hesitate to make contact__! We are an open minded and friendly community of people with a great variety of skills, interest, and capabilities – by no way a closed bunch of oddball, highly technical nerds. diff --git a/wg/modules/ROOT/pages/usr-docs-maintenance/index.adoc b/wg/modules/ROOT/pages/usr-docs-maintenance/index.adoc deleted file mode 100644 index 2b648b5..0000000 --- a/wg/modules/ROOT/pages/usr-docs-maintenance/index.adoc +++ /dev/null @@ -1,75 +0,0 @@ -= User Documentation Maintenance -The Fedora Server Edition working group; Peter Boy (pboy); Stephen Daley (mowest) -:page-authors: {author}, {author_2}, {author_3} -// :revnumber: F37-F38 -:revdate: 2023-04-24 - -== Goals - -We want to and maintain a Fedora Server Edition user documentation and keep it up to date on an ongoing basis that - -* focuses on the specific features and procedures of the Fedora Server Edition -* also includes brief explanations and rationales that convey the meaning and underlying concepts -* contains copy-and-paste capable instructions that allow even less experienced administrators to operate safely and reliably -* refers to the upstream documentation for general information, where available - -== Organization - -Fedora uses Antorra CMS to create the documentation WEB site and stores all documents in various git repositories. The Fedora Server documentation is part of the link:https://pagure.io/fedora-server[Fedora Server repository] in the docs subdirectory. - -The pubic user documentation is available at https://docs.fedoraproject.org/en-US/fedora-server/ - -== Contributions - -Authors as well as users should be able to contribute to Fedora Server documentation with as little effort as possible and without technical hurdles. We provide several ways to contribute. - -1. The most common way for casual contributions is to open a ticket and describe the issue, and maybe to make a proposal. -2. Edit the page in question using a Web-based page editor. -3. Set up and work in a local authoring environment on your desktop. -4. You may send us an email, e.g. while reading a document on our Web pages. -//5. You may download a document, make changes and send it back. - - -=== Open a ticket (problem report) - -When reading a document, you see a "bug" button on the rightmost side below the blue top bar. Click it and you are forwarded to create an issue. Members of the Working Group are notified and will take care of it. However, you must have a Fedora account, so you can log in. - -=== Edit a page via a Web Editor - -Besides the aforementioned "bug" button there is a button that stylizes pen and note. It leads to a web-based editor that can be used to make changes to this very page. These are not applied directly, but members of the documentation team are notified for a review. Detailed information coming soon. - -=== Working in a local authoring environment - -For longer-term engagement, it makes sense to set up a complete authoring environment. It requires some preparations, but it provides the most powerful set of tools. A separate page will provide detailed information. - -=== Sending an email - -If you can't use any of the above options because you don't have a FAS account, you can just write your suggestions or feedback in an email to the Fedora Server list, server@lists.fedoraproject.org, or post a message on our link:https://discussion.fedoraproject.org/tags/c/project/7/server-wg[discussion board]. You have to register, but it is less effort than creating a FAS account. It's best to use a form like "current version" - "proposed version". Suggestions will then be included in the text, or perhaps there will be follow-up questions. - -== Quality assurance - -Prior to publication, each article should be reviewed. Such articles are available in our link:https://docs.stg.fedoraproject.org/en-US/fedora-server/[staging area] and marked as "awaiting review" or similar. - -Reviewer should: - -* check for technical and content accuracy. Contact the author in case of questions. -* check spelling and syntax -* refine the wording and phrases, especially in the case of non-English speaking authors - -The link:https://docs.stg.fedoraproject.org/en-US/fedora-server/[staging area] also contains articles at an early stage of development, allowing for early subject matter exchange and idea collection. - -Furthermore, the published pages are mirrored, giving a complete impression of the later documentation. - - -== Guidelines - -The article link:https://opensource.com/article/20/4/documentation?utm_campaign=intrel[What is good documentation for software projects?] provides a good summary of what we want to achieve with documentation, although it is not entirely new. - -Some pointers for articles: - -* Include of author(s), date of creation, last update, and the Fedora version used to test the examples. -* Start with a short summary of the subject matter, objective and desired outcome. (one paragraph of 2-3 sentences) -* Divide longer sequences into sections with subheadings and short explanations. -* Provide each step with a brief explanation/justification, if possible, a general instruction structure and a concrete example. - - diff --git a/wg/modules/ROOT/pages/usr-docs-maintenance/local-authoring.adoc b/wg/modules/ROOT/pages/usr-docs-maintenance/local-authoring.adoc deleted file mode 100644 index 62d8b54..0000000 --- a/wg/modules/ROOT/pages/usr-docs-maintenance/local-authoring.adoc +++ /dev/null @@ -1,141 +0,0 @@ -= Setting up a local authoring environment -The Fedora Server Edition working group; Peter Boy (pboy); Stephen Daley (mowest) -:page-authors: {author}, {author_2}, {author_3} -// :revnumber: F37-F38 -:revdate: 2023-04-23 - -Fedora Server documentation is at: https://pagure.io/fedora-server/. - -It includes the content as well as various scripts to build and preview the site locally. The directory structure is predefined by the docs Content Management System (Andorra) and must not be changed. - -It has 2 permanent branches: "main" for the published content and "stg" for planning, development, and discussion. Temporarily, additional branches may also be present. - -For up- and download you can use either https or ssh. For people with FAS account ssh may be more convenient. - -The workflow folllow the Fedora docs project "[https://docs.fedoraproject.org/en-US/fedora-docs/contributing/git/ Git for docs writers]". Each contributor should create a fork of the repository for themselves. Contributions are uploaded to the fork and then transferred to the authoritative version via a pull request. This opens up the possibility for others to comment and initiate a broader discussion. - -== Writing tools - -You can use any ASCII editor to work on the documentation files. - -A particularly useful OSS Asciidoc editor is https://asciidocfx.com[AsciidocFX]. It is a Java program, very easy to install, and provides both an integrated directory access, a toolbar with the most common AsciiDoc formatting similar to a Word editor and an integrated instant preview. - -== Creating a new documentation article - -An xref:attachment$srv-template.adoc[annotated template] is available to make things easier. Download it and save it in the appropriate directory with a new name. - -If possible, the files should be named in such a way that related files appear together in the directory listing. The most important, most differentiating parts should be at the front. For example - -* filesharing-nfs-administration.adoc -* filesharing-nfs-installation.adoc -* filesharing-samba-administration.adoc -* filesharing-samba-installation.adoc - -The titles should follow this pattern as far as possible and avoid redundant parts such as "How to install ..." - -* File sharing with NFS - Installation -* File sharing with NFS - Administration -* File sharing using Samba - Installation -* File sharing using Samba - Administration - -All file names are in lower case. - - -== Preparations - -1. *Create a local subdirectory* where the files of the documentation should be stored, and make it your default. We use fedora-server-docs in your home directory throughout this guide -+ - […]$ mkdir ~/fedora-server-docs - […]$ cd ~/fedora-server-docs - -2. Still in your default working directory, *clone fedora-server* repository -+ - […]$ git clone https://git@pagure.io/fedora-server.git -o upstream -+ -Git will copy the complete server repo including all branches, specifically "main" and "stg" mentioned above, into a local repo on your local workstation (into _.git/_ located in your default directory). -+ -Git does "tag" the cloned repo as remote repo "*upstream*". -+ -At the same time it checks out the default branch "''main''" into your ''working directory'' (i.e. ~/fedora-server-docs in the above example). Therefore, when the operation terminates, you will find in your current default directory, which is now your ''working directory'', some files, e.g. README.md, docsbuilder.sh and preview.sh and a directory docs. The latter contains the content. -+ -If you leave off "./" at the end, git creates another directory in your default directory with the name of the repository, i.e. fedora-server. And this directory is then the "_working directory_" to the repository. This can be useful if you want to keep track of different fedora docs projects in one directory. - -3. In your browser go to https://pagure.io/fedora-server/, log in and *create a Fork*. Once you have done it, the button will read _View fork_. Switch to your fork and click on Clone and you will see 2 addresses you can use to clone (copy) the content to your local default directory -+ - ssh://git@pagure.io/forks/[MY_FAS]/fedora-server.git - https://git@pagure.io/forks/[MY_FAS]/fedora-server.git -+ -Still in your default working directory, add the forked Repo to your remote repos. -+ - […]$ git remote add origin ssh://git@pagure.io/forks/[MY_FAS]/fedora-server.git -+ -You can use https as well. For users with a FAS account ssh is usually the better choice. - -4. You have now 2 remote repos defined. Check: -+ - […]$ git remote -v - origin ssh://git@pagure.io/forks/[MY_FAS]/fedora-server.git (fetch) - origin ssh://git@pagure.io/forks/[MY_FAS]/fedora-server.git (push) - upstream https://git@pagure.io/fedora-server.git (fetch) - upstream https://git@pagure.io/fedora-server.git (push) -+ -In your workflow you will update your local version to the latest versions of the server repository by "pulling" the content from "upstream" and upload your modifications and additions by "pushing" it to origin, i.e. to your fork. You will than create a "pull request", i.e. pick up your modifications and additions from your fork and integrate it into the generic repository ("origin"). This enables co-writers to review our work and comment on it. - -5. In your working directory build the local version and start the preview tool. -+ - […]$ ./docsbuilder.sh - -6. Back in your browser enter the *local preview address*': _localhost:8080_ -+ -* You should see a local preview of the current Server documentation - -== Working on content - -1. Check if you are on the branch you intend to work on -+ - […]$ git branch - main - * stg - -2. If not, switch to the branch you want to use. -+ - […]$ git checkout [stg|main] -+ -Git will adjust and modify the content of your working directory accordingly! - -3. Before your begin to work update your working directory -+ - […]$ git commit -m "" - -4. Modify content - -5. Update preview and check: -+ - […]$ ./docsbuilder.sh -+ -Preview in your browser using the address _'localhost:8080_ - -6. Repeat step 4 & 5 as required. - - -== Save Your Work - -Commit your work locally and then push it into your fork "_origin_". - -1. Check status -+ - […]$ git status - -2. Add files to commit stage as appropriate -+ - […]$ git add - -3. Commit locally -+ - […]$ git commit -m "" - -4. Transfer your fork of fedora server to the repository -+ - […]$ git push origin [main|stg] - -5. In your browser open https://pagure.io/fedora-server, login, switch to your fork and create a pull request. diff --git a/wg/modules/ROOT/pages/usr-docs-maintenance/webui-page-editor.adoc b/wg/modules/ROOT/pages/usr-docs-maintenance/webui-page-editor.adoc deleted file mode 100644 index 8b13473..0000000 --- a/wg/modules/ROOT/pages/usr-docs-maintenance/webui-page-editor.adoc +++ /dev/null @@ -1,22 +0,0 @@ -= Working with the Web based Page Editor -The Fedora Server Edition working group; Peter Boy (pboy); Stephen Daley (mowest) -:page-authors: {author}, {author_2}, {author_3} -// :revnumber: F37-F38 -:revdate: 2023-04-24 - -As an example, you may want to propose a modificaten of the local interactive installation guide. - -image::archive/webui-editor-0010.png[Editor button] - -At the top you see an editor button. It opens the pagure web page editor. - -image::archive/webui-editor-0020.png[Fork & Edit button] - -Before you can do anything, you have to log in with your Fedora account. Then, the option Fork and Edit gives you the option to directly modify the page content. - -The Fedora Server Edition working group and Pagure follow the "Pull Request Workflow". According to this, no one is supposed to change a published page immediately, but the workflow creates a copy of the page under your name (the "fork") and when you are done, the community is informed about your proposal (the pull request, or PR for short). The community can discuss the proposal and after agreement the administrator can "pull in" the proposal. The process is also known as "merge request" (MR). - -The pagure Web Editor takes care of all the details "behind the scenes". You don't need to worry about it. Just proceed to edit the page. - -More details to follow soon. - diff --git a/wg/modules/ROOT/pages/wg-communicating.adoc b/wg/modules/ROOT/pages/wg-communicating.adoc deleted file mode 100644 index 1a35055..0000000 --- a/wg/modules/ROOT/pages/wg-communicating.adoc +++ /dev/null @@ -1,25 +0,0 @@ -= Communicating and Meeting -Peter Boy, Stephen Daley -:page-authors: {author} - -[NOTE] -==== -**Work in Progress** Status: Migrating from WIKI -==== - -The Fedora Server Edition Working Group uses various resources - -* Mailing list: server@lists.fedoraproject.org -* IRC: #fedora-server on irc.libera.chat -* Blog: http://fedoramagazine.org/ -* Tickets: https://pagure.io/fedora-server - -== Meetings -* The Server working group meets twice-monthly *every 1st and 3rd Wednesday at 17:00 UTC* in #fedora-meeting on irc.libera.chat. Please, check your local time using e.g. `date -d '2021-11-17 17:00UTC'` -* Each meeting is announced in the Fedora Project Calendar: https://calendar.fedoraproject.org/server/ -* The agenda is announced on the server mailing list server@lists.fedoraproject.org and available from the ticket system at https://pagure.io/fedora-server/report/Meeting -* If there is no agenda, the meeting will be cancelled and the organisator /chair will send out a cancellation notice to the mailing list. -* During meetings, silence indicates consent. If people disagree, then that will bring it to a vote. -* In the case where a voting member can not make a meeting where a vote is scheduled to happen, they can either pre-vote via the mailing list or abstain-by-default. -* After meetings, meeting minutes will be sent to the https://lists.fedoraproject.org/mailman/listinfo/server[server mailing list]. - diff --git a/wg/modules/ROOT/pages/wg-members.adoc b/wg/modules/ROOT/pages/wg-members.adoc deleted file mode 100644 index 1266401..0000000 --- a/wg/modules/ROOT/pages/wg-members.adoc +++ /dev/null @@ -1,33 +0,0 @@ -= Members -Stephen Daley, Peter Boy -// :page-authors: {author} - -* link:https://fedoraproject.org/w/index.php?title=User:Cooltshirtguy[Jason Beard] (**__cooltshirtguy__**) -* link:https://fedoraproject.org/wiki/User:Abbra[Alexander Bokovoy] (**__abbra__**) -* link:https://fedoraproject.org/wiki/User:Pboy[Peter Boy] (**__pboy__**) -* link:https://fedoraproject.org/wiki/User:Fcami[François Cami] (**__fcami__**) -* link:https://fedoraproject.org/wiki/User:Dcavalca[Davide Cavalca] (**__dcavalca__**) -* link:https://fedoraproject.org/w/index.php?title=User:Mowest[Stephen Daley] (**__mowest__**) -* link:https://fedoraproject.org/wiki/User:Nirik[Kevin Fenzi] (**__nirik__**) -* link:https://fedoraproject.org/wiki/User:Sgallagh[Stephen Gallagher] (**__sgallagh__**) -* link:https://fedoraproject.org/w/index.php?title=User:Jwhimpel[John Himpel] (**__jwhimpel__**) -* link:https://fedoraproject.org/wiki/User:Ngompa[Neal Gompa] (**__ngompa__**) -* link:https://fedoraproject.org/wiki/User:Astra[David Kaufmann] (**__astra__**) -* link:https://fedoraproject.org/wiki/User:Copperi[Jan Kuparinen] (**__copperi__**) -* link:https://fedoraproject.org/wiki/User:X3mboy[Eduard Lucena] (**__x3mboy__**) -* link:https://fedoraproject.org/wiki/User:Salimma[Michel Alexandre Salim] (**__salimma__**) -* link:https://fedoraproject.org/wiki/User:Eseyman[Emmanuel Seyman] (**__eseyman__**) -* link:https://fedoraproject.org/wiki/User:Adamw[Adam Williamson] (**__adamw__**) -* link:https://fedoraproject.org/wiki/User:Langdon[Langdon White] (**__langdon__**) - -== Meetings - -* The Server working group meets twice-monthly every 1st and 3rd Wednesday at 17:00 UTC in #fedora-meeting on irc.libera.chat. -* ical: https://calendar.fedoraproject.org/server/ (prefer this source; the wiki sometimes gets out of date, but we keep that meeting correct to reserve the meeting channel). - -== Server Working Group Resources - -* Mailing list: server@lists.fedoraproject.org -* IRC: #fedora-server on irc.libera.chat -* Blog: http://fedoramagazine.org/ -* Tickets: pagure.io/fedora-server \ No newline at end of file diff --git a/wg/modules/ROOT/pages/wg-minutes-2013.adoc b/wg/modules/ROOT/pages/wg-minutes-2013.adoc deleted file mode 100644 index f94bd03..0000000 --- a/wg/modules/ROOT/pages/wg-minutes-2013.adoc +++ /dev/null @@ -1,103 +0,0 @@ -= Meeting Minutes from 2013 -Stephen Daley, Peter Boy - - -//========================================================== -Thursday, December 19, 2013:: -+ -* __**Agenda**__ -** *PRD: Use Cases* -* https://lists.fedoraproject.org/pipermail/server/2013-December/000657.html[Meeting minutes] -* https://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-19/fedora-meeting-1.2013-12-19-14.59.log.html[Full log] - - -//========================================================== -Tuesday, December 17, 2013:: -+ -* __**Agenda**__ -** *Final Assessment of Personas* -** *PRD: Delivery Plan* -** *PRD: Delivery Plan - Delivery Media* -** *Delivery Plan: Release Cadence* -* http://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-17/fedora-meeting-1.2013-12-17-16.00.html[Meeting minutes] -* https://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-17/fedora-meeting-1.2013-12-17-16.00.log.html[Full log] - - -//========================================================== -Tuesday, December 10, 2013:: -+ -* __**Agenda**__ -** *Backup and Monitoring* -** *what goes in the PRD* -** *Personas* -* http://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-10/fedora-meeting-1.2013-12-10-15.59.html[Meeting minutes] -* https://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-10/fedora-meeting-1.2013-12-10-15.59.log.html[Full log] - - -//========================================================== -Tuesday, December 3, 2013:: -+ -* __**Agenda**__ -** *Adam Williamson Confirmation* -** *Discuss Role Implementation* -* https://lists.fedoraproject.org/pipermail/server/2013-December/000631.html[Mailing list thread] -* http://meetbot.fedoraproject.org/fedora-meeting-1/2013-12-03/fedora-meeting-1.2013-12-03-15.59.html[Meeting minutes] - - - -//========================================================== -Tuesday, November 26, 2013:: -+ -* __**Agenda**__ -** *Select a new member of the Working Group* -** *Personas* -* https://lists.fedoraproject.org/pipermail/server/2013-November/000614.html[Mailing list thread] -* https://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-26/fedora-meeting-1.2013-11-26-16.00.html[Meeting minutes] - - -//========================================================== -Tuesday, November 19, 2013:: -+ -* __**Agenda**__ -** *Goals for Server Role Installation* -** *Personas* -** *Server Lifecycle Proposal* -** *Updates and Testing Proposal* -** *Server Role List Proposal* -** *Installation Roles vs. Post-installation Role Assignment* -* https://lists.fedoraproject.org/pipermail/server/2013-November/000535.html[Mailing list thread] -* https://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-19/fedora-meeting-1.2013-11-19-16.00.log.html[Full log] - - -//========================================================== -Tuesday, November 12, 2013:: -+ -* __**Agenda**__ -** *Can a single server have multiple roles?* -** *Installation of base + roles* -* https://lists.fedoraproject.org/pipermail/server/2013-November/000514.html[Mailing list thread] -* https://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-12/fedora-meeting-1.2013-11-12-16.02.log.html[Full log] - - -//========================================================== -Tuesday, November 5, 2013:: -+ -* __**Agenda**__ -** *Finalizing the Governance Charter: Membership (Group representation and terms)* -** *Is Fedora Server One Product?* -* https://blog.linuxgrrl.com/2013/11/05/fedora-server-working-group-nov-5-meeting-2/[Blog summary] -* https://lists.fedoraproject.org/pipermail/server/2013-November/000425.html[Mailing list thread] -* https://meetbot.fedoraproject.org/fedora-meeting-1/2013-11-05/fedora-meeting-1.2013-11-05-16.02.log.html[Full log] - - -//========================================================== -Wednesday, October 30, 2013:: -+ -* __**Agenda**__ -** *Meeting frequency and times* -** *Ticket Tracker/Wiki* -** *Governance Charter* -** *Open Floor* -* https://blog.linuxgrrl.com/2013/10/30/fedora-server-working-group-initial-meeting-minutes/[Blog summary] -* https://lists.fedoraproject.org/pipermail/server/2013-October/000313.html[Mailing list thread] -* http://meetbot.fedoraproject.org/fedora-meeting-1/2013-10-30/fedoraserverwg.2013-10-30-17.00.log.html[Full log] diff --git a/wg/modules/ROOT/pages/wg-minutes-2021.adoc b/wg/modules/ROOT/pages/wg-minutes-2021.adoc deleted file mode 100644 index 3b46545..0000000 --- a/wg/modules/ROOT/pages/wg-minutes-2021.adoc +++ /dev/null @@ -1,321 +0,0 @@ -= Meeting Minutes from 2020-2021 -Stephen Daley, Peter Boy -:page-authors: {author} - -Wednesday, December 15, 2021:: -Standing meeting about -* Migrating WG Wiki Pages to docs.fedoraproject.org -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-12-01-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/KWEP6EL4VEDZK3GO5LAEVXQOUL4DBYUD/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-12-01-17.00.log.html[Full log] - -Wednesday, December 1, 2021:: -Standing meeting about -* Migrating WG Wiki Pages to docs.fedoraproject.org -* Review current Fedora Server Technical Specification -* Facilitated and improved support for Fedora Server Edition VMs -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-12-01-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/KWEP6EL4VEDZK3GO5LAEVXQOUL4DBYUD/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-12-01-17.00.log.html[Full log] - -Wednesday, November 17, 2021:: -Standing meeting about -* Moving Wiki Pages to docs.fedoraproject.org -* Preparing Fedora Release 36 -* Facilitated deployment of key services by combining rpm and Ansible -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-11-17/fedora-server.2021-11-17-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/B36Q2AACPSRNS4DF4MQ7BQHCG5LTF7T5/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-11-17/fedora-server.2021-11-17-17.00.log.html[Full log] - -Wednesday, September 15, 2021:: -Standing meeting about -* Follow up actions -* Fedora 35: Max size arm-32 exceeded, install media blocked -* Facilitated deployment of key services by combining rpm and Ansible -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-09-15/fedora-server.2021-09-15-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/A5FMNBDH5R4ADXGZYVNV7TOGIBDP3FDJ/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-09-15/fedora-server.2021-09-15-17.00.log.html[Full log] - -Wednesday, September 1, 2021:: -Standing meeting about -* Follow up actions -* Fedora 35: Max size arm-32 exceeded, install media blocked -* Facilitated deployment of key services by combining rpm and Ansible -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021/fedora-meeting.2021-09-01-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/6JS7MSAECHVZZZWJU2J5AEISMQBDXLJZ/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021/fedora-meeting.2021-09-01-17.00.log.html[Full log] - -Wednesday, August 18, 2021:: -Standing meeting about -* Follow up actions -* Facilitated deployment of key services by combining rpm and Ansible -* Work planning update -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-08-18/fedora-server.2021-08-18-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/WVRMJ3PVBRR44WLQEK5BNYJ2GU7UYT7R/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-08-18/fedora-server.2021-08-18-17.00.log.html[Full log] - -Wednesday, August 4, 2021:: -Standing meeting about -* Follow up actions -* Facilitated deployment of key services by combining rpm and Ansible -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-08-04/fedora-server.2021-08-04-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/PWJNVPZYMAAQZWJZQKB5TDWE5KYY7ID4/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-08-04/fedora-server.2021-08-04-17.00.log.html[Full log] - -Wednesday, July 21, 2021:: -Standing meeting about -* Open ticket 32 about composition of installation media -* Work on Fedora 35 -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-07-21/fedora-server.2021-07-21-17.00.html[Meeting summary] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-07-21/fedora-server.2021-07-21-17.00.log.html[Full log] - -Wednesday, July 07, 2021:: -Meeting about Ongoing Work Projects -* Status of ongoing activities (some housekeeping) -* Fedora Server Documentation -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-07-07/fedora-server.2021-07-07-17.00.html[Meeting summary] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-07-07/fedora-server.2021-07-07-17.00.log.html[Full log] - -Wednesday, June 23, 2021:: -Meeting about Ongoing Work Projects -* Fedora Server Product Requirement Document (PRD) -* Fedora Server Documentation -* Fedora Website - revamp -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-06-23/fedora-server.2021-06-23-16.59.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/TPYYUQJ6WFU5QSMOLD7Z36NDZAIDBGE6/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-06-23/fedora-server.2021-06-23-16.59.log.html[Full log] - -Wednesday, June 9, 2021:: -Meeting about Ongoing Work Projects -* Fedora Server Release 35 -* Deploying services via RPM and Ansible -* Fedora Server documentation review -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-06-09/fedora-server.2021-06-09-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/ZE3F2U6J5PRB6RISC67DIWTAE2TFQU35/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-06-09/fedora-server.2021-06-09-17.00.log.html[Full log] - -Wednesday, June 2, 2021:: -Meeting about Ongoing Work Projects -* Explore opportunities for cooperation with Cloud WG -* Deploying services via RPM and Ansible -* Fedora Server documentation review -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-06-02/fedora-server.2021-06-02-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/message/WF54CWXOL6HLNJDXL5FUZTWPH46CIC63/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-06-02/fedora-server.2021-06-02-17.00.log.html[Full log] - -Wednesday, May 26, 2021:: -Meeting about Future Fedora Server Releases -* Deploying services via RPM and Ansible -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-05-26/fedora-server.2021-05-26-17.13.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/message/LO45JYWU7WJLQ7U3XHSLPQJBT6RNLX4G/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-05-26/fedora-server.2021-05-26-17.13.log.html[Full log] - -Wednesday, May 19, 2021:: -Meeting about Future Fedora Server Releases -* Issue release composition -* Planning for next Fedora release(s) -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-05-19/fedora-server.2021-05-19-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/IX6ZBBURUUIQNV72LKCUUWZPB4Q4JPA2/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-05-19/fedora-server.2021-05-19-17.00.log.html[Full log] - -Wednesday, May 12, 2021:: -Meeting about Fedora Server PRD and future Fedora Server Releases -* PRD - various reviewer questions to discuss -* Planning for next Fedora release(s) -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-server/2021-05-12/fedora-server.2021-05-12-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/KF2CTZMLFQAJTQIGDQIYQEAVAIYNAHYB/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-server/2021-05-12/fedora-server.2021-05-12-17.00.log.html[Full log] - -Wednesday, May 05, 2021:: -Meeting about Fedora Server Releases -* Planning for next Fedora release(s) -* Fedora release criteria and process -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-05-05-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/EAUPYMONTWRFIZSR4HPPI2TE5FZXGWDT/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-05-05-17.00.log.html[Full log] - -Wednesday, April 28, 2021:: -Meeting about Status PRD Update and Fedora Server Release -* Status Server PRD (Info) -* Fedora release criteria and process -* New Issue: Release composition -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-04-28-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/32IQLMZDPUS7JCF2FFRVJO5IAYYQLEL4/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-04-28/fedora-server.2021-04-28-17.00.log.html[Full log] - -Wednesday, April 21, 2021:: -Meeting about PRD Update and Fedora Server Release -* PRD Update second pass -* Fedora release criteria and process -* Planing for next Fedora release -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-04-21-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/OXWV357OY4ZCC4EFNPU3H4HZRRQIHVZS/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-04-21-17.00.log.html[Full log] - -Wednesday, April 14, 2021:: -Meeting about Mainly Continuation of the last meeting's agenda -* PRD update discussion -* Status F34 release -* Status new documentation -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-04-14-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/J7YI5OSM67O5RKMASL3BWUFMK43OBVCU/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-04-14/fedora-server.2021-04-14-17.00.log.html[Full log] - -Wednesday, April 07, 2021:: -Meeting about continuation of the last meeting's agenda -* PRD Update Proposal -* Collaboration with Cloud WG -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-04-07-17.01.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/LRI6LNKJZYXTS4SUUOZ7NMSIHUWRKM77/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-04-07/fedora-server.2021-04-07-17.01.log.html[Full log] - -Wednesday, March 31, 2021:: -Meeting about continuation of the last meeting's agenda -* PRD Update Proposal -* New Documentation -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-03-31-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/JMZY2TI3W6QMKDPNSZ2SRQN5QDW46A4A/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-03-31-17.00.log.html[Full log] - -Wednesday, March 24, 2021:: -Meeting about continuation of the last meeting's agenda -* Documentation Update -* PRD Update Proposal -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-03-24-17.00.html[Meeting summary] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-03-24-17.00.log.html[Full log] - -Wednesday, March 17, 2021:: -Meeting about continuation of the last meeting's agenda -* Work needed for Fedora 34 -* PRD Update Proposal -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-03-17-18.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/G7OMZFSWAYTYV2OP7ZEK3K4WGWAEKWV3/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2021-03-17-18.00.log.html[Full log] - -Wednesday, March 3, 2021:: -Meeting about -* Status Reboot Server Working Group -* Introduce Dusty Mabe from Cloud Group -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-03-03/fedora-server.2021-03-03-18.04.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/HKMAODK32EQC3MDGLAAVA4LSXAIN2WCM/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-03-03/fedora-server.2021-03-03-18.04.log.html[Full log] - -Wednesday, February 17, 2021:: -Meeting about -* Status Reboot Server Working Group -* Work program for the coming year -* PRD Update (first round of discussion) -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-02-17/fedora-server.2021-02-17-17.58.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/RQWDTIBDAUUK63HYIHLBHGJEMROSELOE/[Detailed agenda] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-02-17/fedora-server.2021-02-17-17.58.log.html[Full log] - -Wednesday, February 3, 2021:: -Meeting about -* Housekeeping -* Wiki Update -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-02-03/fedora-server.2021-02-03-18.15.html[Meeting summary] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-02-03/fedora-server.2021-02-03-18.15.log.html[Full log] - -Wednesday, January 20, 2021:: -Meeting about -* Status PRD Update -* Improving Fedora Server documentation and visibility -* systemd-oomd -+ -Details -+ -** https://meetbot.fedoraproject.org/fedora-meeting/2021-01-20/fedora_server.2021-01-20-17.02.html[Meeting summary] -** https://meetbot.fedoraproject.org/fedora-meeting/2021-01-20/fedora-server.2021-01-20-17.02.log.html[Full log] - -Wednesday, December 16, 2020:: -Fedora Server Reboot Meeting -* Introduction, Quick Hello, the Agenda -* Basic Framework for What's Needed -* Round of Introductions (Who you are, what you're interested in) -* Existing Fedora Server WG -* Volunteers to actually be on the Working Group -* Volunteers for practical action: reviewing and updating the PRD -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/serversig/serversig.2020-12-16-18.00.html[Meeting summary] -** https://meetbot.fedoraproject.org/teams/serversig/serversig.2020-12-16-18.00.log.html[Full log] - diff --git a/wg/modules/ROOT/pages/wg-minutes-2022.adoc b/wg/modules/ROOT/pages/wg-minutes-2022.adoc deleted file mode 100644 index 44b41c0..0000000 --- a/wg/modules/ROOT/pages/wg-minutes-2022.adoc +++ /dev/null @@ -1,646 +0,0 @@ -= Meeting Minutes -Stephen Daley, Peter Boy -:page-authors: {author} - - - - -//========================================================== -Wednesday,December 21, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: No outstanding action item. - -2. *Using Ansible to install and configure Wildfly* -+ -__ACTION__: jwhimpel will continue to work on Ansible roles . - -3. *Server WG work program for upcoming year* -+ -Continued discussion. -+ -__ACTION__: eseyman take a look at the work program over the holidays -+ -__ACTION__: jwhimpel will continue to work on Ansible roles -+ -__ACTION__: eseyman wants to focus on Identity Management for the first half of 2023 - -* https://meetbot.fedoraproject.org/fedora-meeting/2022-12-21/fedora-server.2022-12-21-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-12-21/fedora-server.2022-12-21-18.00.log.html[Full log] - -**Note**: We moved the time of our meeting to UTC so, that the same local time of day is maintained after the DST changeover, that means 18:00 UTC. - - - -//========================================================== -Wednesday,December 07, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: No outstanding action items - -2. *Server critical path definition proposal* -+ -We will review the current version and likely add items as soon as we have made progress in reviewing and updating our release and quality criteria - now that the technical specifications have been updated. - -3. *Server WG work program for upcoming year* -+ -Possible focus areas as currently discussed (should be continued on the mailing list): -+ -** Keeping documentation up to date. -** Using Ansible to install and configure Wildfly -** Fedora Website Revamp - Fedora Server part -** Review installation media - -* https://meetbot.fedoraproject.org/fedora-meeting/2022-12-07/fedora-server.2022-12-07-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-12-07/fedora-server.2022-12-07-17.00.log.html[Full log] - -**Note**: We are moving the time of our meeting to UTC so that the same local time of day is maintained after the DST changeover, that means 18:00 UTC. - - - - - - - - - -//========================================================== -Wednesday,October 19, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: @eseyman and @pboy will keep trying hard to replicate and check the Wildfly certificate issue. - -2. *Release 37 Beta testing* -+ -__info__: Installation issue with GPT and software RAID are resolved. -+ -__info__: Old systemd-nspawn related bugs are basically resolved (bugzilla 1900888, 1900869), but not yet completely -+ -__info__: The new ServerVM works fine. -+ -__agreed__: Server Edition rc 1.2 is ready for release. - -3. *Documentation update Release 37* -+ -__info__: The most important installation articles are reviewed and updated. -+ -__agreed__: For next release we determine the 5 articles mostly in need of an review and work on them on a documentation day in #fedora-server. - -4. *Server critical path definition proposal* -+ -We will continue the mailing list discussion. - -* https://meetbot.fedoraproject.org/fedora-meeting/2022-10-19/fedora-server.2022-10-19-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-10-19/fedora-server.2022-10-19-17.00.log.html[Full log] - - - -//========================================================== -Wednesday,October 05, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: All our open actions are about the next topics. - -2. *Release 37 Beta testing* -+ -__action__: cmurf will test the new ServerVM F37 -+ -SWraid installation on biosBoot GPT has been fixed, needs final testing. - -3. *Documentation update Release 37* -+ -@mowest reviewed 2 docs (local install and post installation). They are now significantly improved. Reveals the relevance of the review process. - -4. *Using Ansible to install and configure Wildfly* -+ -There is still an issue with the certificate. eseyman and pboy will additionally test it. - -* https://meetbot.fedoraproject.org/fedora-meeting/2022-10-05/fedora-server.2022-10-05-17.01.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-10-05/fedora-server.2022-10-05-17.01.log.html[Full log] - - - -//========================================================== -Wednesday,September 21, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: No outstanding action items - -2. *Release 37 Beta testing* -+ -We have assigned various test tasks among us. For details see #actions in the minutes below. - -3. *Documentation update Release 37* -+ -@mowest will begin reviewing docs, especially those not associated in the release 37 test items. - -4. *Release criteria, test procedures and systematization of tests* -+ -We agreed to strive for systematization using the test weeks tools. Details should first be discussed on the mailing list. - -* https://meetbot.fedoraproject.org/fedora-meeting/2022-09-21/fedora-server.2022-09-21-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-09-21/fedora-server.2022-09-21-17.00.log.html[Full log] - - - -//========================================================== -Wednesday,September 07, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: No outstanding action items - -2. *Release 37 Beta testing* -+ -It is verified the https://bugzilla.redhat.com/show_bug.cgi?id=2088113[software raid bug] is a release blocker. Not solved yet, but it is being worked on. - -3. *Server VM status and the way forward* -+ -Thanks to _nirik_ we have a Server VM x86_64 and s390 image in F37 and in Rawhide. It was a kind of last minute rescue after a rather https://pagure.io/fedora-kickstarts/pull-request/905[bumpy ride]. And thanks to _sgallagh_ for support in the not so easy way to get the kick-start file done at all. -+ -The kick-start failed on ppc64le and aarch64, unfortunately. The cause is likely to be different partitioning requirements, but the PR for a customized kick-start file was https://pagure.io/fedora-kickstarts/pull-request/915[hanging again]. -+ -We will need to review the current experience for its impact on our plan to update the server distribution media. Under the current circumstances, implementation seems quite unrealistic or at least extremely costly and time-consuming. - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/P2NNNFYFKIWCKZOPJ3FGHCEIMSDFI3QO/[Detailed agenda] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-09-07/fedora-server.2022-09-07-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-09-07/fedora-server.2022-09-07-17.00.log.html[Full log] - - - -//========================================================== -Wednesday, August 17, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: No outstanding action items - -2. *Final decision about an updated Fedora Server Technical Specification* -+ -It was consensus, that the document is not immutable and thus change be changed later if ideas for improvements surface later. Therefore, a decision now and start with the next tasks. -+ -__AGREED__: WG agrees about the techn.spec. in the current version, with alt. 1 for section 1.2 and editorial adaptations as discussed today. - -3. *Using Ansible to install and configure Wildfly* -+ -This is a key component of our "Supported by Ansible“-project (Server Roles), which has taken a back seat to everyday issues for far too long. -+ -jwhimpel has developed a playbook where currently there is still a problem with Letsencrypt certificates to be fixed. -+ -__ACTION__: jwhimpel will provide access to the playbook on GitHub so we can re-play the installation and test it. - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/2UM3SYJ5BPMUSZJMBTNND5UZCGBSNS3E/[Detailed agenda] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-08-17/fedora-server.2022-08-17-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-08-17/fedora-server.2022-08-17-17.00.log.html[Full log] - - -//========================================================== -Wednesday, July 20, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: No outstanding action items - -2. *Review current Fedora Server Technical Specification* -+ -We agreed about all suggestions in comments with the exception of the final wording of section 1.2 (File System and Storage Organization). We will open a discussion about the wording of section 1.2 on mailing list. -+ -__ACTION__: pboy will create a next version of the techn. spec. containing our agreements today. - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/2DK7BTZZUOASGMU35TJUSYWDZILV7DRV/[Detailed agenda] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-07-20/fedora-server.2022-07-20-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-07-20/fedora-server.2022-07-20-17.00.log.html[Full log] - - - -//========================================================== -Wednesday, July 06, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__DONE__: Change proposal to add Server VM is accepted -+ -__INFO__: Tracking bug https://bugzilla.redhat.com/show_bug.cgi?id=2100621 -+ -__INFO__: Change Proposal regarding the default hostname configuration is accepted by FESCo -+ -__DONE__: pboy to add test of uefi sw raid (https://pagure.io/fedora-server/issue/89) - -2. *Software Raid on UEFI systems* -+ -__AGREED__: We use the Anaconda solution with raid, for the time beeing. Further evaluation on mailing list and next meeting. - -3. *Review current Fedora Server Technical Specification* -+ -Discussion to continue next meting - -4. *Open Floor* - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/W5ACQXVPR3KOHISJC47LNB53KPJU7ISM/[Detailed agenda] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-07-06/fedora-server.2022-07-06-17.01.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2022-07-06/fedora-server.2022-07-06-17.01.log.html[Full log] - - - -//========================================================== -Wednesday, June 15, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__ONGOING__: Change proposal to add Server VM is still processing ( https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/M2YQMVVUCFCV4MMOQ32UMSM5WBBVE2H7/[discussion thread] ) -+ -__INFO__: There is now a Change Proposal regarding the default hostname configuration ( https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Y2TT6VZPGTD5UVGPA6PLNYW2BU4JOC77/[discussion thread] ) -+ -__AGREED__: Server WG is content with the default hostname change proposal - -2. *Further processing of GPT as default partitioning switch* -+ -__ACTION__: pboy to add test of uefi sw raid with LVM RAID (instead of standard raid) -+ -__ACTION__: pboy files a bug about sw raid in uefi mode -+ -Discussion of unversal boot configuration postponed until current problems are solved. - -3. *Test planning for Fedora 37* -+ -__AGREED__: Server WG will strive for a test week for F38 and follow up releases -+ -First step is a final review of the updated Technical Specification next meeting, followed by an update of our release and test criteria. - -4. *How to proceed with Cockpit File Sharing module NFS part* -+ -link: https://pagure.io/fedora-server/issue/86 -+ -Due to the elapsed time further discussion postponed. - -5. *Open Floor* - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/THLAKBXD6YEVGH2NDN4ZOCS3K7TYX3V4/[Detailed agenda] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-06-15-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-06-15-17.00.log.html[Full log] - - - -//========================================================== -Wednesday, June 01, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__DONE__: Post on devel list thread F37 proposed change to GPT as default partitioning schema about the regression regarding software raid installations. -https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/message/DIU6IKPCPD2BXDUFDZUZ2G2ZQNT5JW57/ -+ -__DONE__: Created an issue containing 2 test cases for biosboot GPT software raid installations -https://pagure.io/fedora-server/issue/87 -+ -__DONE__: created a stub of NFS server installation and Cockpit for administration -+ -__ONGOING__: Created Change proposal to add Server VM is still processing -+ -__ONGOING__: Discussion about changes around the default hostname configuration -+ -__ONGOING__: Review of the dnsmasq documentation by eseyman - -2. *Change proposal about GPT as default partitioning for bios boot* -+ -__LINK__: https://fedoraproject.org/wiki/Changes/GPTforBIOSbyDefault -+ -Discussion: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/VSM473WRHKIIIJYZZCVXAO7XFS4ACHPH/ -+ -FESCo has accepted the Change Proposal without discussion. We now have the problem of preserving our users from harm unfortunately done intentionally or, at best, negligently by some of our own members who are owners of the Change Proposal. Unfortunately, the perpetrators do now not care how harm can be averted from our users with Release 37 and do not even bother to attend the meeting on this topic to find a suitable resolution if the issue. -+ -Stephen Gallagher started a process to qualify the Anaconda software raid bug as a blocker to the GPT Change Proposal. If accepted by QA as a blocker, it will have to be fixed (or the Change reverted) in order to ship Fedora. This would be a perfect and constructive solution. -+ -__Agreed__: Server WG agrees with sgallagh's suggestion to block the GPT change until the Anaconda issue is resolved and considers it as most essential. - -3. *Planning for Fedora 37: Additional changes to discuss? (continued)* -+ -For part of the discussion we have a new tracking issue: https://pagure.io/fedora-server/issue/88[#88] , It summarizes all the individual measures that we have discussed for improvement and entail an adjustment of the installation media. -+ -Agreed: Issue #88 is postponed to F38 -+ -There are various new bug reports regarding the size of installation media, very similar to those on F36. We'll ask Adam about it, He resolved those issues for F36. - -4. *How to proceed with Cockpit File Sharing module NFS part* -+ -link: https://pagure.io/fedora-server/issue/86 -+ -Due to the elapsed time further preparatory discussion via e-mail. - -5. *Open Floor* - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/RFUVXGX4XFUJQFAN4QC3JNIYKPTL66GS/[Detailed agenda] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-06-01-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-06-01-17.00.log.html[Full log] - - - -//========================================================== -Wednesday, May 18, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__INFO__: We voted successfully for 4 new members: cooltshirtguy, dcavalca, eseyman, mowest, a very warm welcome. Our list of members is already updated. -+ -__ONGOING__: Created Change proposal to add Server VM is still processing in preparation phase -+ -__ONGOING__: Discussion about changes around the default hostname configuration - -2. *Change proposal about GPT as default partitioning for bios boot* -__LINK__: https://fedoraproject.org/wiki/Changes/GPTforBIOSbyDefault -+ -Discussion: https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/Q2ZBWG3YESG4POYAAZVUKSWMZHG3R7KW/ -TBD -+ -__Agreed__: Server WG insists that before switching to GPT as default for BIOS boot, it is tested, that Anaconda supports a software raid setup smoothly. - -3. *Planning for Fedora 37: Additional changes to discuss? (continued)* -+ -There is an RFE (https://bugzilla.redhat.com/show_bug.cgi?id=2054625) pending to include some additional packages to the full installation DVD, which led to a discussion which packages to add and whether we accept a further increase of the downloads. -+ -Agreed: We combine all installation content related issues and actions into one new ticket. -+ -Action: pboy to create a new ticket about installation media content review - -4. *How to proceed with Cockpit File Sharing module* -+ -link: https://pagure.io/fedora-server/issue/86 -+ -Discussion: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/T75AU7FLZMDUBMXOD3AXSC4VCYIJ6ZMA/ -+ -Agreed: We will divide the topic in several steps and start with nfs. -+ -We'll start with completing our documentation with installing and maintening a nfs server. Pboy will provide a ToC proposal. -+ -5. *Open Floor* -+ -Eseyman will start to review the dnsmasq documentation article with the goal to extend it about setup of an PXE server. Mowest is about to document his setup of a WOL configuration. - - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/R3VWDITZ6A23ZJXWJTUFUWJLGGV6K5W2/[Detailed agenda] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-05-18-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-05-18-17.00.log.html[Full log] - - - -//========================================================== -Wednesday, May 04, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__ONGOING__: Created Change proposal to add Server VM -+ -__DONE__: Supplement to our Product requirements Document (PRD) -+ -__DONE and ONGOING__: Voting about new members (open until Thursday,05 05:00 UTC). -+ -__DONE__: Withdrawal of nb and mhoungbo from member list - -2. *Evaluation of our test efforts for F36* -+ -We agreed, we did better than with F35 and want to further improve with F37. Will open a follow-up discussion on mailing list. - -3. *Planning for Fedora 37: Additional changes to discuss?* -+ -There is an RFE (https://bugzilla.redhat.com/show_bug.cgi?id=2054625) pending to include some additional packages to the full installation DVD, which led to a discussion which packages to add and whether we accept a further increase of the downloads. -+ -__Agreed__: Continue discussion on mailing list. - -4. Open Floor -+ -x3mboy raised the question of migrating our repository to gitlab. -+ -__Agreed__: discuss on mailing list - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/RQIB4PW64KVMD376224UWLHWICTBL3TW/[Detailed agenda] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-05-04-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-05-04-17.00.log.html[Full log] - - - -//========================================================== -Wednesday, April 20, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__DONE__: withdrew Ben Williams from the list of approved members as he had wanted. Many thanks for his contributions. -+ -__DONE__: Opened a discussion about Cockpit and the file-sharing update follow ups on mailing list. -+ -__DONE__: Opened a discussion thread about a specification for a Server Edition VM on mailing list. - - -2. *Planning for Fedora 37: Introducing a Server VM KVM virtual disk image* -+ -https://pagure.io/fedora-server/issue/79 -+ -__Agreed__: WG decides to add a Fedora Server Edition VM image and to make a corresponding Change proposal. -+ -__Action__: pboy creates a change proposal to add a Fedora Server Edition VM image -+ -__Agreed__: WG decides to amend the PRD as proposed in ticket 83 -+ -__Action__: pboy edits the PRD to amend as in issue #83 and initializes the required processing - - -3. *Evaluating Fedora Server Working Group* -+ -https://pagure.io/fedora-server/issue/67 -+ -__Agreed__: WG agrees to open a voting on the admision of cooltshirtguy, dcavalca, eseyman and mowest in one go. -+ -__Action__: pboy start a voting the admision of cooltshirtguy, dcavalca, eseyman and mowest in one go. -+ -__Agreed__: WG agrees to withdraw nb and mhoungbo for the time being (#67). Many thanks to both of them for their willingness to work on the Server WG. -+ -__Action__: Withdrawal of nb and mhoungbo from member list. - -4. *Discussion of a potential change to Fedora surrounding the default hostname* -+ -__Agreed__: salimma and Eighth_Doctor work with Dusty and probably others to explore the possibilities to get the old behaviour (pre f33) back. - -5. *Current discussion about withdrawal of BIOS boot for new installations in F37* -+ -There was a longer discussion about the subject. And the largely unanimous position was that we still need bios boot for a longer time for various reasons. Everything must be done to find a technical solution that makes this possible under the condition of available resources. -+ -__Agreed__: Davide Cavalca and Michel Alexandre Salim volunteer to work further on the subject. - - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/XZBPD436FYFTKU5L6QVUEN2WBCORICQF/[Detailed agenda] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-04-20-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-04-20-17.00.log.html[Full log] - - - -Wednesday, April 06, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__Info__: Had an IRC chat with Ben Williams (jbwillia). He is busy with other projects and we agreed he will withdraw from server WG. So I will remove him from our list. (see https://pagure.io/fedora-server/issue/67[#67]). -+ -__Action__: Will withdraw Ben Williams from the list of approved members for the time being. -+ -__DONE__: Withdrew Subhendu Ghosh from the list of approved members for the time being. -* -__DONE__: pb and sgallagh resolved the installation issue with virtualization. - - -2. *Fedora 36 tests* -+ -__Info__: takes over testing AD from for the F36 test cycle -+ -__Info__: still testing OpenLDAP -+ -__Info__: No issues found with libcirt / postgreSQL / java / Tomcat -+ -__Agreed__: WG will join the Upgrade test day Thursday, April 14. Member will test on their own "real world" configurations - - -3. *Cockpit file-sharing update Change Proposal follow up* -+ -__Agreed__: We close issue https://pagure.io/fedora-server/issue/73[#73] as completed and done. -+ -__Info__: has it on his (long) backlog to add the Cockpit Application stuff to the file-sharing -+ -__Agreed__: We open a discussion thread about file-sharing update followup actions on mailing list - -4. *Planning Fedora 37* -+ -__Info__: There is a hot discussion about withdrawel of bios boot for F37. -+ -We will dedicate a own topic about that next meeting -+ -Regarding our own plannings: -+ -** https://pagure.io/fedora-server/issue/53[#53] ("Facilitated and improved support for Fedora Server Edition VMs", pboy) -+ -There is a https://pagure.io/fedora-server/issue/79#comment-790978[comment] with some specification to add a Fedora Server Edition disk image to our deliverables as part of out Fedora 37 work. -+ -__Agreed__: Open a discussion thread about https://pagure.io/fedora-server/issue/79#comment-790978 and decide next meeting - - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/565ZBHTE3TCNLTJYGMQEY7Q4CWQ2KOZ6/[Detailed agenda] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-04-06-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-04-06-17.00.log.html[Full log] - - - -Wednesday, March 16, 2022:: -+ -* _Summary info_ - -1. *Follow up actions* -+ -__Info__: Startet to contact members who had not been with us for longer than a half year und didn’t contribute anything (see https://pagure.io/fedora-server/issue/67[#67]). -+ -__Info__: Tried to contact Subhendu Ghosh (sghosh). There is no FAS account and no mail address available. -+ -__Agreed__: We withdraw Subhendu Ghosh from the list of approved members for the time being. - - -2. *Fedora 36 tests* -+ -__Action__: sgallagh and pboy work on #80 -+ -__Action__: The migration to the "next generation" of ansible seems to be working fine. - -3. *Planning Fedora 37* -+ -__Result__: Special interests exist so far in -+ -** https://pagure.io/fedora-server/issue/53[#53] ("Facilitated and improved support for Fedora Server Edition VMs", pboy) -+ -** https://pagure.io/fedora-server/issue/54[#54] ("Include automatic notification of updates (dnf-automatic) in Fedora Server", cooltshirtguy) - -* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/2MXO25NSLOVKH7O3OU2JB4QRZWPB44AN/[Detailed agenda] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-03-16-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-03-16-17.00.log.html[Full log] - - -Wednesday, March 02, 2022:: -Standing meeting about -* Check F36 changes and known issues - final pass -+ -__Result__: Composed final list of F36 changes to specifically take care of -* Specifying F36 manual test requirements - final pass -+ -__Result__: Final composition of a list of task & manual tests to be applied to F36 Beta -* Review current Fedora Server Technical Specification – second pass -+ -__Result__: First draft proposal adopted as is, continue with completion of TBDs -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-03-02-17.08.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/SVZCL47QI3DINKADPN3OGESW72DAIQRK/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-03-02-17.08.log.html[Full log] - -Wednesday, February 16, 2022:: -Standing meeting about -* Cockpit file-sharing update Change Proposal -* Specifying F36 manual test requirements -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-02-16-17.00.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/SVZCL47QI3DINKADPN3OGESW72DAIQRK/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-02-16-17.00.log.html[Full log] - -Wednesday, February 02, 2022:: -Standing meeting about -* Current status of Fedora Server User Docs Update -* Using Ansible to install and configure Wildfly -* Review current Fedora Server Technical Specification -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-02-02-17.01.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/QSGS6B22VQBHZGPL6HJPYXMW7O5O7LWC/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-02-02-17.01.log.html[Full log] - -Wednesday, January 19, 2022:: -Standing meeting about -* Current status of Fedora Server User Docs Update -* Current changeset F36, possible specific impacts on Server -* Review current Fedora Server Technical Specification -+ -Details -+ -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-01-19-17.01.html[Meeting summary] -** https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/W3CVVA2JQFYFX7FI6EJ7YBTOLBZJHVSZ/[Detailed agenda] -** https://meetbot.fedoraproject.org/teams/fedora-server/fedora-server.2022-01-19-17.01.log.html[Full log] - diff --git a/wg/modules/ROOT/pages/wg-minutes-2023.adoc b/wg/modules/ROOT/pages/wg-minutes-2023.adoc deleted file mode 100644 index b88096b..0000000 --- a/wg/modules/ROOT/pages/wg-minutes-2023.adoc +++ /dev/null @@ -1,577 +0,0 @@ -= Meeting Minutes 2023 -Stephen Daley; Peter Boy - - -//========================================================== -Wednesday, Dec 06, 2023:: -+ -* __**Essentials at a glance**__ - -** *Next meeting on January 19, 2024!* - -** *Fedora Server release and quality criteria* -+ -We want to further discuss this on mailing list and in the ticket. -** *Work program and goals for F40* -+ -Various ideas discussed, further discussion on the mailing list and in the ticket -. -** *Test planning for F40* -+ -Extensive discussion without a conclusive result yet. Discussion to be continued at the next meeting. - - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-11-15/fedora-server.2023-11-15-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-11-15/fedora-server.2023-11-15-18.00.log.html[Full log] - -* __**Actions summary**__ -. _ACTION_: Mowest will take care ot disussed modifications of the Server download page. - - - -//========================================================== -Wednesday, Nov 15, 2023:: -+ -* __**Essentials at a glance**__ - -** *Fedora release 39 - State of Server media and Download Web page* -+ -The Situation regarding aarch64 on SBC is a bit better then 2 weeks ago, but still but still not satisfactory. A SBC is now installable if you don't use an installation host with actrive LVM drives, but use e.g. Fedora Workstation. In this respect, it would be disproportionate to continue to regard this as a release blocker. The problem must now be solved for Release 40. -+ -It's really unfortunate, that we discovered the bug so late in the Beta process. We need to review our testing procedures. We have relied too much on the automated tests. -+ -For the next release we should improve the download page. We need to find a better name as the outdated term "DVD" and should clearly distinguish the SBC variant from the other installations, it is best to introduce a separate section. -+ -ACTION: Mowest will take care ot disussed modifications of the Server download page. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-11-15/fedora-server.2023-11-15-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-11-15/fedora-server.2023-11-15-18.00.log.html[Full log] - -* __**Actions summary**__ -. _ACTION_: Mowest will take care ot disussed modifications of the Server download page. - - - - -//========================================================== -Wednesday, Nov 01, 2023:: -+ -* __**Essentials at a glance**__ - -** *Fedora release 39 rc current state and how to continue* -+ -The x86_64 versions work great. There is still a severe bug with installing the aarch64 SBC version on Fedora Server. -+ -_AGREED_: If the LVM issue can not be resolved for f39 release, Server WG would like to opt out providing a f39 installation medium for aarch SBC, continue to distribute f38 and encourage to update using dnf. - -** *Package fail2ban orphaned* -+ -In the meantime the orphaned package was picked by a new maintainer. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-11-01/fedora-server.2023-10-11-01.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-11-01/fedora-server.2023-11-01-17.00.log.html[Full log] - -* __**Actions summary**__ -+ -none - - - - -//========================================================== -Wednesday, Oct 18, 2023:: -+ -* __**Essentials at a glance**__ - -** *Maximum size of aarch64 Server network install image* -+ -_AGREED_: Enlarge aarch64 net install media to 1 GB. Letting everything else as is. - -** *Fedora release 39 beta first experience and how to continue* -+ -Mowest has tested the x86_64 installation image and pb the VM image. No issues found. -+ -There is still an issue with the aarch64 on SBC version. pboy will check. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-10-18/fedora-server.2023-10-18-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-10-18/fedora-server.2023-10-18-17.00.log.html[Full log] - -* __**Actions summary**__ -+ -none - - - - -//========================================================== -Wednesday, Sep 20, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. -git+ -Nothing to announce today. - -** *F40 Change proposal dropping sshd.socket file* -+ -ACTION: jwhimpel will keep an eye on behalf of Server WG on the "Change proposal dropping sshd.socket file" discussion. - -** *Fedora release 39 beta first experience and how to continue* -+ -ACTION: jdubby will deploy some of the wildfly quickstarts via localhost and report at our next meeting. - -** *F39/40 Work Project: Fedora Server in a virtualized runtime environment * -+ -ACTION: mowest and pboy will prepare a community action about Fedora Server in a virtualized runtime environment - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-09-20/fedora-server.2023-09-20-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-09-20/fedora-server.2023-09-20-17.00.log.html[Full log] - -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review -. _ACTION_: jwhimpel will keep an eye on behalf of Server WG on the "Change proposal dropping sshd.socket file" discussion. -. _ACTION_: mowest and pboy will prepare a community action about Fedora Server in a virtualized runtime environment - - - - -//========================================================== -Wednesday, Sep 06, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. -git+ -Nothing to announce today. - -** *F39 Work Project: Fedora Server on (ARM) SBC* -+ -ACTION: pboy will complete the intro text about Fedora Server and ARM SBC - -** *Work Project: Using Ansible to install and configure Wildfly* -+ -ACTION: jdubby will deploy some of the wildfly quickstarts via localhost and report at our next meeting. - -** *Fedora release 39 test planning* -+ -ACTION: pboy will open a mailing list thread about F39 change set to review changes and come up with a list of those that affect server edition - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-09-06/fedora-server.2023-09-06-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-09-06/fedora-server.2023-09-06-17.00.log.html[Full log] - -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review -. _ACTION_: pboy will complete the intro text about Fedora Server and ARM SBC -. _ACTION_: jdubby will deploy some of the wildfly quickstarts via localhost and report at our next meeting. -. _ACTION_: pboy will open a mailing list thread about F39 change set to review changes and come up with a list of those that affect server edition - - - - -//========================================================== -Wednesday, Aug 16, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. -git+ -Nothing to announce today. - -** *F39 Work Project: Fedora Server on (ARM) SBC (* -+ -pboy will write a first draft of the first part of the text about Server on SBC (Purpose and summary of the literature). Further discussion on mailing list, - -** *Work Project: Using Ansible to install and configure Wildfly* -+ -The certificate issue got resolved. Next step is installation and configuration of the proxy (nginx). Detailed discussion on mailing list. - -** *Fedora release 39 test planning* -+ -After the first impression, there is no potentially critical change that requires our special attention and testing. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-08-16/fedora-server.2023-08-16-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-08-16/fedora-server.2023-08-16-17.00.log.html[Full log] - -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review - - - - -//========================================================== -Wednesday, Jul 19, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. -. Done: eseyman will review the NFS documentation -** *Announcement* -+ -Nothing to announce today. - -** *Fedora 39 change Proposal: Enable Firmware Update Notification* -+ -In a short discussion we had voted 7:0:0 in favour of the change. To add an email notification is currently useless, because we don't install any email capability by default. - -** *LLMNR should be disabled in resolved in f39* -+ -Nirik and pboy are to formulate a solution on behalf of the WG. - -** *Work Project: Using Ansible to install and configure Wildfly* -+ -We made various decisions - -*** We'll use nginx as proxy solution, because it is able to handle the proxy protocol. -*** pboy asks Java SIG about best practise for a installation location. -*** We will create a separate log. Volume for /opt/wildfly according the Fedora Server Edition storage concept - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-07-19/fedora-server.2023-07-19-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-07-19/fedora-server.2023-07-19-17.00.log.html[Full log] - - - - -//========================================================== -Wednesday, Jul 05, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. -. Ongoing: eseyman will review the NFS documentation - still WIP -** *Announcement* -+ -AS it looks at the moment the committee has accepted and is planning with a presentation: Fedora Server Edition – Quo Vadis? Unfortunately a workshop about Server in virtual environment, that I proposed, too, didn't make it. - -** *Could we drop Active Directory requirements from Fedora release criteria?* -+ -*Agreed* WG agrees about to use automated testing using Samba AD as the server end (instead of a native Windows server) and to keep the status of release criteria. -+ -Full compatibility with Windows Server remains the goal regardless of the testing procedure. And an _inability to connect to a real Microsoft AD server remains a release blocking criterion_, since that is (and remains) the most prominent domain controller in the world. - -** *F39 Work Project: Fedora Server on (ARM) SBC* -+ -We'll complete the current device documentation draft with the devices nominated until now. -+ -** *Open Floor* -+ -We want to replace the "DVD" in the naming of the installation media by "STD". - - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-07-05/fedora-server.2023-07-05-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-07-05/fedora-server.2023-07-05-17.00.log.html[Full log] -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review - - - - -//========================================================== -Wednesday, Jun 21, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. -. Ongoing: eseyman will review the NFS documentation - still WIP -** *Announcement* -+ -pboy has submitted a talk and a workshop idea to Flock - -** *F39 Work Project: Fedora Server on (ARM) SBC* -+ -W'll compose a devices list. -+ -ACTION eseyman to post his ARM SBC list to the list by next week. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-06-21/fedora-server.2023-06-21-17.02.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-06-21/fedora-server.2023-06-21-17.02.log.html[Full log] -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review - - - - -//========================================================== -Wednesday, Jun 07, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. -** *Announcement* -+ -This year's Flock will be in-person Aug. 2-4 in Cork, Ireland. We'll discuss our contribution on mailing list and next meeting. - - -** *F39 Work Project: Fedora Server on (ARM) SBC* -+ -_AGREED_: The WG agrees on part 1 of the plan in issue 108 and will create a reference list. -+ -W'll start a list of desirable or available devices in a comment to on tracking issue #108. -+ -W'll consider the Phoronix list of tests for comparison. - -** *Using Ansible to install and configure Wildfly* -+ -We postpone working on it until July, when jwhimpel has time again. -** *F39/40 Work Project: Fedora Server in a virtualized runtime environment* -+ -_AGREED_: WG will perform the community survey as proposed in #110 . - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-06-07/fedora-server.2023-06-07-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-06-07/fedora-server.2023-06-07-17.00.log.html[Full log] -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review - - - - -//========================================================== -Wednesday, May 03, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. - -** *Fedora Server goal(s) for F39* -+ -_AGREED_: WG will pursue 'Fedora Server Edition on SBC' as first priority for F39, and 'Fedora Server Edition in virtualized environments' as 2nd priority. - -** *"Each Edition has a story for each release"* -+ -_AGREED_: WG will pursue 'Fedora Server Edition on SBC' as the 'story' for F39 with first priority, 'Fedora Server Edition in Virtuialized environments' with 2nd priority. -+ -_ACTION_: pboy will post a first draft regarding 'Fedora Server Edition on SBCs' on hackmd.io for further discussion. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-05-03/fedora-server.2023-05-03-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-05-03/fedora-server.2023-05-03-17.00.log.html[Full log] -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review -. _ACTION_: pboy will post a first draft regarding 'Fedora Server Edition on SBCs' on hackmd.io for further discussion. - - -//========================================================== -Wednesday, April 19, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. - -** *"Each Edition has a story for each release"* -+ -On link:++https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/VILYMWVJ7GVHOSLP3C3YC42S3G7JACM4/++[mailing list] we have a first info and a draft collection of ideas. The challenge is not so much the "story" part, but the "every release" part. -+ -_ACTION_: eseyman will try and think up something for next meeting - -** *Fedora Server goal(s) for F39* -+ -_AGREED_: We evaluate 2 options for F39: ServerVM support for various hosting services and Usage of SBC as a Server device - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-04-19/fedora-server.2023-04-19-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-04-19/fedora-server.2023-04-19-17.00.log.html[Full log] -* __**Actions summary**__ -. _ACTION_: Ongoing pboy will write a info about how to configure the timeout value and nirik will review -. _ACTION_: eseyman will try and think up something for next meeting - - -//========================================================== -Wednesday, April 05, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review. - -** *F38 Beta testing* -+ -We are fine with F38 and should not experience any surprises. - -** *Shorter Shutdown Timer* -+ -_Nirik_ created a PR as decided. It is pushed to stable and will be included in the installation media. - -** *Fedora Website revamp – Fedora Server Edition pages* -+ -AGREED: Server WG would like to get a "Documentation" button/link between Download and Community in the hero graphic -+ -AGREED: Server WG is content with the feature list and descriptions. - -** *Using Ansible to install and configure Wildfly* -+ -We will start thinking about how we're going to get these ansible roles/playbooks into our users' hands. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-04-05/fedora-server.2023-04-05-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-04-05/fedora-server.2023-04-05-17.00.log.html[Full log] -* __**Actions summary**__ -. Ongoing: pboy will write a info about how to configure the timeout value and nirik will review - - -//========================================================== -Wednesday, March 15, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. No open actions - -** *Shorter Shutdown Timer* -+ -AGREED: to take the same route as CoreOS and keep the old default value. (+3, 0, -2 ) -+ -ACTION: pboy will write a info about how to configure the timeout value and nirik will review - - -** *Fedora Website revamp – Fedora Server Edition pages* -+ -We are still missing a documentation button and link. The feature list needs some improvement. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-03-15/fedora-server.2023-03-15-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-03-15/fedora-server.2023-03-15-18.00.log.html[Full log] -* __**Actions summary**__ -. pboy will write a info about how to configure the timeout value and nirik will review - - -//========================================================== -Wednesday, March 01, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. Ongoing: nirik to look up the services in our technical specification and check for time out value -. Ongoing: pboy to create a ticket to collect our central messages for the new web site. - -** *Shorter Shutdown Timer* -+ -We are still evaluating the possible impact and current configuration of the core services. -+ -We want to add to our documentation how to make changes to the .service file if someone has an issue. -+ -*action* pboy will create a summary of our discussion about service specific timeouts. -+ -*action* pboy will open a mailing list discussion about interdependencies between services and the consequences. - -** *Using Ansible to install and configure Wildfly* -+ -We have still 2 unresolved issues: -+ -.... -a. TLS between apache and Wildfly web app -b. Ansiblify Wildfly -.... -+ -*action* jdubby will update his Ansible/Wildfly repo -+ -*action* eseyman will look at the updated repo -+ -*action* pboy will provide a public server where we can work in a cooperative work on all the details - - -** *Fedora Website revamp – Fedora Server Edition pages* -+ -We are generally very content with the current state of the https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/server/[completed draft]. Mowest informed that the design group considers it "near final". Anyway we can request changes after the F38 rollout. - - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-02-15/fedora-server.2023-02-15-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-02-15/fedora-server.2023-02-15-18.00.log.html[Full log] -* __**Actions summary**__ -. pboy to create a ticket to collect our central messages for the new web site -. nirik to look up the services in our technical specification and check for time out value -. pboy pboy will create a summary of our discussion about service specific timeouts. -. pboy will open a mailing list discussion about interdependencies between services and the consequences. -. jdubby will update his Ansible/Wildfly repo -. eseyman will look at the updated repo -. pboy will provide a public server where we can work in a cooperative work on all the details - - -//========================================================== -Wednesday, February 15, 2023:: -+ -* __**Essentials at a glance**__ - -** *Follow up actions* -. nirik to look up the services in our technical specification and check for time out value -. pboy to create a ticket to collect our central messages for the new web site. - -** *Fedora Website revamp – Fedora Server Edition pages* -+ -Mowest informs about the availability of a https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/server/[first complete draft], although still with some placeholders. The discussion about https://gitlab.com/fedora/design/team/wwwfpo-2022/-/issues/23#note_1276926623[further development] is still ongoing. The current topic is the design of the header. We agree that it should express as well as possible the universality and wide scope of Fedora Server Edition (from SBC to SME to Data Center). -+ -Next step is the finetuning of the mission statements. - -** *Shorter Shutdown Timer* -+ -We are still evaluating the possible impact and current configuration of the core services. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-02-15/fedora-server.2023-02-15-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-02-15/fedora-server.2023-02-15-18.00.log.html[Full log] -* __**Actions summary**__ -. pboy to create a ticket to collect our central messages for the new web site -. nirik to look up the services in our technical specification and check for time out value -. pboy to create a list of our core services in the issue for further discussion - - -//========================================================== -Wednesday, February 01, 2023:: -+ -* __**Essentials at a glance**__ - -** *Fedora Website revamp – Fedora Server Edition pages* -+ -Mowest made contact with the revamp team. We are now in the flow to work on it. -See the https://fedora.gitlab.io/websites-apps/fedora-websites/fedora-websites-3.0/server/[current mockup]! The texts are a first draft. The graphical assets are mostly placeholders. -+ -You can also follow the https://gitlab.com/fedora/design/team/wwwfpo-2022/-/issues/23[ongoing conversation about the current status of the website design]. To give feedback, please use our https://pagure.io/fedora-server/issue/66[pagure issue #66]! -+ -Next actions: - -a. Review text right now and give suggestions for changes. -b. Mowest will inform us Emma (the designer) has some of the graphic assets ready for review. -c. Suggestions or ideas for graphic assets that could be used next to each of our "feature points" as suggestions to the graphics team. - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-02-01/fedora-server.2023-02-01-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-02-01/fedora-server.2023-02-01-18.00.log.html[Full log] - - -//========================================================== -Wednesday, January 18, 2023:: -+ -* __**Essentials at a glance**__ - -** *Shorter Shutdown Timer* -+ -We will first review the Core Services of our current xref:docs/server-technical-specification.adoc["_Technical Specification_"] to see what configuration is implemented for a shutdown. Furthermore, we will consider conducting a test tag on this point, although implementation is likely to be difficult. Depending on the findings, we will decide on the further handling of the magnitude of the default timeout. -+ -We found contradictions resp. ambiguities about the exact configuration of the current timeout configuration in Server. Nirik will clarify this. -+ -_Actions_ - - . nirik will look up the services in our technical specification and check for time out value - -** *Fedora Server web site revamp* -+ -Mowest made contact with the revamp team and introduced himself as Server contact. We are now in the flow to work on it. -+ -The next step is to collect content for our pages. Mowest asks to contribute key ideas, messages, mission statements for the content of the page. We prefer professional, meaningful texts, not rather content-less marketing phrases, which can be found partly on some newly designed pages. -+ -_Actions_ - - . pboy to create a ticket to collect our central messages for the new web site. - - -* https://meetbot.fedoraproject.org/fedora-meeting/2023-01-18/fedora-server.2023-01-18-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-01-18/fedora-server.2023-01-18-18.00.log.html[Full log] -* __**Actions summary**__ - - . nirik will look up the services in our technical specification and check for time out value - . pboy to create a ticket to collect our central messages for the new web site. - - -**Keep in mind**: We had moved the time of our meeting in UTC so that the same local time of day is maintained after the DST changeover, that means currently 18:00 UTC. - diff --git a/wg/modules/ROOT/pages/wg-minutes-2024.adoc b/wg/modules/ROOT/pages/wg-minutes-2024.adoc deleted file mode 100644 index 1c788a4..0000000 --- a/wg/modules/ROOT/pages/wg-minutes-2024.adoc +++ /dev/null @@ -1,1026 +0,0 @@ -= Meeting Minutes 2024 -Stephen Daley; Peter Boy -:page-authors: {author}, {author_2} - - -//========================================================== -Wednesday, December 18, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -Still discussion how to organize the classic UID/GID issue with NFS clients. -+ -AGREED Regarding NFS we will start with LDAP ansible playbook and in parallel establish documentation for the manual way in smaller networks. - -** *Server user poll* -+ -Decided to publish the https://fedoramagazine.org/fedora-server-user-survey-your-cattle-or-your-pets/[Fedora Magazine Article] as drafted by Mowest on Dec 20 or Dec 23 and to start the poll immediately. -+ -ACTION DONE: Mowest will write a 1st draft of an article about our poll. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-12-18/fedora-server.2024-12-18-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-12-18/fedora-server.2024-12-18-18.00.log.html[Full log] -// -* __**Current Actions summary**__ -. ON HOLD pboy will file an issue with releng regarding installation media -. ONGOING pboy will close bug #2247872 (https://bugzilla.redhat.com/show_bug.cgi?id=2247872) -. ONGOING pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification -. ONGOING jwhimnpel will develop a Ansible playbook for NFS service -. PENDING eseyman review John's playbooks -. DONE Mowest will write a 1st draft of an article about our poll. - - -//========================================================== -Wednesday, December 11, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Cockpit boot message* -+ -We already discussed this topic on https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-12-11/fedora-server.2024-12-11-18.00.log.html[mailing list]. There is a https://bugzilla.redhat.com/show_bug.cgi?id=1635200[request to remove the Cockpit information] at every ssh login. -+ -AGREED: Regarding bug 1635200, WG agrees to keep the current Cockpit informational message. - -** *Ansible assisted installation and configuration of NFS service* -+ -It appears that f41's move from dnf to dnf5 has caused my ansible modules some heartburn. The issues require further research. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-12-11/fedora-server.2024-12-11-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-12-11/fedora-server.2024-12-11-18.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - -//========================================================== -Wednesday, December 4, 2024:: -+ -**Attention**: We agreed to cancel our regular meetings scheduled for __Dec 25__ and __Jan 1__, but keeping __Dec 18__ and __Jan 08__. - -* __**Essentials at a glance**__ - -** *Server user poll* -+ -AGREED: The current version in Fedora LimeSurvey instance is the final one. -+ -We discussed and agreed on various steps to spread the word about the survey in the Fedora community. - -** *Work program and goals* -+ -We agree that it is time to produce something really new for Fedora Server. Some rough ideas: - -*** Creating a __Fedora Home Server__ spin for Raspberry Pi / SBCs -*** Installing Fedora Server on Windows WSL or macOS UTM - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-12-04/fedora-server.2024-12-04-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-12-04/fedora-server.2024-12-04-18.00.log.html[Full log] -// -* __**Actions summary**__ -. ACTION: pboy will compile statistical data on the use of the Fedora server for one of the next meetings. -. ACTION: eseyman will post on the Fedora group on Facebook about Fedora Server survey. - - - - -//========================================================== -Wednesday, November 27, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Server Poll* -+ -AGREED: The Fedora Server poll should start Dec. 10 24 and run until Feb 18 25 -+ -The survey will be available at https://fedoraproject.limequery.com/fedora-server-f41 when it has been transferred into the Fedora space. - -** *Ansible assisted installation and configuration of NFS service* -+ -@jwhimpel plans to update the current repo. Then we can start testing and reviewing. He will announce the update on the mailing list. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-27/fedora-server.2024-11-27-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-27/fedora-server.2024-11-27-18.00.log.html[Full log] -// -* __**Actions summary**__ -. @jflory7 due:2024-12-04 Import mowest's LimeSurvey survey into the Fedora LimeSurvey instance and set it to public -. mowest and pboy will write in FedMag article in time with the poll planning -. eseyman will post on the mailing list inviting people to fill out the survey when the poll is online - - - - -//========================================================== -Wednesday, November 20, 2024:: - -* __**Essentials at a glance**__ - -** *Future release testing procedures* -+ -*AGREED* pboy writes the draft of a document that describes our test strategy. - - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-20/fedora-server.2024-11-20-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-20/fedora-server.2024-11-20-18.00.log.html[Full log] - - -//========================================================== -Wednesday, November 13, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *KVM image migration to KIWI* -+ -AGREED: The KVM image will be migrated to KIWI now, the adjustment of the naming will de dealt with later together with the isos. - -** *PostgreSQL – is our automatic testing sufficient?* -+ -No decision yet. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-13/fedora-server.2024-11-13-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-13/fedora-server.2024-11-13-18.00.log.html[Full log] -// -* __**Actions summary**__ -. ON HOLD pboy will file an issue with releng regarding installation media -. ONGOING pboy will close bug #2247872 (https://bugzilla.redhat.com/show_bug.cgi?id=2247872) -. ONGOING pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification -. ONGOING jwhimnpel will develop a Ansible playbook for NFS service -. PENDING eseyman review John's playbooks -. DONE eseyman will monitor the change list for possible issues which may affect Server -. DONE mowest will reach out to AdamW and discuss how we can use the result tables. -. DONE pboy will create a tracking issue and copy the table of F 40 as a starting point. -. DONE Mowest will create a Lime survey version of the discussed draft and reach out to Justin to put the project forward. -. PENDING Mowest will write a 1st draft of an article about our poll. - - -//========================================================== -Wednesday, November 06, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *New Anaconda installer for Server* -+ -In F42, only workstation will benefit from the new Anaconda WEB UI. Before Server can use it, a lot of missing functionality remains to get developed. Workstation will switch to RDP instead of VNC. For remote interactive installation, on the kernel line the parameter inst.vnc is replaced by inst.rdp. - -** *Current status and further advancement of server docs* -+ -Thanks to Paul Maconi we have our first entry in the "Fedora Server in a virtualized runtime environment" project about https://docs.fedoraproject.org/en-US/fedora-server/virtualization/vm-install-diskimg-proxmox/[installing on Proxmox]. Emmanuel will review. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-06/fedora-server.2024-11-06-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-11-06/fedora-server.2024-11-06-18.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - -//========================================================== -Wednesday, October 30, 2024:: - -* __**Essentials at a glance**__ - -** *Follow-up actions & announcements* -+ -ACTION: Mowest will write a 1st draft of an article about our poll. - -** *Ansible assisted installation and configuration of NFS service* -+ -NFS 4 is working now, NFS server is running, as well as NFS client. Both need some tweaking. -+ -AGREED Regarding Ansible / NFS we will study and test what we have and continue on meeting in 2 weeks. - -** *Looking back at testing release 41* -+ -AGREED: We discuss this during the next 2-3 weeks on mailing list and try to determine a final plan. One issue to take into account is the lack of test equipment. - -** *Current membership status and clean up process* -+ -Our official current list is here: -+!link https://fedoraproject.org/wiki/Server -+ -We have 7 members that never showed even up for the last 2 years. Qur usual procedure is to contact them and ask, what they are planning. And perhaps agree to retreat. And then we should take an initiative to get 1-2 new members. Maybe as part of our upcoming poll. -+ -AGREED: pboy will start to contact dormant members. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-30/fedora-server.2024-10-30-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-30/fedora-server.2024-10-30-17.00.log.html[Full log] - -* __**Actions summary**__ -. Mowest will write a 1st draft of an article about our poll. -//. action 2 - - - - -//========================================================== -Wednesday, October 23, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Testing Release 41* -+ -After a short reading break postponed to next meeting. - -** *Server user poll* -+ -Justin joined us and made an appointment with Mowest to take things further. So we'll be able to start soon. -+ -AGREED: We finally use the version as now online, i.e. without an "other" option for "How are you using Fedora Server?" - -** *New Business: Generation of the Server KVM image* -+ -LINK: https://pagure.io/fedora-server/issue/146 -+ -With release 42 we will switch to KIWI. ImageFactory is no longer support nor available at all. Current efforts: -+ -LINK https://koji.fedoraproject.org/koji/taskinfo?taskID=125070598 -+ -AGREED:Server WG agrees to switch to KIWI (4:0:0) - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-23/fedora-server.2024-10-23-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-23/fedora-server.2024-10-23-17.00.log.html[Full log] - -* __**Actions summary**__ -. DONE: pboy will write an updated summary about our release 4 testing and we continue on mailing list and next meeting. -. DONE: pboy will write a summary of the current state of our poll on the mailing list and we continue on mailing list and next meeting. - -//========================================================== -Wednesday, October 16, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Testing Release 41* -+ -We agree that manual testing of our installation media and procedures is necessary, and some of this is already included in the test plans. Furthermore, it would be desirable to tailor the test announcement for servers more closely to server issues. -+ -ACTION: pboy will write an updated summary about our release 4 testing and we continue on mailing list and next meeting - -** *Server user poll* -+ -Mowest has requested access to the Fedora Limesurvey instance through Gitlab. Furthermore, he created a draft of our survey in a free account of Limesurvey (https://mowest.limesurvey.net/778249?lang=en). -+ -ACTION: pboy will write a summary of the current state of our poll on the mailing list and we continue on mailing list and next meeting. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-16/fedora-server.2024-10-16-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-16/fedora-server.2024-10-16-17.00.log.html[Full log] -// -* __**Actions summary**__ -. pboy will write an updated summary about our release 4 testing and we continue on mailing list and next meeting. -. pboy will write a summary of the current state of our poll on the mailing list and we continue on mailing list and next meeting. - - -//========================================================== -Wednesday, October 02, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Testing Release 41* -+ -We still have to test installation on SBCs. Eseyman will take this on. - -** *Server user poll* -+ -Mowest had no success yet in pushing the poll through the other Fedora instances. We can't make any progress in the current state without that. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-02/fedora-server.2024-10-02-17.01.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-10-02/fedora-server.2024-10-02-17.01.log.html[Full log] - - -//========================================================== -Wednesday, September 25, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Server user poll* -+ -We decided to use the current version with all inserted modifications and with the shorter of the formulated alternatives on https://hackmd.io/@pboy/ByguCouphC[hackmd.io]. -+ -Mowest will create a Lime survey version of the discussed draft and reach out to Justin to put the project forward. - -** *Testing Release 41* -+ -We agreed to continue the discussion on the mailing list due to running out of time here. *See* https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/ODISTPROLKECRXX73LA5VUVZJFIFEHRR/[*pboy: Improving our release testing efforts. An attempt to summarize our discussion*] - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-09-25/fedora-server.2024-09-25-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-09-25/fedora-server.2024-09-25-17.00.log.html[Full log] - -* __**Actions summary**__ -. *ONGOING*: eseyman will monitor the change list for possible issues which may affect Serve -. *New*: Mowest will create a Lime survey version of the discussed draft and reach out to Justin to put the project forward. - - -//========================================================== -Wednesday, September 18, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Testing Release 41* -+ -The discussion focused on optimizing our approach to release testing. There was agreement on the one hand that the test program should be integrated into the distribution QA, and on the other hand that tests of individual functionalities should be automated. Irrespective of this, there is a need for manual testing, particularly of the (hardware) installation media. -+ -Action: pboy will create a summary on the mailing list, which will be the basis for further discussion. - -** *Server user poll* -+ -We finally agreed on 4 goals: -+ -- Who is the audience for Fedora Server -- Where is Fedora Server primarily used: Hardware or VM -- What are the main use cases for Fedora Server -- Where are future efforts of the Fedora Server WG best applied -+ -A final version is to be decided at the next meeting. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-09-18/fedora-server.2024-09-18-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-09-18/fedora-server.2024-09-18-17.00.log.html[Full log] -// -* __**Actions summary**__ -. *ACTION*: *ONGOING* eseyman will monitor the change list for possible issues which may affect Server -. *ACTION*: *DONE* mowest will reach out to AdamW and discuss how we can use the result tables. - - -//========================================================== -Wednesday, September 04, 2024:: - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -Jwhimpel has finished a first version of the Ansible code including a short documentation. We will discuss this in detail at the next meeting when all members have been able to test it. - -** *Testing Release 41* -+ -Ticket #144 is available for the test. Based on a discussion with adamw, pboy will create a draft test description in the Fedora Server Wiki area. The aim is to automate as much as possible. -+ -Eseyman has created a list of potentially problematic changes, see addendum to the invitation. The list will also be added to the ticket. We will discuss it at the next meeting. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-09-04/fedora-server.2024-09-04-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-09-04/fedora-server.2024-09-04-17.00.log.html[Full log] - -* __**Actions summary**__ -. *ACTION*: *ONGOING* eseyman will monitor the change list for possible issues which may affect Server -. *ACTION*: *DONE* pboy will create a tracking issue and copy the table of F 40 as a starting point. -. *ACTION*: *ONGOING* mowest will reach out to AdamW and discuss how we can use the result tables. - - -//========================================================== -Wednesday, August 28, 2024:: - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -The server roles are basically working. Jwhimpel will add some documentation how to use (and test) it. There are some topics we will have to decide after everyone could use it, e.g. type of mounts. On the client side, we tend to only support and handle Fedora. - -** *Testing Release 41* -+ -We decided to use the same procedure as last time (F40) for now. -+ -*ACTION*: eseyman will monitor the change list for possible issues which may affect Server -+ -*ACTION*: pboy will create a tracking issue and copy the table of F 40 as a starting point. -+ -We want to systematize the process and make greater use of the Fedora options, e.g. the results tables that are created for each build. -+ -*ACTION*: mowest will reach out to AdamW and discuss how we can use the result tables. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-08-28/fedora-server.2024-08-28-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-08-28/fedora-server.2024-08-28-17.00.log.html[Full log] -// -* __**Actions summary**__ -. *ACTION*: *DONE* pboy will create 2 empty docs for installation & configuration to the repo, then everyone can add relevant topics to it and migrate the current integrated doc. -. *ACTION*: *DONE* pboy will add all WG core members as committers to our pagure repo. -. *ACTION*: eseyman will monitor the change list for possible issues which may affect Server -. *ACTION*: pboy will create a tracking issue and copy the table of F 40 as a starting point. -. *ACTION*: mowest will reach out to AdamW and discuss how we can use the result tables. - - -//========================================================== -Wednesday, August 21, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Follow-up, findings and conclusions from Flock 2024* -+ -Eseyman gave an https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/thread/ZFEQZHECF4DNJA3VH4UIGGITRLFCXKFH/[overview of his impressions and experiences]. -+ -One wish that was expressed was to use Fedora as a router, similar to OpenWRT. It was agreed that this is not possible within the framework of Fedora Server, as the requirements for system and data security are too different. -+ -One positive feedback was that Fedora was the slowest moving as well as the most backward compatible, and nevertheless with always up-to-date versions of the server software bits, of the Fedora project. A most welcome characteristic of our goals for Fedora Server Edition. - -** *Optimizing NFS service documentation* -+ -jwhimpel will start to add topics the the empty doc templates when he completed the first version of the Ansible code. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-08-21/fedora-server.2024-08-21-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-08-21/fedora-server.2024-08-21-17.00.log.html[Full log] - -* __**Actions summary**__ -. *DONE* eseyman will post Flock recap to the list. -. *DONE* jednorozec will implement the patch to bug #2247872 - - -//========================================================== -Wednesday, August 14, 2024:: - -* __**Essentials at a glance**__ - -** *Follow-up, findings and conclusions from Flock 2024* -+ -We considered a number of different topics that were discussed. By and large, our current course in the further development of Fedora Server Edition has proven itself. The most important change will be the implementation of Ansible for our special supported services (previous server roles). -+ -Everyone agrees that getting to know each other and discussing goals and next steps in person was a hugely positive experience and a tremendous motivational boost.Nothing else can replace that. Flock was very, very worthwhile and all the effort was very rewarding. Flock next year is already a positive expectation. -+ -*ACTION*: eseyman will post his Flock recap to the list. - -** *Ansible assisted installation and configuration of NFS service* -+ -We decided to do the development in stg branch and add the directory structure there, too. -+ -*AGREED*: Regarding distribution we prefer the rpm path of action. -+ -*ACTION*: eseyman review John's playbooks - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-08-14/fedora-server.2024-08-14-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-08-14/fedora-server.2024-08-14-17.00.log.html[Full log] - -* __**Actions summary**__ -. *ONGOING* pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification -. *PENDING* pboy will create a hackmd draft for a collection of questions about Fedora Server in a virtualized environment -. *PENDING* mowest will come up with a plan and steps to conduct the survey on discussion – waiting for a draft of collection of questions -. *NEW* jednorozec will implement the patch to bug #2247872 - - -//========================================================== -Wednesday, July 31, 2024:: - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -We discussed again about the specific goal we want to achive with the Ansible Playbook. -+ -*AGREED* Server WG agrees to the goal as defined in comment https://pagure.io/fedora-server/issue/138#comment-920322 to issue 138 - -** *Optimizing NFS service documentation* -+ -We want to split the current NFS draft in 2 parts: Installation and Configuration. -+ -*ACTION* __**DONE**__: pboy will create 2 empty docs for installation & configuration to the repo -+ -*AGREED* to postpone this until we have a working version of the Ansible playbook. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-31/fedora-server.2024-07-31-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-31/fedora-server.2024-07-31-17.00.log.html[Full log] - -* __**Actions summary**__ -. *DONE* pboy will add all WG core members as committers to our pagure repo. -. *DONE* pboy will create 2 empty docs for installation & configuration to the repo -. *CANCELED* pboy will close bug #2247872 (https://bugzilla.redhat.com/show_bug.cgi?id=2247872) – There is still an ongoing discussion about improving Server first boot process. -. *ONGOING* pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification - - -//========================================================== -Wednesday, July 24, 2024:: - -* __**Essentials at a glance**__ - -** *Renaming distribution media for Fedora Server* -+ -*AGREED*: We defer the renaming until RelEng has decided about the future Fedora tool set AND has updated the documentation. -+ -*ACTION*: __**canceled**__ pboy will file an issue with releng regarding installation media - -** *Ansible assisted installation and configuration of NFS service* -+ -Eseyman has packed the the robertdebock roles in an rpm : https://eseyman.fedorapeople.org/ansible-robertdebock-roles/. It's an alternative to the current Fedora standard package. Jwhimple has 4 roles ready, but can't upload due to permission issues and incomplete Server repo configuration. -+ -*ACTION*: pboy will add all WG core members as committers to our pagure repo. - -** *Optimizing NFS service documentation* -+ -We want to split the current NFS draft in 2 parts: Installation and (Basic) Configuration. Jwhimpel will start do add at löeast bullet point to outline the intended information. To support this, pboy will add correspoding empty files. We agreed to document the process using Ansible and by using manually CLI. Whether and how we take Cockpit into account is still to be decided. -+ -*ACTION*: pboy will create 2 empty docs for installation & configuration to the repo, then everyone can add relevant topics to it and migrate the current integrated doc. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-24/fedora-server.2024-07-24-16.10.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-24/fedora-server.2024-07-24-16.10.log.html[Full log] - -* __**Actions summary**__ -. *ACTION*: __**new**__ pboy will add all WG core members as committers to our pagure repo. -. *ACTION*: __**new**__ pboy will create 2 empty docs for installation & configuration to the repo, then everyone can add relevant topics to it and migrate the current integrated doc. -. *ACTION*: __**canceled**__ pboy will file an issue with releng regarding installation media - - -//========================================================== -Wednesday, July 17, 2024:: - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -Discussed the specific goal of this work. Agreed to focus on a playbook for commen/default use case and provide hooks to extend to further local use cases. - -** *Fedora Server in a virtualized runtime environment* -+ -We agreed to start with a poll and ask users how they use Fedora Server Edition and what they are missing in the first place. Mowest and pboy will work on it. - - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-17/fedora-server.2024-07-17-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2023-11-15/fedora-server.2023-11-15-18.00.log.html[Full log] -// -* __**Actions summary**__ -. ACTION: pboy will create a hackmd draft for a collection of questions about Fedora Server in a virtualized environment -. ACTION: mowest will come up with a plan and steps to conduct the survey on discussion - - -//========================================================== -Wednesday, July 10, 2024:: -+ - -* __**Essentials at a glance**__ -+ -We had an open discussion about ongoing activities. - -** Humaton started to check out Kiwi to create Server iso distributables. There is a SuSE add-on to achieve that. -** Humaton will care about ticket #114, which is an undecided long standing issue regarding LLMR. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-10/fedora-server.2024-07-10-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-10/fedora-server.2024-07-10-17.00.log.html[Full log] - - -//========================================================== -Wednesday, July 03, 2024:: -// optional general message - -* __**Essentials at a glance**__ - -** *Change to a weekly meeting schedule* -+ -*AGREED*: Server WG switches to a _weekly meeting_ - -** *Ansible assisted installation and configuration of NFS service* -+ -jwhimnpel will provide 2 Ansible roles in about 2 weeks for further discussion and testing. -+ -eseyman and mowest will work on improving the current docs draft. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-03/fedora-server.2024-07-03-17.01.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-07-03/fedora-server.2024-07-03-17.01.log.html[Full log] -// -* __**Actions summary**__ -. pboy will file an issue with releng regarding installation media - pending -. pboy will close bug #2247872 - pending because of ongoing work -. pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification - ongoing -. jwhimpel will provide 2 Ansible roles for NFS service -. eseyman and mowest will start reviewing the currnt NFS doc draft - - - - -//========================================================== -Wednesday, June 26, 2024:: -+ -// optional general message -* __**Essentials at a glance**__ -+ -We had an open discussion about our various ongoing works. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-26/fedora-server.2024-06-26-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-26/fedora-server.2024-06-26-17.00.log.html[Full log] - - - - -//========================================================== -Wednesday, June 19, 2024:: -+ -// optional general message - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -We discussed the results of a short poll about the documentation part and how to improve the current article. Amoung others we want to split into installation and configuration and in each part describe the manual procedure and the Ansible usage. -+ -We will add a new subdirectory to our repo for Ansible scripts. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-19/fedora-server.2024-06-19-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-19/fedora-server.2024-06-19-17.00.log.html[Full log] -// -* __**Actions summary**__ -. *Action*: pboy will create an additional directory fedora-ansible in fedora-server repo -//. action 2 - - - - -//========================================================== -Wednesday, June 12, 2024:: -+ -// optional general message - -* __**Essentials at a glance**__ - -** *Elevating Fedora Server VM distribution image* -+ -Jason will start to elevate Fedora Server VM distribution image to a release requirement as the other Server installation images - - -** *Fixing the "Everything" installation medium problem* -+ -*AGREED*: Server WG agrees that the Fedora Server option has to be removed from the Everything Install medium in the long term. -+ -W'll pick this up again as soon as we have free resources. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-12/fedora-server.2024-06-12-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-12/fedora-server.2024-06-12-17.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - - - - -//========================================================== -Wednesday, June 05, 2024:: -+ -// optional general message - -* __**Essentials at a glance**__ - -** *Fedora Server goal(s) and "story" for F41 / F42* -+ -*AGREED*: WG's goal is to provide a spin "local or public file server (NFS, Samba, Ansible support) -+ -*AGREED*: WG's goal is to improve the use of Fedora Server in a VPS infrastructure and to promote it as a standard offering. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-05/fedora-server.2024-06-05-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-06-05/fedora-server.2024-06-05-17.00.log.html[Full log] - -* __**Actions summary**__ -. *Action*: pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification. -//. *Action*: action 2 - - - - - -//========================================================== -Wednesday, May 01, 2024:: -+ -// optional general message - -* __**Essentials at a glance**__ - -** *Revisiting Server installation media naming convention* -+ -*AGREED*: Server WG decides to rename the installation media: DVD -> offline , netboot -> online, KVM -> virt, and rawsbc for ARM raw image. -+ -*AGREED*: Server WG decides on a consistent naming convention according to the scheme: "Fedora-Server----." - -** *Elevating Fedora Server VM distribution image* -+ -jwhimpel will check the details of the procedure and report back next meeting. - -** *Open Floor* -+ -We will start to discuss and develop NFS service supported by documentation and by Ansible. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-05-01/fedora-server.2024-05-01-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-05-01/fedora-server.2024-05-01-17.00.log.html[Full log] -// -* __**Actions summary**__ -. *Action*: pboy will file an issue with releng. -//. action 2 - - - - - -//========================================================== -Wednesday, Apr 17, 2024:: -+ -// optional general message - -* __**Essentials at a glance**__ - -** *LVM2 configuration & ARM SBC installation* -+ -The issue is resolved, but but - as Vojtech Trefny, one of ghe maintgainers, put it - "unfortunately not thanks to the changes that I made". -+ -*AGREED*: Server WG considers the case closed. - -** *Testing F40* -+ -*AGREED*: Server WG considers F40 ready for publication and closes this topic. - -** *Our "story" for F40* -+ -*AGREED*: Regarding our "story" for F40 we stick sich ARM SBC. - -** *Our "Fedora Server goal(s) and "story" for F41 / F42* -+ -See: https://pagure.io/fedora-server/issue/134[issue #134] -+ -We narrowed the options down to "Fedora Server VM as VPS", "Server Edition as identity server ", and "Server Edition as local or public file server ". - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-17/fedora-server.2024-04-17-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-17/fedora-server.2024-04-17-17.00.log.html[Full log] - -* __**Actions summary**__ -. *Action*: pboy will close https://bugzilla.redhat.com/show_bug.cgi?id=2247872[bug #2247872] -//. action 2 - - - - - -//========================================================== -Wednesday, Apr 03, 2024:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Review installation media* -+ -The discussion revealed obvious inconsistencies between the ways of creating our various installation media that have evolved over time. All of this is difficult to deal with in a matrix discussion. Therefore: -+ -*AGREED*: An additional meeting out of turn on Wednesday, April 10, 17:00 UTC in the Matrix Sever room exclusively to discuss the Review Installation Media topic. -+ -*ACTION*: pboy will prepare the room and provide a test opportunity. - - -** *Testing F40* -+ -No additional issues found yet, but not all planned tests have been carried out yet. -+ -It is unclear how and where the test results should be merged on the server test page. Pboy will contact Adam about this. - - -** *Revisiting Server installation media naming convention* -+ -The online/offline proposal is welcomed, but the overall solution should be presented more clearly. -+ -A decision will be aimed for by mid-May at the latest so that there is sufficient time for implementation. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-03/fedora-server.2024-04-03-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-04-03/fedora-server.2024-04-03-17.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - - - - -//========================================================== -Wednesday, Mar 20, 2024:: - - -* __**Essentials at a glance**__ - -** *Follow-up actions & announcements* -+ -*** We will first discuss a possible change to the time of our meetings on the mailing list and decide at the next meeting. - - -** *LVM2 configuration* -+ -!link https://bugzilla.redhat.com/show_bug.cgi?id=2247872 -+ -The /etc/lvm/devices directory in Fedora-Server-KVM-40_Beta-1.9.x86_64.qcow2 is empty now. So far no check whether First Boot generates a suitable entry. -+ -*INFO update*: Beta 1.10 contains a devices file in both server images (KVM and aarch64 SBC). So the issue is not resolved yet. -+ -Action: cooltshirtguy will monitor and check the aarch64 SBC image, specifically Raspberry Pi. - - -** *F40 release tests* -+ -We have selected items to be tested and allocated work. Details at -+ -!link https://pagure.io/fedora-server/issue/125/ - - -** *Open Floor* -+ -*!info*: Unfortunately, no movement on the Apache / httpd configuration layout yet - - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-03-20/fedora-server.2024-03-20-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-03-20/fedora-server.2024-03-20-17.00.log.html[Full log] - - - - - -//========================================================== -Wednesday, Mar 06, 2024:: - - -* __**Essentials at a glance**__ - -** *Follow-up actions & announcements* -+ -We are discussing how to equalize the times of the meetings of the Server WG and the Epel Team to enable everyone to participate in both. To be continued on the mailing list. - -** *Review installation media* -+ -An initial analysis has revealed a number of warning messages about comps files not being found. Details in: -+ -Link: https://pagure.io/pungi-fedora/blob/main/f/variants-fedora.xml#_46 -+ -Link: https://pagure.io/fedora-server/issue/130 -+ -_Agreed_: Sever WG will check the current compose groups in issues on fedora-server repo. - - -** *LVM2 configuration & ARM SBC installation* -+ -The arm-image-installer script is fixed. -+ -The LVM configuration issue is still open. -+ -Link: https://bugzilla.redhat.com/show_bug.cgi?id=2247872#c19 -+ -This issue is not accepted as release blocker. So it can happen that we release a kind of crap image for the 2nd time in a row. -+ -But LVM group seems to be working hard on it. - - -** *F40 Change Set items requiring our attention* -+ -Eseyman generated a list of items requiring our attention -+ -Link: https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject.org/message/CNH57V7LT4GMQN676XFDJWQ6U46BGDMK/ -+ -_Agreed_: Server WG will continue to discuss this topic on mailing list - - -** *Open Floor* -+ -Nothing to discuss today. - - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-03-06/fedora-server.2024-03-06-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-03-06/fedora-server.2024-03-06-18.00.log.html[Full log] - - - - -//========================================================== -Wednesday, Feb 21, 2024:: -+ -Our first meeting on Matrix. - -* __**Essentials at a glance**__ - -** *Review installation media* -+ -We are trying here for more then 2 years for now without a lot or results. -At Fosdem I met Tomáš, who is very experienced in release engineering (to put it a bit understated) and who has offered to help us with this. This is a great opportunity for Fedora Server Edition. -+ -After an initial discussion about necessary and desired changes, we agreed that Tomáš would further analyze the current configuration files and compile them in a blog or on the server list. - -** *Revisiting Server installation media naming convention* -+ -The various server installation media are (still) named very differently. But it is now too late for a change to Release 40. -+ -_Agreed_: We further discuss naming convention on mailing list and aim to make a final decision in 4 weeks latest. And then it is up to releng to find a workable timeframe. There is no urgency. - - -** *LVM2 default configuration change* -+ -The issue is currently not resolved. -+ -A proper resolution will involve an anaconda fix as well as a fix in arm-image-installer. We will continue to work on it. -+ -Link: https://bugzilla.redhat.com/show_bug.cgi?id=2258764 - -** *Open Floor* -+ -Cloud Sig will stop to maintain ImageFactory. For F41 we have to select another tool for building the non-iso images. Probable choices are Lorax, KIWI, or OSBuild, depending on what is supported in pungi and what artifacts are supported by the different tools. -+ -Neil would support a move to Kiwi if we decide to do so. We want to make a final decision once releng has decided on available and supported options. - - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-21/fedora-server.2024-02-21-18.03.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2024-02-21/fedora-server.2024-02-21-18.03.log.html[Full log] - - - - -//========================================================== -Wednesday, Feb 07, 2024:: -+ -Continuing the Jan 31 meeting - -* __**Essentials at a glance**__ - -** *LVM2 default configuration change* -+ -We finally got information about the reasons for the changes in LVM default configuration and proper ways to resolve the ARM SBC installation issue. -+ -In short we should retain the current default LVM configuration which includes a system.devices file and adjust the arm-image-installer script und our documentation. - -** *Test planning for F40* -+ -We have set up a https://hackmd.io/NtO4O9vRT3a71UMZMkceoA?both[list of manually "smoke tests"]. We now need working group members or other interested parties to take over some of the tests and enter their FAS names in the corresponding column. - -** *Open Floor* -+ -We will switch our meetings from IRC to Matrix starting February 21, provided we can make the necessary organizational arrangements in time. - -* https://meetbot.fedoraproject.org/fedora-meeting/2024-02-07/fedora-server.2024-02-07-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2024-02-07/fedora-server.2024-02-07-18.00.log.html[Full log] - -* __**Actions summary**__ -. eseyman will check the change proposal set for items we should aware of and care about. - - -//========================================================== -Wednesday, Jan 31, 2024:: - -* __**Essentials at a glance**__ - -** *LVM2 default configuration change* -+ -Currently the default LVM configuration results in vgscan and vgchange not inspecting new devices that are not listed in /etc/lvm/devices/system.devices. A follow-up to this is also the error when creating aarch64 SBC filesystem images. -+ -There was neither a change proposal nor a release notes entry for the configuration change, nor any announcement. Accordingly, it is also not known why the change was made. -+ -*ACTION*: eseyman will try to contact the maintainers and get information why the change was made. - -** *Test planning for F40* -+ -We will continue discussion next meeting - -** *A "story" for each release* -+ -We will continue discussion next meeting - -* https://meetbot.fedoraproject.org/fedora-meeting/2024-01-31/fedora-server.2024-01-31-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2024-01-31/fedora-server.2024-01-31-18.00.log.html[Full log] - -* __**Actions summary**__ -+ -New business - -. pboy will create a thread on mailing list to discuss the option for LVM fix. -. jwhimpel will try to contact linux-lvm@lists.linux.dev -. pboy will create a draft wiki page to help to organise and coordinate our release testing efforts. - - - -//========================================================== -Wednesday, Jan 17, 2024:: - -* __**Essentials at a glance**__ - -** *LVM configuration issues* -+ -Currently the default LVM configuration results in vgscan and vgchange not inspecting new devices that are not listed in /etc/lvm/devices/system.devices. A follow-up to this is also the error when creating aarch64 SBC filesystem images. -+ -There was neither a change proposal nor a release notes entry for the configuration change, nor any announcement. Accordingly, it is also not known why the change was made. -+ -*ACTION*: eseyman will try to contact the maintainers and get information why the change was made. - -** *Test planning for F40* -+ -We will continue discussion next meeting - -* https://meetbot.fedoraproject.org/fedora-meeting/2024-01-17/fedora-server.2024-01-17-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/fedora-meeting/2024-01-17/fedora-server.2024-01-17-18.00.log.html[Full log] - -* __**Actions summary**__ -. pboy will write a info about changing the timeout value and nirik will review – still work in progress -. mowest will take care of discussed modifications of the Server download page. - still work in progress -. eseyman will try to contact the maintainers and get information why the change was made. diff --git a/wg/modules/ROOT/pages/wg-minutes-2025.adoc b/wg/modules/ROOT/pages/wg-minutes-2025.adoc deleted file mode 100644 index 267c961..0000000 --- a/wg/modules/ROOT/pages/wg-minutes-2025.adoc +++ /dev/null @@ -1,331 +0,0 @@ -= Meeting Minutes 2025 -Stephen Daley; Peter Boy -:page-authors: {author}, {author_2} -:page-aliases: wg-minutes-current.adoc - - -//========================================================== -//Wednesday, , 2025:: -//+ -// optional general message - -//* __**Essentials at a glance**__ - -//** *topic 1* -//+ -// - -//** *topic 2* -//+ -// - -//* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-01-18/fedora-server.2024-12-18-18.00.html[Meeting summary] -//* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-16/fedora-server.2025-04-16-17.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - -//========================================================== -Wednesday, May 07, 2025:: -+ -AGREED: we skip next meeting (May 14) - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -AGREED: We postpone the NFS Ansible project until eseyman has a robertdebock rpm ready and eseyman and jwhimpel have a proposal how to (re)use it for our purposes. - -** *Server user poll* -+ -Eseyman reported, he was pleasantly surprised. Lots of people seem satisfied with what we ship. The main call for improvement is documentation, use cases, best pratices, ... -+ -Eseyman and pboy will prepare a finer analyses of the data. - -** *Follow-up of the F42 server development and test cycle* -+ -AGREED: We try to create a Server Edition test day (or better test week) - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-05-07/fedora-server.2025-05-07-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-05-07/fedora-server.2025-05-07-17.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - -//========================================================== -Wednesday, April 23, 2025:: - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -ACTION: jwhimpel will create a Beta RPM that will establish the "base" filesystem and related documentation for our ansible setup (on admin's workstation) - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-23/fedora-server.2025-04-23-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-23/fedora-server.2025-04-23-17.00.log.html[Full log] - - -//========================================================== -Wednesday, April 16, 2025:: - -* __**Essentials at a glance**__ - -** *Follow-up of the F42 server development and test cycle* -+ -The final release actually no longer contains the possibility of a remote interactive installation initialized without terminal by kickstart file. This is the result of a system-wide switch from VNC to RDP initiated by the Workstation WG. The discontinuation is a side effect of the changes in Anaconda and was unannounced. We did not expect this omission and unfortunately discovered it too late. -+ -AGREED: We will create a list of minimal manual tests and try to establish a test week for F43. -+ -A particularly intensive checking require all changes that are in any way related to the Workstation WG. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-16/fedora-server.2025-04-16-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-16/fedora-server.2025-04-16-17.00.log.html[Full log] - - -//========================================================== -Wednesday, April 09, 2025:: -+ -Open discussion about the Ansible assisted installation and configuration of NFS service project. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-09/fedora-server.2025-04-09-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-09/fedora-server.2025-04-09-17.00.log.html[Full log] - - -//========================================================== -Wednesday, April 02, 2025:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Bug: Fedora 42: Server boot aarch64 image exceeds maximum size* -+ -There is a pending PR. -+ -ACTION: Paul Maconi (Aggraxis) will take care or the PR regarding the size change for aarch64 architecture. - -** *Status /progress Beta Testing* -+ -Testing so far revealed some minor issues. Really bad, the remote interactive installation doesn't work anymore with the kickstart file. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-02/fedora-server.2025-04-02-15.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-04-02/fedora-server.2025-04-02-15.00.log.html[Full log] - - -//========================================================== -Wednesday, March 26, 2025:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Bug: Fedora 42: Server boot aarch64 image exceeds maximum size* -+ -The reasons are obviously specific to the characteristics of aarch64 architecture. The x86_&4 version is not affected. -+ -AGREED: If the ongoing attempts to reduce the size are not successful, Server WG is in favor of an increase to 1.2 GB as an exception for now. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-26/fedora-server.2025-03-26-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-26/fedora-server.2025-03-26-17.00.log.html[Full log] - - - -//========================================================== -Wednesday, March 19, 2025:: - -* __**Essentials at a glance**__ - -** *Organisation of Beta Testing* -+ -Pboy will perform the hardware relataed testing, eseyman takes care of SBCs and jwhimpel of VM installation. We will track the results in an issue. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-19/fedora-server.2025-03-19-17.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-19/fedora-server.2025-03-19-17.00.log.html[Full log] - - -//========================================================== -Wednesday, March 12, 2025:: - -* __**Essentials at a glance**__ - -** *Announcements* -+ -During US daylight saving time, we adjust the beginning of our meeting to 17:00 UTC, so that local daily routines remain unchanged. - -** *Scheduled Server podcast for March 11* -+ -The podcast scheduled for yesterday was delayed, due to staff shortage. Mowest will try to join the new meeting together with pboy. - -** *Cockpit self-signed certificates change* -+ -AGREED: Server WG emphasizes that we need access without official certificates for private networks - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-12/fedora-server.2025-03-12-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-12/fedora-server.2025-03-12-18.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - -//========================================================== -Wednesday, March 05, 2025:: - -* __**Essentials at a glance**__ - -** *F43 Change proposal: Disabling support of building OpenSSL engines* -+ -Eseyman will track this. - -** *Open Floor* -+ -A review of the current state of the 'countme' statistics is to become a regularly recurring agenda item, approximately monthly or quarterly. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-05/fedora-server.2025-03-05-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-03-05/fedora-server.2025-03-05-18.00.log.html[Full log] -// -//* __**Actions summary**__ -//. action 1 -//. action 2 - - -//========================================================== -Wednesday, February 19, 2025:: - -* __**Essentials at a glance**__ - -** *Server user poll* -+ -AGREED: We will let the survey closed as decided before. - -** *Ansible assisted installation and configuration of NFS service* -+ -AGREED: Server WG will limit NFS support to NFS 4 - -** *Ansible assisted installation and configuration of WEB service* -+ -AGREED: We create a supported web service following the current description of a basic setup in the server docs. This is also the basis for developing an Ansible playbook. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-19/fedora-server.2025-02-19-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-19/fedora-server.2025-02-19-18.00.log.html[Full log] - - -//========================================================== -Wednesday, February 12, 2025:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Server user poll* -+ -We have a "brainstorming collection document" at https://hackmd.io/@pboy/SJzz7VcFJl. We agreed that everybody will enter their idea about data analysis and questions we try to answer by data analysis. -+ -Once the survey is complete, pboy will export the data in a secure form and make it available to interested WG members. - -** *Fedora Server Edition - homelab spin-off* -+ -AGREED Server WG decides to start work on a honelab / homeserver spin-off. - -** *FLOCK 2025* -+ -AGREED Eseyman, Mowest and Pboy will finalize suitable contributions to Flock 2025 on the basis of the current collection of ideas and submit the application(s). - - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-12/fedora-server.2025-02-12-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-12/fedora-server.2025-02-12-18.00.log.html[Full log] - -* __**Recent actions status change**__ -. eseyman DONE will post on redit forum, Fedora general user on Discussion, Fedora Devel on Discussion and the corresponding mailing lists about the next 2 weeks to participate -. pboy ONGOING will ping Abbra and the freeIPA / localKDC people to advice and help us to integrate the right thing into Fedora Server. - - - - -//========================================================== -Wednesday, February 05, 2025:: - -* __**Essentials at a glance**__ - -** *Server user poll* -+ -We currently have 4077 participants, of whom 548 have fully answered the survey. The others have left out several questions. We will continue to promote the poll. The currently scheduled end date is February 18. -+ -ACTION Emmanuel Seyman will post on redit forum, Fedora general user on Discussion, Fedora Devel on Discussion and the corresponding mailing lists about the next 2 weeks to participate -+ -AGREED mowest takes over the conduct and organization of the data analysis. Support from Gwmngilfen, Emmanuel, pboy and anyone who is interested - -** *FOSDEM 2025 & FLOCK 2025* -+ -At _Fosdem_ there was a discussion with abbra about freeIPA and localKDC (local Key Distribution Center) that is planned for F43. It may help us to resolve the UID issue with NFS. -+ -ACTION pboy will ping Abbra and the freeIPA / localKDC people to advice and help us to integrate the right thing into Fedora Server. -+ -Regarding _Flock_ we discussed several ideas for contribution. We will continue the discussion on the mailing list. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-05/fedora-server.2025-02-05-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-02-05/fedora-server.2025-02-05-18.00.log.html[Full log] - -* __**Actions summary**__ -. eseyman will post on redit forum, Fedora general user on Discussion, Fedora Devel on Discussion and the corresponding mailing lists about the next 2 weeks to participate -. pboy will ping Abbra and the freeIPA / localKDC people to advice and help us to integrate the right thing into Fedora Server. - - -//========================================================== -Wednesday, January 15, 2025:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Ansible assisted installation and configuration of NFS service* -+ -Nothing new so far. But we have a new issue to deal with, managing firewall portmapper port (111). - -** *Ansible assisted installation and configuration of WEB service* -+ -Nothing new so far. - -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-01-15/fedora-server.2025-01-15-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-01-15/fedora-server.2025-01-15-18.00.log.html[Full log] - - -//========================================================== -Wednesday, January 8, 2025:: -//+ -// optional general message - -* __**Essentials at a glance**__ - -** *Follow-up actions & announcements* -+ -Just for information see _Current Actions summary_ below. -+ -Fosdem runs from February 1-2. Fedora will be represented by a booth, eseyman and pboy will be there. - -** *Server user poll* -+ -The poll is open and running. We don't have any data on an interim result yet. - -** *Revisiting Fedora Server quality criteria and procedures* -+ -Because of the current issues with NFS which may take some tie to get resolved we open another path with https://docs.stg.fedoraproject.org/en-US/fedora-server/services/httpd-basic-setup/[web services]. - -** *Work program and goals* -+ -We postpone this until we have evidence of our server poll. -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-01-08/fedora-server.2025-01-08-18.00.html[Meeting summary] -* https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2025-01-08/fedora-server.2025-01-08-18.00.log.html[Full log] - -* __**Current Actions summary**__ -. ON HOLD pboy will file an issue with releng regarding installation media -. ONGOING pboy will close bug #2247872 (https://bugzilla.redhat.com/show_bug.cgi?id=2247872) -. ONGOING pboy will write a draft issue for the goal "file server" as a base for further finetuning and detailed specification -. ONGOING jwhimnpel will develop a Ansible playbook for NFS service -. PENDING eseyman review John's playbooks -. DONE Mowest will write a 1st draft of an article about our poll. -