Configure log output to `stdout` about gluster-kubernetes HOT 9 OPEN

@rporres It has to because we use systemd to launch and manage multiple processes in the mainline container images. I can get away with starting it in non-daemon mode because I get rid of systemd and just run them as background processes from a bash script.

from gluster-kubernetes.

@rporres Oh it most certainly does. I can run glusterd in non-daemon mode, but I'm not sure if that's enough to capture the logs from all the subprocesses it spawns. :/

from gluster-kubernetes.

All the glusterfs logs are made persistent on the host where the glusterfs containers are running. Path :/var/log/glusterfs

from gluster-kubernetes.

Ok, good to know :) But I would expect the logs on stdout, so kubectl logs could show them. I am also forwarding the output of all containers to a central logging server. So it would be cool if you could consider a change on that setting.

from gluster-kubernetes.

I guess that comes from the Docker image itself in https://github.com/gluster/gluster-containers... Docker run command in the example mounts log volume too.

I don't see that Gluster supports STDOUT logging in http://docs.gluster.org/en/latest/Administrator%20Guide/Logging/

from gluster-kubernetes.

@rporres It doesn't, but I've played some kinda nasty tricks to get it to log to stdout in my experimental containers. ;) Not sure if/when this will make it to the mainline containers, however.

from gluster-kubernetes.

That looks cool, @jarrpa. I started to think in doing something like that creating a link to /dev/stdout but stopped thinking in that direction when I saw that there are things like brick's logs that you won't know the name beforehand... I'm a total noob here but I have the impression that this is something that has to be addressed at an application level

from gluster-kubernetes.

Is there any reason why gluster is running in daemon mode, @jarrpa? I guess it is quite standard practice to do it in container processes...

from gluster-kubernetes.

@jarrpa +1000 for work towards a gluster container without systemd. We have ran into a number of systemd bugs with the gluster/gluster-containers images and would be very interested in using containerized gluster without it.

We would be willing to help and test if it can get support for this approach in the mainline.

from gluster-kubernetes.