Joshua Harlow has proposed merging
lp:~harlowja/cloud-init/cloud-init-file-logging into lp:cloud-init.
Requested reviews:
cloud init development team (cloud-init-dev)
For more details, see:
https://code.launchpad.net/~harlowja/cloud-init/cloud-init-file-logging/+merge/300798
It's less problematic to just depend on basic file logging to avoid syslog
patterns, syslog being active, syslog being useable as a core dependency of
getting debug logs and other from cloudinit.
--
Your team cloud init development team is requested to review the proposed merge
of lp:~harlowja/cloud-init/cloud-init-file-logging into lp:cloud-init.
=== modified file 'config/cloud.cfg.d/05_logging.cfg'
--- config/cloud.cfg.d/05_logging.cfg 2014-01-14 18:18:14 +0000
+++ config/cloud.cfg.d/05_logging.cfg 2016-07-21 18:01:22 +0000
@@ -54,13 +54,21 @@
log_cfgs:
# These will be joined into a string that defines the configuration
- - [ *log_base, *log_syslog ]
+#
+# If your desire syslog, just uncomment the following line.
+# - [ *log_base, *log_syslog ]
+#
# These will be joined into a string that defines the configuration
+#
+# Otherwise by default we just use the most basic (known to work
+# mechanism that does not depend on a system service to operate; which
+# due to cloud-init execution lifecycle we may not always be able to
+# depend on working correctly).
- [ *log_base, *log_file ]
-# A file path can also be used
+# A file path can also be used.
# - /etc/log.conf
-# this tells cloud-init to redirect its stdout and stderr to
+# This tells cloud-init to redirect its stdout and stderr to
# 'tee -a /var/log/cloud-init-output.log' so the user can see output
# there without needing to look on the console.
output: {all: '| tee -a /var/log/cloud-init-output.log'}
_______________________________________________
Mailing list: https://launchpad.net/~cloud-init-dev
Post to : cloud-init-dev@lists.launchpad.net
Unsubscribe : https://launchpad.net/~cloud-init-dev
More help : https://help.launchpad.net/ListHelp
