IT Tickets issueshttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues2022-01-25T11:21:31+01:00https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/29Central User Management and SSO2022-01-25T11:21:31+01:00Andre LehmannCentral User Management and SSO**General Tasks:**
- [x] install and configure Keycloak
- [ ] install and configure OpenLDAP
- [x] setup admin accounts
- [ ] propose user, group and role structure
- [x] setup normal user accounts accounts
- [x] notify user about their...**General Tasks:**
- [x] install and configure Keycloak
- [ ] install and configure OpenLDAP
- [x] setup admin accounts
- [ ] propose user, group and role structure
- [x] setup normal user accounts accounts
- [x] notify user about their new user account
- [ ] configure user federation with LDAP
- [ ] setup permission structure
**Integrate Platforms:**
1. [x] Git Service (Gitlab)
2. [x] MariaDB Frontend (phpMyAdmin)
3. [x] Dashboard (Traefik)
4. [x] Pad (Hedgedoc) #50
5. [x] Blog (Wordpress)
6. [ ] Wiki (MediaWiki)
7. [ ] Cloud File Share (Nextcloud)
Handle Account Migration (Format: `SSO Account -> Plattform Account`)
- `foo -> ?`:
- Create platform account by impersonating the SSO account
- `foo -> foo`:
- Check if the owner of the SSO account is the same as the platform account
- migrate account to SSO
- `foo -> bar`:
- Check if the SSO account is the same as the platform account (match email)
- rename platform account and migrate to SSO
- `? -> qot`:
- user has no SSO account yet
- check if user is member of OSEG
- either create a SSO account or delete the platform accountMaintenance Cycle 2021-12Alexander StellmachAlexander Stellmachhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/30Distinct favicon for each web application2024-02-08T22:45:44+01:00Andre LehmannDistinct favicon for each web applicationNow that we have a couple of web applications running it might be nice, if we have a distinct favicon for each of the applications, so it is easier to navigate through open browser tabs. My idea is to combine the OSEG logo with a tiny lo...Now that we have a couple of web applications running it might be nice, if we have a distinct favicon for each of the applications, so it is easier to navigate through open browser tabs. My idea is to combine the OSEG logo with a tiny logo of the application software to make it distinct.
- [x] Create favicons and put them into a repository: https://gitlab.opensourceecology.de/server/favicons
- [ ] Install the favicons in the different web services
- [x] Blog: [Uploaded and set via customizer](https://kinsta.com/knowledgebase/wordpress-favicon/)
- [x] Website: green
- [ ] Cloud: blue, set via web interface, Error: `Exception: Argument 2 passed to OCA\Theming\ImageManager::setCachedImage() must be of the type string, null given, called in /container/www/apps/theming/lib/Controller/IconController.php on line 167`
- [x] GitLab: red, set via web interface
- [x] Wiki: grey, set via favicon.ico
- [x] Hedgedoc: black, favicon.ico mounted inside container
- [x] Etherpad: teal
- [x] Survey: yellow, favicon.ico mounted inside container (`/container/www/upload/themes/survey/erweitert_fruity/files`)
- [x] Forum: violet, favicon.ico mounted inside containerMaintenance Cycle 2021-09Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/51Create a Status Page for our Services2022-01-25T11:05:01+01:00Andre LehmannCreate a Status Page for our Services<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, ...<!---
PLEASE READ THIS!
This is the template for proposing a new FEATURE (new functionality). If your
intention is to report a bug or something else, please use the appropriate
template for that instead.
Before creating a new ticket, please search for existing tickets that match your
issue description, to avoid creating a duplicate.
--->
### Problem to solve
<!-- What problem do we solve? Try to define the who/what/why of the opportunity
as a user story. For example, "As a (who), I want (what), so I can (why/value)."
-->
A status page, to display the availability and maintenance status of all our public facing services would be quite beneficial. Users could inform themself about the current status before creating any ticket, when a service appears to be down.
### Intended users
<!-- Who will use this feature? It's okay to write "Unknown" and fill this field
in later. -->
- Administrators:
- get a quick glance about services status
- inform users about
- Users:
- get information about the service status
- check availability and maintenance status, before creating a ticket
### Proposal
<!-- How are we going to solve the problem? -->
There is a [nice list of open-source status page software](https://github.com/ivbeg/awesome-status-pages) we can test out.
### Tasks
- [x] Check the list of status page software and identify potential candidates
- [ ] Test the potential candidates and pick one of them
- [ ] Create a plan to deploy the software on our server
- [ ] Integrate the system
- [ ] Write documentationMaintenance Cycle 2021-12https://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/83Domainwechsel Wikibase2021-09-01T12:20:20+02:00Martin HäuerDomainwechsel WikibaseMit der Ausgliederung von OHO (#56 #57) geht uns auch die Subdomain `wikibase.oho.wiki` verloren.
Das Projekt um Wikibase (LOSH) wird künftig 2 (Sub)Domains benötigen:
- backend (Wikibase) → vorgeschlagene Subdomain: `wikibase.ose-germ...Mit der Ausgliederung von OHO (#56 #57) geht uns auch die Subdomain `wikibase.oho.wiki` verloren.
Das Projekt um Wikibase (LOSH) wird künftig 2 (Sub)Domains benötigen:
- backend (Wikibase) → vorgeschlagene Subdomain: `wikibase.ose-germany.de`
- frontend (voraussichtl. v. WMDE entwickelt, vermutlich Mediawiki-basiert)
Da die Wikibase-Instanz für das Projekt erreichbar bleiben sollte, wäre es gut, wenn wir die Subdomain vor der OHO-Domainübergabe umschalten.
Sofern wir das Frontend hosten möchten (#84), würde ich `losh.ose-germany.de` dafür reservieren wollen.Andre LehmannAndre Lehmannhttps://gitlab.opensourceecology.de/verein/koordination/it/tickets/-/issues/101Switch to Kubernetes2022-01-24T19:23:45+01:00Andre LehmannSwitch to KubernetesTo install and configure Kubernetes I would prefer to use [Kubespray](https://github.com/kubernetes-sigs/kubespray), a set of Ansible Playbooks curated by a quite big community. The configuration can be placed and versioned along with ou...To install and configure Kubernetes I would prefer to use [Kubespray](https://github.com/kubernetes-sigs/kubespray), a set of Ansible Playbooks curated by a quite big community. The configuration can be placed and versioned along with our other Playbooks.
- [ ] Create basic configuration
- [ ] Figure out how to use Traefik as an ingress controller
- [ ] Enable IPv6
- [ ] Create deployments for a few selected applications (like phpMyAdmin) for testing
- [ ] How to use bind mounts? (keeping the current method of handling storage)
- [ ] How to include Ansible as an automated deployment method? Gitlab-CI?Alexander StellmachAlexander Stellmach