Description Arvid Requate 2018-12-13 13:27:22 CET

We need Debian Packaging for the components of the Admin Diary, i.e. a source package univention-admindiary that generates binary packages like

 * univention-admin-diary-storage or univention-admin-diary-backend ?
 * python-univention-admin-diary-lib
 * python-univention-admin-diary-client

or some similar structure. The backend package should advertise a univentionService when it is joined into the domain, which allows clients to discover it.

+++ This bug was initially created as a clone of Bug #48341 +++

This bug is about creating the Python library code and database config that is necessary to *store* Events in the Admin Diary Backend. The idea is that this will be installed on a some system (chosen by customer) in an UCS domain by installing a Debian package, sth. like "univention-admin-diary-storage".

Project context:

The Admin Diary concept has these players:

* Event producer (Client/Source system)
* Event consumer (Server/Backend Storage)
* Diary GUI (UMC Module)

For the Admin Diary the UMC Frontend Module needs to be able to retrieve Events from a database located on some system in the domain (or possibly on two, in case of UCS@school). Let's call this Admin Diary Backend here. We have two options here, how the UMC frontend may access the data in the Admin Diary Backend: Either the UMC frontend directly connect to the Backend Storage Database, or the UMC frontend connects to an Admin Diary backend service (e.g. another UMC module without any GUI). The second approach would have the advantage to abstract from the particular Storage Database component (MariaDB/PostgreSQL).

Anyway, in the first step we should create a Python library for the Admin Diary Backend, which can be used to write Events to a Backend Database. These Events originate from arbitrary UCS systems in the domain, will be buffered locally on the source system and transferred to the remote database once the presence of an Admin Diary Backend service is advertised by some UCS system in the domain.

We need to provision a table in some database. The design should be so, that customers can choose (by setting some UCR variables) to e.g. use an existing MariaDB Cluster hosted on some (possibly non-UCS) server.