From 74cb4644646dd2aeea5d11076f40378b00c6afe9 Mon Sep 17 00:00:00 2001 From: Fabian Arrotin Date: Oct 18 2024 13:32:12 +0000 Subject: Removing decommissioned apps Signed-off-by: Fabian Arrotin --- diff --git a/docs/apps/bugs.md b/docs/apps/bugs.md index 4f9ba31..b4247f5 100644 --- a/docs/apps/bugs.md +++ b/docs/apps/bugs.md @@ -3,25 +3,13 @@ The CentOS project is using different trackers, based on which team needs to be in charge of the issue to solve. While we (CentOS Infra) are ourselves using the pagure.io one (hosted and maintained by Fedora), there is only one that we are hosting : bugs.centos.org. -## bugs.centos.org - -Hosted in CentOS infra. That's the first and legacy tracker that was deployed initially in the CentOS Project, to track all issues, software or infra related. - -The software stack is using : - - * [Mantis BT](https://mantisbt.org/) - * PHP (using SCL newer/higher php version to satisfy dependencies) - * MySQL - -The [ansible-role-mantisbt](https://github.com/centos/ansible-role-mantisbt) is used to deploy dependencies and include all needed roles but itself was never really configured to deploy the application itself (can be easily fixed though) but backup is taking care of application (php files) backup and so can be moved easily if needed (applying the role, restoring backup at proper location) - -!!! note - Worth knowing that because starting from Stream, all bugs will be reported to Bugzilla (see below) and that all infra tickets are also migrated to pagure.io, bugs.centos.org is called "legacy" and will probably be decommissioned soon - ## pagure.io/centos-infra Hosted by Fedora and used for infra tracker. Url is [https://pagure.io/centos-infra/issues](https://pagure.io/centos-infra/issues/) -## bugzilla +## Jira + +Hosted by Red Hat and used for *everything* related to CentOS Stream : -Hosted by Red Hat and used for *everything* related to CentOS Stream + * [CentOS Stream 9](https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12332745&issuetype=1&versions=12412761) + * [CentOS Stream 10](https://issues.redhat.com/secure/CreateIssueDetails!init.jspa?pid=12332745&issuetype=1&versions=12412762) diff --git a/docs/apps/forums.md b/docs/apps/forums.md deleted file mode 100644 index 4c4c644..0000000 --- a/docs/apps/forums.md +++ /dev/null @@ -1,13 +0,0 @@ -# CentOS Forums - -For legacy reasons, we host two different forums instances but still using the same tech stack/solution : - - * https://forums.centos.org (main one) - * https://fr.centos.org/forums (dedicated one to french language) - -The forum tech stack is just using [phpBB](https://www.phpbb.com/) with a MySQL DB -Worth knowing that it's almost the default phpBB stack and no real plugin added, and also meaning that (legacy) using the internal users DB, and so no SSO. - -The ansible role used to deploy the app is the [ansible-role-phpbb](https://github.com/centos/ansible-role-phpbb) - -To update between major release, we have a specific `adhoc-update-phpbb.yml` that can be used to update to a version (test this first on a test instance first) diff --git a/docs/apps/mailman.md b/docs/apps/mailman.md index 463d9c6..2d5d5d6 100644 --- a/docs/apps/mailman.md +++ b/docs/apps/mailman.md @@ -2,39 +2,12 @@ The CentOS Project hosts some public mailing lists that people can subscribe to. -It's hosted at [https://lists.centos.org](https://lists.centos.org) and on a sponsored node. - -Due to the fact that it was created (back in time decision) on the centos.org MX machine , the lists are using the `@centos.org` domain, and so mailman is hosted *on* the main centos [mailserver](/apps/mailservers/), reason why the postfix ansible role will have the `postfix_mailman` [variable boolean](https://github.com/CentOS/ansible-role-postfix/blob/master/defaults/main.yml#L80) set to `True`, as it will automatically create the `@centos.org` aliases on the host (needed to pass through mailman) +It's hosted at [https://lists.centos.org](https://lists.centos.org). Some links: - * [Upstream mailman 2](http://www.list.org/docs.html) documentation - * [mailman](https://github.com/centos/ansible-role-mailman) ansible role - -Worth knowing that to initially fight against spam registration, we added a [recaptcha](https://github.com/CentOS/ansible-role-mailman/blob/master/defaults/main.yml#L24) option to filter massive users registration. -You can find the applied patches (collaboration between Red Hat, Gnome and CentOS, all using the same applied patch for their mailman2 lists) in the mailman role - -The CentOS Theme (written by the Artwork SIG) is also pushed from ansible role and some elements can be modified through `mailman_html_tpl_{head,bodystart,bodyclose}` variables. (also all coming from the ansible mailman role - -## Some operations - -### Adding a new list for a project/SIG - -The Ansible mailman role supports adding lists automatically so it's just a matter of , through ansible inventory, adding new list to the `mailman_lists` ansible list variable with some parameters like : - - * name: the mailman list name - * description: list description appearing on mailman ui - * password: unique password for that list, as we can have specific operators for that list - * admin: the email address of the list owner - -Once pushed to git and applied by ansible, the new list will appear - -### Modifying lists settings - -If the setting you want to modify is one of the previously mentioned variables, updating in git/ansible would then trigger a reconfig with these settings. - -But some settings are just configured through mailman itself, so to modify these ones, you need either the `password` list (specific to that list), or the whole `mailman_admin_pass` (also called site password, that can be used to admin all lists) - -To do this, just browse the [mailman admin UI](https://lists.centos.org/mailman/admin), select your list and auth with the needed password. + * [Upstream mailman 3](https://docs.mailman3.org/en/latest/) documentation + * [mailman3](https://github.com/centos/ansible-role-mailman3) ansible role -You can then proceed with changes like, adding/removing subscribers, work with moderation queue, etc, etc .. +## Authentication +It's just relying on OpenIDC for authentication, as other services in centos infra, and so using https://id.centos.org as IdP (enrolled into Fedora IPA) diff --git a/docs/apps/wiki.md b/docs/apps/wiki.md deleted file mode 100644 index 1dc6eaa..0000000 --- a/docs/apps/wiki.md +++ /dev/null @@ -1,30 +0,0 @@ -# Wiki - -The CentOS [wiki](https://wiki.centos.org) is a place where people can contribute to some documentation/howtos and SIGs are also (some of them) write quick tutorials on how to install packages, etc - -The wiki engine is [moin](http://moinmo.in/) and is packaged and built through [infra SIG tags](https://cbs.centos.org/koji/packageinfo?packageID=6625) - -The [ansible-role-moin](https://github.com/centos/ansible-role-moin) ansible role is used to deploy/update/modify the existing wiki. - -Worth knowing that on the CentOS Wiki, the default ACL is to forbid people to write content : that measure that to be taken some years ago to fight against spammers. - -So the way to request edit permissions on the Wiki is to - - * register an account (wiki isn't tied to central SSO for now) - * send a mail to centos-docs list and ask edit right - -Some trusted users are added (through ansible) in the admins list, or directly in the Edit group (in moin) to have access everywhere. - -## Fighting with spammers - -As all wiki instances, ours is also attracting bots/spammers, adding really heavy load. -To fight against that , some measures are in place : - - * using the `surge` module option in moin (search for `moin_surge_*` settings in ansible) to limit number of requests one could do at the wiki level - * using iptables/ipset lists to block some known bots/ip ranges (see the `ansible-role-iptables` and the ipset lists defined at the host_vars level for that host - * Tuning the wsgi processes/threads at the apache level - * using the mod_qos apache module to also block requests - -## Backup - -Like for other roles, the `ansible-role-moin` one includes the [centos-backup](https://github.com/CentOS/ansible-role-moin/blob/master/tasks/main.yml#L154) role, so backing up daily the wiki data/instance, that is pulled from central backup server, itself rotating and exporting to another site/DC the rotated pool diff --git a/mkdocs.yml b/mkdocs.yml index 2161589..677b606 100644 --- a/mkdocs.yml +++ b/mkdocs.yml @@ -78,9 +78,7 @@ nav: - Duffy: - About: apps/duffy/index.md - apps/www.md - - apps/wiki.md - apps/bugs.md - - apps/forums.md - apps/mailman.md - apps/docs.md - apps/blog.md