It would be very convenient if cloud-init provided a syslog logging configuration that was togglable via a USE flag. This would allow systems or providers that guarantee syslog's availability to simply integrate from the time of first boot or configuration. Reproducible: Always
If it includes a run-time configurable syslogging feature, then why would you want to completely re-emerge the package instead?
I don't want to re-emerge the package. I want to make it easier for cloud providers to use the syslog mechanism so that new fresh images have captured the cloud-init output using that facility.
(In reply to Alex Brandt from comment #2) > I don't want to re-emerge the package. I want to make it easier for cloud > providers to use the syslog mechanism so that new fresh images have captured > the cloud-init output using that facility. This appears to be a good case for use of a virtual package. Your 'wise' colleague suggests it ought be put behind a tailor made virtual package rather then a flag stipulating one specific syslog selected package. 'Luxury of choice'. virtual would mean that the package could depend on it via addition in DEPEND. This way, you get to choose your favoured syslog 'provider'. Well being the evangelist of all things 'cloud' as you are, and a pretty smart dev, 'we' expect you to knock it up in a flash, or at least inside the time of a few commercial breaks.
I have an ebuild ready for review that fixes not only this problem but adds systemd unit support among other minor updates. I have not yet run tests on the ebuild but will do that shortly. prometheanfire, can you review the changes in my overlay on the app-emulation/cloud-init branch and provide feedback before I add the ebuild to the tree and close this bug?
Tests don't pass on a clean install of cloud-init due to improper isolation of the SmartOS unit tests. I'll report an upstream issue to get these fixed in the next release but for now I think we can publish this updated ebuild. If no objections by Saturday I'll go ahead and push my -r2 to the tree.
Upstream bug report: https://bugs.launchpad.net/cloud-init/+bug/1358026
Does anyone have a problem with simply dropping the SmartOS tests on this particular release so the tests pass in this version?