Comment 4 for bug 1491895

Removing the logging all together within the containers for various services is a bad idea and not something that I'd recommend. Additionally, all of the logs are being shipped through the use or rsyslog within all containers and hosts. This gives direct log access to a deployer in a centralized location.Part of the rsyslog_client role is to also setup log rotation for all logs that its shipping. Again this is a pattern that I'm recommending we keep as its proven to be quite efficient and beneficial to large scale deployments. Now we might be able to figure out a better way to store the log (bind mount or otherwise) that would remove the issues with a container FS filling up. Note that this issue is unique to having a container backend type that is limits storage, IE BTRFS, LVM, ect... That said, OSA already can support deployments using the host rootfs and if this is an issue that is causing pain currently it may be best to start by enabling that capability or by making the logical volumes larger for the various containers already in service. Note that there are pros and cons for just about any approach however I'd be nice to have a real time conversation regarding what works best for the majority of deployers so that we can come up with the best solution.