As a administror that is experinced with managing services on a mondern systemd based operating system i expect the services deploy on a host to log to the systemd journald by default. when openstack is deploy on a rhel host i expect to use the same tool to view and manage the openstack service logs.

Podman now logs to the systemd journal by default upstream and i expect the same behavior for the standard out of contaienrs deployed as part of openstack. addtional as openstack supports direct logging to the journal i also expect openstack service logs to be logged to the journal.

As a cloud operator this will simplfy the set of services that are deploy by removeing the need for cron jobs to run logroatate on rhel managed hosts.

NOTE: this applies to all logs generaged by libvirt, ovs nova, neutron, ovn and any other service as part of the openstack contol/dataplane on EDPM hosts. it does not apply to logs generated by tenant workloads such as the qemu console which may have sensitive info and should not be collected in the journal.

In order to conform with GDPR requirements, EDPM nodes must have journald configurable to enforce retention of its log file via MaxRetentionSec. This should be done via edpm-ansible and optionally via BMH operator

Documentation impact: upgrade/adoption guides should mention the changed logs location