I had a discussion with Alexey. We proposed making the Fuel Master host system /var/log accessible directly inside the mcollective container, so that shotgun can access it more directly. To do this we should add the following lines in dockerctl config:
HOST_VOL['hostlogs']="-v /var/log:/log"
REQS["${HOST_VOL['hostlogs']}"]="mcollective"
This would allow us to make symlinks when copying files from a local source to reduce disk space requirements and use tar 'h' option to back up symlinks as files.
With regard to /var/log/docker-logs:/var/log references, we should keep that mapping in place so that IBP and normal mcollective tasks work correctly.
I had a discussion with Alexey. We proposed making the Fuel Master host system /var/log accessible directly inside the mcollective container, so that shotgun can access it more directly. To do this we should add the following lines in dockerctl config:
HOST_VOL[ 'hostlogs' ]="-v /var/log:/log"
REQS["$ {HOST_VOL[ 'hostlogs' ]}"]="mcollecti ve"
This would allow us to make symlinks when copying files from a local source to reduce disk space requirements and use tar 'h' option to back up symlinks as files.
With regard to /var/log/ docker- logs:/var/ log references, we should keep that mapping in place so that IBP and normal mcollective tasks work correctly.